Methods for priority handling between data collection for model training and other immediate procedures

Abstract

Systems and methods are disclosed for mobility-related data collection in wireless communication systems, including embodiments involving a User Equipment (UE) and a network node In one embodiment, a method performed by a UE comprises receiving, from a network node, configuration information that configures the UE for measurements for mobility-related data collection, the measurements for mobility-related data collection comprising measurements on at least one frequency. The method includes performing measurements for mobility-related data collection in accordance with the received configuration information and in such a manner that performing the measurements for mobility-related data collection does not impair one or more certain procedures or functionalities at the UE. Corresponding embodiments of a UE as well as embodiments of a network node and a method of operation thereof are also disclosed.

Description

[0001] METHODS FOR PRIORITY HANDLING BETWEEN DATA COLLECTION FOR MODEL TRAINING AND OTHER IMMEDIATE PROCEDURES RELATED APPLICATIONS

[0002] This application claims the benefit of U. S. Provisional Patent Application No. 63 / 777,397, filed March 25, 2025, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0003] TECHNICAL FIELD

[0004] The present disclosure relates to a wireless communications system and more specifically to data collection for model training in a wireless communication system.

[0005] BACKGROUND

[0006] Data collection is an essential tool that allows the training entity to generate a model suitable for a specific device. In particular, related to the case of Artificial Intelligence and / or Machine Learning (AI / ML) applied to Radio Access Network (RAN) use cases, e.g. beam management, positioning accuracy enhancements, cell / frequency level measurement predictions, mobility event predictions, in a 3rdGeneration Partnership Project (3GPP) 5thGeneration (5G) system, the AI / ML model could be User Equipment (UE)-sided, i.e. tailored for specific UEs, or network (NW)-sided, e.g. tailored for specific next generation NodeBs (gNBs). In order for RAN schemes based on AI / ML models to outperform conventional non-AI / ML based schemes, it is necessary that the device (UE or gNB in this case) collects data so that the training entity can generate a model suitable for the device inference. Otherwise, if the collected data set during the training does not match the inputs during the inference, then it is proven that AI / ML may not provide the expected benefits.

[0007] Related to NW-side models, it has been assumed so far in 3GPP that the gNB and / or the Operations, Administration, and Maintenance (OAM) will be in charge of collection of the training data. If the gNB is responsible, it is assumed that the gNB may configure the UE with a set of resources, e.g. Channel State Information (CSI) Reference Signal (CSI-RS) resources or Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) Block (SSB) resource sets, in which the UE should collect measurements for a certain amount of time. Then, the UE will report the measurement results to the gNB, e.g. via Radio Resource Control (RRC) signaling. Then, the training can be performed in the gNB itself, or in another node controlled by the gNB-vendor, e.g. an Over-The-Top (OTT) server handled by the gNB-vendor. A similar approach would apply for the case in which the OAM performs the NW-side training. In this case, the OAM may request thegNB to provide to the UE a certain configuration according to which the UE should perform certain measurements and collect data. Once the data collection is completed, the UE transfers the collected data to the OAM, e.g. using the Minimization of Drive Testing (MDT) framework such as the immediate MDT or the logged MDT.

[0008] From an operation point of view, performing data collection implies that the UE logs the data intended for the NW-side model training, and stores this collected data in the local memory. Since such type of data does not have any stringent latency requirement, it is beneficial for the UE and for the network (e.g. in terms of UE power consumption, or spectral efficiency) if the UE could log the measured data, e.g. the beam / cell / frequency level qualities, and transmit them at a later point in time, rather than transmitting them immediately upon performing the corresponding measurement (as it is for example for conventional Layer 1 (LI) measurements which are transmitted on Uplink Control Information (UCI)). Transmitting the collected data at a later point in time rather than immediately reduces the power consumed by the UE to continuously access the channel to transmit data that does not have stringent latency requirements and also reduces the impact on the spectral efficiency which instead can be used for transmission of data that have higher priority or more stringent latency requirements.

[0009] For the reasons mentioned above, it was decided in 3GPP to enable the UE to transmit the logged LI measurements (i.e. beam level measurements) via RRC signaling, e.g. periodically, or potentially based on events or upon network request, thereby avoiding the complexity and inefficiency of reporting over the LI as outlined above. The logging of measurements implies that the UE would need to send this logged data in multiple RRC messages. In particular, the preferred framework to transfer this data from the UE to the network is based on the UEInformationRequest and UEInformationResponse procedure, wherein the gNB requests the collected data from the UE, and the UE transmits the collected data upon receiving such request. Further, this framework allows the UE to signal to the gNB a “measurement availability indication” indicating the availability of additional logged data in the UE memory, so that the network can transmit a successive UEInformationRequest for the transmission of other portions of logged data. Related to when to start the data logging, the UE can either start upon receiving a certain configuration, or when certain radio events are fulfilled. On the latter, both LI or Layer 3 (L3) type of events can be considered. A LI event can be based for example on the definition of thresholds based on LI Reference Signal Received Power (RSRP) quality measured for the CSLRS or SSBs, whereas a L3 type of event can be associated to thresholds based on cell level measurements or even to radio events such as beam failure, or radio link failures, or the starting of timers associated to radio link failures (e.g. T310 or T312). The same approach of reporting over the L3 RRC signaling isexpected to be adopted also in future AI / ML RAN use cases, given the flexibility and efficiency of such method.

[0010] The Al / ML for Physical Layer (PHY) Study Item in 3GPP Release (Rel-) 18 has led to a work item in Rel-19. However, the scope has been limited to lower layer features, such as beam management, which is sometimes referred to as intra-cell mobility. Other features, such as L3 handovers, RRC measurements configuration, and reporting of predictions have not been part of Rel-18.

[0011] In Rel-19, a Study Item to study the usage of AI / ML for L3 Mobility and / or Radio Resource Management (RRM) measurements has been approved, which may lay the foundation of AI / ML for RAN2 features for 6thGeneration (6G) higher layers (see RP -234055, Study on Artificial Intelligence (AI) / Machine Learning (ML) for mobility in NR, 3GPP TSG RAN Meeting #102, Edinburgh, GB, December 11-15, 2023). In that case, one of the RRC features which will be considered is event-triggered measurement reporting and / or variants of that related to predictions, as indicated by the objective of the study item shown in the following excerpt from RP -234055:

[0012] The study will focus on mobility enhancement in RRC CONNECTED mode over air interface by following existing mobility framework, i.e., handover decision is always made in network side. Mobility use cases focus on standalone NR PCell change. UE-side and network-side AI / ML model can be both considered, respectively.

[0013] Study and evaluate potential benefits and gains of AI / ML aided mobility for network triggered L3-based handover, considering the following aspects:

[0014] • AI / ML based RRM measurement and event prediction,

[0015] • Cell-level measurement prediction including intra and inter-frequency (UE sided and NW sided model) [RAN2]

[0016] • Inter-cell Beam-level measurement prediction for L3 Mobility (UE sided and NW sided model) [RAN2]

[0017] • HO failure / RLF prediction (UE sided model) [RAN2]

[0018] • Measurement events prediction (UE sided model) [RAN2]

[0019] • Study the need / benefits of any other UE assistance information for the network side model [RAN2]

[0020] • The evaluation of the AI / ML aided mobility benefits should consider HO performance KPIs (e.g., Ping-pong HO, HOF / RLF, Time of stay, Handover interruption, prediction accuracy, and measurement reduction) etc.) and complexity tradeoffs [RAN2]• NOTE: Simulation assumption and methodology can leverage TR 38.901, 38.843 and 36.839. And leave the detail discussion to RAN2

[0021] • Potential Al mobility specific enhancement should be based on the Rell9 AI / ML-air interface WID general framework (e.g. LCM, performance monitoring etc) [RAN2]

[0022] • NOTE: This would only be treated after sufficient progress is made in the Rel-19 AI / ML air interface WID

[0023] • Potential specification impacts of AI / ML aided mobility [RAN2]

[0024] • Evaluate testability, interoperability, and impacts on RRM requirements and performance [RAN4]

[0025] • NOTE 1: RAN1 / 3 work can be triggered via LS

[0026] • NOTE 2: RAN4 scope / work can be defined and confirmed by RAN# 105 after some RAN2 discussions (within the RAN4 pre-allocated TUs)

[0027] NOTE 3: To avoid duplicate study with “AI / ML for NG-RAN” led by RAN3 NOTE 4: Two-sided model is not included

[0028] In regard to legacy consideration of prioritization of data transmissions, in 3GPP New Radio (NR), there are different Quality of Service (QoS) flow identifiers that enable differentiating the treatment of each traffic type. Each QoS flow is connected to (i.e., mapped to) a Data Radio Bearer (DRB), but the mapping is not necessarily a one-to-one mapping. Then, the DRBs are connected to logical channels at the Medium Access Control (MAC) layer.

[0029] A QoS Flow Identifier (QFI) is an 8-bit identifier used in 5G to specify the QoS characteristics of individual network data flows. Each QFI corresponds to a particular set of QoS rules, including aspects like priority, packet delay budget, packet error rate, and bit rate. QFI is primarily used to ensure that data flows are provided with the appropriate level of service quality, meeting the specific requirements of different applications, from voice and video communication to bulk data transfer and real-time gaming.

[0030] DRBs are logical connections in the 5G network that carry user data between the User Equipment (UE) and the base station. Each DRB is configured with specific QoS parameters that dictate how the data should be treated in terms of transmission priorities, throughput, and reliability. DRBs are crucial for handling the diversity of service demands in 5G networks, ensuring that everything from low-latency applications to high-throughput services can coexist and operate efficiently.

[0031] In the MAC layer of 5G, logical channels are used to categorize the type of data being transmitted. These channels determine how data is handled within the MAC layer and include:• Dedicated Traffic Channel (DTCH): Used for transmitting user data. Each DRB is linked to one or more DTCHs depending on the type of data and its QoS requirements.

[0032] • Dedicated Control Channel (DCCH): Used for transmitting control plane information.

[0033] Details regarding the connection between QFI and DRBs are as follows.

[0034] Mapping of QoS Flows to DRBs: There are two ways to map DRB and QFI. The first way is individual mapping where each QoS flow, identified by a QFI, is mapped to a DRB. This mapping is crucial because different data flows may require different handling, depending on their QoS demands. The second way is multiple QoS flows per DRB where it is possible for multiple QoS flows (each with a unique QFI) to be multiplexed onto a single DRB if their QoS requirements are sufficiently similar. This efficient use of DRBs helps in optimizing network resources. In regard to configuration and establishment:

[0035] • At Setup: When a DRB is established, the network configures it based on the QoS requirements of the QoS flows it will carry. This configuration process involves assigning a DRB to handle one or more QFI-marked flows.

[0036] • Dynamic Adjustment: DRB configurations can be dynamically adjusted to accommodate changes in network conditions, QoS requirements, or traffic patterns. Mapping of DRBs to DTCH: Each DRB is mapped to one or more Dedicated Traffic Channels (DTCHs) at the MAC layer. This mapping is crucial because DTCHs are responsible for carrying user data corresponding to the QoS flows identified by QoS Flow Identifiers (QFIs) and managed via the DRBs. The mapping ensures that the QoS requirements assigned to the DRB are implemented at the MAC layer, influencing how data is prioritized and scheduled for transmission.

[0037] Mapping to Logical Channels: Each QoS flow, marked by its QFI, is mapped to a logical channel in the MAC layer. The type of logical channel (e.g., Dedicated Traffic Channel - DTCH) and its configuration will depend on the QoS requirements associated with the QFI.

[0038] Logical Channel Prioritization: Within the MAC layer, each logical channel is assigned a priority level based on the QoS requirements of the DRB it supports. This is where Logical Channel Prioritization (LCP) comes into play. LCP determines the order in which data from different logical channels is processed and transmitted, especially when network resources are limited or contested. Higher-priority channels, which carry more critical or sensitive data, are given preferential treatment over lower-priority channels in terms of resource allocation and scheduling. The LCP procedure is applied whenever a new transmission is performed.

