WO2021076030A1

WO2021076030A1 - Selection and consent for mdt activation

Info

Publication number: WO2021076030A1
Application number: PCT/SE2020/050953
Authority: WO
Inventors: Angelo Centonza; Pradeepa Ramachandra; Panagiotis Saltsidis
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2019-10-15
Filing date: 2020-10-06
Publication date: 2021-04-22

Abstract

According to some embodiments, a method performed by split radio access network (RAN) network node for minimization of drive test (MDT) comprises receiving a MDT activation request from a network management system. The activation request comprises an indication of a MDT area. The method further comprises transmitting an indication of MDT activation to a central unit control plane (CU-CP); receiving, from the CU-CP, an indication of one or more wireless devices that consent to performing MDT; and performing MDT measurements towards the one or more wireless devices that consent to performing MDT and are within the MDT area.

Description

SELECTION AND CONSENT FOR MDT ACTIVATION

TECHNICAL FIELD

Particular embodiments relate to wireless communication, and more specifically to user equipment (UE) selection and consent for minimization of drive test (MDT) activation.

BACKGROUND

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

One feature of long term evolution (LTE) wireless communications networks is minimization of drive tests (MDT). MDT has not been standardized for fifth generation (5G) new radio (NR) wireless communication systems. Some particular use cases for MDT include coverage optimization, mobility optimization, capacity optimization, parameterization for common channels, and quality of service (QoS) verification.

NR includes an RRC INACTIVE state to reduce latency and the amount of signaling during connection establishment. A user equipment (UE) in RRC INACTIVE obtains normal service when camping on a suitable cell and operator service when camping on a reserved cell. The UE in RRC INACTIVE performs cell reselection and the required measurements on the serving cell and neighbor cells similar to that for a UE in RRC IDLE state. RRC INACTIVE is a state where a UE remains in CM-CONNECTED and can move within an area configured by next generation radio access network (NG-RAN) (the RAN-based notification area (RNA)) without notifying NG-RAN. In RRC_INACTIVE, the last serving gNB node keeps the UE context and the UE-associated NG connection with the serving access and mobility management function (AMF) and user plane function (UPF).

At transition to RRC INACTIVE, the NG-RAN node may configure the UE with a periodic RNA Update timer value.

If the UE accesses a gNB other than the last serving gNB, the receiving gNB triggers the XnAP Retrieve UE Context procedure to get the UE context from the last serving gNB and may also trigger an Xn-U Address Indication procedure including tunnel information for potential recovery of data from the last serving gNB. Upon successful UE context retrieval, the receiving gNB performs slice-aware admission control in case of receiving slice information and becomes the serving gNB and it further triggers the next generation application protocol (NGAP) Path Switch Request and applicable radio resource control (RRC) procedures. After the path switch procedure, the serving gNB triggers release of the UE context at the last serving gNB by the XnAP UE Context Release procedure.

If the UE is not reachable at the last serving gNB, the gNB fails any access and mobility management function (AMF) initiated UE-associated class 1 procedure which allows the signaling of unsuccessful operation in the respective response message, and triggers the non- access stratum (NAS) Non Delivery Indication procedure to report the non-delivery of any NAS protocol data unit (PDU) received from the AMF for the UE.

If the UE accesses a gNB other than the last serving gNB and the receiving gNB does not find a valid UE Context, the receiving gNB can perform establishment of a new RRC connection instead of resumption of the previous RRC connection. UE context retrieval will also fail and thus a new RRC connection needs to be established if the serving AMF changes.

A UE in the RRC INACTIVE state is required to initiate RNA update procedure when it moves out of the configured RNA. When receiving RNA update request from the UE, the receiving gNB triggers the XnAP Retrieve UE Context procedure to get the UE context from the last serving gNB and may decide to send the UE back to RRC INACTIVE state, move the UE into RRC CONNECTED state, or send the UE to RRC IDLE. For periodic RNA update, if the last serving gNB decides not to relocate the UE context, it fails the Retrieve UE Context procedure and sends the EE back to RRC IN ACTIVE, or to RRC IDLE directly by an encapsulated RRCRelease message.

The RRC Inactive Transition Report Request information element (E) is used to request the NG-RAN node to report or stop reporting to the fifth generation core (5GC) when the UE enters or leaves RRC INACTIVE state.

The NG-RAN node uses an RRC Inactive Transition Report procedure to notify the AMF when the UE enters or leaves RRC INACTIVE state. The NG-RAN node initiates the procedure by sending an RRC INACTIVE TRANSITION REPORT message to the AMF. Upon reception of the RRC INACTIVE TRANSITION REPORT message, the AMF takes appropriate actions based on the information indicated by the RRC State IE. The message includes the following IEs: Message Type; AMF UE NGAP ID; RAN UE NGAP ID; RRC State; and User Location Information. The AMF includes RRC Inactive Transition Report Request IE in a message from the

