Configuring a wireless device with multi-radio access technology dual connectivity

Abstract

Methods and apparatus are disclosed, including in one example method comprising a method performed by a wireless device configured with multi-radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group. The method comprises receiving at least one message from a first network node in a reconfiguration procedure of the second cell group. The at least one message indicates a mode of operation for the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group.

Description

TECHNICAL FIELD

[0001] Examples of the present disclosure relate to wireless devices configured with multi-radio access technology dual connectivity (MR-DC). BACKGROUND

[0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the application, unless explicitly defined herein and / or explicitly made clear from the context of their usage. Any reference to an element should be interpreted as referring to at least one instance of such element unless explicitly stated otherwise. Steps of any method disclosed herein need not be performed in the exact order disclosed, unless explicitly stated otherwise. Any feature of any embodiment disclosed herein can be applied to any other embodiment, where suitable. Likewise, any advantage of any embodiment can apply to any other embodiment, and vice versa. Other objects, features and advantages of the enclosed embodiments will become apparent from the following description.

[0003] Multi-radio access technology dual connectivity (MR-DC) is a generalization of intra-E-UTRA dual connectivity (DC) as described in TS 36.300 V16.5.0 (incorporated herein by reference), where a UE with multi-Rx / Tx capability can be configured to use resources provided by two different nodes connected by a non-ideal backhaul, one providing NR access and the other providing E-UTRA or NR (New Radio) access. One node acts as a master node (MN) and the other as a secondary node (SN). The MN and SN are connected by a network interface, with at least the MN connected to the core network.

[0004] When configured with MR-DC, the UE typically initially operates a serving cell group called the master cell group (MCG). The network then configures the UE with an additional cell group called the secondary cell group (SCG). Each cell group (CG) can have one or more serving cells. The MCG and SCG can operate on gNBs that are not geographically co-located. The MCG and SCG can operate with corresponding serving cells belonging to different frequency ranges and / or corresponding serving cells in the same and different frequency ranges. In an example, the MCG can have serving cells in frequency range 1 (FR1) and the SCG can also have serving cells in FR1.

[0005] There are different approaches to deploy a 5G network, with or without interworking with LTE (also called E-UTRA) and Evolved Packet Core (EPC). In principle, NR and LTE can be deployed without any interworking, called NR standalone (SA) operation. That is, gNBs in NR can be connected to a 5G core network (5GC) and eNBs can be connected to EPC, with no interworking between the two (options 1 and 2). On the other hand, the first supported version of NR is the so-called EN-DC (E-UTRAN-NR Dual Connectivity), as shown in option 3. In such a deployment, dual connectivity between NR and LTE is employed, with LTE as the master node and NR as the secondary node. The RAN node supporting NR (gNB) can have no control plane connection to the core network (EPC). Instead, it can rely on LTE as the master node (MeNB). This is also called “non-standalone NR”. In this case, the functionality of NR cells is limited and UEs in connected mode are connected as an enhancement and / or diversity leg, but RRC_IDLE UEs cannot camp on these NR cells.

[0006] Since the migration of these options can differ from one operator to another, it is possible to deploy several options in parallel in the same network. For example, in the same network as NR base stations supporting options 2 and 4, there can be eNB base stations supporting options 3, 5 and 7. In combination with the dual connectivity solution between LTE and NR, it is also possible to support carrier aggregation (CA) in each cell group (i.e. MCG and SCG) and dual connectivity between nodes on the same RAT (e.g. NR-NR DC). The result of these different deployments for LTE cells is the coexistence of LTE cells associated with eNBs connected to EPC, 5GC or EPC / 5GC.

[0007] In TS 37.340 V16.5.0 (incorporated herein by reference), the flow classification for MR-DC is as follows:

[0008] - MR-DC with EPC (also called EN-DC)

[0009] - MR-DC with 5GC

[0010] MR-DC with EPC (EN-DC)

[0011] E-UTRAN supports MR-DC through E-UTRA-NR Dual Connectivity (EN-DC), where a UE is connected to one eNB acting as MN and one en-gNB acting as SN. The eNB is connected to EPC through S1 interface and to en-gNB through X2 interface. The en-gNB can also be connected to EPC through S1-U interface and to other en-gNBs through X2-U interface. An example of EN-DC architecture is shown in Figure 1shown.

[0012] MR-DC with 5GC

[0013] In E-UTRA-NR dual connectivity, the NG-RAN supports NG-RAN E-UTRA-NR dual connectivity (NGEN-DC), in which a UE is connected to one ng-eNB as an MN (Master Node) and one gNB as an SN (Secondary Node).

[0014] In NR-E-UTRA dual connectivity, the NG-RAN supports NR-E-UTRA dual connectivity (NE-DC), in which a UE is connected to one gNB as an MN and one ng-eNB as an SN.

[0015] In NR-NR dual connectivity, the NG-RAN supports NR-NR dual connectivity (NR-DC), in which a UE is connected to one gNB as an MN and another gNB as an SN. In addition, NR-DC can also be used when a UE is connected to two gNB-DUs, one serving the MCG and the other serving the SCG, connected to the same gNB-CU, acting as both MN and SN.

[0016] MR-DC user plane architecture

[0017] From the UE’s perspective, there are three data radio bearer (DRB) types in MR-DC: MCG, SCG, and split DRB, which characterize the set of cells used for transmission. MCG DRBs use only the MCG, SCG DRBs use only the SCG, while split DRBs can use both the MCG and the SCG for data transmission. For RLC / MAC, the protocol version (E-UTRA or NR) is selected according to the RAT used by the cell group. NR PDCP is used for all DRB types, except in EN-DC, where the network can also configure E-UTRA PDCP for MCG DRBs.

[0018] From the network’s perspective, each DRB can be terminated by the MN or the SN. This applies to all three bearer types, so from the network’s perspective, there can be six different bearer configurations, see for example Figure 2 Figure 3 ​Network side protocol termination options for MCG bearer, SCG bearer and split bearer in MR-DC with EPC are shown. For bearer types that require data transfer over X2 / Xn interface, a flow control protocol is used between MN and SN to avoid over-buffering data at RLC bearer level, which can cause excessive reordering at the receiving PDCP entity. The RLC bearer contains RLC / MAC configuration for each logical channel leading to the UE.

[0019] For DL transmission on split DRB, the network decides whether each PDCP PDU is transmitted over MCG or SCG. For UL transmission on split DRB, the UE is configured with a buffer threshold. When the data in the corresponding DRB buffer is below the threshold, a buffer status report (BSR) is sent only on the preferred path. The preferred path can be either MCG or SCG and is configured by the network for each DRB. When the data in the buffer is above the buffer threshold, the UE reports a total BSR to both MCG and SCG. The scheduling grants in MCG and SCG are then used by the network scheduler to control the uplink data flow.

[0020] Figure 4 Network side radio protocol termination options for MCG bearer, SCG bearer and split bearer in MN and SN for MR-DC with 5GC are shown.

[0021] MR-DC control plane architecture

[0022] The UE in MR-DC has a single control plane connection to the core network and a single RRC state, controlled by the MN. Both the MN and the SN have their own RRC entity for creating RRC messages or for configuring the information elements (IEs) of the UE, see Figure 5A and Figure 5B , Figure 5A The control plane architecture for EN-DC is shown, Figure 5B The control plane architecture for MR-DC with 5GC is shown. Since the SN is responsible for its own resources, it provides the UE with secondary cell group (SCG) configuration in RRC messages and radio bearer configuration for all bearers terminated in the SN in IEs. The MN in turn creates master cell group (MCG) configuration and radio bearer configuration for all bearers terminated in the MN. The cell group configuration includes configuration of L1 (physical layer), MAC and RLC. The radio bearer configuration includes configuration of PDCP (and SDAP in case of 5GC).

[0023] The MN always sends the initial SN RRC configuration over the MCG SRB (SRB1), but subsequent RRC configurations created by the SN can be sent to the UE by the MN using SRB1 or directly to the UE using SRB3 (if configured). See Figure 6 For the SRB1 case, the MN receives from the SN an RRC message containing the SCG configuration and an IE containing the radio bearer configuration. The MN encapsulates these into an RRC message it creates itself, which can also include changes to the MCG configuration and radio bearer configuration of bearers terminated at the MN. Thus, the MCG configuration and the SCG configuration can be sent to the UE in the same RRC message.

[0024] Split SRB1 is used to create diversity. From an RRC perspective, it behaves like a normal SRB1. However, at the PDCP level, the sender can decide to either select one of the links to schedule the RRC message or it can duplicate the message on both links. In downlink, the path switching between the MCG or SCG leg or duplication on both is implemented by the network. On the other hand, for UL, 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 disclosure.

[0025] For the SRB3 case, the SN creates the RRC message, including the SCG configuration and the radio bearer configuration for radio bearers terminated at the SN. The SN can only use SRB3 for reconfigurations that do not require coordination with the MN.

[0026] SCG mobility (inter-SN / inter-SN)

[0027] The following procedures described in TS 37.340 are relevant for this disclosure:

[0028] - Secondary node modification (MN / SN initiated);

[0029] - Secondary node release (MN / SN initiated);

[0030] - Secondary node change (MN / SN initiated);

[0031] Each of these can be described for MR-DC with EPC (EN-DC) and MR-DC with 5GC, but for brevity, only the MR-DC with 5GC case is explained here.

[0032] SN modification (MN / SN initiated)

[0033] The SN modification procedure can be initiated by the MN or the SN and is used to modify the current user plane resource configuration (e.g. related to PDU Sessions, QoS Flows or DRBs) or to modify other attributes of the UE context in the same SN.

[0034] SN initiated SN modification without MN involvement

[0035] NE-DC does not support this procedure. Figure 7 A signaling flow example of SN initiated SN modification procedure without MN involvement is shown. SN initiated SN modification procedure without MN involvement, as shown in Figure 7 is used to modify the configuration within the SN without the need to coordinate with the MN, including changes of SCG SCell and PSCell addition / modification / release (e.g. when no security key change is needed and the MN does not need to be involved in PDCP recovery). The SN can initiate the procedure to configure or modify the CPC configuration within the same SN. The SN can decide whether a random access procedure is needed.

[0036] SN initiated SN modification with MN involvement

[0037] Figure 8 A signaling flow example of SN initiated SN modification procedure with MN involvement is shown. The SN uses this procedure to perform configuration changes of the SCG within the same SN, e.g. to trigger modification / release of user plane resource configuration, and to trigger changes of PSCell (e.g. when a new security key is needed or when the MN needs to perform PDCP data recovery). The MN cannot reject a PDU Session / QoS Flow release request. The SN also uses this procedure to request the MN to provide more DRB IDs for SN terminated bearers or to return DRB IDs for SN terminated bearers that are not needed anymore.

[0038] SN initiated SN modification (MN / SN initiated)

[0039] MN initiated SN change

[0040] Figure 9 A signaling flow example of MN initiated SN change procedure is shown. The MN initiated SN change procedure is used to transfer the UE context from the source SN to the target SN and to change the SCG configuration in the UE from one SN to another. The Secondary Node Change procedure always involves signaling to the UE over the MCG SRB.

[0041] SN initiated SN change

[0042] Figure 10A signaling flow example showing SN-initiated SN change procedure. The SN-initiated SN change procedure is used to transfer the UE context from the source SN to the target SN and change the SCG configuration in the UE from one SN to another SN.

[0043] SCG power saving mode

[0044] To improve the network energy efficiency and UE battery life of the UE in MR-DC, the Rel-17 work item plans to introduce efficient SCG / SCell activation / deactivation. This is especially important for MR-DC configuration with NR SCG, as evaluated in RP-190919, the power consumption of NR UE is 3 to 4 times higher than LTE in some cases. 3GPP has specified the concept of dormant SCell (in LTE) and dormant behavior similar to SCell (for NR).

[0045] In LTE, when an SCell is in a dormant state, such as a deactivated state, the UE does not need to monitor the corresponding PDCCH or PDSCH, nor can it transmit on the corresponding uplink. However, unlike the deactivated state, the UE needs to perform and report CQI measurements. The PUCCH SCell (SCell configured with PUCCH) cannot be in a dormant state.

[0046] In NR, the dormant behavior of an SCell is implemented using the concept of a dormant BWP. One SCell can be configured with one dormant BWP, which is one of the dedicated BWPs configured by the network through RRC signaling. If the active BWP of an activated SCell is a dormant BWP, the UE stops monitoring PDCCH on the SCell, but continues to perform CSI measurements, AGC, and beam management (if configured). DCI is used to control one or more SCells or one or more SCell groups to enter / leave the dormant BWP, which is sent to the special cell (sPCell) of the cell group to which the SCell belongs (i.e., PCell if the SCell belongs to MCG; PSCell if the SCell belongs to SCG). The SpCell (i.e., PCell of PSCell) and PUCCH SCell cannot be configured with a dormant BWP.

[0047] However, only SCells can be put in dormant state (in LTE) or run with a similar dormant behavior (NR). Also, only SCells can be put in deactivated state in both LTE and NR. Therefore, if a UE is configured with MR-DC, it is not possible to fully benefit from the power saving option of the dormant state or similar dormant behavior, as the PSCell cannot be configured with this functionality. Instead, the existing solution can release (for power saving) and add (when traffic demand requires) the SCG as needed. However, traffic is likely to be bursty and adding and releasing the SCG involves a lot of RRC signaling and inter-node messaging between the MN and the SN, which causes considerable delay.

[0048] In rel-16, there was some discussion about putting the PSCell in dormant state as well, also referred to as SCG suspension. Some preliminary agreements were reached in RAN2-107bis in October 2019 (see Chairman’s notes in R2-1914301):

[0049] R2 assumes the following (can be slightly modified depending on the progress of SCell dormancy):

[0050] • UE supports SCG suspension in RRC_CONNECTED controlled by the network.

[0051] • UE behavior for SCG suspension is FFS

[0052] • UE supports at most one SCG configuration in Rel-16, suspended or not.

[0053] • After adding SCG in RRC_CONNECTED, SCG can be configured to be suspended or not.

[0054] In RAN-2108, further discussions were held to clarify the above FFS.

[0055] Some solutions have been proposed in Rel-16, but these solutions have different issues. For example, in R2-1908679 (Introduction of SCG suspension - Qualcomm), the paper proposes that when no data traffic is expected to be sent in the SCG, the gNB can instruct the UE to suspend SCG transmission so that the UE keeps the SCG configuration but does not use it for power saving purposes. It is mentioned that the signaling to suspend the SCG can be based on DCI / MAC-CE / RRC signaling, but no details are provided about the configuration from the gNB to the UE. Also, unlike the defined behavior for SCells, the PSCell can be associated to a different network node (e.g. a gNodeB operating as a secondary node). In rel-17, it is yet to be seen which behavior is specified for SCG power saving. However, it is likely that one or more of the following cases will occur:

[0056] - the UE starts running the PSCell in a dormant state, e.g. switches the PSCell to a dormant BWP. At the network side, the network considers the PSCell in a dormant state and at least stops transmitting PDCCH in the PSCell and SCells for the UE;

[0057] - the UE deactivates the PSCell like a deactivated SCell; at the network side, the network considers the PSCell as deactivated and at least stops transmitting PDCCH in the PSCell (and on SCells) for the UE;

[0058] - the UE runs the PSCell in long DRX; the SCG DRX can be turned off from the MN (e.g. by MCG RRC, MAC CE or DCI) when needed, e.g. DL data arrives for SN terminated SCG bearers;

[0059] - the UE suspends its running with the SCG (e.g. suspends the bearers associated with the SCG, like SCG MN- / SN-terminated bearers), but keeps the stored SCG configuration (referred to as stored SCG); at the network side, there can be different alternatives, e.g. the SN stores the SCG like the UE, or the SN releases the SCG context of the UE to be generated again upon resumption (e.g. the node that stores the SCG context for the UE whose SCG is suspended is the MN).

[0060] While the energy saving aspects have been discussed so far from the SCG perspective, it is likely that similar approaches can be used on the MCG as well (e.g. the MCG can be suspended or in long DRX state, while data communication happens only through the SCG). SUMMARY

[0061] One aspect of the disclosure provides a method performed by a wireless device configured with multi-radio access technology dual connectivity (MR-DC) for a first group of cells and a second group of cells. The method includes receiving, from a first network node, at least one message in a reconfiguration procedure for the second group of cells. The at least one message indicates a mode of operation for the wireless device for the second group of cells after the wireless device has applied the reconfiguration procedure for the second group of cells.

[0062] Another aspect of the disclosure provides a method performed by a first network node for configuring a wireless device configured with multi-radio access technology dual connectivity (MR-DC) for a first group of cells and a second group of cells. The method includes sending, to the wireless device, at least one message in a reconfiguration procedure for the second group of cells. The at least one message indicates a mode of operation for the wireless device for the second group of cells after the wireless device has applied the reconfiguration procedure for the second group of cells.

[0063] Another aspect of the disclosure provides an apparatus in a wireless device configured with multi-radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group. The apparatus includes a processor and a memory. The memory contains instructions executable by the processor such that the apparatus is operable to receive, from a first network node, at least one message in a reconfiguration procedure for the second cell group. The at least one message indicates a mode of operation for the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group.

[0064] Yet another aspect of the disclosure provides an apparatus of a first network node to configure a wireless device with multi-radio access technology dual connectivity (MR-DC) configured for a first cell group and a second cell group. The apparatus includes a processor and a memory. The memory contains instructions executable by the processor such that the apparatus is operable to send, to the wireless device, at least one message in a reconfiguration procedure for the second cell group. The at least one message indicates a mode of operation for the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group.

[0065] Another aspect of the disclosure provides an apparatus in a wireless device configured with multi-radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group. The apparatus is configured to receive, from a first network node, at least one message in a reconfiguration procedure for the second cell group. The at least one message indicates a mode of operation for the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group.

[0066] Another aspect of the disclosure provides an apparatus in a first network node to configure a wireless device with multi-radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group. The apparatus is configured to send, to the wireless device, at least one message in a reconfiguration procedure for the second cell group. The at least one message indicates a mode of operation for the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group. BRIEF DESCRIPTION OF DRAWINGS

[0067] For a better understanding of example aspects of the present disclosure, and to show how these example aspects can be implemented, reference will now be made, by way of example only, to the following drawings in which:

[0068] Figure 1 An example of an EN-DC architecture is shown;

[0069] Figure 2 Radio bearer types in MR-DC are shown;

[0070] Figure 3Network side protocol termination options for MCG bearer, SCG bearer and split bearer in MR-DC (EN-DC) with EPC are shown;

[0071] Figure 4 Network side radio protocol termination options for MCG bearer, SCG bearer and split bearer in MN and SN for MR-DC with 5GC are shown;

[0072] Figure 5A Control plane architecture for EN-DC is shown;

[0073] Figure 5B Control plane architecture for MR-DC with 5GC is shown;

[0074] Figure 6 Network side protocol termination options for SRBs in MR-DC are shown;

[0075] Figure 7 Signaling flow example for SN initiated SN modification procedure without MN involvement is shown;

[0076] Figure 8 Signaling flow example for SN initiated SN modification procedure with MN involvement is shown;

[0077] Figure 9 Signaling flow example for MN initiated SN change procedure is shown;

[0078] Figure 10 Signaling flow example for SN initiated SN change procedure is shown;

[0079] Figure 11 is an example of a flow diagram of a method performed by a wireless device configured with multi radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group;

[0080] Figure 12 is an example of a flow diagram of a method 1200 performed by a first network node for a wireless device configured with multi radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group;

[0081] Figure 13 Signaling flow example for SN initiated SN modification without MN involvement according to examples of the present disclosure is shown;

[0082] Figure 14 Signaling flow example for SN initiated SN modification with MN involvement according to examples of the present disclosure is shown;

[0083] Figure 15 Signaling flow example for MN initiated SN change according to examples of the present disclosure is shown;

[0084] Figure 16 A signaling flow example of SN initiated SN change is shown in accordance with examples of the present disclosure;

[0085] Figure 17 An example of a wireless network is shown in accordance with some embodiments;

[0086] Figure 18 An example of a user equipment (UE) is shown in accordance with some embodiments;

[0087] Figure 19 is a schematic block diagram illustrating a virtualization environment, in accordance with some embodiments;

[0088] Figure 20 A telecommunication network connected via an intermediate network to a host computer is shown in accordance with some embodiments;

[0089] Figure 21 A host computer communicating with a user equipment through a base station over a partially wireless connection is shown in accordance with some embodiments;

[0090] Figure 22 A method implemented in a communication system is shown in accordance with some embodiments;

[0091] Figure 23 A method implemented in a communication system is shown in accordance with some embodiments;

[0092] Figure 24 A method implemented in a communication system is shown in accordance with some embodiments;

[0093] Figure 25 A method implemented in a communication system including a host computer, a base station and a user equipment is shown in accordance with some embodiments;

[0094] Figure 26 is a schematic block diagram illustrating a virtualization environment, in accordance with some embodiments; and

[0095] Figure 27 is a schematic block diagram illustrating a virtualization environment, in accordance with some embodiments. DETAILED DESCRIPTION

[0096] The following presents a summary of specific details for the purpose of providing a thorough understanding of the disclosure. Specific examples are described in detail for the purpose of providing a thorough understanding of the disclosure. Those skilled in the art will appreciate that other examples can be employed apart from these specific details. In some instances, detailed descriptions of well-known methods, nodes, interfaces, circuits, and devices are omitted so as not to obscure the description with unnecessary detail. Those skilled in the art will appreciate that the described functions can be performed in one or more nodes using hardware circuitry (e.g., analog and / or discrete logic gates interconnected to perform a specialized function, ASICs, PLAs, etc.) and / or using software programs and data in conjunction with one or more digital microprocessors or general purpose computers. Nodes that communicate using the air interface also have suitable radio communications circuitry. Moreover, where appropriate, the technology can additionally be considered to be embodied entirely within any form of computer-readable storage medium having stored therein computer-executable instructions or data structures that, as those

[0097] Hardware implementation can include or encompass, without limitation, digital signal processor (DSP) hardware, a reduced instruction set processor, hardware (e.g., digital or analog) circuitry including, but not limited to, application specific integrated circuit(s) (ASIC) and / or field

[0098] There are certain challenges currently. For example, in dual connectivity, a UE can perform UL / DL transmission / reception (for data transmission / reception using associated MCG and / or SCG radio links) to a master node (MN) and / or a secondary node (SN). In a typical scenario, the MCG can be considered to provide basic coverage, and the SCG is used to increase data rate during data bursts. The UE needs to continuously monitor PDCCH on at least the PCell and PSCell for uplink scheduling assignment and downlink scheduling assignment, and can need to monitor all other SCells if cross-carrier scheduling is not employed. Even if cross-carrier scheduling is employed, the UE needs to perform additional PDCCH listening on the PCell or PSCell for SCells depending on whether the SCell belongs to the MCG or the SCG.

[0099] As mentioned above, there are several ways to put the SCG in power saving mode. In R2-1908679 (Introducing SCG Suspend - Qualcomm), it is suggested that the gNB can instruct the UE to suspend SCG transmission when no data traffic is expected in the SCG for the UE to keep the SCG configuration but not use it for power saving purposes. It is also discussed that both RLM and RRM should continue when the UE is operating in this power saving mode for the SCG.

[0100] In some instances, when the UE-configured SCG is in power saving mode (e.g., suspended SCG), the UE can be far away from the coverage of the PSCell (e.g., PSCell RSRP starts to drop) and / or the UE can enter the coverage of a cell of the same frequency of the PSCell, which can be in better radio conditions (e.g., a neighbor cell of the same frequency of the suspended PSCell has better RSRQ than the suspended PSCell). While this does not necessarily cause interference to the frequency of the PSCell, if the transmission and reception of the SCG is suspended, when the network wants to resume the SCG (or in general, transition the SCG to normal mode of operation), the PSCell of the suspended SCG can not be in good coverage or be the best in terms of radio conditions (e.g., SINR and / or RSRQ) compared to some other neighbor cells, and thus, resuming such a PSCell can result in a failure of the resumption (e.g., due to interference from the neighbor with stronger radio conditions), or even if the resumption is successful, this can be immediately followed by a reconfiguration and synchronization, e.g., PSCell change.

[0101] Certain aspects of the present disclosure and embodiments thereof can provide solutions to these or other challenges. For example, in some instances, methods of second cell group mobility for a UE configured with a first cell group and a second cell group in MR-DC are provided, where the second cell group is in a power saving mode (e.g., deactivated, not activated, suspended, dormant, etc.). While some examples describe the SCG as the second cell group and the MCG as the first cell group, examples of the present methods can also apply to instances where the SCG is the first cell group and the MCG is the second cell group.

[0102] Examples of the present disclosure include a method performed by a wireless terminal (also referred to as a user equipment, UE) configured with multi-radio dual connectivity (MR-DC), i.e., configured with a first cell group (e.g., master cell group - MCG) and a second cell group (e.g., secondary cell group - SCG). The method comprises:

[0103] - receiving a message comprising i) an indication of a mode of operation of a target SpCell (e.g., SpCell is a PSCell to enter a power saving mode, as in a suspended SCG; normal mode / non-power saving mode / resumed, as in a resumed SCG); and ii) a synchronization reconfiguration of the second cell group (e.g., a synchronization reconfiguration of the SCG, PSCell change with PCell unchanged, or PCell change with PSCell unchanged);

