WO2023121533A1

WO2023121533A1 - Logging and reporting of high-speed dedicated network (hsdn) properties

Info

Publication number: WO2023121533A1
Application number: PCT/SE2022/051136
Authority: WO
Inventors: Mattias BERGSTRÖM; Pradeepa Ramachandra
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2021-12-20
Filing date: 2022-12-02
Publication date: 2023-06-29

Abstract

One example of a method according to an embodiment of the invention comprises a method in a wireless device operating in a wireless network. The method comprises determining (110) whether the wireless device is in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available. The method further comprises logging (120) information indicating whether the wireless device is in the high-speed state.

Description

LOGGING AND REPORTING OF HIGH-SPEED DEDICATED

NETWORK (HSDN) PROPERTIES

TECHNICAL FIELD

This document is generally directed to wireless communications and is more directly related to the configuration and use of high-speed-dedicated network cells in wireless communication networks.

BACKGROUND

The high-speed dedicated network (HSDN) is a feature allowing an operator to define cells to be so- called high-speed cells, in comparison to normal cells (i.e., non-high-speed cells). The feature also comprises that UEs will determine their speed. A UE may consider itself to be a high-speed UE or a normal UE (i.e., a non-high-speed UE).

A UE which considers itself to be a high-speed UE would give priority to high-speed cells in the sense that if the UE finds both a high-speed cell and a normal cell, the UE gives the high-speed cell the highest priority when selecting or reselecting cells. A non-high-speed UE, on the other hand, would give the highest priority to non-high-speed cells. A high-speed UE that only finds normal cells would anyway select those normal speed cells, as there is no other option available for the UE.

This feature could for example be used in a high-speed train scenario where there are network cells deployed along a train track, which are meant to provide an increased capacity for UEs traveling in the trains.

To ensure that the cells along the train-track have spare capacity to provide service to the UEs in trains, the feature ensures that potential non-high-speed UEs (e.g., one carried by a person walking along the train tracks), would not select the cells if there are non-high-speed cells that can be selected.

The feature has been implemented in the LTE and NR specifications, where the network can configure the UEs in the cell to operate in a more suitable mode if the UEs are traveling at high speed. These features include, for example, the high-speed measurement feature and high-speed demodulation feature as configured by these parameters in 3GPP TS 38.331 version 16.6.0:

- begin 3GPP excerpt -

HighSpeedConfig-rl 6 : : = SEQUENCE { highSpeedMeas Flag-r! 6 ENUMERATED { true } OPTIONAL, — Need R highSpeedDemodFlag-r! 6 ENUMERATED { true } OPTIONAL, — Need R

} j

end 3GPP excerpt

SUMMARY

For the network operator to know where high-speed cells should be deployed, the operator may need to know where there are high-speed UEs. For example, the operator may have deployed one or more high-speed cells close to a train track, but the deployment of these may not be perfect, meaning that the high-speed cells may not perfectly cover the UEs traveling at high speed. The resources that these cells provide may therefore be wasted. Note that high-speed cells will only be prioritized by high-speed UEs but not by normal-speed UEs. If the high-speed cell is not deployed to cover an area where high-speed UEs are, there may be no UEs that connect to these cells.

Also, the operator may experience a high number of failures in the network, such as radio link failure (RLF) or random access failures. This may be due to UEs moving at a high speed in a certain area, but where the operator has not enabled features suitable for UEs moving at high speed. The operator may have no means to detect that the cause for the failures are that UEs move at a high speed. Hence the issues may remain unsolved.

In various embodiments of the techniques, apparatuses, and systems described herein, the above problems are addressed by having wireless devices each log and report: whether a wireless device is in a state where the wireless device is supposed to prioritize, for selection or re-selection, cells indicated as high-speed cells, and/or whether the cell that the wireless device is associated with is a cell indicated as a high-speed cell, and/or whether the cell that the wireless device is associated with has enabled features related to high-speed moving wireless devices. An example method, according to some of the disclosed techniques in a wireless device operating in a wireless network, comprises determining whether the wireless device is in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available. The method further comprises logging information indicating whether the wireless device is in the highspeed state.

Another example method, according to some of the disclosed techniques in a wireless device operating in a wireless network, comprises determining whether the wireless device is in a highspeed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available, and/or determining whether the wireless device is in a cell designated as a highspeed cell. The method further comprises logging information indicating whether the wireless device is in the high-speed state and/or whether the wireless device is in a cell designated as a high-speed cell and/or an indication of each of one or more features specific to high-speed status enabled in a cell. The method may further comprise reporting some or all of the above information to the wireless network, for use by the wireless network in optimizing performance of a high-speed- dedicated network.

Another example method is carried out by a network node operating in or in association with a wireless network, and comprises receiving a report from each of a plurality of wireless devices operating in the wireless network, each report comprising one or more of any one of: (a) an indication of whether the respective wireless device, at the time information in the report was logged, was in a high-speed state, wherein the high-speed state is such that a wireless device in highspeed state prioritizes cells designated as high-speed cells for selection and/or re-selection, when available, (b) an indication of whether a cell the respective wireless device was in at the time information in the report was logged was designated as a high-speed cell, (c) an indication of which of one or more features specific to high-speed status were enabled in a cell at the time information in the report is logged. This example method further comprises modifying one or more operational parameters in the wireless network, based on the reports. Modifying one or more operational parameters may comprise changing a high-speed designation for at least one cell in the wireless network, for example, or enabling or disabling one or more high-speed related features for at least one cell in the wireless network, in various embodiments.

As described below, these and other similar techniques and their corresponding apparatuses and systems may be used to allow an operator to gather information about whether UEs are in a state where they are supposed to prioritize selecting cells indicated as high-speed cells and whether the cell that the UE is associated to is a, so called, high-speed cell and also whether certain features suitable for high-speed scenarios are enabled in the cell. This information would allow the operator to modify its deployment to avoid failures, e.g., avoid that UEs experience radio link failures, random access failures, etc.

Further, the proposed solutions of the invention enable the operator to identify the reason for certain type of failures like radio link failures. For example, a UE moving from a cell classified as highspeed cell to a cell classified as non-high-speed cell could experience handover failure and the handover parameters to optimize for such a failure could include enabling/disabling certain highspeed status specific features in the source cell or in the target cell. With the help of the proposed solutions of the invention, such a high-speed status specific optimization for handover parameters is possible.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a process flow diagram illustrating an example method in a wireless device.

