WO2021145805A1

WO2021145805A1 - Communication methods and related communication devices and nodes

Info

Publication number: WO2021145805A1
Application number: PCT/SE2020/051065
Authority: WO
Inventors: Pradeepa Ramachandra; Angelo Centonza; Oumer Teyeb
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-01-17
Filing date: 2020-11-05
Publication date: 2021-07-22

Abstract

According to an example embodiment, a method of operating a node of a wireless communication network. A logged measurement configuration is transmitted (2901) to a communication device. A release message is transmitted (2905) to the communication device, wherein the release message initiates transitioning of the communication device to a dormant state. After transmitting the release message, a resume message or a setup message is transmitted (2907) to the communication device, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state. After transmitting the resume message or the setup message, a logged measurement report is received (2909) from the communication device, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency. Related methods of operating a communication device, nodes, communication devices, and computer program products are also discussed.

Description

COMMUNICATION METHODS AND RELATED COMMUNICATION DEVICES AND

NODES

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] Carrier Aggregation (CA) and Dual Connectivity (DC) are discussed below.

[0003] In 3 GPP Rel-10, Carrier Aggregation (CA) was introduced in LTE to enable the UE to transmit/receive information via multiple cells (so called Secondary Cells - SCell(s)) from multiple carrier frequencies, to benefit from the existence of non-contiguous and contiguous carriers. In CA terminology, the PCell is the cell towards which the UE established the RRC (Radio Resource Control) connection or did handover to. In CA, cells are aggregated on MAC- level where MAC (Medium Access Control) gets grants for a certain cell and multiplexes data from different bearers to one Transport Block being sent on that cell. Also, MAC controls how that process is done as shown in Figure 1.

[0004] SCells can be ’’added” (a.k.a. ’’configured”) for the UE using RRC signaling (e.g. RRCConnectionReconfiguration or RRCReconfiguration), which takes in the order of hundreds of milliseconds. A cell which is configured for the UE becomes a ’’serving cell” for this UE.

[0005] With the later introduction of Dual Connectivity in 3 GPP Rel-12, it was also possible to add what is called an SCG (Secondary Cell Group) configuration to the UE. The main benefit would be to add a cell from another eNodeB to the UE configuration. Protocol wise, that would require different MAC entities, one for each cell group. The UE will then be configured with two cell groups, one associated to the PCell (master node) and another associated to a PSCell (of the secondary node), where each group may possibly have their own associated SCells.

[0006] Early measurements in LTE (Long Term Evolution) and NR (New Radio) are discussed below.

[0007] In LTE Rel-15, it is possible to configure the UE to report so called early measurements (also known as idle mode measurements) upon the transition from idle/inactive to connected state. These measurements are measurements that the UE can perform in idle/inactive state, and according to a configuration provided by the source cell with the intention to receive these measurements immediately after the UE gets connected and quickly setup carrier aggregation (CA), without the need to first provide a measurement configuration (measConfig) in RRC CONNECTED and wait for hundreds of milliseconds until first samples are collected, monitored and then the first reports are triggered and transmitted to the network.

[0008] Measurement configuration for early measurements upon setup/resume in LTE rel-15 is discussed below.

[0009] A first aspect of an existing approach, as standardized in EUTRA 36.331, is described in Section 5.6.20 Idle Mode Measurements. A UE can be configured upon the transition from RRC CONNECTED to RRC IDLE/RRC INACTIVE (i.e. RRCConnectionRelease) with an early measurement configuration which contains the measurement duration (measIdleDedicated-rl 5), which can be up to 5 minutes long, indicating for how long the UE shall perform the measurements while in IDLE/INACTIVE state. The exact measurement configuration (i.e. which carriers/cells to measure) can be provided either in dedicated signaling within the same RRCConnectionRelease message or via broadcast signaling (SIB5). If dedicated signaling is provided, it overrides the broadcast signaling. After the measurement duration has expired, the UE can still continue performing the early measurements using broadcasted information in SIB5, based on UE implementation.

[0010] The early measurement configuration is specified in the IE measIdleCarrierListEUTRA-rl 5, indicating up to 8 carrier frequencies (maxFreqldle-rl 5) to measure. For each frequency to be measured, an optional cell list (measCellList) can be included that can contain up to 8 cell ID or ranges of cell IDs to perform measurements on (if the cell list is not included, UE performs measurements on any neighbor cell). Additionally, a validity area (validity Area), which is a list of cell identities, can be configured which limits the area in which the early measurements can be performed (i.e. if the UE goes out of the validity area for any of the configured frequencies to be measured, the UE stops performing early measurements).

[0011] It should be noted that even when the UE is in a valid area and the measIdleDuration has not expired yet, the UE may not perform measurements on a particular frequency if the UE is not capable of performing carrier aggregation between the frequency of the current serving cell (i.e. the cell the UE is camping on) and the carrier configured to be measured, or for the case of inter-RAT carriers, if the UE is not capable of performing dual connectivity between the current serving RAT at the current serving frequency (i.e. the frequency used by the serving cell) and the inter-RAT carrier configured to be measured.

[0012] Other cases where the UE may not perform measurements on a certain carrier/frequency (while camping on a given cell) are (based on current agreements in 3 GPP, for LTE/NR rel-16):

• The UE was configured to perform the measurements on that particular carrier, but it is not capable of performing CA between the serving carrier and the carrier configured to be measured

• The UE was configured to perform the measurements on a certain inter-RAT carrier, but it is not capable of performing DC between the serving carrier and the inter-RAT carrier configured to be measured

• The UE might have performed inter-RAT cell re-selection, upon which the UE stops performing early measurements

• The UE might have done autonomous transition from INACTIVE state to IDLE state due to some erroneous case (e.g. receiving a CN paging while in INACTIVE state), upon which the UE stops performing early measurements

• The UE might have received a dedicated measurement configuration for a certain frequency (e.g. SSB configuration) when it was released/suspended, and it has performed cell re-selection to another cell where the measurement configuration broadcasted at that frequency is different from the one that the UE has been provided via dedicated signalling, upon which the UE stops/pauses performing early measurements for that frequency

• The UE might have received a measurement configuration for a certain frequency (e.g. SSB configuration) via broadcast signalling when it was released/suspended, but it has performed cell re-selection to another cell where the measurement configuration is not broadcasted at that frequency is different from the one that the UE has been provided via broadcasted signalling in the source cell where it was released, upon which the UE stops/pauses performing early measurements for that frequency

[0013] The broadcasted and dedicated signaling early measurement signaling in LTE rel- 15 is illustrated in the RRCconnectionRelease message of Section 6.2.2 of Reference [1] (including the measIdleConfig information element) and the MeasIdleConfig information element of Section 6.3.5 of Reference [1]).

[0014] Another aspect of the existing approach occurs when the UE tries to resume or setup a call from RRC IDLE without context. If the previous step is performed, i.e., if the UE is configured to store idle measurements, the network may request the UE after resume / setup (after security is activated) whether the UE has idle measurements available.

[0015] In the case this UE is setting up a connection coming from RRC IDLE without the AS Context, the network is not aware that the UE has available measurements stored. Then, to allow the network to know that, and possibly request the UE to report early measurements, the UE may indicate the availability of stored idle measurements in RRCConnectionSetupComplete. As not all cells would support the feature anyway, the UE only includes that availability information if the cell broadcasts in SIB2 the idleModeMeasurements indication. The flag in RRCConnectionSetupComplete and procedure text are shown in Section 6.2.2 of Reference [1]

[0016] In the case this UE is setting up a connection coming from RRC IDLE but with a stored AS Context (i.e. resume from suspended) or from RRC INACTIVE, the network may be aware that the UE may have available idle measurements stored after checking the fetched context from the source node where the UE got suspended. However, it is still not certain that the UE has measurements available since the UE is only required to perform the measurements if the cells are above the configured RSRP/RSRQ thresholds and while it performs cell selection/cell reselection within the configured validity area. Then, to allow the network to know that, and possibly request the UE to report early measurements, the UE may also indicate the availability of stored idle measurements in RRCConnectionResumeComplete. As not all cells would support the feature anyway, the UE only includes that availability information if the cell broadcasts in SIB2 the idleModeMeasurements indication. The flag in RRCConnectionResumeComplete and procedure text are shown in Section 6.2.2 of Reference [1]