[0104] . The indication can be defined as an optional field and / or information element (IE);

[0105] . Generally, mobility can correspond to reconfiguration with synchronization procedure;

[0106] . The target PCell / PSCell is the target SpCell indicated in the synchronization reconfiguration of the second cell group;

[0107] . Receive a post-triggered PCell / PSCell change, e.g. SCG RRC reconfiguration, including a synchronization reconfiguration, including an indication of the target operating mode of the new cell;

[0108] . In one embodiment, the message contains a reconfiguration with synchronization indication for the second cell group;

[0109] . When saying “indication of the operating mode of the target SpCell”, it can correspond to “indication of the operating mode of the second cell group”;

[0110] - Set the operating mode of the second cell group to the mode indicated in the message (e.g. like suspend SCG to save power) and perform operations according to that operating mode.

[0111] In other words, in some examples, the same message indicating a PSCell change (e.g. for a UE connected with MR-DC) can include an indication of the operating mode of the SCG. This can be an RRCReconfiguration message, including reconfigurationWithSync in the SCG configuration, and as part of that, an indication of the operating mode set for the SCG at reconfiguration synchronization (e.g. suspend SCG).

[0112] - In some examples, the method can include the case where the SN is not changed, e.g. the PSCell changes but the target PSCell is also associated to the source SN. In that case, it is the source SN that generates the SCG configuration and sets its operating mode.

[0113] - In some examples, the method can include the case where the SN is changed, e.g. the PSCell changes but the target PSCell is also associated to a different SN, i.e. the target SN. In that case, it is the target SN that generates the SCG configuration and sets its operating mode.

[0114] Another example of the present disclosure includes a method where i) the first cell group is a master cell group, MCG, and the second cell group is a secondary cell group, SCG; or ii) the first cell group is a secondary cell group, SCG, and the second cell group is a master cell group, MCG. The first mode of operation can be, for example, a normal mode of operation, while the second mode of operation can be a power saving mode. In some examples, where the first mode of operation is a power saving mode of operation, and the second mode of operation is a normal mode of operation. In some examples, the first mode of operation is a power saving mode of operation, and the second mode of operation is also a power saving mode.

[0115] Upon receiving a message indicating that the mode of operation of the target SCG is set to a power saving mode or that the SCG is already in a power saving mode (such as SCG suspension), in some examples, the methods of the present disclosure can include storing at least some parts of the received SCG configuration (e.g., a synchronization reconfiguration of the SCG), and delaying applying the message or the stored parts (and / or taking action thereon) until a second indication is received to resume the SCG in a power saving mode of operation.

[0116] Certain examples of the present disclosure can provide one or more technical advantages. For example, the examples disclosed herein can enable a UE configured with MR-DC to perform a PSCell mobility (or generally SCG mobility) procedure while the second cell group (e.g., SCG) is in a power saving mode of operation (e.g., SCG suspension). This can be, for example, a PSCell change (with or without SN change) of one PSCell in power saving mode. Setting the mode of operation enables the target party to determine whether the second cell group remains in the same mode of operation before the change (e.g., power saving remains power saving, normal remains normal); or, to modify the mode of operation of the second cell group as the target party (e.g., target SN) deems appropriate (e.g., power saving to normal, normal to power saving). The network can be able to set the mode of operation for the second cell group, such as a secondary cell group (SCG), e.g., a suspended SCG, for an incoming UE in a PSCell mobility procedure, such as a SN initiated PSCell change with SN change. Another benefit of the SCG remaining in a power saving state after SN mobility (e.g., PSCell change) is that when the SCG is activated again, the UE can be prepared with a more suitable PSCell for the SCG, avoiding that the UE would first try to resume in a non-ideal PSCell, which can be a cell with non-optimal radio conditions, triggering an immediate change of PSCell, or even inaccessible, triggering a failure to resume that SCG.

[0117] Some 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 is not to be interpreted in a limiting sense; rather, these embodiments are provided for illustrative purposes. For example, one embodiment can be implemented in a manner that is different from that described herein without departing from the scope of the subject matter disclosed herein.

[0118] Figure 11 is a flowchart of an example of a method 1100 performed by a wireless device (e.g., a UE) configured with multi-radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group. The method 1100 includes, in step 1102, receiving, from a first network node (e.g., a base station, a base station control unit (CU), a base station distributed unit (DU), an eNB, an eNB-CU, an eNB-DU, a gNB, a gNB-CU, or a gNB-DU), at least one message in a reconfiguration procedure for the second cell group, where the at least one message indicates a mode of operation of the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group. For example, the at least one message can be received from a node or cell associated with the first cell group or the second cell group. In some examples, the first cell group can be a master cell group (MCG) and the second cell group can be a secondary cell group (SCG). Alternatively, in some examples, the second cell group can be a master cell group (MCG) and the first cell group can be a secondary cell group (SCG). For example, the at least one message can be at least one RRC message and / or at least one RRC reconfiguration message.

[0119] In some examples, the mode of operation of the wireless device for the second cell group includes a mode of operation of the wireless device for a special cell (e.g., a SpCell) of the second cell group and / or one or more other cells of the second cell group.

[0120] For example, the mode of operation of the wireless device for the second cell group can be a power saving mode of operation of the wireless device for the second cell group, a special cell of the second cell group, and / or one or more other cells of the second cell group. The power saving mode can be, for example, a suspend mode or a dormant mode or a deactivated mode or an inactive mode of operation. In some examples, the method 1100 can include operating the second cell group according to the power saving mode of operation after reconfiguring the second cell group according to the reconfiguration procedure. Operating the second cell group according to the power saving mode of operation after reconfiguring the second cell group according to the reconfiguration procedure can include, for example, at least one of the following: operating the special cell of the second cell group in a dormant mode; operating the special cell of the second cell group in a suspend mode; operating the special cell of the second cell group in a deactivated mode; operating the special cell of the second cell group in an inactive mode; operating the special cell of the second cell group in a dormant bandwidth part (BWP); stopping monitoring PDCCH of the special cell and / or at least one other cell of the second cell group; suspending transmission of data radio bearers (DRBs) associated with the second cell group; suspending transmission of DRBs associated with the special cell of the second cell group; suspending transmission of DRBs terminated at a node associated with the second cell group or the special cell and / or at least one other cell of the second cell group; suspending DRBs associated with the second cell group; operating the special cell of the second cell group according to discontinuous reception (DRX); and monitoring PDCCH on the second cell group only during DRX cycle durations configured for the second cell group and / or at least one cell of the second cell group.

[0121] In some examples, the previous mode of operation of the wireless device for the second cell group prior to receiving the at least one message includes a power saving mode of operation. In such examples, the method 1100 can include, after receiving the at least one message, performing the reconfiguration procedure in response to receiving a command from the first network node to activate, reactivate, or resume the second cell group. The at least one message can include an indication to perform the reconfiguration procedure immediately or an indication to perform the reconfiguration procedure in response to receiving a command from the first network node to activate, reactivate, or resume the second cell group. Thus, for example, the method 1100 can include performing the reconfiguration procedure immediately if the indication is to perform the reconfiguration procedure immediately and / or performing the reconfiguration procedure in response to receiving a command from the first network node to activate, reactivate, or resume the second cell group after receiving the at least one message if the indication is to perform the reconfiguration procedure in response to receiving a command from the first network node to activate, reactivate, or resume the second cell group.

[0122] In some examples, the mode of operation of the wireless device for the second cell group can include a resumed mode, a normal mode, a legacy mode, or an active mode.

[0123] In some examples, the method 1100 can include operating the second cell group according to an operation mode indicated in the at least one message, and / or performing a reconfiguration procedure for the second cell group.

[0124] Figure 12 is a flowchart of an example of a method 1200 performed by a first network node (e.g., a base station, a base station control unit (CU), a base station distributed unit (DU), an eNB, an eNB-CU, an eNB-DU, a gNB, a gNB-CU, or a gNB-DU) for configuring a wireless device (e.g., a UE) configured with multi-radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group. The method 1200 includes, in step 1202, sending, to the wireless device, at least one message (e.g., at least one RRC message and / or at least one RRC reconfiguration message) in a reconfiguration procedure for the second cell group, where the at least one message indicates an operation mode of the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group. In some examples, the first cell group includes a master cell group (MCG), and the second cell group includes a secondary cell group (SCG). Alternatively, for example, the second cell group includes a master cell group (MCG), and the first cell group includes a secondary cell group (SCG). In some examples, the first network node can be associated with a special cell (SpCell) of the first cell group, e.g., be a serving base station of the SpCell.

[0125] In some examples, the operation mode of the wireless device for the second cell group includes a power saving operation mode of the wireless device for the special cell of the second cell group and / or one or more other cells of the second cell group. For example, the operation mode of the wireless device for the second cell group includes a power saving operation mode of the wireless device for the second cell group, the special cell (e.g., SpCell) of the second cell group, and / or one or more other cells of the second cell group, where the power saving operation mode includes a suspend mode or a dormant mode or a deactivated mode or an inactive operation mode. In some examples, prior to receiving the at least one message, a previous operation mode of the wireless device for the second cell group includes a power saving operation mode. In such examples, the method 1200 can include sending a command to the wireless device to cause the wireless device to resume, activate, or reactivate the second cell group based on a configuration of the second cell group stored at the wireless device. In some examples, the method 1200 can also include including in the at least one message an indication to immediately perform the reconfiguration procedure or an indication to perform the reconfiguration procedure in response to receiving a command from the first network node to activate, reactivate, or resume the second cell group. In some examples, the method can include stopping transmitting PDCCH to the wireless device on the special cell associated with the second cell group and / or at least one other cell associated with the second cell group.

[0126] In some examples, the operational mode of the wireless device for the second cell group comprises a resumed mode, a normal mode, a legacy mode, or an active mode.

[0127] In some examples, the method 1200 can comprise receiving, from a network node associated with the second cell group, an indication of the operational mode of the wireless device for the second cell group being reconfigured according to the reconfiguration procedure prior to transmitting the at least one message to the wireless device. Alternatively, for example, the method 1200 can comprise transmitting, to a network node associated with the second cell group, an indication of the operational mode of the wireless device for the second cell group.

[0128] In some examples, the method 1200 can comprise transmitting context information of the wireless device to a node associated with the second cell group being reconfigured according to the reconfiguration procedure.

[0129] Additional specific example embodiments are provided below. The terms “suspended SCG” and “SCG in power saving mode” are used interchangeably in this disclosure. The term “suspended SCG” can also be referred to as “deactivated SCG” or “inactive SCG”. The terms “resumed SCG” and “SCG in non-power saving mode” are used interchangeably. The term “resumed SCG” can also be referred to as “activated SCG” or “active SCG”. The operation of an SCG operating in resumed or active mode can also be referred to as normal SCG operation or legacy SCG operation. Examples of operations are UE signal reception / transmission procedures, e.g. RRM measurements, reception of signals, transmission of signals, measurement configuration, measurement reporting, evaluation of triggering event measurement reporting, etc.

[0130] The present disclosure relates to the terminology like SCG and PSCell, in some examples as one of the cells associated with the SCG. For example, this can be the PSCell as defined in the NR specification (e.g. RRC TS 38.331), as the special cell (SpCell) of the SCG, or the primary SCG cell (PSCell), e.g. as follows:

[0131] • Secondary Cell Group: For a UE configured with dual connectivity, the subset of serving cells includes the PSCell and zero or more secondary cells.

[0132] • Special Cell: For dual connectivity operation, the term special cell refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term special cell refers to the PCell.

[0133] • Primary SCG Cell: For dual connectivity operation, the SCG cell on which the UE performs random access when performing a synchronous reconfiguration procedure.

[0134] The present disclosure relates to some specific examples where the second cell group is a secondary cell group (SCG) that can be suspended for a UE configured with dual connectivity (e.g. MR-DC). However, these examples are also applicable where the second cell group is a master cell group (MCG) for a UE configured with dual connectivity (e.g. MR-DC), where the MCG can be suspended. In that case, when a MCG mobility is triggered, the mode of operation after the mobility can be set to the same or a different mode of operation. Unlike for PSCell, the actions would be related to PCell, or more generally to SpCell of the second cell group. Note that this use case is different from one of the use cases in MCG mobility (e.g. from source MN to target MN), where the SCG mode of operation can be set, e.g. the SCG mode of operation is modified by the target MN from suspended to normal.

