WO2020167206A1

WO2020167206A1 - Event driven logged mdt

Info

Publication number: WO2020167206A1
Application number: PCT/SE2020/050098
Authority: WO
Inventors: Malik WAHAJ ARSHAD; Angelo Centonza; Pablo SOLDATI; Pradeepa Ramachandra; Wei Shen
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2019-02-14
Filing date: 2020-02-04
Publication date: 2020-08-20
Also published as: TW202046763A

Abstract

A method is performed by a wireless device (210) and includes receiving (1410), from a base station (260), a configuration for logging a Minimization of Driving Test, MDT, measurement. The configuration includes an event-driven logging configuration. The wireless device performs (1420) at least one measurement associated with an event configured in the event-driven logging configuration and determines (1430) that at least one condition associated with the event-driven logging configuration has been satisfied. In response to determining that the at least one condition has been satisfied, the wireless device performs (1440) logging of the at least one measurement.

Description

EVENT DRIVEN LOGGED MDT

TECHNICAL FIELD

The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for event driven logged Minimization of Driving Test (MDT)

BACKGROUND

Minimization of Driving Test (MDT) was firstly studied in Rel-9 (3^rd Generation Partnership Project (3GPP) TR 36.805 v. 9.0.0) driven by RAN2 with the purpose to minimize actual drive tests. MDT has been introduced since Rel-10 in Long Term Evolution (LTE). MDT has not been specified for New Radio (NR) in the involved standards in RAN2, RAN3 and SA5 groups.

The use cases in the 3GPP TR 36.805 v. 9.0.0include: coverage optimization, mobility optimization, capacity optimization, parameterization for common channels, and QoS verification.

Normal Radio Resource Management (RRM) mechanisms only allow for measurements to be reported when a wireless device, which may include a User Equipment (UE), has Radio Resource Control (RRC) connection with the particular cell, and there is sufficient uplink (UL) coverage to transport the measurement report. This will restrict measurements to be collected from UEs not experiencing radio link failure (RLF) and experiencing sufficient UL coverage. Additionally, there is no accompanying location information in normal RRM measurements.

In general, there are two types of MDT measurement logging based on RRC states. These are Logged MDT and Immediate MDT.

