WO2023153978A1

WO2023153978A1 - Ue history information (uhi) and mobility history information (mhi) during scg activation/deactivation

Info

Publication number: WO2023153978A1
Application number: PCT/SE2023/050079
Authority: WO
Inventors: Gautham NAYAK SEETANADI; Pradeepa Ramachandra; Julien Muller
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-02-11
Filing date: 2023-01-30
Publication date: 2023-08-17

Abstract

Methods for collecting wireless device history information in dual-connectivity scenarios. An example method, in a wireless device, comprises determining (210) that a secondary cell or secondary cell group configured for the wireless device is deactivated; and in response to said determining, logging (220) certain wireless device history information corresponding to the secondary cell or secondary cell group. The logged wireless device history information may comprise one or more parameters relating to the deactivation. Other example methods include similar methods relating to activation of the secondary cell or secondary cell group, as well as to corresponding methods carried out by network nodes.

Description

UE HISTORY INFORMATION (UHI) AND MOBILITY HISTORY INFORMATION (MHI) DURING SCG ACTIVATION/DEACTIVATION

TECHNICAL FIELD

The present application is related to wireless communication networks and is more particularly related to the collection and reporting of history information for wireless devices operating in such networks.

BACKGROUND

Procedures for the collection of user equipment history information (UHI) were introduced in 3GPP specifications for LTE and have been adopted in the specifications for NR. According to these procedures, a source Radio Access Network (RAN) node collects and stores UE history information for the duration of when a UE is connected and stays in one of its cells.

The UHI collected by the RAN node varies depending upon whether it is NR or LTE, but there are similarities. The UHI includes a cell identifier of the serving primary cell (PCell - the primary cell of the master cell group, or MCG), the time the UE stayed in the cell, and the Handover (HO) cause. The maximum number of cells in UHI for a given UE is capped at 16 entries.

The procedural text related to accumulation of UHI by a concerned NG-RAN node is found in Section 15.5.4 of 3GPP TS 38.300, and the corresponding ASN.l can be found in the information element (IE) UE History Information in section 9.3.1.95 of 3GPP TS 38.413.

The procedural text related to accumulation of UHI by a concerned eNB node is found in Section 16.2.2.1 of 3GPP TS 36.300, and the corresponding ASN.l can be found in the IE UE History Information in section 9.2.1.42 of 3GPP TS 36.413.

Procedures for the collection of mobility history information (MHI) have been introduced in LTE and adopted in NR as well. MHI measurements are accumulated by the UE, independent of its Radio Resource Control (RRC) state, i.e., independently of whether the UE is in Idle, Inactive, or Connected. As part of the MHI, the UE stores the cell identifier for the current serving cell for this UE, as well as information related to how long the UE has stayed in this cell. The UE keeps such a history for up to the past 16 serving cells. The UE also includes information related to how long it has been in an out- of-coverage scenario as well. The procedural text related to the UE's accumulation of the MHI information is in section 5.7.9 of 3GPP TS 38.331 specification and the corresponding ASN.l can be found in the IE VisitedCell InfoList in section 6.3.4 of 3GPP TS 38.331.

Further, the UE can indicate the availability of this mobility history via the field mobilityHistoryAvail in either RRCSetupComplete or RRCResumeComplete messages.

Based on the MHI reported by the UE, the network can estimate UE mobility characteristics such as UE speed.

It is important to note that UHI differs from MHI. MHI is collected by the UE and then transferred to the network and UHI is collected by the concerned network nodes.

Multi-Radio Dual Connectivity (MR-DC) is 3GPP terminology for the scenario where a UE capable of connecting to multiple nodes utilizes the multiple resources to increase throughput, as described in 3GPP TS 37.340. This is a generalization of the intra-E-UTRA Dual connectivity described in 3GPP TS 36.300.

When a UE is in dual connectivity (DC) mode, one RAN node acts as the Master node (MN) and the other RAN node acts as a Secondary node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network. Details on MR-DC can be found in 3GPP TS 38.401. The group of cells that serve a UE configured by the MN is called the master cell group (MCG), and the cell group configured by the SN is called the secondary cell group (SCG). The primary cell in MCG is known as the PCell, and the primary cell in SCG is known as PSCell.

In ongoing RAN3 discussions, it is agreed that the MN should collect UHI related to the PCell. Similarly, the SN should collect UHI related to the PSCell. Also in the discussions, the SN UHI is transferred to the MN and then correlated at the MN. The correlated complete UHI comprises a nested structure, where the SN UHI is listed under the relevant MN UHI. So, a complete UHI structure for a UE comprises a list of PCell information and associated PSCell information, which is listed under the relevant PCell information.

In Release 17 of the 3GPP specifications, current agreements allow for activation or deactivation of the SCG. This enables UE battery consumption reduction, while allowing fast SCG activation when required. During the period when the SCG is deactivated, there is no transmission via SCG RLC bearers. The UE will also not transmit the Physical Uplink Channel (PUSCH) or Sounding Reference Signals (SRS) on SCG, and the UE is not required to monitor the Physical Downlink Control Channel (PDCCH) on SCG. If configured by the network, the UE performs radio link monitor and beam failure detection while SCG is deactivated. In the event of SCG activation without performing random access, the network can indicate Transmission Configuration Indicator (TCI) states to the UE for PDCCH/PDSCH reception on PSCell; if not provided, the UE uses the previously activated TCI states.

The MN can configure the SCG as activated or deactivated upon PSCell addition, PSCell change, RRC Resume or handover. In case the SCG is configured as deactivated, the UE does not perform random access towards the PSCell. The network can trigger SCG RRC reconfiguration (e.g., PSCell change, configuration update) when deactivating the SCG and while the SCG is in deactivated state.

SCG activation can be requested by the MN, by the SN and by the UE. SCG deactivation can be requested by the MN and by the SN. For uplink data arrival on SCG bearer(s) while the SCG is deactivated, the UE indicates to the MN that it has uplink data to transmit over SCG bearer. During handover procedure, the target MN indicates the SCG state in the RRC reconfiguration message sent to the UE by the source MN.

SUMMARY

There currently exist certain challenges. The possibility of activation and deactivation of SCG creates a special situation for the UE, where the UE has an active connection to the SN but the SCG is deactivated (no radio resources are used for the SN connection). There are currently no solutions for how to handle the logging of UE history information or Mobility history information during activation and deactivation of SCG Cells. If the network node is using UHI or MHI for mobility and/or traffic optimization, it will lose valuable information and may take the wrong decision.

Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The techniques provided herein provide for accurate recording of MHI and UHI during scenarios when the SCG is activated/deactivated without SN Release. According to various embodiments of the techniques described in detail below, the MHI and/or UHI may be updated according to one or more of the following:

1) If the SCG is deactivated, then the MHI/UHI for the deactivated duration is logged in the same way as the 'time without PSCell,' i.e., without any explicit indication that the SCG was deactivated.

2) If the SCG is deactivated, then the MHI/UHI for the deactivated duration is logged in the MHI/UHI as a new entry under the current PSCell as the time of deactivated stay in that PSCell. Here, each instance of deactivation would create a new entry under the PSCell MHI/UHI. So, if the UE experiences three SCG deactivations during its time of stay in the PSCell, then the MHI/UHI would include three different entries to indicate how long these individual deactivation durations were.