[0017] Once the UE indicates to the target cell upon resume or setup that idle measurements are available, the network may finally request the UE to report these available measurements by including the field idleModeMeasurementReq in the UEInformationRequest message transmitted to the UE as shown in Figure 2 (corresponding to Figure 5.6.5.1-1 of Reference [1] Then, the UE responds with a UEInformationResponse containing these measurements as further shown in Figure 2 (corresponding to Figure 5.6.5.1-1 of Reference [1] The UEInformationResponse message is illustrated in Section 6.2.2 of Reference [1]

[0018] Measurement configuration for early measurements upon setup/resume in LTE/NR rel-16 is discussed below.

[0019] In rel-16, under the work item called “Multi -RAT Dual-Connectivity and Carrier Aggregation enhancements”, an enhanced version of the LTE rel-15 early measurement approach has been adopted to NR rel-16 (also the LTE rel-16 approach has been enhanced).

Some enhancements are discussed below.

• The early measurement configuration in LTE and NR rel-16 can contain both LTE and NR configuration (i.e. UE can measure both LTE and NR carriers, including beam measurement in the case of NR). This is to enable not only fast CA but also fast DC setup.

• The network can request the early measurements in the resume message and UE can report them in the resume complete messages (while in LTE rel-15, early measurement reporting was possible only via UE Information Request/Response after the connection is resumed/established).

[0020] The signaling diagrams of Figures 3 A, 3B, 4, 5, and 6 indicate the current agreements regarding the early measurement signaling in LTE/NR rel-16.

[0021] Figures 3A and 3B illustrate early measurement reporting in LTE/NR IDLE mode in rel-16 during connection setup, option 1.

[0022] Figure 4 illustrates early measurement reporting in LTE/NR IDLE mode in rel-16 during connection setup, option 2.

[0023] Figure 5 illustrates early measurement reporting in LTE IDLE with suspended, LTE INACTIVE mode or NR INACTIVE mode in rel-16, option 1.

[0024] Figure 6 illustrates early measurement reporting in LTE INACTIVE, LTE IDLE with suspended and NR INACTIVE mode in rel-16, option 2.

[0025] MDT (Minimization of drive test) is discussed below.

[0026] MDT was firstly studied in Rel-9 (TR 36.805) driven by RAN2 with the purpose to reduce/minimize the actual drive tests. MDT has been introduced since Rel-10 in LTE. MDT has not been specified for NR in the involved standards in RAN2, RAN3 and SA5 groups. The use cases in the TR 36.805 include: Coverage improvement/optimization; Mobility improvement/optimization; Capacity improvement/optimization; Parameterization for common channels; and/or QoS verification

[0027] MDT types based on RRC states are discussed below.

[0028] In general, there are two types of MDT measurement logging, i.e., Logged MDT (logging of measurements in idle mode or inactive state) and Immediate MDT (logging of measurements when the UE is RRC Connected mode).

[0029] Logged MDT is discussed below.

[0030] A UE in RRC IDLE state is configured to perform periodical MDT logging after receiving the MDT configurations from the network. The UE shall report the DL pilot strength measurements (RSRP/RSRQ) together with time information, detailed location information if available, and WLAN, Bluetooth to the network via using the 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. The measurement logging for Logged MDT is illustrated below in Table 1.

Table 1. The measurement logging for Logged MDT

[0031] 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 MDT logging is shown in Figure 7. Characteristics of the T330 Timer of Figure 7 are provided below in Table 2.

Table 2. T330 Timer

[0032] The network sends the LoggedMeasurementConfiguration to configure the UE to perform logged measurements

[0033] The LoggedMeasurementConfiguration message is used by E-UTRAN to configure the UE to perform logging of measurement results while in RRC IDLE or to perform logging of measurement results for MBSFN while in both RRC IDLE and RRC CONNECTED. It is used to transfer the logged measurement configuration for network performance optimisation, see TS 37.320. The LoggedMeasurementConfiguration message has the following characteristics:

Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: E-UTRAN to UE

[0034] The LoggedMeasurementConfiguration message is illustrated in Section 6.2.2 of Reference [1] LoggedMeasurementConfiguration fields from the LoggedMeasurementConfiguration message are provided in Table 3 below.

Table 3. LoggedMeasurementConfiguration field descriptions.

[0035] The AreaConfiguration indicates an area for which UE is requested to perform measurement logging. If not configured, measurement logging is not restricted to specific cells or tracking areas but applies as long as the RPLMN (Registered PLMN) is contained in plmn- IdentityList stored in VarLogMeasReport.

[0036] The AreaConfiguration information element is illustrated in Section 6.3.6 of Reference [1] AreaConfiguration field descriptions are provided below in Table 4.

Table 4. AreaConfiguration field descriptions.

[0037] The TraceReference contains parameter Trace Reference as defined in TS 32.422.

[0038] The TraceReference information element is illustrated in Section 6.3.6 of Reference [1].

[0039] The UE stores the logged measurement configuration in the UE variable varLogMeasConfig and the logged measurement results in VarLogMeasReport.

[0040] The UE variable VarLogMeasConfig includes the configuration of the logging of measurements to be performed by the UE while in RRC IDLE, covering intra-frequency, inter- frequency, inter-RAT mobility and MBSFN related measurements. If MBSFN logging is configured, the UE performs logging of measurements while in both RRC IDLE and RRC CONNECTED. Otherwise, the UE performs logging of measurements only while in RRC IDLE.

[0041] The VarLogMeasConfig UE variable is illustrated in Section 7.1 of Reference [1]

[0042] The UE variable VarLogMeasReport includes the logged measurements information. The VarLogMeasReport UE variable and elements thereof are illustrated in Sections 6.2.2, 6.4, and 7.1 of [1]

[0043] On receiving a UEInformationRequest message from the network that includes logMeasReportReq, the UE includes the logged measurements in the UEInformationResponse message. [0044] The procedures for logged measurement configuration and the performing of logged measurements are discussed below with respect to 3GPP TS 36.331, V15.8.0 (2019-12), also referred to as Reference [1]

[0045] Figure 8 (corresponding to Figure 5.6.6.1-1 of Reference [1] illustrates a Logged measurement configuration message transmitted from EUTRAN to the LIE.

[0046] As discussed in Section 5.6.6.1 of Reference [1], the purpose of this procedure is to configure the UE to perform logging of measurement results while in RRC IDLE and to perform logging of measurement results for MBSFN in both RRC IDLE and RRC CONNECTED. The procedure applies to logged measurements capable UEs that are in RRC CONNECTED.

[0047] NOTE:E-UTRAN may retrieve stored logged measurement information by means of the UE information procedure.

[0048] Initiation is discussed in Section 5.6.6.2 of Reference [1]

[0049] E-UTRAN initiates the logged measurement configuration procedure to UE in RRC CONNECTED by sending the LoggedMeasurementConfiguration message.

[0050] Reception of the LoggedMeasurementConfiguration by the UE is discussed in Section 5.6.6.3 of Reference [1]

[0051] T330 expiry is discussed in Section 5.6.6.4 of Reference [1] as follows. Upon expiry of T330 the UE shall: release VarLogMeasConfig; The UE is allowed to discard stored logged measurements, i.e. to release VarLogMeasReport, 48 hours after T330 expiry.

[0052] Release of Logged Measurement Configuration is discussed in Section 5.6.7 of Reference [1].

[0053] As discussed in Section 5.6.7.1 of Reference [1], the purpose of this procedure is to release the logged measurement configuration as well as the logged measurement information.

[0054] Initiation is discussed in Section 5.6.7.2 of Reference [1] as follows. 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: stop timer T330, if running; if stored, discard the logged measurement configuration as well as the logged measurement information, i.e. release the UE variables VarLogMeasConfig and VarLogMeasReport;

[0055] Measurements logging is discussed in Section 5.6.8 of Reference [1] [0056] As discussed in Section 5.6.8.1 of Reference [1], this procedure specifies the logging of available measurements by a UE in RRC IDLE that has a logged measurement configuration and the logging of available measurements by a UE in both RRC IDLE and RRC CONNECTED if targetMBSFN-AreaList is included in VarLogMeasConfig.

[0057] Initiation is discussed in Section 5.6.8.2 of Reference [1]

[0058] Reception of the UEInformationRequest message is discussed in Section 5.6.5.3 of Reference [1].

[0059] Cell reselection in RRC IDLE and in RRC INACTIVE is discussed below.

[0060] When the UE is in dormant state (LTE/NR IDLE, LTE IDLE with suspended, LTE/NR INACTIVE), it performs the cell selection and re-selection procedures. The cell reselection procedure allows the UE to select a more suitable cell and camp on it.

[0061] The UE in dormant state measures signal strength and signal quality of neighboring cells on the current frequency and any inter-frequency carriers. Measurements on cells on inter-frequency carriers and cells on inter-RAT frequencies with higher cell reselection priority than the current frequency are always performed. The priorities can either be broadcasted or sent specifically to the UE when it is released to idle mode.

[0062] The cell (re)selected by the UE in a dormant state is also called camping cell and that is the cell where the UE connects when it has data to send and where the UE will monitor for paging. In case the network has data to transmit to the UE it will page the UE in order to reach the UE, and in response to the paging, the UE will initiate the procedure to establish the connection. Once the UE has an active connection additional resources can be setup, such as through additional cells, using techniques like Dual Connectivity and/or Carrier Aggregation, to e.g. increase the throughput.

[0063] In LTE Rel-13, a mechanism was introduced for the UE to be suspended by the network in a suspended state similar to RRC IDLE but with the difference that the UE stores the Access Stratum (AS) context or RRC context. This makes it possible to reduce the signaling when the UE is becoming active again by resuming the RRC connection, instead of as prior to establish the RRC connection from scratch. Reducing the signaling could have several benefits including: Reduce latency e.g. for smart phones accessing Internet; and/or Reduced signaling leads to reduce battery consumption for machine type devices sending very little data. [0064] In NR, a new RRC INACTIVE state was introduced to reduce the signaling overhead over the radio and network interfaces and to improve the UE access latency as well as UE energy consumption. In this state, the Core Network (CN) still regards the UE as connected and the CN-RAN connection is kept active although the RRC connection between the RAN and the UE is suspended. In order to reduce radio interface signaling at connection establishment, context information is kept active in the UE and in the RAN, which enables the UE to resume its RRC connection when it is paged or has UL data or signaling to send.

[0065] In all these suspended states the UE performs cell reselection procedure for mobility purposes in a similar way as for idle mode, i.e. using priority settings that are either received through broadcast or through dedicated signaling. Based on the received priority settings the UE performs measurements on cells and/or frequencies (including intra- and inter- RAT) in order to determine what cell to camp on.

[0066] Cell reselection can be intra-frequency, inter-frequency or inter-RAT. The primary purpose of cell reselection is to ensure that the UE camps on to the best cell in terms of radio condition so that it will get the best service/throughput when it gets connected (as the UE tries to establish a connection with the cell that it is camping on).

[0067] The UE measures some attributes of the serving and neighbor cells to enable the reselection process. For intra-frequency measurements, the UE is able to detect and measure neighbor cells. For inter-frequency neighbor cells, the UE can be indicated with the carrier frequencies to measure. If the serving cell fulfills particular search/measurement criteria, then measurements for cell re-selection may be avoided, if the serving cell attributes fulfill particular search or measurement criteria.

[0068] The cell reselection process is illustrated in Figure 5.2.2-1 of 3GPP TS 38.304 VI 5.6.0 (2019-12), also referred to as Reference [2], and some excerpts from TS 38.304 about the cell reselection process are provided below as well.

[0069] A Cell Reselection evaluation process is discussed in Section 5.2.4 of Reference [2], and Reselection priorities handling is discussed in Section 5.2.4.1 of Reference [2]

[0070] Absolute priorities of different NR frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an NR frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling and deprioritisationReq received in RRCRelease unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of the network configured values).

[0071] The UE shall only perform cell reselection evaluation for NR frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.

[0072] In case UE receives RRCRelease with deprioritisationReq, UE shall consider current frequency and stored frequencies due to the previously received RRCRelease with deprioritisationReq or all the frequencies of NR to be the lowest priority frequency (i.e. lower than any of the network configured values) while T325 is running irrespective of camped RAT. The UE shall delete the stored deprioritisation request(s) when a PLMN selection is performed on request by NAS (TS 23.122).

[0073] NOTE:UE should search for a higher priority layer for cell reselection as soon as possible after the change of priority. The minimum related performance requirements specified in TS 38.133 are still applicable.

[0074] In Section 5.2.4.2 of Reference [2], the Following rules are used by the UE to limit needed measurements:

• If the serving cell fulfils Srxlev > Sin_traSearchP and Squal > Sin_traSearchQ, the UE may choose not to perform intra-frequency measurements.

• Otherwise, the UE shall perform intra-frequency measurements.

• The UE shall apply the following rules for NR inter-frequencies and inter-RAT frequencies which are indicated in system information and for which the UE has priority provided: o For a NR inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection priority of the current NR frequency, the UE shall perform measurements of higher priority NR inter-frequency or inter-RAT frequencies according to TS 38.133. o For a NR inter-frequency with an equal or lower reselection priority than the reselection priority of the current NR frequency and for inter-RAT frequency with lower reselection priority than the reselection priority of the current NR frequency:

^■ If the serving cell fulfils Srxlev > SnonlntraSearchP and Squal > SnonlntraSear iQ, the UE may choose not to perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority;

^■ Otherwise, the UE shall perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority according to TS 38.133.

[0075] NR Inter-frequency and inter-RAT Cell Reselection criteria is discussed in Section 5.2.4.5 of Reference [2]

[0076] If threshServingLowQ is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:

• A cell of a higher priority NR or EUTRAN RAT/frequency fulfils Squal > Threshx_. mghQ during a time interval TreselectionRAT

[0077] Otherwise, cell reselection to a cell on a higher priority NR frequency or inter- RAT frequency than the serving frequency shall be performed if:

• A cell of a higher priority RAT/ frequency fulfils Srxlev > Threshx_, m _hP during a time interval TreselectionRAT; and

• More than 1 second has elapsed since the UE camped on the current serving cell.

[0078] Cell reselection to a cell on an equal priority NR frequency shall be based on ranking for intra-frequency cell reselection.

[0079] If threshServingLowQ is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if: • The serving cell fulfils Squal < Threshs_emng, L_OWQ and a cell of a lower priority NR or E- UTRAN RAT/ frequency fulfils Squal > Threshx_. L_OWQ during a time interval TreselectionRAT.

[0080] Otherwise, cell reselection to a cell on a lower priority NR frequency or inter- RAT frequency than the serving frequency shall be performed if:

• The serving cell fulfils Srxlev < Threshs_emng, L_OWP and a cell of a lower priority RAT/ frequency fulfils Srxlev > Threshx_, L_OWP during a time interval TreselectionRAT; and

[0081] Cell reselection to a higher priority RAT/frequency shall take precedence over a lower priority RAT/frequency if multiple cells of different priorities fulfil the cell reselection criteria.

[0082] If more than one cell meets the above criteria, the UE shall reselect a cell as follows:

• If the highest-priority frequency is an NR frequency, the highest ranked cell among the cells on the highest priority frequency(ies) meeting the criteria;

• If the highest-priority frequency is from another RAT, the highest ranked cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT

[0083] Section 5.2.4.6 of Reference [2] discusses Intra-frequency and equal priority inter-frequency Cell Reselection criteria.

[0084] The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:

Rs ^— Qmcas.s tQhyst - Qoffsettemp Rn = Qmcas.n -Qoffset - Qoffsettemp where:

Qmeas RSRP measurement quantity used in cell reselections.

Qoffset For intra-frequency: Equals to Qoffset_s,n, if Qoffset_s,n is valid, otherwise this equals to zero.

For inter-frequency: Equals to Qoffset_s,n plus Qoffsetfreq_Uency, if Qoffset_s,n is valid, otherwise this equals to Qoffsetf_reqUency.

Qoffsettemp Offset temporarily applied to a cell as specified in TS 38.331. [0085] The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2.

[0086] The cells shall be ranked according to the R criteria specified above by deriving Qmeas.n and Qmeas.s and calculating the R values using averaged RSRP results.

[0087] If rangeToBestCell is not configured, the UE shall perform cell reselection to the highest ranked cell. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.

[0088] If rangeToBestCell is configured, then the UE shall perform cell reselection to the cell with the highest number of beams above the threshold (i.e. absThreshSS- BlocksConsolidation) among the cells whose Rvalue is within rangeToBestCell of the Rvalue of the highest ranked cell. If there are multiple such cells, the UE shall perform cell reselection to the highest ranked cell among them. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.

[0089] In all cases, the UE shall reselect the new cell, only if the following conditions are met:

• the new cell is better than the serving cell according to the cell reselection criteria specified above during a time interval TreselectionRAT;

Section 5.2.5 of Reference [2] discusses Camped Normally state.

[0090] This state is applicable for RRC IDLE and RRC INACTIVE state.

[0091] When camped normally, the UE shall perform the following tasks:

• monitor the paging channel of the cell as specified in clause 7 according to information broadcast in SIB1;

• monitor Short Messages transmitted with P-RNTI over DCI as specified in clause 6.5 in

TS 38.331;

• monitor relevant System Information as specified in TS 38.331;

• perform necessary measurements for the cell reselection evaluation procedure;

• execute the cell reselection evaluation process on the following occasions/triggers:

1) UE internal triggers, so as to meet performance as specified in TS 38.133;

When information on the BCCH used for the cell reselection evaluation procedure has been modified. [0092] Selection of cell at transition to RRC IDLE or R R C l N A C TI V E state is discussed in Section 5.2.6 of Reference [2]

[0093] At reception of RRCRelease message to transition the UE to RRC IDLE or R R C l N A C TI V E , UE shall attempt to camp on a suitable cell according to redirectedCarrierlnfo if included in the RRCRelease message. If the UE cannot find a suitable cell, the UE is allowed to camp on any suitable cell of the indicated RAT. If the RRCRelease message does not contain the redirectedCarrierlnfo, UE shall attempt to select a suitable cell on an NR carrier. If no suitable cell is found according to the above, the UE shall perform cell selection using stored information in order to find a suitable cell to camp on.

When returning to RRC IDLE state after UE moved to RRC CONNECTED state from camped on any cell state, UE shall attempt to camp on an acceptable cell according to redirectedCarrierlnfo, if included in the RRCRelease message. If the UE cannot find an acceptable cell, the UE is allowed to camp on any acceptable cell of the indicated RAT. If the RRCRelease message does not contain redirectedCarrierlnfo UE shall attempt to select an acceptable cell on an NR frequency. If no acceptable cell is found according to the above, the UE shall continue to search for an acceptable cell of any PLMN in state any cell selection.

[0094] Section 5.2.7 of Reference [2] discusses any Cell Selection state.

[0095] This state is applicable for RRC IDLE and RRC INACTIVE state. In this state, the UE shall perform cell selection process to find a suitable cell. If the cell selection process fails to find a suitable cell after a complete scan of all RATs and all frequency bands supported by the UE, the UE shall attempt to find an acceptable cell of any PLMN to camp on, trying all RATs that are supported by the UE and searching first for a high-quality cell, as defined in subclause 5.1.1.2.

[0096] The UE, which is not camped on any cell, shall stay in this state.

[0097] Section 5.2.8 of Reference [2] discusses Camped on Any Cell state.

[0098] This state is only applicable for RRC IDLE state. In this state, the UE shall perform the following tasks:

TS 38.331;

• monitor relevant System Information as specified in TS 38.331;

• perform necessary measurements for the cell reselection evaluation procedure; • execute the cell reselection evaluation process on the following occasions/triggers:

1) UE internal triggers, so as to meet performance as specified in TS 38.133;

