WO2024094624A1

WO2024094624A1 - Methods by wireless device and network node regarding adaptive multi-chain rx activity

Info

Publication number: WO2024094624A1
Application number: PCT/EP2023/080241
Authority: WO
Inventors: Muhammad Ali Kazmi; Venkatarao Gonuguntla; Iana Siomina
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-11-03
Filing date: 2023-10-30
Publication date: 2024-05-10

Abstract

A method and apparatus are disclosed. A wireless device (WD) configured to communicate with a network node is described. The WD is served by a cell associated with the network node and is configured to, and/or comprise a radio interface and/or processing circuitry configured to determine a need to transmit assistance information indicating an activity level desired by the WD related to multi-RX chain operation over a next time period. The need to transmit assistance information is determined based on at least one condition. A method performed by the network node regarding the desired activity level is also disclosed.

Description

METHODS BY WIRELESS DEVICE AND NETWORK NODE REGARDING ADAPTIVE MULTI-CHAIN RX ACTIVITY

FIELD

The present disclosure relates to wireless communications, and in particular, to assistance information associated with adaptive multi-chain receiver activity.

BACKGROUND

The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes (NN), such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

MIMO in NR

One of the building blocks of latest cellar technologies that enables higher data rates is massive multiple input and multiple output (MIMO). The 3 GPP Release 15 (Rel-15) NR describes MIMO features that facilitate utilization of a large number of antenna elements at base station for both sub-6GHz and over-6GHz frequency bands. With the large number of antenna elements supported at a network node (e.g., base station) and WD, both the network node (e.g., gNB) and WD can transmit its data in a certain beam direction, e.g., to achieve better data rate. With massive number of antenna elements supported, the beam can be very narrow. To cover the entire coverage area of the cell, multiple beams may need to be transmitted. This also means that the WD may have to be switched from one beam to other beam when the WD moves from coverage area of one beam to other beam coverage area. A concept called beam management is introduced to handle the support of multiple beams framework.

The beam management framework allows flexibility for the network to instruct the WD to receive signals from several directions and to transmit signals in several directions. In NR, several signals can be transmitted from different antenna ports of a same base station. These signals can have the same large-scale properties such as Doppler shift/spread, average delay spread, or average delay. These antenna ports are then said to be quasi co-located (QCL).

If the WD knows that two antenna ports are QCL with respect to a certain parameter (e.g., Doppler spread), the WD can estimate that parameter based on one of the antenna ports and apply that estimate for receiving signal on the other antenna port.

For example, there may be a QCL relation between a channel state information reference signal (CSI-RS) for tracking RS (TRS) and the physical downlink shared channel (PDSCH) demodulation reference signal (DMRS). When WD receives the PDSCH DMRS, the WD can use the measurements already made on the TRS to assist the DMRS reception.

Information about what assumptions can be made regarding QCL is signaled to the WD from the network node. In NR, four types of QCL relations between a transmitted source RS and transmitted target reference signal (RS) have been defined:

Type A: {Doppler shift, Doppler spread, average delay, delay spread}

Type B: {Doppler shift, Doppler spread}

Type C: {average delay, Doppler shift}

Type D: {Spatial RX parameter}

QCL type D was introduced to facilitate beam management with analog beamforming and is known as spatial QCL. If two transmitted antenna ports are spatially QCL, the WD can use the same receiver (RX) beam to receive them. This is helpful for a WD that uses analog beamforming to receive signals, since the WD needs to adjust its RX beam in some direction prior to receiving a certain signal. If the WD knows that the signal is spatially QCL with some other signal it has received earlier, then it can safely use the same RX beam to receive also this signal.

Each beam may be indicated using something called Transmission Configuration Indicator (TCI) state, and the WD can be configured up to 128 TCI states using RRC configuration. Downlink beam management is performed by conveying spatial QCL (‘Type D’) assumptions to the WD, which are conveyed in TCI states. One TCI state contains one or two RSs, and each RS is associated with a QCL type. An example TCI state information element is as follows:

TCI-State ::= SEQUENCE { tci-Stateld TCI-Stateld, qcl-Typel QCL-Info, qcl-Type2 QCL-Info

QCL-Info ::= SEQUENCE { cell ServCelllndex bwp-Id BWP-Id referencesignal CHOICE { csi-rs NZP-CSI-RS-Resourceld, ssb SSB -Index

}, qcl-Type ENUMERATED {typeA, typeB, typeC, typeD},

}

NR may provide various configuration options for downlink and uplink beam management such as so that the uplink and downlink configurations are independent (e.g., WD can receive from one direction in downlink (DL) in transmit in other direction in uplink (UL)) or they can be configured to follow same spatial relation (e.g., receive in same direction and transmit in same direction).

NR may support beam management for channels and signals in DL and UL. These signals or channels in DL and UL can be received or transmitted from same or different Transmission and Reception Points (TRP).

DL beam management

PDCCH beam management: The NN may configure the WD with a set of physical downlink control channel (PDCCH) TCI states by radio resource control (RRC), and then activates one TCI state per control resource set (CORESET) using medium access control (MAC) control element (CE).

PDSCH beam management: The NN may configure the WD with a set of PDSCH TCI states by RRC and activate up to 8 TCI states by MAC CE. After activation, the NN may dynamically indicate one of these activated TCI states using a TCI field in DCI when scheduling PDSCH.

Alternatively, the NN may simplify the beam management by not setting the RRC parameter tci-PresentlnDCI to enabled, in which case the WD uses the same TCI state for PDSCH as for PDCCH.

Uplink beam management

Uplink beam management may be performed using configuration of spatial relations. A spatial relation is defined at the WD side between a received DL RS (synchronization signal block (SSB) or CSI-RS) or a sounding reference signal (SRS) on one hand and a transmitted PUCCH or an SRS on the other hand. Note that there is not any direct configuration of the spatial relation for a PUSCH: the PUSCH follows the spatial relation of either a PUCCH or an SRS.

PUCCH beam management: For PUCCH, the NN may configure the WD with a set of 8 spatial relations using RRC, and subsequently activate one of these spatial relations using MAC CE. A spatial relation may be defined per PUCCH resource. In 3 GPP Release (Rel-16), changes where made such that spatial relation could be updated for a group of PUCCH resources using a single MAC-CE. In addition, default spatial relation for PUCCH was introduced in Rel-16, such that when no spatial relation is configured/activated for a PUCCH resource, the WD uses the TCI state/QCL assumption of the CORESET with lowest ID, both to derive spatial relation and to derive path loss reference signal.

PUSCH beam management: A PUSCH scheduled by downlink control information (DCI) Format 0 1 is transmitted over the ports where a configured SRS resource may also be transmitted. Either two (codebook-based) or four (non- codebook-based) SRS resources can be defined in the SRS resource set. The NN selects which SRS resource in the set should be used using the SRI field in DCI. The spatial relation for these SRS resources is provided either by RRC (for periodic or aperiodic SRS) or MAC-CE (for aperiodic or semi -persistent SRS). For PUSCH scheduled by DCI Format 0 0, there is no SRS resource indicator (SRI), and the spatial relation instead follows that of a physical uplink control channel (PUCCH) resource. In Rel-16, a default spatial relation for SRS was introduced, such that when no spatial relation is configured/activated for an SRS resource, the WD uses the TCI state/QCL assumption of the CORESET with lowest ID, both to derive spatial relation and to derive path loss reference signal.

SRS beam management: Spatial relations for SRS may be configured by RRC (for periodic and aperiodic) or by MAC CE (aperiodic or semi-persistent).

The above signals or channels may be received/transmitted from/to same or different TRP. A cell may consist of multiple TRP, and they may have same cell ID or different cell ID. If the TRPs of a certain cell have the same physical cell ID (PCI), they are called intra-cell multi-TRP framework, and if the TRPs of a certain cell have multiple PCI, they are called inter-cell multi-TRP framework.

Simultaneous multi-TRP transmission

When the NN supports simultaneous multi-TRP transmission, the data rate that can be achieved depend on whether the WD supports single panel reception or multi-panel reception. When a WD supports only a single panel reception, whether WD can receive simultaneously from different TRP depend on the angle of arrival (AoA) of the different beams transmitted from multi-TRP. If the beam directions from different TRP fall within certain AoA, the WD may receive them at the same time. If not, the WD can receive only one beam at a time. Whereas, if a WD supports multiple panel reception or RX chains, the WD may receive different beam with different AoA. That means, simultaneous multi-TRP transmission with multi-panel reception can enable joint transmission in frequency range 2 (FR2). An example is shown in FIG. 1, where a PDSCH is sent to a WD over two TRPs, with each TRP transmitting 2 layers. In this case, by transmitting PDSCH over two TRPs to the WD, the peak data rate to the WD can be increased as up to 4 aggregated layers from the two TRPs can be received by the WD. Each TRP may be in the same or different NN.

To enable the simultaneous reception from different AoA, the NN has to know which two beams the WD can receive simultaneously. That means, the WD needs to send information about which beams it can receive simultaneously. This is enabled by NN configuring the WD with higher layer parameter groupBasedBeamReporting set to ‘enabled’. When the groupBasedBeamReporting is enabled, depending on the RS configured for reporting, the WD will report either two different CSI-RS resource Index (CRI) or two different SSB resource Index (SSBRI) in a single reporting instance for each report setting. The two CRIs or two SSBRIs may be chosen such that the corresponding CSI-RS and/or SSB resources can be received simultaneously by the WD. The data beam or measurements beam may be QCLed to the CRI or SSBRI reported by the WD.

FIG. 2 shows an example scenario illustrating simultaneous multi-TRP transmission with multi-panel reception at the WD. In this example, NZP CSI-RS resources #1 and #2 are transmitted from TRP1 (NN1), and NZP CSI-RS resources #3 and #4 are transmitted from TRP2 (NN2). The WD may be equipped with two panels.

In the above example, if the WD uses the existing group-based beam reporting in NR (i.e., when groupBasedBeamReporting is enabled), the WD may choose the two CRIs to be reported in one of the following ways:

•Case 1 : both CRIs correspond to TRP1 (e.g., NZP CSI-RS resources #1 and #2 are chosen by the WD)

•Case 2: both CRIs correspond to TRP2 (e.g., NZP CSI-RS resources #3 and #4 are chosen by the WD)

•Case 3 : one CRI corresponds to TRP1, and the other CRI corresponds to TRP2 (e.g., NZP CSI-RS resources #1 and #3)

If the WD reports the two CRIs according to either Case 1 or Case 2, then both beams reported correspond to the same TRP. In Cases 1 and 2, simultaneous multi- TRP transmission is not possible. Case 3 allows simultaneous multi-TRP transmission as the two beams reported correspond to different TRPs.

Hence, the existing group-based beam reporting does not necessarily ensure simultaneous multi-TRP transmission with multi-panel reception. Without simultaneous multi-TRP transmission with multi-panel reception, up to rank4 reception in FR2 may not be attained.

In addition, even if the WD reports two beams that can be received simultaneously by the WD and where each beam is associated with different TRPs, both beams might be received with the same WD panel (and same spatial filter). Since each WD panel typically supports up to two DL layers, in this case, even though the two reported beams are associated to different TRPs, joint transmission (JT) up to 4 layers might not be possible.

In 3 GPP Release 17 (Rel-17) group-based beam reporting, the WD can be configured to report in a single CSI-report N beam groups (where N is RRC configured and can be up to Nmax, where Nmax={ 1,2, 3, 4} is a WD capability), where each beam group consists of two beams (i.e. 2 SSBRI/CRI values and corresponding Ll-RSRP), and where the two beams can be received simultaneously by the WD. To make sure that each beam in a beam group is associated to different TRPs, the WD can be configured with two channel measurement resource (CMR) sets, where each CMR set is associated to one TRP, and where the WD selects one CMR from each CMR set in each beam group. For periodic /semi -persistent CMRs, two CMR resource sets are configured per periodic/semi-persistent CMR resource setting. For aperiodic CMR, the existing RRC parameter CSI- AssociatedReportConfiglnfo is extended to be configured with two CMR resource sets.

When the NN (e.g., gNB) may configure the WD to report Rel-17 group- based beam reporting, an example supported report format is shown in Table 7 [TS 38.212 vl7.2.0]. In the table, the 1 -bit Resource set indicator, is used to indicate if the strongest beam (i.e., CRI or SSBRI #1 of 1st resource group) belongs to the 1st or the 2nd CMR set. Absolute RSRP (7 bits) may be reported for the strongest beam, and differential RSRP (4 bits) is reported for the remaining beams. The bit width of each SSBRI/CRI is determined based on the number of SSB/CSI-RS resources in the associated CMR resource set.

Table 1.- Supported report format of Rel-17 group-based beam reporting

1.1.1 Multi-RX chain reception

In order to enhance the data rate/throughput, the WD can be configured to receive data using different beams of signals (e.g., PDSCH) from different directions on the same carrier frequency. This requires the WD to implement at least two receiver (RX) chains. The RX chain may refer to a combination of radio frequency (RF) component (e.g., low noise amplifier, RX antenna panel, RX beams, etc.) and/or baseband resources (e.g., memory, processor, etc.). The simultaneous reception of the signals by the WD from different directions (e.g., from two physically separated TRPs) may require the WD to support multiple independent RX chains. For example, the multi-RX chain capable WD may support multiple receive antenna panels (or simply panels). The multi-RX chain operation may enable the WD to simultaneously receive data (e.g., PDSCH) from multiple TRPs, which are non-collocated, i.e., at different physical sites. The multi-RX chain capable WD can also use its capability of simultaneous multi-panel operation to enhance radio measurements. For example, the WD can simultaneously perform the RX beam sweeping in two or more directions using independent set of RX beams where each set is created by one panel.

The simultaneous reception of multiple signals (e.g., two or more PDSCHs, reference signals, etc.) by the FR2 WD supporting multi-RX chain capability may enhance the user and system performance (e.g., increases data rate). Furthermore, in FR2, the mandatory WD channel BW is 200 MHz per carrier frequency and some WDs may support much larger BW e.g., 400-800 MHz. The FR2 WD is typically configured to operate over 100-200 MHz BW. Therefore, multi-RX chain operation in FR2 can lead to manifold increase in the data rate.

SUMMARY

Some embodiments advantageously provide methods, systems, and apparatuses for determining assistance information associated with adaptive multichain RX activity, e.g., under overheating. Some embodiments, a method in a WD is described. In some other embodiments, a method in a NN is described.

The multi-RX chain operation also requires very intense processing at the WD. This may drain WD battery power and/or may increase the heat dissipation inside the WD transceiver circuity. In the short run, if the WD is persistently overheated, it will degrade the WD performance (e.g., lower throughput) and/or may significantly or swiftly drain the WD battery. In the long run the persistent overheating may permanently impair partially or fully certain parts of the WD transceiver circuity.

According to a first embodiment, a WD served by at least first cell (Celli), determines a need to transmit an assistance information indicating an activity level with which the WD can perform multi-RX chain operation in a cell (e.g., Celli and/or on another cell) over the next certain time period (Tl) and/or transmits the assistance information to a first network node (NN1).

According to a second embodiment, a first network node (NN1) receives from a WD, which is served by a first cell (Celli), an assistance information indicating an activity level with which the WD can perform multi-RX chain operation over the next certain time period (Tl) and/or uses the received assistance information for performing one or more operational tasks.

The WD activity level indicated in the assistance information may be expressed in terms of a periodic or aperiodic pattern of two states: state 1 (SI) in which the WD can perform multi-RX chain operation with higher activity and state 2 (S2) in which the WD can perform multi-RX chain operation with lower activity. The lower activity may also be called as no activity. For example, in SI, the WD can perform the multi-RX chain operation using M number of RX chains, and in S2, the WD can perform the multi-RX chain operation using N number of RX chains; where M > N and M > 2 and N >1. In one example, M=2 and N=0.

The multi-RX chain operation comprises WD receiving signals (e.g., RS, data signals such as PDSCH, etc.) using at least two RX chains during at least partially overlapping time. The multi-RX chain operation may also be called as multi-panel operation, e.g., receiving at least two beams simultaneously (over at least partially overlapping time) from different spatial directions (e.g., from two different radio nodes which are non-collocated).

In some embodiments, Therefore, the WD may indicate to the network node if reported beams (e.g., two reported beams) are associated with the same or different WD panels (e.g., since then the network node may get information if JT is likely to work or not).

In one or more embodiments, the WD may be configured to dynamically or semi-statically indicate to the network node to adapt/reduce the activity level with which the WD can be scheduled/served in multi-RX operational scenario.

One or more embodiments provide a process (e.g., mechanism) which is beneficial at least because the process:

• allows the WD to conserve or save its battery power.

• allows the WD to lower its heat dissipation preventing overheating of the device. This in turn enhances average performance in terms of user data rate.

• prevents the degradation or damage of the device hardware due to overheating. BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

FIG. 1 shows an example joint transmission using simultaneous multi-TRP transmission with multi-panel reception;

FIG. 2 shows an example simultaneous multi-TRP transmission with multipanel reception;

FIG. 3 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 4 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure; FIG. 9 is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure;

FIG. 10 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

FIG. 11 shows example assistance information indicating a periodic pattern comprising of two activity states for multi -receiver chain operation during a predetermined time according to some embodiments of the present disclosure;

FIG. 12 shows example assistance information indicating an aperiodic pattern comprising of two activity states for multi -receiver chain operation during a predetermined time according to some embodiments of the present disclosure; and

FIG. 13 shows example assistance information indicating an aperiodic pattern comprising of two activity states with transition time for multi -receiver chain operation during a predetermined time according to some embodiments of the present disclosure; and

FIG. 14 shows example of assistance information indicating pattern comprising of two activity states for multi-receiver chain operation in terms of maximum duty cycle of the first state and/or minimum duty cycle of the second state during a predetermined time according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to determining assistance information associated with adaptive multi-chain RX activity, e.g., under overheating. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. 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,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate, and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of a radio network node, base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), network controller, radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) node, central unit (e.g., in a gNB), distributed unit (e.g., in a gNB), baseband unit, centralized baseband, C- RAN, transmission reception point (TRP), multi -standard radio (MSR) radio node such as MSR BS, multi -cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile switching center (MSC), mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), operation and management (O&M), operation support system (OSS), self-organizing network (SON), positioning node, an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD), and/or in a cellular or mobile communication system. The WD may also be a radio communication device, mobile device, target device, device to device (D2D) WD, vehicular to vehicular (V2V) WD, machine type WD or WD capable of machine to machine communication (M2M), machine type communication (MTC) WD, low-cost and/or low-complexity WD, a sensor equipped with WD, personal digital assistant (PDA), tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

The term signal or radio signal used herein can be any physical signal or physical channel. Examples of downlink (DL) physical signals are reference signal such as a synchronization signal (SS) primary SS (PSS), secondary SS (SSS), channel state information reference signal (CSLRS), demodulation reference signal (DMRS), signals in synchronization signal block (SSB), discovery reference signal (DRS), cell specific reference signal (CRS), positioning signal, positioning reference signal (PRS), radio link monitoring reference signal (RLM-RS), beam management signals, beam management reference signal (BM-RS), BFD-RS, tracking signal, tracking reference signal (TRS), etc. Examples of uplink (UL) physical signals are reference signal such as sounding reference signal (SRS), DMRS, etc. The term physical channel may refer to any channel carrying higher layer information, e.g., data, control, etc. Examples of physical channels are physical broadcast channel (PBCH), physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), narrowband p PBCH (NPBCH), physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), short physical uplink control channel (sPUCCH), short PDSCH (sPDSCH), short PUCCH (sPUCCH), short physical uplink shared channel (sPUSCH), MTC physical downlink control channel (MPDCCH), narrow band physical downlink control channel (NPDCCH), narrow band PDSCH (NPDSCH), E-PDCCH, narrow band PUSCH (NPUSCH), etc.