AMF to the NG-RAN node to request the NG-RAN node to report the RRC state and user location information of a specific UE when the UE enters or leaves RRC INACTIVE. The NG-RAN node that receives the RRC Inactive Transition Report Request IE sends the RRC Inactive Transition Report message for the specific UE to the AMF. The E indicates the RRC state of the UE.

The AMF sends a TRACE-START message to the NG-RAN node to initiate a trace session for a UE.

An NG-RAN node uses a Trace Failure Indication procedure to inform the AMF that a Trace Start procedure or a Deactivate Trace procedure has failed because of an interaction with a handover procedure. The NG-RAN node initiates the procedure by sending a TRACE FAILURE

INDICATION message. Upon reception of the TRACE FAILURE INDICATION message, the AMF takes appropriate actions based on the failure reason indicated by the Cause IE. The message includes the following IEs: Message Type; AMF UE NGAP ID; RAN UE NGAP ID; NG-RAN Trace ID; and Cause. The Trace Activation IE in TS 36.413 defines parameters related to a trace activation.

The Trace Activation IE in TS 38.413 defines parameters related to a trace session activation.

MDT types may be based on RRC states. In general, there are two types of MDT measurement logging, i.e., Logged MDT and Immediate MDT.

For logged MDT, a UE in RRC IDLE state is configured to perform periodical MDT logging after receiving the MDT configurations from the network. The UE reports the downlink pilot strength measurements (Reference Signal Received Power (RSRP)/Reference Signal Received Quality (RSRQ)) together with time information, detailed location information if available, and WLAN, Bluetooth to the network via using the UE information framework when it is in RRC CONNECTED state. The downlink pilot strength measurement of Logged MDT is collected based on the existing measurements required for cell reselection purpose, without imposing on the UE to perform additional measurements.

The UE receives the MDT configurations, including logginginterval and loggingduration , in the RRC message, i.e., LoggedMeasurementConfiguration , from the network. A timer (T330) is started at the UE upon receiving the configurations and set to loggingduration (10 min - 120 min). The UE performs periodical MDT logging with the interval set to logginginterval (1.28 s - 61.44 s) when the UE is in RRC IDLE. An example of MDT logging is illustrated in FIGURE 1. FIGURE l is a timeline illustrating an example logged MDT procedure. As illustrated, in connected mode, the UE receives MDT configuration. In idle mode, the UE performs MDT logging for a first logging interval and a second logging interval during the MDT logging duration. For Immediate MDT, the RAN and UE may perform measurements. There are a number of measurements (M1-M9) which are specified for RAN measurements and UE measurements. For UE measurements, the MDT configuration is based on the existing RRC measurement procedures for configuration and reporting with some extensions for location information. The measurement quantities for Immediate MDT are shown in the table below.

The reporting of the Immediate MDT is specified as follows. Ml reporting includes event-triggered measurement reports according to existing RRM configuration for events Al, A2, A3, A4, A5 A6, B1 or B2. Periodic, A2 event-triggered, or A2 event triggered periodic measurement report according to MDT specific measurement configuration. M2 reporting includes reception of Power Headroom Report (PHR) according to existing RRM configuration. M3 - M9 reporting is at the end of the measurement collection period. 5G NR includes separation of gNB central unit control plane (gNB-CU-CP) and gNB central unit user plane (gNB-CU-UP). An example is illustrated in FIGURE 2.

FIGURE 2 illustrates an architecture for separation of gNB-CU-CP and gNB-CU-UP. A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB distributed units (gNB-Dus). The gNB-CU-CP is connected to the gNB-DU through the Fl-C interface. The gNB-CU-UP is connected to the gNB-DU through the Fl-U interface. The gNB-CU-UP is connected to the gNB-CU-CP through the El interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP.

For resiliency, a gNB-DU and/or a gNB-CU-UP may be connected to multiple gNB- CU-CPs by appropriate implementation. One gNB-DU can be connected to multiple gNB-CU- UPs under the control of the same gNB-CU-CP. One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP.

The connectivity between a gNB-CU-UP and a gNB-DU is established by the gNB- CU-CP using Bearer Context Management functions. The gNB-CU-CP selects the appropriate gNB-CU-UP(s) for the requested services for the UE. In case of multiple CU-UPs they belong to same security domain as defined in TS 33.210. Data forwarding between gNB-CU-UPs during intra-gNB-CU-CP handover within a gNB may be supported by Xn-U.

LTE includes MDT as part of the Trace function, which is able to provide detailed logging data at a call level. Based on the methods of activating/deactivating trace and trace configuration, the trace function can be classified into the following two aspects.

