Method and apparatus for measurement report in mobile communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. The present disclosure can be applied to intelligent services (for example, smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security- and safety-related services, and the like) on the basis of 5G communication technology and IoT-related technology. More specifically, a method provided in the present disclosure comprises the steps of: receiving, from a base station, a configuration message including first configuration information related to a cell measurement report and second configuration information related to a quality of experience (QoE) measurement report, the first configuration information including information about an event in which the cell measurement report is triggered; and transmitting, to the base station, a measurement report message on the basis of the first configuration information and the second configuration information, wherein, if the event in which the cell measurement report is triggered is detected, the measurement report message includes the cell measurement report and a QoE measurement report.

Description

Method and device for measurement reporting in mobile communication systems

[0001] The present disclosure relates to a mobile communication system, and more particularly, to a method and device for Quality of Experience (QoE) measurement and radio measurement in a next-generation mobile communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The disclosed embodiment seeks to provide a method and device capable of effectively providing a service in a wireless communication system.

[0009] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0010] A method performed by a terminal in a wireless communication system, the method comprising: receiving, from a base station, a configuration message including first configuration information related to a cell measurement report and second configuration information related to a quality of experience (QoE) measurement report, the first configuration information including information about an event that triggers the cell measurement report; and transmitting, to the base station, a measurement report message based on the first configuration information and the second configuration information, wherein, when an event that triggers the cell measurement report is detected, the measurement report message may include the cell measurement report and the QoE measurement report.

[0011] A method performed by a base station in a wireless communication system, the method comprising: transmitting, from a terminal, a configuration message including first configuration information related to a cell measurement report and second configuration information related to a quality of experience (QoE) measurement report, the first configuration information including information about an event that triggers the cell measurement report; and receiving, from the terminal, a measurement report message based on the first configuration information and the second configuration information, wherein, when an event that triggers the cell measurement report is detected, the measurement report message may include the cell measurement report and the QoE measurement report.

[0012] In a wireless communication system, a terminal comprises: a transceiver; and a controller connected to the transceiver, wherein the controller receives, from a base station, a configuration message including first configuration information related to a cell measurement report and second configuration information related to a QoE (quality of experience) measurement report, wherein the first configuration information includes information about an event that triggers the cell measurement report, and transmits a measurement report message to the base station based on the first configuration information and the second configuration information, wherein when an event that triggers the cell measurement report is detected, the measurement report message may include the cell measurement report and the QoE measurement report.

[0013] In a wireless communication system, a base station comprises: a transceiver; and a controller connected to the transceiver, wherein the controller transmits, from a terminal, a configuration message including first configuration information related to a cell measurement report and second configuration information related to a quality of experience (QoE) measurement report, wherein the first configuration information includes information about an event that triggers the cell measurement report; and receives, from the terminal, a measurement report message based on the first configuration information and the second configuration information, wherein when an event that triggers the cell measurement report is detected, the measurement report message may include the cell measurement report and the QoE measurement report.

[0014] The disclosed embodiment provides a device and method capable of effectively providing a service in a wireless communication system.

[0015] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0016] FIG. 1 is a diagram illustrating the structure of a mobile communication system according to one embodiment of the present disclosure.

[0017] FIG. 2 is a diagram for explaining a wireless connection state transition in a mobile communication system according to one embodiment of the present disclosure.

[0018] FIG. 3 is a flowchart illustrating a procedure for setting / reporting signaling-based QoE measurement according to one embodiment of the present disclosure.

[0019] FIG. 4 is a flowchart illustrating a procedure for setting / reporting management-based QoE measurement according to one embodiment of the present disclosure.

[0020] FIG. 5 is a flowchart illustrating a setup and reporting procedure for RAN visible QoE measurement according to one embodiment of the present disclosure.

[0021] FIG. 6 is a flowchart illustrating a process in which a terminal performs cell measurement and reporting operations according to one embodiment of the present disclosure.

[0022] FIG. 7 is a diagram for explaining an operation of a terminal reporting cell measurement results based on a reporting condition of cell measurement results according to one embodiment of the present disclosure.

[0023] FIG. 8 is a block diagram illustrating the internal structure of a terminal applied to embodiments of the present disclosure.

[0024] FIG. 9 is a block diagram illustrating the structure of a base station applied to embodiments of the present disclosure.

[0025] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.

[0026] In describing the embodiments of this disclosure, descriptions of technical details that are well known in the technical field to which this disclosure pertains and are not directly related to this disclosure will be omitted. This is to ensure that the gist of this disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.

[0027] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0028] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the present disclosure.

[0029] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0030] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0031] Here, the term '~ unit' used in the embodiments of the present disclosure means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.

[0032] Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel form to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

[0033] In the following description, terms used to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0034] For convenience of explanation, some terms and names defined in the 3rd generation partnership project long-term evolution (3GPP) standards may be used. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0035] In the following description of the present invention, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.

[0036] FIG. 1 is a diagram illustrating the structure of a mobile communication system according to one embodiment of the present disclosure.

[0037] Referring to FIG. 1, a wireless access network of a mobile communication system (New Radio, NR) according to an embodiment of the present disclosure is composed of a base station (New Radio Node B, hereinafter referred to as gNB) (110) and an AMF (105, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter referred to as NR UE or 0) (115) accesses an external network through the gNB (110) and the AMF (105). The mobile communication system according to an embodiment of the present disclosure may be a next-generation mobile communication system, and the base station may be a next-generation base station.

[0038] In Fig. 1, the gNB corresponds to the eNB (Evolved Node B) of the existing LTE system. The gNB is connected to the NR UE via a wireless channel and can provide a service superior to that of the existing Node B (120). In the next-generation mobile communication system according to an embodiment of the present disclosure, since all user traffic is serviced through a shared channel, a device that collects status information such as the buffer status of UEs, available transmission power status, and channel status and performs scheduling is required, and this is handled by the gNB (110). One gNB typically controls multiple cells. In order to implement ultra-high-speed data transmission compared to the existing LTE, it can have a bandwidth higher than the existing maximum, and beamforming technology can be additionally grafted using the orthogonal frequency division multiplexing (OFDM) as a wireless access technology. In addition, the adaptive modulation and coding (AMC) method that determines the modulation scheme and channel coding rate according to the channel status of the terminal is applied.

[0039] The AMF (105) performs functions such as mobility support, bearer setup, and QoS setup. The AMF is a device that handles various control functions as well as mobility management functions for terminals and is connected to multiple base stations. In addition, the mobile communication system according to one embodiment of the present disclosure can be interoperable with an existing LTE system, and the AMF is connected to the MME (125) via a network interface. The MME is connected to an existing base station, an eNB (130). A terminal that supports LTE-NR Dual Connectivity can transmit and receive data while maintaining a connection to both the gNB and the eNB (135).

[0040] FIG. 2 is a diagram for explaining a wireless connection state transition in a mobile communication system according to one embodiment of the present disclosure.

[0041] A mobile communication system according to an embodiment of the present disclosure has three radio resource control (RRC) states. The connected mode (RRC_CONNECTED, 205) is a radio connection state in which a terminal can transmit and receive data. The idle mode (RRC_IDLE, 230) is a radio connection state in which a terminal monitors whether a paging is transmitted to it. The above two modes are radio connection states that are also applied to the existing LTE system, and the detailed technology is the same as that of the existing LTE system. The mobile communication system according to an embodiment of the present disclosure may be a next-generation mobile communication system.

[0042] In a mobile communication system according to one embodiment of the present disclosure, a new inactive (RRC_INACTIVE) radio connection state (215) is defined. In this radio connection state, UE context is maintained between the base station and the terminal, and RAN (radio access network)-based paging is supported. The characteristics of this new radio connection state are listed below.

[0043] - Cell re-selection mobility;

[0044] - CN - NR RAN connection (both C / U-planes) has been established for UE;

[0045] - The UE AS context is stored in at least one gNB and the UE;

[0046] - Paging is initiated by NR RAN;

[0047] - RAN-based notification area is managed by NR RAN;

[0048] - NR RAN knows the RAN-based notification area which the UE belongs to;