[0039] RRC controls the scheduling of uplink data by signaling for each logical channel per MAC entity:

[0040] priority where an increasing priority value indicates a lower priority level;- prioritisedBitRate which sets the Prioritized Bit Rate (PBR);

[0041] bucketSizeDuration which sets the Bucket Size Duration (BSD).

[0042] RRC additionally controls the LCP procedure by configuring mapping restrictions for each logical channel:

[0043] - allowedSCS-List which sets the allowed Subcarrier Spacing(s) for transmission;

[0044] maxPUSCH-Duration which sets the maximum PUSCH duration allowed for transmission;

[0045] configuredGrantType 1 Allowed which sets whether a configured grant Type 1 can be used for transmission;

[0046] allow edServingCells which sets the allowed cell(s) for transmission;

[0047] - allowedCG-List which sets the allowed configured grant(s) for transmission;

[0048] allow edPHY -Priority Index which sets the allowed PHY priority index(es) of a dynamic grant for transmission;

[0049] allow edHARQ-mode which sets the allowed UL HARQ mode for transmission.

[0050] The following UE variable is used for the Logical channel prioritization procedure:

[0051] - Bj which is maintained for each logical channel j.

[0052] The MAC entity initializes Bj of the logical channel to zero when the logical channel is established.

[0053] For each logical channel j, the MAC entity:

[0054] • increments Bj by the product PBR × T before every instance of the LCP procedure, where T is the time elapsed since Bj was last incremented;

[0055] • if the value of Bj is greater than the bucket size (i.e. PBR × BSD):

[0056] o sets Bj to the bucket size.

[0057] Note that the exact moment(s) when the UE updates Bj between LCP procedures is up to UE implementation, as long as Bj is up to date at the time when a grant is processed by LCP.

[0058] SUMMARY

[0059] Systems and methods are disclosed for mobility-related data collection in wireless communication systems, including embodiments involving a User Equipment (UE) and a network node. In one embodiment, a method performed by a UE comprises receiving, from a network node, configuration information that configures the UE for measurements for mobility -related data collection, the measurements for mobility-related data collection comprising measurements on at least one frequency. The method includes performing measurements for mobility-related datacollection in accordance with the received configuration information and in such a manner that performing the measurements for mobility-related data collection does not impair one or more certain procedures or functionalities at the UE. In this manner, the UE is enabled to collect the measurements for the mobility related data collection purpose without impairing other procedures such as Radio Resource Management (RRM) measurements or data transmission in downlink or uplink.

[0060] In one embodiment, performing the measurements for mobility related data collection comprises detecting fulfillment of one or more certain events at the UE, and in response to detecting fulfillment of the one or more certain events at the UE, performing a certain action with respect to the measurements for mobility-related data collection is included.

[0061] In one embodiment, the certain action comprises activating, starting, deactivating, suspending, or stopping the measurements for mobility -related data collection.

[0062] In one embodiment, the one or more certain events are associated to any one or more of performing one or more measurements in one or more frequencies for a purpose of RRM, performing data transmission in uplink or downlink over an uplink or downlink data channel, performing data transmission in uplink over an uplink data channel, performing data transmission in downlink over a downlink data channel, or fulfillment of one or more measurement relaxation conditions.

[0063] In one embodiment, the one or more certain events at the UE comprise performance, at the UE, of one or more measurements at the UE for RRM purpose, and the certain action comprises stopping, suspending, or deactivating the measurements for mobility-related data collection responsive to detecting performance, at the UE, of one or more measurements for RRM purpose.

[0064] In one embodiment, the one or more certain events at the UE comprise a downlink data transmission at the UE over a downlink data channel or an uplink data transmission at the UE over an uplink data channel, and the certain action comprises stopping, suspending, or deactivating the measurements for mobility-related data collection responsive to detecting the downlink data transmission at the UE over a downlink data channel or the uplink data transmission at the UE over an uplink data channel.

[0065] In one embodiment, detecting fulfillment of the one or more certain events at the UE comprises detecting fulfillment of one or more measurement relaxation conditions at the UE or that the UE is performing measurement relaxation, and the certain action comprises starting, resuming, or activating the measurements for mobility-related data collection responsive to detecting fulfillment of one or more measurement relaxation conditions at the UE. In one embodiment, the one or more measurement relaxation conditions comprise any one or more of oneor more conditions for RRM measurement relaxation, one or more conditions for Radio Link Monitoring (RLM) measurement relaxation, or one or more Beam Failure Detection (BFD) measurement relaxation. In one embodiment, the measurement relaxation is RRM measurement relaxation, RLM measurement relaxation, or BFD measurement relaxation.

[0066] In one embodiment, the received configuration for measurements for mobility-related data collection comprises a priority indication. In one embodiment, detecting fulfillment of the one or more events comprises checking the priority indication. In one embodiment, the priority indication indicates whether the UE is to activate, start, deactivate, suspend, or stop the one or more measurements for mobility-related data collection purpose in response to detecting fulfillment of the one or more other events. In one embodiment, the priority indication comprises a prohibition timer indicating a time period for which the UE is to keep the measurements for mobility-related data collection suspended in response to detecting fulfillment of the one or more events and stopping or suspending of the measurements for mobility-related data collection. In one embodiment, the detected event is a data transmission or data reception at the UE, and the priority indication includes a sub-priority of one or more measurements for mobility -related data collection which are to be suspended, deactivated, or stopped in conjunction with a higher data Logical channel priority. In one embodiment, the detected event is a data transmission or data reception, and the priority configuration includes a sub-priority of one or more measurements for mobility-related data collection which will be activated or started in conjunction with a lower data Logical channel priority.

[0067] In one embodiment, performing the certain action comprises fully activating, starting, deactivating, suspending, or stopping the measurements for mobility -related data collection.

[0068] In one embodiment, performing the certain action comprises partially activating, starting, deactivating, suspending, or stopping the measurements for mobility -related data collection.

[0069] In one embodiment, the method further comprises transmitting, to the network node, a status indicator that indicates a status of the measurements for mobility-related data collection is included.

[0070] In one embodiment, the received configuration for measurements for mobility-related data collection comprises a priority indication, and performing measurements for mobility-related data collection comprises performing the measurements for mobility-related data collection in accordance with the received configuration information including the priority indication.

[0071] In one embodiment, the method further comprises reporting results of the measurements for mobility-related data collection to the network node or another network node is included. In one embodiment, the method further comprises reporting information about how long themeasurements for mobility -related data collection were deactivated, suspended, or stopped. In one embodiment, the method further comprises reporting includes reporting a cause or reason for why the measurements or at least some of the measurements for mobility -related data collection were not collected. In one embodiment, the method further comprises reporting an indication that the measurements for mobility -related data collection were deactivated, suspended, or stopped. In one embodiment, the measurement configuration for RRM received by the UE from the network node or another network node that configures the UE to perform measurements for RRM comprises an indication that indicates whether mobility-related data collection on other frequencies is allowed while performing measurements based on the RRM measurement configuration.

[0072] In one embodiment, the configuration information comprises an indication that indicates whether measurements for mobility-related data collection on other frequencies is allowed while the UE performs RRM measurements on a serving and / or neighboring frequencies.

[0073] In one embodiment, the method further comprises transmitting, to the network node, capability information that indicates that the UE is capable of performing measurements for mobility-related data collection as recited is included.

[0074] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE for mobility-related data collection comprises a communication interface comprising a transmitter and a receiver, and processing circuitry associated with the communication interface, the processing circuitry configured to cause the UE to receive, from a network node, configuration information that configures the UE for measurements for mobility-related data collection, the measurements for mobility-related data collection comprising measurements on at least one frequency, and to perform measurements for mobility-related data collection in accordance with the received configuration information and in such a manner that performing the measurements for mobility -related data collection does not impair one or more certain procedures or functionalities at the UE.

[0075] In one embodiment, the processing circuitry is further configured to cause the UE to perform any of the method embodiments described above.

[0076] Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node for mobility-related data collection from a UE comprises transmitting, to a UE, configuration information that configures the UE for measurements for mobility-related data collection, the measurements for mobility-related data collection comprising measurements on at least one frequency.Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for mobility-related data collection from a UE comprises processing circuitry configured to cause the network node to transmit, to a UE, configuration information that configures the UE for measurements for mobility-related data collection, the measurements for mobility-related data collection comprising measurements on at least one frequency.

[0077] BRIEF DESCRIPTION OF THE DRAWINGS

[0078] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0079] Figure 1 illustrates a procedure involving a User Equipment (UE) and a network node that enables the UE to collect measurements for mobility related data collection for model training without impairing one or more other procedures, in accordance with embodiments of the present disclosure.

[0080] Figure 2 shows an example of a communication system in which embodiments of the present disclosure may be implemented.

[0081] Figure 3 is another example of a communication system according to some embodiments. Figure 4 shows a wireless device, which may be configured to operate in communication system of Figure 2 or in communication system of Figure 3.

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

[0083] Figure 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0084] DETAILED DESCRIPTION

[0085] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0086] 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.There currently exist certain challenge(s). As discussed in the Background section above, the 3rdGeneration Partnership Project (3GPP) Release (Rel-) 19 Artificial Intelligence (AI) / Machine Learning (ML) for Mobility study item (see RP -234055) states that the data collection procedure for the model training should be discussed as part of the study item. The study of the Life Cycle Management (LCM) and data collection will start from the meeting RAN2#129bis meeting in April 2025.

[0087] As can be inferred from the Study Item Description (SID) found in RP -234055, in order to train AI / ML models at the network side (or even for the User Equipment (UE) sided models), the UE should be configured to collect measurements for the model training. Such data collection configuration can instruct the UE to perform inter-frequency measurements. In the present disclosure, such measurements are referred to as “measurement for mobility related data collection”. However, measurement for mobility related data collection may not be treated as the highest priority process for the UE to perform as data collection and model training is a slow process that does not require immediate network actions upon reception of such measurements and data.

[0088] Given that some of the data should be collected in non-serving frequencies, the data collection framework can jeopardize other higher priority processes running at the UE. For example, performing inter-frequency measurements for mobility related data collection for model training requires using measurement gaps and if the UE instead of performing Radio Resource Management (RRM) measurements (in some other frequencies) performs mobility related data collection, this may delay reporting RRM measurements to the network, which can lead to radio link failure or a handover failure if the network cannot make a proper mobility decision based on the delayed measurement report. Even for intra-frequency / inter-frequency measurements performed outside of measurement gaps, the measurements for mobility related data collection also delay reporting RRM measurements since it occupies the search engine(s) originally serving legacy (not for data collection) measurements.

[0089] Another example is the data transmission in uplink or downlink. If the UE uses measurement gaps to perform inter-frequency measurements for the mobility related data collection for model training, transmission of data in downlink and uplink might be delayed (i.e., scheduling restriction), which in turn can jeopardize the UE’s quality of service requirements.

[0090] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Systems and methods are disclosed herein that relate to priority handling between data collection for AI / ML model training and one or more other immediate procedures. Embodiments of a method performed by a UE are disclosed, wherein the method enables the UEto collect measurements for mobility related data collection for model training without impairing other procedures such as, e.g., RRM measurements and / or uplink (UL) / downlink (DL) data transmissions. In one embodiment, the method performed by the UE comprises the following. The UE receives, from a network node, a data collection configuration for mobility related data collection for model training. The configuration includes implicit or explicit priority indication, which may also be referred to herein as a priority configuration or priority information. Based on the priority indication, the UE performs measurements for the mobility related data collection in accordance with the received configuration. In particular, the UE performs measurements for the mobility related data collection in accordance with the received configuration and in particular based on the received priority indication such that the UE performs the measurements for the mobility related data collection without impairing one or more other procedures of the UE (e.g., without impairing RRM measurements performed by the UE and / or without impairing UL / DL data transmissions at the UE).

