Configuration for minimizing drive test measurements and experience quality measurements performed by the UE at the start of an application or service.

Abstract

In some wireless communication systems, devices can support Minimized Drive Test (MDT) reporting, Quality of Service (QoS) reporting, and Quality of Experience (QoE) measurements. User Equipment (UE) and serving base stations can obtain measurements based on measurement configurations that indicate various triggering events or reporting adjustment factors associated with the measurements. Measurement configurations can indicate triggering events, such as the start of an application or service at the UE, and the UE can obtain MDT or QoE measurements based on identifying the application or service. Additionally, the serving base station can obtain MDT and QoE measurements based on identifying the application and service or notifications from the UE. The UE and serving base station can identify reporting adjustment factors based on network slices, area configurations, and time of day that affect the reporting intervals and reporting volumes used for measurement reporting.

Description

[0001] This application is a divisional application of patent application No. 202180050205.9, entitled "Configuration for Minimizing Drive Test Measurements and Experience Quality Measurements Performed by the UE at the Start of an Application or Service", filed on August 26, 2021. Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 411,434, filed August 25, 2021, entitled “APPLICATION, SERVICES, AND NETWORK SLICE BASED MEASUREMENTS FOR MINIMIZATION OF DRIVE TEST REPORTING”, which claims the benefit of U.S. Provisional Patent Application No. 63 / 070,726, filed August 26, 2020, entitled “APPLICATION, SERVICES, AND NETWORK SLICE BASED MEASUREMENTS FOR MINIMIZATION OF DRIVE TEST REPORTING”, assigned to the assignee of this application. Technical Field

[0003] The following discussion pertains to wireless communications, including application-, service-, and network slice-based measurements for minimizing drive test (MDT) reports. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems, which may be called New Radio (NR) systems. These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices, also referred to as User Equipment (UE).

[0005] The UE can report measurements to the network via measurement reports. In one example, the reported measurements may be related to communication quality and may be included in the Minimized Drive Test (MDT) report. Improving MDT reporting can be beneficial. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting applications, services, and network or radio access network (RAN) slice-based measurements for minimizing drive test (MDT) and quality of experience (QoE) reports. Devices such as user equipment (UE) and serving base stations can collect various on-the-fly MDT measurements that the network can use for Quality of Service (QoS) verification and other MDT purposes. Additionally or alternatively, the UE can obtain QoE measurements to include in QoE measurement reports used for application-layer QoE verification. The serving base station can obtain MDT and QoE reports from the UE and can send the MDT and QoE reports, along with the MDT measurements obtained by the serving base station, to a trace collection entity (TCE). In some examples, the reports can be used to improve communication quality and device performance in the network.

[0007] The UE and serving base station can obtain MDT measurements based on a measurement configuration (e.g., for performing QoE or MDT measurements) received from the Operation, Management, and Maintenance (OAM) interface. This measurement configuration indicates the number of triggering events that will initiate MDT measurements for the UE and serving base station. For example, the measurement configuration may indicate that the start of an application or service at the UE is a triggering event for obtaining MDT or QoE measurements. In one implementation, the UE may identify a list of application or service identifiers (IDs) eligible to trigger measurement collection, and the UE may compare the application or service IDs with the list of application or service IDs to determine whether to initiate MDT or QoE measurements and generate a measurement report. When an eligible application or service for MDT measurement begins, the base station and UE can initiate immediate MDT measurements, where the base station and UE may obtain different MDT measurement collections. For example, the UE may obtain Radio Resource Management (RRM) measurements, Uplink Packet Data Convergence Protocol (PDCP) packet queuing delays, etc., as immediate measurements, while the base station may obtain data volume, throughput, packet delay, and packet loss in the Radio Access Network (RAN) and air interface. Alternatively, the UE may send an indication to the base station when a triggering condition (or triggering event) is met to indicate the start or end of an application or service session. This indication may be used to indicate the collection of MDT measurements or for other RAN optimizations or requirements. In some examples, the UE may receive a general QoE reporting configuration when connected to the network, or the UE may receive application- and service-specific QoE reporting configurations.

[0008] In another implementation, the UE and serving base station may receive a measurement configuration that includes a reporting adjustment factor affecting at least one of the reporting intervals or reporting volumes used to report MDT reports. For example, a network or RAN slice may provide dedicated resources for applications and services, and the UE may identify different MDT or QoS reports for different networks or RAN slices. Similarly, the serving base station may identify different MDT reports for different networks or RAN slices. Additionally, the UE and serving base station may change the reporting intervals and reporting volumes used for MDT measurements based on area configuration and time of day.

[0009] A method for wireless communication at a UE is described. The method may include: receiving a measurement configuration from an OAM interface, the measurement configuration for performing MDT measurements to be included in an MDT report and performing QoE measurements to be included in a QoE report; identifying one or more triggering events from the measurement configuration, the one or more triggering events triggering the MDT measurements and the QoE measurements when they occur; detecting the start of an application or service at the UE, wherein the start of the application or service is one of the one or more triggering events; sending an indication to a serving base station that the one or more triggering events have occurred; obtaining the MDT measurements and the QoE measurements based at least in part on the fact that the start of the application or service is one of the one or more triggering events; and sending the MDT report and the QoE report, including the MDT measurements and the QoE measurements, to a server.

[0010] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a measurement configuration from an OAM interface, the measurement configuration for performing MDT measurements to be included in an MDT report and performing QoE measurements to be included in a QoE report; identify one or more trigger events from the measurement configuration, the one or more trigger events triggering the MDT measurements and the QoE measurements when they occur; detect the start of an application or service at the UE, wherein the start of the application or service is one of the one or more trigger events; send an indication to a serving base station that the one or more trigger events have occurred; obtain the MDT measurements and the QoE measurements at least in part based on the fact that the start of the application or service is one of the one or more trigger events; and send the MDT report and the QoE report, including the MDT measurements and the QoE measurements, to a server.

[0011] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for receiving a measurement configuration from an OAM interface, the measurement configuration for performing MDT measurements to be included in an MDT report and performing QoE measurements to be included in a QoE report; a unit for identifying one or more triggering events from the measurement configuration, the one or more triggering events triggering the MDT measurements and the QoE measurements when they occur; a unit for detecting the start of an application or service at the UE, wherein the start of the application or service is one of the one or more triggering events; a unit for sending an indication to a serving base station that the one or more triggering events have occurred; a unit for obtaining the MDT measurements and the QoE measurements based at least in part on the fact that the start of the application or service is one of the one or more triggering events; and a unit for sending the MDT report and the QoE report, including the MDT measurements and the QoE measurements, to a server.

[0012] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive a measurement configuration from an OAM interface, the measurement configuration for performing MDT measurements to be included in an MDT report and performing QoE measurements to be included in a QoE report; identify one or more triggering events from the measurement configuration, the one or more triggering events triggering the MDT measurements and the QoE measurements when they occur; detect the start of an application or service at the UE, wherein the start of the application or service is one of the one or more triggering events; send an indication to a serving base station that the one or more triggering events have occurred; obtain the MDT measurements and the QoE measurements at least in part based on the start of the application or service being one of the one or more triggering events; and send the MDT report and the QoE report, including the MDT measurements and the QoE measurements, to a server.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: identifying one or more application or service IDs associated with the application or service; comparing the one or more application or service IDs with a list of IDs stored at the UE, wherein the list of IDs includes IDs of the application or service associated with the one or more triggering events; and determining, based on the comparison, that the one or more application or service IDs may be included in the list of IDs stored at the UE.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: generating the MDT report and the QoE report to include the one or more application or service IDs based on determining that the one or more application or service IDs can be included in the ID list stored at the UE.

[0015] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, obtaining the MDT measurement may include operations, features, units or instructions for performing the following: obtaining radio resource management (RRM) measurements to be included in the MDT report based on determining that the one or more application or service IDs can be included in the list of IDs stored at the UE.

[0016] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the RRM measurement includes at least one of a reference signal received power (RSRP) measurement or a reference signal received quality (RSRQ) measurement.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RRM measurement includes periodic measurements, event-triggered measurements, or combinations thereof.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, obtaining the MDT measurements may include operations, features, units, or instructions for obtaining one or more location measurements based on the start trigger of the application or service, to include the one or more location measurements in the MDT report.

[0019] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, obtaining one or more location measurements may include operations, features, units or instructions for performing the following: obtaining the location measurement as one or more Received Signal Strength Indicator (RSSI) measurements or Round-Trip Time (RTT) measurements, wherein the location measurement may be associated with public location information, wireless LAN location information, Bluetooth location information, sensor information, or any combination thereof.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, obtaining the MDT measurement may include operations, features, units, or instructions for obtaining one or more QoS measurements based on the start trigger of the application or service, to include the one or more QoS measurements in the MDT report.

[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the one or more QoS measurements include one or more packet delay measurements or packet loss rate measurements.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving, in the measurement configuration, an indication that the UE may include one or more application or service IDs in the MDT report, wherein the one or more application or service IDs indicate a QoS measurement of the serving base station.

[0023] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the QoS measurements of the serving base station include data volume measurements, Internet Protocol throughput measurements, packet delay measurements, packet loss measurements, or any combination thereof.

[0024] A method for wireless communication at a UE is described. The method may include: receiving from an OAM interface a first measurement configuration for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application- or service-specific measurement configuration; detecting the start of an application or service at the UE, wherein the start of the application or service is a triggering event for initiating the one or more QoE measurements at the UE; performing the one or more QoE measurements at the UE according to the first measurement configuration; and sending the one or more QoE measurements to a serving base station in a measurement report.

[0025] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive from an OAM interface a first measurement configuration for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application- or service-specific measurement configuration; detect the start of an application or service at the UE, wherein the start of the application or service is a triggering event for initiating the one or more QoE measurements at the UE; perform the one or more QoE measurements at the UE according to the first measurement configuration; and send the one or more QoE measurements to a serving base station in a measurement report.

[0026] Another apparatus for wireless communication at a UE is described. The apparatus may include: unit for receiving from an OAM interface a first measurement configuration for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application- or service-specific measurement configuration; unit for detecting the start of an application or service at the UE, wherein the start of the application or service is a triggering event for initiating the one or more QoE measurements at the UE; unit for performing the one or more QoE measurements at the UE according to the first measurement configuration; and unit for sending the one or more QoE measurements to a serving base station in a measurement report.

[0027] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive from an OAM interface a first measurement configuration for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application- or service-specific measurement configuration; detect the start of an application or service at the UE, wherein the start of the application or service is a triggering event for initiating the one or more QoE measurements at the UE; perform the one or more QoE measurements at the UE according to the first measurement configuration; and send the one or more QoE measurements to a serving base station in a measurement report.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: identifying one or more application or service IDs associated with the application or service; comparing the identified one or more application or service IDs with a list of IDs stored at the UE, wherein the list of IDs includes IDs of the application or service associated with the one or more triggering events; and determining, based on the comparison, that the one or more application or service IDs may be included in the list of IDs stored at the UE, wherein the one or more QoE measurements may be performed based on the determination according to the first measurement configuration.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, performing one or more QoE measurements at the UE according to the first measurement configuration may include operations, features, elements, or instructions for verifying at the UE that the triggering event for initiating the one or more QoE measurements at the UE may not be associated with the application- or service-specific measurement configuration, wherein the one or more QoE measurements may be performed based on the verification according to the first measurement configuration.

[0030] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining that the first measurement configuration includes a default measurement configuration for performing the one or more QoE measurements at the UE.

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing: receiving a second measurement configuration, the second measurement configuration including an application- or service-specific measurement configuration for performing QoE measurements at the UE that may be specific to one or more designated applications or services; and performing the QoE measurements at the UE according to the first measurement configuration based on the detection of the start of the one or more designated applications or services at the UE.

[0032] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the one or more QoE measurements include application layer throughput measurements, RTT, jitter metrics, packet drop rates, or any combination thereof.

[0033] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving the first measurement configuration when establishing a radio resource control (RRC) connection with the serving base station.

[0034] A method for wireless communication at a serving base station is described. The method may include: sending to a UE a first measurement configuration received from an OAM interface for performing MDT measurements to be included in an MDT report, and a second measurement configuration received from the OAM interface for performing QoE measurements at the UE, the second measurement configuration being different from an application- or service-specific measurement configuration, wherein the first or second measurement configuration indicates one or more triggering events, the one or more triggering events including the start of an application or service at the UE, the application or service triggering the MDT measurement, the QoE measurement, the generation of a message indicating the one or more triggering events, or any combination thereof, at the UE upon occurrence. In some examples, the method may include: receiving from the UE the MDT report including the MDT measurements or the measurement report including one or more QoE measurements, or any combination thereof.

[0035] An apparatus for wireless communication at a serving base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send to a UE a first measurement configuration received from an OAM interface for performing MDT measurements to be included in an MDT report, and a second measurement configuration received from the OAM interface for performing QoE measurements at the UE, the second measurement configuration being different from an application- or service-specific measurement configuration, wherein the first or second measurement configuration indicates one or more triggering events, the one or more triggering events including the start of an application or service at the UE, which, when occurring, triggers the MDT measurement, the QoE measurement, the generation of a message indicating the one or more triggering events, or any combination thereof. In some examples, the instructions may be executable by the processor to cause the apparatus to: receive from the UE the MDT report including the MDT measurements or a measurement report including one or more QoE measurements, or any combination thereof.

[0036] Another apparatus for wireless communication at a serving base station is described. The apparatus may include: a unit for transmitting to a UE a first measurement configuration received from an OAM interface for performing MDT measurements to be included in an MDT report, and a second measurement configuration received from the OAM interface for performing QoE measurements at the UE, the second measurement configuration being different from an application- or service-specific measurement configuration, wherein the first or second measurement configuration indicates one or more triggering events, the one or more triggering events including the start of an application or service at the UE, which, when occurring, triggers the MDT measurement, the QoE measurement, the generation of a message indicating the one or more triggering events, or any combination thereof. In some examples, the apparatus includes: a unit for receiving from the UE the MDT report including the MDT measurements or the measurement report including one or more QoE measurements, or any combination thereof.

[0037] A non-transitory computer-readable medium is described, storing code for wireless communication at a serving base station. The code may include instructions executable by a processor to perform: sending to a UE a first measurement configuration received from an OAM interface for performing MDT measurements to be included in an MDT report, and a second measurement configuration received from the OAM interface for performing QoE measurements at the UE, the second measurement configuration being different from an application- or service-specific measurement configuration, wherein the first or second measurement configuration indicates one or more triggering events, the one or more triggering events including the start of an application or service at the UE, which, upon occurrence, triggers the MDT measurement, the QoE measurement, the generation of a message indicating the one or more triggering events, or any combination thereof. In some examples, the code may include instructions executable by a processor to perform: receiving from the UE the MDT report including the MDT measurements or a measurement report including one or more QoE measurements, or any combination thereof.

[0038] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: identifying one or more application or service IDs associated with the application or service, wherein the one or more application or service IDs may be included in a list of IDs stored at the UE and may be associated with the one or more triggering events at the UE.

[0039] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, receiving the MDT measurement may include operations, features, units or instructions for receiving one or more location measurements in the MDT report by obtaining one or more location measurements at the UE based on the start trigger of the application or service.

[0040] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the MDT measurement may include operations, features, units, or instructions for receiving one or more QoS measurements included in the MDT report based on the start trigger of the application or service.

[0041] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the one or more QoE measurements may include operations, features, units, or instructions for performing the following: verifying that the triggering event for initiating the one or more QoE measurements at the UE may not be associated with the application- or service-specific measurement configuration, wherein the one or more QoE measurements may be received based on the verification according to the second measurement configuration.

[0042] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining that the second measurement configuration includes a default measurement configuration for performing the one or more QoE measurements at the UE.

[0043] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing: transmitting a third measurement configuration received from the OAM, the third measurement configuration including a UE-specific measurement configuration for QoE measurements that may be specific to one or more designated applications or services at the UE; and receiving the QoE measurements from the UE according to the third measurement configuration based on the start of one or more designated applications or services at the UE.

[0044] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the one or more QoE measurements include application layer throughput measurements, RTT, jitter metrics, packet drop rates, or any combination thereof. Attached Figure Description

[0045] Figure 1 An example of a system for wireless communication that supports application-, service-, and network-slice-based measurements for minimizing drive test (MDT) reports, according to various aspects of this disclosure.

[0046] Figure 2 Examples of wireless communication systems supporting application-, service-, and network-slice-based measurements for MDT reporting, according to various aspects of this disclosure, are shown.

[0047] Figure 3 An example of a process flow supporting application-, service-, and network slice-based measurements for MDT reporting, based on various aspects of this disclosure, is shown.

[0048] Figure 4 An example of a process flow supporting application-, service-, and network slice-based measurements for MDT reporting, based on various aspects of this disclosure, is shown.

[0049] Figure 5 An example of a process flow supporting application-, service-, and network slice-based measurements for MDT reporting, based on various aspects of this disclosure, is shown.

[0050] Figure 6 and 7 A block diagram of an apparatus supporting application-, service-, and network-slice-based measurements for MDT reporting, according to various aspects of this disclosure, is shown.

[0051] Figure 8 A block diagram is shown of a communication manager that supports application-, service-, and network-slice-based measurements for MDT reporting, according to various aspects of this disclosure.

[0052] Figure 9 A schematic diagram of a system including devices supporting application-, service-, and network-slice-based measurements for MDT reporting is shown, according to various aspects of this disclosure.

[0053] Figure 10 and 11 A block diagram of an apparatus supporting application-, service-, and network-slice-based measurements for MDT reporting, according to various aspects of this disclosure, is shown.

[0054] Figure 12 A block diagram is shown of a communication manager that supports application-, service-, and network-slice-based measurements for MDT reporting, according to various aspects of this disclosure.

[0055] Figure 13 A schematic diagram of a system including devices supporting application-, service-, and network-slice-based measurements for MDT reporting is shown, according to various aspects of this disclosure.

[0056] Figures 14 to 22 A flowchart illustrating methods for application-, service-, and network-slice-based measurements used in MDT reporting, supported by various aspects of this disclosure, is shown. Detailed Implementation

[0057] In some wireless communication systems, devices can support immediate minimized drive test (MDT) measurements to test and report communication quality within an area, thereby reducing operating costs and improving communication quality within the network. Using measurement configurations, devices such as user equipment (UEs) and serving base stations can collect various immediate MDT measurements that can be used by the network for Quality of Service (QoS) verification and other MDT purposes. Additionally, UEs can obtain Quality of Experience (QoE) measurements to include in QoE measurement reports used for application-layer QoE verification. The serving base station can obtain MDT and QoE reports from the UE and can report them, along with the MDT measurements obtained by the serving base station, to a centralized server (e.g., a trace collection entity (TCE)). MDT measurements can be used to improve communication quality and device performance within the network.

[0058] The UE and serving base station can obtain MDT measurements based on measurement configurations received from the Operation, Management, and Maintenance (OAM) interface. These configurations indicate the number of triggering events that will initiate MDT measurements for the UE and serving base station. For example, a measurement report might indicate that the start of an application or service at the UE is a triggering event for the serving base station. In response to the initiation of an application or service, both the UE and serving base station can obtain MDT measurements. To support MDT reporting for various communications and services at the UE, as well as other measurement reports, the UE and serving base station can perform immediate MDT measurements triggered by applications or services. Furthermore, the UE and serving base station can generate MDT reports for various identified network slices (e.g., radio access network (RAN) slices), different area configurations, different times of day, and other network factors. Additionally, the UE can generate QoE reports based on the identified start of an application or service. This immediate measurement and reporting can enhance the performance of applications and services at the UE while improving the overall communication efficiency of the network.

[0059] In one implementation, the UE can identify a list of application or service IDs eligible to be triggered by measurement collection, and the UE can compare the application or service identifier (ID) with the list of application or service IDs to determine whether to start MDT measurement. If the application or service identified by the UE is included in the list of application or service IDs, the UE can obtain MDT measurement and generate an MDT report.

[0060] In another implementation, network (e.g., RAN) slices can provide dedicated resources for applications and services. Because these network slices support different applications and services with different QoS objectives, different QoS authentication schemes can be implemented for different applications and services. The UE can identify different MDTs or QoS reports used for different network slices.

[0061] In another implementation, the UE and serving base station can change the reporting interval and reporting volume for MDT measurements based on regional configuration and time of day. For example, the network can configure the measurement settings to allow the UE and serving base station to adjust MDT measurement collection for different regions and different times of day. For instance, the measurement configuration could be based on different reporting requirements at different times of day, or on different service areas with different quality of service.

[0062] In another implementation, the UE can be configured to obtain QoE measurements based on application and service triggers. The network can configure a specific QoE configuration for the UE to measure QoE based on application and service triggers. Alternatively, if the UE is not configured with a specific QoE configuration, a general or specific QoE configuration can be assigned to the UE based on whether the network requests the QoE for a specific application or service.

[0063] Various aspects of this disclosure are first described in the context of a wireless communication system that supports MDT measurement reporting. These aspects are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to application-, service-, and network-slice-based measurements for MDT reporting, and are described with reference to these diagrams.

[0064] Figure 1 Examples of wireless communication systems 100 supporting application, service, and network slicing measurements for MDT reporting, according to various aspects of this disclosure, are shown. Wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, wireless communication system 100 may be a Long Term Evolution (LTE) network, an improved LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices, or any combination thereof.

[0065] Base stations 105 can be distributed throughout a geographical area to form a wireless communication system 100, and can be devices of different forms or with different capabilities. Base stations 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UE 115 and base station 105 can establish one or more communication links 125 on the coverage area 110. The coverage area 110 can be an example of a geographical area where base stations 105 and UE 115 can support signal transmission according to one or more radio access technologies.

[0066] UE 115 can be distributed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, mobile, or both at different times. UE 115 can be devices of different forms or with different capabilities. Figure 1 Some example UE 115s are shown in the document. The UE 115 described herein may be able to communicate with various types of devices, such as other UE 115s, base station 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices). Figure 1 As shown.