[0049] According to one embodiment of the present disclosure, an INACTIVE wireless connection state can transition to a connected mode or a standby mode using a specific procedure. The INACTIVE mode is switched to a connected mode through a Resume procedure, and the connected mode is switched to an INACTIVE mode through a Release procedure including suspend configuration information (210). The procedure is performed by transmitting and receiving one or more RRC messages between a terminal and a base station, and consists of one or more steps. In addition, a transition from INACTIVE mode to a standby mode is possible through a Release procedure after Resume (220). The transition between the connected mode and the standby mode follows the existing LTE technology. That is, the transition between the modes is performed through an establishment or release procedure (225).

[0050] FIG. 3 is a flowchart illustrating a procedure for setting / reporting signaling-based quality of experience (QoE) measurement according to one embodiment of the present disclosure.

[0051] Referring to FIG. 3, according to one embodiment of the present disclosure, an AS (Access Stratum, 305) of a terminal may transmit information (e.g., qoe-Streaming-MeasReport, qoe-MTSI-MeasReport, qoe-VR-MeasReport) indicating whether quality of experience (QoE) measurement is supported by service type (e.g., streaming, MTSI, VR) to a base station (or NG-RAN, 315) via a UE capability message (e.g., UECapabilityInformation) (310). Before the terminal transmits the UE capability message, the base station may transmit a message (e.g., UECapabilityEnquiry) to the terminal for requesting the UE capability message. In addition, the terminal can report to the base station whether it supports RAN visible QoE measurement by service type (e.g., streaming, VR) through the UE capability message (e.g., ran-VisibleQoE-Streaming-MeasReport, ran-VisibleQoE-VR-MeasReport). In addition, the terminal can report to the base station whether it supports UL RRC segmentation for QoE report message (e.g., ul-MeasurementReportAppLayer-Seg) through the UE capability message. The UE capability message includes ASN.1 information as shown in Table 1 below, and the description of related parameters is as shown in Table 2 below.

[0052]

[0053]

[0054] The types of services that can be supported in LTE may include Streaming and MTSI (Multimedia Telephony Service for IMS (IP Multimedia Subsystem)), and in the case of NR, in addition to the types of services that can be supported in LTE, it was defined in Rel-17 that VR (Virtual Reality) service is additionally supported, and it was defined that services such as MBMS (Multimedia Broadcast Multicast Services) and XR (Extended Reality) may be additionally supported in future releases.

[0055] According to one embodiment of the present disclosure, an Operations Administration and Maintenance (OAM) 320 can provide QoE measurement configuration information to a Core Network (CN) 325 (330). The CN (325) that has received the configuration information can activate QoE measurement by transmitting the configuration information to a base station (315) (335).

[0056] According to one embodiment of the present disclosure, the base station (315) that has received configuration information from the CN (325) may transmit QoE configuration information to the AS (305) of the terminal via an RRC message (e.g., an RRCReconfiguration or RRCResume message) (340). The RRC message may include an IE (APPLayerMeasConfig) as in Table 3 below, and the description of the related parameters is as in Table 4 below.

[0057]

[0058]

[0059]

[0060] In addition, according to one embodiment of the present disclosure, the operation of a terminal AS (305) that receives QoE setting information from a base station through an RRC message may be as described in Table 5 below.

[0061]

[0062]

[0063] As described above, for the QoE measurement settings included in measConfigAppLayerToAddModList, the AS layer (305) of the terminal may transmit part or all of the configuration information to the upper layer or application layer (UE APP, 345) of the terminal via an AT Command (350). In addition, the AS layer (305) of the terminal may send an AT Command to the APP (345) of the terminal to instruct / command to delete the stored configuration information for the QoE measurement settings included in measConfigAppLayerToAddReleaseList.

[0064] According to one embodiment of the present disclosure, the terminal APP (345) can perform QoE measurement according to the received configuration information. In addition, the terminal APP (345) can report the results of the measurement according to the configuration information to the terminal AS (305) via an AT command (355).

[0065] According to one embodiment of the present disclosure, a terminal AS (305) that has received a measurement result report from a terminal APP can report the measurement result to a base station (315) via an RRC message (e.g., a MeasurementReportAppLayer message) (360). SRB (signaling radio bearer) 4 can be used to report the QoE measurement result. The MeasurementReportAppLayer message can include ASN.1 information as in Table 6 below, and the description of the related parameters is as in Table 7 below.

[0066]

[0067]

[0068]

[0069]

[0070] Additionally, according to one embodiment of the present disclosure, a specific procedure of a terminal AS reporting the measurement result may follow the operations described in Table 8 below.

[0071]

[0072]

[0073] According to one embodiment of the present disclosure, the base station (315) can transmit the measurement result report received from the terminal to the final server (TCE (trace collection entity) or MCE (measurement collection entity), 365) that collects the measurement report (370).

[0074] FIG. 4 is a flowchart illustrating a procedure for setting / reporting management-based QoE measurement according to one embodiment of the present disclosure.

[0075] Among the operations performed in the management-based QoE setting / reporting procedure, operations that are identical / similar to and overlapping with the operations performed in the signaling-based QoE setting / reporting procedure described in FIG. 3 will be omitted for separate explanation, and the differences between the management-based QoE setting / reporting procedure and the signaling-based procedure will be mainly explained with reference to FIG. 4.

[0076] According to one embodiment of the present disclosure, in a method related to a Management-based QoE configuration / reporting procedure, an OAM (405) can directly transmit QoE measurement configuration to a base station (410) without going through a CN, thereby instructing the base station to activate QoE measurement of a terminal (415). The base station (410) that has received the QoE measurement configuration can search for a single or multiple terminals that meet at least one condition (e.g., area scope, application layer capability, service type). The base station (410) can transmit / forward the QoE measurement configuration to one of the single or multiple terminals searched for through an RRC message (e.g., an RRCReconfiguration message or an RRCResume) (420). Each terminal that has received the RRC message can exchange configuration and measurement results for QoE measurement between the AS layer and the APP through an AT Command between the AS layer and the APP, as described above in FIG. 3. The AS layer of the terminal reports the measurement results obtained from the APP to the base station (410) via an RRC message, and the base station (410) can transmit the results to the TCE / MCE.

[0077] FIG. 5 is a flowchart illustrating a setup and reporting procedure for RAN visible QoE measurement according to one embodiment of the present disclosure.

[0078] According to one embodiment of the present disclosure, when following the method related to the signaling-based QoE configuration / reporting procedure and the management-based QoE configuration / reporting procedure described in FIGS. 3 and 4, respectively, QoE measurement is configured by OAM, and the QoE measurement report generated according to the configuration is collected by TCE / MCE, and the QoE measurement report can be used by the operator for network optimization. Meanwhile, the base station cannot read or understand the report regarding the OAM-based QoE measurement transmitted by the terminal. More specifically, since the MeasurementReportAppLayer message includes the measurement report generated by the application layer of the terminal in the measurementReportAppLayerContainer, but is stored in the form of OCTEC STRING, the base station or the RRC layer of the base station cannot read or understand the measurement report generated by the application layer of the terminal. To address these issues, i.e., to enable base stations to read QoE measurement reports from terminals and utilize them for network optimization, such as radio resource management, RAN visible QoE (RVQoE) measurements were defined and introduced in 3GPP.

[0079] According to one embodiment of the present disclosure, RVQoE measurement may be defined to be limited to a specific service type (e.g., streaming, VR). The terminal may report to the base station whether it supports RVQoE measurement for each service type (e.g., streaming, VR) (505). At this time, the UECapabilityInformation message may be used. For example, the terminal may include or set the ran-VisibleQoE-Streaming-MeasReport parameter in the UECapabilityInformation message and transmit it to the base station for a Streaming service, and may include or set the ran-VisibleQoE-VR-MeasReport parameter in the UECapabilityInformation message and transmit it to the base station for a VR service.

[0080] According to one embodiment of the present disclosure, based on whether the terminal supports RVQoE measurement for each service type (e.g., streaming, VR) transmitted to the base station by the terminal, the base station can determine whether the terminal supports RVQoE measurement for each service type, and based on this, can generate an RVQoE measurement configuration and transmit it to the terminal (510). At this time, the RVQoE measurement configuration can be transmitted together with the OAM-based QoE measurement configuration. The RVQoE measurement configuration can be included in an RRCReconfiguration or RRCResume message. The base station can instruct the terminal to set up or release RVQoE measurement by setting or releasing the ran-VisibleParameters parameter in the AppLayerMeasConfig IE. The ran-VisibleParameters parameter can include the RAN-VisibleParameters IE, through which some or all of the parameters below can be provided from the base station to the terminal.