[0091] In one embodiment, the UE activates, starts, deactivates, suspends, or stops the measurements for the mobility related data collection upon receiving the configuration and if corresponding certain event(s) is(are) detected by the UE. The events can be explicitly configured by the network or can be implicitly derived. For example, an event can be configured with RRM measurements or transmission of DL / UL traffics or it can be fulfilment of RRM measurement relaxation criteria and performing measurements in relaxed mode.

[0092] In an alternative solution, the handling of prioritization between impacting RRM measurements and / or data transmissions is left to UE implementation. The UE is configured with an indication indicating that certain measurements are for model training purposes. Based on this indication, the UE performs data collection for model training based on best effort. This solution can be combined with other parts of present disclosure, e.g. measurement priorities can be configured also in this alternative solution.

[0093] Some exemplary embodiments of the present disclosure are as follows. In a first embodiment, a method at a UE for activating, starting, deactivating, suspending, or stopping measurements for mobility related data collection purpose comprises:

[0094] • Being configured with one or more measurements on at least one frequency for mobility related data collection purpose;

[0095] • Detecting fulfilment of one or more event(s) at the UE;

[0096] • Determining to activate, start, deactivate, suspend, or stop the measurements for data collection purpose (e.g., responsive to detecting fulfilment of the event(s) at the UE) • wherein the event(s) can be associated with any one or more of the following:o performing one or more measurements in one or more frequencies for RRM purpose,

[0097] o performing data transmission in uplink or downlink over the data channels o fulfilment of one or more measurement relaxation condition

[0098] A second embodiment is the method of the first embodiment, wherein the UE stops, suspends, or deactivates one or more measurements for mobility related data collection purpose if the event is performing one or more measurements for RRM purpose.

[0099] A third embodiment is the method of the first embodiment, wherein the UE stops, suspends, or deactivate one or more measurements for mobility related data collection purpose if the event is performing data transmission in DL or UL over data channels such as Physical Downlink Shared Channel (PDSCH) and / or Physical Uplink Shared Channel (PUSCH).

[0100] A fourth embodiment is the method of the first embodiment, wherein the UE starts, resumes, or activates one or more measurements for mobility related data collection purpose if the event is fulfillment of measurement relaxation according to the received relaxation configuration. The measurement relaxation can be any one or more of the following

[0101] • RRM measurement relaxation,

[0102] • Radio Link Monitoring (RLM) measurement relaxation,

[0103] • Beam Failure Detection (BFD) measurement relaxation.

[0104] A fifth embodiment is the method of the first embodiment, wherein the one or more event(s) for activating, starting, deactivating, suspending, or stopping one or more measurements for mobility related data collection purpose comprises checking a priority indication received by the UE from the network.

[0105] A sixth embodiment is the method of the fifth embodiment, wherein the priority indication received by the UE from the network indicates whether the UE is to activate, start, deactivate, suspend, or stop the one or more measurements for mobility related data collection purpose in conjunction with detecting the other events such as RRM measurements, data transmission, or measurement relaxation.

[0106] A seventh embodiment is the method of the fifth or sixth embodiment, wherein the priority indication includes a prohibition timer indicating a time period for which the UE is to keep the one or more measurements for mobility related data collection purpose suspended in conjunction with detecting the other event(s) and stopping or suspension of the one or more measurements for mobility related data collection purpose.

[0107] An eighth embodiment is the method of the fifth or sixth embodiment, wherein, in case the detected event is a data transmission or data reception, the priority indication includes a sub-priority of one or more measurements for mobility related data collection purpose which are to be suspended, deactivated, or stopped in conjunction with a higher data Logical channel priority.

[0108] A ninth embodiment is the method of the fifth or sixth embodiment, wherein, in case the detected event is a data transmission or data reception, the priority configuration includes a subpriority of one or more measurements for mobility related data collection purpose which will be activated or started in conjunction with a lower data Logical channel priority.

[0109] Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the solutions described herein may enable a UE to collect the measurements for the mobility related data collection purpose without impairing other procedures such as RRM measurements or data transmission in downlink or uplink. In other words, embodiments of the solutions described herein may enable the UE to run the measurement collections for the mobility related data collection for mode training with lower priority compared to the other high priority tasks such as RRM measurements for the immediate mobility decisions by the UE as well as UL / DL data transmission.

[0110] The teachings of certain embodiments may improve, e.g., data rate, latency, and / or power consumption.

[0111] The terms “activation” and “start” of measurements for mobility related data collection are used herein interchangeably and refer to starting a process in the UE for performing measurements e.g., inter-frequency measurements and logging them in a memory. These words can be replaced with the term “resume” or “restart” if the data collection process was already suspended, stopped, deactivated, or paused at the UE.

[0112] The terms “suspend”, “stop”, “deactivate”, and “pause” of measurements for mobility related data collection are used herein interchangeably and refer to stopping a process in the UE for performing measurements e.g., inter-frequency measurements and logging them in a memory.

[0113] The terms “measurement” or “real / current measurement” and RRM measurements are used herein to refer to a radio measurement, such as the measurements described in the RRC specifications (i.e., 3GPP Technical Specification (TS) 38.331, e.g., V18.1.0) in sub-clause 5.5 that may be configured by the network for a CONNECTED UE and / or measurements defined in 3GPP Technical Specification (TS) 38.215, e.g., V18.1.0. These measurements may also be called Radio Resource Management (RRM) measurements (since they assist Radio Resource Management decisions at the network side and / or Layer 3 (L3) measurements, since they are responsibility of the RRC protocol, also called Layer 3 in the Control Plane Radio Access Network (RAN) protocol stack). In the scope of embodiments of the present disclosure, using New Radio(NR) as an example, these measurements to be performed by the UE and reported may include at least one of the following:

[0114] - NR measurements;

[0115] - Inter-Radio Access Technology (RAT) measurements of Evolved Universal Terrestrial Radio Access (E-UTRA) frequencies.

[0116] - Measurements defined for 6G i.e. based on reference signals and / or synchronization signals defined in 6G air interface.

[0117] These measurements may be based on different reference signals. In the case of Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block(s) (SSB(s) or SS / PBCH block(s)), these measurements (or in more general terms, measurement information) are:

[0118] - Measurement results per SS / PBCH block;

[0119] - Measurement results per cell based on SS / PBCH block(s);

[0120] SS / PBCH block(s) indexes.

[0121] In the case of Channel State Information (CSI) Reference Signal (CSI-RS) these measurements (or in more general terms, measurement information) are:

[0122] - Measurement results per CSI-RS resource;

[0123] - Measurement results per cell based on CSI-RS resource(s);

[0124] CSI-RS resource measurement identifiers.

[0125] Each of these measurements may be associated to a measurement quantity, such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), or Signal to Interference plus Noise Ratio (SINR). For example, in the present disclosure, the description talks about a real / current measurement as the cell level or beam level RSRP based on Reference Signal (RS) type SSB, for an NR carrier frequency in the NR RAT. Hence, the term “measurement prediction” is used to refer to a prediction of a radio measurement as one of the measurements described above as a real / current measurement. In other words, the description refers to a prediction of NR or inter-RAT measurements, prediction of measurement results per RS type (i.e. SS / PBCH block or CSI-RS), prediction of cell measurement or beam measurements (e.g. cell level RSRP, cell level RSRQ, cell level SINR, beam level RSRP, beam level RSRQ, beam level SINR).

[0126] According to embodiments of the solutions described herein, these real / current measurements (or simply RRM measurements) may be used as input to predictions models so the UE is able to predict, as output of the AI / ML model, mobility information such as radio quality related parameters such as RSRP, RSRQ, SINR in a given frequency in different levels of granularities such as per cell, per beam, per RS type like SSB and / or CSI-RS, list of cells and / orlist of beams and / or list of RS type coverage (like SSB identifier coverage or CSI-RS identifier coverage) the UE is moving to, etc.

[0127] Even if most of the examples referred to herein are for NR, that may be applied to any system, e.g., in the 6G context, where AI / ML is envisioned to play a more impactful role when it comes to the design of protocols.

[0128] In the present disclosure, the term “legacy event” is used to refer to the mobility related events existing in the RRC TS 38.331 Version 18.1.0. such as A1-A6 events etc. wherein the input to the evaluation of the entering condition and exist conditions for such events is based on the RRM “measurements”.

