ACTIVATION OF A DEACTIVATED GROUP OF CELLS IN A WIRELESS

COMMUNICATION NETWORK

TECHNICAL FIELD

The present application relates generally to a wireless communication network and relates more particularly to activation of a deactivated group of cells in such a network.

BACKGROUND

Multi-connectivity in a wireless communication network serves a wireless device from multiple groups of cells provided by multiple respective radio network nodes. When one of the groups of cells is not needed for data transfer to or from the wireless device, that group of cells may be deactivated with respect to the wireless device. Deactivation may mean that the wireless device need not perform one or more activities with respect to that group, e.g., monitor control and/or data channels for the group. This may advantageously conserve power at the wireless device. However, the possibility to deactivate a group of serving cells of the wireless device introduces challenges to if or how the wireless device is to reactivate the group of serving cells at some point.

SUMMARY

Some embodiments herein notably inform a wireless device about whether or not the wireless device a shall perform a random access procedure towards a group of serving cells that is or is to be in a deactivated state. Some embodiments may thereby advantageously give the network flexibility and control over whether the wireless device performs the random access procedure towards a group of serving cells that is or is to be in the deactivated state. Other embodiments herein alternatively or additionally transmit an activation configuration to the wireless device that indicates one or more parameters governing how the wireless device is to perform an activation procedure for activating the group of serving cells. For example, the activation configuration may be proactively sent to the wireless device, for use if and when the group is later activated.

More particularly, embodiments herein include a method performed by a wireless device. The method comprises receiving an activation configuration that indicates one or more parameters governing how the wireless device is to perform an activation procedure for activating a group of serving cells. In this case, the group of serving cells is a secondary cell group of the wireless device for multi-connectivity operation. In some embodiments, the one or more parameters include a parameter governing whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of the activation procedure for activating the group of serving cells.

In some embodiments, the one or more parameters include one or more parameters governing a random access procedure that the wireless device shall perform towards the group of serving cells as part of the activation procedure for activating the group of serving cells. In one or more of these embodiments, the one or more parameters governing the random access procedure include a dedicated random access channel configuration to be used for the random access procedure.

In some embodiments, the one or more parameters include a parameter indicating resources to be used to access a serving cell of the group without performing a random access procedure towards that serving cell.

In some embodiments, the one or more parameters include a value of a timer that is to supervise the activation procedure for activating the group of serving cells.

In some embodiments, the activation configuration is received in a message that indicates the group of serving cells is to be deactivated.

In some embodiments, the activation configuration is received while the group of serving cells is deactivated. Additionally or alternatively, the activation configuration is received in a message that indicates the group of serving cells is to be activated.

In some embodiments, the method further comprises receiving signaling indicating a duration for which at least a portion of the activation configuration is valid.

In some embodiments, the activation configuration is received before triggering of the activation procedure. In this case, the method further comprises storing the activation configuration, and upon triggering of the activation procedure, performing the activation procedure according to the stored activation configuration.

In some embodiments, the method further comprises performing the activation procedure according to the activation configuration.

Other embodiments herein include a method performed by a radio network node. The method comprises transmitting, to a wireless device, an activation configuration that indicates one or more parameters governing how the wireless device is to perform an activation procedure for activating a group of serving cells. In this case, the group of serving cells is a secondary cell group of the wireless device for multi-connectivity operation. In some embodiments, the one or more parameters include a parameter governing whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of the activation procedure for activating the group of serving cells.

In some embodiments, the one or more parameters include one or more parameters governing a random access procedure that the wireless device shall perform towards the group of serving cells as part of the activation procedure for activating the group of serving cells.

In some embodiments, the one or more parameters governing the random access procedure include a dedicated random access channel configuration to be used for the random access procedure.

In some embodiments, the one or more parameters include a parameter indicating resources to be used to access a serving cell of the group without performing a random access procedure towards that serving cell.

In some embodiments, the one or more parameters include a value of a timer that is to supervise the activation procedure for activating the group of serving cells.

In some embodiments, the activation configuration is transmitted in a message that indicates the group of serving cells is to be deactivated.

In some embodiments, the activation configuration is transmitted while the group of serving cells is deactivated. Additionally or alternatively, the activation configuration is transmitted in a message that indicates the group of serving cells is to be activated.

In some embodiments, the method further comprises transmitting signaling indicating a duration for which at least a portion of the activation configuration is valid.

Other embodiments herein include apparatuses (wireless devices and radio network nodes), computer programs and computer-readable storage mediums corresponding to the above methods are also provided.

Of course, the present invention is not limited to the above features and advantages. Indeed, those skilled in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a block diagram of a wireless communication network according to some embodiments. Figure 2A is a logic flow diagram of a method performed by a wireless device according to some embodiments.

Figure 2B is a logic flow diagram of a method performed by a radio network node according to some embodiments.

Figure 3A is a logic flow diagram of a method performed by a wireless device according to other embodiments.

Figure 3B is a logic flow diagram of a method performed by a radio network node according to other embodiments.

Figure 4 is a block diagram of a wireless device according to some embodiments.

Figure 5 is a block diagram of a radio network node according to some embodiments.

Figures 6A-6B are block diagrams of different options for the architecture of interworking between a 5G network and an LTE network according to some embodiments.

Figure 7 is a block diagram of a control plane architecture for LTE DC and EN- DC according to some embodiments.

Figure 8 is a block diagram of dormancy-like behavior for SCells, realized using the concept of dormant bandwidth parts, according to some embodiments.

Figures 9(a)-9(d) are call flow diagrams of random access procedures according to some embodiments.

Figure 10 is a logic flow diagram of a method performed by a UE according to some embodiments.

Figure 11 is a block diagram of a wireless communication network according to some embodiments.

Figure 12 is a block diagram of a user equipment according to some embodiments.

Figure 13 is a block diagram of a virtualization environment according to some embodiments.

Figure 14 is a block diagram of a communication network with a host computer according to some embodiments.

Figure 15 is a block diagram of a host computer according to some embodiments.

Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

Figure 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.

DETAILED DESCRIPTION

Figure 1 shows a wireless communication network 10 according to some embodiments. The wireless communication network 10 serves a wireless device 12. The wireless communication network 10 in this regard serves the wireless device 12 via a group 20 of serving cells 20-1 ...20-N, where N in some embodiments is configurable to be greater than one.

Figure 1 shows that a radio network node 22 provides this group 20 of serving cells 20-1 ...20-N. In fact, in some embodiments, the group 20 of serving cells 20-1 ...20- N is a group in the sense that the serving cells 20-1 ...20-N in the group 20 are provided by the same radio network node 22. For example, in one or more carrier aggregation embodiments, the different serving cells 20-1 ...20-N in the group 20 correspond to different component carriers on which the radio network node 22 serves the wireless device 12, e.g., whereby the component carriers may be deployed on different frequency bands. In these and other embodiments, one of the serving cells 20-1 ...20-N may be deemed the primary serving cell and one or more others of the serving cells 20- 1 ...20-N may be deemed one or more secondary serving cells.

Alternatively or additionally, the group 20 of serving cells 20-1 ...20-N may be one of multiple groups of serving cells of the wireless device 12 in multi-connectivity (e.g., dual connectivity) operation. Multi-connectivity refers to the simultaneous connection of the wireless device 12 (e.g., at a radio resource control, RRC, layer) to multiple different radio network nodes, or to multiple different groups of cells provided by different radio network nodes. The multiple different radio network nodes or cells may use the same radio access technology (e.g., both may use Evolved Universal Terrestrial Radio Access (E-UTRA) or both may use New Radio (NR)). Or, the multiple different radio network nodes or cells may use different radio access technologies, e.g., one may use E-UTRA and another may use NR.

One example of multi-connectivity is dual connectivity (DC) in which the wireless device 12 is simultaneously connected to two different radio network nodes, or to two different groups of cells provided by two different radio network nodes. In this case, the wireless device 12 may be configured with a so-called master cell group (MCG) and a secondary cell group (SCG), where the MCG includes one or more cells provided by the radio network node acting as a master node (MN) and the SCG includes one or more cells served by the radio network node acting as a secondary node (SN). The master node may be a master in the sense that it controls the secondary node and/or provides the control plane connection to the core network. For example, E-UTRA-NR (EN) DC refers to where the master node uses E-LITRA and the secondary node uses NR, whereas NR-E-UTRA (NE) refers to where the master node uses NR and the secondary node uses E-LITRA.

For example, in multi-connectivity operation, the wireless device 12 with multiple receivers (Rx) and/or transmitters (Tx) may utilize radio resources amongst one or more radio access technologies (e.g., New Radio, NR, and/or E-LITRA) provided by multiple distinct schedulers connected via a non-ideal backhaul. Multi-radio dual connectivity (MR-DC) in this regard is a generalization of Intra-E-UTRA DC, where a multiple Rx/Tx wireless device may be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul, one providing NR access and the other one providing either E-LITRA or NR access. One node acts as the master node (MN) and the other as a SN. E-UTRAN for instance supports MR-DC via E-UTRA-NR dual connectivity (EN-DC), in which a wireless device is connected to one eNB that acts as a MN and one en-gNB that acts as a secondary node (SN). Either way, in MR-DC, the wireless device 12 may have a single Radio Resource Control (RRC) state, based on the MN RRC and a single control plane connection towards the core network.

In any event, Figure 1 shows one example of multi-connectivity operation whereby the wireless communication network 10 serves the wireless device 12 also via another group 30 of serving cells 30-1 ...30-M, where M in some embodiments is configurable to be greater than one. This other group 30 of serving cells 30-1 ...30-M as shown is provided by another radio network node 32. In these and other embodiments, the different serving cells 30-1 ...30-N in the other group 30 may similarly correspond to different component carriers on which the radio network node 32 serves the wireless device 12, e.g., whereby the component carriers may be deployed on different frequency bands. Regardless, in some embodiments, one of the groups 20, 30 of serving cells for the wireless device 12 may be deemed the master cell group (MCG) and another one of the groups 20, 30 of serving cells for the wireless device 12 may be deemed a secondary cell group (SCG). For example, in one embodiment, group 20 is the SCG and group 30 is the MCG, in which case radio network node 32 is referred to as the master node (MN) and radio network node 22 is referred to as the secondary node (SN). In another example, by contrast, group 20 is the MCG and group 20 is the SCG, in which case radio network node 22 is the MN and radio network node 32 is the SN.

No matter the particular deployment, the wireless device 12 under some circumstances performs a random access (RA) procedure 18 towards the group 20 of serving cells 20-1 ...20-N, e.g., more particularly, towards the primary cell of the group 20. Generally, for instance, the wireless device 12 may perform the RA procedure 18 towards the group 20 of serving cells 20-1 ...20-N when the group 20 is initially setup or established. The random access procedure 18 in this regard may involve the wireless device 12 transmitting a random access preamble to the radio network node 22 and receiving an uplink timing advance in a random access response. The random access procedure 18 may for instance be a 4-step procedure or a 2-step procedure as described more fully later.

In some embodiments, though, the group 20 of serving cells 20-1 ...20-N is able to be deactivated, e.g., when there is currently no specific data traffic requiring the group 20 of serving cells 20-1 ...20-N to be active. When deactivated, the group 20 is said to be in a deactivated state, as contrasted with an activated state in which the group 20 is activated. Deactivation or activation of the group 20 in one embodiment means that the group 20 is deactivated or activated with respect to the wireless device 12, e.g., deactivation or activation of the group 20 may represent a state of the group 20 at the wireless device 12 (and the radio network node 22).

In some embodiments, for example, when the group 20 is deactivated, the wireless device 12 is relieved of the obligation to perform one or more activities associated with the group 20. In these and other embodiments, deactivation of the group 20 may conserve power of the wireless device 12, e.g., since the wireless device 12 need not expend power performing the one or more activities when the group 20 is deactivated.

For example, when the group 20 is deactivated, the wireless device 12 in some embodiments is relieved of the obligation to monitor the downlink control channel (e.g., Physical Downlink Control Channel, PDCCH) and/or a downlink data channel (e.g., Physical Downlink Shared Channel, PDSCH) associated with the group 20. In this case, then, the wireless device 12 may be configured to monitor the downlink control channel and/or the downlink data channel when the group 20 is in the activated state, but to refrain from monitoring the downlink control channel and/or the downlink data channel associated with the group 20 when the group 20 is in the deactivated state.

In some embodiments, the activated or deactivated state of the group 20 also impacts the obligation of the wireless device 12 to perform and report channel state measurements for the group 20. In these embodiments, the wireless device 12 performs and reports channel state measurements when the group 20 is in the activated state, but refrains from performing and reporting channel state measurements when the group 20 is in the deactivated state. In other embodiments, by contrast, the activated or deactivated state of the group 20 nonetheless does not impact the obligation of the wireless device 12 to perform and report channel state measurements for the group 20 (or at least the primary cell of the group 20). In these embodiments, then, the wireless device 12 performs and reports channel state measurements no matter whether the group 20 is in the activated state or the deactivated state. In still other embodiments, the above alternatives may be combinable to represent different possible levels of deactivation, e.g., one more significant level of deactivation in which the wireless device 12 does not monitor certain channels for the group 20 and does not report channel state measurements, and one lesser level of deactivation in which the wireless device 12 does not monitor certain channel(s) for the group 20 but still reports channel state measurements. In this case, some embodiments herein refer to the more significant level of deactivation as (full) deactivation and refer to the lesser level of deactivation as dormancy.

As these examples demonstrate, then, deactivation of the group 20 in some embodiments generally means that the wireless device 12 refrains from performing one or more activities with respect to the group 20 that the wireless device 12 would have performed had the group 20 been in the activated state. Accordingly, as used herein, deactivation of the group 20 may represent any degree or level of deactivation in the deactivated state. And, when in the deactivated state, the group 20 may be broadly described as deactivated, inactive, dormant, suspended, or in a power-saving mode, as a few examples of alternative terminology. Similarly, when in the activated state, the group 20 may be broadly described as activated, active, resumed, in a normal or legacy mode, or in a non-power-saving mode. In this context, the group 20 of serving cells 20-1 ...20-N may be deactivated for the wireless device 12 for some time, after which the group 20 of serving cells 20- 1 ...20-N is re-activated, e.g., when the group 20 of serving cells 20-1 ...20-N again becomes needed for data traffic. Depending on for how long the group 20 of serving cells 20-1 ...20-N was deactivated, the wireless device 12 may or may not have lost its uplink time alignment with the group 20 (or at least the primary cell of the group 20) by the time the group 20 is re-activated. In these and other cases, then, the wireless device 12 may or may not need to perform the random access procedure 18 (again) towards the group 20 (e.g., towards the primary cell of the group 20), so as to reacquire uplink time alignment.