Figure 2 is a process flow diagram illustrating an example method in a network node.

Figure 3 shows an example of a communication system in accordance with some embodiments.

Figure 4 shows a wireless device in accordance with some embodiments.

Figure 5 shows a network node in accordance with some embodiments.

Figure 6 is a block diagram of a host.

Figure 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

Figure 8 shows a communication diagram of a host communicating via a network node with a wireless device over a partially wireless connection in accordance with some embodiments.

DETAILED DESCRIPTION

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

In this document, the term "high-speed cell" will herein be used to refer cells that are indicated to be cells which UEs moving at high speed shall prioritize selecting or re-selecting. The term "highspeed UE" will herein be used to refer to UEs that are moving in such a manner that they enter a state, or operating mode, wherein it should prioritize high-speed cells for selection or re-selection.

The term "high-speed features" refers to features that the UE can apply to ensure that the communication between the UE and network is more reliable in scenarios when the UE is moving at a high speed (relative to the network node). These features may put stricter requirements on the UE and may waste the power of the UE, in some cases, thus, it will be generally expected that it is desirable for a UE to avoid using these features except when actually in a high-speed state.

Other terms used herein include:

• Previous PCell : The cell identifier included in the RLF report (previousPCellld in TS 38.331 V16.6.0) in which the UE received the last executed RRCReconfiguration message including reconfigurationWithSync. Refer to the field description of previousPCellld in TS 38.331 V16.6.0.

• Failed PCell: The cell identifier included in the RLF report (failedPCellld in TS 38.331 V16.6.0) in which the UE declares radio link failure or the handover failure. Refer to the field description of failedPCellld in TS 38.331 V16.6.0.

• Reestablishment PCell: The cell identifier included in the RLF report (reestablishmentCellld in TS 38.331 V16.6.0) in which the performs the reestablishment procedure after declaring radio link failure or handover failure. Refer to the field description of reestablishmentCellld in TS 38.331 vl6.6.0.

• Reconnect PCell: The cell identifier included in the RLF report (reconnectCellld in TS 38.331 V16.6.0) in which the performs the re-connection after declaring radio link failure or handover failure and failing to perform reestablishment. Refer to the field description of reconnectCellld in TS 38.331 V16.6.0.

• Previous PSCell: The cell identifier included in the SCGFailurelnformation in which the UE received the last executed RRCReconfiguration message including reconfigurationWithSync associated to the SCG.

• Failed PSCell: The cell identifier included in the SCGFailurelnformation in which the UE declares SCG radio link failure or the PSCell change failure.

Note that several of the above terms are defined in the context of 3GPP specifications for NR and/or LTE wireless systems. These terms should be understood as referring to directly corresponding features or items in future versions of these standards as well as in other wireless systems, even if different names are assigned to the features or things.

In some embodiments of the techniques described here, the UE determines that a certain event has occurred. This event may be referred to as a trigger event or triggering event, for example.

The UE will determine whether, when the event occurred, the UE was in a state where the UE should prioritize high-speed cells or not. The UE logs this information so that the information can later be reported to the network.

This information may be useful to receive for the operator of the network, as the operator may determine that if there are many UEs (e.g., more UEs than a threshold or a larger percentage of all UEs) that are high-speed UEs in a system, or a part of a system, it may be beneficial to deploy cells that are suitable for high-speed UEs. If there are fewer high-speed UEs in a system or part of a system, it may not be beneficial to deploy high-speed cells as these cells may not be utilized by non-high-speed UEs. Note that deploying cells that are suitable for high-speed UEs may comprise configuring one or more cells to identify themselves as high-speed cells or not, depending on the circumstances, and/or may comprise enabling one or more features that are specific to high-speed operation.

In some embodiments the UE may determine that a certain event, or trigger event or triggering event, has occurred. This may or may not be the same event discussed above. The UE in these embodiments will determine whether, when the event occurred, the cell that the UE was associated to was a cell indicated to be for UEs moving with high speed or not. The UE logs this information so that the information can later be reported to the network.

As described in the background, a network cell can indicate whether the UE should apply one or more features which ensure that the communication between the UE and network is more reliable in scenarios when the UE is moving at a high speed (relative to the network node). These features put stricter requirements on the UE and may waste the power of the UE. In some embodiments, then, the UE may determine that a certain event has occurred, where that event may be the same as or different from the events discussed above. The UE will determine which of one or more highspeed features are enabled for a cell for the UE, e.g., a cell in the UE is idle or active. The UE logs this information so that the information can later be reported to the network.

Note the features referred here as "high-speed features" could, for example, mean a feature where the UE shall apply a high-speed measurement feature, e.g., as configured by a flag highSpeedMeasFlag-rl6, or a feature where the UE shall apply a high-speed demodulation feature, e.g., as configured by the flag highSpeedDemodFlag-rl6.

The Carrier Aggregation and Dual Connectivity features defined by 3GPP specifications allow UEs to be served by more than one cell. A cell which is configured to serve the UE is considered to be a "serving cell" for this UE.

In one embodiment, the UE considers only serving cells of certain properties, for purposes of carrying out one or more of the logging and reporting techniques described herein. For example, in the case of Carrier Aggregation the UE may consider only the PCell of the UE, while not considering SCells. Or, in the case of Dual Connectivity, the UE may consider the PCell but not PSCell or SCells, or consider both the PCell and PSCell but not SCells. Another approach is that the UE reports the information for all serving cells of the UE, i.e., PCell, PSCells and SCells.

Above it has been described that the UE, when certain events occur, reports its own speed state and also a speed-related property of the cells that the UE is associated with. The UE may also report status of high-speed features, e.g., which high-speed features are enabled at the time a log is created or updated.

There may be any of a number of various events (trigger events or triggering events) that trigger any of these activities. Several of these events are listed below, along with example details of how the UE may log and report various related parameters:

Radio link failure (RLF) or handover failure o In the case of radio link failure or handover failure, the UE generates an RLF report. In such an RLF report, the UE could further include one or more of the following parameters in RLF report in relation to the HSDN cells and/or UE speed status and/or or high-speed feature status:

■ High-speed status related parameters as discussed above, including, for example,

• High-speed status of the UE in the previous PCell o This field is used to indicate if the UE was in a high-speed status, where the UE should prioritize high-speed cells or not, while being connected to the previous PCell. The advantage of knowing whether the UE was a high-speed status UE at the time of performing handover from the previous PCell is that the high-speed status UE specific HO parameter configuration optimization in the previous PCell can be enabled if such a HO fails rather than optimizing generic HO parameters.

