Method and Network Node for Interference Mitigation for TDD UL/DL Configuration

Abstract

There is presented a method for a network node for reducing interference in a wireless device (200), the wireless device operating using a time division duplex, TDD, configuration in a cell, from at least another wireless device operating in a neighbouring cell using another TDD configuration. The TDD configuration is divided into different time units for at least downlink, DL, and uplink, UL, transmission. The method includes assigning time units in the TDD configuration to one of at least two time unit groups, where the assignment of a time unit to a time unit group is based the interference from the neighboring cell using the another TDD configuration. The method further includes using different link adaptions for the at least two time unit groups. The is also presented a network node.

Claims

1.-32. (canceled)

33. A method in a network node for reducing the impact of interference in a cell from at least another neighbouring cell, the cell operating using a time division duplex (TDD) configuration, and the neighbouring cell operating using another TDD configuration, where the TDD configuration and the another TDD configuration are each divided into different time units for at least downlink (DL) and uplink (UL) transmissions, the method comprising: assigning time units in the TDD configuration to one of at least two time unit groups, where assignment of a time unit to a time unit group is based on the another TDD configuration used in the neighbouring cell; and using different link adaptation methods for the at least two time unit groups.

34. The method according to claim 33, where one time unit group comprises fixed slots and an at least another time unit group comprises varying slots.

35. The method according to claim 33, where assignment of time units to the at least two time unit groups is such that time units experiencing cross-link interference from the neighbouring cell using the another TDD configuration are assigned to one group and the other time units in the TDD configuration are assigned to another group.

36. The method according to claim 35, where a more robust Modulation and Coding Scheme (MCS) is used for the time unit group experiencing cross-link interference from the neighbouring cell using the another TDD configuration compared to the MCS used for the at least another time unit group.

37. The method according to claim 35, where a signal-to-noise ratio (SNR) threshold for selection of a MCS is different for the time unit group most experiencing cross-link interference from neighboring cell using the another TDD configuration compared to the SNR threshold for the other time unit group not experiencing cross-link interference.

38. The method according to claim 33, where using different link adaptation methods comprises using different link adaptation outer loop instances for the at least two time unit groups.

39. The method according to claim 33, where different HARQ processes are used for the at least two different time unit groups.

40. The method according to claim 39, where the HARQ processes associated with the at least two different time unit groups are associated with different link adaptation outer loops.

41. The method according to claim 33, where the HARQ-feedback (ACK/NACK) associated with a time unit group in downlink is transmitted in a time unit in the same time unit group in uplink.

42. The method according to claim 33, where a UL Downlink Control Information (DCI) associated with a UL time unit group is transmitted in the same time unit group in downlink.

43. The method according to claim 33, where control signalling is transmitted in the time unit group experiencing the least interference from the neighbouring cell using the another TDD configuration.

44. The method according to claim 43, wherein the control signaling comprises radio link control (RCL) signaling or radio resource control (RRC) signalling.

45. The method according to claim 33, where the time units are the time units for at least one of sub-frames, slots and symbols.

46. The method according to claim 33, where the time units in the time unit groups are scheduled downlink time units, uplink time units, special downlink time units or flexible time units.

47. The method according to claim 33, where the network node and a wireless device operate in the cell using the TDD configuration, and another network node and another wireless device operate in the neighbouring cell using the another TDD configuration.

48. The method according to claim 47, where the impact of the interference is reduced in the wireless device and/or the network node operating the cell.

49. A network node configured to reduce the impact of interference in a cell from at least another neighbouring cell, the cell configured to operate using a time division duplex (TDD) configuration, and the neighbouring cell configured to operate using another TDD configuration, where the TDD configuration and the another TDD configuration are each divided into different time units for at least downlink (DL) and uplink (UL) transmissions, network node comprising: a processing circuitry and a memory for storing program code that is executable by the processor circuitry whereby the network node is configured to: assign time units in the TDD configuration to one of at least two time unit groups, where assignment of a time unit to a time unit group is based on the another TDD configuration used in the neighbouring cell; and use different link adaptation methods for the at least two time unit groups.