[0081] - RVQoE measurement report cycle (ran-VisiblePeriodicity): Terminal AS or terminal APP can transmit RVQoE measurement reports at the above cycle.

[0082] - Maximum number of reportable buffer levels (numberOfBufferLevelEntries): Terminal AS or terminal APP can include multiple buffer levels when reporting RVQoE measurements, and a number of buffer levels less than or equal to the set value of numberOfBufferLevelEntries can be included in the RVQoE measurement report.

[0083] - Whether to report playout delay at media start (reportPlayoutDelayForMediaStartup): If the value of reportPlayoutDelayForMediaStartup is indicated as true, the terminal AS or terminal APP can include the playout delay at media start in the RVQoE report and transmit it. If the value of reportPlayoutDelayForMediaStartup is indicated as false, the terminal may not include the playout delay at media start in the RVQoE report.

[0084] According to one embodiment of the present disclosure, the AS layer of the terminal can transmit configuration information such as the ran-VisiblePeriodicity described above to the APP layer of the terminal (515). At this time, the RVQoE measurement configuration can be transmitted to the APP layer together with the OAM-based QoE measurement configuration. The APP of the terminal can perform QoE measurement based on the RVQoE measurement configuration information to generate an RVQoE measurement report and transmit it to the AS layer of the terminal (520). At this time, the RVQoE measurement report can be transmitted to the AS layer together with the OAM-based QoE measurement report.

[0085] The AS layer of the terminal that has received the RVQoE measurement report can forward / transmit / report the forwarded RVQoE measurement report to the base station (525). At this time, the RVQoE measurement report can be forwarded / transmitted / reported to the base station together with the OAM-based QoE measurement report. In 525, the RVQoE measurement report can be transmitted via the RAN-VisibleMeasurements IE within the MeasurementReportAppLayer message, and the IE can include some or all of the following parameters.

[0086] - APP layer buffer level list (appLayerBufferLevelList): The terminal can include multiple buffer levels measured by the terminal APP through this parameter. The number included may be limited by numberOfBufferLevelEntries in the RVQoE settings.

[0087] - playout delay (playoutDelayForMediaStartup): The terminal can include the playout delay at the start of the media through this parameter, and can indicate this value in ms. The terminal can include this parameter in the RVQoE measurement report if reportPlayoutDelayForMediaStartup is set to true during the RVQoE configuration.

[0088] - PDU session ID list (pdu-SessionIdList): The terminal can indicate the PDU session(s) used for the application data flow that is the target of RVQoE measurement through this parameter. After receiving the RVQoE measurement report from the terminal, the base station can identify for which PDU session(s) the RVQoE values ​​(e.g., buffer level and playout delay) were measured through this parameter, and based on the identification result, can optimize resource allocation and scheduling for the PDU session(s) indicated by this parameter.

[0089] According to one embodiment of the present disclosure, a base station can read RVQoE reports and utilize them to perform network optimization. For example, if the base station determines, based on the RVQoE reports, that a specific terminal is experiencing poor QoE for a specific service, the base station can improve the QoE of the terminal determined to be experiencing poor QoE by allocating a larger amount of radio resources to the terminal determined to be experiencing poor QoE.

[0090] FIG. 6 is a flowchart illustrating a process in which a terminal performs cell measurement and reporting operations according to one embodiment of the present disclosure.

[0091] According to one embodiment of the present disclosure, a terminal (605) reports its capability information to a base station (610) (615). The base station (610) transmits an RRCReconfiguration message including configuration information (measConfig IE) related to the cell measurement operation to the terminal (605) (620).

[0092] The above configuration information (measConfig IE) includes the information necessary for the terminal to report the measurement results to the base station, depending on the type of measurement report (e.g., periodical, event-triggered, event-triggered periodical). In particular, in the case of event-triggered reporting or event-triggered periodical, the terminal can report a given measurement result when a specific event configured based on the configuration information is satisfied. For example, the following events can be configured in the NR system.

[0093] Events related to typical intra- / inter-RAT measurements are summarized in the table below.

[0094]

[0095] Similar to condition-based measurement reporting, in conditional handover, when specific events are met, the terminal can perform a handover based on conditional handover configuration information. Events related to conditional handover are summarized in Table 10 below.

[0096]

[0097] For sidelink relays, the terminal can perform certain actions when a specific event is met. Events related to relays are summarized in Table 11 below.

[0098]

[0099] Even in the case of NR-U (Unlicensed), the terminal can perform certain actions when certain events are met. Events related to NR-U are summarized in Table 12 below.

[0100]

[0101] According to one embodiment of the present disclosure, if the Events described above are continuously satisfied with a predetermined condition for a predetermined time period (time-to-trigger), the terminal may consider the Event to be satisfied.

[0102] According to one embodiment of the present disclosure, when a set condition is satisfied, the terminal (605) can report a MeasurementReport message including a measurement result to the base station (610) (630). Alternatively, the terminal performs a predetermined terminal operation corresponding to the condition, for example, a condition-based handover. The base station (610) that has received the measurement result can use the result for a predetermined purpose. For example, based on the result, the base station (610) can determine whether to handover the terminal (605) (635). If the base station (610) triggers a handover, it can request the handover to a predetermined target cell (640). In addition, the base station (610) can transmit handover configuration information configured based on predetermined configuration information received from the target cell to the terminal (605) (645). The terminal (605) that has received the configuration information can perform the handover (650).

[0103] FIG. 7 is a diagram illustrating an operation of a terminal according to one embodiment of the present disclosure to report cell measurement results when the conditions for reporting cell measurement results are satisfied. More specifically, FIG. 7 relates to an operation of a terminal according to one embodiment of the present disclosure to report cell measurement results when the conditions for reporting cell measurement results are satisfied.

[0104] According to one embodiment of the present disclosure, the terminal (710) can evaluate the signal strength or quality of the base station (705) signal based on the SSB or CSI-RS transmitted from the base station (705). Hereinafter, for convenience of explanation, the cell measurement result reporting operation of the terminal is described mainly with respect to SSB, but the same can be applied to CSI-RS. In the case of SSB, the transmission cycle of SSB is determined according to the configuration of the base station (705). Generally, the transmission cycle of SSB can be set to 20 ms, and the base station (705) can transmit SSB at a cycle of up to 160 ms. When the base station (705) sets Event A2 for the terminal (710), the terminal (710) can continuously evaluate whether the RSRP value measured based on SSB is lower than the threshold during a predetermined time period (time-to-trigger, TTT) from the time point (715) when the RSRP value measured based on SSB becomes lower than the set absolute threshold. If the RSRP value measured from the initial time point (715) when the RSRP value measured based on SSB becomes lower than the set absolute threshold until the time point (720) when the time period elapses is lower than the threshold, the terminal (710) considers that the Event A2 is satisfied and reports a measurement report triggered by Event A2 to the base station (705). The reason why the TTT is considered in determining whether the condition for performing the measurement report is satisfied may be to compensate for the variability of the measurement signal. The TTT value may be set by the base station for each set Event. If the above-mentioned Events continuously satisfy a predetermined condition for a predetermined time interval (TTT), a terminal operation corresponding to the purpose of the set Event can be performed.If the measurement-related configuration information received by the terminal is periodical or event-triggered periodical, the terminal can perform periodic measurement reporting.

[0105] In this disclosure, the measurements described in FIGS. 6 and 7 (e.g., measurements at the AS layer) may be referred to as radio measurements to distinguish them from QoE measurements (e.g., measurements at the application layer).

[0106] With the existing immediate MDT (Minimization of Drive Tests) technology, a terminal can report location information to a base station along with radio measurement results. For example, a terminal can receive an immediate MDT configuration from a base station at 620, and the terminal can measure the location information configured to be measured for the terminal's measurement report and report it to the base station along with the radio measurement results (630). The base station can transmit the (immediate) MDT measurement result to a TCE or MCE server, and can transmit it including a timestamp. The timestamp can indicate the time at which the base station received the MDT measurement result from the terminal, the time at which the base station transmitted the MDT measurement result, the time at which the base station instructed the terminal to configure the MDT, or the time at which the base station received the MDT configuration. In addition, the timestamp can be a value set depending on the network implementation.

