WO2026037522A1 - Apparatus and methods for allocating ue resources for communication with a plurality of network cells - Google Patents

Abstract

Apparatus and corresponding methods as disclosed One apparatus is caused to maintain a list of user equipment, UE, Channel State Information, CSI, profiles, wherein a UE CSI profile defines an allocation of a UE's CSI resources for communication with a plurality of network cells; and allocate CSI resources in accordance with one of the UE CSI profiles. Another apparatus is caused to provide a cell; maintain a list of UE CSI profiles, wherein a UE CSI profile defines an allocation of a UE's CSI resources for communication with a plurality of network cells; and allocate CSI resources in accordance with one of the UE CSI profiles.

Description

APPARATUS AND METHODS FOR ALLOCATING UE RESOURCES FOR COMMUNICATION WITH A PLURALITY OF NETWORK CELLS

Field of the Invention

Various example embodiments relates to apparatus and related methods for allocating UE resources for communication with a plurality of network cells

Background to the Invention

Carrier Aggregation (CA) and Dual connectivity (DC) are different methods by which user equipment (UE) can transmit and receive data on multiple carriers. Implementation of CA and DC will depend on the capability of UE. Currently, in 5G New Radio (NR), when UE connects to a network for the first time, UE capability information is exchanged which is relevant to CA and/or DC implementation.

Summary of the Invention

According to a first example embodiment, apparatus is provided comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: maintain a list of user equipment, UE, Channel State Information, CSI, profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and allocate CSI resources in accordance with one of the UE CSI profiles.

The apparatus may be further caused to receive from a network cell an indication of which UE CSI profile is to be used, wherein the CSI resources are allocated in accordance with the indication. The apparatus may be further caused to receive the list of UE CSI profiles from a network cell. The list of UE CSI profiles may be received from the network cell by radio resource control, RRC, signalling.

The apparatus may be further caused to transmit to a network cell an indication of which UE CSI profile is to be used. The transmission to a network cell of an indication of which UE CSI profile is to be used may be to a primary cell, PCell, primary secondary cell, PSCell, or a secondary cell, SCell, using a medium access control, MAC, control element, CE. The MAC CE indicating which UE CSI profile is to be used may be integral with a MAC CE associated with the configuration of the cell.

The apparatus may maintain a plurality of lists of UE CSI profiles, one list for a master cell group of a master node and one for a secondary cell group of a secondary node.

According to a second example embodiment, apparatus is provided comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: provide a cell; maintain a list of UE CSI profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and allocate CSI resources in accordance with one of the UE CSI profiles.

The apparatus may be further caused to generate the list of UE CSI profiles; and transmit to at least one of the UE or another network cell the list of UE CSI profiles. The apparatus may be further caused to transmit to at least one of the UE or another network cell an indication of which UE CSI profile is to be used. The list of UE CSI profiles may be generated based on the capabilities of the apparatus, the capability of the UE and available network cells.

The apparatus may be further caused to: regenerate the list of UE CSI profiles when there is a change in the capabilities of at least one of the apparatus, the user equipment or available network cells; and retransmit to at least one of the UE or another network cell the regenerated list of UE CSI profiles.

If the apparatus provides a PCell, PSCell or SCell, the apparatus may be further caused to transmit to the UE an instruction for the UE to transmit to another cell a MAC CE indicating which UE CSI profile is to be used. Similarly, if the apparatus provides a PCell, PSCell or SCell, the apparatus may be caused to receive from the UE a MAC CE indicating which UE CSI profile is to be used.

According to a third example embodiment, a method comprises: maintaining a list of user equipment, UE, Channel State Information, CSI, profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and allocating CSI resources in accordance with one of the UE CSI profiles.

According to a fourth example embodiment, a method comprises: providing a cell; maintaining a list of UE CSI profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and allocate CSI resources in accordance with one of the UE CSI profiles. The method may further comprise: generating the list of UE CSI profiles; and transmitting to the UE and/or another network cell the list of UE CSI profiles.

According to a fifth example embodiment, apparatus comprises: circuitry configured to maintain a list of user equipment, UE, Channel State Information, CSI, profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and circuitry configured to allocate CSI resources in accordance with one of the UE CSI profiles.

The apparatus may further comprise circuitry configured to receive from a network cell an indication of which UE CSI profile is to be used, wherein the CSI resources are allocated in accordance with the indication. The apparatus may further comprise circuitry configured to receive the list of UE CSI profiles from a network cell. The list of UE CSI profiles may be received from the network cell by radio resource control, RRC, signalling.

