WO2024165342A1

WO2024165342A1 - Conditional reconfiguration handling during musim operation in wireless networks

Info

Publication number: WO2024165342A1
Application number: PCT/EP2024/052010
Authority: WO
Inventors: Srinivasan Selvaganapathy; Faranaz SABOURI-SICHANI; Laura Luque SANCHEZ; Janne Veikko Kaasalainen
Original assignee: Nokia Technologies Oy
Priority date: 2023-02-10
Filing date: 2024-01-29
Publication date: 2024-08-15

Abstract

A technique may include establishing a first connection with a first network node via a first subscriber identity; initiating a connection setup procedure to establish a second connection with a second network node via a second subscriber identity; receiving, via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node; determining that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection; and performing an action associated with releasing at least the first conditional configuration with respect to the first network node.

Description

CONDITIONAL RECONFIGURATION HANDLING DURING MUSIM OPERATION IN WIRELESS NETWORKS

TECHNICAL FIELD

[0001] This description relates to telecommunications systems.

BACKGROUND

[0002] A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.

[0003] An example of a cellular communication system is an architecture that is being standardized by the 3^rd Generation Partnership Project (3GPP). A recent development in this field is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. E-UTRA (evolved UMTS Terrestrial Radio Access) is the air interface of 3GPP's LTE upgrade path for mobile networks. In LTE, base stations or access points (APs), which are referred to as enhanced Node AP (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices, or mobile stations are referred to as user equipment (UE). LTE has included a number of improvements or developments.

[0004] A global bandwidth shortage facing wireless carriers has motivated the consideration of the underutilized millimeter wave (mmWave) frequency spectrum for future broadband cellular communication networks, for example. mmWave (or extremely high frequency) may, for example, include the frequency range between 30 and 300 gigahertz (GHz). Radio waves in this band may, for example, have wavelengths from ten to one millimeters, giving it the name millimeter band or millimeter wave. The amount of wireless data will likely significantly increase in the coming years. Various techniques have been used in attempt to address this challenge including obtaining more spectrum, having smaller cell sizes, and using improved technologies enabling more bits/s/Hz. One element that may be used to obtain more spectrum is to move to higher frequencies, e.g., above 6 GHz. For fifth generation wireless systems (5G), an access architecture for deployment of cellular radio equipment employing mmWave radio spectrum has been proposed. Other example spectrums may also be used, such as cmWave radio spectrum (e.g., 3-30 GHz). 6G wireless networks are also being developed or will be developed in the near future.

SUMMARY

[0005] According to an example implementation, a method includes establishing, by a user device having at least a first subscriber identity and a second subscriber identity, a first connection with a first network node via the first subscriber identity; initiating, by the user device, a connection setup procedure to establish a second connection with a second network node via the second subscriber identity; receiving, by the user device via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node; determining, by the user device, that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection; and performing, by the user device, an action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[0006] According to an example implementation, an apparatus includes at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: establish, by a user device having at least a first subscriber identity and a second subscriber identity, a first connection with a first network node via the first subscriber identity; initiate, by the user device, a connection setup procedure to establish a second connection with a second network node via the second subscriber identity; receive, by the user device via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node; determine, by the user device, that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection; and perform, by the user device, an action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[0007] According to an example implementation, an apparatus includes means for establishing, by a user device having at least a first subscriber identity and a second subscriber identity, a first connection with a first network node via the first subscriber identity; means for initiating, by the user device, a connection setup procedure to establish a second connection with a second network node via the second subscriber identity; means for receiving, by the user device via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node; means for determining, by the user device, that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection; and means for performing, by the user device, an action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[0008] According to an example implementation, a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to: establish, by a user device having at least a first subscriber identity and a second subscriber identity, a first connection with a first network node via the first subscriber identity; initiate, by the user device, a connection setup procedure to establish a second connection with a second network node via the second subscriber identity; receive, by the user device via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node; determine, by the user device, that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection; and perform, by the user device, an action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[0009] The details of one or more examples of implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. l is a block diagram of a digital communications system such as a wireless network according to an example implementation.

[0011] FIG. 2 is a flow chart illustrating operation of a UE according to an example embodiment.

[0012] FIG. 3 is a flow chart illustrating operation of a user device or UE according to an example embodiment.

[0013] FIG. 4 is a diagram illustrating operation of a network based on a conditional configuration, such as a CPA, according to an example embodiment.

[0014] FIG. 5 is a diagram illustrating operation of a network based on a conditional configuration, such as a CHO or CPC configuration, according to an example embodiment.

[0015] FIG. 6 is a diagram illustrating operation of a network based on a conditional configuration according to another example embodiment.

[0016] FIG. 7 is a block diagram of a node or wireless station (e.g., base station/access point, relay node, or mobile station/user device) according to an example implementation.

DETAILED DESCRIPTION

[0017] The principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these 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.

[0018] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and/or “including”, when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/ or combinations thereof.

[0019] FIG. l is a block diagram of a digital communications system such as a wireless network 130 according to an example implementation. In the wireless network 130 of FIG. 1, user devices 131, 132, and 133, which may also be referred to as mobile stations (MSs) or user equipment (UEs), may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a gNB (which may be a 5G base station) or a network node. At least part of the functionalities of an access point (AP), base station (BS) or (e)Node B (eNB) may also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. BS (or AP) 134 provides wireless coverage within a cell 136, including the user devices 131, 132 and 133. Although only three user devices are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via an interface 151. This is merely one simple example of a wireless network, and others may be used.

[0020] A user device (user terminal, user equipment (UE)) may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, a vehicle, and a multimedia device, as examples. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.

[0021] In LTE (as an example), core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/serving cell change of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.

[0022] The various example implementations may be applied to a wide variety of wireless technologies, wireless networks, such as LTE, LTE-A, 5G (New Radio, or NR), cmWave, and/or mmWave band networks, or any other wireless network or use case. LTE, 5G, cmWave and mmWave band networks are provided only as illustrative examples, and the various example implementations may be applied to any wireless technology/wireless network. The various example implementations may also be applied to a variety of different applications, services or use cases, such as, for example, ultrareliability low latency communications (URLLC), Internet of Things (loT), time-sensitive communications (TSC), enhanced mobile broadband (eMBB), massive machine type communications (MMTC), vehicle-to-vehicle (V2V), vehicle-to-device, etc. Each of these use cases, or types of UEs, may have its own set of requirements.

[0023] Multiple User Subscriber Identity Module (MUSIM) UE's hardware capabilities are shared by the USIMs (User Subscriber Identity Module), and to use the hardware efficiently and economically, the related capabilities need to be dynamically split between the two USIMs (with each USIM having a different subscriber identity for the UE). While Release 17 3GPP MUSIM work was for UE’s with only Single-Rx/Single-Tx or in best case Dual-Rx/Single-Tx, Release 18 MUSIM work considers UEs with higher capability, e.g., Dual-RX (dual receiver) /Dual-TX (dual transmitter) UE. With dual (or two) receivers and dual (or two) transmitters, such a UE may be capable of maintaining two parallel RRC (radio resource control) connections, but possibly with lower capabilities on each USIM. 3GPP Release 18 will thus provide mechanisms to ease the dynamic split of UE hardware across two USIMs while keeping awareness and control on the network.