[0067] Base station 105 can communicate with core network 130, communicate with each other, or perform both operations. For example, base station 105 can be connected to core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) on backhaul links 120 (e.g., via X2, Xn, or other interfaces), or indirectly (e.g., via core network 130), or perform both operations. In some examples, backhaul link 120 can be or includes one or more radio links.

[0068] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, base station transceiver, radio base station, access point, radio transceiver, node B, evolved node B (eNodeB, eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), home node B, home evolved node B, or other suitable terms.

[0069] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a unit, station, terminal, or client, and other examples. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, and other examples, which may be implemented in various items such as appliances, vehicles, meters, and other examples.

[0070] The UE 115 described in this document may be able to communicate with various types of devices, such as other UE 115s that can sometimes act as repeaters, as well as base station 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, and other examples, such as... Figure 1 As shown.

[0071] UE 115 and base station 105 can wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0072] In some examples (e.g., in a carrier aggregation configuration), carriers may also have acquisition or control signaling that coordinates operation against other carriers. Carriers may be associated with frequency channels (e.g., Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be positioned according to a channel grid for discovery by UE 115. Carriers may operate in standalone mode, where UE 115 performs initial acquisition and connection via a carrier, or in non-standalone mode, where different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0073] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode) or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0074] A carrier may be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a number of defined bandwidths for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication over a specific carrier bandwidth, or may be configurable to support communication over a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0075] The signal waveform transmitted on a carrier can consist of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or Discrete Fourier Transform Spread Spectrum OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element can include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate can be for UE 115. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity used for communication with UE 115.

[0076] It can support one or more digital schemes (numerologies) for the carrier, wherein the digital schemes may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different digital schemes. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for UE 115 can be restricted to one or more active BWPs.

[0077] It can be in the basic unit of time (which can be, for example, referred to as) The sampling period is seconds, where It can represent the maximum supported subcarrier spacing, and The time interval for base station 105 or UE 115 can be represented as a multiple of the maximum supported Discrete Fourier Transform (DFT) size. The time interval for communication resources can be organized based on radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0078] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., this depends on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., (Number) sampling periods. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0079] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Alternatively or additionally, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst form of a shortened TTI (sTTI)).

[0080] Physical channels can be multiplexed on a carrier using various techniques. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. A control region (e.g., a control resource set (CORESET)) for physical control channels can be defined by the number of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a group of UEs 115. For example, one or more of the UEs 115 can monitor or search for control regions against control information based on one or more search space sets, and each search space set can include one or more control channel candidates arranged in a cascaded manner at one or more aggregation levels. The aggregation level for control channel candidates can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set used to send control information to a specific UE 115.

[0081] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., on a carrier) to communicate with base station 105 and may be associated with an identifier used to distinguish neighboring cells (e.g., Physical Cell ID (PCID), Virtual Cell ID (VCID), or others). In some examples, a cell may also refer to a geographic coverage area 110 or a portion of geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of base station 105, the range of such cells can range from small areas (e.g., structures, subsets of structures) to large areas. For example, a cell may be or include buildings, subsets of buildings, or external space between or overlapping geographic coverage areas 110, and other examples.

[0082] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 115 with a service subscription to a network provider supporting the macro cell. In contrast, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UE 115 with a service subscription to a network provider, or restricted access to UE 115 associated with the small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a residence or office). Base station 105 can support one or more cells and can also support communication on one or more cells using one or more component carriers.

[0083] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0084] In some examples, base station 105 may be mobile, and therefore provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different radio access technologies to provide coverage for various geographic coverage areas 110.

[0085] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and in some examples, transmissions from different base stations 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0086] Some UE 115s (e.g., MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated machine-to-machine communication (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices that have integrated sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents it to humans interacting with the application. Some UE 115s can be designed to collect information or automate the behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0087] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via either transmission or reception, rather than simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communication, when operating on limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs) within a carrier, within a carrier's guard band, or outside a carrier.

[0088] Wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE 115 can be designed to support ultra-reliable, low-latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private or group communication and can be supported by one or more mission-critical services such as Mission-Critical Push-to-Talk (MCPTT), Mission-Critical Video (MCVideo), or Mission-Critical Data (MCData). Support for mission-critical functions can include service prioritization, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0089] In some examples, UE 115 may also be able to communicate directly with other UE 115s on a device-to-device (D2D) communication link 135 (e.g., using peer-to-peer (P2P) or D2D protocols). One or more UEs 115s utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UEs 115s in such a group may be outside the geographic coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some examples, groups of UEs 115s communicating via D2D communication may utilize a one-to-many (1:M) system, wherein each UE 115 transmits to each other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

[0090] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information relating to traffic conditions, signal control, weather, safety, emergencies, or any other information relating to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both.

[0091] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), and can include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function unit (AMF)) managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function unit (UPF)) routing packets to or interconnecting with external networks. The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can connect to network operator IP service 150. Carrier IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0092] Some network devices (e.g., base station 105) may include sub-components such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with UE 115 through one or more other access network transport entities 145 (which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP)). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across individual network devices (e.g., radio headends and ANCs) or incorporated into a single network device (e.g., base station 105).

[0093] Wireless communication system 100 can operate using one or more frequency bands (typically in the range of 300 MHz to 300 GHz). The region from 300 MHz to 3 GHz is typically referred to as the UHF region or decimeter band because the wavelength range extends from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves can be sufficiently permeable to penetrate structures for use in macrocells to provide service to UE 115 located indoors. Transmission of UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 km) compared to transmission of smaller frequencies and longer waves in the lower 300 MHz portion of the spectrum, such as the high frequency (HF) or very high frequency (VHF) portions.

[0094] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also referred to as the centimeter band) or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the corresponding device can be even smaller and more closely spaced compared to UHF antennas. In some examples, this can facilitate the use of antenna arrays within the device. However, propagation to EHF transmissions may suffer even greater atmospheric attenuation and shorter distances compared to SHF or UHF transmissions. The techniques disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary depending on the country or regulatory authority.

[0095] Wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 can employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in unlicensed radio frequency spectrum bands, devices (such as base station 105 and UE 115) can employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed frequency bands can be based on carrier aggregation configurations that combine component carriers operating in licensed frequency bands (e.g., LAA). Operation in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and other examples.

[0096] Base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array having a number of rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, antenna panels may support radio frequency beamforming for signals transmitted via antenna ports.

[0097] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique can be called spatial multiplexing. For example, a transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0098] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105, UE 115) to form or guide antenna beams (e.g., transmit beams, receive beams) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating relative to a specific orientation of the antenna array experience constructive interference, while others experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with the transmitting or receiving device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0099] As part of beamforming operations, base station 105 or UE 115 may use beam scanning techniques. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Base station 105 may transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions. For example, base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by a transmitting device (such as base station 105) or by a receiving device (such as UE 115)) to identify the beam direction for subsequent transmissions or receptions performed by base station 105.

[0100] Base station 105 may transmit signals (e.g., data signals associated with a specific receiving device, such as UE 115) in a single beam direction. In some examples, the beam direction associated with transmission along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 with the highest signal quality or otherwise acceptable signal quality.

[0101] In some examples, multiple beam directions can be used to perform transmissions by a device (e.g., base station 105 or UE 115), and the device can use a combination of digital precoding or radio frequency beamforming to generate combined beams for (e.g., from base station 105 to UE 115) transmissions. UE 115 can report feedback indicating precoding weights for one or more beam directions, and this feedback can correspond to a configured number of beams spanning the system bandwidth or one or more subbands. Base station 105 can transmit reference signals that can be precoded or unprecoded (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)). UE 115 can provide feedback on beam selection, which can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam directions for subsequent transmissions or receptions by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0102] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, the receiving device (e.g., UE 115) can attempt multiple receiving configurations (e.g., directional listening). For example, the receiving device can attempt multiple receiving directions by receiving via different antenna subarrays, by processing the received signals according to different antenna subarrays, by receiving according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different sets of directional listening weights), or by processing the received signals according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (any of these operations can be referred to as "listening" according to different receiving configurations or receiving directions). In some examples, the receiving device can use a single receiving configuration to receive along a single beam direction (e.g., when receiving data signals). A single receiver configuration can be aligned to a beam direction determined based on listening in different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening in multiple beam directions).

[0103] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet fragmentation and reassembly for transmission over logical channels. The Media Access Control (MAC) layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of RRC connections (which support radio bearers for user plane data) between the UE 115 and the base station 105 or core network 130. At the physical layer, transport channels can be mapped to physical channels.

[0104] UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correct data reception on communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal and noise conditions). In some examples, the device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in a previous symbol within a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0105] In some wireless communication systems, devices can support immediate MDT measurements to test and report communication quality in areas of the network. Using measurement configurations received from network entities such as base station 105, devices such as UE 115 can collect various MDT measurements, QoE measurements, or any combination thereof to include in the MDT measurement report. Serving base station 105 can use the MDT measurement configuration to perform cell-specific MDT measurements. Some systems can implement immediate MDT reporting, where UE 115 can be configured to perform measurements and immediately report them to serving base station 105. Serving base station 105 can then send a measurement trace by combining the measurement report received from UE 115 and the measurements performed by serving base station 105, which it can use to improve communication quality and device performance in the network.

[0106] UE 115 and serving base station 105 can obtain MDT measurements based on measurement configuration received from OAM, which indicates the number of triggering events for UE 115 and serving base station to initiate MDT measurements. For example, a measurement report (e.g., an MDT measurement report or a QoE measurement report) can indicate the start of an application or service at UE 115, or it can indicate information about other triggering events. In one implementation, UE 115 and serving base station 105 can identify a list of application or service IDs eligible to be triggered as measurement collection, and UE 115 can compare the application or service IDs with the list of application or service IDs to determine whether to initiate MDT measurements. In some other implementations, UE 115 can identify a list of application or service IDs eligible to be triggered as measurement collection, and UE 115 can notify serving base station 105 to begin obtaining MDT measurements.

[0107] In another implementation, network (e.g., RAN) slicing can provide dedicated resources for applications and services. UE 115 and Serving Base Station 105 can identify different MDT or QoS reports for different network slices. In another implementation, UE 115 and Serving Base Station 105 can change the reporting interval and reporting volume for MDT measurements based on area configuration and time of day. In yet another implementation, UE 115 can be configured to obtain QoE measurements based on application and service triggers. The network can configure a specific QoE configuration for UE 115 to measure QoE based on application and service triggers. Alternatively, if UE 115 is not configured with a specific QoE configuration, a general or specific QoE configuration can be assigned to UE 115.

[0108] Figure 2 Examples of a wireless communication system 200 supporting application, service, and network slicing measurements for MDT reporting, according to various aspects of this disclosure, are shown. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. For example, the wireless communication system may implement UE 115-a and base station 105-a (which may be references) Figure 1 Signaling between UE 115 and base station 105 (example described).

[0109] Some wireless communication systems can support devices that perform MDT measurements to test and report communication quality within an area. Using measurement configuration 205 for performing MDT, devices located within wireless communication system 200 (such as UE 115-a) can collect various MDT measurements, QoE measurements, or any combination thereof to autonomously improve network performance. In some examples, UE 115-a and serving base station 105-a can collect various immediate MDT measurements that the network can use for QoS verification and other MDT purposes. Additionally or alternatively, the UE can obtain its QoE measurements to be included in a QoE measurement report used for application layer QoE verification. Serving base station 105-a can obtain MDT and QoE reports from UE 115-a and can report the MDT and QoE reports, along with the MDT measurements obtained by the serving base station, to the TCE. MDT measurements can be used to improve communication quality and device performance in the network. In some aspects, TCE may be referred to as a server or other terms. Some systems, such as wireless communication system 200, can implement immediate MDT reporting, where UE 115-a can be configured to perform measurements and immediately report the measurements to the serving cell (e.g., to the TCE of wireless communication system 200 or serving base station 105-a).