[0135] Examples of the present disclosure can relate to mobility use cases, e.g. when the UE is configured with MR-DC and a PSCell change is triggered. However, many aspects of the present disclosure can also be applicable where the UE is configured with a SCG, where its mode of operation is set to suspended. For example, a received SCG configuration containing a SCG synchronization reconfiguration can be stored (possibly not applied) and only applied when an indication to resume the SCG from the network is received.

[0136] When the present disclosure refers to SN RRC reconfiguration or SCG RRC reconfiguration, this can in some examples correspond to a RRC reconfiguration message generated by the SN and containing a SCG configuration.

[0137] In the present disclosure, the term “suspend SCG” can correspond to any of the following examples:

[0138] • The UE starts running the PSCell in dormant state, e.g. switches the PSCell to a dormant BWP and / or stops PDCCH monitoring in the PSCell and SCells of the SCG. On the network side, the network considers the PSCell in dormant state and at least stops transmitting PDCCH in the PSCell and SCells of the SCG for this UE;

[0139] • The UE deactivates the PSCell like a SCell deactivation and stops monitoring PDCCH in the PSCell and SCells of the SCG; on the network side, the network considers the PSCell deactivated and at least stops transmitting PDCCH in the PSCell for this UE;

[0140] • UE suspends its operation with the SCG (e.g. suspends SCG transmission for all DRBs and SRBs or suspends bearers associated with the SCG like SCG MN- / SN- terminated bearers) but keeps the stored SCG configuration (referred to as stored SCG); on the network side, there can be different alternatives, e.g. the SN stores the SCG like the UE or the SN releases the UE’s SCG context to be generated again at the time of resumption (e.g. the UE’s SCG is suspended with the support of the MN as the node storing the SCG context). More details are provided later.

[0141] • UE receives from the network a command to enter long DRX on the SCG and only monitors PDCCH in the PSCell and SCells of the SCG during the ON duration of the configured SCG DRX cycle.

[0142] The present disclosure can also use the term suspended SCG, SCG suspension, or, when referring to the action of transitioning to a suspended SCG, it can refer to suspend SCG. In this document, the term “resume SCG” can correspond to any of the following examples:

[0143] • UE transitions the PSCell from a sleep-like behavior to a normal active cell behavior (e.g. by switching the PSCell to a non-sleep BWP) and starts monitoring PDCCH at least for one of the cells of the SCG; this transition can be triggered, e.g. by network signaling;

[0144] • UE activates the PSCell and starts monitoring PDCCH at least for one of the cells of the SCG; this transition can be triggered, e.g. by network signaling;

[0145] • UE resumes the stored SCG configuration and starts operating (e.g. resumes SCG transmission / bearers) according to the resumed SCG configuration;

[0146] • UE resumes the stored SCG configuration and receives a message with SCG configuration to be applied on top of the resumed stored SCG configuration (e.g. delta signaling);

[0147] • UE receives from the network a command to exit DRX on the SCG.

[0148] The disclosure can also use the terms resuming SCG, SCG resumption, or, when referring to the action of switching to an active / resumed SCG, it can use resume SCG. At least in some specific examples described below, the request to suspend / resume SCG (whether MN- or SN- triggered) is accepted / confirmed by the other node (SN, if it was MN- triggered; MN, if it was SN- triggered). However, other examples can also include flows where the request is rejected, e.g. if the MN wants to resume the SCG, but the SN can not have the required radio resources to accommodate the UE at that point in time. In these rejected cases, according to the method, the UE can receive an indication from the network (e.g. an RRC reconfiguration message with MR-DC release indication) indicating that the SCG remains suspended or that the SCG has to be released. In some examples, the UE can receive an indication to release the stored SCG due to other reasons that the network can find suitable, e.g. expiry of a timer at the network side (where the timer is defined to determine how long the SCG context is worth storing instead of releasing it).

[0149] The disclosure can describe a UE with MR-DC capability, i.e. can be configured with a master cell group (MCG), associated to a network node operating as master node (MN), and a secondary cell group (SCG), associated to a network node operating as secondary node (SN). According to some examples, the network node operating as MN can be a gNodeB (NR technology) or an eNodeB (LTE node connected to EPC), or an ng-eNodeB (LTE node connected to 5GC). Moreover, the network node operating as SN can be a gNodeB (NR technology) or an eNodeB, or an ng-eNodeB. Possible combinations can be: MN and SN are both gNodeBs, in which case both MCG and SCG are configured with NR cells. Another possible combination can be: MN is an eNodeB and SN is a gNodeB, in which case the MCG is configured with LTE cells and the SCG is configured with NR cells, so the UE is configured with inter-RAT dual connectivity. Even if LTE and NR have been used as different RATs, this should be interpreted as an example, so the method is applicable to inter-RAT dual connectivity with any two different RATs. Or, in an intra-RAT fashion.

[0150] Example of SN initiated SN modification without MN involvement

[0151] Some examples of the disclosure include a method comprising setting a mode of operation of a SCG when performing a SN initiated SN modification procedure without involvement of the MN. For example, Figure 13 A signaling flow 1300 example for SN initiated SN modification without involvement of the MN according to examples of the disclosure is shown. According to Figure 13The illustrated method, in the absence of MN involvement, SN-initiated SN modification procedure is used to modify the configuration within the SN, including the setting of the SCG operation mode, e.g. setting the SCG to suspend (or other power saving operation mode), or to normal operation mode, if no coordination with the MN is needed, including addition / modification / release of SCG SCells and PSCell change (e.g. when security keys do not need to be changed, and the MN does not need to be involved in PDCP recovery). The SN can decide whether random access procedure is needed. This procedure can be used e.g. if SRB3 is configured.

[0152] In Figure 13 Step 1, the SN sends to the UE a “SN RRC Reconfiguration message” (also referred to as SCG RRC Reconfiguration message) over SRB3. The SN RRC Reconfiguration can be a RRCReconfiguration message (or equivalent message) generated by the SN and can include a reconfigurationWithSync field of IEReconfigurationWithSync as part of the CellGroupConfig configuration of the SCG, and an explicit indication of the operation mode of the SCG that the UE is to set / assume at the time of performing this procedure.

[0153] An example is illustrated below, where the RRCReconfiguration message contains the IE CellGroupConfig of the secondaryCellGroup, containing a synchronous reconfiguration (reconfigurationWithSync of the IE ReconfigurationWithSync), and also containing an explicit indication of the operation mode as part of the CellGroupConfig IE, as this operation mode applies to the entire cell group.

[0154]

[0155]

[0156] When performing a PSCell change (e.g. without SN change), there can be further UE actions depending on the mode of operation set by the network for the SCG. For example, in legacy case, when the UE receives a CellGroupConfig with spCellConfig and reconfigurationWithSync, the UE resumes all suspended radio bearers and resumes SCG transmission for all radio bearers, if suspended. However, according to this approach, SCG transmission is resumed for all radio bearers only if the mode of operation of the SCG is set to normal (or active, depending on how normal / legacy operation is defined) in this PSCell change procedure. Still according to this approach, if the mode of operation of the SCG is set to suspended (or any other power saving mode of operation), such action is not performed upon reception of the cell group configuration (but eventually when the SCG is resumed later, e.g. when the UE receives another command to resume the SCG). An example of the RRC specification text is shown below, where this part is modified to implement this approach:

[0157] *****************************************************************************

[0158] 5.3.5.3 Reception of an RRCReconfiguration by the UE

[0159] The UE, upon receipt of an RRCReconfiguration, or upon execution of a conditional reconfiguration (CHO or CPC), shall: ...

[0161] 1> if the RRCReconfiguration includes a secondaryCellGroup:

[0162] 2> perform cell group configuration for the SCG as specified in 5.3.5.5; ...

[0164] 5.3.5.5 Cell Group Configuration

[0165] 5.3.5.5.1 General

[0166] The network configures the UE with a master cell group (MCG) and zero or one secondary cell group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] , and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . In the CellGroupConfig IE, the network provides configuration parameters for a cell group.

[0167] Upon reception of the CellGroupConfig IE, the UE performs the following actions:

[0168] 1> if the CellGroupConfig contains a CellGroupConfig with reconfigurationWithSync:

[0169] 2> resume all suspended radio bearers ;

[0170] 2> perform a synchronous reconfiguration according to 5.3.5.5.2;

[0171] 2> consider the SCG as suspended and perform the actions specified in 5.3.5.5.X if modeOfOperation is set to "normal";

[0172] 3＞ if suspended, resume SCG transmission for all radio bearers;

[0173] 1> if the CellGroupConfig contains modeOfOperation set to "suspend":

[0174] 2> consider the SCG as suspended and perform the actions specified in 5.3.5.5.X; ...

[0176] *****************************************************************************

[0177] In another example, the RRCReconfiguration message contains a secondaryCellGroup message of the IE CellGroupConfig, the IE CellGroupConfig contains a synchronous reconfiguration (reconfigurationWithSync of the IE ReconfigurationWithSync) containing an indication indicating whether the running mode of the SCG is to be set to a power saving running mode (e.g. a suspended SCG). The absence of such indication is to be interpreted by the UE as setting the running mode to normal (i.e. not in power saving state).

[0178]

[0179] As in the previous example, there can be further UE actions depending on the mode of operation set by the network for the SCG at the time of performing the PSCell change (e.g., without SN change). According to this example of the method, if the mode of operation of the SCG is set to active or normal, the UE only resumes SCG transmission. Still according to this method, if the mode of operation of the SCG is set to suspended (or any other power saving mode of operation), no such operation is performed upon reception of the CellGroupConfig (but eventually when the SCG is resumed later). An example of the RRC specification text is shown below, where it is modified to implement this part of the method:

[0180] *****************************************************************************

[0181] 5.3.5.3 Reception of RRCReconfiguration by the UE

[0182] The UE, upon receipt of the RRCReconfiguration, or upon performing a conditional reconfiguration (CHO or CPC), shall: ...

[0184] 1> if the RRCReconfiguration includes secondaryCellGroup:

[0185] 2> perform cell group configuration for the SCG as specified in 5.3.5.5; ...

[0187] 5.3.5.5 Cell Group Configuration

[0188] 5.3.5.5.1 General

[0189] The network configures the UE with a master cell group (MCG) and zero or one secondary cell group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] , and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . In the CellGroupConfig IE, the network provides configuration parameters for the cell group.

[0190] Upon receipt of the CellGroupConfig IE, the UE performs the following actions:

[0191] 1> if the CellGroupConfig contains spCellConfig with reconfigurationWithSync:

[0192] 2> resume all suspended radio bearers ;

[0193] 2> perform a synchronous reconfiguration according to 5.3.5.5.2;

[0194] 2> consider the SCG as suspended and perform the actions specified in 5.3.5.5.X if modeOfOperation is set to "normal";

[0195] 3＞ if suspended, resume SCG transmission for all radio bearers;

[0196] 1> if the CellGroupConfig contains modeOfOperation set to "suspend":

[0197] 2> consider the SCG as suspended and perform the actions specified in 5.3.5.5.X; ...

[0199] 5.3.5.5 Cell Group Configuration

[0200] 5.3.5.5.1 General

[0201] The network configures the UE with a master cell group (MCG) and zero or one secondary cell group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] , and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . In the CellGroupConfig IE, the network provides configuration parameters for a cell group.

[0202] Upon receipt of the CellGroupConfig IE, the UE performs the following actions:

[0203] 1> if the CellGroupConfig contains a CellGroupConfig with reconfigurationWithSync:

[0204] 2> perform a synchronous reconfiguration according to 5.3.5.5.2;

[0205] 2> if suspended, resume all suspended radio bearers ;

[0206] 2> if suspended, resume SCG transmission for all radio bearers , unless suspendedSCG is set to "true";

[0207] 1> if the CellGroupConfig contains suspendedSCG set to "true":

[0208] 2> consider the SCG as suspended and perform the actions specified in 5.3.5.5.X;

[0209] *****************************************************************************

[0210] exist Figure 13 In steps 2 and 3, the UE receives the SN RRC reconfiguration message via SRB3, where the SN RRC reconfiguration may include the information described in step 1 above. Step 1 has already described some actions the UE takes upon receiving the message, such as pausing or resuming SCG transmission according to the operating mode set by the SN. Regarding the reconfiguration of synchronization behavior, there may be further UE actions (e.g., periodically performing random access to the target PSCell), depending on how the SN sets the SCG operating mode and what the SCG operating mode might have been before the UE received the message. This step may also include some improvements to the above actions, such as pausing SCG transmission. Different scenarios are considered:

[0211] ·Scenario A) The source SCG is in power saving mode, and the target SCG is in power saving mode.

[0212] • Scenario B) The source SCG is in active / normal mode, and the target SCG is in power-saving mode.

[0213] ·Scenario C) The source SCG is in power saving mode, and the target SCG is in active / normal mode.

[0214] Scenario A) Source SCG is in power saving mode and target SCG is in power saving mode

[0215] In a first alternative, the UE receives a SCG RRCReconfiguration (e.g. RRCReconfiguration message, also called SN reconfiguration) and if this message contains an indication that the SCG is to be considered in power saving mode of operation (e.g. suspended SCG), the UE stores the message, or at least some parts of it (e.g. reconfigurationWithSync of IEReconfigurationWithSync), but it does not apply the message, or at least some parts of it (e.g. reconfigurationWithSync of IE ReconfigurationWithSync), at reception, but only when it receives a command from the network indicating a SCG mode of operation change (in this case from power saving mode of operation to normal mode of operation). For example, the message can contain some information to be applied at reception, e.g. bearer related configuration, SCG measurement configuration (if RRM measurements are to be performed while the SCG is in power saving mode of operation (e.g. suspended SCG)); but information to be stored at reception, e.g. synchronization reconfiguration. The compliance check and the transmission of the complete message can be handled in different ways, e.g. the following examples:

[0216] - In one option, at reception of the message, the UE performs the compliance check. If the compliance is successfully fulfilled, the UE sends an indication of the reception of the message to the network, e.g. RRCReconfigurationComplete. Upon reception of this message, the network (e.g. SN) knows that the PSCell change procedure of the SCG in suspended mode of operation is successful and the message is stored at the UE (to be applied at a certain point in time determined by the network when another command to resume the SCG is received).

[0217] - In another option, the UE does not perform the compliance check at reception of the message but starts to perform it only when it needs to apply the message, e.g. when it receives a command from the network to switch to normal mode of operation. The UE performs the compliance check and sends an indication of the reception of the message to the network, e.g. RRCReconfigurationComplete, only at the time of the resumption (or switch from power saving mode of operation to normal / active mode of operation). Upon reception of this message, the network (e.g. SN) knows that the PSCell change procedure of the SCG in suspended mode of operation is successful.

[0218] - For both options, if the UE cannot comply with the message (cannot fulfill the compliance), the UE performs at least one of the following actions:

[0219] o Continues to use the configuration used before reception of the RRCReconfiguration message; this can include that the UE takes into account the SCG mode of operation before reception of the message;

[0220] o if the MCG transmission is not suspended, initiate the SCG failure information procedure as specified in subclause 5.7.3 to report the SCG reconfiguration error, the connection reconfiguration procedure ends, possibly including information about the failure and the running mode in the SCG failure report; or

[0221] o initiate the connection re-establishment procedure as specified in clause 5.3.7, the connection reconfiguration procedure ends.

[0222] In this first alternative, upon reception of the message indicating the power saving mode of the SCG (e.g. suspended SCG), the UE does not perform an action as if the message has been applied, i.e. the fact that the UE stores the message without applying (or some parts of the message like reconfigurationWithSync) should be interpreted as one possible way to implement the method. Assuming modelling or implementation, the content described as first option can have a different style if the delta signalling applies, e.g. if the SCG RRCReconfiguration message does not contain an indication of a full configuration. In that case, there can be different options, e.g. the following examples:

[0223] • In one option, upon reception of the SCG configuration, the UE stores: i) the SCG configuration received according to the target (e.g. SCG RRCReconfiguration or parts thereof), and ii) the SCG configuration already stored according to the source (can be stored as RRCReconfiguration* or in a UE variable). Then, upon reception of the command to resume the SCG, both configurations are resumed and the UE applies the SCG configuration according to the target (e.g. UE applies RRCReconfiguration) with the SCG configuration according to the source as baseline (or current SCG configuration).

[0224] • In another option, the UE first generates an SCG configuration that is equivalent to the UE having applied the SCG configuration according to the target and with the SCG configuration according to the source as baseline; then stores this final configuration and applies it only upon reception of the command to resume the SCG.

[0225] • In any of these cases, the command to resume the connection contains a further configuration of the SCG, if the SCG is resumed using an RRC R message (an RRCReconfiguration**), this RRCReconfiguration** is further applied. In other words, the UE generates an equivalent SCG configuration including the target applied to the baseline source and then applies the RRCReconfiguration**.

[0226] • In another option, only full configuration of the target PSCell in power saving mode of operation is allowed to simplify the procedure.

[0227] In a second alternative, the UE receives a SCG RRCReconfiguration message (RRCReconfiguration) and, if this message contains an indication that the SCG is considered to be in power saving mode of operation (e.g. suspended SCG), the UE applies the message upon reception of reconfigurationWithSync (of IE ReconfigurationWithSync) and performs actions including random access in the target PSCell and transmission of RRC reconfiguration complete. After performing these actions, the UE can consider the SCG to be in power saving mode of operation (e.g. suspended / deactivated SCG) and perform actions accordingly.

[0228] In a third alternative, the UE receives a SCG RRCReconfiguration message (RRCReconfiguration) and, if this message contains an indication that the SCG is considered to be in power saving mode of operation (e.g. suspended SCG), the UE checks whether another indication is included in the message to apply the message upon reception (so that the UE behaves as in the second alternative) or whether the message is to be stored and only applied upon reception of another command to switch the SCG from power saving mode to normal / active / activated mode of operation (so that the UE behaves as in the first alternative). In this case, both the source and target SCG (i.e. target PSCell and source PSCell) are in power saving mode of operation (e.g. both relate to a suspended / deactivated SCG) and transmission of the SCG has been suspended when the PSCell change was triggered. In other cases where a mode of operation change occurs, further actions can be required. Since in this case the source SCG is in power saving mode of operation, the UE’s current SCG configuration is stored. Therefore, before applying another SCG configuration (e.g. SCG RRC reconfiguration of the target SCG), the UE’s current SCG configuration is restored.

