METHODS RELATING TO MDT CONFIGURATIONS AND RELATED DEVICES

TECHNICAL FIELD

The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.

BACKGROUND

MDT activation and configuration for an RRC Inactive UE is discussed below.

MDT was firstly studied in Rel-9 (TR 36.805) driven by RAN2 with the purpose to reduce/minimize the actual drive tests. MDT has been introduced since Rel-10 in LTE. MDT has not been specified for NR in the involved standards in RAN2, RAN3 and SA5 groups.

The use cases in the TR 36.805 include: Coverage optimization/improvement; Mobility optimization/improvement; Capacity optimization/improvement; Parameterization for common channels; and QoS verification.

The RRC INACHVE state has been introduced in Rel-15 in NR to reduce the latency and the number of signals of the connection establishment. A UE in RRC INACHVE shall obtain normal service when camping on a suitable cell and operator service when camping on a reserved cell. The UE in RRC INACHVE shall perform cell reselection and the required measurements on the serving cell and neighbor cells, similar to that for the UE in RRC IDLE state.

RRC INACHVE is a state where a UE remains in CM-CONNECTED and can move within an area configured by NG-RAN (the RNA) without notifying NG-RAN. In

RRC_INACTIVE, the last serving gNB node (i.e., the RAN node providing the last serving cell) keeps the UE context and the UE-associated NG connection with the serving AMF and 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 shall perform the slice-aware admission control in case of receiving slice information and becomes the serving gNB and it further triggers the NGAP Path Switch Request and applicable RRC procedures. After the path switch procedure, the serving gNB (i.e., the RAN node providing the serving cell) triggers release of the UE context at the last serving gNB by means of the XnAP UE Context Release procedure.

In case the UE is not reachable at the last serving gNB, the gNB shall: Fail any AMF initiated UE -associated class 1 procedure which allows the signaling of an unsuccessful operation in the respective response message; and Trigger the NAS Non Delivery Indication procedure to report the non-delivery of any NAS 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 hence a new RRC connection needs to be established if the serving AMF changes.

A UE in the RRC INACTIVE state is required to initiate an 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. In case of 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 UE back to RRC_INACTIVE, or to RRC IDLE directly by an encapsulated RRCRelease message.

The RRC Inactive Transition Report Request IE is used to request the NG-RAN node to report or stop reporting to the 5GC when the UE enters or leaves RRC INACTIVE state. The IE is illustrated in the table of Figure 13.

The RRC Inactive Transition Report is discussed below.

The purpose of the RRC Inactive Transition Report procedure is for NG-RAN node 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 shall take 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; User Location Information.

AMF includes RRC Inactive Transition Report Request IE in a message from AMF to NG-RAN node to request NG-RAN node to report the RRC state and user location information of a specific UE when the UE enters or leaves R R C l N A C TI V E . NG-RAN node which receives the RRC Inactive Transition Report Request IE sends the RRC Inactive Transition Report message for the specific UE to the AMF. This IE indicates the RRC state of the UE, and this IE is illustrated in the table of Figure 14.

The TRACE START message is sent by the AMF to initiate a trace session for a UE. Direction: AMF -> NG-RAN node. The TRACE START message is illustrated in the table of Figure 15.

Trace Failure Indication is discussed below.

The purpose of the Trace Failure Indication procedure is to allow the NG-RAN node to inform the AMF that a Trace Start procedure or a Deactivate Trace procedure has failed due to 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 shall take 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; Cause.

The Trace Activation IE in TS 36.413 defines parameters related to a trace activation. Aspects of the Trace Activation IE are illustrated in the table of Figures 16A and 16B.

The Trace Activation IE in TS 38.413 defines parameters related to a trace session activation. Aspects of the Trace Activation IE are illustrated in the table of Figures 17A and 17B.

MDT types based on RRC states are discussed below.

In general, there are two types of MDT measurement logging, i.e., Logged MDT and Immediate MDT.

Logged MDT is discussed below.

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

The measurement logging for Logged MDT is illustrated in the table of Figure 18.

For Logged MDT, UE receives the MDT configurations including logginginterval and logging duration 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 logging duration (10 min - 120 min). The UE shall perform 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 the MDT logging is shown in Figure 19.

Figure 19 illustrates an example of Logged MDT procedure.

Measurements for Immediate MDT purpose can be performed by RAN and UE. There are several measurements (Ml -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 of Figure 20.

The measurement quantities for Immediate MDT are also provided below

Ml : RSRP and RSRQ measurement by UE.

M2: Power Headroom measurement by UE.

M3: Received Interference Power measurement by eNB.

M4: Data Volume measurement separately for DL and UL, per QCI per UE, by eNB.

M5: Scheduled IP Throughput for MDT measurement separately for DL and UL, per RAB per UE and per UE for the DL, per UE for the UL, by eNB.

M6: Packet Delay measurement, separately for DL and UL, per QCI per UE, see UL PDCP Delay, by the UE, and Packet Delay in the DL per QCI, by the eNB.

M7: Packet Loss rate measurement, separately for DL and UL per QCI per UE, by the eNB.

M8: RSSI measurement by UE.

M9: RTT measurement by UE. The reporting of the Immediate MDT is specified as follows.

• For Ml :

o Event-triggered measurement reports according to existing RRM configuration for events Al, A2, A3, A4, A5 A6, B1 or B2.

o Periodic, A2 event-triggered, or A2 event triggered periodic measurement report according to MDT specific measurement configuration.

• For M2: Reception of Power Headroom Report (PHR) according to existing RRM configuration.

• For M3 - M9: End of measurement collection period.

An Overall architecture for separation of gNB-CU-CP and gNB-CU-UP is discussed below.

The overall architecture for separation of gNB-CU-CP and gNB-CU-UP is depicted in Figure 21.

• A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple 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;

NOTE 1 : 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;

NOTE 2: The connectivity between a gNB-CU-UP and a gNB-DU is established by the gNB-CU-CP using Bearer Context Management functions.

NOTE 3: 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 [18] NOTE 4: Data forwarding between gNB-CU-UPs during intra-gNB-CU-CP handover within a gNB may be supported by Xn-U.

Activation and Configuration of MDT in LTE is discussed below.

When MDT was introduced in Rel-10, it was decided to include MDT as a part of the Trace function which can provide very detailed logging data at call level. Based on the processes of activating/deactivating trace and trace configuration, the trace function can be classified into the following two aspects discussed below: Management Activation/Deactivation; and Signaling Based Activation/Deactivation.

Management activation/deactivation: Trace Session is activated/deactivated in different Network Elements (NE) directly from the Element Manager (EM) using the management interfaces of those NEs.

Signaling Based Activation/Deactivation: 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.

On the other hand, the MDT can be classified as Area-based MDT and Signaling -based MDT from the use case perspective illustrated and discussed below.

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.

Signaling based MDT: MDT data is collected from one specific UE. The UE that is participating in the MDT data collection is specified as IMEI(SV) or as IMS! 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 MME which then forwards the parameters to eNB associated with the specific UE. Figure 22 summarizes the classification of the MDT. MDT configuration/activation for a UE which may transit to/from an RRC Inactive state, however, may not be sufficiently supported.

SUMMARY

According to some embodiments, a method is provided to operate a radio access network (RAN) node of a wireless communication network. Information for a minimization of drive tests (MDT configuration for a wireless device is received. A connection state of the wireless device is determined. An MDT configuration state of the wireless device is determined based on the connection state of the wireless device. An MDT configuration state indicator for the wireless device is stored in a context for the wireless device wherein the MDT configuration state indicator is based on the MDT configuration state of the wireless device. The information for the MDT configuration is stored in the context for the wireless device.

According to some embodiments, a RAN node is provided. The RAN node is adapted to: receive information for a MDT configuration for a wireless device; determine a connection state of the wireless device; determine an MDT configuration state of the wireless device based on the connection state of the wireless device; store an MDT configuration state indicator for the wireless device in a context for the wireless device wherein the MDT configuration state indicator is based on the MDT configuration state of the wireless device; and store the information for the MDT configuration in the context for the wireless device.

According to some embodiments, a RAN node includes processing circuitry, and memory coupled with the processing circuitry. The memory includes instructions that when executed by the processing circuitry causes the RAN node to: receive information for a MDT configuration for a wireless device; determine a connection state of the wireless device;

determine an MDT configuration state of the wireless device based on the connection state of the wireless device; store an MDT configuration state indicator for the wireless device in a context for the wireless device wherein the MDT configuration state indicator is based on the MDT configuration state of the wireless device; and store the information for the MDT configuration in the context for the wireless device.

According to some embodiments, a method is provided to operate a first RAN node of a wireless communication network. A request for a context for a wireless device is transmitted to a second RAN node. A context response is received from the second RAN node. The context response includes the context for the wireless device, and the context for the wireless device includes an MDT configuration state indicator for the wireless device and information for an MDT configuration for the wireless device.

According to some embodiments, a first RAN node is provided. The first RAN node is adapted to: transmit a request for a context for a wireless device to a second RAN node; and receive a context response from the second RAN node. The context response includes the context for the wireless device, and the context for the wireless device includes an MDT configuration state indicator for the wireless device and information for an MDT configuration for the wireless device.

According to some embodiments, a first RAN node includes processing circuitry and memory coupled with the processing circuitry. The memory includes instructions that when executed by the processing circuitry causes the RAN node to: transmit a request for a context for a wireless device to a second RAN node; and receive a context response from the second RAN node. The context response includes the context for the wireless device, and the context for the wireless device includes an MDT configuration state indicator for the wireless device and information for an MDT configuration for the wireless device.

According to some embodiments, a method is provided to operate a core network (CN) node of a communication network. Information for a MDT configuration for a wireless device is transmitted to a first RAN node. A request is received from a second RAN node wherein the request indicates that the wireless device is not configured with the MDT configuration.

According to some embodiments, a CN node is provided. The CN node is adapted to: transmit information for a MDT configuration for a wireless device to a first RAN node; and receive a request from a second RAN node. The request indicates that the wireless device is not configured with the MDT configuration.

According to some embodiments, a CN node is provided. The CN node includes processing circuitry and memory coupled with the processing circuitry. The memory includes instructions that when executed by the processing circuitry causes the CN node to: transmit information for a MDT configuration for a wireless device to a first RAN node; and receive a request from a second RAN node wherein the request indicates that the wireless device is not configured with the MDT configuration. According to some embodiments of inventive concepts, handling of MDT configurations may be improved for UEs which may transit to/from an inactive state (e.g. Radio Resource Control (RRC) inactivate state). As an example according to some embodiments, by providing both MDT configuration and an MDT configuration state to a second RAN node responsive to a context request from the second RAN node, the second RAN node is enabled to both identify if a UE has been configured with a certain MDT configuration (so the second RAN node e.g. knows which MDT reports it can expect from the UE, can deduce whether it is desirable to modify the UEs current MDT configuration etc) and also to identify if the UE should be configured with a certain MDT configuration.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

Figure 1 is a diagram illustrating a first scenario where the last serving cell provided by RAN node gNBlOl receiving the signaling-based MDT configuration for a UE in

RRC INACTIVE cannot be used to perform the MDT configuration according to some embodiments of inventive concepts;

Figure 2 is a diagram illustrating a second scenario where the last serving cell provided by RAN node gNBlOl receiving MDT configuration cannot be used to configure UE to perform MDT measurements according to some embodiments of inventive concepts;

Figure 3 is a diagram illustrating a third scenario where the last serving cell provided by RAN node gNBlOl receiving MDT configuration cannot be used to configure UE to perform MDT measurements according to some embodiments of inventive concepts;

Figure 4 is a signal flow diagram illustrating a successful activation operation in the first scenario according to some embodiments of inventive concepts;

Figure 5 is a signal flow diagram illustrating an unsuccessful activation operation in the first scenario according to some embodiments of inventive concepts;

Figure 6 is a diagram illustrating another example of the first scenario where the RAN node gNBlOl that provided the last serving cell sends Trace Failure indication to the AMF if the specific UE is in RRC INACTIVE when RAN node gNBlOl receives Trace Start from the AMF according to some embodiments of inventive concepts; Figure 7 is a signal flow diagram illustrating a successful deactivation operation in the first scenario according to some embodiments of inventive concepts;

Figure 8 is a signal flow diagram illustrating an unsuccessful deactivation operation in the first scenario according to some embodiments of inventive concepts;

Figure 9 is a diagram illustrating an AMF receiving Trace Resume Indication before the expiration of a timer according to some embodiments of inventive concepts;

Figure 10 is a signal flow diagram illustrating an AMF receiving Trace Resume Indication before the expiration of a timer according to some embodiments of inventive concepts;

Figure 11 is a signal flow diagram illustrating an AMF sending Trace start to another gNB after the expiration of a timer according to some embodiments of inventive concepts;

Figure 12 is a signal flow diagram illustrating an AMF sending Trace start to another gNB after the expiration of a timer according to some embodiments of inventive concepts;

Figure 13 is a table illustrating an IE used to request the NG-RAN node;

Figure 14 is a table illustrating an IE indicating the RRC state of the UE;

Figure 15 is a table illustrating a message sent by an AMF to initiate a trace session for a UE;

Figures 16A and 16B provide a table illustrating parameters related to a trace activation;

Figures 17A and 17B provide a table illustrating parameters related to a trace session activation;

Figure 18 is a table illustrating measurement logging for logged MDT;

Figure 19 is a diagram illustrating a logged MDT procedure;

Figure 20 is a table illustrating measurement quantities for immediate MDT;

Figure 21 is a block diagram illustrating an architecture for separation of gNB-CU-CP and gNB-CU-UP;

Figure 22 is a diagram illustrating a summary of MDT classification;

Figure 23 is a table illustrating an RRC Inactive Transition Report Request IE with ready for Trace/MDT activation report according to some embodiments of inventive concepts;

Figure 24 is a block diagram illustrating a wireless device UE according to some embodiments of inventive concepts; Figure 25 is a block diagram illustrating a radio access network RAN node (e.g., a base station eNB/gNB) according to some embodiments of inventive concepts;

Figure 26 is a block diagram illustrating a core network CN node (e.g., an AMF node, an SMF node, an OAM node, etc.) according to some embodiments of inventive concepts;

Figure 27 is a signal flow diagram illustrating NG-RAN node, AMF node, and OAM node operations on setting a status of an MDT configuration, (i.e., a pending or activated MDT configuration) in the NG-RAN node providing the serving cell (also referred to as a serving RAN node) according to some embodiments of inventive concepts;

Figures 28A and 28B provide a signal flow diagram illustrating NG-RAN node and AMF node operations on receiving a UE context request according to some embodiments of inventive concepts;

Figures 29A and 29B provide a signal flow diagram illustrating RAN node and AMF node operations on reception of UE context including MDT activation/configuration according to additional embodiments of inventive concepts;

Figures 30, 31, 32, 33, 34, and 35 are flow charts illustrating Radio Access Network, RAN, node operations according to some embodiments of inventive concepts;

Figures 36, 37, and 38 are flow charts illustrating core network node operations according to some embodiments of inventive concepts;

Figure 39 is a block diagram of a wireless network in accordance with some

embodiments;

Figure 40 is a block diagram of a user equipment in accordance with some embodiments

Figure 41 is a block diagram of a virtualization environment in accordance with some embodiments;

Figure 42 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;

Figure 43 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;

Figure 44 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; Figure 45 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

Figure 46 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; and

Figure 47 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

DETAILED DESCRIPTION

Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

Figure 24 is a block diagram illustrating elements of a wireless device UE 900 (also referred to as a mobile terminal, a mobile communication terminal, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Wireless device 900 may be provided, for example, as discussed below with respect to wireless device QQ110 of Figure 39.) As shown, wireless device UE may include an antenna 907 (e.g., corresponding to antenna QQ111 of Figure 39), and transceiver circuitry 901 (also referred to as a transceiver, e.g., corresponding to interface QQ114 of Figure 39) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node QQ160 of Figure 39, also referred to as a RAN node) of a radio access network. Wireless device UE may also include processing circuitry 903 (also referred to as a processor, e.g., corresponding to processing circuitry QQ120 of Figure 39) coupled to the transceiver circuitry, and memory circuitry 905 (also referred to as memory, e.g., corresponding to device readable medium QQ130 of Figure 39) coupled to the processing circuitry. The memory circuitry 905 may include computer readable program code that when executed by the processing circuitry 903 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 903 may be defined to include memory so that separate memory circuitry is not required. Wireless device UE may also include an interface (such as a user interface) coupled with processing circuitry 903, and/or wireless device UE may be incorporated in a vehicle.

As discussed herein, operations of wireless device UE may be performed by processing circuitry 903 and/or transceiver circuitry 901. For example, processing circuitry 903 may control transceiver circuitry 901 to transmit communications through transceiver circuitry 901 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 901 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 905, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 903, processing circuitry 903 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless devices).