[0110] In some communication deployments (e.g., LTE, 5G / NR, and other networks), the implementation of MDT can reduce operating costs and enable higher communication quality at devices within the network. Additionally, in networks such as wireless communication systems 200, devices can support a wide range of applications and services, and QoS verification can be a factor in maintaining high performance and communication quality.

[0111] To support MDT reporting and other measurement reports for various communications and services at UE 115-a, UE 115-a performs immediate MDT measurements 210 triggered by applications or services. For example, UE 115-a can obtain MDT measurements and generate MDT reports based on the start or completion of identified applications or services. Additionally, UE 115-a can generate MDT reports for various identified changes in network slices (e.g., RAN slices), for different area configurations, for different times of day, and other network factors. Furthermore, UE 115-a can generate QoE reports based on identified applications or services. This immediate measurement and reporting enhances the performance of applications and services at UE 115-a while improving the overall communication efficiency of the network.

[0112] Additionally, network (e.g., RAN) slices can provide dedicated resources for applications and services. Because these network slices support different applications and services with varying QoS objectives, different QoS verification schemes can be implemented for different applications and services. In such cases, the network can implement different policies to meet QoS objectives based on applications, services, and network slices. Therefore, additional QoS and MDT reports can provide the network with extra information about the potential causes of poor QoE or QoS, and the network can implement various techniques to improve performance.

[0113] The wireless communication system 200 can support various measurement types (e.g., M1–M9) to obtain measurement results and report immediate MDT. When UE 115-a is in RRC connected state, UE 115-a can obtain different measurements 210. The different measurements at UE 115-a can involve multiple different system-level management procedures, such as Radio Resource Management (RRM) measurements (e.g., for measurements M1–M2), QoS verification (e.g., for measurement M6 D1, such as uplink PDCP delay measurement), and location purposes (e.g., M8–M9). In addition, the serving base station 105-a can perform different measurements for different system-level management procedures, such as RRM (e.g., for measurement M2) and QoS verification (e.g., for measurements M4–M7).

[0114] More specifically, the network may support measurement collection triggers for different measurements M1–M9. The first measurement collection trigger (M1) at UE 115-a includes Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ) measurements. M1 measurements can be combined with periodic and event-triggered measurements (A... x B y The event (as indicated by the standard) is associated with. A x An event can be represented by a specified A1-A6 event that is defined as a measurement event triggered, and B y Events can indicate measurement trigger events for B1 and B2. The second measurement collection trigger (M2) at UE115-a can include power margin report measurements and can be triggered by received power margin reports. The third measurement trigger (M3) can be a received interference power measurement. The fourth measurement collection trigger (M4) at base station 105a can include data volume measurements for uplink and downlink communications. The fifth measurement collection trigger (M5) at base station 105-a can include Internet Protocol throughput measurements for scheduled uplink and downlink communications. The sixth measurement collection trigger (M6) at both base station and UE 115-a can include packet delay measurements for uplink and downlink communications. The seventh measurement collection trigger (M7) at base station 105-a can include packet loss rate measurements for uplink and downlink. The eighth measurement collection trigger (M8) at UE 115-a can include WLAN and Bluetooth Received Signal Strength Indicator (RSSI) measurements. The ninth collection trigger (M9) at UE 115-a can include WLAN round-trip time (RTT) measurement.

[0115] In some cases, M3–M9 measurements can be associated with the end of the measurement collection period used for MDT measurements. For example, for some wireless networks (e.g., LTE and 5G / NR wireless systems), the end of the measurement period can be between 1024 ms and 1 minute. In some other cases, the OAM or base station can configure the reporting interval from 120 ms to 60 minutes, and can define the reporting amount (1 to infinity) for the reporting interval.

[0116] To trigger specific MDT measurements (M1–M9), the network can configure applications and services to be event-triggered. For example, application and service triggering could be event-triggered for M1 measurements. Alternatively, applications and services could be event-triggered for M8–M9 measurements for location purposes. Furthermore, applications and services could be event-triggered for M4–M7 measurements for QoS authentication.

[0117] In some examples, UE 115-a can be configured to recognize measurement collection trigger events (e.g., "Event S") associated with the start of an application or service at UE 115-a. In some cases, UE 115-a can identify a list of application or service IDs eligible to trigger measurement collection, and UE 115-a can compare the application or service IDs against the list of application or service IDs to determine whether to initiate MDT measurements. For example, the UE application layer at UE 115-a can report the application IDs to the UE modem, and if the list of application or service IDs (e.g., ...) is available, ... s-TriggerList If the application or service ID is included in the list of application or service IDs, then UE 115-a can perform measurements (e.g., MDT measurements or RRM measurements) based on the application or service ID included in the list of application or service IDs. Furthermore, UE 115-a can include the application or service ID in the measurement report when the application or service ID is included in the list of identification application or service IDs, so that the serving base station can determine what application or service is occurring at UE 115-a.

[0118] UE 115-a and base station 105-a can identify the number of measurements to be obtained based on applications or services, network slices, measurement configurations, etc. UE 115-a can receive measurement configuration 205 from base station 105-a or other network entities such as OAM, which contains multiple measurements that UE 115-a can perform and include in the MDT report. UE 115-a can generate a report based on measurement configuration 205 and the start of an application or service, and can send the report to base station 105-a (or a network entity such as TCE).

[0119] In some implementations, the network can support QoS authentication for applications and services, including support for a variety of applications associated with more stringent QoS service objectives, such as strict throughput, latency, and reliability targets. For example, applications may include streaming services or other services with high reliability or low latency requirements. In such cases, the start of an application or service can trigger the initiation of QoS measurements or communication with a specific network or RAN slice.

[0120] Additionally, applications and services can be event-triggered by M8–M9 measurements for location purposes. For example, UE 115-a can determine a degraded quality of service for a given application or service, and UE 115-a can use a location report to report the degraded quality of service to base station 105-a. This report can also be used at base station 105-a, allowing the base station to identify various processes to improve service for the application. The location information included in the measurement report can include detailed location information that can be configured for UE 115-a, public location information, WLAN location information, Bluetooth location information, and sensor location information.

[0121] In another implementation, the application and service can be event-triggered for M4–M7 measurements used in the QoS verification process. For example, base station 105-a can detect packets from a configured application or service (or base station 105-a initiates the application and service), and the serving base station 105-a or UE 115-a (or both) can begin collecting MDT measurements 210. In such an example, UE 115-a can include the application or service ID in the measurement report sent to base station 105-a, which can prompt base station 105-a to begin MDT measurements for the application or service indicated by UE 115-a in the measurement report.

[0122] In some cases, the network can adjust the reporting interval and reporting volume for MDT measurements based on regional configuration and time of day. For example, the network can configure measurement configuration 205 to adjust MDT measurement collection for UE 115-a and serving base station 105-a for different regions and different times of day. For example, the measurement configuration may be based on different reporting requirements at different times of day, or for different service areas with different service qualities.

[0123] For example, for some MDT measurements, the network can configure serving base station 105-a and UE 115-a with different reporting intervals and frequencies based on regional configuration and time of day. For a specific regional configuration (e.g., cell 215, gNB group, or geographic area), the network can configure UE 115-a and base station 105-a to obtain MDT measurements at a first interval (e.g., an interval of 120 ms) and outside that regional configuration at a second interval (e.g., an interval of 1024 ms). The network can similarly configure different reporting intervals and frequencies based on the geographic location of UE 115-a. Additionally, different reporting intervals, reporting frequencies, and sample sizes per report can be configured for different times of day. For example, UE 115-a and base station 105-a can collect samples for MDT measurements at higher or lower frequencies based on different times of day (e.g., based on network traffic or identified events).

[0124] In another implementation, the network can perform immediate MDT measurements based on network slices. Different network slices can support different applications and services, thus different techniques can be used for QoS verification of UE 115-a. In some examples, the network can configure base station 105-a and UE 115-a to obtain immediate MDT measurements for a specific network slice. The network can configure a list of networks or RAN slices (e.g., S-NSSAI-listThe network configures serving base station 105-a and UE 115-a to receive immediate MDT measurements for this list. In some other examples, the network can configure base station 105-a and UE 115-a with different reporting intervals and reporting volumes for different network slices, or the network can prioritize MDT reporting for different RAN slices. For example, the network can configure lower frequency MDT reporting for slices that support low-priority data and higher frequency MDT reporting for slices that support high-priority or low-latency data.

[0125] In another implementation, UE 115-a can be configured to obtain QoE measurements based on application and service triggers. The network can configure a specific QoE configuration for UE 115-a to measure QoE based on application and service triggers. Alternatively, if UE 115-a is not configured with a specific QoE configuration, a general or specific default QoE configuration can be assigned to UE 115-a. In some other cases, when UE 115-a transitions to an RRC connection state with the serving base station, the network can configure UE 115-a with a general QoE configuration, and UE 115-a can receive the general QoE configuration via RRC signaling.

[0126] A generic QoE configuration allows UE 115-a to initiate QoE measurements when an application or service is initiated. The network can indicate a list of service IDs and application IDs for which configured QoE metrics should be collected. This generic QoE configuration can be used to configure UE 115-a to capture multiple different QoE metrics, such as application layer throughput, RTT, jitter, and packet drop rate (average, excessive, or histogram). In some other examples, the network can provide a specific QoE configuration for collecting measurements for a particular application or service, and UE 115-a can use a new QoE configuration for that specific application or service.

[0127] In some examples, the network may request QoE for a specific service (e.g., a streaming service) at UE 115-a and may send a QoE configuration for reporting QoE for that service. In other cases, the network may provide QoE configuration to UE 115-a when the UE establishes an RRC connection. A general QoE configuration may include multiple application and service IDs, allowing UE 115-a to begin QoE measurements according to the general QoE configuration whenever an identified application or service begins. In some examples, UE 115-a may receive signaling, for example, from a network entity such as OAM, including configurations for MDT measurements and configurations for QoE measurements. In such cases, either configuration may indicate one or more of the triggering events described herein (e.g., the start of an application at UE 115-a, the start of a service at UE 115-a).

[0128] Figure 3 Examples of process flow 300 supporting application, service, and network slice-based measurements for MDT reporting, according to various aspects of this disclosure, are shown. In some examples, process flow 300 may implement various aspects of wireless communication system 100. For example, process flow 300 may describe communication between OAM 305, serving base station 105-b, UE 115-b, and TCE 310. Figure 3 The device described in the document may be a reference. Figure 1 and 2 Examples of the described devices, such as base station 105-b and UE 115-b, may be related to... Figure 1 and 2 Examples of base station 105 and UE 115 are described.

[0129] At point 315, OAM 305 can send a measurement configuration to base station 105-b, and base station 105-b can send a measurement configuration to UE 115-b. In some examples, base station 105-b can identify that UE 115-b will use the measurement configuration (e.g., received from the OAM interface) to identify the number of measurements to be performed and the measurements to be included in reports (e.g., MDT reports or QoE reports). For example, the measurement configuration can prompt UE 115-b to collect various immediate MDT measurements that the network can use for QoS verification and other MDT purposes. Additionally, UE 115-b can obtain its various QoE measurements to include in a QoE measurement report used for application layer QoE verification. In some examples, the measurement configuration can indicate one or more triggering events (such as the start of an application or service at UE 115-b) that, when they occur, can trigger MDT measurements at UE 115-b.

[0130] At 320, UE 115-b can identify one or more triggering events from the measurement configuration. For example, a triggering event specified by the measurement configuration could be an event that prompts UE 115-b to perform MDT measurements to be included in the report. Triggering events can be periodic events or one or more individual events specified by the measurement configuration.

[0131] At 325, UE 115-b can detect the start of an application or service, which UE 115-a can identify as a triggering event for MDT and QoE measurements based on its report configuration. In some cases, UE 115-b can be configured with a list of application IDs and service IDs that indicate the application or service that can trigger an MDT measurement. For example, UE 115-b can identify the application or service ID associated with an application or service initiated at UE 115-b. UE 115-b can compare the application or service ID with the list of application and service IDs to determine whether the initiated application or service is a triggering event for UE 115-b to obtain an MDT measurement. If the initiated application or service ID is included in the list of application and service IDs, UE 115-b can perform the MDT measurement and generate a report to send to base station 105-b. In some examples, UE 115-b can include the application or service ID in the report.

[0132] At 330, in some examples, base station 105-b can correspondingly identify the triggering event at UE 115-b, and can detect the start of an application or service at UE 115-b as a triggering event for MDT measurement.

[0133] At 335, UE 115-b may optionally send a notification to base station 105-b, which includes one or more application or service IDs identified at UE 115-b. In some examples, the application or service ID may be used by base station 105-b as a trigger event for performing MDT measurements.

[0134] At 340, base station 105-b can obtain MDT measurements based on notifications received from UE 115-b of one or more application or service IDs. In some examples, the base station can compare one or more received application or service IDs with a list of application or service IDs that prompts the base station to obtain MDT measurements. For example, the base station can determine that one or more application or service IDs are included in the list of application or service IDs, and can obtain QoS measurements (e.g., data volume measurements, Internet Protocol throughput measurements, packet delay measurements, packet loss measurements) based on this determination.

[0135] At 345, the base station can store MDT measurements (e.g., QoS measurements) obtained based on the start of a detected application or service.

[0136] At 350, UE 115-b can obtain MDT and QoE measurements based on determining that an application or service is a triggering event. In some examples, UE 115-b can obtain RRM measurements (e.g., one or more RSRP or RSRQ measurements) to be included in the report based on determining that the application or service ID is included in a list of stored IDs. UE 115-b can obtain RRM measurements as periodic or event-triggered measurements based on measurement configuration.

[0137] In some other examples, UE 115-b may obtain one or more location measurements to be included in the report based on the start of an application or service as a triggering event. For example, UE 115-b may obtain location measurements as one or more RSSI measurements or RTT measurements. Furthermore, location measurements may be associated with public location information, Wi-Fi location information, Bluetooth location information, sensor information, or any combination thereof.

[0138] In some other examples, UE 115-b may obtain one or more QoS measurements to be included in the report based on the start of an application or service triggering QoS measurements. For example, UE 115-b may obtain one or more packet delay or packet loss rate measurements or any other QoS metric.

[0139] At 355, UE 115-b can generate reports (e.g., MDT reports and QoE reports) based on the measurement configuration and the obtained MDT and QoE measurements. In some examples, UE 115-b can generate reports to include one or more application or service IDs that can prompt the base station to obtain one or more QoS measurements. For example, the base station can obtain data volume measurements, Internet Protocol throughput measurements, packet delay measurements, packet loss measurements, or any combination thereof based on the application and service IDs included in the report.

[0140] At 360°, UE 115-b can send reports including MDT measurements and QoE measurements to base station 105-b. In some examples, UE 115-b can send reports via control signaling such as RRC signaling.

[0141] At point 365, base station 105-b can save MDT measurements (e.g., RRM, location, QoS, and QoE measurements) sent from UE 115-b in a report obtained based on the start of a detected application or service. In addition to the saved measurements obtained by base station 105-b, base station 105-b can also save MDT measurements received from UE 115-b. In some examples, the measurements obtained from UE 115-b may differ from the measurements performed by base station 105-b.

[0142] At 370, base station 105-b can send reports to TCE 310. In some examples, TCE 310 can use the information included in the reports (e.g., MDT measurements, QoS measurements, QoE measurements) to improve communication quality and device performance in the network.

[0143] Figure 4 Examples of process flow 400 supporting application, service, and network slice-based measurements for MDT reporting, according to various aspects of this disclosure, are shown. In some examples, process flow 400 may implement various aspects of wireless communication system 100. For example, process flow 400 may describe communication between OAM 405, serving base station 105-c, UE 115-c, and TCE 410. Figure 4 The device described in the document may be a reference. Figure 1-3 Examples of the described devices, such as base station 105-c and UE 115-c, may be related to... Figure 1-3 Examples of base station 105 and UE 115 are described.

[0144] At 415, OAM 405 can send a measurement configuration to base station 105-b, and base station 105-c can send a measurement configuration to UE 115-c. In some examples, base station 105-c can identify that UE 115-c will use the measurement configuration (e.g., received from the OAM interface) to identify the number of measurements to be performed and the measurements to be included in the report. For example, the measurement configuration can prompt UE 115-b to collect various immediate MDT measurements that the network can use for QoS verification and other MDT purposes. Additionally, UE 115-b can obtain various QoE measurements to include in the QoE measurement report used for application layer QoE verification. In some examples, the measurement configuration may include one or more reporting adjustment factors that affect the reporting interval or reporting volume used to report reports from UE 115-c.

[0145] At 420, base station 105-c and UE 115-c can determine one or more reporting adjustment factors specific to a first area configuration common to UE 115-c and serving base station 105-c for obtaining MDT measurements. In such an example, base station 105-c and UE 115-c can obtain MDT measurements based on the reporting adjustment factors specific to the first area configuration. In some other examples, base station 105-c and UE 115-c can identify a second set of reporting adjustment factors specific to a second area configuration, wherein the second set of reporting adjustment factors differs from the one or more reporting adjustment factors specific to the first area configuration.

[0146] In some other examples, base station 105-c and UE 115-c may determine one or more reporting adjustment factors for obtaining MDT measurements associated with a time of day in which UE 115-c receives the measurement configuration, and base station 105-c and UE 115-c may obtain MDT measurements based on the reporting adjustment factors associated with the time of day. In some cases, the reporting adjustment factor associated with a first time of day may be different from the reporting adjustment factor associated with a second time of day.

[0147] In some cases, the reporting adjustment factor can be based on one or more network slices supporting communication between UE 115-c and serving base station 105-c. For example, base station 105-c or UE 115-c can identify a first network slice among one or more network slices supporting communication between UE 115-c and serving base station 105-c, and can determine that the first network slice is included in a list of network slices. The list of network slices can indicate the number of network slices that UE 115-c and base station 105-c want to obtain MDT measurements from. Base station 105-c and UE 115-c can obtain MDT measurements associated with the first network slice based on the fact that the first network slice is included in the list of network slices.

[0148] Additionally, UE 115-c can identify one or more reporting adjustment factors associated with a first network slice and a second network slice (e.g., in cases where the first network slice and the second network slice are different), wherein the reporting adjustment factor associated with the first network slice is different from the reporting adjustment factor associated with the second network slice. In some examples, serving base station 105-c can identify different reports for different networks or RAN slices.

[0149] At 425, UE 115-c can obtain MDT measurements and QoE measurements based on the measurement configuration and according to one or more reporting adjustment factors. UE 115-c can obtain MDT measurements based on the measurement configuration. In some examples, UE 115-c can obtain RRM measurements (e.g., one or more RSRP or RSRQ measurements) to be included in the report based on determining that the application or service ID is included in a list of stored IDs. UE 115-c can obtain RRM measurements as periodic or event-triggered measurements based on the measurement configuration.

[0150] In some other examples, the UE 115-c can obtain one or more location measurements to include in the report based on measurement configuration. For example, the UE 115-c can obtain location measurements as one or more RSSI measurements or RTT measurements. Furthermore, location measurements can be associated with public location information, Wi-Fi location information, Bluetooth location information, sensor information, or any combination thereof.

[0151] In some other examples, UE 115-c may obtain one or more QoS measurements to be included in the report based on the start of an application or service triggering QoS measurements. For example, UE 115-c may obtain one or more packet delay or packet loss rate measurements or any other QoS metric.

[0152] At 430, base station 105-c can obtain MDT measurements based on measurement configuration and one or more reporting adjustment factors. In some examples, the base station can obtain QoS measurements (e.g., data volume measurements, Internet Protocol throughput measurements, packet delay measurements, or packet loss measurements) based on measurement configuration.

[0153] At 435, base station 105-c can store MDT measurements (e.g., QoS measurements) obtained based on the report adjustment factor.

[0154] At 440, UE 115-c can generate reports that include MDT measurements (e.g., RRM, location, and QoS measurements).

[0155] At 445, UE 115-c can send a report based on one or more reporting adjustment factors used for MDT measurements, and base station 105-c can receive the report. In some examples, UE 115-c can use control signaling such as RRC signaling to send the report.

[0156] At 450, base station 105-c can save MDT measurements (e.g., RRM, location, and QoS measurements) sent from UE 115-c in a report. Base station 105-c can save MDT measurements received from UE 115-c, which may differ from the measurements performed by the base station.

[0157] At 455, base station 105-c can send reports to TCE 410. In some examples, TCE 410 can use the information included in the reports (e.g., MDT measurements, QoS measurements, QoE measurements) to improve communication quality and device performance in the network.

[0158] Figure 5 Examples of process flow 500 supporting application, service, and network slicing measurements for MDT reporting, according to various aspects of this disclosure, are shown. In some examples, process flow 500 may implement various aspects of wireless communication system 100. For example, process flow 500 may describe serving base station 105-d and UE 115-d (they may be about...) Figure 1-4 Communication between base station 105 and UE 115 (example described).

[0159] At 505, base station 105-d can identify a first measurement configuration (e.g., received from the OAM interface), which UE 115-c can use to identify the number of QoE measurements to be performed and the associated number of measurements to be included in the QoE report. Base station 105-d can send the first measurement configuration to UE 115-d when establishing an RRC connection with UE 115-d, and UE 115-d can receive this configuration. In some examples, the first measurement configuration may differ from the application- or service-specific measurement configuration identified by UE 115-d and may indicate one or more triggering events, such as the start of an application or service at UE 115-d, which, upon occurrence, can trigger QoE measurements at UE 115-d.

[0160] In some examples, UE 115-d can verify that the triggering event used to initiate one or more QoE measurements is not associated with an application- or service-specific measurement configuration, and UE 115-d performs QoE measurements based on this verification.

[0161] In some examples, UE 115-d can determine that the first measurement configuration is the default measurement configuration used to perform one or more QoE measurements from the UE. In some implementations, UE 115-d can be configured with a default QoE measurement configuration that is independent of the first measurement configuration received from the base station.

[0162] In some other examples, UE 115-d may receive a second measurement configuration that includes an application- or service-specific measurement configuration for performing multiple QoE measurements specific to one or more applications or services specified at UE 115-d. UE 115-d may perform QoE measurements according to the second measurement configuration based on the detection of the start of one or more specified applications or services (e.g., a trigger event). In some examples, the first measurement configuration differs from the second measurement configuration.

[0163] At 510, UE 115-d can identify one or more triggering events from a measurement configuration that prompts UE 115-d to obtain QoE measurements. For example, UE 115-d can detect the start of an application or service, which UE 115-d can identify as a triggering event for QoE measurements based on a first reporting configuration. In some cases, UE 115-d can be configured with a list of application IDs and service IDs that can indicate the application or service that can trigger QoE measurements. For example, UE 115-d can identify the application or service ID associated with an application or service initiated at UE 115-d. UE 115-d can compare the application or service ID with the list of application and service IDs to determine whether the initiated application or service is a triggering event for UE 115-d to obtain QoE measurements.

[0164] When the initiating application or service ID is included in the list of application and service IDs, UE 115-d can obtain QoE measurements and generate reports (e.g., at 520). In some examples, UE 115-d can include the application or service ID in the QoE measurement report. The QoE report can include one or more QoE measurements, such as application layer throughput measurements, RTT measurements, jitter metrics, packet loss rate, or any combination thereof.

[0165] At 525, UE 115-d can send one or more QoE measurements to base station 105-d in the measurement report, whereby the base station can use the QoE measurements to evaluate the communication quality at UE 115-d.

[0166] Figure 6 A block diagram 600 of device 605 supporting application, service, and network slicing measurements for MDT reporting is shown according to various aspects of this disclosure. Device 605 may be an example of various aspects of UE 115 as described herein. Device 605 may include a receiver 610, a communications manager 615, and a transmitter 620. Device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0167] Receiver 610 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to application, service, and network slice-based measurements used for MDT reporting). This information can be passed to other components of device 605. Receiver 610 can be a reference... Figure 9 Examples of various aspects of the transceiver 920 are described. The receiver 610 can utilize a single antenna or a set of antennas.