Note, too, that the group 20 of serving cells 20-1 ...20-N in some embodiments may even be setup or established in the deactivated state, i.e. , the deactivated state is to be the initial state of the group 20 upon the group 20 being set up or established. Here, setup or establishment of the group 20 may encompass setup or establishment of the primary cell of the group 20. So, for example, in some embodiments, the primary cell of the group 20 may be added, changed, or otherwise established with the group 20 of serving cells 20-1 ...20-N in a deactivated state; that is, the group 20 is to be in the deactivated state immediately upon addition or change of the primary cell of the group 20. In this case, the group 20 may be proactively established in case it is later needed, at which point the group 20 can be efficiently activated. When the group 20 is later activated, the wireless device 12 will need valid uplink timing alignment. If the wireless device 12 were to acquire uplink timing alignment by performing the random access procedure 18 already upon setup or establishment of the group 20, even though the group 20 is to be deactivated immediately upon establishment, the wireless device 12 may not need to perform the random access procedure 18 again when the group 20 is later activated if the uplink timing alignment obtained at setup or establishment is still valid. This would advantageously expedite activation of the group 20 and reduce latency. On the other hand, performing the random access procedure 18 at setup or establishment could prove inefficient and wasteful if the uplink timing alignment becomes stale by the time the group 20 is later activated.

Similarly, in some embodiments, a radio resource control (RRC) connection can be suspended and then resumed at the group 20 (e.g., at the primary cell of the group 20), with the group 20 in the deactivated state; that is, the group 20 is to be in the deactivated state immediately upon resumption of the RRC connection at group 20. If the wireless device 12 were to acquire uplink timing alignment by performing the random access procedure 18 already upon resumption of the RRC connection, even though the group 20 is to be deactivated immediately upon resumption, the wireless device 12 may not need to perform the random access procedure 18 again when the group 20 is later activated if the uplink timing alignment obtained at RRC connection resumption is still valid. This would advantageously expedite activation of the group 20 and reduce latency. On the other hand, performing the random access procedure 18 at RRC connection resume could prove inefficient and wasteful if the uplink timing alignment becomes stale by the time the group 20 is later activated.

In this context where the group 20 of serving cells 20-1 ...20-N is or is to be in the deactivated state, some embodiments herein notably inform the wireless device 12 about whether or not the wireless device 12 shall perform the random access procedure 18. Figure 1 in this regard shows that the wireless communication network 10 (e.g., radio network node 22 or 32) in some embodiments transmits a message 14 to the wireless device 12, e.g., an RRC message. The message 14 indicates whether or not the wireless device 12 shall perform the random access procedure 18 towards the group 20 of serving cells 20-1 ...20-N (that is, or is to be, in the deactivated state). The message 14 may for example include a random access procedure indication 16 for indicating this. The message 14 may thereby advantageously give the network 10 flexibility and control over whether the wireless device 12 performs the random access procedure 18 towards a group 20 of serving cells 20-1 ...20-N that is or is to be in the deactivated state.

In one embodiment, for example, the group 20 of serving cells 20-1 ...20-N is to be in the deactivated state as part of, or as a result of, a procedure for setting up the group 20 with the group 20 already in the deactivated state upon setup. This procedure for setting up the group 20 may for instance be a procedure for adding or changing a primary cell of the group 20, e.g., a PSCell addition or change procedure where the group 20 is an SCG or a PCell addition or change procedure where the group is an MCG. Regardless, the message 14 in this embodiment indicates whether or not the wireless device 12 shall perform the random access procedure 18 towards the group 20 of serving cells 20-1 ...20-N as part of, or as a result of, the procedure for setting up the group 20 of serving cells 20-1 ...20-N with the group 20 already in the deactivated state upon setup. The message 14 may for instance be a message that configures this procedure. Where the procedure is a PSCell addition or change procedure, for example, the message 14 indicates whether or not the wireless device 12 shall perform the random access procedure 18 towards the group 20 as part of a PSCell addition or change procedure. The message 14 may thereby advantageously give the network 10 flexibility and control over whether the wireless device 12 performs the random access procedure 18 towards the group 20 when the group 20 is to set up already in the deactivated state. The network 10 may for example dynamically control whether to have the wireless device 12 perform the random access procedure 18 at setup of the group 20 (e.g., to potentially expedite activation later) or to wait to have the wireless device 12 perform the random access procedure 18 only upon activation later (e.g., to avoid potentially wasting resources used for the random access procedure 18 if the group 20 is not likely to be activated until acquired uplink timing alignment would have become stale).

As another example, the group 20 of serving cells 20-1 ...20-N in some embodiments is to be in the deactivated state as part of, or as a result of, a procedure for resuming a radio resource control connection in a primary cell of the group 20, with the group 20 already in the deactivated state upon resumption of the radio resource control connection. The message 14 in this embodiment indicates whether or not the wireless device 12 shall perform the random access procedure 18 towards the group 20 of serving cells 20-1 ...20-N as part of, or as a result of, the procedure for resuming the radio resource control connection in a primary cell of the group 20. The message 14 may for instance be a message that configures this procedure, e.g., an RRC connection resume message. The message 14 may thereby advantageously give the network 10 flexibility and control over whether the wireless device 12 performs the random access procedure 18 towards the group 20 when the RRC connection is to be resumed at the group’s primary cell even though the group 20 is be in the deactivated state immediately upon resumption. The network 10 may for example dynamically control whether to have the wireless device 12 perform the random access procedure 18 at RRC connection resumption (e.g., to potentially expedite activation later) or to wait to have the wireless device 12 perform the random access procedure 18 only upon activation later (e.g., to avoid potentially wasting resources used for the random access procedure 18 if the group 20 is not likely to be activated until acquired uplink timing alignment would have become stale).

In yet another example, the group 20 of serving cells 20-1 ...20-N in other embodiments is in the deactivated state when the message 14 is transmitted to the wireless device 12. That is, the group 20 has already been established before the message 14 is sent, and the message 14 is sent while the group 20 is in the deactivated state. In this case, the message 14 may indicate whether or not the wireless device 12 shall perform the random access procedure 18 towards the group 20 of serving cells 20-1 ...20-N that is in the deactivated state. In one such case, the message 14 may indicate whether or not the wireless device 12 shall perform the random access procedure 18 as part of, or as a result of, a procedure started while the group 20 of serving cells 20-1 ...20-N is in the deactivated state. Where the group 20 is an SCG of the wireless device 12 in multi-connectivity operation, for example, the procedure may be a procedure for changing an MCG of the wireless device 12 and/or a procedure that results in a change in a security key used towards the SCG.

In still another example, the message 14 indicates whether or not the wireless device 12 shall perform the random access procedure 18 towards the group 20 of serving cells 20-1 ...20-N as part of, or as a result of, a procedure for activating the group 20 out of the deactivated state. The message 14 in this case may for instance be received while the group 20 is in the deactivated state, or even before the group 20 has been established, so as to operate as advanced instructions on whether or not the random access procedure 18 shall be performed later on when the group 20 is eventually activated (if at all).

In any event, in some embodiments, the random access procedure indication 16 is an explicit indication (e.g., a Boolean flag) that is mandatory to include in the message 14. The random access procedure indication 16 in this case has two different possible values, one value (e.g., true) indicating that the wireless device 12 shall perform the random access procedure 18 towards the group 20 and another value (e.g., false) indicating that the wireless device 12 shall not perform the random access procedure 18 towards the group 20.

In another embodiment, by contrast, the message 14 is merely configurable to include the random access procedure indication 16, as an option. That is, the random access procedure indication 16 is optional to include in the message 14. The random access procedure indication 16, if included, indicates that the wireless device 12 shall perform the random access procedure 18 towards the group 20. If the random access procedure indication 16 is absent from the message 14, such implicitly indicates that the wireless device 12 shall not perform the random access procedure 18 towards the group 20. Inclusion or exclusion of the random access procedure indication 16 in the message 14 thereby indicates whether or not the wireless device 12 shall perform the random access procedure 18 towards the group 20 of serving cells.

In some embodiments, for example, the message 14 indicates whether or not the wireless device 12 shall perform the random access procedure 18 towards the group 20 of serving cells, by indicating whether or not the wireless device 12 shall skip the random access procedure 18 for a target primary cell of the group 20 of serving cells. In one such embodiment, the message 14 is configurable to include an explicit indication indicating that the wireless device 12 shall skip the random access procedure 18 for a target primary cell of the group 20 of serving cells, and inclusion or exclusion of the explicit indication in the message 14 indicates whether or not the wireless device 12 shall skip the random access procedure 18 for a target primary cell of the group 20 of serving cells.

In view of the above modifications and variations, Figure 2A depicts a method performed by the wireless device 12 in accordance with some embodiments. The method includes receiving a message 14 that indicates whether or not the wireless device 12 shall perform a random access procedure 18 towards a group 20 of serving cells 20-1 ...20-N that is, or is to be, in a deactivated state (Block 200).

In some embodiments, the method further comprises deciding whether or not to perform the random access procedure 18 towards the group 20 of serving cells 20- 1 ...20-N based on the received message 14 (Block 210). The method may then comprise performing, or refraining from performing, the random access procedure 18 towards the group 20 of serving cells 20-1 ...20-N based on that decision (Block 220). For example, the method may comprise performing the random access procedure 18 towards the group 20 of serving cells 20-1 ...20-N if the message 14 indicates that the wireless device 12 shall perform the random access procedure 12 towards the group 20 of serving cells. Or, comprise refraining from performing the random access procedure 18 towards the group 20 of serving cells 20-1 ...20-N if the message 14 indicates that the wireless device 12 shall not perform the random access procedure 12 towards the group 20 of serving cells.

Figure 2B depicts a corresponding method performed by a radio network node 22 or 32 in accordance with other particular embodiments. The method includes transmitting, to a wireless device 12, a message 14 that indicates whether or not the wireless device 12 shall perform a random access procedure 18 towards a group 20 of serving cells 20-1 ...20-N that is, or is to be, in a deactivated state (Block 250). In some embodiments, the method further comprises generating the message 14 (Block 255).

Referring back to Figure 1 , the wireless communication network 10 according to some embodiments herein alternatively or additionally transmits an activation configuration 24 to the wireless device 12, e.g., within the same message 14 or a different message than the random access procedure indication 16. This activation configuration 24 indicates one or more parameters governing how the wireless device 12 is to perform an activation procedure for activating the group 20 of serving cells 20- 1...20-N.

In some embodiments, the activation configuration 24 is transmitted to the wireless device 12 in a message that indicates the group 20 is to be deactivated. In other embodiments, the activation configuration 24 is transmitted to the wireless device 12 in a message that indicates the group 20 of serving cells is to be established with the group 20 deactivated, or in a message that indicates a primary cell of the group 20 is to be changed with the group 20 deactivated. The activation configuration 24 in these and other cases may thereby be proactively sent to the wireless device 12, for use if and when the group 20 is later activated. In these and other embodiments, therefore, the wireless device 12 may store the activation configuration 24. Then, at some point later, upon triggering of the activation procedure, the wireless device 12 may perform the activation procedure according to the stored activation configuration 24.

Regardless, in some embodiments the one or more parameters of the activation configuration 24 include a parameter governing whether or not the wireless device 12 shall perform the random access procedure 18 towards the group 20 as part of the activation procedure for activating the group 20.

Alternatively or additionally, the one or more parameters include one or more parameters governing a random access procedure 18 that the wireless device 12 shall perform towards the group 20 as part of the activation procedure for activating the group 20. In this case, the one or more parameters governing the random access procedure 18 may include a parameter governing a type of the random access procedure that the wireless device shall perform, e.g., a parameter governing whether the random access procedure 18 that the wireless device 12 shall perform is to be a content-based random access (CBRA) procedure or a contention-free random access (CFRA) procedure. Alternatively or additionally, the one or more parameters governing the random access procedure 18 may include a dedicated random access channel configuration to be used for the random access procedure 18. In other embodiments, the one or more parameters may include a parameter indicating resources to be used to access a serving cell of the group 20 without performing a random access procedure towards that serving cell. For example, the indicated resources may include one or more uplink grants for transmission on an uplink data channel towards the serving cell and/or include a configuration for monitoring a downlink control channel of the serving cell.

In still other embodiments, the one or more parameters may include cell-specific parameters for a primary cell of the group 20.

In yet other embodiments, the one or more parameters include a value of a timer that is to supervise the activation procedure for activating the group 20 of serving cells. The value of the timer may for example indicate or represent a maximum allowed duration of the activation procedure.

In view of the modifications and variations of these embodiments, Figure 3A illustrates a method performed by the wireless device 12. The method as shown comprises receiving an activation configuration 24 that indicates one or more parameters governing how the wireless device 12 is to perform an activation procedure for activating a group 20 of serving cells 20-1 ...20-N (Block 300). The method in some embodiments may further comprise performing the activation procedure according to the activation configuration 24 (Block 330).

In some embodiments, the method alternatively or additionally comprises receiving signaling indicating a duration for which at least a portion of the activation configuration 24 is valid (Block 310). The method alternatively or additionally may comprise receiving signaling indicating a maximum allowed duration of the activation procedure (Block 320).

The method in Figures 3A and 3B may be implemented separately from or in combination with the methods in Figures 2A and 2B.

Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a wireless device 12 configured to perform any of the steps of any of the embodiments described above for the wireless device 12.

Embodiments also include a wireless device 12 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the wireless device 12. The power supply circuitry is configured to supply power to the wireless device 12.

Embodiments further include a wireless device 12 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the wireless device 12. In some embodiments, the wireless device 12 further comprises communication circuitry.

Embodiments further include a wireless device 12 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the wireless device 12 is configured to perform any of the steps of any of the embodiments described above for the wireless device 12.

Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the wireless device 12. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

Embodiments herein also include a radio network node 22, 32 configured to perform any of the steps of any of the embodiments described above for the radio network node 22, 32.

Embodiments also include a radio network node 22, 32 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the radio network node 22, 32. The power supply circuitry is configured to supply power to the radio network node 22, 32.

Embodiments further include a radio network node 22, 32 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the radio network node 22, 32. In some embodiments, the radio network node 22, 32 further comprises communication circuitry.

Embodiments further include a radio network node 22, 32 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the radio network node 22, 32 is configured to perform any of the steps of any of the embodiments described above for the radio network node 22, 32.

More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