The term “measurements” or “radio measurements” herein may comprise any one or combination of: radio resource management (RRM) measurement (e.g., received signal strength, Reference Signal Received Power (RSRP), PRS received power (PRP), received signal quality, reference signal based reference signal received quality (RSRQ), Signal to Noise and Interference Ratio (SINR), radio signal strength indication (RSSI), etc.), positioning measurement, channel state or quality measurement or estimation (rank indication or RI, CSI, etc.), radio link evaluation or monitoring (RLM), beam evaluation or beam management, beam failure detection (BFD), candidate beam detection (CBD), signal detection, synchronization, LI measurement, L3 measurement, etc.

The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are: symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, sub-slot, mini-slot, system frame number (SFN) cycle, hyper SFN (H-SFN) cycle, time-frequency resource, resource element (RE), etc.

The terms “multi-RX chain” comprises of at least two receiver (RX) chains in the WD. The term RX chain may comprise any one or more set of resources: baseband resources, memory resources, radio frequency (RF) resources (e.g., LNA, PA, antenna part, antenna panel, antenna module, etc.). For example, dual-RX chain may comprise of two antenna panels (or simply panels) or two antenna modules. The antenna panel may further comprise of two or more antenna elements, which in turn may allow the WD to create a receive beam to receive a beam of signal. The term multi-RX chain may also be called as multi-chain receiver, multi-beam receiver, multi-panel, multi-TCI, etc. The multi-RX chain operation may refer to WD receiving signals (e.g., RS, data, etc.) by at least two RX chains simultaneously, e.g., over fully or partially overlapping time. A special case of multi-RX chain comprises dual-RX chain, which may also be called as dual-panel, dual-beam receiver, dual-TCI, etc.

Note that although terminology from one particular wireless system, such as, for example, 3 GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 3 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