In Management activation/deactivation, a trace session is activated/deactivated in different Network Elements (NE) directly from the Element Manager (EM) using the management interfaces of those NEs. In Signaling Based Activation/Deactivation, a trace session is activated/deactivated in different NEs using the signaling interfaces between those elements so that the NEs may forward the activation/deactivation originating from the EM.

In addition, the MDT may be classified as Area-based MDT and Signaling-based MDT from the following use case perspectives. For Area based MDT, MDT data is collected from UEs in a specified area. The area is defined as a list of cells (UTRAN or E-UTRAN) or as a list of tracking/routing/location areas. The area-based MDT is an enhancement of the management-based trace functionality. Area based MDT can be either a logged MDT or Immediate MDT.

For Signaling based MDT, MDT data is collected from one specific UE. The UE that is participating in the MDT data collection is specified as international mobile station equipment identity and software version number (IMEI(SV)) or as international mobile subscriber identity (IMSI). The signaling based MDT is an enhancement of the signaling based subscriber and equipment trace. The signaling based MDT can be either a logged MDT or Immediate MDT.

In LTE, for Area based MDT, the MDT control and configuration parameters are sent by the network management directly to the eNB. Then, the eNB selects UEs which fulfil the criteria including the area scope and the user consent and starts the MDT. For signaling-based MDT, i.e., UE specific MDT, the MDT control and configuration parameters are sent by the Network Management to a mobility management entity (MME) which then forwards the parameters to eNB associated with the specific UE.

FIGURE 3 is a block diagram summarizing the classification of MDT. As illustrated, both Area based MDT and Signaling based MDT include logged MDT and Immediate MDT

There currently exist certain challenges. For example, in a split RAN architecture, the MDT data is reported to a trace collection entity (TCE) by each node directly, while the user consent principles in LTE for MDT measurement activation means that the measurements can be taken only if the user has consented to provide measurements. However, in the split architecture the node that knows about user consent per UE is the CU-CP and therefore current methods are not sufficient to achieve the management based MDT Activation and in particular the case where the activation is done directly from operation and maintenance (O&M) node to a specific gNB node, i.e. gNB-CU-CP, gNB-CU-UP or gNB-DU.

SUMMARY

As described above, certain challenges currently exist with minimization of drive test (MDT) activation with a split radio access network (RAN) architecture. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Particular embodiments facilitate coordination of information held separately in gNB-CU-CP and in gNB-CU-UP or gNB-DU to select which user equipment (UE) have provided user consent and can therefore be used to collect measurements. Particular embodiments facilitate management based MDT Activation and, in particular, where the activation is done directly from O&M to a specific gNB node, i.e. gNB-CU-CP, gNB-CU-CP or gNB-DU.

For MDT in new radio (NR), UE Context Request and Trace Start on FI, Bearer context Setup and Trace Start on El are used for signaling based MDT activation. The element manager (EM) of each node may send the MDT activation to CU-CP, DU, and CU-UP directly. If a gNB-CU receives a management based MDT activation, it may propagate the MDT configuration to DU and/or CU-UP over FI and El if needed. The EM of each node may send the MDT deactivation to CU-CP, DU, and CU-UP directly. If a gNB-CU receives a management based MDT deactivation, it may propagate the management based MDT deactivation to DU and/or gNB-CU-UP if needed.

In non-split RAN architecture, the NG-RAN node reports the MDT data to the trace collection entity (TCE). In split RAN architecture, the MDT data is reported to the TCE by each node directly. The gNB-CU-CP may combine MDT data received by other nodes to report to the TCE.

As summarized, MDT in NR may follow the user consent principles agreed in long term evolution (LTE), which means that the measurements can be taken only if the user has consented to provide measurements. However, the node that knows about user consent per UE is the CU-CP. Therefore, in particular embodiments, upon reception of a management based MDT activation from the O&M system, the gNB-DU and/or the gNB-CU-UP contacts the gNB-CU-CP to ask which UEs have provided user consent and can therefore be selected to collect measurements. The CU-CP replies with an indication of user identities that enable the gNB-DU and/or gNB-CU-UP to identify the right UEs for collection of measurements.

Another group of embodiments concerns the gNB-CU-UP and the fact that, if an MDT activation including an MDT area is sent directly to CU-UP, CU-UP would not know which UEs to select because the CU-UP does not have knowledge about cells and cannot deduce which UEs are within the MDT area. In this case the CU-UP contacts CU-CP (same signaling used to request UEs that consented to the measurements) and provide the MDT area. CU-CP should respond with a list of UEs (UE identities or equivalent UE identifiers) that are within the MDT area. Namely, the CU-CP may provide a list of UEs to CU-UP that both have consented to the measurements and that are within the MDT area.

According to some embodiments, a method performed by split radio access network (RAN) network node for MDT comprises receiving a MDT activation request from a network management system. The activation request comprises an indication of a MDT area. The method further comprises transmitting an indication of MDT activation to a CU-CP; receiving, from the CU-CP, an indication of one or more wireless devices that consent to performing MDT; and performing MDT measurements towards the one or more wireless devices that consent to performing MDT and are within the MDT area.