50. A computer readable storage medium on which is stored a computer program for reducing the impact of interference in a cell from at least another neighbouring cell, the cell operating using a time division duplex (TDD) configuration, and the neighbouring cell operating using another TDD configuration, where the TDD configuration and the another TDD configuration are each divided into different time units for at least downlink (DL) and uplink (UL) transmissions, the computer program comprising computer code which, when run on processing circuitry of a network node, causes the network node to: assign time units in the TDD configuration to one of at least two time unit groups, where assignment of a time unit to a time unit group is based on the another TDD configuration used in the neighbouring cell; and use different link adaptation methods for the at least two time unit groups.

Description

DETAILED DESCRIPTION

[0017] The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the inventive concept are shown. This inventive concept may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. Like numbers refer to like elements throughout the description. Any step or feature illustrated by dashed lines should be regarded as optional.

[0018] FIG. 3 is a schematic diagram illustrating a communications network 100a where embodiments presented herein can be applied. The communications network 100a could be a third generation (3G) telecommunications network, a fourth generation (4G) telecommunications network, or a fifth (5G) telecommunications network and support any 3GPP telecommunications standard.

[0019] The communications network 100a comprises a transmission point, TP, 140 including an antenna device 500 which may be a Multiple-Input Multiple-Output (MIMO) antenna including two or more antennas. The antenna device 500 is connected to a radio device 400. The communications network 100a further includes the network node 200, which may include one or more TPs. The network node is configured to, in a radio access network 110, provide network access to a user equipment (UE) 300. The radio access network 11o is operatively connected to a core network 120. The core network 120 is in turn operatively connected to a service network 130, such as the Internet. The UE 300 is thereby, via network node and the transmission point 140, enabled to access services of, and exchange data with, the service network 130. Examples of network nodes are radio access network nodes, radio base stations, base transceiver stations, Node Bs, evolved Node Bs, g Node Bs, gNBs, access points, access nodes, antenna integrated radios (AIRs), and transmission and reception points (TRPs). A UE may also be referred to as a wireless device. Other examples of UEs are terminal devices, mobile stations, mobile phones, handsets, wireless local loop phones, smartphones, laptop computers, tablet computers, network equipped sensors, network equipped vehicles, and so-called Internet of Things devices.

[0020] Typically, the structure of the transmitted signal in a communication system is organized in the form of a frame structure. For example, LTE uses ten equally-sized subframes of length 1 ms per radio frame as illustrated in FIG. 4.

[0021] LTE and NR use Orthogonal Frequency Division Multiplexing (OFDM) in the downlink direction and a Discrete Fourier Transform (DFT)-spread OFDM in the uplink direction. The basic LTE downlink physical resource can thus be seen as a time-frequency grid, where each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval. In the time domain, LTE downlink transmissions may be organized into radio frames of 10 ms, with each radio frame consisting of ten equally-sized subframes of length Tsubframe=1 ms.

[0022] Furthermore, the resource allocation in LTE is typically described in terms of resource blocks, where a resource block corresponds to one slot, e.g., 0.5 ms, in the time domain and 12 subcarriers in the frequency domain. A pair of two adjacent resource blocks in time direction, e.g., 1.0 ms, is known as a resource block pair. Resource blocks are numbered in the frequency domain, starting with 0 from one end of the system bandwidth.

[0023] NR terminology and LTE terminology coincide to a considerable extent; for instance, a resource element (RE) remains 1 subcarrier×1 OFDM symbol. Yet some terms known in LTE have been given a new meaning in NR. This disclosure, including the claims, applies prefixes “LTE” and “NR” when indefiniteness could otherwise arise.

[0024] Any term designating an object or operation known from LTE is expected to be reinterpreted functionally in view of NR specifications. Examples: An LTE radio frame may be functionally equivalent to an NR frame, considering that both have a duration of 10 ms. An LTE eNB may be functionally equivalent to an NR gNB, since their functionalities as downlink transmitter are at least partially overlapping. The least schedulable resource unit in LTE may be reinterpreted as the least schedulable resource unit in NR. The shortest data set for which LTE acknowledgement feedback is possible may be reinterpreted as the shortest data set for which NR acknowledgement feedback is possible.

[0025] Therefore, even though some embodiments of this disclosure have been described using LTE-originated terminology or NR-originated terminology, they remain fully applicable to NR technology or LTE technology, respectively. Further throughout the embodiments the term subframe is completely interchangeable with the term slot.