The communication system of FIG. 3 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A network node 16 is configured to include a NN management unit 32 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., receiving assistance information and performing one or more actions based on the received assistance information. A wireless device 22 is configured to include a WD management unit 34 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., determine a need to transmit assistance information and/or transmitting the assistance information.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 2. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a host management unit 54 configured to enable the service provider to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., observe/monitor/ control/transmit to/receive from the network node 16 and/or the wireless device 22.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may include one or more antennas 76. Radio interface 62 (and/or antennas 76) may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry/Circuits) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include NN management unit 32 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., receiving assistance information and performing one or more actions based on the received assistance information.

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 include one or more antennas 83. Radio interface 82 (and/or antennas 83) may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a WD management unit 34 which is configured to perform any step and/or task and/or process and/or method and/or feature described in the present disclosure, e.g., determine a need to transmit assistance information and/or transmitting the assistance information. In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 3.

In FIG. 4, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing and/or initiating and/or maintaining and/or supporting and/or ending a transmission to the WD 22, and/or preparing and/or terminating and/or maintaining and/or supporting and/or ending in receipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 3 and 4 show various “units” such as NN management unit 32, and WD management unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

FIG. 5 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 3 and 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 4. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

FIG. 6 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

FIG. 7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

FIG. 9 is a flowchart of an example process in a wireless device 22 according to some embodiments. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the WD management unit 34), processor 86, radio interface 82 and/or communication interface 60. Wireless device 22 such as via processing circuitry 84 and/or processor 86 and/or radio interface 82 is configured to determine (Block S134) a need to transmit assistance information indicating an activity level usable by the WD to perform a multi -receiver chain operation in the cell over a predetermined time, the need to transmit assistance information being determined based on at least one condition; and transmit (Block S136) the assistance information to the network node based on the determined need.

In some embodiments, the activity level is based on a periodic pattern and/or an aperiodic pattern of a first state (e.g., SI) and a second state (e.g., S2). The first state corresponds to the WD 22 being capable of performing the multi -receiver chain operation using a first predetermined activity, and the second state corresponds to the WD 22 being capable of performing the multi -receiver chain operation using a second predetermined activity.

In some other embodiments, the multi -receiver chain operation comprises at least one of the WD 22 receiving one or more signals using at least two receiver chains during at least partially overlapping times; and a multi-panel operation, the multi-panel operation comprising simultaneously receiving at least two beams during at least partially overlapping times from different spatial directions.

FIG. 10 is a flowchart of an example process in a network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the NN management unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to receive (Block S138) assistance information indicating an activity level usable by the WD 22 to perform a multi-receiver chain operation in the cell over a predetermined time; and perform (Block S140) at least one action based on the received assistance information.

In some embodiments, the activity level is based on a periodic pattern and/or an aperiodic pattern of a first state (e.g., SI) and a second state (e.g., S2). The first state corresponds to the WD 22 being capable of performing the multi -receiver chain operation using a first predetermined activity, and the second state corresponds to the WD 22 being capable of performing the multi -receiver chain operation using a second predetermined activity. In some other embodiments, the multi -receiver chain operation comprises at least one of the WD 22 receiving one or more signals using at least two receiver chains during at least partially overlapping times; and a multi-panel operation, the multi-panel operation comprising simultaneously receiving at least two beams during at least partially overlapping times from different spatial directions.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for determining assistance information associated with adaptive multi-chain RX activity.

Scenario description

In some embodiments, a scenario comprises a WD 22 served by at least a first cell (Celli) which is managed or served by a first network node 16 (NN1) (e.g., base station). The WD 22 may also be served by more than one cell (e.g., cell 1 , a second (Cell2), etc.) in multicarrier operation such as in carrier aggregation (CA), multiconnectivity, dual connectivity (DC), etc. Examples of serving cells are special cell (SpCell), secondary cell (SCell), etc. Examples of sPCell are PCell, PSCell, etc. For example, Celli and Cell2 may operate on a first carrier frequency (Fl) and on a second carrier frequency (F2) respectively.

The term carrier frequency is also called as component carrier (CC), frequency layer, layer, carrier, frequency, serving carrier, frequency channel, positioning frequency layer (PFL), etc. The carrier frequency belongs to certain frequency band, which may contain one or multiple carrier frequencies based on its passband (e.g., size of the band in frequency domain) and/or bandwidth of the carriers and/or the channel raster, etc. The carrier frequency related information is transmitted to the WD 22 by a network node 16 using a channel number or identifier via message, e.g., RRC. Examples of the channel number or identifier, which may be pre-defined, are absolute radio frequency channel number (ARFCN), NR-ARFCN, etc.

The carrier frequencies on which the WD 22 is configured to receive signals (e.g., PDSCH, SSB, CSI.RS, etc.) may belong to certain frequency range (FR). Examples of FR are within frequency range 1 (FR1), within frequency range 2 (FR2), within frequency range 3 (FR3), etc. In one example, frequencies within FR2 are frequencies above certain threshold e.g., 24 GHz or higher. In another example, the frequencies in FR2 may vary between 24 GHz to 52.6 GHz. In another example, frequencies in FR2 may vary between 24 GHz to 71 GHz. Frequencies in FR1 are below the frequencies in FR2. In one example, frequencies in FR1 range between 410 MHz and 7125 MHz. In higher frequencies (e.g., mmwave, FR2, FR3, etc.) due to higher signal dispersion, the transmitted signals are beamformed by a base station, e.g., transmitted in terms of SSB beams. The beam based transmission and/or reception may also be used in lower frequencies, e.g., in FR1. The WD 22 creates a receive (RX) beam at its receiver to receive the signal (e.g., PRS, SSB, CSI-RS, etc.). A DL RS (e.g., PRS, SSB, CSI-RS, etc.) may therefore interchangeably be called as a DL beam, spatial filter, spatial domain transmission filter, main lobe of the radiation pattern of antenna array, etc. The term beam used herein may refer to RS such as PRS, SSB, CSI-RS, etc. The RS or beams may be addressed or configured by an identifier, which can indicate the location of the beam in time in beam pattern, e.g., beam index such as SSB index indicate SSB beam location in the pre-defined SSB format/pattem, beam index such as CSI-RS index indicate CSI-RS beam location in the pre-defined or pre-configured CSI-RS format/pattern, etc. The measurement on such RS may also be called as beam measurement or beam based measurement. The WD 22 may also combine two or more beam measurements to obtain a combine or overall measurement result. Beamforming or spatial filtering is a signal processing technique used in radio communications for directional signal transmission (transmit beamforming) or reception (receive beamforming). Further, there can be narrow beams and/or wide beams.

Embodiment 1: Method in a WD of determining and transmitting multi-RX chain assistance information to a network node

According to a first embodiment, a WD 22 served by at least a first cell (Celli):

• determines a need to transmit an assistance information indicating an activity level with which the WD 22 can perform multi-RX chain operation in a cell (e.g., Celli and/or on another cell) over the next certain time period (Tl); and/or

• transmits the assistance information to a first network node 16 (NN1). In some examples, the WD 22 may determine the need to transmit the assistance information during or due to the multi-RX chain operation. WD 22 may determine the need to transmit the assistance information before multi-RX chain operation, e.g., to reduce its other activities and hereby enabling its multi-RX chain operation.

The WD 22 may determine the need to transmit the assistance information based on one or more triggering conditions or criteria. Examples of the triggering conditions are:

1. In one example, the triggering condition comprises receiving a configuration message from a network node 16 (e.g., NN1) such as using RRC, MAC-CE or DCI command/message. The configuration message allows or permits the WD 22 to transmit the assistance information to the network node 16. In one example, it may be up to the WD implementation whether to transmit the assistance information to the network node 16. In another example, the WD 22 may be required or is expected to transmit the assistance information to the network node 16. In one example, the configuration message may also require the WD 22 to transmit the assistance information to the network node 16 within certain time period starting from a reference time (Tr), e.g., Tr can be the time the WD 22 has received the configuration message. In this case the WD 22 may start a timer at Tr and can transmit the assistance information to the network node 16 until the timer is running. In another example, the configuration message may allow the WD 22 to transmit the assistance information to the network node 16 until another message (e.g., for disabling the assistance information) is received by the WD 22 from the network node 16. The configuration message may also be called as setup/release message, enable/disable message, etc.