Figure 4 for example illustrates a wireless device 12 as implemented in accordance with one or more embodiments. As shown, the wireless device 12 includes processing circuitry 410 and communication circuitry 420. The communication circuitry 420 (e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the wireless device 400. The processing circuitry 410 is configured to perform processing described above, e.g., in Figure 2A and/or 3A, such as by executing instructions stored in memory 430. The processing circuitry 410 in this regard may implement certain functional means, units, or modules.

Figure 5 illustrates a radio network node 22 or 32 as implemented in accordance with one or more embodiments. As shown, the radio network node 22 or 32 includes processing circuitry 510 and communication circuitry 520. The communication circuitry 520 is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The processing circuitry 510 is configured to perform processing described above, e.g., in Figure 2B and/or 3B, such as by executing instructions stored in memory 530. The processing circuitry 510 in this regard may implement certain functional means, units, or modules.

Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

Additional embodiments will now be described. At least some of these embodiments may be described as applicable in certain contexts and/or wireless network types for illustrative purposes, but the embodiments are similarly applicable in other contexts and/or wireless network types not explicitly described. In some of the embodiments exemplified below, the wireless device 12 is exemplified as a user equipment (UE), a radio network node 22 or 32 is exemplified as a gNodeB or eNodeB, and the group 20 of serving cells 20-1 ...20-N is exemplified as an SCG in multiconnectivity operation.

Some embodiments herein are applicable in the context of carrier aggregation (CA). When CA is configured, the UE only has one RRC connection with the network. Further, at RRC connection establishment/re-establishment/handover, one serving cell provides the non-access stratum (NAS) mobility information, and at RRC connection re- establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). In addition, depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. Further, when dual connectivity is configured, it could be the case that one carrier under the SCG is used as the Primary SCell (PSCell). Hence, in this case there is one PCell and one or more SCell(s) over the MCG and one PSCell and one or more SCell(s) over the SCG.

The reconfiguration, addition, and removal of SCells can be performed by RRC. At intra-RAT (radio access technology) handover, RRC can also add, remove, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signalling is used for sending all required system information of the SCell, i.e., while in connected mode, UEs need not acquire broadcasted system information directly from the SCells.

3GPP Dual Connectivity

In 3GPP, the dual-connectivity (DC) solution has been specified, both for LTE and between LTE and NR. In DC two nodes are involved, a master node (MN or MeNB) and a Secondary Node (SN, or SeNB). Multi-connectivity (MC) is the case when there are more than 2 nodes involved. Also, it has been proposed in 3GPP that DC is used in the Ultra Reliable Low Latency Communications (URLLC) cases in order to enhance the robustness and to avoid connection interruptions.

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

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

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

• NE-DC (Option 4): In NR-E-UTRA dual connection (NE-DC), NR is the master node and LTE is the secondary (5GCN employed)

• NGEN-DC (Option 7): In NG-RAN E-UTRA-NR dual connectivity (NGEN-DC), LTE is the master node and NR is the secondary (5GCN employed)

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

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

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

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

1 . Centralized solution (like LTE-DC),

2. Decentralized solution (like EN-DC).

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

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

SCG power saving mode

In order to improve network energy efficiency and UE battery life for UEs in MR- DC, SCG/SCell may be activated and deactivated. This can be especially important for MR-DC configurations with NR SCG, as in some cases NR UE power consumption is 3 to 4 times higher than LTE.

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

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

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

In some embodiments, the UE starts to operate the PSCell in dormancy, e.g., switching the PSCell to a dormant BWP. On the network side, the network considers the PSCell in dormancy and at least stops transmitting PDCCH for that UE in the PSCell(s). In some embodiments, the UE deactivates the PSCell like SCell deactivation; On the network side, the network considers the PSCell as deactivated and at least stops transmitting PDCCH for that UE in the PSCell.

In some embodiments, the UE operates the PSCell in long discontinuous reception (DRX). SCG DRX can be switched off from the MN (e.g., via MCG MAC CE or DCI) when the need arises (e.g., downlink (DL) data arrival for SN terminated SCG bearers).

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

In some embodiments, when the SCG is deactivated, the UE does not monitor PDCCH on the PSCell. As a baseline, MN-configured radio resource management (RRM) measurement/reporting procedures do not depend on the SCG activation state (deactivated or activated). While the SCG is deactivated, PSCell mobility is supported. MN- and SN-configured measurements are supported for deactivated SCG. SCG RRC reconfiguration can select the SCG activation state (activated/deactivated) at PSCell addition/change, RRC resume or handover (HO). When the SCG is in the deactivated state, the UE sends MeasurementReport messages for measurement results of SN- configured measurements embedded in the E-UTRA (if the MCG is EUTRA) or in the NR (if the MCG is NR) ULInformationTransferMRDC message via signaling reader bearer #1 (SRB1 ). When the SCG is in deactivated state, the UE can receive an SCG RRCReconfiguration message embedded in an MCG RRC(Connection)Reconfiguration message on SRB1 , like when the SCG is activated, and then the UE processes the SCG RRCReconfiguration message according to Rel-15/16 procedures.

In some embodiments, while the SCG is deactivated, there can be SCG SCells in the deactivated state and there cannot be SCG SCells in the activated state.

Accordingly, it is thus possible in some embodiments to configure a PSCell with the “SCG activation state” set as deactivated, i.e. , with the SCG in a power saving mode, both at setup (PSCell addition), at SCG and MCG mobility procedures (PSCell change or HO) and at RRC resume including the SCG. Some embodiments herein concern whether or not the UE performs a random access procedure towards the PSCell in these cases and in case of an SCG reactivation.

The SCG is typically in a power saving mode (e.g., deactivated) when there is currently no specific data traffic requiring the SCG or the data volume is limited and the MCG therefore is sufficient. When the data traffic changes, the SCG may then however need to be activated again. The trigger to activate the SCG may be DL triggered, where the network, for example, detects that the amount of traffic increases to a level where it is considered required to perform transmissions also via the SCG or that there is data available for a Data Radio Bearer (DRB) that is mapped to the SCG. An option is then that, when the network determines that the SCG should be activated, it indicates this to the UE through an SCG activation message. This could then, for example, be an RRC message or a Medium Access Control (MAC) Control Element (CE). The activation of the SCG could then possibly either be triggered in the MN or in the SN.

The trigger to activate the SCG could however also be uplink (UL) triggered, i.e., that the UE detects or determines that the SCG should be activated again. This could then be based on for example that the UE has UL data available for a DRB that is mapped only to the SCG or that there is enough UL data available to trigger an SCG activation.

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

Reconfiguration with Sync

The RRC Reconfiguration procedure is performed to modify an RRC connection, e.g., to establish/modify/release radio bearers (RBs), to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to add/modify/release conditional handover configuration, or to add/modify/release conditional PSCell change configuration.

The reconfiguration with sync procedure is performed by the UE when the network includes the reconfigurationWithSync for the spCellConfig of the MCG or SCG, i.e. , the PCell or the PSCell, in the RRC Reconfiguration message. This can for example be seen in 5.3.5.5.1 in 3GPP TS 38.331 v16.3.0 where the reconfiguration with sync procedure in 5.3.5.5.2 is performed if CellGroupConfig contains the spCellConfig with reconfigurationWithSync. The SCG transmission is then also resumed for all radio bearers, if suspended.

In other cases, since the reconfiguration with sync procedure includes a MAC reset (except for the Dual Active Protocol Stack (DAPS) handover case where even a new MAC entity is created towards the target cell), the UE will need to perform a Random Access towards the (target) SpCell in order to transmit, for example, the RRC Reconfiguration Complete message. This is since the MAC reset procedure, as defined in section 5.12 of 3GPP TS 38.321 (v.16.2.1 ), includes that the timeAlignmentTimers then are considered as expired for the MAC entity and there is thus no UL time alignment for the corresponding cell(s). In section 5.2 of 3GPP TS 38.321 (v.16.2.1), it is then specified that the UE shall only perform transmissions of Random Access Preamble, i.e., the Msg1 for a 4-step random access, or MSGA, i.e., the first message of a 2-step random access, when the corresponding timeAlignmentTimer is not running. It is thus not possible to perform any other transmissions in the corresponding cell(s) until the UL time alignment has been achieved again.

The reconfiguration with sync is also needed to change the integrity protection and ciphering algorithms whereby the access stratum (AS) keys (KgNB, KRRCint, KRRCenc, KU Pint and KUPenc) change upon the reconfiguration with sync.

Random access procedure

Two types of random access (RA) procedure are supported: 4-step RA type with MSG1 and 2-step RA type with MSGA. Both types of RA procedure support contentionbased random access (CBRA) and contention-free random access (CFRA). Figure 9(a) shows 4-step CBRA, Figure 9(b) shows 2-step CBRA, Figure 9(c) shows 4-step CFRA, and Figure 9(d) shows 2-step CFRA. The RA procedures in Figures 9(a)-9(d) exemplify the RA procedure 18 in Figure 1 according to different embodiments.

The UE selects the type of random access at initiation of the random access procedure based on network configuration:

- when CFRA resources are not configured, a reference signal received power (RSRP) threshold is used by the UE to select between 2-step RA type and 4- step RA type;

- when CFRA resources for 4-step RA type are configured, UE performs random access with 4-step RA type;

- when CFRA resources for 2-step RA type are configured, UE performs random access with 2-step RA type.

As shown in Figures 9(a) and 9(c), in step 1 , MSG1 of the 4-step RA type consists of a preamble on the Physical Random Access Channel (PRACH). After MSG1 transmission, in step 2, the UE monitors for a response from the network within a configured window. For CFRA, a dedicated preamble for MSG1 transmission is assigned by the network and, upon receiving random access response from the network, the UE ends the random access procedure as shown in Figure 9Error! Reference source not found. (c). For CBRA, upon reception of the random access response in step 2, the UE in step 3 sends MSG3 using the UL grant scheduled in the response and monitors contention resolution as shown in Figure 9(a). If contention resolution is not successful after MSG3 (re)transmission(s), the UE goes back to MSG1 transmission.

As shown in Figures 9(b) and 9(d), MSGA of the 2-step RA type includes a preamble on PRACH and a payload on the Physical Uplink Shared Channel (PUSCH). After MSGA transmission in step 1 , the UE in step 2 monitors for a response from the network within a configured window. For CFRA, a dedicated preamble and PUSCH resource are configured for MSGA transmission and, upon receiving the network response, the UE ends the random access procedure as shown in Figure 9(d). For CBRA, if contention resolution is successful upon receiving the network response, the UE ends the random access procedure as shown in Figure 9(b).

If the random access procedure with 2-step RA type is not completed after a number of MSGA transmissions, the UE can be configured to switch to CBRA with 4- step RA type.

When carrier aggregation (CA) is configured, for random access procedure with 4-step RA type, the first three steps of CBRA always occur on the PCell while contention resolution (step 4) can be cross-scheduled by the PCell. The three steps of a CFRA started on the PCell remain on the PCell. CFRA on SCell can only be initiated by the gNB to establish timing advance for a secondary timing advance group (TAG): the procedure is initiated by the gNB with a Physical Downlink Control Channel (PDCCH) order (step 0) that is sent on a scheduling cell of an activated SCell of the secondary TAG, preamble transmission (step 1) takes place on the indicated SCell, and Random Access Response (step 2) takes place on PCell.

Some embodiments herein address the following challenges in a 3GPP context. In 3GPP Rel-17, it will be possible to let the SCG be deactivated either directly at setup of the PSCell (as part of the PSCell addition or PSCell change procedure) or later on for example through an SCG deactivation procedure due to low traffic. With regard to the procedure to (re)activate the SCG, it can be assumed that there is a need for a random access procedure towards the PSCell at least in some cases, e.g., if the Time Alignment Timer (TAT) has expired. For some cases, however, it is not heretofore clear whether the UE should perform a random access or not for the SCG activation and what configuration that the UE then should use for the SCG activation procedure.

There are several other procedures involving the SCG, which include a random access towards the SCG/PSCell when the SCG is activated (as in legacy). For example, one other procedure is a PSCell addition or PSCell change, i.e. , where the PSCell is added in a new target PSCell, where the SCG is deactivated. The PSCell/SCG is thus added in a deactivated mode. Another procedure is a key change for the SCG, e.g., due to an MCG change (HO), while the SCG is deactivated. Yet another procedure is an RRC Resume procedure where also the PSCell is resumed and where the SCG is deactivated after the RRC Resume. It is however not heretofore clear whether the UE should perform a random access as part of these procedures if the SCG is deactivated when the procedure is started (or if the SCG is setup as deactivated by the procedure). A solution is therefore needed for the UE to determine whether to then perform a random access or not as part of these procedures.

If a random access is to be performed towards the SCG/PSCell as part of the other procedure while the SCG is deactivated, it is also not heretofore clear how the UE should be provided a configuration for both this random access and for a possible random access that is performed at a later SCG activation. Heretofore, where the UE performs a random access towards the PSCell as part of the above procedures, the corresponding RRC Reconfiguration messages (e.g., RRCReconfigu ration) therefore includes a reconfig urationWith Sync for the PSCell. This then triggers the UE to perform a random access to the PSCell when it applies the message. The reconfigurationWithSync provides the UE with, among others, required system information for the PSCell to the UE (including cell specific random access parameters that are used both for CBRA and CFRA), the timer value for supervision of the procedure (T304), and optionally a dedicated RACH configuration. This configuration in reconfigurationWithSync is then applicable for the corresponding procedure as such (e.g., for the PSCell addition/change) but not for a possible SCG activation that may take place at a later point in time. In case the UE should perform a random access both at the other procedure (e.g., PSCell addition/change) and then later at SCG activation, there may therefore be a need to provide the UE with separate configurations for the two procedures, e.g., separate RACH configurations for CBRA or CFRA for the two random access procedures, respectively.

On the other hand, in case the UE should not perform a random access procedure at the other procedure (e.g., the PSCell addition/change) when the SCG is established as deactivated in the target PSCell, it would not work if the UE is provided with the reconfigurationWithSync configuration since that has heretofore triggered a MAC reset and a random access. It is then heretofore not clear how to configure the UE to perform for example a PSCell addition/change without performing random access, while still providing the UE with, for example, the Cell Radio Network Temporary Identifier (C-RNTI) and the required system information for the PSCell.

The SCG activation procedure should be as quick as possible in order to enable a use of the SCG power saving mode without too much impact on the performance. Therefore, in case the UE needs to perform a random access in the PSCell for activation of the (deactivated) SCG, this should then preferably be performed using a Contention Free Random Access (CFRA) procedure. This is since the activation then would be quicker than if a Contention Based Random Access (CBRA) procedure is used, since the latter requires additional signaling in order to complete the random access procedure. In order to perform a CFRA, the UE however needs to be configured with a corresponding dedicated RACH configuration, e.g., dedicated PRACH preambles. The dedicated RACH configurations, for example, dedicated PRACH preambles, are however a restricted resource and they should therefore preferably not be reserved for a longer time. In cases where the UE is to be provided with an SCG activation configuration in advance, i.e., not specifically as part of the SCG activation itself, the corresponding dedicated RACH configuration (e.g., dedicated PRACH preambles) would need to be reserved until the SCG activation (or release). This would for example be the case if the SCG activation could be UL triggered and where the UE then performs a random access procedure directly towards the SCG/PSCell. Since the SCG could potentially be deactivated for quite a long time, the corresponding resources may then need to be reserved for a long time, with the risk that one runs out of those resources in the corresponding cell.