With regard to Logged MDT, a UE in RRC IDLE state is configured to perform periodical MDT logging after receiving the MDT configurations from the network. The UE shall report the downlink (DL) pilot strength measurements such as, for example Reference Signal Received Power(RSRP)/Reference Signal Received Quality (RSRQ) together with time information, detailed location information if available, and Wide Local Area Network (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.

Table 1 shows the measurement logging for Logged MDT

Table 1

For Logged MDT, UE receives the MDT configurations including logginginterval and loggingduration in the RRC message, i.e., LoggedMeasurementConfiguration , from the network. A timer such as a T330 timer is started at the UE upon receiving the configurations and set to loggingduration , which may be 10 min - 120 min, for example. 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.

FIGURE 1 illustrates an example of MDT logging. As depicted UE in RRC Connected receives MDT configurations and starts a T330 timer. This begins a MDT loggingduration , which ends when the T330 timer expires. During the MDT loggingduration , the UE may alternate between Connected Mode and Idle Mode. When the UE enters RRC Idle Mode, the UE starts periodical MDT logging. The periodical MDT logging is performed at a MDT logginginterval while the UE is in Idle Mode. When the UE transitions to connected mode, the UE stops MDT logging; however, the T330 timer is kept running. If the UE then thereafter transitions back into Idle Mode, the UE restarts periodical MDT logging according to the MDT logging interval.

With regard to Immediate MDT, measurements for Immediate MDT purpose can be performed by Radio Access Network (RAN) and UE. There are a number of measurements (M1-M9) that are specified for RAN measurements and UE measurements. For UE measurements, the MDT configuration is based on the existing RRC measurement procedures for configuration and reporting with some extensions for location information.

The measurement quantities for Immediate MDT are shown in Table 2 below.

TABLE 2

The reporting of the Immediate MDT is specified as follows.

- For Ml :

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

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

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

Furthermore, Logged Multimedia Broadcast multicast service Single Frequency Network Minimization of Driving Test (MBSFN MDT) is defined to perform measurement logging when a UE is in RRC IDLE and RRC CONNECTED. An enhancement on RLF is also specified for RLF report with detailed location information (e.g., Global Navigation Satellite System (GNSS) if available. RLF reports may also include available WLAN measurement results and/or Bluetooth measurement results for calculating UE location. The measurement quantities for Logged MBSFN MDT and RLF Enhancement are shown in Table 3.

TABLE 3

With regard to control and configuration of MDT, when MDT was introduced in Rel- 10, it was decided to include MDT as a part of the trace function, which is able to provide very detailed logging data at call level. Based on the methods of activating/deactivating trace and trace configuration, the trace function can be classified into the following two aspects. - Management activation/deactivation: Trace Session is activated/deactivated in different Network Elements (NE) directly from the Element Manager (EM) using the management interfaces of those NEs.

- Signalling Based Activation/Deactivation: Trace Session is activated/deactivated in different NEs using the signalling interfaces between those elements so that the NEs may forward the activation/deactivation originating from the EM.

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

- Area based MDT : MDT data is collected from EIEs in a specified area. The area is defined as a list of cells (Universal Terrestrial Radio Access Network (UTRAN) or Evolved-Universal Terrestrial Radio Access Network (E- UTRAN)) or as a list of tracking/routing/location areas. The area-based MDT is an enhancement of the management-based trace functionality. Area based MDT can be either a logged MDT or Immediate MDT.

- Signalling based MDT: MDT data is collected from one specific UE. The UE that is participating in the MDT data collection is specified as IMEI(SV) or as IMSI. The signalling based MDT is an enhancement of the signalling based subscriber and equipment trace. The signalling based MDT can be either a logged MDT or Immediate MDT.

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

FIGURE 2 summarizes the classification of the MDT.

The Logged MDT measurements are tagged by the UE with location data in the following manner:

- Evolved Cell Global Identifier (ECGI) or Cell Identifier (Cell-Id) of the serving cell when the measurement was taken is always included. - Detailed location information (e.g. GNSS location information) is included if available in the UE when the measurement was taken. If detailed location information is available, the reporting shall consist of latitude and longitude. Depending on availability, altitude, uncertainty and confidence may be also additionally included. UE tags available detailed location information only once with upcoming measurement sample, and then the detailed location information is discarded, i.e. the validity of detailed location information is implicitly assumed to be one logging interval.

For Immediate MDT, the Ml measurements are tagged by the UE with location data in the following manner:

- Detailed location information (e.g. GNSS location information) is included if available in the UE when the measurement was taken. If detailed location information is available, the reporting shall consist of latitude and longitude. Depending on availability, altitude, uncertainty and confidence may be also additionally included.

The UE should include the available detailed location information only once. If the detailed location information is obtained by GNSS positioning method, GNSS time information shall be included. For both event-based and periodic reporting, the detailed location information is included if the report is transmitted within the validity time after the detailed location information was obtained. The validity evaluation of detailed location information is left to UE implementation.

For signalling based MDT, the Core Network (CN) shall not initiate MDT towards a particular user unless the user consent is available.

For area-based MDT, the CN indicates to the RAN whether MDT is allowed to be configured by the RAN for this user considering, e.g. user consent and roaming status, by providing management-based MDT allowed information consisting of the Management Based MDT Allowed indication and optionally the Management Based MDT Public Land Mobile Network (PLMN) List. The management-based MDT allowed information propagates during inter-PLMN handover if the Management Based MDT PLMN List is available and includes the target PLMN. The same user consent information can be used for area-based MDT and for signaling- based MDT. Thus, there is no need to differentiate the user consent per MDT type. Collecting the user consent shall be done via customer care process. The user consent information availability shall be considered as part of the subscription data and as such this shall be provisioned to the Home Subscriber Server (HSS) database.

Certain problems exist. For example, in the logged MDT feature provided in LTE, the UE logs the measurements periodically. The UE stores these measurements as part of a buffer with limited capacity. When the UE’s buffer capacity is filled with measurements so logged, the UE will stop performing logged MDT.

When the memory reserved for the logged measurement information becomes full, the UE stops the duration timer, which may include a T330 timer, and performs the same actions as performed upon expiry of the T330 timer. For example, the UE releases the configuration and the UE is allowed to discard the stored logged measurements 48 hours after the expiry of the timer.

This can be seen as a limiting feature as the UE might identify critical issues in the network (for example, a coverage hole) that the network might benefit from knowing but the UE cannot log this information as the UE’s buffer for logged MDT is already filled with other data. This is especially problematic when the network has a very small coverage hole in a very large geographical area. Also, in those scenarios when the mobility in the region of coverage hole is seldom. In such scenarios, most of the logged MDT is associated to the region where there is good coverage already. Thus, the current logged MDT configuration is very inefficient to capture coverage holes.

SUMMARY

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, according to certain embodiments, a UE is configured with certain events during which the UE may perform storing of measurements associated to logged MDT configuration.

According to certain embodiments, a method is performed by a wireless device and includes receiving, from a base station, a configuration for logging a Minimization of Driving Test, MDT, measurement. The configuration includes an event-driven logging configuration. The wireless device performs at least one measurement associated with an event configured in the event-driven logging configuration and determines that at least one condition associated with the event-driven logging configuration has been satisfied. In response to determining that the at least one condition has been satisfied, the wireless device performs logging of the at least one measurement.

According to certain embodiments, a method is performed by a base station and includes transmitting, to a wireless device, a configuration for logging a MDT measurement. The configuration includes an event-driven logging configuration identifying at least one condition to be satisfied for triggering logging of at least one measurement while the wireless device is in an idle or inactive mode.

According to certain embodiments, a wireless device includes processing circuitry configured to receive, from a base station, a configuration for logging a Minimization of Driving Test, MDT, measurement. The configuration includes an event-driven logging configuration. The processing circuitry is configured to perform at least one measurement associated with an event configured in the event-driven logging configuration and determine that at least one condition associated with the event-driven logging configuration has been satisfied. In response to determining that the at least one condition has been satisfied, the processing circuitry is configured to perform logging of the at least one measurement.

According to certain embodiments, a base station includes processing circuitry configured to transmit, to a wireless device, a configuration for logging a MDT measurement. The configuration includes an event-driven logging configuration identifying at least one condition to be satisfied for triggering logging of at least one measurement while the wireless device is in an idle or inactive mode.

Certain embodiments may provide one or more of the following technical advantages. For example, one technical advantage may be that, according to certain embodiments, the logged MDT can be more relevant in terms of capturing the‘problematic areas’ in the network or in terms of capturing only some relevant type of mobility related information. As another example, a technical advantage may be that the proposed solutions may save UE memory since it is not required to record any measurements periodically and also provide flexibility to UE in terms of measuring prioritized measurements in case there is a memory limitation. As still another example, a technical advantage may be that a management entity may provide a policy- based MDT configuration, giving the radio node flexibility to decide which event based measurements could be relevant for a specific policy based MDT trigger. Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIGURE 1 illustrates an example of MDT logging;

FIGURE 2 illustrates summarizes the classification of the MDT;

FIGURE 3 illustrates a basic method by a UE for event-driven MDT logging, according to certain embodiments;

FIGURE 4 illustrates an example virtual apparatus, according to certain embodiments;

FIGURE 5 illustrates an example wireless network, according to certain embodiments;

FIGURE 6 illustrates an example network node, according to certain embodiments;

FIGURE 7 illustrates an example wireless device, according to certain embodiments;

FIGURE 8 illustrate an example user equipment, according to certain embodiments;

FIGURE 9 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;

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

FIGURE 11 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;

FIGURE 12 illustrates a method implemented in a communication system, according to one embodiment;

FIGURE 13 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 14 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 15 illustrates another method implemented in a communication system, according to one embodiment; FIGURE 16 illustrates an example method by a network node, according to certain embodiments;

FIGURE 17 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 18 illustrates an example method by a wireless device, according to certain embodiments;

FIGURE 19 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 20 illustrates another example method by a network node, according to certain embodiments; and

FIGURE 21 illustrates another exemplary virtual computing device, according to certain embodiments.

DETAILED DESCRIPTION

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

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.

In some embodiments, a more general term“network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node. Examples of network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), MME, etc), Operations and Maintenance (O&M), Operations Support System (OSS), Self-Optimized Network (SON), positioning node (e.g. Evolved Serving Mobile Location Center (E-SMLC)), MDT, test equipment (physical node or software), etc. In some embodiments, the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.

Additionally, terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general,“gNodeB” could be considered as device 1 and“UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNode B (gNB) or UE.

According to certain embodiments, a wireless device, which may include a user equipment (UE), is configured with certain configured events during which the UE may perform storing of measurements associated to a logging MDT configuration. Herein, the terms‘configured events,’‘configured event conditions,’ and‘events’ are used synonymously.

The configured events’ definition could include one or more of (but not limited to) the following types of events:

1. Detection of a coverage hole in the camped frequency

• This is useful to determine a coverage hole in the camped frequency. In addition, this will also act as an indication of the coverage hole of the operator’s network as the UE did not find any other suitable cells before declaring out of coverage. If the UE declares out-of-coverage and reconnects to another frequency of the same operator, then it is an indication to the original camped cell that the inter-frequency related system information broadcasted by it needs to include the information about the frequency in which the UE has come to connected again (provided the out of coverage declaration and the time of finding the new frequency to camp on within a short duration).

2. Detection of a coverage hole in any of the measured frequency • Same usefulness as the previous one but more detailed as the coverage holes in each of the frequency in which the UE is performing measurements is indicated to the network.

Detection of a coverage hole in a Radio Access Technology (RAT) such as NR

• This is useful for operators to make the network planning for new base stations for NR. When a UE performs cell reselection from NR to another RAT such as E-UTRAN or UTRAN or Global System for Mobile (GSM), the UE performs the measurement logging.

Detection of a coverage hole in a given high-prioritized frequency