[0026] In case of FDD operation, illustrated in the left part of FIG. 1, there are two carrier frequencies, one for uplink transmission (fUL) and one for downlink transmission (fDL). At least with respect to the terminal in a cellular communication system, FDD may be either full duplex or half duplex. In the full duplex case, a terminal may transmit and receive simultaneously, while in half-duplex operation, the terminal may not transmit and receive simultaneously. The base station is capable of simultaneous reception/transmission though, e.g., receiving from one terminal while simultaneously transmitting to another terminal. In LTE, a half-duplex terminal is monitoring/receiving in the downlink except when explicitly being instructed to transmit in a certain subframe.

[0027] In case of TDD operation, illustrated in the right part of FIG. 1, there is only a single carrier frequency and uplink and downlink transmissions are always separated in time also on a cell basis. As the same carrier frequency is used for uplink and downlink transmission, both the base station and the mobile terminals need to switch from transmission to reception and vice versa. An aspect of any TDD system is to provide the possibility for a sufficiently large guard time where neither downlink nor uplink transmissions occur. This is required to avoid interference between uplink and downlink transmissions.

[0028] For LTE, this guard time is provided by special subframes, e.g., subframe 1 and, in some cases, subframe 6 of a frame, which are split into three parts: a downlink part (DwPTS), a guard period (GP), and an uplink part (UpPTS), as illustratively shown in FIG. 4. The remaining subframes are either allocated to uplink or downlink transmission.

[0029] TDD allows for different asymmetries in terms of the amount of resources allocated for uplink and downlink transmission, respectively, by means of different uplink-downlink configurations. In LTE, there are seven different configurations as shown in Table 1. It should be appreciated that a DL subframe may mean either DL or the special subframe.

[0030] In TDD, some subframes/slots/symbols are allocated for uplink transmissions and some subframes/slots/symbols are allocated for downlink transmissions. The switch between downlink and uplink occurs in the so called special subframes (LTE) or flexible subframes (NR).

TABLE-US-00001 TABLE 1 LTE uplink-downlink configurations (from 36.211, Table 4.2-2) Uplink- Downlink- downlink to-Uplink config- Switch-point Subframe number uration periodicity 0 1 2 3 4 5 6 7 8 9 0 5 ms D S U U U D S U U U 1 5 ms D S U U D D S U U D 2 5 ms D S U D D D S U D D 3 10 ms  D S U U U D D D D D 4 10 ms  D S U U D D D D D D 5 10 ms  D S U D D D D D D D 6 5 ms D S U U U D S U U D

[0031] The size of the guard period (and hence the number of symbols for DwPTS and UwPTS in the special subframe) can also be configured from a set of possible selections.

[0032] NR on the other hand provides many different uplink-downlink configurations. There are 10 to 320 slots per radio frame (where each radio frame has a duration of 10 ms) depending on subcarrier spacing. Each slot can be configured with a slot format as shown in Table 2. The OFDM symbols in a slot are classified as ‘downlink’ (denoted ‘D’ in Table 2), ‘flexible’ (denoted ‘X’), or ‘uplink’ (denoted ‘U’), if dynamic Slot Format Indication (SFI) is used where the format of a slot is indicated with DCI Format 2_0. As an alternative to this, a semi-static TDD UL-DL configuration may be used where the TDD configuration is RRC configured using the IE TDD-UL-DL-ConfigCommon:

TABLE-US-00002 TDD-UL-DL-ConfigCommon ::= SEQUENCE {  -- Reference SC    to determine the time domain boundaries in the L-DL pattern which must be common across all subcarrier specific  -- virtual carr s, i.e., independent of the actual subcarrier spacing using for data transmission.  -- Only the values 15 or 30 kHz <6GHz , 60 or 120 kHz ( 6 Hz) are applicable.  -- Corresponds to L1 parameter ‘reference CS’ (  3 .211, section _Section)  referenceSubcarrierSpacing  SubcarrierSpacing  -- Periodicity of the DL-UL pattern. Corresponds to L1 parameter ‘ L-DL- transmission-periodicity’ (   .211, section _Section)  dl-UL-TransmissionPeriodicity  ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10}  OPTIONAL,  -- Number of consecutive full D  slots at the beginning of each DL-UL pattern.  -- Corresponds to L1 parameter ‘number-of-DL-slots’ (see 38.211, Table 4.3.2-1  nrofDownlinkSlots  INTEGER (0..maxNrofSlots)  -- Number of consecutive DL symbols in the beginning of the  following the last full DL slot (as derived   Slots).  -- If the field is absent or released, there is no partial-downlink slot.  -- Corresponds to L1 parameter ‘number of L symbols common’ (   .211, section _Section).  nrofDownlinkSymbols  INTEGER (0..maxNrofSymbols-1)  -- Number of consecutive full UL slots at the end of   L- L pattern.  -- Corresponds to L1 parameter ‘number of L slots’ (   .211, Table 4. .2-1)  nrofUplinkSlots  INTEGER (0..maxNrofSlots)  -- Number of consecutive UL symbols in the end of the slot preceding the first full UL slot (as derived from UplinkSlots).  -- If the field is absent or released, there is no partial-uplink slot.  -- Corresponds to L1 parameter ‘number-of-UL-symbols-common’ (  38.211, section _Section) nrofUplinkSymbols  INTEGER (0..maxNrofSymbols-1) indicates data missing or illegible when filed

[0033] That is, the number of UL and DL slots, as well as the guard period (the number of UL and DL symbols in the flexible slot(s)) may be almost arbitrarily configured within the TDD periodicity. This allows for very flexible uplink-downlink configurations.

TABLE-US-00003 TABLE 2 NR slot formats (from 38.211, Table 4.3.2-3) For- Symbol number in a slot mat 0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 D D D D D D D D D D D D D D 1 U U U U U U U U U U U U U U 2 X X X X X X X X X X X X X X 3 D D D D D D D D D D D D D X 4 D D D D D D D D D D D D X X 5 D D D D D D D D D D D X X X 6 D D D D D D D D D D X X X X 7 D D D D D D D D D X X X X X 8 X X X X X X X X X X X X X U 9 X X X X X X X X X X X X U U 10 X U U U U U U U U U U U U U 11 X X U U U U U U U U U U U U 12 X X X U U U U U U U U U U U 13 X X X X U U U U U U U U U U 14 X X X X X U U U U U U U U U 15 X X X X X X U U U U U U U U 16 D X X X X X X X X X X X X X 17 D D X X X X X X X X X X X X 18 D D D X X X X X X X X X X X 19 D X X X X X X X X X X X X U 20 D D X X X X X X X X X X X U 21 D D D X X X X X X X X X X U 22 D X X X X X X X X X X X U U 23 D D X X X X X X X X X X U U 24 D D D X X X X X X X X X U U 25 D X X X X X X X X X X U U U 26 D D X X X X X X X X X U U U 27 D D D X X X X X X X X U U U 28 D D D D D D D D D D D D X U 29 D D D D D D D D D D D X X U 30 D D D D D D D D D D X X X U 31 D D D D D D D D D D D X U U 32 D D D D D D D D D D X X U U 33 D D D D D D D D D X X X U U 34 D X U U U U U U U U U U U U 35 D D X U U U U U U U U U U U 36 D D D X U U U U U U U U U U 37 D X X U U U U U U U U U U U 38 D D X X U U U U U U U U U U 39 D D D X X U U U U U U U U U 40 D X X X U U U U U U U U U U 41 D D X X X U U U U U U U U U 42 D D D X X X U U U U U U U U 43 D D D D D D D D D X X X X U 44 D D D D D D X X X X X X U U 45 D D D D D D X X U U U U U U 46 D D D D D D X D D D D D D X 47 D D D D D X X D D D D D X X 48 D D X X X X X D D X X X X X 49 D X X X X X X D X X X X X X 50 X U U U U U U X U U U U U U 51 X X U U U U U X X U U U U U 52 X X X U U U U X X X U U U U 53 X X X X U U U X X X X U U U 54 D D D D D X U D D D D D X U 55 D D X U U U U D D X U U U U 56 D X U U U U U D X U U U U U 57 D D D D X X U D D D D X X U 58 D D X X U U U D D X X U U U 59 D X X U U U U D X X U U U U 60 D X X X X X U D X X X X X U 61 D D X X X X U D D X X X X U 62- Reserved 255

[0034] To avoid severe interference between downlink and uplink transmissions between different cells, neighbor cells should have the same downlink/uplink configuration. If this is not done, uplink transmission in one cell may interfere with downlink transmission in the neighboring cell and vice versa.

[0035] In reconfigurable TDD systems, the TDD configuration may be changed depending on traffic demands on a cell-by-cell basis. As a result, two neighboring base stations may use respective different resource allocations for UL and DL, which may result in DL-to-UL interference, i.e., transmitting base station to receiving base station interference. DL-to-UL interference, will be referred to herein as cross-link interference (CLI), occurs when one base station, referred to herein as a base station, is transmitting on the DL, while a second base station is receiving transmissions from a UE in the UL. The different resource allocations result in interference.

[0036] FIG. 5 illustratively shows the TDD configurations of two neighbouring cells. It is assumed that the cells are synchronized. If the cells belong to different networks it is assumed that the networks are synchronized.

[0037] In FIG. 5a, one of the UEs has a TDD configuration that is more ‘downlink heavy’. The definition of ‘downlink heavy’ is that the TDD configuration has more subframes or slots available for DL. ‘Uplink heavy’ is defined by TDD configurations having more subframes or slots available for UL. As can be seen from FIG. 5a, subframes or slots where one cell is configured for uplink and the other cell is configured for downlink, or vice versa, are referred to as varying subframes or slots. Subframes or slots where one cell is configured for uplink and the other cell is also configured for uplink, both cells may also be configured for downlink, are referred to as fixed subframes or slots. CLI mainly occurs in the varying subframes or slots as both cells/networks transmit in the same direction in the fixed subframes or slots.

[0038] If two UEs belong to different cells that are in turn scheduled with different uplink-downlink configurations and are near each other as illustrated in FIG. 2, the UE with more DL slots, referred to as Rx UE, will experience interference on the varying slots used for downlink. The UE with more UL slots, referred to as Tx UE, may experience less crosslink interference compared to the Rx UE. This is illustratively shown in FIG. 5b, where it is assumed that the neighbouring UEs are so close that they may experience CLI and other interferences due to their proximity to each other.

[0039] In FIG. 5c the slots are grouped into at least two categories of slots. The first group, Group A, includes varying slots, i.e. slots that are mainly affected by crosslink interference. The second group, Group B, includes slots that are not affected by crosslink interference.

[0040] In another embodiment the slots are grouped into at least two categories of groups. The first group, Group A, includes varying slots, i.e. slots that are more likely to be affected by interference, crosslink interference in particular. The second group, Group B, includes slots that are less likely to be affected by crosslink interference. The slots can be grouped into further groups based on how likely it is that they are affected by crosslink interference.

[0041] In cases where regulations allow only a few different uplink-downlink configurations to be used, the grouping of slots can be configured once and then kept fixed. In this case, the actual uplink-downlink configurations used for the cells in the network don't have to be known when configuring the grouping, it is enough to know that the uplink-downlink configuration is one of a few possible configurations. The grouping may also be dynamic, taking into account which uplink-downlink configurations adjacent cells (co-channel or adjacent channel) are configured with. If these configurations change, the grouping may be updated.

[0042] The at least two slot groups are then treated separately for link adaptation and/or scheduling, thereby reducing the impact of the cross-link interference on e.g. throughput.

[0043] FIG. 6 shows method steps of embodiments disclosed herein. The method is performed by a network node (300) and purpose of the method is to reduce the impact of crosslink interference on transmissions between a wireless device (200) and a network node (300). The wireless device is configured with a certain TDD configuration in the cell, for example one of the configurations in Table 1 or Table 2. The wireless device may experience CLI from another neighbouring wireless device operating in a neighbouring cell using another TDD configuration. For example, one wireless device may belong to a cell configured with uplink-downlink configuration 2 in Table 1 and the neighbouring wireless device may belong to a cell configured with uplink-downlink configuration 3 in Table 1. TDD configurations are divided into different time units for at least downlink, DL, and uplink, UL, transmission, and therefore the wireless device can either receive or transmit in a time unit. A time unit may have the length of a subframe, a slot and/or a symbol. The time unit is in some embodiments a time period, for example 1 ms. In the illustrative embodiments subframe, slot and symbol may be interchangeably used. Although some illustrative embodiments are disclosed for slot time unit, the embodiments are also applicable to symbol time unit or subframe time unit.

[0044] In step 601 the network node assigns time units in a TDD configuration to one of at least two time unit groups. The assignment of a time unit to a time unit group is based on the TDD configurations that are used in the serving cell and in at least one neighbouring cell.

[0045] In an exemplary embodiment it is assumed a first NR TDD slot configuration for 30 kHz sub-carrier spacing as shown in FIG. 7a. The TDD configuration includes DL slots (D), UL slots (U), and special DL slots (S). This could represent the TDD configuration used by the serving cell and a wireless device. Another exemplary TDD configuration with more uplink slots is shown in FIG. 7b. This TDD configuration could represent the TDD configuration used in the neighbouring cell by the neighbouring wireless device. In the exemplary embodiment the time units would be assigned to the various groups as follows:

[0046] Group A fixed: Slot {0, 1, 2, 3, 4, 5, 8, 9, 10, 11, 12, 13, 14, 15, 18, 19}

[0047] Group B varying: Slot {6, 7, 16, 17}

[0048] It is assumed that the special DL slots (S) have the same configuration of DL and UL symbols in each of the two example configurations. There will therefore not be any cross-link interference in the special slots in this exemplary embodiment and these slots can be included in Group A. Group B contains the slots that can be either DL or UL, depending on to which cell (and thereby to which TDD configuration) the wireless device belongs.

[0049] The slots assigned to Group A and Group B are then treated separately for link adaptation and/or scheduling. Different link adaptation methods are applied for the two Groups, step 602.

[0050] In some embodiments the link adaptation is separated into two outer loops for the different Groups. Block errors caused by cross-link interference due to different TDD configurations in neighbouring cells will cause the outer loop to increase margin and use more robust Modulation and Coding Scheme (MCS) for slots in Group B compared to slots in Group A. In one embodiment the signal-to-noise ratio (SNR) threshold for selection of a specific Modulation and Coding Scheme, MCS, is different for Group A and Group B.

[0051] In one exemplary embodiment the Downlink Control Information, DCI, for PUSCH scheduling of varying slots 6, 7, 16 and 17 are allocated into varying DL slots 6, 7, 16 and/or 17. DCI for PUSCH scheduling of fixed UL slots 4, 5, 14 and 15 are allocated into fixed DL slots 0-3, 8-12 and/or 18-19.

[0052] In one exemplary embodiment, the ACK/NACK response to PDSCH on varying slots 6, 7, 16 and 17 are allocated into varying UL slots 6, 7, 16 and/or 17. ACK/NACK response to PDSCH on fixed DL slots 0-3, 8-12 and/or 18-19 are allocated to fixed UL slots 4, 5, 14 and 15.

[0053] Exemplary embodiments are directed to transmitting all control signalling in fixed slots with no cross-link interference, thereby reducing the error-rate of the control signalling. However, in some embodiments the amount of control data to transmit may be too large to fit in the fixed slots. Therefore, the DCI and HARQ ACK/NACK are preferably allocated to slots in the same group as the actual data transmission.

[0054] In another embodiment the control signals (RLC, RRC and higher layer) are scheduled on slots in Group A to maintain connectivity also for wireless devices exposed to severe TDD interference such as CLI.

[0055] Different HARQ processes may be used for the different time-slot groups. Any retransmissions of data from one time-slot group will then be transmitted in a slot belonging to the same time-slot group. This may be advantageous since the number of bits to be transmitted in the time-frequency resources of one slot may differ significantly between the different groups depending on MCS selection offsets, different average SINR, etc. For a packet transmitted over fixed slots first (means a large packet can be transmitted since MCS is typically high) and then being retransmitted over varying slots, capable of carrying much less data, the amount of additional information received in the retransmission may not be enough for correct decoding of the packet.

[0056] In some embodiments, different HARQ processes are used for different time unit groups. Further, the HARQ processes associated with the different time unit groups may be associated with different link adaptation outer loops.

[0057] Different outer loop methods and characteristics, for example SINR offsets, can be used for the two slot groups. For Group B, filtering such as windowing can be applied to not compensate for single block errors to limit the impact of single TDD scheduling collision occurrences. If co-scheduling of two wireless devices close to each other is unlikely, this will improve the overall throughput and capacity.

[0058] In another embodiment, the set of TDD configurations may be limited to only a few allowed configurations. Group A may be selected to include only slots where all possible configurations have the same type of slots. The varying slots included in group B are all slots that are not the same type in each of the allowed configurations. FIG. 7c shows an example embodiment with three allowed TDD configurations. The Figure also shows how the slots are divided into Group A and Group B, where Group A includes the fixed slots and Group B includes the varying slots.

[0059] Thus, the assignment of a time unit to a time unit group is such that the time units are assigned to time unit groups depending on how much crosslink interference they are likely to be subjected to. Thus the time unit groups may in some embodiments be Group A and Group B as described above and in other embodiments the assignment of time units to the at least two time unit groups is such that time units that will, or that possibly will, experience cross-link interference from the neighbouring cell using another TDD configuration are assigned to one time unit group and the other time units in the TDD configuration are assigned to another time unit group.

[0060] FIG. 8 schematically illustrates, in terms of a number of functional units, the components of a network node 200 according to an embodiment. Processing circuitry 210 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 910 (as in FIG. 10), e.g. in the form of a storage medium 230 or memory. The processing circuitry 210 may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

[0061] Particularly, the processing circuitry 210 is configured to cause network node 200 to perform a set of operations, or steps, 601-602, as disclosed above. For example, the storage medium or memory 230 may store the set of operations, and the processing circuitry 210 may be configured to retrieve the set of operations from the storage medium 230 to cause network node 200 to perform the set of operations. The set of operations may be provided as a set of executable instructions.

[0062] Thus the processing circuitry 210 is thereby arranged to execute methods as herein disclosed. The storage medium 230 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory. Network node 200 may further comprise a communications interface 220 at least configured for communications with other nodes, device, functions, and notes of the communications network 100a. As such the communications interface 220 may comprise one or more transmitters and receivers, comprising analogue and digital components. Signals could be transmitted from, and received by, a network node 200 using the communications interface 220.

[0063] The processing circuitry 210 controls the general operation of network 200 e.g. by sending data and control signals to the communications interface 220 and the storage medium 230, by receiving data and reports from the communications interface 220, and by retrieving data and instructions from the storage medium 230. Other components, as well as the related functionality, of network node 200 are omitted in order not to obscure the concepts presented herein.

[0064] FIG. 9 schematically illustrates, in terms of a number of functional units, the components of a wireless device (UE) 300 according to an embodiment. Processing circuitry 310 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 910 (as in FIG. 10), e.g. in the form of a storage medium 330 or memory. The processing circuitry 310 may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

[0065] Particularly, the processing circuitry 310 is configured to cause UE 300 to perform a set of operations as disclosed above. For example, the storage medium or memory 330 may store the set of operations, and the processing circuitry 310 may be configured to retrieve the set of operations from the storage medium 330 to cause UE 300 to perform the set of operations. The set of operations may be provided as a set of executable instructions.

[0066] Thus the processing circuitry 310 is thereby arranged to execute methods as herein disclosed. The storage medium 330 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory. UE 300 may further comprise a communications interface 320 at least configured for communications with other nodes, device, functions, and notes of the communications network 100a. As such the communications interface 320 may comprise one or more transmitters and receivers, comprising analogue and digital components. Signals could be transmitted from, and received by, a UE 300 using the communications interface 320.

[0067] The processing circuitry 310 controls the general operation of UE 300 e.g. by sending data and control signals to the communications interface 320 and the storage medium 330, by receiving data and reports from the communications interface 320, and by retrieving data and instructions from the storage medium 330. Optionally the UE may include a display 340 but the embodiments herein are not limited thereto. Other components, as well as the related functionality, of UE 300 are omitted in order not to obscure the concepts presented herein.

[0068] FIG. 10 shows one example of a computer program product 910 comprising computer readable storage medium 930. On this computer readable storage medium 930, a computer program 920 can be stored, which computer program 920 can cause the processing circuitry 210 or 310 and thereto operatively coupled entities and devices, such as the communications interface 220 or 320 and the storage medium 230 or 330, to execute methods according to embodiments described herein. The computer program 920 and/or computer program product 910 may thus provide means for performing any steps as herein disclosed.

[0069] In the example of FIG. 8, the computer program product 910 is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc. The computer program product 910 could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory. Thus, while the computer program 920 is here schematically shown as a track on the depicted optical disk, the computer program 920 can be stored in any way which is suitable for the computer program product 910.

[0070] The inventive concept has mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the inventive concept, as defined by the appended patent claims.