In particular embodiments, the method further comprises determining which of the one or more wireless devices that consent to performing MDT are within the MDT area.

In particular embodiments, the indication of MDT activation includes the MDT area, and the received indication of one or more wireless devices that consent to performing MDT does not include wireless devices that are not within the MDT area.

In particular embodiments, the indication of MDT activation comprises an MDT activation notification based on the MDT activation request or a MDT assistance information request.

In particular embodiments, the MDT area comprises one or more cells or tracking areas.

In particular embodiments, performing MDT measurements comprises transmitting a trace activation request to the one or more wireless devices that consent to performing MDT and are within the MDT area.

In particular embodiments, the split RAN network node comprises one of a DU or a CU-UP.

According to some embodiments, a method performed by a split RAN network node CU-CP for MDT comprises: receiving an indication of MDT activation from a split RAN network node; determining one or more wireless devices that consent to performing MDT; and transmitting, to the split RAN network node, an indication of the one or more wireless devices that consent to performing MDT.

In particular embodiments, the indication of MDT activation includes an MDT area, the method further comprises determining which of the one or more wireless devices that consent to performing MDT are within the MDT area. The indication of the one or more devices that consent to performing MDT does not include wireless devices that are not within the MDT area.

According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments facilitate management based MDT Activation and, in particular, where the activation is done directly from O&M to a specific gNB node, i.e. gNB- CU-CP, gNB-CU-UP or gNB-DU, enabling coordination of information held separately in gNB-CU-CP and in gNB-CU-UP or gNB-DU.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIGURE l is a timeline illustrating an example logged MDT procedure;

FIGURE 2 illustrates an architecture for separation of gNB-CU-CP and gNB-CU-UP;

FIGURE 3 is a block diagram summarizing the classification of MDT;

FIGURE 4 is a flow diagram illustrating management based MDT activation in DU, according to a particular embodiment;

FIGURE 5 is another flow diagram illustrating management based MDT activation in DU, according to a particular embodiment;

FIGURE 6 is a flow diagram illustrating management based MDT activation in CU- UP, according to a particular embodiment; FIGURE 7 is another flow diagram illustrating management based MDT activation in CU-UP, according to a particular embodiment;

FIGURE 8 is a block diagram illustrating an example wireless network;

FIGURE 9 illustrates an example user equipment, according to certain embodiments;

FIGURE 10 is a flowchart illustrating an example method in a network node, according to certain embodiments;

FIGURE 11 is a flowchart illustrating another example method in a network node, according to certain embodiments;

FIGURE 12 illustrates a schematic block diagram of a wireless device and network node in a wireless network, according to certain embodiments;

FIGURE 13 illustrates an example virtualization environment, according to certain embodiments;

FIGURE 14 illustrates an example telecommunication network connected via an intermediate network to a host computer, according to certain embodiments;

FIGURE 15 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;

FIGURE 16 is a flowchart illustrating a method implemented, according to certain embodiments;

FIGURE 17 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments;

FIGURE 18 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments; and

FIGURE 19 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments.

DETAILED DESCRIPTION

As described above, certain challenges currently exist with minimization of drive test (MDT) activation with a split radio access network (RAN) architecture. For example, in a split RAN architecture, the MDT data is reported to a trace collection entity (TCE) by each node directly, while the user consent principles in long term evolution (LTE) for MDT measurement activation means that the measurements can be taken only if the user has consented to provide measurements. However, in the split architecture the node that knows about user consent per UE is the central unit control plane (CU-CP) and therefore current methods are not sufficient to achieve the management based MDT Activation and in particular the case where the activation is done directly from operation and maintenance (O&M) node to a specific gNB node, i.e. gNB-CU-CP, gNB-CU-UP or gNB-DU.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Particular embodiments facilitate coordination of information held separately in gNB-CU-CP and in gNB-CU-UP or gNB-DU to select which user equipment (UE) have provided user consent and can therefore be used to collect measurements. Particular embodiments facilitate management based MDT Activation and, in particular, where the activation is done directly from O&M to a specific gNB node, i.e. gNB-CU-CP, gNB-CU-CP or gNB-DU.

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

As described above, MDT in NR may use the user consent principles from LTE, which means that measurements are taken only if the user has consented to provide measurements. However, the node that knows about user consent per UE is the CU-CP. The latter is because the CU-CP is provided such user consent information by the access and mobility management function (AMF). Therefore, in particular embodiments, upon reception of a management based MDT activation from the O&M system, the gNB-DU and/or the gNB-CU-UP contact the gNB- CU-CP to ask which UEs out of the UEs served by the CU-UP and/or DU have provided user consent and can therefore be selected to collect measurements. The CU-CP replies with an indication of user identities that allow the gNB-DU and/or gNB-CU-UP to identify the right UEs for collection of measurements.