• When a UE camped on a cell in a given high-prioritized frequency, it is configured to perform the measurement logging when the UE performs cell reselection to a cell in a lower-prioritized frequency.

Detection of only‘acceptable cell’ related coverage

• Indicative of the coverage hole in terms of‘camped normally state’ but where the UE can still receive/send some emergency related information.

Cell reselection occasions

• Indicative of the radio conditions at the cell border. The information logged as part of MDT is more exhaustive (UE location, radio conditions, time of reselection, possible sensor information, speed state information etc.) than the information stored via ‘mobility Hi story Report’ and therefore it is much more useful.

Detection that the UE speed (actual speed / number of handovers (#HO) based estimated speed / radio speed) is above certain threshold

• This is useful to map which area of the network has what type of mobility etc.

Detection that the UE speed (actual speed / #HO based estimated speed / radio speed) is below certain threshold

Detection that the camped cell quality (in terms of RSRP and/or RSRQ) is below certain threshold • Information about those areas of the network where the strongest cell quality is very poor.

Detection that the camped cell quality (in terms of RSRP and/or RSRQ) is above certain threshold

• Information about those areas of the network where the strongest cell quality is very good.

Detection that the measured frequency’s strongest cell quality (in terms of RSRP and/or RSRQ) is below certain threshold

• Information about those areas of the network where the strongest cell per frequency quality is very poor.

Detection that the measured frequency’s strongest cell quality (in terms of RSRP and/or RSRQ) is above certain threshold.

• Information about those areas of the network where the strongest cell quality per frequency is very good.

Detection that the UE is in the coverage of a particular beam(s) of a cell

• This information could be requested by the network when one or two specific beam configurations are modified and the network would like to know how this has impacted the coverage in the area.

Detection that the Quality of Experience measurements including streaming service or MTSI crosses a certain threshold (minimum or maximum), i.e., minimum delay jitter rate or maximum packet drop rate

Detection that one or more sensor-based measurement satisfies a condition (for example the barometer indicating that the current altitude is above/below‘X’)

• This allows the network to associate certain radio measurement with other details like height at which the measurement was taken (basement or in a skyscraper) etc. By allowing logging only when the UE is in skyscraper, the network can collect measurements specific to certain height

Detection that the WiFi related measurements (either of the operator WiFi nodes only or for any other WiFi APs) are below/above certain RSSI measurements • This information allows the network operators to build WiFi coverage overlap understanding (and also for fingerprinting)

17. Detection that the Bluetooth beacon related measurements (either of the operator Bluetooth nodes only or for any other Bluetooth) are below/above certain RSSI measurements

• This information allows the network operators to build Bluetooth coverage overlap understanding (and also for fingerprinting)

18. Detection that the UE battery consumption reduces or increases by every‘X%’

• This information allows the network to identify how much overhead of the battery consumption could be related to the network usage at the UE and the quality of the battery usage at the UE.

According to certain embodiments, a UE receives a logged MDT configuration including an event driven logging configuration. The UE performs RRM measurements and any other measurement associated to the configured events in the event driven logging configuration. The UE then determines if any of the conditions associated to event driven logged MDT are satisfied. If the any of the conditions are satisfied, logging is performed.

According to certain embodiments, a method is provided for the network to enable the measurement logging in the logged MDT process only during those times that are more relevant for the network. FIGURE 3 illustrates a basic method by a wireless device such as a UE, for example, for event-driven MDT logging, according to certain embodiments. Details associated to different steps mentioned in the flowchart of FIGURE 3 are given below. Though all of the described steps are mentioned form the UE point of view, some or all of the described steps may be performed by a network node, such as a base station, as well.

With regard to Step 100, according to certain embodiments, the UE receives a logged

MDT configuration including an event driven logging configuration. For example, the logged

MDT configuration may be received from the network and include one or more event configurations identifying one or more configured events for MDT logging. This event driven logging configuration informs the UE as to when to log the measurements while being in idle/inactive mode. An example format of an example event configuration is given below:

LoggedMeasurementConfiguration ::= SEQUENCE {

traceReference TraceReference,

traceRecordingSessionRef OCTET STRING (SIZE (2)),

tce-Id OCTET STRING (SIZE (1)), absoluteTimelnfo AbsoluteTimelnfo,

ar eaC onfi gur ati on AreaConfiguration OPTIONAL, — Need OR loggingDuration LoggingDuration,

logginglnterval Logginglnterval,

plmn-IdentityList PLMN -IdentityLi st3 OPTIONAL, - Need OR areaConfiguration AreaConfiguration OPTIONAL, — Need OR targetMB SFN - AreaLi st TargetMBSFN-AreaList OPTIONAL, —Need OP bt-NameList BT-NameList OPTIONAL, -Need wlan-NameList WLAN-NameList OPTIONAL, —Need OR eventC onfi gur ati on EventConfiguration OPTIONAL

EventConfiguration : := SEQUENCE {

Priority 1 SEQUENCE {

Overwrite protection BOOLEAN,

campedCellOutOfCoverage BOOLEAN,

measredFreqOutOfCoverage BOOLEAN,

cellRe sel ecti onNRtoOtherRAT BOOLEAN,

cellReselectionToLowerFrequency BOOLEAN,

campedCellQualityBased MeasurementQuantityBasedEvent

OPTIONAL,

}

Priority 2 SEQUENCE {

Overwrite protection BOOLEAN,

measuredFreqStrongestCellQualityBased MeasurementQuantityBasedEvent OPTIONAL,

acceptableCellOnlyCoverage BOOLEAN,

cellReselectionOccasion BOOLEAN,

ueSpeedStateBased UESpeedStateBased OPTIONAL, sesorlnfoBased SensorlnfoBasedList OPTIONAL

}

MeasurementQuantityBasedEvent* : := SEQUENCE {

triggerType CHOICE {

event A 1 SEQUENCE {

a 1 -Threshold ThresholdNR

reportOnLeave BOOLEAN

},

eventA2 SEQUENCE {

a2-Threshold ThresholdNR

reportOnLeave BOOLEAN

},

eventA3 SEQUENCE {

a3 -Offset INTEGER (-30 .30),

reportOnLeave BOOLEAN }

}

triggerQuantity ENUMERATED {rsrp, rsrq}

UESpeedStateBased* * : := SEQUENCE !

speedState ENUMERATED (lowOnly, mediumOnly, highOnly, lowOrMedium, lowORHigh, mediumOrHigh}

}

SensorlnfoBasedList : := SEQUENCE (SIZE (1 . maxSensor)) OF

SensorlnfoBased

SensorlnfoBased: := SEQUENCE {

sensorType ENUMERATED (barometer, lightSesor, . }

sensor Threshold CHOICE (blablal, blabla2}

}

QualityofExperience: := SEQUENCE )

QoeServiceType ENUMERATED (streaming, MTSI, .... }

measurementThreshold CHOICE (video jitter rate, packets drop, . }

}

Embodiments associated to the event configuration can include one or more of the eighteen configured events listed above.

With regard to Step 101 of FIGURE 3, the UE performs RRM measurements and any other measurements associated to the events configured in the event driven logging information. For example, the UE may perform RRM measurements based on radio reference signals that are used for idle/inactive mode cell reselection and also may perform any sensor related measurements continuously. The UE may also continuously maintain any measurement that is required to perform event condition evaluation (for example speed estimation based on deselections within a certain duration).

With regard to Step 102 of FIGURE 3, the UE checks if any of the configured event condition(s) associated to the event driven logged MDT are satisfied.

With regard to Step 103, the UE performs logging. For example, if the UE detects that the configured event condition is satisfied at step 102, then the UE logs the measurements. According to certain embodiments, the UE logs all available measurements. In some other embodiments, there could be different measurements associated to different configured events i.e., event specific measurement logging. According to certain embodiments, the method may also include priority based event logging for efficient buffer utilization. For example, in a particular embodiment, the event configuration would include priority for each or group of sub events. At the start of logging, the UE may measure both priority PI and P2 measurements. If the UE memory available for MDT is eventually full but the high priority event condition is still satisfied, UE may start overwriting the low priority measurements with high priority measurements. This would help to have more records of information that is relevant.

According to certain embodiments, the method may also include MDT log Overwrite Protection. For example, in a particular embodiment, the event configuration may include overwrite protection indicator. If the overwrite protection indicator is set for a specific event or group of configured events and the UE receives another MDT configuration, it would not overwrite the current MDT logs, in a particular embodiment. UE may first report the already stored MDT logs from previous event configuration with overwrite protection to the network before start logging MDT measurements based on new received MDT event configuration.

According to still other embodiments, the method may include reporting to the network about the logged MDT measurements. For example, when the UE comes back to connected, the UE may follow the UEInformationRequest and UEInformationResponse framework to provide the logged MDT measurements to the network node.

Other embodiments

Event entering and event leaving criterion-based logging

According to a particular embodiment, the network configuration associated to event driven logged MDT configuration may include indication whether to log measurements associated to only those instances when the UE satisfies the event entering condition.

According to another particular embodiment, the network configuration associated to event driven logged MDT configuration may include indication whether to log measurements associated to both instances when the UE satisfies the event entering condition and when the UE satisfies the event leaving condition.

Periodic us one-shot event logging

According to certain embodiments, once a configured event is detected, network may enable periodic reporting as long as the event conditions are met. In this embodiment, the periodicity with which the logging is supposed to be done are also part of the event configuration received from the network at the time of informing the UE of event triggered logged MDT configuration.

In some other embodiments, this event related logging may be one shot report i.e., the logging will be associated to only that instant when the UE detected that the event condition(s) (possibly entering only or both entering and leaving) are satisfied.

Policy Driven MDT Configuration

According to a particular embodiment, the network element triggering the MDT report towards the RAN node (including but not limited to Element Manager, OAM, MME/AMF, ONAP or another Management entity) can include as part of MDT configuration:

1. A Policy indicating what measurements could be relevant for RAN to measure, i.e a policy to have statistics on latency. In this case RAN node decides which measurement events are more relevant for a specific policy and configure the UE accordingly.

2. A detailed configuration including priority of measurements to be configured on the UE. This would provide an indication about segregating in terms of prioritized vs best effort measurements. If the UE buffer is full, UE can then start overlapping the non-prioritized measurements first.

Priority based event logging based for energy saving

In a particular embodiment, the MDT configuration may include priority for each or group of sub events within the configured events. At start of logging, a UE may measure both priority PI and P2 measurements. If the UE battery level falls below a threshold or if the UE is configured by the network to operate with an energy saving mode, the UE may continue logging only PI measurements. In another example, the UE could stop logging measurements for MDT.

Contents of the logged MDT measurement report

In addition to the parameters already included in the logged MDT measurement report discussed above, the UE may also be configured according to one or more of the following parameters: 1) Speed state of the UE at the time of logging

2) Any of the sensor related information

3) Quality of Experience measurements