[0107] In FIGS. 3 and 4, the base station can receive the QoE measurement report reported by the terminal and forward it to the TCE or MCE. Similar to MDT, the base station can receive the QoE measurement report from the terminal (e.g., 360), forward / transmit the received QoE measurement report to the TCE or MCE server, and can transmit the received QoE measurement report to the TCE or MCE server along with a timestamp. The timestamp can indicate the time at which the base station received the QoE measurement result from the terminal, the time at which the base station transmitted the QoE measurement result, the time at which the base station instructed the terminal to configure QoE settings, or the time at which the base station received the QoE settings. In addition, the timestamp can be a value set according to the implementation of the network.

[0108] That is, the TCE or MCE can receive the MDT measurement result (radio measurement result) and the QoE measurement result, respectively, and since each measurement result includes a timestamp, the TCE or MCE or the network operator can align the two measurement result values ​​and determine the correlation between the two measurement result values. In other words, the TCE or MCE or the network operator can determine the correlation between the measurement result of the radio side and the QoE of the application side and use it for network optimization. For example, if the radio quality measured by the terminal is poor and the QoE measurement result at the same time is poor, the network operator can try to improve the QoE quality of the terminal by first improving the radio quality of the terminal. In another example, if the radio quality measured by the terminal is good but the QoE measurement result at the same time is poor, the network operator can recognize that the problem is in an interface or layer other than the radio side (Uu interface) and perform network optimization to resolve it.

[0109] One problem that the present disclosure seeks to address is that the timestamp provided / included by the base station in the MDT measurement report or QoE measurement report may be different from the value actually measured by the terminal. In other words, the base station may not be able to accurately determine the point in time when the terminal performed the measurement. More specifically, a delay may occur between the time when the terminal performs the measurement, generates the measurement result as a message, and receives an uplink grant to transmit it to the base station. Therefore, even if the base station sets the time when it receives the measurement report from the terminal as the timestamp value, an error may occur with respect to the actual time when the terminal performed the measurement. Furthermore, the error value may not be constant for each measurement report depending on the network conditions, the scheduling of the base station, and the status of the terminal. As a result, the TCE or MCE or network operator may perform inaccurate alignment of the timestamp for the QoE measurement result indicated by the base station (e.g., a timestamp with an error of 1 from the terminal's measurement time) and the timestamp for the MDT measurement result (e.g., a timestamp with an error of 2 from the terminal's measurement time).

[0110] According to one embodiment of the present disclosure, to address the aforementioned issues, a terminal may report the measurement time at which the terminal performed the measurement to the base station when reporting QoE and MDT (radio) measurements. To achieve this, the terminal may report at least one of the following supported options to the base station via a UE capability message (e.g., UECapabilityInformation).

[0111] - Option 1. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when measuring (reporting) QoE.

[0112] - Option 2. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when measuring (reporting) MDT.

[0113] - Option 3. Whether the terminal supports the ability to provide a timestamp for the measurement point in time during QoE measurement (reporting) and MDT measurement (reporting).

[0114] - Option 4. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when measuring (reporting) QoE by service type or for a specific service type (e.g., XR or streaming).

[0115] - Option 5. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when measuring (reporting) MDT, either by service type or when receiving a service for a specific service type (e.g., XR or streaming).

[0116] - Option 6. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when performing QoE measurements and MDT measurements (reporting) by service type or for a specific service type (e.g., XR or streaming).

[0117] - Option 7. Whether the terminal supports the ability to provide a timestamp for the measurement point when measuring (reporting) QoE for each QoE metric (e.g., buffer level, initial playout delay) or for a specific QoE metric.

[0118] According to one embodiment of the present disclosure, when a terminal receives a UE capability request message (e.g., a UECapabilityEnquiry message) from a base station, the terminal may indicate to the base station that it supports a capability for at least one of the options 1 to 7 by including an indicator corresponding to the options 1 to 7 in the UE capability message when transmitting a UE capability message (e.g., a UECapabilityInformation) to the base station, or by setting a value corresponding to the options 1 to 7 to true. Conversely, the terminal may indicate to the base station that it does not support a capability for at least one of the options 1 to 7 by omitting an indicator corresponding to the options 1 to 7 from the UE capability message, or by setting a value corresponding to the options 1 to 7 to false.