[0168] The communication manager 615 can perform the following operations: receive a measurement configuration from the OAM interface for performing MDT measurements to be included in the MDT report; identify one or more triggering events from the measurement configuration, which trigger the MDT measurement when they occur; detect the start of an application or service at the UE, wherein the start of the application or service is one of the one or more triggering events; obtain the MDT measurement based on the start of the application or service being one of the one or more triggering events; and send an MDT report including the MDT measurement to the TCE.

[0169] The communication manager 615 can perform the following operations: receive a measurement configuration from the OAM interface, which is used to perform MDT measurements for inclusion in the MDT report and to perform QoE measurements for inclusion in the QoE report; identify one or more triggering events from the measurement configuration, which trigger MDT and QoE measurements when they occur; detect the start of an application or service at the UE, wherein the start of the application or service is one of the one or more triggering events; send an indication to the serving base station that one or more triggering events have occurred; obtain MDT and QoE measurements based on the fact that the start of the application or service is one of the one or more triggering events; and send an MDT report and a QoE report including the MDT and QoE measurements to the server.

[0170] The communication manager 615 may also perform the following operations: receive from the OAM interface a measurement configuration for performing MDT measurements to be included in an MDT report; identify from the measurement configuration one or more reporting adjustment factors that affect at least one of the reporting interval or reporting amount used to report the MDT report; obtain the MDT measurement based on the measurement configuration and according to the one or more reporting adjustment factors; and send the MDT report to the TCE according to the one or more reporting adjustment factors.

[0171] The communication manager 615 may also perform the following operations: receive from the OAM interface a first measurement configuration for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application- or service-specific measurement configuration; detect the start of an application or service at the UE, wherein the start of the application or service is a triggering event for initiating one or more QoE measurements at the UE; perform one or more QoE measurements at the UE according to the first measurement configuration; and send one or more QoE measurements to the serving base station in a measurement report. The communication manager 615 may be an example of aspects of the communication manager 910 described herein.

[0172] The communication manager 615 or its sub-components may be implemented in hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented in processor-executable code, the functionality of the communication manager 615 or its sub-components may be performed by a general-purpose processor, DSP, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described in this disclosure.

[0173] The communication manager 615 or its subcomponents may be physically located at various locations, including being distributed such that some functions are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 615 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of this disclosure, the communication manager 615 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof.

[0174] Transmitter 620 can transmit signals generated by other components of device 605. In some examples, transmitter 620 can be co-located with receiver 610 in a transceiver module. For example, transmitter 620 can be a reference... Figure 9 Examples of various aspects of the transceiver 920 are described. The transmitter 620 can utilize a single antenna or a set of antennas.

[0175] Figure 7A block diagram 700 of a device 705 supporting application, service, and network slice-based measurements for MDT reporting, according to various aspects of this disclosure, is shown. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a communications manager 715, and a transmitter 755. Device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0176] Receiver 710 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to application, service, and network slice-based measurements used for MDT reporting). This information can be passed to other components of device 705. Receiver 710 can be a reference... Figure 9 Examples of various aspects of the transceiver 920 are described. The receiver 710 can utilize a single antenna or a set of antennas.

[0177] Communication manager 715 may be an example of aspects of communication manager 615 as described herein. Communication manager 715 may include a measurement configuration receiver 720, a measurement trigger identification component 725, an application and service identification component 730, an MDT measurement component 735, an MDT report transmitter 740, a report adjustment factor component 745, and a QoS measurement component 750. Communication manager 715 may be an example of aspects of communication manager 910 as described herein.

[0178] The measurement configuration receiver 720 can receive measurement configurations from the OAM interface for performing MDT measurements to be included in the MDT report. In some examples, the measurement configuration receiver 720 can receive measurement configurations from the OAM interface for performing MDT measurements to be included in the MDT test report and for performing QoE measurements to be included in the QoE report.

[0179] The measurement trigger identification component 725 can identify one or more trigger events from the measurement configuration, which trigger MDT measurements when they occur. In some examples, the measurement trigger identification component 725 can identify one or more trigger events from the measurement configuration, which trigger both MDT and QoE measurements when they occur.

[0180] The application and service identification component 730 can detect the start of an application or service at the UE, wherein the start of the application or service is one of one or more triggering events. In some examples, the application and service identification component 730 can send an indication to the serving base station that one or more triggering events have occurred.

[0181] The MDT measurement component 735 can obtain MDT measurements, at least in part, based on the application or service starting as one of one or more triggering events. In some examples, the MDT measurement component 735 can obtain both MDT measurements and QoE measurements, at least in part, based on the application or service starting as one of one or more triggering events.

[0182] The MDT report transmitter 740 can send an MDT report, including MDT measurements, to the TCE. In some examples, the MDT report transmitter 740 can send an MDT test and QoE report, including both MDT measurements and QoE measurements, to the server.

[0183] The measurement configuration receiver 720 can receive measurement configurations from the OAM interface for performing MDT measurements and including them in the MDT report.

[0184] The Reporting Adjustment Factor Component 745 can identify one or more reporting adjustment factors from the measurement configuration that affect at least one of the reporting intervals or reporting volumes used to report MDT reports.

[0185] The MDT measurement component 735 can obtain MDT measurements based on the measurement configuration and according to one or more reporting adjustment factors.

[0186] The MDT report transmitter 740 can send an MDT report to the TCE based on one or more report adjustment factors.

[0187] The measurement configuration receiver 720 can receive a first measurement configuration from the OAM interface for performing one or more QoE measurements at the UE. This first measurement configuration is different from the application- or service-specific measurement configuration.

[0188] The measurement trigger identification component 725 can detect the start of an application or service at the UE, wherein the start of the application or service is a trigger event used to initiate one or more QoE measurements at the UE.

[0189] The QoS measurement component 750 can perform one or more QoE measurements at the UE according to the first measurement configuration, and send one or more QoE measurements to the serving base station in the measurement report.

[0190] Transmitter 755 can transmit signals generated by other components of device 705. In some examples, transmitter 755 can be co-located with receiver 710 in a transceiver module. For example, transmitter 755 can be a reference... Figure 9 Examples of various aspects of the transceiver 920 are described. The transmitter 755 can utilize a single antenna or a set of antennas.

[0191] In some examples, the communication manager 715 may be implemented as an integrated circuit or chipset of a mobile device modem, and the receiver 710 and transmitter 755 may be implemented as analog components (e.g., amplifiers, filters, or antennas) coupled to the mobile device modem to enable wireless transmission and reception.

[0192] The Communication Manager 715 described herein can be implemented to achieve one or more potential advantages. Various implementations enable the Communication Manager 715 to: At least one implementation enables the Communication Manager 715 to effectively identify the start of an application or service that triggers the generation of an MDT report for device 705. In some other implementations, the Communication Manager 715 can adjust the amount or duration of reports used for QoS measurements based on identified network conditions, network area, time of day, network slices, and other factors.

[0193] Based on the MDT reporting techniques described herein, one or more processors of device 705 (e.g., one or more of control receiver 710, communication manager 715, and transmitter 755, or processors incorporated therein) can improve the communication quality of applications and services, as well as various network conditions. Furthermore, the techniques described herein can enhance the device's autonomous reporting when triggering events are identified or when events associated with reduced communication quality require reporting.

[0194] Figure 8 A block diagram 800 is shown of a communication manager 805 supporting application, service, and network slice-based measurements for MDT reporting, according to various aspects of this disclosure. The communication manager 805 may be an example of aspects of the communication manager 615, communication manager 715, or communication manager 910 described herein. The communication manager 805 may include a measurement configuration receiver 810, a measurement trigger identification component 815, an application and service identification component 820, an MDT measurement component 825, an MDT report transmitter 830, an application and service ID component 835, an MDT report generation component 840, an RRM measurement component 845, a QoS measurement component 850, a report adjustment factor component 855, and a network slice configuration component 860. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0195] The measurement configuration receiver 810 can receive measurement configurations from the OAM interface for performing MDT measurements to be included in the MDT report. In some examples, the measurement configuration receiver 810 can receive measurement configurations from the OAM interface for performing MDT measurements to be included in the MDT test report and for performing QoE measurements to be included in the QoE report.

[0196] In some examples, the measurement configuration receiver 810 can receive measurement configurations from the OAM interface for performing MDT measurements to be included in the MDT report.

[0197] In some examples, the measurement configuration receiver 810 may receive a second measurement configuration that includes an application- or service-specific measurement configuration for performing one or more application- or service-specific QoE measurements at the UE.

[0198] Measurement trigger identification component 815 can identify one or more trigger events from the measurement configuration, which trigger MDT measurements when they occur. In some examples, measurement configuration receiver 815 can receive measurement configuration from the OAM interface, which is used to perform MDT measurements for inclusion in the MDT test report and to perform QoE measurements for inclusion in the QoE report. In some examples, measurement trigger identification component 815 can detect the start of an application or service at the UE, wherein the start of the application or service is a trigger event for initiating one or more QoE measurements at the UE. MDT measurement component 825 can obtain MDT measurements at least in part based on the start of an application or service as one of the one or more trigger events. In some examples, MDT measurement component 825 can obtain MDT measurements at least in part based on the start of an application or service being one of the one or more trigger events.

[0199] In some examples, the MDT measurement component 825 can obtain MDT measurements based on the measurement configuration and according to one or more reporting adjustment factors.

[0200] In some examples, the MDT measurement component 825 may obtain one or more location measurements based on the start trigger of an application or service to include in the MDT report. In some examples, the MDT measurement component 825 may obtain location measurements as one or more RSSI measurements or RTT measurements, wherein the location measurements are associated with public location information, Wi-Fi location information, Bluetooth location information, sensor information, or any combination thereof.

[0201] The MDT report transmitter 830 can send an MDT report, including MDT measurements, to the TCE. In some examples, the MDT report transmitter 830 can send an MDT test and QoE report, including both MDT measurements and QoE measurements, to the server.

[0202] In some examples, the QoS measurement component 850 can receive the first measurement configuration when establishing an RRC connection with the serving base station.

[0203] The QoS measurement component 850 can perform one or more QoE measurements at the UE based on a first measurement configuration. In some examples, the QoS measurement component 850 can send one or more QoE measurements to the serving base station in a measurement report.