4) EE battery status measurements

FIGURE 4 illustrates a schematic block diagram of a virtual apparatus 150 in a wireless network (for example, the wireless network shown in FIGETRE 4). The apparatus may be implemented in a wireless device or network node (e.g., wireless device or network node such as those shown in FIGURE 5). Apparatus 150 is operable to carry out the example method described with reference to FIGURE 3 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 3 is not necessarily carried out solely by apparatus 150. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 150 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 160, first performing module 170, determining module 180, second performing module 190, and any other suitable units of apparatus 150 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, receiving module 160 may perform certain of the receiving functions of the apparatus 150. For example, receiving module 160 may receive a logged MDT configuration including an event driven logging configuration.

According to certain embodiments, first performing module 170 may perform certain of the performing functions of the apparatus 150. For example, first performing module 170 may performs RRM measurements and any other measurement associated to the events configured in the event driven logging configuration.

According to certain embodiments, determining module 180 may perform certain of the determining functions of the apparatus 150. For example, determining module 180 may determine if any of the conditions associated to event driven logged MDT are satisfied.

According to certain embodiments, second performing module 190 may perform certain of the performing functions of the apparatus 150. For example, second performing module 190 may perform logging if any of the conditions are satisfied.

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.

FIGURE 5 illustrates a wireless network, in accordance with some embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 5. For simplicity, the wireless network of FIGURE 5 only depicts network 206, network nodes 260 and 260b, and WDs 210, 210b, and 210c. 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 260 and wireless device (WD) 210 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

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

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

Network node 260 and WD 210 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.

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