The apparatus may further comprise circuitry configured to transmit to a network cell an indication of which UE CSI profile is to be used. The transmission to a network cell of an indication of which UE CSI profile is to be used may be to a PCell, PSCell or SCell using a medium access control, MAC, control element, CE. The MAC CE indicating which UE CSI profile is to be used may be integral with a MAC CE associated with the configuration of the cell.

The apparatus may further comprise circuitry configured to maintain a plurality of lists of UE CSI profiles, one list for a master cell group of a master node and one for a secondary cell group of a secondary node.

According to a sixth example embodiment, apparatus comprises: circuitry configured to maintain a list of UE CSI profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and circuitry configured to allocate CSI resources in accordance with one of the UE CSI profiles.

The apparatus may further comprise: circuitry configured to generate the list of UE CSI profiles; and circuitry configured to transmit to at least one of the UE or another network cell the list of UE CSI profiles. The apparatus may further comprise circuitry configured to transmit to at least one of the UE or another network cell an indication of which UE CSI profile is to be used. The list of UE CSI profiles may be generated based on the capabilities of the apparatus, the capability of the UE and available network cells. The apparatus may further comprise: circuitry configured to regenerate the list of UE CSI profiles when there is a change in the capabilities of at least one of the apparatus, the user equipment or available network cells; and circuitry configured to retransmit to at least one of the UE or another network cell the regenerated list of UE CSI profiles.

If the apparatus provides a PCell, PSCell or SCell, the apparatus may further comprise circuitry configured to transmit to the UE an instruction for the UE to transmit to another cell a MAC CE indicating which UE CSI profile is to be used. If the apparatus provides a PCell, PSCell or SCell, the apparatus may further comprise circuitry configured to receive from the UE a MAC CE indicating which UE CSI profile is to be used.

According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims

Brief Description of the Drawings.

Example embodiments will now be described with reference to the accompanying figures in which:

Figures 1 and 2 illustrates sub-optimal CSI related UE resource management with CA and DC respectively;

Figures 3 and 4 illustrates example embodiments of CSI related UE resource management with CA and DC respectively.

Figures 5 and 6 are flow diagrams illustrating examples methods of CSI related UE resource management; and

FIG. 7 is a simplified block diagram illustrating a device that is suitable for implementing example embodiments of the present disclosure.

Detailed Description of Embodiments

The principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these example embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below. The terminology used herein to describe embodiments is not intended to limit the scope. The articles “a,” “an,” and “the” are singular in that they have a single referent, however the use of the singular form in the present document should not preclude the presence of more than one referent. In other words, elements referred to in the singular can number one or more, 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, items, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, items, steps, operations, elements, components, and/or groups thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein are to be interpreted as is customary in the art. It will be further understood that terms in common usage should also be interpreted as is customary in the relevant art and not in an idealized or overly formal sense unless expressly so defined herein.

Carrier Aggregation (CA) allows UE to transmit and receive data on multiple component carriers (CCs) at the same time, enabling UE to utilize all available spectrum resources. For example, with 3GPP, in NR, there can be up to 32 CCs aggregated for UE. Each of the CCs can belong to different technologies, e.g. Frequency Division Duplexing (FDD) and Time Division Duplexing (TDD), can belong to different bands, and have different numerologies. The CCs in CA can be either co-located or non-co-located.

UE first connects to a primary cell (PCell) which will serve as the primary component carrier for the UE. During or after the connection setup with the PCell, the PCell may configure eligible secondary carriers (SCells) for the UE. The PCell configures UE with all the necessary configurations for the SCells through RRC preparing the SCells for use when required.

The configured SCells are activated based on activation methods for the UE. That could be either blind activation or buffer-based activation. Once an SCell is activated, UE can start to transmit and receive data from it.

Dual Connectivity (DC) allows a UE to transmit and receive data on multiple component carriers from two cell groups (CG) via master node (MN) and secondary node (SN). With Evolved UMTS Terrestrial Radio Access (E-UTRA) Dual Connectivity (EN-DC), a UE can be connected to both Long-Term Evolution (LTE) E-UTRA and 5G NR nodes. The Core Network (CN) is either LTE Evolved Packet Core (EPC) or 5G Core. This was later expanded so that both cells can belong to 5G NR, in which case the CN is exclusively 5G Core. These various options came under the general term Multi-Radio Dual Connectivity (MR-DC). MR-DC is a generalization of Intra-E-UTRA Dual Connectivity. MR-DC can offer a UE more resources for higher throughput. More commonly, it helps operators improve mobility robustness and handovers in macro/micro-cell deployments. It can also aid in migrating networks from 4G to 5G.