[0204] In some examples, the QoS measurement component 850 may obtain one or more QoS measurements based on the start trigger of an application or service to include in the MDT report. In some examples, the QoS measurement component 850 may perform QoE measurements at the UE based on a second measurement configuration, triggered by the detection of the start of one or more specified applications or services at the UE. In some cases, one or more QoS measurements include one or more packet delay measurements or packet loss rate measurements. In some cases, the QoS measurements of the serving base station include data volume measurements, Internet Protocol throughput measurements, packet delay measurements, packet loss measurements, or any combination thereof.

[0205] The report adjustment factor component 855 can identify one or more report adjustment factors from the measurement configuration that affect at least one of the reporting interval or reporting amount used to report MDT reports. In some examples, the report adjustment factor component 855 can determine that one or more report adjustment factors used to obtain MDT measurements are specific to a first area configuration common to the UE and the serving base station, wherein the MDT measurements are obtained based on report adjustment factors specific to the first area configuration.

[0206] In some examples, the reporting adjustment factor component 855 can identify a second set of reporting adjustment factors specific to a second region configuration, wherein the second set of reporting adjustment factors differs from one or more reporting adjustment factors specific to a first region configuration. In some examples, the reporting adjustment factor component 855 can determine that one or more reporting adjustment factors used to obtain MDT measurements are associated with a time of day in the UE receiving measurement configuration. In some examples, the reporting adjustment factor component 855 can obtain MDT measurements based on the reporting adjustment factors associated with a time of day.

[0207] In some examples, the report adjustment factor component 855 can identify one or more report adjustment factors associated with a first network slice and a second network slice, wherein the report adjustment factor associated with the first network slice is different from the report adjustment factor associated with the second network slice. In some cases, one or more report adjustment factors at a first time of day are different from one or more report adjustment factors at a second time of day. In some examples, the MDT report transmitter 830 can send an MDT report to the TCE based on one or more report adjustment factors.

[0208] The application and service ID component 835 can identify one or more application or service IDs associated with an application or service. In some examples, one or more application or service IDs are compared with a list of IDs stored at the UE, wherein the list of IDs includes IDs for applications or services associated with one or more triggering events. In some examples, the application and service ID component 835 can determine, based on the comparison, that one or more application or service IDs are included in the list of IDs stored at the UE.

[0209] In some examples, the Application and Service ID component 835 can receive an indication in the measurement configuration that the UE will include one or more application or service IDs in the MDT report, wherein the one or more application or service IDs prompt the serving base station to perform QoS measurements. In some examples, the Application and Service ID component 835 can identify one or more application or service IDs (IDs) associated with an application or service. In some examples, the Application and Service ID component 835 can compare the identified one or more application or service IDs with a list of IDs stored at the UE, wherein the list of IDs includes IDs for applications or services associated with one or more triggering events.

[0210] In some examples, the Application and Service ID component 835 can determine, based on comparison, that one or more application or service IDs are included in the ID list stored at the UE. The MDT report generation component 840 can generate an MDT report to include one or more application or service IDs based on the determination that one or more application or service IDs are included in the ID list stored at the UE. In some examples, the Application and Service ID component 835 can generate both the MDT report and the QoE report, to include one or more application or service IDs, based at least in part on the determination that one or more application or service IDs are included in the ID list stored at the UE. The RRM measurement component 845 can obtain RRM measurements to include in the MDT report based on the determination that one or more application or service IDs are included in the ID list stored at the UE. In some cases, the RRM measurement includes at least one of RSRP measurement or RSRQ measurement. In some cases, the RRM measurement includes periodic measurements, event-triggered measurements, or a combination thereof.

[0211] The network slice configuration component 860 can identify a first network slice in one or more network slices that support communication between the UE and the serving base station. In some examples, the network slice configuration component 860 can determine that the first network slice is included in a network slice list, wherein the network slice list indicates the network slices from which the UE and the serving base station will obtain MDT measurements, wherein the MDT measurements associated with the first network slice are obtained based on the fact that the first network slice is included in the network slice list.

[0212] In some examples, the measurement configuration receiver 810 may receive a first measurement configuration from the OAM interface for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application- or service-specific measurement configuration. In some examples, the measurement configuration receiver 810 may determine that the first measurement configuration includes a default measurement configuration for performing one or more QoE measurements at the UE.

[0213] In some examples, the measurement trigger identification component 815 can verify at the UE that the triggering event used to initiate one or more QoE measurements at the UE is not associated with an application- or service-specific measurement configuration, wherein the one or more QoE measurements are performed based on verification according to a first measurement configuration. The application and service identification component 820 can detect the start of an application or service at the UE, wherein the start of the application or service is one of one or more triggering events. In some examples, the application and service identification component 820 can send an indication to the serving base station that one or more triggering events have occurred. In some cases, the one or more QoE measurements are performed based on determination according to a first measurement configuration. In some cases, the one or more QoE measurements include application layer throughput measurements, RTT, jitter metrics, packet drop rate, or any combination thereof.

[0214] Figure 9 A schematic diagram of a system 900, including device 905 supporting application, service, and network slicing measurements for MDT reporting, is shown according to various aspects of this disclosure. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or a component including device 605, device 705, or UE 115. Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 910, an I / O controller 915, a transceiver 920, an antenna 925, a memory 930, and a processor 940. These components may be coupled via one or more buses (e.g., bus 945).

[0215] The communication manager 910 can perform the following operations: receive a measurement configuration from the OAM interface for performing MDT measurements to be included in the MDT report; identify one or more triggering events from the measurement configuration, which trigger the MDT measurement when they occur; detect the start of an application or service at the UE, wherein the start of the application or service is one of the one or more triggering events; obtain the MDT measurement based at least in part on the fact that the start of the application or service is one of the one or more triggering events; and send an MDT report including the MDT measurement to the TCE.

[0216] The communication manager 910 can perform the following operations: receive a measurement configuration from the OAM interface, which is used to perform MDT measurements for inclusion in the MDT report and to perform QoE measurements for inclusion in the QoE report; identify one or more triggering events from the measurement configuration, which trigger MDT and QoE measurements when they occur; detect the start of an application or service at the UE, wherein the start of the application or service is one of the one or more triggering events; send an indication to the serving base station that one or more triggering events have occurred; obtain MDT and QoE measurements based on the fact that the start of the application or service is one of the one or more triggering events; and send an MDT report and a QoE report including the MDT and QoE measurements to the server.

[0217] The communication manager 910 can also perform the following operations: receive from the OAM interface a measurement configuration for performing MDT measurements to be included in an MDT report; identify from the measurement configuration one or more reporting adjustment factors that affect at least one of the reporting interval or reporting amount used to report the MDT report; obtain the MDT measurement based on the measurement configuration and according to the one or more reporting adjustment factors; and send the MDT report to the TCE according to the one or more reporting adjustment factors.

[0218] The communication manager 910 can also perform the following operations: receive from the OAM interface a first measurement configuration for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application- or service-specific measurement configuration; detect the start of an application or service at the UE, wherein the start of the application or service is a triggering event for initiating one or more QoE measurements at the UE; perform one or more QoE measurements at the UE according to the first measurement configuration; and send one or more QoE measurements to the serving base station in a measurement report.

[0219] I / O controller 915 manages input and output signals for device 905. I / O controller 915 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 915 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 915 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In other cases, I / O controller 915 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, I / O controller 915 may be implemented as part of a processor. In some cases, a user may interact with device 905 via I / O controller 915 or via hardware components controlled by I / O controller 915.

[0220] Transceiver 920 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, transceiver 920 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 920 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna.

[0221] In some cases, a wireless device may include a single antenna 1225. However, in other cases, the device may have more than one antenna 925, which are capable of transmitting or receiving multiple wireless transmissions simultaneously.

[0222] Memory 930 may include random access memory (RAM) and read-only memory (ROM). Memory 930 may store computer-readable, computer-executable code 935, which includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, in addition to this, memory 930 may also contain a BIOS, which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0223] Processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 940 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 940. Processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting application-, service-, and network-slice-based measurements for MDT reporting).

[0224] Code 935 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 935 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, code 935 may not be directly executable by processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0225] Figure 10 A block diagram 1000 of a device 1005 supporting application, service, and network slicing measurements for MDT reporting, according to various aspects of this disclosure, is shown. Device 1005 may be an example of various aspects of base station 105 as described herein. Device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1020. Device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0226] Receiver 1010 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to application, service, and network slice-based measurements used for MDT reporting). This information can be passed to other components of device 1005. Receiver 1010 can be a reference... Figure 13 Examples of various aspects of the transceiver 1320 are described. The receiver 1010 may utilize a single antenna or a set of antennas.

[0227] The communication manager 1015 can perform the following operations: send a measurement configuration received from the OAM interface to the UE for performing MDT measurements to be included in an MDT report, the measurement configuration indicating one or more triggering events, the one or more triggering events including the start of an application or service at the UE, which triggers the MDT measurement at the UE when it occurs; and receive an MDT report including the MDT measurements from the UE. The communication manager 1015 can also perform the following operations: send a measurement configuration received from the OAM interface to the UE for performing MDT measurements to be included in an MDT report, the measurement configuration including one or more reporting adjustment factors affecting at least one of the reporting interval or reporting amount used to report the MDT report; and receive the MDT report from the UE according to the one or more reporting adjustment factors. The communication manager 1015 can also perform the following operations: send a first measurement configuration received from the OAM interface to the UE for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application or service-specific measurement configuration, wherein the first measurement configuration indicates the start of an application or service as the triggering event for initiating one or more QoE measurements at the UE; and receive one or more QoE measurements from the UE in the measurement report.

[0228] The communication manager 1015 may also perform the following operations: send to the UE a first measurement configuration received from the OAM interface for performing MDT measurements to be included in an MDT report, and a second measurement configuration received from the OAM interface for performing QoE measurements at the UE, the second measurement configuration being different from an application- or service-specific measurement configuration, wherein the first or second measurement configuration indicates one or more triggering events, the one or more triggering events including the start of an application or service at the UE that, when it occurs, triggers an MDT measurement, a QoE measurement, the generation of a message indicating one or more triggering events, or any combination thereof; and receive from the UE an MDT report including MDT measurements or a measurement report including one or more QoE measurements. The communication manager 1015 may be an example of aspects of the communication manager 1310 described herein.

[0229] The communication manager 1015 or its sub-components may be implemented in hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented in processor-executable code, the functionality of the communication manager 1015 or its sub-components may be performed by a general-purpose processor, DSP, application-specific integrated circuit (ASIC), FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described in this disclosure.

[0230] The communication manager 1015 or its subcomponents may be physically located at various locations, including being distributed such that some functions are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 1015 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of this disclosure, the communication manager 1015 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof.

[0231] Transmitter 1020 can transmit signals generated by other components of device 1005. In some examples, transmitter 1020 can be co-located with receiver 1010 in a transceiver module. For example, transmitter 1020 can be a reference... Figure 13 Examples of various aspects of the transceiver 1320 are described. The transmitter 1020 may utilize a single antenna or a set of antennas.

[0232] Figure 11 A block diagram 1100 of a device 1105 supporting application, service, and network slicing measurements for MDT reporting, according to various aspects of this disclosure, is shown. Device 1105 may be an example of aspects of device 1005 or base station 105 as described herein. Device 1105 may include a receiver 1110, a communication manager 1115, and a transmitter 1135. Device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0233] Receiver 1110 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to application, service, and network slice-based measurements used for MDT reporting). This information can be passed to other components of device 1105. Receiver 1110 can be a reference... Figure 13 Examples of various aspects of the transceiver 1320 are described. The receiver 1110 may utilize a single antenna or a set of antennas.

[0234] Communication manager 1115 may be an example of aspects of communication manager 1015 as described herein. Communication manager 1115 may include measurement configuration transmitter 1120, MDT report receiver 1125, and QoS measurement receiver 1130. Communication manager 1115 may be an example of aspects of communication manager 1310 as described herein.

[0235] The measurement configuration transmitter 1120 can send to the UE a measurement configuration received from the OAM interface for performing MDT measurements to be included in the MDT report. The measurement configuration indicates one or more triggering events, including the start of an application or service at the UE that triggers the MDT measurement at the UE when it occurs.

[0236] The MDT report receiver 1125 can receive MDT reports, including MDT measurements, from the UE.

[0237] The measurement configuration transmitter 1120 can send to the UE a measurement configuration received from the OAM interface for performing MDT measurements to be included in the MDT report. The measurement configuration includes one or more reporting adjustment factors that affect at least one of the reporting interval or reporting amount used to report the MDT report.

[0238] MDT report receiver 1125 can receive MDT reports from UE based on one or more report adjustment factors.

[0239] The measurement configuration transmitter 1120 can send a first measurement configuration received from the OAM interface to the UE for performing one or more QoE measurements at the UE. The first measurement configuration is different from the application- or service-specific measurement configuration, wherein the first measurement configuration will be used to indicate the start of an application or service as a triggering event for initiating one or more QoE measurements at the UE.

[0240] The QoS measurement receiver 1130 can receive one or more QoE measurements from the UE in the measurement report.

[0241] The measurement configuration transmitter 1120 can send to the UE a first measurement configuration received from the OAM interface for performing MDT measurements to be included in the MDT report, and a second measurement configuration received from the OAM interface for performing QoE measurements at the UE. The second measurement configuration is different from the application- or service-specific measurement configuration. The first or second measurement configuration indicates one or more triggering events, including the start of an application or service at the UE that, when it occurs, triggers an MDT measurement, a QoE measurement, the generation of a message indicating one or more triggering events, or any combination thereof.

[0242] The MDT report receiver 1125 can receive an MDT report that includes MDT measurements or a measurement report that includes one or more QoE measurements from the UE.

[0243] Transmitter 1135 can transmit signals generated by other components of device 1105. In some examples, transmitter 1135 can be co-located with receiver 1110 in a transceiver module. For example, transmitter 1135 can be a reference... Figure 13 Examples of various aspects of the transceiver 1320 are described. The transmitter 1135 can utilize a single antenna or a set of antennas.

[0244] Figure 12 A block diagram 1200 is shown of a communication manager 1205 supporting application, service, and network slice-based measurements for MDT reporting, according to various aspects of this disclosure. The communication manager 1205 may be an example of aspects of the communication manager 1015, communication manager 1115, or communication manager 1310 described herein. The communication manager 1205 may include a measurement configuration transmitter 1210, an MDT report receiver 1215, an application and service ID component 1220, an RRM measurement component 1225, an MDT measurement component 1230, a QoS measurement component 1235, a report adjustment factor component 1240, a network slice configuration component 1245, a QoS measurement receiver 1250, and a measurement trigger identification component 1255. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0245] Measurement configuration transmitter 1210 can send to the UE a measurement configuration received from the OAM interface for performing MDT measurements to be included in the MDT report. The measurement configuration indicates one or more triggering events, including the start of an application or service at the UE that triggers the MDT measurement at the UE upon occurrence. Measurement trigger identification component 1255 can verify that the triggering event for initiating one or more QoE measurements at the UE is not associated with an application- or service-specific measurement configuration, wherein the one or more QoE measurements are based on verification received according to the first measurement configuration.

[0246] In some examples, the measurement configuration transmitter 1210 may send to the UE a measurement configuration received from the OAM interface for performing MDT measurements to be included in the MDT report. The measurement configuration includes one or more reporting adjustment factors that affect at least one of the reporting interval or reporting amount used to report the MDT report.

[0247] In some examples, the measurement configuration transmitter 1210 may send to the UE a first measurement configuration received from the OAM interface for performing one or more QoE measurements at the UE. This first measurement configuration differs from application- or service-specific measurement configurations, wherein the first measurement configuration will be used to trigger an event indicating the start of an application or service for initiating one or more QoE measurements at the UE. In some examples, the measurement configuration transmitter 1210 may determine that the first measurement configuration includes a default measurement configuration for performing one or more QoE measurements at the UE. In some examples, the measurement configuration transmitter 1210 may send the first measurement configuration when establishing an RRC connection with the UE.

[0248] In some examples, the measurement configuration transmitter 1210 may transmit a second measurement configuration received from OAM, which includes a UE-specific measurement configuration for QoE measurements of one or more specified applications or services at the UE.

[0249] In some examples, the measurement configuration transmitter 1210 may transmit a first measurement configuration received from the OAM interface for performing MDT measurements to be included in the MDT report, and a second measurement configuration received from the OAM interface for performing QoE measurements at the UE, the second measurement configuration being different from an application- or service-specific measurement configuration. The first or second measurement configuration indicates one or more triggering events, including the start of an application or service at the UE that, upon occurrence, triggers an MDT measurement, a QoE measurement, the generation of a message indicating one or more triggering events, or any combination thereof. The measurement trigger identification component 1255 may verify that the triggering events used to initiate one or more QoE measurements at the UE are not associated with an application- or service-specific measurement configuration, wherein the one or more QoE measurements are based on verification received according to the second measurement configuration.