[0119] According to one embodiment of the present disclosure, a base station may transmit to a terminal a configuration or indicator to include a timestamp in a measurement report (e.g., if the base station determines that the terminal supports the capability after receiving timestamp capability information about the terminal's measurement time point). For this operation, the base station may provide the terminal with at least one of the following options through a QoE configuration (e.g., AppLayerMeasConfig) or a radio measurement configuration (e.g., MeasConfig).

[0120] - Option 1. Instructs the terminal to include the measurement time when measuring (reporting) QoE.

[0121] - Option 2. Instructs the terminal to include the measurement point in time when making radio (or MDT) measurements (reports).

[0122] - Option 3. Instructs the terminal to include the measurement point in the QoE measurement and radio (or MDT) measurement (reporting).

[0123] - Option 4. Instructs the terminal to include a timestamp for the measurement point when measuring (reporting) QoE by service type or for a specific service type (e.g., XR or streaming).

[0124] - Option 5. An instruction to the terminal to include a timestamp for the measurement point in the MDT measurement (report) when receiving a service for a specific service type (e.g., XR or streaming) or by service type.

[0125] - Option 6. Instructs the terminal to include a timestamp for the measurement point in time when measuring QoE and MDT (reporting) by service type or for a specific service type (e.g., XR or streaming).

[0126] - Option 7. An instruction to the terminal to include a timestamp for the measurement point when measuring (reporting) QoE for each QoE metric (e.g., buffer level, initial playout delay) or for a specific QoE metric.

[0127] According to one embodiment of the present disclosure, if the base station includes an indicator corresponding to the options 1 to 7 or the base station sets a value corresponding to the options 1 to 7 to true, the terminal can perform a measurement report including a timestamp according to the option set by the base station. Conversely, if the base station omits an indicator corresponding to the options 1 to 7 or sets a value corresponding to the options 1 to 7 to false, the terminal can perform a measurement report without including a timestamp according to the option.

[0128] According to one embodiment of the present disclosure, a terminal AS (or RRC) layer that has received an indication for the above option from a base station can forward the indication to a terminal application (APP) layer to instruct the terminal APP to include a timestamp when measuring QoE.

[0129] According to one embodiment of the present disclosure, a terminal (e.g., a terminal that has received an instruction from a base station to include a timestamp in a measurement report) may include a timestamp of a measurement point in a measurement report when reporting a QoE measurement report and / or a radio (MDT) measurement report. The terminal may indicate an absolute time of a measurement point in time of a measurement result (e.g., a QoE indicator or RSRP, RSRQ, etc.). For example, the unit of absolute time may be year (e.g., 2023) / month (e.g., August) / day (e.g., 1st) / hour (e.g., 13:00) / minute (e.g., 43 minutes) / second (40 seconds). In order to indicate a more precise measurement point in time, time information in millisecond units and / or microsecond units may also be defined / included in the timestamp. According to one embodiment of the present disclosure, the terminal may indicate a relative time of a measurement point in time of a measurement result (e.g., a QoE indicator or RSRP, RSRQ, etc.). Relative time may indicate elapsed time based on a specific fixed point in time (reference time). For example, the reference time may be the point in time when the terminal AS or terminal APP receives the MDT (radio) measurement configuration or QoE measurement configuration. The unit of relative time may be defined as year and / or month and / or day and / or hour and / or minute and / or second and / or millisecond and / or microsecond.

[0130] When the terminal APP measures a QoE measurement value (e.g., buffer level, initial playout delay, etc.) or inputs (sets) the QoE measurement value into a measurement report, the terminal APP may include in the QoE measurement report a timestamp value of the measurement time or the time at which the QoE measurement value is input into the measurement report. According to one embodiment of the present disclosure, the terminal APP may include a timestamp of the measurement time for each QoE measurement value in the measurement report. According to one embodiment of the present disclosure, the terminal APP may include only one timestamp for a plurality of QoE measurement values ​​(e.g., buffer level) included in the QoE measurement report. This is because the TCE / MCE or OAM that receives the QoE measurement report can know the measurement cycle of the QoE measurement value. For example, when the terminal APP includes a plurality of buffer levels in a measurement report, only the timestamp of the time at which the first buffer level was measured may be included in the measurement report. This is because even if TCE / MCE or OAM receives multiple buffer level values ​​and only the timestamp for the first value, it can calculate / infer the timestamps of the remaining buffer levels by calculating / inferring the measurement period of the buffer level. For example, when configuring QoE, OAM can set the QoE reporting period to 10 seconds and instruct the terminal to report 5 buffer levels at a time. In this case, since the terminal measures the buffer level every 2 seconds and OAM also knows (by calculating) this measurement period, OAM can calculate the timestamp of the second buffer level (= first timestamp + 2 seconds), the timestamp of the third buffer level (= first timestamp + 4 seconds), etc., in that order using only the timestamp of the first buffer level.

[0131] According to one embodiment of the present disclosure, even if a QoE measurement report generated by a terminal APP includes multiple QoE measurement values ​​(of a single type or multiple types), the time at which the terminal APP generated the QoE measurement report or the time at which the terminal APP transmitted the generated QoE measurement report to the terminal AS may be included in the QoE measurement report as a single timestamp value.

[0132] According to one embodiment of the present disclosure, a QoE measurement report generated by a terminal APP, including a QoE measurement result and a timestamp, can be transmitted to a terminal AS via an AT command (e.g., 355). The terminal AS can include the QoE measurement report received from the terminal APP in an RRC message (e.g., a MeasurementReportAppLayer message) in the form of a container and transmit it to a base station (e.g., 360). The base station can transmit the QoE measurement report received from the terminal AS to a TCE / MCE (370).

[0133] According to one embodiment of the present disclosure, the terminal AS may include the MDT (radio) measurement result and a timestamp in an RRC message (e.g., a MeasurementReport message) and transmit it to the base station. At this time, the terminal may include the time point when setting the RSRP and / or RSRP and / or SINR for each cell that triggered the radio measurement report in the message, or when calculating the RSRP and / or RSRP and / or SINR for each cell that triggered the radio measurement report, or when measuring the RSRP and / or RSRP and / or SINR for each cell that triggered the radio measurement report as a timestamp in the RRC message (e.g., a MeasurementReport message). According to one embodiment of the present disclosure, a timestamp for each MeasResultNR (when generating MeasResultNR) may be included in the RRC message. According to one embodiment of the present disclosure, a timestamp for each parameter in MeasResultNR may be included in the RRC message. The base station that receives the MDT (radio) measurement result and timestamp can forward the MDT (radio) measurement result and timestamp to the TCE / MCE. Consequently, the TCE / MCE or OAM can align the QoE measurement result and the radio measurement result by receiving the timestamp (set by the terminal) related to the QoE measurement result and the timestamp (set by the terminal) related to the radio (MDT) measurement result, and can perform network optimization using the aligned QoE measurement result and radio measurement result.

[0134] Unlike the conventional method in which a TCE or MCE or a network operator aligns QoE measurement reports and MDT (radio) measurement reports and utilizes them for network optimization, according to one embodiment of the present disclosure, a base station can utilize network (e.g., Uu interface) optimization by aligning RAN visible QoE measurement reports and MDT (radio) measurement reports. That is, the correlation between the measurement results of the radio side and the QoE of the application side can be utilized for network optimization between the corresponding terminal and the corresponding base station. For example, if the radio quality measured by the terminal is poor and the RVQoE measurement result at the same time is poor, the base station can first try to improve the QoE quality of the terminal by improving the radio quality of the terminal. The base station can calculate each measurement point in time through the point in time when the RVQoE measurement result or the MDT (radio) measurement report is received from the terminal, but the calculated RVQoE measurement result or each measurement point in time of the MDT (radio) may be inaccurate. The timestamp calculated by the base station for the MDT measurement report or RVQoE measurement report may be different from the value actually measured by the terminal. In other words, the base station may not be able to know the exact time when the terminal performed the measurement. More specifically, there may be a delay (latency) between the time when the terminal performs the measurement and generates the measurement result as a message, receives an uplink grant, and transmits it to the base station. Therefore, even if the base station uses the time when it receives the measurement report from the terminal as the timestamp value, there may be an error with the actual time when the terminal performed the measurement. In addition, the error value may not be constant for each measurement report depending on the network conditions, the scheduling of the base station, and the conditions of the terminal.As a result, the base station may perform inaccurate alignment of the timestamps for the QoE measurement results (e.g., timestamps with an error of 1 from the terminal's measurement time) and the timestamps for the MDT measurement results (e.g., timestamps with an error of 2 from the terminal's measurement time).

[0135] According to one embodiment of the present disclosure, to address the aforementioned issues, a terminal may report the measurement time at which the terminal performed the measurement to the base station when reporting RVQoE and MDT (radio) measurements. To achieve this, the terminal may report at least one of the following supported options to the base station via a UE capability message (e.g., UECapabilityInformation).

[0136] - Option 1. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when measuring (reporting) RVQoE.

[0137] - Option 2. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when measuring (reporting) MDT.

[0138] - Option 3. Whether the terminal supports the ability to provide a timestamp for the measurement point in time during RVQoE measurement (reporting) and MDT measurement (reporting).

[0139] - Option 4. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when measuring (reporting) RVQoE by service type or for a specific service type (e.g., XR or streaming).

[0140] - Option 5. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when measuring (reporting) MDT, either by service type or when receiving a service for a specific service type (e.g., XR or streaming).

[0141] - Option 6. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when performing RVQoE measurements and MDT measurements (reporting) by service type or for a specific service type (e.g., XR or streaming).

[0142] - Option 7. Whether the terminal supports the ability to provide a timestamp for the measurement point in time when measuring (reporting) RVQoE for each RVQoE metric (e.g., buffer level, initial playout delay) or for a specific RVQoE metric.

[0143] According to one embodiment of the present disclosure, when a terminal receives a UE capability request message (e.g., a UECapabilityEnquiry message) from a base station, the terminal may indicate to the base station that it supports a capability for at least one of the options 1 to 7 by including an indicator corresponding to the options 1 to 7 or setting a value corresponding to the options 1 to 7 to true when transmitting a UE capability message (e.g., UECapabilityInformation) to the base station. Conversely, the terminal may indicate to the base station that it does not support a capability for at least one of the options 1 to 7 by omitting an indicator corresponding to the options 1 to 7 from the UE capability message or setting a value corresponding to the options 1 to 7 to false.

[0144] According to one embodiment of the present disclosure, a base station may transmit to a terminal a configuration or indicator to include a timestamp in a measurement report of the terminal (e.g., if the base station determines that the terminal supports the capability after receiving timestamp capability information about the measurement time of the terminal). For this operation, the base station may provide at least one of the following options to the terminal through an RVQoE configuration (e.g., AppLayerMeasConfig or RAN-VisibleParameters) or a radio measurement configuration (e.g., MeasConfig).

[0145] - Option 1. Instructs the terminal to include the measurement time when measuring (reporting) RVQoE.

[0146] - Option 2. Instructs the terminal to include the measurement point in time when making radio (or MDT) measurements (reports).

[0147] - Option 3. Instructs the terminal to include the measurement time point when performing RVQoE measurements and radio (or MDT) measurements (reporting).

[0148] - Option 4. Instructs the terminal to include a timestamp for the measurement point when measuring (reporting) RVQoE by service type or for a specific service type (e.g., XR or streaming).

[0149] - Option 5. An instruction to the terminal to include a timestamp for the measurement point in the MDT measurement (report) when receiving a service for a specific service type (e.g., XR or streaming) or by service type.

[0150] - Option 6. Instructs the terminal to include a timestamp for the measurement point in time when measuring RVQoE and MDT (reporting) by service type or for a specific service type (e.g., XR or streaming).

[0151] - Option 7. An instruction to the terminal to include a timestamp for the measurement time when measuring (reporting) RVQoE for each RVQoE metric (e.g., buffer level, initial playout delay) or for a specific RVQoE metric.

[0152] According to one embodiment of the present disclosure, if the base station includes an indicator corresponding to the options 1 to 7 or the base station sets a value corresponding to the options 1 to 7 to true, the terminal can perform a measurement report including a timestamp according to the option set by the base station. Conversely, if the base station omits an indicator corresponding to the options 1 to 7 or sets a value corresponding to the options 1 to 7 to false, the terminal can perform a measurement report without including a timestamp according to the option.

[0153] According to one embodiment of the present disclosure, a terminal AS (or RRC) layer that has received an indication for the above option from a base station can forward the indication to a terminal application (APP) layer to instruct the terminal APP to include a timestamp when measuring RVQoE.

[0154] According to one embodiment of the present disclosure, a terminal (e.g., a terminal that has received an instruction from a base station to include a timestamp in a measurement report) may include a timestamp of a measurement point in a measurement report when reporting an RVQoE measurement report and / or a radio (MDT) measurement report. The terminal may indicate an absolute time of a measurement point in time of a measurement result (e.g., an RVQoE indicator or RSRP, RSRQ, etc.). For example, the unit of absolute time may be year (e.g., 2023) / month (e.g., August) / day (e.g., 1st) / hour (e.g., 13:00) / minute (e.g., 43 minutes) / second (40 seconds). In order to indicate a more precise measurement point in time, time information in millisecond units and / or microsecond units may also be defined / included in the timestamp. According to one embodiment of the present disclosure, the terminal may indicate a relative time of a measurement point in time of a measurement result (e.g., an RVQoE indicator or RSRP, RSRQ, etc.). Relative time may indicate elapsed time based on a specific fixed point in time (reference time). For example, the reference time may be the point in time when the terminal AS or terminal APP received the MDT (radio) measurement configuration or the RVQoE measurement configuration. The unit of relative time may be defined as year and / or month and / or day and / or hour and / or minute and / or second and / or millisecond and / or microsecond.

[0155] When the terminal APP measures an RVQoE measurement value (e.g., buffer level, initial playout delay, etc.) or inputs (sets) an RVQoE measurement value into a measurement report, the terminal APP may include in the RVQoE measurement report a timestamp value of the measurement time or the time at which the RVQoE measurement value is input into the measurement report. According to one embodiment of the present disclosure, the terminal APP may include a timestamp of the measurement time for each RVQoE measurement value in the measurement report. According to one embodiment of the present disclosure, the terminal APP may include only one timestamp for a plurality of RVQoE measurement values ​​(e.g., buffer level) included in the RVQoE measurement report. This is because the base station receiving the RVQoE measurement report can know the measurement cycle of the RVQoE measurement value. For example, when the terminal APP includes a plurality of buffer levels in a measurement report, only the timestamp of the time at which the first buffer level was measured may be included in the measurement report. This is because even if the base station receives multiple buffer level values ​​and only the timestamp for the first value, it can calculate the timestamps of the remaining buffer levels by calculating / inferring the measurement period of the buffer level. For example, when configuring RVQoE, the base station can set the RVQoE reporting period to 10 seconds and instruct the terminal to report 5 buffer levels at a time. In this case, since the terminal measures the buffer level every 2 seconds and the base station also knows this measurement period, the base station can calculate the timestamp of the second buffer level (= first timestamp + 2 seconds), the timestamp of the third buffer level (= first timestamp + 4 seconds), and so on, in that order, with only the timestamp of the first buffer level.

[0156] According to one embodiment of the present disclosure, even if a RVQoE measurement report generated by a terminal APP includes multiple RVQoE measurement values ​​(of a single type or multiple types), the time at which the terminal APP generated the RVQoE measurement report or the time at which the terminal APP transmitted the generated RVQoE to the terminal AS may be included in the RVQoE measurement report as a single timestamp value.

[0157] According to one embodiment of the present disclosure, an RVQoE measurement report generated by a terminal APP, including an RVQoE measurement result and a timestamp, can be transmitted to a terminal AS via an AT command (e.g., 520). The terminal AS can include the RVQoE measurement report received from the terminal APP in an RRC message (e.g., a MeasurementReportAppLayer message) and transmit it to a base station (e.g., 525). According to one embodiment of the present disclosure, the terminal AS can include the MDT (radio) measurement result and a timestamp in an RRC message (e.g., a MeasurementReport message) and transmit it to the base station. At this time, the terminal may include the time point when inputting (setting) values ​​such as RSRP and / or RSRP and / or SINR for each cell that triggered the radio measurement report into a message, or calculating (deriving) values ​​such as RSRP and / or RSRP and / or SINR for each cell that triggered the radio measurement report, or measuring RSRP and / or RSRP and / or SINR for each cell that triggered the radio measurement report as a timestamp in an RRC message (e.g., MeasurementReportAppLayer message). According to one embodiment of the present disclosure, a timestamp for each MeasResultNR (when generating MeasResultNR) may be included in the RRC message. According to one embodiment of the present disclosure, a timestamp for each parameter in MeasResultNR may be included in the RRC message. As a result, the base station can perform alignment of the RVQoE measurement results and the radio measurement results by receiving a timestamp (set by the terminal) related to the RVQoE measurement results and a timestamp (set by the terminal) related to the radio (MDT) measurement results, and can perform network optimization (or Uu interface) using the aligned RVQoE measurement results and the radio measurement results.

[0158] For conventional RAN visible QoE measurements, the terminal APP can periodically report measurement results (520, 525) according to a period (e.g., ran-VisiblePeriodicity) set by the base station (510). However, periodic reporting of RVQoE may have several problems. For example, if the base station sets a short measurement / reporting period to the terminal, the base station can obtain more RVQoE information, but it may require allocation of a large amount of radio resources for RVQoE transmission, which may increase the energy consumption of the terminal. Conversely, if the base station sets a long measurement / reporting period to the terminal, the base station may not be able to receive RVQoE information from the terminal at the necessary moment. For example, if a terminal intermittently detects a bad / poor QoE, but the value at that moment is not captured / measured due to a long measurement / reporting cycle, the measurement result at that point in time will not be included in the RVQoE measurement report, and the base station may not be aware that the measurement result at a certain point in time is not included in the RVQoE measurement report. To solve this problem, event-based RVQoE measurement reporting can be considered. That is, since the terminal periodically reports RVQoE measurement values, the base station will not waste radio resources and energy of the terminal by reporting RVQoE measurement values ​​that the base station is not interested in every time, and the terminal can perform RVQoE measurement reporting only when an event that the base station is interested in (e.g., poor QoE) is detected. The event that the base station is interested in may not only be a poor QoE detection at the terminal APP side, but also an event at the terminal radio side. For example, a base station may want to obtain information on the QoE value actually experienced by a terminal APP, as well as the radio measurement results of the terminal when the signal strength for the serving cell is weakened, such as event A2 of conventional radio measurement.For example, if the base station receives a poor QoE measurement result from the terminal APP along with a radio measurement report triggered by event A2 from the terminal, the base station may handover the terminal. However, if the base station receives a good QoE measurement result from the terminal APP along with a radio measurement report triggered by event A2 from the terminal, the base station may decide not to handover the terminal. Furthermore, if the terminal transmits both the radio measurement result and the RVQoE measurement result measured at the same time to the base station, the base station can easily achieve alignment of the two measurement results (even without introducing the aforementioned timestamp).

[0159] According to one embodiment of the present disclosure, a terminal may transmit a radio (MDT) measurement report and an RVQoE measurement report together when a radio measurement report is triggered. The trigger of the radio measurement report may mean the detection of a conventional radio measurement event (e.g., event A1, A2, B1, B2, etc.) and may also mean that periodic reporting is triggered.

[0160] According to one embodiment of the present disclosure, a terminal may report to a base station its support capability for transmitting an RVQoE measurement report (together with radio measurement results) by a radio measurement report trigger. For this purpose, an indicator may be defined in a UE capability message (e.g., a UECapabilityInfomration message), and this message may be a message transmitted in response to a UECapabilityEnquiry message requested by the base station. If the terminal includes the indicator in the UE capability message or sets it to true, the inclusion or setting of the indicator in the UE capability message of the terminal may mean that the terminal supports the operation of transmitting an RVQoE measurement report (together with radio measurement results) by a radio measurement report trigger. Conversely, if the terminal omits the indicator in the UE capability message or sets it to false, the omission or setting of the indicator in the UE capability message of the terminal may mean that the terminal does not support the operation of transmitting an RVQoE measurement report (together with radio measurement results) by a radio measurement report trigger.

[0161] According to one embodiment of the present disclosure, the support capability may be defined for each service type (e.g., serviceType) or for a specific service type. That is, the support capability may be defined for each service type (e.g., serviceType), or the support capability may be defined only for a specific service type.

[0162] According to one embodiment of the present disclosure, the support capability may be defined for each RVQoE metric (e.g., buffer level) or for a specific RVQoE metric type. That is, the support capability may be defined for each RVQoE metric (e.g., buffer level), or the support capability may be defined only for a specific RVQoE metric (e.g., buffer level).

[0163] According to one embodiment of the present disclosure, after receiving the support capability of the terminal from the terminal [support capability for an operation of transmitting an RVQoE measurement report (together with a radio measurement result) by a radio measurement report trigger], the base station can transmit a related setting [setting for an operation of transmitting an RVQoE measurement report (together with a radio measurement result) by a radio measurement report trigger] to the terminal. The terminal can receive the setting, and the setting can include setting information linking an RVQoE measurement setting and a radio measurement setting (for an operation of transmitting an RVQoE measurement report (together with a radio measurement result) by a radio measurement report trigger).

[0164] According to one embodiment of the present disclosure, a base station may include a QoE configuration ID (e.g., MeasConfigAppLayerId) in a radio measurement configuration (e.g., MeasConfig, EventTriggerConfig, PeriodicalReportConfig, ReportConfigNR) to indicate to a terminal the association of a radio measurement configuration with a QoE configuration. At this time, the QoE configuration ID provided to the terminal may indicate a QoE configuration set in advance to the terminal. According to one embodiment of the present disclosure, there may be multiple QoE configuration IDs included in the radio measurement configuration. The QoE configuration ID may be defined in the radio measurement configuration as a parameter in the form of SetupRelease, and accordingly, the base station may indicate to the terminal the association (via Setup) or release (via release) of the QoE configuration ID with the radio measurement configuration.

[0165] According to one embodiment of the present disclosure, a base station may include a radio measurement related ID (e.g., MeasId, MeasObjectId, ReportConfigId) in an (RV)QoE measurement configuration (e.g., RAN-VisibleParameters or MeasConfigAppLayer) to indicate to a terminal the association of a radio measurement configuration and a QoE configuration.

[0166] According to one embodiment of the present disclosure, a terminal may transmit an RVQoE measurement report (together with a radio measurement result) when a radio measurement report trigger is triggered if at least one or all of the following conditions are satisfied.

[0167] - Condition 1. When a radio measurement report is triggered (e.g., when an event condition is met, when a periodic report is triggered)

[0168] - Condition 2. If the terminal is instructed / configured with a QoE configuration ID (e.g. MeasConfigAppLayerId) linked to the radio measurement report,

[0169] - Condition 3. If the terminal is instructed / set with a radio measurement related ID (e.g., MeasId, MeasObjectId, ReportConfigId) linked to a QoE configuration ID (e.g., MeasConfigAppLayerId),

[0170] - Condition 4. If the terminal has (in advance) set the RVQoE settings for the QoE setting ID associated with the radio measurement report.

[0171] - Condition 5. If the terminal is instructed / set to set QoE settings linked to the radio measurement report,

[0172] - Condition 6. If there is an RVQoE measurement report to be transmitted for the linked QoE setting ID,

[0173] - Condition 7. When the terminal receives an instruction from the base station to include an RVQoE measurement report in the radio measurement report.

[0174] The UE may report the RVQoE measurement report to the base station (together with the radio measurement result report) by including it in a radio measurement result report message (e.g., MeasResults in a MeasurementReport message). The RVQoE measurement report included in the radio measurement report message may include a QoE configuration ID (to indicate which QoE configuration the measurement report was generated for) and RVQoE measurement report parameters (e.g., RAN-VisibleMeasurements or sub-parameters of RAN-VisibleMeasurements).

[0175] According to one embodiment of the present disclosure, when a terminal receives a QoE setting ID in a radio measurement setting from a base station, or receives a radio measurement related ID in an (RV)QoE setting, the radio measurement setting is linked to a QoE setting corresponding to the QoE setting ID included in the radio measurement setting, and the terminal can transmit an RVQoE measurement report (together with a radio measurement result) when a radio measurement report is triggered.

[0176] According to one embodiment of the present disclosure, when a terminal has one radio measurement configuration associated with multiple RVQoE configurations, the terminal can transmit multiple RVQoE measurement reports (together with radio measurement results) for the multiple RVQoE configurations upon a radio measurement report trigger.

[0177] According to one embodiment of the present disclosure, if the QoE configuration is linked to the radio measurement configuration and a radio measurement report trigger does not occur, the terminal may (periodically) report an RVQoE measurement report to the base station according to a conventional QoE measurement reporting procedure. For example, the report may be transmitted to SRB4 using a MeasurementReportAppLayer message. In addition, if the radio measurement report trigger occurs, the terminal may include the RVQoE measurement report in a radio measurement result report message and transmit it to the base station. For example, the report may be transmitted to SRB1 / 3 using a MeasurementReport message.

[0178] According to one embodiment of the present disclosure, if a QoE configuration is linked to a radio measurement configuration and a radio measurement report trigger does not occur, the terminal may not perform an operation of (periodically) reporting an RVQoE measurement report to the base station according to a conventional QoE measurement reporting procedure. Instead, the terminal may transmit an RVQoE measurement report only when a radio measurement report trigger occurs, and may include this in a radio measurement result report message and transmit it to the base station. For example, the MeasurementReport message may be transmitted to SRB1 / 3.

[0179] According to one embodiment of the present disclosure, an event that triggers a radio measurement report using an RVQoE indicator (e.g., buffer level, initial playout delay) may be newly defined. That is, in addition to events (e.g., events A1, A2, B1, B2, etc.) that trigger a radio measurement report based on a radio measurement value, a terminal may trigger a radio measurement report (including an RVQoE indicator value) based on an (RV)QoE indicator actually experienced by the terminal APP. For example, an event is defined when a terminal AS receives an RVQoE measurement report from a terminal APP, and each time the terminal AS receives an RVQoE measurement report from the terminal APP, the terminal may trigger a radio measurement report (including an RVQoE indicator value). For example, as an event, when a terminal APP detects a QoE measurement result that is worse than a specific threshold, or when a terminal AS receives an RVQoE measurement report that is worse than a specific threshold from a terminal APP, it is defined as an event, and whenever the terminal AS receives an RVQoE measurement report from the terminal APP, the terminal can trigger a radio measurement report (including an RVQoE indicator value). For example, as an event, when a terminal APP detects a QoE measurement result that is better than a specific threshold, or when a terminal AS receives an RVQoE measurement report that is better than a specific threshold from a terminal APP, it is defined as an event, and whenever the terminal AS receives an RVQoE measurement report from the terminal APP, the terminal can trigger a radio measurement report (including an RVQoE indicator value). The terminal can trigger a radio measurement report (including an RVQoE indicator value) when the corresponding event is satisfied (entering condition) or no longer satisfied (leaving condition).

[0180] FIG. 8 is a block diagram illustrating the internal structure of a terminal applied to examples of the present disclosure.

[0181] Referring to FIG. 8, the terminal includes an RF (Radio Frequency) processing unit (810), a baseband processing unit (820), a storage unit (830), and a control unit (840).

[0182] The RF processing unit (810) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (810) up-converts the baseband signal provided from the baseband processing unit (820) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (810) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In the drawing, only one antenna is illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (810) may include multiple RF chains. Furthermore, the RF processing unit (810) may perform beamforming. For the above beamforming, the RF processing unit (810) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO, and can receive multiple layers when performing the MIMO operation.

[0183] The baseband processing unit (820) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (820) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (820) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (810). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (820) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit (820) divides the baseband signal provided from the RF processing unit (810) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform) operation, and then restores the received bit string through demodulation and decoding.