Figure 25 is a block diagram illustrating elements of a radio access network RAN node 1000 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. (RAN node 1000 may be provided, for example, as discussed below with respect to network node QQ160 of Figure 39.) As shown, the RAN node may include transceiver circuitry 1001 (also referred to as a transceiver, e.g., corresponding to portions of interface QQ190 of Figure 39) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node may include network interface circuitry 1007 (also referred to as a network interface, e.g., corresponding to portions of interface QQ190 of Figure 39) configured to provide

communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The network node may also include processing circuitry 1003 (also referred to as a processor, e.g., corresponding to processing circuitry QQ170) coupled to the transceiver circuitry, and memory circuitry 1005 (also referred to as memory, e.g., corresponding to device readable medium QQ180 of Figure 39) coupled to the processing circuitry. The memory circuitry 1005 may include computer readable program code that when executed by the processing circuitry 1003 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 1003 may be defined to include memory so that a separate memory circuitry is not required.

As discussed herein, operations of the RAN node may be performed by processing circuitry 1003, network interface 1007, and/or transceiver 1001. For example, processing circuitry 1003 may control transceiver 1001 to transmit downlink communications through transceiver 1001 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 1001 from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry 1003 may control network interface 1007 to transmit communications through network interface 1007 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 1005, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1003, processing circuitry 1003 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes).

According to some other embodiments, a network node may be implemented as a core network CN node without a transceiver. In such embodiments, transmission to a wireless device UE may be initiated by the network node so that transmission to the wireless device is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver.

Figure 26 is a block diagram illustrating elements of a core network CN node (e.g., an SMF node, an AMF node, an O&M node, etc.) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the CN node may include network interface circuitry 1107 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the radio access network RAN. The CN node may also include a processing circuitry 1103 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 1105 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 1105 may include computer readable program code that when executed by the processing circuitry 1103 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 1103 may be defined to include memory so that a separate memory circuitry is not required.

As discussed herein, operations of the CN node may be performed by processing circuitry 1103 and/or network interface circuitry 1107. For example, processing circuitry 1103 may control network interface circuitry 1107 to transmit communications through network interface circuitry 1107 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 1105, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 1103, processing circuitry 1103 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes).

The RRC IN ACTIVE state has been introduced in Rel-15 in NR. The existing scheme of Trace Activation and Configuration for both Trace and MDT may not provide solutions for scenarios when AMF or MME sends the Trace Start containing Trace/MDT

activation/configurations to RAN nodes while UEs are in RRC INACTIVE.

Problems for signaling based MDT activation and configuration are further illustrated with the following examples.

Scenario 1 : OAM initiates a signaling-based MDT for a UE which is in

CM_CONNECTED. After OAM sending Trace Session Activation to AMF, AMF sends Trace Start to the RAN node gNBlOl that provided the last serving cell of the UE with MDT measurement control and configuration parameters. However, the UE is in RRC INACTIVE state and RAN node gNBlOl cannot configure the UE to perform MDT measurement and reporting. The UE is moving and camping on a new serving cell provided by RAN node gNB104 and the UE moves to RRC CONNECTED from RRCJN ACTIVE. The UE in

RRC CONNECTED state can be configured to perform the MDT measurement and reporting. However, the RAN node gNB104 does not have the MDT measurement control and

configuration parameters.

Figure 1 illustrates Scenario 1, where the last serving cell provided by RAN node gNBlOl receiving the signaling-based MDT configuration for a UE in RRC IN ACTIVE cannot be used to perform the MDT configuration. The UE moves from inactive state to Connected state when camping on a new serving cell provided by RAN node gNB104 which does not have the MDT configuration.

Scenario 2: OAM initiates a signaling-based MDT for a UE which is in

CM_CONNECTED. After OAM sending Trace Session Activation to AMF, AMF sends Trace Start to the RAN node gNBlOl that provided the last serving cell of the UE with MDT measurement control and configuration parameters. However, the UE is in RRC INACTIVE state and RAN node gNBlOl cannot configure the UE to perform MDT measurement and reporting. The UE performs RNA update when camping on a new serving cell provided by RAN node gNB104 due to the expiration of RNA timer or the UE moving out of the RNA area. In this case, the RAN node gNB104 can send the MDT configuration to UE. However, the RAN node gNB104 does not have the MDT measurement control and configuration parameters.

Figure 2 illustrates Scenario 2, where the last serving cell provided by RAN node gNBlOl receiving MDT configuration cannot be used to configure UE to perform MDT measurements; UE performs RNA update; the RAN node gNB104 providing the new serving cell does not have the MDT configuration.

Scenario 3: OAM initiates a signaling-based MDT for a UE which is in

CM_CONNECTED. After OAM sending Trace Session Activation to AMF, AMF sends Trace Start to the RAN node gNBlOl that provided the last serving cell of the UE with MDT measurement control and configuration parameters. However, the UE is in RRC INACTIVE state and RAN node gNBlOl cannot configure the UE to perform MDT measurement and reporting. The UE moves to RRC IDLE from RRC INACTIVE due to a failure case such as a failed attempt to establish a connection. The UE in RRC IDLE is camping on a new serving cell provided by RAN node gNB104 and becomes RRC_CONNECTED. In this case, the RAN node gNB104 can send the MDT configuration to UE. However, the RAN node gNB104 does not have the MDT measurement control and configuration parameters.

Figure 3 illustrates Scenario 3, where the last serving cell provided by RAN node gNBlOl receiving MDT configuration cannot be used to configure UE to perform MDT measurements; UE moves to idle from inactive, then, becomes Connected when camping on the new serving cell provided by RAN node gNB104 which does not have the MDT configuration.

Option 1 is provided according to some embodiment of inventive concept.

• RAN nodes can always assume that OAM or AMF knows the RRC state of the UE before sending MDT configuration to gNB.

• When gNB receives a signaling-based MDT configuration for a specific UE from AMF, gNB sends a Trace Failure Indication to AMF if the UE is in RRC INACTIVE state. Option 2 is provided according to some embodiment of inventive concept.

• NG-RAN nodes assume that OAM or AMF may know or may NOT know the RRC state of the UE before AMF sending MDT configuration to gNB.

• Option 2 proposes processes for different scenarios:

o UE moves from Inactive to Connected within the same gNB. A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs. UE may move from one gNB-DU to another or from one gNB-CU-UP to another within the same gNB.

o UE moves from Inactive to Connected at a new gNB. Last/old serving NG-RAN node (e.g., gNB) (that provided the last/old serving cell) sets the MDT state in the UE context so that new NG-RAN node will realize the state of the MDT: whether the UE is already configured with MDT measurement or it is not configured (i.e., suspended/pending MDT activation/configuration).

^■ New serving gNB (that provides the new serving cell) may take

appropriate actions depending on the MDT state in the UE context i.e., new serving gNB may configure the UE with the suspended/pending MDT if the MDT state is set to suspended/pending, or it can let UE perform the MDT measurement if the MDT state is set to configured in the UE context. o If the new serving gNB after UE transition from Inactive to Connected mode does not belong to the same area scope, last/old serving gNB can send a signal to the AMF indicating Trace/MDT failure as UE made transition to connected mode in a cell belonging to a new gNB out of area scope

o Trace Start immediately

Option 3 is provided according to some embodiment of inventive concept.

• Embodiments related to the usage of the“RRC Inactive Transition report” between AMF and NG-RAN are proposed.

• A new RRC Inactive Transition Report Request IE dedicated for Trace and MDT purpose is proposed. An alternative is to add new type,“Ready for Trace/MDT activation report”, into the existing RRC Inactive Transition Report Request IE.

• Another alternative is to make the AMF agnostic to that and simply forward an indication to RAN and then the last serving gNodeB stores that configuration until the UE gets connected or a predefined timer is expired

• In yet another alternative that MDT activation/configuration is stored as part of the UE inactive context e.g. in case the UE performs a 2-step procedure, like an RNA update, and does not enter connected, storing that makes the proper transfer to the new gNodeB so network waits until the UE gets connected

Option 4 is provided according to some embodiment of inventive concept.

• For signaling-based MDT, RAN nodes will be responsible to buffer the MDT

configuration and configure the UE after receiving the MDT configuration from AMF. There is a way for AMF to know whether the configuration is successful. A set of messages and a timer are defined for this process.

The embodiments are also applicable to the signaling-based MDT activation and configuration for UE in RRC INACTIVE in LTE. In this case, OAM initiates a signaling-based MDT for a UE which is in CM_CONNECTED. After OAM sending Trace Session Activation to MME, MME sends Trace Start to the serving eNB.

The embodiments can be extended to management-based MDT activation and configuration in LTE and NR. In this case, the RAN nodes select UEs to perform MDT measurement and reporting. The embodiments can be extended to the signaling-based Trace activation and configuration for UE in RRC IN ACTIVE in LTE and NR.

According to some embodiments of inventive concepts, the MDT activation and configuration procedure may be enabled to cover the RRC INACTIVE state related scenarios. Detailed embodiments for proposed options are illustrated as follows.

Embodiments of Option 1 are discussed below.

For signaling-based MDT, NG-RAN nodes always assume that OAM or AMF knows the RRC state of the LIE before AMF sending MDT configuration to gNB. AMF is aware of the RRC state of a UE before initiating a signaling-based MDT by a process. A process is described as follows.

• AMF includes RRC Inactive Transition Report Request IE in a message from AMF to NG-RAN node to request NG-RAN node to report the RRC state and user location information of a specific UE when the UE enters or leaves RRC INACTIVE. NG-RAN node which receives the RRC Inactive Transition Report Request IE sends the RRC Inactive Transition Report message for the specific UE to the AMF.

(Embodiment 1) When gNB receives a signaling-based MDT measurement control and configuration for a specific UE from AMF, gNB sends a Trace Failure Indication to AMF if the UE is in RRC INACTIVE state.

The proposed approach is illustrated as follows.

• Operation 1 : OAM sends the trace activation for signaling based MDT for a specific UE to AMF.

• Operation 2: AMF sends RRC Inactive Transition Report Request to a NG-RAN node, e.g., the last serving gNB, to request NG-RAN to report the current RRC state (Inactive or Connected) of the UE (when the UE enters Inactive from Connected or leaves Inactive for Connected).

• Operation 3: A serving NG-RAN node (e.g., the last serving gNB or another new gNB) sends RRC state of the UE in the RRC Inactive Transition Report message.

• Operation 4: AMF sends Trace Start message containing the MDT measurement control and configuration to a NG-RAN node which reports that the UE is in RRC Connected state. • Operation 5: When the NG-RAN node receives the MDT measurement control and configuration, it sends a Trace Failure Indication to AMF if the UE is in

RRC_INACTIVE state. The cause value of the Trace Failure Indication is“UE in RRC IN ACTIVE state not reachable”.

• Operation 6: AMF may optionally send RRC Inactive Transition Report Request to a NG-RAN node to cancel the report of the current RRC state for the UE, if AMF does not receive any Trace Failure Indication messages.

Figure 4 illustrates a successful activation operation in Option 1.

Figure 5 illustrates an unsuccessful activation operation on Option 1.

Figure 6 illustrates an example of Option 1 where the RAN node gNBlOl (that provided the last serving cell) sends Trace Failure indication to AMF if the specific UE is in

RRC_INACTIVE when RAN node gNBlOl receives Trace Start from AMF. Figure 6 depicts an example of the solution for Option 1 where:

• OAM is aware of the RRC state of a UE before initiating a signaling-based MDT by a process. One example of the process is to use the“RRC Inactive Transition report”, i.e., AMF subscribes to receive the inactive reports from RAN (upon entering and/or leaving inactive).

• OAM initiates a signaling-based MDT for a UE which is in CM_CONNECTED and RRC CONNECTED according to the Inactive reports from RAN.

• After receiving Trace Session Activation from OAM, AMF sends Trace Start to the RAN node gNBlOl that provided the last serving cell of the UE with MDT measurement control and configuration parameters.

• However, the UE has already been moved to RRC INACTIVE state and RAN node gNBlOl cannot configure the UE to perform MDT measurement and reporting.

• The RAN node gNBlOl sends a Trace Failure Indication to AMF to indicate that RAN node gNBlOl cannot perform MDT measurement and reporting since the UE is in RRC INACTIVE state.

• The UE is moving and camping on a new serving cell provided by RAN node gNB104 which moves the UE to RRC CONNECTED from RRC INACTIVE. AMF sends the Trace start to RAN node gNB104 to perform the MDT configurations. The process is also applicable to the Trace/MDT deactivation procedure in NR, illustrated in the following figures. The deactivation procedure is used to deactivate the immediate MDT.

Figure 7 illustrates a successful deactivation operation in Option 1.

Figure 8 illustrates an unsuccessful deactivation operation in Option 1.

According to some embodiments, after receiving a RRC Inactive Transition report for a UE, the AMF node starts a inactivity timer that is stopped when the AMF receives a RRC Inactive Transition Report. If the AMF timer expires a configured or standardized threshold, AMF sends a MDT activation failure to OAM with cause value: Inaccessible UE.

The process is also applicable to the Trace/MDT activation and deactivation procedure in

LTE.

Embodiments of Option 2 are discussed below.

For signaling-based MDT, NG-RAN nodes assume that OAM or AMF may know or may NOT know the RRC state of the UE before AMF sending MDT configuration to gNB.

According to some embodiments, the UE may move from Inactive to Connected within the same gNB.

A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple 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-CU-CP through the El interface. UE may move from one gNB-DU to another or from one gNB-CU-UP to another within the same gNB.

The proposed approach is illustrated as follows.

• Operation 1 : OAM sends the trace activation for signaling based MDT for a specific UE to AMF.

• Operation 2: AMF sends Trace Start message containing the MDT measurement control and configuration to the last serving NG-RAN node (that provided the last serving cell).

• Operation 3: When the NG-RAN node receives the MDT measurement control and

configuration, the gNB-CU stores the MDT measurement control and configuration in the UE context.

• Operation 4 (a): If the UE is in RRC Connected state, the gNB-CU configures the UE to perform the MDT measurement and reporting. • Operation 4 (b): If the UE is in RRC Inactive, the gNB-CU configures the UE to perform the MDT measurement and reporting when the UE moves to RRC Connected within the gNB.

For Operation 4(a) and Operation 4(b), there are different cases for the MDT

configurations depending on the job type of the MDT.

Logged MDT and Immediate MDT are discussed below

• Operation 1 : gNB-CU prepares measurement configuration for Logged MDT.

• Operation 2: gNB-CU prepares an RRC message containing the prepared measurement configuration.

• Operation 3 : gNB-CU sends the RRC message in DL RRC MESSAGE TRANSFER message to gNB-DU which then sends it to the UE.

Immediate MDT with the serving gNB-CU-CP being involved in performing

measurements are discussed below.

• Operation 1 : gNB-CU-CP prepares measurement configuration based on the List of measurements in the MDT configuration.

• Operation 2: gNB-CU-CP prepares an RRC message containing the prepared

measurement configuration.

• Operation 3 : gNB-CU-CP sends the RRC message in DL RRC MESSAGE TRANSFER message to gNB-DU which then sends it to the UE.

Immediate MDT with the serving gNB-DU being involved in performing measurements is discussed below.

• Operation 1 : gNB-CU sends the MDT activation to gNB-DU over the Fl-C interface. o In one embodiment, a new message from gNB-CU to gNB-DU is defined for MDT configuration purpose.

^■ In one sub-embodiment, the message includes the following fields. In this embodiment, gNB-DU directly reports the MDT data to Trace Collection Entity.

• Message Type

• gNB-CU UE FIAP ID

• gNB-DU UE FIAP ID

• NG-RAN Trace ID • MDT activation

o Trace Collection Entity IP Address

o MDT Configuration

o In another sub-embodiment, the message includes the following fields. In this embodiment, gNB-DU reports the MDT data to gNB-CU which sends the data to Trace Collection Entity.

^■ Message Type

^■ gNB-CU UE F1AP ID

^■ gNB-DU UE F1AP ID

^■ NG-RAN Trace ID

^■ MDT activation

• MDT Configuration

o In another embodiment: The MDT activation is included in UE CONTEXT SETUP REQUEST message, or UE CONTEXT MODIFICATION message, or UE CONTEXT MODIFICATION CONFIRM message which is sent from gNB- CU to gNB-DU. gNB-DU gets the MDT configuration during the UE context setup, UE context modification, or UE context modification required procedure.

^■ In one sub-embodiment, the MDT activation contains Trace Collection Entity IP Address and MDT configuration.

^■ In another sub-embodiment, the MDT activation contains MDT

configuration. In this embodiment, gNB-DU reports the MDT data to gNB-CU which sends the data to Trace Collection Entity.

• Operation 2: gNB-DU prepares the corresponding measurement configuration.

• Operation 3 : gNB-DU sends the prepared measurement configuration to gNB-CU.

• Operation 4: gNB-CU prepares an RRC message containing the prepared measurement configuration.

• Operation 5 : gNB-CU sends the RRC message in DL RRC MESSAGE TRANSFER message to gNB-DU which then sends it to the UE.

Immediate MDT with the serving gNB-CU-UP being involved in performing measurements is discussed below. Operation 1 : gNB-CU-CP sends the MDT activation to gNB-CU-UP over the El interface.

o In one embodiment, a new message from gNB-CU-CP to gNB-CU-UP is defined for MDT configuration purpose.

^■ In one sub-embodiment, the message includes the following fields. In this embodiment, gNB-CU-UP directly reports the MDT data to Trace Collection Entity.

• Message Type

• gNB-CU-CP UE El AP ID

• gNB-CU-UP UE El AP ID

• NG-RAN Trace ID

• MDT activation

o Trace Collection Entity IP Address o MDT Configuration

^■ In another sub-embodiment, the message includes the following fields. In this embodiment, gNB-CU-UP reports the MDT data to gNB-CU-CP which sends the data to Trace Collection Entity.

• Message Type

• gNB-CU-CP UE El AP ID

• gNB-CU-UP UE El AP ID

• NG-RAN Trace ID

• MDT activation

o MDT Configuration

o In another embodiment: The MDT activation is included in BEARER CONTEXT SETUP REQUEST message, or BEARER CONTEXT MODIFICATION message, or BEARER CONTEXT MODIFICATION CONFIRM message which is sent from gNB-CU-CP to gNB-CU-UP. gNB-CU-UP gets the MDT configuration during the bearer context setup, bearer context modification, or bearer context modification required procedure.

^■ In one sub-embodiment, the MDT activation contains Trace Collection Entity IP Address and MDT configuration. ^■ In another sub-embodiment, the MDT activation contains MDT

configuration. In this embodiment, gNB-CU-UP reports the MDT data to gNB-CU-CP which sends the data to Trace Collection Entity.

• Operation 2: gNB-CU-UP prepares the corresponding measurement configuration.

• Operation 3: gNB-CU-UP sends the prepared measurement configuration to gNB-CU- CP.

• Operation 4: gNB-CU-CP prepares an RRC message containing the prepared

measurement configuration.

• Operation 5 : gNB-CU-CP sends the RRC message in DL RRC MESSAGE TRANSFER message to gNB-DU which then sends it to the UE.

The UE moves from Inactive state to Connected state at a new gNB. The proposed approach is discussed below with respect to Figure 27. Figure 9 illustrates operations on setting the status of the MDT configuration i.e., pending (also referred to as suspended) MDT configuration or activated MDT configuration in the serving NG-RAN node (that provides the serving cell).

Operations of the serving gNB after receiving a Trace Start message from the AMF node may include:

• OAM node sends the trace activation for signaling based MDT for a specific UE to the AMF node.

• The AMF sends a Trace Start message containing the MDT measurement control and configuration (also referred to as the MDT configuration) to the last serving NG-RAN node (that provided the last serving cell).

• When the NG-RAN node receives the MDT measurement control and configuration, for example via the NG: Trace Start message, the gNB-CU stores the MDT measurement control and configuration in the UE context.

• When receiving MDT control and configuration from the AMF node, the NG Ran node (e.g., gNB-CU) verifies the RRC state of the UE (e.g., RRC connected state or RRC inactive state).

• If the UE is in RRC Connected state, the NG-RAN node (e.g., gNB-CU) configures the UE to perform the MDT measurement and reporting based on the MDT configuration received in the Trace Start message. • if the UE is in RRC Connected state and after configuring the UE with MDT configuration, the NG-RAN node sets the status/state of the MDT measurement in the EE context to“activated” (also referred to as an activated MDT configuration state). This indicates the MDT measurement is activated for the EE, e.g. MDT state := activated.

• if the EE is in RRC Inactive state, the NG-RAN node (e.g., gNB-CU) sets the MDT_state to“pending” (also referred to as the pending MDT configuration state, suspended, etc.) in the EE context that indicates the MDT measurement is not yet activated and is in a pending status/state. In other words EE is not yet configured to perform MDT measurement since it is in RRC Inactive state, e.g., MDT state = pending.

• Optionally, and if the EE is in RRC Inactive state, the NG RAN node (e.g., gNB-CU) sends a signal to the AMF node indicating that the MDT is pending/suspended as EE is the inactive state.

Operations in the old serving NG-RAN node (e.g., gNB gNBlOl) after receiving EE Context Request from new serving NG-RAN node (e.g., gNB104) are discussed below with respect to Figures 28A and 28B.

If the UE resumes connection from the RRC Inactive state, in a new NG-RAN node, the new NG-RAN node receiving a request to resume from the EE should attempt to retrieve the EE context from the previously serving NG-RAN node.

• After receiving a EE Context Request signal from a different NG-RAN node, the

old/previous serving NG-RAN node, checks whether the new serving NG-RAN node belongs to the same area scope for MDT configuration or not

o If the new NG-RAN node belongs to the same area scope for MDT configuration,

^■ send the EE Context including the MDT configuration and MDT state to the new serving NG-RAN node

^■ Optionally, send a signal to the AMF indicating that the MDT

configuration is transferred to a new gNB in the same area scope (MDT configuration transferred).

o If the new NG-RAN node does not belong to the same area scope for MDT

configuration ^■ Send a signal to the AMF indicating that MDT configuration is failed (MDT failure signal) as UE camped in a cell belonging to an NG-RAN node in a different area.

^■ Alternatively, notification to the AMF can be omitted and the next step can be taken

^■ Send the UE context to the new serving NG_RAN node

^■ If the old serving NG-RAN node does not notify the AMF, it may send the UE context to the new NG-RAN node, which includes the MDT_State flag set to“pending”

Operations in the old serving NG-RAN node upon receiving the UE context request are illustrated in Figures 28A and 28B.

Actions in the new serving gNB gNB104 (after the UE transitions from Inactive to connected state) are discussed below with respect to Figures 29A and 29B.

• Upon resuming a connection, the new serving gNB initiates the UE context retrieve procedure, when the UE moves from Inactive to Connected at a new serving gNB. After retrieving the UE context including the Trace Activation containing the MDT

configuration, the new serving gNB verifies whether the MDT configuration is activated or not e .g., MDT state = configured (also referred to as the activated MTD configuration state) or pending (also referred to as the pending MDT configuration state)

o If the new serving gNB NG-RAN node figures out that the UE is already configured in the last serving cell e.g., MDT state = configured (also referred to as activated MDT configuration state), legacy actions would be taken, i.e., either leaving the same MDT configuration, or configuring the UE with a new MDT configuration if requested by OAM or AMF.

o If new serving gNB figured out that the MDT configuration is not activated in the last serving cell e.g., MDT state = pending (also referred to as the pending MDT configuration state),

^■ configure the UE to perform MDT measurement and reporting,

^■ set the MDT state to“configured” (activated MDT configuration state) ^■ send an indication signal to the AMF (or the old serving gNB) that the MDT is configured for the UE (e.g., MDT start/resumed signal to the AMF).

^■ If the new NG-RAN node is in a different MDT area scope than the old serving NG-RAN node,

• The new NG-RAN node will be aware that the UE has moved outside the MDT area scope (this can be determined by checking that the new NG-RAN serving node is not in the MDT area scope of the UE - where the MDT Area Scope might have been acquired by the new NG-RAN node together with the UE context fetched from the old serving NG-RAN node), while at the same time knowing that the UE has not yet been configured with an MDT configuration.

• The new NG-RAN Node may signal the AMF with an indication that the UE has not been configured with the MDT configuration pending (e.g., MDT update request). The latter may be done by adding new information in the NG: PATH SWITCH REQUEST from new serving NF-RAN Node to AMF.

• The AMF node may respond to the indication from the new

serving NG-RAN Node with a new MDT Configuration for the UE, or it may respond with an indication that the previously sent MDT configuration (e.g., MDT update response), retrieved by the new NG-RAN Node together with the UE context, is still valid and it should be signaled to the UE. Signaling of this information (e.g. a new MDT Configuration or notification of reuse of the old MDT Configuration) from AMF node to new serving NG-RAN node, may be performed via the NG: PATH SWITCH RESPONSE message.

Figures 29A and 29B illustrates operations of the new serving NG-RAN node (e.g., gNB) upon receiving the UE context (including MDT activation/configuration) from the old/last/previous serving gNB after UE transition from RRC Inactive mode to RRC Connected mode.

Trace Start immediately is discussed below.

If the UE is RRC Inactive state when the NG-RAN node receives the MDT the gNB will try to move the UE to RRC Active.

• Operation 1 : OAM sends the trace activation for signaling based MDT for a specific UE to AMF.

• Operation 2: AMF sends Trace Start message containing the MDT measurement control and configuration to the last serving NG-RAN node.

• Operation 3: If the UE is RRC Inactive state when the NG-RAN node receives the MDT measurement control and configuration, the serving gNB-CU triggers a RAN paging procedure to move the UE to RRC CONNECTED state. Once the UE is connected (either in the old serving gNB or in a new serving gNB), the serving gNB configures the UE to perform MDT measurement and reporting.

Embodiments of Option 3 are discussed below.

Another set of embodiments may be related to the usage of the“RRC Inactive Transition report” between AMF and NG-RAN. The AMF may subscribe to receive the inactive reports from RAN (upon the UE entering and/or leaving inactive).

According to some embodiments, it is assumed that, for signaling-based MDT, OAM or AMF knows the RRC state of the UE before AMF sending MDT configuration to gNB.

AMF is aware of the RRC state of a UE before initiating a signaling-based MDT by a process described below.

• AMF includes RRC Inactive Transition Report Request IE in a message from AMF to NG-RAN node to request NG-RAN node to report the RRC state and user location information of a specific UE when the UE enters or leaves RRC INACTIVE. NG-RAN node which receives the RRC Inactive Transition Report Request IE sends the RRC Inactive Transition Report message for the specific UE to the AMF.

According to some embodiments, it is proposed to define a new RRC Inactive Transition Report Request IE dedicated for Trace and MDT purpose. In this way, NG-RAN does not need to make subsequent state transition report and it only reports when the UE moves from Inactive to Connected and stops the report when the Trace Start has been received without AMF sending another stop request. It is proposed that AMF is responsible to“buffer” the MDT activation/configuration from the OAM, the“leaving inactive” report can be used as input to take the action to provide the OAM configuration to the UE.

This new IE is used to request the NG-RAN node to report or stop reporting to the 5GC when the UE enters or leaves RRC INACTFVE state for Trace or MDT purpose.

An alternative is to add new type,“Ready for Trace/MDT activation report”, into the existing RRC Inactive Transition Report Request IE, shown in the table of Figure 23.

Another alternative is to make the AMF agnostic to that and simply forward an indication to RAN and then the last serving gNodeB stores that configuration until the UE gets connected or a predefined timer is expired.

• The indication indicates the NG-RAN node which receives the MDT configuration to store the MDT configuration until the UE becomes RRC Connected or a predefined timer is expired.

• In a sub-embodiment, the indication is included in the MDT configuration contained in Trace Activation or in Trace Activation.

• In another sub-embodiment, the indication contained in the MDT configuration contained in Trace Activation or in Trace Activation is stored in the UE context. When a new serving gNB retrieves the UE context, it will store the MDT configuration if it cannot perform the configuration to the UE.

In yet another alternative that MDT activation/configuration is stored as part of the UE inactive context e.g. in case the UE performs a 2-step procedure, like an RNA update, and does not enter connected, storing that makes the proper transfer to the new gNodeB so network waits until the UE gets connected.

Embodiments of Option 4 are discussed below.

For signaling-based MDT, RAN nodes will be responsible to buffer the MDT

configuration and configure the UE after receiving the MDT configuration from AMF. There is a way for AMF to know whether the configuration is successful.

The following messages and Timer are defined for this process.

• Trace Suspend Indication

o gNB->AMF: to indicate that the UE is RRC_INACTIVE

• Trace Resume Indication o gNB->AMF: to indicate that a new gNB has successfully retrieved the MDT configuration from an old gNB.

• Timer T001

o For both gNB and AMF.

o gNB starts the timer when receiving signaling-based MDT configuration from AMF and the UE is in RRC INACTFVE; the gNB release the MDT configuration when the timer is expired.

o AMF starts the timer when it receives Trace Suspend Indication from a gNB.

• An alternative for Timer 001 could be to reuse the existing discard timer for UE Inactive context for removing the stored MDT configuration.

o If the UE moves from RRC Inactive to RRC Idle, AMF would be informed but AMF would not know if the MDT configuration was received by UE or not. The solution could be that if the discard timer for UE Inactive context expires, AMF is informed about the failure of the MDT configuration.

The solution is illustrated in the following operations:

• Operation 1 : OAM sends the trace activation for signaling based MDT for a specific UE to AMF.

• Operation 2: AMF sends Trace Start message containing the MDT measurement control and configuration to the last serving gNB.

• Operation 3: If the UE is in RRC Inactive when the last gNB receives the configuration, the gNB starts T001 timer and sends Trace Suspend Indication including the duration of the T001 to AMF.

• Operation 4: AMF starts the Timer 001 and wait for Trace Resume Indication from NG- RAN nodes.

There are several cases illustrated as follows.

AMF receives Trace Resume Indication before the expiration of Timer 001 is discussed below.

• Operation 5: A new serving gNB (gNB 104 in the Figure 9) initiates the UE context retrieve procedure. The old serving gNB stops its T001 timer after the release of the UE context including the MDT configuration. • Operation 6: The new serving gNB sends Trace Resume Indication to AMF. AMF releases the T001 timer after receiving the Trace resume indication.

The process is illustrated in Figure 9 and Figure 10 is discussed below. In Figure 9, the AMF receives a Trace Resume Indication before the expiration of Timer 001.

In the diagram of Figure 10, the AMF receives the Trace Resume Indication before the expiration of Timer 001.

At operation 950 of Figure 9, the OAM node transmits the Trace Session Activation message (including the MDT configuration) to the AMF node. At operation 951 of Figures 9 and 10, the AMF node transmits the trace start message (including the MDT configuration) to RAN node gNBlOl . At operation 952 of Figures 9 and 10, RAN node gNBlOl transmits the Trace Suspend Indication message (including the timer T001 duration) to the AMF node. At operation 953, RAN node gNB 104 transmits the Retrieve UE Context Request message to RAN node gNBlOl, and at operation 954, RAN node gNBlOl transmits the Retrieve UE Context Response message (including the MDT configuration) to RAN node gNB 104. After transmitting the Retrieve UE Context Response message, RAN node gNBlOl may release the MDT configuration and stop the timer T001. At operation 955, RAN node gNB104 transmits the Trace Resume Indication message to the AMF node. After receiving the Trace Resume Indication message, the AMF node may stop the Timer T001.

AMF sending Trace start to another gNB after the expiration of Timer 001 is discussed below.

• Operation 5: The serving gNB releases the MDT configuration when the Timer 001 is expired.

• Operation 6: AMF sends Trace Start to a new serving gNB when the UE moves to a new serving cell provided by the new serving gNB.

The process is illustrated in Figure 11.

In the diagram of Figure 11, the AMF sends Trace start to another gNB after the expiration of Timer 001.

AMF sends Trace start to another gNB before the expiration of Timer 001 is discussed below. • Operation 6: AMF stops the Timer 001 and sends Trace Start to a new serving gNB when the UE moves to a new serving cell provided by the new serving gNB before the expiration of Timer 001.

In the diagram of Figure 12, the AMF sends Trace start to another gNB after the expiration of Timer 001.

Additional embodiments are discussed below.

In one embodiment, an indicator field is included in the trace activation for signaling based MDT to indicate the following options:

• Trace start immediately when a NG-RAN node receives trace activation containing MDT configuration.

• NG-RAN node sends Trace Failure Indication to AMF if the UE is RRC Inactive state.

• NG-RAN node stores the trace activation and perform the configuration when the UE becomes RRC Connected.

The operations may also be applicable to the Trace/MDT deactivation procedure in NR. The operations may also be applicable to the Trace/MDT activation and deactivation procedure in LTE.

The operations may also be applicable to the Trace only activation and deactivation procedure in LTE and NR.

The operations may also be extended for management-based Trace and MDT in LTE and NR.

The operations may also be applicable for MDT configuration during inter RAT scenarios, e.g., the UE is released to inactive state in one RAT and goes to connected state in another RAT. This means that the inter RAT Inactive state mobility including gNB, ng-eNB and eNB are covered. Previously, inter RAT inactive state mobility may have been unsupported but it may still be a valid scenario since NG-RAN would span both ng-eNB and gNB, so that it makes sense to have area config of Inactive state covering both ng-eNB and gNB.

Operations of a RAN node 1000 (e.g., RAN node gNBlOl implemented using the structure of Figure 25) will now be discussed with reference to the flow chart of Figure 30 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1005 of Figure 25, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 1003, processing circuitry 1003 performs respective operations of the flow chart.

At block 3005, processing circuitry 1003 of RAN node gNBlOl receives (through network interface 1007) information for a minimization of drive tests MDT configuration for a wireless device UE.

At block 3009, processing circuitry 1003 of RAN node gNBlOl determines a connection state of the wireless device.

At block 3015, processing circuitry 1003 of RAN node gNBlOl determines an MDT configuration state of the wireless device based on the connection state of the wireless device.

At block 3019, processing circuitry 1003 of RAN node gNBlOl stores an MDT configuration state indicator for the wireless device in a context for the wireless device UE wherein the MDT configuration state indicator is based on the MDT configuration state of the wireless device.

At block 3025, processing circuitry 1003 of RAN node gNBlOl stores the information for the MDT configuration in the context for the wireless device UE.

Various operations from the flow chart of Figure 30 may be optional with respect to some embodiments of RAN nodes and related methods.

Operations of a first RAN node 1000 (e.g., first RAN node gNBlOl implemented using the structure of Figure 25) will now be discussed with reference to the flow chart of Figure 31 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1005 of Figure 25, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 1003, processing circuitry 1003 performs respective operations of the flow chart.

At block 3105, processing circuitry 1003 of first RAN node gNBlOl receives (through network interface 1007) information for a minimization of drive tests MDT configuration for a wireless device UE.

At block 3109, processing circuitry 1003 of first RAN node gNBlOl determines a connection state of the wireless device. According to some embodiments of Figure 31, determining the connection state comprises determining that the wireless device is in an inactive state. At block 3115, processing circuitry 1003 of first RAN node gNBlOl determines an MDT configuration state of the wireless device based on the connection state of the wireless device. According to some embodiments of Figure 31, determining the MDT configuration state comprises determining that the MDT configuration state for the wireless device is a pending MDT configuration state responsive to determining that the wireless device is in the inactive state.

At block 3119, processing circuitry 1003 of first RAN node gNB 101 stores an MDT configuration state indicator for the wireless device in a context for the wireless device UE wherein the MDT configuration state indicator is based on the MDT configuration state of the wireless device. According to some embodiments of Figure 31, storing the MDT configuration state indicator comprises storing a pending MDT configuration state indicator in the context for the wireless device responsive to determining that the wireless device is in the inactive state and/or responsive to determining that the MDT configuration state is the pending MDT configuration state.

At block 3125, processing circuitry 1003 of first RAN node gNBlOl stores the information for the MDT configuration in the context for the wireless device (UE). According to some embodiments of Figure 31, the information for the MDT configuration is received from a core network node.

According to some embodiments at block 3129, processing circuitry 1003 of first RAN node gNBlOl transmits (through network interface 1007) an indication that the MDT configuration state for the wireless device is the pending MDT configuration state to the core network node responsive to determining that the wireless device is in the inactive state and/or responsive to determining that the MDT configuration state is the pending MDT configuration state.

According to some embodiments at block 3135, processing circuitry 1003 of first RAN node gNBlOl receives (through network interface 1007) a context request from second RAN node gNB 104 requesting the context for the wireless device after storing the pending MDT configuration state indicator in the context for the wireless device.

According to some embodiments at block 3139, processing circuitry 1003 of first RAN node gNBlOl transmits (through network interface 1007) the context for the wireless device to the second RAN node responsive to receiving the context request, wherein the context includes the pending MDT configuration state indicator for the wireless device.

Various operations from the flow chart of Figure 31 may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of some embodiments, for example, operations of blocks 3129, 3135, and/or 3139 of Figure 31 may be optional.

Operations of a RAN node 1000 (e.g., first RAN node gNBlOl implemented using the structure of Figure 25) will now be discussed with reference to the flow chart of Figure 32 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1005 of Figure 25, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 1003, processing circuitry 1003 performs respective operations of the flow chart.

At block 3205, processing circuitry 1003 of first RAN node gNBlOl receives (through network interface 1007) information for a minimization of drive tests, MDT, configuration for a wireless device HE.

At block 3209, processing circuitry 1003 of first RAN node gNBlOl determines a connection state of the wireless device. According to some embodiments of Figure 32, determining the connection state comprises determining that the wireless device is in a connected state.

At block 3215, processing circuitry 1003 of first RAN node gNBlOl determines an MDT configuration state of the wireless device based on the connection state of the wireless device. According to some embodiments of Figure 32, determining the MDT configuration state comprises determining that the MDT configuration state for the wireless device is an activated MDT configuration state responsive to determining that the wireless device is in the connected state.

At block 3219, processing circuitry 1003 of first RAN node gNBlOl stores an MDT configuration state indicator for the wireless device in a context for the wireless device (UE) wherein the MDT configuration state indicator is based on the MDT configuration state of the wireless device. According to some embodiments of Figure 32, storing the MDT configuration state indicator comprises storing an activated MDT configuration state indicator in the context for the wireless device responsive to determining that the wireless device is in the connected state and/or responsive to determining that the MDT configuration state is the activated MDT configuration state.

At block 3225, processing circuitry 1003 of first RAN node gNBlOl stores the information for the MDT configuration in the context for the wireless device UE.

According to some embodiments at block 3235, processing circuitry 1003 of first RAN node gNBlOl receives (through network interface 1007) a context request from a second RAN node gNB104 requesting the context for the wireless device.

According to some embodiments at block 3239, processing circuitry 1003 of first RAN node gNBlOl transmits (through network interface 1007) the context for the wireless device to second RAN node gNB104 responsive to receiving the context request, wherein the context includes the activated MDT configuration state indicator for the wireless device.

Various operations from the flow chart of Figure 32 may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of some embodiments, for example, operations of blocks 3235 and/or 3239 of Figure 32 may be optional.

Operations of a RAN node 1000 (e.g., first RAN node gNB104 implemented using the structure of Figure 25) will now be discussed with reference to the flow chart of Figure 33 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1005 of Figure 25, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 1003, processing circuitry 1003 performs respective operations of the flow chart.

At block 3305, processing circuitry 1003 of first RAN node gNB104 transmits (through network interface 1007) a request for a context for a wireless device to a second RAN node gNBlOl .

At block 3309, processing circuitry 3309 of first RAN node gNB104 receives (through network interface 1007) a context response from second RAN node gNBlOl . The context response includes the context for the wireless device, and the context for the wireless device includes an MDT configuration state indicator for the wireless device and information for an MDT configuration for the wireless device.

Operations of a RAN node 1000 (e.g., first RAN node gNB104 implemented using the structure of Figure 25) will now be discussed with reference to the flow chart of Figure 34 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1005 of Figure 25, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 1003, processing circuitry 1003 performs respective operations of the flow chart.

At block 3405, processing circuitry 1003 of first RAN node gNB104 transmits (through network interface 1007) a request for a context for a wireless device to a second RAN node gNBlOl .

At block 3409, processing circuitry 1003 of first RAN node gNB104 receives (through network interface 1007) a context response from the second RAN node. The context response includes the context for the wireless device, and the context for the wireless device includes an MDT configuration state indicator for the wireless device and information for an MDT configuration for the wireless device. According to some embodiments of Figure 34, the MDT configuration state indicator for the wireless device is a pending MDT configuration state indicator.

According to some embodiments at block 3415, processing circuitry 1003 of first RAN node gNB104 configures the wireless device with the MDT configuration responsive to the MDT configuration state indicator of the wireless device being the pending MDT configuration state indicator. According to some embodiments of Figure 34, the wireless device is configured with the MDT configuration responsive to the MDT configuration state indicator of the wireless device being the pending MDT configuration state indicator and responsive to first RAN node gNB104 belonging to an area scope of the MDT configuration for the wireless device.

According to some embodiments at block 3419, processing circuitry 1003 of first RAN node gNB104 changes the MDT configuration state indicator for the wireless device from the pending MDT configuration state indicator to an activated MDT configuration state indicator.

Various operations from the flow chart of Figure 34 may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of some embodiments, for example, operations of blocks 3415 and/or 3419 of Figure 34 may be optional.

Operations of a RAN node 1000 (e.g., first RAN node gNB104 implemented using the structure of Figure 25) will now be discussed with reference to the flow chart of Figure 35 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1005 of Figure 25, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 1003, processing circuitry 1003 performs respective operations of the flow chart.

At block 3505, processing circuitry 1003 of first RAN node gNB104 transmits (through network interface 1007) a request for a context for a wireless device to a second RAN node.

At block 3509, processing circuitry 1003 of first RAN node gNB104 receives (through network interface 1007) a context response from the second RAN node. The context response includes the context for the wireless device, and the context for the wireless device includes an MDT configuration state indicator for the wireless device and information for an MDT configuration for the wireless device. According to some embodiments of Figure 35, the MDT configuration state indicator of the wireless device is a pending MDT configuration state indicator.

According to some embodiments at block 3515, processing circuitry 1003 of first RAN node gNB104 transmits (through network interface 1007) an indication that the wireless device is not configured with the MDT configuration responsive to the MDT configuration state indicator of the wireless device being the pending MDT configuration state indicator and responsive to the first RAN node not belonging to an area scope of the MDT configuration for the wireless device. According to some embodiments of Figure 35, the indication that the wireless device is not configured with the MDT configuration is transmitted to a core network node.

Various operations from the flow chart of Figure 35 may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of some embodiments, for example, operations of block 3515 of Figure 35 may be optional.

Operations of a Core Network CN node 1100 (implemented using the structure of Figure 26) will now be discussed with reference to the flow chart of Figure 36 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1105 of Figure 26, and these modules may provide instructions so that when the instructions of a module are executed by respective CN node processing circuitry 1103, processing circuitry 1103 performs respective operations of the flow chart.

At block 3605, processing circuitry 1103 transmits (through network interface 1107) information for a minimization of drive tests MDT configuration for a wireless device UE to a first radio access network RAN node gNBlOl. At block 3609, processing circuitry 1103 receives (through network interface 1107) a request from a second RAN node gNB104, wherein the request indicates that the wireless device is not configured with the MDT configuration.

Operations of a Core Network CN node 1100 (implemented using the structure of Figure 26) will now be discussed with reference to the flow chart of Figure 37 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1105 of Figure 26, and these modules may provide instructions so that when the instructions of a module are executed by respective CN node processing circuitry 1103, processing circuitry 1103 performs respective operations of the flow chart.

At block 3705, processing circuitry 1103 transmits (through network interface 1107) information for a minimization of drive tests MDT configuration for a wireless device (UE) to a first radio access network RAN node gNBlOl.

At block 3709, processing circuitry 3709 receives (through network interface 1107) a request from a second RAN node gNB104 wherein the request indicates that the wireless device is not configured with the MDT configuration.

According to some embodiments at block 3715, processing circuitry 1103 transmits (through network interface 1107) a response to second RAN node gNB104 to use the MDT configuration for the wireless device connected with second RAN node gNB104, wherein the response is transmitted in response to the request.

According to some embodiments of Figure 37, the request of block 3709 is received using a path switch request message, and the response of block 3715 is transmitted using a path switch response message.

Various operations from the flow chart of Figure 37 may be optional with respect to some embodiments of CN nodes and related methods. Regarding methods of embodiments, for example, operations of block 3715 of Figure 37 may be optional.

Operations of a Core Network CN node 1100 (implemented using the structure of Figure 26) will now be discussed with reference to the flow chart of Figure 38 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1105 of Figure 26, and these modules may provide instructions so that when the instructions of a module are executed by respective CN node processing circuitry 1103, processing circuitry 1103 performs respective operations of the flow chart. At block 3805, processing circuitry 1103 transmits (through network interface 1107) information for a first minimization of drive tests MDT configuration for a wireless device UE to a first radio access network RAN node gNBlOl.

At block 3809, processing circuitry 1103 receives (through network interface 1107) a request from a second RAN node wherein the request indicates that the wireless device is not configured with the MDT configuration.

According to some embodiments at block 3815, processing circuitry 1103 transmits (through network interface 1107) a response to second RAN node gNB104 to use a second MDT configuration for the wireless device, wherein the response is transmitted in response to the request, and wherein the first and second MDT configurations are different.

According to some embodiments of Figure 38, the request is received at block 3809 using a path switch request message, and the response is transmitted at block 3815 using a path switch response message.

Various operations from the flow chart of Figure 38 may be optional with respect to some embodiments of CN nodes and related methods. Regarding methods of embodiments, for example, operations of block 3815 of Figure 38 may be optional.

Example embodiments are discussed below.

1. A method of operating a core network, CN, node of a communication network, the method comprising: receiving an inactive transition report message for a wireless device from a radio access network, RAN, node; and determining whether to transmit a trace message including minimization of drive tests, MDT, information for the wireless device based on a status of the wireless device indicated by the inactive transition report message.

2. The method of Embodiment 1 , wherein the inactive transition report message indicates that the wireless device is in an inactive state, and wherein determining comprises determining to not transmit a trace message including MDT information for the wireless device based on the inactive transition report message indicating that the wireless device is in the inactive state.

3. The method of Embodiment 1, wherein the inactive transition report message indicates that the wireless device is in a connected state, and wherein determining comprises determining to transmit a trace message including MDT information for the wireless device based on the inactive transition report message indicating that the wireless device is in the connected state, the method further comprising: transmitting the trace message including the MDT information for the wireless device to the RAN node.

4. The method of Embodiment 3, wherein the trace message is a trace start message with the MDT information including MDT measurement control/configuration information for the wireless device or a deactivate trace message with the MDT information including MDT measurement control/configuration information for the wireless device.

5. The method of Embodiment 4 further comprising: after transmitting the trace message, receiving a trace failure indication message for the wireless device from the RAN node.

6. The method of Embodiment 5, wherein the trace failure indication message includes a cause indication, wherein the cause indication indicates that the wireless device is in a radio resource control, RRC, inactive state and/or that the wireless device is not reachable.

7. The method of any of Embodiments 4-6, wherein the MDT measurement

control/configuration information includes at least one of job Type, SUPI/IMEI(SV), GUTI, C- RNTT, Area scope (e.g. TA, Cell), Trace Reference, List of measurements, Reporting Trigger, Report Interval, Report Amount, Event Threshold, Logging Interval, Logging duration,

Measurement period, Collection period for RRM measurements, Positioning method, and/or MDT PLMN List.

8. The method of any of Embodiments 4-7, wherein the MDT measurement

control/configuration information includes at least one of job Type, Trace Reference, List of measurements, and/or MDT PLMN List

9. The method of any of Embodiments 1-8 further comprising: transmitting an inactive transition report request message for the wireless device to the Radio Access Network RAN node before receiving the inactive transition report message from the wireless device.

10. The method of Embodiment 9, wherein the inactive transition report request message is a radio resource control, RRC, inactive transition report request message.

11. The method of any of Embodiments 9-10 further comprising: receiving a trace session activation message, wherein the trace session activation message includes information regarding signaling based MDT for the wireless device; wherein the inactive transition report request message is transmitted responsive to receiving the trace session activation message. 12. The method of Embodiment 11, wherein the trace session activation message is received from an Operation, Administration and Maintenance, OAM, node of the communication network.

13. The method of any of Embodiments 9-12, wherein the inactive transition report request message includes that the inactive transition report request message is dedicated for MDT purposes.

14. The method of any of Embodiments 1-13, wherein the CN node comprises an Access Management Function, AMF, node of the communication network.

15. A method of operating a radio access network, RAN, node, the method comprising: receiving a trace message including minimization of drive tests, MDT, information for a wireless device from a core network, CN, node; and responsive to the trace message, transmitting a trace failure indication message for the wireless device to the CN node based on the wireless device being in an inactive state and/or based on the wireless device being not reachable.

16. The method of Embodiment 15, wherein the trace failure indication message includes a cause indication, wherein the cause indication indicates that the wireless device is in a radio resource control, RRC, inactive state and/or that the wireless device is not reachable.

17. The method of any of Embodiments 15-16 further comprising: before receiving the trace message, receiving an inactive transition report request message for the wireless device from the CN node; and before receiving the trace message and responsive to receiving the inactive transition report request message, transmitting an inactive transition report message for the wireless device to the CN node, wherein the inactive transition report message indicates that the wireless device is in an active state.

18. The method of any of Embodiment 17, wherein the inactive transition report request message is a radio resource control, RRC, inactive transition report request message.

19. The method of any of Embodiments 17-18, wherein the inactive transition report request message includes an indication that the inactive transition report request message is dedicated for MDT purposes.

20. The method of any of Embodiments 15-19, wherein the trace message is a trace start message with the MDT information including MDT measurement control/configuration information for the wireless device or a deactivate trace message with the MDT information including MDT measurement control/configuration information for the wireless device. 21. The method of any of Embodiments 20, wherein the MDT measurement control/configuration information includes at least one of Area scope (e.g. TA, Cell), Trace Reference, List of measurements, Reporting Trigger, Report Interval, Report Amount, Event Threshold, Logging Interval, Logging duration, Measurement period, Collection period for RRM measurements, Positioning method, and/or MDT PLMN List.

22. The method of any of Embodiments 20-21, wherein the MDT measurement control/configuration information includes at least one of Trace Reference, List of

measurements, and/or MDT PLMN List

23. The method of any of Embodiments 15-22, wherein the CN node comprises an Access Management Lunction, AMF, node of the communication network.

24. A method of operating a radio access network, RAN, node, the method comprising: receiving a trace message including minimization of drive tests, MDT, information for a wireless device from a core network, CN, node; and responsive to receiving the trace message, storing MDT measurement control/configuration information in a context for the wireless device in memory of the RAN node, wherein the MDT measurement control/configuration information is based on the MDT information from the trace message.

25. The method of Embodiment 24 further comprising: configuring the wireless device to perform MDT measurement and reporting based on the MDT measurement and configuration information stored in the context for the wireless device.

26. The method of Embodiment 25 further comprising: responsive to receiving the trace message, determining that the wireless device is in an inactive state; after determining that the wireless device is in the inactive state, determining that the wireless device has transitioned from the inactive state to a connected state; wherein configuring the wireless device comprises configuring the wireless device responsive to determining that the wireless device has transitioned from the inactive state to the connected state.

27. The method of Embodiment 26, wherein the inactive state is a radio resource control, RRC, inactive state, and wherein the connected state is an RRC connected state.

28. The method of any of Embodiments 25-27, wherein the RAN node comprises a central unit, CU, and a distributed unit, DU, wherein the trace message is received by the RAN node CU, wherein the MDT measurement control/configuration information is stored by the RAN node CU, and wherein configuring the wireless device comprises the RAN node CU preparing a measurement configuration based on the MDT measurement control/configuration information stored in the context for the wireless device, the RAN node CU preparing a radio resource control, RRC, message including the measurement configuration, and the RAN node CU sending the RRC message through the RAN node DU to the wireless device.

29. The method of any of Embodiments 25-27, wherein the RAN node comprises a central unit control plane, CU-CP, a central unit user plane, CU-UP, and a distributed unit, DU, wherein the trace message is received by the RAN node CU-CP, wherein the MDT measurement control/configuration information is stored by the RAN node CU-CP, and wherein configuring the wireless device comprises the RAN node CU-CP preparing a measurement configuration based on a list of measurements from the MDT measurement control/configuration information stored in the context for the wireless device, the RAN node CU-CP preparing a radio resource control, RRC, message including the measurement configuration, and the RAN node CU-CP sending the RRC message through the RAN node DU to the wireless device.

30. The method of any of Embodiments 25-27, wherein the RAN node comprises a central unit, CU, and a distributed unit, DU, wherein the trace message is received by the RAN node CU, wherein configuring the wireless device comprises the RAN node CU transmitting information from the trace message to the RAN node DU, the RAN node DU preparing a measurement configuration based on the information from the trace message, the RAN node DU transmitting the measurement configuration to the RAN node CU, the RAN node CU preparing a radio resource control, RRC, message including the measurement configuration, and the RAN node CU sending the RRC message through the RAN node DU to the wireless device.

31. The method of Embodiment 30, wherein configuring the wireless device further comprises sending a notification of configuring the wireless device from the RAN node DU to a core network management system associated with the RAN node DU.

32. The method of Embodiment 30, wherein configuring the wireless device further comprises sending a request for permission to perform configuring the wireless device from the RAN node DU to a core network management system associated with the RAN node DU.

33. The method of Embodiment 30, wherein configuring the wireless device further comprises receiving a trace collection entity IP address at the RAN node DU, the method further comprising: reporting MDT data received from the wireless device at the RAN node DU from the RAN node DU to a trace collection entity using the trace collection entity IP address. 34. The method of Embodiment 30, wherein the information from the trace message includes a trace collection entity IP address, the method further comprising: after configuring the wireless device, receiving MDT data from the wireless device at the RAN node DU; and responsive to receiving the MDT data at the RAN node DU, reporting the MDT data from the RAN node DU to a trace collection entity using the trace collection entity IP address at the RAN node DU.

35. The method of Embodiment 30 further comprising: after configurating the wireless device, receiving MDT data from the wireless device at the RAN node DU; responsive to receiving the MDT data at the RAN node DU, sending the MDT data from the RAN node DU to the RAN node CU; and reporting the MDT data from the RAN node CU to a trace collection entity.

36. The method of any of Embodiments 25-27, wherein the RAN node comprises a central unit control plane, CU-CP, a central unit user plane, CU-UP, and a distributed unit, DU, wherein the trace message is received by the RAN node CU-CP, wherein configuring the wireless device comprises the RAN node CU-CP transmitting information from the trace message to the RAN node CU-UP, the RAN node CU-UP preparing a measurement

configuration based on the information from the trace message, the RAN node CU-UP transmitting the measurement configuration to the RAN node CU-CP, the RAN node CU-CP preparing a radio resource control, RRC, message including the measurement configuration, and the RAN node CU-CP sending the RRC message through the RAN node DU to the wireless device.

37. The method of Embodiment 36, wherein configuring the wireless device further comprises sending a notification of configuring the wireless device from the RAN node CU-UP to a core network management system associated with the RAN node CU-UP.

38. The method of Embodiment 36, wherein configuring the wireless device further comprises sending a request for permission to perform configuring the wireless device from the RAN node CU-UP to a core network management system associated with the RAN node CU- UP.

39. The method of Embodiment 36, wherein configuring the wireless device further comprises receiving a trace collection entity IP address at the RAN node CU-UP, the method further comprising: reporting MDT data received from the wireless device at the RAN node CU- UP from the RAN node CU-UP to a trace collection entity using the trace collection entity IP address.

40. The method of Embodiment 36, wherein the information from the trace message includes a trace collection entity IP address, the method further comprising: after configuring the wireless device, receiving MDT data from the wireless device at the RAN node CU-UP through the RAN node DU; and responsive to receiving the MDT data at the RAN node CU-UP, reporting the MDT data from the RAN node CU-UP to a trace collection entity using the trace collection entity IP address at the RAN node CU-UP.

41. The method of Embodiment 36 further comprising: after configurating the wireless device, receiving MDT data from the wireless device at the RAN node CU-UP through the RAN node DU; responsive to receiving the MDT data at the RAN node CU-UP, sending the MDT data from the RAN node CU-UP to the RAN node CU-CP; and

reporting the MDT data from the RAN node CU-CP to a trace collection entity.

42. The method of any of Embodiments 24-26, wherein the RAN node is a first RAN node, the method further comprising: receiving a request for the context for the wireless device from a second RAN node; and responsive to receiving the request for the context for the wireless device, transmitting the context for the wireless device to the second RAN node, wherein the context for the wireless device includes MDT measurement control/configuration information.

43. The method of Embodiment 24 further comprising: responsive to receiving the trace message, determining that the wireless device is in an inactive state; and responsive to determining that the wireless device is in the inactive state, triggering RAN paging for the wireless device.

44. The method of Embodiment 43 further comprising: after triggering RAN paging, performing a connection procedure for the wireless device based on the RAN paging to move the wireless device to a connected state; and after moving the wireless device to the connected state, configuring the wireless device to perform MDT measurement and reporting based on the MDT measurement control/configuration information stored in the context for the wireless device.

45. The method of Embodiment 43, wherein the RAN node is a first RAN node, the method further comprising: after triggering RAN paging, receiving a request for the context for the wireless device form a second RAN node; and responsive to receiving the request for the context for the wireless device, transmitting the context for the wireless device to the second RAN node, wherein the context for the wireless device includes MDT measurement control/ configuration information.

46. The method of any of Embodiments 24-45, wherein the MDT measurement control/configuration information includes at least one of Area scope (e.g. TA, Cell), Trace Reference, List of measurements, Reporting Trigger, Report Interval, Report Amount, Event Threshold, Logging Interval, Logging duration, Measurement period, Collection period for RRM measurements, Positioning method, and/or MDT PLMN List.

47. The method of any of Embodiments 24-46, wherein the MDT measurement control/configuration information includes at least one of Trace Reference, List of

measurements, and/or MDT PLMN List

48. A method of operating a core network, CN, node of a communication network, the method comprising: transmitting a trace activation message including MDT information for a wireless device to a radio access network, RAN, node; receiving a trace suspend indication message from the RAN node for the wireless device, wherein the trace suspend indication message indicates that the wireless device is in an inactive state; responsive to receiving the trace suspend indication message, starting a timer relating to the wireless device.

49. The method of Embodiment 48, wherein trace suspend indication message indicates a duration of the timer.

50. The method of any of Embodiments 48-49 further comprising: receiving a trace resume indication message for the wireless device, wherein the trace resume indication message indicates that the wireless device is in a radio resource control, RRC, connected state; and responsive to receiving the trace resume indication message for the wireless device before expiration of the timer, releasing the timer.

51. The method of Embodiment 50, wherein the trace resume indication message is received from the RAN node.

52. The method of Embodiment 50, wherein the RAN node is a first RAN node, and wherein the trace resume indication message is received from a second RAN node.

53. The method of any of Embodiments 48-49, wherein the RAN node is a first RAN node, and wherein the trace activation message is a first trace activation message, the method further comprising: responsive to expiration of the timer, transmitting a second trace activation message including the MDT information for the wireless device to a second RAN node. 54. The method of any of Embodiments 48-53, wherein the MDT measurement information includes at least one of job Type, Area scope (e.g. TA, Cell), Trace Reference, List of measurements, Reporting Trigger, Report Interval, Report Amount, Event Threshold, Logging Interval, Logging duration, Measurement period, Collection period for RRM measurements, Positioning method, and/or MDT PLMN List.

55. The method of any of Embodiments 48-54, wherein the MDT information includes at least one of job Type, Trace Reference, List of measurements, and/or MDT PLMN List.

56. A method of operating a radio access network, RAN, node, the method comprising: receiving a trace activation message including MDT information for a wireless device from a core network, CN, node; responsive to receiving the trace activation message, determining whether the wireless device is in a connected or inactive state; responsive to determining that the wireless device is in the inactive state, transmitting a trace suspend indication message to the CN node for the wireless device, wherein the trace suspend indication message indicates that the wireless device is in the inactive state; and responsive to receiving the trace suspend indication message, starting a timer relating to the wireless device.

57. The method of Embodiment 56, wherein trace suspend indication message indicates a duration of the timer.

58. The method of any of Embodiments 56-57, wherein the RAN node is a first RAN node, the method further comprising: responsive to receiving the trace activation message, storing MDT measurement control/configuration information in a context for the wireless device in memory of the RAN node; and responsive to receiving a request for the context for the wireless device from a second RAN node before expiration of the timer, transmitting context response to the second RAN node including the context for the wireless device.

59. The method of Embodiment 58 further comprising: responsive to receiving a request for a context request for the wireless device from a second RAN node before expiration of the timer, releasing the timer and/or releasing the context for the wireless device.

60. The method of any of Embodiments 58-59, wherein the MDT measurement control/configuration information includes at least one of job Type, SUPI/IMEI(SV), GUTI, C- RNTI, Area scope (e.g. TA, Cell), Trace Reference, List of measurements, Reporting Trigger, Report Interval, Report Amount, Event Threshold, Logging Interval, Logging duration, Measurement period, Collection period for RRM measurements, Positioning method, and/or MDT PLMN List.

61. The method of any of Embodiments 58-60, wherein the MDT measurement control/configuration information includes at least one of job Type, Trace Reference, List of measurements, and/or MDT PLMN List.

62. The method of any of Embodiments 56-61 further comprising: responsive to expiration of the timer, releasing the context for the wireless device.

63. A method of operating a wireless device, the method comprising: receiving a minimization of drive tests, MDT, configuration from a wireless communication network, wherein the MDT configuration includes MDT measurement/configuration information and a list of trace collection entity identifiers; performing an MDT measurement based on the MDT measurement/configuration information; and transmitting an MDT report including information based on the MDT measurement and including the list of trace collection entity identifiers.

64. The method of Embodiment 63, wherein each of the trace collection entity identifiers corresponds to a respective trace collection entity internet protocol, IP, address.

65. The method of any of Embodiments 63-64, wherein the MDT measurement control/configuration information includes at least one of job Type, Area scope (e.g. TA, Cell), Trace Reference, List of measurements, Reporting Trigger, Report Interval, Report Amount, Event Threshold, Logging Interval, Logging duration, Measurement period, Collection period for RRM measurements, Positioning method, and/or MDT PLMN List.

66. The method of any of Embodiments 63-65, wherein the MDT measurement control/configuration information includes at least one of job Type, Trace Reference, List of measurements, and/or MDT PLMN List.

67. A method of operating a radio access network, RAN, node, the method comprising: receiving a trace message including minimization of drive tests, MDT, information for a wireless device from a core network, CN, node; and responsive to receiving the trace message, determining an MDT configuration for the wireless device.

68. The method of Embodiment 67 further comprising: configuring the wireless device to perform MDT measurement and reporting based on the MDT configuration for the wireless device. 69. The method of any of Embodiments 68, wherein the RAN node comprises a central unit, CU, and a distributed unit, DU, wherein the trace message is received by the RAN node CU, and wherein configuring the wireless device comprises the RAN node CU preparing a measurement configuration based on the MDT configuration for the wireless device, the RAN node CU preparing a radio resource control, RRC, message including the measurement configuration, and the RAN node CU sending the RRC message through the RAN node DU to the wireless device.

70. The method of any of Embodiments 68, wherein the RAN node comprises a central unit control plane, CU-CP, a central unit user plane, CU-UP, and a distributed unit, DU, wherein the trace message is received by the RAN node CU-CP, and wherein configuring the wireless device comprises the RAN node CU-CP preparing a measurement configuration based on a list of measurements from the MDT information for the wireless device, the RAN node CU-CP preparing a radio resource control, RRC, message including the measurement configuration, and the RAN node CU-CP sending the RRC message through the RAN node DU to the wireless device.

71. The method of any of Embodiments 68, wherein the RAN node comprises a central unit, CU, and a distributed unit, DU, wherein the trace message is received by the RAN node CU, wherein configuring the wireless device comprises the RAN node CU transmitting information from the trace message to the RAN node DU, the RAN node DU preparing a measurement configuration based on the MDT information from the trace message, the RAN node DU transmitting the measurement configuration to the RAN node CU, the RAN node CU preparing a radio resource control, RRC, message including the measurement configuration, and the RAN node CU sending the RRC message through the RAN node DU to the wireless device.

72. The method of Embodiment 71, wherein configuring the wireless device further comprises sending a notification of configuring the wireless device from the RAN node DU to a core network management system associated with the RAN node DU.

73. The method of Embodiment 71, wherein configuring the wireless device further comprises sending a request for permission to perform configuring the wireless device from the RAN node DU to a core network management system associated with the RAN node DU.

74. The method of Embodiment 71, wherein configuring the wireless device further comprises receiving a trace collection entity IP address at the RAN node DU, the method further comprising: reporting MDT data received from the wireless device at the RAN node DU from the RAN node DU to a trace collection entity using the trace collection entity IP address.

75. The method of Embodiment 71, wherein the information from the trace message includes a trace collection entity IP address, the method further comprising: after configuring the wireless device, receiving MDT data from the wireless device at the RAN node DU; and responsive to receiving the MDT data at the RAN node DU, reporting the MDT data from the RAN node DU to a trace collection entity using the trace collection entity IP address at the RAN node DU.

76. The method of Embodiment 71 further comprising: after configurating the wireless device, receiving MDT data from the wireless device at the RAN node DU; responsive to receiving the MDT data at the RAN node DU, sending the MDT data from the RAN node DU to the RAN node CU; and reporting the MDT data from the RAN node CU to a trace collection entity.

77. The method of any of Embodiments 68, wherein the RAN node comprises a central unit control plane, CU-CP, a central unit user plane, CU-UP, and a distributed unit, DU, wherein the trace message is received by the RAN node CU-CP, wherein configuring the wireless device comprises the RAN node CU-CP transmitting information from the trace message to the RAN node CU-UP, the RAN node CU-UP preparing a measurement configuration based on the information from the trace message, the RAN node CU-UP transmitting the measurement configuration to the RAN node CU-CP, the RAN node CU-CP preparing a radio resource control, RRC, message including the measurement configuration, and the RAN node CU-CP sending the RRC message through the RAN node DU to the wireless device.

78. The method of Embodiment 77, wherein configuring the wireless device further comprises sending a notification of configuring the wireless device from the RAN node CU-UP to a core network management system associated with the RAN node CU-UP.

79. The method of Embodiment 77, wherein configuring the wireless device further comprises sending a request for permission to perform configuring the wireless device from the RAN node CU-UP to a core network management system associated with the RAN node CU- UP.

80. The method of Embodiment 77, wherein configuring the wireless device further comprises receiving a trace collection entity IP address at the RAN node CU-UP, the method further comprising: reporting MDT data received from the wireless device at the RAN node CU- UP from the RAN node CU-UP to a trace collection entity using the trace collection entity IP address.

81. The method of Embodiment 77, wherein the information from the trace message includes a trace collection entity IP address, the method further comprising: after configuring the wireless device, receiving MDT data from the wireless device at the RAN node CU-UP through the RAN node DU; and responsive to receiving the MDT data at the RAN node CU-UP, reporting the MDT data from the RAN node CU-UP to a trace collection entity using the trace collection entity IP address at the RAN node CU-UP.

82. The method of Embodiment 77 further comprising: after configurating the wireless device, receiving MDT data from the wireless device at the RAN node CU-UP through the RAN node DU; responsive to receiving the MDT data at the RAN node CU-UP, sending the MDT data from the RAN node CU-UP to the RAN node CU-CP; and reporting the MDT data from the RAN node CU-CP to a trace collection entity.

83. A wireless device (900) configured to operate in a communication network, the wireless device comprising: processing circuitry (903); and memory (905) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the wireless device to perform operations according to any of Embodiments 63-66.

84. A wireless device (900) configured to operate in a communication network, wherein the wireless device is adapted to perform according to any of Embodiments 63-66.

85. A computer program comprising program code to be executed by processing circuitry (903) of a wireless device (900) configured to operate in a communication network, whereby execution of the program code causes the wireless device (900) to perform operations according to any of Embodiments 63-66.

86. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (903) of a wireless device (900) configured to operate in a communication network, whereby execution of the program code causes the wireless device (900) to perform operations according to any of Embodiments 63-66.

87. A radio access network, RAN, node (1000) configured to operate in a

communication network, the RAN node comprising: processing circuitry (1003); and memory (1005) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the RAN node to perform operations according to any of Embodiments 15-47, 56-62, and 67-82.

88. A first radio access network, RAN, node (1000) configured to operate in a communication network, wherein the RAN node is adapted to perform according to any of Embodiments 15-47, 56-62, and 67-82.

89. A computer program comprising program code to be executed by processing circuitry (1003) of a radio access network, RAN, node (1000) configured to operate in a communication network, whereby execution of the program code causes the RAN node (400) to perform operations according to any of Embodiments 15-47, 56-62, and 67-82.

90. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1003) of a radio access network, RAN, node (1000) configured to operate in a communication network, whereby execution of the program code causes the RAN node (1000) to perform operations according to any of

Embodiments 15-47, 56-62, and 67-82.

91. A core network, CN, node (1100) configured to operate in a communication network, the CN node comprising: processing circuitry (1103); and memory (1105) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the CN node to perform operations according to any of Embodiments 1-14 and 48-55.

92. A core network, CN, node (1100) configured to operate in a communication network, wherein the CN node is adapted to perform according to any of Embodiments 1-14 and 48-55.

93. A computer program comprising program code to be executed by processing circuitry (403) of a core network, CN, node (1100) configured to operate in a communication network, whereby execution of the program code causes the CN node (500) to perform operations according to any of Embodiments 1-14 and 48-55.

94. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1103) of a core network, CN, node (1100) configured to operate in a communication network, whereby execution of the program code causes the CN node (1100) to perform operations according to any of Embodiments 1-14 and 48- 55. 95. A method of operating a radio access network, RAN, node (gNBlOl) of a wireless communication network, the method comprising: receiving information for a minimization of drive tests, MDT, configuration for a wireless device (UE); determining a connection state of the wireless device; determining an MDT configuration state of the wireless device based on the connection status of the wireless device; and storing an MDT configuration state indicator for the wireless device in a context for the wireless device (UE) wherein the MDT configuration state indicator is based on the MDT configuration state of the wireless device.

96. The method of Embodiment 95 further comprising: storing the information for the MDT configuration in the context for the wireless device (UE).

97. The method of any of Embodiments 95-96, wherein determining the connection state comprises determining that the wireless device is in an inactive state, and wherein determining the MDT configuration state comprises determining that the MDT configuration state for the wireless device is a pending MDT configuration state responsive to determining that the wireless device is in the inactive state.

98. The method of Embodiment 97, wherein storing the MDT configuration state indicator comprises storing a pending MDT configuration state indicator in the context for the wireless device responsive to determining that the wireless device is in the inactive state and/or responsive to determining that the MDT configuration state is the pending MDT configuration state.

99. The method of Embodiment 97-98, wherein the information for the MDT

configuration is received from a core network node, the method further comprising: transmitting an indication that the MDT configuration state for the wireless device is the pending MDT configuration state to the core network node responsive to determining that the wireless device is in the inactive state and/or responsive to determining that the MDT configuration state is the pending MDT configuration state.

100. The method of Embodiment 99, wherein the core network node comprises an access and mobility management function, AMF, node.

101. The method of any of Embodiments 97-100, wherein the RAN node is a first RAN node, the method further comprising: receiving a context request from a second RAN node requesting the context for the wireless device after storing the pending MDT configuration state indicator in the context for the wireless device; and transmitting the context for the wireless device to the second RAN node responsive to receiving the context request, wherein the context includes the pending MDT configuration state indicator for the wireless device.

102. The method of Embodiment 101, wherein the context for the wireless device is transmitted to the second RAN node responsive to receiving the context request and responsive to the MDT configuration state being the pending MDT configuration state.

103. The method of Embodiment 101-102 further comprising: determining that the second RAN node belongs to an area scope of the MDT configuration for the wireless device; wherein transmitting the context comprises transmitting the context for the wireless device responsive to determining that the second RAN node belongs to the area scope of the MDT configuration for the wireless device.

104. The method of Embodiment 103, wherein the information for the MDT

configuration is received from a core network node, the method further comprising: transmitting an indication that the MDT configuration is transferred to the second RAN node responsive to determining that the second RAN node belongs to the area scope of the MDT configuration for the wireless device, wherein the indication that the MDT configuration is transferred to the second RAN node is transmitted to the core network node.

105. The method of any of Embodiments 97-100, wherein the information for the MDT configuration is received from a core network node, wherein the RAN node is a first RAN node, the method further comprising: receiving a context request from a second RAN node requesting the context for the wireless device after storing the MDT configuration state indicator in the context for the wireless device; determining that the second RAN node does not belong to an area scope of the MDT configuration for the wireless device; and transmitting an indication that the MDT configuration for the wireless device failed responsive to the context request and responsive to the second RAN node not belonging to the area scope of the MDT configuration for the wireless device, wherein the indication that the MDT configuration for the wireless device failed is transmitted to the core network node.

106. The method of any of Embodiments 95-96, wherein determining the connection state comprises determining that the wireless device is in a connected state, and wherein determining the MDT configuration state comprises determining that the MDT configuration state for the wireless device is an activated MDT configuration state responsive to determining that the wireless device is in the connected state, and wherein storing the MDT configuration state indicator comprises storing an activated MDT configuration state indicator in the context for the wireless device responsive to determining that the wireless device is in the connected state and/or responsive to determining that the MDT configuration state is the activated MDT configuration state.

107. The method of Embodiment 106 further comprising: configuring the wireless device with the MDT configuration responsive to determining that the wireless device is in the connected state.

108. The method of Embodiment 107, wherein the connected state is a radio resource control, RRC, connected state, and wherein configuring the wireless device with the MDT configuration comprises configuring the wireless device with the MDT configuration using RRC signaling that is transmitted to the wireless device.

109. The method of any of Embodiments 106-108, wherein the RAN node is a first RAN node, the method further comprising: receiving a context request from a second RAN node requesting the context for the wireless device; and transmitting the context for the wireless device to the second RAN node responsive to receiving the context request, wherein the context includes the activated MDT configuration state indicator for the wireless device.

110. The method of any of Embodiments 95-109, wherein the information for the MDT configuration is received as an element of a trace start message.

I l l The method of any of Embodiments 95-110, wherein the information for the MDT configuration is received from a core network node.

112. The method of Embodiment 111, wherein the core network node comprises an access and mobility management function, AMF, node.

113. The method of any of Embodiments 95-112, wherein the MDT configuration comprises an MDT measurement control and configuration.

114. The method of any of Embodiments 95-113, wherein the connection state comprises a Radio Resource Control, RRC, connection state.

115. A method of operating a first radio access network, RAN, node (gNB104) of a wireless communication network, the method comprising: transmitting a request for a context for a wireless device to a second RAN node; and receiving a context response from the second RAN node, wherein the context response includes the context for the wireless device, and wherein the context for the wireless device includes an MDT configuration state indicator for the wireless device and information for an MDT configuration for the wireless device.

116. The method of Embodiment 115, wherein the MDT configuration state indicator for the wireless device is a pending MDT configuration state indicator, the method further comprising: configuring the wireless device with the MDT configuration responsive to the MDT configuration state indicator of the wireless device being the pending MDT configuration state indicator.

117. The method of Embodiment 116, wherein configuring the wireless device with the MDT configuration comprises configuring the wireless device with the MDT configuration using Radio Resource Control, RRC, signaling that is transmitted to the wireless device.

118. The method of any of Embodiments 116-117 further comprising: changing the MDT configuration state indicator for the wireless device from the pending MDT configuration state indicator to an activated MDT configuration state indicator.

119. The method of Embodiment 118 further comprising: storing the context for the wireless device including the pending MDT configuration state indicator and the information for the MDT configuration for the wireless device responsive to receiving the context response; wherein changing the MDT configuration state indicator comprises changing the MDT configuration state indicator from the pending MDT configuration state indicator to the activated MDT configuration state indicator in the context for the wireless device stored at the first RAN node.

120. The method of any of Embodiments 116-119 further comprising: transmitting an indication that the wireless device is configured with the MDT configuration.

121. The method of Embodiment 120, wherein the indication that the wireless device is configured with the MDT configuration is transmitted to at least one of a core network node and/or the second RAN node.

122. The method of any of Embodiments 116-121, wherein the wireless device is configured with the MDT configuration responsive to the MDT configuration state indicator of the wireless device being the pending MDT configuration state indicator and responsive to the first RAN node belonging to an area scope of the MDT configuration for the wireless device.

123. The method of Embodiment 115, wherein the MDT configuration state indicator of the wireless device is a pending MDT configuration state indicator, the method further comprising: transmitting an indication that the wireless device is not configured with the MDT configuration responsive to the MDT configuration state indicator of the wireless device being the pending MDT configuration state indicator and responsive to the first RAN node not belonging to an area scope of the MDT configuration for the wireless device, wherein the indication that the wireless device is not configured with the MDT configuration is transmitted to a core network node.

124. The method of Embodiment 123 further comprising: receiving an indication to use the MDT configuration for the wireless device from the context response, wherein the indication to use the MDT configuration is received from the core network node after transmitting the indication that the wireless device is not configured with the MDT configuration; and configuring the wireless device with the MDT configuration responsive to receiving the indication to use the MDT configuration.

125. The method of Embodiment 124, wherein the indication to use the MDT configuration is received using a path switch response message.

126. The method of Embodiment 123, wherein the MDT configuration comprises a first MDT configuration, the method further comprising: receiving an indication to use a second MDT configuration for the wireless device, wherein the second MDT configuration is different than the first MDT configuration, and wherein the indication to use the second MDT configuration is received from the core network node; and configuring the wireless device with the second MDT configuration responsive to receiving the indication to use the second MDT configuration.

127. The method of Embodiment 126, wherein the indication to use the second MDT configuration is received using a path switch response message.

128. The method of any of Embodiments 124-127, wherein configuring the wireless device comprises configuring the wireless device using radio resource control, RRC, signaling that is transmitted to the wireless device,

129. The method of any of Embodiments 123-128, wherein the core network node comprises an access and mobility management function, AMF, node.

130. The method of any of Embodiments 123-129, wherein the indication that the wireless device is not configured with the MDT configuration is transmitted using a path switch request message. 131. The method of any of Embodiments 115-130, wherein the request for the context for the wireless device is transmitted responsive to the wireless device changing from an inactivate state to a connected state at the first RAN node.

132. A method of operating a core network node of a communication network, the method comprising: transmitting information for a minimization of drive tests, MDT, configuration for a wireless device (UE) to a first radio access network, RAN, node; and receiving a request from a second RAN node wherein the request indicates that the wireless device is not configured with the MDT configuration.

133. The method of Embodiment 132 further comprising: transmitting a response to the second RAN node to use the MDT configuration for the wireless device connected with the second RAN node, wherein the response is transmitted in response to the request.

134. The method of Embodiment 133, wherein the response to use the MDT configuration is transmitted responsive to determining that an area scope of the MDT configuration is applicable for the wireless device connected to the second RAN node.

135. The method of any of Embodiments 133-134, wherein the request is received using a path switch request message, and wherein the response is transmitted using a path switch response message.

136. The method of Embodiment 132, wherein the MDT configuration is a first MDT configuration for the wireless device, the method further comprising: transmitting a response to the second RAN node to use a second MDT configuration for the wireless device, wherein the response is transmitted in response to the request, and wherein the first and second MDT configurations are different.

137. The method of Embodiment 136, wherein the response to use the second MDT configuration is transmitted responsive to determining that al area scope of the MDT configuration is not applicable for the wireless device connected to the second RAN node.

138. The method of any of Embodiments 136-137, wherein the request is received using a path switch request message, and wherein the response is transmitted using a path switch response message.

139. The method of any of Embodiments 132-138, wherein the core network node comprises an access and mobility management function, AMF, node. 140. A radio access network, RAN, node (gNBlOl, gNB104), the RAN node comprising: processing circuitry (1003); and memory (1005) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the RAN node to perform operations according to any of Embodiments 95-131.

141. A first radio access network, RAN, node (1000), wherein the RAN node is adapted to perform according to any of Embodiments 95-131.

142. A computer program comprising program code to be executed by processing circuitry (1003) of a radio access network, RAN, node (1000), whereby execution of the program code causes the RAN node (400) to perform operations according to any of Embodiments 95- 131.

143. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1003) of a radio access network, RAN, node (1000), whereby execution of the program code causes the RAN node (1000) to perform operations according to any of Embodiments 95-131.

144. A core network, CN, node (1100), the CN node comprising: processing circuitry (1103); and memory (1105) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the CN node to perform operations according to any of Embodiments 132-139.

145. A core network, CN, node (1100), wherein the CN node is adapted to perform according to any of Embodiments 132-139.

146. A computer program comprising program code to be executed by processing circuitry (403) of a core network, CN, node (1100), whereby execution of the program code causes the CN node (500) to perform operations according to any of Embodiments 132-139.

147. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1103) of a core network, CN, node (1100), whereby execution of the program code causes the CN node (1100) to perform operations according to any of Embodiments 132-139.

Explanations are provided below for various abbreviations/acronyms used in the present disclosure.

Abbreviation Explanation 3GPP 3rd Generation Partnership Project

5G 5th Generation

5GC 5G Core network

AMF Access and Mobility management Function

AS Access Stratum

BRSRP Beam level RSRP

BRSRQ Beam level RSRQ

BSINR Beam level SINR

C-RNTI Cell Radio Network Temporary Identifier

CE Control Element

CFRA Contention Free Random Access

CHO Conditional Handover

CN Core Network

CP Control Plane

C-RNTI Cell Radio Network Temporary Identifier

CSI-RS Channel State Information Reference Signal CU Central Unit

dB decibel

DC Dual Connectivity

DL Downlink

DU Distributed Unit

eNB eNodeB

eNodeB Evolved NodeB

EPC Evolved Packet Core

EUTRA Evolved Universal Terrestrial Radio Access

/E-UTRA

EUTRAN Evolved Universal Terrestrial Radio Access Network /E-UTRAN

FFS For Further Study

gNB/gNodeB A radio base station in NR.

GPRS General Packet Radio Service GTP GPRS Tunneling Protocol

GUTI Globally Unique Temporary Identifier

HO Handover

IE Information Element

IMEI International Mobile Equipment Identity

IMSI International Mobile Subscriber Identity

IP Internet Protocol

LTE Long Term Evolution

MAC Medium Access Control

MAC CE MAC Control Element

MCG Master Cell Group

MDT Minimization of drive tests

MME Mobility Management Entity

MSG Message

NAS Non-access Stratum

NG The interface/reference point between NG-RAN and 5GC.

NGAP NG Application Protocol / Next Generation Application Protocol

NG-RAN Next Generation Radio Access Network

NR New Radio

OAM Operations, Administration and Maintenance

PCell Primary Cell (i.e. the primary cell of a MCG)

PDU Protocol Data Unit

PHR Power Headroom Report

PLMN Public Land Mobile Network

PSCell Primary Secondary Cell (i.e. the primary cell of a SCG)

QoS Quality of Service

RA Random Access

RAR Random Access Response

RACH Random Access Channel

RAN Radio Access Network

RAT Radio Access Technology RLF Radio Link Failure

RNA RAN-based Notification Area

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

SI The interface/reference point between E-UTRAN and EPC.

SCell Secondary Cell

SCG Secondary Cell Group

SINR Signal to Interference and Noise Ratio

SpCell Special Cell, i.e. either a PCell or a PSCell.

SN Sequence Number

SRB Signaling Radio Bearer

SSB Synchronization Signal Block

SUPI Subscription Permanent Identifier

TA Tracking Area

TS Technical Specification

UE User Equipment

UP User Plane

UPF User Plane Function

UTRAN Universal Terrestrial Radio Access Network

Uu The interface/reference point between

a gNB/eNB and a UE, i.e. the radio interface.

WLAN Wireless Local Area Network

X2 The interface/reference point between two eNBs.

X2AP X2 Application Protocol

Xn The interface/reference point between two gNBs.

Additional explanation is provided below. 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.

Some of the embodiments contemplated herein will now be 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.

Figure 39 illustrates a wireless network in accordance with some embodiments.

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 39. For simplicity, the wireless network of Figure 39 only depicts network QQ106, network nodes QQ 160 and QQ 160b, and WDs QQ 110, QQ 110b, and QQ110c (also referred to as mobile terminals). 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 QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide

communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network. The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile

Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), 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 QQ106 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 QQ160 and WD QQ110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

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

In Figure 39, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of Figure 39 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 QQ160 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 QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 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 QQ160 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 QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless

technologies integrated into network node QQ160, 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 QQ160.

Processing circuitry QQ170 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 QQ170 may include processing information obtained by processing circuitry QQ170 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 QQ170 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 QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC). In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 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 QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 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 QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.

Device readable medium QQ180 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 QQ170. Device readable medium QQ180 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 QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated. Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 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 QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 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 QQ162, interface QQ190, and/or processing circuitry QQ170 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 QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 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 QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. 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 QQ160 may include additional components beyond those shown in Figure 39 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 QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

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 3 GPP 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 3 GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, 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 QQ110.

Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 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 QQ111 may be considered an interface.

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

Processing circuitry QQ120 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 QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.

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

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, 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 QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry QQ120 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 QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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 QQ130 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 QQ120. Device readable medium QQ130 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 QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated. User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 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 QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 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 QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 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 QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment QQ134 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 QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 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 QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 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 QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

Figure 40 illustrates a user Equipment in accordance with some embodiments.

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

In Figure 40, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 40, 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 40, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 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 QQ201 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 QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. 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 QQ200. 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 QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200. 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 40, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a. Network QQ243a 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 QQ243a may comprise a Wi-Fi network. Network connection interface QQ211 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 QQ211 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 QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 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 QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 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 QQ221 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 QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

Storage medium QQ221 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 QQ221 may allow UE QQ200 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 QQ221, which may comprise a device readable medium.

In Figure 40, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks.

Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 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. QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 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 QQ231 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 QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b 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 QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200.

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 QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231. 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 41 illustrates a virtualization environment in accordance with some embodiments.

Figure 41 is a schematic block diagram illustrating a virtualization environment QQ300 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 QQ300 hosted by one or more of hardware nodes QQ330. 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 QQ320 (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 QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, 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 QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

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

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

As shown in Figure 41, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 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) QQ3100, which, among others, oversees lifecycle management of applications QQ320.

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 QQ340 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 QQ340, and that part of hardware QQ330 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 QQ340, 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 QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in Figure 41.

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

In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200. Figure 42 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to FIGURE 42, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414. Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491, QQ492 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 QQ412.

Telecommunication network QQ410 is itself connected to host computer QQ430, 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 QQ430 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 QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420. Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).

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

Figure 43 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some 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 43. In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 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 QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.

Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 43) served by base station QQ520. Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may pass through a core network (not shown in Figure 43) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, 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 QQ520 further has software QQ521 stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, 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 QQ530 further comprises software QQ531, which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 43 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491, QQ492 of Figure 42, respectively. This is to say, the inner workings of these entities may be as shown in Figure 43 and independently, the surrounding network topology may be that of Figure 42. In Figure 43, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, 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 QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the random access speed and/or reduce random access failure rates and thereby provide benefits such as faster and/or more reliable random access.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection QQ550 between host computer QQ510 and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550 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 QQ511, QQ531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.

Figure 44 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 44 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 42 and 43. For simplicity of the present disclosure, only drawing references to Figure 44 will be included in this section. In step QQ610, the host computer provides user data. In substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (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 QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 45 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

Figure 45 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 42 and 43. For simplicity of the present disclosure, only drawing references to Figure 45 will be included in this section. In step QQ710 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 QQ720, 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 QQ730 (which may be optional), the UE receives the user data carried in the transmission. Figure 46 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 46 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 42 and 43. For simplicity of the present disclosure, only drawing references to Figure 46 will be included in this section. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which may be optional) of step QQ810, 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 QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 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 47 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

Figure 47 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 42 and 43. For simplicity of the present disclosure, only drawing references to Figure 47 will be included in this section. In step QQ910 (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 QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

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

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.

ABBREVIATIONS

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

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel

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

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI

eNB E-UTRAN NodeB

ePDCCH enhanced Physical Downlink Control Channel

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex

FFS For Further Study

GERAN GSM EDGE Radio Access Network gNB Base station in NR

GNSS Global Navigation Satellite System GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

EOS Line of Sight

FPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MBMS Multimedia Broadcast Multicast Services

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel PGW Packet Gateway

PHICH Physical Hybrid- ARQ Indicator Channel

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RAT Radio Access Technology

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR

Reference Signal Received Power

RSRQ Reference Signal Received Quality OR

Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway SI System Information

SIB System Information Block

SNR Signal to Noise Ratio

SON Self Optimized Network

ss Synchronization Signal

sss Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UE User Equipment

UL Uplink

UMTS Universal Mobile Telecommunication System

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WLAN Wide Local Area Network

Further definitions and embodiments are discussed below.

In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" includes any and all combinations of one or more of the associated listed items.

It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another

element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.

Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.

It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality /acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.