In FIGURE 6, network node 260 includes processing circuitry 270, device readable medium 280, interface 290, auxiliary equipment 284, power source 286, power circuitry 287, and antenna 262. Although network node 260 illustrated in the example wireless network of FIGURE 6 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 260 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 280 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 260 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 260 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 260 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 280 for the different RATs) and some components may be reused (e.g., the same antenna 262 may be shared by the RATs). Network node 260 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 260, such as, for example, GSM, Wide Code Division Multiplexing Access (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 260.

Processing circuitry 270 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 270 may include processing information obtained by processing circuitry 270 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

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

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

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

Device readable medium 280 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 270. Device readable medium 280 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 270 and, utilized by network node 260. Device readable medium 280 may be used to store any calculations made by processing circuitry 270 and/or any data received via interface 290. In some embodiments, processing circuitry 270 and device readable medium 280 may be considered to be integrated.

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

In certain alternative embodiments, network node 260 may not include separate radio front end circuitry 292, instead, processing circuitry 270 may comprise radio front end circuitry and may be connected to antenna 262 without separate radio front end circuitry 292. Similarly, in some embodiments, all or some of RF transceiver circuitry 272 may be considered a part of interface 290. In still other embodiments, interface 290 may include one or more ports or terminals 294, radio front end circuitry 292, and RF transceiver circuitry 272, as part of a radio unit (not shown), and interface 290 may communicate with baseband processing circuitry 274, which is part of a digital unit (not shown).

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

Antenna 262, interface 290, and/or processing circuitry 270 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 262, interface 290, and/or processing circuitry 270 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 287 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 260 with power for performing the functionality described herein. Power circuitry 287 may receive power from power source 286. Power source 286 and/or power circuitry 287 may be configured to provide power to the various components of network node 260 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 286 may either be included in, or external to, power circuitry 287 and/or network node 260. For example, network node 260 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 287. As a further example, power source 286 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 287. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

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

FIGURE 7 illustrates an example wireless device 210, according to certain embodiments. 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.

As illustrated, wireless device 210 includes antenna 211, interface 214, processing circuitry 220, device readable medium 230, user interface equipment 232, auxiliary equipment 234, power source 236 and power circuitry 237. WD 210 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 210, 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 210. Antenna 211 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 214. In certain alternative embodiments, antenna 211 may be separate from WD 210 and be connectable to WD 210 through an interface or port. Antenna 211, interface 214, and/or processing circuitry 220 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 211 may be considered an interface.

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

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

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

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

Processing circuitry 220 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 220, may include processing information obtained by processing circuitry 220 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 210, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 230 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 220. Device readable medium 230 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 220. In some embodiments, processing circuitry 220 and device readable medium 230 may be considered to be integrated.

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

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

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

FIGURE 8 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 300 may be any UE identified by the 3^rd Generation Partnership Project (3 GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 300, as illustrated in FIGURE 5, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIGURE 5 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In FIGURE 5, UE 300 includes processing circuitry 301 that is operatively coupled to input/output interface 305, radio frequency (RF) interface 309, network connection interface 311, memory 315 including random access memory (RAM) 317, read-only memory (ROM) 319, and storage medium 321 or the like, communication subsystem 331, power source 333, and/or any other component, or any combination thereof. Storage medium 321 includes operating system 323, application program 325, and data 327. In other embodiments, storage medium 321 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 8, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

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

In FIGURE 8, RF interface 309 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 311 may be configured to provide a communication interface to network 343a. Network 343a 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 343a may comprise a Wi-Fi network. Network connection interface 311 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 311 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 317 may be configured to interface via bus 302 to processing circuitry 301 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 319 may be configured to provide computer instructions or data to processing circuitry 301. For example, ROM 319 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 321 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 321 may be configured to include operating system 323, application program 325 such as a web browser application, a widget or gadget engine or another application, and data file 327. Storage medium 321 may store, for use by UE 300, any of a variety of various operating systems or combinations of operating systems.

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

In FIGURE 8, processing circuitry 301 may be configured to communicate with network 343b using communication subsystem 331. Network 343a and network 343b may be the same network or networks or different network or networks. Communication subsystem 331 may be configured to include one or more transceivers used to communicate with network 343b. For example, communication subsystem 331 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.3, Code Division Multiplexing Access (CDMA), WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 333 and/or receiver 335 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 333 and receiver 335 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

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

The features, benefits and/or functions described herein may be implemented in one of the components of UE 300 or partitioned across multiple components of UE 300. 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 331 may be configured to include any of the components described herein. Further, processing circuitry 301 may be configured to communicate with any of such components over bus 302. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 301 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 301 and communication subsystem 331. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

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

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

The functions may be implemented by one or more applications 420 (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 420 are run in virtualization environment 400 which provides hardware 430 comprising processing circuitry 460 and memory 490. Memory 490 contains instructions 495 executable by processing circuitry 460 whereby application 420 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

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

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

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

As shown in FIGURE 9, hardware 430 may be a standalone network node with generic or specific components. Hardware 430 may comprise antenna 4225 and may implement some functions via virtualization. Alternatively, hardware 430 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) 4100, which, among others, oversees lifecycle management of applications 420.

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

In the context of NFV, virtual machine 440 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 440, and that part of hardware 430 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 440, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 440 on top of hardware networking infrastructure 430 and corresponds to application 420 in FIGURE 9.

In some embodiments, one or more radio units 4200 that each include one or more transmitters 4220 and one or more receivers 4210 may be coupled to one or more antennas 4225. Radio units 4200 may communicate directly with hardware nodes 430 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be affected with the use of control system 4230 which may alternatively be used for communication between the hardware nodes 430 and radio units 4200.

FIGURE 10 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. With reference to FIGURE 10, in accordance with an embodiment, a communication system includes telecommunication network 510, such as a 3GPP-type cellular network, which comprises access network 511, such as a radio access network, and core network 514. Access network 511 comprises a plurality of base stations 512a, 512b, 512c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 513a, 513b, 513c. Each base station 512a, 512b, 512c is connectable to core network 514 over a wired or wireless connection 515. A first UE 591 located in coverage area 513c is configured to wirelessly connect to, or be paged by, the corresponding base station 512c. A second UE 592 in coverage area 513a is wirelessly connectable to the corresponding base station 512a. While a plurality of UEs 591, 592 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 512.

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

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

FIGURE 11 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 11. In communication system 600, host computer 610 comprises hardware 615 including communication interface 616 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 600. Host computer 610 further comprises processing circuitry 618, which may have storage and/or processing capabilities. In particular, processing circuitry 618 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 610 further comprises software 611, which is stored in or accessible by host computer 610 and executable by processing circuitry 618. Software 611 includes host application 612. Host application 612 may be operable to provide a service to a remote user, such as UE 630 connecting via OTT connection 650 terminating at UE 630 and host computer 610. In providing the service to the remote user, host application 612 may provide user data which is transmitted using OTT connection 650.

Communication system 600 further includes base station 620 provided in a telecommunication system and comprising hardware 625 enabling it to communicate with host computer 610 and with UE 630. Hardware 625 may include communication interface 626 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 600, as well as radio interface 627 for setting up and maintaining at least wireless connection 670 with UE 630 located in a coverage area (not shown in FIGURE 11) served by base station 620. Communication interface 626 may be configured to facilitate connection 660 to host computer 610. Connection 660 may be direct or it may pass through a core network (not shown in FIGURE 11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 625 of base station 620 further includes processing circuitry 628, 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 620 further has software 621 stored internally or accessible via an external connection.

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

It is noted that host computer 610, base station 620 and UE 630 illustrated in FIGURE 11 may be similar or identical to host computer 530, one of base stations 512a, 512b, 512c and one of UEs 591, 592 of FIGURE 10, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 11 and independently, the surrounding network topology may be that of FIGURE 10.

In FIGURE 11, OTT connection 650 has been drawn abstractly to illustrate the communication between host computer 610 and UE 630 via base station 620, 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 630 or from the service provider operating host computer 610, or both. While OTT connection 650 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 670 between UE 630 and base station 620 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 630 using OTT connection 650, in which wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.

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

FIGURE 12 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 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 12 will be included in this section. In step 710, the host computer provides user data. In substep 711 (which may be optional) of step 710, the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. In step 730 (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 740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIGURE 13 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 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 13 will be included in this section. In step 810 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 820, 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 830 (which may be optional), the UE receives the user data carried in the transmission.

FIGURE 14 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 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 14 will be included in this section. In step 910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 920, the UE provides user data. In substep 921 (which may be optional) of step 920, the UE provides the user data by executing a client application. In substep 911 (which may be optional) of step 910, 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 930 (which may be optional), transmission of the user data to the host computer. In step 940 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 15 will be included in this section. In step 1010 (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 1020 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

FIGURE 16 depicts a method by a network node, according to certain embodiments. At step 1200, the network node 260 transmits, to a UE 110, a logged MDT configuration including an event-driven logging configuration. The event-driven logging configuration identifies at least one condition to be satisfied for triggering logging of MDT while the UE is in idle or inactive mode.

In a particular embodiment, the UE is in idle or inactive mode when performing the logging of MDT.

In a particular embodiment, the at least one measurements is performed based on radio reference signals that are used for idle/inactive mode cell reselection.

In a particular embodiment, the network node configures the UE to perform any sensor related measurements continuously.

In a particular embodiment, the network node configures the UE to continuously maintain any measurement that is required to perform event condition evaluation.

In a particular embodiment, the network node configures the UE to log all available measurements.

In a particular embodiment, the network node receives, from the UE, the log of MDT.

In a particular embodiment, the log comprises at least one measurement associated with an event for which the at least one condition is satisfied. In a particular embodiment, the event-driven logging configuration includes a priority for each group of sub events, and the method further comprises configuring the UE to overwrite a low priority measurement with a high priority measurement if a memory of the UE is full.

In a particular embodiment, the network node configures an overwrite protection indicator for a specific event or group of events and configuring the UE not to report a stored MDT log from a previous configuration with overwrite protection to the network before logging MDT measurements based on new received MDT logs.

In a particular embodiment, upon coming back to connected, the network node transmits the logged MDT measurements to the network node.

FIGURE 17 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 210 or network node 260 shown in FIGURE 5). Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 16 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 17 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause transmitting module 1310 and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, transmitting module 1310 may perform certain of the transmitting functions of the apparatus 1300. For example, transmitting module M10 may transmit, to a UE, a logged MDT configuration including an event-driven logging configuration. The event-driven logging configuration identifies at least one condition to be satisfied for triggering logging of MDT while the UE is in idle or inactive mode.

FIGURE 18 depicts a method 1400 by a wireless device 210, according to certain embodiments. At step 1410, the wireless device 210 receives, from a base station 260, a configuration for logging a MDT measurement. The configuration includes an event-driven logging configuration. At step 1420, the wireless device 210 performs at least one measurement associated with an event configured in the event-driven logging configuration. At step 1430, the wireless device 210 determines that at least one condition associated with the event-driven logging configuration has been satisfied. In response to determining that the at least one condition has been satisfied, wireless device 210 performs logging of the at least one measurement at step 1440.

In a particular embodiment, the event-driven logging configuration identifies at least one event for triggering when to log the at least one measurement.

In a particular embodiment, the at least one event for triggering when to log the at least one measurement includes detection of a coverage hole in a camped frequency.

In a particular embodiment, the at least one event for triggering when to log the at least one measurement includes detection of a camped cell quality below a threshold. For example, the at least one event for triggering when to log the at least one measurement may include detection of a RSRP and/or RSRQ measurement that is below a threshold.

In a particular embodiment, the at least one event for triggering when to log the at least one measurement comprises at least one of an event associated with a speed event, an event associated with a coverage of a beam, an event associated with a WiFi measurement for MDT, an event associated with a Bluetooth measurement for MDT, an event associated with a battery consumption measurement of the wireless device, an event associated with a Quality of Service (QoS) measurement, and an event associated with a sensor.

In a particular embodiment, the wireless device 210 performs any sensor related measurements continuously. In a particular embodiment, the wireless device 210 continuously maintains any measurement that is required to perform event condition evaluation.

In a particular embodiment, wireless device 210 is in idle or inactive mode when performing the logging of the at least one measurement, and the method further includes transmitting, by the wireless device 210, the logged the least one measurement to the base station 260 upon returning to a connected mode.

In a particular embodiment, the at least one measurement is performed based on at least one radio reference signal that is used for idle/inactive mode cell reselection.

In a particular embodiment, when performing the logging of the at least one measurement, wireless device 210 logs all available measurements.

In a particular embodiment, the at least one measurement that is logged is associated with an event for which the at least one condition is satisfied.

In a particular embodiment, the event-driven logging configuration includes a priority for each group of a plurality of groups of sub events. When a memory of the wireless device 210 is full, wireless device 210 overwrites a low priority measurement with a high priority measurement.

In a particular embodiment, if an overwrite protection indicator is set for a specific event or group of events and the wireless device receives another MDT configuration, the wireless device 210 may not overwrite the current MDT logs. Wireless device 210 may first report the already stored MDT logs from previous configuration with overwrite protection to the network before start logging MDT measurements based on new received MDT logs.

In a particular embodiment, upon coming back to connected, wireless device 210 transmits the logged MDT measurements to the network node.

FIGURE 19 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 210 or network node 260 shown in FIGURE 5). Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 18 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 19 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities. Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1510, first performing module 1520, determining module 1530, second performing module 1540, and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, receiving module 1510 may perform certain of the receiving functions of the apparatus 1500. For example, receiving module 1510 may receive, from a base station 260, a configuration for logging a MDT measurement. The configuration includes an event-driven logging configuration.

According to certain embodiments, first performing module 1520 may perform certain of the performing functions of apparatus 1500. For example, first performing module 1520 may perform at least one measurement associated with an event configured in the event-driven logging configuration.

According to certain embodiments, determining module 1530 may perform certain of the determining functions of apparatus 1500. For example, determining module 1530 may determine that at least one condition associated with the event-driven logging configuration has been satisfied.

According to certain embodiments, second performing module 1540 may perform certain other of the performing functions of apparatus 1500. For example, second performing module 1540 may, in response to determining that the at least one condition has been satisfied, perform logging of the at least one measurement.

FIGURE 20 depicts a method 1600 performed by a network node 260 such as a base station, according to certain embodiments. The method begins at step 1610 when the base station 260 transmits, to a wireless device 210, a configuration for logging a MDT measurement. The configuration includes an event-driven logging configuration identifying at least one condition to be satisfied for triggering logging of at least one measurement while the wireless device 210 is in an idle or inactive mode.

In a particular embodiment, the at least one measurement is performed based on radio reference signals that are used for idle/inactive mode cell reselection.

In a particular embodiment, base station 260 configures the wireless device 210 to perform any sensor related measurements continuously.

In a particular embodiment, base station 260 configures the wireless device 210 to continuously maintain any measurement that is required to perform event condition evaluation.

In a particular embodiment, base station 260 configures the wireless device 210 to log all available measurements.

In a particular embodiment, base station 260 receives, from the wireless device 210, the log of the at least one measurement.

In a particular embodiment, the at least one measurement is associated with an event for which the at least one condition is satisfied.

In a particular embodiment, the event-driven logging configuration includes a priority for each group of a plurality of groups of sub events, and base station 260 configures the wireless device 210 to overwrite a low priority measurement with a high priority measurement when a memory of the wireless device is full.

In a particular embodiment, the base station 260 configures an overwrite protection indicator for a specific event or group of events. Base station 260 configures the wireless device 210 not to report a stored MDT log from a previous configuration with overwrite protection to the network before logging MDT measurements based on new received MDT logs. In a particular embodiment, the base station 260 receives the logged MDT measurements from the wireless device 210 upon the wireless device 210 coming back to connected.

FIGURE 21 illustrates a schematic block diagram of a virtual apparatus 1700 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 210 or network node 260 shown in FIGURE 5). Apparatus 1700 is operable to carry out the example method described with reference to FIGURE 20 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 20 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities.

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

According to certain embodiments, transmitting module 1710 may perform certain of the transmitting functions of the apparatus 1700. For example, transmitting module 1710 may transmit, to a wireless device 210, a configuration for logging a MDT measurement. The configuration includes an event-driven logging configuration identifying at least one condition to be satisfied for triggering logging of at least one measurement while the wireless device 210 is in an idle or inactive mode.

EXAMPLE EMBODIMENTS

Example Embodiment 1. A method performed by a wireless device, the method comprising: receiving a logged MDT configuration including an event-driven logging configuration; performing at least one measurement associated with an event configured in the event-driven logging configuration; determining that at least one condition associated with the event-driven logging configuration has been satisfied; and in response to determining that the at least one condition has been satisfied, performing logging of MDT.

Example Embodiment 2. The method of Embodiment 1, wherein the logged MDT configuration is received from a network node.

Example Embodiment 3. The method of any one of Embodiments 1 to 2, wherein the event-driven logging configuration identifies at least one event for triggering when to log measurement.

Example Embodiment 4. The method of any one of Embodiments 1 to 3, wherein the UE is in idle or inactive mode when performing the logging of MDT.

Example Embodiment 5. The method of any one of Embodiments 1 to 4, wherein at least one measurements is performed based on radio reference signals that are used for idle/inactive mode cell reselection.

Example Embodiment 6. The method of any one of Embodiments 1 to 5, further comprising performing any sensor related measurements continuously.

Example Embodiment 7. The method of any one of Embodiments 1 to 6, further comprising continuously maintaining any measurement that is required to perform event condition evaluation.

Example Embodiment 8. The method of any one of Embodiments 1 to 7, wherein performing logging of MDT comprises logging all available measurements.

Example Embodiment 9. The method of any one of Embodiments 1 to 8, wherein performing logging of MDT comprises logging at least one measurement associated with an event for which the at least one condition is satisfied.

Example Embodiment 10. The method of any one of Embodiments 1 to 9, wherein the event-driven logging configuration includes a priority for each group of sub events, and wherein if a memory of the UE is full, the method comprises overwriting a low priority measurement with a high priority measurement.

Example Embodiment 11. The method of any one of Embodiments 1 to 10, wherein if an overwrite protection indicator is set for a specific event or group of events and the UE receives another MDT configuration, it would not overwrite the current MDT logs. UE would first report the already stored MDT logs from previous configuration with overwrite protection to the network before start logging MDT measurements based on new received MDT logs.

Example Embodiment 12. The method of any one of Embodiments 1 to 11, further comprising, upon coming back to connected, transmitting the logged MDT measurements to the network node.

Example Embodiment 13. A method performed by a base station for improving network efficiency, the method comprising: transmitting, to a UE, a logged MDT configuration including an event-driven logging configuration, the event-driven logging configuration identifying at least one condition to be satisfied for triggering logging of MDT while the UE is in idle or inactive mode.

Example Embodiment 14. The method of Embodiment 12, wherein the UE is in idle or inactive mode when performing the logging of MDT.

Example Embodiment 15. The method of any one of Embodiments 13 to 14, wherein the at least one measurements is performed based on radio reference signals that are used for idle/inactive mode cell reselection.

Example Embodiment 16. The method of any one of Embodiments 13 to 15, further comprising configuring the UE to perform any sensor related measurements continuously.

Example Embodiment 17. The method of any one of Embodiments 13 to 17, further comprising configuring the UE to continuously maintain any measurement that is required to perform event condition evaluation.

Example Embodiment 18. The method of any one of Embodiments 13 to 17, further comprising configuring the UE to log all available measurements.

Example Embodiment 19. The method of any one of Embodiments 13 to 18, further comprising receiving, from the UE, the log of MDT.

Example Embodiment 20. The method of Embodiment 19, wherein the log comprises at least one measurement associated with an event for which the at least one condition is satisfied. Example Embodiment 21. The method of any one of Embodiments 13 to 20, wherein the event-driven logging configuration includes a priority for each group of sub events, and the method further comprises configuring the UE to overwrite a low priority measurement with a high priority measurement if a memory of the UE is full.

Example Embodiment 22. The method of any one of Embodiments 13 to 21, further comprising configuring an overwrite protection indicator for a specific event or group of events and configuring the UE not to report a stored MDT log from a previous configuration with overwrite protection to the network before logging MDT measurements based on new received MDT logs.

Example Embodiment 23. The method of any one of Embodiments 13 to 11, further comprising, upon coming back to connected, transmitting the logged MDT measurements to the network node.

Example Embodiment 24. A wireless device for improving network efficiency, the wireless device comprising: processing circuitry configured to perform any of the steps of any of Example Embodiments 1 to 12; and power supply circuitry configured to supply power to the wireless device.

Example Embodiment 25. A base station for improving network efficiency, the base station comprising: processing circuitry configured to perform any of the steps of any of Example Embodiments 13 to 23; power supply circuitry configured to supply power to the wireless device.

Example Embodiment 26. A user equipment (UE) for improving network efficiency, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of Example Embodiments 1 to 12; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Example Embodiment 27. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Example Embodiments 13 to 23.

Example Embodiment 28. The communication system of the pervious embodiment further including the base station.

Example Embodiment 29. The communication system of the previous 2 embodiments, further including the EE, wherein the EE is configured to communicate with the base station.

Example Embodiment 30. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the EE comprises processing circuitry configured to execute a client application associated with the host application.

Example Embodiment 31. A method implemented in a communication system including a host computer, a base station and a user equipment (EE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of Example Embodiments 13 to 23.

Example Embodiment 32. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

Example Embodiment 33. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

Example Embodiment 34. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

Example Embodiment 35. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of Example Embodiments 1 to 12. Example Embodiment 36. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE

Example Embodiment 37. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

Example Embodiment 38. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of Example Embodiments 1 to 12.

Example Embodiment 39. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

Example Embodiment 40. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of Example Embodiments 1 to 12.

Example Embodiment 41. The communication system of the previous embodiment, further including the UE.

Example Embodiment 42. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

Example Embodiment 43. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

Example Embodiment 44. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

Example Embodiment 45. A method implemented in a communication system including a host computer, a base station and a user equipment (EGE), the method comprising: at the host computer, receiving user data transmitted to the base station from the EGE, wherein the EGE performs any of the steps of any of Example Embodiments 1 to 12.

Example Embodiment 56. The method of the previous embodiment, further comprising, at the EGE, providing the user data to the base station.

Example Embodiment 47. The method of the previous 2 embodiments, further comprising: at the TIE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

Example Embodiment 48. The method of the previous 3 embodiments, further comprising: at the TIE, executing a client application; and at the TIE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

Example Embodiment 49. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (TIE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Example Embodiments 13 to 23.

Example Embodiment 50. The communication system of the previous embodiment further including the base station.

Example Embodiment 51. The communication system of the previous 2 embodiments, further including the TIE, wherein the TIE is configured to communicate with the base station.

Example Embodiment 52. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the TIE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer. Example Embodiment 53. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of Example Embodiments 1 to 12.

Example Embodiment 54. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE

Example Embodiment 55. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

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

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

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

Claims

1. A method (1400) performed by a wireless device (210), the method comprising:

receiving (1410), from a base station (260), a configuration for logging a Minimization of Driving Test, MDT, measurement, the configuration including an event-driven logging configuration;

performing (1420) at least one measurement associated with an event configured in the event-driven logging configuration;

determining (1430) that at least one condition associated with the event-driven logging configuration has been satisfied; and

in response to determining that the at least one condition has been satisfied, performing (1440) logging of the at least one measurement.

2. The method of Claim 1, wherein the event-driven logging configuration identifies at least one event for triggering when to log the at least one measurement.

3. The method of Claim 2, wherein the at least one event for triggering when to log the at least one measurement comprises detection of a coverage hole in a camped frequency.

4. The method of Claim 2, wherein the at least one event for triggering when to log the at least one measurement comprises detection of a camped cell quality below a threshold.

5. The method of Claim 2, wherein the at least one event for triggering when to log the at least one measurement comprises at least one of:

an event associated with a speed event;

an event associated with a coverage of a beam;

an event associated with a WiFi measurement for MDT;

an event associated with a Bluetooth measurement for MDT;

an event associated with a battery consumption measurement of the wireless device; an event associated with a Quality of Service, QoS, measurement; and

an event associated with a sensor.

6. The method of any one of Claims 1 to 5, wherein the wireless device is in idle or inactive mode when performing the logging of the at least one measurement, and the method further comprises transmitting the logged the least one measurement to the base station upon returning to a connected mode.

7. The method of any one of Claims 1 to 6, wherein the at least one measurement is performed based on at least one radio reference signal that is used for idle/inactive mode cell reselection.

8. The method of any one of Claims 1 to 7, wherein performing the logging of the at least one measurement comprises logging all available measurements.

9. The method of any one of Claims 1 to 8, wherein the at least one measurement that is logged is associated with an event for which the at least one condition is satisfied.

10. The method of any one of Claims 1 to 9, wherein the event-driven logging configuration includes a priority for each group of a plurality of groups of sub events, and wherein when a memory of the wireless device is full, the method comprises overwriting a low priority measurement with a high priority measurement.

11. A method (1600) performed by a base station (260), the method comprising:

transmitting (1600), to a wireless device (210), a configuration for logging a

Minimization of Driving Test, MDT, measurement, the configuration including an event- driven logging configuration, the event-driven logging configuration identifying at least one condition to be satisfied for triggering logging of at least one measurement while the wireless device is in an idle or inactive mode.

12. The method of Claim 11, wherein the event-driven logging configuration identifies at least one event for triggering when to log the at least one measurement.

13. The method of any one of Claims 11 to 12, further comprising configuring the wireless device to log all available measurements.

14. The method of any one of Claims 11 to 13, further comprising receiving, from the wireless device, the log of the at least one measurement.

15. The method of any one of Claims 11 to 14, wherein the at least one measurement is associated with an event for which the at least one condition is satisfied.

16. The method of any one of Claims 11 to 15, wherein the event-driven logging configuration includes a priority for each group of a plurality of groups of sub events, and the method further comprises configuring the wireless device to overwrite a low priority measurement with a high priority measurement when a memory of the wireless device is full.

17. A wireless device (210) comprising:

processing circuitry (220) configured to:

receive, from a base station (260), a configuration for logging a Minimization of Driving Test, MDT, measurement, the configuration including an event-driven logging configuration;

perform at least one measurement associated with an event configured in the event-driven logging configuration;

determine that at least one condition associated with the event-driven logging configuration has been satisfied; and

in response to determining that the at least one condition has been satisfied, perform logging of the at least one measurement.

18. The wireless device of Claim 17, wherein the event-driven logging configuration identifies at least one event for triggering when to log the at least one measurement.

19. The wireless device of Claim 18, wherein the at least one event for triggering when to log the at least one measurement comprises detection of a coverage hole in a camped frequency.

20. The wireless device of Claim 18, wherein the at least one event for triggering when to log the at least one measurement comprises detection of a camped cell quality below a threshold.

21. The wireless device of Claim 18, wherein the at least one event for triggering when to log the at least one measurement comprises at least one of:

an event associated with a speed event;

an event associated with a coverage of a beam;

an event associated with a WiFi measurement for MDT;

an event associated with a Bluetooth measurement for MDT;

an event associated with a sensor.

22. The wireless device of any one of Claims 17 to 21, wherein the wireless device is in idle or inactive mode when performing the logging of the at least one measurement, and the processing circuitry is further configured to transmit the logged the least one measurement to the base station upon returning to a connected mode.

23. The wireless device of any one of Claims 17 to 22, wherein the at least one measurement is performed based on at least one radio reference signal that is used for idle/inactive mode cell reselection.

24. The wireless device of any one of Claims 17 to 23, wherein when performing the logging of the at least one measurement the processing circuitry is configured to log all available measurements.

25. The wireless device of any one of Claims 17 to 24, wherein the at least one measurement that is logged is associated with an event for which the at least one condition is satisfied.

26. The wireless device of any one of Claims 17 to 25, wherein the event-driven logging configuration includes a priority for each group of a plurality of groups of sub events, and wherein when a memory of the wireless device is full, the processing circuitry is configured to overwrite a low priority measurement with a high priority measurement.

27. A base station (260) comprising:

processing circuitry (270) configured to:

transmit, to a wireless device (210), a configuration for logging a Minimization of Driving Test, MDT, measurement, the configuration including an event-driven logging configuration, the event-driven logging configuration identifying at least one condition to be satisfied for triggering logging of at least one measurement while the wireless device is in an idle or inactive mode.

28. The base station of Claim 27, wherein the event-driven logging configuration identifies at least one event for triggering when to log the at least one measurement.

29. The base station of any one of Claims 27 to 28, wherein the processing circuity is configured to configure the wireless device to log all available measurements.

30. The base station of any one of Claims 27 to 29, wherein the processing circuitry is configured to receive, from the wireless device, the log of the at least one measurement.

31. The base station of any one of Claims 27 to 30, wherein the at least one measurement is associated with an event for which the at least one condition is satisfied.

32. The base station of any one of Claims 27 to 31, wherein the event-driven logging configuration includes a priority for each group of a plurality of groups of sub events, and the processing circuitry is configured to configure the wireless device to overwrite a low priority measurement with a high priority measurement when a memory of the wireless device is full.

33. A wireless device (210) adapted to perform a method according to any one of Claims 1 to 10.

34. A base station (760) adapted to perform a method according to any one of Claims 11 to 16.