Handling of multiple minimization of drive test contexts in multiple radio resource controller states

Abstract

Systems, methods, apparatus, and computer program products for processing multiple minimization of drive tests (MDT) contexts for use in a radio resource controller (RRC) state. A method may include receiving a logged measurement configuration from a network element, the logged measurement configuration including specific configuration content for a user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment. The method may also include performing logging of measurements by state of the user equipment according to the specific configuration content in the logged measurement configuration. The method may also include transmitting to the network element a report of logged measurements related to one of the user equipment states. The specific configuration content may restrict logging according to one or more of: network-based selection criteria, and user equipment-based selection criteria.

Description

Technical Field

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as long term evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or may relate to other communication systems. For example, certain embodiments may relate to apparatus, systems and / or methods for handling multiple minimization of drive tests (MDT) contexts for use in a radio resource controller (RRC) state. Background Art

[0002] 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), Advanced LTE (LTE-A), MulteFire, LTE-A Pro and / or fifth generation (5G) radio access technology or new radio (NR) access technology. Fifth generation (5G) wireless systems refer to next generation (NG) radio systems and network architectures. 5G is primarily built on New Radio (NR), but 5G (or NG) networks can also be built on E-UTRAN radios (E-UTRAN connected to a 5G core, also known as eLTE). It is estimated that NR will provide bit rates of 10-20G bit / s or higher and will support at least enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC) and massive machine type communications (mMTC). NR is expected to provide ultra-wideband and ultra-robust, low latency connectivity and massive networks to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become more prevalent, the demand for networks that can meet the requirements of low power consumption, low data rates, and long battery life will continue to grow. Note that in 5G, a node that can provide radio access functions for user equipment (i.e., similar to a Node B in UTRAN or an eNB in ​​LTE) is called a gNB when built on an NR radio and is called an NG-eNB when built on an E-UTRAN radio.

[0003] 5G is expected to have multiple radio interfaces, namely, sub-6GHz, cmWave, and mmWave, and can also be integrated with existing legacy radio access technologies (e.g., LTE). At least in the early stages, integration with LTE can be implemented as a system in which macro coverage is provided by LTE and 5G radio interface access comes from small cells by aggregation to LTE. In other words, 5G plans to support both inter-RAT operability (e.g., LTE-5G) and inter-RI operability (inter-radio interface operability, such as sub-6GHz-cmWave, sub-6GHz-cmWave-mmWave). One of the concepts considered for use in 5G networks is network slicing, in which multiple independent and dedicated virtual subnets (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0004] The current architecture in LTE networks is completely distributed in the radio and completely centralized in the core network. Low-latency applications and services in 5G require content to be close to the radio, resulting in local outages and multi-access edge computing (MEC). 5G enables analysis and knowledge generation to occur at the data source. This approach requires the use of resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also enables the storage and processing of content close to cellular subscribers, thereby speeding up response times. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data collection, mobile signature analysis, collaborative distributed point-to-point self-organizing networks and processing can also be classified as local cloud / fog computing and grid / grid computing, dew computing, mobile edge computing, micro cloud (cloudlet), distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and / or latency critical) and critical communications (autonomous vehicles, traffic safety, real-time analysis, time-critical control, healthcare applications). Summary of the invention

[0005] According to some example embodiments, a method may include receiving a logged measurement configuration from a network element, the logged measurement configuration including specific configuration content for a user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment. The method may also include performing logging of measurements by state of the user equipment according to the specific configuration content in the logged measurement configuration. The method may also include transmitting to the network element a report of logged measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may restrict logging according to one or more of: network-based selection criteria, and user equipment-based selection criteria.

[0006] According to some example embodiments, an apparatus may include means for receiving a logged measurement configuration from a network element, the logged measurement configuration including specific configuration content for a user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment. The apparatus may also include means for performing logging of measurements by state of the user equipment according to the specific configuration content in the logged measurement configuration. The apparatus may also include means for transmitting to the network element a report of logged measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may restrict logging according to one or more of: network-based selection criteria, and user equipment-based selection criteria.

[0007] According to some example embodiments, an apparatus may include 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 to, together with the at least one processor, cause the apparatus to at least receive a logging measurement configuration from a network element, the logging measurement configuration including specific configuration content for a user equipment, the specific configuration content being differentiated by and depending on the connection state of the user equipment. The apparatus may also be caused to perform logging of measurements according to the state configuration content of the user equipment in the logging measurement configuration. The apparatus may also be caused to transmit to the network element a report of the logged measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may be recorded based on one or more of the following restrictions: network-based selection criteria, and user equipment-based selection criteria.

[0008] According to some example embodiments, a non-transitory computer readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may receive a recorded measurement configuration from a network element, the recorded measurement configuration including specific configuration content for a user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment. The method may also perform recording of measurements by state of the user equipment according to the specific configuration content in the recorded measurement configuration. The method may also transmit to the network element a report of recorded measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may restrict recording according to one or more of the following: network-based selection criteria, and user equipment-based selection criteria.

[0009] According to some example embodiments, a computer program product may perform a method. The method may receive a log measurement configuration from a network element, the log measurement configuration including specific configuration content for a user equipment, the specific configuration content being differentiated by and depending on a connection state of the user equipment. The method may also perform logging of measurements by state of the user equipment according to the specific configuration content in the log measurement configuration. The method may also transmit to the network element a report of the logged measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may restrict logging according to one or more of: a network-based selection criterion, and a user equipment-based selection criterion.

[0010] According to some example embodiments, an apparatus may include a circuit device configured to receive a recorded measurement configuration from a network element, the recorded measurement configuration including specific configuration content for a user equipment, the specific configuration content being differentiated by and depending on a connection state of the user equipment. The circuit device may also be configured to perform recording of measurements by the state of the user equipment according to the specific configuration content in the recorded measurement configuration. The circuit device may also be configured to transmit a report of recorded measurements related to one of the user equipment states to the network element. In an example embodiment, the specific configuration content may restrict recording according to one or more of: network-based selection criteria, and user equipment-based selection criteria.

[0011] According to some example embodiments, a method may include sending a logged measurement configuration to a user equipment, the logged measurement configuration including specific configuration content for the user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment. The method may also include receiving from the user equipment a report of logged measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may restrict logging according to one or more of: network-based selection criteria, and user equipment-based selection criteria.

[0012] According to some example embodiments, an apparatus may include means for sending a logged measurement configuration to a user equipment, the logged measurement configuration including specific configuration content for the user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment. The apparatus may also include means for receiving from the user equipment a report of logged measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may restrict logging according to one or more of: network-based selection criteria, and user equipment-based selection criteria.

[0013] According to some example embodiments, an apparatus may include 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 to, together with the at least one processor, cause the apparatus to at least send a recorded measurement configuration to a user equipment, the recorded measurement configuration including specific configuration content for the user equipment, the specific configuration content being differentiated by and depending on the connection state of the user equipment. The apparatus may also be caused to receive from the user equipment a report of recorded measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may be recorded based on one or more of the following restrictions: network-based selection criteria, and user equipment-based selection criteria.

[0014] According to some example embodiments, a non-transitory computer readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may send a recorded measurement configuration to a user equipment, the recorded measurement configuration including specific configuration content for the user equipment, the specific configuration content being differentiated by and dependent on the connection state of the user equipment. The method may also receive from the user equipment a report of recorded measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may restrict recording according to one or more of: network-based selection criteria, and user equipment-based selection criteria.

[0015] According to some example embodiments, a computer program product may perform a method. The method may send a logged measurement configuration to a user equipment, the logged measurement configuration including specific configuration content for the user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment. The method may also receive from the user equipment a report of logged measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may restrict logging according to one or more of: network-based selection criteria, and user equipment-based selection criteria.

[0016] According to some embodiments, an apparatus may include a circuit device configured to send a recorded measurement configuration to a user equipment, the recorded measurement configuration including specific configuration content for the user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment. The circuit device may also be configured to receive from the user equipment a report of recorded measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may restrict recording according to one or more of: network-based selection criteria, and user equipment-based selection criteria. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] For a proper understanding of the exemplary embodiments, reference should be made to the accompanying drawings, in which:

[0018] Figure 1 An example Minimization of Drive Tests (MDT) measurement configuration for logging MDT is shown.

[0019] Figure 2a A process for handling multiple MDT contexts in multiple radio resource controller (RRC) states according to an example embodiment is shown.

[0020] Figure 2b Another process for handling multiple MDT contexts in multiple RRC states according to an example embodiment is shown.

[0021] Figure 3 A possible Logged Measurement Configuration (LMC) message ASN.1 syntax and implementation according to an example embodiment is shown.

[0022] Figure 4 A second LMC message implementation according to an example embodiment is shown.

[0023] Figure 5 An LMC storage implementation according to an example embodiment is shown.

[0024] Figure 6 A VarLogMeasConfigInactive (VLMCI) implementation according to an example embodiment is shown.

[0025] Figure 7 A VLM Report (VLMR) User Equipment (UE) variable implementation according to an example embodiment is shown.

[0026] Figure 8 A VLMR Inactive (VLMRI) UE variant implementation according to an example embodiment is shown.

[0027] Fig. 9 A flow chart of a method according to an example embodiment is shown.

[0028] Fig.10 A flow chart of another method according to an example embodiment is shown.

[0029] Fig.11a A block diagram of an apparatus according to an example embodiment is shown.

[0030] Fig.11b A block diagram of another apparatus according to an example embodiment is shown. DETAILED DESCRIPTION

[0031] It will be readily appreciated that the components of certain example embodiments as generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for processing multiple minimization of drive tests (MDT) contexts for use in a radio resource controller (RRC) state.

[0032] The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the use of the phrases "certain embodiments," "example embodiments," "some embodiments," or other similar language throughout the specification refers to the fact that a particular feature, structure, or characteristic described in conjunction with one embodiment may be included in at least one embodiment. Thus, the appearance of the phrases "certain embodiments," "example embodiments," "in some embodiments," "in other embodiments," or other similar language throughout the specification does not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0033] In addition, if necessary, the different functions or steps discussed below can be performed in different orders and / or simultaneously with each other. In addition, if necessary, one or more of the described functions or steps can be optional or can be combined. Therefore, the following description should be considered as only an explanation of the principles and teachings of some example embodiments, rather than a limitation thereof.

[0034] MDT is a standardized 3rd Generation Partnership Project (3GPP) feature that involves automatically measuring a set of commercial user equipment (UE) and reporting them to the network. The basic concept aims to replace dedicated and expensive drive tests performed for network optimization.

[0035] MDT involves regular users of a cellular network and makes use of the data collected by it (for example, for mobility purposes). In MDT, two MDT reporting methods have been defined in Release 10. One method is immediate MDT reporting and the second method is logged MDT reporting. In immediate MDT reporting, the UE generates a real-time report of the radio measurements immediately after performing the radio measurements. However, in logged MDT reporting, the configuration is performed when the UE is in connected mode, and the MDT data collection is performed at the UE when the UE enters idle mode. Then, when the UE enters connected mode, a delayed report in the form of a log can be sent. Therefore, the MDT measurement record can be placed in the MDT trace record and signaled to the operator's operations, administration and management (OAM) entity for further post-processing.

[0036] Radio Access Network (RAN)-centric data collection has been described in 3GPP as a mechanism that enables operators to monitor and optimize their 5G deployments. The ultimate goal is to standardize a data collection and utilization method. Self-Organizing Networks (SON) and MDT-oriented solutions (from LTE) have become the baseline for new standardized data collection methods. Therefore, automatic data collection in 5G inherits these two types of MDT reporting methods to provide real-time measurements (e.g., the results of measurements performed for typical Radio Resource Management (RRM) operations) and non-real-time measurement results obtained during the time when the UE is out of network coverage (in RRC_IDLE state), respectively.

[0037] In the Rel-10 LTE specification, logged MDT may occur when the UE is in the Radio Resource Controller (RRC) "idle" (IDLE) state. In Release 16, data collection centered on the 3GPP Radio Access Network (RAN) is also intended to define logged MDT support in the new RRC_INACTIVE (RRC inactive) state. However, the data storage model for RRC_INACTIVE is not discussed in 3GPP. In addition, when both RRC_IDLE and RRC_INACTIVE states support logged measurements, the amount of measurements is expected to increase significantly. However, the large increase in logged data may have a significant impact on the following: a) the energy consumption of the UE that performs the logging and ultimately transmits the data to the network, b) the limited memory storage at the UE, and c) the usefulness of the data. Therefore, in order to control the amount of data, certain example embodiments introduced in this application can provide intelligent MDT configuration for both RRC_INACTIVE and RRC_IDLE states. The measurement logs in the existing specifications are static and do not adapt to changing situations on the network and / or UE side.

[0038] Figure 1 An example MDT measurement configuration for logging MDT is shown. In LTE, the network may configure a UE in the RRC_CONNECTED state to log MDT measurements. For example, the configuration may be as follows: Figure 1 For example, the (E-)UTRAN 105 may send a message 110 including the LMC to the UE 100.

[0039] The LMC at the UE may be released if the LMC at the UE is replaced with another logged MDT configuration, or when a configuration clear occurs in the sense that a certain duration timer expires or another expiration condition is met. In the existing LTE specification, logged MDT measurements may be configured only for the RRC_IDLE state. The logged measurements may include the configuration of downlink pilot strength measurement records, and the configuration of E-UTRA's multicast broadcast single frequency network (MBSFN) measurement records. The logged measurements may also include the configuration of the triggering of the logging event. For example, when the logging interval is configurable, only periodic measurement triggers may be supported. In addition to the measurement period, a period for storing measurements may also be given. The period can be configured in seconds as a multiple of the applied "idle" mode discontinuous reception (DRX) (i.e., a multiple of 1.28 seconds). In addition, when the UE is configured with a DRX period larger than the logging interval, the UE behavior may be unspecified.

[0040] The logged measurements may also include a network absolute timestamp used as a time reference for the UE and include a trace reference parameter indicated by OAM. In addition, the logged measurements may include a trace logging session reference indicated by OAM and a transmission configuration indication (TCI) identifier (ID) indicated by OAM. In addition, the logged measurements may include an MDT, public land mobile network (PLMN) list indicating the PLMNs for which measurement collection and log reporting are allowed. The indication may depend on whether the MDT is initiated by signaling (signaling based on the MDT PLMN list) or by area-based configuration (MDT PLMN list based on management).

[0041] In addition, the logged measurements may include the configuration of a logging area (optional). In particular, the logging area defines: if the UE is within a configured logging area which may include a list of 32 global cell identities, the UE will log measurements. If this list is configured, the UE will only log measurements when it is stationed in any of these cells. The logging area may also include a list of up to 8 tracking areas (TAs) or 8 location areas (LAs) or 8 routing areas (RAs). If the list is configured, the UE will only log measurements when it is stationed in any cell belonging to the pre-configured TA / LA / RA.

[0042] In addition, the logged measurements may include a configured logging area, which may span PLMNs in the MDT PLMN list. If no area is configured, the UE shall log measurements on all PLMNs in the MDT PLMN list. The logged measurements may also include the configuration of the target MBSFN area(s) for MBSFN measurement logging, and the configuration of the WLAN measurements in which the UE attempts to obtain WLAN measurements. In addition, the logged measurements may include the configuration of the target MBSFN area(s) for MBSFN measurement logging, and the configuration of the WLAN measurements in which the UE attempts to obtain WLAN measurements. Measuring Configuration of the measurement.

[0043] The LMC and logs can be maintained when the UE is in any state of the radio access technology (RAT), even if there are multiple interruption periods when the UE is in different RATs. In addition, for a RAT, there is a single LMC in the UE that logs MDT. In addition, when the network provides a configuration, the previously configured LMC will be replaced with the new configuration and the logged measurements corresponding to the previous configuration will be cleared. During these processes, the network can retrieve the data before it is deleted, such as when a new configuration is provided to the UE.

[0044] In some cases, the UE may perform WLAN and In addition, it can be used in WLAN and The measurement logging is performed during the available logging interval. For example, the measurement quantities of WLAN may include the basic service set identifier (BSSID), service set identifier (SSID), homogeneous extended service set identifier (HESSID), and optional received signal strength indicator (RSSI) and round trip time (RTT) of the WLAN access point. Measurement records can include The Media Access Control (MAC) address of the beacon and optionally the RSSI if available.

[0045] In one case, the UE may collect MDT measurements and logs according to its configuration until its reserved memory for MDT is full. If this happens, the UE may stop logging, stop the logging duration timer, and start a 48 hour timer.

[0046] In data collection centered around RAN2 for 3GPP Radio Access Network (RAN), several requirements are defined for NR MDT in the RRC_INACTIVE state. For example, RRC_INACTIVE and RRC_IDLE should also support logged MDT. There is also agreement on applying the logged MDT configuration, logged measurements, and reporting procedures to the RRC_INACTIVE state. In addition, for logged MDT, the network may send an LMC to the UE in connected mode, and the UE may then collect measurements in RRC_IDLE / INACTIVE. When the UE restarts the RRC connection, the UE may send (multiple) available indicators to the network, and the network may then command the UE to send measurements.

[0047] Following this framework, 3GPP defines several requirements specifically for NR MDT and MDT under RRC_INACTIVE. For example, for UE measurements, in order to limit the impact on UE power consumption and processing, UE measurement logging can rely on measurements available in R15 NR and existing in LTE MDT as a baseline. Further, the protocol also includes the release operation of LMC under INACTIVE UE, which can only be achieved by configuration replacement when the configuration is overwritten or by configuration clearing (due to expiration of the logging duration).

[0048] In another protocol, for the collection of logged MDT measurements for RRC_INACTIVE UEs, the actual logging process within the UE may occur in RRC_INACTIVE and continue in RRC_IDLE state. In addition, the logged measurements stored in the UE during RRC_INACTIVE and IDLE states may be kept for a given common period before they are deleted (as in LTE MDT). In addition, the MDT reports from RRC_INACTIVE and IDLE states may be followed by a log availability indicator that indicates the availability of logs at the UE.

[0049] Logged MDT support for both RRC states requires handling of multiple RRC contexts for logging. Figure 2a A process for handling multiple MDT contexts in multiple RRC states according to an example embodiment is shown. Figure 2b Another process for handling multiple MDT contexts in multiple RRC states according to an example embodiment is shown. According to certain example embodiments, enabling and storing of logging contexts for two different RRC states may be provided. The two different RRC states may include an RRC_IDLE state and an RRC_INACTIVE state. Another example embodiment may define a new data storage model for the RRC_INACTIVE state.

[0050] Since the recording of the two RRC states can generate a large amount of data, additional example embodiments may provide two methods for selecting data to be allocated from the UE. For example, one method may include a network-based method, in which the network may configure the UE with a selective configuration based on deployment, configuration, region, or topology. Another method may include a user-based method, in which the UE may define the best configuration from a set of configurations configured for it by the network based on its own internal state (e.g., remaining energy or battery level).

[0051] The above process Figure 2a and Figure 2b As shown in Figure 2aAs shown, at 210, network element 205 may send an LMC message of RRC_IDLE state to UE 200. At 215, in response to LMC message 210, UE 200 may send a logged measurement report (LMR) message of RRC_IDLE state to network element 205. At 220, network element 205 may send an LMC message of RRC_INACTIVE state to UE 200. In response, at 225, UE 200 may send an LMR message of RRC_INACTIVE state to network element 205.

[0052] Figure 2b It is shown that at 230, the network element 205 sends an LMC message to the UE 200. In an example embodiment, the LMC message 230 may include two configurations ("IDLE" and "INACTIVE") in a single message. At 235, the UE 200 may send an LMR message of the RRC_IDLE state to the network element 205 in response to the LMC message. At 240, the UE 200 may also send an LMR message of the RRC_INACTIVE state to the network element 205.

[0053] As mentioned above and as Figure 2a and Figure 2b As shown, an example embodiment may have two different and separate logs for storing "idle" and "inactive" logs. Alternatively, in another example embodiment, the logs may be stored in the same variable. As described above, certain example embodiments may define a process for enabling and storing logging contexts for two different RRC states including, for example, an RRC_IDLE state and an RRC_INACTIVE state. An example embodiment may provide a logged MDT configuration that allows the applicability of the configuration to be differentiated per RRC state. For example, a state logging indication (SLI) information element (IE) ("idle", "inactive") may be introduced in an LMC message to indicate whether the measurement configuration is for an RRC_IDLE state or an RRC_INACTIVE state.

[0054] According to an example embodiment, a common LMC message may be sent to configure the RRC_IDLE and RRC_INACTIVE states. In this case, the LMC message may be sent with both SLIs enabled and may include configuration parameters for the RRC_INACTIVE and RRC_IDLE states. The two contexts of the UE ("idle" and "inactive") may then require coordinated access to one storage location (e.g., a common VarLogMeasConfig (VLMC) that may be accessed by both RRC states. Furthermore, in certain example embodiments, different options may be available for the network to configure logged measurements to the UE. For example, in certain embodiments, the LMC may have various ways to distinguish the applicability of the logging configuration to the RRC states, as described above with respect to Figure 2a and Figure 2b In an example embodiment, the differentiation of logging configuration applicability to RRC states may include different contents of LMC messages, for example, the signaling procedure / message may be the same, but the content may be different depending on the RRC state.

[0055] In another example embodiment, two separate LMC messages may be sent to configure two RRC states ("idle" and "inactive"). In this case, the network may trigger the UE in the RRC_CONNECTED state separately by sending two different LMC messages with an enabled StateLoggingIndication (SLI) IE corresponding to "idle" or "inactive", respectively. In certain example embodiments, this may allow the network to trigger the UE in the RRC_IDLE state to first acquire measurements before triggering the UE in the RRC_INACTIVE state, and vice versa. Alternatively, in other example embodiments, the triggering may occur independently in different states. Here, the two configurations may be retained in the "idle" access stratum (AS) context and the "inactive" AS context of the UE. According to an example embodiment, the two configurations may be stored as VarLogMeasConfigIdle (VLMCId) and VarLogMeasConfigInactive (VLMCI), which may result in two sets of logging parameters.

[0056] According to an example embodiment, one logging parameter set may include a logging and / or logging configuration duration timer (timer T330). The logging duration timer may be maintained per configuration. In addition, a timer may be defined per RRC_state. Another logging parameter set may include an area range. Specifically, the area range may be maintained per state and may cover / trigger a logging area per UE state.

[0057] In an example embodiment, when the UE receives a LMC Inactive (LMCI) message, the UE does not discard its VLMCId configurations, but stores them as two different contexts. In addition, when the UE receives a LMC Idle (LMCId), the UE does not discard its VLMCI configurations, but stores them both as two different contexts. According to an example embodiment, when the T330 timer expires, the UE may discard the stored logged measurements for a particular context by releasing the VLM Report Idle (VLMRId) or VLM Report Inactive (VLMRI) context.

[0058] As described above, certain example embodiments may define a new data storage model for RRC_INACTIVE. In an example embodiment, for the logged MDT storage for each RRC state, a UE receiving a differentiated logged LMC message with one or more RRC states indicated records measurements for all of these configured states. According to certain example embodiments, two options may be provided in this regard.

[0059] According to an example embodiment, as an option, the UE may use common RRC protocol variables. The common RRC protocol variables may include VarLogMeasReport (VLMR) to record its measurements and RRC state, in which the measurements made are recorded. Alternatively, the UE may create two different RRC protocol variables / reports, including, for example, VLMRId and VLMRI. According to an example embodiment, these reports may be stored in separate locations in the UE's memory. In an example embodiment, storing reports in different locations in the UE's memory may be preferred because it makes it easier for the network to process data based on different contexts. In addition, it makes it possible to utilize fragmented portions of the UE's memory, because the log may require two smaller portions of the UE's memory, rather than a larger portion (which is typically more difficult to find). Therefore, certain example embodiments enable the size of the report to be further controlled based on the UE's RRC state, because the memory reserved for storing reports of different states does not need to be of the same size.

[0060] In an example embodiment, selective configuration with the goal of filtering data and precisely scheduling what the UE should log can also be achieved through two options or a combination thereof. One option may include network-based data selection. Here, the network may configure the UE with the most promising configuration. The network may select the most promising configuration based on several parameters.

[0061] One parameter may be the UE type. In this case, the UE may be a normal mobile device, a vehicle-to-everything (V2X) vehicle, or a relay UE. According to an example embodiment, more measurements (smaller logging period and larger logging duration) may be requested from UEs that are not limited by certain energy constraints (e.g., from V2X vehicles and repeaters). In an example embodiment, the network may determine the "most promising" configuration based on the UE capability elements. For example, the UE type may be scheduled as an attribute from the core network to the RAN entity, or may be decided directly by the RAN entity. The RAN entity may have knowledge of the UE capabilities and be able to obtain this information directly before scheduling the MDT session.

[0062] Conventional mobile devices or MTC or Narrowband IoT (Nb-IoT) may not be categorized by the network as a user type with a low likelihood of logging large amounts of data. However, the network can specifically select UEs when troubleshooting involves a group of users. When the network is interested in a persistent logging session, it can decide to select users with no or limited power concerns (e.g., V2X vehicles).

[0063] The second parameter may be an area. Here, the network may obtain UE location information and then use that information to configure more or fewer measurements for the UE. For example, in one embodiment, more measurements may be requested from the UE in areas with poor coverage, or in areas where the network has received a large number of radio link failures (RLFs). Due to the new RRC states and selective configuration involved in the logging session, the area range may be based on a RAN-based Notification Area (RNA).

[0064] The third parameter may include the PLMN network in which the measurement is performed. Here, different measurement granularities may be defined for different PLMNs. For example, a UE roaming in a neighboring PLMN may request more frequent measurements so that the network can obtain information about services in the neighboring PLMN. In addition, the PLMN may be a set of PLMN-IDs covering a shared network, including shared 4G and 5G radio access technologies (RATs).

[0065] A second option of what the UE should record may be based on the UE's data selection. In this option, the network may configure multiple configurations (e.g., x configurations) for the UE in the LMC message. In an example embodiment, these configurations may have different logging periods and different logging durations. In addition, each configuration may depend on the RRC state of the UE ("inactive" or "idle"), and different states may have different configurations. In addition, in certain example embodiments, different trigger conditions may be defined and sent from the network to the UE to enable the UE to select the best configuration each time. According to certain example embodiments, these trigger conditions may depend on the UE.

[0066] For example, in one embodiment, a trigger for which a configuration may be used is a condition satisfied at the UE. According to an example embodiment, a trigger condition may involve the remaining battery power. In this energy consumption scenario, the network may configure different measurement configurations based on the remaining battery power range at the UE. For example, in an energy consumption scenario, when the remaining battery capacity at the UE is within the range of 90-100% of its remaining battery capacity (referring to the battery being full or almost full), the UE may use a configuration corresponding to this condition. Further, when the remaining battery capacity at the UE drops to different levels, the UE may trigger the use of different configurations. In another example embodiment, as opposed to when the UE's battery power is almost exhausted (e.g., within the range of 0-10%), the network may request more aggressive measurements from the UE. Alternatively, in another example embodiment, a drop in energy level (e.g., by observing a gradient) may be used to determine the switching of configurations. For example, if the energy consumption gradient associated with the configuration exceeds a threshold, the UE may switch to a configuration with lower energy consumption. In addition, UEs with weaker batteries may request fewer measurements in this manner. Furthermore, if the UE is reconfigured to a different MDT logging configuration, it will not clear its log file unless the timer T330 for reporting status expires.

[0067] According to an example embodiment, another trigger condition may include the remaining memory capacity at the UE. For example, triggers similar to those described above may be used with the remaining memory. In an example embodiment, the UE may more actively log measurements when the available memory reserved for measurements in a given state ("idle" or "inactive") is almost empty, as opposed to the case where the UE's memory is almost full.

[0068] In an example embodiment, the UE may select the best measurement configuration based on its internal conditions. Specifically, if the LMC message is based on the UE type or 2 separate logs, the UE may record the measurement configuration in its VLMR, and if the LMC message is based on a specific area and depends on the state of the record, the UE may record the measurement configuration in VLMRId and / or VLMRI. In another example embodiment, the network receiving reports from the UE may understand what the best MDT configuration is for each RRC state and update one or more configurations that it signals to the UE. The network may also do this, for example, by checking the energy consumption report under a given configuration divided by the useful measurements received by the network from the record. In an example embodiment, a usefulness measurement may refer to the amount of measurements received by the network that are not too similar to measurements it has already received.

[0069] Figure 3 A possible LMC message ASN.1 syntax and implementation according to an example embodiment is shown. Figure 3, the gNB and UE may conform to an RRC protocol version that supports the embodiment and shall be coded to be able to understand, comprehend and act on the message. In addition, Figure 4 A second LMC message implementation according to an example embodiment is shown. In addition, Figure 5 FIG. 1 shows an LMC storage implementation according to an example embodiment. For LMC storage, it may be necessary to store the configuration in the AS layer of the UE. Figure 3 In the case of Figures 5 to 8 The variable shown may be retained in the UE memory as VLMCId. According to an example embodiment, the UE variable VLMCId may include the configuration of the log of measurements to be performed by the UE when in the RRC_IDLE state, such as Figure 5 shown.

[0070] In another example embodiment, the UE variable VLMCI may include the configuration of the logging of measurements to be performed by the UE when in the RRC_INACTIVE state, such as Figure 6 According to another exemplary embodiment, the log obtained by the UE may need to be stored in the AS layer of the UE, for example, see Figure 3 and Figure 4 The LMC message configuration is shown in Figure 3 and Figure 4 In this case, the two variables can ensure a clearer modeling of the data storage in the UE and provide a simpler reference for the network to retrieve the data.

[0071] Figure 7 1 shows a VLMRUE variable according to an example embodiment. Here, the UE variable VLMR may include logged measurement information from the RRC_IDLE state. In addition, Figure 8 A VLMRIUE variable according to an example embodiment is shown. Here, the UE variable VLMRI may include logged measurement information from the RRC_INACTIVE state.

[0072] Fig. 9 A flow chart of a method according to an example embodiment is shown. In some example embodiments, Fig. 9 The flowchart may be performed by a mobile station and / or a UE (e.g., similar to Fig.11a According to an exemplary embodiment, Fig. 9The method may include: initially, at 300, receiving a logged measurement configuration from a network element, the logged measurement configuration including specific configuration contents for a user equipment, the specific configuration contents being differentiated per each connection state of the user equipment and depending on the connection state of the user equipment. The method may also include: at 305, performing logging of measurements per state of the user equipment according to the specific configuration contents in the logged measurement configuration. The method may also include: at 310, transmitting to the network element a report of logged measurements related to one of the user equipment states.

[0073] According to an example embodiment, specific configuration content can be limited to recording according to one or more of network-based selection criteria and user equipment-based selection criteria. According to other example embodiments, 300, 305, and 310 may depend on UE-based selection criteria in addition to the UE connection state. For example, the UE-based selection criteria may include UE internal conditions in terms of battery and memory as described herein. Alternatively, 300, 305, and 310 may depend on network-based criteria, including, for example, user equipment type, coverage area, and network configuration as described herein.

[0074] In an example embodiment, the network-based selection criteria may include at least one of the following: a user equipment parameter depending on the type of user equipment, a coverage area parameter of the user equipment, a connection state specific parameter of the user equipment, and a communication service type parameter. In another example embodiment, the user equipment-based selection criteria may define a trigger condition for the user equipment to record, and the trigger condition may include a remaining battery charge of the user equipment and a remaining memory capacity at the user equipment.

[0075] According to an example embodiment, the logged measurement configuration may be received in a common logged measurement configuration message or multiple logged measurement configuration messages. According to another example embodiment, the logged measurement configuration may define a logging period and duration of the user equipment according to a connection state of the user equipment. According to another example embodiment, the connection state of the user equipment may include a radio resource controller connected state, a radio resource controller inactive state, and a radio resource controller idle state. Preferably, the user equipment's access to the storage location may be coordinated between the connection states of the user equipment.

[0076] Fig.10 A flow chart of another method according to an example embodiment is shown. In some example embodiments, Fig.10 The flowchart may be executed by a network entity or a network node in a 3GPP system such as LTE or 5G-NR. For example, in some exemplary embodiments, Fig.10 The method may be performed by a base station, an eNB or a gNB (e.g., similar to Fig.11bThe device 20 shown is executed.

[0077] According to an exemplary embodiment, Fig.10 The method may include: initially, at 400, sending a logged measurement configuration to a user equipment, the logged measurement configuration including specific configuration content for the user equipment, the specific configuration content being differentiated for each connection state of the user equipment and depending on the connection state of the user equipment. The method may also include: at 405, receiving from the user equipment a report of logged measurements related to one of the user equipment states. In an example embodiment, the specific configuration content may limit the logging according to one or more of a network-based selection criterion and a user equipment-based selection criterion.

[0078] According to an example embodiment, 400 and 405 may depend on UE-based selection criteria in addition to the UE connection state. For example, the UE-based selection criteria may include UE internal conditions in terms of battery and memory as described herein. Alternatively, 400 and 405 may depend on network-based criteria, including, for example, user equipment type, coverage area, and network configuration as described herein.

[0079] In an example embodiment, the network-based selection criteria may include at least one of the following: a user equipment parameter depending on the type of user equipment, a coverage area parameter of the user equipment, a connection state specific parameter of the user equipment, and a communication service type parameter. In another example embodiment, the user equipment-based selection criteria may define a trigger condition for the user equipment to record, and the trigger condition may include a remaining battery charge of the user equipment and a remaining memory capacity at the user equipment. In another example embodiment, the logging measurement configuration may be sent in a common logging measurement configuration message or multiple logging measurement configuration messages.

[0080] According to an example embodiment, the logging measurement configuration may define a logging period and duration of the user equipment according to the connection state of the user equipment. According to another example embodiment, the logging measurement configuration may authorize the user equipment in the first connection state to log measurements before the user equipment in the second connection state can log measurements.

[0081] Fig.11aAn example apparatus 10 according to an example embodiment is shown. In one embodiment, the apparatus 10 may be a node or element in a communication network, or may also be a node or element associated with such a network, such as a UE, a mobile equipment (ME), a mobile station, a mobile device, a fixed device, an IoT device, or other device. As described herein, a UE may alternatively be referred to as, for example, a mobile station, a mobile equipment, a mobile unit, a mobile device, a user equipment, a subscriber station, a wireless terminal, a tablet computer, a smart phone, an IoT device, a sensor, or a NB-IoT device, etc. As an example, the apparatus 10 may be implemented in, for example, a wireless handheld device, a wireless plug-in accessory, etc.

[0082] In some example embodiments, the apparatus 10 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or a user interface. In some embodiments, the apparatus 10 may be configured to operate using one or more radio access technologies (e.g., GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology). It should be noted that one of ordinary skill in the art will appreciate that the apparatus 10 may include Fig.11a Components or features not shown.

[0083] like Fig.11a As shown in the example of , the device 10 may include or be coupled to a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general-purpose processor or special-purpose processor. In fact, for example, the processor 12 may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture.

[0084] Although Fig.11a A single processor 12 is shown in FIG. 1 , but according to other embodiments, multiple processors may be used. For example, it should be understood that in some example embodiments, the apparatus 10 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case the processor 12 may represent a multiprocessor). According to some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0085] Processor 12 may perform functions associated with the operation of device 10, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits that form communication messages, formatting of information, and overall control of device 10, including processes associated with communication resource management.

[0086] The device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12, and the memory 14 is used to store information and instructions that can be executed by the processor 12. The memory 14 can be one or more memories and any type suitable for the local application environment, and can be implemented using any suitable volatile or non-volatile data storage technology (e.g., semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory). For example, the memory 14 may include any combination of random access memory (RAM), read-only memory (ROM), static memory such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, enables the device 10 to perform tasks as described herein.

[0087] In one embodiment, the device 10 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software executed by the processor 12 and / or the device 10.

[0088] In some embodiments, the device 10 may also include or be coupled to one or more antennas 18 for receiving downlink signals and for transmitting from the device 10 via an uplink. The device 10 may also include a transceiver 18 configured to transmit and receive information. The transceiver 18 may also include a radio interface (e.g., a modem) coupled to the antenna 15. The radio interface may correspond to a variety of radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by a downlink or uplink, such as OFDMA symbols.

[0089] For example, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of the device 10. In other embodiments, the transceiver 18 is capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, the device 10 may include input and / or output devices (I / O devices). In some embodiments, the device 10 may also include a user interface, such as a graphical user interface or a touch screen.

[0090] In one embodiment, the memory 14 stores software modules that provide functionality when executed by the processor 12. The modules may include, for example, an operating system that provides operating system functionality for the device 10. The memory may also store one or more functional modules, such as applications or programs, for providing additional functionality for the device 10. The components of the device 10 may be implemented in hardware or any suitable combination of hardware and software. According to an example embodiment, the device 10 may optionally be configured to communicate with the device 10 via a wireless or wired communication link 70 according to any radio access technology (e.g., NR).

[0091] According to some example embodiments, the processor 12 and the memory 14 may be included in a processing circuit or a control circuit, or may form part of a processing circuit or a control circuit. In addition, in some embodiments, the transceiver 18 may be included in a transceiver circuit, or may form part of a transceiver circuit.

[0092] As described above, according to some example embodiments, the apparatus 10 may be, for example, a UE, a mobile device, a mobile station, a ME, an IoT device, and / or an NB-IoT device. According to some embodiments, the apparatus 10 may be controlled by the memory 14 and the processor 12 to perform functions associated with the example embodiments described herein. For example, in some embodiments, the apparatus 10 may be configured to execute the flowcharts or signaling diagrams described herein (e.g., Figures 1 to 9 One or more processes depicted in any one of the flowcharts shown in the drawings.

[0093] For example, in one embodiment, the apparatus 10 may be controlled by the memory 14 and the processor 12 to receive a recorded measurement configuration from a network element, the recorded measurement configuration including specific configuration contents for the user equipment, which are distinguished by each connection state of the user equipment and depend on the connection state of the user equipment. The apparatus 10 may also be controlled by the memory 14 and the processor 12 to perform recording of measurements by each state of the user equipment according to the specific configuration contents in the recorded measurement configuration. The apparatus 10 may also be controlled by the memory 14 and the processor 12 to transmit a report of recorded measurements related to one of the user equipment states to the network element. In an example embodiment, the specific configuration contents restrict recording according to one or more of a network-based selection criterion and a user equipment-based selection criterion.

[0094] Fig.11b An example of an apparatus 20 according to an example embodiment is shown. In an example embodiment, the apparatus 20 may be a node, host, or server in a communication network, or may also be a node, host, or server serving such a network. For example, the apparatus 20 may be a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB), and / or a WLAN access point associated with a radio access network (RAN) (e.g., an LTE network, 5G, or NR). In some example embodiments, the apparatus 20 may be an eNB in ​​LTE or a gNB in ​​5G.

[0095] It should be understood that in some example embodiments, the device 20 may include an edge cloud server as a distributed computing system, where the server and the radio node may be independent devices that communicate with each other via a radio path or via a wired connection, or they may be located in the same entity that communicates via a wired connection. For example, in certain example embodiments where the device 20 represents a gNB, it may be configured in a centralized unit (CU) and distributed unit (DU) architecture, the aforementioned CU and DU dividing the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functionality such as transmission of user data, mobility control, radio access network sharing, positioning and / or session management. The CU may control the operation of (multiple) DUs via a fronthaul interface. Depending on the functional split option, the DU may be a logical node that includes a subset of gNB functionality. It should be noted that a person of ordinary skill in the art will understand that the device 20 may include Fig.11b Components or features not shown.

[0096] like Fig.11bAs shown in the example of , the device 20 may include a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general-purpose processor or a special-purpose processor. For example, the processor 22 may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Fig.11b A single processor 22 is shown in FIG. 1 , but according to other embodiments, multiple processors may be used. For example, it should be understood that in some embodiments, the apparatus 20 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case the processor 22 may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0097] According to certain example embodiments, processor 22 may perform functions associated with the operation of device 20, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits that form communication messages, formatting of information, and overall control of device 20, including processes related to communication resource management.

[0098] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22, and the memory 24 is used to store information and instructions that can be executed by the processor 22. The memory 24 can be one or more memories and any type suitable for the local application environment, and can be implemented using any suitable volatile or non-volatile data storage technology (e.g., semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory). For example, the memory 24 may include any combination of random access memory (RAM), read-only memory (ROM), static memory such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium. The instructions stored in the memory 24 may include program instructions or computer program code that, when executed by the processor 22, enables the device 20 to perform tasks as described herein.

[0099] In one embodiment, the device 20 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software executed by the processor 22 and / or the device 20.

[0100] In certain example embodiments, the apparatus 20 may also include or be coupled to one or more antennas 25 for transmitting signals and / or data to and receiving signals and / or data from the apparatus 20. The apparatus 20 may also include or be coupled to a transceiver 28 configured to transmit and receive information. The transceiver 28 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 25. The radio interfaces may correspond to a variety of radio access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultra-wideband (UWB), MulteFire, and the like. The radio interfaces may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, and the like to generate symbols for transmission via one or more downlinks and receive symbols (e.g., via an uplink).

[0101] Thus, the transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 25 and to demodulate information received via the antenna(s) 25 for further processing by other elements of the apparatus 20. In other embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, the apparatus 20 may include input and / or output devices (I / O devices).

[0102] In one embodiment, memory 24 may store software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for device 20. The memory may also store one or more functional modules, such as applications or programs, for providing additional functionality for device 20. The components of device 20 may be implemented in hardware or any suitable combination of hardware and software.

[0103] According to some embodiments, the processor 22 and the memory 24 may be included in a processing circuit or a control circuit, or may form part of a processing circuit or a control circuit. In addition, in some embodiments, the transceiver 28 may be included in a transceiver circuit, or may form part of a transceiver circuit.

[0104] As used herein, the term "circuitry" may refer to a pure hardware circuitry implementation (e.g., analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, any portion of a (multiple) hardware processor (including a digital signal processor) with software that works together to enable the device (e.g., device 20) to perform various functions, and / or (multiple) hardware circuits and / or (multiple) processors or portions thereof that operate using software, but the software may not be present when the software is not required for operation. As a further example, as used herein, the term "circuitry" may also encompass an implementation of only a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term "circuitry" may also encompass, for example, a baseband integrated circuit in a server, a cellular network node or device, or other computing or network device.

[0105] As described above, in some example embodiments, the apparatus 20 may be a network node or a RAN node, such as a base station, an access point, a Node B, an eNB, a gNB, a WLAN access point, etc. In another example embodiment, the apparatus 20 may be an LFM. According to some embodiments, the apparatus 20 may be controlled by the memory 24 and the processor 22 to perform functions associated with any of the embodiments described herein, such as Figures 1 to 8 And the flowchart or signaling diagram shown in 10.

[0106] For example, in one embodiment, the apparatus 20 may be controlled by the memory 24 and the processor 22 to send a recorded measurement configuration to the user equipment, the recorded measurement configuration including specific configuration content for the user equipment, the specific configuration content being differentiated by each connection state of the user equipment and depending on the connection state of the user equipment. The apparatus 20 may also be controlled by the memory 24 and the processor 22 to receive a report of recorded measurements related to one of the user equipment states from the user equipment. In an example embodiment, the specific configuration content limits the recording according to one or more of a network-based selection criterion and a user equipment-based selection criterion.

[0107] Certain example embodiments described herein provide several technical improvements, enhancements and / or advantages. In some example embodiments, the amount of data in a recorded measurement scenario can be controlled and a large increase in recorded data can be avoided. Thus, negative impacts on energy consumption and memory storage at the UE can be avoided.

[0108] In other example embodiments, state specific data of the user equipment may be collected. According to further embodiments, state characteristics or faults may be detected and troubleshooting or network optimization may be applied specifically per state accordingly. In other example embodiments, a network may be provided that triggers MDT logging for "inactive" state UEs by modifying an RRC release message. According to further example embodiments, the UE may mark the measurement results to indicate the RRC state. Thus, certain example embodiments provide a way to distinguish between MDT logging measurement activation and content for RRC_IDLE and RRC_INACTIVE states that was not previously provided.

[0109] According to certain example embodiments, a method and apparatus for inter-RAT load balancing for MC-DSS (MC-DSS LB) may also be provided, which maximizes user throughput and improves reliability by iteratively and fairly adjusting certain elements. For example, the adjustment may include 1) an RSS or power margin threshold and a target allocation ratio for the primary carrier allocation. The adjustment may also include 2) partitioning of a shared resource pool, and 3) TDD frame configuration. For certain example embodiments, the load of other RATs may be considered when allocating users to the primary carrier in order to provide sufficient resources for the other RATs. The load of other RATs may also be considered when calculating TDD UL / DL splits and shared resource pool splits. The result may be a throughput-optimized allocation of common resources for the two RATs used by the operator.

[0110] The computer program product may include one or more computer executable components that are configured to perform some example embodiments when the program is run. The one or more computer executable components may be at least one software code or part thereof. Modifications and configurations required to implement the functions of the example embodiments may be performed as (multiple) routines, which may be implemented as (multiple) added or updated software routines. (Multiple) software routines may be downloaded to a device.

[0111] As an example, the software or computer program code or part thereof may be in source code form, object code form or some intermediate form, and it may be stored in some carrier, distribution medium or computer readable medium which may be any entity or device capable of carrying the program. For example, such carriers may include recording media, computer memory, read-only memory, optoelectronic and / or electrical carrier signals, telecommunication signals and software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or distributed among multiple computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0112] In other example embodiments, the function may be performed by hardware or circuitry included in a device (e.g., device 10 or device 20), such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other hardware and software combination. In yet another example embodiment, the function may be implemented as a signal, i.e., an intangible device that may be carried by an electromagnetic signal downloaded from the Internet or other network.

[0113] According to example embodiments, an apparatus such as a node, a device or a corresponding component may be configured as a circuit device, a computer or a microprocessor, such as a single-chip computer element, or as a chipset, comprising at least a memory and an operation processor for performing arithmetic operations, wherein the aforementioned memory is used to provide storage capacity for arithmetic operations.

[0114] Those of ordinary skill in the art will readily appreciate that the present invention as discussed above may be practiced with steps in a different order and / or hardware elements in a different configuration than those disclosed. Therefore, although the present invention has been described based on these preferred embodiments, it will be clear to those skilled in the art that certain modifications, variations, and alternative constructions will be clear while remaining within the spirit and scope of the present invention. Although the above embodiments refer to 5G NR and LTE technologies, the above embodiments may also be applied to any other current or future 3GPP technologies, such as Advanced LTE and / or fourth generation (4G) technologies.

[0115] Partial Glossary

[0116] 3GPP Third Generation Partnership Project

[0117] AMF Access Management Function

[0118] eNB Enhanced Node B

[0119] gNB 5G or NR base station

[0120] LTE Long Term Evolution

[0121] MDT Minimized Drive Test

[0122] MTC Machine Type Communication

[0123] Nb-IoT Narrowband Internet of Things

[0124] NR New Radio

[0125] OAM Operations, Administration and Management

[0126] PLMN Public Land Mobile Network

[0127] RAN Radio Access Network

[0128] RLF Radio Link Failure

[0129] RRC Radio Resource Controller

[0130] RRM Radio Resource Management

[0131] UE User Equipment

Claims

1. A method performed by a user equipment, comprising: receiving a logged measurement configuration from a network element, the logged measurement configuration comprising specific configuration content for the user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment, wherein the connection state of the user equipment comprises a radio resource controller connected state, a radio resource controller inactive state, and a radio resource controller idle state; According to the specific configuration content in the recorded measurement configuration, recording the measurement according to the connection state of the user equipment; as well as transmitting to the network element a report of logged measurements relating to one of the connection states of the user equipment, wherein the specific configuration content limits the recording according to one or more of the following: network-based selection criteria, and user device-based selection criteria, wherein the logging measurement configuration defines a logging period and duration of the user equipment according to the connection state of the user equipment, wherein the user equipment-based selection criteria define trigger conditions for recording by the user equipment, The trigger condition includes the remaining battery power of the user equipment and the remaining memory capacity of the user equipment, and The network-based selection criteria include at least one of the following: User equipment parameters depending on the user equipment type; A coverage area parameter of the user equipment; Connection state specific parameters of the user equipment; and Communication service type parameter.

2. The method of claim 1 , wherein the user equipment logs its measurements and RRC state using common RRC protocol variables including VarLogMeasReport (VLMR), wherein measurements are logged, and wherein two different RRC protocol variables are created by the user equipment and then stored at different locations in a memory of the user equipment.

3. A method according to claim 1 or 2, wherein for the trigger condition comprising the remaining memory capacity at the user equipment, the user equipment records measurements more actively when the available memory reserved for measurements in a given state "idle" or "inactive" is almost empty. 4 . The method of claim 1 , wherein the logged measurement configuration is received in a common logged measurement configuration message or in a plurality of logged measurement configuration messages. 5 . The method of claim 1 , wherein access to a storage location by the user device is coordinated between connection states of the user device.

6. A method performed by a network element, comprising: sending a logged measurement configuration to a user equipment, the logged measurement configuration comprising specific configuration content for the user equipment, the specific configuration content being differentiated by and depending on a connection state of the user equipment, wherein the connection state of the user equipment comprises a radio resource controller connected state, a radio resource controller inactive state, and a radio resource controller idle state; and receiving from the user equipment a report of logged measurements relating to one of the connection states of the user equipment, wherein the specific configuration content limits the recording according to one or more of the following: network-based selection criteria, and user device-based selection criteria, wherein the logging measurement configuration defines a logging period and duration of the user equipment according to the connection state of the user equipment, wherein the user equipment-based selection criteria define trigger conditions for recording by the user equipment, The trigger condition includes the remaining battery power of the user equipment and the remaining memory capacity of the user equipment, and The network-based selection criteria include at least one of the following: User equipment parameters depending on the user equipment type; A coverage area parameter of the user equipment; Connection state specific parameters of the user equipment; and Communication service type parameter.

7. The method of claim 6, wherein the logged measurement configuration is sent in a common logged measurement configuration message or in a plurality of logged measurement configuration messages.

8. The method of claim 6, wherein the logged measurements configuration authorizes the user equipment in a first connected state to log measurements before the user equipment in a second connected state is able to log measurements.

9. A user equipment, comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, together with the at least one processor, cause the user equipment to at least receiving a logged measurement configuration from a network element, the logged measurement configuration comprising specific configuration content for the user equipment, the specific configuration content being differentiated by and dependent on a connection state of the user equipment, wherein the connection state of the user equipment comprises a radio resource controller connected state, a radio resource controller inactive state, and a radio resource controller idle state; According to the specific configuration content in the recorded measurement configuration, recording the measurement according to the connection state of the user equipment; as well as transmitting to the network element a report of logged measurements relating to one of the connection states of the user equipment, wherein the specific configuration content limits the recording according to one or more of the following: network-based selection criteria, and user device-based selection criteria, wherein the logging measurement configuration defines a logging period and duration of the user equipment according to the connection state of the user equipment, wherein the user equipment-based selection criteria define trigger conditions for recording by the user equipment, The trigger condition includes the remaining battery power of the user equipment and the remaining memory capacity of the user equipment, and The network-based selection criteria include at least one of the following: User equipment parameters depending on the user equipment type; A coverage area parameter of the user equipment; Connection state specific parameters of the user equipment; and Communication service type parameter.

10. The user equipment of claim 9, wherein the user equipment logs its measurements with the RRC state using common RRC protocol variables including VarLogMeasReport (VLMR), wherein measurements are logged, and wherein two different RRC protocol variables are created by the user equipment and then stored at different locations in a memory of the user equipment.

11. The user equipment of claim 9, wherein for the trigger condition comprising remaining memory capacity at the user equipment, the user equipment records measurements more actively when the available memory reserved for measurements in a given state "idle" or "inactive" is almost empty.

12. The user equipment of claim 9, wherein the logged measurement configuration is received in a common logged measurement configuration message or in a plurality of logged measurement configuration messages.

13. The user device of claim 9, wherein access to storage locations by the user device is coordinated between connection states of the user device.

14. A network element comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, together with the at least one processor, cause the network element to at least sending a logged measurement configuration to a user equipment, the logged measurement configuration comprising specific configuration content for the user equipment, the specific configuration content being differentiated by and depending on a connection state of the user equipment, wherein the connection state of the user equipment comprises a radio resource controller connected state, a radio resource controller inactive state, and a radio resource controller idle state; and receiving from the user equipment a report of logged measurements relating to one of the connection states of the user equipment, wherein the specific configuration content limits the recording according to one or more of the following: network-based selection criteria, and user device-based selection criteria, wherein the logging measurement configuration defines a logging period and duration of the user equipment according to the connection state of the user equipment, wherein the user equipment-based selection criteria define trigger conditions for recording by the user equipment, The trigger condition includes the remaining battery power of the user equipment and the remaining memory capacity of the user equipment, and The network-based selection criteria include at least one of the following: User equipment parameters depending on the user equipment type; A coverage area parameter of the user equipment; Connection state specific parameters of the user equipment; and Communication service type parameter.

15. The network element of claim 14, wherein the logged measurement configuration is sent in a common logged measurement configuration message or in a plurality of logged measurement configuration messages.

16. The network element of claim 14, wherein the logged measurements configuration authorizes the user equipment in a first connected state to log measurements before the user equipment in a second connected state is able to log measurements.

17. An apparatus for communication, comprising a circuit device, wherein the circuit device is configured to cause the apparatus to perform the method according to any one of claims 1 to 8.

18. A computer program product encoded with instructions for executing the method according to any one of claims 1 to 8.

Images