[0024] A multi -USIM (MUSIM) device (e.g., a MUSIM UE) has two (Dual) or more (Multiple) simultaneous 3GPP/3GPP2 network subscriptions (or subscriber identities or SIMs), e.g., with multiple corresponding International Mobile Subscriber Identities (IMSI) in case of EPS or Subscription Permanent Identifier (SUPI), each associated with a particular subscription belonging to the same or different Mobile Network Operator (MNO (/Mobile Virtual Network Operator (MVNO)).

[0025] In dual connectivity or muti-connectivity, the UE may be connected to multiple cells, e.g., such as the UE connected to a primary cell (PCell) and a secondary cell(s). The secondary cell(s) may include at least a primary secondary cell (PSCell). As noted, the UE may be assigned multiple subscriber identities, e.g., including a first subscriber identity and a second subscriber identity, for example. Also, for example, the UE may be connected to (or may initiate a connection or make a decision to connect to, or attempt a connection to) a first network (or first network node/gNB, such as network A) via a first subscriber identity, and similarly, the UE may be connected to (or may initiate a connection or make a decision to connect to or attempt to connect to) a second network (or a second network node or second gNB, such as network B) via a second subscriber identity.

[0026] Also, the UE may be configured with one or more conditional configurations with respect to one or more of the networks or network nodes. Conditional configurations may be or may include, for example, configurations for establishing a connection with a cell (e.g., a PCell or a PSCell), which may be triggered upon fulfillment or satisfaction of a condition. A conditional configuration, e.g., may include an indication of resources to be used for the potential (or possible) connection and other configuration information for the potential connection to a candidate target cell, and a trigger condition that may be evaluated by the UE, and if the trigger condition is or becomes true, the UE may or will then execute the change, addition or handover to the indicated candidate target cell. A conditional configuration may include, for example, one of several different conditional configuration types, such as a conditional handover (CHO) to perform a handover to a new PCell, a conditional PSCell change (CPC) to change a PSCell to a different cell, and/or a conditional PSCell addition (CPA) to add a new PSCell.

[0027] In some cases, a UE may have a first connection to a first gNB (first network node, which may be referred to as network node A or NW node A) via a first subscriber identity (e.g., via a first USIM) of the UE. Also, the UE may have a second connection to a second network node (e.g., network-B or NW-B) via a second subscriber identity (e.g., via a second USIM) of the UE, or at least the UE has initiated a connection setup procedure for the second connection to the second gNB (or second network node, network node-B, or NW node-B). Also, for example, the UE may receive one or more conditional configurations (e.g., CHO, CPC, and/or CPA configurations) with respect to the first gNB (or NW node-A). However, in some cases, after the UE detects an execution or trigger condition for one of these conditional configurations, the UE performing or executing the conditional configuration to the candidate target cell with respect to the first gNB may not be currently (e.g., at least temporarily) compatible with (or may be at least temporarily incompatible with) capability limitations of the UE, e.g., taking into account at least a current or predicted capability or resource utilization of the UE with respect to the second gNB or second connection (and also of course taking into account the current or predicted capability or resource utilization for a connection based on the triggered conditional configuration with respect to the first gNB or first connection). Thus, the capability or resource utilization for the first connection based on execution of the conditional configuration (if triggered) and the current or predicted capability or resource utilization with respect to the (at least initiated) second connection to the second gNB may currently (or at least temporarily) be incompatible with capability limitations of the UE.

[0028] When the UE is configured with conditional reconfigurations and evaluating the conditions, handling of MUSIM signaling procedure for simultaneous RRC connections may require some additional changes or techniques to be applied, for example. In this scenario, as the conditional configurations are not yet activated/triggered, and the UE can proceed with RRC connection setup at NW node B (second gNB or second network node, for the second connection). But, in this example, when the execution condition is met for the conditional configuration with respect to the first network node, the conditional (or target) configuration to add/change PSCell or handover to a new PCell is not compatible with the current operations of both RRC connections. Thus, the UE may need to declare the conditional change/addition of PSCell or conditional handover as a failure (e.g., as creating an incompatibility at the UE) and inform the network (e.g., UE to release and/or request the first network node to release such conditional configuration based on an incompatibility of such conditional configuration with UE capabilities, e.g., taking into account the current or predicted capabilities or resources used by the UE for the second connection). This procedure may involve the UE declaring or reporting a failure (and/or release) of the conditional configuration (and/or releasing and/or requesting a release of such conditional configuration) not due to mobility reasons but due to other (MUSIM specific) constraints or incompatibilities of the UE, e.g., based on current or predicted capabilities or resources used by the UE for connection to the first network node based on the conditional configuration, and the current or predicted capabilities or resources used by the UE for the second connection to the second network node. Moreover, the network resources and CPA/CHO/CPC evaluations until execution may be redundant until the execution condition is met.

[0029] According to an example embodiment, various techniques are described herein for a UE to indicate its preference for temporary capability restriction in NW node A (network node A, or first network node) by releasing/deactivating cells or cell groups (releasing a conditional configuration(s)) to allow the RRC connection setup in NW node B to be performed or continue, e.g., in order to avoid or prevent execution of the conditional configuration that would cause the UE incompatibility based on these two connections. Also, for example, the signalling procedure and/or techniques described herein may be extended to additional scenarios of adding and/or releasing secondary cells to the second network node (NW node B).

[0030] According example embodiments, various techniques and/or methods are described to allow a UE to detect or determine such an incompatibility for the UE, and then the UE perform an action associated with releasing a conditional configuration with respect to the first gNB or first connection (with respect to the first network node, or NW node A) that may be currently incompatible with current or predicted capability or resource utilization of the UE with respect to the second connection or second gNB (network node B). For example, the action performed by the UE associated with releasing a conditional configuration with respect to the first gNB may include, e.g., the UE performing one or more of releasing (by the UE) such conditional configuration and sending, by the UE to the first gNB or NW node A, a message or indication that the UE has released such conditional configuration with respect to the first gNB that is incompatible with the (current or predicted) capability or resource utilization of the UE for the second connection; or sending, by the UE to the first network node or network node A, a request or preference to release the conditional configuration with respect to the first gNB that is (at least temporarily) incompatible with the current or predicted capabilities or resources utilized by the UE. Or, alternatively, the UE may receive from the first network node (NW node A), a timer value indicating a delay time period the UE should delay releasing the conditional configuration. For example, upon expiration of the timer, if the second connection still exists, the UE will release the conditional configuration that caused the incompatibility with UE capabilities. Other actions may be performed.

[0031] According to an example embodiment, the capability limitations of the UE may include, e.g., one or more of a resource limitation of the UE that would be exceeded based on resource utilization of a connection that would be established, if triggered, based on at least a conditional configuration with respect to the first network node, and the current or predicted capability or resource utilization and/or resource utilization preallocation of the UE with respect to the second connection between the UE and the second network node; or an incompatibility between the conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the UE with respect to the second connection between the UE and the second network node.

[0032] For example, a resource limitation of the UE may include one or more of the following, as illustrative examples: processing or processor limitations of the UE; memory limitations of the UE; protocol stack limitations of the UE; limitations of transmitter(s) and/or receiver(s) of the UE; or frequency band and/or bandwidth limitations, or limitations as to a maximum number of frequency bands for connections of the UE. These are merely illustrative examples, and other resource limitations may be used or may exist.

[0033] Also, for example, an incompatibility between the conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the UE with respect to the second connection may include, for example: a frequency band combination incompatibility between one or more frequency bands used, predicted to be used, or allocated by the user device for the second connection to the second network node, and one or more frequency bands for at least the first conditional configuration with respect to the first network node. For example, there may be only two frequency combinations that the UE can perform: 1) frequencies or frequency bands Fl and F3 may be used at the same time by the UE; or, 2) frequencies or frequency bands F2 and F4 may be used at the same time by the UE. In this example, a frequency combination of Fl and F2 may not be used by the UE (UE may not use Fl and F2 at same time), and a frequency combination of F3 and F4 may not be used by the UE (UE may not use F3 and F4 at the same time in this example), for example. Thus, in this illustrative example, if the UE is using or will (or is predicted to) use frequency Fl for the second connection to the second network node, then a first conditional configuration with respect to the first network node will be released by the UE (or a message may be sent to cause or request such release) if that first conditional configuration indicates a frequency of F2, since the combination of Fl and F2 is not compatible (may not be used at the same time) by the UE. On the other hand, a second conditional configuration with respect to the first network node that indicates a frequency of F3 is compatible (or is not incompatible) with Fl used by the UE for the second connection, and thus, there is no need for the UE to release such second conditional configuration. These are merely some illustrative examples, and other UE incompatibilities may be used or indicated.