[0184] The baseband processing unit (820) and the RF processing unit (810) transmit and receive signals as described above. Accordingly, the baseband processing unit (820) and the RF processing unit (810) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (820) and the RF processing unit (810) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (820) and the RF processing unit (810) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (mm wave) (e.g., 60GHz) band.

[0185] The storage unit (830) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (830) can store information related to a second access node that performs wireless communication using wireless access technology. In addition, the storage unit (830) provides the stored data at the request of the control unit (840).

[0186] The control unit (840) controls the overall operations of the terminal. For example, the control unit (840) transmits and receives signals through the baseband processing unit (820) and the RF processing unit (810). In addition, the control unit (840) records and reads data in the storage unit (830). For this purpose, the control unit (840) may include at least one processor. For example, the control unit (840) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs, and may include a multi-connection processing unit (842) as illustrated in the drawing.

[0187] FIG. 9 is a block diagram illustrating the structure of a base station applied to examples of the present disclosure.

[0188] Referring to FIG. 9, a base station according to an example of the present disclosure is configured to include an RF processing unit (910), a baseband processing unit (920), a backhaul communication unit (930), a storage unit (940), and a control unit (950).

[0189] The RF processing unit (910) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (910) up-converts the baseband signal provided from the baseband processing unit (920) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (910) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is illustrated, but the base station may have multiple antennas. In addition, the RF processing unit (910) may include multiple RF chains. Furthermore, the RF processing unit (910) may perform beamforming. For the beamforming, the RF processing unit (910) may adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The above RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.