[0129] Figure 1 illustrates a procedure involving a UE 100 and a network node 102 that enables the UE 100 to collect measurements for mobility related data collection for model training without impairing one or more other procedures (e.g., RRM measurements and / or UL / DL data transmissions), in accordance with embodiments of the present disclosure. Optional steps are represented in Figure 1 by dashed lines or dashed boxes. The network node 102 may be a RAN node such as, e.g., a base station (e.g., a gNB or 6G base station) or a RAN node that performs pat of the functionality of a base station (e.g., a Central Unit (CU) such as a gNB-CU or a Distributed Unit (DU) such as a gNB-DU of a base station having a CU-DU split architecture.

[0130] As illustrated in Figure 1, optionally, the UE 100 sends, to the network node 102, capability information that indicates at the UE 100 supports the feature according to embodiments of the present disclosure in which the UE 100 collects measurements for mobility related data collection for AI / ML model training without impairing one or more certain other procedures or functionalities at the UE 100 (step 103). Further details regarding such capability signaling are described below.

[0131] The UE 100 receives, from the network node 102, a data collection configuration for mobility related data collection for AI / ML model training (step 104). The data collection configuration configures the UE 100 for measurements for mobility related data collection purpose, where these measurements include measurements on at least one frequency. In some embodiments, the configuration includes or is otherwise associated with an implicit or explicit priority indication (also referred to herein as a priority configuration or priority information) for measurements for mobility related data collection, e.g., relative to one or more other certain procedures or functionalities of the UE 100 such as, for example, RRM measurements, UL data transmission, and / or DL data transmission.

[0132] The UE 100 performs measurements for the mobility related data collection in such a manner as to not impair the other procedure(s) or functionality(ies) (step 106). As discussed below,in some embodiments, the UE 100 performs the measurements for the mobility related data collection in prioritized manner (e.g., in accordance with the priority indication of step 104 if present) in relation to the one or more other certain procedures or functionalities of the UE 100 such that UE 100 performs the measurements for the mobility related data collection without impairing the other procedures or functionalities of the UE 100. As described below in detail, in some embodiments, step 106 includes the UE 100 detecting that one or more events at the UE 100 are fulfilled (i.e., have occurred) (step 106A) and, in response thereto, performing an associated action in relation to the measurements for mobility related data collection (e.g., activates, starts, deactivates, suspends, or stops (partially or fully) the measurements for mobility related data collection) (step 106B). Details regarding various embodiments and examples of events for which the UE 100 monitors and the associated actions performed by the UE 100 in response thereto are described below. Note that steps 106 A and 106B may be repeated where the UE 100 monitors for certain events and, upon detecting a certain event, performs an associated action relative to the measurements for mobility data collection (i.e., activates, starts, deactivates, suspends, or stops the measurements for mobility data collection, partially or fully). Also, as discussed below, in some embodiments, the UE 100 may send, to the network node 102, a status of the measurements (step 107).

[0133] The UE 100 may report the measurements for the mobility related data collection, a subset of the measurements for the mobility related data collection, and / or information derived therefrom to, in this example, the network node 102 (step 108).

[0134] Non-limiting examples of how the UE 100 prioritizes the measurements for the mobility related data collection with respect to the one or more other procedures (e.g., RRM measurements and / or UL / DL data transmissions) are described below.

[0135] Example embodiments related to the RRM measurements:

[0136] If the UE 100 is configured with inter-frequency measurements as part of RRM for mobility purpose (the measurements based on which the network takes mobility actions), the UE 100 (e.g., in step 106) does not perform inter-frequency measurements for the mobility related data collection or the UE 100 stops, suspends, or deactivates inter-frequency measurements for the mobility related data collection when performing RRM measurements for mobility decisions.

[0137] In an example, the UE 100 is configured with A4 event for Primary Secondary Cell (PSCell) addition or change on the frequency different than the serving frequency. The UE 100, when performing A4 event related measurements, does not perform the mobility related data collection related measurements, if such configuration is received from the network node 102. The UE 100 may start the mobility related data collection related measurements when the A4 relatedmeasurements is reported to the network and / or A4 related configuration is released by the network (e.g., by the network node 102).

[0138] In another example, the UE 100 is already performing inter-frequency measurements for mobility related data collection. The UE 100 is then configured with A4 event for PSCell addition or change on the frequency different than the serving frequency. When performing A4 event related measurements, the UE 100 stops, suspends, or deactivates performing the inter-frequency measurements for the mobility related data collection related measurements. The UE 100 may restart / resume the mobility related data collection related measurements, when the A4 related measurements is reported to the network and / or A4 related configuration is released by the network.

[0139] In another example, the UE 100 is configured with A4 event for PSCell addition or change on the frequency different than the serving frequency. The UE 100, when performing A4 event related measurements, does not perform the mobility related data collection related measurements (e.g. logged RRM measurement configuration, logged RRM measurement configuration via MeasConfig from the network to UE) which have impact on this A4 event related measurements.

[0140] In another example, the UE 100 is configured with A4 event for PSCell addition or change on the frequency different than the serving frequency. The UE 100, when performing A4 event related measurements, does not perform the mobility related data collection related measurements (e.g. the measurement configuration associated with low priority information for data collection).

[0141] In another example, the UE 100 is already performing inter-frequency measurements for mobility related data collection. The UE 100 is then configured with A4 event for PSCell addition or change on the frequency different than the serving frequency. When performing A4 event related measurements, the UE stops, suspends, or deactivates performing the inter-frequency measurements for the mobility related data collection related measurements, but the UE 100 may restart or resume the mobility related data collection related measurements which have no impact on the A4 related measurements.

[0142] In another example, the UE 100 is configured with A5 event for an inter-frequency handover. When performing A5 event related measurements, the UE 100 does not perform the mobility related data collection related measurements. The UE 100 starts inter-frequency measurements for mobility related data collection when the measurement report is sent to the network or when the network reconfigures the A5 related measurement configuration.

[0143] In another example, the UE 100 is already performing inter-frequency measurements for mobility related data collection. The UE 100 is then configured with A5 event for inter-frequency handover. When performing A5 event related measurements, the UE 100 stops or suspendsperforming the inter-frequency measurements for the mobility related data collection related measurements. The UE 100 may restart or resume the mobility related data collection related measurements, when the A5 related measurements is reported to the network and / or A5 related configuration is released by the network.

[0144] In another example the UE 100 is configured with A5 event for an inter-frequency handover. When performing A5 event related measurements, the UE 100 does not perform the mobility related data collection related measurements (e.g. logged RRM measurement configuration, logged RRM measurement configuration via MeasConfig from the network to UE) which have impact on this A5 event related measurements.

[0145] In another example, the UE 100 is configured with A5 event for an inter-frequency handover. The UE 100, when performing A5 event related measurements, does not perform the mobility related data collection related measurements (e.g. the measurement configuration associated with low priority information for data collection).

[0146] In another example the UE 100 is already performing inter-frequency measurements for mobility related data collection. The UE 100 is then configured with A5 event for inter-frequency handover. When performing A5 event related measurements, the UE 100 stops or suspends performing the inter-frequency measurements for the mobility related data collection related measurements, but the UE 100 may restart or resume the mobility related data collection related measurements which have no impact on the A5 event related measurements.

[0147] In an embodiment, the UE 100 (e.g., in step 106) suspends measurement for the mobility related data collection purpose only for the neighboring frequencies configured for data collection which are not among the frequencies configured for RRM measurement purpose (i.e., for immediate mobility decisions).

[0148] In an embodiment, the UE 100 (e.g., in step 106) suspends measurement for the mobility related data collection purpose only for the neighboring frequencies configured for data collection which requests additional radio frequency (RF) switching at the UE side to support these measurements.

[0149] In an embodiment, the UE 100 is configured with a prohibition timer. The UE 100 (e.g., in step 106) starts the prohibition timer after finishing the RRM measurements. When the prohibition timer is running, the UE 100 is not allowed to (e.g., the UE 100 does not in step 106) perform inter-frequency measurements for mobility related data collection purpose. The UE 100 starts the inter-frequency measurements for mobility related data collection purpose only when the prohibition timer expires. In an option, the UE 100 starts the inter-frequency measurements formobility related data collection purpose only when the prohibition timer expires, and the network has not configured any other RRM measurements.

[0150] In an embodiment, the UE 100 is configured with a prohibition timer. When the prohibition timer is running, the UE 100 is not allowed to (e.g., the UE 100 does not in step 106) perform inter-frequency measurements for mobility related data collection purpose which requires RF switching. The UE 100 starts the inter-frequency measurements for mobility related data collection purpose which requires RF switching when the prohibition timer expires. In an option, the UE 100 starts the inter-frequency measurements for mobility related data collection purpose which requires RF switching when the prohibition timer expires.

[0151] Example embodiments related to the uplink / downlink traffic:

[0152] If the UE 100 is configured with inter-frequency measurements as part of mobility related data collection (e.g. logged RRM measurement configuration, logged RRM measurement configuration via MeasConfig), if the UE 100 receives a traffic in uplink buffer to be transmitted in uplink, the UE 100 (e.g., in step 106) stops, suspends, deactivates (if already running) the interfrequency measurements for the data collection purpose. In particular, if the traffic in uplink buffer to be transmitted in uplink whose symbols collide or are placed close to the symbols used for measurements for the data collection purpose, the UE 104 stops, suspends, or deactivates (if already running) the inter-frequency measurements for the data collection purpose.

[0153] If the UE 100 is configured with inter-frequency measurements as part of mobility related data collection, if the UE 100 receives a downlink traffic to be received in downlink channel, the UE (e.g., in step 106) stops, suspends, or deactivates (if already running) the inter-frequency measurements for the data collection purpose. In particular, if the traffic in downlink buffer to be transmitted in downlink whose symbols collide or place close to the symbols used for measurements for the data collection purpose, the UE 100 (e.g., in step 106) stops, suspends, or deactivates (if already running) the inter-frequency measurements for the data collection purpose.

[0154] In an embodiment, the UE 104 is configured with a prohibition timer. The UE 104 starts the prohibition timer after transmitting or receiving the uplink or downlink data. When the prohibition timer is running, the UE 104 is not allowed to (e.g., the UE 104 does not in step 106) perform inter-frequency measurements for the data collection purpose. The UE 104 starts the inter-frequency measurements for the data collection purpose only when the prohibition timer expires. In an option, the UE 104 starts the inter-frequency measurements for the data collection purpose only when the prohibition timer expires, and the UE 104 does not receive any new downlink data or does not need to transmit any uplink data.

[0155] Example embodiments related to the measurement relaxation:If the UE 104 is configured with inter-frequency measurements as part of mobility related data collection, if the UE 104 fulfils the measurement relaxation criteria, the UE 104 (e.g., in step 106) starts, resumes, or activates the inter-frequency measurements for mobility related data collection purpose.

[0156] In an option, if the UE 104 is configured with inter-frequency measurements as part of mobility related data collection, if the UE 104 relaxes the RRM measurements (i.e., if the RRM relaxation criteria is fulfilled, provided there are at least two RRM measurement rules / requirements, one is normal / non-relaxed, the other one is relaxed), the UE 104 (e.g., in step 106) starts, resumes, or activates (if already suspended / deactivated) the inter-frequency measurements for mobility related data collection purpose. The UE 104 may stop, suspend, or deactivate (if data collection is already running) the measurement collections if the RLM measurement relaxation criteria is not fulfilled anymore. Particularly, if the UE 104 is configured with inter-frequency measurements as part of mobility related data collection, and the if the UE 104 detects the received signal quantity / quality (or change of signal quantity / quality in a time period) from the cell involved in RRM measurements is higher than a threshold, the UE 104 (e.g., in step 106) starts, resumes, or activates (if already suspended / deactivated) the inter-frequency measurements for mobility related data collection purpose. The UE 104 may stop, suspend, or deactivate (if data collection is already running) the measurement collections if the UE 104 detects the received signal quantity / quality (or change of signal quantity / quality in a time period) from the cell involved in RRM measurements is lower than a threshold.

[0157] In an option, if the UE 104 is configured with inter-frequency measurements as part of mobility related data collection, if the UE 104 relaxes the RLM measurements (if the RLM relaxation criteria is fulfilled), the UE 104 (e.g., in step 106) starts, resumes, or activate (if already suspended / deactivated) the inter-frequency measurements for mobility related data collection purpose. The UE 104 may stop, suspend, or deactivate (if data collection is already running) the measurement collections if the RLM measurement relaxation criteria is not fulfilled anymore.

[0158] In an option, if the UE 104 is configured with inter-frequency measurements as part of mobility related data collection, if the UE 104 relaxes the BFD measurements (if the BFD relaxation criteria is fulfilled), the UE 104 (e.g., in step 106) starts, resumes, or activate (if already suspended / deactivated) the inter-frequency measurements for mobility related data collection purpose. The UE 104 may stop, suspend, or deactivate (if data collection is already running) the measurement collections if the BFD relaxation criteria is not fulfilled anymore.

[0159] In an embodiment, the UE 104 can be configured with a prohibition timer. The UE starts the prohibition timer when the RRM or RLM or BFD relaxation criteria is fulfilled. When theprohibition timer is running, the UE 104 is not allowed to (e.g., does not in step 106) perform interfrequency measurements for the data collection purpose. The UE 104 starts the inter-frequency measurements for the data collection purpose only when the prohibition timer expires. In an option, the UE 104 starts the inter-frequency measurements for the data collection purpose only when the prohibition timer expires, and at least one or all the relaxation criteria are still fulfilled.

[0160] Extension to allow partial activation / deactivation of the data collection procedure The embodiments described thus far enable the UE 100 to assure the normal (or high priority) measurements as well as data transmissions work properly at the UE 100 and are not impaired by the inter-frequency measurements the UE 100 performs for the mobility related data collection purpose. However, in some scenarios, the network might be interested in collecting and receiving the measurements for mobility related data collection from the UE 100 in scenarios in which the other functionalities e.g., RRM measurements are running at the UE 100 (e.g., data collection at cell edge where the UE 100 normally performs more inter-cell or inter-frequency RRM measurements).

[0161] Given that the embodiments described above may deactivate the entire data collection process, in the following, an extension is described in which the activation and deactivation of the mobility related data collection is performed partially. This means that, in the described scenarios above (RRM measurements or UL / DL data transmission), the UE partially stops, suspends, or deactivates some of the inter-frequency measurements for mobility related data collection purpose and continues with the inter-frequency measurements for data collection on some other frequencies.

[0162] Extension using an indication in the RRM measurement configuration

[0163] In an embodiment, in addition to the measurement configuration for the RRM purpose or as part of such measurement configuration, the network configures the UE 100 with an indication of whether mobility related data collection on other frequency(ies) is allowed while performing measurements based on this measurement configuration.

[0164] In an embodiment, the network configures an indication in the reportConfig associated with this measurement configuration (measConfig) if the inter-frequency measurements for the mobility related data collection are allowed for other frequencies when the UE performs measurements on the frequency associated to this measurement configuration. This approach enables the network to be selective on setting the priority depending on which event is configured for this measurement. For example, if the network configured A5 event as part of reportConfig for the sake of inter-frequency handover, the network may not include the indication (i.e., instructs the UE to deactivate the data collection process). However, if the network configures the A4 eventfor this measurement configuration for the sake of PSCell Addition / change, it may also include the indication, allowing the UE to perform inter-frequency measurements for the sake of mobility related data collection on other frequencies.

[0165] In an embodiment, the network configures an indication in the measObject associated with this measurement configuration (measConfig) if the inter-frequency measurements for the mobility related data collection is allowed for other frequencies when the UE performs measurements on the frequency associated to this measurement configuration. This approach enables the network to set one priority for which is applicable to all the reportConfig associated with this measurement object (measObject), instead of setting such priority per reportConfig.

[0166] Extension using an indication in the data collection configuration

[0167] In another embodiment, in addition to (e.g., along with) or as part of the measurement configuration for the mobility related data collection purposes, the network configures the UE with an indication of whether mobility related data collection on this frequency is allowed while performing RRM measurements on serving or other neighboring frequencies. In a non-limiting example, if the indication is included the UE continue performing measurements on this frequency when the RRM measurement is running at the UE. If the indication is not included in the measurement configuration for the mobility related data collection, the UE deactivates / stops / suspends the measurement on this frequency if the RRM measurement is running. If deactivated, the UE may start / resume / activate the data collection process if the RRM measurement is finished or reconfigured by the network. In another embodiment if the prohibition timer is configured the UE may start / activate / resume the measurement on this frequency if the prohibition timer expires after the RRM measurements.

[0168] In another embodiment, in addition to (or as part of) the measurement configuration for the mobility related data collection purpose, the network configures the UE with an indication of whether mobility related data collection on this frequency is allowed when the UE is performing DL or UL data transmission. In a non-limiting example, if the indication is included the UE continues performing measurements on this frequency when DL / UL data transmission is ongoing. The UE deactivates / stops / suspends the measurement on this frequency when RRM measurement is running and if the indication is not included in the measurement configuration for the mobility related data collection. If deactivated, the UE may start / resume / activate the data collection process if the DL / UL data transmission is finished. In another embodiment if the prohibition timer is configured the UE may start / activate / resume the measurement on this frequency if the prohibition timer expires after the data transmission.In an option, the network includes the priority indication in the measurement configuration (measConfig) associated to the measurements for mobility related data collection purpose.

[0169] In another option, the network includes the priority indication in the logging configuration (loggingConfig) associated to the measurements for mobility related data collection purpose. The logging configuration instructs the UE how / when to log the data for mobility related data collection purpose.

[0170] In yet another option, the network includes the priority indication in the measurement object configuration (measObject) associated to the measurements for mobility related data collection purpose.

[0171] In an option, the network configures the data collection priority as part of a separate list of priorities wherein each entry in the list refers to a priority of a measurement for mobility related data collection. The list may include non-binary values (Integer values) wherein each value indicates the priority of the measurement over the other measurements to be considered by the UE when performing measurements over multiple frequencies. When selecting the frequency to switch the RF and performing the measurements the UE makes sure that there is no higher priority measurements to be performed prior to this measurement according to the provided priority values in the list. In an option the priority list might be only limited to the measurement objects / configurations associated to the mobility related data collection. In another option, the list may include the priorities associated to all the measurement objects / configurations irrespective of whether they are configured for the RRM purpose or for the mobility related data collection purpose.

[0172] In an option, the priority list may associate the measurement priority with the measID. In another option the priority list may associate the measurement priority with the reportConfigID. In yet another option, the priority list may associate the measurement priority with the measObjectID. In another option the priority list may associate the measurement priority with the logging config ID.

[0173] Logging information in the report upon activation / deactivation of the data collection process at the UE

[0174] In an embodiment, the UE 100 upon stopping, suspending, or deactivating the measurements for the mobility related data collection, includes in the report (e.g., the report of step 108) an indication indicating for how long the measurement logging process was stopped, suspended, or deactivated.

[0175] The UE 104 may include the time information indicating for how long the process was stopped, suspended, or deactivated. The time information can be relative time with respect to thestart time of the data collection process or it can be absolute timestamp of each measurement sample.

[0176] In another option, the UE 104 may log for how long the measurement for data collection purpose was suspended prior to logging the current sample since the last logged sample.

[0177] Such time information can be logged per each frequency that UE 104 logs the measurement as part of mobility related data collection process.

[0178] In another embodiment, the UE may include an indication on a cause or reason that the measurements for the mobility related data collection were not logged, for instance “logging suspended due to RRM measurements”, “logging suspended due to UL / DL traffic” or “logging suspended due to measurements relaxation”.

[0179] In another embodiment, the UE includes an indication, indicating that the measurements were stopped, suspended, or deactivated, but no additional information related to time or reason for the stop.

[0180] Indicating the data collection process status to the network

[0181] In one embodiment, the UE 100 upon starting, stopping, suspending, or resuming the data collection process based on the priority configuration and the relevant events occurring at the UE (e.g., performing RRM measurements for mobility purpose or UL / Dl data transmission) indicates to the network the status of the data collection procedure (e.g., via an additional notification sent from the UE 100 to the network node 102 in Figure 1; see, e.g., step 107).

[0182] In an embodiment, the UE 100 is configured (e.g., as part of otherConfig) to indicate the status of the mobility related data collection as part of UE assistance information procedure. The UE 100 uses UE assistance information message to the network indicating the status of the mobility related data collection process

[0183] In an embodiment, the UE 100 upon start / stop / suspend / resume of the data collection process based on the priority configuration and the relevant events occurring at the UE (e.g., performing RRM measurements for mobility purpose or UL / Dl data transmission) indicates to thenetwork the status of the data collection procedure via an RRM measurement report. In an option the network configures whether the UE should provide the data collection status as part of RRM measurement report or not.

[0184] In an embodiment, the UE 100 upon start / stop / suspend / resume of the data collection process based on the priority configuration and the relevant events occurring at the UE 100 (e.g., performing RRM measurements for mobility purpose or UL / Dl data transmission) indicates to the network the status of the data collection procedure via Uplink Control Information (UCI) signaling to the lower layers of the network node e.g., to the distributed unit. In an option the networkconfigures whether the UE should provide the data collection status as part of RRM measurement report or not. In an option the network configures whether the UE should provide the data collection status as part of lower layer UCI signaling to the lower layers of the network or not. Such configuration can be sent to the UE either as part of RRC signaling or as part of the lower layer configuration.

[0185] By receiving such indication, the network (e.g., the network node 102) can determine whether the UE 100 uses the measurement gaps for the inter-frequency measurements for the data collection purpose or not. If the UE 100 suspends the inter-frequency measurements for the mobility related data collection, the network understands that the UE 100 does not use the configured measurement gaps and hence can use the measurement gaps time slots for the data transmission to the UE 100.

[0186] UE capabilities

[0187] Prior to the steps described above, e.g., in step 103 of Figure 1, the UE 100 may have indicated support for prioritization of measurements for the mobility related data collection or (partial) activation or deactivation of such measurements so as to not impair other functionality(ies) (e.g., RRM measurements and / or UL / DL data transmissions) by signaling of UE capability(es). The UE capability may e.g. indicate support for reporting of measurements for mobility related data collection purpose. In one option, there is a UE capability for the support on the measurement prioritization functionality support of the UE. In one option, there is a UE capability for the support on indicating to the network whether the status of the measurement for mobility related data collection (statuses such as stopped / paused / suspended / resumed) can be reported to the network e.g., via UE assistance information or not. The UE capabilities may be further detailed, e.g. support for prioritization of measurements per each / group of frequencies, per frequency band, per frequency band combination, per frequency range etc.

[0188] Detailing on prioritization with respect to data transmission / reception:

[0189] As noted the Background section, there is a clear connection of QoS Flow Identifier (which represent different service priority) to Data Radio bearers (which are a logical connection between UE and gNB) to MAC logical channels (DTCH or DCCH). So, in terms of priority, QoS flow ID (QFI) represents traffic priority, and MAC’S logical channels also have a priority term that differentiates between which data to send first and how much data to send within the Transport Blocks (TBs).

[0190] To connect the proposed measurement (for mobility related data collection purpose) priority (for mobility related data collection purpose) to data transmission priorities (QFI orMAC’S LCH priority), in one embodiment, a measurement alt-priority is proposed. This should be relevant to the data transmission priority indicators.

[0191] In a follow-up embodiment, the measurement alt-priority (translated priority configuration) is compared to the event of data transmission’s QFI. If alt-priority is higher than QFI, then the UE 100 activates or starts the measurement.

[0192] In a follow-up embodiment, the measurement alt-priority (translated priority configuration) is compared to the event of data transmission’s QFI. If alt-priority is lower than QFI, then the UE 100 deactivates, stops, or suspends the measurement.

[0193] In another follow-up embodiment, the measurement alt-priority (translated priority configuration) is compared to the event of data transmission’s MAC’S LCH priority, and if alt-priority is higher than MAC’S LCH priority, then the UE 100 activate or start the measurement.

[0194] In a follow-up embodiment, the measurement alt-priority (translated priority configuration) is compared to the event of data transmission’s MAC’S LCH priority. If alt-priority is lower than MAC’s LCH priority, then the UE deactivates, stops, or suspends the measurement.

[0195] In an alternative solution, the handling of prioritization is left to UE implementation. The UE 100 is configured with an indication indicating that certain measurements are for model training purposes. Based on this indication, the UE 100 determines the priorities in the implementation and ensures that collection of measurements for the model training does not impact other, more important procedures. The measurement collection for training is done based on best effort in the UE.

[0196] This solution can be combined with other parts of the present disclosure, e.g. measurement priorities can be configured also in this solution. In one option, the priorities for data collection for training serves as the indication to the UE that the measurements are for model training and that it has lower priority than basic procedures.

[0197] In an option, the UE 100 may apply priority of the measurements for the mobility related data collection or not, which is indicated by UE capability or UE assistance information (UAI). The network (e.g., network node 102) may respect and assume the UE’s reported preferred priority accordingly after reception of the indication.

[0198] An example of standard impact to indicate whether mobility related data collection on other frequency is allowed while performing measurements based on this measurement configuration, is shown below. Here the indication is included in the measObject associated with the RRM measurement configuration (measConfig). In this case, all the reportConfig associated with this measurement object (measObject) will use the same priority and prohibit timer.— ASN1START

[0199] — TAG-MEASOBJECTNR-START

[0200] MeasObj ectNR SEQUENCE {

[0201] s sb Frequency ARFCN-ValueNR OPTIONAL, — Cond SSBorAssociatedSSB ssbSub carrierspacing SubcarrierSpacing OPTIONAL, — Cond SSBorAssociatedSSB smtcl SSB-MTC OPTIONAL, — Cond SSBorAssociatedSSB smtc2 SSB-MTC2 OPTIONAL, — Cond IntraFreqConnected ref FreqCSI-RS ARFCN-ValueNR OPTIONAL, — Cond CSI-RS referenceSignalConfig ReferenceSignalConfig, absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, — Need R absThreshCSI-RS-Consolidation ThresholdNR OPTIONAL, — Need R nrof SS-BlocksToAverage INTEGER ( 2.. maxNro f SS-BlocksToAverage ) OPTIONAL, — Need R nrof OS I -RS -Res ounces ToAve rage INTEGER ( 2.. maxNrof CSI -RS-Resour cesToAverage ) OPTIONAL, — Need R quantityConfiglndex INTEGER ( 1.. maxNrofQuantityConfig ), of f setMO Q-Of f setRangeList, cellsToRemoveList PCI-List OPTIONAL, — Need N cellsToAddModList CellsToAddModList OPTIONAL, — Need N excludedCellsToRemoveList PCI-RangelndexList OPTIONAL, — Need N excludedCellsToAddModList SEQUENCE ( SIZE ( 1.. maxNro f PCI -Ranges ) ) OF PCIRangeElement OPTIONAL, — Need N allowedCellsToRemoveList PCI -Range I ndexLi st OPTIONAL, — Need N allowedCellsToAddModList SEQUENCE ( SIZE ( 1.. maxNro f PCI -Ranges ) ) OF PCI- RangeElement OPTIONAL, — Need N

[0202] [ [ f reqBandlndicatorNR FreqBandlndicatorNR

[0203]

[0204] OPTIONAL, — Need R me as Cycles Cell ENUMERATED ( s flSO, s f256, s f320, s f512, s f640, s fl024, s fl280 } OPTIONAL — Need R

[0205] ] ],

[0206] [ [

[0207] smtc31ist-rl6 SSB-MTC3List-rl6

[0208] OPTIONAL, — Need R

[0209] rmtc-Config-rl6 SetupRelease ( RMTC-Config-rl6 }

[0210] OPTIONAL, — Need M

[0211] t312-r!6 SetupRelease ( T312-rl6 }

[0212] OPTIONAL — Need M

[0213] ] ],

[0214] [ [

[0215] associatedMeasGapSSB-r 17 MeasGapId-r 17

[0216] OPTIONAL, — Need R

[0217] associatedMeasGapCSIRS-r 17 MeasGapId-r 17

[0218] OPTIONAL, — Need R

[0219] smtc41ist-r 17 SSB-MTC4List-r 17

[0220] OPTIONAL, — Need R

[0221] meas Cycle PSCell-r 17 ENUMERATED (ms lSO, ms256, ms320, ms512, ms 640, ms l024, ms l280, sparel )

[0222] OPTIONAL, — Cond SCG

[0223] cellsToAddModListExt-vl710 CellsToAddModListExt-vl710

[0224] OPTIONAL — Need N

[0225] ] ],

[0226] [ [

[0227] associatedMeasGapSSB2-vl720 MeasGapId-r 17

[0228] OPTIONAL, — Cond AssociatedGapSSB

[0229] associatedMeasGapCSIRS2-vl720 MeasGapId-r 17

[0230] OPTIONAL — Cond AssociatedGapCSIRS

[0231] ] ],

[0232] [ [

[0233] measSequence-rl8 MeasSequence-rl8

[0234] OPTIONAL, — Need R

[0235] cellsToAddModListExt-vl800 CellsToAddModListExt-vl800

[0236] OPTIONAL — Need N

[0237] ] ],[ [

[0238] lowPrioLogging ENUMERATED { true }

[0239] OPTIONAL, — Need R

[0240] prohibitLoggingTimer ENUMERATED { ms50, mslOO, ms200, ms400, ms500, mslOOO } OPTIONAL — Need R

[0241] ] ]

[0242] }

[0243] In another example, the priority indication and the prohibit timer are included in the reportConfig IE. In this way, only the measurement configuration (measObject) associated with that reportConfig will use the indicated priority and the prohibit timer.

[0244] — ASN1START

[0245] — TAG-REPORTCONFIGNR-START

[0246] ReportConf igNR:: = SEQUENCE {

[0247] reportType CHOICE {

[0248] periodical PeriodicalReportConf ig,

[0249] event! rigge red EventT rigger Con fig,

[0250] reportCGI ReportCGI,

[0251] reportSFTD ReportSFTD-NR,

[0252] co ndT rigger Conf ig-r 16 Co ndT rigger Conf ig-r 16,

[0253] cli- Period! cal- r 1 CLI-PeriodicalReportConf ig-r 16,

[0254] cli-EventT rigge red- r 16 CLI -Event Trigger Conf ig-r 16, rxTxPeriodical-rl7 RxTxPeriodical-r 17,

[0255] repo rtOnS cellAct i vat ion- r 18 Report0nScellActivation-rl8,

[0256] lowPri ©Logging ENUMERATED { true }

[0257] OPTIONAL, — Need R

[0258] prohibitLoggingTimer ENUMERATED { ms50, mslOO, ms200, ms400, ms500, mslOOO } OPTIONAL — Need R

[0259] }

[0260] }

[0261] In another option the new introduced flag:

[0262] lowPrioLogging ENUMERATED { true }

[0263] can be replaced by an integer value indicating the priority of the measurement over the other measurements, e.g.,:

[0264] measPrio INTEGER (E.maxPrioValue),

[0265] where “1” indicates the measurement with lowest priority and “maxPrioValue” the highest priority (or vice versa).

[0266] Figure 2 shows an example of a communication system 200 in which embodiments of the present disclosure may be implemented. For instance, the UE 100 may be any one of the UEs 212 of Figure 2. The network node 102 may be one of the access network nodes 210, for example.

[0267] In the example, the communication system 200 includes a telecommunications network 202 that includes an access network 204, such as a radio access network (RAN), and a core network 206, which includes one or more core network nodes 208. The access network 204 includes one or more access network nodes or base stations of various types, access network nodes 210A and 210B are depicted (which may be collectively referred to as network nodes 210), or any othersimilar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 204 may include more than one access network technology. The network nodes 210 of access network 204 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 212A, 212B, 212C, and 212D (one or more of which may be generally referred to as UEs 212) to the core network 206 over one or more wireless connections.

[0268] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 202 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 202, including one or more access network nodes 210 and / or core network nodes 208.

[0269] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0270] The network nodes 210 facilitate direct or indirect connection of one or more UEs 212 to the core network 206 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 forconveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 200 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 200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0271] The UEs 212 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 210 and other communication devices. Similarly, the network nodes 208, 210 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 202) with the UEs 212 and / or with other network nodes or equipment in the telecommunications network 202 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 202. More specifically, UEs 212 may send messages, data, and / or other signals to network nodes 208, 210 or other elements of the telecommunications network 202 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 208, 210 may send messages, data, and other signals to UEs 2122, other network nodes 208, 210, and other devices in telecommunications network 202 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 212 by transmitting the message to an access network node 210 that will then transmit the message to the intended UE 212. Similarly, a core network node 108 may receive a particular message from a UE 212 by receiving the message from an access network node 210 that itself received the message from the UE 212.