[0229] Scenario B) Source SCG is in active / normal mode and target SCG is in power saving mode:

[0230] In scenario B, the first, second and third alternatives of scenario A apply equally. In addition, the UE also suspends / stops / aborts SCG transmission; the reason is that the source SCG is in active / normal mode of operation while the target SCG is in power saving mode, i.e. SCG transmission is not continued after the PSCell change. In other words, if the mode of operation set for the target SCG indicates power saving mode of operation, SCG transmission is not resumed upon suspension.

[0231] Scenario C) Source SCG is in power saving mode and target SCG is in active / normal mode

[0232] In scenario C, the second alternative of scenarios A and B also applies. In other words, the UE can also perform the actions described accordingly. However, since in this case the source SCG is in power saving mode, the current SCG configuration of the UE is stored. Therefore, before applying another SCG configuration (e.g. SCG RRC reconfiguration of the target SCG), the current SCG configuration of the UE is restored.

[0233] In these different scenarios, there are some common aspects:

[0234] - First alternative:

[0235] o If the target SCG operation mode is power saving (e.g. SCG suspended), the UE does not apply a synchronized reconfiguration, e.g. does not perform random access in the target PSCell;

[0236] - Second alternative:

[0237] o Regardless of the target SCG operation mode (e.g. SCG suspended or normal / active), the UE applies a synchronized reconfiguration (e.g. performs random access in the target PSCell) before entering the power saving mode of the SCG (e.g. before suspending the SCG).

[0238] - Third alternative:

[0239] o Indication controls whether to perform the actions according to the first alternative or the second alternative.

[0240] A possible implementation example in the RRC specification for the first alternative is shown below.

[0241] First alternative

[0242] Another aspect that can be considered in this first alternative is how the UE knows that the SCG RRC reconfiguration is not applied, but only stored (and only applied at reception of a resume / activate command). In one option, the SCG RRC reconfiguration message is contained in an IE, possibly in a RRC container, where a field of the associated IE indicates that the target SCG mode is to be set to a power saving mode, like a suspended SCG. This SCG RRC reconfiguration message is to be stored. This IE is contained in another RRCReconfiguration message received by the UE, and can contain no other configuration than the IE, or can contain some configuration that the network wants the UE to apply at reception, e.g. some bearer reconfiguration at reception. In this example, a UE variable is used to model the UE storing the SCG configuration. In this example, it is also assumed that the command to resume the suspended SCG is transmitted via RRC, although other alternatives (e.g. MAC CE) are possible alternatives.

[0243] *****************************************************************************

[0244]

[0245] 5.3.5.3 RRCReconfiguration received by the UE

[0246] The UE, upon reception of the RRCReconfiguration, or upon execution of a conditional reconfiguration (CHO or CPC), shall perform the following actions: ...

[0248] 1> if the RRCReconfiguration message includes suspendConfig-SCG:

[0249] 2> suspend SCG transmission for all radio bearers, if not suspended already;

[0250] 2> store the SCG configuration;

[0251] 2> store nr-suspend-scg; ...

[0253] / / second loop when the UE receives a command to resume the suspended PSCell, e.g.

[0254] / / because of PSCell change

[0255]

[0256] 1> if the RRCReconfiguration message includes resume-SCG:

[0257] 2> resume the SCG configuration;

[0258] 2> apply the stored nr-suspend-scg;

[0259] 2> resume all suspended radio bearers and resume SCG transmission for all radio bearers, if suspended; ...

[0261] 5.3.5.3 Reception of RRCReconfiguration by the UE

[0262] Upon receipt of RRCReconfiguration, or upon performing a conditional reconfiguration (CHO or CPC), the UE shall perform the following actions: ...

[0264] 1> if the RRCReconfiguration includes secondaryCellGroup:

[0265] 2> perform cell group configuration for the SCG as specified in 5.3.5.5; ...

[0267] 5.3.5.5 Cell group configuration

[0268] 5.3.5.5.1 General

[0269] The network configures the UE with a master cell group (MCG) and zero or one secondary cell group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] , and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . In the CellGroupConfig IE, the network provides configuration parameters for a cell group.

[0270] Upon receipt of the CellGroupConfig IE, the UE performs the following actions:

[0271] 1> if the CellGroupConfig contains a CellGroupConfig with reconfigurationWithSync:

[0272] 2> resume all suspended radio bearers and resume SCG transmission for all radio bearers, if suspended;

[0273] 2> perform a synchronous reconfiguration according to 5.3.5.5.2; ...

[0275] *****************************************************************************

[0276] Example of SN initiated SN modification with MN involvement

[0277] One example method includes setting a mode of operation of the SCG when performing SN-initiated SN modification procedure with MN involvement. Figure 14 Signaling flow 1400 example for SN-initiated SN modification with MN involvement is shown, according to an example of the present disclosure. The SN uses this procedure to perform a configuration change of the SCG within the same SN, e.g., to trigger a modification / release of user plane resource configuration, and to modify the configuration within the SN, including the setting of the SCG mode of operation, e.g., to set the SCG to suspended (or other power saving mode of operation), or to normal mode of operation when a PSCell change is triggered (e.g., when new security keys are needed or the MN needs to perform PDCP data recovery).

[0278] In Figure 14 In step 1 shown, the SN sends a SN Modification Required message containing a SN RRC Reconfiguration message to the UE, which contains an indication whether the SCG is considered to be in power saving mode of operation (e.g., SCG suspended) or normal mode of operation (so that the UE knows the target state of the new PSCell / SCG being modified). The indication whether the SCG is considered to be in power saving mode of operation (e.g., SCG suspend indication) can be included in the SN Modification Required message so that the MN is aware of the mode of operation of the SCG. In one option, if the SCG is in power saving mode of operation (e.g., SCG suspended) and the message contains the SCG configuration (e.g., with SCG synchronous reconfiguration), the UE resumes the SCG configuration as indicated (if suspended for incremental signaling purposes) and sets the mode of operation of the SCG. Details are provided in steps 4 and 5. The SN RRC Reconfiguration message is an RRCReconfiguration message generated by the SN and provided to the MN.

[0279] In Figure 14Step 4 in this procedure has some similarities (common UE actions) compared to Step 1 in 5.2.1. In Step 1 of 5.2.1, the SN sends an SN RRC Reconfiguration message to the UE over SRB3, where the SN RRC Reconfiguration can be an RRCReconfiguration message (or equivalent message) generated by the SN and can include the reconfigurationWithSync field of the IE ReconfigurationWithSync as part of the cellGroupConfig configuration for the SCG, and an indication of the operational mode of the SCG that the UE is to set / assume when performing this procedure. One difference, however, is that in Step 4 of this implementation, the SN sends an SN RRC Reconfiguration message (RRCReconfiguration message (or equivalent message) generated by the SN and possibly including the reconfigurationWithSync field of the IE ReconfigurationWithSync as part of the cellGroupConfig configuration for the SCG, and an indication of the operational mode of the SCG that the UE is to set / assume when performing this procedure) to the MN. The MN, upon reception, generates another RRC Reconfiguration (in MN format, e.g., RRCReconfiguration*) that includes the SN RRC Reconfiguration message (RRCReconfiguration) as the SCG configuration. For example, the MN sets the nr-scg field to the RRCReconfiguration* within the RRCReconfiguration.

[0280]

[0281] Upon reception, the UE applies the RRCReconfiguration* message (in MN format) and applies the nr-SCG field, as shown in the following example:

[0282] *****************************************************************************

[0283] 5.3.5.3 Reception of RRCReconfiguration by the UE

[0284] Upon receipt of the RRCReconfiguration, or when performing conditional reconfiguration (CHO or CPC), the UE shall perform the following actions: ...

[0286] 1> if the RRCReconfiguration includes mrdc-SecondaryCellGroupConfig:

[0287] 2> if the mrdc-SecondaryCellGroupConfig is set to setup: ...

[0289] 3> if the received mrdc-SecondaryCellGroup is set to nr-SCG:

[0290] 4> perform RRC reconfiguration according to 5.3.5.3 on the RRCReconfiguration message contained in the nr-SCG; ...

[0292] *****************************************************************************

[0293] From this point, where the UE applies the message associated with the nr-SCG field, the actions can correspond to the actions described in step 1 of Figure 13 , where the RRCReconfiguration message received over SRB3 in step 1 of Figure 13 corresponds to the RRCReconfiguration received in the nr-SCG. Figure 13 An example of step 1 of is reproduced again, although other examples / embodiments apply.

[0294] An example is shown below, where the message RRCReconfiguration containing the IE CellGroupConfig secondaryCellGroup contains a synchronous reconfiguration (IE ReconfigurationWithSync reconfigurationWithSync), also contains an explicit indication of the mode of operation as part of the CellGroupConfig IE, since this mode of operation applies to the entire cell group:

[0295]

[0296]

[0297] When performing a PSCell change (e.g. without SN change), there can be further UE actions depending on the mode of operation set by the network for the SCG. For example, in legacy cases, when the UE receives a CellGroupConfig with spCellConfig and reconfigurationWithSync, the UE resumes all suspended radio bearers and resumes SCG transmission for all radio bearers, if suspended. However, according to this approach, the resumption of SCG transmission for all radio bearers, if suspended, is only performed when the mode of operation for the SCG is set to normal (or active, depending on how normal / legacy operation is defined). Still according to this approach, if the mode of operation for the SCG is set to suspended (or any other power saving mode of operation), such operation is not performed upon reception of the CellGroupConfig (but will eventually be performed when the SCG is later resumed). An example of the RRC specification text is shown below, where this part has been modified to implement this approach:

[0298] *****************************************************************************

[0299] 5.3.5.3 Reception of an RRCReconfiguration by the UE

[0300] The UE, upon receipt of an RRCReconfiguration, or upon performing a conditional reconfiguration (CHO or CPC), shall: ...

[0302] 1> if the RRCReconfiguration includes secondaryCellGroup:

[0303] 2> perform cell group configuration for the SCG as specified in 5.3.5.5; ...

[0305] 5.3.5.5 Cell Group Configuration

[0306] 5.3.5.5.1 General

[0307] The network configures the UE with a master cell group (MCG) and zero or one secondary cell group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] , and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . In the CellGroupConfig IE, the network provides configuration parameters for a cell group.

[0308] According to the received CellGroupConfig IE, the UE performs the following operations:

[0309] 1> if the CellGroupConfig contains a CellGroupConfig with reconfigurationWithSync:

[0310] 2> resume all suspended radio bearers ;

[0311] 2> perform a synchronous reconfiguration according to 5.3.5.5.2;

[0312] 2> consider the SCG as suspended and perform the actions specified in 5.3.5.5.X if modeOfOperation is set to "normal";

[0313] 3> if suspended, resume SCG transmission for all radio bearers;

[0314] 1> if the CellGroupConfig contains modeOfOperation set to "suspend":

[0315] 2> consider the SCG as suspended and perform the actions specified in 5.3.5.5.X; ...

[0317] *****************************************************************************

[0318] In another example, the RRCReconfiguration message contains a message of the IE CellGroupConfig of secondaryCellGroup, the CellGroupConfig contains a synchronous reconfiguration (IEReconfigurationWithSync of reconfigurationWithSync) containing an indication indicating whether the running mode of the SCG is to be set to the power saving running mode (e.g. suspended SCG). Without such indication will be interpreted by the UE as setting the running mode to normal (i.e. not in power saving state).

[0319]

[0320]

[0321] As in the previous example, there can be further UE actions depending on the mode of operation set by the network for the SCG at the time of performing the PSCell change (e.g., without SN change). According to this example of the method, if the mode of operation of the SCG is set to active or normal, the UE only resumes all suspended actions. Still according to this example of the method, if the mode of operation of the SCG is set to suspended (or any other power saving mode of operation), no such actions are performed upon reception of the CellGroupConfig (but eventually when the SCG is resumed later). An example of the RRC specification text is shown below, where it has been modified to implement this part of the method:

[0322] *****************************************************************************

[0323] 5.3.5.3 Reception of RRCReconfiguration by the UE

[0324] The UE, upon receipt of the RRCReconfiguration, or upon performing conditional reconfiguration (CHO or CPC), shall: ...

[0326] 1> if the RRCReconfiguration includes secondaryCellGroup:

[0327] 2> perform cell group configuration for the SCG as specified in 5.3.5.5; ...

[0329] 5.3.5.5 Cell Group Configuration

[0330] 5.3.5.5.1 General

[0331] The network configures the UE with a master cell group (MCG) and zero or one secondary cell group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] , and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . In the CellGroupConfig IE, the network provides configuration parameters for a cell group.

[0332] Depending on the received CellGroupConfig IE, the UE performs the following actions:

[0333] 1> if the CellGroupConfig contains a CellGroupConfig with reconfigurationWithSync:

[0334] 2> resume all suspended radio bearers ;

[0335] 2> perform a synchronous reconfiguration according to 5.3.5.5.2;

[0336] 2> consider the SCG as suspended and perform the actions specified in 5.3.5.5.X if modeOfOperation is set to "normal";

[0337] 3＞ if suspended, resume SCG transmission for all radio bearers;

[0338] 1> if the CellGroupConfig contains modeOfOperation set to "suspend":

[0339] 2> consider the SCG as suspended and perform the actions specified in 5.3.5.5.X; ...

[0341] 5.3.5.5 Cell Group Configuration

[0342] 5.3.5.5.1 General

[0343] The network configures the UE with a master cell group (MCG) and zero or one secondary cell group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . In the CellGroupConfig IE, the network provides configuration parameters for a cell group.

[0344] Upon receipt of the CellGroupConfig IE, the UE performs the following actions:

[0345] 1> if the CellGroupConfig contains a CellGroupConfig with reconfigurationWithSync:

[0346] 2> perform a synchronous reconfiguration according to 5.3.5.5.2;

[0347] 2> if suspended, resume all suspended radio bearers ;

[0348] 2＞ if suspended, resume SCG transmission for all radio bearers , unless suspendedSCG is set to "true";

[0349] 1> if the CellGroupConfig contains suspendedSCG set to "true":

[0350] 2> consider the SCG suspended and perform the actions specified in 5.3.5.5.x;

[0351] *****************************************************************************

[0352] exist Figure 14 In steps 5, 6, and 7, the UE (via SRB1) receives the nr-SCG SN RRC reconfiguration message within an RRCReconfiguration* message in MN format. This SN RRC reconfiguration may include the information described in step 4 above. Some actions the UE takes upon receiving this message have already been described in step 4, such as pausing or resuming SCG operation according to the operating mode set by the SN. Regarding the reconfiguration of synchronization behavior, there may be further UE actions (e.g., periodically performing random access to the target PSCell), depending on how the SN sets the SCG's operating mode and what the SCG's operating mode might have been before the UE received the message. This step may also include some improvements to the above operations, such as pausing SCG transmission. Different scenarios are considered:

[0353] -Scenario A) Source SCG is in power saving mode → Target SCG is in power saving mode

[0354] -Scenario B) Source SCG is in active / normal mode → Target SCG is in power saving mode

[0355] -Scenario C) Source SCG is in power saving mode → Target SCG is in active / normal mode

[0356] Scenario A) Source SCG is in power saving mode and target SCG is in power saving mode

[0357] In a first alternative, the UE receives the SCG RRCReconfiguration message (RRCReconfiguration) and, if this message contains an indication that the SCG is considered to be in power saving mode of operation (e.g. suspended SCG), the UE stores the message or at least some parts of it (e.g. reconfigurationWithSync of IE ReconfigurationWithSync) but it does not apply the message, or at least some parts of it (e.g. reconfigurationWithSync of IE ReconfigurationWithSync), at reception but only when it receives an order from the network indicating a change of SCG mode of operation (in this case from power saving to normal mode of operation). Upon reception of the RRCReconfiguration* message in MN format, the UE sends an RRCReconfigurationComplete* message in MN format to the MN. The compliance check of the received SCG configuration (i.e. RRCReconfiguration in nr-scg) and the transmission of the SCG complete message within RRCReconfiguration-Complete* can be handled in different ways, e.g.:

[0358] - In one option, upon reception of the SCG RRCReconfiguration message, the UE performs the compliance check. If the compliance is successful, the UE sends an indication of the reception of a confirmation message to the network, e.g. RRCReconfigurationComplete in RRCReconfigurationComplete*. The MN sends the RRCReconfigurationComplete to the SN so that upon reception of the RRCReconfigurationComplete, the SN knows that the PSCell change procedure with the SCG in suspended mode of operation is successful and the message is stored at the UE (to be applied at a certain point in time determined by the network, upon reception of another command to resume the SCG).

[0359] - In another option, the UE does not perform compliance check upon reception of the SCG RRCReconfiguration message, but it starts performing only when it needs to apply it, e.g. when it receives an order from the network to switch to normal operation mode of the SCG. Only upon resumption (or switching from power saving to normal / active operation mode) the UE performs compliance check and sends an indication of the reception of a confirmation message to the network, e.g. RRCReconfigurationComplete, possibly in an MRDC uplink message. Upon reception of this message, the MN can send an RRCReconfigurationComplete to the SN, so the SN knows that the PSCell change procedure of the SCG in suspended operation mode was successful.

[0360] - For both options, if the UE cannot comply with the message (cannot comply), the UE performs at least one of the following actions:

[0361] o continue using the configuration used before receiving the RRCReconfiguration message; this can include that the UE considers the SCG operation mode before receiving the message;

[0362] o if the MCG transmission is not suspended, initiate the SCG failure information procedure as specified in subclause 5.7.3 to report the SCG reconfiguration error, the connection reconfiguration procedure ends, possibly including information about the failure and the operation mode in the SCG failure report; or

[0363] o initiate the connection re-establishment procedure as specified in clause 5.3.7, the connection reconfiguration procedure ends.

[0364] In this first alternative, upon reception of a message indicating a power saving mode of the SCG (e.g. suspended SCG), the UE does not perform an action as if the message has been applied, i.e. the fact that the UE stores the message without applying (or certain parts of the message like reconfigurationWithSync) should be interpreted as one possible way to implement this approach. Assuming modelling or implementation, the content described as first option can have a different style if the incremental signaling applies, e.g. if the SCG RRCReconfiguration message does not contain an indication of a complete configuration. In this case, there can be different options, e.g.:

[0365] - In one option, upon reception of the SCG configuration, the UE stores: i) the SCG configuration received according to the target (e.g. SCG RRCReconfiguration or part thereof), and ii) the SCG configuration already stored according to the source (which can be stored as RRCReconfiguration* or in a UE variable). Then, upon reception of the command to resume the SCG, both configurations are resumed and the UE applies the SCG configuration according to the target (e.g. the UE applies RRCReconfiguration) with the SCG configuration according to the source as baseline (or current SCG configuration).

