CN112292881A - Bias control for dynamic time division duplexing - Google Patents

Bias control for dynamic time division duplexing Download PDF

Info

Publication number
CN112292881A
CN112292881A CN201880094429.8A CN201880094429A CN112292881A CN 112292881 A CN112292881 A CN 112292881A CN 201880094429 A CN201880094429 A CN 201880094429A CN 112292881 A CN112292881 A CN 112292881A
Authority
CN
China
Prior art keywords
interference
link
direction deviation
network entity
cross
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.)
Pending
Application number
CN201880094429.8A
Other languages
Chinese (zh)
Inventor
郭海友
T·A·勒瓦南
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.)
Nokia Shanghai Bell Co Ltd
Nokia Oyj
Nokia Solutions and Networks Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Networks Oy
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 Nokia Shanghai Bell Co Ltd, Nokia Networks Oy filed Critical Nokia Shanghai Bell Co Ltd
Publication of CN112292881A publication Critical patent/CN112292881A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J11/00Orthogonal multiplex systems, e.g. using WALSH codes
    • H04J11/0023Interference mitigation or co-ordination
    • H04J11/005Interference mitigation or co-ordination of intercell interference
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058Allocation criteria
    • H04L5/0073Allocation arrangements that take into account other cell interferences

Abstract

An apparatus comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to receive one or more cross-link interference overload indications. The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: updating one or more link direction deviation control parameters based at least on the one or more cross-link interference overload indications. The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to: transmitting and/or receiving a signal using the adjusted one or more link direction deviation control parameters.

Description