Another group of embodiments concerns the gNB-CU-UP and the fact that if an MDT activation including an MDT area is sent directly to CU-UP, the CU-UP does not know which UEs to select because the CU-UP does not have knowledge about cells and cannot deduce which UEs are within the MDT area. In this case, the CU-UP contacts the CU-CP (e.g. by using the same signaling used to request UEs that consented to the measurements) and may provide the MDT area. The CU-CP responds with a list of UEs (UE identities or equivalent UE identifiers) that are within the MDT area and that are served by the CU-UP. Namely, the CU- CP may provide a list of UEs to CU-UP that both have consented to the measurements and that are within the MDT area.

Some embodiments include FI related signaling flow for management based MDT. Based the description above, FIGURES 4-7 illustrate the signaling flow for management based MDT. FIGURES 4 and 5 illustrate scenarios when O&M initiates MDT in the DU. FIGURES 6 and 7 illustrate scenarios when O&M initiates MDT in the CU-UP.

FIGURE 4 is a flow diagram illustrating management based MDT activation in DU, according to a particular embodiment. At step 1, the EM sends a Trace Session activation request to the DU. The request includes the parameters for configuring UE measurements, such as trace reference, trace depth, NG-RAN cells list (or an indication of the MDT area within which UE measurements need to be collected), list of interfaces for NG-RAN node, and IP address of Trace Collection Entity.

At step 2, the DU sends the MDT configuration information as part of an MDT notification message to the CU-CP. At step 3, the CU-CP selects the suitable UEs for MDT data collection. The selection is based on the MDT allowed area and UE consent received from the O&M, and the CU-CP replies with an indication of user identities that enable the gNB-DU to identify the right UEs for collection of measurements. This can be carried, for example, by a GNB CU CONFIGURATION UPDATE message or UE associated signaling like UE context setup request.

At step 4, the DU selects the suitable UEs for MDT data collection based on the received UE identifiers. The selection is based on the area received from the EM and the area where the UE is located. If the user is not in the specified area or if the Management Based MDT Allowed IE is not present in the UE context, the UE may not be selected by the DU for MDT data collection.

For each selected user, the DU sends an indication to the CU-CP in the FI either in a GNB-CU CONFIGURATION UPDATE ACKNOWLDGE message, including the RAN UE ID of the selected UE (or associated UE identifier), the NG-RAN Trace ID, serving cell CGI, TCE IP address and Privacy Indicator, or a UE associated signaling, including the NG-RAN Trace ID, serving cell CGI, TCE IP address and Privacy Indicator.

Another way to perform Management Based MDT Activation at the gNB-DU is illustrated in FIGUE 5.

FIGURE 5 is another flow diagram illustrating management based MDT activation in DU, according to a particular embodiment. At step 1, the EM sends a Trace Session activation request to the DU. The request includes the parameters for configuring UE measurements, such as trace reference, trace depth, NG-RAN cells list (or an indication of the MDT area within which UE measurements need to be collected), list of interfaces for NG-RAN node, and IP address of Trace Collection Entity.

At step 2, the DU sends the MDT Assistance Information message to the CU-CP, including the MDT area that was signaled to it by the OAM for the Management Based MDT activation. At step 3, the CU-CP selects the suitable UEs for MDT data collection. The selection is based on the MDT allowed area and UE consent received from the O&M, and the CU-CP replies with an MDT Assistance Information Response including a list of user identities that enable the gNB-DU to identify the right UEs for collection of measurements.

At reception of Message 3, the DU selects the suitable UEs for MDT data collection based on the received UE identifiers. The selection is based on the area received from the EM and the area where UE is located. If the user is not in the specified area or if the Management Based MDT Allowed IE is not present in the UE context, the UE may not be selected by the DU for MDT data collection.

Some embodiments include El related signaling flow for management based MDT. An example is illustrated in FIGURE 6.

FIGURE 6 is a flow diagram illustrating management based MDT activation in CU- UP, according to a particular embodiment. At step 1, the EM sends a Trace Session activation request to the CU-UP. The request includes the parameters for configuring UE measurements, such as trace reference, trace depth, NG-RAN cells list (or an indication of the MDT area within which UE measurements need to be collected), list of interfaces for NG-RAN node, and IP address of Trace Collection Entity.

At step 2, the CU-UP sends the MDT configuration information as part of an MDT notification message to the CU-CP. At step 3, the CU-CP selects the suitable UEs for MDT data collection. The selection is based on the MDT allowed area and UE consent received from the O&M, and the CU-CP replies with an indication of user identities that enable the gNB-CU- UP to identify the right UEs for collection of measurements. This can be carried, for example, by a GNB CU-CP CONFIGURATION UPDATE message or UE associated signaling like UE bearer context setup request.

