Patent Description:
Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (<NUM>) radio access technology or new radio (NR) access technology, or other communications systems. The invention relates to methods, apparatuses and non-transitory computer readable medium. <CIT> discloses logged minimization of drive test (MDT) measurements recorded at the UE at a selected rate when the UE is in a radio resource control (RRC) idle mode in a first LTE cell in a cellular network. A change in a UE state of the RRC idle mode can be identified. The Logged MDT measurements can stop being recorded at the UE when the UE state changes from a camped normally UE state to another UE state of the RRC idle mode. The Logged MDT measurements can resume being recorded when the UE state changes to the camped normally UE state of the RRC idle mode.

Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, and/or fifth generation (<NUM>) radio access technology or new radio (NR) access technology. Fifth generation (<NUM>) wireless systems refer to the next generation (NG) of radio systems and network architecture. <NUM> is mostly built on a new radio (NR), but the <NUM> (or NG) network can also build on E-UTRAN radio. It is estimated that NR will provide bitrates on the order of <NUM>-<NUM> Gbit/s or higher, and will support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency-communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. It is noted that, in <NUM>, the nodes that can provide radio access functionality to a user equipment (i.e., similar to Node B in UTRAN or eNB in LTE) are named gNB when built on NR radio and named NG-eNB when built on E-UTRAN radio.

It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for preventing signaling based minimization of drive test (MDT) configuration overwrite in dual connectivity (DC).

For example, the usage of the phrases "certain embodiments," "an example embodiment," "some embodiments," or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases "in certain embodiments," "an example embodiment," "in some embodiments," "in other embodiments," or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

Additionally, if desired, the different functions or steps discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or steps may be optional or may be combined. As such, the following description should be considered as merely illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

<NUM>rd Generation Partnership (3GPP) describes radio access network (RAN) centric data collection, which can provide mechanisms to assist operators in monitoring and optimizing their <NUM> deployment. These mechanisms may also provide a standardized method for data collection and utilization. Self-organizing network (SON) and MDT-oriented solutions (from LTE) may provide a baseline in the newly standardized method for data collection. Thus, automated data collection in <NUM> may inherit the two types of MDT including, for example, immediate MDT and logged MDT. These two MDT methods provide the ability to deliver real-time measurements (e.g., results of measurements performed from radio resource management (RRM) operators), and non real-time measurement results taken during the time a user equipment (UE) is out of network reach (e.g., in a radio resource control (RRC) IDLE state), respectively.

Furthermore, 3GPP specifies necessary standard enablers to support MDT in DC. However, according to legacy methods, only a master node (MN) may trigger logged MDT and immediate MDT configurations. Additionally, in a single node case (MN) the baseline principles of handling logged MDT configuration(s) may imply that newly arriving configuration(s) may overwrite any previous configuration(s).

<FIG> illustrates an example MDT configuration in a DC scenario. In one example, DC may allow direct configurations by a secondary node (SN). However, there are currently no principles for handling the configuration and reporting in case two different nodes can schedule the same UE for the MDT. Further, if exactly the same method was applied for SN as it used to be for MN (<FIG>), the other node may overwrite a previous message to the UE given by MN. In addition, the overwrite may be done without informing MN that its configuration has been overwritten. This replacement has not been considered as a problem in legacy MDT, as MDT configuration was only one radio access technology (RAT) specific. With Evolved Universal Terrestrial Radio Access (E-UTRA) New Radio DC (EN-DC) deployment, the configuration received from MN and SN may represent two different RATs, and the replacement may imply ignoring the operations, administration, and maintenance (OAM) trigger to collect data from another technology (e.g., <NUM> vs. <NUM> or vice versa). The eNB (controlling cells from one RAT, i.e. E-UTRA) and the en-gNB or the gNB (controlling cells of another RAT, i.e. NR) may use separate OAM systems. For example, OAMs may be from two different vendors or two OAMs configurations paths from the same vendor (NR OAM and EUTRA OAM). Further, MDT configurations may originate from these OAM systems, and it should not be excluded that the OAM system responsible for the NR cells could also generate EUTRA MDT configurations for the purpose of multi-RAT dual connectivity (MR-DC). For the same reason, the OAM system responsible for the EUTRA cells could generate MDT configurations for both EUTRA and NR. In addition, the two configurations may target different purposes and different RATs.

Furthermore, MDT configuration may originate from either management-based (targeting an area) or signaling-based tracing (targeting a user). In a case where a RAN node receives a management-based trigger, it does not matter which UE will be selected for data collection. However, signaling based MDT may be triggered towards one particular UE. If a UE has been selected for signaling-based tracing, it may suggest that the operator had a reason (e.g., customer complaints/care) to trace the device performance. In one example, the UE may be MDT capable, and if its capability to collect data is selected by the other node (and RAT) to take part in management based MDT, the operator may lose the UE data. Further, lack of awareness that one node may involve the same UE in a different session than the other has not been resolved. Thus, realization of a method is currently non-existing in the standard, and therefore a solution is needed.

3GPP technical specifications (TS) generally describes immediate MDT configurations that are supported for DC scenarios. Further, logged MDT configurations may be received from the SN node in a DC scenario, and the existing MDT framework may be a baseline for the secondary cell group (SCG) cells related MDT configuration. In addition, the triggers for MDT measurements associated with master cell group (MCG) and SCG may be separate, and MN-SN coordination may be required for MDT measurements' configuration and reporting in the DC framework. Further, if signaling radio bearer (SRB) <NUM> is not configured, SN related measurements may be transmitted to the MN via SRB <NUM>/<NUM>, and then forwarded to the SN. However, if SRB3 is configured, then MN related measurements may be transmitted to the MN via SRB1/<NUM>, and SN related measurements may be transmitted to the SN via SRB3.

According to certain example embodiments, MDT configuration(s) may be handled in various scenarios including, for example, EN-DC scenarios where two RATs of two separate nodes are involved in triggering a UE to collect logged MDT data. Certain example embodiments also provide procedures to prioritize signaling based MDT over management based MDT, and ensure that the latter does not replace the configuration that has been specifically dedicated to the UE.

Certain example embodiments may also provide OAM and core network (CN) signaling procedures. For example, signaling between OAM and RAN for MDT trace activation may differentiate the configuration trigger for DC. In an example embodiment, the configuration may be split into LTE and NR specific MDT configurations.

Another example embodiment may provide procedures for inter-node signaling. Here, signaling between MN and SN may be defined to exchange information on the ongoing MDT configuration. Furthermore, the exchange may result in restricting the other node not to initiate any MDT configuration, or applying a limited configuration. For example, in one embodiment, restrictions may apply at least to avoid signaling based MDT overwriting. In another example embodiment, the exchange may result in feedback information towards the MN so that it instructs the SN how to generate MDT configuration(s). In another example embodiment, the exchange may result in storing the configuration and its propagation between the involved RAN nodes. In a further example embodiment, the exchange may result in feedback information towards the CN entity so that it receives information on impossibility to apply the sent MDT configuration(s).

Certain example embodiments may also provide certain UE procedures. For instance, according to one example embodiment, the UE may be capable of receiving logged MDT configuration(s) from the SN, managing in case of conflicting configuration(s) received, and notifying the network about the conflict.

According to certain example embodiments, trace configuration triggers may be extended with DC support for EN-DC. In an example embodiment, at the time of generating the MDT configuration, OAM may provide trace configuration (which may be mapped into another control message such as for example trace activation message) parameters applicable for MN only, SN only, or both. For example, in one embodiment, trace configuration parameters may include a flag on DC applicability. This attribute may be further compiled in a network node (e.g., an evolved NodeB (eNB) or gNB) to generate MDT signaling that allows LTE MDT specific configuration and NR MDT specific configuration. Alternatively, in another example embodiment, trace configuration parameters may directly include NR MDT specific configuration triggers (NR MDT configuration e.g. MDT configuration <NUM> in <FIG>). In a further example embodiment, the parameters may be implemented as MDT specific configuration parameters in an initial context setup request message.

Based on the received MDT configuration, in an example embodiment, the receiving node (e.g., eNB or gNB), which may be involved in EN-DC, may determine NR specific MDT configuration parameters that may include periodicity or event-triggered configurations for NR radio measurement results. According to another example embodiment, the receiving node may determine trace activation for signaling based MDT type, which may be provided with the NR specific MDT configuration parameters or the flag on DC applicability. In an example embodiment, the parameters may be defined or applied on LTE, NR, or both. In another example embodiment, the trace activation for signaling based MDT type may be received over an S1 application protocol (AP).

According to certain example embodiments, the MN may compile the MDT configuration that includes a legacy part (EUTRAN MDT configuration, e.g. MDT configuration <NUM> in <FIG>), and a newly supported enabler for EN-DC specific MDT configuration. In an example embodiment, the MN may generate signaling towards the SN to negotiate priorities and processing of MDT NR configurations. For instance, in an example embodiment, the MN may decide whether to send NR MDT configuration to the SN so that the SN may trigger (e.g., send or transmit) the configuration towards the UE.

According to an example embodiment, if the original configuration from the OAM was signaling-based MDT, then the MN may restrict the SN from selecting the same UE for configuration of management based MDT. For instance, in an example embodiment, the MN may decide whether to send NR MDT configuration to the SN so that the SN may trigger the configuration towards the UE. In another example embodiment, this may be accomplished by using an X2 interface message with a flag to not involve the UE in the management-based MDT. In a further example embodiment, this may be accomplished by using an X2 interface message with a flag to not allow the management-based MDT due to involvement in DC. Alternatively, in another example embodiment, if the procedure is extended to a MR-DC case, the SN may inform the MN about restriction(s) not to involve the same UE in management based MDT if it was already involved in signaling-based MDT. For instance, the SN may decide to inform the MN that the signaling based configuration towards the UE has been made, and management-based MDT should not be allowed in the MN area. In a further example embodiment, this may be accomplished by using an Xn interface message with a flag to not allow the management-based MDT due to involvement in DC. According to a further example embodiment, based on the information exchange of the MN with the SN, the SN may be triggered to send the NR MDT configuration to the UE. For example, the SN may process the NR MDT configuration to send a LoggedMeasurementConfiguration over SRB3 with RRC signaling.

In certain example embodiments, the UE procedures may follow the MN-SN information exchange, or manage the two incoming MDT configurations for EN-DC by itself (in case the network-based exchange is not supported). For instance, in one embodiment, the UE may maintain one MDT configuration at a time. This may include, for example, the UE replacing the previous MDT configuration. In another example embodiment, the UE may log the event of overwriting MDT configuration. For example, the MDT data may be reported back to the network, and based on an analysis of the data by the network, the network may know that there was an attempt to configure the same UE for different MDT configurations. In addition, based on certain post-processing, it may be possible to determine the overall situation. According to a further example embodiment, the UE may log time stamps. The logged record may be realized by either placing logged MDT configuration (e.g., logged EUTRA MDT configuration) in the measurement logs, or tagging in the log with an indication that there were other RATs attempting the logged MDT configuration. According to another example embodiment, upon receiving the LoggedMeasurementConfiguration, the UE may detect which SRB has been used to pass the configuration, and may store the event in case configuration replacement concerned configurations coming from MN (e.g., eNB) and SN (e.g., gNB). In another example embodiment, the UE may store contexts and one or more MDT configurations.

In 3GPP TS <NUM>, the E-UTRAN may initiate the logged measurement configuration procedure to the UE in RRC_CONNECTED state by sending the LoggedMeasurementConfiguration message via SRB1. When the UE is configured with DC, NG-RAN may initiate the logged measurement configuration procedure to the UE via SRB3. In certain example embodiments, upon receiving the LoggedMeasurementConfiguration message, the UE may, if the configuration was initiated by E-UTRAN, store the configuration-RAT set to E-UTRAN in a VarLogMeasConfig. Otherwise, the UE may store the configuration-RAT set to NG-RAN in the VarLogMeasConfig. According to an example embodiment, upon receiving the report and VarLogMeasConfig, the network may recognize that replacement of the configuration took place, which may allow the network to react accordingly.

According to an example embodiment, the logging principles for the UE in LTE may be enhanced in a way that it may always measure all possible detected cells, including LTE and NR as serving cells, and marks in the log that there was a change in the serving cell (RAT). In an example embodiment, this implementation may ensure broadcast data collection covers all possible detectable radio measurements by the UE without ignoring any RAT-specific configuration.

In certain example embodiments, the measurement results may cover LTE measurement results and neighboring cells resulting from cell re-selection process, NR measurement results and all neighboring cells resulting from cell re-selection process, and any cell selection state indicating lack of detectable cell in LTE and NR. In all the above cases, the UE may indicate the serving cell and RAT (and the change in serving RAT). In another example embodiment, the UE may indicate in the log, a serving RAT change and, thus, a serving cell change.

According to certain example embodiments, the UE may keep both MDT configurations and two MDT contexts. For instance, in two separate variables for logged measurement results, the UE may store LTE and NR specific logs according to a RAT-specific configuration. In addition, the UE may tag different log information pertaining to different MDT configurations, i.e. RAT-specific or configuration trigger specific (e.g. management based or signaling based-tracing).

Additionally, certain example embodiments may provide radio access network trace collection entity (RAN-TCE) signaling. In RAN-TCE signaling, the MN node may retrieve MDT reports from the UE, and may forward the data to a TCE. However, in certain example embodiments, the signaling procedures and formats that result from the interaction defined for DC support that different RAT-specific records are sent in one reporting file.

<FIG> illustrates a flow diagram of a method, according to certain example embodiments. In certain example embodiments, the flow diagram of <FIG> may be performed by a mobile station and/or UE, for instance similar to apparatus <NUM> illustrated in <FIG>. According to one example embodiment, the method of <FIG> may include initially, at <NUM>, receiving, at a UE, a configuration message from a network element. The method may also include, at <NUM>, detecting a signaling radio bearer that has been used to transmit the configuration message. In addition, the method may include, at <NUM>, storing the configuration message according to a trigger associated with the configuration message, wherein the configuration message may be either management-based or signaling-based. At <NUM>, the method may include performing measurement data collection pertaining to a cell according to the configuration message.

In an example embodiment, storing the configuration message may occur according to a radio access technology associated with the configuration message. In another example embodiment, the method may further include identifying a serving cell and a serving radio access technology of the UE. According to another example embodiment, the method may include identifying a trigger pertaining to signaling-based tracing or management-based tracing. According to further example embodiments, the method may include managing the configuration message in case of a conflict with another configuration message, and notifying the network element about the conflict or the stored configuration message (e.g. positive or negative response or reject message). In an example embodiment, managing of the configuration message may imply storing the configuration message. Yet, in another example embodiment, managing of the configuration message may imply ignoring or rejecting the configuration message. In a further example embodiment, the configuration message may include minimization of drive tests configurations for evolved universal terrestrial radio access new radio dual connectivity. According to another example embodiment, the method may include storing LTE and NR specific logs. In a further example embodiment, the method may include tagging the LTE and NR specific logs.

<FIG> illustrates a flow diagram of another method, according to certain example embodiments. In an example embodiment, the method of <FIG> may be performed by a telecommunications network, network entity or network node in a 3GPP system, such as LTE or <NUM>-NR. For instance, in an example embodiment, the method of <FIG> may be performed by a base station, eNB, or gNB for instance similar to apparatus <NUM> illustrated in <FIG>.

According to an example embodiment, the method of <FIG> may include initially, at <NUM>, determining, by a network element, a new radio specific minimization of drive test configuration parameter, or a trace activation for a signaling based minimization of drive test.

The method may also include, at <NUM>, configuring a UE by sending a configuration message to the UE. Further, at <NUM>, the method may include signaling a message to another network element to negotiate a priority and a processing procedure of a MDT configuration for the user equipment. In an example embodiment, negotiating the priority and the processing procedure may include restricting the another network element from selecting the user equipment for MDT configuration.

According to an example embodiment, the message may include a flag indicating to the another network not to select the user equipment. According to an example embodiment, the message may include a flag indicating to the another network element not to allow management based MDT configuration due to involvement in signaling based MDT configuration. According to further example embodiments, the message may include a flag indicating to the network element to inform about ongoing involvement in signaling based minimization of drive test configuration to not to allow management based minimization of drive test configuration. In a further example embodiment, the message may include a flag indicating to the another network element not to propagate management based MDT configuration due to involvement in signaling based MDT configuration. According to another example embodiment, the configuration message may include minimization of drive tests configurations for evolved universal terrestrial radio access new radio dual connectivity.

<FIG> illustrates an apparatus <NUM> according to certain example embodiments. In an embodiment, apparatus <NUM> may be a node or element in a communications network or associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, stationary device, IoT device, or other device. As described herein, UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user device, subscriber station, wireless terminal, tablet, smart phone, IoT device, sensor or NB-IoT device, or the like. As one example, apparatus <NUM> may be implemented in, for instance, a wireless handheld device, a wireless plug-in accessory, or the like.

For example, it should be understood that, in certain example embodiments, apparatus <NUM> may include two or more processors that may form a multiprocessor system (e.g., in this case processor <NUM> may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

Processor <NUM> may perform functions associated with the operation of apparatus <NUM> including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus <NUM>, including processes illustrated in <FIG> and <FIG>.

For example, the external computer readable storage medium may store a computer program or software for execution by processor <NUM> and/or apparatus <NUM> to perform any of the methods illustrated in <FIG> and <FIG>.

According to certain example embodiments, processor <NUM> and memory <NUM> may be included in or may form a part of processing circuitry or control circuitry.

As discussed above, according to certain example embodiments, apparatus <NUM> may be a UE for example. According to certain embodiments, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to perform the functions associated with example embodiments described herein. For instance, in one embodiment, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to receive a configuration message from a network element. Apparatus <NUM> may also be controlled by memory <NUM> and processor <NUM> to detect a signaling radio bearer that has been used to transmit the configuration message. Apparatus <NUM> may further be controlled by memory <NUM> and processor <NUM> to store the configuration message according to a trigger associated with the configuration message, wherein the configuration message may be either management-based or signaling-based. In addition, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to perform measurement data collection pertaining to a cell according to the configuration message.

<FIG> illustrates an apparatus <NUM> according to certain example embodiments. In an example embodiment, the apparatus <NUM> may be a RAT, node, host, or server in a communication network or serving such a network. For example, apparatus <NUM> may be a base station, a Node B, an evolved Node B (eNB), <NUM> Node B or access point, next generation Node B (NG-NB, en-gNB or gNB), and/or WLAN access point, associated with a radio access network (RAN), such as an LTE network, <NUM> or NR.

For example, processor <NUM> may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster.

According to certain example embodiments, processor <NUM> may perform functions associated with the operation of apparatus <NUM>, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus <NUM>, including processes illustrated in <FIG> and <FIG>.

For example, the external computer readable storage medium may store a computer program or software for execution by processor <NUM> and/or apparatus <NUM> to perform the methods illustrated in <FIG> and <FIG>.

In certain example embodiments, apparatus <NUM> may also include or be coupled to one or more antennas <NUM> for transmitting and receiving signals and/or data to and from apparatus <NUM>. Apparatus <NUM> may further include or be coupled to a transceiver <NUM> configured to transmit and receive information. The transceiver <NUM> may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) <NUM>. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, <NUM>, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink).

As used herein, the term "circuitry" may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to cause an apparatus (e.g., apparatus <NUM> and <NUM>) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation.

As introduced above, in certain embodiments, apparatus <NUM> may be a radio resource manager, RAT, node, host, or server in a communication network or serving such a network. For example, apparatus <NUM> may be a satellite, base station, a Node B, an evolved Node B (eNB), <NUM> Node B or access point, next generation Node B (NG-NB, en-gNB or gNB), and/or WLAN access point, associated with a radio access network (RAN), such as an LTE network, <NUM> or NR. According to certain embodiments, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to perform the functions associated with any of the embodiments described herein.

For instance, in one embodiment, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to determine a new radio specific minimization of drive test configuration parameter, or a trace activation for a signaling based minimization of drive test. Apparatus <NUM> may also be controlled by memory <NUM> and processor <NUM> to configure a UE by sending the configuration message to the UE. In addition, apparatus <NUM> may be controlled by memory <NUM> and processor <NUM> to signal a message to a network element to negotiate a priority and a processing procedure of a MDT configuration for the user equipment.

Further example embodiments may provide means for performing any of the functions or procedures described herein. For example, certain example embodiments may be directed to an apparatus that includes means for receiving a configuration message from a network element. The apparatus may also include means for detecting a signaling radio bearer that has been used to transmit the configuration message. The apparatus may further include means for storing the configuration message according to a trigger associated with the configuration message, wherein the configuration message may be either management-based or signaling-based. In addition, the apparatus may include means for performing measurement data collection pertaining to a cell according to the configuration message.

Other example embodiments may be directed to a further apparatus that includes means for determining a new radio specific minimization of drive test configuration parameter, or a trace for a signaling based minimization of drive test. The apparatus may also include means for configuring a user equipment by sending a configuration message to the user equipment. The apparatus may further include means for signaling a message to a network element to negotiate a priority and a processing procedure of a minimization of drive test configuration for the user equipment.

Certain example embodiments described herein provide several technical improvements, enhancements, and /or advantages. In some example embodiments, it may be possible to provide network coordination to avoid negative impact on the UE. It may also be possible to provide a mechanism for managing a UE's contexts, and coordinating between different MDT configurations from different network nodes. Additionally, it may be possible to provide a mechanism to prevent MDT configuration overwrite in a UE under an EN-DC deployment. Additionally, it may be possible to provide a mechanism to enable customer care process, and coordination on tracing critical issues in the network in inter-RAT deployments. Furthermore, it may be possible to provide a mechanism to control simultaneous configurations coming from different origins (e.g., RATs, vendors).

According to another example embodiment, it may be possible to enhance logging principles for the UE in LTE. It may also be possible to ensure that broadcast data collection covers all possible detectable radio measurements by the UE without ignoring any RAT-specific configuration.

A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. The computer readable medium or computer readable storage medium may be a non-transitory medium.

In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus <NUM> or apparatus <NUM>), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

According to an example embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. Although the above embodiments refer to <NUM> NR and LTE technology, the above embodiments may also apply to any other present or future 3GPP technology, such as LTE-advanced, and/or fourth generation (<NUM>) technology.

A first embodiment is directed to a method that may include receiving, at a user equipment, a configuration message from a network element. The method may also include detecting a signaling radio bearer that has been used to transmit the configuration message. The method may further include storing the configuration message according to a radio access technology associated with the configuration message. In addition, the method may include performing measurement data collection pertaining to a cell according to the configuration message.

In a variant, the method may further include identifying a serving cell and a serving radio access technology of the user equipment.

In a variant, the method may further include managing the configuration message in case of a conflict with another configuration message, and notifying the network element about the conflict.

In a variant, the configuration message may include minimization of drive tests configurations for evolved universal terrestrial radio access new radio dual connectivity.

In a variant, the method may further include storing long-term evolution and new radio specific logs.

In a variant, the method may further include tagging the long-term evolution and new radio specific logs.

A second embodiment may be directed to a method that may include determining, by a network element, a new radio specific minimization of drive test configuration parameter, or a trace for a signaling based minimization of drive test. The method may also include configuring a user equipment by sending a configuration message to the user equipment. The method may further include signaling a message to another network element to negotiate a priority and a processing procedure of the MDT configuration for the user equipment.

In a variant, negotiating the priority and the processing procedure may include restricting the another network element from selecting the user equipment for MDT configuration.

In a variant, the message may include a flag indicating to the another network not to select the user equipment.

In a variant, the message may include a flag indicating to the another network not to allow management based MDT configuration due to involvement in signaling based MDT configuration.

In a variant, the message may include a flag indicating to the another network not to propagate management based MDT configuration due to involvement in signaling based MDT configuration.

In a variant, the configuration message comprises minimization of drive tests configurations for evolved universal terrestrial radio access new radio dual connectivity.

Another embodiment is directed to an apparatus including at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus at least to perform the method according to the first embodiment or the second embodiment or any of their variants discussed above.

Another embodiment is directed to an apparatus that may include circuitry configured to perform the method according to the first embodiment or the second embodiment or any of their variants.

Another embodiment is directed to an apparatus that may include means for performing the method according to the first embodiment or the second embodiment or any of their variants.

Claim 1:
A method, comprising:
receiving (<NUM>), at a user equipment, a configuration message from a network element, wherein the configuration message is for either management-based or signaling-based logged measurement;
identifying a trigger pertaining to signaling-based tracing or management-based tracing;
storing (<NUM>) the configuration message according to the trigger associated with the configuration message; and
performing (<NUM>) measurement data collection pertaining to a cell according to the configuration message.