2) When information on the BCCH used for the cell reselection evaluation procedure has been modified.

• regularly attempt to find a suitable cell trying all frequencies of all RATs that are supported by the UE. If a suitable cell is found, UE shall move to camped normally state.

[0099] Cell re-selection priorities are discussed below.

[0100] The cell re-selection priorities can be specified either in a dedicated manner (using RRCRelease when the UE is commanded to transition to a dormant state) or via broadcast using system information.

[0101] The ASN.1 structures for the NR RRCRelease message and the CellReslectionPriority and CellReselectionSubPriority elements are shown in Sections 6.2.2 and 6.3.2 of [4]

[0102] As shown in Sections 6.2.2 and 6.3.2 of [4], the UE can be provided with an optional cellReselectionPriorities that includes the list of NR or EUTRA frequencies, along with their priorities.

[0103] The cell selection priorities and/or additional information (E.g. threshold) can also be provided in system information, specifically, SIB2, SIB3, SIB4 and SIB5.

[0104] SIB2 contains cell re-selection information common for intra-frequency, inter- frequency and/or inter-RAT cell re-selection (i.e. applicable for more than one type of cell re selection but not necessarily all) as well as intra-frequency cell re-selection information other than neighbouring cell related. For example, the thresholds controlling whether intra and inter- frequency cell re-selection measurements should be performed (s-IntraSearchP, s-IntraSearchQ, s-NonlntraSearchP, s-NonlntraSearchQ) are included n SIB2.

[0105] SIB3 contains neighbouring cell related information relevant only for intra- frequency cell re-selection. The IE includes cells with specific re-selection parameters as well as blacklisted cells.

[0106] SIB4 contains information relevant only for inter-frequency cell re-selection i.e. information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection. The IE includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters. [0107] SIB5 contains information relevant only for inter-RAT cell re-selection i.e. information about E-UTRA frequencies and E-UTRAs neighbouring cells relevant for cell re selection. The IE includes cell re-selection parameters common for a frequency.

[0108] A UE in RRC IDLE or R R C l N A C TI V E will camp on the highest ranking cell, based on The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by (TS 38.304 vl5.2.0):

Rs ⁼ Qmcas.s +Qlyst Qoffsettemp Rn = Qmeas.n -Qoffset - Qoffsettemp where:

Qmeas RSRP measurement quantity used in cell reselections.

Qoffset For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this equals to zero.

For inter-frequency: Equals to Qoffsets,n plus Qoffsetfrequency, if Qoffsets,n is valid, otherwise this equals to Qoffsetfrequency. Qoffset_temp Offset temporarily applied to a cell as specified in TS 38.331.

In all cases, the UE shall reselect the new cell, only if the following conditions are met:

Qoffset_s.n This specifies the offset between the two cells.

Qoffsetfrequency Frequency specific offset for equal priority NR frequencies.

Q_hyst This specifies the hysteresis value for ranking criteria.

Qoffset_temp This specifies the additional offset to be used for cell selection and re-selection. It is temporarily used in case the RRC Connection Establishment fails on the cell as specified in TS 38.331.

Qquaimin This specifies the minimum required quality level in the cell in dB.

Qrxievmin This specifies the minimum required Rx level in the cell in dBm.

Qrxievminoff setceii This specifies the cell specific Rx level offset in dB to Qrxievmin. Qquaiminoff setceii This specifies the cell specific quality level offset in dB to Qquaimin. SUMMARY

[0109] When a logged MDT report is received by the network which is missing a measurement for a particular frequency, the network may be unable to determine whether the lack of measurement for the frequency is due to a coverage hole or due to a measurement configuration.

[0110] According to some embodiments of inventive concepts, a method is provided to operate a node of a wireless communication network. A logged measurement configuration is transmitted to a communication device. A release message is transmitted to the communication device, wherein the release message initiates transitioning of the communication device to a dormant state. After transmitting the release message, a resume message or a setup message is transmitted to the communication device, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state. After transmitting the resume message or the setup message, a logged measurement report is received from the communication device, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency.

[0111] According to some embodiments of inventive concepts, a method is provided to operate a communication device in communication with a node of a wireless communication network. A logged measurement configuration is received from the wireless communication network. A release message is received from the wireless communication network, wherein the release message initiates transitioning of the communication device to a dormant state. After receiving the release message and transitioning to the dormant state, a resume message or a setup message is received from the wireless communication network, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state. After receiving the resume message or the setup message, a logged measurement report is transmitted to the wireless communication network, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency.

[0112] According to some other embodiments of inventive concepts, related nodes, communication devices, computer programs and computer program products are also discussed. [0113] According to some embodiments, by providing an explicit indication for a coverage hole in a measurement report, ambiguity with respect to a frequency for which no measurement is received in the logged measurement report may be reduced. Accordingly, the network may be better able to identify and/or address coverage holes.

BRIEF DESCRIPTION OF THE DRAWINGS

[0114] 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:

[0115] Figure 1 is a diagram illustrating MAC control of grants for a cell and multiplexing of data;

[0116] Figure 2 is a message diagram illustrating UEInformationRequest and UEInformationResponse messages;

[0117] Figures 3 A and 3B provide a message diagrams illustrating early measurement reporting in FTE/NRIDFE mode in rel-16 during connection setup, option 1;

[0118] Figure 4 provides a message diagram illustrating early measurement reporting in FTE/NR IDEE mode in rel-16 during connection setup, option 2;