[0366] - In another option, the UE first generates an SCG configuration which is equivalent to the UE having applied the SCG configuration according to the target and with the SCG configuration according to the source as baseline; then stores this final configuration and applies it only upon reception of the command to resume the SCG.

[0367] - In any of these cases, the command to resume the connection contains further configuration of the SCG, if the SCG is resumed using an RRC R message (an RRCReconfiguration**), this RRCReconfiguration** is further applied. In other words, the UE generates an equivalent SCG configuration including the target applied to the baseline source and then applies the RRCReconfiguration**.

[0368] - In another option, only full configuration of the target PSCell in power saving mode is allowed to simplify the procedure.

[0369] In a second alternative, the UE receives an SCG RRCReconfiguration message (RRCReconfiguration) and, if this message contains an indication that the SCG is considered to be in power saving mode of operation (e.g. suspended SCG), the UE applies the message upon reception of reconfigurationWithSync (of IE Reconfiguration-WithSync) and performs actions including random access and transmission of RRC reconfiguration complete in the target PSCell. After performing these actions, the UE can consider the SCG to be in power saving mode of operation (e.g. suspended / deactivated SCG) and perform actions accordingly.

[0370] In a third alternative, the UE receives the SCG RRCReconfiguration message (RRCReconfiguration) and, if this message contains an indication that the SCG is considered to be in power saving mode of operation (e.g. a suspended SCG), the UE checks whether another indication is included in the message at the time of reception to apply the message (so that the UE behaves as in the second alternative) or whether the message is to be stored and applied only upon reception of another command to switch the SCG from power saving mode to normal / active / activated mode of operation (so that the UE behaves as in the first alternative). In this case, both the source and target SCG (i.e. target PSCell and source PScell) are in power saving mode of operation (e.g. both are associated with a suspended / deactivated SCG) and, when the PSCell change is triggered, the transmission of the SCG is already suspended. In other cases where a change of mode of operation occurs, further actions can be required. Since in this case the source SCG is in power saving mode of operation, the current SCG configuration of the UE is stored. Therefore, before applying another SCG configuration (e.g. the SCG RRC reconfiguration of the target SCG), the current SCG configuration of the UE is restored.

[0371] Scenario B) Source SCG is in active / normal mode -> target SCG is in power saving mode

[0372] In scenario B, the first, second and third alternatives of scenario A apply equally. In addition, the UE also suspends / stops / aborts the SCG transmission; the reason is that the source SCG is in active / normal mode of operation while the target SCG is in power saving mode, i.e. the SCG transmission is not continued after the PSCell change. In other words, if the mode of operation set for the target SCG is power saving mode of operation, the SCG transmission is not resumed upon suspension.

[0373] Scenario C) Source SCG is in power saving mode -> target SCG is in active / normal mode

[0374] In scenario C, the second alternative of scenarios A and B also applies. In other words, the UE can also perform the actions described accordingly. However, since in this case the source SCG is in power saving mode of operation, the current SCG configuration of the UE is stored. Therefore, before applying another SCG configuration (e.g. the SCG RRC reconfiguration of the target SCG), the current SCG configuration of the UE is restored.

[0375] In these different scenarios, there are some common aspects:

[0376] - First alternative:

[0377] o If the target SCG mode of operation is power saving (e.g. SCG suspended), the UE does not apply the synchronous reconfiguration, e.g. does not perform random access in the target PSCell;

[0378] - Second alternative:

[0379] o Regardless of the operation mode of the target SCG (e.g. SCG suspended or normal / active), the UE applies a synchronous reconfiguration (e.g. performs random access in the target PSCell) before entering the power saving mode of the SCG (e.g. before suspending the SCG);

[0380] - Third alternative:

[0381] o Indicate whether the control performs the actions according to the first or second alternative.

[0382] A possible implementation example in the RRC specification for the first alternative is shown below.

[0383] First alternative

[0384] Another aspect that can be considered in this first alternative is how the UE knows that the SCG RRC reconfiguration (e.g. RRCReconfiguration in nr-SCG within the RRCReconfiguration* in MN format) will not be applied but only stored (and only applied upon reception of the resume / activate command). In one option, the SCG RRC reconfiguration message is contained in an IE, possibly in a RRC container, where a field of the associated IE indicates that the target SCG mode will be set to the power saving mode, like a suspended SCG. This SCG RRC reconfiguration message will be stored. This IE is contained in another RRCReconfiguration message received by the UE and can contain no other configuration but only the IE, or can contain some configuration that the network wants the UE to apply at reception, e.g. some bearer reconfiguration to apply at reception. In this example, a UE variable is used to model the UE storing the SCG configuration.

[0385] In this example, it is also assumed that the command to indicate the resumption of the suspended SCG is via RRC transmission, although other alternatives (e.g. MAC CE) are also possible alternatives.

[0386] *****************************************************************************

[0387] / / First loop when the UE receives the RRCReconfiguration PSCell change message

[0388]

[0389] 5.3.5.3 Reception of RRCReconfiguration by the UE

[0390] Upon receipt of RRCReconfiguration, or when performing conditional reconfiguration (CHO or CPC), the UE shall perform the following actions: ...

[0392] 1> if the RRCReconfiguration message includes mrdc-SecondaryCellGroupConfig:

[0393] 2> if mrdc-SecondaryCellGroupConfig is set to setup: ...

[0395] 3> if the received mrdc-SecondaryCellGroup is set to nr-SCG:

[0396] 4> perform RRC reconfiguration according to 5.3.5.3 on the RRCReconfiguration message contained in the nr-SCG; ...

[0398] ***************************************************************************** ...

[0400] / / Second loop when the UE applies the RRCReconfiguration PSCell change message (i.e. RRCReconfiguration within nr-SCg in the RRC Reconfiguration in MN format)

[0401]

[0402] 5.3.5.3 Reception of RRCReconfiguration by the UE

[0403] Upon receipt of RRCReconfiguration, or when performing conditional reconfiguration (CHO or CPC), the UE shall perform the following actions: ...

[0405] 1> if the RRCReconfiguration message includes suspendConfig-SCG:

[0406] 2> suspend SCG transmission for all radio bearers if not already suspended;

[0407] 2> store the SCG configuration;

[0408] 2> store nr-suspend-scg; ...

[0410] / / third loop when the UE receives the order to resume the suspended PSCell, e.g.,

[0411] / / because of PSCell change

[0412]

[0413]

[0414] 1> if the RRCReconfiguration message includes resume-SCG:

[0415] 2> resume the SCG configuration;

[0416] 2> apply the stored nr-suspend-scg;

[0417] 2> resume SCG transmission for all radio bearers that were suspended, resume SCG transmission for all radio bearers; ...

[0419] 5.3.5.3 Reception of RRCReconfiguration by the UE

[0420] Upon receipt of RRCReconfiguration, or when performing conditional reconfiguration (CHO or CPC), the UE shall perform the following actions: ...

[0422] 1> if the RRCReconfiguration includes secondaryCellGroup:

[0423] 2> perform cell group configuration for the SCG as specified in 5.3.5.5; ...

[0425] 5.3.5.5 Cell group configuration

[0426] 5.3.5.5.1 General

[0427] The network configures the UE with a master cell group (MCG) and zero or one secondary cell group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331

[10] and for NE-DC, the SCG is configured as specified in TS 36.331

[10] . In the CellGroupConfig IE, the network provides configuration parameters for a cell group.

[0428] Upon reception of the CellGroupConfig IE, the UE performs the following operations:

[0429] 1> if the CellGroupConfig contains a CellGroupConfig with reconfigurationWithSync:

[0430] 2> resume all suspended radio bearers and resume SCG transmission for all radio bearers, if suspended;

[0431] 2> perform a synchronous reconfiguration according to 5.3.5.5.2; ...

[0433] *****************************************************************************

[0434] Example of MN initiated SN change

[0435] The method comprises setting the operation mode of the SCG when performing a MN initiated SN change procedure. Figure 15 A signaling flow 1500 example for MN initiated SN change according to examples of the present disclosure is shown. The MN initiated SN change procedure is used to transfer the UE context from the source SN to the target SN and change the SCG configuration in the UE from one SN to another, where the context can also include information about the operation mode of the SCG, for example, the power saving mode of the SCG, such as a suspended SCG.

[0436] In Figure 15In step 1 of the SN Addition procedure, the MN initiates the SN change by requesting the target SN to allocate resources for the UE. The MN sends a SN Addition Request including the current SCG context of the UE (possibly including the current SCG operation mode, e.g. power saving mode like SCG suspended, active, resumed) so that the target SN (T-SN) upon reception can determine whether to change the operation mode. The MN can include information about how long the UE has been in power saving mode of the SCG, e.g. a timer value. The MN can trigger a MN initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration and allow to provide data forwarding related information prior to step 1. In this case, the current SCG configuration can contain the operation mode of the SCG; or, if it is in power saving mode, an indication, e.g. SCG suspended, otherwise it is active (option is better backward compatibility).

[0437] In step 2, upon reception of the SN Addition Request including the SCG configuration, the T-SN can include the current SCG operation mode of the UE (e.g. power saving / suspended mode, or normal / active) and determines the SCG operation mode after SN change, e.g. power saving / suspended mode, or normal / active. Thus, the T-SN determines whether the operation mode of the SCG is changed or kept the same as in the source. After determination, the T-SN generates a SCG RRC Reconfiguration (e.g. RRCReconfiguration) including a synchronization reconfiguration (for PSCell change of a UE configured with MR-DC) and including an indication of the SCG operation mode related to the target PSCell. The T-SN sends a SN Addition Request Acknowledge message including the SCG RRC Reconfiguration (e.g. RRCReconfiguration) including a synchronization reconfiguration (for PSCell change of a UE configured with MR-DC) and including an indication of the SCG operation mode related to the target PSCell. The indication of the SCG operation mode related to the target PSCell can also be included outside the RRC container, i.e. in the XnAP message, if the MN needs to know the target SCG operation mode.

[0438] In step 3, if the allocation of target SN resources is successful, the MN initiates the release of source SN resources including an indication of the cause of the SCG mobility, an indication of the target operation mode of the SCG, e.g. power saving operation mode like suspended SCG. If data forwarding is needed, the MN provides the data forwarding address to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides the data forwarding address received from the target SN to the source SN. The reception of the SN Release Request message triggers the source SN to stop providing user data to the UE.

[0439] - The MN can determine whether data forwarding is needed based on the operation mode set by the T-SN for the SCG associated with the target PSCell and target SN.

[0440] o In one option, if the operation mode set by the T-SN for the SCG associated with the target PSCell and target SN is set to active / normal / activated, the MN determines to perform data forwarding and performs actions such as steps 3a, 3b, 3c, 8a, 8b and 9 in the figure.

[0441] - The MN determines whether data forwarding is needed according to the target SCG operation mode set by the T-SN and the current SCG operation mode of the UE.

[0442] o In one option, if the operation mode set by the T-SN for the SCG associated with the target PSCell and target SN is set to active / normal / activated, and the source operation mode of the SCG is set to active / normal / activated, the MN determines to perform data forwarding and performs actions such as steps 3a, 3b, 3c, 8a, 8b and 9 in the figure.

[0443] - The MN can determine whether data forwarding is needed according to the current SCG operation mode of the UE.

[0444] o In one option, if the operation mode of the current SCG (source SCG) of the UE is set to suspended, the MN determines not to perform data forwarding and does not perform actions such as steps 3a, 3b, 3c, 8a, 8b and 9 in the figure.

[0445] o In one option, if the operation mode of the current SCG (source SCG) of the UE is set to active / normal / activated, the MN determines not to perform data forwarding and does not perform actions such as steps 3a, 3b, 3c, 8a, 8b and 9 in the figure.

[0446] In step 4, the SN sends an SN RRC Reconfiguration message (RRCReconfiguration message (or equivalent message) generated by the SN, possibly including the reconfigurationWithSync field of the IEReconfigurationWithSync for a part of the cellGroupConfig configuration of the SCG, and an indication indicating the operation mode of the SCG that the UE is to set / assume when performing this procedure) to the MN. The above different alternatives can also apply here.

[0447] Steps 5, 6 and 7 are similar to Figure 14Steps 5, 6 and 7 of Figure 1. The difference can involve the handling of the RRC Reconfiguration Complete message received at the MN (in MN format, like RRCReconfigurationComplete*). The MN sends the RRCReconfigurationComplete to the SN (associated with the source PSCell and the target PSCell). However, in a MN initiated SN change, the target PSCell is associated to a different SN, here denoted T-SN, while the source PSCell is associated to the source SN (denoted S-SN). Therefore, the MN sends the RRCReconfigurationComplete to the target SN (T-SN), where the complete message is received at the MN according to the method described above.

[0448] Example of SN initiated SN change

[0449] The method comprises setting the operation mode of the SCG when performing the SN initiated SN change procedure. Figure 16 A signaling flow example for SN initiated SN change according to examples of the disclosure is shown. The SN initiated SN change procedure is used to transfer the UE context from the source SN to the target SN and change the SCG configuration in the UE from one SN to another, where the UE context can contain an indication of the SCG operation mode, e.g. power saving operation mode like SCG suspend.

[0450] In Figure 16 In step 1 of Figure 1, the source SN initiates the SN change procedure by sending a SN change required message containing the candidate target node ID and possibly the SCG configuration (to support delta configuration) and measurement results related to the target SN. This SCG configuration can contain an indication of the current operation mode of the SCG, so the T-SN is aware of this and decides to keep the same operation mode or change it. In one alternative, this indication is included within the RRC container of the SCG configuration in the SN change required message, or outside, i.e. as part of the XnAP information in the SN change required message. Figure 16 Steps 2, 3 and 4 of Figure 1 are similar to steps 2, 3 and 4 of Figure 15 Steps 1, 2 and 4 of Figure 1. Figure 16 Steps 5, 6 and 7 of Figure 1. Figure 15 Steps 5, 6 and 7 of Figure 1.

[0451] PSCell change of PSCell in power saving mode of operation

[0452] In some examples, the MN or SN (e.g., source SN or target SN) can determine to perform a PSCell change (e.g., SN change) based on measurement results received by the UE in power saving mode of the UE SCG, such as suspended SCG. In this case, the measurements can include cell quality measurements (such as RSRP, RSRQ, SINR) of cells at the same frequency as the UE’s current PSCell. The measurement results can have been received in a SCG failure report or a measurement report, e.g., for power saving mode of the SCG without suspension of SCGmeasConfig.

[0453] Although the subject matter described herein can 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 FIG. 1. Figure 17 For simplicity, only network QQ106, network nodes QQ160 and QQ160b, and WDs QQ110, QQ110b, and QQ110c are depicted in Figure 17 In practice, a wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other communication device). In the example shown, network nodes QQ160 and wireless devices (WDs) QQ110 are depicted as being part of a wireless network. The wireless network can provide service to one or more wireless devices QQ110, QQ110b, and QQ110c located in a small

[0454] The wireless network can comprise or interface to any type of access network

[0455] Network QQ106 can 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 among devices.

[0456] Network node QQ160 and WD QQ110 comprise various components described in more detail below. These components work together to provide network node and / or wireless device functionality such as providing wireless connections in a wireless network. In different embodiments, the wireless network can 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 can facilitate or participate in communication of data and / or signals between and among each other. Network nodes QQ160 comprise antennas 2a, 2b, processing circuitry 4, and a

[0457] 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 equipment capable of providing the wireless device with access to a wireless network or to equipment capable of providing other functions in a wireless network as well as combinations thereof. 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 can be categorized based on the amount of coverage they provide (or, stated differently, the transmission power they employ) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Base stations can be a relay node or a relay donor node controlling a relay. A network node can 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 called remote radio heads (RRHs). Such remote radio units can be integrated with, or operate in conjunction with, an antenna tower. Parts of a distributed radio base station can also be referred to as nodes of 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 can be a virtual network node as described in more detail below. More generally, however, network nodes can 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 a wireless network or to provide some other function within a wireless network.

[0458] In Figure 17 The network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interfaces QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although Figure 17The network nodes QQ160 illustrated in the example wireless network can represent devices that include combinations of the illustrated hardware components, but other embodiments can include network nodes with different combinations of components. It is to be understood that the network nodes include any suitable combinations of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Furthermore, while the components of the network nodes QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node can comprise multiple different physical components (e.g., device readable medium QQ180 can comprise multiple individual disk drives as well as multiple RAM modules) constituting a single illustrated component. Similarly, a network node QQ160 can be composed of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which can have their own respective components. In certain scenarios in which a network node QQ160 includes multiple separate components (such as BTS and BSC components), one or more separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair can in some instances be considered a single separate network node. In some embodiments, network node QQ160 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components can be reused (e.g., the same antenna QQ162 can be shared by the multiple RATs). Network node QQ160 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into network node QQ160 as the same or different chipsets or chip sets and other components. Processing circuitry QQ170 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 QQ170 can include processing information obtained by processing circuitry QQ170 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 an

[0459] The processing circuitry QQ170 can 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 processing circuit, combinations of any of the above, or the like, provided herein purpose a network node QQ160 function alone or in combination with other network node QQ160 elements such as a device readable medium QQ180 and / or a user interface QQ190. For example, processing circuitry QQ170 can execute instructions stored in a memory within processing circuitry QQ170 or instructions stored in a memory QQ180 to provide the functionality described herein. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170 can include a system on a chip (SOC).

[0460] In some embodiments, processing circuitry QQ170 can include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 can 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 QQ172 and baseband processing circuitry QQ174 can be on the same chip or set of chips, boards, or units.

[0461] 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 equipment can be performed by processing circuitry QQ170 executing instructions stored in a memory within processing circuitry QQ170 or instructions stored in a memory QQ180. In alternative embodiments, some or all of the functionality can be provided by processing circuitry QQ170 without executing instructions stored in a separate or discrete memory from processing circuitry QQ170, such as in a hardwired manner. In any of those embodiments, whether executing instructions stored in a memory or not, processing circuitry QQ170 can be configured to perform the described functions. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160 but are enjoyed by network node QQ160 as a whole, and / or by end users and the wireless network generally.

[0462] Device readable medium QQ180 can include any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic materials, optical materials, random access memory (RAM), read only memory (ROM), mass storage media, and / or any other volatile or non-volatile non-transitory device readable and / or computer-executable memory devices storing information, data, and / or instructions that can be used by processing circuitry QQ170. Device readable medium QQ180 can 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 QQ170 and used by network node QQ160. Device readable medium QQ180 can include, but can not be limited to, all types of volatile and non-volatile computer-readable media, storage media, and memory media including magnetic storage media, optical storage media, solid-state media and / or any other storage media.