5G-New Radio Dual Connectivity (NR-DC) is a 5G connectivity option where one 5G user equipment (UE) connects to the 5G network via both a MN (Master Node) and a SN (Secondary Node). The UE serving cells in MN define the Master Cell Group (MCG), whereas the UE serving cells in SN define the Secondary Cell Group (SCG). DC allows a UE to transmit and receive data on multiple component carriers from two cell groups via master gNodeB (MN) and secondary gNodeB (SN).

With NR-DC, UE is connected to a Next Generation Node B (gNB) that acts as MN and one gNB that acts as SN. The MN is connected to 5G core network while the SN is connected to MN via the Xn interface. NR-DC can also be used when a UE is connected to two gNB-DUs (Distributed Unit), one serving the MCG and the other serving the SCG, connected to the same gNB-CU (Centralized Unit)), acting both as a MN and as a SN.

Currently, in 5G NR, when UE connects to network for the first time, if the UE is capable of multiconnectivity (CA / DC), UE is provided with configuration that can enable UE to operate in multiconnectivity mode. Some of the configurations involve static configuration for the CSI RS resources for the UE. E.g. how many CSI-RS measurements the UE can run in parallel in the time domain. However, during run-time, it may turn out that this configuration will not be the best one for the UE. And, with the current framework, there is no possibility to quickly update the static configuration so that the capabilities are re-configured across the CCs in an optimal way.

In the context of dual connectivity, 3GPP already allows that some UE capabilities which need coordination can be exchanged between MCG and SCG. For example, already now MCG and SCG can exchange the following UE capabilities: maxNumberResAcrossCC-AcrossFR-r16 (max number of SSB/CSI-RS/CSI-IM resources for beam management, pathloss measurement, BFD, RLM and new beam identification across frequency ranges and MCG&SCG); maxNumberAperiodicCSI-RS-Resource (max number of configured aperiodic CSI-RS resources per FR across MCG&SCG); maxNumberCSI-RS-Resource (max number of configured NZP-CSI-RS resources to measure L1-RSRP per FR across MCG&SCG); maxNumberCSI-RS-SSB-CBD (max number of different CSI-RS [and/or SSB] resources per FR across MCG&SCG); maxNumberSSB-BFD (max number of different SSBs per FR across MCG&SCG); maxNumberCSI-RS-BFD (max number of CSI-RS resources to monitor PDCCH quality per FR across MCG&SCG); maxNumberConfigsAIICC-r16 (max number of configured/active configured grant configurations per FR across MCG&SCG); maxNumberConfigsAIICC-r16 (max number of active SPS configurations per FR across MCG&SCG); and maxConfiguredResourceSetsAIICC (max number of TRS resource sets configured to UE per FR across MCG&SCG).

MN indicates to SN how many of the above resources SN can use and SN sends feedback to MN to inform how many of such resources it takes. Such information is exchanged using inter-node RRC messages via CG-Config and/or CG-Configlnfo. In context of inter-gNB CA, similar methods of information exchange can be accomplished using for example proprietary messages over the Xn interface.

It is observed that the UE capabilities that are presently exchanged are semi-static UE resources, i.e. resources which are allocated as soon as they are configured at the UE independent from the point in time when they are used and which configuration can only be changed via RRC signaling.

The inventors have appreciated that the number of CSI related RS and CPU resources (both per cell and in total) can vary in use. In current methods, these are agreed between the two nodes/gNBs, with static split between the nodes/gNBs, once in the beginning when RRC connection with MN and SN for the UE takes place.