[0250] In some examples, the measurement configuration transmitter 1210 may transmit a third measurement configuration received from OAM, which includes a UE-specific measurement configuration for one or more specified application or service-specific QoE measurements at the UE. In some examples, the measurement configuration transmitter 1210 may determine that a second measurement configuration includes a default measurement configuration for performing one or more QoE measurements at the UE.

[0251] MDT report receiver 1215 can receive MDT reports, including MDT measurements, from the UE. In some examples, MDT report receiver 1215 can receive MDT reports from the UE based on one or more report adjustment factors. In some examples, MDT report receiver 1215 can receive MDT reports based on one or more application or service IDs being included in an ID list stored at the UE, the MDT report including one or more application or service IDs. In some examples, MDT report receiver 1215 can receive MDT measurements based on a report adjustment factor associated with the time of day.

[0252] In some examples, the MDT report receiver 1215 can receive an MDT report that includes MDT measurements or a measurement report that includes one or more QoE measurements from the UE.

[0253] The QoS measurement component 1235 can receive one or more QoS measurements based on one or more QoS measurements included in the MDT report obtained upon the start of an application or service. In some examples, the QoS measurement component 1235 can measure one or more QoS metrics based on one or more application or service IDs received in the MDT report. In some cases, the one or more QoS measurements include one or more packet delay measurements or packet loss rate measurements. In some cases, QoS measurements performed by the serving base station include data volume measurements, Internet Protocol throughput measurements, packet delay measurements, packet loss measurements, or any combination thereof.

[0254] QoS measurement receiver 1250 can receive one or more QoE measurements from the UE in a measurement report. In some examples, QoS measurement receiver 1250 can receive QoE measurements from the UE based on the start of one or more specified applications or services at the UE, according to a second measurement configuration. In some examples, QoS measurement receiver 1250 can receive QoE measurements from the UE based on the start of one or more specified applications or services at the UE, according to a third measurement configuration. In some cases, one or more QoE measurements include application layer throughput measurements, RTT, jitter metrics, packet drop rate, or any combination thereof.

[0255] Application and Service ID component 1220 can identify one or more application or service IDs associated with an application or service, wherein the one or more application or service IDs are included in an ID list stored at the UE and associated with one or more triggering events at the UE. In some examples, application and service ID component 1220 can identify one or more application or service IDs associated with an application or service, wherein the one or more application or service IDs are included in an ID list stored at the UE and associated with one or more triggering events at the UE.

[0256] RRM measurement component 1225 can receive RRM measurements in the MDT report based on determining that one or more application or service IDs are included in the ID list stored at the UE. In some cases, RRM measurements include at least one of RSRP measurements or RSRQ measurements. In some cases, RRM measurements include periodic measurements, event-triggered measurements, or a combination thereof.

[0257] The MDT measurement component 1230 can receive one or more location measurements in the MDT report by obtaining one or more location measurements at the UE based on the start trigger of an application or service. In some examples, the MDT measurement component 1230 can receive the location measurements as one or more RSSI measurements or RTT measurements, wherein the location measurements are associated with public location information, wireless LAN location information, Bluetooth location information, sensor information, or any combination thereof.

[0258] The report adjustment factor component 1240 can assign one or more report adjustment factors for obtaining MDT measurements by the UE to a first area configuration common to both the UE and the serving base station, wherein the MDT measurements are based on report adjustment factors specific to the first area configuration. In some examples, the report adjustment factor component 1240 can assign a second set of report adjustment factors specific to a second area configuration, wherein the second set of report adjustment factors differs from the one or more report adjustment factors specific to the first area configuration.

[0259] In some examples, the reporting adjustment factor component 1240 can determine that one or more reporting adjustment factors used to obtain MDT measurements will be associated with a time of day when the serving base station sends the measurement configuration. In some cases, one or more reporting adjustment factors at a first time of day differ from one or more reporting adjustment factors at a second time of day.

[0260] The network slice configuration component 1245 can identify a first network slice among one or more network slices that support communication between the UE and the serving base station. In some examples, the network slice configuration component 1245 can determine that the first network slice is included in a network slice list, wherein the network slice list indicates network slices identified by the serving base station for the UE to obtain MDT measurements, wherein the MDT measurements associated with the first network slice are based on the fact that the first network slice is included in the network slice list.

[0261] In some examples, the network slice configuration component 1245 can assign one or more reporting adjustment factors associated with a first network slice and a second network slice, wherein the reporting adjustment factor associated with the first network slice is different from the reporting adjustment factor associated with the second network slice.

[0262] Figure 13A schematic diagram of a system 1300, including device 1305 supporting application, service, and network slicing measurements for MDT reporting, is shown according to various aspects of this disclosure. Device 1305 may be an example of device 1005, device 1105, or base station 105 as described herein, or a component including device 1005, device 1105, or base station 105. Device 1305 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 1310, a network communication manager 1315, a transceiver 1320, an antenna 1325, a memory 1330, a processor 1340, and an inter-site communication manager 1345. These components may be coupled via one or more buses (e.g., bus 1350).

[0263] The communication manager 1310 can perform the following operations: send a measurement configuration received from the OAM interface to the UE for performing MDT measurements to be included in an MDT report, the measurement configuration indicating one or more triggering events, the one or more triggering events including the start of an application or service at the UE, which triggers the MDT measurement at the UE when it occurs; and receive an MDT report including the MDT measurements from the UE. The communication manager 1310 can also perform the following operations: send a measurement configuration received from the OAM interface to the UE for performing MDT measurements to be included in an MDT report, the measurement configuration including one or more reporting adjustment factors affecting at least one of the reporting interval or reporting amount used to report the MDT report; and receive the MDT report from the UE according to the one or more reporting adjustment factors. The communication manager 1310 can also perform the following operations: send a first measurement configuration received from the OAM interface to the UE for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application or service-specific measurement configuration, wherein the first measurement configuration indicates the start of an application or service as the triggering event for initiating one or more QoE measurements at the UE; and receive one or more QoS measurements from the UE in the measurement report.

[0264] The communication manager 1310 may also perform the following operations: send to the UE a first measurement configuration received from the OAM interface for performing MDT measurements to be included in an MDT report, and a second measurement configuration received from the OAM interface for performing QoE measurements at the UE, the second measurement configuration being different from an application- or service-specific measurement configuration, wherein the first or second measurement configuration indicates one or more triggering events, the one or more triggering events including the start of an application or service at the UE that, when it occurs, triggers an MDT measurement, a QoE measurement, the generation of a message indicating one or more triggering events, or any combination thereof; and receive from the UE an MDT report including MDT measurements or a measurement report including one or more QoE measurements.

[0265] The network communication manager 1315 can manage communications with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1315 can manage the transmission of data communications to client devices (e.g., one or more UEs 115).

[0266] Transceiver 1320 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, transceiver 1320 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1320 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna.

[0267] In some cases, a wireless device may include a single antenna 1325. However, in other cases, a device may have more than one antenna 1325, which may be able to transmit or receive multiple wireless transmissions simultaneously.

[0268] Memory 1330 may include RAM, ROM, or a combination thereof. Memory 1330 may store computer-readable code 1335, including instructions that, when executed by a processor (e.g., processor 1340), cause the device to perform the various functions described herein. In some cases, memory 1330 may include the like, which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0269] Processor 1340 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1340 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks supporting application-, service-, and network-slice-based measurements for MDT reporting).

[0270] Inter-site communication manager 1345 can manage communication with other base stations 105, and may include a controller or scheduler for controlling communication with UE 115 in coordination with other base stations 105. For example, inter-site communication manager 1345 can coordinate the scheduling of UE 115's transmissions for various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-site communication manager 1345 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0271] Code 1335 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 1335 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, code 1335 may not be directly executable by processor 1340, but may cause a computer (e.g., at compile and execution time) to perform the functions described herein.

[0272] Figure 14 A flowchart illustrating a method 1400 for application, service, and network slicing-based measurements supporting MDT reporting, according to various aspects of this disclosure, is shown. Operation of method 1400 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1400 can be implemented by, as referred to... Figures 6 to 9 The described communication manager is used to execute this. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively or concurrently, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0273] At 1405, the UE can receive a measurement configuration from the OAM interface. This configuration is used to perform MDT measurements for inclusion in the MDT report and to perform QoE measurements for inclusion in the QoE report. The operation at 1405 can be performed according to the methods described herein. In some examples, aspects of the operation at 1405 can be determined by reference to... Figures 6 to 9 The described measurement configuration is used to perform the measurement.

[0274] At 1410, the UE can identify one or more trigger events from the measurement configuration, which, when they occur, trigger both MDT and QoE measurements. The operation of 1410 can be performed according to the methods described herein. In some examples, aspects of the operation of 1410 can be defined as follows: Figures 6 to 9 The described measurement triggers the identification component to perform the action.

[0275] At point 1415, the UE can detect the start of an application or service, where the start of the application or service is one of one or more triggering events. The operation at point 1415 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1415 can be derived from, as referenced... Figures 6 to 9 The described services and applications identify the components to be executed.

[0276] At point 1420, the UE can send an indication to the serving base station that one or more triggering events have occurred. The operation at point 1420 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1420 can be derived as described in reference... Figures 6 to 9 The described application and service identify the components to be executed.

[0277] At point 1425, the UE can obtain MDT and QoE measurements, at least in part, based on the application or service starting as one of one or more trigger events. The operation at point 1425 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1425 can be derived as referenced... Figures 6 to 9 The MDT measurement components described are used to perform this.

[0278] At point 1430, the UE can send an MDT report and a QoE report, including MDT measurements and QoE measurements, to the server. The operation at point 1430 can be performed according to the method described herein. In some examples, aspects of the operation at point 1430 can be determined by referring to... Figures 6 to 9 The MDT report transmitter is described and executed.

[0279] Figure 15 A flowchart illustrating a method 1500 for application, service, and network slicing-based measurements for MDT reporting, according to various aspects of this disclosure, is shown. Operation of method 1500 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1500 can be implemented by, as referred to... Figures 6 to 9 The described communication manager is used to execute this. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively or concurrently, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0280] At 1505, the UE can receive a measurement configuration from the OAM interface. This configuration is used to perform MDT measurements for inclusion in the MDT report and to perform QoE measurements for inclusion in the QoE report. Operation at 1505 can be performed according to the methods described herein. In some examples, aspects of operation at 1505 can be determined by reference to... Figures 6 to 9 The described measurement configuration is used to perform the measurement.

[0281] At 1510, the UE can identify one or more trigger events from the measurement configuration, which, when they occur, trigger both MDT and QoE measurements. The operation of 1510 can be performed according to the methods described herein. In some examples, aspects of the operation of 1510 can be defined as follows: Figures 6 to 9 The described measurement triggers the identification component to perform the action.

[0282] At point 1515, the UE can detect the start of an application or service, where the start of the application or service is one of one or more triggering events. The operation of point 1515 can be performed according to the methods described herein. In some examples, aspects of the operation of point 1515 can be derived from, as referenced... Figures 6 to 9 The described application and service identify the components to be executed.

[0283] At point 1520, the UE can send an indication to the serving base station that one or more triggering events have occurred. The operation at point 1520 can be performed according to the method described herein. In some examples, aspects of the operation at point 1520 can be derived as described in reference... Figures 6 to 9 The described application and service identify the components to be executed.

[0284] At point 1525, the UE can obtain MDT and QoE measurements, at least in part, based on the application or service starting as one of one or more triggering events. Operation at point 1525 can be performed according to the methods described herein. In some examples, aspects of operation at point 1525 can be derived from, as referenced... Figures 6 to 9 The MDT measurement components described are used to perform this.

[0285] At point 1530, the UE can identify one or more application or service IDs associated with an application or service. Operations at point 1530 can be performed according to the methods described herein. In some examples, aspects of operations at point 1530 can be derived from, as referenced... Figures 6 to 9 The application and service ID components are described and used for execution.

[0286] At point 1535, the UE can compare one or more application or service IDs with a list of IDs stored at the UE, wherein the ID list includes IDs of applications or services associated with one or more triggering events. The operation at point 1535 can be performed according to the method described herein. In some examples, aspects of the operation at point 1535 can be derived from, as referenced... Figures 6 to 9 The application and service ID components are described and used for execution.

[0287] At 1540, the UE can determine, based on comparison, that one or more application or service IDs are included in the ID list stored at the UE. The operation at 1540 can be performed according to the methods described herein. In some examples, aspects of the operation at 1540 can be determined by, as referenced... Figures 6 to 9 The application and service ID components are described and used for execution.

[0288] At point 1545, the UE can send an MDT report and a QoE report, including MDT measurements and QoE measurements, to the server. The operation at point 1545 can be performed according to the method described herein. In some examples, aspects of the operation at point 1545 can be defined as follows: Figures 6 to 9 The MDT report transmitter is described and executed.

[0289] Figure 16 A flowchart illustrating a method 1600 for application, service, and network slicing-based measurements supporting MDT reporting, according to various aspects of this disclosure, is shown. Operation of method 1600 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1600 can be implemented by, as referenced... Figures 6 to 9 The described communication manager is used to execute this. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively or concurrently, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0290] At 1605, the UE can receive a measurement configuration from the OAM interface. This configuration is used to perform MDT measurements for inclusion in the MDT report and to perform QoE measurements for inclusion in the QoE report. Operation at 1605 can be performed according to the methods described herein. In some examples, aspects of operation at 1605 can be determined by reference to... Figures 6 to 9 The described measurement configuration is used to perform the measurement.

[0291] At 1610, the UE can identify one or more trigger events from the measurement configuration, which, when they occur, trigger both MDT and QoE measurements. Operation of 1610 can be performed according to the methods described herein. In some examples, aspects of the operation of 1610 can be defined as follows: Figures 6 to 9 The described measurement triggers the identification component to perform the action.

[0292] At point 1615, the UE can detect the start of an application or service, where the start of the application or service is one of one or more triggering events. The operation of point 1615 can be performed according to the methods described herein. In some examples, aspects of the operation of point 1615 can be derived from, as referenced... Figures 6 to 9 The described services and applications identify the components to be executed.

[0293] At point 1620, the UE can send an indication to the serving base station that one or more triggering events have occurred. The operation at point 1620 can be performed according to the method described herein. In some examples, aspects of the operation at point 1620 can be derived as described in reference... Figures 6 to 9 The described services and applications identify the components to be executed.

[0294] At point 1625, the UE can obtain MDT and QoE measurements, at least in part, based on the application or service starting as one of one or more trigger events. Operations at point 1625 can be performed according to the methods described herein. In some examples, aspects of operations at point 1625 can be derived from, as referenced... Figures 6 to 9 The MDT measurement components described are used to perform this.

[0295] At point 1630, the UE can obtain one or more location measurements based on the start trigger of an application or service to include in the MDT report. The operation at point 1630 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1630 can be determined by referring to... Figures 6 to 9 The MDT measurement components described are used to perform this.

[0296] At step 1635, the UE can send an MDT report and a QoE report, including MDT measurements and QoE measurements, to the server. The operation at step 1635 can be performed according to the method described herein. In some examples, aspects of the operation at step 1635 can be determined by referring to... Figures 6 to 9 The MDT report transmitter is described and executed.

[0297] Figure 17 A flowchart illustrating method 1700 for application, service, and network slicing-based measurements for MDT reporting, according to various aspects of this disclosure, is shown. Operation of method 1700 can be implemented by UE 115 or its components as described herein. For example, operation of method 1700 can be implemented by, as referenced... Figures 6 to 9 The described communication manager is used to execute this. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively or concurrently, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0298] At 1705, the UE can receive measurement configurations from the OAM interface for performing MDT measurements to be included in the MDT report. Operation at 1705 can be performed according to the methods described herein. In some examples, aspects of operation at 1705 can be determined by referring to... Figures 6 to 9 The described measurement configuration is used to perform the measurement.

[0299] At 1710, the UE can identify from the measurement configuration one or more reporting adjustment factors that affect at least one of the reporting interval or reporting amount used for reporting MDT reports. Operation 1710 can be performed according to the methods described herein. In some examples, aspects of operation 1710 can be determined by, as referenced... Figures 6 to 9 The report adjustment factor component is described to perform this.

[0300] At 1715, the UE can obtain MDT measurements based on the measurement configuration and according to one or more reporting adjustment factors. Operation at 1715 can be performed according to the methods described herein. In some examples, aspects of operation at 1715 can be determined by, as referenced... Figures 6 to 9 The MDT measurement components described are used to perform this.

[0301] At point 1720, the UE can send an MDT report to the TCE based on one or more reporting adjustment factors. The operation at point 1720 can be performed according to the method described herein. In some examples, aspects of the operation at point 1720 can be determined by referring to... Figures 6 to 9 The MDT report transmitter is described and executed.