Bias control for dynamic time division duplexing
Technical Field
Some examples may relate to a communication system. For example, some examples may relate to dynamic time division duplexing.
Background
Dynamic Time Division Duplexing (TDD), also known as enhanced interference mitigation and traffic adaptation (eIMTA), allows a network to dynamically use resources for Uplink (UL) or Downlink (DL) transmissions in order to match instantaneous traffic conditions. The UL/DL allocations may be signaled at the beginning of each frame or at the beginning of a set of frames to achieve dynamically changing UL/DL usage. The UL/DL configuration in eIMTA may not be static, but may change from frame to frame. The broadcast allows the UL/DL configuration to adjust and meet various requirements for UL/DL traffic. Thus, eIMTA uses a frame structure with flexible subframes, where some subframes in one radio frame may be defined as flexible subframes, where the UL/DL configuration is allowed to vary from frame to frame.
However, the introduction of dynamic TDD creates a new type of inter-cell interference, sometimes referred to as cross-link interference (CLI). In particular, misalignment between neighboring cells in the link direction may generate interference such as User Equipment (UE) to UE and Transmission Reception Point (TRP) to TRP between network entities. CLI may also be responsible for most transmission failures in dynamic TDD systems.
The New Radio (NR) system uses dynamic TDD to determine the appropriate sequence of UL/DL symbols/slots for the associated cell, where each UL/DL OFDM symbol is scheduled for the UE to accommodate traffic variations and various CLI cases. The set of OFDM symbols to be assigned is distributed in multiple slots in a continuous or non-continuous manner without loss of generality. In this way, the coordination of symbol scheduling is the same for all cells. For example, the total number of symbols/slots may be denoted by N, where the set ScellIndicating all NcellA coordinated cell. Cell n belongs to ScellIs used SneiSurrounded by an indicated set of neighbouring cells. The total number of UL/DL symbols/slots assigned for cell N will be Nn UL(Nn DL). Each cell attempts to determine a different N that satisfies UL/DL traffic requirementsn ULAnd Nn DLValue, resulting in link direction collisions between neighboring cells and thus in an undesirable CLI.
For example, fig. 1 illustrates significant performance degradation due to link direction collisions based on a signal-to-interference-and-noise ratio (SINR) Cumulative Distribution Function (CDF). For two arbitrary adjacent cells m and N, the difference | Nm UL–Nn UL|(|Nm DL–Nn DL|) is a link direction deviation, where a larger difference indicates a greater potential for CLI, since the link direction deviation is directly related to the CLI. Thus, if a cell prevents its UL/DL ratio from deviating from a predetermined UL/DL ratio, such as an average UL/DL ratio, on neighboring cells, the collision of link directions will be controlled.
CLI can be reduced by reducing link direction bias, but at the same time, the flexibility gain of TDD will be reduced. Each cell needs to balance traffic adaptation and CLI mitigation. As such, the link direction deviation should be controlled within a predetermined range to balance duplex flexibility and CLI compromise. In addition, the link direction deviation should be controlled between all neighboring cells. For example, one cell may cause UE-to-UE interference on some cells and TRP-TRP interference on other cells, which further complicates link direction deviation control. Under these spatio-temporal variations in flow requirements and channel conditions, the link direction deviation cannot be set to a static value. Therefore, the cell is required to tune the link deviation parameter in response to CLI overload.
Disclosure of Invention
According to an example, a method may include receiving, by a network entity, one or more cross-link interference overload indications. The method may also include updating, by the network entity, one or more link direction deviation control parameters based at least on the one or more cross-link interference overload indications. The method may also include transmitting and/or receiving, by the network entity, a signal using the adjusted one or more link direction deviation control parameters.
According to an example, an apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to receive one or more cross-link interference overload indications. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus at least to update one or more link direction deviation control parameters based at least on the one or more cross-link interference overload indications. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to transmit and/or receive signals using the adjusted one or more link direction deviation control parameters.
According to one example, an apparatus may include means for receiving one or more cross-link interference overload indications. The apparatus may also include means for updating one or more link direction deviation control parameters based at least on the one or more cross-link interference overload indications. The apparatus may also include means for transmitting and/or receiving a signal using the adjusted one or more link direction deviation control parameters.
According to an example, in some examples, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, may perform a process. The process may include a method that may receive one or more cross-link interference overload indications. The process may include a method that may update one or more link direction deviation control parameters based at least on one or more cross-link interference overload indications. The process may include a method that may transmit and/or receive signals using the adjusted one or more link direction deviation control parameters.
According to an example, according to some examples, a computer program product may have instructions encoded for performing a process. The process may include a method that may receive one or more cross-link interference overload indications. The process may also include a method that may update one or more link direction deviation control parameters based at least on the one or more cross-link interference overload indications. The process may also include a method that may transmit and/or receive signals using the adjusted one or more link direction deviation control parameters.
According to one example, an apparatus may include circuitry configured to receive one or more cross-link interference overload indications. The apparatus may also include circuitry configured to update one or more link direction deviation control parameters based at least on the one or more cross-link interference overload indications. The apparatus may also include circuitry configured to transmit and/or receive signals using the adjusted one or more link direction deviation control parameters.
Drawings
For a proper understanding of the present disclosure, reference should be made to the accompanying drawings, in which:
fig. 1 illustrates an example of uplink signal to interference and noise ratio loss due to link direction deviation in the prior art.
Fig. 2 illustrates an example of a signaling diagram according to some examples.
Fig. 3 illustrates an example of a cross-link indication overload indication according to some examples.
Fig. 4 illustrates an example of a method performed by a network entity, according to some examples.
Fig. 5 illustrates another example of a method performed by a network entity, according to some examples.
Fig. 6 illustrates an example system consisting of macrocells in a regular hexagonal grid, according to some examples.
Fig. 7 illustrates another example of a method performed by a network entity, according to some examples.
Fig. 8 illustrates another example of a method performed by a user device, according to some examples.
Fig. 9 illustrates an example of a system according to some examples.
Detailed Description
The features, structures, or characteristics of some examples described throughout this specification may be combined in any suitable manner in one or more examples. For example, throughout the specification, use of the phrases "some examples," "other examples," or other similar language refers to the fact that: the particular features, structures, or characteristics described in connection with the example may be included in at least one example of the invention. Thus, appearances of the phrases "in certain examples," "in some examples," "in other examples," or other similar language throughout this specification do not necessarily refer to the same group of examples, and the described features, structures, or characteristics may be combined in any suitable manner in one or more examples.
In response to the challenges in the prior art discussed above, certain examples described herein may help reduce interference in a dynamic TDD system by balancing TDD flexibility gains with CLI hazards in the dynamic TDD system. The examples described herein may have various benefits and/or advantages. For example, some examples may balance flexibility gains for traffic adaptation and performance loss caused by CLI by controlling link direction collisions in an adaptive manner. Accordingly, certain examples are directed towards improvements in computer-related technology, particularly by conserving network resources and reducing power consumption of UEs and/or network entities located within the network.
Fig. 2 illustrates an example of a signaling diagram showing the communication between Network Entity (NE)220, NE 230 and NE 240. NE 220, NE 230, and/or NE 240 may be similar to NE 910, as illustrated in fig. 9.
In step 201, NE 220, NE 230 and/or NE 240 may assign an initial or updated value to an uplink direction deviation control parameter and/or assign an initial or updated value to a downlink direction deviation control parameter. The uplink direction deviation control parameter may be represented by Δn ULThe index, and/or the downlink direction deviation control parameter may be represented by Δn DLAnd marking. In some examples, 0 ≦ Δn ULAnd/or 0. ltoreq. deltan DL. In some examples, in response to CLI, is represented by Δ, respectivelyn UL(t) and. DELTA.n DLThe uplink and/or downlink direction deviation control parameters represented by (t) may be updated and/or tuned in time.
In step 203, in NEAny NE may apply a feasible TDD mode configuration for traffic adaptation that ensures that the link direction deviation meets a predefined criterion, e.g. one or more quality metric parameters. In some examples, any of the NEs may select N _ N that satisfies one or more currently used bias control constraints based on a link direction control parameter such as/Delta _ N. In some examples, the number of UL and DL slots/symbols assigned for one cell may both fall within a tolerable range centered on an average over neighboring cells. E.g. according to the existing signalling procedure, Nm ULAnd Nm DL|m∈Snei,nMay be available for cell N such that the network entity may be constrained N by bi-directional bias controln UL–1/|Snei,nm∈Snei,n Nm UL≤Δn UL(t),n∈ScellAnd Nn DL–1/|Snei,nm∈Snei,n Nm DL≤Δn DL(t),n∈ScellUnder the constraint of (2), N for cell N is determined independentlyn ULAnd Nn DLWherein | Snei,nI represent the set S according to various optimization criteria (such as max-min traffic matching method)nei,nCardinality (cardinality), as discussed below. In other examples, the bi-directional bias control constraint may be based on an average, such as a simple average, a geometric average, and/or a weighted average, of the number of UL and/or DL symbols used by the neighboring cells.
In some examples, the cell may determine the UL/DL transmission ratio for the next several time slots according to the current link direction deviation control parameter to maximize the minimum traffic matching factor. For a time slot t, the integer optimization problem max (N) can be solvedn UL,Nn DL)minn min(Nn UL/Ndemand,,n UL,Nn DL/Ndemand,n DL) To determine such a desired TDD mode configuration such that Nn UL–1/|Snei,nm∈Snei,n Nm UL≤Δn UL(t),n∈Scell,Nn DL–1/|Snei,nm∈Snei,n Nm DL≤Δn DL(t),n∈Scell,Nn UL+Nn DL=N,n∈Scell,and Nn UL,Nn DL∈{0,1,L,…N},n∈ScellIn which Δn UL(t) and. DELTA.n DL(t) respectively indicate current link direction deviation control parameters. In some examples, the current link direction deviation control parameter is updated for every predetermined number of time slots (such as N-10 time slots). In addition, one or more time resources are used for transmission, where one slot may be an UL or DL slot.
In step 205, any one of the NEs may receive one or more CLI measurements, including NE-to-NE measurements and/or UE-to-UE measurements for one or more slot/symbol combinations. In some examples, at least one of one or more NE-to-NE interference measurements and UE-to-UE interference measurements may be received. In some examples, satisfactory CLI measurements may indicate which network entity or entities are causing NE-to-NE and/or UE-to-UE interference.
In step 207, any of the NEs may exchange one or more CLI measurement indication Information Elements (IEs) with one or more other network entities. In some examples, the one or more CLI measurement indication information elements may include one or more CLI overload indication information elements over an Xn interface between two or more NEs. The CLI overload indication IE may contain a UE-to-UE interference overload indication IE and/or a NE-to-NE interference overload indication IE. Any of these interference overload indication IEs may be included in one or more of the channels XnLOAD INFORMATION (LOAD INFORMATION) messages defined by the application protocol and/or other dedicated messages.
In various examples, one or more generated CLI overload indicator IEs may indicate one or more CLI levels associated with various frequency and/or time resources of neighboring NEs. One or more CLI overload indicator IEs may be generated according to the method illustrated in fig. 5. One or more CLI overload indicator IEs may define CLIs as low, medium, and high. In addition, one or more CLI overload indicator IEs may provide a report on CLI interference overload for each resource block, similar to the table shown in fig. 3. In particular, if one or more UE-to-UE interference overload indication IEs are received in a particular message, this may indicate a time-averaged UE-to-UE interference level caused by the receiving network entity and/or experienced by the indicated network entity on some or all resource blocks. Further, the receiving network entity may utilize the one or more UE-to-UE interference overload indication IEs when creating the one or more scheduling policies, and may consider the one or more UE-to-UE interference overload indication IE values to be valid until one or more new messages are received, the one or more new messages including an updated version of the one or more UE-to-UE interference overload indication IEs.
Similarly, if one or more NE-to-NE interference overload indication IEs are received in one or more messages, this may indicate one or more time-averaged NE-to-NE interference levels caused by the receiving network entity and/or experienced by the indicated network entity on some or all resource blocks. Further, the receiving network entity may utilize the one or more NE-to-NE interference overload indication IEs when creating the one or more scheduling policies, and may consider the one or more NE-to-NE interference overload indication IE values to be valid until one or more new messages are received, the one or more new messages including an updated version of the one or more UE-to-UE interference overload indication IEs.
In step 209, any NE may update the link direction deviation control parameter. In step 211, any NE may transmit and/or receive signals using the adjusted one or more link direction deviation control parameters.
Fig. 4 illustrates an example event-triggering mechanism for generating one or more CLI overload indications, one for every N slots. For example, the event triggering mechanism may be applicable to multiple UEs, where one cell serves only one UE in one time slot, and allows different UEs to be served in different time slots. At each time slot, the NE and/or UE may measure the current UL/DL SINR, the power of NE-to-NE interference, and/or UE-to-UE interference. The UE should transmit the relevant measurements to its serving network entity so that the network entity can calculate the mean UL/DL SINR over the previous N time slots.
An NE-to-NE and/or UE-to-UE interference overload indication may be triggered once the one or more mean UL/DL SINRs are less than the one or more corresponding thresholds. In response, the network entity may send one or more UE-to-UE interference overload indication IEs and/or NE-to-NE interference overload indication IEs indicating high, medium, and/or low interference values. The interference value may be transmitted to one or more identified interfering cells that cause the smallest corresponding amount of UL/DL SINR at different time slots. E.g. in different time slots t1、t2And t3At the minimum corresponding amount of UL/DL SINR and at time slot t1、t3And t3Where the maximum NE-to-NE interference received may come from neighboring cell m, respectively1、m2And m3. Therefore, the network cells can respectively move to the adjacent cells m1、m2And m3The NE to NE interference overload indication IE is sent with "high interference", "medium interference" and "low interference" values. Thus, one or more link direction deviation control parameters may be updated for every N slots/symbols.
In step 401, the parameter n may be set to a value such as 0. In step 403, it may be determined whether slot n is a UL slot or a DL slot. If slot n is a DL slot, the UE measures the DL SINR and/or UE-to-UE interference power from all neighboring cells and then identifies the aggressor cell with the largest UE-to-UE interference in step 405. In step 407, the UE transmits the measured SINR value and/or the identity of the aggressor cell to its serving network entity. If it is determined in step 403 that time slot n is UL, then in step 409 the network entity measures the UL SINR and NE-to-NE interference power from all neighboring cells and then identifies the aggressor cell with the largest NE-to-NE interference.
In step 411, in some examples, it is determined that N is equal to (N +1, N), and the method returns to step 403. In step 413, in some examples, it is determined whether N-1, and if so, in step 415, the network entity calculates the mean UL and DL SINR over the first N slots. In some embodiments, the step size may be adapted based on one or more of CLI measurements, information exchanged by one or more network entities, and/or other higher layer signaling. In step 417, it is determined whether the mean UL SINR is less than a threshold, and if so, in step 419 the network entity sends one or more NE-to-NE interference overload indication IEs with "high interference", "medium interference" and "low interference" values to a plurality of aggressor cells that caused a corresponding minimum amount of UL SINR at the corresponding time slot. In parallel, in step 421, it is determined whether the mean DL SINR is less than a threshold, and if so, in step 423, the network entity sends one or more NE-to-NE interference overload indication IEs with "high interference", "medium interference", and "low interference" values to a plurality of aggressor cells that caused a corresponding minimum number of UL SINR at corresponding time slots.
Fig. 5 illustrates a strategy for updating link direction deviation control parameters. In step 501, one or more network entities may receive one or more NE-to-NE/UE-to-UE interference overload indication IEs from one or more neighboring cells. In step 503, if one or more network entities receive the NE-to-NE interference overload indication IE, a determination is made whether an aggressor cell is causing NE-to-NE interference. If the aggressor cell is causing NE to NE interference, then in step 505, Δn DL=max{Δn DL-1,0}. If the aggressor cell is not causing NE to NE interference, then in step 507, Δn DL=min{Δn DL+1,N}。
In step 509, if one or more network entities receive the UE-to-UE interference overload indication IE, it is determined whether an aggressor cell is causing UE-to-UE interference. If the aggressor cell is causing UE-to-UE interference, then in step 511, Δn UL=max{Δn UL-1,0}. If an aggressor cell is not causing UE-to-UE interference,then in step 513, Δn UL=min{Δn UL+1,N}。
In some examples, the designed update strategy may involve a negative feedback mechanism, which may improve the stability and performance of the parameter update process. The negative feedback mechanism may encompass various algorithms used to determine whether a cell is an aggressor cell of NE-to-NE/UE-to-UE interference. Each cell may employ different criteria and/or algorithms. For example, one or more simple majority and/or minority mechanisms may be applied. For most mechanisms, if more than half of the neighboring cells advertise via CLI overload IEs one or more cells causing high interference in the NE-to-NE/UE-to-UE, then that cell may be considered an aggressor cell of NE-to-NE/UE-to-UE interference. Alternatively, for a few mechanisms, one or more cells may be identified as aggressor cells of NE-to-NE/UE-to-UE interference — as long as one cell advertises via CLI overload IE that it is high interference in NE-to-NE/UE-to-UE interference.
In some examples, a max-min traffic matching scheme may be applied with closed loop link direction deviation control. For example, as illustrated in fig. 6, a system may consist of macro cells in a regular hexagonal grid. For example, each cell may adjust the UL/DL transmission ratio every N-10 slots based on UL/DL traffic demand and CLI overload indication IEs transmitted from neighboring cells. Given the required UL/DL traffic ratio Δ for cell ndemand,n ULdemand,n DLSo that N isdemand,n UL+Ndemand,n DLThe ideal traffic match may be N for all cellsn UL/Ndemand,n UL=Nn DL/Ndemand,n DL=1。Nn UL/Ndemand,n ULAnd Nn DL/Ndemand,n DLMay be a traffic matching factor. Thus, traffic adaptation may be improved by the traffic matching factors of all cells being closer to unity. To achieve UL/DL traffic adaptation, the minimum traffic matching factor may be in { N }n UL,Nn DLIs maximized. Minimum flowThe matching factor may be equal to the set Nn X/Ndemand,n X|X∈{UL,DL},n∈ScellThe smallest element in (c). When in constraint Nn UL+Nn DLApplying this criterion at N, the maximum flow matching factor may be reduced.
Fig. 7 illustrates an example method performed by a network entity, according to some examples. The network entity may be similar to network entity 910, as illustrated in fig. 9. In step 701, the network entity may assign an initial or updated value to the uplink direction deviation control parameter and an initial or updated value to the downlink direction deviation control parameter. In step 703, the network entity may apply a time division duplex mode configuration that ensures that the link direction deviation meets a predefined criterion, such as one or more quality metric parameters. In some examples, any of the NEs may select N _ N that satisfies one or more currently used bias control constraints based on a link direction control parameter such as/Delta _ N. In step 705, a network entity may receive a cross-link interference measurement. In step 707, the network entity may exchange one or more CLI measurement indication information elements with one or more network entities. In step 709, the network entity may update one or more link direction deviation control parameters based at least on the one or more cross-link interference overload indications. In step 711, the network entity may transmit and/or receive a signal using the adjusted one or more link direction deviation control parameters.
Fig. 8 illustrates an example method performed by a user equipment, according to some examples. The user device may be similar to user device 920, as illustrated in fig. 9. In step 801, if time slot n is a downlink time slot, the user equipment may measure DL SINR and/or UE-to-UE interference power from one or more neighboring cells. In step 803, the user equipment may identify an aggressor cell with the largest UE-to-UE interference. In step 805, the user equipment may transmit the measured SINR value and/or the identity of the aggressor cell to the serving network entity. The network entity may be similar to network entity 910, as illustrated in fig. 9. In some examples, the measured SINR value and/or the identification of aggressor cells may be configured to calculate a mean UL and/or DL SINR over the previous N time slots.
Fig. 9 illustrates an example of a system according to some examples. In one example, a system may include multiple devices, such as, for example, a network entity 910 and a user equipment 920.
The UE 920 may include one or more of the following: a mobile device such as a mobile phone, a smart phone, a Personal Digital Assistant (PDA), a tablet or portable media player, a digital camera, a camcorder, a video game, a navigation unit such as a Global Positioning System (GPS) device, a desktop or laptop computer, a single positioning device such as a sensor or smart meter, or any combination thereof. Network entity 910 may be one or more of the following: a base station such as an evolved node b (enb) or 5G or a new wireless node b (gnb), a serving gateway, a server, and/or any other access node or combination thereof. Further, the user equipment 920 and/or the network entity 910 may be one or more of a citizen broadband radio service device (CBSD).
One or more of these devices may include at least one processor, indicated as 911 and 921, respectively. At least one memory indicated at 912 and 922 may be provided in one or more devices. The memory may be fixed or removable. The memory may include computer program instructions or computer code embodied therein. The processors 911 and 921 and the memories 912 and 922, or a subset thereof, may be configured to provide means corresponding to the respective blocks of fig. 1-8. Although not shown, the device may also include positioning hardware, such as GPS or micro-electro-mechanical systems (MEMS) hardware, which may be used to determine the location of the device. Other sensors are also permitted and may be included to determine position, altitude, orientation, and the like, such as a barometer, compass, and the like.
As shown in fig. 9, transceivers 913 and 923 can be provided, and one or more devices can also include at least one antenna, illustrated as 914 and 924, respectively. The device may have a number of antennas, such as an antenna array configured for multiple-input multiple-output (MIMO) communication or multiple antennas for multiple radio access technologies. For example, other configurations of these devices may be provided.
The transceivers 913 and 923 may be transmitters, receivers, or both transmitters and receivers, or may be units or devices that may be configured for both transmission and reception.
The processors 911 and 921 may be embodied by any computing or data processing device, such as a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or similar device. The processor may be implemented as a single controller or as multiple controllers or processors.
Memories 912 and 922 may independently be any suitable storage device, such as a non-transitory computer-readable medium. A Hard Disk Drive (HDD), Random Access Memory (RAM), flash memory, or other suitable memory may be used. The memory may be combined as the processor on a single integrated circuit or may be separate from the processor or processors. Furthermore, the computer program instructions stored in the memory and processable by the processor may be any suitable form of computer program code, such as a compiled or interpreted computer program written in any suitable programming language. The memory may or may not be removable.
The memory and computer program instructions may be configured with a processor for a particular device to cause a hardware apparatus, such as a user device, to perform any of the processes described below (e.g., see fig. 1-8). Thus, in certain examples, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, some examples may be performed entirely in hardware.
In some examples, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in fig. 1-8. For example, the circuitry may be hardware-only circuit implementations, such as analog and/or digital circuitry. In another example, the circuitry may be a combination of hardware circuitry and software, such as a combination of analog and/or digital hardware circuit(s) and software or firmware, and/or any portion of hardware processor(s) with software (including digital signal processor (s)), software, and at least one memory that work together to cause the apparatus to perform various processes or functions. In yet another example, the circuitry may be hardware circuit(s) and/or processor(s), such as microprocessor(s) or a portion of microprocessor(s), including software, such as firmware, for operation. Software in the circuitry may not be present when it is not required for hardware operation.
One of ordinary skill in the art will readily appreciate that certain examples described above may be practiced with steps in a different order and/or with hardware elements in configurations other than those disclosed. It will thus be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be apparent, while remaining within the spirit and scope of the invention. Therefore, to ascertain the metes and bounds of the invention, the appended claims should be referenced.
Part glossary
3GPP third generation partnership project
5G fifth generation wireless system
CDF cumulative distribution function
CLI cross-link interference
DL downlink
eIMTA enhanced interference mitigation and traffic adaptation
gNB next generation node
IE information element
LTE Long term evolution
NR new radio
OFDM orthogonal frequency division multiplexing
OI overload indication
SINR signal-to-interference-and-noise ratio
TDD time division duplex
TRP transmission receiving point
UE user equipment
UL uplink