At step 4, the CU-UP selects the suitable UEs for MDT data collection based on the received UE identifiers. The selection is based on the area received from the EM and the area where UE is located. If the user is not in the specified area or if the Management Based MDT Allowed IE is not present in the UE context, the UE may not be selected by the DU for MDT data collection.

For each selected user, the CU-UP sends an indication to the CU-CP in El either in a GNB-CU-UP CONFIGURATION UPDATE ACKNOWLDGE message, including the RAN UE ID of the selected UE (or associated UE identifier), the NG-RAN Trace ID, TCE IP address and Privacy Indicator, or a UE associated signaling, including the NG-RAN Trace ID, serving cell CGI, TCE IP address and Privacy Indicator.

The CU-UP selects the suitable UEs for MDT data collection. The selection is based on the area received from the EM and the area where UE is located. If the relationship between cell and tracking area code (TAC) is preconfigured in the CU-UP, the CU-UP can know the UE located TAC from the serving cell ID.

For each selected user, the CU-UP sends Cell Traffic Trace to the CU-CP in the FI UE associated signaling, including the NG-RAN Trace ID, serving cell CGI, TCE IP address and Privacy Indicator.

Another way to perform the Management Based MDT Activation at the gNB-CU-UP is illustrated in FIGURE 7.

FIGURE 7 is another flow diagram illustrating management based MDT activation in CU-UP, according to a particular embodiment. At step 1, the EM sends a Trace Session activation request to the CU-UP. The request includes the parameters for configuring UE measurements, such as trace reference, trace depth, NG-RAN cells list (or an indication of the MDT area within which UE measurements need to be collected), list of interfaces for NG-RAN node, and IP address of Trace Collection Entity.

At step 2, the CU-UP sends the MDT Assistance Information message to the CU-CP, including the MDT area that was signaled to it by the OAM for the Management Based MDT activation. At step 3, the CU-CP selects the suitable UEs for MDT data collection. The selection is based on the MDT allowed area and UE consent received from the O&M, and the CU-CP replies with an MDT Assistance Information Response including a list of user identities that allow the gNB-CU-UP to identify the right UEs for collection of measurements. The CU-CP knows the location of UEs and therefore is able to select them appropriately after it receives the MDT Area information.

At reception of Message 3, the DU selects the suitable UEs for MDT data collection based on the received UE identifiers. The selection is based on the area received from the EM and the area where the UE is located. If the user is not in the specified area or if the Management Based MDT Allowed IE is not present in the UE context, the UE may not be selected by the DU for MDT data collection.

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

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

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

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.

Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.

A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.

As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIGURE 8, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIGURE 8 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.

It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node.

In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.

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

Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality.

For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 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 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, gNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.

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

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

In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

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

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

Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160.

For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 8 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.

In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.

Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.

As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one example, the WD may be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).

In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110.

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

As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114.

Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.

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

As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of WD 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips.

In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.

In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110, and/or by end users and the wireless network generally.

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

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

User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).

User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.

Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario. Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry.

Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.

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

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

In FIGURE 9, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 213, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may use all the components shown in FIGURE 9, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205.

An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.

UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

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

RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.

Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.

Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium. In FIGURE 9, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

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

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

FIGURE 10 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 10 may be performed by network node 160 described with respect to FIGURE 8. The network node is a split RAN network node (e.g., DU or CU-UP) operable to perform MDT.

The method begins at step 1012, where the network node (e.g., network node 160) receives a MDT activation request from a network management system. The activation request comprises an indication of a MDT area (e.g., one or more cells or tracking areas). The network node then must determine what UEs in the MDT area consent to MDT.

To do that, at step 1014, the network node transmits an indication of MDT activation to a CU-CP. In some embodiments, the indication of MDT activation comprises an MDT activation notification based on the MDT activation request or a MDT assistance information request. The indication of MDT activation may or may not include the MDT area.

At step 1016, the network node receives from the CU-CP, an indication of one or more wireless devices that consent to performing MDT. The network node may or may not know if the indicated wireless devices are in the MDT area. For example, in some embodiments the network node may not know what wireless devices are in the MDT area. The network node, in previous step 1014, may send the MDT area to the CU-CP. The response from the CU-CP may include nodes that consent to MDT and are in the MDT area.

In some embodiments, the network node may have the information to determine what wireless devices are in the MDT area, and the response from the CU-CP may only include wireless devices that consent to MDT. In these embodiments, the method may include step 1018, where the network node determining which of the one or more wireless devices that consent to performing MDT are within the MDT area. Specific example are described above with respect to FIGURES 4-7.

