EP3682564A1 - Schémas d'atténuation d'interférence pour des systèmes cellulaires en duplex intégral - Google Patents

Schémas d'atténuation d'interférence pour des systèmes cellulaires en duplex intégral

Info

Publication number
EP3682564A1
EP3682564A1 EP17924431.4A EP17924431A EP3682564A1 EP 3682564 A1 EP3682564 A1 EP 3682564A1 EP 17924431 A EP17924431 A EP 17924431A EP 3682564 A1 EP3682564 A1 EP 3682564A1
Authority
EP
European Patent Office
Prior art keywords
interference
enb
ues
traffic
boosting factor
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP17924431.4A
Other languages
German (de)
English (en)
Other versions
EP3682564A4 (fr
Inventor
Jingwen BAI
Shu-Ping Yeh
Yang-Seok Choi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
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 Corp filed Critical Intel Corp
Publication of EP3682564A1 publication Critical patent/EP3682564A1/fr
Publication of EP3682564A4 publication Critical patent/EP3682564A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/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
    • H04J—MULTIPLEX COMMUNICATION
    • H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
    • H04J11/0023—Interference mitigation or co-ordination
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/06—TPC algorithms
    • H04W52/14—Separate analysis of uplink or downlink
    • H04W52/146—Uplink power control

Definitions

  • aspects pertain to wireless communications. Some aspects relate to wireless networks including 3 GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Advanced) networks, and fifth-generation (5G) networks including new radio (NR) networks. Other aspects are directed to full duplex (FD) cellular systems and various interference mitigation (IM) schemes for FD cellular systems.
  • 3 GPP Transmissiond Generation Partnership Project
  • 3GPP LTE Long Term Evolution
  • 3GPP LTE-A Long Term Evolution Advanced
  • 5G fifth-generation
  • NR new radio
  • Other aspects are directed to full duplex (FD) cellular systems and various interference mitigation (IM) schemes for FD cellular systems.
  • FD full duplex
  • IM interference mitigation
  • Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device).
  • Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in an uplink (UL) transmission.
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • OFDM orthogonal frequency- division multiplexing
  • 3GPP third generation partnership project
  • IEEE Institute of Electrical and Electronics Engineers
  • 802.16 e.g., 802.16e, 802, 16m
  • WiMAX Worldwide interoperability for Microwave Access
  • IEEE 802. 1 1 Standard, which is commonly known to industry groups as WiFi.
  • E- UTRAN Evolved Universal Terrestrial Radio Access Network
  • UE user equipment
  • the DL transmission can be a communication from the eNB to the UE
  • the UL transmission can be a communication from the UE to the eNB.
  • data can be transmitted from the eNB to the UE via a physical downlink shared channel (PDSCH), and a physical uplink control channel (PUCCH) can be used to acknowledge that data was received.
  • PDSCH physical downlink shared channel
  • PUCCH physical uplink control channel
  • Downlink and uplink channels or transmissions can use time-division duplexing (TDD) or frequency-division duplexing (FDD).
  • TDD time-division duplexing
  • FDD frequency-division duplexing
  • FIG. 1 illustrates an architecture of a network in accordance with some aspects.
  • FIG. 2 illustrates example components of a device 200 in accordance with some aspects.
  • FIG. 3 illustrates example interfaces of baseband circuitry in accordance with some aspects.
  • FIG. 4 is an illustration of a control plane protocol stack in accordance with some aspects.
  • FIG. 5 is an illustration of a user plane protocol stack in accordance with some aspects.
  • FIG. 6 is a block diagram illustrating components, according to some example aspects, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • FIG. 7 illustrates an example full duplex (FD) cel lular communication system in accordance with some aspects.
  • FIG. 8 illustrates a message exchange flow between a network controller and a base station (or eNB) for interference mitigation (IM) triggering in accordance with some aspects.
  • IM interference mitigation
  • FIG. 9 illustrates example graphs of network UL
  • FIG. 10 illustrates example graphs of network DL interference information used for UL power control in accordance with some aspects.
  • FIG. 11 illustrates an example graph of network interference information used for scheduling in accordance with some aspects.
  • FIG. 12 illustrates an example graph of FD gain under varying traffic loads using interference mitigation techniques in accordance with some aspects.
  • FIG. 13, FIG. 14, FIG. 15, and FIG. 16 illustrate flow diagrams of example functionalities for interference mitigation in FD cellular systems in accordance with some aspects,
  • FIG. 17 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB), or a user equipment (UE), in accordance with some aspects.
  • eNB evolved Node-B
  • gNB new generation Node-B
  • UE user equipment
  • FIG. 1 illustrates an architecture of a network in accordance with some aspects.
  • the network 100 is shown to include a user equipment (UE) 101 and a UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless handsets
  • any of the UEs 101 and 102 can comprise an Internet of Things (loT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to- machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PL.MN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.
  • the UEs 101 and 102 may he configured to connect, e.g., communicatively couple, with a radio access network (RAN) 1 10 - the RAN 110 may be, for example, an Evolved Universal Mobile
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular
  • GSM Global System for Mobile communications
  • CDMA Code Division Multiple Access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 05.
  • the ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 102 is shown to be configured to access an access point (AP) 106 via connection 107.
  • the connection 107 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 1 protocol, wherein the AP 106 would comprise a wireless fidelity (WiFi®) router.
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 1 0 can include one or more access nodes that enable the connections 103 and 104.
  • the access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtoceils or picoceils (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 1 2,
  • LP low power
  • the nodes 111, ... , 112 can be remote radio heads (RRHs) coupled to a network gateway, such as network controller 36.
  • the network controller 136 can include a baseband unit (BBU) or a BBU pool.
  • BBU baseband unit
  • the network controller can be coupled to the nodes 1 1 1, 112, via communication links 132, ..., 134, which can include Common Public Radio Interface (CPRI) and/or Open Base Station Architecture Initiative (OBSAI) interfaces.
  • CPRI Common Public Radio Interface
  • OBSAI Open Base Station Architecture Initiative
  • any of the RAN nodes 1 1 1 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 02. in some aspects, any of the RAN nodes 1 11 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer
  • RNC radio network controller
  • any of the nodes 111 and/or 1 12 can be a new generation node-B (gNB), an eveloved node-B (eNB) or another type of RAN node,
  • gNB new generation node-B
  • eNB eveloved node-B
  • RAN node another type of RAN node
  • the UEs 101 and 102 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 1 1 1 and 112 over a multi carrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the aspects is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 111 and 112 to the UEs 101 and 102, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time- frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource gri d in the time domain corresponds to one slot in a radio frame.
  • the smallest time-frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid compri ses a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements: in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the physical downlink shared channel may carry user data and higher-layer signaling to the UEs 101 and 102.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 101 and 102 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • H-ARQ Hybrid Automatic Repeat Request
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 111 and 112 based on channel quality information fed back from any of the UEs 101 and 102.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101 and 102.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadmplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DO) and the channel condition.
  • DO downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
  • Some aspects may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some aspects may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113.
  • the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the S I interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 1 12 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 1 1 1 and 112 and MMEs 121.
  • the CN 120 comprises the MMEs 121 , the S-
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the SI interface 113 towards the RAN 1 10, and routes data packets between the RAN 110 and the CN 120.
  • the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a
  • the P-GW 123 may route data packets between the EPC network 123 and external networks such as a network including the application server 130 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the application server 130 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS Packet Services
  • LTE PS data services etc.
  • the application server 130 can also be configured to support one or more communication sendees (e.g., Voice- over- Internet Protocol (VoIP) sessions, PTT sessions, group com muni cation sessions, social networking services, etc) for the UEs 101 and 102 via the CN 120.
  • VoIP Voice- over- Internet Protocol
  • PTT sessions PTT sessions
  • group com muni cation sessions social networking services, etc
  • the P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging
  • PCRF Policy and charging control element of the CN 120.
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF 126 may be communicatively coupled to the application server 130 via the P-GW 123.
  • the application server 130 may signal the PCRF 126 to indicate a new service flow and select the appropriate Quality of Service (QoS ) and charging parameters.
  • the PCRF 126 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 130.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • any of the nodes 1 11 or 1 12 can be configured to communicate to the UEs 101/102 (e.g., dynamically) an antenna panel selection and a receive (Rx) beam selection that should be used by the UE for data reception on a physical downlink shared channel (PDSCH) as well as for channel state information reference signal (C SIRS) measurements and channel state information (CSI) calculation.
  • PDSCH physical downlink shared channel
  • C SIRS channel state information reference signal
  • CSI channel state information
  • any of the nodes 111 or 112 can be configured to communicate to the UEs 101/102 (e.g., dynamically) an antenna panel selection and a transmit (Tx) beam selection that should be used by the UE for data transmission on a physical uplink shared channel (PUSCH) as well as for sounding reference signal (SRS) transmission.
  • Tx transmit
  • PUSCH physical uplink shared channel
  • SRS sounding reference signal
  • the UEs 101 and 102 can be configured for full duplex (FD) operation within the network 100,
  • full duplex operation within the network 100 can be subject to the newly introduced BS-BS and UE-UE interferences (as discussed in reference to FIG. 7), which can potentially reduce the FD gain.
  • one or more interference mitigation techniques can be used to reduce interference during FD communications. For example, interference can be reduced via BS elevation beamforming nulling and UL power control. Additional methods for managing interference include joint scheduling and inter-cell interference
  • ICIC inter-cell interference coordination
  • Each of these interference mitigation (IM) techniques offers different performance and complexity levels (e.g., different signaling overhead). For example, some IM techniques can provide better FD performance at the cost of higher complexity. Therefore, it may not be necessary to always use a complex IM scheme if a simpler one can mitigate the interference to the required level. Additionally, since network traffic environment may change dynamically, the use of a fixed parameter to trigger the same IM scheme mav not be suitable.
  • one or more interference mitigation related parameters can be dynamically updated within the communication network 100 and various interference mitigation techniques can be applied based on the updated parameters.
  • interference mitigation triggering mechanisms can be used to determine when and how to adopt different levels of interference mitigation methods based on system interference level and traffic loading to achieve optimal FD gains.
  • one or more of the UEs can determine a downlink interference indicator 191, which can be communicated to a corresponding eNB such as eNB 1 1 1.
  • the downlink interference indicator 191 can quantify different types of interference as measured by the UE, such as conventional downlink interference (eNB-to-UE interference) and UE-to-UE interference.
  • the eNB 1 1 can also determine an uplink
  • the uplink interference indicator 190 can include conventional uplink interference (UE-to-eNB interference) as well as eNB-to-e B interference.
  • the downlink interference indicator 191 and/or the uplink interference indicator 190 can be communicated to the network controller 136.
  • the network controller 136 can apply one or more cumulative distribution functions to the indicators 190 and 191 and/or ratios of various interference components of such indicators to determine UE density, traffic load, usage pattern, and other characteristics of the communication environment within the network 100.
  • the network controller 136 and/or the eNB 1 11 can implement one or more interference mitigation techniques based on the indicators 190, 191, and/or the determined cumulative distribution functions.
  • FIG. 2 illustrates exampl e components of a devi ce 200 in accordance with some aspects.
  • the device 200 may include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 212 coupled together at least as shown.
  • the components of the illustrated device 200 may be included in a UE or a RAN node.
  • the device 200 may include less elements (e.g., a RAN node may not utilize application circuitry 202, and instead include a processor/controller to process IP data received from an EPC).
  • the device 200 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud- RAN ⁇ ' -RAN ) implementations).
  • the application circuitry 202 may include one or more application processors.
  • the application circuitry 202 may include circuitr' such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general -purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 200.
  • processors of application circuitry 202 may process IP data packets received from an EPC.
  • the baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 204 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206.
  • Baseband processing circuity 204 may interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF ci rcuitry 206.
  • the baseband circuitry 204 may include a third generation (3G) baseband processor 204 A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processor(s) 204D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 204 e.g., one or more of baseband processors 204A-D
  • baseband processors 204A-D may be included in modules stored in the memory 204G and executed via a Central Processing Unit (CPU) 204E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 204 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 204 may- include convolution, tail -biting convolution, turbo, Viterbi, or Low Density
  • LDPC Parity Check
  • the baseband circuitry 204 may include one or more audio digital signal processor(s) (DSP) 2041 ⁇ ' .
  • the audio DSP(s) 204F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other aspects.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some aspects.
  • some or all of the constituent components of the baseband circuitry 204 and the application circuitry 202 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 204 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 204 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Aspects in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 206 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 206 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 206 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204.
  • RF circuitry 206 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the FEM circuitry 208 for
  • RF circuitry 206 may include mixer circuitry 2Q6A, amplifier circuitry 206B and filter circuitry 206C.
  • the transmit signal path of the RF circuitr 206 may include filter circuitry 206C and mixer circuitry 206A.
  • RF circuitry 206 may also include synthesizer circuitry 206D for synthesizing a frequency for use by the mixer circuitry 206A of the receive signal path and the transmit signal path.
  • the mixer circuitry 206 A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206D.
  • the amplifier circuitry 206B may be configured to amplify the down-converted signals and the filter circuitry 206C may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 204 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 206A of the receive signal path may comprise passive mixers, although the scope of the aspects is not limited in this respect.
  • the mixer circuitry 206 A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206D to generate RF output signals for the FEM circuitry 208.
  • the baseband signals may be provided by the baseband circuitry 204 and may be filtered by filter circuitry 206C,
  • the mixer circuitry 206 A of the receive signal path and the mixer circuitry 206 A of the transmit signal path may include two or more mixers and may be arranged for quadrature
  • the 206A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 206A of the receive signal path and the mixer circuitry 206A may be arranged for direct down conversion and direct upconversion, respectively.
  • the mixer circuitry 206A of the receive signal path and the mixer circuitry 206A of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the aspects is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 204 may include a digital baseband interface to communicate with the RF circuitry 206.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the aspects is not limited in this respect.
  • the synthesizer circuitry 206D may be a fractional -N synthesizer or a fractional N/N+l synthesizer, although the scope of the aspects is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 206D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 206D may be configured to synthesize an output frequency for use by the mixer circuitry 206A of the RF circuitry 206 based on a frequency input and a divider control input. In some aspects, the synthesizer circuitry 206D may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 204 or the applications processor 202 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 202.
  • Synthesizer circuitry 206D of the RF circuitry 206 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A),
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 206D may be configured to generate a carrier frequency as the output frequency, while in other aspects, the output frequency may be a multipl e of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 206 may include an IQ/polar converter.
  • FEM circuitry 208 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 206 for further processing.
  • FEM circuitry 208 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 210.
  • the amplification through the transmit signal paths or the receive signal paths may be done solely in the RF circuitry 206, solely in the FEM 208, or in both the RF circuitry 206 and the FEM 208.
  • the FEM circuitry 208 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 206 for further processing.
  • FEM circuitry 208 may also
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 206).
  • the transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify input RF ' signals (e.g., provided by RF ' circuitry 206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 210).
  • PA power amplifier
  • the PMC 212 may manage power provided to the baseband circuitry 204.
  • the PMC 212 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 212 may often be included when the device 200 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 2 2 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 2 shows the PMC 212 coupled only with the baseband circuitry 204.
  • the PMC 212 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM 208.
  • the PMC 212 may control, or otherwise be part of, various power saving mechanisms of the device 200. For example, if the device 200 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 200 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 200 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as
  • the device 200 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 200 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 202 and processors of the baseband circuitry 204 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 204 may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitn,' 204 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 3 illustrates example interfaces of baseband circuitry in accordance with some aspects.
  • the baseband circuitry 204 of FIG. 2 may comprise processors 204A-204E and a memory 204G utilized by said processors.
  • Each of the processors 2G4A-2Q4E may include a memory interface, 304A-304E, respectively, to send/receive data to/from the memory 204G.
  • the baseband circuitry 204 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a
  • Q memory interface 312 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 204
  • an application circuitry interface 314 e.g., an interface to send/receive data to/from the application circuitry 202 of FIG. 2
  • an RF circuitry interface 316 e.g., an interface to send/receive data to/from RF circuitry 206 of FIG, 2)
  • a wireless hardware connectivity interface 318 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components
  • NFC Near Field Communication
  • Bluetooth ⁇ components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components
  • a power management interface 320 e.g., an interface to send/receive power or control signals to/from the PMC 212).
  • FIG. 4 is an illustration of a control plane protocol stack in accordance with some aspects.
  • a control plane 400 is shown as a communications protocol stack between the UE 101 (or alternatively, the UE 102), the RAN node 1 1 1 (or alternatively, the RAN node 112), and the MME 121.
  • the PHY layer 401 may transmit or receive information used by the MAC layer 402 over one or more air interfaces.
  • the PBY layer 401 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 405.
  • the PHY layer 401 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output ( ⁇ ) antenna processing.
  • FEC forward error correction
  • the MAC layer 402 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.
  • the RLC layer 403 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).
  • the RLC layer 403 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.
  • the RLC layer 403 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.
  • the PDCP layer 404 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).
  • security operations e.g., ciphering, deciphering, integrity protection, integrity verification, etc.
  • the main services and functions of the RRC layer 405 may include broadcast of system information (e.g., included in Master
  • MIBs MIBs
  • SIBs System Information Blocks
  • AS access stratum
  • RRC connection paging RRC connection establishment, RRC connection modification, and RRC connection release
  • RRC connection release RRC connection release
  • security functions including key management, inter radio access technology (RAT) mobility, and
  • the UE 101 and the RAN node 11 1 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 401, the MAC layer 402, the RLC layer 403, the PDCP layer 404, and the RRC layer 405.
  • a Uu interface e.g., an LTE-Uu interface
  • the non-access stratum (NAS) protocols 406 form the highest stratum of the control plane between the UE 101 and the MME 121.
  • the NAS protocols 406 support the mobility of the UE 101 and the session management procedures to establish and maintain IP connectivity between the UE 101 and the P-GW 123.
  • the S I Application Protocol (Sl-AP) layer 415 may support the functions of the SI interface and comprise Elementary Procedures (EPs).
  • An EP is a unit of interaction between the RAN node 111 and the CN 120.
  • the Sl-AP layer services may comprise two groups: UE- associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and
  • E-RAB E-UTRAN Radio Access Bearer
  • RIM RAN Information Management
  • the Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SC TP/IP layer) 414 may ensure reliable delivery of signaling messages between the RAN node 111 and the MME 121 based, in part, on the IP protocol, supported by the IP layer 413.
  • the L2 layer 412 and the LI layer 411 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • the RAN node 11 1 and the MME 121 may utilize an S 1 -
  • MME interface to exchange control plane data via a protocol stack comprising the LI layer 411, the L2 layer 412, the IP layer 413, the SCTP layer 414, and the Sl-AP layer 415.
  • FIG. 5 is an illustration of a user plane protocol stack in accordance with some aspects.
  • a user plane 500 is shown as a communications protocol stack between the UE 101 (or alternatively, the UE 102), the RAN node 3 11 (or alternatively, the RAN node 112), the S- GW 122, and the P-GW 123.
  • the user plane 500 may utilize at least some of the same protocol layers as the control plane 400.
  • the UE 101 and the RAN node 11 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 401, the MAC layer 402, the RLC layer 403, and the PDCP layer 404.
  • a Uu interface e.g., an LTE-Uu interface
  • Protocol for the user plane (GTP-U) layer 504 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP and IP security (UDP/IP) layer 503 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows.
  • the RAN node 1 11 and the S-GW 122 may utilize an Sl-U interface to exchange user plane data via a protocol stack comprising the LI layer 41 1, the !,2 layer 412, the UDP/IP layer 503, and the GTP-U layer 504,
  • the S-GW 122 and the P-GW 123 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the LI layer 41 1, the L2 layer 412, the UDP/IP layer 503, and the GTP-U layer 504.
  • NAS protocols support the mobility of the UE 101 and the session management procedures to establish and maintain IP
  • FIG. 6 is a block diagram illustrating components, according to some example aspects, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • FIG. 6 shows a diagrammatic representation of hardware resources 600 including one or more processors (or processor cores) 610, one or more memor /storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640.
  • node virtualization e.g., NFV
  • a hypervisor 602 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 600
  • the processors 610 may include, for example, a processor 612 and a processor 614.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RF C radio-frequency integrated circuit
  • the memory/storage devices 620 may include main memory, disk storage, or any suitable combination thereof.
  • memory/storage devices 620 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 630 may include
  • the communication resources 630 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.
  • wired communication components e.g., for coupling via a Universal Serial Bus (USB)
  • cellular communication components e.g., for coupling via a Universal Serial Bus (USB)
  • NFC components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components
  • Instructions 650 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 610 to perform any one or more of the methodologies discussed herein.
  • the instructions 650 may reside, completely or partially, within at least one of the processors 610 (e.g., within the processor's cache memory), the memory/storage devices 620, or any suitable combination thereof.
  • any portion of the instructions 650 may be transferred to the hardware resources 600 from any combination of the peripheral devices 604 or the databases 606.
  • the memory of processors 610, the memory/storage devices 620, the peripheral devices 604, and the databases 606 are examples of computer-readable and machine-readable media,
  • FIG. 7 illustrates an example full duplex (FD) cellular communication system in accordance with some aspects.
  • the communication system 700 can include eNB 702 serving an FD cell 714, and an eNB 704 serving an FD cell 716.
  • UEs 706 and 708 can operate in FD cell 714, and UEs 710 and 712 can operate in FD cell 716.
  • eNB 702 can be receiving an uplink transmission 718A from the UE 706 and sending a downlink transmission 718B to UE 708.
  • eNB 704 can be receiving an uplink transmission 718C from the UE 710 and sending a downlink transmission 718D to UE 71 ⁇
  • FIG. 7 Conventional interferences that occur in half duplex (HD) systems are represented by arrows 720 A - 720D.
  • Arrow 720 A represents conventional interference between the uplink transmission from UE 706 and the uplink transmission from the UE 710.
  • Arrow 720.A points towards eNB 704 because the quality of reception at eNB 704 of the uplink transmission from UE 710 will be affected by the interference from the uplink transmission of UE 706 represented by arrow 720A.
  • Arrow 720B represents conventional interference between the downlink transmission from eNB 702 and the downlink transmission from eNB 704.
  • Arrow 720B points to UE 708 because the quality of reception at the UE 708 of the downlink transmission from eNB 702 will be affected by the interference from the downlink transmission by eNB 704.
  • Arrow 720C represents conventional interference between the uplink transmission from UE 710 and the uplink transmission from UE 706.
  • Arrow 720C points to eNB 702 because the quality of reception at eNB 702 of the uplink transmission from UE 706 will be affected by the interference from the uplink transmission by UE 710.
  • Arrow 720D represents conventional interference between the downlink transmission from eNB 704 and the downlink transmission from eNB 702. Arrow 720D points to UE 712 because the quality of
  • reception at UE 712 of the downlink transmission 718D will be affected by the interference from the downlink transmission by eNB 702.
  • e B-to-eNB interference represented by arrow 722D
  • UE-to- UE interferences represented by arrows 722 A, 722B, and 722C.
  • Arrow 722D represents FD interference between the downlink transmission sent by eNB 702 and the uplink transmission sent by UE 710.
  • Arrow 722D points towards eNB 704 because the quality of reception at eNB 704 of the uplink transmission from UE 710 will be affected by the interference caused by the downlink transmission of eNB 702 to UE 708,
  • Arrow 722A represents FD interference between the uplink transmission sent by UE 706 and the downlink transmission sent by eNB 702.
  • Arrow 722A points towards UE 708 because the quality of reception at UE 708 of the downlink transmission from eNB 702 will be affected by the interference represented by arrow 722A resulting from the uplink transmission by UE 706.
  • arrow 722B points towards UE 708 because the quality of reception at UE 708 of the downlink transmission from eNB 702 will be affected by the uplink transmission by UE 710.
  • Arrow 722C represents FD interference between the uplink transmission sent by UE 710 and the downlink transmission sent by eNB 704.
  • Arrow 722C points towards UE 712 because the quality of reception at UE 712 of the downlink transmission from eNB 704 will be affected by the interference represented by arrow 722C resulting from the uplink transmission by UE 710.
  • FD systems such as system 700 can experience interference between downlink and uplink transmissions in addition to interference between downlink and downlink transmissions and interference between uplink and uplink transmissions.
  • eNB-to-eNB interference refers to interference between downlink traffic sent from one or more eNBs and uplink traffic sent to another eNB, whose reception of the uplink traffic is affected by the eNB-to-eNB interference.
  • UE-to-UE interference refers to interference between uplink traffic sent to one or more eNBs and downlink traffic sent from an e B to a UE.
  • triggering and parameter update mechanisms can be used for activating different levels of FD IM schemes within an FD communication environment (e.g., network 700 or 100), such as UL open loop power control, scheduling algorithms and inter-cell interference cancellation (IOC).
  • an eNB can be configured (e.g., at the instruction from a network controller, such as 136) to accumulate network metrics, such as interference-over-thermal-noise (loT) levels from different types of interference sources (e.g., UEs and eNBs). Techniques discussed herein can also be used by the eNB to feedback the IoT information to a network central controller (e.g., 136, which can include a BBU pool in a C-RAN architecture).
  • a network central controller e.g., 136, which can include a BBU pool in a C-RAN architecture.
  • the network controller (and/or the reporting eNB) can be configured to monitor such IoT information, which can be further used to determine or asses a type of network deployment environment, wireless traffic dynamics (such as UE density, traffic loads and usage pattern), and other network characteristics associated with interference mitigation.
  • One or more of the following techniques can be used to trigger enhanced interference management based on the reported interference information (e.g., interference levels indicated by a downlink interference indicator or an applicant interference indicator), and adjust parameters for better interference mitigation: (a) parameter update rules for UL open loop power control to adjust a power boosting factor; (b) triggering mechanism for joint scheduling algorithms; and (c) triggering mechanism for an ICIC scheme to protect cell-edge users.
  • FIG. 8 illustrates a message exchange flow between a network controller and a base station (or eNB) for interference mitigation (IM) triggering in accordance with some aspects.
  • IM interference mitigation
  • the network controller 802 can be configured to instruct the eNB 804 to adopt one of a plurality of available interference mitigation (IM) methods and parameters in a full duplex communication network.
  • IM interference mitigation
  • different levels of IM approaches can be triggered and IM parameters can be updated for the following IM schemes: (a) UL power control; (b) scheduling; and (c) inter-cell interference coordination.
  • interference-over-thermal- noise can be used as a critical metric to assist the network controller 802 to determine which IM method(s)/parameters can be used.
  • An example message exchange flow of IM triggering and parameter update mechanisms is illustrated in FIG. 8. More specifically, the network controller 802 can send an loT information request 806 to the eNB 804.
  • the IoT information request 806 can include request for an uplink and/or downlink interference indication, such as the downlink interference indicator 191 (measured by an UE) and/or the uplink interference indicator 190 (measured by an eNB). After the eNB collects the interference related information, the IoT information feedback 808 is communicated back to the network controller 802.
  • the network controller 802 can generate one or more cumulative distribution functions based on the received IoT information feedback 808, to assess the deployment environment and wireless traffic dynamics, such as UE density, traffic loads, and usage patterns.
  • the network controller 802 can generate an interference mitigation parameter update 8 0, which can be communicated back to the eNB 804.
  • the IM parameter update 810 can include a power boosting factor for communication to one or more UEs.
  • the eNB 804 can communicate the IM parameter update 810 to the UE's within its cell and trigger uplink power control 814. During the uplink power control 814 that UEs can adjust their corresponding transmission power based on the IM parameter update 810 (such as a power boosting factor).
  • the network controller 802 can further send an instruction 8 2 to bigger difterent levels of interference mitigation, such as methods 816 performed by the eNB 804 (including scheduling and ICIC).
  • UL power control can be used to mitigate e B-to-eNB interference.
  • a timely adjustment of the power boosting factor for uplink power control can be used to mitigate eNB-to-eNB interference in a dynamic environment.
  • the boosting factor for FD uplink power control algorithm which can be based on fractional open-loop power control (OLPC)
  • different loT values can be monitored.
  • each FD eNB can monitor UL IoT, such as conventional uplink IoT (representing UE-to-eNB interference) and eNB- to-eNB IoT.
  • An FD eNB can also monitor DL IoT (e.g., using reports from UEs), which can include conventional DL IoT (representing eNB-to-UE interference), and UE-to-UE IoT.
  • the eNB can then feedback such IoT information to a network central controller (e.g., 136),, such as a BBU pool in a C-RAN architecture via Common Public Radio Interface (CPRI) or Open Base Station Architecture Initiative (OBSAI) interfaces.
  • the conventional UL IoT can be measured at the eNB based on, e.g., Demodulation Reference Signals (DM-RS) and/or Sounding
  • DM-RS Demodulation Reference Signals
  • the eNB can further use cell-specific reference signals (CRS), or Primary and secondary synchronization signals (PSS and SSS) to estimate eNB-to-eNB IoT.
  • CRS cell-specific reference signals
  • PSS and SSS Primary and secondary synchronization signals
  • a UE can also use CRS to measure conventional DL IoT and report it back to the eNB. Based on one or more reference signals, UE-to-UE IoT can be estimated at the DL UE and fed back to the eNB.
  • IoT feedback from the e ' NB to the network can be periodic (e.g., with low frequency), upon request from the network controller, or eNB autonomous report when detecting noticeable IoT change (i.e., IoT above a threshold level).
  • the feedback IoT can be used to determine the wireless traffic dynamics, such as UE density, wireless traffic load and usage pattern, and so forth.
  • the eNB can also inform the network controller what type of joint scheduling algorithm is adopted for mitigating UE-to-UE interference so that the network controller can better estimate the impact of UL power boosting to DL performance. For example (and as explained herein below), in instances when a naive scheduler is used at the eNB, total UE-UE IoT can be used as a more optimal metric for boosting factor selection, while inter-cell only UE-UE IoT can be used to model the interference level more accurately when joint DL-UL scheduler is used.
  • the network central controller 802 can construct and maintain an empirical cumulative distribution function (or CDF) for UL power control.
  • FIG. 9 and FIG. 10 illustrate CDF graphs of network information that can be leveraged to trigger FD power control for different network deployment scenarios and traffic dynamics. More specifically, such empirical cumulative distribution function information generated at the network controller can be used to adjust the power boosting factor in UL OLPC at each eNB.
  • the UL OLPC can be completed after beam- nulling is applied at the eNB (each eNB can create a wide-null around 90 degree to suppress eNB-to-eNB interference).
  • the CDF plots in FIG. 9 apply 40 dB eNB-to-eNB nulling (in some instances, the CDF plots maintained at the network controller may be different from the plots shown in FIGS, 9-10 since the reported IoT measurements will have already reflected the power offset).
  • FIG. 9 illustrates example graphs of network UL
  • the example graph plots 902 - 912 can represent CDF's of a ratio of conventional uplink interference to eNB-to- eNB interference as measured and reported by an eNB, More specifically, graph plots 902 - 906 can represent CDF of the uplink interference in a dense communication environment of 40 UEs, while graph plots 908 - 912 can represent CDF of the uplink interference in a more sparse
  • FIG. 10 illustrates example graphs of network DL interference information used for UL power control in accordance with some aspects.
  • the example graph plots 1002 - 1012 can represent CDF's of a ratio of conventional downlink interference to UE-to-UE interference as measured and reported by an UE. More specifically, graph plots 1002 - 1006 can represent CDF of the downlink interference in a dense communication environment of 40 UEs, while graph plots 1008 - 1012 can represent CDF of the downlink interference in a more sparse communication environment of four UEs.
  • the network controller can detect a type of communication environment based on the periodically received interference information, and generate a CDF function associated with the specific type of communication environment.
  • Example communication environments, as seen in FIG. 9 and FIG. 10, include an outdoor uniform communication environment, and indoor communication environment, and an outdoor cluster communication environment. Even though only three example communication
  • the network controller can determine the power boosting factor (e.g., x dB), based on the IoT CDF plots to satisfy predetermined system requirements (e.g., a predetermined threshold level of interference).
  • the power boosting factor can be selected so that the medium ratio between conventional UL IoT and eNB-to-eNB IoT can meet a predetermined target (the CDF curves in FIG. 9 will be shifted to the right by x dB).
  • the medium ratio between conventional DL IoT and UE -UE IoT can meet another predetermined target (the CDF curves in FIG. 10 will be shifted to the left by x dB).
  • the network controller can be configured to send signals (e.g., 810) to the e Bs informing them of the power change.
  • the eNBs will receive a signal from the network controller indicating the power boosting factor of x dB, and the eNBs can then broadcast such information to its serving UEs so that the UL UE transmit power is boosted by x dB.
  • the network controller can use the IoT information to track the deployment environment and wireless traffic dynamics, such as UE density, wireless traffic load and usage pattern, etc, and different power boosting factors for the UL OLPC can be selected to mitigate eNB-to-e ' NB interference in the FD system.
  • wireless traffic dynamics such as UE density, wireless traffic load and usage pattern, etc.
  • different power boosting factors for the UL OLPC can be selected to mitigate eNB-to-e ' NB interference in the FD system.
  • the power boosting factor depends on several factors, such as deployment environment, traffic dynamics, and UE battery consumption,
  • Power boosting factor can be higher for dense deployment environments, such as indoor and outdoor cluster environments, and lower for sparse deployment environments, such as outdoor uniform environment.
  • Traffic dynamics such as UE density, traffic load and wireless data usage pattern.
  • the power boosting factor can be set higher since the ratio between conventional UL IoT and eNB-to-eNB IoT becomes smaller (see FIG. 9), and UE-UE interference becomes weaker (see FIG 10) as UE density or traffic load reduces.
  • the wireless data usage will vary during different times of the day. For example, there might be more traffic during the day while less traffic at night.
  • the network controller can be configured to notify the eNB of the power adjustment to be lower in the daytime and higher at night.
  • the e ' NB can be configured to also keep track of the UE battery consumption. In instances when a particular UE's battery drains quickly because of significant power boosting, the eNB can be configured to send signals to the network controller requesting change of the power boosting factor to save UE battery,
  • the network controller can create a boosting factor selection profile to indicate what boosting factor can be used for different loading conditions.
  • the network controller can be configured to monitor current traffic load and broadcast what boosting factor can be used in the network.
  • An eNB can also monitor its local IoT measurement to estimate neighbor cell loading conditions and send boosting factor update request to the network controller to achieve more dynamic boosting factor adjustment.
  • the following steps can be used for uplink power control .
  • the network controller can request UL and DL IoT information from the eNBs.
  • the UL IoT can include conventional uplink IoT (UE-to-eNB interference) and eNB-to-eNB IoT.
  • the DL IoT can include conventional DL IoT (eNB-to-UE interference) and UE-UE IoT.
  • the eNB can feed back the required IoT to the network controller.
  • the network controller can be configured to generate an empirical cumulative distribution function (CDF) (as shown in FIG. 9 and FIG.
  • CDF empirical cumulative distribution function
  • the recommended power boosting factors for the UL OLPC can be selected and broadcast to the BSs (IM parameter update from network controller to BSs).
  • the power control parameter update/setting can depend on the scheduler used at the eNB.
  • the UL power control parameter update and scheduling algorithm selection (as described in the following section) can be designed jointly.
  • Example schedulers that can be used by an eNB include a naive scheduler and a joint scheduler for mitigating UE-UE interference.
  • Each scheduler can be associated with different amount of overhead.
  • the nai ve scheduler can be configured to perform scheduling without the use of per UL-DL pair UE- UE interference feedback, and can perform UL and DL scheduling independently.
  • a joint scheduler can be configured to use per pair UE-UE information to select the best pair of UL and DL users to mitigate UE-UE interference.
  • using naive scheduler can be insufficient to recover FD gain, while in other scenarios, joint schedulers can use more resources.
  • different FD scheduling algorithms can be triggered to achieve optimal performance and overhead tradeoff,
  • each eNB can be configured to monitor the DL loT, including conventional DL loT (eNB-to-UE interference) and UE-to- UE loT.
  • the UEs can estimate conventional DL IoT using, for example, CRS, and the UE-UE IoT using reference signals.
  • the CDF of the IoT ratio between conventional DL IoT and UE-UE IoT can be constructed to first determine whether naive scheduler or joint scheduler can be used. An example is given in FIG. 10 for different deployment and traffic dynamics.
  • the DL IoT CDF information is collected and maintained at each individual eNB, including the
  • each individual eNB can be configured to feed back its collected IoT information to the network central controller or exchange the IoT information among the cooperative eNBs to mitigate overall UE-UE interference.
  • the resulting DL IoT CDFs will incorporate IoT information from all the cooperative BSs, and such information can be maintained at the network central controller, including conventional DL loT vs. UE-UE IoT level and overall UE-UE vs.
  • the network central controller can make the joint scheduling decision for all the cooperative eNBs and inform each remaining eNB of the scheduling decision.
  • a naive scheduler can be used because the conventional DL interference is more dominant for majority of the DL UEs, and UE-UE interference can become relatively trivial.
  • a joint scheduler can be triggered because the average UE-UE interference can be comparable to the conventional DL interference.
  • Traffic dynamics such as UE density, traffic load and wireless data usage pattern.
  • the traffic dynamics reflect the UE-UE interference level and multi-user diversity level. For example, with lower UE density or traffic load, the expected UE-UE interference can be weak and there may not exist sufficient multi-user diversity, hence naive scheduler can be triggered. Additionally, the wireless data usage can affect the scheduling algorithms. For example, there might be more traffic during the day while less traffic at night. Hence during the daytime, a joint schedulers can be employed, while at night a naive scheduler can be sufficient to maintain the FD performance.
  • the e ' NB can simply check the distribution of DL loT to UE-UE loT ratio for current active users and trigger more advanced joint DL-UL scheduler when there is a critical mass of UE-UE pairs suffering from large UE-UE interference. For example, joint scheduling can be triggered, if x percentage (pre-determined threshold) of UE-UE pairs are with UE-UE IoT y dB higher than DL IoT. The parameters of x and y can be adjusted according to current loading conditions.
  • the eNB can also broadcast different feedback rules for DL UEs to apply joint scheduling algorithms. For example, the eNB can send signals to the x-percentile DL UEs in the IoT CDF plots in FIG. 10 whose conventional DL IoT vs. UE- UE IoT level is below y dB to request additional feedback, where x and y values depend on deployment, traffic dynamics and system requirements captured by the IoT CDFs. For outdoor cluster environment, for instance, 40% of DL users can be signaled to feedback additional information whose conventional DL IoT vs. UE-UE IoT level is below 5 dB. More detailed feedback instructions can be triggered using the IoT ratio between intra-cell UE-UE IoT and inter-cell IoT, as explained below.
  • the DL UEs can be configured to observe interference measurement from multiple UL UEs, and feedback the intra-cell UE-UE vs. average inter-cell interference (including conventional DL IoT and inter-cell UE-UE IoT) level to the eNBs, so that the eNBs can again construct an empirical CDF of the IoT ratio between intra-cell UE- UE IoT and inter-cell IoT.
  • An example is shown in FIG. 11 for different deployment scenarios which have already captured traffic dynamics. More specifically, FIG. 1 1 illustrates example graphs 1102-1 106 of network interference information used for scheduling in accordance with some aspects.
  • the eNB can be configured to determine the amount of additional feedback for the DL UEs. For example, for indoor and outdoor cluster environment, less than 5% of the DL UEs will experience higher intra-cell UE-UE interference, hence these DL UEs can feedback 1-bit per UL-DL pair wide-band feedback to detect aggressors (i.e., stations causing interference).
  • the eNB can be configured to avoid scheduling victim (i.e., stations experiencing interference) and aggressor in the same resource to mitigate intra-cell UE-UE interference.
  • the intra-cell UE-UE vs. average inter-cell interference level can vary from -100 dB to 50 dB, different levels of additional feedback can be used for joint scheduling.
  • FIG. 12 illustrates an example graph of FD gain under varying traffic loads using interference mitigation techniques in accordance with some aspects. More specifically, FIG. 12 shows the simulation results 1200 using a fully standardized LTE small cell system level simulation with FTP-3 traffic model, where y-axis represents the throughput gain over a 10MHz FDD system (20M spectrum in total). Based on the loT information fed back from the FD eNBs, the network central controller can be configured to inform the BS to apply naive scheduler under low and medium traffic load with suggested power boosting factor for UL power control, which is sufficient to achieve optimal FD performance.
  • the network central controller can be configured to inform the BS to use more advanced joint scheduler with the proper IM parameter (such as a power boosting factor) to effectively combat the new- interference in FD system.
  • the proposed IM triggering mechanisms discussed herein can be used to achieve optimal performance and complexity tradeoff with varying traffic loads. As seen in FIG. 12, more than two times the FD gain is observed under certain traffic load regime, because of the queueing delay reduction achieved by FD when calculating the perceived throughput in non-full buffer traffic environment.
  • each e B can be configured to request DL loT information from the UEs within the corresponding cells of the eNBs.
  • the DL IoT can include conventional DL IoT (eNB-to-UE interference) and UE-UE IoT.
  • the UEs can be configured to feed back the required IoT to the serving eNB.
  • each eNB can be configured to generate an empirical cumulative distribution function (CDF) (e.g., similar to FIG. 10 but for each eNB, not network-wide) based on the IoT information sent from the UEs.
  • CDF empirical cumulative distribution function
  • the scheduling decision can be made by each eNB on whether to use a naive scheduler or a joint scheduler. Moreover, each eNB can inform the UEs of the feedback rules as to which UE needs to feedback additional information, what type of information and so forth.
  • the following steps can be used in FD scheduling with cross-cell coordination.
  • the network controller can be configured to request DL IoT information from the eNBs.
  • the DL IoT can include conventional DL IoT (eNB-to-UE interference) and UE-UE IoT.
  • the eNBs can be configured to feedback the IoT information to the network controller by collecting the DL IoT from UEs.
  • the network controller can be configured to generate an empirical cumulative distribution function (CDF) (e.g., as shown in FIG. 10) based on the IoT information sent from the eNBs.
  • CDF empirical cumulative distribution function
  • the recommended scheduling decision on whether to use a naive scheduler or a joint scheduler is made by the network controller and sent back to the eNBs,
  • ICIC can be used to mitigate inter-cell interference via network frequency and power planning.
  • an ICIC scheme can be applied based on the observed and collected DL and UL IoT information at eNBs or at the network controller.
  • the eNBs or the network controller can be configured to determine the victim cell-edge users based on UE CQI information.
  • the neighboring eNBs can be configured to coordinate to mute downlink transmission or transmit with reduced power in certain predefined and agreed-to subframes.
  • the eNB-to-eNB interference can be effectively alleviated to enable UL transmission of cell- edge users.
  • the eNB can be configured to coordinate to mute the neighboring UL UE transmission or cause the neighboring UL UE to transmit with reduced power in certain predefined and agreed subframes for the cell-edge DL user transmission, which can prevent UE-UE interference from degrading cell-edge DL performance.
  • the number and position of the cell-edge protection subframes in the frame structure can be decided by DL and UL IoT, as well as the system requirements. For example, based on the conventional UL vs. eNB-to-eNB IoT level (as shown in FIG. 9), victim cell-edge UL users can be identified from, e.g., the fifth percentile on the CDF curve. Additionally, based on the conventional DL vs. UE-UE IoT level (as shown in FIG. 10), victim cell-edge DL users can be identified from, e.g., the fifth percentile of the CDF curve.
  • the above ICIC scheme (as well as other ICIC schemes) can be triggered by network indicators, based on the deployment environment and the traffic dynamics. For example, if there is sufficient multi-user diversity, the ICIC schemes may not be triggered. However, if the networks observe insufficient multi-user diversity (and/or persistent traffic), then the above-mentioned semi-static ICIC scheme can be triggered to mitigate inter-cell interference and protect cell-edge users to guarantee the quality of service.
  • the following steps can be used in FD ICIC.
  • the network controller can be configured to request from an eNB UE CQI info and DL and UL IoT information.
  • the eNB can be configured to feedback the requested information to the network controller.
  • the network controller can be configured to generate CDF of DL/UL UE CQI curves. In instances when a DL UE has a low CQI (i.e., SINR below threshold) and the UE-UE IoT is high (i.e., above a threshold), such DL UE can be classified as victim cell-edge DL UE.
  • the network controller can be configured to instruct the eNBs to coordinate and mute downlink transmission or transmit with reduced power in certain predefined and agreed subframes used by victim cell-edge UL UE.
  • the network controller can be configured to instruct the BS to coordinate to mute the neighboring UL user transmission or transmit with reduced power in certain predefined and agreed subframes for the cell-edge DL user transmission. Based on DL and UL IoT, as well as the system
  • the number and position of the cell-edge protection subframes in the frame structure can be decided by the network controller and broadcast to the eNBs.
  • FIG. 13, FIG. 14, FIG. 15, and FIG. 16 illustrate flow diagrams of example functionalities for interference mitigation in FD cellular systems in accordance with some aspects
  • the example method 1300 can start at 1302 when in response to a request for interference information, an uplink (UL) interference indicator can be determined.
  • the e B 1 11 can determine an uplink interference indicator 190.
  • the UL interference indicator 190 can quantify eNB-to-eNB interference resulting from downlink (DL) traffic sent from one or more neighboring e Bs and UE-to-eNB interference resulting from UL traffic sent to the eNB.
  • the DL traffic and the UL traffic can be configured to use overlapping time and frequency resources, such as during FD communications.
  • a parameter update request can be decoded. More specifically, the eNB 111 can receive their parameter update request from the network controller 136.
  • the parameter update request can including a power boosting factor, wherein the power boosting factor is selected based on a ratio of the UE-to- eNB interference and the eNB-to-eNB interference (e.g., as described in reference to FIG. 9 and FIG. 10).
  • the power boosting factor can be encoded for transmission to one or more UEs (e.g., UE 101) within a ceil of the eNB.
  • the power boosting factor can indicate a power level adjustment in the transmit power of the one or more UEs.
  • the example method 1400 can start at 1402, when a request for an uplink (UL) interference indicator encode for transmission to an evolved Node-B (eNB).
  • the network controller 136 can encode such request for the uplink interference indicator 190 and send it to the eNB 111.
  • the UL interference indicator 190 can be configured to quantify eNB-to-eNB interference resulting at the eNB from downlink (DL) traffic sent from one or more neighboring eNBs, and UE-to-eNB interference resulting at the eNB from UL traffic sent to the eNB.
  • the DL traffic and the UL traffic can use overlapping time and frequency resources, such as during FD communications.
  • a cumulative distribution function (CDF) of the ratio of the UE-to-eNB interference and the eNB-to-eNB interference can be generated (e.g., by the network controller 136).
  • CDF cumulative distribution function
  • a power boosting factor can be determined based on the ratio of the UE-to-e ' NB interference and the eNB- to-eNB interference being higher than a threshold interference (e.g., as described in reference to FIG. 9 and FIG. 10).
  • the power boosting factor can be encoded for transmission to the eNB.
  • the power boosting factor can indicate a power level adjustment in transmit power of one or more user equipments (UEs) within a ceil of the eNB.
  • UEs user equipments
  • the example method 1500 can start at 1502 when, in response to an interference measurement request from an evolved Node-B (eNB), a downlink (DL) interference indicator is determined. More specifically, the eNB 1 1 1 can send an interference measurement request to UE 101, and UE 101 can determine the downlink interference indicator 191.
  • the downlink interference indicator 191 can be configured to quantify UE-to-UE interference resulting from uplink (UL) traffic sent to the eNB or to one or more neighboring eNBs by another UE, and interference resulting from DL traffic sent from the eNB.
  • the UL traffic sent to the eNB or to the one or more neighboring eNBs and the DL traffic sent from the eNB use overlapping time and frequency resources, such as during FD communications.
  • the downlink interference indicator 191 can be encoded for transmission to the eNB 1 11.
  • a parameter update request including a power boosting factor is decoded.
  • the UE 101 can receive power boosting factor from the eNB 111.
  • the power boosting factor can be selected based on a ratio of eNB-to- UE interference and the UE-to-UE interference (e.g., as described in reference to FIG. 9 and FIG. 10).
  • the eNB-to-UE interference can result from downlink traffic from the one or more neighboring eNBs.
  • the UE 101 can adjust the transmit power based on the power boosting factor.
  • the example method 1600 can start at 602, when interference information associated with a downlink (DL) user equipment (UE) receiving data on a DL channel is decoded.
  • the interference information can include a DL interference indicator, such as downlink interference indicator 191.
  • the downlink interference indicator 191 can be configured to quantify UE-to-UE interference resulting from UL traffic sent to the eNB or to one or more neighboring eNBs by other UEs, and DL traffic sent from the eNB.
  • the UL traffic sent to the eNB or to the one or more neighboring eNBs and the DL traffic sent from the eNB can use overlapping time and frequency resources, such as during FD communications.
  • channel quality information (CQI) associated with the DL UE can be decoded.
  • CQI channel quality information
  • configuration information identifying a plurality of protection subframe resources can be decoded.
  • eNB 111 can communicate the downlink interference indicator and the CQI information to the network controller 136, and in response, receive configuration information identifying protection subframe resources as well as an inter-cell interference coordination (ICIC) instruction.
  • the ICIC instruction can be decoded at the eNB 111.
  • the ICIC instruction can be configured to cause reduction of transmission power or muting transmission of the UL traffic by the other UEs during transmission of the DL traffic using the plurality of protection subframe resources, when the CQI falls below a threshold signal quality level.
  • FIG. 17 illustrates a block diagram of a communication device such as an eNB, a g ' NB, or a UE, in accordance with some aspects.
  • the communication device 1700 may operate as a standalone device or may be connected (e.g., networked) to other communication devices. In a networked deployment, the communication device 1700 may operate in the capacity of a seiver communication device, a client communication device, or both in server-client network
  • the communication device 1700 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment.
  • the communication device 1700 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device.
  • communication device shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.
  • cloud computing software as a service
  • SaaS software as a service
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a communication device readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • Com muni cation device (e.g., LIE) 1700 may include a hardware processor 1702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1704 and a static memory 1706, some or ail of which may communicate with each other via an interlink (e.g., bus) 1708.
  • the communication device 1700 may further include a display unit 1710, an alphanumeric input device 1712 (e.g., a keyboard), and a user interface (UI) navigation device 1714 (e.g., a mouse).
  • the display unit 1710, input device 1712 and UI navigation device 1714 may be a touch screen di play.
  • the communication device 1700 may additionally include a storage device (e.g., drive unit) 1716, a signal generation device 1718 (e.g., a speaker), a network interface device 1720, and one or more sensors 1721, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • the communication device 1700 may include an output controller 1728, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal serial bus
  • the storage device 1716 may include a communication device readable medium 1722 on which is stored one or more sets of data structures or instructions 1724 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 1724 may also reside, completely or at least partially, within the main memory 1704, within static memory 1706, or within the hardware processor 702 during execution thereof by the communication device 1700.
  • one or any combination of the hardware processor 1702, the main memory 1704, the static memory 1706, or the storage device 1716 may constitute communication device readable media,
  • the term "communication device readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instaictions 1724.
  • the terra "communication device readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the com muni cation device 1700 and that cause the communication device 1700 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting communication device readable medium examples may include solid-state memories, and optical and magnetic media.
  • communication device readable media may include: non- volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices: magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • non- volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices: magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices such as internal hard disks and removable disks
  • magneto-optical disks such as internal hard disks
  • the instructions 1724 may further be transmitted or received over a communications network 1726 using a transmission medium via the network interface device 1720 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.1 1 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others.
  • LAN local area network
  • WAN wide area network
  • POTS Plain Old Telephone
  • wireless data networks e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.1 1 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®
  • IEEE 802.15.4 family of standards e.g., Institute of Electrical and Electronics Engineers (IEEE
  • the network interface device 1720 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the com muni cations network 1726.
  • the network interface device 1720 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) techniques.
  • SIMO single-input multiple-output
  • MIMO multiple-input single-output
  • MISO multiple-input single-output
  • the network interface device 1720 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the communication device 1700, and includes digital or analog
  • Example 1 is an apparatus of an evolved Node-B (eNB), the apparatus comprising: processing circuitry, the processing circuitry configured to: in response to a request for interference information, determine an uplink (UL) interference indicator, wherein the UL interference indicator quantifies eNB-to-eNB interference resulting from downlink (DL) traffic sent from one or more neighboring e Bs and UE-to- eNB interference resulting from UL traffic sent to the eNB, the DL traffic and the UL traffic using overlapping time and frequency resources; decode a parameter update request, the parameter update request including a power boosting factor, wherein the power boosting factor is selected based on a ratio of the UE-to-eNB interference and the eNB-to-eNB interference; and encode the power boosting factor for transmission to one or more user equipments (UEs) within a cell of the eNB, the power boosting factor indicating a power level adjustment in the transmit power of the one or more UEs; and memory configured to store the power boosting
  • Example 2 the subject matter of Example 1 includes, wherein the power boosting factor is selected based on a cumulative distribution function (CDF) of the ratio of the UE-to-eNB interference and the eNB-to-eNB interference being higher than a threshold interference.
  • CDF cumulative distribution function
  • Example 3 the subject matter of Examples 1-2 includes, wherein the request for interference information is received from a network controller of a cloud radio access network (C-RAT) associated with the e B.
  • C-RAT cloud radio access network
  • Example 4 the subject matter of Example 3 includes, wherein the network controller is a baseband unit (BBU) pool of the C- RAT.
  • BBU baseband unit
  • Example 5 the subject matter of Examples 1-4 includes, wherein the processing circuitry is further configured to: decode additional interference information from the one or more UEs, the additional interference information including a DL interference indicator.
  • Example 6 the subject matter of Example 5 includes, wherein the DL interference indicator quantifies UE-to-UE interference resulting from UL traffic sent to the eNB or the one or more neighboring eNBs and interference resulting from DL traffic sent from the eNB, wherein the UL traffic sent to the eNB or to the one or more neighboring eNBs and the DL traffic sent from the eNB use overlapping time and frequency resources.
  • Example 7 the subject matter of Example 6 includes, wherein the processing circuitry is further configured to: encode the UL interference indicator and the DL interference indicator for transmission in response to the request for interference information.
  • Example 8 the subject matter of Example 7 includes, wherein the power boosting factor corresponds to the UL interference indicator and the DL interference indicator.
  • Example 9 the subject matter of Examples 7-8 includes, wherein the power boosting factor is based on a cumulative distribution function (CDF) of a ratio of eNB-to-UE interference and the UE-to-UE interference being higher than a threshold interference, the eNB-to-UE interference resulting from downlink traffic by the one or more neighboring eNBs.
  • CDF cumulative distribution function
  • Example 10 the subject matter of Example 9 includes, wherein the processing circuitry is further configured to: determine a scheduling identifier based on the ratio of the eNB-to-UE interference and the UE-to-UE interference, wherein the scheduling identifier identifies one of a naive scheduler or a joint scheduler for use by the e B to mitigate the UE-to-UE interference when scheduling a pair of UEs for full duplex communication with the eNB.
  • Example 1 1 the subject matter of Example 10 includes, wherein the processing circuitry is further configured to: decode a scheduling configuration request from a network controller associated with the eNB and the one or more neighboring eNBs, the scheduling
  • Example 12 the subject matter of Examples 10-11 includes, wherein the naive scheduler is configured to schedule UL-DL communication in FD for the pair of UEs without using UE-to-UE interference feedback from the pair of UEs.
  • Example 13 the subject matter of Examples 10-12 includes, wherein the joint scheduler is configured to schedule UL-DL communication in FD for the pair of UEs UE-to-UE interference feedback from the pair of UEs.
  • Example 14 is a computer-readable storage medium thai- stores instructions for execution by one or more processors of a network controller, the one or more processors to configure the network controller to: encode for transmission to an evolved Node-B (eNB) a request for an uplink (UL) interference indicator, wherein the UL interference indicator quantifies eNB-to-eNB interference resulting at the eNB from downlink (DL) traffic sent from one or more neighboring eNBs, and UE-to-eNB interference resulting at the eNB from UL traffic sent to the eNB, the DL traffic and the UL traffic using overlapping time and frequency resources; in response to receiving the UL interference indicator from the eNB, generate a cumulative distribution function (CDF) of the ratio of the UE-to- eNB interference and the eNB-to-eNB interference; determine a power boosting factor based on the ratio of the UE-to-eNB interference and the eNB-to-eNB interference being higher than a threshold interference;
  • Example 15 the subject matter of Example 14 includes, wherein the one or more processors further configure the network controller to: encode the power boosting factor for transmission to the one or more neighboring eNBs, the power boosting factor further indicating a power level adjustment in transmit power of one or more user equipments (UEs) within ceils of the one or more neighboring eNBs.
  • the one or more processors further configure the network controller to: encode the power boosting factor for transmission to the one or more neighboring eNBs, the power boosting factor further indicating a power level adjustment in transmit power of one or more user equipments (UEs) within ceils of the one or more neighboring eNBs.
  • UEs user equipments
  • Example 16 the subject matter of Examples 14-15 includes, wherein the one or more processors further configure the network controller to: decode additional interference information from the eNB, the additional interference information including a DL interference indicator originating from one of the UEs within the cell of the eNB.
  • Example 17 the subject matter of Example 16 includes, wherein the DL interference indicator quantifies UE-to-UE interference at the one of the UEs resulting from UL traffic sent to the eNB or the one or more neighboring eNBs and DL traffic sent from the eNB, wherein the UL traffic sent to the eNB or to the one or more neighboring eNBs and DL traffic sent from the eNB use overlapping time and frequency resources, and wherein the DL interference indicator further quantifies eNB-to-UE interference resulting from downlink traffic from the one or more neighboring eNBs.
  • Example 18 the subject matter of Example 17 includes, wherein the one or more processors further configure the network controller to; decode additional DL interference indicators from the one or more neighboring eNBs, wherein the additional DL interference indicators quantify UE-to-UE interference and eNB-to-UE interference reported by UEs served by the one or more neighboring eNBs; and generate a second cumulative distribution function (CDF) of a ratio of the eNB-to-UE interference and the UE-to-UE interference using the DL interference indicator and the additional DL interference indicators.
  • CDF cumulative distribution function
  • Example 19 the subject matter of Example 18 includes, wherein the one or more processors further configure the network controller to; detect a deployment environment associated with the eNB and the one or more neighboring eNBs based at least on the generated second cumulative distribution function, wherein the deployment environment is one of an outdoor cluster environment, an indoor cluster environment, and a uniform environment.
  • Example 20 the subject matter of Example 19 includes, wherein the one or more processors further configure the network controller to: determine the power boosting factor further based on one or more of the following: the ratio of the eNB-to-UE interference and the UE- to-UE interference being higher than a second threshold interference, the deployment environment, and a level of network traffic associated with the deployment environment.
  • Example 21 the subj ect matter of Examples 19-20 includes, wherein the one or more processors further configure the network controller to: determine a scheduling identifier based on one or more of the following: the ratio of the eNB-to-UE interference and the UE-to-UE interference being higher than a second threshold interference, the deployment environment, and a level of network traffic associated with the deployment environment, wherein the scheduling identifier identifies one of a naive scheduler or a joint scheduler for use by the eNB to mitigate the UE-to-UE interference when scheduling a pair of UEs for full duplex communication with the eNB; and encode the scheduling identifier for transmission to the eNB.
  • Example 22 the subject matter of Example 21 includes, wherein the naive scheduler is configured to schedule UL-DL
  • Example 23 the subject matter of Examples 21-22 includes, wherein the joint scheduler is configured to schedule UL-DL communication in FD for the pai r of UEs UE-to-UE interference feedback from the pair of UEs.
  • Example 24 the subject matter of Examples 19-23 includes, wherein the one or more processors further configure the network controller to: decode channel quality information (CQI) reported by the one of the UEs, wherein the one of the UEs is a downlink UE receiving data on a downlink channel; and encode for transmission an inter-cell interference coordination (ICIC) instruction when the CQI is below a signal quality threshold.
  • CQI channel quality information
  • ICIC inter-cell interference coordination
  • Example 25 the subject matter of Example 24 includes, wherein the ICIC instruction causes muting of transmissions of neighboring UEs to the downlink UE or transmission at reduced power by the neighboring UEs during one or more protection subframes when the downlink UE receives the data.
  • Example 26 the subject matter of Examples 24-25 includes, wherein the ICIC instruction further identifies the one or more protection subframes.
  • Example 27 the subject matter of Examples 19-26 includes, wherein the one or more processors further configure the network controller to: decode channel quality information (CQI) reported by the one of the UEs, wherein the one of the UEs is an uplink UE transmitting data on an uplink channel; and encode for transmission an inter-cell interference coordination (ICIC) instruction when the CQI is below a signal quality threshold.
  • CQI channel quality information
  • IIC inter-cell interference coordination
  • Example 28 the subject matter of Example 27 includes, wherein the ICIC instruction causes reducing transmission power or muting of transmission of the eNB during one or more protection subframes when the uplink UE transmits the data.
  • Example 29 is an apparatus of a user equipment (UE), the apparatus comprising: processing circuitry, the processing circuitry configured to: in response to an interference measurement request from an evolved Node-B (eNB), determine a downlink (DL) interference indicator quantifying UE-to-UE interference resulting from uplink (UL) traffic sent to the eNB or to one or more neighboring eNBs by another UE, and interference resulting from DL traffic sent from the eNB, wherein the UL traffic sent to the eNB or to the one or more neighboring eNBs and the DL traffic sent from the eNB use overlapping time and frequency resources; encode the DL interference indicator for transmission to the eNB; decode a parameter update request including a power boosting factor, wherein the power boosting factor is selected based on a ratio of eNB-to-UE
  • the eNB-to-UE interference results from downlink traffic from the one or more neighboring e Bs; and cause adjustment of transmit power based on the power boosting factor, and memory configured to store the power boosting factor.
  • Example 30 the subject matter of Example 29 includes, wherein the processing circuitry is further configured to: encode channel quality information (CQI) associated with a DL communication channel for transmission, and decode downlink data received using the overlapping time and frequency resources, wherein UL transmission by the another UE during the overlapping time and frequency resources is muted or is permitted at a reduced power when the CQI is below a threshold amount.
  • CQI channel quality information
  • Example 31 the subject matter of Examples 29-30 includes, wherein the downlink data is received during one or more protection subframes specified by higher layer signaling.
  • Example 32 the subject matter of Examples 29-31 includes, transceiver circuitry coupled to the processing circuitry and a plurality of available antenna panels.
  • Example 33 is an apparatus of an evolved Node-B (eNB), the apparatus comprising processing circuitry, the processing circuitry configured to: decode interference information associated with a downlink (DL) user equipment (UE) receiving data on a DL channel, the interference information including a DL interference indicator quantifying UE-to-UE interference resulting from UL traffic sent to the eNB or to one or more neighboring eNBs by other UEs, and DL traffic sent from the eNB, wherein the UL traffic sent to the eNB or to the one or more neighboring eNBs and the DL traffic sent from the eNB use overlapping time and frequency resources; decode channel quality information (CQI) associated with the DL UE, in response to the DL interference indicator and the CQI, decode configuration information identifying a plurality of protection subframe resources; and decode inter-cell interference coordination (ICIC) instruction, the ICIC instruction causing reduction of transmission power or muting transmission of the UL traffic by the other UEs during transmission
  • Example 35 the subject matter of Example 34 includes, wherein the processing circuitry is configured to: cause the reduction of transmission power or muting the transmission of the UL traffic by the other UEs during the plurality of protection subframe resources further based on the UE-to-UE interference or a ratio of eNB-to-UE interference and the UE-to-UE interference, the eNB-to-UE interference resulting from downlink traffic sent by the one or more neighboring eNBs.
  • Example 36 is an apparatus of an evolved Node-B (eNB), the apparatus comprising: means for, in response to a request for interference information, determining an uplink (UL) interference indicator, wherein the UL interference indicator quantifies eNB-to-eNB interference resulting from downlink (DL) traffic sent from one or more neighboring eNBs and UE-to-eNB interference resulting from UL traffic sent to the eNB, the DL traffic and the UL traffic using overlapping time and frequency resources, means for decoding a parameter update request, the parameter update request including a power boosting factor, wherein the power boosting factor is selected based on a ratio of the UE-to-eNB interference and the eNB-to-eNB interference; and means for encoding the power boosting factor for transmission to one or more user equipments (UEs) within a cell of the eNB, the power boosting factor indicating a power level adjustment in the transmit power of the one or more UEs.
  • UEs user equipments
  • Example 37 the subject matter of Example 36 includes, wherein the power boosting factor is selected based on a cumulative distribution function (CDF) of the ratio of the UE-to-eNB interference and the eNB-to-eNB interference being higher than a threshold interference.
  • CDF cumulative distribution function
  • Example 38 the subject matter of Examples 36-37 includes, wherein the request for interference information is received from a network controller of a cloud radio access network (C-RAT) associated with the eNB.
  • C-RAT cloud radio access network
  • Example 39 the subject matter of Example 38 includes, wherein the network controller is a baseband unit (BBU) pool of the C- RAT.
  • BBU baseband unit
  • Example 40 the subject matter of Examples 36-39 includes, wherein the apparatus further comprises: means for decoding additional interference information from the one or more UEs, the additional interference information including a DL interference indicator.
  • Example 41 the subject matter of Example 40 includes, wherein the DL interference indicator quantifies UE-to-UE interference resulting from UL traffic sent to the eNB or the one or more neighboring eNBs and interference resulting from DL traffic sent from the eNB, wherein the UL traffic sent to the eNB or to the one or more neighboring eNBs and the DL traffic sent from the eNB use overlapping time and frequency resources.
  • Example 42 the subject matter of Example 41 includes, wherein the apparatus further comprises: means for encoding the UL interference indicator and the DL interference indicator for transmission in response to the request for interference information.
  • Example 43 the subject matter of Example 42 includes, wherein the power boosting factor corresponds to the UL interference indicator and the DL interference indicator.
  • Example 44 the subject matter of Examples 42-43 includes, wherein the power boosting factor is based on a cumulative distribution function (CDF) of a ratio of eNB-to-UE interference and the UE-to-UE interference being higher than a threshold interference, the eNB- to-UE interference resulting from downlink traffic by the one or more neighboring eNBs.
  • CDF cumulative distribution function
  • Example 45 the subject matter of Example 44 includes, wherein the apparatus further comprises: means for determining a scheduling identifier based on the ratio of the eNB-to-UE interference and the UE-to-UE interference, wherein the scheduling identifier identifies one of a naive scheduler or a joint scheduler for use by the eNB to mitigate the UE-to-UE interference when scheduling a pair of UEs for full duplex communication with the eNB.
  • Example 46 the subject matter of Example 45 includes, wherein the apparatus further comprises: means for decoding a scheduling configuration request from a network controller associated with the e ' NB and the one or more neighboring eNBs, the scheduling configuration request including the scheduling identifier.
  • Example 47 the subject matter of Examples 45-46 includes, wherein the naive scheduler is configured to schedule UL-DL communication in FD for the pair of UEs without using UE-to-UE interference feedback from the pair of UEs.
  • Example 48 the subject matter of Examples 45-47 includes, wherein the joint scheduler is configured to schedule UL-DL communication in FD for the pair of UEs UE-to-UE interference feedback from the pair of UEs.
  • Example 49 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-48.
  • Example 50 is an apparatus comprising means to implement of any of Examples 1—48.
  • Example 51 is a system to implement of any of Examples 1-
  • Example 52 is a method to implement of any of Examples

Landscapes

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

Abstract

La présente invention porte, de manière générale, sur des dispositifs et sur des procédés d'atténuation des interférences dans un système cellulaire en duplex intégral. Un nœud B évolué (eNB) peut comprendre un ensemble de circuits de traitement configuré, en réponse à une demande d'informations d'interférence, à déterminer un indicateur d'interférence de liaison montante (UL pour UpLink). L'indicateur d'interférence de liaison montante quantifie des interférences entre nœuds eNB résultant d'un trafic de liaison descendante (DL pour DownLink) envoyé depuis un ou plusieurs nœuds eNB voisins et des interférences entre un équipement utilisateur (UE pour User Equipment) et un nœud eNB résultant d'un trafic de liaison montante envoyé au nœud eNB, le trafic de liaison descendante et le trafic de liaison montante utilisant des ressources de temps et de fréquence qui se chevauchent. L'ensemble de circuits de traitement peut en outre décoder une demande de mise à jour de paramètre, qui comprend un facteur d'amplification de puissance. Le facteur d'amplification de puissance est sélectionné sur la base d'un rapport entre les interférences entre un équipement utilisateur et un nœud eNB et les interférences entre nœuds eNB. Le facteur d'amplification de puissance est codé pour une transmission à un ou plusieurs équipements utilisateurs à l'intérieur d'une cellule du nœud eNB, le facteur d'amplification de puissance indiquant un ajustement de niveau de puissance dans la puissance d'émission du ou des équipements utilisateurs.
EP17924431.4A 2017-09-11 2017-09-11 Schémas d'atténuation d'interférence pour des systèmes cellulaires en duplex intégral Withdrawn EP3682564A4 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2017/050977 WO2019050544A1 (fr) 2017-09-11 2017-09-11 Schémas d'atténuation d'interférence pour des systèmes cellulaires en duplex intégral

Publications (2)

Publication Number Publication Date
EP3682564A1 true EP3682564A1 (fr) 2020-07-22
EP3682564A4 EP3682564A4 (fr) 2021-04-21

Family

ID=65634312

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17924431.4A Withdrawn EP3682564A4 (fr) 2017-09-11 2017-09-11 Schémas d'atténuation d'interférence pour des systèmes cellulaires en duplex intégral

Country Status (2)

Country Link
EP (1) EP3682564A4 (fr)
WO (1) WO2019050544A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12593346B2 (en) 2020-03-19 2026-03-31 Qualcomm Incorporated Uplink indication for full-duplex operation
US12302399B2 (en) * 2022-01-07 2025-05-13 Qualcomm Incorporated Random access channel occasions and resources for interference mitigation
WO2025210481A1 (fr) * 2024-04-04 2025-10-09 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et nœuds pour une perception de ran améliorée, pour améliorer une procédure de planification basée sur un lecteur pour l'ido-a

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7512412B2 (en) * 2005-03-15 2009-03-31 Qualcomm, Incorporated Power control and overlapping control for a quasi-orthogonal communication system
US8160631B2 (en) * 2008-12-30 2012-04-17 Airvana, Corp. Power control for reverse link
US20110176497A1 (en) * 2010-01-20 2011-07-21 Nandu Gopalakrishnan Inter-cell interference coordination and power control scheme for downlink transmissions
AU2011308576C1 (en) * 2010-10-01 2016-03-03 Interdigital Patent Holdings, Inc. Systems and methods for uplink feedback for high-speed downlink packet access (HSDPA)
US9768929B2 (en) * 2012-12-21 2017-09-19 Blackberry Limited Method and apparatus for identifying interference type in time division duplex systems
JP2015185956A (ja) * 2014-03-20 2015-10-22 株式会社Ｎｔｔドコモ ユーザ装置及び基地局
WO2017111807A1 (fr) * 2015-12-24 2017-06-29 Intel Corporation Commande de puissance de liaison montante pour limitation de brouillage dans des réseaux cellulaires de type duplex intégral

Also Published As

Publication number Publication date
EP3682564A4 (fr) 2021-04-21
WO2019050544A1 (fr) 2019-03-14

Similar Documents

Publication Publication Date Title
US12101153B2 (en) Group based beam reporting and channel state information reference signal configuration in new radio systems
US20250226899A1 (en) Methods and arrangements for cross-link interference mitigation
US11917626B2 (en) Uplink transmission for multi-panel operation
US20240147488A1 (en) Enhancement of Performance of Ultra-Reliable Low-Latency Communication
US11006429B2 (en) Antenna panel switching and beam indication
US11122516B2 (en) Systems and methods for uplink transmission power control
US10771214B2 (en) System and method for uplink power contrl framework
US11464075B2 (en) Method and apparatus for configuration of reference signal
US20230014081A1 (en) Radio link monitoring (rlm) evaluation mechanism for new radio (nr) systems
US11140634B2 (en) Narrowband internet-of-things (NB-IOT) enhancements
US20250226898A1 (en) Methods and arrangements for cross-link interference mitigation
US10911996B2 (en) Beamforming measurements based on PSS/SSS
US10897776B2 (en) Downlink control information design with shorter TTI
EP4307588A2 (fr) Dispositifs et procédés de déclenchement et de rétroaction de régulation de flux
US10530503B2 (en) Apparatus and method for RSRP measurement and allocation of downlink transmission resources
WO2018064182A1 (fr) Adaptation de liaison pour une communication à faible latence ultra-fiable
WO2018093939A1 (fr) Transfert sans rach
WO2018204273A1 (fr) Gestion de systèmes de communication mimo
US20200373989A1 (en) Method and apparatus for beam recovery
WO2019050544A1 (fr) Schémas d'atténuation d'interférence pour des systèmes cellulaires en duplex intégral
US20210281368A1 (en) Managing link quality and using partial subframes in wireless telecommunication networks
WO2018102098A1 (fr) Systèmes, procédés et dispositifs de gestion d'état de tampon de harq
US20240032002A1 (en) Dynamic resource allocation
WO2018144892A1 (fr) Dispositions facilitant la transition et la mesure d'adaptation de bande passante

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200107

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Free format text: PREVIOUS MAIN CLASS: H04J0011000000

Ipc: H04W0052240000

A4 Supplementary search report drawn up and despatched

Effective date: 20210318

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 52/14 20090101ALN20210312BHEP

Ipc: H04J 11/00 20060101ALI20210312BHEP

Ipc: H04W 52/24 20090101AFI20210312BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20230426

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20250401