WO2024030134A1 - Adjusting radio link quality monitoring based on potential cli such as for advanced duplexing cases - Google Patents

Adjusting radio link quality monitoring based on potential cli such as for advanced duplexing cases Download PDF

Info

Publication number
WO2024030134A1
WO2024030134A1 PCT/US2022/039519 US2022039519W WO2024030134A1 WO 2024030134 A1 WO2024030134 A1 WO 2024030134A1 US 2022039519 W US2022039519 W US 2022039519W WO 2024030134 A1 WO2024030134 A1 WO 2024030134A1
Authority
WO
WIPO (PCT)
Prior art keywords
resources
radio link
user equipment
monitoring
network node
Prior art date
Application number
PCT/US2022/039519
Other languages
French (fr)
Inventor
Klaus Ingemann Pedersen
Roberto Maldonado
Claudio Rosa
Guillermo POCOVI
Original Assignee
Nokia Technologies Oy
Nokia Of America Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy, Nokia Of America Corporation filed Critical Nokia Technologies Oy
Priority to PCT/US2022/039519 priority Critical patent/WO2024030134A1/en
Publication of WO2024030134A1 publication Critical patent/WO2024030134A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0062—Avoidance of ingress interference, e.g. ham radio channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path

Definitions

  • Exemplary embodiments herein relate generally to wireless communications and, more specifically, relate to communications where a UE is able to receive signals from one network node (or cells) while other UEs transmit to other network node(s) (or their cell(s)).
  • 3GPP third generation partnership project
  • Rel-18 release- 18 study item on flexible duplexing.
  • One of the objectives is to enable more dynamic TDD (time-division duplexing) operation, where neighbor cells may use different TDD radio frame configurations. For this situation, at a given time, one cell may have downlink (DL) transmission, while another cell may have uplink (UL) transmissions.
  • DL downlink
  • UL uplink
  • the main advantage of dynamic TDD is that it allows each cell (or a group of cells) to select its TDD UL/DL pattern in accordance with its own traffic load conditions, e.g., a cell serving one single UE with UL-heavy traffic may temporarily use a UL-heavy TDD pattern to increase UL capacity and minimize the latency, while switching later to a DL-heavy TDD pattern when the traffic conditions change.
  • cross-link interference affects cause the following:
  • a method includes, for a network node serving a user equipment in a wireless system, identifying by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment.
  • the method includes sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
  • An additional exemplary embodiment includes a computer program, comprising code for performing the method of the previous paragraph, when the computer program is run on a processor.
  • the computer program according to this paragraph wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer.
  • Another example is the computer program according to this paragraph, wherein the program is directly loadable into an internal memory of the computer.
  • An exemplary apparatus includes one or more processors and one or more memories including computer program code.
  • the one or more memories and the computer program code are configured to, with the one or more processors, cause the apparatus at least to: for a network node serving a user equipment in a wireless system, identify by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and send, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
  • An exemplary computer program product includes a computer-readable storage medium bearing computer program code embodied therein for use with a computer.
  • the computer program code includes: code, for a network node serving a user equipment in a wireless system, for identifying by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and code for sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
  • an apparatus comprises means for performing: for a network node serving a user equipment in a wireless system, identifying by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
  • a method includes, for a user equipment being served by a network node in a wireless system, receiving information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment.
  • the method includes, for the set of resources, not performing by the user equipment radio link quality monitoring in those resources.
  • An additional exemplary embodiment includes a computer program, comprising code for performing the method of the previous paragraph, when the computer program is run on a processor.
  • the computer program according to this paragraph wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer.
  • Another example is the computer program according to this paragraph, wherein the program is directly loadable into an internal memory of the computer.
  • An exemplary apparatus includes one or more processors and one or more memories including computer program code.
  • the one or more memories and the computer program code are configured to, with the one or more processors, cause the apparatus at least to: for a user equipment being served by a network node in a wireless system, receive information from the network node indicating a set of resources is potentially subject to cross-link- interference affecting the user equipment; and for the set of resources, not perform by the user equipment radio link quality monitoring in those resources.
  • An exemplary computer program product includes a computer-readable storage medium bearing computer program code embodied therein for use with a computer.
  • the computer program code includes: code, for a user equipment being served by a network node in a wireless system, for receiving information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment; and code, for the set of resources, for not performing by the user equipment radio link quality monitoring in those resources.
  • an apparatus comprises means for performing: for a user equipment being served by a network node in a wireless system, receiving information from the network node indicating a set of resources is potentially subject to cross- link-interference affecting the user equipment; and for the set of resources, not performing by the user equipment radio link quality monitoring in those resources.
  • FIG. 1 is a block diagram of one possible and non-limiting exemplary system in which the exemplary embodiments may be practiced;
  • FIG. 2 illustrates the variables used for RLM that are signaled by the network with the IE UE-TimersAndConstants
  • FIG. 3 is a logic flow diagram for enhanced RLM/BFD mechanism for advanced duplexing cases, and illustrates the operation of an exemplary method, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with an exemplary embodiment;
  • FIG. 4 illustrates indication of CLI slots for accurate RLF procedure in dynamic TDD deployments, in accordance with an exemplary embodiment
  • FIG. 4A illustrates timer T310 evolution over 12 slots using a CLI slots vector similar to the one illustrated in FIG. 4.
  • the exemplary embodiments herein describe techniques for enhanced RLM/BFD Mechanism for Advanced Duplexing Cases. Additional description of these techniques is presented after a system into which the exemplary embodiments may be used is described.
  • FIG. 1 shows a block diagram of one possible and nonlimiting exemplary system in which the exemplary embodiments may be practiced.
  • a user equipment (UE) 110 radio access network (RAN) nodes 170 and 170-1, and network element(s) 190 are illustrated.
  • RAN radio access network
  • a user equipment (UE) 110 is in wireless communication with a wireless network 100.
  • a UE is a wireless, typically mobile device that can access a wireless network.
  • the UE 110 includes circuitry comprising one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127.
  • Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133.
  • the one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like.
  • the one or more transceivers 130 are connected to one or more antennas 128.
  • the one or more memories 125 include computer program code 123.
  • the UE 110 includes a control module 140, comprising one of or both parts 140-1 and/or 140-2, which may be implemented in a number of ways.
  • the control module 140 may be implemented in hardware as control module 140-1, such as being implemented as part of the one or more processors 120.
  • the control module 140-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array.
  • the control module 140 may be implemented as control module 140- 2, which is implemented as computer program code 123 and is executed by the one or more processors 120.
  • the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein.
  • the UE 110 communicates with RAN node 170 via a wireless link 111 and with RAN node 170-1 via wireless link 111-1.
  • the RAN nodes 170, 170-1 are network nodes such as base stations that provide access by wireless devices such as the UE 110 to the wireless network 100.
  • the RAN nodes 170, 170-1 are referred to herein as gNB 170, but this is only one example. Additionally, if the network (NW or N/W) is referred to as performing an action, that action is typically performed by the gNB 170, although other options are possible.
  • the RAN nodes 170, 170-1 are considered to be similar, and thus the circuitry for RAN node 170 will only be described.
  • the RAN node 170 may be, for instance, a base station for 5G, also called New Radio (NR).
  • the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or an ng-eNB.
  • a gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (e.g., the network element(s) 190).
  • the ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC.
  • the NG-RAN may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs), of which DU 195 is shown.
  • the DU may include or be coupled to and control a radio unit (RU).
  • the gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs.
  • the gNB-CU terminates the Fl interface connected with the gNB-DU.
  • the Fl interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195.
  • the gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU.
  • One gNB-DU supports one or multiple cells. One cell is supported by one gNB-DU.
  • the gNB-DU terminates the Fl interface 198 connected with the gNB-CU.
  • the DU 195 is considered to include the transceiver 160, e.g., as part of an RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under control of and connected to the DU 195.
  • the RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution), or any other suitable base station.
  • eNB evolved NodeB
  • the RAN node 170 includes circuitry comprising one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157.
  • Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163.
  • the one or more transceivers 160 are connected to one or more antennas 158.
  • the one or more memories 155 include computer program code 153.
  • the CU 196 may include the processor(s) 152, memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory/memories and processor(s), and/or other hardware, but these are not shown.
  • the RAN node 170 includes a control module 150, comprising one of or both parts 150-1 and/or 150-2, which may be implemented in a number of ways.
  • the control module 150 may be implemented in hardware as control module 150-1, such as being implemented as part of the one or more processors 152.
  • the control module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array.
  • the control module 150 may be implemented as control module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152.
  • the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein.
  • the functionality of the control module 150 may be distributed, such as being distributed between the DU 195 and the CU 196, or be implemented solely in the DU 195.
  • the one or more network interfaces 161 communicate over a network such as via the links 176 and 131.
  • Two or more RAN nodes 170 communicate using, e.g., link 176.
  • the link 176 may be wired or wireless or both and may implement, e.g., an Xn interface for 5G, an X2 interface for LTE, or other suitable interface for other standards.
  • the one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like.
  • the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH/DU, and the one or more buses 157 could be implemented in part as, e.g., fiber optic cable or other suitable network connection to connect the other elements (e.g., a central unit (CU), gNB-CU) of the RAN node 170 to the RRH/DU 195.
  • Reference 198 also indicates those suitable network link(s).
  • each cell can correspond to a single carrier and a base station may use multiple carriers. So, if there are three 120 degree cells per carrier and two carriers, then the base station has a total of 6 cells.
  • the wireless network 100 may include a network element or elements 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a data network 191, such as a telephone network and/or a data communications network (e.g., the Internet).
  • a data network 191 such as a telephone network and/or a data communications network (e.g., the Internet).
  • core network functionality for 5G may include access and mobility management function(s) (AMF(s)) and/or user plane functions (UPF(s)) and/or session management function(s) (SMF(s)).
  • AMF(s) access and mobility management function(s)
  • UPF(s) user plane functions
  • SMF(s) session management function
  • Such core network functionality for LTE may include MME (Mobility Management Entity) functionality and/or SGW (Serving Gateway) functionality. These are merely exemplary functions that may be supported by the network element(s) 190, and note that both 5G and LTE functions might be supported.
  • the RAN node 170 is coupled via a link 131 to a network element 190.
  • the link 131 may be implemented as, e.g., an NG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards.
  • the network element 190 includes circuitry comprising one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s)) 180, interconnected through one or more buses 185.
  • the one or more memories 171 include computer program code 173.
  • the one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the network element 190 to perform one or more operations.
  • the wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network.
  • Network virtualization involves platform virtualization, often combined with resource virtualization.
  • Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.
  • the computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, firmware, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the computer readable memories 125, 155, and 171 may be means for performing storage functions.
  • the processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples.
  • the processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN node 170, and other functions as described herein.
  • the various embodiments of the user equipment 110 can include, but are not limited to, cellular telephones (such as smart phones, mobile phones, cellular phones, voice over Internet Protocol (IP) (VoIP) phones, and/or wireless local loop phones), tablets, portable computers, vehicles or vehicle-mounted devices for, e.g., wireless V2X (vehicle-to- everything) communication, image capture devices such as digital cameras, gaming devices, music storage and playback appliances, Internet appliances (including Internet of Things, loT, devices), loT devices with sensors and/or actuators for, e.g., automation applications, as well as portable units or terminals that incorporate combinations of such functions, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), Universal Serial Bus (USB) dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.
  • cellular telephones
  • the UE 110 could be any end device that may be capable of wireless communication.
  • the UE may also be referred to as a communication device, terminal device (MT), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT).
  • MT terminal device
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • one cell may have downlink (DL) transmission, while another cell may have uplink (UL) transmissions.
  • This can cause severe cross-link-interference (CLI) between cells on slots where neighbor cells use opposite link directions.
  • CLI cross-link-interference
  • RLM radio link monitoring
  • RLF radio link failure
  • the UE performs Radio Link Monitoring (RLM) in the active BWP based on reference signals (e.g., SSB/CSLRS) and signal quality thresholds configured by the network.
  • RLM Radio Link Monitoring
  • SSB-based RLM is based on the SSB associated to the initial DL BWP and can only be configured for the initial DL BWP and for DL BWPs containing the SSB associated to the initial DL BWP.
  • RLM can only be performed based on CSLRS.
  • the UE also performs Beam Failure Detection (BFD) to monitor the quality of the connected beam.
  • BFD Beam Failure Detection
  • BFD is also based on reference signals (SSB & CSI-RS) and signal quality threshold configured by the network.
  • SSB & CSI-RS reference signals
  • the detection of a beam failure triggers a beam failure recovery in which the UE switches to a different beam after a successful random-access procedure.
  • NR Rel-16 include simple coordination between gNBs (via the Xn and Fl interfaces) to make them aware of CLI-slots.
  • Conducting RLM/BFD during CLI-slots is therefore not desirable as it does not really reflect the experienced end-user quality. Conducting RLM/BFD in CLI-slots can therefore cause undesirable problems, which can be characterized as false RLF/BFD events, and hence should be avoided. This is one exemplary problem addressed herein.
  • the UE performs Radio Link Monitoring (RLM) in the active BWP based on reference signals (SSB/CSLRS) and signal quality thresholds configured by the network.
  • RLM Radio Link Monitoring
  • SSB-based RLM is based on the SSB associated to the initial DL BWP and can only be configured for the initial DL BWP and for DL BWPs containing the SSB associated to the initial DL BWP.
  • RLM can only be performed based on CSLRS.
  • the UE continues the detection of radio link failure at the source cell until the successful completion of the random access procedure to the target cell.
  • the UE declares Radio Link Failure (RLF) when one of the following criteria are met: [0051] - Expiry of a radio problem timer started after indication of radio problems from the physical layer (if radio problems are recovered before the timer is expired, the UE stops the timer); or
  • UE configuration of RLM happens via RRC signaling as defined in 3 GPP TS 38.331. This includes options for relaxed measurement criterion for low mobility users as defined in clause 5.7.13.
  • the UE requirements for RLM are defined in 3GPP TS 38.133, clause 8.1 as follows (the quoted part is between opening and closing quotation marks):
  • the UE shall monitor the downlink radio link quality based on the reference signal configured as RLM-RS resource(s) in order to detect the downlink radio link quality of the PCell, PSCell and deactivated PSCell as specified in TS 38.213 [3].
  • the configured RLM-RS resources can be all SSBs, or all CSLRSs, or a mix of SSBs and CSLRSs.
  • UE is not required to perform RLM outside the active DL BWP.
  • the UE On each RLM-RS resource, the UE shall estimate the downlink radio link quality and compare it to the thresholds Qout and Qin for the purpose of monitoring downlink radio link quality of the cell.
  • a CORESET that the UE uses for monitoring PDCCH includes two TCI states and the UE is provided sfnSchemePdcch set to 'sfnSchemeA' or 'sfnSchemeB', the UE shall estimate the downlink radio link quality and compare it to the single thresholds Qout and Qin for the purpose of monitoring downlink radio link quality of the cell(s). How to compute the single hypothetical PDCCH SNR based on two active TCI states is up to UE implementation.
  • the threshold Qout is defined as the level at which the downlink radio link cannot be reliably received and shall correspond to the out-of-sync block error rate (BLERout) as defined in Table 8.1.1-1.
  • BLERout block error rate
  • Qout_SSB is derived based on the hypothetical PDCCH transmission parameters listed in Table 8.1.2.1-1.
  • Qout_CSI-RS is derived based on the hypothetical PDCCH transmission parameters listed in Table 8.1.3.1-1.
  • the threshold Qin is defined as the level at which the downlink radio link quality can be received with significantly higher reliability than at Qout and shall correspond to the in-sync block error rate (BLERin) as defined in Table 8.1.1-1.
  • BLERin block error rate
  • Qin_SSB is derived based on the hypothetical PDCCH transmission parameters listed in Table 8.1.2.1-2.
  • Qin_CSI-RS is derived based on the hypothetical PDCCH transmission parameters listed in Table 8.1.3.1-2.
  • BEERout The out-of-sync block error rate (BEERout) and in-sync block error rate (BLERin) are determined from the network configuration via parameter rlmlnSyncOutOfSyncThreshold signaled by higher layers.
  • UE determines out-of-sync and in-sync block error rates from Configuration #0 in Table 8.1.1-1 by default. All requirements in clause 8.1 are applicable for BLER Configuration #0 in Table 8.1.1-1.”
  • the downlink radio link quality of the primary cell is monitored by a UE for the purpose of indicating out-of-sync/in-sync status to higher layers.
  • the UE is not required to monitor the downlink radio link quality in DL BWPs other than the active DL BWP, as described in clause 12, on the primary cell. If the active DL BWP is the initial DL BWP and for SS/PBCH block and CORESET multiplexing pattern 2 or 3, as described in clause 13, the UE is expected to perform RLM using the associated SS/PBCH block when the associated SS/PBCH block index is provided by RadioLinkMonitoringRS.”
  • the radio problem timer is started as indicated in 3GPP TS 38.331 (the quoted part is between opening and closing quotation marks):
  • the UE shall:
  • the variables used for RLM are signaled by the network with the IE UE- TimersAndConstants specified in TS 38.331 (for RLF purposes T310, N310, N311 are used) as illustrated in FIG. 2.
  • NR Rel-16 also includes options for gNBs to exchange their intended UL-DL configuration (i.e., their TDD radio frame configuration) over the Xn and Fl interfaces.
  • gNBs to exchange their intended UL-DL configuration (i.e., their TDD radio frame configuration) over the Xn and Fl interfaces.
  • IEEE publication ‘Advancements in 5G New Radio TDD Cross Link Interference Mitigation’, IEEE Wireless Communications ( Volume: 28, Issue: 4, August 2021) (DOI: 10.1109/MWC.001.2000376).
  • This IEEE publication describes that new TDD coordination mechanisms have been defined between gNBs, and between CU and DUs, to foster effective and simple solutions.
  • IE information element
  • the aforementioned IE contains the SCS, cyclic prefix and TDD DL-UL slot configuration of an NR cell that a neighbor cell needs to take into account for cross-link interference mitigation when operating its own cells.
  • the actual TDD radio frame configuration is expressed as a list of slot formats.
  • Signaling of the Intended TDD DL-UL Configuration is supported between two gNBs on the Xn interface, using the Xn application protocol (XnAP), as well as between CU and DU. Additionally, signaling for this may be performed as in 3GPP TS 38.423 V17.1.0 (2022-06), section 9.2.2.40, which describes an IE for “Intended TDD DL-UL Configuration NR”.
  • the network will know in which slots a UE may be subject to CLI for downlink reception, and in which slots transmission from a UE may be subject to strong CLI for reception at its source cell.
  • the NW will exploit such knowledge to avoid uplink and downlink scheduling in such CLI slots, which anyways will be subject to poor reception quality.
  • BFD beam failure detection
  • the gNB configures the UE with beam failure detection reference signals (SSB or CSLRS) and the UE declares beam failure when the number of beam failure instance indications from the physical layer reaches a configured threshold before a configured timer expires.”
  • SSB beam failure detection reference signals
  • CSLRS beam failure detection reference signals
  • the BFD and BFR variables are configured via RRC with the parameters indicated in BeamFailureRecoveryConfig, BeamFailureRecoverSCellConfig and Radio LinkMoniloringConfig.
  • the UE behavior for BFD is defined in 3GPP TS 38.321 as shown below:
  • the network can configure UEs to only perform REM on dedicated time-domain resources, such that the UE does not perform such actions during so-called CLI slots, where the network may not intend to schedule the UE.
  • This may involve configuring the UE with a timedomain mask or other pattern (such as a vector) that informs in which symbols or slots the UE shall not perform RLM. That includes not performing DL RLM measurement on RLM-RS resources during such symbols or slots.
  • the timer that is to be started after indication of radio problems from the physical layer is not advanced during the symbols/slots indicated by the time-domain mask (i.e., the timer is stopped during CLI symbols/slots), such that expiry of this timer excludes CLI-slots for triggering potential RLF.
  • Signaling of the time-domain mask may be realized with RRC signaling, MAC signaling (e.g., MAC CE), or in the event of fast adapting dynamic TDD by means for physical layer signaling.
  • the time-domain mask indicating resources (e.g., slots/symbols) with potential high CLI and the (de-)activation of the time-domain mask for RLM purposes may be separately signaled.
  • the time-domain mask may be configured using higher layer signaling (RRC) while the activation of the time-domain mask for RLM purposes may be signaled using either MAC or PHY signaling.
  • the UE only applies the time-domain mask if explicitly signaled by the gNB, e.g., the use of the time-domain mask is activated after a CLI measurement report from the UE indicating high CLI level.
  • the UE may also autonomously activate the time-domain mask for RLM purposes if e.g., the UE detects that the radio link quality in CLI slots/symbols is significantly worse than radio link quality in non-CLI slots/symbols or if the measured CLI exceeds a certain threshold (e.g., using existing Rel-16 UE CLI measurements).
  • the UE may also perform separate RLM procedures, possibly using different RLM configurations, on CLI and non-CLI slots, as indicated by the network-configured time-domain mask.
  • the UE may only trigger RLF based on RLM on non-CLI slots, while upon detection of RLF on CLI slots, the UE may only send a specific report to the network but continue normal operation on the serving cell. In this case, the UE may suspend RLM on CLI slots after sending the report to the network.
  • the gNB 170 could dynamically indicate to the UE 110 that RLM-RS measurements on the n previous slots should be considered to be invalid, given the presence of CLI. The UE could then adjust the RLM counters accordingly. For instance, the UE could subtract n from a value in the N310 counter.
  • An exemplary advantage and technical effect of the proposed techniques is that they allow the network to control UEs so the UEs do not perform RLM, and trigger false RLF events, as a result of radio performance conditions in so-called CLI slots where the network anyways has no intention of scheduling the UE. Thereby, false RLF triggering is avoided for dynamic TDD cases, and hence unnecessary actions for the UE to perform RRC re-establishment events, or in worst case experiencing dropped calls.
  • the present idea is primarily targeted to dynamic TDD, it may also be applicable to subband non-overlapping full duplex (SBFD) operation, which is also in the objective of the ongoing Rel-18 study item on Evolution of Duplex Operation.
  • SBFD subband non-overlapping full duplex
  • the gNB may make use of the proposed ideas to configure a UE to only perform RLM on DL-only slots/symbols and not on SBFD slots/symbols due to potentially high inter-subband UE-2-UE CLI.
  • FIG. 3 is a logic flow diagram for enhanced RLM/BFD mechanism for advanced duplexing cases.
  • FIG. 3 also illustrates the operation of an exemplary method, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with an exemplary embodiment.
  • the steps are performed by the UE 110, e.g., under control of the control module 140 and by the gNB 170, e.g., under control of the control module 150.
  • the network (NW) is the gNB 170, although other options are possible.
  • the NW identifies that a set of resources (which could be slots, symbols, or other resources, at least one resource) is potentially subject to high CLI.
  • This set of resources is deemed to be resources that are potentially subjected to cross-link-interference high enough to impair reception by the user equipment.
  • This determination of potentially high enough interference is up to gNB implementation.
  • the “potentially” occurs because, even if CLI has been determined to be high in a slot or resource, this does not mean the UE’s reception will actually be impaired in any particular slot or resource. For instance, the UE could move to be near the center of the cell for its serving gNB, and away from any interfering UEs transmitting to a different cell. That is, while the gNB can assume a particular slot will have high CLI, there is no guarantee that will be true for every UE being served by that gNB.
  • a gNB may identify CLI resources as resources where the gNB uses a transmission direction that is different from that of a neighboring gNB (e.g., or a cell formed by the gNB).
  • the gNB in step Lb., may also utilize UE CLI measurements to identify if a UE is subject to noticeable CLI levels for DL reception.
  • the gNB may not schedule certain UEs during such CLI-resource(s) (e.g., slots/symbols). For instance, the gNB might decide not to schedule reception for these UEs during CLI slots because the interference level is too high to ensure a reliable decoding of the data.
  • the gNB may not schedule those UEs during the CLI slots. On the other hand, cell-centered UEs could still be scheduled. The gNB could use the UE CLI measurements to identify the UEs with high CLI.
  • the gNB 170 could dynamically indicate to the UE 110 that RLM-RS measurements on the n previous slots should be considered to be invalid, given the presence of CLI. See step l.d. [00102] 2.
  • the NW e.g., gNB
  • Signaling and activation of such time-domain mask may be realized (see step 2.a.i) with RRC signaling, MAC-signaling (e.g., MAC CE), physical layer signaling, or a combination of the above (e.g., configuration via RRC and activation via MAC CE).
  • RRC signaling e.g., RRC signaling
  • MAC-signaling e.g., MAC CE
  • physical layer signaling e.g., configuration via RRC and activation via MAC CE
  • the UE complies with the received instructions in step 2 by, e.g., not performing (step 3. a.) DL RLM measurement on RLM-RS resources during such CLI resources (e.g., slots/symbols). Furthermore, in step 3.b., the radio problem timer that is started after indication of radio problems from the physical layer is not advanced during times of CLI resources (i.e., the timer is stopped), such that expiry of this timer excludes the time spent in CLI-resources (e.g., slotsO for triggering potential RLF).
  • CLI resources e.g., slots/symbols
  • the UE should only monitor the downlink radio link quality based on the reference signal configured as RLM-RS resource(s) in non-CLI resources (e.g., slots or symbols) in order to detect the downlink radio link quality and compare the quality to the thresholds Qout and Qin for the purpose of monitoring downlink radio link quality of the cell.
  • RLM-RS resource(s) in non-CLI resources e.g., slots or symbols
  • T310 (also known as the radio problem timer in the stage-2 specs - 3GPP TS 38.300) upon detecting physical layer RLM problems upon receiving N310 consecutive out-of-sync indications from lower layers, where N310 is the maximum number of consecutive “out-of-sync” indications for the PCell received from lower layers.
  • Timer T310 is stopped during all CLI slots or symbols.
  • RLF is declared when T310 expires.
  • Random-access procedure failure for RLM purposes and RLF triggering is only monitored during resources that are not CLI-resources. That is, random-access attempts sent during CLI resources (e.g., slots) are not counted for RLM/RLF purposes.
  • the UE requirements in 3GPP TS 38.133, clause 8.1, may be updated accordingly so RLM and RLF triggering is omitted during CLI resources (e.g., slots or symbols).
  • CLI resources e.g., slots or symbols.
  • the gNB 170 has dynamically indicated to the UE 110 that RLM-RS measurements on the n previous slots should be considered to be invalid, given the presence of CLI.
  • the UE then adjusts (in step 3.g.) the RLM counters accordingly. For instance, the UE could subtract n from a value in the N310 counter (e.g., or other appropriate counter).
  • Non-CLI and “CLI slots” or symbols or resources, but may only refer to, e.g., first and second subset of slots/symbols, where, e.g., RLM is only to be performed during the first subset of slots/symbols.
  • RLM is only to be performed during the first subset of slots/symbols.
  • FIG. 4 illustrates indication of CLI slots for RLF procedure in dynamic TDD deployments, in accordance with an exemplary embodiment.
  • TDD radio frame configurations 400-1 and 400-2 for two neighboring cells are illustrated.
  • the TDD radio frame configurations 400-1 and 400-2 have 10 slots, slot-0410-0 through slot-9 410-9, the DL and UL slots are shown, and the dashed ovals are used to illustrate a slot where one cell is performing DL while the other is performing UL.
  • the “Xs” in the vector indicate CLI slots, and no indication indicate non-CLI slots.
  • cell #1 420-1 e.g., formed by gNB 170
  • cell #2 420-2 e.g., formed by gNB 170-1. It is noted that, for cells to have different TDD patterns, the cells should be served/formed by different gNBs.
  • CLI slots For slots where the two cells 420-1 and 420-2 have identical transmission direction, there is no CLI between the cells. For slots where they have opposite transmission directions, there is CLI, i.e., denoted as CLI slots via the Xs.
  • the vector 420 e.g., a time-domain mask
  • CLI slots is signaled to the UE as per step 2 in FIG. 3 to inform the UE not to perform RLM and RLF triggering during these slots.
  • the UE takes the defined actions as per 3.a.-3.f.. For instance, as shown in reference 440, the RLM and RLF triggering is not happening in these slots and the T310 timer (if otherwise started) is temporarily stopped in these CLI slots.
  • FIG. 4A this figure illustrates timer T310 evolution over 12 slots using a CLI slots vector similar to the one illustrated in FIG. 4.
  • the CLI slots vector 430-1 has 12 entries, and similar to the CLI slots vector 430 in FIG. 4, slots 2, 4, 7, and 9 are denoted.
  • the T310 timer starts at T310 initial value 450 and ends at value 455 after all 12 slots 410.
  • Each time period 460-1, 460-2, 460-3, and 460-4 corresponds to slots 2, 4, 7, and 9, respectively, having a corresponding entry in the vector 430 indicating the T310 timer is to be stopped in those slots.
  • the UE is configured via RRC with a time-domain mask (e.g., the vector 430) identifying slots/symbols with potentially high CLI.
  • the vector 430 can be anything that indicates slots (or symbols), and a vector or mask are possible implementations of this.
  • the following slots are indicated in vector 430: slot-2 410-2; slot-4 410-4; slot-7 410-7; and slot- 9 410-9.
  • the UE still performs RLM in all slots/symbols according to legacy behavior until the UE receives an explicit activation message (MAC CE) from the gNB.
  • MAC CE explicit activation message
  • the UE After the activation message is received, the UE only performs RLM during one subset of the slots/symbols indicated by the time-domain mask (i.e., non-CLI slots/symbols).
  • the transmission of the activation message from the gNB to the UE may be triggered by the reception of a CLI measurement report indicating high CLI at the UE.
  • the UE may autonomously activate the use of the network-configured time-domain mask for RLM purposes if the UE detects that the radio link quality in one subset of resources (e.g., slots/symbols such as CLI slots/symbols) is significantly worse than radio link quality in the other subset of resources (e.g., slots/symbols such as non-CLI slots/symbols).
  • the radio link quality in one subset of resources e.g., slots/symbols such as CLI slots/symbols
  • slots/symbols such as non-CLI slots/symbols
  • UE-specific CLI measurements such as CLLRSSI and/or CLI SRS-RSRP could also be used as trigger for the time-domain mask activation.
  • the UE may be configured to perform separate RLM procedures using different RLM configurations in different subsets of the time-domain resources, i.e., in CLI and non-CLI resources (e.g., slots/symbols).
  • CLI and non-CLI resources e.g., slots/symbols.
  • the UE may send a report to the network but continue normal operation on the serving cell. In this case, the UE may suspend performing RLM on CLI slots (e.g., until further notification or until a timer expires).
  • the UE Upon detection of RLF on non-CLI slots/symbols, the UE triggers RLF recovery according to a legacy procedure. It should be noted that the CLI and non-CLI resources do not overlap.
  • Example 1 A method, comprising:
  • Example 2 The method according to example 1, wherein the identifying comprises determining that the set of resources is potentially subject to cross -link-interference high enough to impair reception by the user equipment.
  • Example 3 The method according one of examples 1 to 2, wherein the identifying determines the set of resources as resources with cross-link-interference where the network node uses a transmission direction that is different from that of a neighboring network node, and wherein the sending comprises sending information identifying the set of resources where the network node uses a transmission direction that is different from that of a neighboring network node.
  • Example 4 The method according one of examples 1 to 2, wherein the identifying utilizes user equipment cross-link interference measurements to determine if a user equipment is subject to cross-link interference levels above a threshold for downlink reception, and wherein the sending comprises sending information identifying the cross-link interference resources where the user equipment cross-link interference measurements indicate cross-link interference levels above the threshold for downlink reception.
  • Example 5 The method according one of examples 1 to 4, further comprising the network node not scheduling selected user equipment for reception during the set of recourses.
  • Example 6 The method according to any one of examples 1 to 5, wherein the set of resources comprise either slots or symbols.
  • Example 7 The method according to any one of examples 1 to 6, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring.
  • Example 8 The method according to any one of examples 1 to 6, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms.
  • Example 9 A method, comprising:
  • Example 10 The method according to example 9, further comprising not advancing by the user equipment a timer that is started after indication of radio problems during times of the set of resources.
  • Example 11 The method according to one of examples 9 or 10, further comprising monitoring by the user equipment downlink radio link quality based on a reference signal configured by the network node as one or more radio link monitoring-reference signal resource(s) in the set of resources in order to detect the downlink radio link quality and compare the measured downlink radio link quality with one or more thresholds to determine downlink radio link quality.
  • Example 12 The method according to one of examples 9 to 11, further comprising starting by the user equipment a timer, to be started after indication of radio problems, in response to detecting physical layer radio link monitoring problems, but stopping the timer for periods of the set of resources.
  • Example 13 The method according to one of examples 9 to 12, further comprising not counting by the user equipment random access attempts sent during the set of resources for radio link monitoring or radio link failure or beam failure detection purposes.
  • Example 14 The method according to one of examples 9 to 12, further comprising omitting by the user equipment radio link monitoring or radio link failure or beam failure detection triggering during the set of resources.
  • Example 15 The method according to any one of examples 9 to 14, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring.
  • Example 16 The method according to any one of examples 9 to 14, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms.
  • Example 17 The method according to any one of examples 9 to 16, further comprising the user equipment receiving configuration from the network node to only perform radio link quality monitoring on downlink-only resources and wherein the set of resources are subband non-overlapping full-duplex resources.
  • Example 18 The method according to any one of examples 9 to 16, wherein: [00141] the set of resources is a first set of time-domain resources;
  • the information comprises a time-domain mask indicating the first set of timedomain resources and a second set of time-domain resources where radio link quality monitoring is to be performed;
  • the method comprises:
  • Example 19 The method according to any one of examples 9 to 16, wherein: [00148] the set of resources are a first set of time-domain resources;
  • the information comprises a time-domain mask indicating the first set of timedomain resources and a second set of time-domain resources where radio link quality monitoring is to be performed;
  • the method comprises autonomously activating by the user equipment use of the time-domain mask for radio link monitoring purposes in response to the user equipment detecting that radio link quality in one of the first or second set of resources is significantly worse than radio link quality in another of the first or second set of resources.
  • Example 20 The method according to any one of examples 9 to 19, further comprising receiving an indication, by the user equipment from the network node, indicating n previous radio link quality monitoring measurements, n 1, are to be considered to be invalid, and wherein the method further comprises adjusting by the user equipment a counter for radio link monitoring by subtracting n from the counter.
  • Example 21 A computer program, comprising code for performing the methods of any of examples 1 to 20, when the computer program is run on a computer.
  • Example 22 The computer program according to example 21, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with the computer.
  • Example 23 The computer program according to example 21, wherein the computer program is directly loadable into an internal memory of the computer.
  • Example 24 An apparatus, comprising means for performing:
  • Example 25 The apparatus according to example 24, wherein the identifying comprises determining that the set of resources is potentially subject to cross -link-interference high enough to impair reception by the user equipment.
  • Example 26 The apparatus according one of examples 24 to 25, wherein the identifying determines the set of resources as resources with cross-link-interference where the network node uses a transmission direction that is different from that of a neighboring network node, and wherein the sending comprises sending information identifying the set of resources where the network node uses a transmission direction that is different from that of a neighboring network node.
  • Example 27 The apparatus according one of examples 24 to 25, wherein the identifying utilizes user equipment cross-link interference measurements to determine if a user equipment is subject to cross-link interference levels above a threshold for downlink reception, and wherein the sending comprises sending information identifying the cross-link interference resources where the user equipment cross-link interference measurements indicate cross-link interference levels above the threshold for downlink reception.
  • Example 28 The apparatus according one of examples 24 to 27, wherein the means are further configured to perform not scheduling by the network node selected user equipment for reception during the set of recourses.
  • Example 29 The apparatus according to any one of examples 24 to 28, wherein the set of resources comprise either slots or symbols.
  • Example 30 The apparatus according to any one of examples 24 to 29, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring.
  • Example 31 The apparatus according to any one of examples 24 to 29, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms.
  • Example 32 An apparatus, comprising means for performing:
  • Example 33 The apparatus according to example 32, wherein the means are further configured to perform not advancing by the user equipment a timer that is started after indication of radio problems during times of the set of resources.
  • Example 34 The apparatus according to one of examples 32 or 33, wherein the means are further configured to perform monitoring by the user equipment downlink radio link quality based on a reference signal configured by the network node as one or more radio link monitoring-reference signal resource(s) in the set of resources in order to detect the downlink radio link quality and compare the measured downlink radio link quality with one or more thresholds to determine downlink radio link quality.
  • Example 35 The apparatus according to one of examples 32 to 34, wherein the means are further configured to perform starting by the user equipment a timer, to be started after indication of radio problems, in response to detecting physical layer radio link monitoring problems, but stopping the timer for periods of the set of resources.
  • Example 36 The apparatus according to one of examples 32 to 35, wherein the means are further configured to perform not counting by the user equipment random access attempts sent during the set of resources for radio link monitoring or radio link failure or beam failure detection purposes.
  • Example 37 The apparatus according to one of examples 32 to 35, wherein the means are further configured to perform omitting by the user equipment radio link monitoring or radio link failure or beam failure detection triggering during the set of resources.
  • Example 38 The apparatus according to any one of examples 32 to 37, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring.
  • Example 39 The apparatus according to any one of examples 32 to 37, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms.
  • Example 40 The apparatus according to any one of examples 32 to 39, wherein the means are further configured to perform the user equipment receiving configuration from the network node to only perform radio link quality monitoring on downlink-only resources and wherein the set of resources are subband non-overlapping full-duplex resources.
  • Example 41 The apparatus according to any one of examples 32 to 39, wherein:
  • the set of resources is a first set of time-domain resources
  • the information comprises a time-domain mask indicating the first set of timedomain resources and a second set of time-domain resources where radio link quality monitoring is to be performed;
  • the means are further configured to perform:
  • Example 42 The apparatus according to any one of examples 32 to 39, wherein:
  • the set of resources are a first set of time-domain resources
  • the information comprises a time-domain mask indicating the first set of timedomain resources and a second set of time-domain resources where radio link quality monitoring is to be performed;
  • the means are further configured to perform autonomously activating by the user equipment use of the time-domain mask for radio link monitoring purposes in response to the user equipment detecting that radio link quality in one of the first or second set of resources is significantly worse than radio link quality in another of the first or second set of resources.
  • Example 43 The apparatus according to any one of examples 32 to 42, wherein the means are further configured to perform receiving an indication, by the user equipment from the network node, indicating n previous radio link quality monitoring measurements, n 1, are to be considered to be invalid, and wherein the means are further configured to perform adjusting by the user equipment a counter for radio link monitoring by subtracting n from the counter.
  • Example 44 The apparatus of any preceding apparatus example, wherein the means comprises:
  • At least one processor at least one processor
  • At least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
  • Example 45 An apparatus, comprising:
  • a network node serving a user equipment in a wireless system identify by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment;
  • Example 46 An apparatus, comprising:
  • one or more memories including computer program code
  • circuitry may refer to one or more or all of the following:
  • software e.g., firmware
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • Embodiments herein may be implemented in software (executed by one or more processors), hardware (e.g., an application specific integrated circuit), or a combination of software and hardware.
  • the software e.g., application logic, an instruction set
  • a “computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer, with one example of a computer described and depicted, e.g., in FIG. 1.
  • a computer-readable medium may comprise a computer-readable storage medium (e.g., memories 125, 155, 171 or other device) that may be any media or means that can contain, store, and/or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • a computer-readable storage medium does not comprise propagating signals.
  • eNB or eNodeB evolved Node B (e.g., an LTE base station)
  • EN-DC E-UTRA-NR dual connectivity [00227] en-gNB or En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as secondary node in EN-DC
  • E-UTRA evolved universal terrestrial radio access i.e., the LTE radio access technology
  • gNB or gNodeB base station for 5G/NR, i.e., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC
  • ng-eNB or NG-eNB next generation eNB [00237]
  • UE user equipment e.g., a wireless, typically mobile device