[0463] Interface QQ190 is used for the wired or wireless communication of signaling and / or data between network nodes QQ160, network QQ106, and / or WDs QQ110. As shown, interface QQ190 comprises a port / terminal QQ194 for sending and receiving data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that can be coupled to, or in some embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 can be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry can be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 can convert the digital data into a signal with the appropriate channel and bandwidth parameters using a combination of filters QQ198 and / or amplifiers QQ196. The signal can then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 can collect signals transmitted by other network nodes or WDs. The signals can then be converted by radio front end circuitry QQ192 into digital data, which can be passed to processing circuitry QQ170. In other embodiments, the interface can comprise different components and / or different combinations of components. In some alternative embodiments, network node QQ160 can not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 can comprise radio front end circuitry and can be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 can be considered a part of interface QQ190. In still other embodiments, interface QQ190 can include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172 as part of a radio unit (not shown), and interface QQ190 can communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

[0464] Antenna QQ162 can include one or more antennas or antenna arrays, configured to send and / or receive wireless signals. Antenna QQ162 can be coupled to radio front-end circuitry QQ190 and can be any type of antenna and / or antenna array. In some embodiments, antenna QQ162 can include one or more omnidirectional, sector or panel antennas, which can operate to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna can be used to send / receive radio signals in all directions, a sector antenna can be used to send / receive radio signals in specific areas, and a panel antenna can be a line of sight antenna used to send / receive radio signals in relatively straight lines. In some cases, the use of more than one antenna can be referred to as MIMO. In certain embodiments, antenna QQ162 can be separate from network node QQ160 and can be connectable to network node QQ160 through an interface or port.

[0465] Antenna QQ162, interface QQ190, and / or processing circuitry QQ170 can 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 can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna QQ162, interface QQ190, and / or processing circuitry QQ170 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and / or signals can be transmitted to a wireless device, another network node and / or any other network equipment.

[0466] Power supply circuitry QQ187 can comprise or be coupled to power management circuitry and can be configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power supply circuitry QQ187 can receive power from power supply QQ186. Power supply QQ186 and / or power supply circuitry QQ187 can be configured to supply the power to the components of network node QQ160 in a form suitable for use by each of the components (e.g., at a voltage and current level that each component needs). Power supply QQ186 can be incorporated into, or external to, power supply circuitry QQ187 and / or network node QQ160. For example, network node QQ160 can be connectable to an external power supply (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power supply supplies power to power supply circuitry QQ187. As a further example, power supply QQ186 can comprise one or more electrically rechargeable batteries or batteries having capacity to supply power to power supply circuitry QQ187. Batteries can be rechargeable, and can be recharged by power supply circuitry QQ187. Other types of power supply circuitry QQ187 can be used to supply power to network node QQ160. Figure 17In addition to the components illustrated in FIG. 12, the components of network node QQ160 can also include a radio interface configured to transmit and receive data, according to physical, media, and higher- layer protocols under the control of the CPU QQ170. The network node QQ160 can further include a power source configured to supply power to the various components of the network node QQ160. The power source can include one or more rechargeable batteries that can be repeatedly charged and discharged. The power source can supply varying amounts of power to the components of the network node QQ160 as needed. In some embodiments, the power source can supply different levels of power to the components of the network node QQ160 based on a power management policy.

[0467] As used herein, wireless device (WD) refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network equipment and / or other wireless devices. Unless otherwise mentioned, the term WD can be used interchangeably herein with user equipment (UE) and / or user terminal (UT). The communication can comprise transmitting and / or receiving wireless signals. In some embodiments, the WD can be configured to transmit and / or receive data using electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for conveying information over a network. In some embodiments, the WD can be designed to transmit and / or receive information without direct human interaction (e.g., automatically). For example, the WD can be designed to transmit information to a network and / or receive information from a network according to a predetermined schedule, without further human intervention. Examples of WDs include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminals, wireless endpoints, mobile stations, tablet computers, laptops, laptop computers embedded electronic devices (LEEs), laptop computers mounted electronic devices (LMEs), smart devices, wireless customer-premises equipment (CPE), vehicle-mounted wireless terminal equipment, etc. A WD can be able to make and receive voice and / or data transmissions over the wireless network. The WD can further be capable of accessing information over the network, receiving data scheduled transmissions over the network, and transmitting private information over the network. A WD can further be capable of transmitting and / or receiving data according to a scheduled access protocol. Although the WD is typically a mobile device capable of movement, in some embodiments, the WD can be fixed and / or stationary, such as a desktop computer or a smart device installed in a fixed location.

[0468] As illustrated, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136, and power circuitry QQ137. WD QQ110 can include multiple instances of each component, e.g., as needed for different wireless

[0469] Antenna QQ111 can include one or more antennas or antenna arrays, configured to send and / or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 can be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111, interface QQ114, and / or processing circuitry QQ120 can be configured to perform any of the receiving or transmitting operations described herein as being performed by a WD. Any information, data and / or signals can be received from a network node and / or another WD. In some embodiments, radio front end and / or antenna QQ111 can be considered an interface. As illustrated, interface QQ114 includes radio front end circuitry QQ112 and antenna QQ111. Radio front end circuitry QQ112 includes one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120 and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120. Radio front end circuitry QQ112 can be coupled to or a part of processing circuitry QQ120. In some embodiments, WD QQ110 can not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 can comprise radio front end circuitry and can be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 can be considered a part of interface QQ114. Radio front end circuitry QQ112 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters for transmission, using a combination of filters QQ118 and / or amplifiers QQ116. The radio signal can then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 can collect radio signals, which are then converted into digital data by radio front end circuitry QQ112. The digital data can be passed on to processing circuitry QQ120. In other embodiments, the interface can comprise different components and / or combinations of components.

[0470] Processing circuitry QQ120 can 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 processing circuitry, in conjunction with a memory, such as device readable medium QQ130. These components can be implemented as part of the same device or different devices. Processing circuitry QQ120 can be configured to perform processing, such as processing related to the techniques discussed herein, such as determining a location of a device, providing a location of a device, or any other processing. In some embodiments, processing circuitry QQ120 can include a system on a chip (SoC) that integrates one or more of the components of WD QQ110. In some embodiments, processing circuitry QQ120 can include a single core or multiple cores of an Intel Core i5 processor or similar processor.

[0471] As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry can comprise different components and / or different combinations of components. In certain embodiments processing circuitry QQ120 of WD QQ110 can comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 can be combined into one chip or set of chips, and RF transceiver circuitry QQ122 can be on a separate chip or set of chips. In yet another alternative embodiment, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 can be combined into the same chip or set of chips, and application processing circuitry QQ126 can be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 can be combined into the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 can be part of interface QQ114. RF transceiver circuitry QQ122 can condition RF signals for processing circuitry QQ120.

[0472] In certain embodiments, some or all of the functionality described herein as being performed by a WD can be performed by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided by processing circuitry QQ120 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 QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 or other components of WD QQ110 alone or in conjunction with other components, but are enjoyed by WD QQ110 as a whole, and / or by end users and the wireless network generally.

[0473] Processing circuitry QQ120 can 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 QQ120, can include processing information obtained by processing circuitry QQ120 (e.g., by

[0474] Device readable medium QQ130 can be used for storage of information and instructions to be executed by processing circuitry QQ120. Device readable medium QQ130 can be an example of a computer readable storage medium. Device readable medium QQ130 can include one or more types of computer readable storage medium. For example, device readable medium QQ130 can include semiconductor memory devices, such as erasable programmable read only memories (EPROM), electrically erasable programmable read only memories (EEPROM), and flash memories; magnetic storage devices, such as magnetic disks or tapes; optical storage devices, such as compact discs (CDs) or digital versatile discs (DVDs); tapes; solid state drives (SSDs); and / or other appropriate devices.

[0475] The user interface devices QQ132 can provide means for allowing a human user to interact with the WD QQ110. Such interaction can be of many forms, such as visual, audial, tactile, etc. The user interface devices QQ132 can operate under direction of the processing circuitry QQ120 to produce output to the user and to allow input to be received from the user. The interaction can be, for example, to allow the user to operate the WD QQ110 and to allow the user to receive the benefit of the operation of the WD QQ110. The output can be of many forms, such as visual (including text), audio, haptic, etc. The input can be of many forms, such as voice input, touch input, motion input, etc.

[0476] Auxiliary equipment QQ134 can be used to provide specific functionality not all WDs can need. This can be sensors for doing measurements for various purposes, interfaces for extra types of communication, etc. The composition and type of auxiliary equipment QQ134 can vary depending on the embodiment and / or scenario.

[0477] In some embodiments, power source QQ136 can 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, can also be used. WD QQ110 can further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any of the functionality described or indicated herein. Power circuitry QQ137 can in some embodiments comprise power management circuitry. Power circuitry QQ137 can additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 can be connectable to the external power source (such as an electricity outlet) through an input circuitry or interface (such as an electrical power cable). Power circuitry QQ137 can also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This can be, for example, for the purpose of charging power source QQ136. Power circuitry QQ137 can perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 that are supplied power by power circuitry QQ137.

[0478] Figure 18 One embodiment of a UE is illustrated in accordance with various aspects described herein. As used herein, a user equipment or UE does not necessarily have a human user in the sense of a person using the equipment; instead, a UE can represent a device that is intended for sale to, or operation by, a human user but that can not, or that can initially not, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended for sale to, or operation by, an end user but that can be associated with or operated for the benefit of a user (e.g., a smart power meter). UE QQ200 can be any UE Figure 18 As shown, UE QQ200 is one example of a WD configured to communicate using one or more communication standards promulgated by the third generation partnership project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. The term WD and UE can be used interchangeably herein. Thus, although Figure 18 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[0479] In Figure 18In some embodiments, the UE QQ200 includes processing circuitry QQ201 that is operably coupled to input / output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 (including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221), communication subsystem QQ231, power source QQ233, and / or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 can include other similar types of information. Certain UEs can utilize all of the components shown in FIG. 2, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. Figure 18 In some embodiments, the UE QQ200 includes processing circuitry QQ201 that is operably coupled to input / output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 (including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221), communication subsystem QQ231, power source QQ233, and / or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 can include other similar types of information. Certain UEs can utilize all of the components shown in FIG. 2, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0480] In Figure 18 In some embodiments, processing circuitry QQ201 can be configured to process computer instructions and data. Processing circuitry QQ201 can be configured to implement any sequential state machine operative to

[0481] In the depicted embodiment, input / output interface QQ205 can be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 can be configured to use the output device through input / output interface QQ205. The output device can use the same type of interface port as the input device. For example, a USB port can be used to provide input to and output from UE QQ200. The output device can 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 QQ200 can be configured to use the input device through input / output interface QQ205 to allow a user to capture information into UE QQ200. The input device can include a touch-sensitive or presence-sensitive display, a camera (for example, a digital still or motion camera), 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 can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, 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 can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0482] In Figure 18 RF interface QQ209 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 can be configured to provide a communication interface to network QQ243a. Network QQ243a can encompass

[0483] The RAM QQ217 can be configured to include a cache of the storage medium QQ221. The ROM QQ219 can be configured to include a cache of the storage medium QQ221. The ROM QQ219 can be configured to store computer instructions or data, e.g., that are non-transitory. For example, the ROM QQ219 can be configured to store invariant low-level system code or data for basic system functions (including start-up or reception of keystrokes) that are stored in a non-volatile memory outside of (that is, separate from) the processing circuitry QQ201, e.g., that are stored in the storage medium QQ221. The storage medium QQ221 can be on-board the UE QQ200 or external to UE QQ200. For example, the storage medium QQ221 can include a magnetic storage, an optical disk, a solid state drive, or any mix of these, or the like. The storage medium QQ221 can be removable and / or built-in. In one example, the storage medium QQ221 can include a non-transitory computer-readable medium. In one example, the storage medium QQ221 can include a non-transitory computer-readable storage medium. In one example, the storage medium QQ221 can include a non-transitory computer-readable storage medium that is tangible. In this aspect, the storage medium QQ221 can be a material, a compound, or a combination of material and compound that is tangible. In one example, the storage medium QQ221 can include a computer-readable storage medium that is non-transitory. In this aspect, the storage medium QQ221 can be a material, a compound, or a combination of material and compound that does not fit within the definition of a transitory signal. In this aspect, the storage medium QQ221 can be a material, a compound, or a combination of material and compound that is tangible.

[0484] The storage medium QQ221 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), soft disk drive, flash memory, external hard drives, thumb drives, pen drives, key drives, high-density digital versatile disks (DVDs) or other optical disk drives, memory cards (e.g., SD cards, xD picture cards), smart cards, a floppy diskette, a magnetic tape, a magnetic strip, an audio tape, a holographic disk, a Bernoulli drive, an optical disk, a compact disk, a mini disk, a feather disk, a laser disk, a floppy disk, a diskette, a thumb drive, a flash drive, a bay drive, an extended capacity drive (ECD), a micro drive, other removable memory, or any combination thereof. The storage medium QQ221 can allow the UE QQ200 to access computer-executable instructions, application programs or the like, stored on a transitory or non-transitory storage medium to off-load data or to store information for later access. An article of manufacture, such as one utilizing a communication system can be tangibly embodied in the storage medium QQ221, which can comprise a device readable medium.

[0485] In Figure 18In particular embodiments, processing circuitry QQ201 can be configured to use communication subsystem QQ231 to communicate with network QQ243b. Network QQ243a and network QQ243b can be the same network or networks or different network or networks. Communication subsystem QQ231 can be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another wireless communication device such as another WD, UE, or base station of a radio access network (RAN). Each transceiver can include transmitter QQ233 and / or receiver QQ235 to implement transmitter or receiver functions of the transceiver, as appropriate for the RAN links. Further, transmitter QQ233 and receiver QQ235 of each transceiver can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0486] The communication functions of communication subsystem QQ231 can include data communication, voice communication, multimedia communication, short-range communications, location-based communications (e.g., using the global positioning system (GPS) to determine a location), another like function, or any combination thereof. For example, communication subsystem QQ231 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b can 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 QQ243b can be a cellular network, a Wi-Fi network, and / or a near-field network. Power source QQ213 can be configured to provide alternating current (AC) or direct current (DC) power to the components of UE QQ200.

[0487] The features, benefits and / or functions described herein can be implemented in one or more components of the UE QQ200, or elsewhere. Further, the features, benefits and / or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231 can be configured to include any of the components described herein. Further, processing circuitry QQ201 can be configured to communicate with any such components over bus QQ202. In another example, any of the components described herein can be represented by instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions. In another example, the functionality of any of the components described herein can be partitioned between processing circuitry QQ201 and communication subsystem QQ231. In another example, non-computationally intensive functions of any of the components described herein can be implemented in software or firmware and computation-intensive functions can be implemented in hardware.

[0488] Figure 19 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments can be virtualized. In this context, virtualization means the creation of a virtual version of a device or system that can include the virtualization of hardware platforms, storage devices and network resources. As used herein, virtualization can apply to nodes (e.g., virtualized base stations or virtualized radio access nodes) or devices (e.g., UEs, wireless devices or any other type of communication device) or components thereof, and involves an implementation in which at least a portion of the functionality is implemented as a virtual component (e.g., by one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).

[0489] In some embodiments, part or all of the functions described herein can be implemented as virtual components executed by one or more applications QQ320 implemented in one or more virtual environments QQ300 hosted by one or more hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (for example, a core network node), then the network node can be entirely virtualized. Such virtual nodes can be implemented as one or more applications QQ320 (which can also be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) running in a virtualization environment QQ300 and executable on one or more hardware nodes QQ330. These nodes can be of any suitable type. As one example, the hardware nodes QQ330 can comprise server computers configured to provide infrastructure as a service (IaaS), platform as a service (PaaS), or software as a service (SaaS). By way of another example, the hardware nodes QQ330 can comprise server computers configured to provide cloud computing. The applications QQ320 can be provided by any cloud computing or software distribution service.

[0490] Virtualization environment QQ300, comprises general or dedicated network hardware devices QQ330, comprising a set of one or more processors or processing circuitry QQ360, which can 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 can comprise memory QQ390-1, which can be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device can comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interfaces QQ380. Each hardware device can also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and / or instructions executable by processing circuitry QQ360. Software QQ395 can include any type of software including software to instantiate one or more virtualization layers, software to execute virtual machines, and software allowing the software to perform functions, features, and / or benefits described in this document related to some embodiments.

[0491] Virtual machines QQ340, comprise virtual processing, memory, networking or interface, and storage, and can be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 can be implemented on one or more virtual machines QQ340 and can be implemented by different ways.

[0492] During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 can present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