2. In one example, the triggering condition comprises receiving an indication from the internal circuitry of the WD 22 (e.g., from WD’s lower layers such as physical layer, RF circuitry, baseband unit). Examples are: o For example, the WD’s internal circuitry (e.g., processing circuitry) may detect overheating or is expected to detect overheating over the next certain time period. The WDs internal circuitry may request the WD higher layer to transmit (e.g., via radio interface 82) the assistance information to the network node 16.

■ In one example, the overheating is detected by the WD 22 if the temperature of one or more hardware components (e.g., LNA, power amplifier, processor, etc.) of the WD 22 is above certain threshold over certain time period (e.g., XI 1 number of slots, X12 seconds, etc.).

■ In another example, the overheating is detected by the WD 22 if the total amount of the heat dissipated by the WD 22 over the last certain time period is above certain threshold.

■ In another example, the overheating is detected by the WD 22 if the WD 22 has been operating with more than certain number of RX chains (e.g., 2 or more) over a time period which is above certain threshold. The threshold may further depend on the number of RX chains, e.g., lower threshold (faster triggering) with more RX chains.

■ In another example, to prevent the overheating, the trigger condition may be triggered as a periodic event if WD 22 is operating with multiple RX chains (e.g., 2 or more). That means WD 22 may trigger the overheating once every XI 1 slots or X12 ms, or X13 seconds, if WD 22 is operating with multi-RX chain.

■ In another example, if WD 22 observe problem over a RX chain (e.g., out of sync or beam failure), to save battery power it may trigger overheating indication.

■ In another example, the overheating is detected in by the WD 22 when the total amount of WD operational activities of certain types over a certain time period exceeds a threshold. In another example, the WD’s battery life is below certain threshold or is expected to fall below certain threshold. This in turn may triggers the WD’s higher layer to transmit the assistance information to the network node 16.

The WD 22 may transmits the assistance information to the network node 16 (e.g., NN1) using one or more signaling such as radio resource control (RRC), medium access control (MAC) control element (CE), downlink control information DCI command/message.

Examples of multi-RX operational activity assistance information:

The WD 22 may determine the desired activity level of the multi-RX operation which can allow the WD 22 to revert to a normal operation (e.g., overheating is prevented, WD 22 temperature falls within an acceptable range, battery power falls at a rate lower than certain threshold, etc.). The activity level of the multi- RX operation, which may also simply be called as “multi-RX operational activity” can be determined based on one or more rules. The rules can be pre-defined, autonomously determined by the WD 22 or configured by the network node 16. The WD 22 transmits the multi-RX operational activity assistance information to the network node 16 based on one or more rules. If at least two rules exist then in one example, the WD 22 autonomously selects the rule and multi-RX operational activity assistance information to the network node 16 based on the selected rule. In another example, the WD 22 can be configured by the network node 16 (e.g., in the configuration message) to select one of the plurality of the rules for transmitting the multi-RX operational activity assistance information to the network node 16. The rules are described below with examples.

1. According to a general principle of the rule, the multi-RX operational activity comprises of a pattern of at least two activity states: State # 1 (SI) and State # 2 (S2). The pattern of SI and S2 may be applicable for a certain time period. The pattern starts at a reference time (Tr) and ends at ending time (Te). The parameters Tr and Te may be pre-defined, indicated by the WD 22 in the assistance information or configured by the network node 16 (e.g., in the configuration message, etc.). In one example, Tr and/or Te may be expressed in a universal or global time such as UTC time. In another example, Tr and/or Te may be expressed in one or more cell or network related timing parameters e.g., hyper SFN number # X21, SFN number # X22, subframe number # X23, slot number # X24, symbol number # X25, etc. In another example, Tr is the time instance when the WD 22 has transmitted the assistance information to the network node 16 or when the network node 16 has received the assistance information from the WD 22. In another example, Te is the time instance when the WD 22 has received a configuration message from the network node 16 indicating the release of the assistance information e.g., after which the WD 22 cannot transmit the assistance information. The WD 22 during the state, SI, can operate up to M number of RX chains. The WD 22 during the state, S2, can operate up to N number of RX chains. Where M > 2 and N > 0; and M > N. Therefore, the WD 22 can operate signals using larger number of RX chains while in state, SI, compared to being in state, S2. In one specific example, M=2 and N=0. In another specific example, M=2 and N=l. In one example, M may correspond to the maximum number of the RX chains supported by the WD 2, e.g., according to the WD capability. In another example, M may correspond to the number of the RX chains smaller than those supported by the WD 22. The pattern of SI and S2 may be indicated by the WD 22 as part of the assistance information for one or more serving cells and/or for certain type of the operations as described below: a. In one example, the same pattern of SI and S2 may be indicated by the WD 22 for all the serving cells of the WD 22, e.g., for Celli, Cell2, etc. b. In another example, the pattern of SI and S2 may be indicated by the WD 22 for a group of serving cells of the WD 22. The group may comprise one or more serving cells e.g., for only Celli, for only Cell2 or for both Celli and Cell2, etc. c. In another example, the pattern of SI and S2 may be indicated by the WD 22 for all types of the operations applicable for the multi- RX chain. For example, by default the pattern may apply for all types of operations performed using the multi -RX chain e.g., predefined, for which the requirements are defined, etc. Examples of operations are reception of signals related to data, link recovery procedure (LRP), radio link monitoring (RLM), LI measurement (e.g., Ll-RSRP, Ll-SINR, etc.), layer 3 measurements (e.g., cell search, RSRP, RSRQ, SINR, SSB index acquisition, etc.), etc. Examples of reception of signals related to the data are data channel reception (e.g., PDSCH reception), control channel reception (e.g., PDCCH reception), etc. Examples of link recovery procedure are beam failure detection (BFD), candidate beam detection (CBM), etc. Examples of procedures involving or part of RLM are out of sync (OOS) detection, in-sync (IS) detection, radio link failure, etc. d. In another example, the pattern of SI and S2 may be indicated by the WD 22 for one or more types of operations. For example, the WD 22 may indicate in the assistance information that the pattern is applicable for the reception of the data signals. In another example, the WD 22 may indicate in the assistance information that the pattern is applicable for the reception of the data signals and link recovery procedure. In another example, the WD 22 may indicate in the assistance information that the pattern is applicable for the reception of the data signals, link recovery procedure and RLM. According to one specific example of the rule, the multi-RX operational activity comprises of a periodic pattern of the at least two activity states, SI and S2, e.g., any one of FIGS. 11-14. The two states (SI and S2) occur periodically with certain period (Tp). The figure also shows the pattern starts at Tr and ends at Te. The time duration of each state may be the same or they may be different. The duration of one or both states can be pre-defined or configured by the network node 16 or indicated by the WD 22 in the assistance information. An example of the periodic pattern is shown in figure 4. As described in the general principle, during SI and S2 the WD 22 can operate using M number of RX chains and N number of RX chains respectively. In one specific example, during SI, the WD 22 can operate signals (e.g., receive signals) using all its RX chains, and during S2, the WD 22 cannot operate signals using any of its RX chains. This may be called as a periodic ON-OFF pattern. The assistance information may further indicate that the WD 22 can perform reception of 2-layer or 4-layer transmission using up to N number of RX chains (e.g., N=l) i.e. according to S2. The assistance information may further indicate that the WD 22 can perform one or more layer- 1 measurements using up to N number of RX chains (e.g., N=l) i.e. according to S2. Examples of layer-1 measurements (or types of LI -measurements) are measurements related to the LRP (e.g, BFD, CBD, etc ), RLM (e g., OOC, IS, etc ), Ll- RSRP/L1-SINR, TCI switching, etc. The assistance information may further indicate that the WD 22 can perform one or more layer- 1 measurements according to relaxed measurement procedures. During the relaxed measurement procedure, the WD 22 performs a measurement over long measurement time (Trm) compared to the measurement time (Tnm) of the same type of the measurement performed according to the nonrelaxed measurement procedure (i.e. normal procedure). For example, Trm > Tnm. In one example, Trm = K*Tnm. Examples of the measurement time are BFD evaluation period, CBD evaluation period, OOS evaluation period, IS evaluation period, L1-RSRP/L1-SINR measurement period, TCI switching delay/time period, etc. FIG. 11 shows example assistance information indicating a periodic pattern comprising of two activity states for multi-receiver chain operation during a predetermined time. According to another specific example of the rule, the multi -RX operational activity indicate that the WD 22 should operate in state, S2, starting from time instance, Tr and until the time instance, Te. After Te the WD 22 can revert to the normal operation i.e. can operate using M number of the RX chains. This example of the rule is shown in FIG. 12 (showing example assistance information indicating an aperiodic pattern comprising of two activity states for multi -receiver chain operation during a predetermined time). The assistance information may further indicate that the WD 22 can perform one or more layer- 1 measurements (as described in rule 2) using up to N number of RX chains (e.g., N=l), i.e., according to S2. The assistance information may further indicate that the WD 22 can perform one or more layer- 1 measurements according to relaxed measurement procedures (as described in rule 2).