• High-speed status of the UE in the failed PCell o This field is used to indicate if the UE was in a high-speed status, where the UE should prioritize high-speed cells or not, while being connected to the failed PCell or attempting to connect to the failed PCell. The advantage of knowing whether the UE was a high-speed status UE at the time of declaring failure in the failed PCell is that the highspeed status UE-specific parameter configuration (e.g., RLM configuration to the high-speed UEs) optimization in the failed PCell can be enabled rather than optimizing generic configuration parameters.

• High-speed status of the UE in the reestablishment PCell o This field is used to indicate if the UE was in a high-speed status, where the UE should prioritize high-speed cells or not, while being connected to the reestablishment PCell or attempting to connect to the reestablishment PCell. The advantage of knowing whether the UE was a high-speed status UE at the time of performing reestablishment in the reestablishment PCell is that the high-speed status UE specific parameter configuration (e.g., RA configuration to the high-speed UEs) optimization can be enabled in the reestablishment PCell rather than optimizing generic configuration parameters.

• High-speed status of the UE in the reconnect PCell o This field is used to indicate if the UE was in a high-speed status, where the UE should prioritize high-speed cells or not, while being connected to the reconnection PCell. The advantage of knowing whether the UE was a high-speed status UE at the time of performing reestablishment in the reconnect PCell is that the high-speed status UE specific parameter configuration (e.g., RA configuration to the high-speed UEs) optimization can be enabled in the reconnect PCell rather than optimizing generic configuration parameters.

■ High-speed status related parameters for a cell as discussed above, including, e.g.:

• Whether the previous PCell was a high-speed cell o This field is used to indicate if the previous PCell was a high-speed cell or not. The advantage of knowing whether the cell was a high-speed status cell at the time of sending HO command to the UE is that the high-speed cell specific HO parameter configuration optimization can be enabled in the previous PCell if such a HO fails rather than optimizing generic HO parameters.

• Whether the failed PCell was a high-speed cell o This field is used to indicate if the failed PCell was a highspeed cell or not. The advantage of knowing whether the cell was a high-speed status cell at the time of UE declaring a failure is that the high-speed cell specific parameter optimization (e.g., RLM configuration) can be enabled in the failed PCell rather than optimizing generic configuration parameters.

• Whether the reestablishment cell was a high-speed cell o This field is used to indicate if the reestablishment PCell was a high-speed cell or not. The advantage of knowing whether the cell was a high-speed status cell at the time of UE performing reestablishment in the reestablishment PCell is that the high-speed cell specific parameter configuration (e.g., RA configuration to the high-speed cell) optimization can be enabled in the reestablishment PCell rather than optimizing generic configuration parameters.

• Whether the reconnect cell was a high-speed cell o This field is used to indicate if the reconnect PCell was a high-speed cell or not. The advantage of knowing whether the cell was a high-speed status cell at the time of UE performing reconnection in the reconnect PCell is that the high-speed cell specific parameter configuration (e.g., random access (RA) configuration to the high-speed cell) optimization can be enabled in the reconnect PCell rather than optimizing generic configuration parameters.

■ Cell high-speed features enablement-related parameters as discussed above, including, e.g.:

• An indication of which of the high-speed status specific features were enabled for the UE in the previous PCell. Such an additional information would enable feature-specific failure cause analysis (i.e., whether the enabling/disabling the feature resulted in the failure) and also aid in feature-specific parameter optimization.

• An indication of which of the high-speed status specific features were enabled for the UE in the failed PCell. Such an additional information would enable feature-specific failure cause analysis (i.e., whether the enabling/disabling the feature resulted in the failure) and also aid in feature-specific parameter optimization.

• An indication of which of the high-speed status specific features were enabled for the UE in the reestablishment PCell. Such additional information would enable feature-specific failure cause analysis (i.e., whether the enabling/disabling the feature resulted in the failure) and also aid in feature-specific parameter optimization.

• An indication of which of the high-speed status specific features were enabled for the UE in the reconnect PCell. Such an additional information would enable feature-specific failure cause analysis (i.e., whether the enabling/disabling the feature resulted in the failure) and also aid in feature-specific parameter optimization.

Random access (RA) o Upon completing a random access procedure, the UE stores the RA related parameters in the RAReport (see TS 38.331 V16.6.0 for details) and reports to the network at a later point in time. Upon completing a RA procedure, the UE could further include one or more of the following parameters in RA report in relation to the HSDN cells and/or UE speed status and/or or high-speed feature status: ■ High-speed status related parameters as discussed above, including, e.g.:

• Whether the high-speed status of the UE in the cell in which the RA was performed was true or not. o This field is used to indicate if the UE was in a high-speed status, where the UE should prioritize high-speed cells or not, at the time of performing the RA procedure. The advantage of knowing whether the UE was a high-speed status UE at the time of performing RA procedure is that the high-speed status UE specific RA parameter configuration optimization can be enabled rather than optimizing generic RA parameters.

• Whether the high-speed status of the cell in which the UE performed the RA procedure was true or not. o This field is used to indicate if the cell was in a high-speed status or not at the time of the UE performing the RA procedure. The advantage of knowing whether the cell was a high-speed status cell at the time of the UE performing RA procedure is that the high-speed status cell specific RA parameter configuration optimization can be enabled rather than optimizing generic RA parameters.

■ Cell high-speed features enablement related parameters as discussed above, including, e.g.:

• An indication of which of the high-speed status specific features were enabled in the cell in which the UE performed the RA procedure. Such an additional information would enable featurespecific failure cause analysis (i.e., whether the enabling/disabling the feature resulted in the failure) and also aid in feature-specific parameter optimization.

Connection establishment failure o Upon failing to perform connection establishment from idle (RRCSetup failure) or inactive (RRCResume failure) states, the UE stores the failed access related parameters in the connection establishment failure Report (see ConnEstFailReport in TS 38.331 V16.6.0 for details) and reports to the network at a later point in time. Upon failing the access procedure, the UE could further include one or more of the following parameters in ConnEstFailReport in relation to the HSDN cells and/or UE speed status and/or or high-speed feature status:

■ High-speed status related parameters as discussed above, including, e.g.:

• Whether the high-speed status of the UE in the cell in which the connection establishment/resume was attempted was true or not. o This field is used to indicate if the UE was in a high-speed status, where the UE should prioritize high-speed cells or not, at the time of attempting the connection establishment/resume procedure. The advantage of knowing whether the UE was a high-speed status UE at the time of attempting the connection establishment/resume procedure is that the high-speed status UE specific parameter configuration optimization (e.g., RA parameters) can be enabled rather than optimizing generic RA parameters.

■ Cell high-speed status related parameters as described above, including, e.g.:

• Whether the high-speed status of the cell in which the UE attempted to perform connection establishment/resume procedure was true or not. o This field is used to indicate if the cell was in a high-speed status at the time of the UE attempting the connection establishment/resume procedure in that cell. The advantage of knowing whether the cell was a high-speed status cell at the time of attempting the connection establishment/resume procedure by the UE is that the high-speed status UE specific parameter configuration optimization (e.g., RA parameters) can be enabled rather than optimizing generic RA parameters.

■ Cell high-speed features enablement related parameters as discussed above, including, e.g.: • An indication of which of the high-speed status specific features were enabled in the cell in which the UE attempted the connection establishment/resume procedure. Such an additional information would enable feature-specific failure cause analysis (i.e., whether the enabling/disabling the feature resulted in the failure) and also aid in feature-specific parameter optimization.

A failure in the secondary leg (i.e., SCG radio link failure or SCG change failure) o In the case of SCG radio link failure or SCG handover failure, the UE generates an SCGFailurelnformation. In such a report or in any other report carrying the SCG failure related information, the UE could further include one or more of the following parameters in relation to the HSDN cells and/or UE speed status and/or or high-speed feature status:

■ High-speed status related parameters as discussed above, including, e.g.:

• High-speed status of the UE in the previous PSCell o This field is used to indicate if the UE was in a high-speed status, where the UE should prioritize high-speed cells or not, while being connected to the previous PSCell. The advantage of knowing whether the UE was a high-speed status UE at the time of performing handover from the previous PSCell is that the high-speed status UE specific HO parameter configuration optimization in the previous PSCell can be enabled if such a HO fails rather than optimizing generic HO parameters.

• High-speed status of the UE in the failed PSCell o This field is used to indicate if the UE was in a high-speed status, where the UE should prioritize high-speed cells or not, while being connected to the failed PSCell or attempting to connect to the failed PSCell. The advantage of knowing whether the UE was a high-speed status UE at the time of declaring failure in the failed PSCell is that the high-speed status UE specific parameter configuration (e.g., RLM configuration to the high-speed UEs) optimization in the failed PSCell can be enabled rather than optimizing generic configuration parameters. ■ Cell high-speed status related parameters as discussed above, including, e.g.:

• Whether the previous PSCell was a high-speed cell o This field is used to indicate if the previous PSCell was a high-speed cell or not. The advantage of knowing whether the cell was a high-speed status cell at the time of sending HO command to the UE is that the high-speed cell specific HO parameter configuration optimization can be enabled in the previous PSCell if such a HO fails rather than optimizing generic HO parameters.

• Whether the failed PSCell was a high-speed cell o This field is used to indicate if the failed PSCell was a highspeed cell or not. The advantage of knowing whether the cell was a high-speed status cell at the time of UE declaring a failure is that the high-speed cell specific parameter optimization (e.g., RLM configuration) can be enabled in the failed PSCell rather than optimizing generic configuration parameters.

• An indication of which of the high-speed status specific features were enabled for the UE in the previous PSCell. Such additional information would enable feature-specific failure cause analysis (i.e., whether the enabling/disabling the feature resulted in the failure) and also aid in feature-specific parameter optimization.

• An indication of which of the high-speed status specific features were enabled for the UE in the failed PSCell. Such an additional information would enable feature-specific failure cause analysis (i.e., whether the enabling/disabling the feature resulted in the failure) and also aid in feature-specific parameter optimization.

On-demand system information request o Upon performing the on-demand system information request procedure, the UE could further include one or more of the following parameters in a report in relation to the HSDN cells and/or UE speed status and/or or high-speed feature status and report the same to the network node at a later point in time:

■ High-speed status related parameters as discussed above, including, e.g.:

• Whether the high-speed status of the UE in the cell, in which the UE attempted to perform on-demand system information request procedure, was true or not. o This field is used to indicate if the UE was in a high-speed status, where the UE should prioritize high-speed cells or not, at the time of attempting the on-demand SI request procedure. The advantage of knowing whether the UE was a high-speed status UE at the time of attempting the on- demand SI request procedure is that the high-speed status UE specific parameter configuration optimization (e.g., RA parameters) can be enabled rather than optimizing generic RA parameters.

■ Cell high-speed status related parameters as discussed above, including, e.g.:

• Whether the high-speed status of the cell in which the UE attempted to perform on-demand SI request procedure was true or not. o This field is used to indicate if the cell was in a high-speed status at the time of the UE attempting the on-demand SI request procedure in that cell. The advantage of knowing whether the cell was a high-speed status cell at the time of attempting the on-demand SI request procedure by the UE is that the high-speed status UE specific parameter configuration optimization (e.g., RA parameters) can be enabled rather than optimizing generic RA parameters.

• An indication of which of the high-speed status specific features were enabled in the cell in which the UE attempted the on- demand SI procedure. Such an additional information would enable feature-specific failure cause analysis (i.e., whether the enabling/disabling the feature resulted in the failure) and also aid in feature-specific parameter optimization.

In the above discussion, examples of the presently disclosed techniques are described in the context of the 3GPP specifications for NR and LTE. Thus, 3GPP terminology is used. It should be appreciated, however, that the techniques are applicable to other wireless systems in which crossscheduling of carriers is employed, where the specific terminology may differ.

Figure 1 illustrates an example method, as implemented by a wireless device operating in a wireless device. Just as "wireless device" may be considered a generalization of "UE," the method illustrated here is a generalization of several of the techniques described above and should be understand as encompassing those techniques. Thus, wherever there are differences in terminology, the terms used in connection with Figure 1 should be understood as generalizations or synonyms of the terms used in describing the detailed examples above. For example, the term "wireless device" is a generalization of the 3GPP-specific term "UE." Furthermore, variations and modifications described in connection with the examples above are applicable to the method shown in Figure 1, even if those variations are not explicitly discussed below.