[0190] The baseband processing unit (920) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the wireless access technology. For example, when transmitting data, the baseband processing unit (920) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (920) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (910). For example, in the case of OFDM, when transmitting data, the baseband processing unit (920) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (920) divides the baseband signal provided from the RF processing unit (910) into OFDM symbol units, restores signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (920) and the RF processing unit (910) transmit and receive signals as described above. Accordingly, the baseband processing unit (920) and the RF processing unit (910) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0191] The backhaul communication unit (930) provides an interface for communicating with other nodes within the network. That is, the backhaul communication unit (930) converts a bit string transmitted from the main base station to another node, such as an auxiliary base station or a core network, into a physical signal, and converts a physical signal received from the other node into a bit string.

[0192] The storage unit (940) stores data such as basic programs, application programs, and configuration information for the operation of the main base station. In particular, the storage unit (940) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (940) can store information that serves as a judgment criterion for whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (940) provides the stored data at the request of the control unit (950).

[0193] The control unit (950) controls the overall operations of the base station. For example, the control unit (950) transmits and receives signals through the baseband processing unit (920) and the RF processing unit (910) or through the backhaul communication unit (930). In addition, the control unit (950) records and reads data in the storage unit (940). To this end, the control unit (950) may include at least one processor, and may include a multi-connection processing unit (952) as illustrated in the drawing. Meanwhile, the embodiments of the present disclosure disclosed in the present specification and drawings are merely specific examples presented to easily explain the technical contents of the present disclosure and help in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to a person skilled in the art to which the present disclosure pertains that other modified examples based on the technical idea of ​​the present disclosure are possible. In addition, each of the above embodiments may be combined and operated as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. Furthermore, the embodiments of the present disclosure are applicable to other communication systems, and other modifications based on the technical concepts of the embodiments may also be implemented. For example, the embodiments may be applied to LTE systems, 5G, NR systems, or 6G systems. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.