When the SCG is to be activated, there is a risk that the procedure fails, for example due to that the radio contact towards the PSCell is not sufficiently good (e.g., that it has deteriorated since the SCG was deactivated) or that the signaling procedure towards the PSCell fails for some reason. To avoid that the UE continues the SCG activation for too long, there is a need to supervise that the procedure is successful.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Some embodiments include a method at the UE to determine whether to perform random access towards the SCG/PSCell, when the SCG is deactivated or to be setup as deactivated, as part of the following procedures, for example:

• PSCell change, i.e. , where the PSCell is added in a new target PSCell with the SCG in a power saving mode of operation (i.e., the SCG is deactivated) after the PSCell change procedure;

• PSCell addition where the PSCell is added with the SCG in a power saving mode of operation (i.e., the SCG is deactivated);

• A security key change for the PSCell/SCG when the SCG is in a power saving mode of operation, i.e., while the SCG is deactivated. This can for example be due to an MCG change procedure (HO);

• RRC Resume procedure where the SCG/PSCell is resumed and where the PSCell then is resumed in a power saving mode of operation (SCG is deactivated).

The method may include for example that:

• An explicit indication is included in the message (e.g., RRC Reconfiguration message) that configures the other procedure (e.g., PSCell addition, PSCell change, key change, handover, or RRC resume), e.g., within ReconfigurationWithSync, to indicate whether the UE should perform a random access procedure towards the SCG/PSCell as part of (or resulting from) the other procedure or not.

• The network does not include the ReconfigurationWithSync for the deactivated SCG in the message (e.g., RRC Reconfiguration message) that configures the other procedure (e.g., PSCell addition, PSCell change, key change, handover, or RRC resume) if no random access procedure is to be performed towards the SCG/PSCell as part of (or resulting from) that other procedure. If the ReconfigurationWithSync then is included in the message that configures the other procedure, the UE then performs random access towards the SCG/PSCell even if the SCG is deactivated.

• The UE (implicitly) does not perform any random access towards the SCG/PSCell as part of one or more of the other procedures (e.g., PSCell addition, PSCell change, key change, handover, or RRC resume) if the SCG is deactivated when the corresponding other procedure is triggered or as a result of the other procedure. If the SCG is activated at the trigger or as a result of the procedure, the UE then performs a random access procedure towards the SCG/PSCell.

Some embodiments alternatively or additionally include a method for providing the UE with a specific SCG activation configuration, i.e. , a configuration to be used for the SCG activation, including for example, an indication about whether to perform a random access procedure towards the SCG/PSCell at the SCG activation, and/or related configuration such as for example a dedicated RACH configuration for CFRA. Since the SCG activation may be triggered by the UE and performed directly towards the SCG/PSCell, for example based on UL data availability above a threshold, there may be a need to provide the configuration to the UE prior to the actual SCG activation. The method in some embodiments includes that the SCG activation configuration is provided to the UE in for example:

• a message that is used for the network to indicate to the UE that the SCG is to be activated, e.g., an RRC message, or a MAC CE (which then, as an option, may refer to a stored configuration);

• a message that configures the SCG to become deactivated, for example, an RRC message or a MAC CE (which then as an option may refer to a stored configuration). The UE then stores the configuration and may use it a later point in time (e.g., when the SCG is to be activated);

• a message (e.g., RRC(Connection)Reconfiguration) for configuration of the SCG, which may be sent independently of the other procedures for example just to provide the UE with an updated configuration for SCG activation. The UE then stores the configuration and may use it a later point in time (e.g., when the SCG is to be activated). The configuration could then be provided either when the SCG is deactivated or when it is activated;

• the RRC message (e.g., RRC(Connection)Reconfiguration) that is used for adding and/or modifying the PSCell/SCG, e.g., as part of an PSCell addition or PSCell change procedure. In some alternatives, the UE then stores the configuration and uses it a later point in time (e.g., when the SCG is to be activated);

• the RRC message (e.g., RRC(Connection)Reconfiguration) that is used for handover (change of the MCG PCell). The UE then either utilizes the configuration for activation of the SCG in connection with the handover procedure, or stores the configuration for use at a later point in time (e.g., when the SCG is to be activated).

• the RRC message (e.g., RRC Resume) that is used for resuming the connection.

The UE then either utilizes the configuration for activation of the SCG in connection with the resume procedure (reconfiguration with sync with the PSCell upon resume), or stores the configuration for use at a later point in time (e.g., when the SCG is to be activated).

• the RRC message (e.g., RRC Release) that is used for suspending the connection. In that case, the configuration can be stored and restored upon resumption so that it could possibly be used to activate the SCG, as the UE may for example store servingCellConfigCommon for the SCG that is being suspended while deactivated.

Embodiments herein also include a method where the SCG activation configuration includes parts that have a limited validity. As an example, the dedicated RACH configuration for the SCG activation that the UE receives (to enable CFRA) can then be valid only for a limited time. After the validity for the (relevant) dedicated RACH configuration has expired, the UE should then for example perform a CBRA instead.

Embodiments herein further include a method where the SCG activation procedure is supervised through a timer. The UE then for example starts a timer to supervise that the SCG activation procedure does not continue for too long. The UE may be configured by the network with a timer value for supervision of the SCG activation procedure or the timer value can be specified or hard coded. The timer value can then be dependent on (or different for) the alternative procedures for activation of the SCG, e.g., whether random access is used towards the SCG/PSCell or not, what types of measurements and/or synchronization that the UE needs to perform as part of the SCG activation and what types of signals that the UE then can use for the measurements and/or synchronization. In one example the UE is then configured with an SCG activation timer (Txxx), i.e. , a timer value for supervision of the SCG activation procedure. The UE then receives a timer Txxx value configuration (which e.g., is received and stored according to the methods disclosed above for the SCG activation configuration). The timer Txxx is to be started upon the reception of the command to activate the SCG, or when the SCG activation is triggered by the UE, e.g., due to availability of UL data, and stopped upon a successful activation of the SCG, in particular if that requires a random access procedure. If the timer expires while the UE is trying to activate the SCG the UE declares an SCG failure and sets the cause value to be associated to the expiry of Txxx timer. The SCG failure message may include an indication that the failure has occurred while an SCG activation procedure was performed.

In one method, the UE also receives a C-RNTI for the SCG MAC entity, which then may be received and stored according to the methods disclosed above for the SCG activation configuration).

Certain embodiments may provide one or more of the following technical advantage(s). The UE can determine whether to perform a random access towards the PSCell when the SCG is in a power saving mode of operation (e.g., deactivated SCG) when performing a procedure that requires that a random access is performed when the SCG is not in a power saving mode of operation, i.e., when the SCG is activated. The UE can also be provided with a configuration for the SCG activation procedure, for example including an indication whether to perform a random access towards the PSCell at the SCG activation and, if so, dedicated RACH configuration to support CFRA. It is possible for the network to configure the UE with a configuration for SCG activation prior to the actual SCG activation procedure, including dedicated RACH configuration, without reserving for example dedicated PRACH preambles for an indefinite time. The UE can be provided with a timer value for supervision of the SCG activation procedure.

In any event, note that the terms deactivated SCG, suspended SCG, inactive SCG and SCG in power saving mode are used interchangeably. The terms activated SCG, active SCG, resumed SCG and SCG in non-power saving mode are used interchangeably. The operation of the SCG operating in resumed or active mode may also be called 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 triggered event measurement reports, etc.

The text mostly refers and shows examples wherein the second cell group is a Secondary Cell Group (SCG) for a UE configured with Dual Connectivity (e.g., MR-DC). In that case, when the text refers to that a procedure is performed on the SCG, e.g., a random access, or performing measurements on the SCG, that may correspond to performing the procedure or the measurements on a cell of the SCG, e.g., the SpCell of the SCG and/or performing the procedure (or measurements) according to a configuration for the SCG.

The text describes terms like SCG and PSCell, as one of the cells associated with the SCG. That can be for example a PSCell as defined in NR specifications (e.g., RRC TS 38.331 v16.3.0), defined as a Special Cell (SpCell) of the SCG, or a Primary SCG Cell (PSCell), as follows:

- Secondary Cell Group: For a UE configured with dual connectivity, the subset of serving cells comprising of the PSCell and zero or more secondary cells.

- 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.

- Primary SCG Cell: For dual connectivity operation, the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure.

The text mostly refers and shows examples wherein the second cell group (as an example of group 20) is a Secondary Cell Group (SCG) that can be deactivated or suspended, for a UE configured with Dual Connectivity (e.g., MR-DC). However, some embodiments herein are also applicable for the case where the second cell group is a Master Cell Group (MCG) for a UE configured with Dual Connectivity (e.g., MR-DC), wherein the MCG could be deactivated or suspended.

The text “RACH configuration” refers to either or both 4-step RA type and the 2- step RA type. For 4-step RA-type, where the configuration includes (but is not limited to) the PRACH allocation and the preamble for MSG1 and for 2-step RA-type, the configuration includes (but is not limited to) the preamble and the PRACH/PUSCH allocation for MSGA.

Some embodiments herein provide an indication about random access towards (target) PSCell as part of another procedure.

In a first embodiment, the UE, which is configured with Dual Connectivity (e.g., MR-DC), receives a message indicating that a PSCell change is to be performed (i.e. , that the current (source) PSCell is to be changed to another (target) PSCell) where the SCG is to be in a power saving mode of operation (e.g., SCG deactivated) with the target PSCell, and where the message includes an indication whether the UE shall perform a random access procedure towards the target PSCell as part of the procedure or not.

Figure 10 illustrates a method performed by the UE in this first embodiment. In Step 15001 , the UE, which is configured with Dual Connectivity (e.g., MR-DC) receives a message from a network node instructing the UE to perform a PSCell change procedure, i.e., that the current (source) PSCell is to be changed to another (target) PSCell, where the SCG is to be in a power saving mode of operation (e.g., SCG deactivated) with the target PSCell (after the PSCell change procedure). The received message also includes an indication whether the UE shall perform a random access procedure towards the target PSCell as part of (or as a result of) the PSCell change procedure. This received message is one example of message 14 in Figure 1 , with the group 20 being exemplified as an SCG.

In Step 15002, in response to the received message, the UE initiates the PSCell change procedure towards the target PSCell.

In Steps 15003-15005, based on the indication in the received message, the UE determines whether to perform a random access towards the target PSCell as part of (or as a result of) the PSCell change procedure where the SCG is deactivated with the target PSCell after the PSCell change procedure. If the indication says that the UE shall not perform the random access procedure (NO at Step 15003), the UE then skips the random access procedure towards the target PSCell during the PSCell change procedure (Step 15005). If the indication says that the UE shall perform the random access procedure (YES at Step 15003), the UE then performs a random access procedure towards the target PSCell even if the SCG is deactivated (Step 15004).

In one example, the instruction whether to perform a random access procedure towards the target PSCell as part of (or as a result of) the PSCell change procedure is included as an explicit indication in the RRCReconfiguration message that configures the PSCell change. In one example, the indication is included within the corresponding Reconfiguration With Sync.

In one alternative, the network includes a Reconfig urationWith Sync for the SCG in the RRC Reconfiguration message that includes the instruction to perform the PSCell change procedure with the SCG in a power saving mode of operation (SCG deactivated) if the UE is to perform a random access procedure towards the target PSCell even if the SCG is deactivated. In case the Reconfig urationWith Sync is not included in the RRC Reconfiguration message that includes the instruction to perform the PSCell change procedure (with the SCG deactivated), the UE does then not perform the random access procedure towards the target PSCell.

In another alternative, the instruction of whether to perform a random access procedure towards the target PSCell as part of (or as a result of) the PSCell change procedure is provided through system information, which e.g., may be broadcasted or provided through dedicated signaling. In one example, the instruction is provided through system information for the target PSCell. In another example, the instruction is provided through system information for the source PSCell. In yet another example, the instruction is provided through system information for the MCG (PCell).

In another alternative, the UE (implicitly) does not perform any random access procedure towards the target PSCell as part of (or as a result of) the PSCell change procedure if the SCG is deactivated with the target PSCell (i.e. , after the PSCell change procedure). If the SCG is instead activated after the PSCell change, the UE performs the random access procedure towards the target PSCell as part of (or as a result of) the PSCell change procedure. Whether to perform the random access procedure towards the target PSCell is then based on whether the SCG is activated or deactivated after the PSCell change procedure.

In a second embodiment, the UE receives a message indicating that a PSCell addition is to be performed, i.e., as part of an SCG configuration, where the SCG is to be setup as deactivated, and where the message includes an indication whether the UE shall perform a random access procedure towards the PSCell as part of the PSCell addition procedure or not.

In one example, the instruction whether to perform a random access procedure towards the PSCell as part of (or as a result of) the PSCell addition procedure is included as an explicit indication in the RRCReconfiguration message that configures the PSCell addition. In one example, the indication is included within the corresponding Reconfiguration With Sync.

In one alternative, the network includes a Reconfig urationWith Sync for the SCG in the RRC Reconfiguration message that includes the instruction to perform the PSCell addition procedure with the SCG in a power saving mode of operation (SCG deactivated) if the UE is to perform a random access procedure towards the target PSCell even if the SCG is to be deactivated. In case the Reconfig urationWith Sync is not included in the RRC Reconfiguration message that includes the instruction to perform the PSCell addition procedure (with the SCG deactivated), the UE does then not perform the random access procedure towards the PSCell.

In another alternative, the instruction of whether to perform a random access procedure towards the PSCell as part of (or as a result of) the PSCell addition procedure is provided through system information, which e.g. may be broadcasted or provided through dedicated signaling. In one example, the instruction is provided through system information for the PSCell that is to be added. In another example, the instruction is provided through system information for the MCG (PCell).

In another alternative, the UE (implicitly) does not perform any random access procedure towards the PSCell as part of (or as a result of) the PSCell addition procedure if the SCG is setup in a power saving mode of operation (SCG deactivated). If the SCG is instead setup as activated as part of the PSCell addition procedure, the UE performs the random access procedure towards the PSCell as part of (or as a result of) the PSCell addition procedure. Whether to perform the random access procedure towards the PSCell is then based on whether the SCG setup as activated or deactivated after the PSCell addition procedure.

In another embodiment the UE, which is configured with Dual Connectivity (e.g., MR-DC) where the SCG is in a power saving mode of operation (e.g., SCG deactivated), receives a message indicating that an MCG mobility procedure (PCell handover) is to be performed including a key change for the SCG, and where the message includes an indication whether the UE shall perform a random access procedure towards the PSCell as part of (or as a result of) the MCG mobility/key change procedure or not.