As shown at block 110, the method of Figure 1 begins with determining whether the wireless device is in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available, and/or determining whether the wireless device is in a cell designated as a high-speed cell. This is shown at block 110. The method further comprises logging information indicating whether the wireless device is in the high-speed state and/or whether the wireless device is in a cell designated as a high-speed cell and/or an indication of each of one or more features specific to high-speed status enabled in a cell.

In some embodiments, the determining shown in block 110 and the logging of information shown in block 120 are in response to determining that a triggering event has occurred. In some of these embodiments, the logging may comprise logging an indication of the triggering event. In some embodiments, the logging may comprise logging an indication of each of one or more features specific to high-speed status that were enabled in the cell at the time of the triggering event. In various embodiments or instances, the triggering event may comprise any one of the following examples: a radio link failure; a handover failure; a random access procedure; a connection establishment failure; a failure in a secondary cell group leg; and a request from the wireless network. In some such embodiments or instances, the triggering event is a radio link failure or a handover failure, and the logging of information comprises generating a radio link failure report, the radio link failure report comprising at least one of any one or more of the following: a high-speed state of the wireless device in a primary cell immediately prior to the handover failure; a high-speed state of the wireless device in a primary cell in which radio link failure is declared; a high-speed state of the wireless device when performing reestablishment; an indication of whether a primary cell immediately prior to the handover failure was a high-speed cell; an indication of whether a primary cell in which radio link failure is declared was a high-speed cell; an indication of whether a reestablishment cell following the radio link failure or handover failure was a high-speed cell; an indication of which features specific to high-speed status were enabled in a primary cell immediately prior to the handover failure; an indication of which features specific to high-speed status were enabled in a primary cell in which radio link failure is declared; and an indication of which features specific to high-speed status were enabled in a reestablishment cell following the radio link failure or handover failure.

In some embodiments or instances, the triggering event may be a random access procedure, and the logging of information may comprise generating a random access report. This random access report may at least one of any one or more of the following, in various examples: a high-speed state of the wireless device in the cell in which random access was performed; an indication of whether the cell in which random access was performed was a high-speed cell; and an indication of which features specific to high-speed status were enabled in the cell in which random access was performed.

In other embodiments or instances, the triggering event may be a failed connection establishment or connection resumption, and the logging of information may comprise generating a connection establishment failure report. This connection establishment failure report may comprise at least one of any one or more of the following: a high-speed state of the wireless device in the cell in which connection establishment or connection resumption was attempted; an indication of whether the cell in which connection establishment or connection resumption was attempted was a high-speed cell; and an indication of which features specific to high-speed status were enabled in the cell in which connection establishment or connection resumption was attempted.

In still other embodiments or instances, the triggering event may be a request received from the wireless network and the logging of information may comprise generating a report, where the report comprises at least one of any one or more of the following: a high-speed state of the wireless device in the cell in which the request was received; an indication of whether the cell in which the request was received was a high-speed cell; and an indication of which features specific to high-speed status were enabled in the cell in which the request was received.

In various embodiments or instances of the method shown in Figure 1, the method may comprise sending the logged information to the wireless network. This is shown at block 130.

Figure 2 illustrates another example method, this one as implemented by a network node. Again, this method is a generalization of several of the techniques described above and should be understand as encompassing those techniques. So, wherever there are differences in terminology, the terms used in connection with Figure 2 should be understood as generalizations or synonyms of the terms used in describing the detailed examples above. For example, the term "network node" is a generalization of the 3GPP terms "gNB" and "eNB." Furthermore, variations and modifications described in connection with the examples above are applicable to the method shown in Figure 2, even if those variations are not explicitly discussed below.

As shown at block 210, the method illustrated in Figure 2 comprises receiving a report from each of a plurality of wireless devices operating in the wireless network. Each of these reports comprises one or more of any one of: (a) an indication of whether the respective wireless device, at the time information in the report was logged, was in a high-speed state, wherein the highspeed state is such that a wireless device in high-speed state prioritizes cells designated as highspeed cells for selection and/or re-selection, when available, (b) an indication of whether a cell the respective wireless device was in at the time information in the report was logged was designated as a high-speed cell, (c) an indication of which of one or more features specific to high-speed status were enabled in a cell at the time information in the report is logged. As shown at block 210, the method further comprises modifying one or more operational parameters in the wireless network, based on the reports.

In some embodiments or instances of the illustrated method, modifying one or more operational parameters may comprise changing a high-speed designation for at least one cell in the wireless network. In some of these or in other embodiments or instances, modifying one or more operational parameters may comprise enabling or disabling one or more high-speed related features for at least one cell in the wireless network.

Figure 3 shows an example of a communication system 300 in accordance with some embodiments. The techniques described above may be implemented in such a communication system, in various embodiments. In the example, the communication system 300 includes a telecommunication network 302 that includes an access network 304, such as a radio access network (RAN), and a core network 306, which includes one or more core network nodes 308. The access network 304 includes one or more access network nodes, such as network nodes 310a and 310b (one or more of which may be generally referred to as network nodes 310), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 310 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 312a, 312b, 312c, and 312d (one or more of which may be generally referred to as UEs 312) to the core network 306 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 300 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 300 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs 312 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 310 and other communication devices. Similarly, the network nodes 310 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 312 and/or with other network nodes or equipment in the telecommunication network 302 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 302.

In the depicted example, the core network 306 connects the network nodes 310 to one or more hosts, such as host 316. 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 306 includes one more core network nodes (e.g., core network node 308) 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 308. 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 316 may be under the ownership or control of a service provider other than an operator or provider of the access network 304 and/or the telecommunication network 302, and may be operated by the service provider or on behalf of the service provider. The host 316 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 300 of Figure 3 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, 3G, 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 302 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 302. For example, the telecommunications network 302 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 312 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 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304. 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 314 communicates with the access network 304 to facilitate indirect communication between one or more UEs (e.g., UE 312c and/or 312d) and network nodes (e.g., network node 310b). In some examples, the hub 314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 314 may be a broadband router enabling access to the core network 306 for the UEs. As another example, the hub 314 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 310, or by executable code, script, process, or other instructions in the hub 314. As another example, the hub 314 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 314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 314 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 314 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 314 may have a constant/persistent or intermittent connection to the network node 310b. The hub 314 may also allow for a different communication scheme and/or schedule between the hub 314 and UEs (e.g., UE 312c and/or 312d), and between the hub 314 and the core network 306. In other examples, the hub 314 is connected to the core network 306 and/or one or more UEs via a wired connection. Moreover, the hub 314 may be configured to connect to an M2M service provider over the access network 304 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection. In some embodiments, the hub 314 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 310b. In other embodiments, the hub 314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 310b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 4 shows a UE 400 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 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a power source 408, a memory 410, a communication interface 412, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 4. 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 402 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 410. The processing circuitry 402 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 402 may include multiple central processing units (CPUs).