3) If the SCG is activated, then the MHI/UHI for the activated duration is logged in the same way as the 'time of stay in the PSCell,' i.e., without any explicit indication that the SCG was activated.

4) If the SCG is activated, then the MHI/UHI for the deactivated duration is logged in the MHI/UHI as a new entry under the current PSCell as the time of deactivated stay in that PSCell. Here, each instance of activation would create a new entry under the PSCell MHI/UHI. So, if a UE experiences four SCG activations during its time of stay in the PSCell, then the MHI/UHI would consist of four different entries to indicate how long these individual activation durations were.

5) The MHI/UHI associated to a PSCell comprises a total number of activation and/or total number of deactivations in that PSCell.

6) The MHI/UHI associated to a PSCell comprises a total accumulated duration of activation and/or total accumulated duration of deactivation in that PSCell.

In all of these example embodiments summarized above, the UHI related information is collected by the SN/MN while the MHI related information is collected by the UE.

Embodiments include an example method carried out by a wireless device operating in a wireless network. The example method begins with determining that a secondary cell or secondary cell group configured for the wireless device is deactivated. The method further comprises, in response to this determination, logging certain wireless device history information corresponding to the secondary cell or secondary cell group. Note that the term "wireless device history information," as used here and elsewhere in this document, is meant to be generic with respect to all of the types of mobility history information and UE history information described herein.

This wireless device history information may comprise at least one of (a) an indication of a quantity of deactivations for the secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative deactivation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of an activation period of the secondary cell or secondary cell group ended by deactivation of the secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was deactivated.

Other embodiments include another example of a method carried out by a wireless device operating in a wireless network. This example method comprises determining that a secondary cell or secondary cell group configured for the wireless device is activated. The method further comprises, in response to this determination, logging certain wireless device history information corresponding to the secondary cell or secondary cell group. This wireless device history information may comprise at least one of (a) an indication of a quantity of activations for the secondary cell or secondary cell group, (b) a running indication of an activation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative activation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of a deactivation period of the secondary cell or secondary cell group ended by activation of the secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was activated.

Corresponding embodiments for a network node, e.g., a secondary node (SN) operating in a wireless network, are also detailed below, as are example apparatuses, systems, and variations of these methods and techniques.

Various embodiments of the disclosed techniques provide for the accurate recording of PSCell information either in the UHI or MHI or both, during scenarios involving activation/deactivation of secondary cell group serving a UE.

BRIEF DESCRIPTION OF THE FIGURES

Figure 1 illustrates example steps carried out in various embodiments or instances of the techniques described herein.

Figure 2 and Figure 3 are process flow diagrams illustrating example methods carried out by a wireless device.

Figure 4 and Figure 5 are process flow diagrams illustrating example methods carried out by a network node. Figure 6 illustrates an example communication system.

Figure 7 illustrates an example wireless device.

Figure 8 is a block diagram showing components of an example network node.

Figure 9 shows an example host.

Figure 10 pictures an example virtualization environment.

Figure 11 illustrates a system including a host, network node, and wireless device.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Figure 1 illustrates examples of actions that may be taken by a secondary node (SN) and/or a UE, in various scenarios where the secondary cell or, more generally, a secondary cell group (SCG) operated by the SN for the UE is activated or deactivated. Note that for each row of blocks, one several or all of the blocks may be carried out, in various embodiments or instances.

As shown at step 100a, when a SN addition procedure is performed with respect to a certain UE, the SN may, in some embodiments or instances, initialize and/or start one or more timers as part of UHI for the UE. The timer(s) may correspond to total connection time for the SCG, a total (cumulative) activation time for the SCG, a total (cumulative) deactivation time for the SCG, a current activation duration for the SCG, and/or a current deactivation duration for the SCG, in various embodiments. Similar actions might be taken at SN change or PSCell change procedures.

As shown at step 100b, at SN addition, SN change, or PSCell change, the SN may, in some embodiments or instances, log a number of SCG changes.

Similarly, at the UE end, when a SN addition procedure is performed with respect to the UE, the SN may, in some embodiments or instances, initialize and/or start one or more timers as part of MHI for the UE. Again, the timer(s) may correspond to total connection time for the SCG, a total (cumulative) activation time for the SCG, a total (cumulative) deactivation time for the SCG, a current activation duration for the SCG, and/or a current deactivation duration for the SCG, in various embodiments.

This is shown at step 100c. Similar actions might be taken at SN change or PSCell change procedures. As shown at step lOOd, at SN addition, SN change, or PSCell change, the UE may, in some embodiments or instances, log a number of SCG changes.

As shown at steps 101a and 101b, and 102, the SCG may be deactivated. This may occur at the time of a PSCell addition or PSCell change, in some embodiments or instances. It may occur later, in some embodiments or instances. In various instances, it may be initiated by the network, e.g., by either the MN or SN, or by a request from the UE.

As shown at step 103a, responsive to the deactivation, the UE collects certain MHI. Likewise, as shown at step 103b, the SN may collect certain SN UHI when the SCG is deactivated. This MHI and/or UHI may comprise any of the various elements of information described herein, in connection with activation or deactivation.

For instance, with respect to the UE, the collected MHI may comprise any of: an indication of a quantity of deactivations for the secondary cell or SCG, a running indication of a deactivation duration for the secondary cell or SCG starting as of the time of the deactivation, a running indication of a cumulative deactivation duration for the secondary cell or secondary cell group, started or re-started as of the time of the deactivation, an indication of a duration of an activation period of the secondary cell or secondary cell group ended by deactivation of the secondary cell or secondary cell group, an indication of a cumulative activation period of the secondary cell or secondary cell group as of the time of the deactivation, and a binary indication that the secondary cell or secondary cell group was deactivated.

Similarly, with respect to the SN, the collected UHI may comprise any of: an indication of a quantity of deactivations for the secondary cell or secondary cell group, a running indication of a deactivation duration for the secondary cell or secondary cell group, starting as of the time of the deactivation, a running indication of a cumulative deactivation duration for the secondary cell or secondary cell group, started or re-started as of the time of the deactivation, an indication of a duration of an activation period of the secondary cell or secondary cell group ended by deactivation of the secondary cell or secondary cell group, an indication of a cumulative activation period of the secondary cell or secondary cell group as of the time of the deactivation, and a binary indication that the secondary cell or secondary cell group was deactivated.

As shown at steps 104a and 104b, the network may reactivate the SCG for the UE, or the PSCell may change while the SCG is deactivated. In either or both cases, the SN and/or the UE may collect the various types of history information described herein, as shown at steps 105a, 105b, 106a, and 106b. For instance, in the case of reactivation of the same secondary cell or SCG, or of a PSCell change to an activated PSCell, e.g., to a different secondary cell or SCG, the UE may log any of: an indication of a quantity of activations for the same or different secondary cell or secondary cell group; a running indication of an activation duration for the same or different secondary cell or secondary cell group, starting as of the time of the activation or change; a running indication of a cumulative activation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of the activation or change; an indication of a duration of a deactivation period of the same or different secondary cell or secondary cell group ended by activation of the same or different secondary cell or secondary cell group; an indication of a cumulative deactivation period of the same or different secondary cell or secondary cell group as of the time of the activation or change; and a binary indication that the same or different secondary cell or secondary cell group was activated.

Similarly, in the case of reactivation of the same secondary cell or SCG, or of a PSCell change to an activated secondary cell or SCG, e.g., a different secondary cell or SCG, the SN may log any of: an indication of a quantity of activations for the same or different secondary cell or secondary cell group; a running indication of an activation duration for the same or different secondary cell or secondary cell group, starting as of the time of the activation or change; a running indication of a cumulative activation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of the activation or change; an indication of a duration of a deactivation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group; an indication of a cumulative deactivation period of the same or different secondary cell or secondary cell group as of the time of the activation or change; and a binary indication that the same or different secondary cell or secondary cell group was activated.

It should be appreciated that the order of events described above may be varied, in various instances. For example, a deactivation of a secondary cell or secondary cell group may follow an earlier activation of the same or different secondary cell or secondary cell group. Any of the corresponding types of history information may be collected, in response to such deactivation.

A brief summary of several of the steps shown in Figure 1 is given below. This summary is intended to be consistent with the preceding description. To the extent there are any inconsistencies, those inconsistencies should be resolved in favor of a broader, more inclusive reading of which sorts of information may be logged, without ruling out an implementation or embodiment that collects information according to a narrower reading. Step 100a: At SN Addition, if the SCG is added as activated, the SN starts a timer logging the overall activation time of the SCG.

Step 100b: At SN Addition or SN change or PSCell change, the SN starts logging the number of SCG status changes (i.e., number of activations/deactivations).

Step 100c: At SN Addition, if the SCG is added as activated, the UE starts a timer logging the overall activation time of the SCG.

Step lOOd: At SN Addition or SN change or PSCell change, the UE starts logging the number of SCG status changes (i.e., a number of activation/deactivation).

Step lOOe: At SN Addition or SN change or PSCell change, the UE increments the counter(s) associated to the number of SCG activation/deactivation in the current PSCell depending on the SCG activation/deactivation status.

Step 101a: The network decides to deactivate the SCG of a UE. The decision to deactivate the SCG signal can be taken either by the MN, or the SN.

Step 101b: The UE requests the network to deactivate SCG. The UE can request the network to deactivate the SCG by sending a deactivation request to the MN or the SN.

Step 102: The network node deactivates the SCG serving the UE.

Step 103a: The different ways for the UE to collects MHI include the following:

• The UE pauses the timer associated to the overall activation time for this PSCell.

• The UE stops the timer associated to the SCG activation time for the current PSCell and logs an entry in the MHI associated to the PSCell.

• The UE increases the counter associated to the number of SCG deactivation for the current PSCell.

• The UE counts the duration while being deactivated state to be same as time without a PSCell.

Step 103b: The different ways for the network (SN) to collect SN UHI include the following:

• The SN stops the overall activation timer (e.g., as started in step 100a) and keeps its value in memory.

• The SN continues collecting SN UHI and stores it under the current active PSCell with no changes compared to legacy. • The SN collects the SN UHI and stores it with a special flag indicating that the SCG was deactivated.

• The SN stops collecting SN UHI for the PSCell belonging to the deactivated SCG.

Step 104a: The MN activates the SCG.

Step 105a: The different ways for the UE to collect MHI include the following:

• The UE restarts the timer associated to the overall activation time for this PSCell.

• The UE starts the timer associated to the SCG activation time for the current PSCell and logs an entry in the MHI associated to the PSCell.

• The UE increases the counter associated to the number of SCG activation for the current PSCell.

Step 105b: The different ways for the network (SN) to collect SN UHI include the following:

• The SN restarts the overall activation timer (e.g., as originally started at step 100a) at the value previously stored at step 103b.

• The SN collects SN UHI of the previously deactivated SCG and stores it without any change.

• The SN collects SN UHI of the previously deactivated SCG and stores it with a special flag.

• The SN collects SN UHI of the previously deactivated SCG and stores it in a new entry.

Step 104b: The PSCell changes when the SCG is deactivated.

Step 106a: The different ways for the UE to collect MHI include the following:

• The UE stops the timer associated with the current PSCell and starts a new timer associated with the new PSCell.

Step 106b: The different ways for the network (SN) to collect SN UHI include the following:

• The SN stops collecting SN UHI of the deactivated SCG with no changes to legacy, and starts collecting SN UHI of the new PSCell under a new entry.

• The SN stops collecting SN UHI of the deactivated SCG and stores it with a special flag, and starts collecting SN UHI of the new PSCell under a new entry

• The SN discards the SN UHI of the deactivated SCG, and starts collecting SN UHI of the new PSCell under a new entry

Following are examples of possible implementations of certain ones of the steps described above in 3GPP specifications. These should be understood to be non-limiting examples - other implementations are possible. In step 103b - 1, the SN might collect SN UHI and stores it under the current active PSCell with no changes compared to legacy. This could be implemented in 3GPP specifications as follows. begin proposed 3GPP specification excerpts

TS 38.423

8.3 Procedures for Dual Connectivity

8.3.1 S-NG-RAN node Addition Preparation

8.3.1.1 General

The purpose of the S-NG-RAN node Addition Preparation procedure is to request the S-NG-RAN node to allocate resources for dual connectivity operation for a specific UE.

The procedure uses UE-associated signalling.

8.3.1.2 Successful Operation odel

Figure 8.3.1.2-1: S-NG-RAN node Addition Preparation, successful operation

If the deactivate SCG flag is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node shall, if supported, deactivate the SCG and shall, if supported, collect SCG information and continue for as long as the UE stays in the cell.

- _enc| proposed 3GPP specification excerpts -

Step 103b - 2 : In some embodiments or instances, the SN may collect the SN UHI and store it with a special flag indicating that the SCG was deactivated.

Step 105b - 2: In some embodiments or instances, the SN may collect SN UHI of the previously deactivated SCG and store it with a special flag.

Step 106b - 2 : In some embodiments, the SN may stop collecting SN UHI of the deactivated SCG and store it with a special flag, and start collecting SN UHI of the new PSCell under a new entry.

Some or all of these alternatives may be implemented in 3GPP according to the following:

- begin proposed 3GPP specification excerpts - TS 38.413

9.2.3.X Last Visited NG-RAN PSCell Information

The Last Visited NG-RAN PSCell Information contains information on the PSCell used and the time the UE accessed the cell.

end proposed 3GPP specification excerpts

Step 103b - 3 : In some embodiments or instances, the SN may stop collecting SN UHI for the PSCell belonging to the deactivated SCG. begin proposed 3GPP specification excerpts

TS 38.423

8.3 Procedures for Dual Connectivity

8.3.1 S-NG-RAN node Addition Preparation

8.3.1.1 General

The procedure uses UE-associated signalling.

8.3.1.2 Successful Operation

Figure 8.3.1.2-1: S-NG-RAN node Addition Preparation, successful operation If the deactivate SCG flag is included in the S-NODE ADDITION REQUEST message, the S-NG-RAN node does not collect any SCG information.

- _enc| proposed 3GPP specification excerpts -

Step 105b - 3: In some embodiments or instances, the SN may collect SN UHI of the previously deactivated SCG and store it in a new entry.

- begin proposed 3GPP specification excerpts -

TS 38.473

8.3 Procedures for Dual Connectivity

8.3.3.2 Successful Operation

If the activate SCG flag is included in the S-NODE MODIFICATION REQUEST message, the S-NG-RAN node, if supported, start collecting SCG information and continue for as long as the UE stays in the cell.

- _enc| proposed 3GPP specification excerpts -

Step 106b - 3: In some embodiments, the SN may discard the SN UHI of the deactivated SCG, and start collecting SN UHI of the new PSCell under a new entry. Possible implementation of the overall activation timer and the number of SCG status changes in NGAP (TS 38.413) is shown below.

- begin proposed 3GPP specification excerpts -

9.2.3. XI Last Visited NG-RAN PSCell Information

Alternatively, the Overall activation timer IE is a percentage of Time UE Stayed in Cell IE. end proposed 3GPP specification excerpts

In various embodiments or instances, the overall activation timer and the number of SCG status changes, or other history information associated to a secondary cell or SCG are added to the PSCell entry in SN UHI, and signaled by the SN to the MN and as part of SN UHI signaling, or to a target node as part of mobility signaling. In various embodiments or instances, an activation-related timer or deactivation-related timer can be represented by a percentage of the "Time UE stayed in cell" (e.g., 60% for the overall connection to the SN, the SCG was in "activated" state 60% of the time).

In view of the various examples and details provided above, it will be appreciated that Figure 2 is a process flow diagram illustrating an example method, as carried out by a wireless device, such as a UE operating in an LTE or NR radio access network (RAN). This example method and the description that follows is intended to generalize and encompass several of the detailed techniques and wireless device history information described above. Thus, where there are minor inconsistencies in terminology and/or procedure, the following should be interpreted to be as consistent with and inclusive of the preceding examples as possible, without ruling out embodiments or instances that are more limited.

As shown at block 210, the illustrated method begins with determining that a secondary cell or secondary cell group configured for the wireless device is deactivated. As shown at block 220, the method further comprises, in response to this determination, logging certain wireless device history information corresponding to the secondary cell or secondary cell group. Note that the term "wireless device history information," as used here and elsewhere in this document, is meant to be generic with respect to all of the types of mobility history information and UE history information described herein.

In some embodiments, the wireless device history information is mobility history information (UHI) according to specifications for LTE or NR. The method shown in Figure 2, however, may apply to embodiments in other wireless RANs, or with respect to networks that use different names for similar wireless device history information.

In some embodiments, the logging comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information corresponding to a master cell or master cell group configured for the wireless device.

In some instances of a method like that shown in Figure 2, the method may further comprise subsequently determining that the same or a different secondary cell or secondary cell group is activated. This is shown at block 230, with a dashed outline to indicate that this may not be present in all instances or embodiments of the illustrated method. The method may further comprise, in response to this subsequent determination, logging additional wireless device history information corresponding to the activated same or different secondary cell or secondary cell group. This is shown at block 240. The additional wireless device history information may comprise at least one of (a) an indication of a quantity of activations for the same or different secondary cell or secondary cell group, (b) a running indication of an activation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative activation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of a deactivation period of the same or different secondary cell or secondary cell group ended by activation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining, and (f) a binary indication that the same or different secondary cell or secondary cell group was activated.

In some embodiments or instances of the method illustrated in Figure 2, determining that a secondary cell or secondary cell group configured for the wireless device is deactivated comprises determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell (PSCell) addition procedure, PSCell change procedure, Radio Resource Control (RRC) resume procedure, or handover procedure.

In some embodiments or instances, the method may further comprise reporting the logged wireless device history information to the wireless network. This is shown at block 250.

Figure 3 illustrates another example of a method carried out by a wireless device operating in a wireless network. Again, this example method and the description that follows is intended to generalize and encompass several of the detailed techniques and wireless device history information described above. Thus, where there are minor inconsistencies in terminology and/or procedure, the following should be interpreted to be as consistent with and inclusive of the preceding examples as possible, without ruling out embodiments or instances that are more limited.

As shown at block 310, the method comprises determining that a secondary cell or secondary cell group configured for the wireless device is activated. As shown at block 320, the method further comprises, in response to this determination, logging certain wireless device history information corresponding to the secondary cell or secondary cell group. This wireless device history information may comprise at least one of (a) an indication of a quantity of activations for the secondary cell or secondary cell group, (b) a running indication of an activation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative activation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of a deactivation period of the secondary cell or secondary cell group ended by activation of the secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was activated. In some embodiments, the wireless device history information is user equipment history information (UHI) according to specifications for LTE or NR. In some embodiments or instances, the logging comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information corresponding to a master cell or master cell group configured for the wireless device.

As shown at block 330, the method may further comprise subsequently determining that the same or a different secondary cell or secondary cell group is deactivated. As shown at block 340, the method may further comprise, in response to this subsequent determination, logging additional wireless device history information corresponding to the deactivated same or different secondary cell or secondary cell group, the additional wireless device history information comprising at least one of (a) an indication of a quantity of deactivations for the same or different secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative deactivation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of an activation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining, and (f) a binary indication that the same or different secondary cell or secondary cell group was deactivated.

In some embodiments or instances, determining that a secondary cell or secondary cell group configured for the wireless device is activated comprises determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell (PSCell) addition procedure, PSCell change procedure, Radio Resource Control (RRC) resume procedure, or handover procedure.

In some embodiments or instances, the method further comprises reporting the logged wireless device history information to the wireless network. This is shown at block 350.

Figure 4 illustrates an example method as might be implemented in a network node operating in a wireless network and serving a wireless device, e.g., as a secondary node. Yet again, this example method and the description that follows is intended to generalize and encompass several of the detailed techniques and wireless device history information described above. Thus, where there are minor inconsistencies in terminology and/or procedure, the following should be interpreted to be as consistent with and inclusive of the preceding examples as possible, without ruling out embodiments or instances that are more limited.

The method comprises, as shown at block 410, determining that a secondary cell or secondary cell group configured for the wireless device is deactivated for the wireless device or to be deactivated for the wireless device. As shown at block 420, the method further comprises, in response to said determining, logging certain wireless device history information for the wireless device corresponding to the secondary cell or secondary cell group. This wireless device history information may comprise at least one of (a) an indication of a quantity of deactivations for the secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative deactivation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of an activation period of the secondary cell or secondary cell group ended by deactivation of the secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was deactivated.

In various embodiments or instances, the wireless device history information may be user equipment history information (UHI) according to specifications for LTE or NR. However, this method, like the other methods described herein, may be used in a network using different terminology.

In some embodiments or instances, this logging comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information for the wireless device corresponding to a master cell or master cell group configured for the wireless device.

As shown at block 430, the method may, in some instances, further comprise subsequently determining that the same or a different secondary cell or secondary cell group is activated or to be activated for the wireless device. As shown at block 440, the method in these instances may further comprise, in response to this subsequent determination, logging additional wireless device history information for the wireless device, corresponding to the activated same or different secondary cell or secondary cell group. This additional wireless device history information may comprise at least one of (a) an indication of a quantity of activations for the same or different secondary cell or secondary cell group, (b) a running indication of an activation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative activation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of a deactivation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining; and (f) a binary indication that the same or different secondary cell or secondary cell group was activated.

In some embodiments or instances, determining that the secondary cell or secondary cell group configured for the wireless device is deactivated may comprise determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell (PSCell) addition procedure, PSCell change procedure, Radio Resource Control (RRC) resume procedure, or handover procedure.

In some embodiments or instances, the method shown in Figure 4 is carried out by a node operating a primary secondary cell (PSCell) for the wireless device, and the method further comprises sending the wireless device history information to a node operating a primary cell (PCell) for the wireless device, e.g., to the MN for the wireless device. This is shown at block 450.

Figure 5 illustrates another example method carried out by a network node operating in a wireless network and serving a wireless device. Once more, this example method and the description that follows is intended to generalize and encompass several of the detailed techniques and wireless device history information described above. Thus, where there are minor inconsistencies in terminology and/or procedure, the following should be interpreted to be as consistent with and inclusive of the preceding examples as possible, without ruling out embodiments or instances that are more limited.

As shown at block 510, the method includes determining that a secondary cell or secondary cell group configured for the wireless device is activated for the wireless device. As shown at block 520, the method further comprises, in response to this determination, logging wireless device history information for the wireless device, corresponding to the secondary cell or secondary cell group, where the wireless device history information may comprise at least one of (a) an indication of a quantity of activations for the secondary cell or secondary cell group, (b) a running indication of an activation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative activation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of a deactivation period of the secondary cell or secondary cell group ended by activation of the secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the secondary cell or secondary cell group as of the time of said determining; and (f) a binary indication that the secondary cell or secondary cell group was activated.

Again, the wireless device history information may be user equipment history information (UHI) according to specifications for LTE or NR. Likewise, the logging may be performed such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information corresponding to a master cell or master cell group configured for the wireless device.

In some instance, the method may further comprise subsequently determining that the same or a different secondary cell or secondary cell group is deactivated or to be deactivated for the wireless device, as shown at block 530. In these instances, the method may further comprise, in response to this subsequent determination, logging additional wireless device history information for the wireless device, corresponding to the deactivated same or different secondary cell or secondary cell group. This additional wireless device history information may comprise at least one of (a) an indication of a quantity of deactivations for the same or different secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative deactivation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of an activation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining, and (f) a binary indication that the same or different secondary cell or secondary cell group was deactivated.

In some embodiments or instances, determining that a secondary cell or secondary cell group configured for the wireless device is activated comprises determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell (PSCell) addition procedure, PSCell change procedure, Radio Resource Control (RRC) resume procedure, or handover procedure. In some embodiments or instances, the method shown in Figure 6 is carried out by a node operating a primary secondary cell (PSCell) for the wireless device, and the method further comprises sending the wireless device history information to a node operating a primary cell (PCell) for the wireless device, e.g., to the MN for the wireless device. This is shown at block 550.

Figure 6 shows an example of a communication system 700 in accordance with some embodiments. Various embodiments of the techniques described above may be implemented in such a communication system.

In the example, the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a radio access network (RAN), and a core network 606, which includes one or more core network nodes 608. The access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which may be generally referred to as network nodes 610), or any other similar 3^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections.

Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 600 may include any number of wired or wireless networks, network nodes, UEs, 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. The communication system 600 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs 612 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 610 and other communication devices. Similarly, the network nodes 610 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 612 and/or with other network nodes or equipment in the telecommunication network 602 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 602. In the depicted example, the core network 606 connects the network nodes 610 to one or more hosts, such as host 616. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 606 includes one more core network nodes (e.g., core network node 608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 608. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

The host 616 may be under the ownership or control of a service provider other than an operator or provider of the access network 604 and/or the telecommunication network 602, and may be operated by the service provider or on behalf of the service provider. The host 616 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

As a whole, the communication system 600 of Figure 6 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

In some examples, the telecommunication network 602 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 602. For example, the telecommunications network 602 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.

In some examples, the UEs 612 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 604. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, the hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and/or 612d) and network nodes (e.g., network node 610b). In some examples, the hub 614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 614 may be a broadband router enabling access to the core network 606 for the UEs. As another example, the hub 614 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 610, or by executable code, script, process, or other instructions in the hub 614. As another example, the hub 614 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 614 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 614 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

The hub 614 may have a constant/persistent or intermittent connection to the network node 610b. The hub 614 may also allow for a different communication scheme and/or schedule between the hub 614 and UEs (e.g., UE 612c and/or 612d), and between the hub 614 and the core network 606. In other examples, the hub 614 is connected to the core network 606 and/or one or more UEs via a wired connection. Moreover, the hub 614 may be configured to connect to an M2M service provider over the access network 604 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 610 while still connected via the hub 614 via a wired or wireless connection. In some embodiments, the hub 614 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 610b. In other embodiments, the hub 614 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 610b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 7 shows a UE 700 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to- vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a 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).

The UE 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a power source 708, a memory 710, a communication interface 712, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 7. 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.

The processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine- readable computer programs in the memory 710. The processing circuitry 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, 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 702 may include multiple central processing units (CPUs).

In the example, the input/output interface 706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include 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. An input device may allow a user to capture information into the UE 700. Examples of an input device 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, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

In some embodiments, the power source 708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 708 may further include power circuitry for delivering power from the power source 708 itself, and/or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied. The memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716. The memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems.

The memory 710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), 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 tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or IS IM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as 'SIM card.' The memory 710 may allow the UE 700 to access instructions, application programs and 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 as or in the memory 710, which may be or comprise a device-readable storage medium.

The processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 718 and/or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately. In the illustrated embodiment, communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication, LPWAN communication, 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. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), Q.UIC, Hypertext Transfer Protocol (HTTP), and so forth.

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 712, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 700 shown in Figure 7.

As yet another specific example, in an loT scenario, a UE 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 UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone's speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

Figure 8 shows a network node 800 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication 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 so, depending on the provided amount of coverage, may 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).

Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

The network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. The network node 800 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 the network node 800 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 NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) 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 800.

The processing circuitry 802 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 800 components, such as the memory 804, to provide network node 800 functionality.

In some embodiments, the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 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 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.

The memory 804 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 the processing circuitry 802. The memory 804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 802 and utilized by the network node 800. The memory 804 may be used to store any calculations made by the processing circuitry 802 and/or any data received via the communication interface 806. In some embodiments, the processing circuitry 802 and memory 804 is integrated.

The communication interface 806 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 806 comprises port(s)/terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. The communication interface 806 also includes radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810. Radio front-end circuitry 818 comprises filters 820 and amplifiers 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio front-end circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 820 and/or amplifiers 822. The radio signal may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 800 does not include separate radio frontend circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).

The antenna 810 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 810 is separate from the network node 800 and connectable to the network node 800 through an interface or port.

The antenna 810, communication interface 806, and/or the processing circuitry 802 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 810, the communication interface 806, and/or the processing circuitry 802 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein. For example, the network node 800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 808. As a further example, the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of the network node 800 may include additional components beyond those shown in Figure 8 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, the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.

Figure 9 is a block diagram of a host 900, which may be an embodiment of the host 616 of Figure 6, in accordance with various aspects described herein. As used herein, the host 900 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 900 may provide one or more services to one or more UEs.

The host 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a network interface 908, a power source 910, and a memory 912. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 7 and 8, such that the descriptions thereof are generally applicable to the corresponding components of host 900.

The memory 912 may include one or more computer programs including one or more host application programs 914 and data 916, which may include user data, e.g., data generated by a UE for the host 900 or data generated by the host 900 for a UE. Embodiments of the host 900 may utilize only a subset or all of the components shown. The host application programs 914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 914 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 900 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 914 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

Figure 10 is a block diagram illustrating a virtualization environment 1000 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 any device described herein, 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. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1000 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

Applications 1002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q.400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware 1004 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1008a and 1008b (one or more of which may be generally referred to as VMs 1008), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to the VMs 1008.

The VMs 1008 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of VMs 1008, and the implementations may be made in different ways. 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, a VM 1008 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1008, and that part of hardware 1004 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1008 on top of the hardware 1004 and corresponds to the application 1002.

Hardware 1004 may be implemented in a standalone network node with generic or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1010, which, among others, oversees lifecycle management of applications 1002. In some embodiments, hardware 1004 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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 signaling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.

Figure 11 shows a communication diagram of a host 1102 communicating via a network node 1104 with a UE 1106 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 612a of Figure 6 and/or UE 700 of Figure 7), network node (such as network node 610a of Figure 6 and/or network node 800 of Figure 8), and host (such as host 616 of Figure 6 and/or host 900 of Figure 9) discussed in the preceding paragraphs will now be described with reference to Figure 11.

Like host 900, embodiments of host 1102 include hardware, such as a communication interface, processing circuitry, and memory. The host 1102 also includes software, which is stored in or accessible by the host 1102 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1106 connecting via an over-the-top (OTT) connection 1150 extending between the UE 1106 and host 1102. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1150.

The network node 1104 includes hardware enabling it to communicate with the host 1102 and UE 1106. The connection 1160 may be direct or pass through a core network (like core network 606 of Figure 6) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

The UE 1106 includes hardware and software, which is stored in or accessible by UE 1106 and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific "app" that may be operable to provide a service to a human or nonhuman user via UE 1106 with the support of the host 1102. In the host 1102, an executing host application may communicate with the executing client application via the OTT connection 1150 terminating at the UE 1106 and host 1102. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1150 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1150.

The OTT connection 1150 may extend via a connection 1160 between the host 1102 and the network node 1104 and via a wireless connection 1170 between the network node 1104 and the UE 1106 to provide the connection between the host 1102 and the UE 1106. The connection 1160 and wireless connection 1170, over which the OTT connection 1150 may be provided, have been drawn abstractly to illustrate the communication between the host 1102 and the UE 1106 via the network node 1104, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection 1150, in step 1108, the host 1102 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1106. In other embodiments, the user data is associated with a UE 1106 that shares data with the host 1102 without explicit human interaction. In step 1110, the host 1102 initiates a transmission carrying the user data towards the UE 1106. The host 1102 may initiate the transmission responsive to a request transmitted by the UE 1106. The request may be caused by human interaction with the UE 1106 or by operation of the client application executing on the UE 1106. The transmission may pass via the network node 1104, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1112, the network node 1104 transmits to the UE 1106 the user data that was carried in the transmission that the host 1102 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1114, the UE 1106 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1106 associated with the host application executed by the host 1102.

In some examples, the UE 1106 executes a client application which provides user data to the host 1102. The user data may be provided in reaction or response to the data received from the host 1102. Accordingly, in step 1116, the UE 1106 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1106. Regardless of the specific manner in which the user data was provided, the UE 1106 initiates, in step 1118, transmission of the user data towards the host 1102 via the network node 1104. In step 1120, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1104 receives user data from the UE 1106 and initiates transmission of the received user data towards the host 1102. In step 1122, the host 1102 receives the user data carried in the transmission initiated by the UE 1106.

One or more of the various embodiments improve the performance of OTT services provided to the UE 1106 using the OTT connection 1150, in which the wireless connection 1170 forms the last segment. More precisely, the teachings of these embodiments may improve the connection reliability for wireless devices by allowing for better optimization of mobility, thereby providing benefits such as reduced service interruptions and reduction of unnecessary delays.

In an example scenario, factory status information may be collected and analyzed by the host 1102. As another example, the host 1102 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1102 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1102 may store surveillance video uploaded by a UE. As another example, the host 1102 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1102 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, 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 the OTT connection 1150 between the host 1102 and UE 1106, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1102 and/or UE 1106. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1150 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 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1150 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1104. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1102. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 1150 while monitoring propagation times, errors, etc.

Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non- computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

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

EXAMPLE EMBODIMENTS

Embodiments of the presently disclosed techniques, apparatuses, and systems include, but are not limited to, the following enumerated examples:

Group A Embodiments

1. A method, in a wireless device operating in a wireless network, the method comprising: determining that a secondary cell or secondary cell group configured for the wireless device is deactivated; and in response to said determining, logging wireless device history information corresponding to the secondary cell or secondary cell group, the wireless device history information comprising at least one of (a) an indication of a quantity of deactivations for the secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative deactivation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of an activation period of the secondary cell or secondary cell group ended by deactivation of the secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was deactivated.

2. The method of example embodiment 2, wherein the wireless device history information is mobility history information (UHI) according to specifications for LTE or NR.

3. The method of example embodiment 1 or 2, wherein said logging comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information corresponding to a master cell or master cell group configured for the wireless device.

4. The method of any one of example embodiments 1-3, wherein the method further comprises: subsequently determining that the same or a different secondary cell or secondary cell group is activated; and, in response to said subsequently determining, logging additional wireless device history information corresponding to the activated same or different secondary cell or secondary cell group, the additional wireless device history information comprising at least one of (a) an indication of a quantity of activations for the same or different secondary cell or secondary cell group, (b) a running indication of an activation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative activation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of a deactivation period of the same or different secondary cell or secondary cell group ended by activation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining, and (f) a binary indication that the same or different secondary cell or secondary cell group was activated.

5. The method of any one of example embodiments 1-4, wherein said determining that a secondary cell or secondary cell group configured for the wireless device is deactivated comprises determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell (PSCell) addition procedure, PSCell change procedure, Radio Resource Control (RRC) resume procedure, or handover procedure.

6. The method of any one of embodiments 1-5, wherein the method further comprises reporting the logged wireless device history information to the wireless network.

7. A method, in a wireless device operating in a wireless network, the method comprising: determining that a secondary cell or secondary cell group configured for the wireless device is activated; and in response to said determining, logging wireless device history information corresponding to the secondary cell or secondary cell group, the wireless device history information comprising at least one of (a) an indication of a quantity of activations for the secondary cell or secondary cell group, (b) a running indication of an activation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative activation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of a deactivation period of the secondary cell or secondary cell group ended by activation of the secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was activated.

8. The method of example embodiment 7, wherein the wireless device history information is user equipment history information (UHI) according to specifications for LTE or NR.

9. The method of example embodiment 7 or 8, wherein said logging comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information corresponding to a master cell or master cell group configured for the wireless device.

10. The method of any one of example embodiments 7-9, wherein the method further comprises: subsequently determining that the same or a different secondary cell or secondary cell group is deactivated; and, in response to said subsequently determining, logging additional wireless device history information corresponding to the deactivated same or different secondary cell or secondary cell group, the additional wireless device history information comprising at least one of (a) an indication of a quantity of deactivations for the same or different secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative deactivation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of an activation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining, and (f) a binary indication that the same or different secondary cell or secondary cell group was deactivated.

11. The method of any one of example embodiments 7-10, wherein said determining that a secondary cell or secondary cell group configured for the wireless device is activated comprises determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell (PSCell) addition procedure, PSCell change procedure, Radio Resource Control (RRC) resume procedure, or handover procedure.

12. The method of any one of embodiments 7-11, wherein the method further comprises reporting the logged wireless device history information to the wireless network.

13. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

Group B Embodiments

14. A method, in a network node operating in a wireless network and serving a wireless device, the method comprising: determining that a secondary cell or secondary cell group configured for the wireless device is deactivated for the wireless device or to be deactivated for the wireless device, and in response to said determining, logging wireless device history information for the wireless device, corresponding to the secondary cell or secondary cell group, the wireless device history information comprising at least one of (a) an indication of a quantity of deactivations for the secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative deactivation duration for the secondary cell or secondary cell group, started or restarted as of the time of said determining, (d) an indication of a duration of an activation period of the secondary cell or secondary cell group ended by deactivation of the secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was deactivated.

15. The method of example embodiment 14, wherein the wireless device history information is user equipment history information (UHI) according to specifications for LTE or NR.

16. The method of example embodiment 14 or 15, wherein said logging comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information for the wireless device corresponding to a master cell or master cell group configured for the wireless device.

17. The method of any one of example embodiments 14-16, wherein the method further comprises: subsequently determining that the same or a different secondary cell or secondary cell group is activated or to be activated for the wireless device; and, in response to said subsequently determining, logging additional wireless device history information for the wireless device, corresponding to the activated same or different secondary cell or secondary cell group, the additional wireless device history information comprising at least one of (a) an indication of a quantity of activations for the same or different secondary cell or secondary cell group, (b) a running indication of an activation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative activation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of a deactivation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining; and (f) a binary indication that the same or different secondary cell or secondary cell group was activated.

18. The method of any one of example embodiments 14-17, wherein said determining that a secondary cell or secondary cell group configured for the wireless device is deactivated comprises determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell (PSCell) addition procedure, PSCell change procedure, Radio Resource Control (RRC) resume procedure, or handover procedure.

19. The method of any one of example embodiments 14-18, wherein the method is carried out by a node operating a primary secondary cell (PSCell) for the wireless device, and wherein the method further comprises sending the wireless device history information to a node operating a primary cell (PCell) for the wireless device.

20. A method, in a network node operating in a wireless network and serving a wireless device, the method comprising: determining that a secondary cell or secondary cell group configured for the wireless device is activated for the wireless device; and in response to said determining, logging wireless device history information for the wireless device, corresponding to the secondary cell or secondary cell group, the wireless device history information comprising at least one of (a) an indication of a quantity of activations for the secondary cell or secondary cell group, (b) a running indication of an activation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative activation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of a deactivation period of the secondary cell or secondary cell group ended by activation of the secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the secondary cell or secondary cell group as of the time of said determining; and (f) a binary indication that the secondary cell or secondary cell group was activated.

21. The method of example embodiment 20, wherein the wireless device history information is user equipment history information (UHI) according to specifications for LTE or NR.

22. The method of example embodiment 20 or 21, wherein said logging comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information corresponding to a master cell or master cell group configured for the wireless device.

23. The method of any one of example embodiments 20-22, wherein the method further comprises: subsequently determining that the same or a different secondary cell or secondary cell group is deactivated or to be deactivated for the wireless device; and, in response to said subsequently determining, logging additional wireless device history information for the wireless device, corresponding to the deactivated same or different secondary cell or secondary cell group, the additional wireless device history information comprising at least one of (a) an indication of a quantity of deactivations for the same or different secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative deactivation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of an activation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining, and (f) a binary indication that the same or different secondary cell or secondary cell group was deactivated. 24. The method of any one of example embodiments 20-23, wherein said determining that a secondary cell or secondary cell group configured for the wireless device is activated comprises determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell (PSCell) addition procedure, PSCell change procedure, Radio Resource Control (RRC) resume procedure, or handover procedure.

25. The method of any one of embodiments 20-24, wherein the method is carried out by a node operating a primary secondary cell (PSCell) for the wireless device, and wherein the method further comprises sending the wireless device history information to a node operating a primary cell (PCell) for the wireless device.

Group C Embodiments

26. A user equipment, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

27. A network node, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

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

29. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.

30. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

31. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

32. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

33. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

34. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

35. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.

36. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

37. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

38. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

39. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. 40. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

41. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

42. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

43. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

44. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

45. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application. 46. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

47. The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.

48. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.

49. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

50. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data. 51. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.

52. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

Claims

CLAIMS What is claimed is:

1. A method, in a wireless device operating in a wireless network, the method comprising: determining (210) that a secondary cell or secondary cell group configured for the wireless device is deactivated; and in response to said determining, logging (220) wireless device history information corresponding to the secondary cell or secondary cell group, the wireless device history information comprising at least one of (a) an indication of a quantity of deactivations for the secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative deactivation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of an activation period of the secondary cell or secondary cell group ended by deactivation of the secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was deactivated.

2. The method of claim 2, wherein the wireless device history information is mobility history information, MHI, according to specifications for LTE or NR.

3. The method of claim 1 or 2, wherein said logging (220) comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information corresponding to a master cell or master cell group configured for the wireless device.

4. The method of any one of claims 1-3, wherein the method further comprises: subsequently determining (230) that the same or a different secondary cell or secondary cell group is activated; and, in response to said subsequently determining, logging (240) additional wireless device history information corresponding to the activated same or different secondary cell or secondary cell group, the additional wireless device history information comprising at least one of (a) an indication of a quantity of activations for the same or different secondary cell or secondary cell group, (b) a running indication of an activation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative deactivation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of a deactivation period of the same or different secondary cell or secondary cell group ended by activation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining, and (f) a binary indication that the same or different secondary cell or secondary cell group was activated.

5. The method of any one of claims 1-4, wherein said determining (210) that a secondary cell or secondary cell group configured for the wireless device is deactivated comprises determining an activation status for the secondary cell or secondary cell group as part of a secondary node addition procedure, secondary node change procedure, Radio Resource Control, RRC, resume procedure, or handover procedure.

6. The method of any one of claims 1-5, wherein the method further comprises reporting (250) the logged wireless device history information to the wireless network.

7. A method, in a wireless device operating in a wireless network, the method comprising: determining (310) that a secondary cell or secondary cell group configured for the wireless device is activated after previously having been deactivated; and in response to said determining, logging (320) wireless device history information corresponding to the secondary cell or secondary cell group, the wireless device history information comprising at least one of (a) an indication of a quantity of activations for the secondary cell or secondary cell group, (b) a running indication of an activation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative activation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of a deactivation period of the secondary cell or secondary cell group ended by activation of the secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was activated.

8. The method of claim 7, wherein the wireless device history information is mobility history information, MHI, according to specifications for LTE or NR.

9. The method of claim 7 or 8, wherein said logging (320) comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information corresponding to a master cell or master cell group configured for the wireless device.

10. The method of any one of claims 7-9, wherein the method further comprises: subsequently determining (330) that the same or a different secondary cell or secondary cell group is deactivated; and, in response to said subsequently determining, logging (340) additional wireless device history information corresponding to the deactivated same or different secondary cell or secondary cell group, the additional wireless device history information comprising at least one of (a) an indication of a quantity of deactivations for the same or different secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative deactivation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of an activation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining, and (f) a binary indication that the same or different secondary cell or secondary cell group was deactivated.

11. The method of any one of claims 7-10, wherein said determining (310) that a secondary cell or secondary cell group configured for the wireless device is activated comprises determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell, PSCell, addition procedure, PSCell change procedure, Radio Resource Control, RRC, resume procedure, or handover procedure.

12. The method of any one of claims 7-11, wherein the method further comprises reporting (350) the logged wireless device history information to the wireless network.

13. A method, in a network node operating in a wireless network and serving a wireless device, the method comprising: determining (410) that a secondary cell or secondary cell group configured for the wireless device is deactivated for the wireless device or to be deactivated for the wireless device, and in response to said determining, logging (420) wireless device history information for the wireless device, corresponding to the secondary cell or secondary cell group, the wireless device history information comprising at least one of (a) an indication of a quantity of deactivations for the secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative deactivation duration for the secondary cell or secondary cell group, started or re-started as of the time of said determining, (d) an indication of a duration of an activation period of the secondary cell or secondary cell group ended by deactivation of the secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the secondary cell or secondary cell group as of the time of said determining, and (f) a binary indication that the secondary cell or secondary cell group was deactivated.

14. The method of claim 13, wherein the wireless device history information is user equipment history information, UHI, according to specifications for LTE or NR.

15. The method of claim 13 or 14, wherein said logging (420) comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information for the wireless device corresponding to a master cell or master cell group configured for the wireless device.

16. The method of any one of claims 13-15, wherein the method further comprises: subsequently determining (430) that the same or a different secondary cell or secondary cell group is activated or to be activated for the wireless device; and, in response to said subsequently determining, logging (440) additional wireless device history information for the wireless device, corresponding to the activated same or different secondary cell or secondary cell group, the additional wireless device history information comprising at least one of (a) an indication of a quantity of activations for the same or different secondary cell or secondary cell group, (b) a running indication of an activation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative activation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of a deactivation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining; and (f) a binary indication that the same or different secondary cell or secondary cell group was activated.

17. The method of any one of claims 13-16, wherein said determining (410) that a secondary cell or secondary cell group configured for the wireless device is deactivated comprises determining an activation status for the secondary cell or secondary cell group as part of a primary secondary cell, PSCell, addition procedure, PSCell change procedure, Radio Resource Control, RRC, resume procedure, or handover procedure.

18. The method of any one of claims 13-17, wherein the method is carried out by a node operating a primary secondary cell, PSCell, for the wireless device, and wherein the method further comprises sending (450) the wireless device history information to a node operating a primary cell, PCell, for the wireless device.

19. A method, in a network node operating in a wireless network and serving a wireless device, the method comprising: determining (510) that a secondary cell or secondary cell group configured for the wireless device is activated for the wireless device after previously having been deactivated; and in response to said determining, logging (520) wireless device history information for the wireless device, corresponding to the secondary cell or secondary cell group, the wireless device history information comprising at least one of (a) an indication of a quantity of activations for the secondary cell or secondary cell group, (b) a running indication of an activation duration for the secondary cell or secondary cell group, starting as of the time of said determining, (c) a running indication of a cumulative activation duration for the secondary cell or secondary cell group, started or restarted as of the time of said determining, (d) an indication of a duration of a deactivation period of the secondary cell or secondary cell group ended by activation of the secondary cell or secondary cell group, (e) an indication of a cumulative deactivation period of the secondary cell or secondary cell group as of the time of said determining; and (f) a binary indication that the secondary cell or secondary cell group was activated.

20. The method of claim 19, wherein the wireless device history information is user equipment history information, UHI, according to specifications for LTE or NR.

21. The method of claim 19 or 20, wherein said logging (520) comprises logging the wireless device history information corresponding to the secondary cell or secondary cell group such that the logging indicates an association of the wireless device history information corresponding to the secondary cell or secondary cell group with wireless device history information corresponding to a master cell or master cell group configured for the wireless device.

22. The method of any one of claims 19-21, wherein the method further comprises: subsequently determining (530) that the same or a different secondary cell or secondary cell group is deactivated or to be deactivated for the wireless device; and, in response to said subsequently determining, logging (540) additional wireless device history information for the wireless device, corresponding to the deactivated same or different secondary cell or secondary cell group, the additional wireless device history information comprising at least one of (a) an indication of a quantity of deactivations for the same or different secondary cell or secondary cell group, (b) a running indication of a deactivation duration for the same or different secondary cell or secondary cell group, starting as of the time of said subsequently determining, (c) a running indication of a cumulative deactivation duration for the same or different secondary cell or secondary cell group, started or re-started as of the time of said subsequently determining, (d) an indication of a duration of an activation period of the same or different secondary cell or secondary cell group ended by deactivation of the same or different secondary cell or secondary cell group, (e) an indication of a cumulative activation period of the same or different secondary cell or secondary cell group as of the time of said subsequently determining, and (f) a binary indication that the same or different secondary cell or secondary cell group was deactivated.

23. The method of any one of claims 19-22, wherein said determining (510) that a secondary cell or secondary cell group configured for the wireless device is activated comprises determining an activation status for the secondary cell or secondary cell group as part of a secondary node addition procedure, secondary node change procedure, Radio Resource Control, RRC, resume procedure, or handover procedure.

24. The method of any one of claims 19-23, wherein the method is carried out by a node operating a primary secondary cell, PSCell, for the wireless device, and wherein the method further comprises sending (550) the wireless device history information to a node operating a primary cell, PCell, for the wireless device.

25. A user equipment, UE, (700), the UE (700) comprising: radio circuitry (718, 720) configured to communicate with one or more network nodes; and processing circuitry (702) operatively coupled to the radio circuitry (718, 720) and configured to carry out a method according to any one of claims 1-12.

26. A user equipment, UE, (700) adapted to carry out a method according to any one of claims 1-12.

27. A network node (800), the network node (800) comprising: radio circuitry (818) configured to communicate with one or more user equipments, UEs; and processing circuitry (802) operatively coupled to the radio circuitry (818) and configured to carry out a method according to any one of claims 13-24.

28. A network node (800) adapted to carry out a method according to any one of claims 13-24.

29. A computer program product comprising program instructions for execution by processing circuitry in a user equipment, UE, the program instructions being configured to cause the UE to carry out a method according to any one of claims 1-12.

30. A computer program product comprising program instructions for execution by processing circuitry in a network node, the program instructions being configured to cause the network node to carry out a method according to any one of claims 13-24.

31. A computer-readable medium comprising, stored thereupon, a computer program product according to claim 29 or 30.