At step 1020, the network node performs MDT measurements towards the one or more wireless devices that consent to performing MDT and are within the MDT area. The network node may perform some measurements and/or the network node may transmit a trace activation request to the one or more wireless devices that consent to performing MDT and are within the MDT area.

Modifications, additions, or omissions may be made to method 1000 of FIGURE 10. Additionally, one or more steps in the method of FIGURE 10 may be performed in parallel or in any suitable order.

FIGURE 11 is a flowchart illustrating another example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 11 may be performed by network node 160 described with respect to FIGURE 8. The network node is a split RAN network node (e.g., CU-CP) operable to perform MDT.

The method begins at step 1112, where the network node (e.g., network node 160) receives an indication of MDT activation from a split RAN network node. For example, the network node may receive the indication described with respect to step 1014 of FIGURE 10.

At step 1114, the network node determines one or more wireless devices that consent to performing MDT. The network node may determine the wireless devices according to any of the embodiments and examples described above with respect to FIGURES 4-7.

At step 1116, the network node transmits, to the split RAN network node, an indication of the one or more wireless devices that consent to performing MDT. The indication is described with respect to step 1016 of FIGURE 10.

Modifications, additions, or omissions may be made to method 1100 of FIGURE 11. Additionally, one or more steps in the method of FIGURE 11 may be performed in parallel or in any suitable order.

FIGURE 12 illustrates a schematic block diagram of an apparatus in a wireless network (for example, the wireless network illustrated in FIGURE 8). The apparatus includes a network node (e.g., network node 160 illustrated in FIGURE 8). Apparatus 1700 is operable to carry out the example methods described with reference to FIGURES 10 and 11, and possibly any other processes or methods disclosed herein. It is also to be understood that the methods of FIGURES 10 and 11 are not necessarily carried out solely by apparatus 1700. At least some operations of the methods can be performed by one or more other entities.

Virtual apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.

In some implementations, the processing circuitry may be used to cause receiving module 1702, determining module 1704, transmitting module 1706, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in FIGURE 12, apparatus 1700 includes receiving module 1702 configured to receive MDT activation requests, indications of MDT activation, and/or indications of one or more wireless devices that consent to performing MDT, according to any of the embodiments and examples described herein. Determining module 1704 is configured to determine what wireless devices consent to performing MDT and/or what wireless devices are in a MDT area, according to any of the embodiments and examples described herein. Transmitting module 1706 is configured to transmit indications of MDT activation and/or indications of wireless devices that consent to performing MDT, according to any of the embodiments and examples described herein.

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

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

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

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

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

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

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

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 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 virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE). Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in FIGURE 13.

In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 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 effected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

With reference to FIGURE 14, in accordance with an embodiment, a communication system includes telecommunication network 410, such as a 3 GPP -type cellular network, which comprises access network 411, such as a radio access network, and core network 414. Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.

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

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

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

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

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

It is noted that host computer 510, base station 520 and UE 530 illustrated in FIGURE 15 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 14, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 15 and independently, the surrounding network topology may be that of FIGURE 14.

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

Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the signaling overhead and reduce latency, and thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery life.

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

FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 15 will be included in this section.

In step 610, the host computer provides user data. In substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIGURE 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 16 will be included in this section. In step 710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

FIGURE 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 17 will be included in this section.

In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally, or alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIGURE 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 18 will be included in this section.

In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

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

Modifications, additions, or omissions may be made to the systems and apparatuses disclosed herein without departing from the scope of the invention. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). lx RTT CDMA2000 lx Radio Transmission Technology

3 GPP 3rd Generation Partnership Project

5G 5th Generation

ABS Almost Blank Subframe

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI

EM Element Manager eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex

GERAN GSM EDGE Radio Access Network gNB Base station in NR gNB-CU gNB Central Unit gNB-CU-CP gNB-CU Control Plane gNB-CU-UP gNB-CU User Plane gNB -DU gNB Distributed Unit

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

IE Information Element

IMEI International Mobile Station Equipment Identity IMEI(SV) International Mobile station Equipment Identity and Software Version number

IMSI International Mobile Subscriber Identity

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NAS Non-Access Stratum

NE Network Element

NG Next Generation

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

O&M Operation and Maintenance

OAM Operation and Maintenance

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel PHR Power Headroom Report

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QoS Quality of Service

RAN Radio Access Network

RAT Radio Access Technology

RLM Radio Link Management

RNA RAN Notification Area

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR Reference Signal Received Power

RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information SIB System Information Block

SNR Signal to Noise Ratio

SON Self Optimized Network ss Synchronization Signal SSS Secondary Synchronization Signal

TAC Tracking Area Code TCE Trace Collection Entity TDD Time Division Duplex TDOA Time Difference of Arrival TTI Transmission Time Interval

UE User Equipment UL Uplink

UMTS Universal Mobile Telecommunication System

UPF User Plane Function USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA Wide CDMA WLAN Wide Local Area Network XnAP Xn Application Protocol