[0272] In the depicted example, the core network 206 connects elements of the access network 204 (e.g., one or more of the network nodes 210) to one or more host computing systems, such as host 216. 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 206 includes one or more core network nodes (e.g., core network node 208) of various types, one or more of which may be generally referred to as network nodes 208. Network nodes 208 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / orhosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 208. Example core network nodes provide 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).

[0273] The host 216 may be under the ownership or control of a service provider other than an operator or provider of the access network 204 and / or the telecommunications network 202. The host 216 may be operated by the service provider or on behalf of the service provider. The host 216 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.

[0274] As a whole, the communication system 200 of Figure 2 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 200 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 200 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 200 supporting different standards, protocols, or rule sets.

[0275] As one example, in certain embodiments, access network 204 may contain some access network nodes 210 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 210 support (or the same access network nodes 210 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example,telecommunications network 202 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0276] Telecommunications network 202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 202. For example, the telecommunications network 202 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 IoT services to yet further UEs.

[0277] In some examples, one or more of the UEs 212 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 204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 204. 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).

[0278] In the example, the hub 214 communicates with the access network 204 to facilitate indirect communication between one or more UEs (e.g., UE 212C and / or 212D) and network nodes (e.g., network node 210B). In some examples, the hub 214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 214 may be a broadband router enabling access to the core network 206 for the UEs. As another example, the hub 214 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 210, or by executable code, script, process, or other instructions in the hub 214.