Claims (16)

1. An apparatus, comprising:
at least one processor; and
at least one memory including computer program code,
wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to:
receiving one or more cross-link interference overload indications;
updating one or more link direction deviation control parameters based at least on the one or more cross-link interference overload indications; and
transmitting and/or receiving a signal using the adjusted one or more link direction deviation control parameters.
2. The apparatus of claim 1, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to:
an initial or updated value is assigned to the uplink direction deviation control parameter and an initial or updated value is assigned to the downlink direction deviation control parameter.
3. The apparatus of any of claims 1 or 2, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to:
applying a time division duplex mode configuration that ensures that the link direction deviation meets a predefined criterion.
4. The apparatus of any of claims 1-3, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to:
measuring one or more of: cross-link interference between the apparatus and a network entity, and cross-link interference between a first user equipment and a second user equipment.
5. The apparatus of any of claims 1-4, wherein the one or more link direction deviation control parameters are updated based on one or more cross-link interference overload indications transmitted by the apparatus.
6. A method, comprising:
receiving, by a network entity, one or more cross-link interference overload indications;
updating, by the network entity, one or more link direction deviation control parameters based at least on the one or more cross-link interference overload indications; and
transmitting and/or receiving, by the network entity, a signal using the adjusted one or more link direction deviation control parameters.
7. The method of claim 6, further comprising:
assigning, by the network entity, an initial or updated value to an uplink direction deviation control parameter and an initial or updated value to a downlink direction deviation control parameter.
8. The method of any of claims 6 or 7, further comprising:
applying, by the network entity, a time division duplex mode configuration that ensures that the link direction deviation meets a predefined criterion.
9. The method according to any one of claims 6-8, further comprising:
measuring, by the network entity, one or more of: cross-link interference between the apparatus and a network entity, and cross-link interference between a first user equipment and a second user equipment.
10. The method of claims 6-9, wherein the one or more link direction deviation control parameters are updated based on one or more cross-link interference overload indications transmitted by the apparatus.
11. An apparatus, comprising:
at least one processor; and
at least one memory including computer program code,
wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to:
if the time slot n is a downlink time slot, measuring DL SINR and/or UE-to-UE interference power from one or more neighboring cells;
identifying an aggressor cell with maximum UE-to-UE interference; and
transmitting one or more measured SINR values and/or an identification of the aggressor cell to a serving network entity.
12. A method, comprising:
if the time slot n is a downlink time slot, measuring, by the user equipment, DL SINR and/or UE-to-UE interference power from one or more neighboring cells;
identifying, by the user equipment, an aggressor cell with maximum UE-to-UE interference; and
transmitting, by the user equipment, one or more measured SINR values and/or an identification of the aggressor cell to a serving network entity.
13. A non-transitory computer-readable medium encoding instructions that, when executed in hardware, perform the process of any of claims 1-12.
14. An apparatus comprising means for performing a process according to any one of claims 1-12.
15. An apparatus comprising circuitry configured to cause the apparatus to perform the process of any of claims 1-12.
16. A computer program product encoded with instructions for performing a process according to any of claims 1-12.
CN201880094429.8A 2018-06-08 2018-06-08 Bias control for dynamic time division duplexing Pending CN112292881A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/090446 WO2019232787A1 (en) 2018-06-08 2018-06-08 Bias control for dynamic time-division duplexing