In one example, the instruction whether to perform a random access procedure towards the PSCell (when the SCG is deactivated) as part of (or as a result of) the MCG mobility procedure with key change for the PSCell, is included as an explicit indication within the RRC Reconfiguration message that configures the MCG mobility procedure with key change for the PSCell. In one example, the indication is included within the corresponding Reconfig urationWith Sync for the SCG. In another example, the indication is included within the Reconfig urationWith Sync for the MCG.

In one alternative, the network includes a Reconfig urationWith Sync for the SCG within the RRC Reconfiguration message that includes the instruction to perform the MCG mobility procedure with key change for the PSCell if the UE is to perform a random access procedure towards the PSCell even if the SCG is deactivated. In case the ReconfigurationWithSync is not included in the corresponding RRC Reconfiguration message, the UE does then not perform the random access procedure towards the PSCell as part of the MCG mobility/key change procedure.

In another alternative, the instruction whether to perform a random access procedure towards the PSCell as part of (or as a result of) the MCG mobility procedure with key change for the PSCell is provided through system information, which e.g. may be broadcasted or provided through dedicated signaling. In one example, the instruction is provided through system information for the PSCell. In another example, the instruction is provided through system information for the MCG, either for the source PCell or for the target PCell.

In another alternative, the UE (implicitly) does not perform any random access procedure towards the PSCell as part of (or as a result of) the MCG mobility procedure with key change for the PSCell if the SCG is in a power saving mode of operation (SCG deactivated). Otherwise, i.e., if the SCG is activated, the UE performs the random access procedure towards the PSCell as part of (or as a result of) the MCG mobility procedure with key change for the PSCell. Whether to perform the random access procedure towards the PSCell is then based on whether the SCG is activated or deactivated when the MCG mobility procedure with key change for the PSCell is performed.

In yet another embodiment, the UE, which is resuming a connection from RRCJNACTIVE to RRC_CONNECTED including a resumption or setup of the SCG, where the SCG is resumed/setup in a power saving mode of operation (e.g. as SCG deactivated), receives an indication whether the UE shall perform a random access procedure towards the PSCell as part of (or as a result of) the RRC Resume procedure.

In one example, the instruction whether to perform a random access procedure towards the PSCell (when the SCG is deactivated) as part of (or as a result of) the RRC Resume procedure is included as an explicit indication within the RRC Resume message that includes the resumption (or setup) of the SCG. In one example, the indication is included within the corresponding ReconfigurationWithSync for the SCG. In another example, the indication is included within the ReconfigurationWithSync for the MCG. In yet another example, the indication is included as a separate indication in the RRCResume message.

In one alternative, the network includes a ReconfigurationWithSync for the SCG within the RRCResume message (or within the therein included RRCReconfigu ration message that contains the SCG configuration) if the UE is to perform a random access procedure towards the PSCell even if the SCG is resumed/setup as deactivated as part of the RRC resume procedure. In case the ReconfigurationWithSync is not included in the corresponding message, the UE does then not perform the random access procedure towards the PSCell as part of the RRC resume procedure.

In another alternative, the instruction of whether to perform a random access procedure towards the PSCell as part of (or as a result of) the RRC resume procedure where the SCG is resumed/setup in a power saving mode of operation (e.g. as SCG deactivated) is provided through system information, which e.g. may be broadcasted or provided through dedicated signaling. In one example, the instruction is provided through system information for the PSCell. In another example, the instruction is provided through system information for the MCG (in the serving cell that becomes the PCell after the RRC resume procedure).

In another alternative, the UE (implicitly) does not perform any random access procedure towards the PSCell as part of (or as a result of) the RRC resume procedure including a resumption or setup of the SCG, if the SCG resumed/setup in a power saving mode of operation (e.g. as SCG deactivated). Otherwise, i.e., if the SCG is activated, the UE performs the random access procedure towards the PSCell as part of (or as a result of) the RRC resume procedure. Whether to perform the random access procedure towards the PSCell is then based on whether the SCG is activated or deactivated when the SCG is resumed/setup as part of the RRC resume procedure.

In yet another alternative, the instruction of whether to perform a random access procedure towards the PSCell as part of (or as a result of) the RRC resume procedure where the SCG is resumed/setup in a power saving mode of operation (e.g. as SCG deactivated), is included in the RRC message (e.g. RRC Release) that is used for suspending the connection. In that case, the configuration can be stored and restored upon resumption so that it can be used to determine whether to perform the random access procedure towards the PSCell at the RRC resume procedure.

An alternative in the above embodiments is that in case the ReconfigurationWithSync is not included for the SCG in the RRC message that triggers the other procedure, in order to not trigger a random access towards the PSCell as part of that procedure (e.g. PSCell change, PSCell addition, MCG mobility or RRC resume), the UE receives some of the parameters that are included within ReconfigurationWithSync (e.g. C-RNTI for the SCG, ServingCellConfigCommon for the SCG and/or timer T304 for the corresponding procedure) in a separate configuration in the same message, and they are then applied at reception of the message. In one alternative, some or all of these parameters are instead only received and/or applied by the UE when the SCG is activated.

Provision of SCG activation configuration

When the SCG/PSCell is added/resumed in a power saving mode of operation (e.g., as SCG deactivated), or if it is deactivated (i.e. , changed from SCG activated to SCG deactivated), it will typically be activated at a later point in time. The SCG activation may then possibly require a random access procedure (depending on e.g. whether there is a need to align the UL time between the UE and the SN or if there is a need to achieve a beam alignment between the UE and the PSCell). As described further down, there may also be a need for a time supervision of the SCG activation procedure. There is then a need for a so-called SCG activation configuration, i.e., a configuration that e.g., includes instructions for how the SCG activation procedure should be performed.

In one embodiment, the UE is provided with a SCG activation configuration (as an example of activation configuration 24 in Figure 1) that includes one or more of the following parameters:

• An indication of whether to perform a random access procedure towards the PSCell as part of the SCG activation procedure, or whether to access the PSCell without a preceding random access procedure.

• A dedicated RACH configuration to be used for Contention Free Random Access towards the PSCell at the SCG activation.

• An indication that the UE is to perform a CBRA for the SCG activation, e.g., an indication that it is not configured with any dedicated RACH configuration.

• A configuration for resources to be used for access to the PSCell without performing a random access, e.g., UL grants for transmission of PUSCH towards the PSCell or an indication that the UE should start monitoring the DL PDCCH of the PSCell for scheduling.

• Cell specific parameters for the PSCell, such as e.g., the ServingCellConfigCommon defined in TS 38.331 v16.3.0.

• A timer value for supervision of the SCG activation procedure.

The indication whether to perform random access at the SCG activation can e.g., be used to determine whether to perform a random access towards the PSCell even if there is UL time alignment towards the PSCell (e.g., that the corresponding timeAlignmentTimer is still running) and there is still a beam alignment towards the PSCell. In one example, if the indication to mandatorily perform random access then is included, the random access procedure is thus performed regardless if the timeAlignmentTimer associated with the Primary Timing Advance Group (PTAG) has expired or not. Otherwise (i.e. , the indication is not included), the random access procedure is performed only if the timeAlignmentTimer associated with the PTAG is not running. In other words, if the timeAlignmentTimer associated with the PTAG is still running, then the random access procedure is not performed.

The need to perform a random access towards the PSCell at the SCG activation may depend on different aspects. As mentioned above, it could be based on e.g., whether the UE still has an uplink time alignment towards the PSCell at the point of time when the SCG activation takes place (e.g., based on whether the corresponding TimeAlignmentTimer is still running if this timer is till maintained) and whether the UE is considered to still have a beam alignment towards the PSCell. These are factors that may be possible for the UE to determine itself. In some cases and/or for some aspects, it may however be a network node that can best determine whether the UE should perform a random access or try to access without a random access. This could e.g., be related to whether the network node can handle that the UE starts accessing the PSCell without first performing a random access, e.g., based on the possibility to handle that the beam alignment towards the UE has become worse or the possibility to accommodate resources for an access without a preceding random access.

Based on the SCG activation configuration, the UE determines how to perform the SCG activation procedure towards the PSCell. In one example, the UE determines whether to perform a random access procedure towards the PSCell or whether to signal towards the PSCell without a preceding random access procedure. In one example, this is determined based on an indication that is included in the message from the network node. If the UE is to perform a random access procedure towards the PSCell as part of the activation of the SCG, the UE determines whether to then perform a CFRA or a CBRA based on the content of the received SCG activation configuration, e.g., whether a dedicated RACH configuration is included. If the UE then has received a dedicated RACH configuration that is valid for the (selected) beam in the PSCell, the UE performs a CFRA. Otherwise, it performs a CBRA. In one example, if the UE is not to perform a random access towards the PSCell for the SCG activation, it is provided a configuration for how to instead access the PSCell, e.g., as a configuration with UL grants for PUSCH transmission or a configuration for monitoring the DL PDCCH of the PSCell. In one example, the SCG activation procedure is supervised by a timer, with a value as indicated within the SCG activation configuration

In one alternative, the SCG activation configuration is provided to the UE in the message that indicates that the SCG should be activated.

In one other alternative, the SCG activation configuration is provided to the UE in a message that indicates that the SCG should be deactivated, and where the SCG activation configuration then is stored by the UE until the later SCG activation. This can e.g., be beneficial if the SCG activation is UL triggered, i.e., determined by the UE itself, or if the SCG activation is triggered by the network through a small indication to the UE, e.g., a MAC CE which cannot include the needed configuration.

In another alternative, the above SCG activation configuration is provided to the UE in a message that instructs that an SCG should be established for the UE, i.e., a PSCell addition procedure, where it is then indicated that the SCG/PSCell is to be setup as deactivated (i.e., in an SCG power saving mode of operation).

In one alternative, the SCG activation configuration is provided to the UE, which is configured with Dual Connectivity (e.g., MR-DC), in a message for reconfiguration where the current source PSCell is to be replaced by another target PSCell (i.e., a PSCell change procedure) and where the PSCell/SCG is to be in a power saving mode of operation (e.g., as deactivated SCG) with the target PSCell.

In one alternative, the SCG activation configuration is provided to the UE, which is configured with Dual Connectivity (e.g., MR-DC), in a message configuring a handover procedure (i.e., change of MCG PCell).

In another alternative, the SCG activation configuration is provided to the UE within an RRC Resume message that includes the resumption of the (or setup of an) SCG. The SCG may then be resumed/setup in a power saving mode of operation (e.g., as SCG deactivated) or as SCG activated.

In one alternative, the SCG activation configuration is provided to the UE within the RRC message (e.g., an RRC Release message) that is used for suspending the connection. The configuration can then be stored and restored upon resumption so that it can be used at activation of the SCG at a later point in time (or at the RRC resume procedure).

In yet another alternative, the UE, which is configured with Dual Connectivity (e.g., MR-DC), receives the SCG activation configuration in a message from the network (e.g., an RRC(Connection)Reconfiguration message) that is not sent to trigger any of the other above procedures. It can e.g., be a message that only includes the SCG activation configuration. The UE then stores the received SCG activation configuration for a later use when the SCG is to be activated. The included SCG activation configuration may be a first SCG activation configuration that is sent to the UE (i.e. , when the UE has no stored SCG activation configuration) or it can replace or update a previous configuration that the UE has stored. In one example, the UE receives the message with the SCG activation configuration when the SCG is activated. The configuration can then be used for activation of the SCG at a later point in time, after the SCG has first been deactivated. In another example, the message with the SCG activation configuration is sent by the network to the UE when the SCG is already deactivated.

In one alternative, the UE may be provided with one or several alternative configurations for the SCG activation, which then are stored by the UE. The network can then indicate to the UE which of these stored configurations that is to be used for the SCG activation. As an example, the network can indicate the UE to activate the SCG using a MAC CE (or RRC message), where this MAC CE (or RRC message) then may include an indication to which of the one or more stored SCG activation configurations to use. In another example, the network can indicate to the UE that the SCG is to be deactivated using a MAC CE (or RRC message), where this MAC CE (or RRC message) then may include an indication to which of the one or more stored SCG activation configurations that it shall use when the SCG is later to be activated again.

In one alternative, in case a random access procedure is to be performed towards the (target) PSCell at e.g. a PSCell addition, PSCell change, (MCG) handover or RRC Resume procedure even though the SCG is deactivated, the UE is provided two separate configurations for random access towards the PSCell in the corresponding message that triggers the procedure, one configuration to be used for the random access during that procedure and one to be used for a random access at a later SCG activation. In one alternative, the same configuration, or at least parts of the configuration, is used both for the random access that is performed towards the PSCell as part of the e.g. PSCell addition, PSCell change, (MCG) handover or RRC Resume procedure and for the random access procedure that is performed later for the SCG activation. As an example, the same dedicated RACH configuration, or parts of it, may then be used for both those random access procedures to enable CFRA.

Validity of SCG activation configuration

Since for example dedicated RACH configurations may be a limited resource in a network it may not be desirable or even possible to reserve them for a long time. Since it is not known beforehand how long time it will take until the SCG is to be activated again, which is typically done when there is traffic available that requires the SCG connection, a dedicated RACH configuration that is provided for a later SCG activation may need to be reserved for a long time. This is because the dedicated RACH configuration would be reserved until the SCG activation procedure is performed. In one alternative to the above embodiments, the dedicated RACH configuration that is provided to the UE for the (later) SCG activation is therefore only reserved to the UE for a limited time. In one example, the SCG activation configuration that is provided to the UE may then include an indication about how long the included dedicated RACH configuration, if any, is valid. When the UE shall use the configuration for SCG activation using random access, and the configuration includes an indication about the validity time for the dedicated RACH configuration only if the validity time has not expired for the dedicated RACH configuration for the PSCell beam that the UE has selected. Otherwise, the UE performs a CBRA. In another example, if the UE performs a random access when the timeAlignmentTimer expires, during this random access procedure, the network provides the UE with a new time-limited SCG activation information, for example in an RRCReconfigu ration message transmitted to the UE during or immediately after the random access procedure. In this example, the network may set the validity of the time-limited SCG activation information long enough to avoid that the SCG activation information expires before the timeAlignmentTimer.

Time supervision of SCG activation procedure

Some embodiments also include a method where the SCG activation procedure is supervised through a timer. The UE then starts a timer when the SCG activation procedure is triggered in order to supervise that the SCG activation procedure does not continue for too long. In one example, the timer is started by the UE when it receives an indication from the network, e.g. an RRC message or a MAC CE, to perform the SCG activation procedure. In another example, the UE starts the timer when it determines itself, e.g., based on that it has UL traffic for the SCG, that the SCG should be activated. The UE may be configured by the network with a timer value for supervision of the SCG activation procedure or the timer value can be specified or hard coded. The timer value can then be dependent on (or different for) the alternative procedures for activation of the SCG, e.g., whether random access is used towards the SCG/PSCell or not, what types of measurements and/or synchronization that the UE needs to perform as part of the SCG activation and what types of signals that the UE then can use for the measurements and/or synchronization. In one example, the UE is then configured with an SCG activation timer.