Currently 5G NR supports limited information exchange between MN and SN about the operated carrier and limited UE capability related information as for example the maximum number of aperiodic CSI-RS resources that the SCG is allowed to configure for the UE to measure L1-RSRP etc. However, such semi-static information exchange is optional and even more important, certain important “dynamic” information related to UE capability is missing. Examples of such dynamic UE capabilities are: simultaneousCSI-ReportsAIICC, this parameter is used to indicate the total number of CSI reports (e.g. 14 for certain UE device models) that the UE can simultaneously process across all serving CCs and across MCG and SCG in case of NR-DC. This capability refers to the maximum number of CSI Processing Units (CPU) that the UE can allocate in parallel for measuring CSI-RS resources from all serving CCs across MN and SN. maxNumberSimultaneousNZP-CSI-RS-ActBWP-AIICC, indicating the maximum number of CSI-RS resources that the UE can read in parallel (i.e. “active CSI-RS resources”) in the active Bandwidth Parts (BWP) of all serving CCs across MN and SN. totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AIICC, indicating the total number of CSI-RS ports that the UE supports for the active CSI-RS resources (i.e. “active CSI-RS ports”) in the active BWPs of all serving CCs across MN and SN.

In any slot, a UE is not expected to have more allocated CSI processing units (CPUs) or active CSI-RS ports or active CSI-RS resources in the active bandwidth parts (BWPs) than reported as capability. If this happens, the UE behaviour is not defined in 3GPP specifications.

Without coordinating UE capabilities at run-time, how can network avoid requesting the UE to perform more CSI-RS reports or to read more CSI-RS resources that it is capable of? And in the other way, where without timely information available at the gNB, when new component carriers are config ured/activated, the only way for not exceeding the limit for such UE capabilities is to take a conservative approach by assuming that the other node/CC is consuming the maximum number of these resources based on the configured CCs (information which today is already possible to exchange between MN and SN). Clearly this is not optimal, and the network (NW) is not taking full advantage of the UE capabilities.

For example, figures 1 and 2 illustrates conventional, sub-optimal UE resource management with CA and DC respectively;

In FIG. 1 , when UE first connects to the PCell, if UE is capable of CA, candidate SCells are configured for the UE. gNB will make a static split of CSI resources across all the cells (PCell and all SCells configured), such that the allocation does not exceed the maximum supported values from the UE capabilities. In this scenario, the UE provides for up to 10 CSI-RS and 10 CSI reporting resources, with up to 4 each per cell as defined by the UE capability parameters of table 1 .

Table 1 : UE Capability Parameters gNB initially allocates 4 x CSI-RS and 4 x CSI reporting resources for the PCell (simplified as 4 x CSI in FIG. 1). Upon SCelH and SCell2 addition and corresponding capability co-ordination, gNB reallocates CSI-RS and CSI reporting resources whereby 4 of each remain allocated to the PCell and 4 of each are allocated to SCelH . Since the UE supports max 10 CSI resources that can be simultaneously used, gNB will allocate only 2 resources for SCell2, which is a downgraded configuration for the UE. Resources allocated and configured for the SCells are not used unless the SCells are activated. SCell2 gets activated based on SCell selection algorithm and for example buffer based SCell activation algorithm. Based on the CSI configuration, UE will start reporting CSI reports using just 2 CSI resources available for SCell2, even though SCelH is not using its configured 4 CSI resources. This is a sub-optimal configuration scenario that happens.

In FIG. 2, there is a similar sub-optimal resource allocation shown in the context of DC which is configured with a PCell and an SCell of a Master Node (MN) and a PSCell, SCelH and SCell2 of a Secondary Node (SN). In this scenario, the UE provide for up to 16 CSI-RS and 16 CSI reporting resources, with up to 4 each per cell as defined by the UE capability parameters of table 2.

Table 2: UE Capability Parameters

A static split of CSI resources across all the nodes is such that 8 resources are allocated for each node out a max 16 CSI resources that the UE can simultaneously support. A gNB is illustrated allocating 4 CSI resources for PCell and SCelH . However, only 2 resources can be re allocated for each of SCelH and SCell2 of SN notwithstanding that resources allocated to SCell of MN are not used unless that SCell is activated. Taking the example of UE capability for CSI RS and CSI reporting resource allocation, a solution to such sub-optimal resource allocation is provided by the use of a UE capability profile (UE CSI profile in the claims) which creates a framework that allows network to configure a list of UE capability profiles at the UE during the RRC configuration. The list of UE capability profiles contains all supported/suitable combinations of splitting the CSI RS and CSI reporting resources across the UE configured CCs. The content of the UE capabilities profiles is dependent on the overall UE capabilities. That is to say, different UEs may have different UE capabilities profiles. However, there could be a basic/default UE capability profile which defines the minimum set of capabilities supported by all UEs. It should be noted that although UE CSI profile is used here, other terminology such as UE CSI configurations can be equally used as well.