[0119] Figure 5 provides a message diagram illustrating early measurement reporting in FTE IDEE with suspended, LTE INACTIVE mode or NR INACTIVE mode in rel-16, option 1;

[0120] Figure 6 provides a message diagram illustrating early measurement reporting in LTE INACTIVE, LTE IDLE with suspended and NR INACTIVE mode in rel-16, option 2;

[0121] Figure 7 provides a timing diagram illustrating an example of MDT logging;

[0122] Figure 8 is a message diagram illustrating a LoggedMeasurementConfiguration message;

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

[0124] 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;

[0125] Figures 11, 12, 13, and 16 are flow charts illustrating operations of a communication device according to some embodiments of inventive concepts; [0126] Figures 14 and 15 are a flow charts illustrating operations of a network node according to some embodiments of inventive concepts;

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

[0128] Figure 18 is a block diagram of a user equipment in accordance with some embodiments

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

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

[0131] Figure 21 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;

[0132] Figure 22 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;

[0133] 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;

[0134] 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;

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

[0136] Figure 26 is a diagram illustrating a deployment where a UE performs logged MDT at different time instances according to some embodiments of inventive concepts.

DETAILED DESCRIPTION

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

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

[0139] Figure 9 is a block diagram illustrating elements of a communication device UE 300 (also referred to as a mobile terminal, a mobile communication terminal, a wireless communication device, a wireless device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Wireless device 300 may be provided, for example, as discussed below with respect to wireless device 4110 of Figure 17.) As shown, wireless device UE may include an antenna 307 (e.g., corresponding to antenna 4111 of Figure 17), and transceiver circuitry 301 (also referred to as a transceiver, e.g., corresponding to interface 4114 of Figure 17) 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 17, also referred to as a RAN node) of a radio access network. Wireless device UE may also include processing circuitry 303 (also referred to as a processor, e.g., corresponding to processing circuitry 4120 of Figure 17) coupled to the transceiver circuitry, and memory circuitry 305 (also referred to as memory, e.g., corresponding to device readable medium 4130 of Figure 17) coupled to the processing circuitry. The memory circuitry 305 may include computer readable program code that when executed by the processing circuitry 303 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 303 may be defined to include memory so that separate memory circuitry is not required. Wireless device UE may also include an interface (such as a user interface) coupled with processing circuitry 303, and/or wireless device UE may be incorporated in a vehicle.

[0140] As discussed herein, operations of wireless device UE may be performed by processing circuitry 303 and/or transceiver circuitry 301. For example, processing circuitry 303 may control transceiver circuitry 301 to transmit communications through transceiver circuitry 301 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 301 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 305, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 303, processing circuitry 303 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless devices).

[0141] Figure 10 is a block diagram illustrating elements of a radio access network RAN node 400 (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 400 may be provided, for example, as discussed below with respect to network node 4160 of Figure 17.) As shown, the RAN node may include transceiver circuitry 401 (also referred to as a transceiver, e.g., corresponding to portions of interface 4190 of Figure 17) 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 407 (also referred to as a network interface, e.g., corresponding to portions of interface 4190 of Figure 17) 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 405 (also referred to as memory, e.g., corresponding to device readable medium 4180 of Figure 17) coupled to the processing circuitry. The memory circuitry 405 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. [0142] As discussed herein, operations of the RAN node may be performed by processing circuitry 403, network interface 407, and/or transceiver 401. For example, processing circuitry 403 may control transceiver 401 to transmit downlink communications through transceiver 401 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 401 from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry 403 may control network interface 407 to transmit communications through network interface 407 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 405, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 403, processing circuitry 403 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes).

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

[0144] Neighbour cell measurements in the logged MDT are stored if available i.e., if there are no measurements on a certain frequency in the existing logged MDT report, it is not guaranteed that there is (or is not) coverage from that frequency. This could be caused from the lack of such frequency related measurement configuration in the inter-frequency/ inter-RAT SIBs. Therefore, the OAM is not sure if the lack of measurement on a frequency means lack of coverage or due to configuration associated to that frequency in SIBs or dedicated signalling.

[0145] To explain the problem further, consider a scenario wherein the UE is camping on frequency FI and the camped cell broadcasts F2, F3 and F4 related measurement information in its inter-frequency reselection SIBs (i.e. F2, F3 and F4 are candidate frequencies for cell re selection). Assume also that F4 is a high priority frequency and frequencies F2 and F3 are equal priority frequencies (but of lower priority than F4). In the current location where the UE is camping, there is no coverage from F3 and F4. Thus, the UE includes only the neighbour cell measurements associated to frequency FI and F2 as part of measResultNeighCells, and there is no indication about the coverage availability of F3 and F4. The OAM cannot deduce if there is coverage from these frequencies or not as the non-inclusion of these frequencies could be due to non-transmission of these frequencies as candidate frequencies for cell re-selection in the SIBs of the camped cell, due to priorities of the different frequencies broadcasted by the camped cell, rather than actually the UE experiencing coverage holes for those frequencies at that location.

[0146] Another example is, as described earlier, the UE’s cell re-selection measurement is controlled by several parameters such as the s-IntraSearchP, s-IntraSearchQ, s- NonlntraSearchP, and s-NonlntraSearchQ. That is, the UE may not have performed (new) cell re-selection measurements for a certain duration (and hence not having entries in the logged MDT for certain locations) due to excellent conditions at the current serving cell/frequency) and thus not including the neighbor cell measurements on neighbor frequencies cannot be seen as a direct implication of lack of coverage in those frequencies.

[0147] According to some embodiments of inventive concepts, methods may be provided wherein the UE could explicitly indicate the lack of coverage on a frequency wherein the UE has performed measurements but has not found any suitable cell.

[0148] According to some embodiments of inventive concepts, the UE may include the indicator in the logged measurement report about when there is no coverage available on frequencies on which the UE has performed measurements but has not found any cell.

[0149] Based on the logged measurement report containing an indicator about the lack of coverage of certain frequencies, the OAM may more accurately deduce that there is a coverage hole on that frequency in that location.

[0150] Some embodiments of inventive concepts may be equally applicable to LTE and NR. In the following embodiments, the terminologies used are for logged MDT reports, but the same can be applicable for any report from the UE where the network might benefit from knowing the lack of coverage on a configured frequency, e.g., early measurement reporting. The terms “frequency” and “carrier” are used interchangeably. The terms “released” and “suspended” are used interchangeably. The term “dormant state” is used to describe IDLE or INACTIVE states.

[0151] UE embodiments are discussed below.

[0152] The invention comprises methods executed by a user equipment (UE) in relation to measurements and measurement logging, specifically: • receiving a logged measurement configuration when the UE is in RRC CONNECTED, the measurement configuration includes one or more of the following: o areaConfiguration, specifying the set of cells/frequencies which indicates the UE to perform logging of MDT when the LIE is camping on these cells o Logging duration, specifying for how long the LIE should keep logging measurements o Logging interval, specifying the amount of time the LIE waits between logging the measurements while the logging duration still has not expired o Indication whether to report coverage holes, the indication being one or more of the following:

^■ A single indication/flag that is applicable for all frequencies to be logged in the logged MDT report;