[0302] Figure 18 A flowchart illustrating method 1800 for application, service, and network slicing-based measurements for MDT reporting, according to various aspects of this disclosure, is shown. Operation of method 1800 can be implemented by UE 115 or its components as described herein. For example, operation of method 1800 can be implemented by, as referred to... Figures 6 to 9 The described communication manager is used to execute this. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively or concurrently, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0303] At 1805, the UE can receive measurement configuration from the OAM interface for performing MDT measurements to be included in the MDT report. The operation at 1805 can be performed according to the methods described herein. In some examples, aspects of the operation at 1805 can be defined as follows: Figures 6 to 9 The described measurement configuration is used to perform the measurement.

[0304] At 1810, the UE can identify one or more reporting adjustment factors from the measurement configuration that affect at least one of the reporting interval or reporting amount used for reporting MDT reports. The operation at 1810 can be performed according to the method described herein. In some examples, aspects of the operation at 1810 can be determined by, as referenced... Figures 6 to 9 The report adjustment factor component is described to perform this.

[0305] At point 1815, the UE can identify a first network slice among one or more network slices that support communication between the UE and the serving base station. Operation at point 1815 can be performed according to the method described herein. In some examples, aspects of operation at point 1815 can be derived from, as referenced... Figures 6 to 9 The network slicing configuration component is described and executed.

[0306] At 1820, the UE can determine that a first network slice is included in the network slice list, wherein the network slice list indicates the network slices from which the UE and the serving BS will obtain MDT measurements, wherein the MDT measurements associated with the first network slice are obtained based on the fact that the first network slice is included in the network slice list. The operation at 1820 can be performed according to the method described herein. In some examples, aspects of the operation at 1820 can be derived from, as referenced... Figures 6 to 9 The network slicing configuration component is described and executed.

[0307] At 1825, the UE can obtain MDT measurements based on the measurement configuration and according to one or more reporting adjustment factors. Operation at 1825 can be performed according to the method described herein. In some examples, aspects of operation at 1825 can be determined by referring to... Figures 6 to 9 The MDT measurement components described are used to perform this.

[0308] At 1830, the UE can send an MDT report to the TCE based on one or more reporting adjustment factors. The operation at 1830 can be performed according to the method described herein. In some examples, aspects of the operation at 1830 can be determined by referring to... Figures 6 to 9 The MDT report transmitter is described and executed.

[0309] Figure 19 A flowchart illustrating a method 1900 for application, service, and network slicing-based measurements for MDT reporting, according to various aspects of this disclosure, is shown. Operation of method 1900 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1900 can be implemented by, as referenced... Figures 6 to 9 The described communication manager is used to execute this. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively or concurrently, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0310] At 1905, the UE can receive a first measurement configuration from the OAM interface for performing one or more QoE measurements at the UE. This first measurement configuration differs from application- or service-specific measurement configurations. Operations at 1905 can be performed according to the methods described herein. In some examples, aspects of the operations at 1905 can be derived from, as referenced... Figures 6 to 9The described measurement configuration is used to perform the measurement.

[0311] At point 1910, the UE can detect the start of an application or service, where the start of the application or service is a triggering event used to initiate one or more QoE measurements at the UE. The operation of point 1910 can be performed according to the methods described herein. In some examples, aspects of the operation of point 1910 can be derived from, as referenced... Figures 6 to 9 The described measurement triggers the identification component to perform the action.

[0312] At point 1915, the UE can perform one or more QoE measurements based on a first measurement configuration. The operation at point 1915 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1915 can be determined by, as referenced... Figures 6 to 9 The QoS measurement components described are used to perform this.

[0313] At point 1920, the UE can send one or more QoE measurements to the serving base station in the measurement report. The operation at point 1920 can be performed according to the method described herein. In some examples, aspects of the operation at point 1920 can be defined as follows: Figures 6 to 9 The QoS measurement components described are used to perform this.

[0314] Figure 20 A flowchart illustrating a method 2000 for application, service, and network slice-based measurements used in MDT reporting, according to various aspects of this disclosure, is shown. Operation of method 2000 can be implemented by a base station 105 or its components as described herein. For example, operation of method 2000 can be implemented by, as described in reference... Figures 10 to 13 The described communication manager is used to execute this. In some examples, the base station may execute a set of instructions to control the functional units of the base station to perform the functions described herein. Alternatively or concurrently, the base station may use dedicated hardware to perform aspects of the functions described herein.

[0315] In 2005, the base station can send a measurement configuration received from the OAM interface to the UE for performing MDT measurements to be included in the MDT report. The measurement configuration indicates one or more triggering events, including the start of an application or service at the UE that triggers the MDT measurement at the UE upon occurrence. Operation 2005 can be performed according to the method described herein. In some examples, aspects of operation 2005 can be determined by referring to... Figures 10 to 13 The described measurement configuration is used to perform the transmitter.

[0316] At 2010, the base station can receive an MDT report from the UE, including MDT measurements. Operation at 2010 can be performed according to the method described herein. In some examples, aspects of operation at 2010 can be determined by referring to... Figures 10 to 13 The described MDT report receiver is used to perform the operation.

[0317] Figure 21 A flowchart illustrating method 2100 for application, service, and network slice-based measurements supporting MDT reporting, according to various aspects of this disclosure, is shown. Operation of method 2100 can be implemented by base station 105 or its components as described herein. For example, operation of method 2100 can be implemented by, as referred to... Figures 10 to 13 The described communication manager is used to execute this. In some examples, the base station may execute a set of instructions to control the functional units of the base station to perform the functions described herein. Alternatively or concurrently, the base station may use dedicated hardware to perform aspects of the functions described herein.

[0318] At 2105, the base station may send to the UE a measurement configuration received from the OAM interface for performing MDT measurements to be included in the MDT report. The measurement configuration includes one or more reporting adjustment factors affecting at least one of the reporting interval or reporting amount used for reporting the MDT report. Operation 2105 can be performed according to the method described herein. In some examples, aspects of the operation of 2105 may be determined by reference to... Figures 10 to 13 The described measurement configuration is used to perform the transmitter.

[0319] At point 2110, the base station can receive an MDT report from the UE based on one or more report adjustment factors. The operation at point 2110 can be performed according to the method described herein. In some examples, aspects of the operation at point 2110 can be determined by, as referenced... Figures 10 to 13 The described MDT report receiver is used to perform the operation.

[0320] Figure 22 A flowchart illustrating method 2200 for application, service, and network slice-based measurements supporting MDT reporting, according to various aspects of this disclosure, is shown. Operation of method 2200 can be implemented by base station 105 or its components as described herein. For example, operation of method 2200 can be implemented by, as referred to... Figures 10 to 13 The described communication manager is used to execute this. In some examples, the base station may execute a set of instructions to control the functional units of the base station to perform the functions described herein. Alternatively or concurrently, the base station may use dedicated hardware to perform aspects of the functions described herein.

[0321] At 2205, the base station may send a first measurement configuration received from the OAM interface to the UE for performing one or more QoE measurements at the UE. This first measurement configuration differs from application- or service-specific measurement configurations, wherein the first measurement configuration will be used to indicate the start of an application or service as a triggering event for initiating one or more QoE measurements at the UE. Operation 2205 can be performed according to the methods described herein. In some examples, aspects of operation 2205 may be derived from, as referenced... Figures 10 to 13 The described measurement configuration is used to perform the transmitter.

[0322] At 2210, the base station can receive one or more QoE measurements from the UE in the measurement report. The operation of 2210 can be performed according to the methods described herein. In some examples, aspects of the operation of 2210 can be derived from, as referenced... Figures 10 to 13 The QoS measurement receiver described is used to perform the measurement.

[0323] The following provides a summary of various aspects of this disclosure:

[0324] Aspect 1: A method for wireless communication at a UE, comprising: receiving from an OAM interface a measurement configuration for performing MDT measurements to be included in an MDT report; identifying one or more triggering events from the measurement configuration, the one or more triggering events triggering the MDT measurement when they occur; detecting at the UE the start of an application or service, wherein the start of the application or service is one of the one or more triggering events; obtaining the MDT measurement based at least in part on the fact that the start of the application or service is one of the one or more triggering events; and sending the MDT report including the MDT measurement to a TCE.

[0325] Aspect 2: The method according to aspect 1 further includes: identifying one or more application or service IDs associated with the application or service; comparing the one or more application or service IDs with a list of IDs stored at the UE, wherein the list of IDs includes IDs of the application or service associated with the one or more triggering events; and determining, at least in part, based on the comparison, that the one or more application or service IDs are included in the list of IDs stored at the UE.

[0326] Aspect 3: The method according to aspect 2 further includes: generating an MDT report to include the one or more application or service IDs, at least in part based on determining that the one or more application or service IDs are included in the ID list stored at the UE.

[0327] Aspect 4: The method according to any one of Aspects 2 or 3, wherein obtaining the MDT measurement further includes: obtaining RRM measurement to be included in the MDT report based at least in part on determining that the one or more application or service IDs are included in the ID list stored at the UE.

[0328] Aspect 5: The method according to any one of Aspects 2 to 4, wherein the RRM measurement includes at least one of RSRP measurement or RSRQ measurement.

[0329] Aspect 6: The method according to any one of Aspects 2 to 5, wherein the RRM measurement includes periodic measurement, event-triggered measurement, or a combination thereof.

[0330] Aspect 7: The method according to any one of Aspects 1 to 6, wherein obtaining the MDT measurement further includes: obtaining one or more location measurements at least in part based on the start trigger of the application or service, to obtain the one or more location measurements for inclusion in the MDT report.

[0331] Aspect 8: According to the method of aspect 7, obtaining the one or more positioning measurements further includes: obtaining the positioning measurements as one or more RSSI measurements or RTT measurements, wherein the positioning measurements are associated with public location information, wireless LAN location information, Bluetooth location information, sensor information, or any combination thereof.

[0332] Aspect 9: The method according to any one of Aspects 1 to 8, wherein obtaining the MDT measurement further comprises: obtaining one or more QoS measurements at least in part based on the start trigger of the application or service, to include the one or more QoS measurements in the MDT report.

[0333] Aspect 10: According to the method of aspect 9, wherein the one or more QoS measurements include one or more packet delay measurements or packet loss rate measurements.

[0334] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: receiving, in the measurement configuration, an indication that the UE should include one or more application or service IDs in the MDT report, wherein the one or more application or service IDs indicate QoS measurements of the serving base station.

[0335] Aspect 12: According to the method of aspect 11, wherein the QoS measurement of the serving base station includes data volume measurement, Internet Protocol throughput measurement, packet delay measurement, packet loss measurement, or any combination thereof.

[0336] Aspect 13: A method for wireless communication at a UE, comprising: receiving from an OAM interface a measurement configuration for performing MDT measurements to be included in an MDT report; identifying from the measurement configuration one or more reporting adjustment factors affecting at least one of a reporting interval or a reporting amount for reporting the MDT report; obtaining the MDT measurements at least in part based on the measurement configuration and according to the one or more reporting adjustment factors; and transmitting the MDT report to a TCE according to the one or more reporting adjustment factors.

[0337] Aspect 14: The method according to aspect 13 further includes: determining that the one or more reporting adjustment factors used to obtain the MDT measurement are configured for a first area specific to the UE and the serving base station, wherein the MDT measurement is obtained based on the reporting adjustment factors configured for the first area.

[0338] Aspect 15: The method according to aspect 14 further includes: identifying a second set of reporting adjustment factors specific to a second region configuration, wherein the second set of reporting adjustment factors is different from the one or more reporting adjustment factors specific to the first region configuration.

[0339] Aspect 16: The method according to any one of Aspects 13 to 15 further includes: determining that the one or more reporting adjustment factors for obtaining the MDT measurement are associated with a time of day in which the UE receives the measurement configuration; and obtaining the MDT measurement based on the reporting adjustment factors associated with the time of day.

[0340] Aspect 17: The method according to any one of Aspects 13 to 16, wherein one or more reporting adjustment factors at a first time of day are different from one or more reporting adjustment factors at a second time of day.

[0341] Aspect 18: The method according to any one of Aspects 13 to 17 further includes: identifying a first network slice among one or more network slices supporting communication between the UE and the serving base station; and determining that the first network slice is included in a network slice list, wherein the network slice list indicates network slices from which the UE and the serving base station will obtain the MDT measurement and QoE measurement, wherein the MDT measurement associated with the first network slice is obtained at least in part based on the fact that the first network slice is included in the network slice list.

[0342] Aspect 19: According to the method of aspect 18, obtaining the MDT measurement further includes: identifying one or more reporting adjustment factors associated with the first network slice and the second network slice, wherein the reporting adjustment factor associated with the first network slice is different from the reporting adjustment factor associated with the second network slice.

[0343] Aspect 20: A method for wireless communication at a UE, comprising: receiving from an OAM interface a first measurement configuration for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application- or service-specific measurement configuration; detecting the start of an application or service at the UE, wherein the start of the application or service is a triggering event for initiating the one or more QoE measurements at the UE; performing the one or more QoE measurements at the UE according to the first measurement configuration; and sending the one or more QoE measurements to a serving base station in a measurement report.

[0344] Aspect 21: The method according to aspect 20 further includes: identifying one or more application or service IDs associated with the application or service; comparing the identified one or more application or service IDs with a list of IDs stored at the UE, wherein the list of IDs includes IDs of the application or service associated with the one or more triggering events; and determining, at least in part, that the one or more application or service IDs are included in the list of IDs stored at the UE, wherein the one or more QoE measurements are performed, at least in part, based on the determination according to the first measurement configuration.

[0345] Aspect 22: The method according to any one of Aspects 20 or 21, wherein performing the one or more QoE measurements at the UE according to the first measurement configuration comprises: verifying at the UE that the triggering event for initiating the one or more QoE measurements at the UE is not associated with the application- or service-specific measurement configuration, wherein the one or more QoE measurements are performed at least in part based on the verification according to the first measurement configuration.

[0346] Aspect 23: The method according to any one of Aspects 20 to 22 further includes: determining that the first measurement configuration includes a default measurement configuration for performing the one or more QoE measurements at the UE.

[0347] Aspect 24: The method according to any one of Aspects 20 to 23 further includes: receiving a second measurement configuration, the second measurement configuration including an application- or service-specific measurement configuration for performing a QoE measurement specific to one or more designated applications or services at the UE; and performing the QoE measurement at the UE according to the second measurement configuration, at least in part based on the detection of the start of the one or more designated applications or services at the UE.

[0348] Aspect 25: The method according to any one of Aspects 20 to 24, wherein the one or more QoE measurements include application layer throughput measurement, RTT, jitter metric, packet drop rate, or any combination thereof.

[0349] Aspect 26: The method according to any one of aspects 20 to 22 further includes: receiving the first measurement configuration when establishing an RRC connection with the serving base station.

[0350] Aspect 27: A method for wireless communication at a serving base station, comprising: sending to a UE a measurement configuration received from an OAM interface for performing MDT measurements to be included in an MDT report, the measurement configuration indicating one or more triggering events, the one or more triggering events including the start of an application or service at the UE, the application or service triggering the MDT measurements at the UE when it occurs; and receiving from the UE the MDT report including the MDT measurements.

[0351] Aspect 28: The method according to aspect 27 further includes: identifying one or more application or service IDs associated with the application or service, wherein the one or more application or service IDs are included in a list of IDs stored at the UE and associated with the one or more triggering events at the UE.

[0352] Aspect 29: The method of claim 28 further comprises: receiving an MDT report, at least in part, based on the fact that the one or more application or service IDs are included in the ID list stored at the UE, the MDT report including the one or more application or service IDs.

[0353] Aspect 30: The method according to any one of Aspects 28 or 29, wherein obtaining the MDT measurement further includes: receiving the RRM measurement in the MDT report based at least in part on determining that the one or more application or service IDs are included in the ID list stored at the UE.

[0354] Aspect 31: The method according to aspect 30, wherein the RRM measurement includes at least one of RSRP measurement or RSRQ measurement.

[0355] Aspect 32: The method according to any one of Aspects 30 or 31, wherein the RRM measurement includes periodic measurement, event-triggered measurement, or a combination thereof.

[0356] Aspect 33: The method according to any one of Aspects 27 to 32, wherein receiving the MDT measurement further comprises: receiving the one or more location measurements in the MDT report by obtaining one or more location measurements at the UE based at least in part on the start trigger of the application or service.

[0357] Aspect 34: According to the method of aspect 33, receiving the one or more positioning measurements further includes: receiving the positioning measurements as one or more RSSI measurements or RTT measurements, wherein the positioning measurements are associated with public location information, wireless LAN location information, Bluetooth location information, sensor information, or any combination thereof.

[0358] Aspect 35: The method according to any one of Aspects 27 to 34, wherein receiving the MDT measurement further comprises: receiving the one or more QoS measurements at least in part based on the start trigger of the application or service to obtain one or more QoS measurements included in the MDT report.

[0359] Aspect 36: According to the method of aspect 35, wherein the one or more QoS measurements include one or more packet delay measurements or packet loss rate measurements.

[0360] Aspect 37: The method according to any one of Aspects 27 to 36 further includes: measuring one or more QoS metrics based at least in part on the one or more application or service IDs received in the MDT report.

[0361] Aspect 38: According to the method of aspect 37, the QoS measurement of the serving base station includes data volume measurement, Internet Protocol throughput measurement, packet delay measurement, packet loss measurement, or any combination thereof.

