CONPIGURATION AND/OR REPORTING OP MEASUREMENTS IN LOGGED MDT

TECHNICAL FIELD

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

BACKGROUND

[0002] Minimization of Drive Test, MDT, was firstly studied in 3GPP Rel-9 (TR 36.805) driven by RAN2 with the purpose to 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.

[0003] The use cases in the TR 36.805 include: Coverage improvement/optimization; Mobility improvement/optimization; Capacity improvement/optimization; Parameterization for common channels; and/or Quality of Service, QoS, verification.

[0004] MDT types based on Radio Resource Control, RRC, states are discussed below.

[0005] In general, there are two types of MDT measurement: logging, i.e., Logged MDT; and Immediate MDT.

[0006] Logged MDT is discussed below.

[0007] 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 DownLink DL pilot strength measurements (RSRP/RSRQ) together with time information, detailed location information if available, and Wireless Local Area Network, WLAN, Bluetooth to the network using the UE 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 UE to perform additional measurements.

[0008] Table 1 illustrates measurement logging for Logged MDT. Table 1

[0009] For Logged MDT, UE receives the MDT configurations including logginginterval and loggingduration in the RRC message, i.e.,

LoggedMeasurementConfiguration, from the network. A timer (T330) is started at the UE upon receiving the configurations and set to loggingduration (10 min - 120 min). The UE 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 procedure is illustrated in Figure 1. As shown in Figure 1, a UE may perform MDT logging of Radio Resource Management RRM measurements at a plurality of MDT logging occasions (also referred to as MDT logging events) over an MDT logging interval.

[0010] The following text is captured in the vl6.0.0 of TS 38.331 associated to logged MDT configuration and measurements for New Radio NR. The User Equipment UE is not required to perform additional Radio Resource Management RRM measurements (i.e., intra-frequency, inter-frequency, and inter-RAT neighbor cell measurements), when the UE is configured with logged MDT.

[0011] Section 5.5a of TS 38.331 discusses Logged Measurements, and Section 5.5a.l of TS 38.331 discusses Logged Measurement Configuration.

[0012] Figure 5.5a.1.1-1 from Section 5.5a.l.l of TS 38.331 illustrates a Logged measurement configuration, and this figure is provided herewith as Figure 2.

[0013] The purpose of this procedure is to configure the UE to perform logging of measurement results while in RRC IDLE and RRC INACTIVE. The procedure applies to logged measurements capable UEs that are in RRC CONNECTED.

[0014] NOTE: NG-RAN may retrieve stored logged measurement information by means of the UE information procedure.

[0015] Section 5.5a.l.2 of TS 38.331 discusses Initiation.

[0016] NG-RAN initiates the logged measurement configuration procedure to UE in RRC CONNECTED by sending the LoggedMeasurementConfiguration message. [0017] Section 5.5a.l.3 of TS 38.331 discusses Reception of the LoggedMeasurementConfiguration by the UE as set forth below.

[0018] Upon receiving the LoggedMeasurementConfiguration message the UE shall:

1> discard the logged measurement configuration as well as the logged measurement information as specified in 5.5a.2;

1> store the received loggingDuration, logginglnterval and areaConfiguration, if included, in VarLogMeasConfig;

1> if the LoggedMeasurementConfiguration message includes plmn-

IdentityList:

2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN as well as the PLMNs included in plmn-IdentityList;

1> else:

2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN;

1> store the received absoluteTimelnfo, traceReference, traceRecordingSessionRef, tce-Id and reportType in VarLogMeasReport;

1> start timer T330 with the timer value set to the loggingDuration;

[0019] Section 5.5a.l.4 of TS 38.331 discusses T330 expiry as set forth below.

Upon expiry of T330 the UE shall:

1> release VarLogMeasConfig;

[0020] The UE is allowed to discard stored logged measurements, i.e. to release VarLogMeasReport, 48 hours after T330 expiry.

[0021] Section 5.5a.2 of TS 38.331 discusses Release of Logged Measurement Configuration.

[0022] In Section 5.5a.2.1 of TS 38.331, the purpose of this procedure is to release the logged measurement configuration as well as the logged measurement information.

[0023] Section 5.5a.2.2 of TS 38.331 discusses Initiation.

[0024] The UE shall initiate the procedure upon receiving a logged measurement configuration in another RAT. The UE shall also initiate the procedure upon power off or detach.

The UE shall: 1> stop timer T330, if running;

1> if stored, discard the logged measurement configuration as well as the logged measurement information, i.e. release the UE variables VarLogMeasConfig and VarLogMeasReport.

[0025] Section 5.5a.3 of TS 38.331 discusses Measurements logging.

[0026] In Section 5.5a.3.1 of TS 38.331, this procedure specifies the logging of available measurements by a UE in RRC IDLE and RRC INACTIVE that has a logged measurement configuration. The actual process of logging within the UE, takes place in RRC IDLE state could continue in RRC INACTIVE state or vice versa.

[0027] Section 5.5a.3.2 of TS 38.331 discusses Initiation as set forth below.

[0028] While T330 is running, the UE shall:

1> perform the logging in accordance with the following:

2> if the reportType is set to periodical in the VarLogMeasConfig:

3> if the UE is camping normally on an NR cell and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport and, if the cell is part of the area indicated by areaConfiguration if configured in VarLogMeasConfig:

4> perform the logging at regular time intervals, as defined by the logginglnterval in the LoggedEventTriggerConfig;

2> else if the reportType is set to eventTriggered, which indicates outOfCoverage:

3> perform the logging at regular time intervals as defined by the logginglnterval in VarLogMeasConfig only when the UE is in any cell selection state;

2> else if the reportType is set to eventType and eventLl is indicated:

3> perform the logging at regular time intervals as defined by the logginglnterval in VarLogMeasConfig only when the conditions indicated by the eventLl are met;

2> when performing the logging: > set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged measurement configuration was received; > if detailed location information became available during the last logging interval, set the content of the locationlnfo as follows:

4> include the locationCoordinates; > if WLAN-NameList is included in VarLogMeasConfig:

4> if detailed WLAN measurements are available:

5> include logMeasResultListWLAN, in order of decreasing RSSI for WLAN APs; > if BT-NameList is included in VarLogMeasConfig:

4> if detailed Bluetooth measurements are available:

5> include logMeasResultListBT, in order of decreasing RSSI for Bluetooth beacons; > if Sensor-NameList is included in VarLogMeasConfig:

4> if detailed Sensor measurements are available:

5> include Sensor-LocationInfo-rl6 for sensors; > if the UE is in any cell selection state (as specified in TS 38.304

[20]):

4> set anyCellSelectionDetected to indicate the detection of no suitable or no acceptable cell found;

4> set the servCellldentity to indicate global cell identity of the last logged cell that the UE was camping on;

4> set the measResultServCell to include the quantities of the last logged cell the UE was camping on; > else:

4> set the servCellldentity to indicate global cell identity of the cell the UE is camping on;

4> set the measResultServCell to include the quantities of the cell the UE is camping on; 4> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements (excluding the resultsSSB-Indexes IE) that became available during the last logging interval for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter -RAT neighbours, per frequency/ set of frequencies per RAT and according to the following:

5> for each neighbour cell included, include the optional fields that are available;

4> for the cells included according to the previous (i.e. covering previous and current serving cells as well as neighbouring NR cells) include results according to the extended RSRQ if corresponding results are available according to the associated performance requirements defined in TS 38.133 [14];

NOTE: The UE includes the latest results of the available measurements as used for cell reselection evaluation in RRC IDLE or RRC INACTIVE or as used for evaluation of reporting criteria or for measurement reporting according to 5.5.3 in RRC CONNECTED, which are performed in accordance with the performance requirements as specified in TS 38.133 [14]

2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in 5.5a.1.4.

[0029] Radio Resource Management (RRM) measurement relaxation is discussed below.

[0030] Already as part of 3GPP Rel-15, there are means for a UE in states RRC IDLE and RRC INACTIVE to relax neighbour cell measurements in certain conditions. These relaxation criteria (note that in Rel-15 the terminology relaxation is not used) are based on thresholds (SlntraSearchP, SlntraSearcliQ, SnonlntraSearchP, SnonlntraSearcliQ) that may be Configured by the

NW via broadcast parameters in system information (System Information Block 2). Such thresholds can separately be configured for intra frequency and non-intra frequency. The relaxation criteria which the UE evaluates is outlined below:

If (Srxiev > SintraSearchP and S _quai > SlntraSeardiQ) , the UE is not required to perform intra frequency neighbour RRM measurements

If (Srxiev > SnonlntraSearchP and Squai > SnonlntraSearcliQ), the UE IS not required tO perform

RRM measurements on inter-frequency/RAT cells of equal/lower priority;

Where:

S _rxiev is cell selection RX level value (dB) , simply described a relative measure of

RSRP compared to a minimum threshold

S _quai is a cell selection quality value (dB) , simply described a relative measure of

RSRQ compared to a minimum threshold

[0031] In 3GPP Rel-16, additional RRM relaxation criteria is introduced for UEs in states RRC IDLE and RRC IN ACTIVE. Similar to Rel-15, these criteria are based on serving cell quality. These conditions can be configured by the NW via broadcast configuration. Two main RRM relaxation criteria are defined for detecting scenarios in which:

• UEs are not at cell edge: o This criterion is quite similar to Rel-15 threshold-based criteria described earlier. New thresholds (SsearchThreshoidP, SsearchThreshoidQ) are introduced in SIB2 (System Information Block 2) helping the UE understand whether it is on cell edge. The relaxation criteria which the UE evaluates is outlined below

^■ If (Srxiev S SearchThresholdP and Squai S SearcliThreslioldQ) , the UE may relax

RRM measurements on intra-frequency and inter-frequency/RAT cells of equal/lower priority neighbors.

• UEs are in low mobility: o The low-mobility criterion is built on top of LTE’s MTC (CAT-M, NB-IoT) RRM relaxation criteria with some tweaks suitable for NR eMBB (enhanced Mobile Broadband) UEs. In general, the idea is that the UE tracks variations in serving cell’s RSRP (Reference Signal Received Power) measurement compared to a reference point and detect high mobility when the RSRP drops more than a relative threshold during a time period. The UE is assumed to be in low mobility otherwise in which case the UE may relax RRM measurements on intra frequency and inter-frequency /RAT cells of equal/lower priority neighbors.

In addition, the NW can configure the UE via a configuration parameter highPriorityMeasRelax whether relaxed RRM measurement on higher priority frequency is allowed or not (in case the relaxed measurement criteria is fulfilled).

[0032] Figure 3 illustrates 3GPP Rel-16 RRM relaxation criteria.

[0033] Similar to Rel-15, these criteria can be optionally configured via broadcast system information (SIB2). These criteria can be configured irrespective of/unconditional to the Rel-15 configurations. Furthermore, the Rel-16 conditions can be configured separately and either standalone or in combination, as shown in Figures 4A, 4B, 4C, and 4D by the four configuration options for Rel-16 relaxation criteria.

SUMMARY

[0034] If a UE uses relaxed RRM measurements for MDT logging, a resulting MDT report may be transmitted with incomplete information, and a receiving network node may misinterpret this incomplete information as resulting in a coverage hole.

[0035] According to some embodiments of inventive concepts, a method is provided to operate a communication device in a network. Radio Resource Management, RRM, measurements are performed according to an RRM configuration. The RRM measurements are stored in a Minimization of Drive Test MDT log for an MDT logging occasion according to an MDT configuration. An indication of a status of the RRM measurements as being performed using relaxed RRM measurements or normal RRM measurements is stored in MDT log for the MDT logging occasion.

[0036] Storing an indication of a status of the RRM measurements as being performed using relaxed RRM or normal RRM in the MDT log for the MDT logging occasion enables the communication device to include the status of the RRM measurements as being performed using relaxed or normal RRM measurements when reporting the RRM measurements in an MDT report to the network. By including the status of the RRM measurements as being performed using relaxed or normal RRM measurements in the MDT report, the receiving network node can better interpret/use the information of the MDT report. [0037] According to some embodiments, a method is provided to operate a node of a communication network. An MDT report is received from a communication device while the communication device is in a connected state. The MDT report includes Radio Resource Management, RRM, measurements and an indication of a status of the RRM measurements as being performed using relaxed RRM measurements or normal RRM measurements.

[0038] According to some embodiments of inventive concepts, a method is provided to operate a communication device in a network. A Radio Resource Management, RRM, configuration is received from the network, with the RRM configuration including configuration for relaxed RRM measurements. A Minimization of Drive Test, MDT, configuration is received from the network, with the MDT configuration including an indication to allow use of relaxed RRM measurements for MDT logging. Relaxed RRM measurements are performed according to the RRM configuration including configuration for relaxed RRM measurements. The relaxed RRM measurements are stored in an MDT log for an MDT logging occasion according to the MDT configuration.

[0039] According to some embodiments, relaxed RRM measurements may be allowed by the network for MDT logging so that the network can control use of such relaxed RRM measurements.

[0040] According to some embodiments of inventive concepts, a method is provided to operate a communication device in a network. A Radio Resource Management, RRM, configuration is received from the network, with the RRM configuration including configuration for relaxed RRM measurements. A Minimization of Drive Test, MDT, configuration is received from the network, with the MDT configuration including an indication to allow use of only relaxed RRM measurements for MDT logging. Relaxed RRM measurements are performed according to the RRM configuration including configuration for relaxed RRM measurements.

The relaxed RRM measurements are stored in an MDT log for an MDT logging occasion according to the MDT configuration.

[0041] According to some embodiments, by allow use of only RRM measurements for MDT logging, the network can use the resulting information to tune RRM thresholds.

[0042] According to some embodiments of inventive concepts, a method is provided to operate a communication device in a network. A Radio Resource Management, RRM, configuration is received from the network, with the RRM configuration including configuration for relaxed RRM measurements. A Minimization of Drive Test, MDT, configuration is received from the network, with the MDT configuration including an indication to require use of normal RRM measurements during MDT logging. A determination is made that a criteria for relaxed RRM measurements is satisfied according to the RRM configuration during an MDT logging interval according to the MDT configuration. Normal RRM measurements may be performed during the MDT logging interval according to the MDT configuration including the indication to require use of normal RRM measurements during MDT logging. The normal RRM measurements are stored in an MDT log for an MDT logging occasion according to the MDT configuration. An indication that the criteria for relaxed RRM measurements was satisfied during the MDT logging interval is stored in the MDT log for the MDT logging occasion.

[0043] According to some embodiments, the MDT configuration can override relaxed RRM measurements during MDT logging intervals so that only normal RRM measurements are included in MDT logging.

[0044] According to some embodiments of inventive concepts, a method is provided to operate a communication device in a network. A Radio Resource Management, RRM, configuration is received via broadcast signaling, with the RRM configuration including configuration for relaxed RRM measurements. A Minimization of Drive Test, MDT, configuration is received via dedicated signaling, with the MDT configuration including an indication to allow use of relaxed RRM measurements for MDT logging. Relaxed RRM measurements are performed according to an RRM configuration. The relaxed RRM measurements are stored in an MDT log for an MDT logging occasion according to an MDT configuration.

[0045] According to some embodiments, by logging relaxed RRM measurements, the network can use the information relating to relaxed RRM measurements to tune RRM thresholds.

BRIEF DESCRIPTION OF THE DRAWINGS [0046] 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:

[0047] Figure 1 is a timing diagram illustrating MDT logging; [0048] Figure 2 is a message diagram illustrating logged measurement configuration;

[0049] Figure 3 is a diagram illustrating 3 GPP Rel-16 RRM relaxation criteria;

[0050] Figures 4A, 4B, 4C, and 4D are diagrams illustrating configuration options for Rel-16 relaxation criteria;

[0051] Figure 5 is a flow diagram illustrating UE operations according to some embodiments of inventive concepts;

[0052] Figures 6, 7, and 8 are flow diagrams illustrating UE operations according to some embodiments of inventive concepts;

[0053] Figure 9 is a block diagram illustrating a wireless device UE according to some embodiments of inventive concepts;

[0054] Figure 10 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;

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

[0056] Figures 12A, 12B, 13, 14A, 14B, 15, and 16 are flow charts illustrating operations of communication devices according to some embodiments of inventive concepts;

[0057] Figures 17A, 17B, and 17C are flow charts illustrating operations of nodes of a communication network according to some embodiments of inventive concepts;

[0058] Figure 18 is a block diagram of a wireless network in accordance with some embodiments;

[0059] Figure 19 is a block diagram of a user equipment in accordance with some embodiments

[0060] Figure 20 is a block diagram of a virtualization environment in accordance with some embodiments;

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

[0062] Figure 22 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; [0063] Figure 23 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;

[0064] Figure 24 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;

[0065] Figure 25 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

[0066] Figure 26 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

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

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

[0069] Figure 9 is a block diagram illustrating elements of a communication device UE 900 (also referred to as a mobile terminal, a mobile communication terminal, a wireless device, 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. (Communication device 900 may be provided, for example, as discussed below with respect to wireless device 4110 of Figure 18.) As shown, communication device UE may include an antenna 907 (e.g., corresponding to antenna 4111 of Figure 18), and transceiver circuitry 901 (also referred to as a transceiver, e.g., corresponding to interface 4114 of Figure 18) 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 4160 of Figure 18, also referred to as a RAN node) of a radio access network. Communication device UE may also include processing circuitry 903 (also referred to as a processor, e.g., corresponding to processing circuitry 4120 of Figure 18) coupled to the transceiver circuitry, and memory circuitry 905 (also referred to as memory, e.g., corresponding to device readable medium 4130 of Figure 18) 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. Communication device UE may also include an interface (such as a user interface) coupled with processing circuitry 903, and/or communication device UE may be incorporated in a vehicle.

[0070] As discussed herein, operations of communication 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 communication devices).

[0071] Figure 10 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 4160 of Figure 18.) As shown, the RAN node may include transceiver circuitry 1001 (also referred to as a transceiver, e.g., corresponding to portions of interface 4190 of Figure 18) 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 4190 of Figure 18) 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 403 (also referred to as a processor, e.g., corresponding to processing circuitry 4170) coupled to the transceiver circuitry, and memory circuitry 1005 (also referred to as memory, e.g., corresponding to device readable medium 4180 of Figure 18) coupled to the processing circuitry. The memory circuitry 1005 may include computer readable program code that when executed by the processing circuitry 403 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 403 may be defined to include memory so that a separate memory circuitry is not required.

[0072] As discussed herein, operations of the RAN node may be performed by processing circuitry 403, network interface 1007, and/or transceiver 1001. For example, processing circuitry 403 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).

[0073] 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 communication device UE may be initiated by the network node so that transmission to the wireless communication device UE 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.

[0074] Figure 11 is a block diagram illustrating elements of a core network CN node (e.g., an SMF node, an AMF 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.

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

[0076] When the UE is configured with logged MDT, it performs measurements while being in idle/inactive state and reports the measurements to the network. The network uses these measurements for coverage analysis of different cells that the UE has logged in the logged MDT report. Typically, a subset of UEs are configured to report logged MDT, which e.g. enable the operator to evaluate NW performance i.e. Idle mobility, when the network deployment is changed (e.g. new cell is added), or when cell re-selection parameters are changed (e.g. network configurations tuning). When a specific UE has reported problems, it is also possible to configure that particular UE with logged MDT analyze (signaling-based MDT).

[0077] If the network broadcasts the relaxed RRM measurements’ related configuration, then the idle/inactive UEs are allowed to perform relaxed RRM measurements to save the battery. The UE uses the relaxed measurement parameters in system information to determine if the relaxed monitoring criterion is met, allowing the UE to apply relaxed RRM measurements. The relaxed RRM measurement allow the UE to reduce measure intra frequency and/or inter-frequency /RAT neighbor cell measurements. The RRM relaxation may allow the UE to measure less often, or not at all, during the period that the relaxation criterion is met. The RRM relaxation may also allow the UE to measure less frequencies simultaneously.

[0078] However, when the UE is configured with logged MDT and if the cell in which the UE is camping broadcasts relaxed RRM related configurations, then the UE might perform relaxed RRM measurements thus resulting in less information about the neighboring intra and inter frequency /RAT cells. As the OAM is not aware of the fact that this UE is using relaxed RRM measurements, the OAM might think that there is no coverage from the neighboring intra/inter frequency /RAT cells in that location which is wrong.

[0079] Another problem is related to tuning of relaxed measurement configuration parameters and NW knowledge about usage of the feature. The actual relaxation within UE is transparent to NW, i.e. the NW does not know whether its broadcast configuration of relaxed monitoring parameters actually result in any UE relaxing its measurements and if so for how long time. Furthermore, the NW does not know whether its configuration may lead to out of coverage in UEs as a result of relaxed measurements or reduced idle mode mobility performance, i.e. the UE is not camped on the strongest cell all the time.

[0080] According to some embodiments of inventive concepts, a method includes an indication in the logged MDT report as to whether the UE was using relaxed RRM measurements or normal RRM measurements at the time of logging the measurements for logged MDT purposes.

[0081] According to some embodiments of inventive concepts, a method is provided wherein the network (OAM/RAN node/Core) can control whether the UE can use relaxed RRM measurements or not while being configured with logged MDT procedure. In case relaxed RRM measurements are allowed during MDT, the NW can control which/combination of the relaxation criteria (Rel-15, Rel-16 Low-Mobility, Rel-16 UE-Not- At-Cell-Edge) shall be allowed. This way the NW can (re-)tune configuration of each criteria based on gathered results. Furthermore, via such filtering, the NW can disallow certain risky criteria, e.g. while at cell edge the NW might not want the UE to perform relaxation during MDT.

[0082] According to some embodiments of inventive concepts, a method is provided such that a UE only carries out MDT measurement logging when the UE is actually experiencing RRM relaxations. This way the NW can carry out targeted MDT measurements rather than having to gather MDT results from all UEs and checking whether any of them have been in relaxed RRM mode.

[0083] For the UEs entering and being in relaxed RRM mode, the Network NW can configure those UEs to perform normal RRM measurements. However, these UEs indicate in their report that the measurement results belong to the time period in which the UE would have relaxed its measurement otherwise. This way the NW can see what the UEs miss out on with respect to neighbor cell measurement if they would have relaxed their measurements.

[0084] By using the methods according to some embodiments, the Operations and Management OAM node/system can build the coverage map associated with normal RRM measurements and relaxed RRM measurements independently.

[0085] According to some embodiments, the NW may be able to disallow certain sub criteria of relaxed RRM if the NW doesn’t see it as suitable; e.g. a UE at cell edge is not allowed to relax RRM while performing MDT whereas a UE close to the gNB (e.g. as per Rel- 15 relaxation criteria) is allowed to relax.

[0086] Some embodiments of inventive concepts may facilitate tuning of RRM relaxation for various criteria through targeted MDT results from specific UEs experiencing certain criteria fulfillment.

[0087] According to some embodiments illustrated in the flow diagram of Figure 5, related to the MDT reporting, the UE includes an indication for each sample associated with the logged MDT. Referring to the example of Figure 5, the UE receives 501 a logged MDT configuration. The UE, at each logging of a sample in logged MDT report, includes 502 an indicator to indicate whether the UE is using relaxed RRM measurements or normal RRM.

The UE then transitions 503 to RRC connected and reports the stored logged MDT report. An example ASN.1 implementation of this in the RRC specification is illustrated in Table 2 below. As shown a relaxedRRMMeasurementsUsed flag/field may be used to indicate whether a logged MDT measurement/sample was obtained based on a regular RRM Measurement or based on a relaxed RRM Measurement.

Table 2 [0088] In some sub-embodiments of Figure 5, especially when the NW aims to configure several of the criteria outlined above with respect to Radio Resource Management (RRM) measurement relaxation, further details may be included in the reported results from the UE with respect to which of the Relaxed RRM Criteria was fulfilled during RRM. An example ASN.1 implementation is illustrated in Table 3 below, which includes the additional fields/flags: lowMobilityFulfilled, notAtCellEdgeFulfilled, and rel-15CriteriaFulfilled.

Table 3

[0089] In some sub-embodiments, the UE may also provide all or parts of the relaxed RRM measurements’ related configuration (e.g., SsearchDeitaP, TsearchDeitaP, SsearchThreshoidP, Ss _{earciiThreshoidQ} , relaxedMeasCondition, highPriorityMeasRelax) as provided by the camped cell (also referred to as the serving cell). These terms are defined below:

[0090] SintraSearchQ - This specifies the Squal threshold (in dB) for intra-frequency measurements. [0091] SnonintraSearchP - This specifies the Srxlev threshold (in dB) for NR inter frequency and inter-RAT measurements.

[0092] SnonintraSearchQ - This specifies the Squal threshold (in dB) for NR inter frequency and inter-RAT measurements.

[0093] SsearchDeitaP - This specifies the threshold (in dB) on Srxlev variation for relaxed measurement.

[0094] Ss _{earchThreshoidP} - This specifies the Srxlev threshold (in dB) for relaxed measurement.

[0095] Ss _{ear iThreshoidQ} - This specifies the Squal threshold (in dB) for relaxed measurement.

[0096] T s _earchDeitaP - This specifies the time period over which the Srxlev variation is evaluated for relaxed measurement.

[0097] highPriorityMeasRelax - This indicates whether relaxed measurement on higher priority frequency is allowed or not (in case the relaxed measurement criteria is fulfilled).

[0098] In some embodiments, the UE may also provide an indication related to whether the relaxed RRM measurements were configured by the camped cell, but the associated conditions are not fulfilled. In such an embodiment, relaxedRRMMEasurementsUsed is set when the UE camps in/on a cell which is broadcasting the usage of relaxed RRM measurements and the UE sets another flag, e.g. relaxedRRMMEasurementsConditionFulfilled when the conditions as configured for relaxed RRM measurements are satisfied. Similarly, as per the second ASN.1 implementation example of Table 3, the UE may include a finer granular version of the relaxedRRMMEasurementsUsed including information about which of the criteria was configured/used and according to what configuration combination, as shown in Table 4 below. In Table 4, the UE may provide the fields/flags: lowMobilityOrNotAtCellEdge, lowMobilityAndNotAtCellEdge, highPriorityMeasRelax, and/or rel-15Criteria.

Table 4 _

[0099] Figure 6 is a flow diagram illustrating UE operations according to some embodiment. According to some embodiments of Figure 6, the MDT configuration as received from the network has an indicator to control whether the UE can use the relaxed RRM measurements or not when the UE is performing the logging of measurements associated to logged MDT (i.e., until the timer T330 is running). Referring to the example of Figure 6, the UE receives 600 the logged MDT configuration that includes an indication as to whether the UE is allowed to use relaxed RRM measurements or not while performing logging of measurements in a logged MDT report. If a condition 601 is satisfied that the UE is configured not to use relaxed RRM measurements, then the UE performs normal RRM measurements in idle or inactive state and performs logging of measurements in logged MDT. In contrast if another condition 602 is satisfied that the UE is configured to use relaxed RRM measurements and the camped cell broadcasts relaxed RRM measurements related configuration, then the UE performs relaxed RRM measurements in idle or inactive state and performs logging of measurements in logged MDT. In contrast if another condition 603 is satisfied that the UE is configured to use relaxed RRM measurements and the camped cell does not broadcast relaxed RRM measurements related configuration, then the UE performs normal RRM measurements in idle or inactive state and performs logging of measurements in logged MDT. Following any of operations 601-603, the UE can transition 604 to RRC connected and report the stored logged report.

[0100] In a sub-embodiment of Figure 6, the control from the NW of whether the UE may use relaxed RRM measurements or not has finer granularity. I.e. the NW may want to control whether the UE, while performing MDT, is allowed to relax its RRM measurements according to one, or combination of criteria outlined earlier. E.g. the NW might want to allow the UE to relax its RRM measurement when not-at-cell-edge and/or according to Rel-15 criteria but not otherwise.

[0101] The network entity to control this configuration could be OAM or core network node or the RAN node. [0102] Figure 7 is another flow diagram illustrating UE operations according to some embodiments in which embodiments of Figures 5 and 6 may be combined. Referring to the example of Figure 7, a UE receives 700 the logged MDT configuration that includes an indication as to whether the UE is allowed to use relaxed RRM measurements or not while performing logging of measurements in a logged MDT report. If a condition 701 is satisfied that the UE is configured not to use relaxed RRM measurements, then the UE performs normal RRM measurements in idle or inactive state and performs logging of measurements in logged MDT.

In contrast if another condition 702 is satisfied that the UE is configured to use relaxed RRM measurements and the camped cell broadcasts relaxed RRM measurements related configuration, then the UE performs relaxed RRM measurements in idle or inactive state and performs logging of measurements in logged MDT and includes an indication that the current sample is associated to related RRM measurements. In contrast if another condition 703 is satisfied that the UE is configured to use relaxed RRM measurements and the camped cell does not broadcast relaxed RRM measurements related configuration, then the UE performs normal RRM measurements in idle or inactive state and performs logging of measurements in logged MDT. Following any of operations 701-703, the UE can transition 704 to RRC connected and report the stored logged report.

[0103] Figure 8 is another flow diagram illustrating UE operations according to some embodiments where the NW may want to gather logged MDT from a UE only when the UE actually spends time in Relaxed RRM measurement mode. Similar to embodiments discussed above, the NW may further want to have specific relaxation criterion or combinations thereof to be applicable in this case. As such, the NW may be interesting in gathering logged MDT from a UE at the point the UE enters a certain relaxation criterion (or criteria combination), continue while the criteria are fulfilled until and including the point in time when the UE exits the RRM relaxations. This way the NW can get information about surrounding neighbors at the point of entering and exiting the relaxed RRM mode. Referring to the example of Figure 8, the UE receives 800 a logged MDT configuration that includes an indication as to whether the UE shall perform logging of MDT measurements or not while entering, being in, or exiting relaxed RRM measurements mode. If a condition 801 is satisfied that the UE is configured not to perform MDT logging when entering, being in, or exiting relaxed RRM measurements mode, then the UE does not perform MDT logging while performing normal RRM measurements in idle or inactive state. In contrast if another condition 802 is satisfied that the UE is configured to perform MDT logging when entering, being in, or exiting relaxed RRM measurements mode, then the UE performs MDT logging while entering, being in, or exiting relaxed RRM measurements mode in idle or inactive state. Following any of operations 801-802, the UE can transition 803 to RRC connected and report the stored logged report.

[0104] As an example, this aspect may be implemented through introduction of new event Triggered logged MDT configuration in which case the event types may be extended to include relaxed RRM criteria as illustrated in Table 5 below. As shown, the configuration may specify logged MDT configuration in the event of Relaxed RRM resulting from one or more of: lowMobilityEnterExit; notAtCellEdgeEnterExit; lowMobilityOrNotAtCellEdgeEnterExit; lowMobilityAndNotAtCellEdgeEnterExit; and/or rel- 15CriteriaEnterExit.

Table 5 [0105] Note that in some aspects, the outOfCoverage and eventRelaxedRRM can be combined rather than the example illustrated in Table 5 (i.e. instead of CHOICE, combination may be allowed). This means that the two events may co-exist and triggering of any of them triggers start of MDT logging procedure in the UE.

[0106] In all of the embodiments mentioned above, it shall also be possible to configure the UE to not actually relax its RRM measurements, but still track the relaxed measurement criteria and report the time (e.g. time stamps) during which they entered/exited an RRM relaxation mode or sub-mode, e.g. (related to sub-mode), if multiple criteria are configured, the UE time tracks each criteria separately such as low-mobility fulfilled at time X, not-at-cell-edge fulfilled at time Y. This way the NW can observe and get input to (re-)tuning of configuration parameters related to RRM relaxations based on what the UE would have experienced (or missed out on) with respect to e.g. neighbor cell RRM measurements if it would have relaxed its RRM measurements otherwise.

[0107] Some embodiments of inventive concepts may provide extension of NW configuration of MDT, and UE MDT measurements and reporting of MDT to the NW to handle Relaxed RRM measurements in the UE. Some embodiments of inventive concepts are discussed below:

• A method which includes an indication in the logged MDT as to whether the UE was using relaxed RRM measurements or normal RRM measurements at the time of logging the measurements for logged MDT purposes. o Further sub aspects related to this include the granularity of the indication, providing information to the NW about which of the RRM relaxation criteria was fulfilled.

• A method wherein the network (O AM/RAN node/Core) can control whether the UE can use relaxed RRM measurements or not while being configured with logged MDT procedure. o Further, in case relaxed RRM measurements are allowed during MDT, the NW can control which/combination of the relaxation criteria (Rel-15, Rel-16 Low- Mobility, Rel-16 UE-Not-At-Cell-Edge) shall be allowed. o Furthermore, via such filtering, the NW can disallow certain risky criteria, e.g. while at cell edge the NW might not want the UE to perform relaxation during MDT. o In a sub-embodiment, even though the UEs do not relax their RRM measurements, they still track the relaxed measurement criteria and report the time (e.g. time stamps) of entering/exiting the condition when criteria are fulfilled. This way the NW can see what the UE would have experienced (or misses out on) with respect to e.g. neighbor cell RRM measurements if it would have relaxed its RRM measurements otherwise.

• A method for which a UE only carries out MDT measurements when experiencing

RRM relaxations. o In one aspect, this method may be implemented by extending the event triggered logged MDT with Relaxed RRM events that may or may not be combined with existing events specified for MDT logging.

[0108] Operations of the communication device 900 (implemented using the structure of the block diagram of Figure 9) will now be discussed with reference to the flow chart of Figures 12A and 12B according to some embodiments of inventive concepts. For example, modules may be stored in memory 905 of Figure 9, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 903, processing circuitry 903 performs respective operations of the flow chart.

[0109] At block 1705, processing circuitry 903 receives (through transceiver 901) a Radio Resource Management RRM configuration via broadcast signaling, with the RRM configuration including configuration for relaxed RRM measurements.

[0110] At block 1709, processing circuitry 903 receives (through transceiver 901) an MDT configuration via dedicated signaling, with the MDT configuration including an indication to allow use of relaxed RRM measurements for MDT logging.

[0111] At block 1711, processing circuitry 1711 performs RRM measurements according to the RRM configuration of block 1705. RRM measurements of block 1711 may be performed when the communication device 900 is in an idle state or in an inactive state (e.g., a Radio Resource Control, RRC, idle state or an RRC inactive state). Operations of block 1711 are illustrated in greater detail in Figure 12B according to some embodiments of inventive concepts. At each occurrence of RRM measurements, processing circuitry 903 determines at block 1791 whether the RRM measurements are to be performed as relaxed RRM measurements or as normal RRM measurements. When relaxed RRM measurements are to be performed at block 1791, processing circuitry 903 performs relaxed RRM measurements at block 1793 for the occurrence of RRM measurements in accordance with the RRM configuration. When normal RRM measurements are to be performed at block 1791, processing circuitry 903 performs normal RRM measurements at block 1795 for the occurrence of RRM measurements in accordance with the RRM configuration.

[0112] At block 1715, processing circuitry 903 determines whether an MDT measurement occasion has been triggered according to the MDT configuration as discussed above with respect to Figure 1. If not, processing circuitry 903 determines at block 1775 whether a transition to connected state has been triggered, and if not, processing circuitry 903 proceeds with next RRM measurements at block 1711.

[0113] When an MDT measurement occasion is triggered according to the MDT configuration at block 1715, processing circuitry 903 determines at block 1719 whether a most recent RRM measurements from block 1711 was relaxed or normal.

[0114] When the most recent RRM measurements from blocks 1711 and 1793 were performed as relaxed RRM measurements according to the RRM configuration, processing circuitry 903 stores the relaxed RRM measurements in an MDT log (e.g., in memory 905) for the MDT logging occasion according to the MDT configuration at block 1725, and processing circuitry 903 stores an indication of a status of the relaxed RRM measurements being performed as/using relaxed RRM measurements. According to some embodiments for relaxed RRM measurements, the indication of the status of the RRM measurements may also include an indication that the RRM measurements were performed as/using relaxed RRM measurements due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold. According to some embodiments for relaxed RRM measurements, the indication of the status of the RRM measurements may also include information of the RRM configuration relating to the relaxed RRM measurements. [0115] When the most recent RRM measurements from blocks 1711 and 1795 were performed as normal RRM measurements according to the RRM configuration, processing circuitry 903 stores the normal RRM measurements in the MDT log (e.g., in memory 905) for the MDT logging occasion according to the MDT configuration at block 1755, and processing circuitry 903 stores an indication of a status of the relaxed RRM measurements being performed as/using normal RRM measurements. According to some embodiments for normal RRM measurements, the indication of the status of the RRM measurements may include an indication that relaxed RRM measurements have been configured.

[0116] Processing circuitry 903 may perform operations of blocks 1711, 1715, 1719, 1725, 1729, 1755, and/or 1759 repeatedly until a transition to connected state (e.g., RRC connected state) is triggered at block 1775. Responsive to such a trigger, processing circuitry 903 transitions to a connected state (e.g., an RRC connected state) at block 1785. At block 1789 while in the connected state, processing circuitry 903 may transmit (through transceiver 901) an MDT report to the network (e.g., responsive to a request from the network). The MDT report includes the RRM measurements from blocks 1725 and/or 1755 and the indications of status of blocks 1729 and/or 1759 from the MDT log.

[0117] Various operations from the flow charts of Figures 12A and 12B may be optional with respect to some embodiments of communication devices and related methods. Regarding methods of example embodiment 1 (set forth below), for example, operations of some or all of blocks 1705, 1709, 1715, 1719, 1725, 1729, 1755, 1759, 1775, 1785, and/or 1789 of Figures 12A and/or 12B may be optional.

[0118] Operations of the communication device 900 (implemented using the structure of the block diagram of Figure 9) will now be discussed with reference to the flow chart of Figure 13 according to some embodiments of inventive concepts. For example, modules may be stored in memory 905 of Figure 9, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 903, processing circuitry 903 performs respective operations of the flow chart.

[0119] At block 1805, processing circuitry 903 receives (through transceiver 901) a Radio Resource Management RRM configuration from the network (e.g., via broadcast signaling), with the RRM configuration including configuration for relaxed RRM measurements. [0120] At block 1809, processing circuitry 903 receives (through transceiver 901) a Minimization of Drive Test MDT configuration from the network (e.g., via dedicated signaling), with the MDT configuration including an indication to allow use of relaxed RRM measurements for MDT logging. According to some embodiments, the indication to allow use of relaxed RRM measurements for MDT logging may include an indication to use relaxed RRM measurements for MDT logging due at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold, without allowing use of relaxed RRM measurements for MDT logging due to at least another one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold. According to such an MDT configuration, RRM measurements resulting from some condition/conditions may be used for MDT logging while RRM measurements resulting from some other condition/conditions may not be used for MDT logging.

[0121] At block 1811, processing circuitry 903 performs relaxed RRM measurements according to the RRM configuration including configuration for relaxed RRM measurements. According to some embodiments, the communication device is in an idle state or an inactive state (e.g., a Radio Resource Control RRC idle state or an RRC inactive) state when performing the relaxed RRM measurements.

[0122] At block 1825, processing circuitry 903 stores the relaxed RRM measurements in an MDT log (e.g., in memory 905) for an MDT logging occasion according to the MDT configuration.

[0123] At block 1829, processing circuitry 903 stores in the MDT log (e.g., in memory 905) for the MDT logging occasion an indication of a status of the relaxed RRM measurements as being performed using relaxed RRM measurements. According to some embodiments, the indication of the status of the relaxed RRM measurements may also include an indication that the relaxed RRM measurements were performed due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold. [0124] At block 1885, processing circuitry 903 may transition to a connected state (e.g., an RRC connected state) after performing the relaxed RRM measurements.

[0125] At block 1889, processing circuitry 903 may transmit (through transceiver 901) an MDT report to the network while in the connected state, with the MDT report including the MDT log with the relaxed RRM measurements.

[0126] Various operations from the flow chart of Figure 13 may be optional with respect to some embodiments of communication devices and related methods. Regarding methods of example embodiment 11 (set forth below), for example, operations of blocks 1829, 1875, and/or 1889 of Figure 13 may be optional.

[0127] Operations of the communication device 900 (implemented using the structure of the block diagram of Figure 9) will now be discussed with reference to the flow chart of Figures 14A and 14B according to some embodiments of inventive concepts. For example, modules may be stored in memory 905 of Figure 9, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 903, processing circuitry 903 performs respective operations of the flow chart.

[0128] At block 1905, processing circuitry 903 receives (through transceiver 901) a Radio Resource Management RRM configuration from the network (e.g., via broadcast signaling), with the RRM configuration including configuration for relaxed RRM measurements.

[0129] At block 1909, processing circuitry 903 receives (through transceiver 901) a Minimization of Drive Test MDT configuration from the network (e.g., via dedicated signaling), with the MDT configuration including an indication to allow use of only relaxed RRM measurements for MDT logging. According to some embodiments, the indication to allow use of only relaxed RRM measurements may include an indication to allow use of only relaxed RRM measurements due to one or more of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

[0130] At block 1911, processing circuitry 903 performs RRM measurements according to the RRM configuration of block 1905. RRM measurements of block 1911 may be performed when the communication device is in an idle state or an inactive state (e.g., a Radio Resource Control RRC idle state or an RRC inactive state). Operations of block 1911 are illustrated in greater detail in Figure 14B according to some embodiments of inventive concepts.

[0131] At each occurrence of RRM measurements, processing circuitry 903 determines at block 1991 whether the RRM measurements are to be performed as relaxed RRM measurements or as normal RRM measurements. When relaxed RRM measurements are to be performed at block 1991, processing circuitry 903 performs relaxed RRM measurements at block 1993 for the occurrence of RRM measurements in accordance with the RRM configuration.

When normal RRM measurements are to be performed at block 1991, processing circuitry 903 performs normal RRM measurements at block 1995 for the occurrence of RRM measurements in accordance with the RRM configuration.

[0132] At block 1915, processing circuitry determines whether an MDT measurement occasion has been triggered according to the MDT configuration as discussed above with respect to Figure 1. If not, processing circuitry 903 determines at block 1975 whether a transition to connected state has been triggered, and if not, processing circuitry 903 proceeds with next RRM measurements at block 1911.

[0133] When an MDT measurement occasion is triggered according to the MDT configuration at block 1915, processing circuitry 903 determines at block 1919 whether a most recent RRM measurements from block 1911 was relaxed or normal.

[0134] When the most recent RRM measurements from blocks 1911 and 1993 were performed as relaxed RRM measurements according to the RRM configuration at block 1919, processing circuitry 903 stores the relaxed RRM measurements in an MDT log (e.g., in memory 905) for the MDT logging occasion according to the MDT configuration at block 1925, and at block 1929, processing circuitry 903 may store in the MDT log (e.g., in memory 905) for the MDT logging occasion an indication that the relaxed RRM measurements were performed due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

[0135] When the most recent RRM measurements from blocks 1911 and 1995 were performed as normal RRM measurements according to the RRM configuration at block 1919, processing circuitry 903 performs normal RRM measurement of blocks 1911 and 1995 according to the RRM configuration without storing the normal RRM measurements in the MDT log based on the MDT configuration including the indication to allow use of only relaxed RRM measurements for MDT logging.

[0136] Processing circuitry 903 may perform operations of blocks 1911, 1915, 1919, 1925, and/or 1929, 1755 repeatedly until a transition to connected state (e.g., RRC connected state) is triggered at block 1975. Responsive to such a trigger, processing circuitry 903 transitions to a connected state (e.g., an RRC connected state) at block 1985. At block 1989 while in the connected state, processing circuitry 903 may transmit (through transceiver 901) an MDT report to the network (e.g., responsive to a request from the network). The MDT report may include the MDT log with the relaxed RRM measurements from block 1925 and the indication that-the relaxed RRM measurements were performed due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

[0137] Various operations from the flow charts of Figures 14A and 14B may be optional with respect to some embodiments of communication devices and related methods. Regarding methods of example embodiment 17 (set forth below), for example, operations of some or all of blocks 1915, 1919, 1975, 1985, 1989, 1991, 1993, and/or 1995 of Figures 14A and/or 14B may be optional.

[0138] Operations of the communication device 900 (implemented using the structure of the block diagram of Figure 9) will now be discussed with reference to the flow chart of Figure 15 according to some embodiments of inventive concepts. For example, modules may be stored in memory 905 of Figure 9, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 903, processing circuitry 903 performs respective operations of the flow chart.

[0139] At block 2005, processing circuitry 903 receives (through transceiver 901) a Radio Resource Management RRM configuration from the network (e.g., via broadcast signaling), with the RRM configuration including configuration for relaxed RRM measurements.

[0140] At block 2009, processing circuitry 903 receives (through transceiver 901) a Minimization of Drive Test MDT configuration from the network (e.g., via dedicated signaling), with the MDT configuration including an indication to require use of normal RRM measurements during MDT logging. [0141] At block 2015, processing circuitry 903 determines that a criteria for relaxed RRM measurements is satisfied according to the RRM configuration during an MDT logging interval according to the MDT configuration.

[0142] At block 2019, processing circuitry 903 performs normal RRM measurements during the MDT logging interval according to the MDT configuration including the indication to require use of normal RRM measurements during MDT logging. According to some embodiments, the communication device is in an idle state or an inactive state (e.g., a Radio Resource Control RRC idle state or an RRC inactive state) when performing the normal RRM measurements.

[0143] At block 2025, processing circuitry 903 stores the normal RRM measurements in an MDT log (e.g., in memory 905) for an MDT logging occasion according to the MDT configuration.

[0144] At block 2029, processing circuitry 903 stores in the MDT log (e.g., in memory 905) for the MDT logging occasion an indication that the criteria for relaxed RRM measurements was satisfied during the MDT logging interval. According to some embodiments, the indication that the criteria for relaxed RRM measurements was satisfied during the MDT logging interval may also include an indication that the criteria for relaxed RRM measurements was satisfied due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

[0145] At block 2085, processing circuitry 903 transitions to a connected state (e.g., an RRC connected state) after performing the normal RRM measurements.

[0146] At block 2089, processing circuitry 903 transmits (through transceiver 901) an MDT report to the network while in the connected state, with the MDT report including the normal RRM measurements and the indication that the criteria for relaxed RRM measurements was satisfied.

[0147] Various operations from the flow chart of Figure 15 may be optional with respect to some embodiments of communication devices and related methods. Regarding methods of example embodiment 23 (set forth below), for example, operations of blocks 2085 and/or 2089 of Figure 15 may be optional. [0148] Operations of the communication device 900 (implemented using the structure of the block diagram of Figure 9) will now be discussed with reference to the flow chart of Figure 16 according to some embodiments of inventive concepts. For example, modules may be stored in memory 905 of Figure 9, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 903, processing circuitry 903 performs respective operations of the flow chart.

[0149] At block 2105, processing circuitry 903 receives (through transceiver 901) a Radio Resource Management RRM configuration via broadcast signaling, with the RRM configuration including configuration for relaxed RRM measurements.

[0150] At block 2109, processing circuitry 903 receives (through transceiver 901) a Minimization of Drive Test MDT configuration via dedicated signaling, with the MDT configuration including an indication to allow use of relaxed RRM measurements for MDT logging.

[0151] At block 2111, processing circuitry 903 performs relaxed RRM measurements according to an RRM configuration.

[0152] At block 2125, processing circuitry 903 stores the relaxed RRM measurements in an MDT log (e.g., in memory 905) for an MDT logging occasion according to an MDT configuration.

[0153] At block 2129, processing circuitry stores in the MDT log (e.g., in memory 905) for the MDT logging occasion an indication of a status of the relaxed RRM measurements as being performed using relaxed RRM measurements.

[0154] At block 2185, processing circuitry 903 may transition to a connected state (e.g., an RRC connected state) after performing the relaxed RRM measurements.

[0155] At block 2189, processing circuitry 903 may transmit (through transceiver 901) an MDT report to the network while in the connected state, with the MDT report including the MDT log with the relaxed RRM measurements and the status of the relaxed RRM measurements as being performed using relaxed RRM measurements.

[0156] Various operations from the flow chart of Figure 16 may be optional with respect to some embodiments of communication devices and related methods. Regarding methods of example embodiment 27 (set forth below), for example, operations of blocks 2185 and/or 2189 of Figure 16 may be optional. [0157] Operations of a node 1000/1100 (implemented using the structure of Figure 10 or Figure 11) will now be discussed with reference to the flow charts of Figures 17A, 17B, and 17C according to some embodiments of inventive concepts. For example, modules may be stored in memory 1005/1105 of Figure(s) 10/11, and these modules may provide instructions so that when the instructions of a module are executed by respective processing circuitry 1003/1103, processing circuitry 1003/1103 performs respective operations of the flow chart.

[0158] According to some embodiments of Figures 17A, 17B, andl7C at block 2201, processing circuitry 1003/1103 receives (e.g., through transceiver 1001 and/or network interface 1107) an MDT report from a communication device (900) while the communication device (900) is in a connected state. The MDT report includes Radio Resource Management, RRM, measurements and an indication of a status of the RRM measurements as being performed using relaxed RRM measurements or normal RRM measurements.

[0159] According to some embodiments, the indication of the status of the RRM measurements may include an indication that the RRM measurements were performed as relaxed RRM measurements. For example, the indication of the status of the RRM measurements may further include an indication that the RRM measurements were performed using relaxed RRM measurements due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

[0160] According to some embodiments, the indication of the status of the RRM measurements may include an indication that the RRM measurements were performed as normal RRM measurements, and the indication of the status of the RRM measurements may include an indication that relaxed RRM measurements have been configured.

[0161] According to some embodiments of Figure 17A at block 2205a, processing circuitry 1003/1103 interprets information of the MDT report based on the indication of the status of the RRM measurements as being performed using relaxed RRM measurements or normal RRM measurements.

[0162] According to some embodiments of Figure 17B at block 2205b, processing circuitry 1003/1103 performs coverage analysis of different cells of the network based on the RRM measurements and the indication of the status of the RRM measurements. [0163] According to some embodiment of Figure 17C at block 2205c, processing circuitry 1003/1103 evaluates network performance based on the RRM measurements and the indication of the status of the RRM measurements.

[0164] Various operations from the flow charts of Figures 22A, 22B, and/or 22C may be optional with respect to some embodiments of nodes and related methods. Regarding methods of some embodiments, for example, operations of blocks 2205a, 2205b, and/or 2205c of Figures 22A, 22B, and/or 22C may be optional.

[0165] Example embodiments are discussed below.

1. A method of operating a communication device (900) in a network, the method comprising: performing (1711, 1793, 1795) Radio Resource Management, RRM, measurements according to an RRM configuration; storing (1725, 1755) the RRM measurements in a Minimization of Drive Test, MDT, log for an MDT logging occasion according to an MDT configuration; and storing (1729, 1759) in the MDT log for the MDT logging occasion an indication of a status of the RRM measurements as being performed using relaxed RRM measurements or normal RRM measurements.

2. The method of Embodiment 1 , wherein the RRM measurements are performed as relaxed RRM measurements according to the RRM configuration, and wherein the indication of the status of the RRM measurements comprises an indication that the RRM measurements were performed as relaxed RRM measurements.

3. The method of Embodiment 2, wherein the indication of the status of the RRM measurements further comprises an indication that the RRM measurements were performed using relaxed RRM measurements due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

4. The method of any of Embodiments 2-3, wherein the indication of the status of the RRM measurements further comprises information of the RRM configuration relating to the relaxed RRM measurements.

5. The method of Embodiment 1, wherein the RRM measurements are performed as normal RRM measurements according to the RRM configuration, and wherein the indication of the status of the RRM measurements comprises an indication that the RRM measurements were performed as normal RRM measurements.

6. The method of Embodiment 5, wherein the indication of the status of the RRM measurements comprises an indication that relaxed RRM measurements have been configured.

7. The method of any of Embodiments 1 -6, wherein the communication device is in an idle state or an inactive state (e.g., a Radio Resource Control, RRC, idle state or an RRC inactive state) when performing the RRM measurements, the method further comprising: after performing the RRM measurements, transitioning (1755) to a connected state (e.g., an RRC connected state); and transmitting (1789) an MDT report to the network while in the connected state, wherein the MDT report includes the RRM measurements and the indication of the status of the RRM measurements from the MDT log.

8. The method of Embodiment 1 , wherein the RRM measurements are first RRM measurements performed as relaxed RRM measurements, wherein the MDT logging occasion is a first MDT logging occasion, wherein the indication is an indication that the first RRM measurements were performed using relaxed RRM measurements, the method further comprising: performing (1711, 1795) second RRM measurements as normal RRM measurements according to the RRM configuration; storing (1755) the second RRM measurements in the MDT log for a second MDT logging occasion according to the MDT configuration; storing (1759) in the MDT log for the second MDT logging occasion a second indication of a status of the second RRM measurements as being normal RRM measurements; and transmitting (1789) an MDT report to the network, wherein the MDT report includes the MDT log with the first RRM measurements, the first indication, the second RRM measurements, and the second indication.

9. The method of any of Embodiments 1-8 further comprising: receiving (1705) the RRM configuration via broadcast signaling; and receiving (1709) the MDT configuration via dedicated signaling.

10. The method of Embodiment 1 further comprising: receiving (1705) the RRM configuration via broadcast signaling, wherein the RRM configuration includes configuration for relaxed RRM measurements; and receiving (1709) the MDT configuration via dedicated signaling, wherein the MDT configuration includes an indication to allow use of relaxed RRM measurements for MDT logging; wherein performing RRM measurements comprise performing relaxed RRM measurements according to the RRM configuration including configuration for relaxed RRM measurements; wherein storing the RRM measurements comprises storing the relaxed RRM measurements; and wherein storing the indication comprises storing in the MDT log for the MDT logging occasion an indication of a status of the RRM measurements as being performed using relaxed RRM measurements.

11. A method of operating a communication device (900) in a network, the method comprising: receiving (1805) a Radio Resource Management, RRM, configuration from the network, wherein the RRM configuration includes configuration for relaxed RRM measurements; receiving (1809) a Minimization of Drive Test, MDT, configuration from the network, wherein the MDT configuration includes an indication to allow use of relaxed RRM measurements for MDT logging; performing (1811) relaxed RRM measurements according to the RRM configuration including configuration for relaxed RRM measurements; and storing

(1825) the relaxed RRM measurements in an MDT log for an MDT logging occasion according to the MDT configuration.

12. The method of Claim 11 further comprising: storing (1829) in the MDT log for the MDT logging occasion an indication of a status of the relaxed RRM measurements as being performed using relaxed RRM measurements.

13. The method of any of Embodiments 11-12, wherein the indication of the status of the relaxed RRM measurements further comprises an indication that the relaxed RRM measurements were performed due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

14. The method of any of Embodiments 11-12, wherein the indication to allow use of relaxed RRM measurements for MDT logging comprises an indication to use relaxed RRM measurements for MDT logging due at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold, without allowing use of relaxed RRM measurements for MDT logging due to at least another one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

15. The method of any of Embodiments 11-14, wherein the communication device is in an idle state or an inactive state (e.g., a Radio Resource Control, RRC, idle state or an RRC inactive state) when performing the relaxed RRM measurements, the method further comprising: after performing the relaxed RRM measurements, transitioning (1885) to a connected state (e.g., an RRC connected state); and transmitting (1889) an MDT report to the network while in the connected state, wherein the MDT report includes the MDT log with the relaxed RRM measurements.

16. The method of any of Embodiments 11-15, wherein the RRM configuration is received via broadcast signaling, and wherein the MDT configuration is received via dedicated signaling.

17. A method of operating a communication device (900) in a network, the method comprising: receiving (1905) a Radio Resource Management, RRM, configuration from the network, wherein the RRM configuration includes configuration for relaxed RRM measurements; receiving (1909) a Minimization of Drive Test, MDT, configuration from the network, wherein the MDT configuration includes an indication to allow use of only relaxed RRM measurements for MDT logging; performing (1911) relaxed RRM measurements according to the RRM configuration including configuration for relaxed RRM measurements; storing (1925) the relaxed RRM measurements in an MDT log for an MDT logging occasion according to the MDT configuration.

18. The method of Embodiment 17, wherein the indication to allow use of only relaxed RRM measurements comprises an indication to allow use of only relaxed RRM measurements due to one or more of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

19. The method of any of Embodiments 17-18 further comprising: storing (1929) in the MDT log for the MDT logging occasion an indication that the relaxed RRM measurements were performed due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

20. The method of any of Embodiments 17-19 further comprising: performing (1911) normal RRM measurement according to the RRM configuration without storing the normal RRM measurements in the MDT log based on the MDT configuration including the indication to allow use of only relaxed RRM measurements for MDT logging.

21. The method of any of Embodiments 17-20, wherein the communication device is in an idle state or an inactive state (e.g., a Radio Resource Control, RRC, idle state or an RRC inactive state) when performing the relaxed RRM measurements, the method further comprising: after performing the relaxed RRM measurements, transitioning (1985) to a connected state (e.g., an RRC connected state); and transmitting (1989) an MDT report to the network while in the connected state, wherein the MDT report includes the MDT log with the relaxed RRM measurements.

22. The method of any of Embodiments 17-21, wherein the RRM configuration is received via broadcast signaling, and wherein the MDT configuration is received via dedicated signaling.

23. A method of operating a communication device (900) in a network, the method comprising: receiving (2005) a Radio Resource Management, RRM, configuration from the network, wherein the RRM configuration includes configuration for relaxed RRM measurements; receiving (2009) a Minimization of Drive Test, MDT, configuration from the network, wherein the MDT configuration includes an indication to require use of normal RRM measurements during MDT logging; determining (2015) that a criteria for relaxed RRM measurements is satisfied according to the RRM configuration during an MDT logging interval according to the MDT configuration; performing (2019) normal RRM measurements during the MDT logging interval according to the MDT configuration including the indication to require use of normal RRM measurements during MDT logging; storing (2025) the normal RRM measurements in an MDT log for an MDT logging occasion according to the MDT configuration; and storing (2029) in the MDT log for the MDT logging occasion an indication that the criteria for relaxed RRM measurements was satisfied during the MDT logging interval.

24. The method of Embodiment 23, wherein the indication that the criteria for relaxed RRM measurements was satisfied during the MDT logging interval further comprises an indication that the criteria for relaxed RRM measurements was satisfied due to at least one of a low mobility condition of the communication device, a condition of the communication device not being at a cell edge, a received power of a serving cell exceeding a power threshold, and/or a received quality of a serving cell exceeding a quality threshold.

25. The method of any of Embodiments 23-24, wherein the communication device is in an idle state or an inactive state (e.g., a Radio Resource Control, RRC, idle state or an RRC inactive state) when performing the normal RRM measurements, the method further comprising: after performing the normal RRM measurements, transitioning (2085) to a connected state (e.g., an RRC connected state); and transmitting (2089) an MDT report to the network while in the connected state, wherein the MDT report includes the normal RRM measurements and the indication that the criteria for relaxed RRM measurements was satisfied.

26. The method of any of Embodiments 23-25, wherein the RRM configuration is received via broadcast signaling, and wherein the MDT configuration is received via dedicated signaling.

27. A method of operating a communication device (900) in a network, the method comprising: receiving (2105) a Radio Resource Management, RRM, configuration via broadcast signaling, wherein the RRM configuration includes configuration for relaxed RRM measurements; receiving (2109) a Minimization of Drive Test, MDT, configuration via dedicated signaling, wherein the MDT configuration includes an indication to allow use of relaxed RRM measurements for MDT logging; performing (2111) relaxed RRM measurements according to an RRM configuration; and storing (2125) the relaxed RRM measurements in an MDT log for an MDT logging occasion according to an MDT configuration.

28. The method of Embodiment 27 further comprising: storing (2129) in the MDT log for the MDT logging occasion an indication of a status of the relaxed RRM measurements as being performed using relaxed RRM measurements.

29. A communication device (900) 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 communication device to perform operations according to any of Embodiments 1-28.

30. A communication device (900) adapted to perform according to any of Embodiments

1-28. 31. A computer program comprising program code to be executed by processing circuitry (903) of a communication device (900), whereby execution of the program code causes the communication device (900) to perform operations according to any of embodiments 1-28.

32. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (903) of a communication device (900), whereby execution of the program code causes the communication device (900) to perform operations according to any of embodiments 1-28.

[0166] Citations are provided below for references mentioned in the present disclosure.

[1] 3GPP TR 36.805 V9.0.0 (2009-12), Technical Specification Group Radio Access Network; Study on Minimization of drive-tests in Next Generation Networks; (Release 9)

[2] 3GPP TS 38.331 V16.0.0 (2020-03), Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16)

[0167] Additional explanation is provided below.

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

[0169] 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. [0170] Figure 18 illustrates a wireless network in accordance with some embodiments.

[0171] 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 18. For simplicity, the wireless network of Figure 18 only depicts network 4106, network nodes 4160 and 4160b, and WDs 4110, 4110b, and 4110c (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 landbne telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 4160 and wireless device (WD) 4110 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.

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

[0173] Network 4106 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.

[0174] Network node 4160 and WD 4110 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.

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

[0176] In Figure 18, network node 4160 includes processing circuitry 4170, device readable medium 4180, interface 4190, auxiliary equipment 4184, power source 4186, power circuitry 4187, and antenna 4162. Although network node 4160 illustrated in the example wireless network of Figure 18 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 4160 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 4180 may comprise multiple separate hard drives as well as multiple RAM modules).

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

[0178] Processing circuitry 4170 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 4170 may include processing information obtained by processing circuitry 4170 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.

[0179] Processing circuitry 4170 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 4160 components, such as device readable medium 4180, network node 4160 functionality. For example, processing circuitry 4170 may execute instructions stored in device readable medium 4180 or in memory within processing circuitry 4170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 4170 may include a system on a chip (SOC).

[0180] In some embodiments, processing circuitry 4170 may include one or more of radio frequency (RF) transceiver circuitry 4172 and baseband processing circuitry 4174. In some embodiments, radio frequency (RF) transceiver circuitry 4172 and baseband processing circuitry 4174 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 4172 and baseband processing circuitry 4174 may be on the same chip or set of chips, boards, or units

[0181] 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 4170 executing instructions stored on device readable medium 4180 or memory within processing circuitry 4170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 4170 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 4170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 4170 alone or to other components of network node 4160, but are enjoyed by network node 4160 as a whole, and/or by end users and the wireless network generally.

[0182] Device readable medium 4180 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 4170. Device readable medium 4180 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 4170 and, utilized by network node 4160. Device readable medium 4180 may be used to store any calculations made by processing circuitry 4170 and/or any data received via interface 4190. In some embodiments, processing circuitry 4170 and device readable medium 4180 may be considered to be integrated.

[0183] Interface 4190 is used in the wired or wireless communication of signalling and/or data between network node 4160, network 4106, and/or WDs 4110. As illustrated, interface 4190 comprises port(s)/terminal(s) 4194 to send and receive data, for example to and from network 4106 over a wired connection. Interface 4190 also includes radio front end circuitry 4192 that may be coupled to, or in certain embodiments a part of, antenna 4162. Radio front end circuitry 4192 comprises filters 4198 and amplifiers 4196. Radio front end circuitry 4192 may be connected to antenna 4162 and processing circuitry 4170. Radio front end circuitry may be configured to condition signals communicated between antenna 4162 and processing circuitry 4170. Radio front end circuitry 4192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 4192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 4198 and/or amplifiers 4196. The radio signal may then be transmitted via antenna 4162. Similarly, when receiving data, antenna 4162 may collect radio signals which are then converted into digital data by radio front end circuitry 4192. The digital data may be passed to processing circuitry 4170. In other embodiments, the interface may comprise different components and/or different combinations of components.

[0184] In certain alternative embodiments, network node 4160 may not include separate radio front end circuitry 4192, instead, processing circuitry 4170 may comprise radio front end circuitry and may be connected to antenna 4162 without separate radio front end circuitry 4192. Similarly, in some embodiments, all or some of RF transceiver circuitry 4172 may be considered a part of interface 4190. In still other embodiments, interface 4190 may include one or more ports or terminals 4194, radio front end circuitry 4192, and RF transceiver circuitry 4172, as part of a radio unit (not shown), and interface 4190 may communicate with baseband processing circuitry 4174, which is part of a digital unit (not shown).

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

[0186] Antenna 4162, interface 4190, and/or processing circuitry 4170 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 4162, interface 4190, and/or processing circuitry 4170 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.

[0187] Power circuitry 4187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 4160 with power for performing the functionality described herein. Power circuitry 4187 may receive power from power source 4186. Power source 4186 and/or power circuitry 4187 may be configured to provide power to the various components of network node 4160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 4186 may either be included in, or external to, power circuitry 4187 and/or network node 4160. For example, network node 4160 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 4187. As a further example, power source 4186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 4187. 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.

[0188] Alternative embodiments of network node 4160 may include additional components beyond those shown in Figure 18 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 4160 may include user interface equipment to allow input of information into network node 4160 and to allow output of information from network node 4160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 4160.

[0189] 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 3GPP 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.

[0190] As illustrated, wireless device 4110 includes antenna 4111, interface 4114, processing circuitry 4120, device readable medium 4130, user interface equipment 4132, auxiliary equipment 4134, power source 4136 and power circuitry 4137. WD 4110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 4110, 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 4110.

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

[0192] As illustrated, interface 4114 comprises radio front end circuitry 4112 and antenna 4111. Radio front end circuitry 4112 comprise one or more filters 4118 and amplifiers 4116. Radio front end circuitry 4112 is connected to antenna 4111 and processing circuitry 4120, and is configured to condition signals communicated between antenna 4111 and processing circuitry 4120. Radio front end circuitry 4112 may be coupled to or a part of antenna

4111. In some embodiments, WD 4110 may not include separate radio front end circuitry 4112; rather, processing circuitry 4120 may comprise radio front end circuitry and may be connected to antenna 4111. Similarly, in some embodiments, some or all of RF transceiver circuitry 4122 may be considered a part of interface 4114. Radio front end circuitry 4112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 4112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 4118 and/or amplifiers 4116. The radio signal may then be transmitted via antenna 4111. Similarly, when receiving data, antenna 4111 may collect radio signals which are then converted into digital data by radio front end circuitry

4112. The digital data may be passed to processing circuitry 4120. In other embodiments, the interface may comprise different components and/or different combinations of components.

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

[0194] As illustrated, processing circuitry 4120 includes one or more of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 4120 of WD 4110 may comprise a SOC. In some embodiments, RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 4124 and application processing circuitry 4126 may be combined into one chip or set of chips, and RF transceiver circuitry 4122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 4122 and baseband processing circuitry 4124 may be on the same chip or set of chips, and application processing circuitry 4126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 4122 may be a part of interface 4114. RF transceiver circuitry 4122 may condition RF signals for processing circuitry 4120.

[0195] In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 4120 executing instructions stored on device readable medium 4130, 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 4120 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 4120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 4120 alone or to other components of WD 4110, but are enjoyed by WD 4110 as a whole, and/or by end users and the wireless network generally.

[0196] Processing circuitry 4120 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 4120, may include processing information obtained by processing circuitry 4120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 4110, 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. [0197] Device readable medium 4130 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 4120. Device readable medium 4130 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 4120. In some embodiments, processing circuitry 4120 and device readable medium 4130 may be considered to be integrated.

[0198] User interface equipment 4132 may provide components that allow for a human user to interact with WD 4110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 4132 may be operable to produce output to the user and to allow the user to provide input to WD 4110. The type of interaction may vary depending on the type of user interface equipment 4132 installed in WD 4110. For example, if WD 4110 is a smart phone, the interaction may be via a touch screen; if WD 4110 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 4132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 4132 is configured to allow input of information into WD 4110, and is connected to processing circuitry 4120 to allow processing circuitry 4120 to process the input information. User interface equipment 4132 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 4132 is also configured to allow output of information from WD 4110, and to allow processing circuitry 4120 to output information from WD 4110. User interface equipment 4132 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 4132, WD 4110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein. [0199] Auxiliary equipment 4134 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 4134 may vary depending on the embodiment and/or scenario.

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

[0201] Figure 19 illustrates a user Equipment in accordance with some embodiments.

[0202] Figure 19 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 42200 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 4200, as illustrated in Figure 19, 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 19 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[0203] In Figure 19, UE 4200 includes processing circuitry 4201 that is operatively coupled to input/output interface 4205, radio frequency (RF) interface 4209, network connection interface 4211, memory 4215 including random access memory (RAM) 4217, read-only memory (ROM) 4219, and storage medium 4221 or the like, communication subsystem 4231, power source 4213, and/or any other component, or any combination thereof. Storage medium 4221 includes operating system 4223, application program 4225, and data 4227. In other embodiments, storage medium 4221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 19, 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.

[0204] In Figure 19, processing circuitry 4201 may be configured to process computer instructions and data. Processing circuitry 4201 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 4201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0205] In the depicted embodiment, input/output interface 4205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 4200 may be configured to use an output device via input/output interface 4205. 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 4200. 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 4200 may be configured to use an input device via input/output interface 4205 to allow a user to capture information into UE 4200. 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.

[0206] In Figure 19, RF interface 4209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 4211 may be configured to provide a communication interface to network 4243a. Network 4243a 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 4243a may comprise a Wi-Fi network. Network connection interface 4211 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 4211 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.

[0207] RAM 4217 may be configured to interface via bus 4202 to processing circuitry 4201 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 4219 may be configured to provide computer instructions or data to processing circuitry 4201. For example, ROM 4219 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 4221 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 4221 may be configured to include operating system 4223, application program 4225 such as a web browser application, a widget or gadget engine or another application, and data file 4227. Storage medium 4221 may store, for use by UE 4200, any of a variety of various operating systems or combinations of operating systems.

[0208] Storage medium 4221 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 4221 may allow UE 4200 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 4221, which may comprise a device readable medium.

[0209] In Figure 19, processing circuitry 4201 may be configured to communicate with network 4243b using communication subsystem 4231. Network 4243a and network 4243b may be the same network or networks or different network or networks. Communication subsystem 4231 may be configured to include one or more transceivers used to communicate with network 4243b. For example, communication subsystem 4231 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.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 4233 and/or receiver 4235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 4233 and receiver 4235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0210] In the illustrated embodiment, the communication functions of communication subsystem 4231 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 4231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 4243b 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 4243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 4213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 4200.

[0211] The features, benefits and/or functions described herein may be implemented in one of the components of UE 4200 or partitioned across multiple components of UE 4200. 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 4231 may be configured to include any of the components described herein. Further, processing circuitry 4201 may be configured to communicate with any of such components over bus 4202.

In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 4201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 4201 and communication subsystem 4231. 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.

[0212] Figure 20 illustrates a virtualization environment in accordance with some embodiments.

[0213] Figure 20 is a schematic block diagram illustrating a virtualization environment 4300 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).

[0214] 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 4300 hosted by one or more of hardware nodes 4330. 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.

[0215] The functions may be implemented by one or more applications 4320 (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 4320 are run in virtualization environment 4300 which provides hardware 4330 comprising processing circuitry 4360 and memory 4390. Memory 4390 contains instructions 4395 executable by processing circuitry 4360 whereby application 4320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

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

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

[0218] During operation, processing circuitry 4360 executes software 4395 to instantiate the hypervisor or virtualization layer 4350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 4350 may present a virtual operating platform that appears like networking hardware to virtual machine 4340.

[0219] As shown in Figure 20, hardware 4330 may be a standalone network node with generic or specific components. Hardware 4330 may comprise antenna 43225 and may implement some functions via virtualization. Alternatively, hardware 4330 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) 43100, which, among others, oversees lifecycle management of applications 4320.

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

[0221] In the context of NFV, virtual machine 4340 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 4340, and that part of hardware 4330 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 4340, forms a separate virtual network elements (VNE). [0222] 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 4340 on top of hardware networking infrastructure 4330 and corresponds to application 4320 in Figure 20.

[0223] In some embodiments, one or more radio units 43200 that each include one or more transmitters 43220 and one or more receivers 43210 may be coupled to one or more antennas 43225. Radio units 43200 may communicate directly with hardware nodes 4330 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.

[0224] In some embodiments, some signalling can be effected with the use of control system 43230 which may alternatively be used for communication between the hardware nodes 4330 and radio units 43200.

[0225] Figure 21 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

[0226] With reference to Figure 21 , in accordance with an embodiment, a communication system includes telecommunication network 4410, such as a 3GPP-tyP ^e cellular network, which comprises access network 4411, such as a radio access network, and core network 4414. Access network 4411 comprises a plurality of base stations 4412a, 4412b, 4412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c is connectable to core network 4414 over a wired or wireless connection 4415. A first UE 4491 located in coverage area 4413 c is configured to wirelessly connect to, or be paged by, the corresponding base station 4412c. A second UE 4492 in coverage area 4413a is wirelessly connectable to the corresponding base station 4412a. While a plurality of UEs 4491, 4492 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 4412.

[0227] Telecommunication network 4410 is itself connected to host computer 4430, 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 4430 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 4421 and 4422 between telecommunication network 4410 and host computer 4430 may extend directly from core network 4414 to host computer 4430 or may go via an optional intermediate network 4420. Intermediate network 4420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 4420, if any, may be a backbone network or the Internet; in particular, intermediate network 4420 may comprise two or more sub-networks (not shown).

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

[0229] Figure 22 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

[0230] 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 22. In communication system 4500, host computer 4510 comprises hardware 4515 including communication interface 4516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 4500. Host computer 4510 further comprises processing circuitry 4518, which may have storage and/or processing capabilities. In particular, processing circuitry 4518 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 4510 further comprises software 4511, which is stored in or accessible by host computer 4510 and executable by processing circuitry 4518. Software 4511 includes host application 4512.

Host application 4512 may be operable to provide a service to a remote user, such as UE 4530 connecting via OTT connection 4550 terminating at UE 4530 and host computer 4510. In providing the service to the remote user, host application 4512 may provide user data which is transmitted using OTT connection 4550.

[0231] Communication system 4500 further includes base station 4520 provided in a telecommunication system and comprising hardware 4525 enabling it to communicate with host computer 4510 and with UE 4530. Hardware 4525 may include communication interface 4526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 4500, as well as radio interface 4527 for setting up and maintaining at least wireless connection 4570 with UE 4530 located in a coverage area (not shown in Figure 22) served by base station 4520. Communication interface 4526 may be configured to facilitate connection 4560 to host computer 4510. Connection 4560 may be direct or it may pass through a core network (not shown in Figure 22) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 4525 of base station 4520 further includes processing circuitry 4528, 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 4520 further has software 4521 stored internally or accessible via an external connection.

[0232] Communication system 4500 further includes UE 4530 already referred to.

Its hardware 4535 may include radio interface 4537 configured to set up and maintain wireless connection 4570 with a base station serving a coverage area in which UE 4530 is currently located. Hardware 4535 of UE 4530 further includes processing circuitry 4538, 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 4530 further comprises software 4531, which is stored in or accessible by UE 4530 and executable by processing circuitry 4538. Software 4531 includes client application 4532. Client application 4532 may be operable to provide a service to a human or non-human user via UE 4530, with the support of host computer 4510. In host computer 4510, an executing host application 4512 may communicate with the executing client application 4532 via OTT connection 4550 terminating at UE 4530 and host computer 4510. In providing the service to the user, client application 4532 may receive request data from host application 4512 and provide user data in response to the request data. OTT connection 4550 may transfer both the request data and the user data. Client application 4532 may interact with the user to generate the user data that it provides.

[0233] It is noted that host computer 4510, base station 4520 and UE 4530 illustrated in Figure 22 may be similar or identical to host computer 4430, one of base stations 4412a, 4412b, 4412c and one of UEs 4491, 4492 of Figure 21, respectively. This is to say, the inner workings of these entities may be as shown in Figure 22 and independently, the surrounding network topology may be that of Figure 21.

[0234] In Figure 22, OTT connection 4550 has been drawn abstractly to illustrate the communication between host computer 4510 and UE 4530 via base station 4520, 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 4530 or from the service provider operating host computer 4510, or both. While OTT connection 4550 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).

[0235] Wireless connection 4570 between UE 4530 and base station 4520 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 4530 using OTT connection 4550, in which wireless connection 4570 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.

[0236] 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 4550 between host computer 4510 and UE 4530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 4550 may be implemented in software 4511 and hardware 4515 of host computer 4510 or in software 4531 and hardware 4535 of UE 4530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 4550 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 4511, 4531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 4550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 4520, and it may be unknown or imperceptible to base station 4520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 4510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 4511 and 4531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 4550 while it monitors propagation times, errors etc.

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

[0238] Figure 23 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 21 and 22. For simplicity of the present disclosure, only drawing references to Figure 23 will be included in this section. In step 4610, the host computer provides user data. In substep 4611 (which may be optional) of step 4610, the host computer provides the user data by executing a host application. In step 4620, the host computer initiates a transmission carrying the user data to the UE. In step 4630 (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 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0239] Figure 24 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments. [0240] Figure 24 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 21 and 22. For simplicity of the present disclosure, only drawing references to Figure

24 will be included in this section. In step 4710 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 4720, 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 4730 (which may be optional), the UE receives the user data carried in the transmission.

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

[0242] Figure 25 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 21 and 22. For simplicity of the present disclosure, only drawing references to Figure

25 will be included in this section. In step 4810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 4820, the UE provides user data. In substep 4821 (which may be optional) of step 4820, the UE provides the user data by executing a client application. In substep 4811 (which may be optional) of step 4810, 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 4830 (which may be optional), transmission of the user data to the host computer. In step 4840 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.

[0243] Figure 26 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments [0244] Figure 26 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 21 and 22. For simplicity of the present disclosure, only drawing references to Figure 26 will be included in this section. In step 4910 (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 4920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 4930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

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

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

[0247] 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

AP Access Point

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

CN Core Network

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

IoT Internet of Things

LOS Line of Sight

LPP 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

MTC Machine Type Communication

NG Next Generation

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

NW Network

OAM Operations, administration and management

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

OAM 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

QoS Quality of Service

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 Wireless Local Area Network

[0248] Further definitions and embodiments are discussed below.

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

[0250] 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" (abbreviated ‘7”) includes any and all combinations of one or more of the associated listed items.

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

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

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

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

[0256] 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 claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.