^■ An indication could include a list of frequencies for which the coverage hole report logging is applicable (e.g. {fl, f2, f3}

^■ An indication could include one of more RATs for which the coverage hole report logging is applicable (e.g. and indication include EUTRA means all EUTRA frequencies will be considered)

^■ An indication could include time or location information, for example:

• A duration during which the coverage hole report logging should be performed

• A list of cells, RAN area information, tracking area information, etc... that specifies the UE should perform logging related to coverage holes only while in one of the specified cells, when it is within the current RAN/tracking area during which the coverage hole report logging should be performed

• Alternative to receiving the indication with the logged MDT configuration, the indication can be provided by other means, for example: o The indication can be included in the RRCConnectionRelease/RRCRelease message o Cells can broadcast in their system information whether coverage holes detected while the UE is camping in that cell should be logged or not o UEs can decide to perform coverage hole logging based on UE implementation, UE capability, information specified/hard-coded in 3GPP specifications, etc... o The indication can be included in the early measurement configuration (measIdleConfig).

• Transitioning to a dormant state (i.e. LTE/NR IDLE, LTE IDLE with suspended, LTE/NR INACTIVE) up on receiving an RRCConnectionRelease/RRCRelease message.

• While in the dormant state: o Performing the measurements on frequencies/RATs as specified by the cell reselection related SIBs. o At every logging interval, performing the logging of all available neighbor cell measurements and also about the frequencies where in the UE has performed measurements but has not found any cell,

• Transitioning to RRC CONNECTED state (e.g. upon the arrival of UL data, paging due to DL data, need to update tracking area, etc) o Sending the RRCConnectionResumeRequest/RRCResumeRequest or RRCConnectionSetupRequest/RRCSetupRequest message to the network o Transitioning to the RRC CONNECTED state upon receiving

RRConnectionResume/RRCResume or RRCConnectionSetup/RRCSetup message from the network

• Indicating the availability of logged MDT measurements in the RRCConnectionResume/RRCResume, RRCReestablishmentComplete/ RRCConnectionReestablishmentComplete, RRCReconfigurationComplete/ RRCConnectionReconfigurationComplete or RRCConnectionSetup/RRCSetup message via logMeasAvailable flag.

• Receiving a UEInformationRequest that includes the logMeasReportReq, and reporting the logged MDT measurements in UEInformationResponse, which includes measurements performed based on LoggedMeasurementConfiguration.

Network embodiments are discussed below.

[0153] The invention comprises several methods executed by a network node in relation easurements and measurement logging by a UE, specifically: • Configuring the UE with a logged measurement configuration that includes one or more of the following: o areaConfiguration, specifying the set of cells/frequencies which indicates the UE to perform logging of MDT when the UE is camping on these cells. o Logging duration, specifying for how long the UE should keep logging measurements o Logging interval, specifying the amount of time the UE waits between logging the measurements while the logging duration still has not expired o Indication regarding the logging of coverage holes

• Instructing the UE to transition to a dormant state (i.e. LTE/NR IDLE, LTE IDLE with suspended, LTE/NR INACTIVE) by sending an RRCConnectionRelease/RRCRelease message o Which could include indication regarding the logging of coverage holes

• Broadcasting in the system information indication regarding the logging of coverage holes

• Instructing the UE to transition to RRC CONNECTED state by sending RRCConnectionResume/RRCResume or RRCConnectionSetup/RRCSetup message

• Receiving an indication from the UE about the availability of logged measurements via the logMeasAvailable flag in the RRCConnectionResume/RRCResume, RRCReestablishmentComplete/ RRCConnectionReestablishmentComplete, RRCReconfigurationComplete/ RRCConnectionReconfigurationComplete or RRCConnectionSetup/RRCSetup message.

• Sending a UEInformationRequest that includes the logMeasReportReq o In some embodiments, this request includes an explicit indication to log the coverage hole reports whereas in some other embodiments there is no explicit requesting of coverage hole related reports and the UE is expected to include the coverage hole related report whenever the network requests the logMeasReportReq.

• Receiving the logged MDT measurements in UEInformationResponse message from the UE, which includes measurements performed based on

LoggedMeasurementConfiguration, including information regarding coverage holes. [0154] Additional Embodiments are discussed below.

[0155] Instead of UE including the indicator regarding the lack of coverage on a frequency at every logged MDT sample, the UE logs a list of the frequencies on which it is performing measurements while camping in a cell. If the UE has not included any logged MDT measurements associated to these frequencies, then it is an implicit indication to the OAM that there is no coverage on these frequencies.

[0156] Mechanisms have also been discussed to include early measurements in the logged MDT report. Embodiments of inventive concepts may be equally applicable for such measurements as well. For example, if a UE is reported to perform early measurements on frequencies fl and f2, and the UE is able to detect a neighbor cell operating on fl but not f2, the UE includes that it has detected a coverage hole regarding f2 when it includes the early measurement results in the logged MDT report.

[0157] An example realization according to some embodiments is illustrated below in Table 5 which provide an example ASN.1 coding to enable some embodiments of inventive concepts for NR (i.e., 3 GPP TS 38.331).

Table 5

_

[0158] Another example realization according to some embodiments is illustrated in Table 6 which provide example ASN.1 coding to enable additional embodiments of inventive concepts for NR (i.e. 38.331).

Table 6

_ _

[0159] The running CR on the RRC specification for MDT and SON (Reference [3]) captures the contents of the logged MDT report. The logged MDT report contains cell level and beam level measurements of the serving cell (camped cell) and neighbor cells, location information, sensor measurements etc. In this disclosure, the neighbor cells’ related information that is stored in the logged MDT is discussed and what could be added is analyzed.

[0160] Consider the deployment shown in Figure 26 which shows a UE performing the logged MDT at different time instances (T1 to T7). The deployment includes two frequencies FI and F2. The UE is currently camping on FI.

[0161] Consider that the UE is configured with the same reselection priorities for both FI and F2. In such a scenario, the UE performs serving cell measurements on FI and it shall also perform neighbor cell measurements on both FI and F2 all the time (assuming there is no s- NonlntraSearchP or s-IntraSearchP are configured). In such a scenario, the UE shall include the following measurements of Table 7 at each of the time samples (T1 to T7). Table 7.

Measurements at Time Samples T1 to T7.

[0162] An observation is that at time instances T3, T4 and T5, the UE has not included the F2 related measurements as part of neighbor cell measurements in the logged MDT report. The OAM may be unable to directly interpret that there is no coverage from F2 at the locations associated with T3, T4 and T5 as the UE might have been configured with a cell reselection priority which did not mandate the UE to perform measurements on F2.

Observation 1 Lack of neighbor frequency measurements on a particular frequency in the logged MDT may not imply that there is no coverage in that frequency as the UE might not be performing measurements on that frequency as the UE might have been configured with a cell reselection priority which did not mandate the UE to perform measurements on that frequency.

[0163] According to some embodiments, if the UE performs measurements on a frequency, as per the reselection related frequency priority configuration, and the UE does not detect any SSBs on that frequency, then the UE can include an indicator in the neighbor cell related measurements’ of logged MDT that there is no coverage from that frequency at that location. This may be beneficial for the operators to identify the coverage holes in different frequencies using the logged MDT report.

Proposal 1 According to some embodiments, an indicator may be included in the logged MDT report associated with neighbor frequencies on which the UE has performed measurements and has not detected any SSBs.

[0164] In the example scenario above, it was assumed that s-NonlntraSearchP or s- IntraSearchP are bit configured. This is not a limiting scenario. If the camped cell has configured s-NonlntraSearchP or s-IntraSearchP, then the UE does not include the above proposed flag if the UE does not even perform the neighbor frequency measurements due to the excellent quality of the camped cell.

[0165] The implementation of such an indicator in the RRC specification is provided in the UEInformationResponse message illustrated below in Table 8.

Table 8

_ _

[0166] Regarding the UEInformation Response message of Table 8, field descriptions are discussed below: logMeasReport:

This field is used to provide the measurement results stored by the UE associated to logged MDT. rach-Report: This field is used to provide the list of RACH reports that is stored by the UE for the past upto maxRACHReport number of successful RACH procedures. rlf-Report: This field is used to indicate the RLF report related contents.

[0167] Regarding the UEInformation Response message of Table 8, LogMeasReport field descriptions are discussed below: absoluteTimeStamp :

Indicates the absolute time when the logged measurement configuration logging is provided, as indicated by E-UTRAN within absoluteTimelnfo. logMeasResultListBT:

This field refers to the Bluetooth measurement results. logMeasResultListWLAN :

This field refers to the WLAN measurement results. measResultServCell:

This field refers to the log measurement results taken in the Serving cell. noCoverage: This field is set to true when the UE performs measurements on the associated frequency (ssbFrequency) but fails to detect any SSBs on that frequency. relativeTimeS tamp :

Indicates the time of logging measurement results, measured relative to the absoluteTimeStamp. Value in seconds. tce-Id: Parameter Trace Collection Entity Id: See TS 32.422 [x4] timeStamp: Includes time stamps for the waypoints that describe planned locations for the UE. traceRecordingSessionRef:

Parameter Trace Recording Session Reference: See TS 32.422 [x4]

[0168] Regarding the UEInformation Response message of Table 8, ConnEstFailReport field descriptions are discussed below: measResultFailedCell :

This field refers to the last measurement results taken in the cell, where connection establishment failure happened. measResultNeighCells:

This field refers to the neighbour cell measurements when connection establishment failure happened. numberOfConnFailPerCell:

This field is used to indicate the number of failed connection setup attempts per cell after radio link failure. numberOfPreamblesSent:

This field is used to indicate the number of RACH preambles that were transmitted. maxTxPowerReached:

This field is used to indicate whether or not the maximum power level was used for the last transmitted preamble. timeSinceFailure: This field is used to indicate the time that elapsed since the connection (establishment) failure. Value in seconds. The maximum value 172800 means 172800s or longer.

[0169] Regarding the UEInformation Response message of Table 8, RACH-Report field descriptions are discussed below: absoluteFrequencyPointA

This field indicates the absolute frequency position of the reference resource block (Common RB 0). celllD

This field indicates the CGI of the cell in which the associated random access procedure was performed. contentionDetected

This field is used to indicate that contention was detected for the transmitted preamble in the given RACH attempt or not. csi-RS-Index

This field is used to indicate the CSI-RS index corresponding to the random access attempt. dlRSRPQualitylndicator

This field is used to indicate whether the DL beam (SSB or CSI-RS) qualtiy associated to the random access attempt was above or below the threshold (rsrp-ThresholdSSB when NUL is used and rsrp-ThresholdSSB- SUL when SUL is used). locationAnfBandwidth

Frequency domain location and bandwidth of the bandwidth part associated to the random-access resources used by the UE. msgl -FrequencyStart

Offset of lowest PRACH transmission occasion in frequency domain with respective to PRB 0 of the UL BWP. msgl -SubcarrierSpacing

Subcarrier spacing of PRACH resources. numberOfPreamblesSentOnCSI-RS

This field is used to indicate the total number of successive RACH preambles that were transmitted on the corresponding CSI-RS. numberOfPreambles S entOnS SB

This field is used to indicate the total number of successive RACH preambles that were transmitted on the corresponding SSB/PBCH block. perRACHAttemptlnfoList

This field provides detailed information about a RACH attempt. perRACHInfoList

This field provides detailed information about each of the RACH attempts in the chronological order of the RACH attempts. perRACHCSI-RSInfoList

This field provides detailed information about the successive random access attempts associated to the same CSI-RS. perRACHS SBInfoList

This field provides detailed information about the successive random access attempts associated to the same SS/PBCH block. rachPurpose

This field is used to indicate the RACH scenario for which the RACH report entry is triggered. The RACH accesses associated to Initial access from RRC IDLE, transition from RRC-INACTIVE and the MSG3 based SI request are indicated using the indicator ‘accessRelated’. ssb-Index

This field is used to indicate the SS/PBCH index of the SS/PBCH block corresponding to the random access attempt. ssbRSRPQualitylndicator

This field is used to indicate the SS/PBCH RSRP of the SS/PBCH block corresponding to the random access attempt is above rsrp-ThresholdSSB or not. subcarrierSpacing Subcarrier spacing used in the BWP associated to the random-access resources used by the UE.

[0170] Regarding the UEInformation Response message of Table 8, RLF-Report field descriptions are discussed below: connectionFailureType

This field is used to indicate whether the connection failure is due to radio link failure or handover failure. csi-rsRLMConfigBitmap

This field is used to indicate the CSI-RS indexes that are also part of the RLM configurations. c-RNTI

This field indicates the C-RNTI used in the PCell upon detecting radio link failure or the C-RNTI used in the source PCell upon handover failure. failedCellld

This field is used to indicate the cell in which connection establishment failed. failedPCellld

This field is used to indicate the PCell in which RLF is detected or the target PCell of the failed handover. The UE sets the ARFCN according to the band used for transmission/ reception when the failure occurred. measResultLastS ervCell

This field refers to the last measurement results taken in the PCell, where radio link failure or handover failure happened. measResultListEUTRA

This field refers to the last measurement results taken in the neighboring EUTRA Cells, when the radio link failure or handover failure happened. measResultListNR

This field refers to the last measurement results taken in the neighboring NR Cells, when the radio link failure or handover failure happened. measResultS ervCell

This field refers to the log measurement results taken in the Serving cell. previousPCellld

This field is used to indicate the source PCell of the last handover (source PCell when the last RRCReconfiguration message including reconfigurationWithSync was received). reestablishmentCellld

This field is used to indicate the cell in which the re-establishment attempt was made after connection failure. rlf-Cause

This field is used to indicate the cause of the last radio link failure that was detected. In case of handover failure information reporting (i.e., the connectionFailureType is set to 'hof ), the UE is allowed to set this field to any value. ssbRLMConfigBitmap

This field is used to indicate the SS/PBCH block indexes that are also part of the RLM configurations. timeConnFailure

This field is used to indicate the time elapsed since the last HO initialization until connection failure. Actual value = field value * 100ms. The maximum value 1023 means 102.3s or longer. timeSinceFailure

This field is used to indicate the time that elapsed since the connection (establishment) failure. Value in seconds. The maximum value 172800 means 172800s or longer.

[0171] Operations of the communication device 300 (implemented using the structure of the block diagram of Figure 9) will now be discussed with reference to the flow chart of Figure 11 according to some embodiments of inventive concepts. For example, modules may be stored in memory 305 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 303, processing circuitry 303 performs respective operations of the flow chart. [0172] At block 2601, processing circuitry 303 may receive (through transceiver 301) a logged measurement configuration from the wireless communication network, and the logged measurement configuration may include an indication to report coverage holes.

[0173] At block 2603, processing circuitry 303 may receive (through transceiver 301) a release message. For example, the release message may be a Radio Resource Control RRC connection release message or an RRC release message.

[0174] At block 2605, processing circuitry 303 may transition to a dormant state in response to receiving the release message.

[0175] Responsive a timer indicating occurrence of a logging interval at block 2607, processing circuitry 303 may proceed with measurements as discussed with respect to blocks 2609, 2611, 2615, and 2617.

[0176] At block 2609, processing circuitry 303 may perform measurements for a plurality of frequencies at a first logging interval while in the dormant state to generate a received signal measurement for a first frequency of the plurality of frequencies.

[0177] At blocks 2611 and 2615, processing circuitry may identify a coverage hole for a second frequency of the plurality of frequencies at the first logging interval.

[0178] At block 2617, processing circuitry may log first results of the measurements for the plurality of frequencies in memory (305) of the communication device, wherein the first results include the received signal measurement for the first frequency and an indication of the coverage hole for the second frequency.

[0179] At block 2619, processing circuitry 303 may determine whether a transition to connected state has occurred. Accordingly, any number of measurements may be performed at respective logging intervals as discussed above with respect to blocks 2609, 2611, 2615, 2617, and 2619 as long as communication device 300 remains in the dormant state.

[0180] Accordingly, at block 2609, processor 303 may perform measurements for the plurality of frequencies at a second logging interval to provide second results regarding the first and second frequencies while still in the dormant state.

[0181] At block 2617, processing circuitry 303 may log the second results regarding the first and second frequencies in the memory of the communication device.

[0182] At block 2619, processing circuitry 303 may transition to a connected state. [0183] Once the communication device has transitioned to the connected state at block 2619, processing circuitry may at block 2623, transmit (through transceiver 301) a logged measurement report to the communication network while in the connected state, wherein the logged measurement report includes the first results including the received signal measurement for the first frequency and the indication of the coverage hole for the second frequency and the second results of the second logging interval. In addition, the indication of the coverage hole for the second frequency may be included in the logged measurement report responsive to the indication to report coverage holes.

[0184] Various operations from the flow chart of Figure 11 may be optional with respect to some embodiments of wireless devices and related methods. Regarding methods of example embodiment 1 (set forth below), for example, operations of blocks 2603, 2607, and/or 2611 of Figure 11 may be optional.

[0185] Operations of the communication device 300 (implemented using the structure of the block diagram of Figure 9) will now be discussed with reference to the flow chart of Figure 12 according to some embodiments of inventive concepts. For example, modules may be stored in memory 305 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 303, processing circuitry 303 performs respective operations of the flow chart.

[0186] At block 2701, processing circuitry 303 may receive (through transceiver 301) a logged measurement configuration from the wireless communication network.

[0187] At block 2703, processing circuitry 303 may receive (through transceiver 301) a release message including an indication to report coverage holes. For example, the release message may be a Radio Resource Control RRC connection release message or an RRC release message.

[0188] At block 2705, processing circuitry 303 may transition to a dormant state in response to receiving the release message.

[0189] Responsive a timer indicating occurrence of a logging interval at block 2707, processing circuitry 303 may proceed with measurements as discussed with respect to blocks 2709, 2711, 2715, and 2717. [0190] At block 2709, processing circuitry 303 may perform measurements for a plurality of frequencies at a first logging interval while in the dormant state to generate a received signal measurement for a first frequency of the plurality of frequencies.

[0191] At blocks 2711 and 2715, processing circuitry 303 may identify a coverage hole for a second frequency of the plurality of frequencies at the first logging interval.

[0192] At block 2717, processing circuitry 303 may log first results of the measurements for the plurality of frequencies in memory (305) of the communication device, wherein the first results include the received signal measurement for the first frequency and an indication of the coverage hole for the second frequency.

[0193] At block 2719, processing circuitry 303 may determine whether a transition to connected state has occurred. Accordingly, any number of measurements may be performed at respective logging intervals as discussed above with respect to blocks 2709, 2711, 2715, 2717, and 2719 as long as communication device 300 remains in the dormant state.

[0194] Accordingly, at block 2709, processor 303 may perform measurements for the plurality of frequencies at a second logging interval to provide second results regarding the first and second frequencies while still in the dormant state.

[0195] At block 2717, processing circuitry 303 may log the second results regarding the first and second frequencies in the memory of the communication device.

[0196] At block 2719, processing circuitry 303 may transition to a connected state.

[0197] Once the communication device has transitioned to the connected state at block 2719, processing circuitry 303 may, at block 2723, transmit (through transceiver 301) a logged measurement report to the communication network while in the connected state, wherein the logged measurement report includes the first results including the received signal measurement for the first frequency and the indication of the coverage hole for the second frequency and the second results of the second logging interval. In addition, the indication of the coverage hole for the second frequency may be included in the logged measurement report responsive to the indication to report coverage holes.

[0198] Various operations from the flow chart of Figure 12 may be optional with respect to some embodiments of wireless devices and related methods. Regarding methods of example embodiment 1 (set forth below), for example, operations of blocks 2703, 2707, and/or 2711 of Figure 12 may be optional. [0199] Operations of the communication device 300 (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 305 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 303, processing circuitry 303 performs respective operations of the flow chart.

[0200] At block 2801, processing circuitry 303 may receive (through transceiver 301) a logged measurement configuration from the wireless communication network.

[0201] At block 2802, processing circuitry 330 may receive an indication to report coverage holes. For example, the indication to report coverage holes may be received as an element of system information broadcast from the wireless communication network, or the indication to report coverage holes may be received as an element of an early measurement configuration.

[0202] At block 2803, processing circuitry 303 may receive (through transceiver 301) a release message. For example, the release message may be a Radio Resource Control RRC connection release message or an RRC release message.

[0203] At block 2805, processing circuitry 303 may transition to a dormant state in response to receiving the release message.

[0204] Responsive a timer indicating occurrence of a logging interval at block 2807, processing circuitry 303 may proceed with measurements as discussed with respect to blocks 2809, 2811, 2815, and 2817.

[0205] At block 2809, processing circuitry 303 may perform measurements for a plurality of frequencies at a first logging interval while in the dormant state to generate a received signal measurement for a first frequency of the plurality of frequencies.

[0206] At blocks 2811 and 2815, processing circuitry 303 may identify a coverage hole for a second frequency of the plurality of frequencies at the first logging interval.

[0207] At block 2817, processing circuitry 303 may log first results of the measurements for the plurality of frequencies in memory (305) of the communication device, wherein the first results include the received signal measurement for the first frequency and an indication of the coverage hole for the second frequency. [0208] At block 2819, processing circuitry 303 may determine whether a transition to connected state has occurred. Accordingly, any number of measurements may be performed at respective logging intervals as discussed above with respect to blocks 2809, 2811, 2815, 2817, and 2819 as long as communication device 300 remains in the dormant state.

[0209] Accordingly, at block 2809, processor 303 may perform measurements for the plurality of frequencies at a second logging interval to provide second results regarding the first and second frequencies while still in the dormant state.

[0210] At block 2817, processing circuitry 303 may log the second results regarding the first and second frequencies in the memory of the communication device.

[0211] At block 2819, processing circuitry 303 may transition to a connected state.

[0212] Once the communication device has transitioned to the connected state at block 2819, processing circuitry may at block 2823, transmit (through transceiver 301) a logged measurement report to the communication network while in the connected state, wherein the logged measurement report includes the first results including the received signal measurement for the first frequency and the indication of the coverage hole for the second frequency and the second results of the second logging interval. In addition, the indication of the coverage hole for the second frequency may be included in the logged measurement report responsive to receiving the indication to report coverage holes.

[0213] Various operations from the flow chart of Figure 13 may be optional with respect to some embodiments of wireless devices and related methods. Regarding methods of example embodiment 1 (set forth below), for example, operations of blocks 2802, 2803, 2807, and/or 2811 of Figure 13 may be optional.

[0214] Operations of a RAN node 400 (implemented using the structure of Figure 10) will now be discussed with reference to the flow chart of Figure 14 according to some embodiments of inventive concepts. For example, modules may be stored in memory 405 of Figure 10, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 403, processing circuitry 403 performs respective operations of the flow chart.

[0215] At block 2901, processing circuitry 403 may transmit (through transceiver 401) a logged measurement configuration to a communication device. [0216] At block 2905, processing circuitry 403 may transmit (through transceiver 401) a release message to the communication device, wherein the release message initiates transitioning of the communication device to a dormant state.

[0217] At block 2907, processing circuitry 403 may transmit (through transceiver 401) a resume message or a setup message to the communication device after transmitting the release message (e.g., responsive to a request from the communication device), wherein the resume message or the setup message initiates transitioning of the communication device to a connected state; and

[0218] At block 2909, processing circuitry 303 may receive (through transceiver 401) a logged measurement report from the communication device after transmitting the resume message or the setup message, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency.

[0219] According to some embodiments, the logged measurement configuration may include an indication to report coverage holes. According to some other embodiments the release message may include an indication to report coverage holes.

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

[0221] Operations of a RAN node 400 (implemented using the structure of Figure 10) 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 405 of Figure 10, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 403, processing circuitry 403 performs respective operations of the flow chart.

[0222] At block 3001, processing circuitry 403 may transmit (through transceiver 401) a logged measurement configuration to a communication device.

[0223] At block 3003, processing circuitry 403 may transmit (through transceiver 401) an indication to report coverage holes to the communication device.

[0224] At block 3005, processing circuitry 403 may transmit (through transceiver 401) a release message to the communication device, wherein the release message initiates transitioning of the communication device to a dormant state. [0225] At block 3007, processing circuitry 403 may transmit (through transceiver 401) a resume message or a setup message to the communication device after transmitting the release message, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state.

[0226] At block 3009, processing circuitry 403 may receive (through transceiver 401) a logged measurement report from the communication device after transmitting the resume message or the setup message, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency.

[0227] According to some embodiments, the indication to report coverage holes may be transmitted as an element of system information that is broadcast from the wireless communication network. According to some other embodiments, the indication to report coverage holes may be transmitted as an element of an early measurement configuration.

[0228] Various operations from the flow chart of Figure 15 may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiment 27 (set forth below), for example, operations of block 3003 of Figure 15 may be optional.

[0229] Operations of the communication device 300 (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 305 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 303, processing circuitry 303 performs respective operations of the flow chart.

[0230] At block 3051, processing circuitry 303 may receive (through transceiver 301) a logged measurement configuration from the wireless communication network.

[0231] At block 3053, processing circuitry 303 may receive (through transceiver 301) an indication to report coverage holes from the wireless communication network.

[0232] At block 3055, processing circuitry 303 may receive (through transceiver 301) a release message from the wireless communication network. The release message initiates transitioning of the communication device to a dormant state, and at block 3056, processing circuitry 303 may transition to the dormant state in response to receiving the release message. [0233] At block 3057, processing circuitry 303 may perform measurements for a plurality of frequencies including first and second frequencies while in the dormant state.

[0234] At block 3067, processing circuitry 303 may receive (through transceiver 301) a resume message or a setup message from the wireless communication network after receiving the release message and transitioning to the dormant state. The resume message or the setup message initiates transitioning of the communication device to a connected state, and at block 3068, processing circuitry 303 may transition to the connected state in response to receiving the resume message.

[0235] At block 3069, processing circuitry 303 may transmit (through transceiver 301) a logged measurement report to the wireless communication network after receiving the resume message or the setup message. The logged measurement report includes a received signal measurement for the first frequency and an indication of a coverage hole for the second frequency.

[0236] According to some embodiments, the indication to report coverage holes may be included in the logged measurement configuration or in the release message. According to some embodiments, the indication to report coverage holes may include a list of frequencies for which coverage hole reporting is applicable, and the second frequency may be included in the list of frequencies for which coverage hole reporting is applicable. According to some embodiments, the indication to report coverage holes may include an indication of a Radio Access Technology RAT for which coverage hole reporting is applicable, and the second frequency may be a frequency of the RAT.

[0237] Various operations from the flow chart of Figure 16 may be optional with respect to some embodiments of wireless devices and related methods. For example, operations of blocks 3053, 3056, 3057, and/or 3068 of Figure 16 may be optional.

[0238] Example embodiments are discussed below.

1. A method of operating a communication device (300) in communication with a wireless communication network, the method comprising: receiving (2601, 2701, 2801) a logged measurement configuration from the wireless communication network; transitioning (2605,

2705, 2805) to a dormant state; performing (2609, 2709, 2809) measurements for a plurality of frequencies while in the dormant state to generate a received signal measurement for a first frequency of the plurality of frequencies; identifying (2615, 2715, 2815) a coverage hole for a second frequency of the plurality of frequencies; logging (2617, 2717, 2817) results of the measurements for the plurality of frequencies in memory (305) of the communication device, wherein the results include the received signal measurement for the first frequency and an indication of the coverage hole for the second frequency; transitioning (2619, 2719, 2819) to a connected state; and transmitting (2623, 2723, 2823) a logged measurement report to the communication network while in the connected state, wherein the logged measurement report includes the received signal measurement for the first frequency and the indication of the coverage hole for the second frequency.

2. The method of Embodiment 1, wherein the logged measurement configuration includes an indication to report coverage holes, and wherein the indication of the coverage hole for the second frequency is included in the logged measurement report responsive to the indication to report coverage holes.

3. The method of Embodiment 1 further comprising: receiving (2703) a release message including an indication to report coverage holes; wherein the indication of the coverage hole for the second frequency is included in the logged measurement report responsive to the indication to report coverage holes; wherein transitioning to the dormant state is in response to receiving the release message.

4. The method of Embodiment 3, wherein the release message comprises a Radio Resource Control, RRC, connection release message or an RRC release message.

5. The method of Embodiment 1 further comprising: receiving (2802) an indication to report coverage holes; wherein the indication of the coverage hole for the second frequency is included in the logged measurement report responsive to receiving the indication to report coverage holes.

6. The method of Embodiment 5, wherein receiving the indication to report coverage holes comprises receiving the indication to report coverage holes as an element of system information broadcast from the wireless communication network.

7. The method of Embodiment 5, wherein receiving the indication to report coverage holes comprises receiving the indication to report coverage holes as an element of an early measurement configuration.

8. The method of any of Embodiments 2-7, wherein the indication to report coverage holes includes a list of frequencies for which coverage hole reporting is applicable, and wherein the logged measurement report includes the indication of the coverage hole for the second frequency responsive to the second frequency being included in the list of frequencies for which coverage hole reporting is applicable.

9. The method of any of Embodiments 2-8, wherein the indication to report coverage holes includes an indication of a Radio Access Technology, RAT, for which coverage hole reporting is applicable, and wherein the logged measurement report includes the indication of the coverage hole for the second frequency responsive to the second frequency being a frequency of the RAT.

10. The method of any of Embodiments 2-9, wherein the indication to report coverage holes defines a time period for which coverage hole reporting is applicable, and wherein the logged measurement report includes the indication of the coverage hole for the second frequency responsive to performing the measurements for the plurality of frequencies including the second frequency during the time for which coverage hole reporting is applicable.

11. The method of any of Embodiments 2-10, wherein the indication to report coverage holes includes location information at which coverage hole reporting is applicable, and wherein the logged measurement report includes the indication of the coverage hole for the second frequency responsive to performing the measurements for the plurality of frequencies including the second frequency at a location defined according to the location information.

12. The method of Embodiment 11, wherein the location information includes at least one of a list of cells, Radio Access Network, RAN, area information, and/or tracking area information, and wherein the logged measurement report includes the indication of the coverage hole for the second frequency responsive to performing the measurement for the plurality of frequencies including the second frequency while in a cell associated with the list of cells, the RAN area information, and/or the tracking area information.

13. The method of any of Embodiments 1-12, wherein transitioning to the dormant state comprises transitioning to the dormant state responsive to receiving a release message from the wireless communication network.

14. The method of Embodiment 13, wherein the release message comprises a Radio Resource Control, RRC, release message or an RRC connection release message. 15. The method of any of Embodiments 1-14, wherein transitioning to the connected state comprises transitioning to the connected state responsive to receiving a resume message or a setup message from the wireless communication network.

16. The method of Embodiment 15, wherein the resume message comprises a Radio Resource Control, RRC, connection resume message or an RRC resume message, or wherein the setup message comprises an RRC connection setup message or an RRC setup message.

17. The method of any of Embodiments 1-16, wherein the logged measurement report is transmitted responsive to receiving an information request from the wireless communication network.

18. The method of any of Embodiments 1-17, wherein the logged measurement configuration includes an area configuration defining a set of frequencies, and wherein the measurements are performed for the plurality of frequencies responsive to the plurality of frequencies being included in the set.

19. The method of any of Embodiments 1-18, wherein the logged measurement configuration includes a logging duration defining a duration over which measurements should be logged, and wherein the measurements are performed for the plurality of frequencies during the logging duration.

20. The method of any of Embodiments 1-19, wherein the logged measurement configuration includes a logging interval defining a period between measurements of the logged measurement configuration, and wherein the measurements are performed for the plurality of frequencies in accordance with the logging interval.

21. The method of Embodiment 20, wherein the plurality of frequencies are measured at a first logging interval to provide first results including the received signal measurement for the first frequency and the indication of the coverage hole detected for the second frequency, wherein logging results comprises logging the first results, the method further comprising: performing (2609, 2709, 2809) measurements for the plurality of frequencies at a second logging interval to provide second results regarding the first and second frequencies; and logging (2617, 2717, 2817) the second results regarding the first and second frequencies in the memory of the communication device; wherein the logged measurement report includes the first results of the first logging interval and the second results of the second logging interval. 22. The method of any of Embodiments 1-21, wherein the logged measurement configuration comprises a logged Minimization of Drive Test, MDT, measurement configuration, and wherein the logged measurement report comprises a logged MDT measurement report.

23. The method of any of Embodiments 1-22, wherein the dormant state comprises an idle state or an inactive state.

24. The method of any of Embodiments 1-23, where the coverage hole is identified for the second frequency responsive to the communication device failing to detect a cell on the second frequency that satisfies a power threshold and/or quality threshold. (For example, the communication device UE may declare that it has detected a coverage hole on a frequency when the UE fails to find any cell on that frequency which satisfies the frequency specific s-criterion (measured RSRP to be above q-RxLevMin and measured RSRQ to be above q-QualMin) as broadcast by the camped cell.)

25. The method of any of Embodiments 1-24, wherein the coverage hole is identified for the second frequency responsive to the communication device failing to detect a synchronization block on the second frequency. (For example, the communication device UE may declare that it has detected a coverage hole on a frequency when the UE fails to detect any SSBs (synchronized signal blocks) on that frequency.)

26. The method of any of Embodiments 1-25, wherein the received signal measurement for the first frequency comprises a received signal quality and/or power measurement for the first frequency.

27. A method of operating a node of a wireless communication network, the method comprising: transmitting (2901, 3001) a logged measurement configuration to a communication device; transmitting (2905, 3005) a release message to the communication device, wherein the release message initiates transitioning of the communication device to a dormant state; after transmitting the release message, transmitting (2907, 3007) a resume message or a setup message to the communication device, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state; and after transmitting the resume message or the setup message, receiving (2909, 3009) a logged measurement report from the communication device, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency. 28. The method of Embodiment 27, wherein the logged measurement configuration includes an indication to report coverage holes.

29. The method of Embodiment 27, wherein the release message includes an indication to report coverage holes.

30. The method of Embodiment 27 further comprising: transmitting (3003) an indication to report coverage holes to the communication device.

31. The method of Embodiment 30, wherein the indication to report coverage holes is transmitted as an element of system information that is broadcast from the wireless communication network.

32. The method of Embodiment 30, wherein the indication to report coverage holes is transmitted as an element of an early measurement configuration.

33. The method of any of Embodiments 28-32, wherein the indication to report coverage holes includes a list of frequencies for which coverage hole reporting is applicable, and wherein the second frequency is included in the list of frequencies for which coverage hole reporting is applicable.

34. The method of any of Embodiments 28-33, wherein the indication to report coverage holes includes an indication of a Radio Access Technology, RAT, for which coverage hole reporting is applicable, and wherein the second frequency is a frequency of the RAT.

35. The method of any of Embodiments 28-34, wherein the indication to report coverage holes includes a time during which coverage hole reporting is applicable.

36. The method of any of Embodiments 28-35, wherein the indication to report coverage holes includes location information at which coverage hole reporting is applicable.

37. The method of Embodiment 36, wherein the location information includes at least one of a list of cells, Radio Access Network, RAN, area information, and/or tracking area information.

38. The method of any of Embodiments 27-37, wherein the resume message comprises a Radio Resource Control, RRC, connection resume message or an RRC resume message, or wherein the setup message comprises an RRC connection setup message or an RRC setup message.

39. The method of any of Embodiments 27-38, wherein the release message comprises a Radio Resource Control, RRC, connection release message or an RRC release message. 40. The method of any of Embodiments 27-39 further comprising: transmitting an information request to the communication device after transmitting the resume message or the setup message, to initiate transmission of the logged measurement report by the communication device.

41. The method of any of Embodiments 27-40, wherein the logged measurement configuration includes an area configuration defining a set of frequencies, and wherein the first and second frequencies are included in the set.

42. The method of any of Embodiments 27-41, wherein the logged measurement configuration includes a logging duration defining a duration over which measurements should be logged.

43. The method of any of Embodiments 27-42, wherein the logged measurement configuration includes a logging interval defining a period between measurements of the logged measurement configuration.

44. The method of any of Embodiments 27-43, wherein the logged measurement configuration comprises a logged Minimization of Drive Test, MDT, measurement configuration, and wherein the logged measurement report comprises a logged MDT measurement report.

45. The method of any of Embodiments 27-44, wherein the dormant state comprises an idle state or an inactive state.

46. The method of any of Embodiments 27-45, wherein the received signal measurement for the first frequency comprises a received signal quality and/or power measurement for the first frequency.

47. A method of operating communication device in communication with a node of a wireless communication network, the method comprising: receiving a logged measurement configuration from the wireless communication network; receiving a release message from the wireless communication network, wherein the release message initiates transitioning of the communication device to a dormant state; after receiving the release message and transitioning to the dormant state, receiving a resume message or a setup message from the wireless communication network, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state; and after receiving the resume message or the setup message, transmitting a logged measurement report to the wireless communication network, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency.

48. The method of Embodiment 47, wherein the logged measurement configuration includes an indication to report coverage holes.

49. The method of Embodiment 47, wherein the release message includes an indication to report coverage holes.

50. The method of Embodiment 47 further comprising: receiving an indication to report coverage holes from the wireless communication network.

51. The method of any of Embodiments 48-50, wherein the indication to report coverage holes includes a list of frequencies for which coverage hole reporting is applicable, and wherein the second frequency is included in the list of frequencies for which coverage hole reporting is applicable.

52. The method of any of Embodiments 48-51, wherein the indication to report coverage holes includes an indication of a Radio Access Technology, RAT, for which coverage hole reporting is applicable, and wherein the second frequency is a frequency of the RAT.

53. The method of any of Embodiments 47-52, the method further comprising: performing measurements for a plurality of frequencies including the first and second frequencies while in the dormant state.

54. A communication device (300) comprising: processing circuitry (303); and memory (305) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the wireless device to perform operations according to any of Embodiments 1-26.

55. A communication device (300) adapted to perform according to any of Embodiments

1-26.

56. A computer program comprising program code to be executed by processing circuitry (303) of a communication device (300), whereby execution of the program code causes the communication device (300) to perform operations according to any of embodiments 1-26.

57. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (303) of a communication device (300), whereby execution of the program code causes the communication device (300) to perform operations according to any of embodiments 1-26. 58. A radio access network, RAN, node (400) comprising: processing circuitry (403); and memory (405) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the RAN node to perform operations according to any of Embodiments 27-46.

59. A radio access network, RAN, node (400) adapted to perform according to any of Embodiments 27-46.

60. A computer program comprising program code to be executed by processing circuitry (403) of a radio access network, RAN, node (400), whereby execution of the program code causes the RAN node (400) to perform operations according to any of embodiments 27-46.

61. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (403) of a radio access network, RAN, node (400), whereby execution of the program code causes the RAN node (400) to perform operations according to any of embodiments 27-46.

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

Abbreviation Explanation AS Access Stratum

CA Carrier Aggregation

DC Dual Connectivity

DL Downlink

EUTRA Evolved Universal Terrestrial Radio Access

E-UTRAN Evolved Universal Terrestrial Radio Access Network ID Identity

IE Information Element

LTE Long Term Evolution

MBSFN Multicast-broadcast single-frequency network

MDT Minimization of drive test

NR New Radio

OAM Operation and Maintenance

PLMN Public Land Mobile Network

RPLMN Registered PLMN UE User Equipment

RAT Radio Access Technology

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

SIB System Information Block

SSB Synchronization Signal Block

UL Uplink

[0240] References are identified below.

Reference [1] 3 GPP TS 36.331 V15.8.0 (2019-12)

Reference [2] 3 GPP TS 38.304 V15.6.0 (2019-12)

Reference [3] [108#42][NR/MDT] running 38.331 CRto support SON/MDT (Huawei and Ericsson)

Reference [4] 3 GPP TS 38.331 V15.8.0 (2019-12)

[0241] Additional explanation is provided below.

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

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

[0244] Figure 17 illustrates a wireless network in accordance with some embodiments.

[0245] 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 17. For simplicity, the wireless network of Figure 17 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 landline 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.

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

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

[0249] 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. [0250] In Figure 17, 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 17 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).

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

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

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

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

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

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

[0259] 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 4190 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.

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

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

[0262] Alternative embodiments of network node 4160 may include additional components beyond those shown in Figure 17 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.

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

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

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

[0266] 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 4114 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.

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

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

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

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

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

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

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

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

[0275] Figure 18 illustrates a user Equipment in accordance with some embodiments.

[0276] Figure 18 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) EE. LIE 4200, as illustrated in Figure 18, 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, EMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and EE may be used interchangeable. Accordingly, although Figure 18 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[0277] In Figure 18, EE 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 4233, 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 EEs may utilize all of the components shown in Figure 18, or only a subset of the components. The level of integration between the components may vary from one EE to another EE. Further, certain EEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0278] In Figure 18, 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.

[0279] 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. EE 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.

[0280] In Figure 18, 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 (FAN), 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.

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

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

[0283] In Figure 18, 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.

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

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

[0286] Figure 19 illustrates a virtualization environment in accordance with some embodiments. [0287] Figure 19 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).

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

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

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

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

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

[0293] As shown in Figure 19, 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.

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

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

[0296] 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 19.

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

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

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

[0300] With reference to Figure 20, 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 4413c 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.

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

[0302] The communication system of Figure 20 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.

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

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

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

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

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

[0308] In Figure 21, 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).

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

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

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

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

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

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

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

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