[0362] Aspect 39: A method for wireless communication at a serving base station, comprising: transmitting to a UE a measurement configuration received from an OAM interface for performing MDT measurements to be included in an MDT report, the measurement configuration including one or more reporting adjustment factors affecting at least one of a reporting interval or a reporting amount for reporting the MDT report; and receiving the MDT report from the UE according to the one or more reporting adjustment factors.

[0363] Aspect 40: The method according to aspect 39 further includes: assigning one or more reporting adjustment factors for obtaining the MDT measurement by the UE to a first area configuration common to the UE and the serving base station, wherein the MDT measurement is at least partially based on the reporting adjustment factors specific to the first area configuration.

[0364] Aspect 41: The method according to aspect 40 further includes: allocating a second set of reporting adjustment factors specific to a second region configuration, wherein the second set of reporting adjustment factors is different from the one or more reporting adjustment factors specific to the first region configuration.

[0365] Aspect 42: The method according to any one of aspects 39 to 41 further includes: determining that the one or more reporting adjustment factors for obtaining the MDT measurement will be associated with a time of day in which the serving base station transmits the measurement configuration; and receiving the MDT measurement according to the reporting adjustment factors associated with the time of day.

[0366] Aspect 43: The method according to any one of Aspects 39 to 42, wherein one or more reporting adjustment factors at a first time of day are different from one or more reporting adjustment factors at a second time of day.

[0367] Aspect 44: The method according to any one of aspects 39 to 43 further includes: identifying a first network slice among one or more network slices supporting communication between the UE and the serving base station; and determining that the first network slice is included in a network slice list, wherein the network slice list indicates network slices identified by the serving base station for the UE to obtain the MDT measurement, wherein the MDT measurement associated with the first network slice is at least partially based on the fact that the first network slice is included in the network slice list.

[0368] Aspect 45: According to the method of aspect 44, receiving the MDT measurement further includes: assigning one or more reporting adjustment factors associated with the first network slice and the second network slice, wherein the reporting adjustment factor associated with the first network slice is different from the reporting adjustment factor associated with the second network slice.

[0369] Aspect 46: A method for wireless communication at a serving base station, comprising: sending to a UE a first measurement configuration received from an OAM interface for performing one or more QoE measurements at the UE, the first measurement configuration being different from an application- or service-specific measurement configuration, wherein the first measurement configuration indicates a triggering event for initiating the one or more QoE measurements at the UE as the start of the application or service; and receiving the one or more QoS measurements from the UE in the measurement report.

[0370] Aspect 47: The method according to aspect 46 further includes: identifying one or more application or service IDs associated with the application or service, wherein the one or more application or service IDs are included in a list of IDs stored at the UE and associated with the one or more triggering events at the UE.

[0371] Aspect 48: The method according to any one of Aspects 46 or 47, wherein receiving the one or more QoE measurements further comprises: verifying that the triggering event for initiating the one or more QoE measurements at the UE is not associated with the application- or service-specific measurement configuration, wherein the one or more QoE measurements are received at least in part based on the verification according to the second measurement configuration.

[0372] Aspect 49: The method according to any one of aspects 46 to 48 further includes: determining that the first measurement configuration includes a default measurement configuration for performing the one or more QoE measurements at the UE.

[0373] Aspect 50: The method according to any one of Aspects 46 to 49 further includes: transmitting a second measurement configuration received from the OAM, the second measurement configuration including a UE-specific measurement configuration for QoE measurements of one or more designated applications or services specific to the UE; and receiving the QoE measurements from the UE according to the second measurement configuration, at least in part based on the start of one or more designated applications or services at the UE.

[0374] Aspect 51: The method according to any one of Aspects 46 to 50, wherein the one or more QoE measurements include application layer throughput measurement, RTT, jitter metric, packet drop rate, or any combination thereof.

[0375] Aspect 52: The method according to any one of aspects 46 to 51 further includes: sending the first measurement configuration when establishing an RRC connection with the UE.

[0376] Aspect 53: An apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 1 to 12.

[0377] Aspect 54: An apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 13 to 19.

[0378] Aspect 55: An apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 20 to 26.

[0379] Aspect 56: An apparatus comprising at least one unit for performing the method according to any one of aspects 1 to 12.

[0380] Aspect 57: An apparatus comprising at least one unit for performing the method according to any one of aspects 13 to 19.

[0381] Aspect 58: An apparatus comprising at least one unit for performing the method according to any one of aspects 20 to 26.

[0382] Aspect 59: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 12.

[0383] Aspect 60: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method according to any one of aspects 13 to 19.

[0384] Aspect 61: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by a processor to perform a method according to any one of aspects 20 to 26.

[0385] Aspect 62: An apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 27 to 38.

[0386] Aspect 63: An apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 39 to 45.

[0387] Aspect 64: An apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 46 to 52.

[0388] Aspect 65: An apparatus comprising at least one unit for performing the method according to any one of aspects 27 to 38.

[0389] Aspect 66: An apparatus comprising at least one unit for performing the method according to any one of aspects 39 to 45.

[0390] Aspect 67: An apparatus comprising at least one unit for performing the method according to any one of aspects 46 to 52.

[0391] Aspect 68: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by a processor to perform a method according to any one of Aspects 27 to 38.

[0392] Aspect 69: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by a processor to perform a method according to any one of aspects 39 to 45.

[0393] Aspect 70: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform a method according to any one of aspects 46 to 52.

[0394] Aspect 71: A method for wireless communication at a serving base station, comprising: sending to a UE a first measurement configuration received from an OAM interface for performing MDT measurements to be included in an MDT report, and a second measurement configuration received from the OAM interface for performing QoE measurements at the UE, the second measurement configuration being different from an application- or service-specific measurement configuration, wherein the first measurement configuration or the second measurement configuration indicates one or more triggering events, the one or more triggering events including the start of an application or service at the UE, the application or service triggering the MDT measurement or the QoE measurement, or any combination thereof, at the UE when it occurs; and receiving from the UE the MDT report including the MDT measurement or the measurement report including one or more QoE measurements, or any combination thereof.

[0395] Aspect 72: The method according to aspect 71 further includes: identifying one or more application or service IDs associated with the application or service, wherein the one or more application or service IDs are included in a list of IDs stored at the UE and associated with the one or more triggering events at the UE.

[0396] Aspect 73: The method according to any one of Aspects 71 and 72, wherein receiving the MDT measurement further comprises: receiving one or more location measurements at the UE based at least in part on the start trigger of the application or service to receive one or more location measurements in the MDT report.

[0397] Aspect 74: The method according to any one of aspects 71 to 73, wherein receiving the MDT measurement further comprises: receiving the one or more QoS measurements at least in part based on the start trigger of the application or service to obtain one or more QoS measurements included in the MDT report.

[0398] Aspect 75: The method according to any one of Aspects 71 to 74, wherein receiving the one or more QoE measurements further comprises: verifying that the triggering event for initiating the one or more QoE measurements at the UE is not associated with the application- or service-specific measurement configuration, wherein the one or more QoE measurements are received at least in part based on the verification according to the second measurement configuration.

[0399] Aspect 76: The method according to any one of aspects 71 to 75 further includes: determining that the second measurement configuration includes a default measurement configuration for performing the one or more QoE measurements at the UE.

[0400] Aspect 77: The method according to any one of aspects 71 to 76 further includes: transmitting a third measurement configuration received from the OAM, the third measurement configuration including a UE-specific measurement configuration for QoE measurements of one or more designated applications or services specific to the UE; and receiving the QoE measurement from the UE according to the third measurement configuration, at least in part based on the start of one or more designated applications or services at the UE.

[0401] Aspect 78: The method according to any one of aspects 71 to 77, wherein the one or more QoE measurements include application layer throughput measurement, RTT, jitter metric, packet drop rate, or any combination thereof.

[0402] Aspect 79: An apparatus for wireless communication at a serving base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 71 to 78.

[0403] Aspect 80: An apparatus for wireless communication at a serving base station, comprising at least one unit for performing the method according to any one of aspects 71 to 78.

[0404] Aspect 81: A non-transitory computer-readable medium storing code for wireless communication at a serving base station, the code comprising instructions executable by a processor to perform a method according to any one of aspects 71 to 78.

[0405] Aspect 82: A method for wireless communication at a UE, comprising: receiving a measurement configuration from an OAM interface, the measurement configuration for performing MDT measurements to be included in an MDT report and performing QoE measurements to be included in a QoE report; identifying one or more triggering events from the measurement configuration, the one or more triggering events triggering the MDT measurements and the QoE measurements when they occur; detecting the start of an application or service at the UE, wherein the start of the application or service is one of the one or more triggering events; sending an indication to a serving base station that the one or more triggering events have occurred; obtaining the MDT measurements and the QoE measurements based at least in part on the fact that the start of the application or service is one of the one or more triggering events; and sending the MDT report and the QoE report, including the MDT measurements and the QoE measurements, to a server.

[0406] Aspect 83: The method according to aspect 82 further includes: identifying one or more application or service IDs associated with the application or service; comparing the one or more application or service IDs with a list of IDs stored at the UE, wherein the list of IDs includes IDs of the application or service associated with the one or more triggering events; and determining, at least in part, based on the comparison, that the one or more application or service IDs are included in the list of IDs stored at the UE.

[0407] Aspect 84: The method according to aspect 83 further includes: generating the MDT report and the QoE report to include the one or more application or service IDs, at least in part based on determining that the one or more application or service IDs are included in the ID list stored at the UE.

[0408] Aspect 85: The method according to any one of Aspects 83 to 84, wherein obtaining the minimized drive test measurement further comprises: obtaining RRM measurements to be included in the MDT report based at least in part on determining that the one or more application or service IDs are included in the ID list stored at the UE.

[0409] Aspect 86: The method according to aspect 85, wherein the RRM measurement includes at least one of RSRP measurement or RSRQ measurement.

[0410] Aspect 86: The method according to any one of aspects 85 to 86, wherein the RRM measurement includes periodic measurement, event-triggered measurement, or any combination thereof.

[0411] Aspect 88: The method according to any one of Aspects 82 to 87, wherein obtaining the minimized drive test measurements further comprises: obtaining one or more location measurements at least in part based on the start trigger of the application or the service, to obtain the one or more location measurements for inclusion in the MDT report.

[0412] Aspect 89: According to the method of aspect 88, obtaining the one or more positioning measurements further includes: obtaining the positioning measurements as one or more RSSI measurements or RTT measurements, wherein the positioning measurements are associated with public location information, wireless LAN location information, Bluetooth location information, sensor information, or any combination thereof.

[0413] Aspect 90: The method according to any one of Aspects 82 to 89, wherein obtaining the minimized drive test measurement further comprises: obtaining one or more QoS measurements at least in part based on the start trigger of the application or the service, to include the one or more QoS measurements in the MDT report.

[0414] Aspect 91: According to the method of aspect 90, wherein the one or more QoS measurements include one or more packet delay measurements or packet loss rate measurements.

[0415] Aspect 92: The method according to any one of aspects 82 to 91 further includes: receiving, in the measurement configuration, an indication that the UE should include one or more application or service identifiers in the MDT report, wherein the one or more application or service identifiers indicate QoS measurements of the serving base station.

[0416] Aspect 93: According to the method of aspect 92, wherein the QoS measurement of the serving base station includes data volume measurement, Internet Protocol throughput measurement, packet delay measurement, packet loss measurement, or any combination thereof.

[0417] Aspect 94: An apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 82 to 93.

[0418] Aspect 95: An apparatus comprising at least one unit for performing the method according to any one of aspects 82 to 93.

[0419] Aspect 96: A non-transitory computer-readable medium storing code, said code comprising instructions executable by a processor to perform the method according to any one of aspects 82 to 93.

[0420] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0421] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in much of the description, the techniques described herein apply beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0422] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0423] The various illustrative blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of digital signal processing (DSP) and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0424] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions can be stored as one or more instructions or code on or transmitted through a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including being distributed such that different parts of the functions are implemented in different physical locations.

[0425] Computer-readable media includes both non-transitory computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium accessible by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired units of program code in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically copy data magnetically, while optical discs use lasers to copy data optically. The combinations described above are also included within the scope of computer-readable media.

[0426] As used herein (including in the claims), the word "or" in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same way as the phrase "at least partially based on".

[0427] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by a dash and a second reference numeral following the reference numeral, used to differentiate between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, without regard to the second reference numeral or other subsequent reference numerals.

[0428] This document describes exemplary configurations in conjunction with the accompanying drawings, and does not represent all examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be implemented without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0429] The description herein is provided to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is to be given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication, comprising: One or more processors; A memory coupled to the one or more processors; as well as Instructions, stored in the memory and executable by the one or more processors, to cause the device to perform the following operations: Receive the measurement configuration for performing experience quality measurements to be included in the experience quality report; The experience quality measurement is obtained at least in part based on the start of the service that triggers the experience quality measurement; Send an instruction to the serving network device to initiate the service; Minimum drive test measurements are obtained to be included in the minimum drive test report, at least in part based on the start of the service triggering the quality of experience measurement, wherein obtaining the minimum drive test measurements includes obtaining one or more received signal strength indicator measurements, one or more round-trip time measurements, or a combination thereof; as well as Send the quality of experience report and the minimized drive test report to the service network device.

2. The apparatus according to claim 1, wherein, Receiving the measurement configuration includes: Receive the measurement configuration indicating one or more services, which trigger the experience quality measurement upon initiation, and the one or more services include the service.

3. The apparatus according to claim 1, wherein, Receiving the measurement configuration includes: The measurement configuration is received via radio resource control signaling.

4. The apparatus according to claim 1, wherein, The experience quality report is used for application layer experience quality verification.

5. The apparatus according to claim 1, wherein, Obtaining the minimized road test measurements includes: When operating in Radio Resource Control (RRC) connection state, immediate minimized drive test measurements are obtained.

6. The apparatus according to claim 1, wherein, The one or more received signal strength indicator measurements, the one or more round-trip time measurements, or a combination thereof, are associated with wireless local area network information.

7. The apparatus according to claim 1, wherein, The experience quality report includes a service identifier (ID) corresponding to the service.

8. The apparatus according to claim 1, wherein, The quality of experience measurements include application layer throughput measurements, round-trip time measurements, jitter metrics, packet drop rate, or any combination thereof.

9. The apparatus according to claim 1, wherein, Obtaining the minimized road test measurements includes: Radio resource management measurements are obtained, at least in part, based on the start of the service triggering the experience quality measurement.

10. The apparatus according to claim 9, wherein, The radio resource management measurements include at least one of a reference signal received power measurement or a reference signal received quality measurement.

11. The apparatus according to claim 1, wherein, Obtaining the aforementioned experience quality measurement includes: One or more service quality measurements are obtained, at least in part, based on the start of the service triggering the experience quality measurement.

12. The apparatus according to claim 1, wherein, Receiving the measurement configuration includes: The measurement configuration is received from the Operation, Administration and Maintenance (OAM) interface.

13. An apparatus for wireless communication, comprising: One or more processors; A memory coupled to the one or more processors; as well as Instructions, stored in the memory and executable by the one or more processors, to cause the device to perform the following operations: The output is used to perform experience quality measurements to include the measurement configuration in the experience quality report; The indication to begin the service is obtained, at least in part, based on sending the measurement configuration; as well as Obtain the Quality of Experience report and a Minimized Drive Test report including minimized drive test measurements, wherein receiving the minimized drive test measurements includes receiving one or more received signal strength indicator measurements, one or more round-trip time measurements, or a combination thereof.

14. The apparatus of claim 13, further comprising: The experience quality report and the minimized road test report are output to the tracking and collection entity.

15. The apparatus according to claim 13, wherein, The output of the measurement configuration includes: The output indicates the measurement configuration of one or more services, which trigger the quality of experience measurement when initiated, and the one or more services include the service.

16. The apparatus according to claim 13, wherein, The output of the measurement configuration includes: The measurement configuration is output via radio resource control signaling.

17. The apparatus according to claim 13, wherein, The experience quality report is used for application layer experience quality verification.

18. The apparatus according to claim 13, wherein, The one or more received signal strength indicator measurements, the one or more round-trip time measurements, or a combination thereof, are associated with wireless local area network information.

19. The apparatus according to claim 13, wherein, The experience quality report includes a service identifier (ID) corresponding to the service.

20. A method for conducting wireless communication at a user equipment (UE), comprising: Receive the measurement configuration for performing experience quality measurements to be included in the experience quality report; The experience quality measurement is obtained at least in part based on the start of the service that triggers the experience quality measurement; Send an instruction to the serving network device to initiate the service; Minimum drive test measurements are obtained to be included in the minimum drive test report, at least in part based on the start of the service triggering the quality of experience measurement, wherein obtaining the minimum drive test measurements includes obtaining one or more received signal strength indicator measurements, one or more round-trip time measurements, or a combination thereof; as well as Send the quality of experience report and the minimized drive test report to the service network device.

Images