Furthermore, a mechanism is introduced for a network node to indicate at run-time to UE which capability profile should be used. Depending on CA or DC configuration permutations, UE involvement may be required in the change of allocation of CSI-RS and CSI reporting resources to the respective carriers as specified by the indicated profile.

Example Embodiment for Carrier Aggregation

Stepl : RRC Setup/Reconfiguration. Referring to FIG. 3, when UE connects to PCell for the first time, PCell generates the UE capability profile table for the UE, based on UE CSI RS and CSI reporting capability for example, its own cell and the SCells that will be configured. In this example, the UE capability is that defined by the parameters of table 1 above wherein UE can provide for up to 10 CSI-RS and 10 CSI reporting resources, with up to 4 each per cell.

All UE configured SCells are also informed about the UE capability profiles and their corresponding cell configuration. PCell then configures the UE with the generated capability profiles and indicates a default profile to be used via RRC configuration. Whenever an SCell is added/activated/released, PCell re-computes the profiles tables, indicates the same to all the UE configured SCells, and configures the updated profiles table to the UE via the RRC reconfiguration. The UE capability profile table will contain a set of different profiles, each indicating a possible UE capability allocation for the UE across the CC(s) as shown in Tabe 3 below. In this example, the CSI allocation indicates the number of CSI-RS and CSI reporting resources that UE should use for all configured carriers (configured via RRC signalling).

Table 3: UE CSI Capability Profiles Table For Carrier Aggregation

Step 2: SCell activation/de-activation. In CA, ‘SCell activation MAC CE’ may be sent from the PCell. So, PCell will have a view of which SCells are activated and in use, and which are not in use, and so it is in a better position to decide which profile UE should apply after certain SCell is activated/deactivated. When PCell sends a MAC CE to activate/deactivate an SCell, e.g: Activate SCelU , it indicates in the MAC CE the UE capability profile index that the UE should use; in this case profile 3 denoted by the ‘(3)’. Based on the profile indicated, UE should assume a different allocation of CSI-RS and CSI reporting resources as defined by the indicated capability profile index.

Step 3: Indication to other CCs. In respect of inter-cell latency, if the latency between the PCell and the SCells is not high (e.g. below a configured threshold T_Xp), PCell can quickly indicate the profile index change to the relevant SCells. Once PCell receives a HARQ ACK from the UE for the Activation MAC CE, PCell will indicate the profile in use by the UE to the respective SCells by the proprietary interface or future standardized interface between the PCell and the SCell. If the latency between the PCell and SCells is high (e.g. longer than a configured threshold T_Xp), PCell will not be able to inform the SCells quickly about the profile index change at the UE. In that case, it will be useful if the UE indicates the profile in use to the SCells (e.g. if respective SCell supports UL CA), by sending the UE capability reporting MAC CE with an indication of the profile in use.

Example Embodiment for Dual Connectivity

Step 1 : RRC Setup/Reconfiguration. Referring to FIG. 4, when UE connects to MN for the first time, for example, when NR-DC is established, MN generates the UE capability profiles table for the UE, based on UE capability and the cells that will be configured within the MN and the SN. In this example, the UE capability is that defined by the parameters of table 2 above wherein the UE provides for up to 16 CSI-RS and 16 CSI reporting resources, with up to 4 each per cell. All UE configured cells within the MN and the SN are also informed about the UE capability profiles and their corresponding cell configuration. MN then configures the UE with the generated capability profiles (e.g. with a UE CSI Capability Profiles Table) and indicates a default profile to be used via RRC configuration. Whenever any SCell is added/released, MN PCell re-computes the profiles tables, indicates the same to all the configured SCells for the UE, and configures the updated profiles table via the RRC re-configuration. The UE capability profile table will contain a set of different profiles, each indicating a possible UE capability allocation for the UE across the CC(s) as shown in Table 4 below.

Table 4: UE CSI Capability profiles for DC

An alternative approach for step 1, is that MN and SN independently generate the UE capability profiles that the UE should use in the respective cell groups (MCG and SCG). In generating its own capability profiles, SN takes into account MN generated profiles in order to make them compatible with its own profiles. This means that MN also needs to provide its own profiles to the SN during the initial NR-DC setup, and whenever it changes for example when cells are added/activated/released in MN. Such localised MN and SN profile management enables respective PCells and PSCells to be more responsive to SCell activation or deactivation.