24 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. [0317] 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.

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

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

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

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

3 GPP 3rd Generation Partnership Project

5G 5th Generation

ABS Almost Blank Subframe

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel

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

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex

FFS For Further Study

GERAN GSM EDGE Radio Access Network gNB Base station in NR

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

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

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid- ARQ Indicator Channel

PFMN Public Fand Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RAT Radio Access Technology

RFM Radio Fink Management RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR

Reference Signal Received Power

RSRQ Reference Signal Received Quality OR

Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SNR Signal to Noise Ratio

SON Self Optimized Network ss Synchronization Signal sss Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UE User Equipment

UL Uplink

UMTS Universal Mobile Telecommunication System USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WLAN Wide Local Area Network

[0322] Further definitions and embodiments are discussed below.

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

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

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

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

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

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

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

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

Claims

CLAIMS:

1. A method of operating a node of a wireless communication network, the method comprising: transmitting (2901, 3001) a logged measurement configuration to a communication device; transmitting (2905, 3005) a release message to the communication device, wherein the release message initiates transitioning of the communication device to a dormant state; after transmitting the release message, transmitting (2907, 3007) a resume message or a setup message to the communication device, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state; and after transmitting the resume message or the setup message, receiving (2909, 3009) a logged measurement report from the communication device, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency.