[0279] As another example, the hub 214 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 214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 214 then provides to the UE either directly, after performing local processing, and / or after addingadditional local content. In still another example, the hub 214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.

[0280] The hub 214 may have a constant / persistent or intermittent connection to the network node 210B. The hub 214 may also allow for a different communication scheme and / or schedule between the hub 214 and UEs (e.g., UE 212C and / or 212D), and between the hub 214 and the core network 206. In other examples, the hub 214 is connected to the core network 206 and / or one or more UEs via a wired connection. Moreover, the hub 214 may be configured to connect to an M2M service provider over the access network 204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 210 while still connected via the hub 214 via a wired or wireless connection. In some embodiments, the hub 214 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 210B. In other embodiments, the hub 214 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 210B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0281] Figure 3 is another example of a communication system 300 according to some embodiments. As used herein, the communication system 300 includes multiple access points (APs) 310 (with four exemplary APs 310A, 310B, 310C, and 310D being depicted) and multiple wireless devices, referred to in the context of communication system 300 as stations (STAs) 312 (referred to individually as STA 312A, STA 312B, STA 312C, STA 312D, and STA 312E). STA 312A is served by AP 310A in a first basic service set (BSS) 320A. STA 310B and STA 310C are served by AP 310B in a second BSS, BSS 320B. STA 312D is served by AP 310C in a third BSS, BSS 320C. STA 312E is served by AP 310D in a fourth BSS, BSS 320D. Stations 312 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 312 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0282] Each of STAs 312 may connect through a radio link to one of APs 310. For example, depending on location or channel conditions experienced by a given STA 312, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exemptband like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0283] Each AP 310 may provide data connectivity to STAs 312 connected to a particular AP 310. As illustrated, APs 310 may be connected to a data network 330. In this way, APs 310 may also provide data connectivity between STAs 312 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 312 and its serving AP 310 may be used for providing various kinds of services to STA 312, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 312 and / or on a device linked to STA 312. By way of example, Figure 3 illustrates an application service platform 332 provided in data network 330. The application(s) executed on STA 312 and / or on one or more other devices linked to STA 312 may use the radio link for data communication with one or more other STA 312 and / or the application service platform 332, thereby enabling utilization of the corresponding service(s) at STA 312.

[0284] Figure 4 shows a wireless device 400, which may be configured to operate in communication system 200 of Figure 2 or in communication system 300 of Figure 3. The wireless device 400 may be alternatively referred to as a UE 400, like a UE 212 within the context of communication system 200, or as a station (STA) 400 or as a non-access-point station (non-AP STA) 400, like a STA 312 within the context of the communication system 300, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device 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, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0285] A wireless device 400 may support device-to-device (D2D) communication, for example by implementing a 3 GPP 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, wireless device 400 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 400 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, wireless device 400 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).

[0286] In particular embodiments, wireless device 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 embodiments of wireless device 400 may include all or a subset of the components shown in Figure 4. The level of integration between the components may vary from one embodiment of wireless device 400 to another. In general, in a particular embodiment of wireless device 400, processing circuitry 402, input / output interface 406, power source 408, memory 410, and communication interface 412 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 400. Further, certain embodiments of wireless devices 400 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0287] 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).

[0288] 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 wireless device 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.

[0289] 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 to supply power to circuitry or to charge an associated battery. 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 wireless device 400 via input circuitry or an interface such as an electrical power cable. Power source 408 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 400 to which power is supplied.

[0290] 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 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 wireless device 400, any of a variety of various operating systems or combinations of operating systems.

[0291] 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 (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 410 may allow wireless device 400 to access instructions, programs, and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, suchas 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.

[0292] The processing circuitry 402 may be configured to communicate with an access network or other network via or 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 wireless device 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.

[0293] In the illustrated embodiment, communication functions of the communication interface 412 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), 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 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), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0294] In particular embodiments, wireless device 400 may provide an output of data captured via a sensor, through its communication interface 412, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 400 can be communicated through a wireless connection to a network node via another wireless device 400. In particular embodiments, such 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, wireless device 400 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, wireless device 400 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.

[0295] Wireless device 400, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT 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 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. In particular embodiments, wireless device 400 represents an IoT device that 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 example embodiment of wireless device 400 shown in Figure 4.

[0296] As yet another specific example, in an IoT scenario, wireless device 400 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 wireless device and / or a network node. Wireless device 400 may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, wireless device 400 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 400 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.