In the example, the input/output interface 406 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 400. 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 408 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 408 may further include power circuitry for delivering power from the power source 408 itself, and/or an external power source, to the various parts of the UE 400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 408. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 408 to make the power suitable for the respective components of the UE 400 to which power is supplied.

The memory 410 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 410 includes one or more application programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by the UE 400, any of a variety of various operating systems or combinations of operating systems.

The memory 410 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 ISIM, 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 410 may allow the UE 400 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 410, which may be or comprise a device-readable storage medium.

The processing circuitry 402 may be configured to communicate with an access network or other network using the communication interface 412. The communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422. The communication interface 412 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 418 and/or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., antenna 422) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface 412 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 412, 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 400 shown in Figure 4.

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 5 shows a network node 500 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, SelfOrganizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

The network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508. The network node 500 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 500 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 500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, 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 500.

The processing circuitry 502 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 500 components, such as the memory 504, to provide network node 500 functionality. In some embodiments, the processing circuitry 502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 502 includes one or more of radio frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the radio frequency (RF) transceiver circuitry 512 and the baseband processing circuitry 514 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 512 and baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.

The memory 504 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 502. The memory 504 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 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and/or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and memory 504 is integrated.

The communication interface 506 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 506 comprises port(s)/terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. The communication interface 506 also includes radio frontend circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510. Radio front-end circuitry 518 comprises filters 520 and amplifiers 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio frontend circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502. The radio front-end circuitry 518 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 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 520 and/or amplifiers 522. The radio signal may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 500 does not include separate radio frontend circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

The antenna 510 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.

In certain embodiments, the antenna 510 is separate from the network node 500 and connectable to the network node 500 through an interface or port.

The antenna 510, communication interface 506, and/or the processing circuitry 502 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 510, the communication interface 506, and/or the processing circuitry 502 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 508 provides power to the various components of network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 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 508. As a further example, the power source 508 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 500 may include additional components beyond those shown in Figure 5 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 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.

Figure 6 is a block diagram of a host 600, which may be an embodiment of the host 316 of Figure 3, in accordance with various aspects described herein. As used herein, the host 600 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 600 may provide one or more services to one or more UEs.

The host 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a network interface 608, a power source 610, and a memory 612. 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 4 and 5, such that the descriptions thereof are generally applicable to the corresponding components of host 600.

The memory 612 may include one or more computer programs including one or more host application programs 614 and data 616, which may include user data, e.g., data generated by a UE for the host 600 or data generated by the host 600 for a UE. Embodiments of the host 600 may utilize only a subset or all of the components shown. The host application programs 614 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 614 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 600 may select and/or indicate a different host for over- the-top services for a UE. The host application programs 614 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 7 is a block diagram illustrating a virtualization environment 700 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 700 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 702 (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 704 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 706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 708a and 708b (one or more of which may be generally referred to as VMs 708), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 706 may present a virtual operating platform that appears like networking hardware to the VMs 708.

The VMs 708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 706. Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of VMs 708, 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 708 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 708, and that part of hardware 704 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 708 on top of the hardware 704 and corresponds to the application 702.

Hardware 704 may be implemented in a standalone network node with generic or specific components. Hardware 704 may implement some functions via virtualization. Alternatively, hardware 704 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 710, which, among others, oversees lifecycle management of applications 702. In some embodiments, hardware 704 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 712 which may alternatively be used for communication between hardware nodes and radio units.

Figure 8 shows a communication diagram of a host 802 communicating via a network node 804 with a UE 806 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 312a of Figure 3 and/or UE 400 of Figure 4), network node (such as network node 310a of Figure 3 and/or network node 500 of Figure 5), and host (such as host 316 of Figure 3 and/or host 600 of Figure 6) discussed in the preceding paragraphs will now be described with reference to Figure 8. Like host 600, embodiments of host 802 include hardware, such as a communication interface, processing circuitry, and memory. The host 802 also includes software, which is stored in or accessible by the host 802 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 806 connecting via an over-the-top (OTT) connection 850 extending between the UE 806 and host 802. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 850.

The network node 804 includes hardware enabling it to communicate with the host 802 and UE 806. The connection 860 may be direct or pass through a core network (like core network 306 of Figure 3) 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 806 includes hardware and software, which is stored in or accessible by UE 806 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 non-human user via UE 806 with the support of the host 802. In the host 802, an executing host application may communicate with the executing client application via the OTT connection 850 terminating at the UE 806 and host 802. 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 850 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 850.

The OTT connection 850 may extend via a connection 860 between the host 802 and the network node 804 and via a wireless connection 870 between the network node 804 and the UE 806 to provide the connection between the host 802 and the UE 806. The connection 860 and wireless connection 870, over which the OTT connection 850 may be provided, have been drawn abstractly to illustrate the communication between the host 802 and the UE 806 via the network node 804, 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 850, in step 808, the host 802 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 806. In other embodiments, the user data is associated with a UE 806 that shares data with the host 802 without explicit human interaction. In step 810, the host 802 initiates a transmission carrying the user data towards the UE 806. The host 802 may initiate the transmission responsive to a request transmitted by the UE 806. The request may be caused by human interaction with the UE 806 or by operation of the client application executing on the UE 806. The transmission may pass via the network node 804, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 812, the network node 804 transmits to the UE 806 the user data that was carried in the transmission that the host 802 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 814, the UE 806 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 806 associated with the host application executed by the host 802.

In some examples, the UE 806 executes a client application which provides user data to the host 802. The user data may be provided in reaction or response to the data received from the host 802. Accordingly, in step 816, the UE 806 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 806. Regardless of the specific manner in which the user data was provided, the UE 806 initiates, in step 818, transmission of the user data towards the host 802 via the network node 804. In step 820, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 804 receives user data from the UE 806 and initiates transmission of the received user data towards the host 802. In step 822, the host 802 receives the user data carried in the transmission initiated by the UE 806.