[0493] As Figure 19 shown, hardware QQ330 can be a standalone network node with generic or specific components. Hardware QQ330 can comprise antenna QQ3225 and some functions can be implemented in software. Alternatively, hardware QQ330 can be part of a larger cluster of hardware (such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed by management and orchestration (MANO) QQ3100, which, among other things, oversees lifecycle management of applications QQ320.

[0494] Hardware virtualization is in some cases referred to as network function virtualization (NFV). NFV can 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.

[0495] In the context of NFV, virtual machine QQ340 can be a software implementation of a physical machine that runs programs just as if they were executing on a physical, non-virtual machine. Each virtual machine QQ340 and that part of the hardware QQ330 that executes that virtual machine, whether hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with others, forms a separate virtual network elements (VNE).

[0496] 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 QQ340 on top of hardware networking infrastructure QQ330 and corresponds to Figure 19 application(s) QQ320 in

[0497] In some embodiments, one or more radio units QQ3200 (each including one or more transmitters QQ3220 and one or more receivers QQ3210) can be coupled to one or more antennas QQ3225. Radio units QQ3200 can communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

[0498] In some embodiments, some signaling can be effected with the use of control system QQ3230, which can alternatively be used for communication between hardware nodes QQ330 and radio units QQ3200.

[0499] Reference is made to Figure 20According to an embodiment, the communication system includes a telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access networks QQ411, such as a radio access network, and a core network QQ414. The access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c, within which wireless devices can typically communicate with the base station QQ412a, QQ412b, QQ412c. Each base station QQ412a, QQ412b, QQ412c is connectable to the core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491, QQ492 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 QQ412.

[0500] The telecommunication network QQ410 is itself connected to a host computer QQ430, which can embody a standalone, a cloud-implemented, or a distributed server; or a plurality of servers working together. The host computer QQ430 can be administered or controlled by a service provider. The connection QQ421 and the connection QQ422 between the telecommunication network QQ410 and the host computer QQ430 can extend directly from the core network QQ414 to the host computer QQ430 or can go via an optional intermediate network QQ420. The intermediate network QQ420 can be a public, private or hosted network; and can include a combination of one or more networks owned and / or operated by other service providers; the intermediate network QQ420, if any, can be a backbone network or a

[0501] Figure 20The communication system as a whole enables connectivity between the connected UEs QQ491, QQ492 and the host computer QQ430. The connectivity can be described as an over-the-top (OTT) connection QQ450. The host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and / or signaling over the OTT connection QQ450 using the access network QQ411, the core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. The OTT connection QQ450 can be transparent in the sense that the entities involved in the communication, e.g. base stations QQ412, UEs QQ491, QQ492, and host computers QQ430, are not aware of all the others but exchange communication data and / or signaling with an intermediate entity. OTT connection QQ450 can be a wired or wireless connection. For example, the OTT connection QQ450 can be a wireless connection if the UE QQ491 is a mobile device such as a smartphone, a wireless modem, a tablet computer, a laptop, or a similar device configured to communicate wirelessly with the base station QQ412. The base station QQ412 can be configured to communicate with the host computer QQ430 via the core network QQ414 and with the UE QQ491 via the access network QQ411. The base station QQ412 can therefore act as a relay or switch for the transfer of data and / or signaling between the core network QQ414 and the UE QQ491. The base station QQ412 can be configured to perform functions including but not limited to radio resource management, load balancing, cell selection, synchronization, and scheduling. The base station QQ412 can serve a plurality of UEs QQ491.

[0502] Reference will now be made to Figure 21 An example implementation of the UE, base station, and host computer described in the preceding paragraphs will now be discussed in relation to the example of a communication system QQ500. In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which can have storage and / or processing capabilities. In particular, processing circuitry QQ518 can 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 QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 can be an application that provides services to users via their remote terminals, e.g. UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing services to users, host application QQ512 can provide user data that is transmitted using OTT connection QQ550.

[0503] The communication system QQ500 also includes a base station QQ520 provided in the telecommunications system, and includes hardware QQ525 enabling it to communicate with the host computer QQ510 and the UE QQ530. Hardware QQ525 may include a communication interface QQ526 for establishing and maintaining wired or wireless connections with different communication devices of the communication system QQ500, and a radio interface QQ527 for setting up and maintaining connections with the coverage area served by the base station QQ520. Figure 21 (Not shown in the image) The UE QQ530 has at least a wireless connection to the QQ570. The communication interface QQ526 can be configured to facilitate connection to the host computer QQ510 QQ560. The connection to QQ560 can be direct or it can be through the core network of the telecommunications system ( Figure 21 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware QQ525 of the base station QQ520 also includes processing circuitry QQ528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The QQ520 base station also has built-in software QQ521, which can also be accessed via an external connection.

[0504] The communication system QQ500 also includes the previously mentioned UE QQ530. Its hardware QQ535 may include a radio interface QQ537, configured to establish and maintain a radio connection QQ570 with a base station serving the coverage area currently occupied by the UE QQ530. The hardware QQ535 of the UE QQ530 further includes processing circuitry QQ538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown), adapted to execute instructions. The UE QQ530 also includes software QQ531, which is stored in or accessible by the UE QQ530 and executable by the processing circuitry QQ538. Software QQ531 includes a client application QQ532. With the support of the host computer QQ510, the client application QQ532 can be used to provide services to human or non-human users through the UE QQ530. Within the host computer QQ510, the executing main application QQ512 communicates with the executing client application QQ532 via an OTT connection QQ550 terminated between the UE QQ530 and the host computer QQ510. When providing services to the user, the client application QQ532 can receive request data from the main application QQ512 and provide user data in response to the request data. The OTT connection QQ550 can transmit both request data and user data. The client application QQ532 can interact with the user to generate the user data it provides.

[0505] It is important to note thatFigure 21 The host computer QQ510, base station QQ520, and UE QQ530 illustrated in Figure 13 can be seen from the software perspective as Figure 20 The host computer QQ430, one of the base stations QQ412a, QQ412b, QQ412c, and the UE QQ491, QQ492 of Figure 14 can be seen as instances of the host computer QQ510, the base station QQ520, and the UE QQ530 of Figure 13, respectively. That is, their internal workings can be as shown in Figure 13 and independently, the surrounding network topology can be that of Figure 14. Figure 21 The host computer QQ430, one of the base stations QQ412a, QQ412b, QQ412c, and the UE QQ491, QQ492 of Figure 14 can be seen as instances of the host computer QQ510, the base station QQ520, and the UE QQ530 of Figure 13, respectively. That is, their internal workings can be as shown in Figure 13 and independently, the surrounding network topology can be that of Figure 14. Figure 20 The host computer QQ430, one of the base stations QQ412a, QQ412b, QQ412c, and the UE QQ491, QQ492 of Figure 14 can be seen as instances of the host computer QQ510, the base station QQ520, and the UE QQ530 of Figure 13, respectively. That is, their internal workings can be as shown in Figure 13 and independently, the surrounding network topology can be that of Figure 14.

[0506] In Figure 13, the OTT connection QQ550 is drawn abstractly with a cloud to indicate that the OTT connection QQ550 is made between the host computer QQ510 and the UE QQ530 via one or more intermediary devices and networks not shown in the drawing. These intermediary devices and networks can include Figure 21 In Figure 13, the OTT connection QQ550 is drawn abstractly with a cloud to indicate that the OTT connection QQ550 is made between the host computer QQ510 and the UE QQ530 via one or more intermediary devices and networks not shown in the drawing. These intermediary devices and networks can include

[0507] The wireless connection QQ570 between the UE QQ530 and the base station QQ520 is in accordance with the teachings of the embodiments of the present disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE QQ530 using the OTT connection QQ550, in which the wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments can improve the connectivity and / or the data rate, and thereby provide benefits such as improved connectivity, connection reliability, and / or data rate.

[0508] A measurement procedure can be implemented for monitoring data rate, latency and other factors improved by one or more embodiments. There can also be an optional network functionality for reconfiguring OTT connection QQ550 between host computer QQ510 and UE QQ530, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring OTT connection QQ550 can be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments, sensors (not shown) can be deployed in or in association with communication devices through which OTT connection QQ550 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ511, QQ531 can compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550 can include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect base station QQ520, and base station QQ520 can be unaware of or uninvolved in the reconfiguring. Procedures and functionalities of this sort can be known and practiced in the art, as reflected by the above-mentioned common patent applications. In certain embodiments, measurements can involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency, and the like. The measurements can be implemented in software QQ511 and QQ531 to cause messages to be transmitted with OTT connection QQ550, particularly empty messages or “dummy” messages, whilst measurements are made.

[0509] Figure 22 is a flowchart of a method implemented in a communication system including a host computer, a base station and a UE, in accordance with an embodiment. The communication system can be that described with reference to Figure 20 and 21 The description in this section will only include references to the figures of Figure 22 In step QQ610, the host computer provides user data. In sub-step QQ611 (which can be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which can be optional), the base station transmits to the UE the user data carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described in the present disclosure. In step QQ640 (which can also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0510] Figure 23 is a flowchart of a method implemented in a communication system including a host computer, a base station and a UE, in accordance with an embodiment. The communication system can be that described with reference to Figure 20 and 21those described above with reference to the drawing figures. To simplify the present disclosure, in this section only references to the above-mentioned drawing figures will be included. Figure 23 In step QQ710 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 QQ720, the host computer initiates a transmission of the user data to the UE. The transmission can pass via the base station, according to the teachings of the embodiments described in the present disclosure. In step QQ730 (which can be optional), the UE receives the user data carried in the transmission.

[0511] Figure 24 is a flowchart of a method implemented in a communication system including a host computer, a base station and a UE, in accordance with an embodiment. The communication system can be that described above with reference to the drawing figures. To simplify the present disclosure, in this section only references to the above-mentioned drawing Figure 20 and 21 those described above with reference to the drawing figures. To simplify the present disclosure, in this section only references to the above-mentioned drawing figures will be included. Figure 24 In step QQ810 (which can be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which can be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which can be optional) of step QQ810, the UE executes a client application which provides the user data in response to receiving the input data provided by the host computer. In providing the user data, the executing client application can further consider user input received from the user. Regardless of the specific manner in which the user data is provided, the UE initiates, in substep QQ830 (which can be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, according to the teachings of the embodiments described in the present disclosure.

[0512] Figure 25 is a flowchart of a method implemented in a communication system including a host computer, a base station and a UE, in accordance with an embodiment. The communication system can be that described above with reference to the drawing figures. To simplify the present disclosure, in this section only references to the above-mentioned drawing Figure 20 and 21 those described above with reference to the drawing figures. To simplify the present disclosure, in this section only references to the above-mentioned drawing figures will be included. Figure 25 In step QQ910 (which can be optional), the base station receives user data from the UE, according to the teachings of the embodiments described in the present disclosure. In step QQ920 (which can be optional), the base station initiates a transmission of the received user data to the host computer. In step QQ930 (which can be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0513] Figure 26 shows a wireless network (e.g. Figure 17The diagram shows a schematic block diagram of device WW00 in a wireless network. This device can be used in wireless devices or network nodes (e.g., Figure 17 This is implemented in the wireless device QQ110 or network node QQ160 shown. Device WW00 is operable to perform the reference. Figure 11 The example methods described herein, as well as any other possible processes or methods disclosed herein. It should also be understood that... Figure 11 The method does not necessarily need to be performed solely by the device WW00. At least some operations of the method can be performed by one or more other entities.

[0514] The virtual device WW00 may include processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be used to cause the receiving unit WW02, and any other suitable unit of the device WW00, to perform corresponding functions according to one or more embodiments of this disclosure.

[0515] like Figure 26 As shown, the device WW00 includes a receiving unit WW02 configured to receive at least one message from a first network node during a reconfiguration process of a second cell group, wherein the at least one message indicates the network operating mode of the wireless devices in the second cell group after the wireless devices have applied the reconfiguration process of the second cell group.

[0516] Figure 27 A wireless network (e.g.) is shown Figure 17 The diagram shows a schematic block diagram of device WW10 in a wireless network. This device can be used in wireless devices or network nodes (e.g., Figure 17 This is implemented in the wireless device QQ110 or network node QQ160 shown. Device WW10 is operable to perform the reference. Figure 12 The example methods described herein, as well as any other possible processes or methods disclosed herein. It should also be understood that... Figure 12 The method does not necessarily need to be performed solely by device WW10. At least some operations of the method can be performed by one or more other entities.

[0517] The virtual device WW10 can include processing circuitry, which can include one or more microprocessor or microcontroller, and other digital hardware, which can include digital signal processors (DSPs), special-purpose computer chips, etc. The processing circuitry can be configured to execute program code stored in memory, which can include one or more types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. In various embodiments, the program code stored in the memory includes program instructions for implementing one or more telecommunication and / or data

[0518] As shown in Figure 27 The apparatus WW10 comprises a sending unit WW12 configured to send, in a reconfiguration procedure of the second cell group, at least one message to the wireless device; wherein the at least one message indicates a mode of operation of the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group.

[0519] The term “unit” can have the conventional meaning in the field of electronics, electrical devices and / or electronic devices, and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions, etc., for performing tasks, processes, calculations, outputs and / or displays, etc., as described herein.

[0520] Embodiments

[0521] The following provides enumerated example embodiments that form part of the present disclosure.

[0522] Group A embodiments

[0523] 1. A method performed by a wireless device for configuring the wireless device with multi-radio access technology dual connectivity (MR-DC) utilizing a first cell group and a second cell group, the method comprising:

[0524] - receiving, in a reconfiguration procedure of the second cell group, at least one message from a first network node;

[0525] - wherein the at least one message indicates a mode of operation of the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group.

[0526] 2. The method of embodiment 1, wherein the mode of operation of the wireless device for the second cell group comprises a mode of operation of the wireless device for a particular cell in the second cell group and / or one or more other cells in the second cell group.

[0527] 3. The method of embodiment 1 or 2, wherein the mode of operation of the wireless device for the second cell group comprises a power saving mode of operation of the wireless device for the second cell group, the particular cell in the second cell group and / or the one or more other cells in the second cell group.

[0528] 4. The method of embodiment 3, wherein the power saving mode comprises a suspend mode or a dormant mode for the second cell group, the particular cell in the second cell group and / or the one or more other cells in the second cell group.

[0529] 5. The method of any one of embodiments 3 to 4, comprising operating the second cell group according to the power saving mode of operation after reconfiguring the second cell group according to the reconfiguration procedure.

[0530] 6. The method of embodiment 5, wherein operating the second cell group according to the power saving mode of operation after reconfiguring the second cell group according to the reconfiguration procedure comprises at least one of:

[0531] - operating the particular cell in the second cell group in a dormant mode;

[0532] - operating the particular cell in the second cell group in a suspend mode;

[0533] - operating the particular cell in the second cell group in a dormant bandwidth part (BWP);

[0534] - stopping monitoring PDCCH for the particular cell and / or the at least one other cell in the second cell group;

[0535] - suspending transmission of data radio bearers (DRBs) associated with the second cell group;

[0536] - suspending transmission of DRBs associated with the particular cell in the second cell group;

[0537] - suspending transmission of DRBs terminated at nodes associated with the second cell group or the particular cell in the second cell group and / or the at least one other cell in the second cell group;

[0538] - suspending DRBs associated with the second cell group;

[0539] - operating the particular cell in the second cell group according to discontinuous reception (DRX); and

[0540] - only monitor PDCCH on the second cell group during a DRX cycle duration configured for the second cell group and / or at least one cell in the second cell group.

[0541] 7. The method of any of embodiments 3 to 6, wherein the previous operational mode of the wireless device for the second cell group prior to receiving the at least one message comprises a power saving operational mode.

[0542] 8. The method of embodiment 7, comprising performing the reconfiguration procedure in response to a command received from the first network node to activate, re-activate or resume the second cell group after receiving the at least one message.

[0543] 9. The method of embodiment 7 or 8, wherein the at least one message comprises an indication to perform the reconfiguration procedure immediately or to perform the reconfiguration procedure in response to a command received from the first network node to activate, re-activate or resume the second cell group.

[0544] 10. The method of embodiment 9, comprising performing the reconfiguration procedure immediately if the indication is to perform the reconfiguration procedure immediately.

[0545] 11. The method of embodiment 9 or 10, comprising performing the reconfiguration procedure in response to a command received from the first network node to activate, re-activate or resume the second cell group after receiving the at least one message if the indication is to perform the reconfiguration procedure in response to a command received from the first network node to activate, re-activate or resume the second cell group.

[0546] 12. The method of embodiment 2, wherein the operational mode of the wireless device for the second cell group comprises a resumed mode, a normal mode, a legacy mode or an active mode.

[0547] 13. The method of any of embodiments 1 to 12, comprising receiving the at least one message from a node or cell associated with the first cell group.

[0548] 14. The method of any of embodiments 1 to 12, comprising receiving the at least one message from a node or cell associated with the second cell group.

[0549] 15. The method of any of embodiments 1 to 14, comprising operating the second cell group according to the operational mode indicated in the at least one message.

[0550] 16. The method of any of embodiments 1 to 15, comprising performing a reconfiguration procedure for the second cell group.

[0551] 17. The method of any one of embodiments 1 to 16, wherein the at least one message comprises at least one RRC message and / or at least one RRC reconfiguration message.

[0552] 18. The method of any one of embodiments 1 to 17, wherein the first group of cells comprises a master cell group (MCG), and the second group of cells comprises a secondary cell group (SCG).

[0553] 19. The method of any one of embodiments 1 to 18, wherein the second group of cells comprises a master cell group (MCG), and the first group of cells comprises a secondary cell group (SCG).

[0554] 20. The method of any one of embodiments 1 to 19, wherein the wireless device comprises a user equipment (UE).

[0555] 21. The method of any one of embodiments 1 to 20, wherein the first network node comprises a base station, a base station control unit (CU), a base station distributed unit (DU), an eNB, an eNB-CU, an eNB-DU, a gNB, a gNB-CU, or a gNB-DU.

[0556] 22. The method of any one of the preceding embodiments, further comprising:

[0557] - providing user data; and

[0558] - forwarding the user data to the host computer for further transmission by transmission to the base station.

[0559] Group B embodiments

[0560] 23. A method performed by a first network node for configuring a wireless device having multi radio access technology dual connectivity (MR-DC) with a first group of cells and a second group of cells, the method comprising:

[0561] - sending at least one message to the wireless device in a reconfiguration procedure of the second group of cells;

[0562] - wherein the at least one message indicates a mode of operation of the wireless device for the second group of cells after the wireless device has applied a reconfiguration procedure for the second group of cells.

[0563] 24. The method of embodiment 23, wherein the mode of operation of the wireless device for the second group of cells comprises a mode of operation of the wireless device for a particular cell in the second group of cells and / or one or more other cells in the second group of cells.

[0564] 25. The method of embodiments 23 or 24, wherein the operational mode of the wireless device for the second cell group comprises a power saving operational mode of the wireless device for the second cell group, a special cell in the second cell group, and / or one or more other cells in the second cell group.

[0565] 26. The method of embodiment 25, wherein the power saving mode comprises a suspended mode or a dormant mode of the second cell group, the special cell in the second cell group, and / or the one or more other cells in the second cell group.

[0566] 27. The method of embodiments 25 or 26, wherein the previous operational mode of the wireless device for the second cell group prior to receiving the at least one message comprises a power saving operational mode.

[0567] 28. The method of embodiment 27, comprising sending a command to the wireless device to cause the wireless device to resume, activate or reactivate the second cell group based on a configuration of the second cell group stored at the wireless device.

[0568] 29. The method of embodiment 27, comprising including in the at least one message an indication of whether to perform a reconfiguration procedure immediately or in response to receiving a command from the first network node to activate, reactivate or resume the second cell group.

[0569] 30. The method of any one of embodiments 25 to 29, comprising stopping transmission of PDCCH to the wireless device on a special cell associated with the second cell group and / or at least one other cell associated with the second cell group.

[0570] 31. The method of embodiment 24, wherein the operational mode of the wireless device for the second cell group comprises a resumed mode, a normal mode, a legacy mode or an active mode.

[0571] 32. The method of any one of embodiments 23 to 31, comprising receiving an indication of the operational mode of the second cell group of the wireless device for reconfiguration according to the reconfiguration procedure from a network node associated with the second cell group prior to sending the at least one message to the wireless device.

[0572] 33. The method of any one of embodiments 23 to 31, comprising sending an indication of the operational mode of the wireless device for the second cell group to a network node associated with the second cell group.

[0573] 34. The method of any one of embodiments 23 to 33, comprising sending context information of the wireless device to a node associated with the second cell group reconfigured according to the reconfiguration procedure.

[0574] 35. The method of any one of embodiments 23 to 34, wherein the at least one message comprises at least one RRC message and / or at least one RRC reconfiguration message.

[0575] 36. The method of any one of embodiments 23 to 35, wherein the first group of cells comprises a master cell group (MCG) and the second group of cells comprises a secondary cell group (SCG).

[0576] 37. The method of any one of embodiments 23 to 36, wherein the second group of cells comprises a master cell group (MCG) and the first group of cells comprises a secondary cell group (SCG).

[0577] 38. The method of any one of embodiments 23 to 37, wherein the wireless device comprises a user equipment (UE).

[0578] 39. The method of any one of embodiments 23 to 38, wherein the first network node comprises a base station, a base station control unit (CU), a base station distributed unit (DU), an eNB, an eNB-CU, an eNB-DU, a gNB, a gNB-CU, or a gNB-DU.

[0579] 40. The method of any one of embodiments 23 to 39, wherein the first network node is associated with a special cell (SpCell) in the first group of cells.

[0580] 41. The method of any one of the preceding embodiments, further comprising:

[0581] - obtaining user data; and

[0582] - forwarding the user data to the host computer or the wireless device.

[0583] Group C embodiments

[0584] 42. A wireless device for configuring a wireless device with multi radio access technology dual connectivity (MR-DC), the wireless device comprising:

[0585] - processing circuitry configured to perform any of the steps of any of Group A embodiments; and

[0586] - power supply circuitry configured to supply power to the wireless device.

[0587] 43. A base station for configuring a wireless device with multi radio access technology dual connectivity (MR-DC), the base station comprising:

[0588] - processing circuitry configured to perform any of the steps of any of Group B embodiments;

[0589] - a power supply circuit configured to supply power to the base station.

[0590] 44. A user equipment (UE) for configuring a wireless device with multi radio access technology dual connectivity (MR-DC), the UE comprising:

[0591] - an antenna configured to send and receive wireless signals;

[0592] - a radio front-end circuitry connected to the antenna and the processing circuitry and configured to condition signals communicated between the antenna and the processing circuitry;

[0593] - the processing circuitry configured to perform any of the steps of any of the Group A embodiments;

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

[0595] - 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

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

[0597] 45. A communication system including a host computer comprising:

[0598] - the processing circuitry configured to provide user data; and

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

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

[0601] 46. The communication system of the previous embodiment, further comprising the base station.

[0602] 47. The communication system of the two previous embodiments, further comprising the UE, wherein the UE is configured to communicate with the base station.

[0603] 48. The communication system of the three previous embodiments, wherein:

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

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

[0606] 49. A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising:

[0607] - at the host computer, providing user data; and

[0608] - 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.

[0609] 50. The method of the preceding embodiment, further comprising at the base station, transmitting the user data.

[0610] 51. The method of the two preceding embodiments, wherein at the host computer the user data is provided by executing a host application, the method further comprising: at the UE, executing a client application associated with the host application.

[0611] 52. A User Equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform one of the three preceding embodiments.

[0612] 53. A communication system including a host computer, comprising:

[0613] - the processing circuitry configured to provide user data; and

[0614] - the communication interface configured to forward the user data to a cellular network for transmission to a User Equipment (UE),

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

[0616] 54. The communication system of the preceding embodiment, wherein the cellular network further includes the base station configured to communicate with the UE.

[0617] 55. The communication system of the two preceding embodiments, wherein:

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

[0619] - the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0620] 56. A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising:

[0621] - at the host computer, providing user data; and

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

[0623] 57. The method of the preceding embodiment, further comprising receiving, at the UE, the user data from the base station.

[0624] 58. A communication system including a host computer comprising:

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

[0626] - wherein the UE includes 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.

[0627] 59. The communication system of the preceding embodiment, further comprising the UE.

[0628] 60. The communication system of the two preceding embodiments, further comprising the base station, wherein the base station includes a radio interface configured to communicate with the UE and a communication interface configured to forward the user data carried from the UE to the base station to the host computer.

[0629] 61. The communication system of the three preceding embodiments, wherein:

[0630] - the host computer’s processing circuitry is configured to execute a host application; and

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

[0632] 62. The communication system of the four preceding embodiments, wherein:

[0633] - the host computer’s processing circuitry is configured to execute a host application, thereby providing request data; and

[0634] - 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.

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

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

[0637] 64. The method of the preceding embodiment, further comprising providing, at the UE, the user data to the base station.

[0638] 65. The method of the two previous embodiments, further comprising:

[0639] - at the UE, executing a client application thereby providing the user data to be transmitted; and

[0640] - at the host computer, executing a host application associated with the client application.

[0641] 66. The method of the three previous embodiments, further comprising:

[0642] - at the UE, executing a client application; and

[0643] - at the UE, receiving input data to the client application, the input data being provided by execution of a host application associated with the client application at the host computer,

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

[0645] 67. 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.

[0646] 68. The communication system of the previous embodiment, further including the base station.

[0647] 69. The communication system of the two previous embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

[0648] 70. The communication system of the three previous embodiments, wherein:

[0649] - the host computer’s processing circuitry is configured to execute the host application;

[0650] - 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.

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

[0652] - the host computer receiving from the base station user data originating from a transmission from the UE to the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

[0653] 72. The method of the previous embodiment, further comprising receiving at the base station the user data from the UE.

[0654] 73. The method of the previous two embodiments, further comprising initiating, at the base station, transmission of the received user data to the host computer.

[0655] Abbreviations

[0656] At least some of the following abbreviations can be used in the present disclosure. If there is an inconsistency between the above usage and the usage between the abbreviations, the above usage should be taken as the preferred meaning. If listed multiple times below, the first list should take precedence over any subsequent list.

[0657] 1xRTT CDMA2000 1x Radio Transmission Technology

[0658] 3GPP Third Generation Partnership Project

[0659] 5G Fifth Generation

[0660] ABS Almost Blank Subframe

[0661] ARQ Automatic Repeat reQuest

[0662] AWGN Additive White Gaussian Noise

[0663] BCCH Broadcast Control Channel

[0664] BCH Broadcast Channel

[0665] CA Carrier Aggregation

[0666] CC Carrier Component

[0667] CCCH SDU Common Control Channel SDU

[0668] CDMA Code Division Multiple Access

[0669] CGI Cell Global Identifier

[0670] CIR Channel Impulse Response

[0671] CP Cyclic Prefix

[0672] CPICH Common Pilot Channel

[0673] CPICH Ec / No Received energy per chip divided by power density in the frequency band

[0674] CQI Channel Quality Information

[0675] C-RNTI Cell RNTI

[0676] CSI Channel State Information

[0677] DCCH Dedicated Control Channel

[0678] DL downlink

[0679] DM demodulation

[0680] DMRS demodulation reference signal

[0681] DRX discontinuous reception

[0682] DTX discontinuous transmission

[0683] DTCH dedicated traffic channel

[0684] DUT device under test

[0685] E-CID enhanced cell ID (positioning method)

[0686] E-SMLC evolved serving mobile location center

[0687] ECGI evolved CGI

[0688] eNB E-UTRAN NodeB

[0689] ePDCCH enhanced physical downlink control channel

[0690] E-SMLC evolved serving mobile location center

[0691] E-UTRA evolved UTRA

[0692] E-UTRAN evolved UTRAN

[0693] FDD frequency division duplex

[0694] FFS further study

[0695] GERAN GSM EDGE radio access network

[0696] gNB base station in NR

[0697] GNSS global navigation satellite system

[0698] GSM global system for mobile communications

[0699] HARQ hybrid automatic repeat request

[0700] HO handover

[0701] HSPA high speed packet access

[0702] HRPD high rate packet data

[0703] LOS line of sight

[0704] LPP LTE positioning protocol

[0705] LTE long term evolution

[0706] MAC medium access control

[0707] MBMS multimedia broadcast multicast service

[0708] MBSFN multimedia broadcast multicast service single frequency network

[0709] MBSFN ABS MBSFN almost blank subframe

[0710] MDT minimization of drive testing

[0711] MIB master information block

[0712] MME mobile management entity

[0713] MSC mobile switching center

[0714] NPDCCH narrowband physical downlink control channel

[0715] NR new radio

[0716] OCNG OFDMA channel noise generator

[0717] OFDM orthogonal frequency division multiplexing

[0718] OFDMA orthogonal frequency division multiple access

[0719] OSS operation support system

[0720] OTDOA observed time difference of arrival

[0721] O&M operation and maintenance

[0722] PBCH physical broadcast channel

[0723] P-CCPCH primary common control physical channel

[0724] PCell primary cell

[0725] PCFICH physical control format indicator channel

[0726] PDCCH physical downlink control channel

[0727] PDP profile delay profile

[0728] PDSCH physical downlink shared channel

[0729] PGW packet gateway

[0730] PHICH Physical Hybrid-ARQ Indicator Channel

[0731] PLMN Public Land Mobile Network

[0732] PMI Precoding Matrix Indicator

[0733] PRACH Physical Random Access Channel

[0734] PRS Positioning Reference Signal

[0735] PSS Primary Synchronization Signal

[0736] PUCCH Physical Uplink Control Channel

[0737] PUSCH Physical Uplink Shared Channel

[0738] RACH Random Access Channel

[0739] QAM Quadrature Amplitude Modulation

[0740] RAN Radio Access Network

[0741] RAT Radio Access Technology

[0742] RLM Radio Link Management

[0743] RNC Radio Network Controller

[0744] RNTI Radio Network Temporary Identifier

[0745] RRC Radio Resource Control

[0746] RRM Radio Resource Management

[0747] RS Reference Signal

[0748] RSCP Received Signal Code Power

[0749] RSRP Reference Symbol Received Power or Reference Signal Received Power

[0750] RSRQ Reference Signal Received Quality or Reference Symbol Received Quality

[0751] RSSI Received Signal Strength Indicator

[0752] RSTD Reference Signal Time Difference

[0753] SCH Synchronization Channel

[0754] SCell Secondary Cell

[0755] SDU Service Data Unit

[0756] SFN system frame number

[0757] SGW serving gateway

[0758] SI system information

[0759] SIB system information block

[0760] SNR signal to noise ratio

[0761] SON self-optimizing network

[0762] SS synchronization signal

[0763] SSS secondary synchronization signal

[0764] TDD time division duplex

[0765] TDOA time difference of arrival

[0766] TOA time of arrival

[0767] TSS tertiary synchronization signal

[0768] TTI transmission time interval

[0769] UE user equipment

[0770] UL uplink

[0771] UMTS universal mobile telecommunications system

[0772] USIM universal subscriber identity module

[0773] UTDOA uplink time difference of arrival

[0774] UTRA universal terrestrial radio access

[0775] UTRAN universal terrestrial radio access network

[0776] WCDMA wideband CDMA

[0777] WLAN wireless local area network

Claims

1. A method performed by a wireless device, the wireless device being configured with multi-radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group, the method comprising: receiving, from a first network node, at least one message in a reconfiguration procedure for the second cell group; wherein the at least one message indicates a mode of operation of the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group, wherein the at least one message further comprises an indication of whether to perform the reconfiguration procedure immediately or in response to receiving a command from the first network node to activate, re-activate, or resume the second cell group.

2. The method of claim 1, wherein, the mode of operation of the wireless device for the second cell group comprises a mode of operation of the wireless device for a particular cell in the second cell group and / or one or more other cells in the second cell group.

3. The method according to claim 1 or 2, characterized in that, the mode of operation of the wireless device for the second cell group comprises a power saving mode of operation of the wireless device for the second cell group, a special cell in the second cell group, and / or one or more other cells in the second cell group, wherein the power saving mode of operation comprises a suspended mode of operation or a dormant mode of operation or a deactivated mode of operation or an inactive mode of operation.

4. The method of claim 3, wherein, comprises at least one of the following: running a special cell in the second cell group in a dormant mode; running the special cell in the second cell group in a suspended mode; running the special cell in the second cell group in a deactivated mode; running the special cell in the second cell group in an inactive mode; running the special cell in the second cell group in a dormant bandwidth part (BWP); stopping monitoring PDCCH of the special cell and / or at least one other cell in the second cell group; suspending transmission of data radio bearers (DRBs) associated with the second cell group; suspending transmission of DRBs associated with a special cell in the second cell group; suspending transmission of DRBs terminated at a node associated with the second cell group or a special cell in the second cell group and / or at least one other cell in the second cell group; suspending DRBs associated with the second cell group; running the special cell in the second cell group according to discontinuous reception (DRX); and monitoring PDCCH on the second cell group only during ON durations of a DRX cycle configured for the second cell group and / or at least one cell in the second cell group.

5. The method according to claim 3 or 4, characterized in that, The previous mode of operation of the wireless device for the second cell group prior to receiving the at least one message comprises a power saving mode of operation, and the method comprises: after receiving the at least one message, in response to receiving a command from the first network node to activate, re-activate or resume the second cell group, performing the reconfiguration procedure.

6. The method of claim 1, wherein, comprises: if the indication is to perform the reconfiguration procedure immediately, performing the reconfiguration procedure immediately; and if the indication is to perform the reconfiguration procedure in response to receiving a command from the first network node to activate, re-activate or resume the second cell group, after receiving the at least one message, in response to receiving a command from the first network node to activate, re-activate or resume the second cell group, performing the reconfiguration procedure.

7. The method of claim 2, wherein, The mode of operation of the wireless device for the second cell group comprises a resumed mode, a normal mode, a legacy mode or an active mode.

8. The method according to any one of claims 1 to 7, characterized in that, comprises receiving the at least one message from a node or cell associated with the first cell group or the second cell group.

9. The method according to any one of claims 1 to 8, characterized in that, comprises: operating the second cell group according to the mode of operation indicated in the at least one message, and / or performing the reconfiguration procedure for the second cell group.

10. The method according to any one of claims 1 to 9, characterized in that, The at least one message comprises at least one RRC message and / or at least one RRC reconfiguration message.

11. The method of any one of claims 1-10, the first cell group comprises a master cell group (MCG) and the second cell group comprises a secondary cell group (SCG); or the second cell group comprises a master cell group (MCG) and the first cell group comprises a secondary cell group (SCG).

12. The method according to any one of claims 1 to 11, characterized in that, The wireless device comprises a user equipment (UE).

13. The method according to any one of claims 1 to 12, characterized in that, The first network node comprises a base station, a base station control unit (CU), a base station distributed unit (DU), an eNB, an eNB-CU, an eNB-DU, a gNB, a gNB-CU or a gNB-DU.

14. The method according to any one of claims 1 to 13, characterized in that, further comprises: providing user data; and forwarding the user data to the host computer through transmission to a base station.

15. A method performed by a first network node, the method being for configuring a wireless device configured with multi radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group, the method comprising: in a reconfiguration procedure for the second cell group, sending at least one message to the wireless device; wherein the at least one message indicates a mode of operation of the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group, wherein the at least one message further comprises an indication of whether to perform the reconfiguration procedure immediately or in response to receiving a command from the first network node to activate, re-activate or resume the second cell group.

16. The method of claim 15, wherein, The operational mode of the wireless device for the second cell group comprises an operational mode of the wireless device for a particular cell in the second cell group and / or one or more other cells in the second cell group.

17. The method according to claim 15 or 16, characterized in that The operational mode of the wireless device for the second cell group comprises a power saving operational mode of the wireless device for the second cell group, a particular cell in the second cell group, and / or one or more other cells in the second cell group, wherein the power saving operational mode comprises a suspended operational mode or a dormant operational mode or a deactivated operational mode or an inactive operational mode.

18. The method of claim 17, wherein, The previous operational mode of the wireless device for the second cell group prior to receiving the at least one message comprises the power saving operational mode, and the method comprises sending a command to the wireless device to cause the wireless device to resume, activate or reactivate the second cell group based on a configuration of the second cell group stored at the wireless device.

19. The method of any one of claims 17-18, wherein, comprises stopping sending PDCCH to the wireless device on a particular cell associated with the second cell group and / or at least one other cell associated with the second cell group.

20. The method of any one of claims 16-19, wherein, The operational mode of the wireless device for the second cell group comprises a resumed mode, a normal mode, a legacy mode or an active mode.

21. The method of any one of claims 15-20, wherein, comprises receiving, prior to sending the at least one message to the wireless device, an indication of the operational mode of the wireless device for the second cell group reconfigured according to the reconfiguration procedure from a network node associated with the second cell group.

22. The method of any one of claims 15-20, wherein, comprises sending an indication of the operational mode of the wireless device for the second cell group to a network node associated with the second cell group.

23. The method of any one of claims 15-22, wherein, comprises sending context information of the wireless device to a node associated with the second cell group reconfigured according to the reconfiguration procedure.

24. The method of any one of claims 15-23, wherein, The at least one message comprises at least one RRC message and / or at least one RRC reconfiguration message.

25. The method of any one of claims 15 to 24, The first cell group comprises a master cell group (MCG) and the second cell group comprises a secondary cell group (SCG); or The second cell group comprises a master cell group (MCG) and the first cell group comprises a secondary cell group (SCG).

26. The method of any one of claims 15 to 25, wherein, The wireless device comprises a user equipment (UE).

27. The method of any one of claims 15-26, wherein, The first network node comprises a base station, a base station control unit (CU), a base station distributed unit (DU), an eNB, an eNB-CU, an eNB-DU, a gNB, a gNB-CU or a gNB-DU.

28. The method of any one of claims 15-27, wherein, The first network node is associated with a special cell (SpCell) of the first cell group.

29. A computer-readable storage medium having stored a computer program comprising instructions, which when executed on at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 28.

30. A computer program product storing a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1 to 28.

31. An apparatus in a wireless device configured with multi-radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor to enable the apparatus to operate to: receive, from a first network node, at least one message in a reconfiguration procedure for the second cell group; the at least one message indicating a mode of operation for the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group, wherein the at least one message further comprises an indication of whether to perform the reconfiguration procedure immediately or in response to receiving a command from the first network node to activate, re-activate, or resume the second cell group. The memory contains instructions executable by the processor to enable the apparatus to operate to perform the method according to any one of claims 2 to 14. wherein, 33. An apparatus in a first network node for configuring a wireless device configured with multi-radio access technology dual connectivity (MR-DC) for a first cell group and a second cell group, the apparatus comprising a processor and a memory, the memory containing instructions executable by the processor to enable the apparatus to operate to: send, to the wireless device, at least one message in a reconfiguration procedure for the second cell group; the at least one message indicating a mode of operation for the wireless device for the second cell group after the wireless device has applied the reconfiguration procedure for the second cell group, wherein the at least one message further comprises an indication of whether to perform the reconfiguration procedure immediately or in response to receiving a command from the first network node to activate, re-activate, or resume the second cell group. The memory contains instructions executable by the processor to enable the apparatus to operate to perform the method according to any one of claims 16 to 28.

32. The apparatus of claim 31, wherein, ​ ​ ​ wherein ​ ​ 34. The apparatus of claim 33, wherein, ​

Images