Step 2: SCell activation/de-activation. When PSCell sends a MAC CE to activate an SCell in respective node, PSCell indicates in the MAC CE the UE capability profile index the UE should use. Once PSCell receives a HARQ ACK from the UE for the Activation MAC CE, it will indicate the profile in use by the UE to all its activated SCells by the proprietary interface or standardized interface. Optionally, e.g. if the latency between the PSCell and SCells is very high, UE can indicate the profile index in use by explicitly reporting via MAC CE to the SCells (if SCells support UL CA). Step 3: Extension for DC case. Since there is no communication possible between the MAC entities of the two legs, UE should indicate the capability profile in use in one leg (MN or SN) to the other leg (SN or MN respectively) using the UE capability reporting MAC-CE, so that the PSCell (if the other leg is SN) or the PCell (if the other leg is MN) is in better position to select the profile in future. If the alternative approach for Step 1 is used, when UE receives the profile index from one node (MN or SN), UE should find the compatible profile to be used in the other node, and indicate it to the other node via this MAC-CE

In both example embodiments above, the UE configuration for CSI resources can be dynamically configured/updated based on the run time situation for the UE. Moreover, timely information may be provided at PCell and SCells (in case with CA) or MN and/or SN (in case with DC) about the above mentioned “dynamic” UE capabilities usage status to take full advantage of UE capabilities without exceeding their maximum limit.

In practice, this could be facilitated by changes to certain technical standards. For example, in 5G NR TS 38.331 (RRC specification) or similar specification in the coming 6G: RRC definition of UE capability profile could indicate the capability profiles for the UE during RRC (re)configuration phase and PCell informing the UE capability profiles/selected UE capability profile to the other node/other CCs.

In 5G NR TS 38.321 (MAC specification), the SCell activation/deactivation MAC CE could be enhanced to include a field to specify the UE capability profile index that UE should use. One example embodiment for the MAC CE would be by extending Enhanced SCell Activation/Deactivation MAC CE with one Octet Ci field for the UE capability profile index. With the new MAC CE, at the same time when gNB sending SCell Activation/Deactivation MAC CE, gNB can also inform UE the selected UE Capability Profile Index. UE will allocate the processing capability accordingly. This means UE should assume a change in the allocation of CSI-RS and CSI reporting resources for the respective carriers as specified by the indicated profile.

In addition to MAC CE, other L2 or even L1 (PHY) signalling can be used as well for gNB to inform UE which UE Capability Profile should be applied. As another embodiment, when configured, UE can autonomously report the selected UE Capability Profile as well for example depending on the UE battery level. FIG. 5 is a flowchart of an example method according to some example embodiments of the present disclosure. The method can be implemented by cell providing apparatus such as PCells and PSCells, and comprises steps 501-504. Step 501 - provide a cell. Step 502 - generate and maintain a list of UE CSI profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells. Step 503 - transmit to a UE or another network cell the list of UE CSI profiles. Step 504 - allocate CSI resources in accordance with one of the UE CSI profiles

FIG. 6 is a flowchart of an example method according to some example embodiments of the present disclosure. The method can be implemented by UE apparatus and SCell apparatus, and comprises steps 601-604. Step 601 - maintain a list of UE CSI profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells. Step 602 - allocate CSI resources in accordance with one of the UE CSI profiles

FIG. 7 is a simplified block diagram of a device 700 that is suitable for implementing example embodiments of the present disclosure. The device 700 can be implemented at or as a part of either UE apparatus or cell providing apparatus.

As shown, the device 700 includes a processor 710, a memory 720 coupled to the processor 710, a communication module 730 coupled to the processor 710, and a communication interface (not shown) coupled to the communication module 730. The memory 720 stores at least a program 740. The communication module 730 is for bidirectional communications, for example, via multiple antennas. The communication interface may represent any interface that is necessary for communication.

The program 740 is assumed to include program instructions that, when executed by the associated processor 710, enable the device 700 to operate in accordance with the example embodiments of the present disclosure, as discussed herein with reference to FIGS. 1-6. The example embodiments herein may be implemented by computer software executable by the processor 710 of the device 700, or by hardware, or by a combination of software and hardware. The processor 710 may be configured to implement various example embodiments of the present disclosure.

The memory 720 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as nonlimiting examples. While only one memory 720 is shown in the device 700, there may be several physically distinct memory modules in the device 700. The processor 710 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 700 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable):