4. According to another specific example of the rule, the multi-RX operational activity indicate that the WD 22 should operate in state, S2, starting from time instance, Ts and until the time instance, Te. The WD 22 can also operate in state, SI, between time instances Tr and Ts. The duration (Ts-Tr) may be termed as the transition period. The difference with the previous pattern is that this pattern enables the reception of signals with M number of RX chains during the transition period. Therefore, the necessary data (e.g., retransmissions, critical signals, etc.) can be transmitted to the WD 22 before the WD 22 enters in state, S2. After Te, the WD 22 can revert to the normal operation i.e. can operate using M number of the RX chains. This example of the rule is shown in figure 13. The assistance information may further indicate that the WD 22 can perform one or more layer- 1 measurements (as described in rule 2) using up to N number of RX chains (e.g., N=l) i.e. according to S2. The assistance information may further indicate that the WD 22 can perform one or more layer- 1 measurements according to relaxed measurement procedures (as described in rule 2). FIG. 13 shows example assistance information indicating an aperiodic pattern comprising of two activity states with transition time for multi -receiver chain operation during a predetermined time.

5. According to another specific example of the rule, the multi-RX operational activity indicate that the WD 22 can operate in states, SI and/or S2, with certain duty cycle during certain time period (Tl) starting from Tr. In one example, the information related to the duty cycle indicates that the WD 22 can operate in SI certain probability (Pl) and/or in state, S2, with certain probability (P2) during Tl starting from Tr. In another example, the information related to the duty cycle indicates that the WD 22 can operate in SI with certain maximum duty cycle (MxUDC) during T1 starting from Tr. In another example, the information related to the duty cycle indicates that the WD 22 can operate in S2 with certain minimum duty cycle (MmUDC) during T1 starting from Tr. This example of the rule is shown in FIG. 14. In this example, T1 = (Te-Tr). The assistance information may further indicate that the WD 22 can perform one or more layer- 1 measurements (as described in rule 2) using up to N number of RX chains (e.g., N=l) i.e. according to S2. The assistance information may further indicate that the WD 22 can perform one or more layer- 1 measurements according to relaxed measurement procedures (as described in rule 2). The parameters Pl, P2, MxUDC and MmUDC are described below: a. Pl is a ratio of maximum number of DL time resources over which the WD 22 can operate signals in SI with M number of RX chains during T1 to the total number of DL time resources during Tl. Examples of time resources are symbols, slots, subframes, frames, etc. b. P2 is a ratio of minimum number of DL time resources over which the WD 22 should operate signals in S2 with N number of RX chains during Tl to the total number of DL time resources during TL c. MxUDC is Pl expressed in percentage and MmUDC is P2 expressed in percentage According to another specific example of the rule, the multi-RX operational activity indicate that the WD 22 can perform one or more layer- 1 measurements according to relaxed measurement procedures during Tl starting from Tr. The relaxed measurement procedure enables the WD 22 to reduce its receiver activity and thereby reducing the heat dissipation. The WD 22 may or may not indicate the amount of time or percentage of time or duty cycle with which the WD 22 should operate in states, SI and/or S2 during the relaxed measurement procedure. Instead, the reduced WD 22 activity is realized by meeting certain pre-defined measurement requirements. The WD 22 operates according to the relaxed measurement procedure by meeting the relaxed measurement requirements e.g., relaxed or extended measurement time (Tmr). Examples of layer-1 measurements are the same described in rule # 2. Trm is longer compared to Tnm for the same type of type of the measurement. Tnm and the relation between Tnr and Tnm are the same as described in rule # 2. A specific example of the relaxed evaluation period (TEvaiuate BFD Rs Relax) for BFD performed by the WD 22 on reference signal (RS) is shown in table 2. The normal or non-relaxed evaluation period (TEvaiuate BFD RS) for the BFD performed on reference signal (RS) is shown in table 3. The parameters, P and N are scaling factors. Examples of RS are SSB, CSI-RS, etc. In this example, TEvaiuate BFD RS Relax corresponds to Trm and

TEvaiuate BFD RS corresponds to Tnm. From the tables 2 and 3, it can be seen that T Evaluate BFD RS Relax > Tfivaluate BFD RS.

Table 2. - Evaluation period T Evaluate BFD RS Relax for relaxed BFD in FR2.