Claims

CLAIMS:

1. A method performed by a split radio access network (RAN) network node for minimization of drive test (MDT), the method comprising: receiving (1012) a MDT activation request from a network management system, the activation request comprising an indication of a MDT area; transmitting (1014) an indication of MDT activation to a central unit control plane (CU- CP); receiving (1016), from the CU-CP, an indication of one or more wireless devices that consent to performing MDT; and. performing (1020) MDT measurements towards the one or more wireless devices that consent to performing MDT and are within the MDT area.

2. The method of claim 1, further comprising determining (1018) which of the one or more wireless devices that consent to performing MDT are within the MDT area.

3. The method of claim 1, wherein the indication of MDT activation includes the MDT area, and the received indication of one or more wireless devices that consent to performing MDT does not include wireless devices that are not within the MDT area.

4. The method of any one of claims 1-3, wherein the indication of MDT activation comprises an MDT activation notification based on the MDT activation request.

5. The method of any one of claims 1-3, wherein the indication of MDT activation comprises a MDT assistance information request.

6. The method of any one of claims 1-5, wherein the MDT area comprises one or more cells or tracking areas.

7. The method of any one of claims 1-6, wherein performing MDT measurements comprises transmitting a trace activation request to the one or more wireless devices that consent to performing MDT and are within the MDT area.

8. The method of any one of claims 1-7, wherein the split RAN network node comprises one of a distributed unit (DU) or a central unit user plane (CU-UP).

9. A split radio access network (RAN) network node (160) operable to perform minimization of drive test (MDT), the network node comprising processing circuitry (170) operable to: receive a MDT activation request from a network management system, the activation request comprising an indication of a MDT area; transmit an indication of MDT activation to a central unit control plane (CU-CP); receive, from the CU-CP, an indication of one or more wireless devices that consent to performing MDT; and. perform MDT measurements towards the one or more wireless devices that consent to performing MDT and are within the MDT area.

10. The split RAN network node of claim 9, the processing circuitry further operable to determine which of the one or more wireless devices that consent to performing MDT are within the MDT area.

11. The split RAN network node of claim 9, wherein the indication of MDT activation includes the MDT area, and the received indication of one or more wireless devices that consent to performing MDT does not include wireless devices that are not within the MDT area.

12. The split RAN network node of any one of claims 9-11, wherein the indication of MDT activation comprises an MDT activation notification based on the MDT activation request.

13. The split RAN network node of any one of claims 9-11, wherein the indication of MDT activation comprises a MDT assistance information request.

14. The split RAN network node of any one of claims 9-13, wherein the MDT area comprises one or more cells or tracking areas.

15. The split RAN network node of any one of claims 9-14, wherein performing MDT measurements comprises transmitting a trace activation request to the one or more wireless devices that consent to performing MDT and are within the MDT area.

16. The split RAN network node of any one of claims 9-15, wherein the split RAN network node comprises one of a distributed unit (DU) or a central unit user plane (CU-UP).

17. A method performed by a split radio access network (RAN) network node central unit control plane (CU-CP) for minimization of drive test (MDT), the method comprising: receiving (1112) an indication of MDT activation from a split RAN network node; determining (1114) one or more wireless devices that consent to performing MDT; and transmitting (1118), to the split RAN network node, an indication of the one or more wireless devices that consent to performing MDT.

18. The method of claim 17, wherein the indication of MDT activation includes an MDT area, the method further comprising determining (1116) which of the one or more wireless devices that consent to performing MDT are within the MDT area, and wherein the indication of the one or more devices that consent to performing MDT does not include wireless devices that are not within the MDT area.

19. The method of any one of claims 17-18, wherein the MDT area comprises one or more cells or tracking areas.

20. The method of any one of claims 17-19, wherein the split RAN network node comprises one of a distributed unit (DU) or a central unit user plane (CU-UP).

21. A split radio access network (RAN) network node (160) central unit control plane (CU-CP) operable to perform minimization of drive test (MDT), the network node comprising processing circuitry (170) operable to: receive an indication of MDT activation from a split RAN network node; determine one or more wireless devices that consent to performing MDT; and transmit, to the split RAN network node, an indication of the one or more wireless devices that consent to performing MDT.

22. The split RAN network node of claim 20, wherein the indication of MDT activation includes an MDT area, the method further comprising determining (1116) which of the one or more wireless devices that consent to performing MDT are within the MDT area, and wherein the indication of the one or more devices that consent to performing MDT does not include wireless devices that are not within the MDT area.

23. The split RAN network node of any one of claims 21-23, wherein the MDT area comprises one or more cells or tracking areas.

24. The split RAN network node of any one of claims 21-23, wherein the split RAN network node comprises one of a distributed unit (DU) or a central unit user plane (CU-UP).