Landscapes

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

Abstract

For a network node serving a UE in a wireless system, the network node identifies that a set of resources is potentially subject to cross-link-interference affecting the UE. The network node sends, toward the UE, information indicating the set of resources is potentially subject to cross-link-interference affecting the UE. For a UE being served by a network node in a wireless system, the UE receives information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the UE. For the set of resources, the UE does not perform radio link quality monitoring in those resources.

Description

Adjusting Radio Link Quality Monitoring based on Potential CLI such as for Advanced
Duplexing Cases
TECHNICAL FIELD
[0001] Exemplary embodiments herein relate generally to wireless communications and, more specifically, relate to communications where a UE is able to receive signals from one network node (or cells) while other UEs transmit to other network node(s) (or their cell(s)).
BACKGROUND
[0002] 3GPP (third generation partnership project) is currently having a Rel-18 (release- 18) study item on flexible duplexing. One of the objectives is to enable more dynamic TDD (time-division duplexing) operation, where neighbor cells may use different TDD radio frame configurations. For this situation, at a given time, one cell may have downlink (DL) transmission, while another cell may have uplink (UL) transmissions. The main advantage of dynamic TDD is that it allows each cell (or a group of cells) to select its TDD UL/DL pattern in accordance with its own traffic load conditions, e.g., a cell serving one single UE with UL-heavy traffic may temporarily use a UL-heavy TDD pattern to increase UL capacity and minimize the latency, while switching later to a DL-heavy TDD pattern when the traffic conditions change.
[0003] This is different to current coordinated TDD operation, where all the cells (within a certain geographical region) operate with aligned uplink/downlink switching pattern to avoid cross-link interference between cells and/or UEs. This is because dynamic TDD can cause severe cross-link-interference (CLI) between cells on slots where neighbor cells use opposite link directions.
[0004] In further detail, when two neighbor cells use different link directions for a given slot, cross-link interference affects cause the following:
[0005] 1 - The reception of the uplink transmission at the gNB A is impacted by the downlink transmission of the gNB B in the neighbor cell.
[0006] 2- The reception of the downlink transmission at the UE B (served by gNB B) is impacted by the uplink transmission by UE A (served by gNB A). BRIEF SUMMARY
[0007] This section is intended to include examples and is not intended to be limiting.
[0008] In an exemplary embodiment, a method is disclosed that includes, for a network node serving a user equipment in a wireless system, identifying by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment. The method includes sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
[0009] An additional exemplary embodiment includes a computer program, comprising code for performing the method of the previous paragraph, when the computer program is run on a processor. The computer program according to this paragraph, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer. Another example is the computer program according to this paragraph, wherein the program is directly loadable into an internal memory of the computer.
[0010] An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and the computer program code are configured to, with the one or more processors, cause the apparatus at least to: for a network node serving a user equipment in a wireless system, identify by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and send, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
[0011] An exemplary computer program product includes a computer-readable storage medium bearing computer program code embodied therein for use with a computer. The computer program code includes: code, for a network node serving a user equipment in a wireless system, for identifying by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and code for sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment. [0012] In another exemplary embodiment, an apparatus comprises means for performing: for a network node serving a user equipment in a wireless system, identifying by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
[0013] In an exemplary embodiment, a method is disclosed that includes, for a user equipment being served by a network node in a wireless system, receiving information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment. The method includes, for the set of resources, not performing by the user equipment radio link quality monitoring in those resources.
[0014] An additional exemplary embodiment includes a computer program, comprising code for performing the method of the previous paragraph, when the computer program is run on a processor. The computer program according to this paragraph, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer. Another example is the computer program according to this paragraph, wherein the program is directly loadable into an internal memory of the computer.
[0015] An exemplary apparatus includes one or more processors and one or more memories including computer program code. The one or more memories and the computer program code are configured to, with the one or more processors, cause the apparatus at least to: for a user equipment being served by a network node in a wireless system, receive information from the network node indicating a set of resources is potentially subject to cross-link- interference affecting the user equipment; and for the set of resources, not perform by the user equipment radio link quality monitoring in those resources.
[0016] An exemplary computer program product includes a computer-readable storage medium bearing computer program code embodied therein for use with a computer. The computer program code includes: code, for a user equipment being served by a network node in a wireless system, for receiving information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment; and code, for the set of resources, for not performing by the user equipment radio link quality monitoring in those resources.
[0017] In another exemplary embodiment, an apparatus comprises means for performing: for a user equipment being served by a network node in a wireless system, receiving information from the network node indicating a set of resources is potentially subject to cross- link-interference affecting the user equipment; and for the set of resources, not performing by the user equipment radio link quality monitoring in those resources.
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] In the attached Drawing Figures:
[0019] FIG. 1 is a block diagram of one possible and non-limiting exemplary system in which the exemplary embodiments may be practiced;
[0020] FIG. 2 illustrates the variables used for RLM that are signaled by the network with the IE UE-TimersAndConstants;
[0021] FIG. 3 is a logic flow diagram for enhanced RLM/BFD mechanism for advanced duplexing cases, and illustrates the operation of an exemplary method, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with an exemplary embodiment;
[0022] FIG. 4 illustrates indication of CLI slots for accurate RLF procedure in dynamic TDD deployments, in accordance with an exemplary embodiment; and
[0023] FIG. 4A illustrates timer T310 evolution over 12 slots using a CLI slots vector similar to the one illustrated in FIG. 4.
DETAILED DESCRIPTION OF THE DRAWINGS
[0024] Abbreviations that may be found in the specification and/or the drawing figures are defined below, at the end of the detailed description section.
[0025] The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. All of the embodiments described in this Detailed Description are exemplary embodiments provided to enable persons skilled in the art to make or use the invention and not to limit the scope of the invention which is defined by the claims.
[0026] When more than one drawing reference numeral, word, or acronym is used within this description with
Figure imgf000006_0001
and in general as used within this description, the
Figure imgf000006_0002
may be interpreted as “or”, “and”, or “both”.
[0027] As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and/or “including”, when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/ or combinations thereof.
[0028] The exemplary embodiments herein describe techniques for enhanced RLM/BFD Mechanism for Advanced Duplexing Cases. Additional description of these techniques is presented after a system into which the exemplary embodiments may be used is described.
[0029] Turning to FIG. 1, this figure shows a block diagram of one possible and nonlimiting exemplary system in which the exemplary embodiments may be practiced. A user equipment (UE) 110, radio access network (RAN) nodes 170 and 170-1, and network element(s) 190 are illustrated. In FIG. 1, a user equipment (UE) 110 is in wireless communication with a wireless network 100.
[0030] A UE is a wireless, typically mobile device that can access a wireless network. The UE 110 includes circuitry comprising one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127. Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a control module 140, comprising one of or both parts 140-1 and/or 140-2, which may be implemented in a number of ways. The control module 140 may be implemented in hardware as control module 140-1, such as being implemented as part of the one or more processors 120. The control module 140-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the control module 140 may be implemented as control module 140- 2, which is implemented as computer program code 123 and is executed by the one or more processors 120. For instance, the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein. The UE 110 communicates with RAN node 170 via a wireless link 111 and with RAN node 170-1 via wireless link 111-1.
[0031] The RAN nodes 170, 170-1 are network nodes such as base stations that provide access by wireless devices such as the UE 110 to the wireless network 100. The RAN nodes 170, 170-1 are referred to herein as gNB 170, but this is only one example. Additionally, if the network (NW or N/W) is referred to as performing an action, that action is typically performed by the gNB 170, although other options are possible.
[0032] The RAN nodes 170, 170-1 are considered to be similar, and thus the circuitry for RAN node 170 will only be described. The RAN node 170 may be, for instance, a base station for 5G, also called New Radio (NR). In 5G, the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or an ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (e.g., the network element(s) 190). The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. The NG-RAN may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs), of which DU 195 is shown. Note that the DU may include or be coupled to and control a radio unit (RU). The gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the Fl interface connected with the gNB-DU. The Fl interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195. The gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by one gNB-DU. The gNB-DU terminates the Fl interface 198 connected with the gNB-CU. Note that the DU 195 is considered to include the transceiver 160, e.g., as part of an RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under control of and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution), or any other suitable base station.
[0033] The RAN node 170 includes circuitry comprising one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157. Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include the processor(s) 152, memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory/memories and processor(s), and/or other hardware, but these are not shown.
[0034] The RAN node 170 includes a control module 150, comprising one of or both parts 150-1 and/or 150-2, which may be implemented in a number of ways. The control module 150 may be implemented in hardware as control module 150-1, such as being implemented as part of the one or more processors 152. The control module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the control module 150 may be implemented as control module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152. For instance, the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein. Note that the functionality of the control module 150 may be distributed, such as being distributed between the DU 195 and the CU 196, or be implemented solely in the DU 195.
[0035] The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more RAN nodes 170 communicate using, e.g., link 176. The link 176 may be wired or wireless or both and may implement, e.g., an Xn interface for 5G, an X2 interface for LTE, or other suitable interface for other standards.
[0036] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH/DU, and the one or more buses 157 could be implemented in part as, e.g., fiber optic cable or other suitable network connection to connect the other elements (e.g., a central unit (CU), gNB-CU) of the RAN node 170 to the RRH/DU 195. Reference 198 also indicates those suitable network link(s).
[0037] It is noted that description herein indicates that “cells” perform functions, but it should be clear that the base station that forms the cell will perform the functions. The cell makes up part of a base station. That is, there can be multiple cells per base station. For instance, there could be three cells for a single carrier frequency and associated bandwidth, each cell covering one-third of a 360-degree area so that the single base station’s coverage area covers an approximate oval or circle. Furthermore, each cell can correspond to a single carrier and a base station may use multiple carriers. So, if there are three 120 degree cells per carrier and two carriers, then the base station has a total of 6 cells.
[0038] The wireless network 100 may include a network element or elements 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a data network 191, such as a telephone network and/or a data communications network (e.g., the Internet). Such core network functionality for 5G may include access and mobility management function(s) (AMF(s)) and/or user plane functions (UPF(s)) and/or session management function(s) (SMF(s)). Such core network functionality for LTE may include MME (Mobility Management Entity) functionality and/or SGW (Serving Gateway) functionality. These are merely exemplary functions that may be supported by the network element(s) 190, and note that both 5G and LTE functions might be supported. The RAN node 170 is coupled via a link 131 to a network element 190. The link 131 may be implemented as, e.g., an NG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards. The network element 190 includes circuitry comprising one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s)) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the network element 190 to perform one or more operations.
[0039] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.
[0040] The computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, firmware, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories 125, 155, and 171 may be means for performing storage functions. The processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN node 170, and other functions as described herein.
[0041] In general, the various embodiments of the user equipment 110 can include, but are not limited to, cellular telephones (such as smart phones, mobile phones, cellular phones, voice over Internet Protocol (IP) (VoIP) phones, and/or wireless local loop phones), tablets, portable computers, vehicles or vehicle-mounted devices for, e.g., wireless V2X (vehicle-to- everything) communication, image capture devices such as digital cameras, gaming devices, music storage and playback appliances, Internet appliances (including Internet of Things, loT, devices), loT devices with sensors and/or actuators for, e.g., automation applications, as well as portable units or terminals that incorporate combinations of such functions, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), Universal Serial Bus (USB) dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. That is, the UE 110 could be any end device that may be capable of wireless communication. By way of example rather than limitation, the UE may also be referred to as a communication device, terminal device (MT), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT).
[0042] Having thus introduced one suitable but non-limiting technical context for the practice of the exemplary embodiments, the exemplary embodiments will now be described with greater specificity.
[0043] As stated above, at a given time, one cell may have downlink (DL) transmission, while another cell may have uplink (UL) transmissions. This can cause severe cross-link-interference (CLI) between cells on slots where neighbor cells use opposite link directions. Herein, it is identified that such CLI effects will impact radio link monitoring (RLM) with the risk of causing undesired radio link failure (RLF) triggering, also known as false RLF events. Exemplary solutions to overcome such problems are presented.
[0044] In RRC_CONNECTED mode, the UE performs Radio Link Monitoring (RLM) in the active BWP based on reference signals (e.g., SSB/CSLRS) and signal quality thresholds configured by the network. SSB-based RLM is based on the SSB associated to the initial DL BWP and can only be configured for the initial DL BWP and for DL BWPs containing the SSB associated to the initial DL BWP. For other DL BWPs, RLM can only be performed based on CSLRS. [0045] In the case of beamformed transmissions, the UE also performs Beam Failure Detection (BFD) to monitor the quality of the connected beam. As with REM, BFD is also based on reference signals (SSB & CSI-RS) and signal quality threshold configured by the network. The detection of a beam failure triggers a beam failure recovery in which the UE switches to a different beam after a successful random-access procedure.
[0046] When a UE is conducting RLM/BFD in a timeslot where there is significant CLI (denoted as a CLI-slot), the UE is likely to increase the out-of-sync counter which ultimately can trigger RLF/BFR. This can cause re-establishment attempts, or in worst cases result in call dropping, or beam failure recovery. At the network, NR Rel-16 include simple coordination between gNBs (via the Xn and Fl interfaces) to make them aware of CLI-slots. This is often used by the gNBs to apply coordinated scheduling, so nearby UEs are not scheduled during CLI slots with opposite transmission directions (e.g., one UE receiving in DL, while another nearby UE transmits in UL with high transmit power). Conducting RLM/BFD during CLI-slots is therefore not desirable as it does not really reflect the experienced end-user quality. Conducting RLM/BFD in CLI-slots can therefore cause undesirable problems, which can be characterized as false RLF/BFD events, and hence should be avoided. This is one exemplary problem addressed herein.
[0047] Before describing the exemplary embodiments, it is helpful to provide an introduction into this technical area. The top-level stage-2 description of RLM/RLF appears in 3GPP TS 38.300 as follows (the quoted part is between opening and closing quotation marks):
[0048] “9.2.7 Radio Link Failure
[0049] In RRC_CONNECTED, the UE performs Radio Link Monitoring (RLM) in the active BWP based on reference signals (SSB/CSLRS) and signal quality thresholds configured by the network. SSB-based RLM is based on the SSB associated to the initial DL BWP and can only be configured for the initial DL BWP and for DL BWPs containing the SSB associated to the initial DL BWP. For other DL BWPs, RLM can only be performed based on CSLRS. In case of DAPS handover, the UE continues the detection of radio link failure at the source cell until the successful completion of the random access procedure to the target cell.
[0050] The UE declares Radio Link Failure (RLF) when one of the following criteria are met: [0051] - Expiry of a radio problem timer started after indication of radio problems from the physical layer (if radio problems are recovered before the timer is expired, the UE stops the timer); or
[0052] - Expiry of a timer started upon triggering a measurement report for a measurement identity for which the timer has been configured while another radio problem timer is running; or
[0053] Random access procedure failure; or
[0054] - RLC failure; or”
[0055] This ends the quoted part of section 9.2.7 of 3GPP TS 38.300.
[0056] UE configuration of RLM happens via RRC signaling as defined in 3 GPP TS 38.331. This includes options for relaxed measurement criterion for low mobility users as defined in clause 5.7.13. The UE requirements for RLM are defined in 3GPP TS 38.133, clause 8.1 as follows (the quoted part is between opening and closing quotation marks):
[0057] “8.1 Radio Link Monitoring
[0058] 8.1.1 Introduction
[0059] The requirements in clause 8.1 apply for radio link monitoring on:
[0060] - PCell in SA NR, NR-DC and NE-DC operation mode,
[0061] - Deactivated PSCell in NR-DC and EN-DC operation mode.
[0062] The UE shall monitor the downlink radio link quality based on the reference signal configured as RLM-RS resource(s) in order to detect the downlink radio link quality of the PCell, PSCell and deactivated PSCell as specified in TS 38.213 [3]. The configured RLM-RS resources can be all SSBs, or all CSLRSs, or a mix of SSBs and CSLRSs. UE is not required to perform RLM outside the active DL BWP.
[0063] On each RLM-RS resource, the UE shall estimate the downlink radio link quality and compare it to the thresholds Qout and Qin for the purpose of monitoring downlink radio link quality of the cell.
[0064] When a CORESET that the UE uses for monitoring PDCCH includes two TCI states and the UE is provided sfnSchemePdcch set to 'sfnSchemeA' or 'sfnSchemeB', the UE shall estimate the downlink radio link quality and compare it to the single thresholds Qout and Qin for the purpose of monitoring downlink radio link quality of the cell(s). How to compute the single hypothetical PDCCH SNR based on two active TCI states is up to UE implementation.
[0065] The threshold Qout is defined as the level at which the downlink radio link cannot be reliably received and shall correspond to the out-of-sync block error rate (BLERout) as defined in Table 8.1.1-1. For SSB based radio link monitoring, Qout_SSB is derived based on the hypothetical PDCCH transmission parameters listed in Table 8.1.2.1-1. For CSI-RS based radio link monitoring, Qout_CSI-RS is derived based on the hypothetical PDCCH transmission parameters listed in Table 8.1.3.1-1.
[0066] The threshold Qin is defined as the level at which the downlink radio link quality can be received with significantly higher reliability than at Qout and shall correspond to the in-sync block error rate (BLERin) as defined in Table 8.1.1-1. For SSB based radio link monitoring, Qin_SSB is derived based on the hypothetical PDCCH transmission parameters listed in Table 8.1.2.1-2. For CSI-RS based radio link monitoring, Qin_CSI-RS is derived based on the hypothetical PDCCH transmission parameters listed in Table 8.1.3.1-2.
[0067] The out-of-sync block error rate (BEERout) and in-sync block error rate (BLERin) are determined from the network configuration via parameter rlmlnSyncOutOfSyncThreshold signaled by higher layers. When UE is not configured with rlmlnSyncOutOfSyncThreshold from the network, UE determines out-of-sync and in-sync block error rates from Configuration #0 in Table 8.1.1-1 by default. All requirements in clause 8.1 are applicable for BLER Configuration #0 in Table 8.1.1-1.”
[0068] This ends the quoted part of section 8.1 of 3 GPP TS 38.133.
[0069] With the corresponding physical aspects of RLM appearing in 3GPP TS 38.213 as follows (the quoted part is between opening and closing quotation marks):
[0070] “Radio link monitoring
[0071] The downlink radio link quality of the primary cell is monitored by a UE for the purpose of indicating out-of-sync/in-sync status to higher layers. The UE is not required to monitor the downlink radio link quality in DL BWPs other than the active DL BWP, as described in clause 12, on the primary cell. If the active DL BWP is the initial DL BWP and for SS/PBCH block and CORESET multiplexing pattern 2 or 3, as described in clause 13, the UE is expected to perform RLM using the associated SS/PBCH block when the associated SS/PBCH block index is provided by RadioLinkMonitoringRS.”
[0072] The radio problem timer is started as indicated in 3GPP TS 38.331 (the quoted part is between opening and closing quotation marks):
[0073] “5.3.10.1 Detection of physical layer problems in RRC_CONNECTED
[0074] The UE shall:
[0075] 1> upon receiving N310 consecutive ‘out-of-sync’ indications for the SpCell from lower layers while neither T300, T301, T304, T319 not T311 is running:
[0076] 2> start timer T310 for the corresponding SpCell.”
[0077] The variables used for RLM are signaled by the network with the IE UE- TimersAndConstants specified in TS 38.331 (for RLF purposes T310, N310, N311 are used) as illustrated in FIG. 2.
[0078] Note that, from the current NR specifications, the UE is completely unaware of whether the UE is subject to CLI interference, and when so-called CLI slots may occur. RLM is therefore conducted fully independently of whether CLI is present or not, even though the network in general will avoid scheduling a UE during such CLI slots.
[0079] From NR Rel-16 specifications, it is possible to configure a UE to perform so- called UE-to-UE CLI measurements as it is summarized in the following overview paper: K. Pedersen et al., "Advancements in 5G New Radio TDD Cross Link Interference Mitigation," in IEEE Wireless Communications, vol. 28, no. 4, pp. 106-112, August 2021, doi: 10.1109/MWC.001.2000376.
[0080] As also reported in that article, NR Rel-16 also includes options for gNBs to exchange their intended UL-DL configuration (i.e., their TDD radio frame configuration) over the Xn and Fl interfaces. For more information, see the IEEE publication ‘Advancements in 5G New Radio TDD Cross Link Interference Mitigation’, IEEE Wireless Communications ( Volume: 28, Issue: 4, August 2021) (DOI: 10.1109/MWC.001.2000376). This IEEE publication describes that new TDD coordination mechanisms have been defined between gNBs, and between CU and DUs, to foster effective and simple solutions. This includes options for a gNB to inform its neighboring gNBs which radio frame configurations it intends to use in its served cells, expressed with a new information element (IE) labelled the Intended TDD DL-UL Configuration NR. This offers a simple proactive TDD coordination solution, where a cell can announce in advance which TDD radio frame configuration it intends to use. As different cells may use different SCS and cyclic prefix configurations, the aforementioned IE contains the SCS, cyclic prefix and TDD DL-UL slot configuration of an NR cell that a neighbor cell needs to take into account for cross-link interference mitigation when operating its own cells. The actual TDD radio frame configuration is expressed as a list of slot formats. Signaling of the Intended TDD DL-UL Configuration is supported between two gNBs on the Xn interface, using the Xn application protocol (XnAP), as well as between CU and DU. Additionally, signaling for this may be performed as in 3GPP TS 38.423 V17.1.0 (2022-06), section 9.2.2.40, which describes an IE for “Intended TDD DL-UL Configuration NR”.
[0081] Based on such inter-gNB signaling and the aforementioned UE CLI measurements, the network (NW) will know in which slots a UE may be subject to CLI for downlink reception, and in which slots transmission from a UE may be subject to strong CLI for reception at its source cell. The NW will exploit such knowledge to avoid uplink and downlink scheduling in such CLI slots, which anyways will be subject to poor reception quality.
[0082] Concerning beam failure detection, in deployments using beamforming, UEs are able to detect the poor quality of the connected beam. This is known as beam failure detection (BFD) and it follows very similar steps as the RLM/RLF procedure described above.
[0083] The top-level stage-2 description of BFD appears in 3GPP TS 38.300 as follows (the quoted part is between opening and closing quotation marks):
[0084] “9.2.8 Beam failure detection and recovery
[0085] For beam failure detection, the gNB configures the UE with beam failure detection reference signals (SSB or CSLRS) and the UE declares beam failure when the number of beam failure instance indications from the physical layer reaches a configured threshold before a configured timer expires.”
[0086] The BFD and BFR variables are configured via RRC with the parameters indicated in BeamFailureRecoveryConfig, BeamFailureRecoverSCellConfig and Radio LinkMoniloringConfig. [0087] The UE behavior for BFD is defined in 3GPP TS 38.321 as shown below:
Figure imgf000017_0001
[0088] Now that an introduction into this technical area has been provided, an overview of the exemplary embodiments is provided. An exemplary method is proposed herein where the network can configure UEs to only perform REM on dedicated time-domain resources, such that the UE does not perform such actions during so-called CLI slots, where the network may not intend to schedule the UE. This may involve configuring the UE with a timedomain mask or other pattern (such as a vector) that informs in which symbols or slots the UE shall not perform RLM. That includes not performing DL RLM measurement on RLM-RS resources during such symbols or slots. Moreover, the timer that is to be started after indication of radio problems from the physical layer is not advanced during the symbols/slots indicated by the time-domain mask (i.e., the timer is stopped during CLI symbols/slots), such that expiry of this timer excludes CLI-slots for triggering potential RLF.
[0089] Signaling of the time-domain mask may be realized with RRC signaling, MAC signaling (e.g., MAC CE), or in the event of fast adapting dynamic TDD by means for physical layer signaling. The time-domain mask indicating resources (e.g., slots/symbols) with potential high CLI and the (de-)activation of the time-domain mask for RLM purposes may be separately signaled. For instance, the time-domain mask may be configured using higher layer signaling (RRC) while the activation of the time-domain mask for RLM purposes may be signaled using either MAC or PHY signaling. That is, the UE only applies the time-domain mask if explicitly signaled by the gNB, e.g., the use of the time-domain mask is activated after a CLI measurement report from the UE indicating high CLI level. The UE may also autonomously activate the time-domain mask for RLM purposes if e.g., the UE detects that the radio link quality in CLI slots/symbols is significantly worse than radio link quality in non-CLI slots/symbols or if the measured CLI exceeds a certain threshold (e.g., using existing Rel-16 UE CLI measurements). The UE may also perform separate RLM procedures, possibly using different RLM configurations, on CLI and non-CLI slots, as indicated by the network-configured time-domain mask. In this case, the UE may only trigger RLF based on RLM on non-CLI slots, while upon detection of RLF on CLI slots, the UE may only send a specific report to the network but continue normal operation on the serving cell. In this case, the UE may suspend RLM on CLI slots after sending the report to the network.
[0090] In summary, a framework is proposed that includes one or more of the following:
[0091] 1) Techniques for the gNB to configure the UE with a time-domain mask that identifies at least two subsets of time domain resources (e.g., CLI and non-CLI slots/symbols); [0092] 2) Techniques for the gNB and/or the UE to (de-)activate the use of the configured time-domain mask for the purpose of RLM; or
[0093] 3) Techniques for the UE to either only perform RLM procedure on one subset of the time-domain resources or to perform separate RLM procedures on different subsets of the time-domain resources, as indicated by the configured and activated time-domain mask
[0094] As an alternative to the time-domain mask configuration, the gNB 170 could dynamically indicate to the UE 110 that RLM-RS measurements on the n previous slots should be considered to be invalid, given the presence of CLI. The UE could then adjust the RLM counters accordingly. For instance, the UE could subtract n from a value in the N310 counter.
[0095] An exemplary advantage and technical effect of the proposed techniques is that they allow the network to control UEs so the UEs do not perform RLM, and trigger false RLF events, as a result of radio performance conditions in so-called CLI slots where the network anyways has no intention of scheduling the UE. Thereby, false RLF triggering is avoided for dynamic TDD cases, and hence unnecessary actions for the UE to perform RRC re-establishment events, or in worst case experiencing dropped calls.
[0096] Note that, while the present idea is primarily targeted to dynamic TDD, it may also be applicable to subband non-overlapping full duplex (SBFD) operation, which is also in the objective of the ongoing Rel-18 study item on Evolution of Duplex Operation. In this case, the gNB may make use of the proposed ideas to configure a UE to only perform RLM on DL-only slots/symbols and not on SBFD slots/symbols due to potentially high inter-subband UE-2-UE CLI.
[0097] Note that the description herein is focused on RLM/RLF rather than BFD/BFR. However, the same concept can be applied during the beam failure detection procedure at the UE.
[0098] Now that an overview has been provided, more details are provided. An exemplary embodiment that may be implemented as summarized by the following procedural steps. These procedural steps are illustrated by FIG. 3, which is a logic flow diagram for enhanced RLM/BFD mechanism for advanced duplexing cases. FIG. 3 also illustrates the operation of an exemplary method, a result of execution of computer program instructions embodied on a computer readable memory, functions performed by logic implemented in hardware, and/or interconnected means for performing functions in accordance with an exemplary embodiment. In this example, the steps are performed by the UE 110, e.g., under control of the control module 140 and by the gNB 170, e.g., under control of the control module 150. It is assumed for ease of description that the network (NW) is the gNB 170, although other options are possible.
[0099] 1. The NW identifies that a set of resources (which could be slots, symbols, or other resources, at least one resource) is potentially subject to high CLI. This set of resources is deemed to be resources that are potentially subjected to cross-link-interference high enough to impair reception by the user equipment. This determination of potentially high enough interference is up to gNB implementation. The “potentially” occurs because, even if CLI has been determined to be high in a slot or resource, this does not mean the UE’s reception will actually be impaired in any particular slot or resource. For instance, the UE could move to be near the center of the cell for its serving gNB, and away from any interfering UEs transmitting to a different cell. That is, while the gNB can assume a particular slot will have high CLI, there is no guarantee that will be true for every UE being served by that gNB.
[00100] In step La., a gNB may identify CLI resources as resources where the gNB uses a transmission direction that is different from that of a neighboring gNB (e.g., or a cell formed by the gNB). The gNB, in step Lb., may also utilize UE CLI measurements to identify if a UE is subject to noticeable CLI levels for DL reception. In step l.c., the gNB may not schedule certain UEs during such CLI-resource(s) (e.g., slots/symbols). For instance, the gNB might decide not to schedule reception for these UEs during CLI slots because the interference level is too high to ensure a reliable decoding of the data. Consider dynamic TDD deployments, where typically UEs in the cell-edge are prone to be impacted by cross-link interference. The gNB may not schedule those UEs during the CLI slots. On the other hand, cell-centered UEs could still be scheduled. The gNB could use the UE CLI measurements to identify the UEs with high CLI.
[00101] As described above, as an alternative to the time-domain mask configuration, the gNB 170 could dynamically indicate to the UE 110 that RLM-RS measurements on the n previous slots should be considered to be invalid, given the presence of CLI. See step l.d. [00102] 2. The NW (e.g., gNB) informs the UE not to perform RLM in the CLI- resource(s) (such as slots or symbols). This may involve (step 2. a.) configuring and activating a time-domain mask to the UE that informs in which resources the UE is not to perform RLM actions. Signaling and activation of such time-domain mask may be realized (see step 2.a.i) with RRC signaling, MAC-signaling (e.g., MAC CE), physical layer signaling, or a combination of the above (e.g., configuration via RRC and activation via MAC CE).
[00103] 3. The UE complies with the received instructions in step 2 by, e.g., not performing (step 3. a.) DL RLM measurement on RLM-RS resources during such CLI resources (e.g., slots/symbols). Furthermore, in step 3.b., the radio problem timer that is started after indication of radio problems from the physical layer is not advanced during times of CLI resources (i.e., the timer is stopped), such that expiry of this timer excludes the time spent in CLI-resources (e.g., slotsO for triggering potential RLF).
[00104] The actions taken by the UE may involve the following implications on the 3 GPP NR specifications:
[00105] 3.c. Impact on PHY specifications in 3 GPP TS 38.213: The UE should only monitor the downlink radio link quality based on the reference signal configured as RLM-RS resource(s) in non-CLI resources (e.g., slots or symbols) in order to detect the downlink radio link quality and compare the quality to the thresholds Qout and Qin for the purpose of monitoring downlink radio link quality of the cell.
[00106] 3.d. Impact on RRC specifications (3GPP TS 38.331): The UE starts timer
T310 (also known as the radio problem timer in the stage-2 specs - 3GPP TS 38.300) upon detecting physical layer RLM problems upon receiving N310 consecutive out-of-sync indications from lower layers, where N310 is the maximum number of consecutive “out-of-sync” indications for the PCell received from lower layers. Timer T310 is stopped during all CLI slots or symbols. RLF is declared when T310 expires.
[00107] 3.e. Random-access procedure failure for RLM purposes and RLF triggering is only monitored during resources that are not CLI-resources. That is, random-access attempts sent during CLI resources (e.g., slots) are not counted for RLM/RLF purposes.
[00108] 3.f. The UE requirements in 3GPP TS 38.133, clause 8.1, may be updated accordingly so RLM and RLF triggering is omitted during CLI resources (e.g., slots or symbols). [00109] 3.g. Concerning the alternative to the time-domain mask configuration, in step l.d., the gNB 170 has dynamically indicated to the UE 110 that RLM-RS measurements on the n previous slots should be considered to be invalid, given the presence of CLI. The UE then adjusts (in step 3.g.) the RLM counters accordingly. For instance, the UE could subtract n from a value in the N310 counter (e.g., or other appropriate counter).
[00110] Note that 3GPP specifications may not use the term “non-CLI” and “CLI slots” or symbols or resources, but may only refer to, e.g., first and second subset of slots/symbols, where, e.g., RLM is only to be performed during the first subset of slots/symbols. The terms ““non-CLI resources” and “CLI resources” are used here for ease of reference.
[00111] Aspects of possible exemplary embodiments are further illustrated in FIG. 4, which illustrates indication of CLI slots for RLF procedure in dynamic TDD deployments, in accordance with an exemplary embodiment. Here the TDD radio frame configurations 400-1 and 400-2 for two neighboring cells are illustrated. The TDD radio frame configurations 400-1 and 400-2 have 10 slots, slot-0410-0 through slot-9 410-9, the DL and UL slots are shown, and the dashed ovals are used to illustrate a slot where one cell is performing DL while the other is performing UL. There is a vector 430 to indicate CLI slots (or other resources such as symbols). The “Xs” in the vector indicate CLI slots, and no indication indicate non-CLI slots. There is a cell #1 420-1, e.g., formed by gNB 170, and another cell #2 420-2, e.g., formed by gNB 170-1. It is noted that, for cells to have different TDD patterns, the cells should be served/formed by different gNBs.
[00112] For slots where the two cells 420-1 and 420-2 have identical transmission direction, there is no CLI between the cells. For slots where they have opposite transmission directions, there is CLI, i.e., denoted as CLI slots via the Xs. The vector 420 (e.g., a time-domain mask) of CLI slots is signaled to the UE as per step 2 in FIG. 3 to inform the UE not to perform RLM and RLF triggering during these slots. In line with step 3 of FIG. 3, the UE takes the defined actions as per 3.a.-3.f.. For instance, as shown in reference 440, the RLM and RLF triggering is not happening in these slots and the T310 timer (if otherwise started) is temporarily stopped in these CLI slots.
[00113] Referring to FIG. 4A, this figure illustrates timer T310 evolution over 12 slots using a CLI slots vector similar to the one illustrated in FIG. 4. In this example, the CLI slots vector 430-1 has 12 entries, and similar to the CLI slots vector 430 in FIG. 4, slots 2, 4, 7, and 9 are denoted. The T310 timer starts at T310 initial value 450 and ends at value 455 after all 12 slots 410. Each time period 460-1, 460-2, 460-3, and 460-4 corresponds to slots 2, 4, 7, and 9, respectively, having a corresponding entry in the vector 430 indicating the T310 timer is to be stopped in those slots.
[00114] Returning to a description of FIG. 4, in one possible implementation, the UE is configured via RRC with a time-domain mask (e.g., the vector 430) identifying slots/symbols with potentially high CLI. It is noted that the vector 430 can be anything that indicates slots (or symbols), and a vector or mask are possible implementations of this. In the example of FIG. 4, the following slots are indicated in vector 430: slot-2 410-2; slot-4 410-4; slot-7 410-7; and slot- 9 410-9. The UE still performs RLM in all slots/symbols according to legacy behavior until the UE receives an explicit activation message (MAC CE) from the gNB. After the activation message is received, the UE only performs RLM during one subset of the slots/symbols indicated by the time-domain mask (i.e., non-CLI slots/symbols). The transmission of the activation message from the gNB to the UE may be triggered by the reception of a CLI measurement report indicating high CLI at the UE.
[00115] In an alternative implementation, see step 3.h. of FIG. 3, the UE may autonomously activate the use of the network-configured time-domain mask for RLM purposes if the UE detects that the radio link quality in one subset of resources (e.g., slots/symbols such as CLI slots/symbols) is significantly worse than radio link quality in the other subset of resources (e.g., slots/symbols such as non-CLI slots/symbols). This could be based on SINR and/or block error rate estimations. UE-specific CLI measurements such as CLLRSSI and/or CLI SRS-RSRP could also be used as trigger for the time-domain mask activation.
[00116] In yet another implementation, see step 3.i. of FIG. 3, the UE may be configured to perform separate RLM procedures using different RLM configurations in different subsets of the time-domain resources, i.e., in CLI and non-CLI resources (e.g., slots/symbols). Upon detection of RLF on CLI slots/symbols, the UE may send a report to the network but continue normal operation on the serving cell. In this case, the UE may suspend performing RLM on CLI slots (e.g., until further notification or until a timer expires). Upon detection of RLF on non-CLI slots/symbols, the UE triggers RLF recovery according to a legacy procedure. It should be noted that the CLI and non-CLI resources do not overlap.
[00117] Note that the description above is focused on RLM/RLF procedure but the same concept can be applied for BFD in case of beamformed transmissions. In such case, the UE is instructed to not perform BFD in CLI slots such that the BFI counter is not increased due to the presence of CLI. Furthermore, in cases where the timer beamFailureDetectionTimer is running, it will be stopped during CLI slots (as it is described for T310 timer).
[00118] The following are other examples.
[00119] Example 1. A method, comprising:
[00120] for a network node serving a user equipment in a wireless system, identifying by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and
[00121] sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
[00122] Example 2. The method according to example 1, wherein the identifying comprises determining that the set of resources is potentially subject to cross -link-interference high enough to impair reception by the user equipment.
[00123] Example 3. The method according one of examples 1 to 2, wherein the identifying determines the set of resources as resources with cross-link-interference where the network node uses a transmission direction that is different from that of a neighboring network node, and wherein the sending comprises sending information identifying the set of resources where the network node uses a transmission direction that is different from that of a neighboring network node.
[00124] Example 4. The method according one of examples 1 to 2, wherein the identifying utilizes user equipment cross-link interference measurements to determine if a user equipment is subject to cross-link interference levels above a threshold for downlink reception, and wherein the sending comprises sending information identifying the cross-link interference resources where the user equipment cross-link interference measurements indicate cross-link interference levels above the threshold for downlink reception. [00125] Example 5. The method according one of examples 1 to 4, further comprising the network node not scheduling selected user equipment for reception during the set of recourses.
[00126] Example 6. The method according to any one of examples 1 to 5, wherein the set of resources comprise either slots or symbols.
[00127] Example 7. The method according to any one of examples 1 to 6, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring.
[00128] Example 8. The method according to any one of examples 1 to 6, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms.
[00129] Example 9. A method, comprising:
[00130] for a user equipment being served by a network node in a wireless system, receiving information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment; and
[00131] for the set of resources, not performing by the user equipment radio link quality monitoring in those resources.
[00132] Example 10. The method according to example 9, further comprising not advancing by the user equipment a timer that is started after indication of radio problems during times of the set of resources.
[00133] Example 11. The method according to one of examples 9 or 10, further comprising monitoring by the user equipment downlink radio link quality based on a reference signal configured by the network node as one or more radio link monitoring-reference signal resource(s) in the set of resources in order to detect the downlink radio link quality and compare the measured downlink radio link quality with one or more thresholds to determine downlink radio link quality.
[00134] Example 12. The method according to one of examples 9 to 11, further comprising starting by the user equipment a timer, to be started after indication of radio problems, in response to detecting physical layer radio link monitoring problems, but stopping the timer for periods of the set of resources. [00135] Example 13. The method according to one of examples 9 to 12, further comprising not counting by the user equipment random access attempts sent during the set of resources for radio link monitoring or radio link failure or beam failure detection purposes.
[00136] Example 14. The method according to one of examples 9 to 12, further comprising omitting by the user equipment radio link monitoring or radio link failure or beam failure detection triggering during the set of resources.
[00137] Example 15. The method according to any one of examples 9 to 14, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring.
[00138] Example 16. The method according to any one of examples 9 to 14, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms.
[00139] Example 17. The method according to any one of examples 9 to 16, further comprising the user equipment receiving configuration from the network node to only perform radio link quality monitoring on downlink-only resources and wherein the set of resources are subband non-overlapping full-duplex resources.
[00140] Example 18. The method according to any one of examples 9 to 16, wherein: [00141] the set of resources is a first set of time-domain resources;
[00142] the information comprises a time-domain mask indicating the first set of timedomain resources and a second set of time-domain resources where radio link quality monitoring is to be performed;
[00143] the method comprises:
[00144] performing by the user equipment separate radio link monitoring procedures using different radio link monitoring configurations in different subsets of the first and second time-domain resources;
[00145] in response to detecting radio link monitoring on the first set of time-domain resources, suspending by the user equipment performing radio link monitoring on the first set of resources; and
[00146] in response to detecting radio link monitoring on the second set of timedomain resources, triggering by the user equipment a procedure for radio link failure recovery. [00147] Example 19. The method according to any one of examples 9 to 16, wherein: [00148] the set of resources are a first set of time-domain resources;
[00149] the information comprises a time-domain mask indicating the first set of timedomain resources and a second set of time-domain resources where radio link quality monitoring is to be performed; and
[00150] the method comprises autonomously activating by the user equipment use of the time-domain mask for radio link monitoring purposes in response to the user equipment detecting that radio link quality in one of the first or second set of resources is significantly worse than radio link quality in another of the first or second set of resources.
[00151] Example 20. The method according to any one of examples 9 to 19, further comprising receiving an indication, by the user equipment from the network node, indicating n previous radio link quality monitoring measurements, n
Figure imgf000027_0001
1, are to be considered to be invalid, and wherein the method further comprises adjusting by the user equipment a counter for radio link monitoring by subtracting n from the counter.
[00152] Example 21. A computer program, comprising code for performing the methods of any of examples 1 to 20, when the computer program is run on a computer.
[00153] Example 22. The computer program according to example 21, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with the computer.
[00154] Example 23. The computer program according to example 21, wherein the computer program is directly loadable into an internal memory of the computer.
[00155] Example 24. An apparatus, comprising means for performing:
[00156] for a network node serving a user equipment in a wireless system, identifying by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and
[00157] sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment. [00158] Example 25. The apparatus according to example 24, wherein the identifying comprises determining that the set of resources is potentially subject to cross -link-interference high enough to impair reception by the user equipment.
[00159] Example 26. The apparatus according one of examples 24 to 25, wherein the identifying determines the set of resources as resources with cross-link-interference where the network node uses a transmission direction that is different from that of a neighboring network node, and wherein the sending comprises sending information identifying the set of resources where the network node uses a transmission direction that is different from that of a neighboring network node.
[00160] Example 27. The apparatus according one of examples 24 to 25, wherein the identifying utilizes user equipment cross-link interference measurements to determine if a user equipment is subject to cross-link interference levels above a threshold for downlink reception, and wherein the sending comprises sending information identifying the cross-link interference resources where the user equipment cross-link interference measurements indicate cross-link interference levels above the threshold for downlink reception.
[00161] Example 28. The apparatus according one of examples 24 to 27, wherein the means are further configured to perform not scheduling by the network node selected user equipment for reception during the set of recourses.
[00162] Example 29. The apparatus according to any one of examples 24 to 28, wherein the set of resources comprise either slots or symbols.
[00163] Example 30. The apparatus according to any one of examples 24 to 29, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring.
[00164] Example 31. The apparatus according to any one of examples 24 to 29, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms.
[00165] Example 32. An apparatus, comprising means for performing:
[00166] for a user equipment being served by a network node in a wireless system, receiving information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment; and [00167] for the set of resources, not performing by the user equipment radio link quality monitoring in those resources.
[00168] Example 33. The apparatus according to example 32, wherein the means are further configured to perform not advancing by the user equipment a timer that is started after indication of radio problems during times of the set of resources.
[00169] Example 34. The apparatus according to one of examples 32 or 33, wherein the means are further configured to perform monitoring by the user equipment downlink radio link quality based on a reference signal configured by the network node as one or more radio link monitoring-reference signal resource(s) in the set of resources in order to detect the downlink radio link quality and compare the measured downlink radio link quality with one or more thresholds to determine downlink radio link quality.
[00170] Example 35. The apparatus according to one of examples 32 to 34, wherein the means are further configured to perform starting by the user equipment a timer, to be started after indication of radio problems, in response to detecting physical layer radio link monitoring problems, but stopping the timer for periods of the set of resources.
[00171] Example 36. The apparatus according to one of examples 32 to 35, wherein the means are further configured to perform not counting by the user equipment random access attempts sent during the set of resources for radio link monitoring or radio link failure or beam failure detection purposes.
[00172] Example 37. The apparatus according to one of examples 32 to 35, wherein the means are further configured to perform omitting by the user equipment radio link monitoring or radio link failure or beam failure detection triggering during the set of resources.
[00173] Example 38. The apparatus according to any one of examples 32 to 37, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring.
[00174] Example 39. The apparatus according to any one of examples 32 to 37, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms.
[00175] Example 40. The apparatus according to any one of examples 32 to 39, wherein the means are further configured to perform the user equipment receiving configuration from the network node to only perform radio link quality monitoring on downlink-only resources and wherein the set of resources are subband non-overlapping full-duplex resources.
[00176] Example 41. The apparatus according to any one of examples 32 to 39, wherein:
[00177] the set of resources is a first set of time-domain resources;
[00178] the information comprises a time-domain mask indicating the first set of timedomain resources and a second set of time-domain resources where radio link quality monitoring is to be performed;
[00179] the means are further configured to perform:
[00180] performing by the user equipment separate radio link monitoring procedures using different radio link monitoring configurations in different subsets of the first and second time-domain resources;
[00181] in response to detecting radio link monitoring on the first set of time-domain resources, suspending by the user equipment performing radio link monitoring on the first set of resources; and
[00182] in response to detecting radio link monitoring on the second set of timedomain resources, triggering by the user equipment a procedure for radio link failure recovery.
[00183] Example 42. The apparatus according to any one of examples 32 to 39, wherein:
[00184] the set of resources are a first set of time-domain resources;
[00185] the information comprises a time-domain mask indicating the first set of timedomain resources and a second set of time-domain resources where radio link quality monitoring is to be performed; and
[00186] the means are further configured to perform autonomously activating by the user equipment use of the time-domain mask for radio link monitoring purposes in response to the user equipment detecting that radio link quality in one of the first or second set of resources is significantly worse than radio link quality in another of the first or second set of resources.
[00187] Example 43. The apparatus according to any one of examples 32 to 42, wherein the means are further configured to perform receiving an indication, by the user equipment from the network node, indicating n previous radio link quality monitoring measurements, n
Figure imgf000031_0001
1, are to be considered to be invalid, and wherein the means are further configured to perform adjusting by the user equipment a counter for radio link monitoring by subtracting n from the counter.
[00188] Example 44. The apparatus of any preceding apparatus example, wherein the means comprises:
[00189] at least one processor; and
[00190] at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
[00191] Example 45. An apparatus, comprising:
[00192] one or more processors; and
[00193] one or more memories including computer program code,
[00194] wherein the one or more memories and the computer program code are configured, with the one or more processors, to cause the apparatus to:
[00195] for a network node serving a user equipment in a wireless system, identify by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and
[00196] send, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
[00197] Example 46. An apparatus, comprising:
[00198] one or more processors; and
[00199] one or more memories including computer program code,
[00200] wherein the one or more memories and the computer program code are configured, with the one or more processors, to cause the apparatus to:
[00201] for a user equipment being served by a network node in a wireless system, receive information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment; and
[00202] for the set of resources, not perform by the user equipment radio link quality monitoring in those resources. [00203] As used in this application, the term “circuitry” may refer to one or more or all of the following:
[00204] (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and
[00205] (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and
[00206] (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[00207] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[00208] Embodiments herein may be implemented in software (executed by one or more processors), hardware (e.g., an application specific integrated circuit), or a combination of software and hardware. In an example embodiment, the software (e.g., application logic, an instruction set) is maintained on any one of various conventional computer-readable media. In the context of this document, a “computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer, with one example of a computer described and depicted, e.g., in FIG. 1. A computer-readable medium may comprise a computer-readable storage medium (e.g., memories 125, 155, 171 or other device) that may be any media or means that can contain, store, and/or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. A computer-readable storage medium does not comprise propagating signals.
[00209] If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined.
[00210] Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.
[00211] It is also noted herein that while the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.
[00212] The following abbreviations that may be found in the specification and/or the drawing figures are defined as follows:
[00213] 3GPP third generation partnership project
[00214] 5G fifth generation
[00215] 5GC 5G core network
[00216] AMF access and mobility management function
[00217] BFD beam failure detection
[00218] BFR beam failure recovery
[00219] BWP bandwidth part
[00220] CLI cross-link-interference
[00221] CSI-RS channel state information-reference signal
[00222] CU central unit
[00223] DL downlink
[00224] DU distributed unit
[00225] eNB (or eNodeB) evolved Node B (e.g., an LTE base station)
[00226] EN-DC E-UTRA-NR dual connectivity [00227] en-gNB or En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as secondary node in EN-DC
[00228] E-UTRA evolved universal terrestrial radio access, i.e., the LTE radio access technology
[00229] gNB (or gNodeB) base station for 5G/NR, i.e., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC
[00230] IE information element
[00231] PF interface
[00232] LTE long term evolution
[00233] MAC medium access control
[00234] MAC CE MAC control element
[00235] MME mobility management entity
[00236] ng or NG next generation
[00237] ng-eNB or NG-eNB next generation eNB
[00238] NR new radio
[00239] N/W or NW network
[00240] PDCP packet data convergence protocol
[00241] PHY physical layer
[00242] RAN radio access network
[00243] Rel release
[00244] RLC radio link control
[00245] RLF radio link failure
[00246] RLM radio link monitoring
[00247] RRH remote radio head
[00248] RRC radio resource control
[00249] RS reference signal
[00250] RSRP Reference Signal Received Power [00251] RU radio unit
[00252] Rx receiver
[00253] SBFD subband non-overlapping full duplex
[00254] SDAP service data adaptation protocol
[00255] SGW serving gateway
[00256] SINR Signal to Interference plus Noise Ratio
[00257] SMF session management function
[00258] SRS Sounding Reference Signal
[00259] SSB synchronization signal block
[00260] TDD time-division duplexing
[00261] TS technical specification
[00262] Tx transmitter
[00263] UE user equipment (e.g., a wireless, typically mobile device)
[00264] UL uplink
[00265] UPF user plane function

Claims

CLAIMS What is claimed is:
1. A method, comprising: for a network node serving a user equipment in a wireless system, identifying by the network node that a set of resources is potentially subject to cross-link- interference affecting the user equipment; and sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment.
2. The method according to claim 1, wherein the identifying comprises determining that the set of resources is potentially subject to cross-link-interference high enough to impair reception by the user equipment.
3. The method according one of claims 1 to 2, wherein the identifying determines the set of resources as resources with cross-link-interference where the network node uses a transmission direction that is different from that of a neighboring network node, and wherein the sending comprises sending information identifying the set of resources where the network node uses a transmission direction that is different from that of a neighboring network node.
4. The method according one of claims 1 to 2, wherein the identifying utilizes user equipment cross-link interference measurements to determine if a user equipment is subject to cross-link interference levels above a threshold for downlink reception, and wherein the sending comprises sending information identifying the cross-link interference resources where the user equipment cross-link interference measurements indicate cross-link interference levels above the threshold for downlink reception. The method according one of claims 1 to 4, further comprising the network node not scheduling selected user equipment for reception during the set of recourses. The method according to any one of claims 1 to 5, wherein the set of resources comprise either slots or symbols. The method according to any one of claims 1 to 6, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring. The method according to any one of claims 1 to 6, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms. A method, comprising: for a user equipment being served by a network node in a wireless system, receiving information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment; and for the set of resources, not performing by the user equipment radio link quality monitoring in those resources. The method according to claim 9, further comprising not advancing by the user equipment a timer that is started after indication of radio problems during times of the set of resources. The method according to one of claims 9 or 10, further comprising monitoring by the user equipment downlink radio link quality based on a reference signal configured by the network node as one or more radio link monitoring-reference signal resource(s) in the set of resources in order to detect the downlink radio link quality and compare the measured downlink radio link quality with one or more thresholds to determine downlink radio link quality. The method according to one of claims 9 to 11, further comprising starting by the user equipment a timer, to be started after indication of radio problems, in response to detecting physical layer radio link monitoring problems, but stopping the timer for periods of the set of resources. The method according to one of claims 9 to 12, further comprising not counting by the user equipment random access attempts sent during the set of resources for radio link monitoring or radio link failure or beam failure detection purposes. The method according to one of claims 9 to 12, further comprising omitting by the user equipment radio link monitoring or radio link failure or beam failure detection triggering during the set of resources. The method according to any one of claims 9 to 14, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring. The method according to any one of claims 9 to 14, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms. The method according to any one of claims 9 to 16, further comprising the user equipment receiving configuration from the network node to only perform radio link quality monitoring on downlink-only resources and wherein the set of resources are subband non-overlapping full-duplex resources. The method according to any one of claims 9 to 16, wherein: the set of resources is a first set of time-domain resources; the information comprises a time-domain mask indicating the first set of time-domain resources and a second set of time-domain resources where radio link quality monitoring is to be performed; the method comprises: performing by the user equipment separate radio link monitoring procedures using different radio link monitoring configurations in different subsets of the first and second time-domain resources; in response to detecting radio link monitoring on the first set of time-domain resources, suspending by the user equipment performing radio link monitoring on the first set of resources; and in response to detecting radio link monitoring on the second set of time-domain resources, triggering by the user equipment a procedure for radio link failure recovery. The method according to any one of claims 9 to 16, wherein: the set of resources are a first set of time-domain resources; the information comprises a time-domain mask indicating the first set of time-domain resources and a second set of time-domain resources where radio link quality monitoring is to be performed; and the method comprises autonomously activating by the user equipment use of the timedomain mask for radio link monitoring purposes in response to the user equipment detecting that radio link quality in one of the first or second set of resources is significantly worse than radio link quality in another of the first or second set of resources. The method according to any one of claims 9 to 19, further comprising receiving an indication, by the user equipment from the network node, indicating n previous radio link quality monitoring measurements, n > 1, are to be considered to be invalid, and wherein the method further comprises adjusting by the user equipment a counter for radio link monitoring by subtracting n from the counter. A computer program, comprising code for performing the methods of any of claims 1 to
20, when the computer program is run on a computer. The computer program according to claim 21, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with the computer. The computer program according to claim 21, wherein the computer program is directly loadable into an internal memory of the computer. An apparatus, comprising means for performing: for a network node serving a user equipment in a wireless system, identifying by the network node that a set of resources is potentially subject to cross-link- interference affecting the user equipment; and sending, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment. The apparatus according to claim 24, wherein the identifying comprises determining that the set of resources is potentially subject to cross-link-interference high enough to impair reception by the user equipment. The apparatus according one of claims 24 to 25, wherein the identifying determines the set of resources as resources with cross-link-interference where the network node uses a transmission direction that is different from that of a neighboring network node, and wherein the sending comprises sending information identifying the set of resources where the network node uses a transmission direction that is different from that of a neighboring network node. The apparatus according one of claims 24 to 25, wherein the identifying utilizes user equipment cross-link interference measurements to determine if a user equipment is subject to cross-link interference levels above a threshold for downlink reception, and wherein the sending comprises sending information identifying the cross-link interference resources where the user equipment cross-link interference measurements indicate cross-link interference levels above the threshold for downlink reception. The apparatus according one of claims 24 to 27, wherein the means are further configured to perform not scheduling by the network node selected user equipment for reception during the set of recourses. The apparatus according to any one of claims 24 to 28, wherein the set of resources comprise either slots or symbols. The apparatus according to any one of claims 24 to 29, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring. The apparatus according to any one of claims 24 to 29, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms. An apparatus, comprising means for performing: for a user equipment being served by a network node in a wireless system, receiving information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment; and for the set of resources, not performing by the user equipment radio link quality monitoring in those resources. The apparatus according to claim 32, wherein the means are further configured to perform not advancing by the user equipment a timer that is started after indication of radio problems during times of the set of resources. The apparatus according to one of claims 32 or 33, wherein the means are further configured to perform monitoring by the user equipment downlink radio link quality based on a reference signal configured by the network node as one or more radio link monitoring-reference signal resource(s) in the set of resources in order to detect the downlink radio link quality and compare the measured downlink radio link quality with one or more thresholds to determine downlink radio link quality. The apparatus according to one of claims 32 to 34, wherein the means are further configured to perform starting by the user equipment a timer, to be started after indication of radio problems, in response to detecting physical layer radio link monitoring problems, but stopping the timer for periods of the set of resources. The apparatus according to one of claims 32 to 35, wherein the means are further configured to perform not counting by the user equipment random access attempts sent during the set of resources for radio link monitoring or radio link failure or beam failure detection purposes. The apparatus according to one of claims 32 to 35, wherein the means are further configured to perform omitting by the user equipment radio link monitoring or radio link failure or beam failure detection triggering during the set of resources. The apparatus according to any one of claims 32 to 37, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises radio link monitoring. The apparatus according to any one of claims 32 to 37, wherein the set of resources comprise resources for radio link quality monitoring, and wherein radio link quality monitoring comprises beam failure detection mechanisms. The apparatus according to any one of claims 32 to 39, wherein the means are further configured to perform the user equipment receiving configuration from the network node to only perform radio link quality monitoring on downlink-only resources and wherein the set of resources are subband non-overlapping full-duplex resources. The apparatus according to any one of claims 32 to 39, wherein: the set of resources is a first set of time-domain resources; the information comprises a time-domain mask indicating the first set of time-domain resources and a second set of time-domain resources where radio link quality monitoring is to be performed; the means are further configured to perform: performing by the user equipment separate radio link monitoring procedures using different radio link monitoring configurations in different subsets of the first and second time-domain resources; in response to detecting radio link monitoring on the first set of time-domain resources, suspending by the user equipment performing radio link monitoring on the first set of resources; and in response to detecting radio link monitoring on the second set of time-domain resources, triggering by the user equipment a procedure for radio link failure recovery. The apparatus according to any one of claims 32 to 39, wherein: the set of resources are a first set of time-domain resources; the information comprises a time-domain mask indicating the first set of time-domain resources and a second set of time-domain resources where radio link quality monitoring is to be performed; and the means are further configured to perform autonomously activating by the user equipment use of the time-domain mask for radio link monitoring purposes in response to the user equipment detecting that radio link quality in one of the first or second set of resources is significantly worse than radio link quality in another of the first or second set of resources. The apparatus according to any one of claims 32 to 42, wherein the means are further configured to perform receiving an indication, by the user equipment from the network node, indicating n previous radio link quality monitoring measurements, n
Figure imgf000044_0001
1, are to be considered to be invalid, and wherein the means are further configured to perform adjusting by the user equipment a counter for radio link monitoring by subtracting n from the counter. The apparatus of any preceding apparatus claim, wherein the means comprises: at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus. An apparatus, comprising: one or more processors; and one or more memories including computer program code, wherein the one or more memories and the computer program code are configured, with the one or more processors, to cause the apparatus to: for a network node serving a user equipment in a wireless system, identify by the network node that a set of resources is potentially subject to cross-link-interference affecting the user equipment; and send, by the network node toward the user equipment, information indicating the set of resources is potentially subject to cross-link-interference affecting the user equipment. An apparatus, comprising: one or more processors; and one or more memories including computer program code, wherein the one or more memories and the computer program code are configured, with the one or more processors, to cause the apparatus to: for a user equipment being served by a network node in a wireless system, receive information from the network node indicating a set of resources is potentially subject to cross-link-interference affecting the user equipment; and for the set of resources, not perform by the user equipment radio link quality monitoring in those resources.
PCT/US2022/039519 2022-08-05 2022-08-05 Adjusting radio link quality monitoring based on potential cli such as for advanced duplexing cases WO2024030134A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2022/039519 WO2024030134A1 (en) 2022-08-05 2022-08-05 Adjusting radio link quality monitoring based on potential cli such as for advanced duplexing cases

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2022/039519 WO2024030134A1 (en) 2022-08-05 2022-08-05 Adjusting radio link quality monitoring based on potential cli such as for advanced duplexing cases

Publications (1)

Publication Number Publication Date
WO2024030134A1 true WO2024030134A1 (en) 2024-02-08

Family

ID=84359327

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/039519 WO2024030134A1 (en) 2022-08-05 2022-08-05 Adjusting radio link quality monitoring based on potential cli such as for advanced duplexing cases

Country Status (1)

Country Link
WO (1) WO2024030134A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210203466A1 (en) * 2018-06-04 2021-07-01 Nokia Technologies Oy Inter-gnb xn signaling of nr tdd radio frame configuration and cli sensitivity
WO2021217648A1 (en) * 2020-04-30 2021-11-04 Qualcomm Incorporated Cross-link interference (cli) measurements for cli resources

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210203466A1 (en) * 2018-06-04 2021-07-01 Nokia Technologies Oy Inter-gnb xn signaling of nr tdd radio frame configuration and cli sensitivity
WO2021217648A1 (en) * 2020-04-30 2021-11-04 Qualcomm Incorporated Cross-link interference (cli) measurements for cli resources

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.321
K. PEDERSEN ET AL.: "Advancements in 5G New Radio TDD Cross Link Interference Mitigation", IEEE WIRELESS COMMUNICATIONS, vol. 28, no. 4, August 2021 (2021-08-01), pages 106 - 112, XP011877083, DOI: 10.1109/MWC.001.2000376
PEDERSEN KLAUS ET AL: "Advancements in 5G New Radio TDD Cross Link Interference Mitigation", IEEE WIRELESS COMMUNICATIONS, COORDINATED SCIENCE LABORATORY; DEPT. ELECTRICAL AND COMPUTER ENGINEERING; UNIVERSITY OF ILLINOIS AT URBANA-CHAMPAIGN, US, vol. 28, no. 4, 6 April 2021 (2021-04-06), pages 106 - 112, XP011877083, ISSN: 1536-1284, [retrieved on 20210910], DOI: 10.1109/MWC.001.2000376 *

Similar Documents

Publication Publication Date Title
US11259306B2 (en) Utilizing interference measurements in beam recovery procedure
TWI508598B (en) Methods and apparatus for in-device coexistence detection and mitigation
US20240008077A1 (en) Method for sidelink communication and terminal device
US20200221464A1 (en) Techniques To Reduce Interference Between Uplink Channel and Adjacent Channel TDD Transmissions In Wireless Networks
EP3991471B1 (en) Apparatus, system, method and computer-readable medium for performing beam failure recovery
US11956683B2 (en) Robust beam failure recovery using a non-serving cell
JP2021519558A (en) Equipment, methods and computer programs
US20220232611A1 (en) Dynamic Scheduling Offset Adaptation in UE Power Saving
WO2020170218A1 (en) Methods for flexible cli measurement reporting
US20230246764A1 (en) Determining presence of ues having low radio quality and adjusting reference signals for use by these ues
WO2024030134A1 (en) Adjusting radio link quality monitoring based on potential cli such as for advanced duplexing cases
WO2022236557A1 (en) Priority setting for quality of experience
US20230396303A1 (en) Failure Cancellation Recording
CN115053626A (en) Multi-SIM UE assistance information with unavailability time
CN116114303A (en) Serving cell change procedure with multiple candidate target cells
WO2019229292A1 (en) Radio link evaluation for bandwidth parts
US20230042400A1 (en) Temporary Bandwidth Part Switch Suitable for Reduced Capability Device
WO2023082256A1 (en) Fallback behavior for sounding reference signal transmissions
WO2024040401A1 (en) Mechanism for failure detection
US20230412290A1 (en) Dynamic UE Signal Level Correction for Measurement Modification and/or Stationarity Detection
WO2024093052A1 (en) Terminal device and method for sidelink communication
WO2023115424A1 (en) Secondary cell activation and deactivation
US20230058523A1 (en) Reporting preconfigured uplink transmission failures
WO2023208583A1 (en) Ue processing indication for positioning measurement in ue rrc inactive state
WO2023057052A1 (en) Drx with carrier aggregation for telecommunication systems

Legal Events

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

Ref document number: 22803399

Country of ref document: EP

Kind code of ref document: A1