[0297] In practice, any number of wireless devices 400 may be used together with respect to a single use case. For example, a first wireless device 400 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 400 that is a remote controller operating the drone. When a user makes changes from theremote controller, the first wireless device 400 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 wireless device 400 can also include more than one of the functionalities described above. For example, wireless device 400 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0298] 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 telecommunications network. In accordance with respective embodiments, network node 500 may be configured to operate in communication system 200 of Figure 2, like network nodes 208 or 210, or in communication system 300 of Figure 3, like an AP 310 or a station 312. 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 NRNodeBs (gNBs)), O-RAN nodes or components of an 0-RAN node (e.g., O-RU, O-DU, O-CU).

[0299] Network nodes 500 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. Network node 500 may be a relay node or a relay donor node controlling a relay. Network nodes 500 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) 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).

[0300] Other examples of network nodes 500 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O& M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0301] In particular embodiments, network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508. In general, in a particular embodiment of network node 500, processing circuitry 502, memory 504, communicationinterface 506, and power source 508 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 500.

[0302] The network node 500 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 500 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities 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 memories 504 or portions of 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, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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.

[0303] 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 components, such as the memory 504, to provide network node 500 functionality.

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

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

[0306] The communication interface 506 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, 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. In particular embodiments, network node 400 may be capable of wireless communication and communication interface 506 may also include radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, an antenna 510. Particular embodiments of radio front-end circuitry 518 include filter(s) 520 and amplifier(s) 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end 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(s) having the appropriate channel and bandwidth parameters using a combination of filters 520 and / or amplifiers 522. The radio signal(s) 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.

[0307] In certain alternative embodiments, network node 500 may be capable of wireless communication but does not include separate radio front-end 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, aspart 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).

[0308] 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 one or more interfaces or ports.

[0309] The antenna 510, communication interface 506, and / or the processing circuitry 502 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 500. 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 some or all of the transmitting or sending operations described herein as being performed by the network node 500. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

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

[0311] 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 illustrating a virtualization environment 600 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 600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

[0313] Hardware 604 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 606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 608A and VM 608B (which may be collectively referred to as VMs 608), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 606 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 608.

[0314] The VMs 608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 606. Different embodiments of the instance of a virtual appliance 602 may be implemented on one or more of VMs 608, 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, each of the VMs 608 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 608, and that part of hardware 604 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 of the VMs 608 on top of the hardware 604 and corresponds to an application 602.

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

[0316] 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 maybe 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.

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

[0318] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0319] Some exemplary embodiments of the present disclosure are as follows:

[0320] Group A Embodiments

[0321] Embodiment 1: A method performed by a User Equipment, UE, (100) for mobility related data collection, the method comprising: receiving (104), from a network node (102), configuration information that configures the UE (100) for measurements for mobility -related data collection (e.g., for AI / ML model training), the measurements for mobility -related data collection comprising measurements on at least one frequency; performing (106) measurements for mobility related data collection in accordance with the received configuration information an in such a manner that performing (106) the measurements for mobility related data collection does not impair one or more certain procedures or functionalities at the UE (100).

[0322] Embodiment 2: The method of embodiment 1, wherein performing (106) measurements for mobility related data collection comprises: detecting (106A) fulfilment of one or more certain event(s) at the UE (100); and in response to detecting (106 A) fulfilment of the one or more certain event(s) at the UE (100), performing (106B) a certain action with respect to the measurements for mobility related data collection.Embodiment 3: The method of embodiment 2, wherein the certain action comprises activating, starting, deactivating, suspending, or stopping the measurements for mobility related data collection.

[0323] Embodiment 4: The method of embodiment 2 or 3, wherein the one or more certain events is(are) associated to any one or more of the following: performing one or more measurements in one or more frequencies for a purpose of Radio Resource Management, RRM; performing data transmission in uplink or downlink over an uplink or downlink data channel; performing data transmission in uplink over an uplink data channel; performing data transmission in downlink over a downlink data channel; fulfilment of one or more measurement relaxation conditions.

[0324] Embodiment 5: The method of any of embodiments 2 to 4, wherein the one or more certain events at the UE comprise performance, at the UE (100), of one or more measurements at the UE (100) for RRM purpose, and performing (106B) the certain action comprises stopping, suspending, or deactivating the measurements for mobility related data collection responsive to detecting performance, at the UE (100), of one or more measurements for RRM purpose.

[0325] Embodiment 6: The method of any of embodiments 2 to 4, wherein the one or more certain events at the UE comprise a downlink data transmission (received or to be received) at the UE over a downlink data channel or an uplink data transmission (transmitted or to be transmitted) at the UE over an uplink data channel, and performing (106B) the certain action comprises stopping, suspending, or deactivating the measurements for mobility related data collection responsive to detecting the downlink data transmission (received or to be received) at the UE over a downlink data channel or the uplink data transmission (transmitted or to be transmitted) at the UE over an uplink data channel.

[0326] Embodiment 7: The method of any of embodiments 2 to 4, wherein detecting (106 A) fulfillment of the one or more certain events at the UE comprises detecting (106A) fulfillment of one or more measurement relaxation conditions at the UE or that the UE is performing measurement relaxation, and performing (106B) the certain action comprises starting, resuming, or activating the measurements for mobility related data collection responsive to detecting fulfillment of one or more measurement relaxation conditions at the UE.

[0327] Embodiment 8: The method of embodiment 7, wherein the one or more measurement relaxation conditions comprise any one or more of the following: one or more conditions for RRM measurement relaxation; one or more conditions for Radio Link Monitoring, RLM, measurement relaxation; one or more Beam Failure Detection, BFD, measurement relaxation.Embodiment 9: The method of embodiment 7, wherein the measurement relaxation is any of the following: RRM measurement relaxation; Radio Link Monitoring, RLM, measurement relaxation; Beam Failure Detection, BFD, measurement relaxation.

[0328] Embodiment 10: The method of any of embodiments 2 to 4, wherein the received configuration for measurements for mobility related data collection comprises a priority indication (configuration or information that explicitly or implicitly indicates a priority of the measurements for mobility related data collection, e.g., with respect to the one or more other certain procedures or functionalities).

[0329] Embodiment 11: The method of embodiment 10, wherein detecting (106A) fulfillment of the one or more events comprises checking the priority indication.

[0330] Embodiment 12: The method of embodiment 11, wherein the priority indication indicates whether the UE is to activate, start, deactivate, suspend, or stop the one or more measurements for mobility related data collection purpose in response to detecting (106 A) fulfillment of the one or more other events.

[0331] Embodiment 13: The method of any of embodiments 10 to 12, wherein the priority indication comprises a prohibition timer indicating a time period for which the LTE is to keep the measurements for mobility related data collection suspended in response to detecting (106 A) fulfillment of the one or more events and stopping or suspending of the measurements for mobility related data collection.

[0332] Embodiment 14: The method of any of embodiments 10 to 12, wherein the detected event is a data transmission or data reception at the LTE (100), and the priority indication includes a subpriority of one or more measurements for mobility related data collection which are to be suspended, deactivated, or stopped in conjunction with a higher data Logical channel priority.

[0333] Embodiment 15: The method of any of embodiments 10 to 12, wherein the detected event is a data transmission or data reception, and the priority configuration includes a sub-priority of one or more measurements for mobility related data collection which will be activated or started in conjunction with a lower data Logical channel priority.

[0334] Embodiment 16: The method of any of embodiments 2 to 15, wherein performing (106B) the certain action comprise fully activating, starting, deactivating, suspending, or stopping the measurements for mobility related data collection.

[0335] Embodiment 17: The method of any of embodiments 2 to 15, wherein performing (106B) the certain action comprise partially activating, starting, deactivating, suspending, or stopping the measurements for mobility related data collection.Embodiment 18: The method of any of embodiments 2 to 17, further comprising transmitting (107), to the network node, a status indicator that indicates a status of the measurements for mobility-related data collection (e.g., responsive to performing (106B) the certain action).

[0336] Embodiment 19: The method of embodiment 1, wherein: the received configuration for measurements for mobility related data collection comprises a priority indication (configuration or information that explicitly or implicitly indicates a priority of the measurements for mobility related data collection, e.g., with respect to the one or more other certain procedures or functionalities); and performing (106) measurements for mobility related data collection comprises performing (106) the measurements for mobility related data collection in accordance with the received configuration information including the priority indication.

[0337] Embodiment 20: The method of any of embodiments 1 to 19, further comprising reporting (108) results of the measurements for mobility related data collection to the network node (102) or another network node.

[0338] Embodiment 21: The method of embodiment 20, further comprising reporting information about how long the measurements for mobility related data collection were deactivated, suspended, or stopped.

[0339] Embodiment 22: The method of embodiment 20, further comprising reporting a cause or reason for why the measurements (or at least some of the measurements) for mobility related data collection were not collected.

[0340] Embodiment 23: The method of embodiment 20, further comprising reporting an indication that the measurements for mobility related data collection were deactivated, suspended, or stopped.

[0341] Embodiment 24: The method of any of embodiments 1 to 23, wherein measurement configuration for RRM received by the UE (100) from the network node (or another network node) that configures the UE to perform measurements for RRM comprises an indication (explicit or implicit) that indicates whether mobility related data collection on other frequencies is allowed while performing measurements based on the RRM measurement configuration.

[0342] Embodiment 25: The method of any of embodiments 1 to 23, wherein the configuration information comprises an indication that indicates whether measurements for mobility related data collection on other frequencies is allowed while the UE performs RRM measurements, e.g., on a serving and / or neighboring frequencies.

[0343] Embodiment 26: The method of any of embodiments 1 to 25, further comprising transmitting (103), to the network node (102), capability information that indicates that the UE(100) is capable of performing measurements for mobility related data collection as recited in any of embodiments 1 to 25.

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

[0345] Group B Embodiments

[0346] Embodiment 28: A method performed by a network node (102) for mobility related data collection from a User Equipment, UE, (100), the method comprising: transmitting (104), to a UE (100), configuration information that configures the UE (100) for measurements for mobility-related data collection (e.g., for AI / ML model training), the measurements for mobility -related data collection comprising measurements on at least one frequency.

[0347] Embodiment 29: The method of embodiment 28, wherein the configuration information that configures the UE (100) for measurements for mobility related data collection comprises a priority indication (configuration or information that explicitly or implicitly indicates a priority of the measurements for mobility related data collection, e.g., with respect to the one or more other certain procedures or functionalities).

[0348] Embodiment 30: The method of embodiment 29, wherein the priority indication indicates whether the UE is to activate, start, deactivate, suspend, or stop the measurements for mobility related data collection purpose in response to detecting fulfillment of one or more events (e.g., one or more events related to RRM measurements, downlink data transmission, uplink data transmission, or measurement relaxation).

[0349] Embodiment 31: The method of embodiment 29 or 30, wherein the priority indication comprise a prohibition timer indicating a time period for which the UE is to keep the measurements for mobility related data collection suspended in response to detecting fulfillment of one or more events at the UE and stopping or suspending of the measurements for mobility related data collection in response thereto.

[0350] Embodiment 32: The method of any of embodiments 29 to 31, wherein the priority indication includes a sub-priority of one or more measurements for mobility related data collection which are to be suspended, deactivated, or stopped in conjunction with detection of an event associated to downlink or uplink data transmission on a logical channel having a higher data Logical channel priority.

[0351] Embodiment 33: The method of any of embodiments 29 to 31, wherein the priority configuration includes a sub-priority of one or more measurements for mobility related datacollection which the UE is to activate or start in response to detecting an event associated with an uplink or downlink data transmission on a logical channel having a lower data Logical channel priority.

[0352] Embodiment 34: The method of any of embodiments 28 to 33, further comprising receiving (107), from the UE (100), a status indicator that indicates a status of the measurements for mobility-related data collection.

[0353] Embodiment 35: The method of any of embodiments 28 to 34, further comprising receiving (108), from the UE (100), a report comprising the measurements for mobility related data collection and / or information derived therefrom.

[0354] Embodiment 36: The method of embodiment 35, wherein the report comprises information about how long the measurements for mobility related data collection were deactivated, suspended, or stopped.