One or more of the various embodiments improve the performance of OTT services provided to the UE 806 using the OTT connection 850, in which the wireless connection 870 forms the last segment. More precisely, by allowing an operator to gather information about whether UEs are in a state where they are supposed to prioritize selecting cells indicated as high-speed cells and whether the cell that the UE is associated to is a, so called, high-speed cell and also whether certain features suitable for high-speed scenarios are enabled in the cell, an operator may modify its deployment to avoid failures, e.g., avoid that UEs experience radio link failures, random access failures, etc. , Thus, the teachings of these embodiments may improve connection reliability and latencies and thereby provide benefits such as reduced user waiting time.

In an example scenario, factory status information may be collected and analyzed by the host 802.

As another example, the host 802 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 802 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 802 may store surveillance video uploaded by a UE. As another example, the host 802 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 802 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 850 between the host 802 and UE 806, 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 802 and/or UE 806. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 850 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 850 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 804. 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 802. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 850 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 in memory, which in certain embodiments may be a computer program product, e.g., 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.

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 whether the wireless device is in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available; and logging information indicating whether the wireless device is in the high-speed state. 2. The method of example embodiment 1, wherein the determining step further comprises determining whether the wireless device is in a cell designated as a high-speed cell and the logging step further comprises logging information indicating whether the wireless device is in a cell designated as a high-speed cell.

3. The method of example embodiment 1, wherein the determining step further comprises determining one or more features specific to high-speed status enabled in a cell and the logging step further comprises logging information indicating each of the one or more features specific to highspeed status enabled in the cell.

4. A method, in a wireless device operating in a wireless network, the method comprising: determining whether the wireless device is in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available, and/or determining whether the wireless device is in a cell designated as a high-speed cell; and logging information indicating whether the wireless device is in the high-speed state and/or whether the wireless device is in a cell designated as a high-speed cell and/or an indication of each of one or more features specific to high-speed status enabled in a cell.

5. The method of any of example embodiments 1-4, wherein said determining steps and said logging information are in response to determining that a triggering event has occurred.

6. The method of example embodiment 5, wherein said logging information comprises logging an indication of the triggering event.

7. The method of example embodiment 5 or 6, wherein said logging information comprises logging an indication of each of one or more features specific to high-speed status that were enabled in the cell at the time of the triggering event.

8. The method of any of example embodiments 5-7, wherein the triggering event comprises any one of: a radio link failure; a handover failure; a random access procedure; a connection establishment failure; a failure in a secondary cell group leg; and a request from the wireless network.

9. The method of example embodiment 8, wherein the triggering event is a radio link failure or a handover failure, and wherein said logging information comprises generating a radio link failure report, the radio link failure report comprising at least one of any one or more of the following: a high-speed state of the wireless device in a primary cell immediately prior to the handover failure; a high-speed state of the wireless device in a primary cell in which radio link failure is declared; a high-speed state of the wireless device when performing reestablishment; an indication of whether a primary cell immediately prior to the handover failure was a highspeed cell; an indication of whether a primary cell in which radio link failure is declared was a highspeed cell; an indication of whether a reestablishment cell following the radio link failure or handover failure was a high-speed cell; an indication of which features specific to high-speed status were enabled in a primary cell immediately prior to the handover failure; an indication of which features specific to high-speed status were enabled in a primary cell in which radio link failure is declared; and an indication of which features specific to high-speed status were enabled in a reestablishment cell following the radio link failure or handover failure.

10. The method of example embodiment 8, wherein the triggering event is a random access procedure, and wherein said logging information comprises generating a random access report, the random access report comprising at least one of any one or more of the following: a high-speed state of the wireless device in the cell in which random access was performed; an indication of whether the cell in which random access was performed was a high-speed cell; and an indication of which features specific to high-speed status were enabled in the cell in which random access was performed. 11. The method of example embodiment 8, wherein the triggering event is a failed connection establishment or connection resumption, and wherein said logging information comprises generating a connection establishment failure report, the connection establishment failure report comprising at least one of any one or more of the following: a high-speed state of the wireless device in the cell in which connection establishment or connection resumption was attempted; an indication of whether the cell in which connection establishment or connection resumption was attempted was a high-speed cell; and an indication of which features specific to high-speed status were enabled in the cell in which connection establishment or connection resumption was attempted.

12. The method of example embodiment 8, wherein the triggering event is a request received from the wireless network and wherein said logging information comprises generating a report, the report comprising at least one of any one or more of the following: a high-speed state of the wireless device in the cell in which the request was received; an indication of whether the cell in which the request was received was a high-speed cell; and an indication of which features specific to high-speed status were enabled in the cell in which the request was received.

13. The method of any of example embodiments 1-12, further comprising sending the logged information to the wireless network.

Group B Embodiments

14. A method in a network node operating in or in association with a wireless network, the method comprising: receiving a report from each of a plurality of wireless devices operating in the wireless network, each report comprising one or more of any one of: (a) an indication of whether the respective wireless device, at the time information in the report was logged, was in a high-speed state, wherein the high-speed state is such that a wireless device in high-speed state prioritizes cells designated as high-speed cells for selection and/or re-selection, when available, (b) an indication of whether a cell the respective wireless device was in at the time information in the report was logged was designated as a high-speed cell, (c) an indication of which of one or more features specific to high-speed status were enabled in a cell at the time information in the report is logged ; and modifying one or more operational parameters in the wireless network, based on the reports.

15. The method of example embodiment 14, wherein modifying one or more operational parameters comprises changing a high-speed designation for at least one cell in the wireless network.

16. The method of example embodiment 14, wherein modifying one or more operational parameters comprises enabling or disabling one or more high-speed related features for at least one cell in the wireless network.

17. A wireless device comprising transceiver circuitry configured to communicate with a wireless network and processing circuitry operatively coupled to the transceiver circuitry, wherein the processing circuitry is configured to carry out a method according to any one of example embodiments 1-13.

18. A wireless device adapted to carry out a method according to any one of example embodiments 1-13.

19. A network node comprising transceiver circuitry configured to communicate with a wireless device served by the network node and processing circuitry operatively coupled to the transceiver circuitry, wherein the processing circuitry is configured to carry out a method according to any one of example embodiments 14-16.

20. A network node adapted to carry out a method according to any one of example embodiments 14-16.

Group C Embodiments

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

45. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

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

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

Some abbreviations:

UE User Equipment (Wireless device in 3GPP systems)

NR New Radio

LTE Long Term Evolution gNB Base station in NR eNB Base station in LTE