2. The method of Claim 1, wherein the logged measurement configuration includes an indication to report coverage holes.

3. The method of Claim 1, wherein the release message includes an indication to report coverage holes.

4. The method of Claim 1 further comprising: transmitting (3003) an indication to report coverage holes to the communication device.

5. The method of any of Claims 2-4, wherein the indication to report coverage holes includes a list of frequencies for which coverage hole reporting is applicable, and wherein the second frequency is included in the list of frequencies for which coverage hole reporting is applicable.

6. The method of any of Claims 2-5, wherein the indication to report coverage holes includes an indication of a Radio Access Technology, RAT, for which coverage hole reporting is applicable, and wherein the second frequency is a frequency of the RAT.

7. A method of operating communication device in communication with a node of a wireless communication network, the method comprising: receiving (3051) a logged measurement configuration from the wireless communication network; receiving (3055) a release message from the wireless communication network, wherein the release message initiates transitioning of the communication device to a dormant state; after receiving the release message and transitioning (3056) to the dormant state, receiving (3067) a resume message or a setup message from the wireless communication network, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state; and after receiving the resume message or the setup message, transmitting (3069) a logged measurement report to the wireless communication network, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency.

8. The method of Claim 7, wherein the logged measurement configuration includes an indication to report coverage holes.