(i) a combination of analog and/or digital hardware circuit(s) with software/firmware and

(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

Generally, various example embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of example embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as nonlimiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the methods of figures 5 and 6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various example embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable media.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), Digital Versatile Disc (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Various example embodiments of the techniques have been described. In addition to or as an alternative to the above, the following examples are described. The features described in any of the following examples may be utilized with any of the other examples described herein.

Acronyms

CA Carrier Aggregation

CC Component Carrier

CG Cell Group

CN Core Network

CPU CSI Processing Units

CSI Channel State Information

CSI-RS CSI Reference Signal

DC Dual Connectivity

DCI Downlink Control Information

EPC Evolved Packet Core

FR1 Frequency Range 1

FR2 Frequency Range 2

LCH Logical Channel

LCID Logical Channel Identifier

LTE Long Term Evolution

MAC Medium Access Control

MAC CE MAC Control Element MCG Master Cell Group

MN Master Node

NR New Radio

NR-DC New Radio Dual Connectivity PCell Primary Cell

PSCell Primary Secondary Cell

RRC Radio Resource Control

RSRP Reference Signals Received Power

SCell Secondary Cell

SCG Secondary Cell Group

SN Secondary Node

UCI Uplink Control Information

UE User Equipment

Claims

1. Apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: maintain a list of user equipment, UE, Channel State Information, CSI, profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and allocate CSI resources in accordance with one of the UE CSI profiles.

2. Apparatus according to claim 1 further caused to: receive from a network cell an indication of which UE CSI profile is to be used, wherein the CSI resources are allocated in accordance with the indication.

3. Apparatus according to claim 1 or claim 2 further caused to: receive the list of UE CSI profiles from a network cell.

4. Apparatus according to claim 3, wherein the list of UE CSI profiles is received from the network cell by radio resource control, RRC, signalling.

5. Apparatus according to any preceding claim further caused to: transmit to a network cell an indication of which UE CSI profile is to be used.

6. Apparatus according to claim 5, wherein the transmission to a network cell of an indication of which UE CSI profile is to be used is to a primary cell, PCell, primary secondary cell, PSCell, or secondary cell, SCell, using a medium access control, MAC, control element, CE.

7. Apparatus according to claim 6 wherein the MAC CE indicating which UE CSI profile is to be used is integral with a MAC CE associated with the configuration of the cell.

8. Apparatus according to any preceding claim, wherein the apparatus maintains a plurality of lists of UE CSI profiles, one list for a master cell group of a master node and one for a secondary cell group of a secondary node.

9. Apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: provide a cell; maintain a list of UE CSI profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and allocate CSI resources in accordance with one of the UE CSI profiles.

10. Apparatus according to claim 9 further caused to: generate the list of UE CSI profiles; and transmit to at least one of the UE or another network cell the list of UE CSI profiles.

11 . Apparatus according to claim 10 further caused to: transmit to at least one of the UE or another network cell an indication of which UE CSI profile is to be used.

12. Apparatus according to claim 10 or claim 11 , wherein the list of UE CSI profiles is generated based on the capabilities of the apparatus, the capability of the UE and available network cells.

13. Apparatus according to claim 12 further caused to: regenerate the list of UE CSI profiles when there is a change in the capabilities of at least one of the apparatus, the user equipment or available network cells; and retransmit to at least one of the UE or another network cell the regenerated list of UE CSI profiles.

14. Apparatus according to any of claims 9 to 13, wherein the apparatus provides a PCell, PSCell or SCell, and wherein the apparatus is further caused to: transmit to the UE an instruction for the UE to transmit to another cell a MAC CE indicating which UE CSI profile is to be used.

15. Apparatus according to any of claims 9 to 13, wherein the apparatus provides a PCell, PSCell or SCell, and wherein the apparatus further caused to: receive from the UE a MAC CE indicating which UE CSI profile is to be used.

16. A method comprising: maintaining a list of user equipment, UE, Channel State Information, CSI, profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and allocating CSI resources in accordance with one of the UE CSI profiles.

17. A method comprising: providing a cell; maintain a list of UE CSI profiles, wherein a UE CSI profile defines an allocation of a UE’s CSI resources for communication with a plurality of network cells; and allocating CSI resources in accordance with one of the UE CSI profiles.

18. A method according to claim 17 further comprising: generating the list of UE CSI profiles; and transmitting to the UE and/or another network cell the list of UE CSI profiles.