Detailed example embodiments

RRC

Below is a detailed example, as an implementation in the RRC specification TS 38.331 v16.3.0, of the embodiment when the instruction of whether to perform a random access procedure towards the target PSCell as part of (or as a result of) the PSCell change procedure is included as an explicit rach-SkipSCG indication in the ReconfigurationWithSync within the RRCReconfiguration message that configures the PSCell change. This thereby is a specific example of message 14 in Figure 1 , for indicating whether or not the wireless device is to perform the random access procedure towards a target PSCell (as an example of the primary cell of the group 20). Text that is added is underlined.

ReconfigurationWithSync ::= SEQUENCE { spCellConfigCommon ServingCellConfigCommon

OPTIONAL, - Need M newllE-ldentity RNTI-Value, t304 ENUMERATED {ms50, ms100, ms150, ms200, ms500, rnslOOO, ms2000, mslOOOO}, rach-ConfigDedicated CHOICE { uplink RACH-ConfigDedicated, supplementaryUplink RACH-ConfigDedicated

} OPTIONAL, - Need N

[[ smtc SSB-MTC

OPTIONAL - Need S

]],

[[ daps-UplinkPowerConfig-r16 DAPS-UplinkPowerConfig-r16

OPTIONAL - Need N

]],

[[ rach-SkipSCG-r17 Rach-SkipSCG-r17 OPTIONAL -

Need N

]]

}

5.3.5.3 Reception of an RRCReconfiguration by the UE

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

[...some parts skipped...]

1 > if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (UE in (NG)EN-DC):

2> if the RRCReconfiguration message was received via E-

UTRA SRB1 as specified in TS 36.331 [10]; or

2> if the RRCReconfiguration message was received via E-

UTRA RRC message RRCConnectionReconfiguration within

MobilityFromNRCommand',

3> if the RRCReconfiguration is applied due to a conditional reconfiguration execution: 4> submit the RRCReconfigurationComplete message via the E-UTRA MCG embedded in E-LITRA RRC message ULInformationTransferMRDC as specified in TS

36.331 [10], clause 5.6.2a.

3> else:

4> submit the RRCReconfigurationComplete via E- LITRA embedded in E-LITRA RRC message RRCConnectionReconfigurationComplete as specified in TS

36.331 [10], clause 5.3.5.3/5.3.5.4/5.4.2.3;

3> if reconfigurationWith Sync was included in spCellConfig of an SCG:

4> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3], if rach-SkipSCG is not configured;

3> else:

4> the procedure ends;

2> if the RRCReconfigu ration message was received within nr- SecondaryCellGroupConfig in RRCConnectionReconfiguration message received via SRB3 within DLlnformationTransferMRDC

3> submit the RRCReconfigurationComplete via E-LITRA embedded in E-LITRA RRC message RRCConnectionReconfigurationComplete as specified in TS

36.331 [10], clause 5.3.5.3/5.3.5.4;

3> if reconfigurationWithSync was included in spCellConfig of an SCG:

4> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3], if rach-SkipSCG is not configured;

3> else:

4> the procedure ends;

NOTE 1 : The order the UE sends the

RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.

2> else (RRCReconfigu ration was received via SRB3) but not within DUnformation TransferMRDC

3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;

NOTE 2: In (NG)EN-DC and NR-DC, in the case RRCReconfiguration is received via SRB1 or within DLlnformationTransferMRDC via SRB3, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3 but not within DLlnformationTransferMRDC, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete.

1 > else if the RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc- SecondaryCellGroup was received in RRCReconfiguration via SRB1):

2> if the RRCReconfiguration is applied due to a conditional reconfiguration execution:

3> submit the RRCReconfigurationComplete message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3.

2> if reconfigurationWithSync was included in spCellConfig in nr-SCG'.

3> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [31, if rach-SkipSCG is not configured: 2> else

3> the procedure ends;

NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.

1 > else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC):

2> if the RRCReconfiguration message was received within DLlnformationTransferMRDC'.

3> if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (NR SCG RRC Reconfiguration):

4> if reconfigurationWithSync was included in spCellConfig in nr-SCG:

5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3], if rac/i- SkipSCG is not configured;

4> else:

5> the procedure ends;

3> else:

4> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;

2> else:

3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;

1 > else (RRCReconfigu ration was received via SRB1 ):

2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;

2> if this is the first RRCReconfigu ration message after successful completion of the RRC re-establishment procedure:

3> resume SRB2 and DRBs that are suspended;

[... last parts skipped...]

5.3.5.5. 7 General

The network configures the UE with 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], The network provides the configuration parameters for a cell group in the CellGroupConfig IE.

The UE performs the following actions based on a received CellGroupConfig IE:

1 > if the CellGroupConfig contains the spCellConfig with reconfiguration With Sync:

2> perform Reconfiguration with sync according to 5.3.5.5.2;

2> if rach-SkipSCG is not configured:

3> resume all suspended radio bearers and resume SCG transmission for all radio bearers, if suspended;

1 > if the CellGroupConfig contains the rlc-BearerToReleaseList: 2> perform RLC bearer release as specified in 5.3.5.5.3; 1 > if the CellGroupConfig contains the rlc-BearerToAddModList.

2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4;

1 > if the CellGroupConfig contains the mac-CellGroupConfig

2> configure the MAC entity of this cell group as specified in 5.3.5.5.5;

1 > if the CellGroupConfig contains the sCellToReleaseList 2> perform SCell release as specified in 5.3.5.5.8;

1 > if the CellGroupConfig contains the spCellConfig 2> configure the SpCell as specified in 5.3.5.5.7;

1 > if the CellGroupConfig contains the sCellToAddModList

2> perform SCell addition/modification as specified in 5.3.5.5.9;

1 > if the CellGroupConfig contains the bh-RLC-ChannelToReleaseList 2> perform BH RLC channel release as specified in 5.3.5.5.10;

1 > if the CellGroupConfig contains the bh-RLC-ChannelToAddModList. 2> perform the BH RLC channel addition/modification as specified in 5.3.5.5.11 ;

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

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

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

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

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

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

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

Processing circuitry 1170 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 1170 may include processing information obtained by processing circuitry 1170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

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

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

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

Device readable medium 1180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1170. Device readable medium 1180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1170 and, utilized by network node 1160. Device readable medium 1180 may be used to store any calculations made by processing circuitry 1170 and/or any data received via interface 1190. In some embodiments, processing circuitry 1170 and device readable medium 1180 may be considered to be integrated.

Interface 1190 is used in the wired or wireless communication of signalling and/or data between network node 1160, network 1106, and/or WDs 1110. As illustrated, interface 1190 comprises port(s)/terminal(s) 1194 to send and receive data, for example to and from network 1106 over a wired connection. Interface 1190 also includes radio front end circuitry 1192 that may be coupled to, or in certain embodiments a part of, antenna 1162. Radio front end circuitry 1192 comprises filters 1198 and amplifiers 1196. Radio front end circuitry 1192 may be connected to antenna 1162 and processing circuitry 1170. Radio front end circuitry may be configured to condition signals communicated between antenna 1162 and processing circuitry 1170. Radio front end circuitry 1192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1198 and/or amplifiers 1196. The radio signal may then be transmitted via antenna 1162. Similarly, when receiving data, antenna 1162 may collect radio signals which are then converted into digital data by radio front end circuitry 1192. The digital data may be passed to processing circuitry 1170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 1160 may not include separate radio front end circuitry 1192, instead, processing circuitry 1170 may comprise radio front end circuitry and may be connected to antenna 1162 without separate radio front end circuitry 1192. Similarly, in some embodiments, all or some of RF transceiver circuitry 1172 may be considered a part of interface 1190. In still other embodiments, interface 1190 may include one or more ports or terminals 1194, radio front end circuitry 1192, and RF transceiver circuitry 1172, as part of a radio unit (not shown), and interface 1190 may communicate with baseband processing circuitry 1174, which is part of a digital unit (not shown).

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

Antenna 1162, interface 1190, and/or processing circuitry 1170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1162, interface 1190, and/or processing circuitry 1170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 1187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 1160 with power for performing the functionality described herein. Power circuitry 1187 may receive power from power source 1186. Power source 1186 and/or power circuitry 1187 may be configured to provide power to the various components of network node 1160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1186 may either be included in, or external to, power circuitry 1187 and/or network node 1160. For example, network node 1160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 1187. As a further example, power source 1186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

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

As illustrated, wireless device 1110 includes antenna 1111 , interface 1114, processing circuitry 1120, device readable medium 1130, user interface equipment 1132, auxiliary equipment 1134, power source 1136 and power circuitry 1137. WD 1110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-loT, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 1110.

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

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

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

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

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

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

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

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

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

Power source 1136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 1110 may further comprise power circuitry 1137 for delivering power from power source 1136 to the various parts of WD 1110 which need power from power source 1136 to carry out any functionality described or indicated herein. Power circuitry 1137 may in certain embodiments comprise power management circuitry. Power circuitry 1137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 1137 may also in certain embodiments be operable to deliver power from an external power source to power source 1136. This may be, for example, for the charging of power source 1136. Power circuitry 1137 may perform any formatting, converting, or other modification to the power from power source 1136 to make the power suitable for the respective components of WD 1110 to which power is supplied.

Figure 12 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 12200 may be any UE identified by the 3 ^rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 1200, as illustrated in Figure 12, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 ^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 12 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 12, UE 1200 includes processing circuitry 1201 that is operatively coupled to input/output interface 1205, radio frequency (RF) interface 1209, network connection interface 1211 , memory 1215 including random access memory (RAM) 1217, read-only memory (ROM) 1219, and storage medium 1221 or the like, communication subsystem 1231 , power source 1233, and/or any other component, or any combination thereof. Storage medium 1221 includes operating system 1223, application program 1225, and data 1227. In other embodiments, storage medium 1221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 12, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

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

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

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

Storage medium 1221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 1221 may allow UE 1200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 1221 , which may comprise a device readable medium.

In Figure 12, processing circuitry 1201 may be configured to communicate with network 1243b using communication subsystem 1231 . Network 1243a and network 1243b may be the same network or networks or different network or networks. Communication subsystem 1231 may be configured to include one or more transceivers used to communicate with network 1243b. For example, communication subsystem 1231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11 , CDMA, WCDMA, GSM, LTE, LITRAN, WiMax, or the like. Each transceiver may include transmitter 1233 and/or receiver 1235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1233 and receiver 1235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

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

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

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

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

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

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

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

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

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

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, virtual machine 1340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of virtual machines 1340, and that part of hardware 1330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1340, forms a separate virtual network elements (VNE).

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

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

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

Figure 14 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference to FIGURE 14, in accordance with an embodiment, a communication system includes telecommunication network 1410, such as a 3GPP-type cellular network, which comprises access network 1411 , such as a radio access network, and core network 1414. Access network 1411 comprises a plurality of base stations 1412a, 1412b, 1412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1413a, 1413b, 1413c. Each base station 1412a, 1412b, 1412c is connectable to core network 1414 over a wired or wireless connection 1415. A first UE 1491 located in coverage area 1413c is configured to wirelessly connect to, or be paged by, the corresponding base station 1412c. A second UE 1492 in coverage area 1413a is wirelessly connectable to the corresponding base station 1412a. While a plurality of UEs 1491 , 1492 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 1412.

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

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

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 15. Figure 15 illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system 1500, host computer 1510 comprises hardware 1515 including communication interface 1516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1500. Host computer 1510 further comprises processing circuitry 1518, which may have storage and/or processing capabilities. In particular, processing circuitry 1518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 1510 further comprises software 1511 , which is stored in or accessible by host computer 1510 and executable by processing circuitry 1518. Software 1511 includes host application 1512. Host application 1512 may be operable to provide a service to a remote user, such as UE 1530 connecting via OTT connection 1550 terminating at UE 1530 and host computer 1510. In providing the service to the remote user, host application 1512 may provide user data which is transmitted using OTT connection 1550.

Communication system 1500 further includes base station 1520 provided in a telecommunication system and comprising hardware 1525 enabling it to communicate with host computer 1510 and with UE 1530. Hardware 1525 may include communication interface 1526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1500, as well as radio interface 1527 for setting up and maintaining at least wireless connection 1570 with UE 1530 located in a coverage area (not shown in Figure 15) served by base station 1520. Communication interface 1526 may be configured to facilitate connection 1560 to host computer 1510. Connection 1560 may be direct or it may pass through a core network (not shown in Figure 15) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1525 of base station 1520 further includes processing circuitry 1528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 1520 further has software 1521 stored internally or accessible via an external connection.

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

It is noted that host computer 1510, base station 1520 and UE 1530 illustrated in Figure 15 may be similar or identical to host computer 1430, one of base stations 1412a, 1412b, 1412c and one of UEs 1491 , 1492 of Figure 14, respectively. This is to say, the inner workings of these entities may be as shown in Figure 15 and independently, the surrounding network topology may be that of Figure 14.

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

Wireless connection 1570 between UE 1530 and base station 1520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 1530 using OTT connection 1550, in which wireless connection 1570 forms the last segment.

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

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

Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 14 and 15. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section. In step 1710 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 1720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1730 (which may be optional), the UE receives the user data carried in the transmission.

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

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

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

In view of the above, then, embodiments herein generally include a communication system including a host computer. The host computer may comprise processing circuitry configured to provide user data. The host computer may also comprise a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The cellular network may comprise a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the embodiments described above for a base station.

In some embodiments, the communication system further includes the base station.

In some embodiments, the communication system further includes the UE, wherein the UE is configured to communicate with the base station.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data. In this case, the UE comprises processing circuitry configured to execute a client application associated with the host application.

Embodiments herein also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, providing user data. The method may also comprise, at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The base station performs any of the steps of any of the embodiments described above for a base station.

In some embodiments, the method further comprising, at the base station, transmitting the user data.

In some embodiments, the user data is provided at the host computer by executing a host application. In this case, the method further comprises, at the UE, executing a client application associated with the host application.

Embodiments herein also include a user equipment (UE) configured to communicate with a base station. The UE comprises a radio interface and processing circuitry configured to perform any of the embodiments above described for a UE.

Embodiments herein further include a communication system including a host computer. The host computer comprises processing circuitry configured to provide user data, and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE). The UE comprises a radio interface and processing circuitry. The UE’s components are configured to perform any of the steps of any of the embodiments described above for a UE.