[0034] FIG. 2 is a flow chart illustrating operation of a UE according to an example embodiment. Operation 210 includes establishing, by a user device (e.g., UE) having at least a first subscriber identity and a second subscriber identity, a first connection with a first network node via the first subscriber identity. Operation 220 includes initiating, by the user device, a connection setup procedure to establish a second connection with a second network node via the second subscriber identity. Operation 230 includes receiving, by the user device via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node. Operation 240 includes determining, by the user device, that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection. And, operation 250 includes performing, by the user device, an action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[0035] With respect to the method of FIG. 2, the initiating may include, for example, at least one of the following: making a decision to establish or attempt to establish a connection with the second network node via the second subscriber identity; transmitting a random access preamble to the second network node in order to establish a connection with the second network node via the second subscriber identity; and/or transmitting a RRC (radio resource control) connection request to the second network node in order to establish a connection with the second network node via the second subscriber identity.

[0036] With respect to the method of FIG. 2, the plurality of conditional configurations may include, for example, one or more of the following conditional configuration types with respect to the first network node: a conditional handover (CHO); a conditional primary secondary cell (PSCell) change (CPC); and/or a conditional primary secondary cell (PSCell) addition (CPA).

[0037] With respect to the method of FIG. 2, the capability limitations of the user device may include, by way of illustrative example, at least one of the following: a resource limitation of the user device that would be exceeded based on resource utilization of a connection that would be established, if triggered, based on at least the first conditional configuration with respect to the first network node, and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node; or an incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node.

[0038] With respect to the method of FIG. 2, the resource limitation may include, by way of illustrative example, at least one of the following resource limitations of the user device (or UE): processing or processor limitations of the user device; memory limitations of the user device; protocol stack limitations of the user device; limitations of transmitter(s) and/or receiver(s) of the user device; or frequency band and/or bandwidth limitations, or limitations as to a maximum number of frequency bands for connections of the user device.

[0039] With respect to the method of FIG. 2, the incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection may include (by way of illustrative example): a frequency band combination incompatibility between one or more frequency bands used, predicted to be used, or allocated by the user device for the second connection to the second network node, and one or more frequency bands for at least the first conditional configuration with respect to the first network node.

[0040] With respect to the method of FIG. 2, the the performing, by the user device, the action associated with releasing at least the first conditional configuration may include, for example: sending, by the user device to the first network node, an indication that the user device has released the conditional configuration of at least the first conditional configuration with respect to the first network node that is incompatible with capability limitations of the user device.

[0041] With respect to the method of FIG. 2, the performing, by the user device, the action associated with releasing at least the first conditional configuration may include, for example: sending, by the user device to the first network node, a list of one or more conditional configurations, including at least the first conditional configuration, that are requested to be released, or which should be released, due to incompatibility of such conditional configurations with the capability limitations of the user device.

[0042] With respect to the method of FIG. 2, the method may include: receiving, by the user device from the first network node, a timer value indicating a delay time period the user device should delay releasing any of the conditional configurations with respect to the first network node including at least the first conditional configuration with respect to the first network node; upon expiration of a timer based on the timer value, determining, by the user device, whether the second connection to the second network node still exists; releasing, by the user device, at least the first conditional configuration if the second connection still exists at the timer expiration; and otherwise, maintaining, by the user device, at least the first conditional configuration, or omitting releasing at least the first conditional configuration, if the second connection has been disconnected or no longer exists at the timer expiration.

[0043] With respect to the method of FIG. 2, the performing, by the user device, the action associated with releasing the at least one of the plurality of conditional configurations may include, for example: sending, by the user device to the first network node, an indication to deprioritize use of the at least one conditional configuration due to incompatibility with capability limitations of the user device.

[0044] With respect to the method of FIG. 2, the determining may include, for example: receiving, by the user device via the second subscriber identity from the second network node with respect to the second connection after the connection setup procedure is completed for the second connection, configuration or reconfiguration information that indicates capabilities or resources to be used with respect to the second connection; determining or predict the capability or resource utilization of the user device with respect to the second connection based on the received configuration or reconfiguration information with respect to the second connection; evaluating whether one or more conditional configurations including at least the first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account or considering the capability or resource utilization of the user device with respect to the second connection determined or predicted based on the received configuration or reconfiguration information; and delaying use of the one or more of the conditional configurations with respect to the first network node until after the evaluating.

[0045] With respect to the method of FIG. 2, the performing the action may include, for example: performing, by the user device, after the evaluating, the action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[0046] FIG. 3 is a flow chart illustrating operation of a user device or UE according to an example embodiment. At 310, the UE may be a dualRx/dualTx MUSIM UE is in RRC-CONNECTED (a first connection) with network node A or connected to the first network node, via a USIM-A (or the first subscriber identity for the UE). At 312, the UE may receive one or more conditional configurations from network node A (the first network node), such as a CPA configuration to add a SCG (secondary cell group) in network node A. UE may initially be in RRC-IDLE with network node B (second network node). At 314, the UE may initiate a second connection to network node B (or the second network node) via USIM-B (via a second subscriber identify for the UE).

[0047] At 316, the UE may check or compare the overall UE capabilities (or limitations) to the current or predicted capability or resource utilization of the conditional configuration (e.g., CPA to add a SCG) for the NW node A with respect to network node A, and the current or predicted capability or resource utilization for a second connection (or initiated second connection) to network node B, to determine if the conditional configuration (e.g., CPA) with respect to network node A may be incompatible with the capability limitations of the UE, e.g., taking into account the current or predicted capability or resource utilization of the UE with respect to the second connection to network node B.

[0048] At 328, if the conditional configuration (e.g., CPA) with respect to the network node A is incompatible with UE capabilities, then there may be multiple options for actions that the UE may perform, such as, for example, option 1 and option 2 indicated in FIG. 3. At option 1, at 320, the UE may release the conditional configuration (e.g., CPA) with respect to the network node A. And at 322, the UE may send UE assistance information (UAI) to network node A indicating a list of one or more conditional configurations (e.g., including the CPA, and possibly other conditional configurations) that have been released by the UE, e.g., based on incompatibility, for example. At option 2, at 324, the UE may send UE assistance information (UAI) to network node A with a list of one or more conditional configurations (e.g., including the CPA) that are not compatible with the UE, which may be or may be interpreted as a request to release such incompatible conditional configuration(s). At 326 of option 2, the UE may pause evaluation of such one or more incompatible conditional configurations (thus, not execute such incompatible conditional configurations, even if the trigger condition for any of such conditional configuration(s) is met). The UE may receive a confirmation from the network node A instructing or confirming that the UE should release (or network node A has released) the one or more incompatible conditional configurations with respect to network node A.