[0194] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made without detracting from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.

[0195] The operations of the base station or terminal described above can be realized by providing a memory device storing the corresponding program code in any component within the base station or terminal device. That is, the control unit of the base station or terminal device can execute the operations described above by reading and executing the program code stored in the memory device using a processor or CPU (Central Processing Unit).

[0196] The various components and modules of the entity, base station or terminal device described in the present disclosure may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates and application-specific semiconductors.

[0197] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

[0198] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0199] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0200] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0201] While the detailed description of the present disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the claims described below but also by equivalents thereof. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-described embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above-described embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

[0202] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: A step of receiving a configuration message including first configuration information related to a cell measurement report and second configuration information related to a QoE (quality of experience) measurement report from a base station; The above first setting information includes information about an event that triggers the cell measurement report; and Including a step of transmitting a measurement report message to the base station based on the first setting information and the second setting information, A method wherein, when an event that triggers the cell measurement report is detected, the measurement report message includes the cell measurement report and the QoE measurement report.

2. In paragraph 1, The second setting information includes information on the relationship between the first setting information and the second setting information, The above cell measurement report is associated with the QoE measurement report based on information about the above correlation.

3. In paragraph 1, A method wherein the event triggering the above cell measurement report includes an event configured based on a QoE related indicator.

4. In paragraph 1, One of the first configuration information and the second configuration information includes a first indicator instructing that information about a time at which measurement for the cell measurement report was performed is included in the cell measurement report, and a second indicator instructing that information about a time at which measurement for the QoE measurement report was performed is included in the QoE measurement report, A method wherein the above measurement report message includes information about when the measurement for the cell measurement report was performed and / or information about when the measurement for the QoE measurement report was performed.

5. A method performed by a base station in a wireless communication system, the method comprising: A step for transmitting a configuration message including first configuration information related to a cell measurement report and second configuration information related to a QoE (quality of experience) measurement report to a terminal; The above first setting information includes information about an event that triggers the cell measurement report; and Including a step of receiving a measurement report message from the terminal based on the first setting information and the second setting information, A method wherein, when an event that triggers the cell measurement report is detected, the measurement report message includes the cell measurement report and the QoE measurement report.

6. In paragraph 5, The second setting information includes information on the relationship between the first setting information and the second setting information, The above cell measurement report is associated with the QoE measurement report based on information about the above correlation.

7. In paragraph 5, A method wherein the event triggering the above cell measurement report includes an event configured based on a QoE related indicator.

8. In paragraph 5, One of the first configuration information and the second configuration information includes a first indicator instructing that information about a time at which measurement for the cell measurement report was performed is included in the cell measurement report, and a second indicator instructing that information about a time at which measurement for the QoE measurement report was performed is included in the QoE measurement report, A method wherein the above measurement report message includes information about when the measurement for the cell measurement report was performed and / or information about when the measurement for the QoE measurement report was performed.

9. In a wireless communication system, the terminal comprises: transceiver; Including a controller connected to the above transceiver, The above controller: Receive a configuration message from a base station, including first configuration information related to a cell measurement report and second configuration information related to a QoE (quality of experience) measurement report, The above first setting information includes information about an event that triggers the cell measurement report, To the above base station, a measurement report message is transmitted based on the first setting information and the second setting information, A terminal, wherein when an event that triggers the above cell measurement report is detected, the measurement report message includes the cell measurement report and the QoE measurement report.

10. In paragraph 9, The second setting information includes information on the relationship between the first setting information and the second setting information, The above cell measurement report is associated with the QoE measurement report based on information about the above correlation, terminal.

11. In paragraph 9, An event that triggers the above cell measurement report is a terminal that includes an event configured based on QoE related indicators.

12. In paragraph 9, One of the first configuration information and the second configuration information includes a first indicator instructing that information about a time at which measurement for the cell measurement report was performed is included in the cell measurement report, and a second indicator instructing that information about a time at which measurement for the QoE measurement report was performed is included in the QoE measurement report, A terminal, wherein the above measurement report message includes information about the time at which measurement for the cell measurement report was performed and / or information about the time at which measurement for the QoE measurement report was performed.

13. In a wireless communication system, at a base station, the base station, transceiver; Including a controller connected to the above transceiver, The above controller: Transmitting a configuration message including first configuration information related to a cell measurement report and second configuration information related to a QoE (quality of experience) measurement report to the terminal, The above first setting information includes information about an event that triggers the cell measurement report, From the above terminal, based on the first setting information and the second setting information, a measurement report message is received, A base station, wherein when an event that triggers the above cell measurement report is detected, the measurement report message includes the cell measurement report and the QoE measurement report.

14. In paragraph 13, The second setting information includes information on the relationship between the first setting information and the second setting information, The above cell measurement report is associated with the QoE measurement report based on information about the above correlation, base station.

15. In paragraph 13, A base station, wherein the event that triggers the above cell measurement report includes an event configured based on QoE related indicators.

Images