In some embodiments, the cellular network further includes a base station configured to communicate with the UE.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data. The UE’s processing circuitry is configured to execute a client application associated with the host application.

Embodiments also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, providing user data and initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The UE performs any of the steps of any of the embodiments described above for a UE.

In some embodiments, the method further comprises, at the UE, receiving the user data from the base station.

Embodiments herein further include a communication system including a host computer. The host computer comprises a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The UE comprises a radio interface and processing circuitry. The UE’s processing circuitry is configured to perform any of the steps of any of the embodiments described above for a UE.

In some embodiments the communication system further includes the UE.

In some embodiments, the communication system further including the base station. In this case, the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application. And the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing request data. And the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

Embodiments herein also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, receiving user data transmitted to the base station from the UE. The UE performs any of the steps of any of the embodiments described above for the UE.

In some embodiments, the method further comprises, at the UE, providing the user data to the base station.

In some embodiments, the method also comprises, at the UE, executing a client application, thereby providing the user data to be transmitted. The method may further comprise, at the host computer, executing a host application associated with the client application.

In some embodiments, the method further comprises, at the UE, executing a client application, and, at the UE, receiving input data to the client application. The input data is provided at the host computer by executing a host application associated with the client application. The user data to be transmitted is provided by the client application in response to the input data.

Embodiments also include a communication system including a host computer. The host computer comprises a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The base station comprises a radio interface and processing circuitry. The base station’s processing circuitry is configured to perform any of the steps of any of the embodiments described above for a base station.

In some embodiments, the communication system further includes the base station.

In some embodiments, the communication system further includes the UE. The UE is configured to communicate with the base station.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application. And 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.

Embodiments moreover include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE. The UE performs any of the steps of any of the embodiments described above for a UE.

In some embodiments, the method further comprises, at the base station, receiving the user data from the UE.

In some embodiments, the method further comprises, at the base station, initiating a transmission of the received user data to the host computer.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the description.

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

The term “A and/or B” as used herein covers embodiments having A alone, B alone, or both A and B together. The term “A and/or B” may therefore equivalently mean “at least one of any one or more of A and B”.

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

Notably, modifications and other embodiments of the disclosed invention(s) will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention(s) is/are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Example embodiments of the techniques and apparatus described herein include, but are not limited to, the following enumerated examples: Group A Embodiments

A1 . A method performed by a wireless device, the method comprising: receiving a message that indicates whether or not the wireless device shall perform a random access procedure towards a group of serving cells that is, or is to be, in a deactivated state.

A2. The method of embodiment A1 , wherein the message indicates whether or not the wireless device shall perform a random access procedure towards a group of serving cells that is to be in the deactivated state.

A3. The method of embodiment A2, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of, or as a result of, a procedure for setting up the group of serving cells with the group already in the deactivated state upon setup.

A4. The method of embodiment A3, wherein the procedure is a procedure for adding or changing a primary cell of the group.

A5. The method of embodiment A2, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of, or as a result of, a procedure for resuming a radio resource control connection in a primary cell of the group, with the group already in the deactivated state upon resumption of the radio resource control connection.

A6. The method of embodiment A1 , wherein the message indicates whether or not the wireless device shall perform a random access procedure towards a group of serving cells that is in the deactivated state.

A7. The method of embodiment A6, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of, or as a result of, a procedure started while the group of serving cells is in the deactivated state.

A8. The method of embodiment A7, wherein group of serving cells is a secondary cell group of the wireless device for multi-connectivity operation, and wherein the procedure is a procedure for changing a master cell group of the wireless device for multi-connectivity operation and/or a procedure that results in a change in a security key used towards the secondary cell group.

A9. The method of embodiment A1 , wherein the message indicates whether or not the wireless device shall perform a random access procedure towards a group of serving cells as part of, or as a result of, a procedure for activating the group of serving cells out of the deactivated state.

A10. The method of any of embodiments A1 -A9, wherein the message is received while the group of serving cells is in the deactivated state or is received before the group of serving cells has been established.

A11 . The method of any of embodiments A1 -A10, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of, or as a result of, a certain procedure.

A12. The method of embodiment A11 , wherein the message configures the certain procedure.

A13. The method of embodiment A11 , wherein the message configures another procedure and is received before the certain procedure is triggered.

A14. The method of any of embodiments A1 -A13, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells, by indicating whether or not the wireless device shall skip a random access procedure for a target primary cell of the group of serving cells.

A15. The method of embodiment A14, wherein the message is configurable to include an explicit indication indicating that the wireless device shall skip a random access procedure for a target primary cell of the group of serving cells, and wherein inclusion or exclusion of the explicit indication in the received message indicates whether or not the wireless device shall skip a random access procedure for a target primary cell of the group of serving cells.

A16. The method of any of embodiments A1 -A15, wherein the message is configurable to include an explicit indication indicating that the wireless device shall perform a random access procedure towards the group of serving cells, and wherein inclusion or exclusion of the explicit indication in the received message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells.

A17. The method of any of embodiments A1 -A15, wherein the message is configurable to include an information element with parameters for synchronous reconfiguration to a target cell in the group, and wherein inclusion or exclusion of the information element in the received message respectively indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells.

A18. The method of any of embodiments A1 -A17, wherein the message is a radio resource control message.

A19. The method of any of embodiments A1 -A18, wherein the message is a system information message that conveys system information.

A20. The method of any of embodiments A1 -A19, further comprising: deciding whether or not to perform the random access procedure towards the group of serving cells based on the received message; and performing, or refraining from performing, the random access procedure towards the group of serving cells based on said deciding.

A21 . The method of any of embodiments A1 -A20, further comprising: performing the random access procedure towards the group of serving cells if the message indicates that the wireless device shall perform the random access procedure towards the group of serving cells; or refraining from performing the random access procedure towards the group of serving cells if the message indicates that the wireless device shall not perform the random access procedure towards the group of serving cells.

A22. The method of embodiment A5, wherein the message is a release message indicating that the radio resource control connection is to be suspended.

A23. The method of embodiment A5, wherein the message is a resume message indicating that the radio resource control connection is to be resumed.

A24. The method of embodiment A5, wherein the message indicates that the group of serving cells is to be deactivated or is to be set up as deactivated.

A25. The method of embodiment A9, further comprising deciding, based on the message, whether or not to perform a random access procedure towards the group of serving cells as part of, or as a result of, a procedure for activating the group of serving cells out of the deactivated state, irrespective of whether or not the wireless has uplink time alignment towards a primary cell of the group of serving cells when the procedure is performed and/or irrespective of whether or not the wireless device has beam alignment towards a primary cell of the group of serving cells when the procedure is performed.

A26. The method of any of embodiments A1 -A25, wherein the wireless device is configured to monitor a downlink control channel and/or a downlink data channel associated with the group of serving cells when the group of serving cells is in an activated state , and wherein the wireless device is configured to refrain from monitoring the downlink control channel and/or the downlink data channel associated with the group of serving cells when the group of serving cells is in the deactivated state.

A27. The method of embodiment A26, wherein the wireless device is configured to perform and report channel state measurements when the group of serving cells is in the activated state, and wherein the wireless device is configured to refrain from performing and reporting channel state measurements when the group of serving cells is in the deactivated state.

A28. The method of embodiment A26, wherein the wireless device is configured to perform and report channel state measurements no matter whether the group of serving cells is in the activated state or the deactivated state.

A29. The method of any of embodiments A1 -A28, wherein group of serving cells is a secondary cell group of the wireless device for multi-connectivity operation.

A30. The method of any of embodiments A1 -A28, wherein group of serving cells is a master cell group of the wireless device for multi-connectivity operation.

AA. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to a base station.

Group AA Embodiments

AA1 . A method performed by a wireless device, the method comprising: receiving an activation configuration that indicates one or more parameters governing how the wireless device is to perform an activation procedure for activating a group of serving cells.

AA2. The method of embodiment AA1 , wherein the one or more parameters include a parameter governing whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of the activation procedure for activating the group of serving cells.

AA3. The method of any of embodiments AA1 -AA2, wherein the one or more parameters include one or more parameters governing a random access procedure that the wireless device shall perform towards the group of serving cells as part of the activation procedure for activating the group of serving cells.

AA4. The method of embodiment AA3, wherein the one or more parameters governing the random access procedure include a parameter governing a type of the random access procedure that the wireless device shall perform.

AA5. The method of any of embodiments AA3-AA4, wherein the one or more parameters governing the random access procedure include a parameter governing whether the random access procedure that the wireless device shall perform is to be a content-based random access procedure or a contention-free random access procedure.

AA6. The method of any of embodiments AA3-AA5, wherein the one or more parameters governing the random access procedure include a dedicated random access channel configuration to be used for the random access procedure.

AA7. The method of any of embodiments AA1 -AA6, wherein the one or more parameters include a parameter indicating resources to be used to access a serving cell of the group without performing a random access procedure towards that serving cell.

AA8. The method of embodiment AA7, wherein the indicated resources include one or more uplink grants for transmission on an uplink data channel towards the serving cell and/or include a configuration for monitoring a downlink control channel of the serving cell.

AA9. The method of any of embodiments AA1 -AA8, wherein the one or more parameters include cell-specific parameters for a primary cell of the group.

AA10. The method of any of embodiments AA1-AA9, wherein the one or more parameters include a value of a timer that is to supervise the activation procedure for activating the group of serving cells.

AA11 . The method of any of embodiments AA1-AA10, wherein the activation configuration is received while the group of serving cells is deactivated and/or is received in a message that indicates the group of serving cells is to be activated.

AA12. The method of any of embodiments AA1-AA10, wherein the activation configuration is received in a message that indicates the group of serving cells is to be deactivated.

AA13. The method of any of embodiments AA1-AA10, wherein the activation configuration is received in a message that indicates: the group of serving cells is to be established with the group of serving cells deactivated; or a primary cell of the group is to be changed with the group of serving cells deactivated.

AA14. The method of any of embodiments AA1-AA10, wherein the activation configuration is received in a message that configures a handover of the wireless device.

AA15. The method of any of embodiments AA1-AA10, wherein the activation configuration is received in a message dedicated to conveying the activation configuration.

AA16. The method of any of embodiments AA1-AA10, wherein the activation configuration is received in a message that indicates a radio resource control connection is to be suspended or resumed at a primary cell of the group.

AA17. The method of any of embodiments AA1-AA16, wherein the activation configuration is received in a message that also includes a deactivation configuration, wherein the deactivation configuration indicates one or more parameters governing how the wireless device is to perform a deactivation procedure for deactivating the group of serving cells.

AA18. The method of embodiment AA17, wherein the one or more parameters indicated by the activation configuration include one or more parameters governing a random access procedure that the wireless device shall perform towards the group of serving cells as part of the activation procedure, and wherein the one or more parameters indicated by the deactivation configuration include one or more parameters governing a random access procedure that the wireless device shall perform towards the group of serving cells as part of the deactivation procedure.

AA19. The method of any of embodiments AA1-AA18, further comprising receiving signaling indicating a duration for which at least a portion of the activation configuration is valid.

AA20. The method of embodiment AA19, wherein the at least a portion of the activation configuration is a dedicated random access channel configuration.

AA21 . The method of embodiment AA20, further comprising performing contention-free random access towards the group of serving cells using the dedicated random access channel configuration or performing contention-based random access towards the group of serving cells, depending respectively on whether or not the dedicated random access channel configuration is valid. AA22. The method of any of embodiments AA19-AA21 , wherein the duration is indicated by the activation configuration.

AA23. The method of any of embodiments AA1-AA22, further comprising receiving signaling indicating a maximum allowed duration of the activation procedure.

AA24. The method of embodiment AA23, wherein the maximum allowed duration is indicated by the activation configuration.

AA25. The method of any of embodiments AA1-AA24, wherein said activating activates the group of serving cells from a deactivated state into an activated state, wherein the wireless device is configured to monitor a downlink control channel and/or a downlink data channel associated with the group of serving cells when the group of serving cells is in the activated state , and wherein the wireless device is configured to refrain from monitoring the downlink control channel and/or the downlink data channel associated with the group of serving cells when the group of serving cells is in the deactivated state.

AA26. The method of embodiment AA25, wherein the wireless device is configured to perform and report channel state measurements when the group of serving cells is in the activated state, and wherein the wireless device is configured to refrain from performing and reporting channel state measurements when the group of serving cells is in the deactivated state.

AA27. The method of embodiment AA25, wherein the wireless device is configured to perform and report channel state measurements no matter whether the group of serving cells is in the activated state or the deactivated state.

AA28. The method of any of embodiments AA1-AA27, wherein group of serving cells is a secondary cell group of the wireless device for multi-connectivity operation.

AA29. The method of any of embodiments AA1-AA27, wherein group of serving cells is a master cell group of the wireless device for multi-connectivity operation. AA30. The method of any of embodiments AA1-AA29, wherein the activation configuration is received before triggering of the activation procedure, and wherein the method further comprises: storing the activation configuration; and upon triggering of the activation procedure, performing the activation procedure according to the stored activation configuration.

AA31 . The method of any of embodiments AA1-AA30, further comprising performing the activation procedure according to the activation configuration.

AA. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to a base station.

Group B Embodiments

B1 . A method performed by a radio network node, the method comprising: transmitting, to a wireless device, a message that indicates whether or not the wireless device shall perform a random access procedure towards a group of serving cells that is, or is to be, in a deactivated state.

B2. The method of embodiment B1 , wherein the message indicates whether or not the wireless device shall perform a random access procedure towards a group of serving cells that is to be in the deactivated state.

B3. The method of embodiment B2, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of, or as a result of, a procedure for setting up the group of serving cells with the group already in the deactivated state upon setup.

B4. The method of embodiment B3, wherein the procedure is a procedure for adding or changing a primary cell of the group.

B5. The method of embodiment B2, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of, or as a result of, a procedure for resuming a radio resource control connection in a primary cell of the group, with the group already in the deactivated state upon resumption of the radio resource control connection.

B6. The method of embodiment B1 , wherein the message indicates whether or not the wireless device shall perform a random access procedure towards a group of serving cells that is in the deactivated state.

B7. The method of embodiment B6, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of, or as a result of, a procedure started while the group of serving cells is in the deactivated state.

B8. The method of embodiment B7, wherein group of serving cells is a secondary cell group of the wireless device for multi-connectivity operation, and wherein the procedure is a procedure for changing a master cell group of the wireless device for multi-connectivity operation and/or a procedure that results in a change in a security key used towards the secondary cell group.

B9. The method of embodiment B1 , wherein the message indicates whether or not the wireless device shall perform a random access procedure towards a group of serving cells as part of, or as a result of, a procedure for activating the group of serving cells out of the deactivated state.

B10. The method of any of embodiments B1 -B9, wherein the message is transmitted while the group of serving cells is in the deactivated state or is transmitted before the group of serving cells has been established.