Publications (1)

Publication Number Publication Date
CN112292881A true CN112292881A (en) 2021-01-29

Family

ID=68770735

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201880094429.8A Pending CN112292881A (en) 2018-06-08 2018-06-08 Bias control for dynamic time division duplexing

Country Status (2)

Country Link
CN (1) CN112292881A (en)
WO (1) WO2019232787A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113438674B (en) * 2021-06-24 2022-08-12 中国联合网络通信集团有限公司 Method and device for reducing control channel cross link interference

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102007789A (en) * 2009-11-12 2011-04-06 高通股份有限公司 Apparatus and method for facilitating dynamic time slot allocation
US20140269456A1 (en) * 2011-10-20 2014-09-18 Haiming Wang Method, an Apparatus and a Computer Program Product for Flexible TDD Configuration
EP2840851A1 (en) * 2013-08-21 2015-02-25 Nokia Corporation UL-DL Interference Management for TDD eIMTA

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2447889B (en) * 2007-03-21 2012-02-29 Motorola Mobility Inc Power control in a cellular communication system
US9768929B2 (en) * 2012-12-21 2017-09-19 Blackberry Limited Method and apparatus for identifying interference type in time division duplex systems
CN107453834A (en) * 2016-05-31 2017-12-08 华为技术有限公司 A kind of descending interference management method, base station and user equipment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102007789A (en) * 2009-11-12 2011-04-06 高通股份有限公司 Apparatus and method for facilitating dynamic time slot allocation
US20140269456A1 (en) * 2011-10-20 2014-09-18 Haiming Wang Method, an Apparatus and a Computer Program Product for Flexible TDD Configuration
EP2840851A1 (en) * 2013-08-21 2015-02-25 Nokia Corporation UL-DL Interference Management for TDD eIMTA