RRC Radio Resource Control

PDCP Packet Data Convergence Protocol

RLC Radio Link Control

MAC Medium Access Control

RAN Radio Access Network

3GPP 3rd generation partnership project

TS Technical Specification

RLF Radio Link Failure

PCell Primary Cell

SCell Secondary Cell

PSCell Primary Secondary Cell

HO Handover

RLM Radio Link Monitoring

HSDN High Speed Dedicated Network

RA Random Access

SCG Secondary Cell Group

MCG Master Cell Group

Claims

CLAIMS What is claimed is:

1. A method, in a wireless device operating in a wireless network, the method comprising: determining (110) whether the wireless device is in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available; and logging (120) information indicating whether the wireless device is in the high-speed state.

2. The method of claim 1, wherein the method further comprises determining whether the wireless device is in a cell designated as a high-speed cell and logging information indicating whether the wireless device is in a cell designated as a high-speed cell.

3. The method of claim 1, wherein the determining step comprises determining one or more features specific to high-speed status enabled in a cell and the logging step comprises logging information indicating each of the one or more features specific to high-speed status enabled in the cell.

4. A method, in a wireless device operating in a wireless network, the method comprising: determining (110) whether the wireless device is in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available, and/or determining whether the wireless device is in a cell designated as a high-speed cell; and logging (120) information indicating whether the wireless device is in the high-speed state and/or whether the wireless device is in a cell designated as a high-speed cell and/or an indication of each of one or more features specific to high-speed status enabled in a cell.

5. The method of any of claims 1-4, wherein said determining steps and said logging information are in response to determining that a triggering event has occurred.

6. The method of claim 5, wherein said logging information comprises logging an indication of the triggering event.

47

7. The method of claims 5 or 6, wherein said logging information comprises logging an indication of each of one or more features specific to high-speed status that were enabled in the cell at the time of the triggering event.

8. The method of any one of claims 1-7, further comprising sending (130) the logged information to the wireless network.

9. A method in a network node operating in or in association with a wireless network, the method comprising: receiving (210) a report from each of a plurality of wireless devices operating in the wireless network, each report comprising one or more of any one of: (a) an indication of whether the respective wireless device, at the time information in the report was logged, was in a high-speed state, wherein the high-speed state is such that a wireless device in high-speed state prioritizes cells designated as high-speed cells for selection and/or re-selection, when available, (b) an indication of whether a cell the respective wireless device was in at the time information in the report was logged was designated as a high-speed cell, (c) an indication of which of one or more features specific to high-speed status were enabled in a cell at the time information in the report is logged; and modifying (220) one or more operational parameters in the wireless network, based on the reports.

10. The method of claim 9, wherein modifying (220) one or more operational parameters comprises changing a high-speed designation for at least one cell in the wireless network.

11. The method of claim 9, wherein modifying (220) one or more operational parameters comprises enabling or disabling one or more high-speed related features for at least one cell in the wireless network.

12. A wireless device (400) comprising transceiver circuitry (418, 420) configured to communicate with a wireless network and processing circuitry (402) operatively coupled to the transceiver circuitry (418, 420), wherein the processing circuitry (402) is configured to: determine whether the wireless device (400) is in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available; and

48 log information indicating whether the wireless device (400) is in the high-speed state.

13. The wireless device of claim 12, wherein the processing circuitry (402) is configured to determine whether the wireless device (400) is in a cell designated as a high-speed cell and log information indicating whether the wireless device (400) is in a cell designated as a high-speed cell.

14. The wireless device (400) of claim 12, wherein the processing circuitry (402) is configured to determine one or more features specific to high-speed status enabled in a cell and log information indicating each of the one or more features specific to high-speed status enabled in the cell.

15. A wireless device (400) comprising transceiver circuitry (418, 420) configured to communicate with a wireless network and processing circuitry (402) operatively coupled to the transceiver circuitry, wherein the processing circuitry (402) is configured to: determine whether the wireless device (400) is in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available, and/or determine whether the wireless device (400) is in a cell designated as a highspeed cell; and log information indicating whether the wireless device (400) is in the high-speed state and/or whether the wireless device (400) is in a cell designated as a high-speed cell and/or an indication of each of one or more features specific to high-speed status enabled in a cell.

16. The wireless device (400) of any of claims 12-15, wherein the processing circuitry (402) is configured to perform said determining and logging in response to determining that a triggering event has occurred.

17. The wireless device (400) of claim 16, wherein the processing circuitry (402) is configured to log an indication of the triggering event.

18. The wireless device (400) of claim 16 or 17, wherein the processing circuitry (402) is configured to log an indication of each of one or more features specific to high-speed status that were enabled in the cell at the time of the triggering event.

49

19. The wireless device (400) of any one of claims 12-18, wherein the processing circuitry (402) is configured to send the logged information to the wireless network, via the transceiver (418, 420).

20. A wireless device (400) adapted to carry out a method according to any one of claims 1-8.

21. A network node (500) comprising transceiver circuitry (512, 514) configured to communicate with a wireless device served by the network node (500) and processing circuitry (502) operatively coupled to the transceiver circuitry (512, 514), wherein the processing circuitry is configured to: receive a report from each of a plurality of wireless devices operating in a wireless network, each report comprising one or more of any one of: (a) an indication of whether the respective wireless device, at the time information in the report was logged, was in a high-speed state, wherein the high-speed state is such that a wireless device in highspeed state prioritizes cells designated as high-speed cells for selection and/or reselection, when available, (b) an indication of whether a cell the respective wireless device was in at the time information in the report was logged was designated as a high-speed cell, (c) an indication of which of one or more features specific to highspeed status were enabled in a cell at the time information in the report is logged; and modify one or more operational parameters in the wireless network, based on the reports.

22. The network node (500) of claim 21, wherein modifying one or more operational parameters comprises changing a high-speed designation for at least one cell in the wireless network.

23. The network node (500) of claim 21, wherein modifying one or more operational parameters comprises enabling or disabling one or more high-speed related features for at least one cell in the wireless network.

24. A network node (500) adapted to carry out a method according to any one of claims 9-11.

25. A computer program product comprising program instructions for execution by processing circuitry in a wireless device, the program instructions being configured to cause the wireless device to carry out a method according to any one of claims 1-8.

26. A computer-readable medium comprising the computer program product of claim 25.

50

27. 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 9-11.

28. A computer-readable medium comprising the computer program product of claim 27.