B11 . The method of any of embodiments B1 -B10, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of, or as a result of, a certain procedure.

B12. The method of embodiment B11 , wherein the message configures the certain procedure.

B13. The method of embodiment B11 , wherein the message configures another procedure and is transmitted before the certain procedure is triggered.

B14. The method of any of embodiments B1 -B13, wherein the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells, by indicating whether or not the wireless device shall skip a random access procedure for a target primary cell of the group of serving cells.

B15. The method of embodiment B14, wherein the message is configurable to include an explicit indication indicating that the wireless device shall skip a random access procedure for a target primary cell of the group of serving cells, and wherein inclusion or exclusion of the explicit indication in the message indicates whether or not the wireless device shall skip a random access procedure for a target primary cell of the group of serving cells.

B16. The method of any of embodiments B1 -B15, wherein the message is configurable to include an explicit indication indicating that the wireless device shall perform a random access procedure towards the group of serving cells, and wherein inclusion or exclusion of the explicit indication in the message indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells.

B17. The method of any of embodiments B1 -B15, wherein the message is configurable to include an information element with parameters for synchronous reconfiguration to a target cell in the group, and wherein inclusion or exclusion of the information element in the message respectively indicates whether or not the wireless device shall perform a random access procedure towards the group of serving cells.

B18. The method of any of embodiments B1 -B17, wherein the message is a radio resource control message.

B19. The method of any of embodiments B1 -B18, wherein the message is a system information message that conveys system information.

B20. The method of embodiment B5, wherein the message is a release message indicating that the radio resource control connection is to be suspended.

B21 . The method of embodiment B5, wherein the message is a resume message indicating that the radio resource control connection is to be resumed.

B22. The method of embodiment B5, wherein the message indicates that the group of serving cells is to be deactivated or is to be set up as deactivated.

B23. The method of any of embodiments B1 -B22, wherein the wireless device is configured to monitor a downlink control channel and/or a downlink data channel associated with the group of serving cells when the group of serving cells is in an activated state , and wherein the wireless device is configured to refrain from monitoring the downlink control channel and/or the downlink data channel associated with the group of serving cells when the group of serving cells is in the deactivated state.

B24. The method of embodiment B23, wherein the wireless device is configured to perform and report channel state measurements when the group of serving cells is in the activated state, and wherein the wireless device is configured to refrain from performing and reporting channel state measurements when the group of serving cells is in the deactivated state.

B25. The method of embodiment B23, wherein the wireless device is configured to perform and report channel state measurements no matter whether the group of serving cells is in the activated state or the deactivated state.

B26. The method of any of embodiments B1 -B25, wherein group of serving cells is a secondary cell group of the wireless device for multi-connectivity operation.

B27. The method of any of embodiments B1 -B25, wherein group of serving cells is a master cell group of the wireless device for multi-connectivity operation. Group BB Embodiments

BB1 . A method performed by a radio network node, the method comprising: transmitting, to a wireless device, an activation configuration that indicates one or more parameters governing how the wireless device is to perform an activation procedure for activating a group of serving cells.

BB2. The method of embodiment BB1 , wherein the one or more parameters include a parameter governing whether or not the wireless device shall perform a random access procedure towards the group of serving cells as part of the activation procedure for activating the group of serving cells.

BB3. The method of any of embodiments BB1 - BB2, wherein the one or more parameters include one or more parameters governing a random access procedure that the wireless device shall perform towards the group of serving cells as part of the activation procedure for activating the group of serving cells.

BB4. The method of embodiment BB3, wherein the one or more parameters governing the random access procedure include a parameter governing a type of the random access procedure that the wireless device shall perform.

BB5. The method of any of embodiments BB3-BB4, wherein the one or more parameters governing the random access procedure include a parameter governing whether the random access procedure that the wireless device shall perform is to be a content-based random access procedure or a contention-free random access procedure.

BB6. The method of any of embodiments BB3-BB5, wherein the one or more parameters governing the random access procedure include a dedicated random access channel configuration to be used for the random access procedure.

BB7. The method of any of embodiments BB1-BB6, wherein the one or more parameters include a parameter indicating resources to be used to access a serving cell of the group without performing a random access procedure towards that serving cell. BB8. The method of embodiment BB7, wherein the indicated resources include one or more uplink grants for transmission on an uplink data channel towards the serving cell and/or include a configuration for monitoring a downlink control channel of the serving cell.

BB9. The method of any of embodiments BB1-BB8, wherein the one or more parameters include cell-specific parameters for a primary cell of the group.

BB10. The method of any of embodiments BB1-BB9, wherein the one or more parameters include a value of a timer that is to supervise the activation procedure for activating the group of serving cells.

BB11 . The method of any of embodiments BB1 -BB10, wherein the activation configuration is transmitted while the group of serving cells is deactivated and/or is transmitted in a message that indicates the group of serving cells is to be activated.

BB12. The method of any of embodiments BB1-BB10, wherein the activation configuration is transmitted in a message that indicates the group of serving cells is to be deactivated.

BB13. The method of any of embodiments BB1-BB10, wherein the activation configuration is transmitted a message that indicates: the group of serving cells is to be established with the group of serving cells deactivated; or a primary cell of the group is to be changed with the group of serving cells deactivated.

BB14. The method of any of embodiments BB1-BB10, wherein the activation configuration is transmitted in a message that configures a handover of the wireless device.

BB15. The method of any of embodiments BB1-BB10, wherein the activation configuration is transmitted in a message dedicated to conveying the activation configuration. BB16. The method of any of embodiments BB1 -BB10, wherein the activation configuration is transmitted in a message that indicates a radio resource control connection is to be suspended or resumed at a primary cell of the group.

BB17. The method of any of embodiments BB1 -BB16, wherein the activation configuration is transmitted in a message that also includes a deactivation configuration, wherein the deactivation configuration indicates one or more parameters governing how the wireless device is to perform a deactivation procedure for deactivating the group of serving cells.

BB18. The method of embodiment BB17, wherein the one or more parameters indicated by the activation configuration include one or more parameters governing a random access procedure that the wireless device shall perform towards the group of serving cells as part of the activation procedure, and wherein the one or more parameters indicated by the deactivation configuration include one or more parameters governing a random access procedure that the wireless device shall perform towards the group of serving cells as part of the deactivation procedure.

BB19. The method of any of embodiments BB1 -BB18, further comprising transmitting signaling indicating a duration for which at least a portion of the activation configuration is valid.

BB20. The method of embodiment BB19, wherein the at least a portion of the activation configuration is a dedicated random access channel configuration.

BB21 . The method of embodiment BB20, wherein the duration is indicated by the activation configuration.

BB22. The method of any of embodiments BB1 -BB21 , further comprising transmitting signaling indicating a maximum allowed duration of the activation procedure.

BB23. The method of embodiment BB22, wherein the maximum allowed duration is indicated by the activation configuration. BB25. The method of any of embodiments BB1-BB23, wherein said activating activates the group of serving cells from a deactivated state into an activated state, wherein the wireless device is to monitor a downlink control channel and/or a downlink data channel associated with the group of serving cells when the group of serving cells is in the activated state , and wherein the wireless device is to refrain from monitoring the downlink control channel and/or the downlink data channel associated with the group of serving cells when the group of serving cells is in the deactivated state.

BB26. The method of embodiment BB25, wherein the radio network node is to receive one or more channel state measurement reports from the wireless device when the group of serving cells is in the activated state, and wherein the radio network node is configured to not receive channel state measurement reports from the wireless device when the group of serving cells is in the deactivated state.

BB27. The method of embodiment BB25, wherein the radio network node is configured to receive channel state measurement reports from the wireless device no matter whether the group of serving cells is in the activated state or the deactivated state.

BB28. The method of any of embodiments BB1-BB27, wherein group of serving cells is a secondary cell group of the wireless device for multi-connectivity operation.

BB29. The method of any of embodiments BB1-BB27, wherein group of serving cells is a master cell group of the wireless device for multi-connectivity operation.

BB30. The method of any of embodiments BB1-BB29, wherein the activation configuration is transmitted before the activation procedure is triggered.

BB. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.

Group C Embodiments

C1 . A wireless device configured to perform any of the steps of any of the Group A or Group AA embodiments.

C2. A wireless device comprising processing circuitry configured to perform any of the steps of any of the Group A or Group AA embodiments.

C3. A wireless device comprising: communication circuitry; and processing circuitry configured to perform any of the steps of any of the Group A or Group AA embodiments.

C4. A wireless device comprising: processing circuitry configured to perform any of the steps of any of the Group A or Group AA embodiments; and power supply circuitry configured to supply power to the wireless device.

C5. A wireless device comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the wireless device is configured to perform any of the steps of any of the Group A or Group AA embodiments.

C6. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A or Group AA embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

C7. A computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to carry out the steps of any of the Group A or Group AA embodiments.

C8. A carrier containing the computer program of embodiment C7, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

C9. A radio network node configured to perform any of the steps of any of the Group B or Group BB embodiments.

C10. A radio network node comprising processing circuitry configured to perform any of the steps of any of the Group B or Group BB embodiments.

C11 . A radio network node comprising: communication circuitry; and processing circuitry configured to perform any of the steps of any of the Group B or Group BB embodiments.

C12. A radio network node comprising: processing circuitry configured to perform any of the steps of any of the Group B or Group BB embodiments; power supply circuitry configured to supply power to the radio network node.

C13. A radio network node comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the radio network node is configured to perform any of the steps of any of the Group B or Group BB embodiments.

C14. The radio network node of any of embodiments C9-C13, wherein the radio network node is a base station.

C15. A computer program comprising instructions which, when executed by at least one processor of a radio network node, causes the radio network node to carry out the steps of any of the Group B or Group BB embodiments.

C16. The computer program of embodiment C14, wherein the radio network node is a base station.

C17. A carrier containing the computer program of any of embodiments C15-C16, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Group D Embodiments

D1 . A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B or Group BB embodiments.

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

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

D4. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

D5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B or Group BB embodiments.

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

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

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

D9. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A or Group AA embodiments.

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

D11 . The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

D12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A or Group AA embodiments.

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

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

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

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

D17. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

D18. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

D19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A or Group AA embodiments.

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

D21 . The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

D22. The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

D23. 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 or Group BB embodiments.

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

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

D26. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

D27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A or Group AA embodiments.

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

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

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). 5GC or 5GCN 5G core network ACK Acknowledgement AGC Automatic Gain Control AM Acknowledged Mode AMF Access and Mobility management Function AP Application Protocol AS Access Stratum BSR Buffer Status Report BWP Bandwidth Part C-RNTI Cell Radio Network Temporary Identifier CA Carrier Aggregation CE Control Element CHO Conditional Handover CN Core Network CPA Conditional PSCell Addition CPC Conditional PSCell Change CP Control Plane CPC Conditional PSCell Change CQI Channel Quality Indicator C-RNTI Cell Radio Network Temporary Identifier CSI Channel State Information DAPS Dual Active Protocol Stack DC Dual Connectivity DCI Downlink Control Information DL Downlink DRB Data Radio Bearer DRX Discontinuous Reception eNB (ELITRAN) base station E-RAB ELITRAN Radio Access Bearer E-UTRA Evolved Universal Terrestrial Radio Access E-UTRAN Evolved Universal Terrestrial Radio Access Network FDD Frequency Division Duplex gNB NR base station GTP-U GPRS Tunneling Protocol - User Plane HO Handover IE Information Element IP Internet Protocol LTE Long Term Evolution MCG Master Cell Group MAC Medium Access Control MAC CE MAC Control Element MeNB Master eNB MgNB Master gNB MN Master Node MR-DC Multi-Radio Dual Connectivity MSG1 Message 1 MSG3 Message 3 MSGA Message A MSGB Message B NACK Negative Acknowledgement NAS Non Access Stratum NG-RAN Next Generation Radio Access Network Ng-eNB Next Generation Evolved Node B NR New Radio PDCP Packet Data Convergence Protocol PCell Primary Cell PCI Physical Cell Identity PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PDU Protocol Data Unit PRACH Physical Random Access Channel PSCell Primary Secondary Cell (in LTE) or Primary SCG Cell (in NR) PUCCH Physical Uplink Control Channel PUSCH Phyical Uplink Shared Channel QoS Quality of Service RA Random Access RACH Random Access Channel RAT Radio Access Technology RB Radio Bearer RLC Radio Link Control RLF Radio Link Failure ROHC Robust Header Compression RRC Radio Resource Control RSRP Reference Signal Received Power SCell Secondary Cell SCG Secondary Cell Group SCTP Stream Control Transmission Protocol SeNB Secondary eNB SgNB Secondary gNB SINR Signal to Interference plus Noise Ratio SN Secondary Node SR Scheduling Request SRB Signaling Radio Bearer S-SN Source Secondary Node SUL Supplementary uplink TAG Timing Advance Group TDD Time Division Duplex TEID Tunnel Endpoint IDentifier TNL Transport Network Layer T-SN Target Secondary Node UCI Uplink Control Information UDP User Datagram Protocol UPF User Plane Function UE User Equipment UL Uplink UP User Plane URLLC Ultra Reliable Low Latency Communication X2 Interface between base stations 1x RTT CDMA2000 1x Radio Transmission Technology 3GPP 3rd Generation Partnership Project 5G 5th Generation ABS Almost Blank Subframe ARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CC Carrier Component CCCH SDU Common Control Channel SDU CDMA Code Division Multiplexing Access CGI Cell Global Identifier CIR Channel Impulse Response CP Cyclic Prefix CPICH Common Pilot Channel CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information C-RNTI Cell RNTI CSI Channel State Information DCCH Dedicated Control Channel DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell-ID (positioning method) E-SMLC Evolved-Serving Mobile Location Centre ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel E-SMLC evolved Serving Mobile Location Center E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FFS For Further Study GE RAN GSM EDGE Radio Access Network gNB Base station in NR GNSS Global Navigation Satellite System GSM Global System for Mobile communication HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term Evolution MAC Medium Access Control MBMS Multimedia Broadcast Multicast Services MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDP Profile Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid-ARQ Indicator Channel PLMN Public Land Mobile Network PMI Precoder Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS Primary Synchronization Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS Reference Signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power OR

Reference Signal Received Power

RSRQ Reference Signal Received Quality OR

Reference Symbol Received Quality

RSSI Received Signal Strength Indicator RSTD Reference Signal Time Difference SCH Synchronization Channel SCell Secondary Cell SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self Optimized Network SS Synchronization Signal SSS Secondary Synchronization Signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Time of Arrival TSS Tertiary Synchronization Signal TTI Transmission Time Interval UE User Equipment UL Uplink UMTS Universal Mobile Telecommunication System USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA Wide CDMA WLAN Wide Local Area Network