Table 3: Evaluation period TEvaluate BFD RS for non-relaxed BFD in FR2 WD performing multi-RX chain operation with the reduced activity level In one example, the WD 22 starts performing the multi-RX chain operation with the activity level as indicated in the assistance information (e.g., based on any of the rules #1-6) after transmitting the assistance information to the network node 16. In another example, the WD 22 performs the multi-RX chain operation with the activity level as indicated in the assistance information only after receiving confirmation from the network node 16. For example, in the latter case, the WD 22 may further be configured by the network node 16 indicating whether the WD 22 can perform or is going to perform multi-RX chain operation as requested by the WD 22 in the assistance information i.e. with reduced activity level. In one example, the network node 16 may allow the WD 22 to perform multi-RX chain operation as requested/indicated by the WD 22. In another example, the network node 16 may not allow the WD 22 to perform multi-RX chain operation as requested/indicated by the WD 22. In another example, the network node 16 may allow the WD 22 to perform multi-RX chain operation but with a modified pattern of the activity levels compared to the one requested/indicated by the WD 22. In one example, the WD 22 performs the multi-RX chain operation with the activity level as indicated in the assistance information or according to the modified activity level by the network node 16 over certain time period (T2). T2 can be the same period as indicated in the assistance information (e.g., Tl), pre-defined valued or configured by the network node 16.

WD behavior under radio link problem during reduced multi-RX operational activity:

According to another aspect of this embodiment, if the WD 22 is performing or is configured to multi-RX chain operation with reduced activity level and if the WD 22 has detected at least one radio link problem (RLP) then the WD 22 performs one or more operational tasks related the multi-RX chain operations. The reduced activity is based on or is according to any of the rules and principles described in previous sections “Examples of multi-RX operational activity assistance information” and “WD behavior under radio link problem during reduced multi-RX operational activity.” The WD 22 detects RLP if at least one of the following conditions or criteria is met by the WD 22:

The received signal level (e.g., signal strength (SS), signal quality (SQ), etc.) estimated or measured by the WD 22 on signals of the serving cell is below certain threshold. Examples of SS are RSRP, path loss, etc. Examples of SQ are RSRQ, SNR, SINR, etc.

The received signal level (e.g., SS, SQ, etc.) estimated or measured by the WD 22 on signals of the serving cell is below certain threshold over certain time period.

- WD 22 detecting a beam failure (e.g., beam failure is detected if the signal quality of the beam is below certain threshold, hypothetical BLER of DL control channel (e.g., PDCCH) is above certain threshold (e.g., 10%), etc.),

- WD 22 has performed or is performing one or more candidate beam detection.

- WD 22 has detected at least LI 1 number of out of sync e.g., LI 1 > 1.

- WD 22 has triggered a radio link failure (RLF). The RLF is triggered if the WD 22 has detected more than L12 number of consecutive OOSs, etc.

- WD 22 has initiated a RRC connection re-establishment procedure.

- WD 22 has started a timer related to one or more RLP. The timer may start when the WD 22 detects the corresponding RLP. Examples of such timers are RLF related timer (e.g., T310), RRC connection re-establishment related timer (e.g., T311), etc.

- WD 22 has stopped the timer related to the one or more RLP. For example, when it has stopped timers such as T310, T311, etc.

Examples of one or more operational tasks performed by the WD 22 upon detecting at least one RLP are:

- WD 22 stops performing the multi-RX chain operation with reduced activity level. In this case the WD 22 may perform the one or more procedures such as LI -measurements with full or normal activity level e.g., according to the nonrelaxed measurement procedure.

- WD 22 releases one or more configurations related to the assistance information which in turn is related to the multi-RX chain operation with reduced activity. For example, the WD 22 is not allowed to transmit any assistance information to the network node 16 even if the WD 22 is configured/allowed to do so, e.g., based on pre-defined rule or configured/allowed by the network node 16.

- WD 22 stops one or more timers associated with the assistance information related to the multi-RX chain operation with reduced activity. For example, the WD 22 stops the timer which the WD 22 starts after it has transmitted the assistance information to the network node 16. In another example, the WD 22 stops the timer which the WD 22 starts after it has been configured by the network node 16 to transmit the assistance information to the network node 16.

- WD 22 switches to a less-demanding multi-RX chain operation mode, e.g., starts using smaller number of RX chains (for example, going from 3 to 2 RX chains).

The WD 22 may further be allowed or configured to revert to the original multi-RX chain operation with reduced activity after the RLP has been alleviated, e.g., the RLP does not exist anymore.

Embodiment 2: Method in a network node of receiving and using multi-RX chain assistance information from a WD

According to a second embodiment, a first network node 16 (NN1):

- receives from a WD 22, which is served by a first cell (Celli), an assistance information indicating an activity level with which the WD 22 can perform multi-RX chain operation over the next certain time period (Tl) and

- uses the received the assistance information for performing one or more operational tasks.

The examples of the rules according to which the WD 22 can transmit the assistance information are the same as described in the WD embodiment (e.g., as described in section “Embodiment 1 : Method in a WD of determining and transmitting multi-RX chain assistance information to a network node”).

Examples of the one or more operational tasks are:

1. Network node 16 (e.g., NN1) configuring the WD 22 to perform multi-RX chain operation or informing the WD 22 through RRC message or MAC CE message or DCI message that network node 16 (e.g., NN1) is performing or is going to perform multi-RX chain operation with the activity level as requested by the WD 22, e.g., in the assistance information.

2. Network node 16 (e.g., NN1) configuring the WD 22 to perform the multi- RX chain operation or informing the WD 22 that network node 16 (e.g., NN1) is performing or is going to perform multi-RX chain operation with the modified activity level compared to the WD’s requested activity level by the WD 22.

3. Network node 16 (e.g., NN1) informing the WD 22 with multi-RX chain operation level (e.g., reduced activity level configuration), when WD 22 informs Network node 16 (e.g., NN1) about over heating without indicating any priority or preference for reduced activity level.

4. Network node 16 (e.g., NN1) schedules the WD 22 with signals (e.g., data such as PDSCH) according to the configured activity level or according to the WD requested activity level in one or more cells e.g., Celli, Cell2, etc.

Network node 16 (e.g., NN1) may further configure the WD 22 by sending configuration message which enables/setup or disables/releases the transmission of the assistance information by the WD 22 to the network node 16. For example, the WD 22 can send the assistance information related to the multi-RX chain operation activity to the network node 16 only when the WD 22 is allowed to do so according to the configuration message, e.g., is set as enabled, setup, etc. But, the WD 22 cannot send the assistance information related to the multi-RX chain operation activity to the network node 16 if the WD 22 is not allowed to do so according to the configuration message, e.g., is set as disabled, released, etc.

Network node 16 (e.g., NN1) may further configure the WD 22 with one or more rules according to which or based on which the WD 22 can transmit the assistance information to the network node 16.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

Abbreviations that may be used in the preceding description include:

ARFCN Absolute Radio Frequency Channel Number

BFD Beam Failure Detection BFD-RS BFD Reference Signal

BM Beam Management

BM-RS Beam Management Reference Signal

BS Base Station

BSC Base Station Controller

BTS Base Transceiver Station

BW Bandwidth

CA Carrier Aggregation

CBM Common Beam Management

CC Component Carrier

CSI Channel-State Information

CSI-RS CSI Reference Signal

CQI Channel Quality Indication

DMRS Demodulation Reference Signal

FR Frequency Range

L 1 -RSRP Layer one RSRP

NR New Radio

NR-DC NR-Dual Connectivity

PBCH Physical Broadcast Channel

PCC Primary Component Carrier

PCell Primary Cell

PDCCH Physical Downlink Control Channel

PDSCH Physical Downlink Shared Channel

PFL Positioning Frequency Layer

PMI Pre-coding Matrix Indicator

PRS Positioning reference signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RAT Radio Access Technology

RB Radio Blocks

RAT Radio Access Technology

RI Rank Indicator RLM Radio Link Monitoring

RLM-RS Reference Signal for RLM

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSTD Reference Signal Time Difference

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

SI System Information

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SCS Subcarrier Spacing

SFN System Frame Number

SpCell Special Cell

SRS Sounding Reference Signal

SS Synchronization Signal

SSB Synchronization Signal Block

SSS Secondary Synchronization Signal

TCI Transmission Configuration Indicator

TRP Transmission and/or Reception Point

TRS Tracking Reference Signal

TTI Transmission Time Interval

UAI UE Assistance Information

UE User Equipment

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings. Embodiments:

Embodiment Al . A wireless device (WD) configured to communicate with a network node, the WD being served by a cell associated with the network node, the WD being configured to, and/or comprising a radio interface and/or processing circuitry configured to: determine a need to transmit assistance information indicating an activity level usable by the WD to perform a multi -receiver chain operation in the cell over a predetermined time, the need to transmit assistance information being determined based on at least one condition; and transmit the assistance information to the network node based on the determined need.

Embodiment A2. The WD of Embodiment Al, wherein the activity level is based on a periodic pattern and/or an aperiodic pattern of a first state and a second state, the first state corresponding to the WD being capable of performing the multireceiver chain operation using a first predetermined activity, the second state corresponding to the WD being capable of performing the multi -receiver chain operation using a second predetermined activity.

Embodiment A3. The WD of any one of Embodiments Al and A2, wherein the multi-receiver chain operation comprises at least one of: the WD receiving one or more signals using at least two receiver chains during at least partially overlapping times; and a multi-panel operation, the multi-panel operation comprising simultaneously receiving at least two beams during at least partially overlapping times from different spatial directions.

Embodiment Bl. A method implemented in a wireless device (WD) configured to communicate with a network node, the WD being served by a cell associated with the network node, the method comprising: determining a need to transmit assistance information indicating an activity level usable by the WD to perform a multi-receiver chain operation in the cell over a predetermined time, the need to transmit assistance information being determined based on at least one condition; and transmitting the assistance information to the network node based on the determined need.

Embodiment B2. The method of Embodiment Bl, wherein the activity level is based on a periodic pattern and/or an aperiodic pattern of a first state and a second state, the first state corresponding to the WD being capable of performing the multi -receiver chain operation using a first predetermined activity, the second state corresponding to the WD being capable of performing the multi -receiver chain operation using a second predetermined activity.

Embodiment B3. The method of any one of Embodiments Bl and B2, wherein the multi-receiver chain operation comprises at least one of: the WD receiving one or more signals using at least two receiver chains during at least partially overlapping times; and a multi-panel operation, the multi-panel operation comprising simultaneously receiving at least two beams during at least partially overlapping times from different spatial directions.

Embodiment Cl. A network node configured to communicate with a wireless device (WD), the WD being served by a cell associated with the network node, the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: receive assistance information indicating an activity level usable by the WD to perform a multi-receiver chain operation in the cell over a predetermined time; and perform at least one action based on the received assistance information.

Embodiment C2. The network node of Embodiment Cl, wherein the activity level is based on a periodic pattern and/or an aperiodic pattern of a first state and a second state, the first state corresponding to the WD being capable of performing the multi -receiver chain operation using a first predetermined activity, the second state corresponding to the WD being capable of performing the multi -receiver chain operation using a second predetermined activity.

Embodiment C3. The network node of any one of Embodiments Cl and C2, wherein the multi-receiver chain operation comprises at least one of the WD receiving one or more signals using at least two receiver chains during at least partially overlapping times; and a multi-panel operation, the multi-panel operation comprising simultaneously receiving at least two beams during at least partially overlapping times from different spatial directions.

Embodiment DI . A method implemented in a network node configured to communicate with a wireless device (WD), the WD being served by a cell associated with the network node, the method comprising: receiving assistance information indicating an activity level usable by the WD to perform a multi-receiver chain operation in the cell over a predetermined time; and perform at least one action based on the received assistance information.

Embodiment D2. The method of Embodiment DI, wherein the activity level is based on a periodic pattern and/or an aperiodic pattern of a first state and a second state, the first state corresponding to the WD being capable of performing the multi -receiver chain operation using a first predetermined activity, the second state corresponding to the WD being capable of performing the multi -receiver chain operation using a second predetermined activity.

Embodiment D3. The method of any one of Embodiments DI and D2, wherein the multi-receiver chain operation comprises at least one of the WD receiving one or more signals using at least two receiver chains during at least partially overlapping times; and a multi-panel operation, the multi-panel operation comprising simultaneously receiving at least two beams during at least partially overlapping times from different spatial directions.

Claims

1. A method performed by a wireless device, WD, capable of operating under multi-RX chain, the WD being served by a cell associated with a network node, the method comprising: determining an activity level with which the WD desires related to multi-RX chain operation over a next time period; and transmitting, to the network node, an assistance information indicating the desired activity level, wherein the desired activity level indicates an N number of RX chain(s) operation following an M number of RX chains operation, wherein M>N and M > 2.

2. Method according to Claim 1, wherein the desired activity level further indicates duration period of the N number of RX chain(s) operation and duration period of the M number of RX chains operation.

3. Method according to any of Claims 1 or 2, wherein N=1.

4. Method according to any of Claims 1 to 3, further comprising: receiving a confirmation from the network node that the WD is allowed to perform the multi-RX chain operations with the desired activity level.

5. Method according to any of Claims 1 to 4, wherein the desired activity level is determined when one or more of following conditions are satisfied: temperature of one or more hardware components of the WD is above a threshold; total amount of heat dissipated by the WD over a last certain time period is above a threshold; the WD has been operating with more than certain number of RX chains over a time period; the WD has been operating with multiple TX chains once every X time units; a problem over a RX chain is observed; total amount of the WD operational activities of certain types over a certain time period exceeds a threshold; or battery life of the WD is below certain threshold or is expected to fall below certain threshold.

6. Method according to any of Claims 1 to 5, wherein the M number of RX chains operation comprises at least one of: the WD receiving one or more signals using up to M number of receiver chains during at least partially overlapping times; and a multi-panel operation comprising simultaneously receiving up to M beams during at least partially overlapping times from different spatial directions.

7. A wireless device, WD, configured to communicate with a network node, the WD being served by a cell associated with the network node, the WD being configured to, and/or comprising a radio interface and/or processing circuitry configured to: determine an activity level with which the WD desires related to multi-RX chain operation over a next time period; and transmit, to the network node, an assistance information indicating the desired activity level, wherein the desired activity level indicates an N number of RX chain(s) operation following an M number of RX chains operation, wherein M>N and M > 2.

8. WD according to Claim 7, the WD is further configured to perform the method according to any of Claims 2 to 6.

9. A method performed by a network node associated with a cell by which a wireless device capable of operating under multi-RX chain is served, comprising: receiving, from the wireless device, assistance information indicating a desired activity level with which the wireless device desires related to multi-RX chain operation over a next time period, wherein the desired activity level indicates an N number of RX chain(s) operation following an M number of RX chains operation, wherein M>N and M > 2; and performing at least one action based on the received assistance information.

10. Method according to Claim 9, wherein performing at least one action comprises: informing the wireless device that the network node is to perform multi-RX chain operation with the wireless device on desired activity level; informing the wireless device that the network node is to perform multi-RX chain operation with a modified activity level compared to the desired activity level; or scheduling the wireless device according to a configured activity level or the desired activity level.

11. Method according to any of Claim 9 or 10, wherein N=1.

12. Method according to any of Claims 9 to 11, further comprising: configuring the wireless device which enables/disables transmission of assistance information by the wireless device.

13. A network node configured to communicate with a wireless device WD capable of operating under multi-RX chain, the WD being served by a cell associated with the network node, the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: receive, from the wireless device, assistance information indicating a desired activity level with which the wireless device desires related to multi-RX chain operation over a next time period, wherein the desired activity level indicates an N number of RX chain(s) operation following an M number of RX chains operation, wherein M>N and M > 2; and perform at least one action based on the received activity level.

14. Network node according to Claim 13, further configured to perform the method according to any of Claims 10 to 12.