Thus, the UE may then release such incompatible conditional configuration(s) based on the instruction or confirmation received by the UE that instructs or confirms the UE to release and thus not use, such incompatible configuration. Other actions may also be performed, such as the UE receiving a timer value from network node A, and upon expiration of such timer, the UE may release such incompatible conditional configuration if the UE second connection to network node B still exists. If the second connection to network node B does not exist or is no longer in place with network node B, then the UE may keep or maintain (and thus omit releasing) such conditional configuration with respect to network node A, since such conditional configuration with respect to network node A no longer presents or creates an incompatibility at the UE with respect to the second connection, since the second connection no longer exists (and thus such capabilities or resources utilized for such second connection are no longer being used by the UE). Other actions may be performed as well.

[0049] Various example embodiments may provide techniques for interworking of MUSIM operation and dual connectivity operation for the use case related to simultaneous RRC connection setup in one network and CPA, CHO or CPC procedures in another network for Dual TX/RX UE, for example. A number of different example embodiments are described and shown in various FIGs, as illustrative examples.

[0050] The first set of embodiments may apply to the use case where a MUSIM UE with dual connectivity (DC) may be configured with conditional PSCell addition (CPA) (as an example conditional configuration) as described below.

[0051] UE Embodiment 1 :

[0052] MUSIM UE has an ongoing RRC connection with NW node A.

[0053] MUSIM UE receives RRCReconfiguration with conditional configuration for addition of PSCell (CPA) in NW node A.

[0054] MUSIM UE needs to establish RRC Connection with (and/or has initiated a connection with) NW node B.

[0055] MUSIM UE decodes the conditional configuration for CPA after NW node B RRC connection setup and determines one or more configured candidate PSCells cannot be added due UE incompatibility, e.g., based on the overall UE capability and the resources in use (e.g., either current resources that are used, or predicted resources) in RRC connection with NW node B.

[0056] MUSIM UE may release the conditional configurations that are not compatible with overall UE capability, considering network node B resource or capability utilization, and UE may indicate the released configuration identifiers in the UAI to NW node A, for example.

[0057] NW node A releases the conditional (e.g., CPA) configurations at corresponding candidate PSCells based on the received UAI.

[0058] UE may trigger this message (message to be sent to NW node A including the UAI that indicates identifiers of released conditional configuration(s)) depending on the current status of CPA evaluation after the establishment of the RRC connection in NW node B, for example.

[0059] UE may also trigger (send) this message (message sent to NW node A including the UAI that indicates identifiers of released conditional configuration(s)), even before the RRC connection setup in network node B if the TTT (time to trigger) for evaluation condition is already started.

[0060] UE Embodiment 2:

[0061] In an alternative method, instead of releasing the conditional configurations, UE will trigger UAI and indicate its preference to release a subset of target cells and pause the CPA evaluation until the NW response.

[0062] NW Embodiment 3 :

[0063] Network method where NW node A may decide to continue with CPA configuration with delayed execution until the RRC connection with NW node B is released or using an additional timer. NW node A sends RRC Reconfiguration message with an additional timer value to delay the CPA execution. This method may be used, for example, for the scenarios where NW node B operation is of short duration adding the CPA or conditional configuration back for UE requires additional signaling and delay in resuming these conditional configuration(s) with respect to NW node A.

[0064] As alternative NW embodiment, NW node A may configure the timer for delayed execution after NW node B connection establishment to allow the UE to wait for release of NW node B connection and start the execution of CPA. Here, the UE may decide to delay the execution depending on the NW node B connection duration estimated or predicted at the time of connection setup. For example, for short signalling and small data transmission (SDT) scenarios. For example, if the UE is still connected to NW node B when such timer expires, then the UE may release the conditional configuration (e.g., CPA) with respect to NW node A that caused the UE incompatibility. Otherwise, at the timer expiration, if the UE is no longer connected to NW node B (e.g., small data transmission from UE to NW node B has completed, and UE terminated connection to NW node B), then the UE may keep or not release (omit releasing) the conditional configuration with respect to NW node A that temporarily caused an incompatibility for the UE.

[0065] Also, for example, the example solutions or technique can be extended for Embodiment 1 and 2 to Conditional Handover (CHO) or to Conditional PSCell Change (CPC) at NW node A where more than one candidate target PCells or target PSCells configuration are provided to a UE for CHO or CPC, respectively.

[0066] When the configuration for CHO or CPC in (or with respect to) NW node A is pending in UE at the time of RRC connection setup in NW node B, the UE may check the candidate target cells’ frequencies of the conditional configurations for compatibility with NW node B operation, and may send UAI (UE assistance information) to reduce the capability and include a list of conditional configurations that can be (or should be) released in the same UAI. UE may also release the configurations by itself and may send a message (e.g., UAI) to NW node A identifying the conditional configurations that have been released by UE due to incompatibility between NW node conditional configuration and a connection to another NW node (e.g., to NW node B).

[0067] Also, for example, an alternative or extension to previous technique(s) or method(s) described above may be to provide (e.g., guarantee) that CHO for NW node A is not completely terminated or released, and the UE may request extended time from NW node A and indicate need for measurement gap from NW node B. In this case, UE may trigger CHO to not the best cell to keep also NW node B connection or, alternatively, when NW node A goes bad (and thus the connection to NW node A is dropped or degrades), the UE may terminate its connection to NW node B and perform CHO to the needed cell.

[0068] For a CPA, for example, the UE may be in single connectivity, and the UE may be transitioning or moving to dual connectivity. For example, the UE may currently have a MCG (Master cell group) with a PCell, and then would like to add a secondary PCell, e.g., PSCell (with SCG). Thus, a CPA may be used to change a UE from single connectivity to dual connectivity by adding a PSCell and SCG (secondary cell group) for UE with respect to the NW node A.

[0069] UE may receive and decode the conditional configurations. As part of decoding the conditional configurations, the UE may determine the details of each of those configurations for different candidate cells, including determining information about the cells (carrier frequency, cell ID, and the UE may consider frequency combinations), and trigger condition to cause it to change to this cell, or to add this cell, or to perform handover to this cell, etc. UE may then check, for example, for one or more incompatibilities between each of these conditional configurations with respect to NW node A, and the connection for NW node B. For example, the UE may check for band or band combination limitations for the UE, considering the frequency or frequency bands used by both the conditional configuration for NW node A and the connection for NW node B. The UE may check for other incompatibilities as well for each of the received conditional configurations.

[0070] FIG. 4 is a diagram illustrating operation of a network based on a conditional configuration, such as a CPA, according to an example embodiment.

[0071] 1. A dualRx/dualTx MUSIM UE has two subscriber identities, including

UE1 (which is a first subscriber identity for the UE) and UE2 (which is a second subscriber identity for the UE). Thus, as shown in FIG. 4, UE1 and UE2 refer to (or identify) the two different subscriber identities of the UE. The UE may communicate (e.g., send and receive messages) via each of the subscriber identities(via UE1 subscriber identity and UE2 subscriber identity). The UE is in RRC-CONNECTED via UE1 (via a first subscriber identity of the UE) with NW (network) node A.

[0072] 2. The UE, via a second subscriber identity (UE2), may be (at least initially) in RRC-IDLE with NW node B.

[0073] 3. NW node A transmits a RRCReconfiguration to UE via the UE first subscriber identity (UE1) including the conditional configurations of candidate PSCells for addition (CPA). Thus, the UE receives, via its first subscriber identity (UE1), one or more conditional configurations with respect to network node A.

[0074] 4. UE2 intends to initiate RRC connection with NW node B (or UE may have already established a connection to NW node B), via the UE second subscriber identity (UE2).

[0075] 5. The UE proceeds with a connection setup procedure with respect to the

NW node B. The UE, via UE2, receives a RRC connection setup message from NW node B.

[0076] 6. UE (e.g., via UE1) decodes the CPA configurations received from NW node A, and thus the UE determines the resources or capabilities indicated for each of the conditional configurations. In some cases, the resources or capabilities to be utilized for a prospective connection of a candidate target cell associated with a conditional configuration may be incompatible (at the UE) (or may cause or create an incompatibility at the UE) with respect to the connection or initiated connection of the UE to NW node B.

[0077] 7. At the same time as step 6, UE checks for (or determines or detects) compatibility/incompatibility of a resource or capability used by a conditional configuration with a capability or resource to be used by the UE for the connection to NW node B. For example, the UE may detect or determine the compatibility or incompatibility of candidate PSCells frequency (associated with a conditional configuration with respect to NW node A) or with current ongoing RRC connection with NW node B. Thus, for example, the UE may check the candidate PSCells and/or conditional configurations received for NW node A (and their indicated resources or capabilities that will be utilized) to determine whether there is an incompatibility between any of the resources or capabilities to be used by the UE for a connection triggered by the conditional configuration with respect to NW node A and the resources or capabilities used (or planned or predicted to be used) by the UE for the connection to NW node B. In this example, the UE determines that some (or one or more) of the CPA configurations are not compatible (or are incompatible). Thus, for example, the UE may determine or detect UE incompatibilities or UE features limitations between the connection to NW node B and one or more of the conditional configurations with respect to NW node A, which may cause the UE to reject (e.g., including to release and/or request a release of such incompatible conditional configuration) one or more of the conditional configurations with respect to NW node A, based on a conflict or incompatibility of the conditional configuration with the current UE capability and ongoing connection with NW node B, for example.

[0078] Embodiment 1:

[0079] 8. The UE, via UE1 (via the first subscriber identity) releases the noncompatible conditional configurations with respect to NW node A (e.g., UE releases the incompatible CPA configurations).

[0080] 9. The UE, via UE1, sends User Assistance Information (UAI) to NW node

A indicating the conditional configurations for CPA that have been released with respect to NW node A.

[0081] 10. NW node A releases the CPA configurations indicated by the UE via

UE1.

[0082] Embodiment 2:

[0083] 11. UE, via UE1, indicates via User Assistance Information (UAI) to NW node A the preferred CPA configurations to be released due to non-compatibility.

[0084] 12. The UE, via UE1, pauses the evaluation of CPA evaluation (for the incompatible conditional configuration) until it receives a response from NW node A.

[0085] 13. NW node A releases the indicated CPA configurations, in response or based on the UAI received from the UE. [0086] 14. NW node A sends a new RRC reconfiguration to UE1 which includes valid CPA configurations (e.g., which are compatible with the current connection to network node B).

[0087] Embodiment 3:

[0088] 15. NW node A may decide to send a new RRC reconfiguration to provide a new timer via UE1 to the UE to increase the CPA execution deadline before the configured resources are released at SN (source node). If UE, via UE2, has released the RRC connection with NW node B before the timer expiry, the UE, via UE1, will proceed with evaluation of the conditional configuration with respect to NW node A. Otherwise, the may release the CPA (since the incompatibility still exists with respect to the connection with NW node B) or act according to embodiments 1 or 2.

[0089] FIG. 5 is a diagram illustrating operation of a network based on a conditional configuration, such as a CHO or CPC configuration, according to an example embodiment.

[0090] 1. Similar to FIG. 4, a dualRx/dualTx MUSIM UE is in RRC-

CONNECTED with network node A, and may communicate via a first subscriber identity (e.g., UE1) with NW node A, and may communicate via a second subscriber identity (e.g., UE2) with NW node B.

[0091] 2. The UE is in RRC -IDLE with network node B.

[0092] 3. NW node A transmits RRC Reconfiguration message to UE via UE1 in which a conditional configuration for PCell change (for CHO) and PSCell (for CPC) is included (these are the conditional configurations with respect to NW node A), or other conditional configurations. These are merely illustrative examples of conditional configuration types.

[0093] 4. The UE, via UE2, intends to initiate, or has initiated, a RRC connection with NW node B.

[0094] 5. The UE, via UE2, proceeds with the RRC connection setup procedure with NW node B, to establish a connection with NW node B.

[0095] 6. The UE, via UE1, decodes the CHO/CPC configurations received in the

RRCReconfiguration from NW node A.

[0096] 7. At the same time as previous step, UE internally checks the frequency or frequency band of the target cells received in the conditional configuration from NW node A and determines which ones are non-compatible with the current UE capabilities due to the ongoing RRC connection with NW node B. Other capabilities or resources indicated for these conditional configurations may also be checked or compared to determine if the conditional configurations are compatible or incompatible with UE capabilities, based on the ongoing or initiated connection to NW node B.

[0097] 8. The UE, via UE1, sends User Assistance Information(UAI) to NW node

A indicating the reduced capabilities (e.g., such as frequency band combination limitations or other capability limitations of the UE) and providing a list of target cells and/or conditional configurations that could (or should, or are requested to) be released due to non-compatibility.

[0098] FIG. 6 is a diagram illustrating operation of a network based on a conditional configuration according to another example embodiment.

[0099] 1. A dualRx/dualTx MUSIM UE is in RRC-CONNECTED with network node A.

[00100] 2. The UE is in RRC -IDLE with network node B.

[00101] 3. NW node A transmits RRCReconfiguration message to UE, via UE1, including configuration of candidate target PCell (in case of CHO) or target PSCells (in case of CPC), for example, or other conditional configurations.

[00102] 4. The UE, via UE2, intends to initiate, or has initiated, a RRC connection with NW node B.

[00103] 5. UE, via UE2, proceeds with the RRC connection setup procedure, in order to set up a connection with NW node B.

[00104] 6. The UE, via UE1, decodes the received conditional configurations, such as the CHO/CPC configuration(s), or other conditional configurations.

[00105] 7. At the same time as previous step, UE internally checks the frequency or frequency bands of the target cells received in the conditional configuration from NW node A and determines which ones are non-compatible with the current UE capabilities due to the ongoing RRC connection with NW node B.

[00106] 8. The UE, via UE 1, indicates to NW node A in UAI to keep measurement, or to continue performing signal measurements, for these and deprioritize CHO for these candidates (or for these candidate cells or these conditional configurations, e.g., which are incompatible). Thus, UE, via UE1, sends UAI to NW node A indicating conditional configurations that should be deprioritized, e.g., based on incompatibility of these conditional configurations.

[00107] 9. UE, via UE2, sends User Assistance Information to NW node B indicating need or request for measurement gap to keep measurements ongoing for NW node A. Then, the UE, via UE1, checks or performs measurements and prioritizes CHO to candidate cells or conditional configurations that were not deprioritized (e.g., UE prioritizes CHO to conditional configurations or candidate cells that were not incompatible). If NW node A connection fails or goes bad, the UE (e.g., via UE2) may release NW node B connection and may perform CHO for the needed cell. Alternatively, if NW node A connection fails or goes bad, the UE (e.g., via UE1) may release NW node A connection and may perform CHO for the needed cell.

[00108]

Table 1

[00109] Table 1 illustrates some example frequency combinations that may be used together by the UE, and some frequency combinations that are incompatible. In this example, frequency combinations Fl, F3 may be used by the UE, or F2, F4. If, for example, UE is already using Fl for NW node A connection, and has a connection with NW node B using F3, then a conditional configuration for CHO for NW node A that indicates frequency F2 (based on the conditional handover by UE from Fl to F2) would be rejected by the UE (e.g., released, or message sent by UE to NW node A suggesting or requesting release of this conditional configuration) as being incompatible by the UE, since a frequency combination of F2 and F3 is not compatible. The second row of Table 1 illustrates another example, where a CHO indicating F2 would be compatible with F4 used by existing connection to NW node B (and thus, the UE would not reject or release such CHO or conditional configuration). [00110] Example 1 : An apparatus, comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to cause the apparatus at least to: establish, by a user device having at least a first subscriber identity and a second subscriber identity, a first connection with a first network node via the first subscriber identity; initiate, by the user device, a connection setup procedure to establish a second connection with a second network node via the second subscriber identity; receive, by the user device via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node; determine, by the user device, that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection; and perform, by the user device, an action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[00111] Example 2. The apparatus of example 1 wherein the at least one processor and the computer program code configured to cause the apparatus to initiate a connection setup procedure comprises the at least one processor and the computer program code configured to cause the apparatus to perform at least one of the following: make a decision to establish or attempt to establish a connection with the second network node via the second subscriber identity; transmit a random access preamble to the second network node in order to establish a connection with the second network node via the second subscriber identity; and/or transmit a RRC (radio resource control) connection request to the second network node in order to establish a connection with the second network node via the second subscriber identity.

[00112] Example 3. The apparatus of any of examples 1-2, wherein the plurality of conditional configurations comprises one or more of the following conditional configuration types with respect to the first network node: a conditional handover (CHO); a conditional primary secondary cell (PSCell) change (CPC); or a conditional primary secondary cell (PSCell) addition (CPA).

[00113] Example 4. The apparatus of any of examples 1-3, wherein the capability limitations of the user device comprise at least one of the following: a resource limitation of the user device that would be exceeded based on resource utilization of a connection that would be established, if triggered, based on at least the first conditional configuration with respect to the first network node, and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node; and/or an incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node.

[00114] Example 5. The apparatus of example 4, wherein the resource limitation comprises at least one of the following resource limitations of the user device: processing or processor limitations of the user device; memory limitations of the user device; protocol stack limitations of the user device; limitations of transmitter(s) and/or receiver(s) of the user device; or frequency band and/or bandwidth limitations, or limitations as to a maximum number of frequency bands for connections of the user device.

[00115] Example 6. The apparatus of any of examples 4-5, wherein the incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection comprises: a frequency band combination incompatibility between one or more frequency bands used, predicted to be used, or allocated by the user device for the second connection to the second network node, and one or more frequency bands for at least the first conditional configuration with respect to the first network node.

[00116]

[00117] Example 7. The apparatus of any of examples 1-6, wherein the at least one processor and the computer program code configured to cause the apparatus to perform, by the user device, the action associated with releasing at least the first conditional configuration comprises the at least one processor and the computer program code configured to cause the apparatus to: send, by the user device to the first network node, an indication that the user device has released the conditional configuration of at least the first conditional configuration with respect to the first network node that is incompatible with capability limitations of the user device.

[00118] Example 8. The apparatus of any of examples 1-6, wherein the at least one processor and the computer program code configured to cause the apparatus to perform, by the user device, the action associated with releasing at least the first conditional configuration comprises the at least one processor and the computer program code configured to cause the apparatus to: send, by the user device to the first network node, a list of one or more conditional configurations, including at least the first conditional configuration, that are requested to be released, or which should be released, due to incompatibility of such conditional configurations with the capability limitations of the user device.

[00119] Example 9. The apparatus of example 8, wherein the at least one processor and the computer program code are configured to cause the apparatus to: receive, by the user device from the first network node, a timer value indicating a delay time period the user device should delay releasing any of the conditional configurations with respect to the first network node including at least the first conditional configuration with respect to the first network node; upon expiration of a timer based on the timer value, determine, by the user device, whether the second connection to the second network node still exists; release, by the user device, at least the first conditional configuration if the second connection still exists at the timer expiration; and otherwise, maintain, by the user device, at least the first conditional configuration, or omit releasing at least the first conditional configuration, if the second connection has been disconnected or no longer exists at the timer expiration.

[00120] Example 10. The apparatus of any of examples 1-6, wherein the at least one processor and the computer program code configured to cause the apparatus to perform, by the user device, the action associated with releasing the at least one of the plurality of conditional configurations comprises the at least one processor and the computer program code configured to cause the apparatus to: send, by the user device to the first network node, an indication to deprioritize use of the at least one conditional configuration due to incompatibility with capability limitations of the user device.

[00121] Example 11. The apparatus of any of examples 1-10, wherein the at least one processor and the computer program code configured to determine comprises the at least one processor and the computer program code configured to: receive, by the user device via the second subscriber identity from the second network node with respect to the second connection after the connection setup procedure is completed for the second connection, configuration or reconfiguration information that indicates capabilities or resources to be used with respect to the second connection; determine or predict the capability or resource utilization of the user device with respect to the second connection based on the received configuration or reconfiguration information with respect to the second connection; evaluate whether one or more conditional configurations including at least the first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account or considering the capability or resource utilization of the user device with respect to the second connection determined or predicted based on the received configuration or reconfiguration information; and delay use of the one or more of the conditional configurations with respect to the first network node until after the evaluating.

[00122] Example 12. The apparatus of example 11, wherein the configuration or reconfiguration information with respect to the second connection is received via a RRC (radio resource control) reconfiguration message.

[00123] Example 13. The apparatus of any of examples 11-12, wherein the at least one processor and the computer program code configured to perform the action comprises the at least one processor and the computer program code configured to: perform, by the user device, after the evaluating, the action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[00124] Example 14. A method, comprising: establishing, by a user device having at least a first subscriber identity and a second subscriber identity, a first connection with a first network node via the first subscriber identity; initiating, by the user device, a connection setup procedure to establish a second connection with a second network node via the second subscriber identity; receiving, by the user device via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node; determining, by the user device, that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection; and performing, by the user device, an action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[00125] Example 15. The method of example 14 wherein the initiating comprises at least one of the following: making a decision to establish or attempt to establish a connection with the second network node via the second subscriber identity; transmitting a random access preamble to the second network node in order to establish a connection with the second network node via the second subscriber identity; and/or transmitting a RRC (radio resource control) connection request to the second network node in order to establish a connection with the second network node via the second subscriber identity.

[00126] Example 16. The method of any of examples 14-15, wherein the plurality of conditional configurations comprises one or more of the following conditional configuration types with respect to the first network node: a conditional handover (CHO); a conditional primary secondary cell (PSCell) change (CPC); or a conditional primary secondary cell (PSCell) addition (CPA).

[00127] Example 17. The method of any of examples 14-16, wherein the capability limitations of the user device comprise at least one of the following: a resource limitation of the user device that would be exceeded based on resource utilization of a connection that would be established, if triggered, based on at least the first conditional configuration with respect to the first network node, and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node; or an incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node.

[00128] Example 18. The method of example 17, wherein the resource limitation comprises at least one of the following resource limitations of the user device: processing or processor limitations of the user device; memory limitations of the user device; protocol stack limitations of the user device; limitations of transmitter(s) and/or receiver(s) of the user device; or frequency band and/or bandwidth limitations, or limitations as to a maximum number of frequency bands for connections of the user device.

[00129] Example 19. The method of any of examples 17-18, wherein the incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection comprises: a frequency band combination incompatibility between one or more frequency bands used, predicted to be used, or allocated by the user device for the second connection to the second network node, and one or more frequency bands for at least the first conditional configuration with respect to the first network node.

[00130] Example 20. The method of any of examples 14-19, wherein the performing, by the user device, the action associated with releasing at least the first conditional configuration comprises: sending, by the user device to the first network node, an indication that the user device has released the conditional configuration of at least the first conditional configuration with respect to the first network node that is incompatible with capability limitations of the user device.

[00131] Example 21. The method of any of examples 14-19, wherein the performing, by the user device, the action associated with releasing at least the first conditional configuration comprises: sending, by the user device to the first network node, a list of one or more conditional configurations, including at least the first conditional configuration, that are requested to be released, or which should be released, due to incompatibility of such conditional configurations with the capability limitations of the user device.

[00132] Example 22. The method of example 21, comprising: receiving, by the user device from the first network node, a timer value indicating a delay time period the user device should delay releasing any of the conditional configurations with respect to the first network node including at least the first conditional configuration with respect to the first network node; upon expiration of a timer based on the timer value, determining, by the user device, whether the second connection to the second network node still exists; releasing, by the user device, at least the first conditional configuration if the second connection still exists at the timer expiration; and otherwise, maintaining, by the user device, at least the first conditional configuration, or omitting releasing at least the first conditional configuration, if the second connection has been disconnected or no longer exists at the timer expiration.

[00133] Example 23. The method of any of examples 14-19, wherein the performing, by the user device, the action associated with releasing the at least one of the plurality of conditional configurations comprises: sending, by the user device to the first network node, an indication to deprioritize use of the at least one conditional configuration due to incompatibility with capability limitations of the user device.

[00134] Example 24. The method of any of examples 14-23, wherein the determining comprises: receiving, by the user device via the second subscriber identity from the second network node with respect to the second connection after the connection setup procedure is completed for the second connection, configuration or reconfiguration information that indicates capabilities or resources to be used with respect to the second connection; determining or predict the capability or resource utilization of the user device with respect to the second connection based on the received configuration or reconfiguration information with respect to the second connection; evaluating whether one or more conditional configurations including at least the first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account or considering the capability or resource utilization of the user device with respect to the second connection determined or predicted based on the received configuration or reconfiguration information; and delaying use of the one or more of the conditional configurations with respect to the first network node until after the evaluating.

[00135] Example 25. The method of any of examples 23-24, wherein the performing the action comprises: performing, by the user device, after the evaluating, the action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

[00136] Example 26. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of examples 14-25.

[00137] Example 27. An apparatus comprising means for performing the method of any of examples 14-25.

[00138] Example 28. An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any of examples 14-25.

[00139] FIG. 7 is a block diagram of a wireless station (e.g., AP, BS, e/gNB, NB- loT UE, UE or user device) 700 according to an example implementation. The wireless station 700 may include, for example, one or multiple RF (radio frequency) or wireless transceivers 702A, 702B, where each wireless transceiver includes a transmitter to transmit signals (or data) and a receiver to receive signals (or data). The wireless station also includes a processor or control unit/entity (controller) 704 to execute instructions or software and control transmission and receptions of signals, and a memory 706 to store data and/or instructions.

[00140] Processor 704 may also make decisions or determinations, generate slots, subframes, packets or messages for transmission, decode received slots, subframes, packets or messages for further processing, and other tasks or functions described herein. Processor 704, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 702 (702A or 702B). Processor 704 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 702, for example). Processor 704 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 704 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 704 and transceiver 702 (702A or 702B) together may be considered as a wireless transmitter/receiver system, for example.

[00141] In addition, referring to FIG. 7, a controller (or processor) 708 may execute software and instructions, and may provide overall control for the station 700, and may provide control for other systems not shown in FIG. 7 such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 700, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.

[00142] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 704, or other controller or processor, performing one or more of the functions or tasks described above.

[00143] According to another example implementation, RF or wireless transceiver(s) 702A/702B may receive signals or data and/or transmit or send signals or data. Processor 704 (and possibly transceivers 702A/702B) may control the RF or wireless transceiver 702A or 702B to receive, send, broadcast or transmit signals or data.

[00144] The embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems. Another example of a suitable communications system is the 5G concept. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G uses multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in cooperation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.

[00145] It should be appreciated that future networks will most probably utilise network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into “building blocks” or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent.

[00146] Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software implementations that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks. In addition, implementations may be provided via machine type communications (MTC), and also via an Internet of Things (loT).

[00147] The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.

[00148] Furthermore, implementations of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers,...) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various implementations of techniques described herein may be provided via one or more of these technologies.

[00149] A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

[00150] Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[00151] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[00152] To provide for interaction with a user, implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. [00153] Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components. Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.

[00154] While certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall as intended in the various embodiments.

Claims

WHAT IS CLAIMED IS:

1. An apparatus, comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to cause the apparatus at least to: establish, by a user device having at least a first subscriber identity and a second subscriber identity, a first connection with a first network node via the first subscriber identity; initiate, by the user device, a connection setup procedure to establish a second connection with a second network node via the second subscriber identity; receive, by the user device via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node; determine, by the user device, that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection; and perform, by the user device, an action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

2. The apparatus of claim 1 wherein the at least one processor and the computer program code configured to cause the apparatus to initiate a connection setup procedure comprises the at least one processor and the computer program code configured to cause the apparatus to perform at least one of the following: make a decision to establish or attempt to establish a connection with the second network node via the second subscriber identity; transmit a random access preamble to the second network node in order to establish a connection with the second network node via the second subscriber identity; and/or transmit a RRC (radio resource control) connection request to the second network node in order to establish a connection with the second network node via the second subscriber identity.

3. The apparatus of any of claims 1-2, wherein the plurality of conditional configurations comprises one or more of the following conditional configuration types with respect to the first network node: a conditional handover (CHO); a conditional primary secondary cell (PSCell) change (CPC); or a conditional primary secondary cell (PSCell) addition (CPA).

4. The apparatus of any of claims 1-3, wherein the capability limitations of the user device comprise at least one of the following: a resource limitation of the user device that would be exceeded based on resource utilization of a connection that would be established, if triggered, based on at least the first conditional configuration with respect to the first network node, and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node; and/or an incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node.

5. The apparatus of claim 4, wherein the resource limitation comprises at least one of the following resource limitations of the user device: processing or processor limitations of the user device; memory limitations of the user device; protocol stack limitations of the user device; limitations of transmitter(s) and/or receiver(s) of the user device; or frequency band and/or bandwidth limitations, or limitations as to a maximum number of frequency bands for connections of the user device.

6. The apparatus of any of claims 4-5, wherein the incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection comprises: a frequency band combination incompatibility between one or more frequency bands used, predicted to be used, or allocated by the user device for the second connection to the second network node, and one or more frequency bands for at least the first conditional configuration with respect to the first network node.

7. The apparatus of any of claims 1-6, wherein the at least one processor and the computer program code configured to cause the apparatus to perform, by the user device, the action associated with releasing at least the first conditional configuration comprises the at least one processor and the computer program code configured to cause the apparatus to: send, by the user device to the first network node, an indication that the user device has released the conditional configuration of at least the first conditional configuration with respect to the first network node that is incompatible with capability limitations of the user device.

8. The apparatus of any of claims 1-6, wherein the at least one processor and the computer program code configured to cause the apparatus to perform, by the user device, the action associated with releasing at least the first conditional configuration comprises the at least one processor and the computer program code configured to cause the apparatus to: send, by the user device to the first network node, a list of one or more conditional configurations, including at least the first conditional configuration, that are requested to be released, or which should be released, due to incompatibility of such conditional configurations with the capability limitations of the user device.

9. The apparatus of claim 8, wherein the at least one processor and the computer program code are configured to cause the apparatus to: receive, by the user device from the first network node, a timer value indicating a delay time period the user device should delay releasing any of the conditional configurations with respect to the first network node including at least the first conditional configuration with respect to the first network node; upon expiration of a timer based on the timer value, determine, by the user device, whether the second connection to the second network node still exists; release, by the user device, at least the first conditional configuration if the second connection still exists at the timer expiration; and otherwise, maintain, by the user device, at least the first conditional configuration, or omit releasing at least the first conditional configuration, if the second connection has been disconnected or no longer exists at the timer expiration.

10. The apparatus of any of claims 1-6, wherein the at least one processor and the computer program code configured to cause the apparatus to perform, by the user device, the action associated with releasing the at least one of the plurality of conditional configurations comprises the at least one processor and the computer program code configured to cause the apparatus to: send, by the user device to the first network node, an indication to deprioritize use of the at least one conditional configuration due to incompatibility with capability limitations of the user device.

11. The apparatus of any of claims 1-10, wherein the at least one processor and the computer program code configured to determine comprises the at least one processor and the computer program code configured to: receive, by the user device via the second subscriber identity from the second network node with respect to the second connection after the connection setup procedure is completed for the second connection, configuration or reconfiguration information that indicates capabilities or resources to be used with respect to the second connection; determine or predict the capability or resource utilization of the user device with respect to the second connection based on the received configuration or reconfiguration information with respect to the second connection; evaluate whether one or more conditional configurations including at least the first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account or considering the capability or resource utilization of the user device with respect to the second connection determined or predicted based on the received configuration or reconfiguration information; and delay use of the one or more of the conditional configurations with respect to the first network node until after the evaluating.

12. The apparatus of claim 11, wherein the configuration or reconfiguration information with respect to the second connection is received via a RRC (radio resource control) reconfiguration message.

13. The apparatus of any of claims 11-12, wherein the at least one processor and the computer program code configured to perform the action comprises the at least one processor and the computer program code configured to: perform, by the user device, after the evaluating, the action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

14. A method, comprising: establishing, by a user device having at least a first subscriber identity and a second subscriber identity, a first connection with a first network node via the first subscriber identity; initiating, by the user device, a connection setup procedure to establish a second connection with a second network node via the second subscriber identity; receiving, by the user device via the first subscriber identity from the first network node, a plurality of conditional configurations including a conditional configuration for one or more candidate cells with respect to the first network node; determining, by the user device, that at least a first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account at least a current or predicted capability or resource utilization of the user device with respect to the second connection; and performing, by the user device, an action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

15. The method of claim 14 wherein the initiating comprises at least one of the following: making a decision to establish or attempt to establish a connection with the second network node via the second subscriber identity; transmitting a random access preamble to the second network node in order to establish a connection with the second network node via the second subscriber identity; and/or transmitting a RRC (radio resource control) connection request to the second network node in order to establish a connection with the second network node via the second subscriber identity.

16. The method of any of claims 14-15, wherein the plurality of conditional configurations comprises one or more of the following conditional configuration types with respect to the first network node: a conditional handover (CHO); a conditional primary secondary cell (PSCell) change (CPC); or a conditional primary secondary cell (PSCell) addition (CPA).

17. The method of any of claims 14-16, wherein the capability limitations of the user device comprise at least one of the following: a resource limitation of the user device that would be exceeded based on resource utilization of a connection that would be established, if triggered, based on at least the first conditional configuration with respect to the first network node, and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node; or an incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection between the user device and the second network node.

18. The method of claim 17, wherein the resource limitation comprises at least one of the following resource limitations of the user device: processing or processor limitations of the user device; memory limitations of the user device; protocol stack limitations of the user device; limitations of transmitter(s) and/or receiver(s) of the user device; or frequency band and/or bandwidth limitations, or limitations as to a maximum number of frequency bands for connections of the user device.

19. The method of any of claims 17-18, wherein the incompatibility between at least the first conditional configuration with respect to the first network node and the current or predicted capability or resource utilization and/or resource utilization pre-allocation of the user device with respect to the second connection comprises: a frequency band combination incompatibility between one or more frequency bands used, predicted to be used, or allocated by the user device for the second connection to the second network node, and one or more frequency bands for at least the first conditional configuration with respect to the first network node.

20. The method of any of claims 14-19, wherein the performing, by the user device, the action associated with releasing at least the first conditional configuration comprises: sending, by the user device to the first network node, an indication that the user device has released the conditional configuration of at least the first conditional configuration with respect to the first network node that is incompatible with capability limitations of the user device.

21. The method of any of claims 14-19, wherein the performing, by the user device, the action associated with releasing at least the first conditional configuration comprises: sending, by the user device to the first network node, a list of one or more conditional configurations, including at least the first conditional configuration, that are requested to be released, or which should be released, due to incompatibility of such conditional configurations with the capability limitations of the user device.

22. The method of claim 21, comprising: receiving, by the user device from the first network node, a timer value indicating a delay time period the user device should delay releasing any of the conditional configurations with respect to the first network node including at least the first conditional configuration with respect to the first network node; upon expiration of a timer based on the timer value, determining, by the user device, whether the second connection to the second network node still exists; releasing, by the user device, at least the first conditional configuration if the second connection still exists at the timer expiration; and otherwise, maintaining, by the user device, at least the first conditional configuration, or omitting releasing at least the first conditional configuration, if the second connection has been disconnected or no longer exists at the timer expiration.

23. The method of any of claims 14-19, wherein the performing, by the user device, the action associated with releasing the at least one of the plurality of conditional configurations comprises: sending, by the user device to the first network node, an indication to deprioritize use of the at least one conditional configuration due to incompatibility with capability limitations of the user device.

24. The method of any of claims 14-23, wherein the determining comprises: receiving, by the user device via the second subscriber identity from the second network node with respect to the second connection after the connection setup procedure is completed for the second connection, configuration or reconfiguration information that indicates capabilities or resources to be used with respect to the second connection; determining or predict the capability or resource utilization of the user device with respect to the second connection based on the received configuration or reconfiguration information with respect to the second connection; evaluating whether one or more conditional configurations including at least the first conditional configuration of the plurality of conditional configurations with respect to the first network node is currently incompatible with capability limitations of the user device, taking into account or considering the capability or resource utilization of the user device with respect to the second connection determined or predicted based on the received configuration or reconfiguration information; and delaying use of the one or more of the conditional configurations with respect to the first network node until after the evaluating.

25. The method of any of claims 23-24, wherein the performing the action comprises: performing, by the user device, after the evaluating, the action associated with releasing at least the first conditional configuration with respect to the first network node that is currently incompatible with capability limitations of the user device.

26. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of claims 14-25.

27. An apparatus comprising means for performing the method of any of claims 14-25.

28. An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any of claims 14-25.