Also Published As

Publication number Publication date
WO2019232787A1 (en) 2019-12-12

Similar Documents

Publication Publication Date Title
EP3225044B1 (en) Methods and apparatus for enabling proximity services in mobile networks
US10412691B1 (en) Use of power headroom as basis to control configuration of MU-MIMO service
EP2491749B1 (en) Communication system for inter-cell coordination
US9288772B2 (en) Method and system for self-organizing networks using cooperative sensing
CN108632968B (en) Method and apparatus for uplink power control
US10015829B2 (en) Controlling interference
CN108112065B (en) Method and device for determining transmission power and configuring signaling, terminal and base station
CN113597799B (en) Apparatus, method and computer readable medium for adjusting a beamforming profile
JP7391941B2 (en) Power control method and device, method and device for determining target received power
US10757599B1 (en) Use of block error rate as basis to control configuration of MU-MIMO service
US11265816B2 (en) Beam based uplink (UL) power control
US9554379B2 (en) Method and network node for link adaptation in a wireless communications network
US9467265B2 (en) Method and access point for assigning sounding resources
US10602478B1 (en) Use of mobility as basis to control configuration of MU-MIMO service
US8761682B2 (en) Distributed interference management
US11337113B2 (en) Use of uplink communication quality as basis to control split-uplink operation for dual-connectivity service
US11700584B1 (en) Use of power class as basis to control configuration of MU-MIMO service
US10477435B2 (en) Resource allocation method and apparatus
CN110536392B (en) Power control method, device, equipment and storage medium
WO2018127100A1 (en) Uplink power control method and communication apparatus
CN112292881A (en) Bias control for dynamic time division duplexing
EP3516802B1 (en) Method and apparatus for providing channel state information status by a transceiver
US20190200336A1 (en) Method And Apparatus For Scheduling User Device In Multi-User Multi-Input Multi-Output Wireless System
CN110856250A (en) Scheduling method, base station, and computer-readable medium
US20230353294A1 (en) Network slicing in cellular systems

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination