WO2022086389A1 - Methods, apparatus and computer-readable media relating to conditional reconfigurations in wireless networks - Google Patents

Abstract

The disclosure provides, inter alia, a method performed by a wireless device. The wireless device receives (8001) one or more reconfiguration messages from a network node, the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device, the one or more conditional reconfigurations to be executed upon fulfilment of respective associated conditions. The wireless device monitors (8002) one or more of the conditions and determines (8003) a SCG mode of the SCG for the target PSCell. Upon fulfilment of one of the monitored conditions, the wireless device executes (8003) the conditional reconfiguration associated with the fulfilled condition to add or change to the target PSCell and operatein accordance with the determined SCG mode.

Description

METHODS, APPARATUS AND COMPUTER-READABLE MEDIA RELATING TO CONDITIONAL RECONFIGURATIONS IN WIRELESS NETWORKS Technical field Embodiments of the disclosure relate to wireless communication, and particularly to methods, apparatus and computer-readable media for conditional reconfigurations in wireless networks. Background Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description. Carrier Aggregation (CA) When CA is configured, the UE has only one RRC connection with the network. Further, at RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). In addition, depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. Further, when dual connectivity is configured, it could be the case that one carrier under the SCG is used as the Primary SCell (PSCell). Hence, in this case we have one PCell and one or more SCell(s) over the MCG and one PSCell and one or more SCell(s) over the SCG. The reconfiguration, addition and removal of SCells can be performed by RRC. At intra-RAT handover, RRC can also add, remove, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signalling is used for sending all required system information of the SCell i.e. while in connected mode, UEs need not acquire broadcasted system information directly from the SCells. 3GPP Dual Connectivity In 3GPP the dual-connectivity (DC) solution has been specified, both for LTE and between LTE and NR. In DC two nodes are involved, a master node (MN or MeNB) and a Secondary Node (SN, or SeNB). Multi- connectivity (MC) is the case when there are more than 2 nodes involved. Also, it has been proposed in 3GPP that DC is used in Ultra Reliable Low Latency Communications (URLLC) cases in order to enhance robustness and avoid connection interruptions.

There are different ways to deploy 5G network with or without interworking with LTE (also referred to as E-UTRA) and evolved packet core (EPC), as depicted in Figure 1. In principle, NR and LTE can be deployed without any interworking, denoted by NR stand-alone (SA) operation, that is a gNB in NR can be connected to the 5G core network (5GC) and an eNB can be connected to EPC with no interconnection between the two (Option 1 and Option 2 in Figure 1). On the other hand, the first supported version of NR is the so-called EN-DC (E-UTRAN- NR Dual Connectivity), illustrated by Option 3. In such a deployment, dual connectivity between NR and LTE is applied with LTE as the master and NR as the secondary node. The RAN node (gNB) supporting NR may not have a control plane connection to core network (EPC), instead it relies on the LTE as master node (MeNB). This is also called “Non-standalone NR". Notice that in this case the functionality of an NR cell is limited and would be used for connected mode UEs as a booster and/or diversity leg, but an RRCJDLE UE cannot camp on these NR cells.

With the introduction of 5GC (also known as 5GCN), other options may also be valid. As mentioned above, option 2 supports stand-alone NR deployment where a gNB is connected to the 5GC. Similarly, LTE can also be connected to 5GC using option 5 (also known as eLTE, E-UTRA/5GC, or LTE/5GC and the node can be referred to as an ng-eNB). In these cases, both NR and LTE are seen as part of the NG-RAN (and both the ng- eNB and the gNB can be referred to as NG-RAN nodes). It is worth noting that, Option 4 and option 7 are other variants of dual connectivity between LTE and NR which will be standardized as part of NG-RAN connected to 5GC, denoted by MR-DC (Multi-Radio Dual Connectivity). Under the MR-DC umbrella, we have:

• EN-DC (Option 3): LTE is the master node and NR is the secondary (EPC CN employed)

• NE-DC (Option 4): NR is the master node and LTE is the secondary (5GCN employed)

• NGEN-DC (Option 7): LTE is the master node and NR is the secondary (5GCN employed)

• NR-DC (variant of Option 2): Dual connectivity where both the master and secondary are NR (5GCN employed).

As migration for these options may differ between different operators, it is possible to have deployments with multiple options in parallel in the same network e.g. there could be an eNB base station supporting option 3, 5 and 7 in the same network as an NR base station supporting 2 and 4. In combination with dual connectivity solutions between LTE and NR it is also possible to support CA in each cell group (i.e. MCG and SCG) and dual connectivity between nodes on the same RAT (e.g. NR-NR DC). For the LTE cells, a consequence of these different deployments is the co-existence of LTE cells associated with eNBs connected to EPC, 5GC or both EPC/5GC.

As stated earlier, DC is standardized for both LTE and E-UTRA -NR DC (EN-DC).

LTE DC and EN-DC are designed differently when it comes to which nodes control what. Basically, there are two options:

1. Centralized solution (like LTE-DC),

2. Decentralized solution (like EN-DC). Figure 2 shows the schematic control plane architecture for LTE DC and EN-DC. The main difference is that, in EN-DC, the SN has a separate RRC entity (NR RRC). This means that the SN can also control the UE, sometimes without the knowledge of the MN, but often the SNs need to coordinate with the MN. In LTE-DC, the RRC decisions always come from the MN (MN to UE). Note, however, the SN still decides the configuration of the SN, since it is only the SN itself that has knowledge of what kind of resources, capabilities etc. it has.

For EN-DC, the major changes compared to LTE DC are:

• The introduction of split bearer from the SN (known as SCG split bearer)

• The introduction of split bearer for RRC

• The introduction of a direct RRC from the SN (also referred to as SCG SRB)

Figures 3 and 4 show the User Plane (UP) and Control Plane (CP) architectures for EN-DC.

The SN is sometimes referred to as SgNB (where gNB is an NR base station), and the MN as MeNB in the case that the LTE is the master node and NR is the secondary node. In the other case where NR is the master and LTE is the secondary node, the corresponding terms are SeNB and MgNB.

Split RRC messages are mainly used for creating diversity, and the sender can decide either to choose one of the links for scheduling the RRC messages, or to duplicate the message over both links. In the downlink, the path switching between the MCG or SCG legs or duplication on both is left to network implementation. On the other hand, for the uplink, the network configures the UE to use the MCG, SCG or both legs. The terms “leg”, “path” and “RLC bearer” are used interchangeably throughout this document.

SCG power saving mode

In order to improve network energy efficiency and UE battery life for UEs in MR-DC, a Rel-17 work item is planned to introduce efficient SCG/SCell activation/deactivation. This can be especially important for MR-DC configurations with NR SCG, as it has been evaluated in 3GPP TDoc submission RP-190919 by China Telecom that in some cases NR UE power consumption is three to four times higher than LTE.

3GPP has specified the concepts of dormant SCell (in LTE) and dormancy like behavior of an SCell (for NR).

In LTE, when an SCell is in the dormant state, like in the deactivated state, the UE does not need to monitor the corresponding PDCCH or PDSCH and cannot transmit in the corresponding uplink. However, differently from the deactivated state, the UE is required to perform and report CQI measurements. A PUCCH SCell (SCell configured with PUCCH) cannot be in the dormant state.

In NR, dormancy like behaviour for SCells is realized using the concept of dormant BWPs. See Figure 5. One dormant BWP, which is one of the dedicated BWPs configured by the network for the UE via RRC signaling, can be configured for an SCell. If the active BWP of the activated SCell is a dormant BWP, the UE stops monitoring PDCCH on the SCell but continues performing CSI measurements, AGC and beam management, if configured. A DCI is used to control entering/leaving the dormant BWP for one or more SCell(s) or one or more SCell group(s), and it is sent via the special cell (sPCell) of the cell group that the SCell belongs to (i.e. PCell in case the SCell belongs to the MCG and PSCell if the SCell belongs to the SCG). The SpCell (i.e. PCell of PSCell) and PUCCH SCell cannot be configured with a dormant BWP.

However, only SCells can be put into the dormant state (in LTE) or operate in dormancy like behavior (NR). Also, only SCells can be put into the deactivated state in both LTE and NR. Thus, if the UE is configured with MR-DC, it is not possible to fully benefit from the power saving options of dormant state or dormancy like behavior, as the PSCell cannot be configured with that feature. Instead, an existing solution could be releasing (for power savings) and adding (when traffic demand requires) the SCG on a need basis. However, traffic is likely to be bursty, and adding and releasing the SCG involves a significant amount of RRC signaling and inter-node messaging between the MN and the SN, which causes considerable delay.

In rel-16, some discussions were made regarding also putting the PSCell into dormancy, referred to as SCG Suspension. Some preliminary agreements were made in RAN2-107bis, Oct 2019 (see chairman notes at R2-1914301):

R2 assumes the following (can be slightly modified due to progress on Scell dormancy):

The UE supports network-controlled suspension of the SCG in RRCJDONNECTED.

UE behavior for a suspended SCG is FFS

The UE supports at most one SCG configuration, suspended or not suspended, in Rel 16.

In RRCJDONNECTED upon addition of the SCG, the SCG can be either suspended or not suspended by configuration.

In RAN2-108, further discussion was made to clarify the above FFS items.

Some solutions have been proposed in Rel-16, but these have different problems. For example, in 3GPP TDoc submission R2-1908679 by Qualcomm (Introducing suspension of SCG - Qualcomm) it is proposed that the gNB can instruct the UE to suspend SCG transmissions when no data traffic is expected to be sent in SCG so that the UE keeps the SCG configuration but does not use it for power saving purpose. Therein, it is mentioned that signaling to suspend SCG could be based on DCI/MAC-CE/RRC signaling, but no details were provided regarding the configuration from the gNB to the UE. And, differently from the defined behavior for SCell(s), PSCell(s) may be associated to a different network node (e.g. a gNodeB operating as Secondary Node).

It is yet to be seen which behavior will be specified for SCG power saving in rel-17. However, it may involve one or more of the following:

The UE starting to operate the PSCell in dormancy, e.g. switching the PSCell to a dormant BWP. On the network side, the network considers the PSCell in dormancy and at least stops transmitting PDCCH for that UE in the PSCell(s);

The UE deactivating the PSCell like SCell deactivation. On the network side, the network considers the PSCell as deactivated and at least stops transmitting PDCCH for that UE in the PSCell; The UE operating the PSCell in long DRX; SCG DRX can be switched off from the MN (e.g. via MCG MAC CE or DCI) when the need arises (e.g. DL data arrival for SN terminated SCG bearers);

The UE suspending its operation with the SCG (e.g. suspending bearers associated with the SCG, like SCG MN-/SN-terminated bearers), but keeping the SCG configuration stored (referred to as Stored SCG). On the network side there can be different alternatives such as the SN storing the SCG as the UE does, or the SN releasing the SCG context of the UE to be generated again upon resume (e.g. with the support from the MN that is the node storing the SCG context for that UE whose SCG is suspended).

Though the power saving aspect has so far been discussed only from the SCG point of view, similar approaches may be used on the MCG as well (e.g. the MCG may be suspended or in long DRX, while data communication is happening only via the SCG).

Conditional Handover (CHO)

Handovers are normally triggered when the UE is at the cell edge and experiences poor radio conditions. If the UE enters poor radio conditions quickly the conditions may already be so poor that the actual handover procedure may be hard to execute. If the UL is already bad it may lead to the network being unable to detect the measurement report transmitted by the UE and hence unable to initiate the handover procedure. DL problems may lead to the handover command (i.e. the RRCReconfiguration message with a reconfigurationWithSync field) failing to reach the UE. In poor radio conditions the DL message is more often segmented, which increases the risk of retransmissions with an increased risk that the message doesn't reach the UE in time. Failed transmission of handover command is a common reason for unsuccessful handovers.

To improve mobility robustness and address the issues above, a concept known as conditional handover (CHO) was introduced in 3GPP Release 16. The key idea in CHO is that transmission and execution of the handover command are separated. This allows the handover command to be sent earlier to the UE when the radio conditions are still good, thus increasing the likelihood that the message is successfully transferred. The execution of the handover command is done at a later point in time based on an associated execution condition. The execution condition is typically in the form of a threshold, e.g. signal strength of candidate target cell becomes X dB better than the serving cell (so called A3 event) or signal strength of serving cell becomes worse than X dBm and signal strength of candidate target cell becomes better than Y dBm (so called A5 event).

In the context of this document, a cell for which conditional handover (or other conditional mobility procedure) is configured is denoted “candidate target cell” or “potential target cell”. Similarly, a radio network node controlling a candidate/potential target cell is denoted “candidate target node” or “potential target node”. Once the CHO execution condition has been fulfilled for a candidate/potential target cell and CHO execution towards this candidate/potential target cell has been triggered, this cell is no longer “potential” or a “candidate” in the normal senses of these words, since it is no longer uncertain whether the CHO will be executed towards it. Hence, after the CHO execution condition has been fulfilled/triggered, the concerned candidate/potential target cell is herein sometimes referred to as “target cell”. Figure 6 shows the signaling flow for a conditional handover.

Steps 6001-6002. The UE and source gNB have an established connection and are exchanging user data. Due to some trigger, e.g. a measurement report from the UE, the source gNB decides to configure one or multiple CHO candidate cells. The threshold used for the measurement reporting should be chosen lower than the one in the handover execution condition. This allows the serving cell to prepare the handover when the radio link to the UE is still stable. The execution of the handover is done at a later point in time (and threshold) which is considered optimal for the handover execution.

Step 6003. The source gNB sends a CHO REQUEST to the target gNB with necessary information to prepare a conditional handover at the target side. The information includes among other things the current source configuration and the UE capabilities.

Step 6004. The target gNB prepares the handover and responds with a CHO REQUEST ACKNOWLEDGE to the source gNB, which includes the handover command (a RRCReconfiguration message) to be sent to the UE and later executed if/when the execution condition would be fulfilled. The handover command includes information needed by the UE to access the target cell, e.g., random access configuration, a new C-RNTI assigned by the target access node and security parameters enabling the UE to calculate the target security key so the UE can send the handover complete message (a RRCReconfigurationComplete message).

Steps 6005-6006. To configure a candidate target cell the source node sends the CHO configuration (i.e. a RRCReconfiguration message) to the UE which contains the handover command and the associated execution condition. The handover command (also an RRCReconfiguration message) is the same as the one generated by the target node during the handover preparation phase in steps 6003-6004 and the execution condition is generated by the source node.

Steps 6007-6008. Later on, if the execution condition is met, the UE executes the handover by performing random access and sending the handover complete message (i.e. an RRCReconfigurationComplete message) to the target node.

Step 6009. The target gNB sends a HANDOVER SUCCESS message to the source gNB indicating the UE has successfully established the target connection.

Steps 6010-6011. Upon reception of the handover success indication, the source gNB stops scheduling any further DL or UL data to the UE and sends a SN STATUS TRANSFER message to the target gNB indicating the latest PDCP SN transmitter and receiver status. The source node now also starts to forward User Data to the target node.

Step 6012. Upon receiving the handover complete message, the target node can start exchanging user data with the UE. The target node also requests the AMF to switch the DL data path from the UPF from the source node to the target node (not shown). Once the path switch is completed the target node sends the UE CONTEXT RELEASE to the source node.

The conditional handover concept in 3GPP Rel-16 has been generalized into a generic conditional reconfiguration framework, wherein a UE may be configured in advance with other types of reconfigurations which can be executed by an RRCReconfiguration message (in NR) or an RRCConnectionReconfiguration message (in LTE) upon a certain associated condition is triggered.

The network can configure the UE with one or more conditional reconfiguration(s) in the RRC Reconfiguration message, as can be seen in the RRCReconfiguration message in TS 38.331 v16.1.0. The RRCReconfiguration message then includes the conditionalReconfiguration-r16 to add, change and/or remove conditional reconfiguration(s), where added or changed conditional reconfigurations are included in condReconfigToAddModList-r16.

Conditional PSCell Addition/Change

Conditional PSCell Change (CPC) is another type of reconfiguration which uses the conditional reconfiguration framework in Rel-16. In CPC, when an execution condition is met, rather than a handover a PSCell change is executed.

In Rel-16, the procedure for CPC was introduced, and this is illustrated in Figure 7. In Rel-16, CPC is limited to intra-SN without MN involvement and uses the following steps (referring to Figure 7):

Steps 7001-7002. The Secondary Node (SN) prepares the UE with one or multiple CPC configurations, each containing a CPC condition (e.g. indicated by one or multiple measurement identifiers associated to an event of type A3 or A5), and an association to an RRCReconfiguration message to perform a conditional PSCell change to a given target cell upon fulfilment of the entry condition associated to the one or multiple measurement identities. Upon configuration, the UE stores these CPC configurations and acknowledges the reception of those conditions by transmitting an RRCReconfigurationComplete message to the SN. The UE is not required to verify the compliance of each target candidate’s RRCReconfiguration upon reception of the configuration.

Steps 7003-7004. The UE evaluates the fulfilment of the stored CPC conditions for the target cell(s) prepared in steps 7001-7002. If a CPC condition is met, the UE executes the PSCell change to the particular target cell by applying the RRCReconfiguration message that was associated with the condition.

Steps 7005-7006. The UE performs a random access procedure in the target cell and transmits an RRCReconfigurationComplete message in the target cell to the SN to confirm that the PSCell change has been performed. The UE then deletes all stored CPC configurations.

The conditional procedure for SN modification is expected to be faster compared to legacy procedures. In legacy PSCell Change, once a better cell in the same frequency as the PSCell triggers an event, a measurement report and preparation of the target SN are needed before the RRCReconfiguration message to execute addition/modification can be sent to the UE. Summary

There currently exist certain challenge(s). In 3GPP Rel-17, as part of the MR-DC enhancements Work Item, Intra-SN Conditional PSCell Change without MN involvement is expected to be further enhanced to support other scenarios such as Conditional PSCell addition, inter-SN Conditional PSCell change (SN or MN initiated) and intra-SN Conditional PSCell change (MN initiated).

Conditional PSCell Addition is one Rel-17 feature being discussed as well as the remaining scenarios for Conditional PSCell Change. At the same time a power saving mode for the SCG, herein referred to as “SCG deactivated mode” is discussed. For example, it has been proposed that a UE with an SCG in SCG deactivated mode, in order to save power, does not need to monitor the Physical Downlink Control Channel (PDCCH). In addition, procedures are being discussed with the purpose of efficient SCG activation/deactivation, in other words a fast change between “SCG deactivated mode” and the non- power saving (normal) mode, herein referred to as “SCG activated mode”.

When introducing the SCG deactivated mode, it has yet not been discussed how to enable the use of SCG deactivated mode in combination with the execution of conditional reconfigurations, such as Conditional PSCell Addition/Change, including the use of SCG deactivated mode for the target SCG or target PSCell for these procedures.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Some embodiments of the disclosure provide mechanisms to enable procedures for conditional reconfigurations, such as conditional PSCell Addition or conditional PSCell Change, in combination with an SCG in SCG deactivated mode.

Some embodiments of the disclosure provide methods for the UE to determine the SCG mode (SCG deactivated mode or SCG activated mode) for the target SCG, or target PSCell, during execution of conditional PSCell Addition and conditional PSCell Change.

Some embodiments of the disclosure provide methods for the network to control the UE to determine the mode (SCG deactivated mode or SCG activated mode) for the target SCG, or target PSCell, during execution of conditional PSCell Addition and conditional PSCell Change.

There are, proposed herein, various embodiments which address one or more of the issues disclosed herein.

One aspect provides a method performed by a wireless device. The method comprises: receiving one or more reconfiguration messages from a network node, the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell (PSCell) of a secondary cell group (SCG) associated with the wireless device. The one or more conditional reconfigurations are to be executed upon fulfilment of respective associated conditions. The method further comprises: monitoring one or more of the conditions; determining a SCG mode of the SCG for the target PSCell; and, upon fulfilment of one of the monitored conditions, executing the conditional reconfiguration associated with the fulfilled condition to add or change to the target PSCell and operating in accordance with the determined SCG mode.

Apparatus and device-readable media for performing the method set out above are also provided. For example, a further aspect of the disclosure provides a wireless device, comprising: power supply circuitry configured to supply power to the wireless device; and processing circuitry. The processing circuitry is configured to cause the wireless device to: receive one or more reconfiguration messages from a network node, the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell (PSCell) of a secondary cell group (SCG) associated with the wireless device. The one or more conditional reconfigurations are to be executed upon fulfilment of respective associated conditions. The processing circuitry is further configured to cause the wireless device to: monitor one or more of the conditions; determine a SCG mode of the SCG for the target PSCell; and, upon fulfilment of one of the monitored conditions, execute the conditional reconfiguration associated with the fulfilled condition to add or change to the target PSCell and operating in accordance with the determined SCG mode.

A second aspect provides a method performed by a base station. The method comprises: causing transmission of one or more reconfiguration messages to a wireless device. The one or more reconfiguration messages comprise an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell (PSCell) of a secondary cell group (SCG) associated with the wireless device. The target PSCell is served by the base station. The one or more conditional reconfigurations are to be executed by the wireless device upon fulfilment of respective associated conditions. The method further comprises: after execution of a conditional reconfiguration by the wireless device, determining a SCG mode for the target PSCell; and operating the target PSCell for the wireless device in accordance with the determined SCG mode.

Apparatus and device-readable media for performing the method set out above are also provided. For example, a further aspect of the disclosure provides a base station comprising power supply circuitry configured to supply power to the base station; and processing circuitry. The processing circuitry is configured to cause the base station to: cause transmission of one or more reconfiguration messages to a wireless device. The one or more reconfiguration messages comprise an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell (PSCell) of a secondary cell group (SCG) associated with the wireless device. The target PSCell is served by the base station. The one or more conditional reconfigurations are to be executed by the wireless device upon fulfilment of respective associated conditions. The processing circuitry is further configured to cause the base station to: after execution of a conditional reconfiguration by the wireless device, determine a SCG mode for the target PSCell; and operate the target PSCell for the wireless device in accordance with the determined SCG mode.

Certain embodiments may provide one or more of the following technical advantage(s). Some embodiments of the disclosure reduce the amount of signalling and UE power at conditional reconfigurations, such as conditional PSCell Addition or conditional PSCell Change, in conjunction with an SCG in SCG deactivated mode.

Some embodiments of the disclosure enable the possibility to perform conditional PSCell Addition with a target SCG configured in SCG deactivated mode upon addition, without the need to deactive the SCG after addition.

Some embodiments of the disclosure enable the possibility to perform conditional PSCell Change when source and/or target SCG is configured in SCG deactivated mode, without the need to activate or deactivate the SCG after addition.

Brief description of the drawings

For a better understanding of examples of the present disclosure, and to show more clearly how the examples may be carried into effect, reference will now be made, by way of example only, to the following drawings in which:

Figure 1 shows LTE and NR interworking options;

Figure 2 shows a control plane architecture for dual connectivity in LTE DC and EN DC;

Figure 3 shows the network-side protocol termination options for MCG, SCG and split bearers in MR DC with EPC (EN DC);

Figure 4 shows the network architecture for control plane in EN DC;

Figure 5 shows the dormancy like behaviour for SCells in NR;

Figure 6 is a signalling diagram showing conditional handover in NR;

Figure 7 is a signalling diagram showing intra-SN conditional PSCell Change without MN involvement;

Figure 8 is a flowchart of a method performed by a wireless device according to embodiments of the disclosure;

Figure 9 is a message sequence chart for conditional PSCell addition according to embodiments of the disclosure;

Figure 10 is a message sequence chart for conditional PSCell change according to embodiments of the disclosure;

Figure 11 is a flowchart of a method performed by a network node according to embodiments of the disclosure;

Figure 12 is a schematic diagram of a wireless network in accordance with some embodiments;

Figure 13 is a schematic diagram of a user equipment in accordance with some embodiments;

Figure 14 is a schematic diagram of a virtualization environment in accordance with some embodiments;

Figure 15 schematically illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments; Figure 16 schematically illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;

Figures 17 - 20 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

Figure 21 is a flowchart of a method performed by a wireless device according to further embodiments of the disclosure;

Figure 22 is a schematic diagram showing a virtualization apparatus in accordance with some embodiments;

Figure 23 is a flowchart of a method performed by a network node or base station according to further embodiments of the disclosure; and

Figure 24 is a schematic diagram showing a virtualization apparatus in accordance with some embodiments.

Detailed description

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Figure 8 illustrates the main steps of a method performed by a wireless device or UE, such as the wireless device 1210 or the user equipment 1300 described below. Further information regarding the method may be found below with respect to Figure 21.

Step 8001 . The UE is configured, by a network node, with conditional configuration(s), each containing a condition, such as a reference to a configured measurement, and an associated RRC message to be applied upon execution, such as an RRC message to perform conditional PSCell addition or conditional PSCell change. The UE may have a Secondary Cell Group (SCG) configured. The SCG mode may either be SCG deactivated mode or SCG activated mode.

Step 8002. The UE starts to monitor the conditions according to the conditional configuration(s) including performing measurements.

Step 8003. When a monitored condition is fulfilled, the UE executes the conditional configuration by applying the RRC message associated with the fulfilled condition, such as performing a conditional PSCell Change or conditional PSCell Addition as instructed by the RRC message. As part of the execution, the UE determines the SCG mode of the SCG with the target PSCell (also known as the "target SCG"), as further described below. UE may also determine how to respond to a network node, such as a target SN, as further described below.

A message sequence chart for conditional PSCell addition according to embodiments of the disclosure is illustrated in Figure 9. Steps 9001-9002: The MN, assisted by the SN, prepares one or more candidate target PSCells controlled by target secondary nodes. Selection of these PSCell candidates may be based on received measurement reports from the UE. During the preparation of a candidate target PSCell, an RRCReconfiguration message is generated, corresponding to the one that would be sent to the UE for the PSCell addition procedure.

Steps 9003-9004: The MN then sends an RRCReconfiguration message to the UE containing one or several conditional configuration(s), including one or more configurations for each candidate target PSCell. Each conditional configuration in turn includes the generated RRCReconfiguration message in steps 9001-9002 as well as a triggering condition. The triggering condition may be a measurement event (such as A3/A5) including thresholds. The UE stores the conditional configuration(s).

Step 9005: The UE then monitors the triggering conditions for all configured candidate target

PSCells according to the stored conditional configuration(s).

Step 9006: When a triggering condition becomes fulfilled for a given candidate target PSCell, the UE executes the PSCell addition of that PSCell. As part of the execution, the UE determines the SCG mode of the SCG with that particular PSCell.

Steps 9007-9008: The UE determines how to respond to the network. As an outcome of the determination, the UE may perform a random access procedure in the particular PSCell and transmit the RRCReconfiguration message, part of the stored conditional reconfiguration for the particular PSCell, to the SN (as illustrated in Error! Reference source not found.), or alternatively, to the MN.

A message sequence chart according to embodiments of the disclosure for conditional PSCell change from a source PSCell, controlled by a source SN, S-SN, to a target PSCell, controlled by a target SN, T-SN, is illustrated in Figure 10.

Step 10001 : This step is optional. In one alternative, the source SN (S-SN) may determine the need to perform PSCell change. The source SN may base this on received measurement reports from the UE. The S-N transmits an S-NODE CHANGE REQUIRED message to the Master Node, MN, and may also indicate a number of candidate target PSCells in this message.

Steps 10002-10003: The MN, together with one or multiple target secondary nodes, SN(s), prepares, one or more candidate target PSCells controlled by the respective target SN. Selection of these PSCell candidates may be based on received measurement reports from the UE by the MN and/or the indicated candidate target PSCells from the source SN in the previous step. During the preparation of a candidate target PSCell, the target SN generates an RRCReconfiguration message, corresponding to the one that would be sent to the UE for the PSCell change procedure to that particular candidate target PSCell. These steps may be repeated for each candidate target PSCell.

Steps 10004-10005: The MN asks the source SN to generate an RRCReconfiguration message for the conditional PSCell change procedure, including one or more conditional configurations for each candidate target PSCell. Each conditional configuration in turn includes the generated RRCReconfiguration message in steps 10002-10003 as well as a triggering condition. The triggering condition may be a measurement event (such as A3/A5) including thresholds.

Steps 10006-10007: The MN transmits the RRCReconfiguration message received from the source SN in step 10005 to the UE. The UE stores the conditional configuration(s) and replies with an RRCReconfigurationComplete message to the MN.

Step 10008: The MN transmits an S-NODE MODIFICATION CONFIRM message to the source

SN to indicate that the preparation of the conditional PSCell change procedure is complete.

Step 10009: The UE then monitors the triggering conditions for all configured candidate target

PSCells according to the stored conditional configuration(s).

Step 10010: When a triggering condition becomes fulfilled for a given candidate target PSCell, the UE executes the PSCell change of that PSCell. As part of the execution, the UE determines the SCG mode of the SCG with that particular PSCell.

Steps 10011-10013: The UE determines how to respond to the network. As an outcome of the determination, the UE may transmit an RRCReconfigurationComplete message to the target SN via the MN encapsulated in an ULInformationTransfer message. In this case the MN forwards the RRCReconfigurationComplete message to the target SN and it also transmit an S-NODE CHANGE CONFIRM message to the source SN to indicate that the execution of the conditional PSCell change procedure has been started. As an outcome of the determination, the UE may also perform, in step 10014, a random access procedure in the target PSCell, to the target SN.

The main steps of a method according to embodiments of the disclosure performed by a network node, such as a target secondary node at conditional PSCell addition or conditional PSCell change, are shown in Figure 11.

Step 11001 : The network node generates one or more conditional configuration(s), each containing a condition and associated reconfiguration (e.g., RRC message).

Step 11002: The network node transmits the conditional configuration(s) to the UE.

Step 11003: The network node waits for execution of one of the conditional reconfiguration(s).

Step 11004: After the network node is informed about successful execution of the conditional reconfiguration, it determines the SCG mode of the SCG with the target PSCell (also known as the "target SCG"), as further described below.

Methods for the UE to determine the SCG mode of the SCG with the target PSCell

In step 8003, 9006 or 10010, the UE determines the SCG mode of the SCG with the target PSCell. There are multiple alternative methods for how this may be achieved.

In one alternative, the SCG mode of the SCG with the target PSCell is always SCG activated mode. This can then be related to the fact that the procedure concerns a conditional PSCell change or a conditional PSCell addition, i.e. that in case the execution is based on one or more conditions and thus typically may take place some time after the configuration is sent to the UE. In other words, in case of a conditional PSCell change or conditional PSCell addition, the SCG mode/state will always be activated in the target PSCell as part of the execution, whereas it might be deactivated in case of a non-conditional PSCell change or PSCell addition.

In another alternative, an indication of the SCG mode (for example an information element with a value interpreted as “SCG activated mode” or “SCG deactivated mode”) is received by the UE from a network node and then stored by the UE. For example, the indication may be part of the conditional reconfiguration (e.g. in the RRCReconfigu ration message) transmitted from a network node to the UE, e.g. in step 8001, 9003 or 10006. The SCG mode of the SCG with the target PSCell is determined by the UE based on this indication upon execution of the conditional reconfiguration.

In yet another alternative, the UE determines the SCG mode of the SCG with the target PSCell based on the SCG mode of the SCG with the source PSCell at the time when the condition(s) are fulfilled. This alternative may be used in some cases, including at conditional PSCell change. For example, if the SCG mode of the SCG with the source PSCell is SCG activated mode when the condition(s) are fulfilled, the SCG mode of the SCG with the target PSCell is also set to SCG activated mode. And for example, if the SCG mode of the SCG with the source PSCell is SCG deactivated mode when the condition(s) are fulfilled, the SCG mode of the SCG with the target PSCell is also set to SCG deactivated mode. The SCG mode/state may then be different at the point in time where the condition(s) is/are fulfilled than when the configuration was built. In yet another alternative, the SCG mode of the SCG with the target PSCell is determined by a traffic volume condition upon execution of the conditional reconfiguration. For example, if the buffer status is above a certain threshold the SCG mode is activated directly when the condition(s) are fulfilled. The threshold may be configurable.

Methods for a network node to determine the SCG mode of the SCG with the target PSCell

The UE and the target SN should be aligned on the SCG mode/state that is in use since the procedures are dependent on this, e.g. whether the UE will monitor the PDCCH or not. In case the SCG mode/state to use after execution of the (conditional) PSCell change or PSCell addition configuration is dependent on aspects that are not controlled/configured by the target SN, the target SN then needs to be informed about the SCG mode/state that is applicable after the execution. As an example, in case the same SCG mode/state that the UE has in the source PSCell/SN at the time of the execution should be used in the target PSCell/SN . This is since the SCG mode state may have changed in the source SN from the time of the configuration of the conditional PSCell change/addition until the corresponding execution.

In step 11004, the network node determines the SCG mode of the SCG with the target PSCell. There are multiple alternative methods for how the network node may determine the SCG mode.

In one alternative, the network node determines the SCG mode of the SCG with the target PSCell based on how the network node is informed about successful execution of the conditional reconfiguration. For example, if the UE transmits a message in the target PSCell controlled by this network node, such as if the UE performs a random access and/or transmits an RRC message (such as RRCReconfigurationComplete) in the target PSCell, the network node determines that the SCG mode of the SCG with the target PSCell is SCG activated mode. In an alternative, the UE sends an RRCReconfigurationComplete message (or similar) to the network (typically from the UE via the MN to the target SN) in any case to indicate initiation of execution of conditional reconfiguration, but indicates in the complete message whether the new SCG is deactivated (or not). See example below.

In one example, if the UE performs a random access only (but not followed by an RRC message), the network node determines that the SCG mode of the SCG with the target PSCell is SCG deactivated mode. And in this example, if the UE performs a random access which is followed by an RRC message, the network node determines that the SCG mode of the SCG with the target PSCell is SCG activated mode.

In another example, the UE performs the random access procedure to the target SN, as part of (or after) the execution of the conditional PSCell change procedure/addition, only if the SCG mode/state is activated. In case the SCG mode/state is activated at the time of the execution of the PSCell change or PSCell addition, the UE then performs the random access procedure to the target SN (PSCell), whereas if the SCG mode/state is deactivated the UE does not perform the random access procedure to the target SN (PSCell). The target SN will typically anyway be informed about the execution of the conditional PSCell change from the MN. This way the target SN will be informed that the UE has initiated execution of the PSCell change and can then consider the SCG mode/state as deactivated unless the UE performs the random access procedure. There will anyway typically not be a need to perform the random access procedure towards the PSCell/SN in case the SCG is deactivated.

In another example, the MN sends information about the current SCG mode/state to the target SN. This information can then e.g. be included in signaling sent when execution of the conditional reconfiguration (e.g. PSCell change or PSCell addition) is performed, such as in the XnAP S-NODE RECONFIGURATION COMPLETE message. If the network node (e.g. the target SN) then receives a message from another network node (such as a S-NODE RECONFIGURATION COMPLETE message from the MN at step 10013), including an indication of the SCG mode of the SCG with the target PSCell (or an indication about the SCG mode/state that the UE has in the source SN/PSCel I at the time of the execution), the network node (e.g. the target SN) determines the SCG mode of the SCG with the target PSCell based on the value of the received indication.

In yet another example, if the network node (e.g. the target SN) receives a message from another network node (such as a S-NODE RECONFIGURATION COMPLETE message from the MN at step 10013), the network node (e.g. the target SN) determines that the SCG mode of the SCG with the target PSCell is SCG deactivated mode.

In another alternative, which can be combined with other alternatives, the network node includes an indication of the SCG mode (for example an information element with a value interpreted as “SCG activated mode” or “SCG deactivated mode”) transmitted to the UE. For example, included as part of the conditional reconfiguration (e.g. in the RRCReconfiguration message), e.g. in step 8001, 9003 or 10006.

In yet another alternative, the MN or the source SN sends information to the target SN in case there is a change to the current SCG mode/state while the UE has a conditional PSCell change or PSCell addition configuration towards that SN. This way the target SN is kept up to date on the current SCG mode/state and it would then be possible to apply the same SCG mode/state in the target SN (PSCell) as in the source SN (PSCell) at execution of e.g. a conditional PSCell change.

Methods to determine how to respond to the network

After execution of the conditional reconfiguration, there are multiple methods for the UE to respond to the network. Specifically, the UE may respond to the network with a method that is determined based on the SCG mode of the SCG with the target PSCell. For example, the UE may respond in the target PSCell (with a random access procedure and/or an RRC message or MAC CE, such as e.g. RRCReconfigurationComplete in steps 9007- 9008) directly to the target SN if the SCG mode of the SCG with the target PSCell is SCG activated mode. Alternatively, the UE may respond in another cell, such as the PCell, with an RRC message (such as ULInformationTransfer containing an RRCReconfigurationComplete message in step 10011) to the target SN via the MN. In one example, the UE responds only in another cell if the SCG mode of the SCG with the target PSCell is SCG deactivated mode.

In one alternative the UE performs a random access procedure to the target SN (PSCell), independent of the SCG mode of the target PSCel l/SCG, and then includes an indication about the SCG mode (e.g. activated or deactivated). The indication can then be sent directly to the target SN (PSCell), for example in an RRC message or a MAC CE. The UE could then, in one embodiment, determine whether to include the indication about the SCG mode to the target PSCell/SCG based on information received from the network (e.g. the target PSCell/SCG or the PCell/MCG), e.g. in the RRC Reconfiguration message that includes the conditional reconfiguration or in a message received in the target PSCell/SCG.

RRC signalling

Below is an example how to indicate the SCG state in the RRCReconfigurationComplete message by adding a new field here named scgDeactivated:

RRCReconfigurationComplete

The RRCReconfigurationComplete message is used to confirm the successful completion of an RRC connection reconfiguration.

Signalling radio bearer: SRB1 or SRB3

RLC-SAP: AM

Logical channel: DCCH

Direction: UE to Network

RRCReconfigurationComplete message

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 12. For simplicity, the wireless network of Figure 12 only depicts network 1206, network nodes 1260 and 1260b, and WDs 1210, 1210b, and 1210c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 1260 and wireless device (WD) 1210 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 1206 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 1260 and WD 1210 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In Figure 12, network node 1260 includes processing circuitry 1270, device readable medium 1280, interface 1290, auxiliary equipment 1284, power source 1286, power circuitry 1287, and antenna 1262. Although network node 1260 illustrated in the example wireless network of Figure 12 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 1260 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 1280 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 1260 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 1260 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 1260 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 1280 for the different RATs) and some components may be reused (e.g., the same antenna 1262 may be shared by the RATs). Network node 1260 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1260, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1260.

Processing circuitry 1270 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 1270 may include processing information obtained by processing circuitry 1270 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 1270 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1260 components, such as device readable medium 1280, network node 1260 functionality. For example, processing circuitry 1270 may execute instructions stored in device readable medium 1280 or in memory within processing circuitry 1270. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1270 may include a system on a chip (SOC).

In some embodiments, processing circuitry 1270 may include one or more of radio frequency (RF) transceiver circuitry 1272 and baseband processing circuitry 1274. In some embodiments, radio frequency (RF) transceiver circuitry 1272 and baseband processing circuitry 1274 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1272 and baseband processing circuitry 1274 may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 1270 executing instructions stored on device readable medium 1280 or memory within processing circuitry 1270. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1270 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 1270 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1270 alone or to other components of network node 1260, but are enjoyed by network node 1260 as a whole, and/or by end users and the wireless network generally.

Device readable medium 1280 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1270. Device readable medium 1280 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1270 and, utilized by network node 1260. Device readable medium 1280 may be used to store any calculations made by processing circuitry 1270 and/or any data received via interface 1290. In some embodiments, processing circuitry 1270 and device readable medium 1280 may be considered to be integrated. Interface 1290 is used in the wired or wireless communication of signalling and/or data between network node 1260, network 1206, and/or WDs 1210. As illustrated, interface 1290 comprises port(s)/terminal(s) 1294 to send and receive data, for example to and from network 1206 over a wired connection. Interface 1290 also includes radio front end circuitry 1292 that may be coupled to, or in certain embodiments a part of, antenna 1262. Radio front end circuitry 1292 comprises filters 1298 and amplifiers 1296. Radio front end circuitry 1292 may be connected to antenna 1262 and processing circuitry 1270. Radio front end circuitry may be configured to condition signals communicated between antenna 1262 and processing circuitry 1270. Radio front end circuitry 1292 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1292 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1298 and/or amplifiers 1296. The radio signal may then be transmitted via antenna 1262. Similarly, when receiving data, antenna 1262 may collect radio signals which are then converted into digital data by radio front end circuitry 1292. The digital data may be passed to processing circuitry 1270. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 1260 may not include separate radio front end circuitry 1292, instead, processing circuitry 1270 may comprise radio front end circuitry and may be connected to antenna 1262 without separate radio front end circuitry 1292. Similarly, in some embodiments, all or some of RF transceiver circuitry 1272 may be considered a part of interface 1290. In still other embodiments, interface 1290 may include one or more ports or terminals 1294, radio front end circuitry 1292, and RF transceiver circuitry 1272, as part of a radio unit (not shown), and interface 1290 may communicate with baseband processing circuitry 1274, which is part of a digital unit (not shown).

Antenna 1262 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1262 may be coupled to radio front end circuitry 1290 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1262 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 1262 may be separate from network node 1260 and may be connectable to network node 1260 through an interface or port.

Antenna 1262, interface 1290, and/or processing circuitry 1270 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1262, interface 1290, and/or processing circuitry 1270 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment. Power circuitry 1287 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 1260 with power for performing the functionality described herein. Power circuitry 1287 may receive power from power source 1286. Power source 1286 and/or power circuitry 1287 may be configured to provide power to the various components of network node 1260 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1286 may either be included in, or external to, power circuitry 1287 and/or network node 1260. For example, network node 1260 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 1287. As a further example, power source 1286 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1287. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 1260 may include additional components beyond those shown in Figure 12 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 1260 may include user interface equipment to allow input of information into network node 1260 and to allow output of information from network node 1260. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1260.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customerpremise equipment (CPE), a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehide-to- vehicle (V2V), vehide-to-infrastructure (V2I), vehide-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 1210 includes antenna 1211, interface 1214, processing circuitry 1220, device readable medium 1230, user interface equipment 1232, auxiliary equipment 1234, power source 1236 and power circuitry 1237. WD 1210 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1210, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 1210.

Antenna 1211 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1214. In certain alternative embodiments, antenna 1211 may be separate from WD 1210 and be connectable to WD 1210 through an interface or port. Antenna 1211, interface 1214, and/or processing circuitry 1220 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 1211 may be considered an interface.

As illustrated, interface 1214 comprises radio front end circuitry 1212 and antenna 1211. Radio front end circuitry 1212 comprise one or more filters 1218 and amplifiers 1216. Radio front end circuitry 1214 is connected to antenna 1211 and processing circuitry 1220, and is configured to condition signals communicated between antenna 1211 and processing circuitry 1220. Radio front end circuitry 1212 may be coupled to or a part of antenna 1211. In some embodiments, WD 1210 may not include separate radio front end circuitry 1212; rather, processing circuitry 1220 may comprise radio front end circuitry and may be connected to antenna 1211. Similarly, in some embodiments, some or all of RF transceiver circuitry 1222 may be considered a part of interface 1214. Radio front end circuitry 1212 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1212 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1218 and/or amplifiers 1216. The radio signal may then be transmitted via antenna 1211. Similarly, when receiving data, antenna 1211 may collect radio signals which are then converted into digital data by radio front end circuitry 1212. The digital data may be passed to processing circuitry 1220. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 1220 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 1210 components, such as device readable medium 1230, WD 1210 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1220 may execute instructions stored in device readable medium 1230 or in memory within processing circuitry 1220 to provide the functionality disclosed herein.

As illustrated, processing circuitry 1220 includes one or more of RF transceiver circuitry 1222, baseband processing circuitry 1224, and application processing circuitry 1226. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1220 of WD 1210 may comprise a SOC. In some embodiments, RF transceiver circuitry 1222, baseband processing circuitry 1224, and application processing circuitry 1226 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1224 and application processing circuitry 1226 may be combined into one chip or set of chips, and RF transceiver circuitry 1222 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1222 and baseband processing circuitry 1224 may be on the same chip or set of chips, and application processing circuitry 1226 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 1222, baseband processing circuitry 1224, and application processing circuitry 1226 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 1222 may be a part of interface 1214. RF transceiver circuitry 1222 may condition RF signals for processing circuitry 1220.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 1220 executing instructions stored on device readable medium 1230, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1220 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 1220 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1220 alone or to other components of WD 1210, but are enjoyed by WD 1210 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 1220 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1220, may include processing information obtained by processing circuitry 1220 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1210, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 1230 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1220. Device readable medium 1230 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1220. In some embodiments, processing circuitry 1220 and device readable medium 1230 may be considered to be integrated.

User interface equipment 1232 may provide components that allow for a human user to interact with WD 1210. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 1232 may be operable to produce output to the user and to allow the user to provide input to WD 1210. The type of interaction may vary depending on the type of user interface equipment 1232 installed in WD 1210. For example, if WD 1210 is a smart phone, the interaction may be via a touch screen; if WD 1210 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 1232 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1232 is configured to allow input of information into WD 1210, and is connected to processing circuitry 1220 to allow processing circuitry 1220 to process the input information. User interface equipment 1232 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 1232 is also configured to allow output of information from WD 1210, and to allow processing circuitry 1220 to output information from WD 1210. User interface equipment 1232 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 1232, WD 1210 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment 1234 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 1234 may vary depending on the embodiment and/or scenario.

Power source 1236 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 1210 may further comprise power circuitry 1237 for delivering power from power source 1236 to the various parts of WD 1210 which need power from power source 1236 to carry out any functionality described or indicated herein. Power circuitry 1237 may in certain embodiments comprise power management circuitry. Power circuitry 1237 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1210 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 1237 may also in certain embodiments be operable to deliver power from an external power source to power source 1236. This may be, for example, for the charging of power source 1236. Power circuitry 1237 may perform any formatting, converting, or other modification to the power from power source 1236 to make the power suitable for the respective components of WD 1210 to which power is supplied. Figure 13 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 1300 may be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 1300, as illustrated in Figure 13, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 13 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 13, UE 1300 includes processing circuitry 1301 that is operatively coupled to input/output interface 1305, radio frequency (RF) interface 1309, network connection interface 1311, memory 1315 including random access memory (RAM) 1317, read-only memory (ROM) 1319, and storage medium 1321 or the like, communication subsystem 1331, power source 1333, and/or any other component, or any combination thereof. Storage medium 1321 includes operating system 1323, application program 1325, and data 1327. In other embodiments, storage medium 1321 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 13, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In Figure 13, processing circuitry 1301 may be configured to process computer instructions and data. Processing circuitry 1301 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1301 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 1305 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 1300 may be configured to use an output device via input/output interface 1305. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 1300. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 1300 may be configured to use an input device via input/output interface 1305 to allow a user to capture information into UE 1300. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In Figure 13, RF interface 1309 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1311 may be configured to provide a communication interface to network 1343a. Network 1343a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1343a may comprise a Wi-Fi network. Network connection interface 1311 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 1311 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 1317 may be configured to interface via bus 1302 to processing circuitry 1301 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 1319 may be configured to provide computer instructions or data to processing circuitry 1301. For example, ROM 1319 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 1321 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 1321 may be configured to include operating system 1323, application program 1325 such as a web browser application, a widget or gadget engine or another application, and data file 1327. Storage medium 1321 may store, for use by UE 1300, any of a variety of various operating systems or combinations of operating systems.

Storage medium 1321 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUI M) module, other memory, or any combination thereof. Storage medium 1321 may allow UE 1300 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 1321, which may comprise a device readable medium. In Figure 13, processing circuitry 1301 may be configured to communicate with network 1343b using communication subsystem 1331. Network 1343a and network 1343b may be the same network or networks or different network or networks. Communication subsystem 1331 may be configured to include one or more transceivers used to communicate with network 1343b. For example, communication subsystem 1331 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 1333 and/or receiver 1335 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1333 and receiver 1335 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 1331 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 1331 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 1343b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1343b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 1313 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1300.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 1300 or partitioned across multiple components of UE 1300. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 1331 may be configured to include any of the components described herein. Further, processing circuitry 1301 may be configured to communicate with any of such components over bus 1302. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 1301 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 1301 and communication subsystem 1331. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

Figure 14 is a schematic block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes 1430. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 1420 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 1420 are run in virtualization environment 1400 which provides hardware 1430 comprising processing circuitry 1460 and memory 1490. Memory 1490 contains instructions 1495 executable by processing circuitry 1460 whereby application 1420 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 1400, comprises general-purpose or special-purpose network hardware devices 1430 comprising a set of one or more processors or processing circuitry 1460, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 1490-1 which may be non-persistent memory for temporarily storing instructions 1495 or software executed by processing circuitry 1460. Each hardware device may comprise one or more network interface controllers (NICs) 1470, also known as network interface cards, which include physical network interface 1480. Each hardware device may also include non-transitory, persistent, machine-readable storage media 1490-2 having stored therein software 1495 and/or instructions executable by processing circuitry 1460. Software 1495 may include any type of software including software for instantiating one or more virtualization layers 1450 (also referred to as hypervisors), software to execute virtual machines 1440 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 1440, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1450 or hypervisor. Different embodiments of the instance of virtual appliance 1420 may be implemented on one or more of virtual machines 1440, and the implementations may be made in different ways.

During operation, processing circuitry 1460 executes software 1495 to instantiate the hypervisor or virtualization layer 1450, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1450 may present a virtual operating platform that appears like networking hardware to virtual machine 1440.

As shown in Figure 14, hardware 1430 may be a standalone network node with generic or specific components. Hardware 1430 may comprise antenna 14225 and may implement some functions via virtualization. Alternatively, hardware 1430 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 14100, which, among others, oversees lifecycle management of applications 1420.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 1440 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 1440, and that part of hardware 1430 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1440, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1440 on top of hardware networking infrastructure 1430 and corresponds to application 1420 in Figure 14.

In some embodiments, one or more radio units 14200 that each include one or more transmitters 14220 and one or more receivers 14210 may be coupled to one or more antennas 14225. Radio units 14200 may communicate directly with hardware nodes 1430 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system 14230 which may alternatively be used for communication between the hardware nodes 1430 and radio units 14200.

With reference to FIGURE 15, in accordance with an embodiment, a communication system includes telecommunication network 1510, such as a 3GPP-type cellular network, which comprises access network 1511, such as a radio access network, and core network 1514. Access network 1511 comprises a plurality of base stations 1512a, 1512b, 1512c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1513a, 1513b, 1513c. Each base station 1512a, 1512b, 1512c is connectable to core network 1514 over a wired or wireless connection 1515. A first UE 1591 located in coverage area 1513c is configured to wirelessly connect to, or be paged by, the corresponding base station 1512c. A second UE 1592 in coverage area 1513a is wirelessly connectable to the corresponding base station 1512a. While a plurality of UEs 1591, 1592 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1512.

Telecommunication network 1510 is itself connected to host computer 1530, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 1530 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1521 and 1522 between telecommunication network 1510 and host computer 1530 may extend directly from core network 1514 to host computer 1530 or may go via an optional intermediate network 1520. Intermediate network 1520 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1520, if any, may be a backbone network or the Internet; in particular, intermediate network 1520 may comprise two or more sub-networks (not shown).

The communication system of Figure 15 as a whole enables connectivity between the connected UEs 1591, 1592 and host computer 1530. The connectivity may be described as an over-the-top (OTT) connection 1550. Host computer 1530 and the connected UEs 1591, 1592 are configured to communicate data and/or signaling via OTT connection 1550, using access network 1511, core network 1514, any intermediate network 1520 and possible further infrastructure (not shown) as intermediaries. OTT connection 1550 may be transparent in the sense that the participating communication devices through which OTT connection 1550 passes are unaware of routing of uplink and downlink communications. For example, base station 1512 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1530 to be forwarded (e.g., handed over) to a connected UE 1591. Similarly, base station 1512 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1591 towards the host computer 1530.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 16. In communication system 1600, host computer 1610 comprises hardware 1615 including communication interface 1616 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1600. Host computer 1610 further comprises processing circuitry 1618, which may have storage and/or processing capabilities. In particular, processing circuitry 1618 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 1610 further comprises software 1611, which is stored in or accessible by host computer 1610 and executable by processing circuitry 1618. Software 1611 includes host application 1612. Host application 1612 may be operable to provide a service to a remote user, such as UE 1630 connecting via OTT connection 1650 terminating at UE 1630 and host computer 1610. In providing the service to the remote user, host application 1612 may provide user data which is transmitted using OTT connection 1650.

Communication system 1600 further includes base station 1620 provided in a telecommunication system and comprising hardware 1625 enabling it to communicate with host computer 1610 and with UE 1630. Hardware 1625 may include communication interface 1626 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1600, as well as radio interface 1627 for setting up and maintaining at least wireless connection 1670 with UE 1630 located in a coverage area (not shown in Figure 16) served by base station 1620. Communication interface 1626 may be configured to facilitate connection 1660 to host computer 1610. Connection 1660 may be direct or it may pass through a core network (not shown in Figure 16) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1625 of base station 1620 further includes processing circuitry 1628, which may comprise one or more programmable processors, applicationspecific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 1620 further has software 1621 stored internally or accessible via an external connection.

Communication system 1600 further includes UE 1630 already referred to. Its hardware 1635 may include radio interface 1637 configured to set up and maintain wireless connection 1670 with a base station serving a coverage area in which UE 1630 is currently located. Hardware 1635 of UE 1630 further includes processing circuitry 1638, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 1630 further comprises software 1631, which is stored in or accessible by UE 1630 and executable by processing circuitry 1638. Software 1631 includes client application 1632. Client application 1632 may be operable to provide a service to a human or non-human user via UE 1630, with the support of host computer 1610. In host computer 1610, an executing host application 1612 may communicate with the executing client application 1632 via OTT connection 1650 terminating at UE 1630 and host computer 1610. In providing the service to the user, client application 1632 may receive request data from host application 1612 and provide user data in response to the request data. OTT connection 1650 may transfer both the request data and the user data. Client application 1632 may interact with the user to generate the user data that it provides.

It is noted that host computer 1610, base station 1620 and UE 1630 illustrated in Figure 16 may be similar or identical to host computer 1530, one of base stations 1512a, 1512b, 1512c and one of UEs 1591, 1592 of Figure 15, respectively. This is to say, the inner workings of these entities may be as shown in Figure 16 and independently, the surrounding network topology may be that of Figure 15.

In Figure 16, OTT connection 1650 has been drawn abstractly to illustrate the communication between host computer 1610 and UE 1630 via base station 1620, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 1630 or from the service provider operating host computer 1610, or both. While OTT connection 1650 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 1670 between UE 1630 and base station 1620 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 1630 using OTT connection 1650, in which wireless connection 1670 forms the last segment. More precisely, the teachings of these embodiments may improve the reliability of a radio connection and thereby provide benefits such as fewer call drops, smoother video streaming, etc.

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

Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 15 and 16. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section. In step 1710, the host computer provides user data. In substep 1711 (which may be optional) of step 1710, the host computer provides the user data by executing a host application. In step 1720, the host computer initiates a transmission carrying the user data to the UE. In step 1730 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 15 and 16. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section. In step 1810 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1820, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1830 (which may be optional), the UE receives the user data carried in the transmission.

Figure 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 15 and 16. For simplicity of the present disclosure, only drawing references to Figure 19 will be included in this section. In step 1910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1920, the UE provides user data. In substep 1921 (which may be optional) of step 1920, the UE provides the user data by executing a client application. In substep 1911 (which may be optional) of step 1910, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1930 (which may be optional), transmission of the user data to the host computer. In step 1940 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 20 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 15 and 16. For simplicity of the present disclosure, only drawing references to Figure 20 will be included in this section. In step 2010 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 2020 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Figure 21 depicts a method in accordance with particular embodiments. The method may be performed by a wireless device, such as the wireless device 1210 or the user equipment 1300 described above. Figure 21 is complementary and may correspond to the method shown in Figure 8 in some respects, and/or the signalling of the UE in Figures 9 and 10.

The method begins at step 2102, in which the wireless device receives one or more reconfiguration messages (e.g., RRC messages) from a network node. The one or more reconfiguration messages comprise an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device. The one or more conditional reconfigurations are to be executed upon fulfilment of respective associated conditions. Thus the one or more reconfiguration messages may comprise indications of the conditional reconfiguration (e.g., addition or change of a PSCell from the SCG), as well as the associated condition. The condition may relate to relate to radio parameters measured by the wireless device. For example, the condition may be in the form of a threshold, e.g. signal strength of candidate target cell becomes X dB better than the serving cell (so called A3 event) or signal strength of serving cell becomes worse than X dBm and signal strength of candidate target cell becomes better than Y dBm (so called A5 event).

The wireless device may transmit one or more reconfiguration complete messages in response to receipt of the reconfiguration messages.

In step 2104, the wireless device monitors one or more of the conditions. Here it is noted that the wireless device may not monitor all of those conditions specified in the reconfiguration messages, but may monitor only a subset of the conditions, e.g., based on its connection state with the network.

In step 2106, the wireless device determines an SCG mode of the target PSCell and/or the SCG for the PSCell.

In step 2108, upon fulfilment of one of the monitored conditions, the wireless device executes the reconfiguration associated with the fulfilled condition, and operates in the target PSCell in accordance with the determined SCG mode. The SCG mode may be one of: activated mode and deactivated mode. Activated mode may correspond to a normal mode of operation, e.g., non-dormant, whereas deactivated mode may correspond to a low-power, or dormant mode of operation (“dormancy like behaviour” in NR). In this context, deactivated mode comprise one or more of the following: the wireless device performs and reports radio measurements for one or more cells of the SCG, but refrains from monitoring downlink control and shared channels for the one or more cells of the SCG; network nodes serving one or more cells of the SCG refrain from transmitting downlink control channels for the one or more cells; one or more cells of the SCG are configured with a dormant bandwidth part, BWP; the wireless device operates one or more cells of the SCG in a long discontinuous reception, DRX, mode; the wireless device suspends operation in one or more cells of the SCG, and stores a context for the one or more cells of the SCG.

Conversely, activated mode may comprise the wireless device and/or network node performing the opposite of these statements, e.g., the wireless device monitors downlink control and shared channels (and the network nodes transmit those channels), the cells are not configured with a dormant BWP, the cells are not operated in long DRX, and/or the wireless device does not suspend operation in the cells of the SCG.

In some embodiments, step 2106 may be performed in conjunction with step 2108, such that the SCG mode is determined at the same time as, or as part of, executing the reconfiguration associated with the fulfilled condition.

In one embodiment, step 2106 comprises selecting a same SCG mode as used in a source PSCell at execution of the conditional reconfiguration. Alternatively or additionally, step 2106 may comprise selecting a same SCG mode as used in a source PSCell at fulfilment of the one of the monitored conditions. Alternatively or additionally, step 2106 may comprise selecting a default SCG mode, such as an activated mode. Alternatively or additionally, step 2106 may comprise receiving, from the network node, an indication of the SCG mode for the target PSCell. For example, the indication of the SCG mode for the target PSCell may be received in the one or more reconfiguration messages. Alternatively or additionally, step 2106 may comprise selecting the SCG mode as a function of traffic volume at the wireless device, such as a volume of data in one or more transmit buffers of the wireless device. For example, the traffic volume at the wireless device may be compared to one or more thresholds and the SCG mode selected based on the comparison. Traffic volume in excess of a threshold may lead to the wireless device selected activated mode; traffic volume less than the threshold may lead to the wireless device selecting deactivated mode.

In some embodiments, the wireless device may further inform a target network node serving the target PSCell of the determined SCG mode.

For example, the wireless device may implicitly inform the target network node of the determined SCG mode by selectively performing a random-access procedure with the PSCell or not performing a random-access procedure with the PSCell according to the determined SCG mode. In another example, the wireless device may implicitly inform the target network node of the determined SCG mode by selectively transmitting a radio resource control, RRC, message to the PSCell or not transmitting a RRC message to the target network node according to the determined SCG mode.

In a further example, the wireless device may implicitly inform the target network node of the determined SCG mode by transmitting an information message to a master node configured for the wireless device, prompting the master node to communicate with the target network node.

Figure 22 illustrates a schematic block diagram of an apparatus 2200 in a wireless network (for example, the wireless network shown in Figure 12). The apparatus may be implemented in a wireless device (e.g., wireless device 1210 shown in Figure 12 or user equipment 1300). Apparatus 2200 is operable to carry out the example method described with reference to Figure 21 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 21 is not necessarily carried out solely by apparatus 2200. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 2200 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving unit 2202, monitoring unit 2204, determining unit 2206 and executing unit 2208, and any other suitable units of apparatus 2200 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in Figure 22, apparatus 2200 includes receiving unit 2202, monitoring unit 2204, determining unit 2206 and executing unit 2208. Receiving unit 2202 is configured to receive one or more reconfiguration messages from a network node, the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device, the one or more conditional reconfigurations to be executed upon fulfilment of respective associated conditions. Monitoring unit 2204 is configured to monitor one or more of the conditions. Determining unit 2206 is configured to determine an SCG mode of the SCG for the target PSCell. Executing unit 2208 is configured to, upon fulfilment of one of the monitored conditions, execute the conditional reconfiguration associated with the fulfilled condition to add or change to the target PSCell and operating in accordance with the determined SCG mode.

Figure 23 depicts a method in accordance with particular embodiments. The method may be performed by a network node or base station, such as the network node 1260 described above. The network node may be a target network node serving a target PSCell for a wireless device during reconfiguration of an SCG of the wireless device to add or change a PSCell for the SCG. Figure 23 is complementary and may correspond to the method shown in Figure 11 in some respects, and/or the signalling of the target secondary node (T-SN) in Figures 9 and 10.

The method begins at step 2302, in which the network node causes transmission of one or more reconfiguration messages (e.g., RRC messages) to a wireless device. The one or more reconfiguration messages comprise an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device. The target PSCell is served by the network node, and the one or more conditional reconfigurations are to be executed by the wireless device upon fulfilment of respective associated conditions. Thus the one or more reconfiguration messages may comprise indications of the conditional reconfiguration (e.g., addition or change of a PSCell from the SCG), as well as the associated condition. The condition may relate to relate to radio parameters measured by the wireless device. For example, the condition may be in the form of a threshold, e.g. signal strength of candidate target cell becomes X dB better than the serving cell (so called A3 event) or signal strength of serving cell becomes worse than X dBm and signal strength of candidate target cell becomes better than Y dBm (so called A5 event).

For example, step 2302 may comprise the network node causing the master node to transmit the one or more reconfiguration messages to the wireless device (e.g., by transmitting an indication of one or more conditional reconfigurations to the master node for onward transmission to the wireless device).

The network node may then receive one or more reconfiguration complete messages from the wireless device in response to receipt of the reconfiguration messages.

In step 2304, after execution of a conditional reconfiguration by the wireless device, the network node determines a SCG mode for the target PSCell. In step 2306, the wireless device operates the target PSCell for the wireless device in accordance with the determined SCG mode.

The SCG mode may be one of: activated mode and deactivated mode. Activated mode may correspond to a normal mode of operation, e.g., non-dormant, whereas deactivated mode may correspond to a low-power, or dormant mode of operation (“dormancy like behaviour” in NR). In this context, deactivated mode comprise one or more of the following: the wireless device performs and reports radio measurements for one or more cells of the SCG, but refrains from monitoring downlink control and shared channels for the one or more cells of the SCG; network nodes serving one or more cells of the SCG (such as the target PSCell) refrain from transmitting downlink control channels for the one or more cells; one or more cells of the SCG are configured with a dormant bandwidth part, BWP; the wireless device operates one or more cells of the SCG in a long discontinuous reception, DRX, mode; the wireless device suspends operation in one or more cells of the SCG, and stores a context for the one or more cells of the SCG.

Conversely, activated mode may comprise the wireless device and/or network node performing the opposite of these statements, e.g., the wireless device monitors downlink control and shared channels (and the network nodes transmit those channels), the cells are not configured with a dormant BWP, the cells are not operated in long DRX, and/or the wireless device does not suspend operation in the cells of the SCG. Step 2304 may comprise the network node receiving an indication of the determined SCG mode from the wireless device. For example, the indication of the determined SCG mode may comprise the wireless device selectively performing a random-access procedure with the target PSCell or not performing a random-access procedure with the target PSCell according to the determined SCG mode. Alternatively, the indication of the determined SCG mode may comprise the wireless device selectively transmitting a radio resource control, RRC, message to the target network node or not transmitting a RRC message to the target network node according to the determined SCG mode.

Alternatively or additionally, step 2304 may comprise the network node receiving an indication of the determined SCG mode from a master node configured for the wireless device. The indication of the determined SCG mode from the master node may be implicit or explicit.

Alternatively or additionally, an indication of the determined SCG mode may be included in the one or more reconfiguration messages transmitted to the wireless device.

Figure 24 illustrates a schematic block diagram of an apparatus 2400 in a wireless network (for example, the wireless network shown in Figure 12). The apparatus may be implemented in a network node (e.g., network node 1260 shown in Figure 12). Apparatus 2400 is operable to carry out the example method described with reference to Figure 23 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 23 is not necessarily carried out solely by apparatus 2400. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 2400 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause causing unit 2402, determining unit 2404 and executing unit 2406, and any other suitable units of apparatus 2400 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in Figure 24, apparatus 2400 includes causing unit 2402, determining unit 2404 and executing unit 2406. Causing unit 2402 is configured to cause transmission of one or more reconfiguration messages to a wireless device, the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device, the target PSCell being served by the base station, the one or more conditional reconfigurations to be executed by the wireless device upon fulfilment of respective associated conditions. Determining unit 2404 is configured to, after execution of a conditional reconfiguration by the wireless device, determining a SCG mode for the target PSCell. Executing unit 2406 is configured to operate the target PSCell for the wireless device in accordance with the determined SCG mode.

The term “unit” may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

For the avoidance of doubt, the following statements set out embodiments of the disclosure:

Group A Embodiments

1. A method performed by a wireless device, the method comprising:

- receiving one or more reconfiguration messages from a network node, the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device, the one or more conditional reconfigurations to be executed upon fulfilment of respective associated conditions;

- monitoring one or more of the conditions;

- determining a SCG mode of the SCG for the target PSCell; and

- upon fulfilment of one of the monitored conditions, executing the conditional reconfiguration associated with the fulfilled condition to add or change to the target PSCell and operating in accordance with the determined SCG mode.

2. The method of embodiment 1 , wherein determining the SCG mode of the SCG for the target PSCell comprises selecting a same SCG mode as used in a source PSCell at execution of the conditional reconfiguration.

3. The method of embodiment 1 , wherein determining the SCG mode of the SCG for the target PSCell comprises selecting a same SCG mode as used in a source PSCell at fulfilment of the one of the monitored conditions.

4. The method of embodiment 1 , wherein determining the SCG mode of the SCG for the target PSCell comprises selecting a default SCG mode.

5. The method of embodiment 4, wherein the default SCG mode is an activated mode.

6. The method of embodiment 1 , wherein determining the SCG mode of the SCG for the target PSCell comprises receiving, from the network node, an indication of the SCG mode for the target PSCell.

7. The method of embodiment 6, wherein the indication of the SCG mode for the target PSCell is received in the one or more reconfiguration messages. 8. The method of embodiment 1 , wherein determining the SCG mode of the SCG for the target PSCell comprises selecting the SCG mode as a function of traffic volume at the wireless device.

9. The method of embodiment 8, wherein the traffic volume at the wireless device comprises a volume of data in one or more transmit buffers of the wireless device.

10. The method of embodiment 8 or 9, wherein the selecting the SCG mode as a function of traffic volume at the wireless device comprises comparing the traffic volume at the wireless device to one or more thresholds and selecting the SCG mode based on the comparison.

11. The method of any one of the preceding embodiments, further comprising informing a target network node serving the target PSCell of the determined SCG mode.

12. The method according to embodiment 11, wherein informing the target network node of the determined SCG mode comprises implicitly informing the target network node of the determined SCG mode by selectively performing a random-access procedure with the PSCell or not performing a random-access procedure with the PSCell according to the determined SCG mode.

13. The method according to embodiment 11, wherein informing the target network node of the determined SCG mode comprises implicitly informing the target network node of the determined SCG mode by selectively transmitting a radio resource control, RRC, message to the PSCell or not transmitting a RRC message to the target network node according to the determined SCG mode.

14. The method according to embodiment 11, wherein informing the target network node of the determined SCG mode comprises implicitly informing the target network node of the determined SCG mode by transmitting an information message to a master node configured for the wireless device, prompting the master node to communicate with the target network node.

15. The method of any one of the preceding embodiments, wherein the SCG mode is one of: activated mode and deactivated mode.

16. The method of embodiment 15 wherein, in the deactivated mode, one of more of the following apply: the wireless device performs and reports radio measurements for the target PSCell, but refrains from monitoring downlink control and shared channels for the target PSCell; a network node serving the target PSCell refrains from transmitting downlink control channels for the target PSCell; the target PSCell is configured with a dormant bandwidth part, BWP; the wireless device operates in a long discontinuous reception, DRX, mode in the target PSCell; the wireless device suspends operation in the target PSCell and stores a context for the target PSCell. 17. The method of any one of the preceding embodiments, wherein one or more of the conditions relate to radio parameters measured by the wireless device.

18. The method of any one of the preceding embodiments, wherein the one or more reconfiguration messages comprise radio resource control, RRC, reconfiguration messages.

19. The method of any one of the preceding embodiments, further comprising, responsive to receipt of the one or more reconfiguration messages, transmitting one or more reconfiguration complete messages to the network node, and thereafter monitoring the one or more of the conditions.

20. The method of any of the previous embodiments, further comprising:

- providing user data; and

- forwarding the user data to a host computer via the transmission to the base station.

Group B Embodiments

21. A method performed by a base station, the method comprising:

- causing transmission of one or more reconfiguration messages to a wireless device, the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device, the target PSCell being served by the base station, the one or more conditional reconfigurations to be executed by the wireless device upon fulfilment of respective associated conditions;

- after execution of a conditional reconfiguration by the wireless device, determining a SCG mode for the target PSCell; and

- operating the target PSCell for the wireless device in accordance with the determined SCG mode.

22. The method of embodiment 21 , wherein determining the SCG mode for the target PSCell comprises receiving an indication of the determined SCG mode from the wireless device.

23. The method according to embodiment 22, wherein the indication of the determined SCG mode comprises the wireless device selectively performing a random-access procedure with the target PSCell or not performing a random-access procedure with the target PSCell according to the determined SCG mode.

24. The method according to embodiment 22, wherein the indication of the determined SCG mode comprises the wireless device selectively transmitting a radio resource control, RRC, message to the target network node or not transmitting a RRC message to the target network node according to the determined SCG mode. 25. The method according to embodiment 21 , wherein determining the SCG mode for the target PSCell comprises receiving an indication of the determined SCG mode from a master node configured for the wireless device.

26. The method according to embodiment 25, wherein the indication of the determined SCG mode from the master node is implicit.

27. The method according to embodiment 25, wherein the indication of the determined SCG mode from the master node is explicit.

28. The method according to embodiment 21, wherein an indication of the determined SCG mode is included in the one or more reconfiguration messages transmitted to the wireless device.

29. The method according to any one of embodiments 21 to 28, wherein causing transmission of one or more reconfiguration messages to the wireless device comprises providing an indication of the one or more conditional reconfigurations to a master node configured for the wireless device, for onward transmission to the wireless device.

30. The method of any one of embodiments 21 to 29, wherein the SCG mode is one of: activated mode and deactivated mode.

31. The method of embodiment 30 wherein, in the deactivated mode, one of more of the following apply: the wireless device performs and reports radio measurements for the target PSCell, but refrains from monitoring downlink control and shared channels for the target PSCell; the base station serving the target PSCell refrains from transmitting downlink control channels for the target PSCell; the target PSCell is configured with a dormant bandwidth part, BWP; the wireless device operates in a long discontinuous reception, DRX, mode in the target PSCell; the wireless device suspends operation in the target PSCell and stores a context for the target PSCell.

32. The method of any one of embodiments 21 to 31, wherein one or more of the conditions relate to radio parameters measured by the wireless device.

33. The method of any one of embodiments 21 to 32, wherein the one or more reconfiguration messages comprise radio resource control, RRC, reconfiguration messages.

34. The method of any of the previous embodiments, further comprising:

- obtaining user data; and

- forwarding the user data to a host computer or a wireless device. Group C Embodiments

35. A wireless device, the wireless device comprising:

- processing circuitry configured to cause the wireless device to perform any of the steps of any of the Group A embodiments; and

- power supply circuitry configured to supply power to the wireless device.

36. A base station, the base station comprising:

- processing circuitry configured to cause the base station to perform any of the steps of any of the Group B embodiments;

- power supply circuitry configured to supply power to the base station.

37. A user equipment (UE), the UE comprising:

- an antenna configured to send and receive wireless signals;

- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;

- the processing circuitry being configured to cause the UE to perform any of the steps of any of the Group A embodiments;

- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;

- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and

- a battery connected to the processing circuitry and configured to supply power to the UE.

38. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

39. The communication system of the previous embodiment further including the base station.

40. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

41. The communication system of the previous 3 embodiments, wherein: - the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

- the UE comprises processing circuitry configured to execute a client application associated with the host application.

42. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, providing user data; and

- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

43. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

44. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

45. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

46. A communication system including a host computer comprising:

- processing circuitry configured to provide user data; and

- a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),

- wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.

47. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

48. The communication system of the previous 2 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and

- the UE’s processing circuitry is configured to execute a client application associated with the host application.

49. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, providing user data; and - at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

50. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

51. A communication system including a host computer comprising:

- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,

- wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.

52. The communication system of the previous embodiment, further including the UE.

53. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

54. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application; and

- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

55. The communication system of the previous 4 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and

- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

56. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

57. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

58. The method of the previous 2 embodiments, further comprising:

- at the UE, executing a client application, thereby providing the user data to be transmitted; and - at the host computer, executing a host application associated with the client application.

59. The method of the previous 3 embodiments, further comprising:

- at the UE, executing a client application; and

- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,

- wherein the user data to be transmitted is provided by the client application in response to the input data.

60. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

61. The communication system of the previous embodiment further including the base station.

62. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

63. The communication system of the previous 3 embodiments, wherein:

- the processing circuitry of the host computer is configured to execute a host application;

- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

64. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:

- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

65. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

66. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer. Abbreviations

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

5GC or 5GCN 5G core network

ACK Acknowledgement

AGC Automatic Gain Control

AMF Access and Mobility management Function

AP Application Protocol

BSR Buffer Status Report

BWP Bandwidth Part

CA Carrier Aggregation

CE Control Element

CHO Conditional Handover

CPA Conditional PSCell Addition

CN Core Network

CPC Conditional PSCell Change

CP Control Plane

CQI Channel Quality Indicator

C-RNTI Cell Radio Network Temporary Identifier

CSI Channel State Information

DC Dual Connectivity

DCI Downlink Control Information

DL Downlink

DRB Data Radio Bearer eNB (EUTRAN) base station

EPC Evolved Packet Core

E-RAB EUTRAN Radio Access Bearer

E-UTRA Evolved Universal Terrestrial Radio Access

E-UTRAN Evolved Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex gNB NR base station

GTP-U GPRS Tunneling Protocol - User Plane

IE Information Element

IP Internet Protocol

LTE Long Term Evolution

MCG Master Cell Group

MAC Medium Access Control

MAC CE MAC Control Element MeNB Master eNB

MgNB Master gNB

MN Master Node

MR-DC Multi-Radio Dual Connectivity

NACK Negative Acknowledgement

NAS Non Access Stratum

NG-RAN Next Generation Radio Access Network

Ng-eNB Next Generation Evolved Node B

NR New Radio

PDCP Packet Data Convergence Protocol

PCell Primary Cell

PCI Physical Cell Identity

PDCCH Physical Downlink Control Channel

PSCell Primary Secondary Cell (in LTE) or Primary SCG Cell (in NR)

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RAT Radio Access Technology

RB Radio Bearer

RLC Radio Link Control

RLF Radio Link Failure

RRC Radio Resource Control

SCell Secondary Cell

SCG Secondary Cell Group

SCTP Stream Control Transmission Protocol

SeNB Secondary eNB

SgNB Secondary gNB

SINR Signal to Interference plus Noise Ratio

SN Secondary Node

SR Scheduling Request

SRB Signaling Radio Bearer

S-SN Source Secondary Node

SUL Supplementary uplink

TDD Time Division Duplex

TEID Tunnel Endpoint IDentifier

TNL Transport Network Layer

T-SN Target Secondary Node

UCI Uplink Control Information

UDP User Datagram Protocol UPF User Plane Function

UE User Equipment

UL Uplink

UP User Plane

URLLC Ultra Reliable Low Latency Communication

X2 Interface between base stations

1x RTT CDMA2000 1x Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

ABS Almost Blank Subframe

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel

CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel E-SMLC evolved Serving Mobile Location Center E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FFS For Further Study GERAN GSM EDGE Radio Access Network gNB Base station in NR GNSS Global Navigation Satellite System GSM Global System for Mobile communication HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term Evolution MAC Medium Access Control MBMS Multimedia Broadcast Multicast Services MBSFN Multimedia Broadcast multicast service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network

PM I Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RAT Radio Access Technology

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR

Reference Signal Received Power RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SNR Signal to Noise Ratio

SON Self Optimized Network

SS Synchronization Signal SSS Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UE User Equipment

UL Uplink

UMTS Universal Mobile Telecommunication System

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WLAN Wide Local Area Network

Claims

53 CLAIMS

1. A method performed by a wireless device (1210, 1300, 2200), the method comprising:

- receiving (8001 , 9003, 10006, 2102) one or more reconfiguration messages from a network node (1260), the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device, the one or more conditional reconfigurations to be executed upon fulfilment of respective associated conditions;

- monitoring (8002, 9005, 10009, 2104) one or more of the conditions;

- determining (8003, 9006, 10010, 2106) a SCG mode of the SCG for the target PSCell; and

- upon fulfilment of one of the monitored conditions, executing (8003, 9006, 10010, 2108) the conditional reconfiguration associated with the fulfilled condition to add or change to the target PSCell and operating in accordance with the determined SCG mode.

2. The method of claim 1 , wherein determining the SCG mode of the SCG for the target PSCell comprises selecting a same SCG mode as used in a source PSCell at execution of the conditional reconfiguration.

3. The method of claim 1 , wherein determining the SCG mode of the SCG for the target PSCell comprises selecting a default SCG mode.

4. The method of claim 3, wherein the default SCG mode is an activated mode.

5. The method of claim 1 , wherein determining the SCG mode of the SCG for the target PSCell comprises receiving, from the network node, an indication of the SCG mode for the target PSCell.

6. The method of claim 1 , wherein determining the SCG mode of the SCG for the target PSCell comprises selecting the SCG mode as a function of traffic volume at the wireless device.

7. The method of any one of the preceding claims, further comprising informing a target network node serving the target PSCell of the determined SCG mode.

8. A method performed by a base station (1260, 2400), the method comprising:

- causing (9003, 10006, 11002, 2302) transmission of one or more reconfiguration messages to a wireless device (1210), the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device, the target PSCell being served by the base station, the one or more conditional reconfigurations to be executed by the wireless device upon fulfilment of respective associated conditions;

- after execution of a conditional reconfiguration by the wireless device, determining (2304) a SCG mode for the target PSCell; and 54

- operating (2306) the target PSCell for the wireless device in accordance with the determined SCG mode. The method of claim 8, wherein determining the SCG mode for the target PSCell comprises receiving an indication of the determined SCG mode from the wireless device. The method according to claim 8, wherein determining the SCG mode for the target PSCell comprises receiving an indication of the determined SCG mode from a master node configured for the wireless device. A wireless device adapted to perform a method according to any one of claims 1 to 7. A base station adapted to perform a method according to any one of claims 8 to 10. A wireless device (1210, 1300), the wireless device comprising:

- power supply circuitry (1237, 1313) configured to supply power to the wireless device; and

- processing circuitry (1220, 1301) configured to cause the wireless device to: receive one or more reconfiguration messages from a network node, the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device, the one or more conditional reconfigurations to be executed upon fulfilment of respective associated conditions; monitor one or more of the conditions; determine a SCG mode of the SCG for the target PSCell; and upon fulfilment of one of the monitored conditions, execute the conditional reconfiguration associated with the fulfilled condition to add or change to the target PSCell and operate in accordance with the determined SCG mode. The wireless device of claim 13, wherein the wireless device is caused to determine the SCG mode of the SCG for the target PSCell by selecting a same SCG mode as used in a source PSCell at execution of the conditional reconfiguration. The wireless device of claim 13, wherein the wireless device is caused to determine the SCG mode of the SCG for the target PSCell by selecting a default SCG mode. The wireless device of claim 15, wherein the default SCG mode is an activated mode. The wireless device of claim 13, wherein the wireless device is caused to determine the SCG mode of the SCG for the target PSCell by receiving, from the network node, an indication of the SCG mode for the target PSCell. 55 The wireless device of claim 13, wherein the wireless device is caused to determine the SCG mode of the SCG for the target PSCell by selecting the SCG mode as a function of traffic volume at the wireless device. The wireless device of any one of claims 13 to 18, the wireless device is further caused to inform a target network node serving the target PSCell of the determined SCG mode. A base station (1260), the base station comprising:

- power supply circuitry (1287) configured to supply power to the base station; and

- processing circuitry (1270) configured to cause the base station to: causing transmission of one or more reconfiguration messages to a wireless device, the one or more reconfiguration messages comprising an indication of one or more conditional reconfigurations for adding or changing to a target primary secondary cell or a primary secondary cell group cell, PSCell, of a secondary cell group, SCG, associated with the wireless device, the target PSCell being served by the base station, the one or more conditional reconfigurations to be executed by the wireless device upon fulfilment of respective associated conditions; after execution of a conditional reconfiguration by the wireless device, determining a SCG mode for the target PSCell; and operating the target PSCell for the wireless device in accordance with the determined SCG mode. The base station of claim 20, wherein the base station is caused to determine the SCG mode for the target PSCell by receiving an indication of the determined SCG mode from the wireless device. The base station of claim 20, wherein the base station is caused to determine the SCG mode for the target PSCell by receiving an indication of the determined SCG mode from a master node configured for the wireless device. A non-transitory device-readable medium (1230, 1321) storing instructions which, when executed by processing circuitry of a wireless device, cause the wireless device to perform the method according to any one of claims 1 to 7. A non-transitory device-readable medium (1280) storing instructions which, when executed by processing circuitry of a base station, cause the base station to perform the method according to any one of claims 8 to 10.