9. The method of Claim 7, wherein the release message includes an indication to report coverage holes.

10. The method of Claim 7 further comprising: receiving (3053) an indication to report coverage holes from the wireless communication network.

11. The method of any of Claims 8-10, wherein the indication to report coverage holes includes a list of frequencies for which coverage hole reporting is applicable, and wherein the second frequency is included in the list of frequencies for which coverage hole reporting is applicable.

12. The method of any of Claims 8-11, wherein the indication to report coverage holes includes an indication of a Radio Access Technology, RAT, for which coverage hole reporting is applicable, and wherein the second frequency is a frequency of the RAT.

13. The method of any of Claims 7-12, the method further comprising: performing (3057) measurements for a plurality of frequencies including the first and second frequencies while in the dormant state.

14. A radio access network, RAN, node (400) adapted to perform a method according to any of claims 1-6.

15. A computer program comprising program code to be executed by processing circuitry (403) of a radio access network, RAN, node (400), whereby execution of the program code causes the RAN node (400) to perform operations according to any of claims 1-6.

16. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (403) of a radio access network, RAN, node (400), whereby execution of the program code causes the RAN node (400) to perform operations according to any of claims 1-6.

17. A communication device (300) adapted to perform a method according to any of claims 7-13.

18. A computer program comprising program code to be executed by processing circuitry (303) of a communication device (300), whereby execution of the program code causes the communication device (300) to perform operations according to any of claims 7-13.

19. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (303) of a communication device (300), whereby execution of the program code causes the communication device (300) to perform operations according to any of claims 7-13.

20. A radio access network, RAN, node (400) comprising: processing circuitry (403); and memory (405) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the RAN node to, transmit a logged measurement configuration to a communication device, transmit a release message to the communication device, wherein the release message initiates transitioning of the communication device to a dormant state, transmit a resume message or a setup message to the communication device after transmitting the release message, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state, and receive a logged measurement report from the communication device after transmitting the resume message or the setup message, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency.

21. The RAN node of Claim 20, wherein the logged measurement configuration includes an indication to report coverage holes.

22. The RAN node of Claim 20, wherein the release message includes an indication to report coverage holes.

23. The RAN node of Claim 20 wherein the memory includes instructions that when executed by the processing circuitry causes the RAN node to, transmit an indication to report coverage holes to the communication device.

24. The RAN node of any of Claims 21-23, wherein the indication to report coverage holes includes a list of frequencies for which coverage hole reporting is applicable, and wherein the second frequency is included in the list of frequencies for which coverage hole reporting is applicable.

25. The RAN node of any of Claims 21-24, wherein the indication to report coverage holes includes an indication of a Radio Access Technology, RAT, for which coverage hole reporting is applicable, and wherein the second frequency is a frequency of the RAT.

26. A communication device (300) comprising: processing circuitry (303); and memory (305) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the communication device to, receive a logged measurement configuration from a wireless communication network, receive a release message from the wireless communication network, wherein the release message initiates transitioning of the communication device to a dormant state, receive a resume message or a setup message from the wireless communication network after receiving the release message and transitioning to the dormant state, wherein the resume message or the setup message initiates transitioning of the communication device to a connected state, and transmit a logged measurement report to the wireless communication network after receiving the resume message or the setup message, wherein the logged measurement report includes a received signal measurement for a first frequency and an indication of a coverage hole for a second frequency.

27. The communication device of Claim 26, wherein the logged measurement configuration includes an indication to report coverage holes.

28. The communication device of Claim 26, wherein the release message includes an indication to report coverage holes.

29. The communication device of Claim 26, wherein the memory includes instructions that when executed by the processing circuitry causes the communication device to, receive an indication to report coverage holes from the wireless communication network.

30. The communication device of any of Claims 27-29, wherein the indication to report coverage holes includes a list of frequencies for which coverage hole reporting is applicable, and wherein the second frequency is included in the list of frequencies for which coverage hole reporting is applicable.

31. The communication device of any of Claims 27-30, wherein the indication to report coverage holes includes an indication of a Radio Access Technology, RAT, for which coverage hole reporting is applicable, and wherein the second frequency is a frequency of the RAT.

32. The communication device of any of Claims 26-31, wherein the memory includes instructions that when executed by the processing circuitry causes the communication device to, perform measurements for a plurality of frequencies including the first and second frequencies while in the dormant state.