[0355] Embodiment 37: The method of embodiment 35 or 36, wherein the report comprises a cause or reason for why the measurements (or at least some of the measurements) for mobility related data collection were not collected.

[0356] Embodiment 38: The method of any of embodiments 35 to 37, wherein the report comprises an indication that the measurements for mobility related data collection were deactivated, suspended, or stopped.

[0357] Embodiment 39: The method of any of embodiments 28 to 38, wherein a measurement configuration for RRM transmitted the UE (100) (e.g., from the network node or another network node) that configures the UE to perform measurements for RRM comprises an indication (explicit or implicit) that indicates whether mobility related data collection on other frequencies is allowed while performing measurements based on the RRM measurement configuration.

[0358] Embodiment 40: The method of any of embodiments 28 to 38, wherein the configuration information comprises an indication that indicates whether measurements for mobility related data collection on other frequencies is allowed while the UE performs RRM measurements, e.g., on a serving and / or neighboring frequencies.

[0359] Embodiment 41: The method of any of embodiments 28 to 40, further comprising receiving (103), from the UE (100), capability information that indicates that the UE (100) is capable of performing measurements for mobility related data collection as recited in any of embodiments 1 to 25.

[0360] Embodiment 42: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.Group C Embodiments

[0361] Embodiment 43: A wireless device, comprising: processing circuitry configured to perform any of the operations of any of the Group A embodiments; and a power source configured to supply power to the processing circuitry.

[0362] Embodiment 44: A network node, the network node comprising: processing circuitry configured to perform any of the operations of any of the Group B embodiments; a power source circuitry configured to supply power to the processing circuitry.

[0363] Embodiment 45: A wireless device, the wireless device comprising: one or more antennas; communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to perform any of the operations 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 power source connected to the processing circuitry and configured to supply power to the UE.

Claims

1. CLAIMS1. A method performed by a User Equipment, UE, (100) for mobility related data collection, the method comprising:receiving (104), from a network node (102), configuration information that configures the UE (100) for measurements for mobility -related data collection, the measurements for mobility-related data collection comprising measurements on at least one frequency; and performing (106) measurements for mobility related data collection in accordance with the received configuration information and in such a manner that performing (106) the measurements for mobility related data collection does not impair one or more certain procedures or functionalities at the UE (100).

2. The method of claim 1, wherein performing (106) measurements for mobility related data collection comprises:detecting (106 A) fulfilment of one or more certain events at the UE (100); and in response to detecting (106 A) fulfilment of the one or more certain events at the UE (100), performing (106B) a certain action with respect to the measurements for mobility related data collection.

3. The method of claim 2, wherein the certain action comprises activating, starting, deactivating, suspending, or stopping the measurements for mobility related data collection.

4. The method of claim 2 or 3, wherein the one or more certain events are associated to any one or more of the following:performing one or more measurements in one or more frequencies for a purpose of Radio Resource Management, RRM;performing data transmission in uplink or downlink over an uplink or downlink data channel;performing data transmission in uplink over an uplink data channel;performing data transmission in downlink over a downlink data channel; fulfilment of one or more measurement relaxation conditions.

5. The method of any of claims 2 to 4, wherein the one or more certain events at the UE (100) comprise performance, at the UE (100), of one or more measurements at the UE (100) for RRM purpose, and performing (106B) the certain action comprises stopping, suspending, or deactivatingthe measurements for mobility related data collection responsive to detecting performance, at the UE (100), of one or more measurements for RRM purpose.

6. The method of any of claims 2 to 4, wherein the one or more certain events at the UE (100) comprise a downlink data transmission at the UE (100) over a downlink data channel or an uplink data transmission at the UE (100) over an uplink data channel, and performing (106B) the certain action comprises stopping, suspending, or deactivating the measurements for mobility related data collection responsive to detecting the downlink data transmission at the UE over a downlink data channel or the uplink data transmission at the UE over an uplink data channel.

7. The method of any of claims 2 to 4, wherein detecting (106A) fulfillment of the one or more certain events at the UE comprises detecting (106A) fulfillment of one or more measurement relaxation conditions at the UE or that the UE is performing measurement relaxation, and performing (106B) the certain action comprises starting, resuming, or activating the measurements for mobility related data collection responsive to detecting fulfillment of one or more measurement relaxation conditions at the UE.

8. The method of claim 7, wherein the one or more measurement relaxation conditions comprise any one or more of the following:one or more conditions for RRM measurement relaxation;one or more conditions for Radio Link Monitoring, RLM, measurement relaxation; one or more Beam Failure Detection, BFD, measurement relaxation.

9. The method of claim 7, wherein the measurement relaxation is any of the following:RRM measurement relaxation;Radio Link Monitoring, RLM, measurement relaxation;Beam Failure Detection, BFD, measurement relaxation.

10. The method of any of claims 2 to 4, wherein the received configuration for measurements for mobility related data collection comprises a priority indication.

11. The method of claim 10, wherein detecting (106A) fulfillment of the one or more events comprises checking the priority indication.

12. The method of claim 10, wherein the priority indication indicates whether the UE is to activate, start, deactivate, suspend, or stop the one or more measurements for mobility related data collection purpose in response to detecting (106 A) fulfillment of the one or more other events.

13. The method of any of claims 10 to 12, wherein the priority indication comprises a prohibition timer indicating a time period for which the UE is to keep the measurements for mobility related data collection suspended in response to detecting (106 A) fulfillment of the one or more events and stopping or suspending of the measurements for mobility related data collection.

14. The method of any of claims 10 to 12, wherein the detected event is a data transmission or data reception at the UE (100), and the priority indication includes a sub-priority of one or more measurements for mobility related data collection which are to be suspended, deactivated, or stopped in conjunction with a higher data Logical channel priority.

15. The method of any of claims 10 to 12, wherein the detected event is a data transmission or data reception, and the priority configuration includes a sub-priority of one or more measurements for mobility related data collection which will be activated or started in conjunction with a lower data Logical channel priority.

16. The method of any of claims 2 to 15, wherein performing (106B) the certain action comprise fully activating, starting, deactivating, suspending, or stopping the measurements for mobility related data collection.

17. The method of any of claims 2 to 15, wherein performing (106B) the certain action comprise partially activating, starting, deactivating, suspending, or stopping the measurements for mobility related data collection.

18. The method of any of claims 2 to 17, further comprising transmitting (107), to the network node, a status indicator that indicates a status of the measurements for mobility-related data collection.

19. The method of claim 1, wherein:the received configuration for measurements for mobility related data collection comprisesa priority indication; andperforming (106) measurements for mobility related data collection comprises performing (106) the measurements for mobility related data collection in accordance with the received configuration information including the priority indication.

20. The method of any of claims 1 to 19, further comprising reporting (108) results of the measurements for mobility related data collection to the network node (102) or another network node.

21. The method of claim 20, further comprising reporting information about how long the measurements for mobility related data collection were deactivated, suspended, or stopped.

22. The method of claim 20, further comprising reporting a cause or reason for why the measurements or at least some of the measurements for mobility related data collection were not collected.

23. The method of claim 20, further comprising reporting an indication that the measurements for mobility related data collection were deactivated, suspended, or stopped.

24. The method of any of claims 1 to 23, wherein the measurement configuration for RRM received by the UE (100) from the network node or another network node that configures the UE to perform measurements for RRM comprises an indication that indicates whether mobility related data collection on other frequencies is allowed while performing measurements based on the RRM measurement configuration.

25. The method of any of claims 1 to 23, wherein the configuration information comprises an indication that indicates whether measurements for mobility related data collection on other frequencies is allowed while the UE performs RRM measurements on a serving and / or neighboring frequencies.

26. The method of any of claims 1 to 25, further comprising transmitting (103), to the network node (102), capability information that indicates that the UE (100) is capable of performing measurements for mobility related data collection as recited in any of claims 1 to 25.

27. A User Equipment, UE, (100; 400) for mobility related data collection, the UE (100; 400) comprising:a communication interface (412) comprising a transmitter (418) and a receiver (420); andprocessing circuitry (402) associated with the communication interface (412), the processing circuitry (402) configured to cause the UE (100; 400) to:receive (104), from a network node (102), configuration information that configures the UE (100) for measurements for mobility -related data collection, the measurements for mobility-related data collection comprising measurements on at least one frequency; and perform (106) measurements for mobility related data collection in accordance with the received configuration information and in such a manner that performing (106) the measurements for mobility related data collection does not impair one or more certain procedures or functionalities at the UE (100).

28. The UE of claim 27, wherein the processing circuitry is further configured to cause the UE to perform the method of any of claims 2 to 26.

29. A method performed by a network node (102) for mobility related data collection from a User Equipment, UE, (100), the method comprising:transmitting (104), to a UE (100), configuration information that configures the UE (100) for measurements for mobility -related data collection, the measurements for mobility -related data collection comprising measurements on at least one frequency.

30. The method of claim 29, wherein the configuration information that configures the UE (100) for measurements for mobility related data collection comprises a priority indication.

31. The method of claim 30, wherein the priority indication indicates whether the UE is to activate, start, deactivate, suspend, or stop the measurements for mobility related data collection purpose in response to detecting fulfillment of one or more events related to radio resource monitoring, RRM, measurements, downlink data transmission, uplink data transmission, or measurement relaxation.

32. The method of claim 30 or 31, wherein the priority indication comprise a prohibition timer indicating a time period for which the UE is to keep the measurements for mobility related datacollection suspended in response to detecting fulfillment of one or more events at the UE and stopping or suspending of the measurements for mobility related data collection in response thereto.

33. The method of any of claims 30 to 32, wherein the priority indication includes a subpriority of one or more measurements for mobility related data collection which are to be suspended, deactivated, or stopped in conjunction with detection of an event associated to downlink or uplink data transmission on a logical channel having a higher data logical channel priority.

34. The method of any of claims 30 to 32, wherein the priority configuration includes a subpriority of one or more measurements for mobility related data collection which the UE is to activate or start in response to detecting an event associated with an uplink or downlink data transmission on a logical channel having a lower data Logical channel priority.

35. The method of any of claims 29 to 34, further comprising receiving (107), from the UE (100), a status indicator that indicates a status of the measurements for mobility-related data collection.

36. The method of any of claims 29 to 35, further comprising receiving (108), from the UE (100), a report comprising the measurements for mobility related data collection and / or information derived therefrom.

37. The method of claim 36, wherein the report comprises information about how long the measurements for mobility related data collection were deactivated, suspended, or stopped.

38. The method of claim 36 or 37, wherein the report comprises a cause or reason for why the measurements or at least some of the measurements for mobility related data collection were not collected.

39. The method of any of claims 36 to 38, wherein the report comprises an indication that the measurements for mobility related data collection were deactivated, suspended, or stopped.

40. The method of any of claims 29 to 39, wherein a measurement configuration for RRMtransmitted the UE (100) from the network node or another network node that configures the UE to perform measurements for RRM comprises an indication that indicates whether mobility related data collection on other frequencies is allowed while performing measurements based on the RRM measurement configuration.

41. The method of any of claims 29 to 39, wherein the configuration information comprises an indication that indicates whether measurements for mobility related data collection on other frequencies is allowed while the UE performs RRM measurements on a serving and / or neighboring frequencies.

42. The method of any of claims 29 to 41, further comprising receiving (103), from the UE (100), capability information that indicates that the UE (100) is capable of performing measurements for mobility related data collection as recited in any of claims 1 to 25.

43. A network node (102; 500) for mobility related data collection from a User Equipment, UE, (100), the network node (102; 500) comprising processing circuitry (502) configured to cause the network node (102; 500) to:transmit (104), to a UE (100), configuration information that configures the UE (100) for measurements for mobility -related data collection, the measurements for mobility-related data collection comprising measurements on at least one frequency.

44. The network node of claim 43, wherein the processing circuitry is further configured to cause the network node to perform the method of any of claims 30 to 42.

Images