Method and apparatus for transmitting and receiving qoe measurement configuration information between dual access base stations in 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 businesses, security- and safety-related services, and the like) on the basis of 5G communication technology and IoT-related technology. More specifically, the present disclosure relates to a method performed by a terminal in a wireless communication system, the method comprising the steps of: receiving configuration information related to a quality of experience (QoE) measurement configuration, wherein the QoE measurement configuration includes first information indicating a signaling radio bearer (SRB) over which a QoE measurement report related to the QoE measurement configuration is transmitted and second information instructing the terminal to report information about a start or end of a measurement session related to the QoE measurement configuration; and transmitting, to a first node associated with an SRB indicated by the first information, the QoE measurement report including information about the start or end of the measurement session related to the QoE measurement configuration, wherein the information about the start or end of the measurement session related to the QoE measurement configuration may be forwarded to a second node associated with the first node on the basis of dual connectivity (DC).

Description

Method and device for transmitting and receiving QOE measurement setting information between dual access base stations in a communication system

[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] Based on the discussion as described above, the present disclosure relates to a method performed by a terminal in a wireless communication system, the method comprising: receiving configuration information related to a quality of experience (QoE) measurement configuration, wherein the QoE measurement configuration includes first information indicating a signaling radio bearer (SRB) to which a QoE measurement report related to the QoE measurement configuration is transmitted and second information instructing the terminal to report information about the start or end of a measurement session related to the QoE measurement configuration; and transmitting the QoE measurement report including the information about the start or end of the measurement session related to the QoE measurement configuration to a first node associated with an SRB indicated by the first information, wherein the information about the start or end of the measurement session related to the QoE measurement configuration can be forwarded to a second node associated with the first node based on dual connectivity (DC).

[0011] In addition, the present disclosure relates to a method performed by a first node in a wireless communication system, the method comprising: transmitting, to a terminal, configuration information related to a quality of experience (QoE) measurement configuration, the QoE measurement configuration including first information indicating a signaling radio bearer (SRB) over which a QoE measurement report related to the QoE measurement configuration is transmitted, and second information instructing the terminal to report information about the start or end of a measurement session related to the QoE measurement configuration, wherein the first node is associated with an SRB indicated by the first information; and receiving, from the terminal, the QoE measurement report including information about the start or end of the measurement session related to the QoE measurement configuration, wherein the information about the start or end of the measurement session related to the QoE measurement configuration can be forwarded to a second node associated with the first node based on dual connectivity (DC).

[0012] In addition, the present disclosure provides a terminal in a wireless communication system, the terminal including: a transceiver; and a controller connected to the transceiver, wherein the controller receives configuration information related to a quality of experience (QoE) measurement configuration, the QoE measurement configuration including first information indicating a signaling radio bearer (SRB) to which a QoE measurement report related to the QoE measurement configuration is transmitted, and second information instructing the terminal to report information about the start or end of a measurement session related to the QoE measurement configuration, and is configured to transmit the QoE measurement report including information about the start or end of the measurement session related to the QoE measurement configuration to a first node associated with an SRB indicated by the first information, wherein the information about the start or end of the measurement session related to the QoE measurement configuration can be forwarded to a second node associated with the first node based on dual connectivity (DC).

[0013] In addition, the present disclosure relates to a first node in a wireless communication system, wherein the first node comprises a transceiver; and a controller connected to the transceiver, wherein the controller transmits, to a terminal, configuration information related to a quality of experience (QoE) measurement configuration, the QoE measurement configuration including first information indicating a signaling radio bearer (SRB) over which a QoE measurement report related to the QoE measurement configuration is transmitted, and second information instructing the terminal to report information about the start or end of a measurement session related to the QoE measurement configuration, and the first node is associated with an SRB indicated by the first information, and is configured to receive, from the terminal, the QoE measurement report including information about the start or end of a measurement session related to the QoE measurement configuration, wherein the information about the start or end of the measurement session related to the QoE measurement configuration can be forwarded to a second node associated with the first node based on dual connectivity (DC).

[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 disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs 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 diagram showing an SRB path in an SA situation according to one embodiment of the present disclosure.

[0022] FIG. 7 is a diagram showing an SRB path in a DC situation 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 disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Hereinafter, embodiments of the present disclosure 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 terminal) (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, an adaptive modulation and coding (AMC) method that determines a modulation scheme and a 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 (control plane / user plane)) has been established for UE;

[0045] - The UE AS (Access Stratum) 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, a terminal in an INACTIVE wireless connection state can transition from a connected mode or a standby mode using a specific procedure. The terminal transitions from INACTIVE mode to a connected mode through a Resume procedure, and transitions from a connected mode to 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 the terminal and a base station, and consists of one or more steps. In addition, transition from INACTIVE mode to 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 QoE (quality of experience) measurement is supported by service type (e.g., streaming, MTSI (Multimedia Telephony Service for IMS (IP (internet protocol) Multimedia Subsystem)), VR (virtual reality)) 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 a QoE report message (e.g., ul-MeasurementReportAppLayer-Seg) through the UE capability message. The UE capability message includes ASN.1 (Abstract Syntax Notation One) information as shown in Table 1 below, and the description of the 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] 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.

[0060]

[0061]

[0062] 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.

[0063] 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).

[0064] 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). A signaling radio bearer (SRB) 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.

[0065]

[0066]

[0067] 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.

[0068] [Correction pursuant to Rule 91, November 26, 2024] [Table 8]

[0069]

[0070] 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).

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

[0072] 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.

[0073] 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., at least one of an area scope, an application layer capability, and a service type). The base station (410) can transmit / forward the QoE measurement configuration to one of the searched single or multiple terminals via 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 via an AT Command between the AS layer and the APP, as described above with reference to 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.

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

[0075] 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.

[0076] 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.

[0077] 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 information element (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.

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

[0079] - 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.

[0080] - 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.

[0081] 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.

[0082] 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.

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

[0084] - playout delay (playoutDelayForMediaStartup): This parameter allows the terminal to include / report the playout delay at media startup, specifying this value in milliseconds. The terminal can include this parameter in the RVQoE measurement report if reportPlayoutDelayForMediaStartup is set to true during RVQoE configuration.

[0085] - PDU session ID list (pdu-SessionIdList): The terminal can indicate the PDU (Protocol Data Unit) 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.

[0086] 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.

[0087] FIG. 6 is a diagram showing an SRB path in an SA situation according to one embodiment of the present disclosure.

[0088] Referring to FIG. 6, a terminal can be connected to a network in a SA (Standalone) state. That is, a terminal (605) can communicate with one base station (610). At this time, a Signaling Radio Bearer (SRB) can be defined / used / configured between the base station and the terminal for transmitting an RRC message or a non-access stratum (NAS) message. More specifically, for example, in the SA state, SRB0, SRB1, SRB2, and SRB4 can be configured / used. Among SRB0, SRB1, SRB2, and SRB4, SRB4 can be used for transmitting a QoE measurement report message (or an App layer measurement report message) of the terminal.

[0089] FIG. 7 is a diagram showing an SRB path in a DC situation according to one embodiment of the present disclosure.

[0090] Referring to FIG. 7, a terminal may be connected to a network in a DC (dual connectivity) state (e.g., NR-DC (NR-NR Dual Connectivity)). That is, when a terminal (705) establishes connections with two base stations (710 and 715) individually, the terminal may communicate with both base stations simultaneously. In DC (dual connectivity), each base station may be referred to as an MN (Master node, 710) and an SN (Secondary node, 715). At this time, a SRB (Signaling Radio Bearer) may be defined / used between the base station and the terminal for transmitting an RRC message or NAS message. More specifically, for example, SRB0, SRB1, SRB2, and SRB4 may be configured / used for communication between the terminal and the MN. In addition, among SRB0, SRB1, SRB2, and SRB4, SRB4 may be used for transmitting a QoE measurement report message (or an App layer measurement report message) of the terminal. In addition, among SRB0, SRB1, SRB2, and SRB4, SRB1 and SRB2 can be set as Split SRB (720), and Split SRB can support communication between the terminal and the MN through the RRC / PDCP (packet data convergence protocol) layer of the MN and the RLC (radio link control) / MAC (medium access control) / PHY layer of the SN. The base station can set an SRB path for communication with the terminal using Split SRB. More specifically, for example, the base station can set whether to use the RLC / MAC / PHY layer of the MN, the RLC / MAC / PHY layer of the SN, or both the RLC / MAC / PHY layer of the MN and the RLC / MAC / PHY layer of the SN.When both the MN and SN's RLC / MAC / PHY layers are used (duplication), transmission reliability can be improved through packet duplication. Additionally, among SRB0, SRB1, SRB2, and SRB4, SRB3 and SRB5 can be configured / used for communication between the MN and the SN.

[0091] According to one embodiment of the present disclosure, the terminal may need to establish an SRB with the SN as well as the MN in order to transmit a QoE measurement report message. The terminal may use SRB4 to transmit the QoE measurement report message to the MN (the RRC layer of the MN). Alternatively, the terminal may define / use Split SRB4 to transmit the QoE measurement report message to the MN (the RRC layer of the MN). In this case, the QoE measurement report message may be transmitted to the PDCP / RRC layer of the MN via the PHY / MAC / RLC layers of the SN. Alternatively, the terminal may use SRB3 to transmit the QoE measurement report message to the SN (the RRC layer of the SN). The QoE measurement report message may be a message with a lower priority than other uplink RRC messages (e.g., transmitted via SRB3). This may be because the QoE report may be used to optimize network operation but may not be an essential message for network operation. Therefore, for transmitting QoE measurement report messages to the SN (the RRC layer of the SN), a new (separate / additional) SRB (e.g., SRB5 with lower priority than SRB3) can be defined / used. Like SRB3, SRB5 can connect to the RRC layer of the SN via the PHY / MAC / RLC / PDCP layers of the SN.

[0092] In order for the terminal to receive QoE configuration information from the MN (the RRC layer of the MN), the terminal may configure SRB1 (or Split SRB1) and use the configured SRB1 (or Split SRB1). In addition, in order for the terminal to receive QoE configuration information from the SN (the RRC layer of the SN), the terminal may configure SRB3 and use the configured SRB3. Alternatively, the terminal may receive QoE configuration information in the form of an SN message (including SN QoE configuration information) included in a message transmitted from SRB1.

[0093] According to one embodiment of the present disclosure, a terminal in NR-DC state can receive an indication from the network regarding a reporting leg to be used when reporting QoE measurement. Here, the reporting leg can be, for example, for indicating to the terminal whether the terminal will transmit a QoE measurement report to an MN, whether the terminal will transmit a QoE measurement report to an SN, whether the terminal will use SRB4 for QoE measurement reporting, or whether the terminal will use SRB5 for QoE measurement reporting. The terminal can transmit a QoE measurement report to a base station using the indicated reporting leg.

[0094] According to one embodiment of the present disclosure, a terminal in NR-DC state may receive an indication from the network regarding a reporting leg to be used when performing a RAN visible QoE (RVQoE) measurement report. Here, the reporting leg may be for indicating to the terminal whether the terminal transmits an RVQoE measurement report to the MN, whether the terminal transmits an RVQoE measurement report to the SN, whether the terminal uses SRB4 for the RVQoE measurement report, or whether the terminal uses SRB5 for the RVQoE measurement report. The reporting leg related to RVQoE may be indicated separately from the reporting leg related to non-RVQoE QoE. Since the configuration and reporting of non-RVQoE QoE are not visible within the RRC layer as they are contained / included in a container, for convenience of explanation, the non-RVQoE QoE may be referred to as encapsulated QoE hereinafter. That is, the terminal can separately receive from the network a reporting leg for measurement reporting on encapsulated QoE and a reporting leg for measurement reporting on RVQoE. The network can set / instruct the same value for each of the reporting leg for measurement reporting on encapsulated QoE and the reporting leg for measurement reporting on RVQoE. Additionally, the network can set / instruct different values ​​for each of the reporting leg for measurement reporting on encapsulated QoE and the reporting leg for measurement reporting on RVQoE. The terminal can transmit an RVQoE measurement report to the base station using the instructed reporting leg for RVQoE.

[0095] For convenience of explanation, various embodiments of the present disclosure have been described assuming NR-DC, but the methods according to various embodiments of the present disclosure can be equally applied (with appropriate modifications) to various types of DC situations (e.g., MR (multi-radio access technology (RAT)-DC).

[0096] According to one embodiment of the present disclosure, with respect to QoE settings for a terminal, an MN or a master cell group (MCG) may transmit QoE settings to the terminal via SRB1, and an SN or a secondary cell group (SCG) may transmit QoE settings to the terminal via SRB3.

[0097] According to one embodiment of the present disclosure, in relation to QoE settings for a terminal, the MN or MCG may transmit the QoE settings (e.g., in the form of an encapsulated message) to the SN or SCG, and the SN or SCG may set the QoE settings received from the MN or MCG to the terminal through SRB3.

[0098] According to one embodiment of the present disclosure, in relation to QoE settings for a terminal, an SN or SCG may transmit the QoE settings (e.g., in the form of an encapsulated message) to an MN or MCG, and the MN or MCG may set the QoE settings received from the SN or SCG to the terminal via SRB1.

[0099] According to one embodiment of the present disclosure, with respect to a QoE measurement report of a terminal, the terminal may transmit a QoE measurement report to an MN or MCG via SRB4, and may transmit a QoE measurement report to an SN or SCG via SRB5.

[0100] According to one embodiment of the present disclosure, in relation to a QoE measurement report of a terminal, the terminal can transmit the QoE measurement report to an MN or MCG via SRB4, and the MN or MCG that receives the QoE measurement report from the terminal can transmit the QoE measurement report received from the terminal to a TCE or MCE (via a CN).

[0101] According to one embodiment of the present disclosure, in relation to a QoE measurement report of a terminal, the terminal can transmit the QoE measurement report to an MN or MCG via SRB4, and the MN or MCG that receives the QoE measurement report from the terminal can transmit the QoE measurement report received from the terminal to an SN or SCG (e.g., in the form of an encapsulated message). The SN or SCG that receives the QoE measurement report of the terminal from the MN or MCG can transmit the QoE measurement report of the terminal to a TCE or MCE (via a CN).

[0102] According to one embodiment of the present disclosure, a terminal can transmit a QoE measurement report to an SN or SCG via SRB5, and the SN or SCG, which receives the QoE measurement report from the terminal, can transmit the QoE measurement report of the terminal to a TCE or MCE (via a CN).

[0103] According to one embodiment of the present disclosure, a terminal can transmit a QoE measurement report to an SN or SCG via SRB5, and the SN or SCG, which receives the QoE measurement report from the terminal, can transmit the QoE measurement report of the terminal to an MN or MCG (e.g., in the form of an encapsulated message). The MN or MCG, which receives the QoE measurement report of the terminal from the SN or SCG, can transmit the QoE measurement report of the terminal to a TCE or MCE (via a CN).

[0104] According to one embodiment of the present disclosure, when configuring QoE, the base station can instruct the terminal whether RRC segmentation can be used (whether allowed) when the terminal performs QoE measurement report. According to one embodiment of the present disclosure, the base station can instruct the terminal (e.g., via indicator 1) whether RRC segmentation can be used (whether allowed) when the terminal performs QoE measurement report (transmitted to MN) via SRB4. Separately from the configuration of indicator 1, the base station can instruct (e.g., via indicator 2) whether RRC segmentation can be used (whether allowed) when the terminal performs QoE measurement report (transmitted to SN) via SRB5. Here, indicator 1 and indicator 2 are merely arbitrary names for convenience of description and are not to be construed as limiting the meaning of the technical idea according to the embodiment of the present disclosure. In addition, terms referred to as indicator A, etc. below are merely arbitrary terms and are not to be construed as limiting the meaning of the technical idea according to the embodiment of the present disclosure. If some or all (i.e., at least one) of the conditions below are satisfied, the terminal may use RRC segmentation when reporting QoE measurements via SRB4. That is, by using RRC segmentation, the terminal may divide the QoE measurement report message into multiple RRC messages and transmit them to the MN.

[0105] (Condition 1) If the terminal receives a QoE setting that includes indicator 1 or is set to true.

[0106] (Condition 2) If the terminal supports the (uplink) RRC segmentation function for QoE measurement reporting.

[0107] (Condition 3) When the RRC message (encoded RRC message) generated by the terminal to transmit the QoE measurement report through SRB4 is larger than the maximum supported PDCU SDU size.

[0108] In one embodiment of the present disclosure, if the terminal does not satisfy at least one of conditions 1 and 2 but satisfies condition 3, the terminal may discard the generated RRC message. This may mean a loss of QoE measurement reports.

[0109] A terminal may use RRC segmentation when reporting QoE measurements via SRB5 if some or all (i.e., at least one) of the conditions below are satisfied. That is, by using RRC segmentation, a QoE measurement report message can be divided into multiple RRC messages and transmitted to the SN.

[0110] (Condition 1) If the terminal receives a QoE setting that includes indicator 2 or is set to true.

[0111] (Condition 2) If the terminal supports the (uplink) RRC segmentation function for QoE measurement reporting.

[0112] (Condition 3) When the RRC message (encoded RRC message) generated by the terminal to transmit the QoE measurement report through SRB5 is larger than the maximum supported PDCU SDU size.

[0113] In one embodiment of the present disclosure, if the terminal does not satisfy at least one of conditions 1 and 2 but satisfies condition 3, the terminal may discard the generated RRC message. This may mean a loss of QoE measurement reports.

[0114] According to one embodiment of the present disclosure, since indicator 1 is for whether RRC segmentation is allowed for a QoE measurement report received by the MN (transmitted by the terminal), the MN can determine whether indicator 1 is set (whether indicator 1 is included in the QoE configuration) or its setting value (true or false). Since indicator 2 is for whether RRC segmentation is allowed for a QoE measurement report received by the SN (transmitted by the terminal), the SN can determine whether indicator 2 is set (whether indicator 2 is included in the QoE configuration) or its setting value (true or false). According to one embodiment of the present disclosure, there may be only one node (MN or SN) that transmits the QoE configuration to the terminal. For example, when the MN provides / transmits / forwards the QoE configuration to the terminal, the MN can set both indicator 1 and indicator 2 to the terminal. Meanwhile, although the MN may provide both indicator 1 and indicator 2 to the UE when configuring QoE, the MN may not be able to determine whether to configure indicator 2 (i.e., whether indicator 2 is included in the QoE configuration or not) or what value to configure (true or false). This is because the MN may not be able to know whether the SN supports or allows RRC segmentation. Methods according to various embodiments of the present disclosure can solve this problem. Conversely, while the SN provides / transmits / forwards the QoE configuration to the UE, the SN may configure both indicator 1 and indicator 2 to the UE. Meanwhile, although the SN may provide both indicator 1 and indicator 2 to the UE when configuring QoE, the SN may not be able to determine whether to configure indicator 1 (i.e., whether indicator 1 is included in the QoE configuration or not) or what value to configure (true or false).This is because the SN may not know whether the MN supports or allows RRC segmentation. Methods according to various embodiments of the present disclosure can address this issue.

[0115] In addition, when the MN decides / configures the reporting leg (e.g., whether the UE will use SRB4 for QoE measurement reporting or whether the UE will use SRB5 for QoE measurement reporting), it may need to know whether the SN supports or allows RRC segmentation for SRB5 (e.g., indicator 2). The reason why it is necessary to know whether the SN supports or allows RRC segmentation for SRB5 from the MN's perspective is that if the SN does not support or allow RRC segmentation for SRB5 but the MN supports or allows RRC segmentation for SRB4, the MN can decide / configure the reporting leg to SRB4 by considering the SN's non-support / disallowance of RRC segmentation for SRB5 and the MN's support / allowance of RRC segmentation for SRB4 in order to prevent loss of large-sized QoE measurement reports. Additionally, if the SN supports or allows RRC segmentation for SRB5 and the MN does not support or allow RRC segmentation for SRB4, the MN may determine / configure the reporting leg to SRB5 to avoid loss of large-sized QoE measurement reports. For this reason, for example, when the SN determines / configures the reporting leg (e.g., SRB4 or SRB5), it may need to know (or be aware of) whether the MN supports or allows RRC segmentation for SRB4 (e.g., indicator 1).

[0116] In order to solve the aforementioned situations in which the MN does not know whether the SN supports or allows RRC segmentation, the SN does not know whether the MN supports or allows RRC segmentation, the MN needs to determine whether the SN supports or allows RRC segmentation for SRB5, and the SN needs to determine whether the MN supports or allows RRC segmentation for SRB5, RRC segmentation information can be exchanged between the MN and the SN according to one embodiment of the present disclosure.

[0117] According to one embodiment of the present disclosure, Node 1 (e.g., an MN or SN that instructs a terminal to set up QoE) may request Node 2 (e.g., another node, SN or MN) to transmit whether Node 2 supports or allows RRC segmentation (e.g., when initially setting up QoE to a terminal). In order for Node 1 to request Node 2 to transmit whether Node 2 supports or allows RRC segmentation, one indicator (e.g., indicator A) may be defined in the S-NODE ADDITION REQUEST and / or S-NODE MODIFACATION REQEUST and / or S-NODE MODIFICATION REQURIED and / or S-NODE ADDITION REQUEST ACKNOWLEDGE and / or S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or S-NODE MODIFICATION CONFIRM messages, and indicator A may also be defined in various messages other than the messages described above. Node 1 may request transmission of whether Node 2 supports or allows RRC segmentation by including the indicator A in the message or setting it to true. In addition, Node 1 may not request transmission of whether Node 2 supports or allows RRC segmentation by not including the indicator A in the message or setting it to false.

[0118] According to one embodiment of the present disclosure, when Node 2 (e.g., SN or MN) receives a request from Node 1 (e.g., MN or SN) to transmit whether RRC segmentation is supported or allowed (e.g., when receiving a message including the indicator A or set to true)), Node 2 (SN or MN) may transmit to Node 1 (MN or SN) whether Node 2 supports or allows RRC segmentation. In order for Node 2 to transmit to Node 1 whether Node 2 supports or allows RRC segmentation, one indicator (e.g., indicator B) may be defined in the S-NODE ADDITION REQUEST and / or S-NODE MODIFACATION REQEUST and / or S-NODE MODIFICATION REQURIED and / or S-NODE ADDITION REQUEST ACKNOWLEDGE and / or S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or S-NODE MODIFICATION CONFIRM messages, and indicator B may also be defined in various messages other than the messages described above. Node 2 may indicate / transmit that Node 2 supports or allows RRC segmentation by including the indicator B in the above messages or setting it to true. Thereafter, Node 1 or Node 2 may instruct the UE to allow RRC segmentation for Node 2. Additionally, Node 2 can indicate / transmit that Node 2 does not support or allow RRC segmentation by not including the indicator B in the message or setting it to false. Afterwards, Node 1 or Node 2 can indicate to the terminal that RRC segmentation for Node 2 is not allowed.

[0119] By receiving information about the above indicator B from node 2, node 1 can set an indicator for whether RRC segmentation is allowed for node 2 to the terminal, and can also determine / set the reporting leg (SRB4 or SRB5) in consideration of this.

[0120] According to one embodiment of the present disclosure, node 1 (e.g., an MN or SN that instructs a terminal to set up QoE) can request node 2 (e.g., another node, SN or MN) to allow RRC segmentation of node 2 (e.g., when initially setting up QoE to the terminal). In order for node 1 to request node 2 to allow RRC segmentation of node 2, one indicator (e.g., indicator C) can be defined in the S-NODE ADDITION REQUEST and / or S-NODE MODIFACATION REQEUST and / or S-NODE MODIFICATION REQURIED and / or S-NODE ADDITION REQUEST ACKNOWLEDGE and / or S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or S-NODE MODIFICATION CONFIRM messages, and indicator C can also be defined in various messages other than the messages described above. Node 1 can request permission for RRC segmentation of Node 2 by including the indicator C in the message or setting it to true. Additionally, Node 1 can not request permission for RRC segmentation of Node 2 by not including the indicator C in the message or setting it to false.

[0121] According to one embodiment of the present disclosure, when Node 2 (e.g., SN or MN) receives a request for RRC segmentation permission from Node 1 (MN or SN) (e.g., receives a message including the indicator C or set to true)), Node 2 (SN or MN) can instruct Node 1 (MN or SN) to accept or reject Node 2's RRC segmentation permission request. In order for Node 2 to indicate to Node 1 whether to accept or reject an RRC segmentation permission request from Node 2, an indicator (e.g., indicator D) may be defined in the S-NODE ADDITION REQUEST and / or S-NODE MODIFACATION REQEUST and / or S-NODE MODIFICATION REQURIED and / or S-NODE ADDITION REQUEST ACKNOWLEDGE and / or S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or S-NODE MODIFICATION CONFIRM messages, and the indicator D may also be defined in various messages other than the messages described above. By including the indicator D in the above messages or setting it to true, Node 2 may indicate acceptance of the RRC segmentation permission request from Node 1. Thereafter, Node 1 or Node 2 may indicate to the UE to allow RRC segmentation for Node 2. Additionally, Node 2 may indicate rejection of the RRC segmentation permission request from Node 1 by not including the indicator D in the message or setting it to false. Subsequently, Node 1 or Node 2 may indicate to the terminal that RRC segmentation for Node 2 is not permitted.

[0122] By receiving information about the above indicator D, node 1 can set an RRC segmentation allowance indicator for node 2 to the terminal, and node 1 can also determine / set a reporting leg (SRB4 or SRB5) by considering the segmentation allowance indicator for node 2.

[0123] According to one embodiment of the present disclosure, Node 2 (e.g., an SN or MN requesting a change in QoE settings to Node 1) may request Node 1 (e.g., an MN or SN instructing other nodes, terminals, to change an RRC segmentation permission indicator of Node 2 (e.g., when requesting a change in QoE settings to Node 1). For example, Node 2 may allow RRC segmentation during QoE initialization, but may not allow RRC segmentation in a specific case (e.g., when computing resources and energy resources consumed due to RRC segmentation operation are large). Alternatively, Node 2 may not allow RRC segmentation during QoE initialization, but may allow RRC segmentation in a specific case (e.g., when a problem of insufficient radio resources is resolved). In order for Node 2 to request Node 1 to change the RRC segmentation permission indicator of Node 2, one indicator (e.g., indicator E) can be defined in the S-NODE ADDITION REQUEST and / or S-NODE MODIFACATION REQEUST and / or S-NODE MODIFICATION REQURIED and / or S-NODE ADDITION REQUEST ACKNOWLEDGE and / or S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or S-NODE MODIFICATION CONFIRM messages, and the indicator E can also be defined in various messages other than the messages described above. Node 2 can request a change in whether RRC segmentation is allowed for Node 2 by including the indicator E in the message or setting it to "true." In addition, Node 2 can not request a change in whether RRC segmentation is allowed for Node 2 by not including the indicator E in the message or setting it to false.

[0124] According to one embodiment of the present disclosure, when Node 1 (e.g., MN or SN) receives a request to change RRC segmentation permission from Node 2 (SN or MN) (e.g., receives a message including the indicator E or set to true)), Node 1 (MN or SN) can instruct Node 2 (SN or MN) to accept or reject Node 2's request to change RRC segmentation permission. In order for Node 1 to instruct Node 2 to accept or reject a request to change the RRC segmentation permission status of Node 2, one indicator (e.g., indicator F) may be defined in the S-NODE ADDITION REQUEST and / or S-NODE MODIFACATION REQEUST and / or S-NODE MODIFICATION REQURIED and / or S-NODE ADDITION REQUEST ACKNOWLEDGE and / or S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or S-NODE MODIFICATION CONFIRM messages, and the indicator F may also be defined in various messages other than the messages described above. By including the indicator F in the above messages or setting it to true, Node 1 may instruct Node 2 to accept the request to change the RRC segmentation permission status from Node 2. Thereafter, Node 1 or Node 2 may change the RRC segmentation permission status for Node 2 and instruct the UE to do so. Additionally, Node 1 may indicate rejection of a request to change whether RRC segmentation is allowed from Node 2 by not including the indicator F in the message or setting it to false. Thereafter, Node 1 or Node 2 may maintain the terminal's setting for whether RRC segmentation is allowed for Node 2 without changing it.

[0125] By receiving information about the above indicator F, node 1 can set (change or maintain) the RRC segmentation allowance indicator for node 2 to the terminal, and also determine / set the reporting leg (SRB4 or SRB5) taking this into consideration.

[0126] According to one embodiment of the present disclosure, node 1 (e.g., MN or SN) can provide QoE configuration to a terminal. For the QoE configuration, a reporting leg configured for the terminal can indicate node 2 (e.g., SN or MN). According to the information (node ​​2) indicated by the reporting leg, the terminal can transmit a QoE measurement report to node 2. Node 2 can forward the received QoE measurement report to node 1. Node 1, which receives the QoE measurement report from node 2, can forward it to TCE / MCE. Meanwhile, node 2 may experience RAN overload, and due to the RAN overload, node 2 may temporarily suspend QoE measurement reporting of the terminal. Node 2 can temporarily suspend QoE measurement reporting of the terminal by including a pause indicator (e.g., pauseReporting) or indicating it as true to the terminal. However, the QoE setting used in the QoE measurement report of the terminal is information set by Node 1, not Node 2, to the terminal. If Node 2, which did not instruct the terminal to set the QoE setting, temporarily suspends the terminal's measurement report of the QoE setting without consulting Node 1, Node 1 may determine that the QoE measurement report has caused a problem in the terminal's QoE transmission (e.g., an incorrect determination) and change the network setting (e.g., releasing the QoE setting for the terminal and setting the QoE for another terminal) related to the QoE setting (e.g., changing the incorrect setting).

[0127] In order to solve a problem that may occur when Node 1 instructs the QoE settings used in QoE measurement reporting of a terminal, and Node 2, which has not instructed the QoE settings to the terminal, instructs the terminal to temporarily suspend the QoE settings without consulting Node 1, the base station (either Node 1 or Node 2) may negotiate information about indicator settings for pause / resume (before providing, for example, indicators for pause (temporarily suspending QoE measurement reporting) and resume (resuming temporarily suspended QoE measurement reporting) to the terminal). At this time, the negotiation about information about indicator settings performed between Node 1 and Node 2 may include information about QoE IDs that can request pause / resume and / or QoE IDs that should not request pause / resume.

[0128] According to one embodiment of the present disclosure, when a Node 2 (e.g., MN or SN) detects RAN overload, it may request an indication for a pause of measurement reporting of a UE (or transmit a preference for a pause) to a Node 1 (SN or MN) (by QoE ID). For the Node 2's request for an indication for a pause of measurement reporting of a UE to a Node 1, one indicator (e.g., indicator G) may be defined in the S-NODE ADDITION REQUEST and / or the S-NODE MODIFACATION REQEUST and / or the S-NODE MODIFICATION REQURIED and / or the S-NODE ADDITION REQUEST ACKNOWLEDGE and / or the S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or the S-NODE MODIFICATION CONFIRM messages, and the indicator G may also be defined in various messages other than the messages described above. Node 2 may use the above indicator G to indicate one or more QoE IDs that request a pause in the terminal's measurement report, or may include or set to true one indicator (e.g., indicator K) per QoE configuration ID that requests a pause.

[0129] According to one embodiment of the present disclosure, node 1 (e.g., receiving a pause indication request) can instruct node 2 (by instructed QoE ID) whether to grant or deny the pause indication request. To indicate whether to grant the pause indication request from node 1 to node 2, an indicator (e.g., indicator H) can be defined in the S-NODE ADDITION REQUEST and / or S-NODE MODIFACATION REQEUST and / or S-NODE MODIFICATION REQURIED and / or S-NODE ADDITION REQUEST ACKNOWLEDGE and / or S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or S-NODE MODIFICATION CONFIRM messages, and indicator H can also be defined in various messages other than the messages described above. Node 1 can use the indicator H to indicate one or more QoE IDs for which a pause instruction request is to be granted (or denied), or can indicate whether to grant or deny a pause instruction request based on the QoE ID that received the pause instruction request. Afterwards, for the QoE IDs for which the pause instruction request is granted, Node 1 or Node 2 can indicate a pause to the terminal based on the QoE ID (e.g., by setting the pauseReporting indicator to true).

[0130] According to one embodiment of the present disclosure, when RAN overload is resolved, Node 2 (e.g., MN or SN) may request (by QoE ID) an instruction for resuming measurement reporting of a UE (or transmit a preference for resuming) to Node 1 (e.g., SN or MN) (to resume QoE measurement reporting of a paused UE). For an indication request for a resume of a measurement report of a terminal from node 1 to node 2, one indicator (e.g., indicator I) may be defined in the S-NODE ADDITION REQUEST and / or S-NODE MODIFACATION REQEUST and / or S-NODE MODIFICATION REQURIED and / or S-NODE ADDITION REQUEST ACKNOWLEDGE and / or S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or S-NODE MODIFICATION CONFIRM messages, and the indicator I may also be defined in various messages other than the messages described above. Node 2 may use the indicator I to indicate one or more QoE IDs for which a resume indication request is made, or may omit or set to false one indicator (e.g., the same as the indicator K above) for each QoE configuration ID for which a resume indication request is made.

[0131] According to one embodiment of the present disclosure, node 1 (e.g., receiving a resume indication request) can instruct node 2 (for each instructed QoE ID) whether to grant or deny the resume indication request. For indicating whether to grant the resume indication request from node 1 to node 2, one indicator (e.g., indicator J) can be defined in the S-NODE ADDITION REQUEST and / or S-NODE MODIFACATION REQEUST and / or S-NODE MODIFICATION REQURIED and / or S-NODE ADDITION REQUEST ACKNOWLEDGE and / or S-NODE MODIFACATION REQEUST ACKNOWLEDGE and / or S-NODE MODIFICATION CONFIRM messages, and indicator J can also be defined in various messages other than the messages described above. Node 1 can use the indicator J to indicate one or more QoE IDs for which a resume instruction request is permitted (or rejected), or can indicate permission or rejection for each QoE ID that receives the resume request. Afterwards, for each QoE ID for which a resume instruction request is permitted, Node 1 or Node 2 can instruct the terminal to resume (e.g., by setting the pauseReporting indicator to false).

[0132] According to one embodiment of the present disclosure, for example, during QoE initialization or change, node 1 (e.g., MN or SN) can instruct node 2 (e.g., SN or MN) one or more QoE IDs for which the terminal should not be instructed to pause (and / or resume). Node 2, upon receiving the instruction for one or more QoE IDs for which the terminal should not be instructed to pause (and / or resume), may not instruct the terminal to pause (or resume) for the instructed QoE IDs or may not transmit a pause instruction request to node 1. Node 2 may instruct the terminal to pause (or resume) for the QoE IDs for which it was not instructed or may transmit a pause instruction request to node 1. For this purpose, negotiation between node 1 and node 2 for instructing the terminal to pause (or resume) in the above-described embodiment may be performed.

[0133] According to one embodiment of the present disclosure, for example, when QoE initialization or QoE setting change is performed, node 1 (e.g., MN or SN) may instruct node 2 (e.g., SN or MN) one or more QoE IDs for which the terminal may be instructed to pause (and / or resume). Node 2, which has received an instruction for one or more QoE IDs for which the terminal may be instructed to pause (and / or resume), may not instruct the terminal to pause (or resume) or may not transmit a pause instruction request to node 1 for the QoE IDs for which the node 2 has not been instructed. Node 2 may instruct the terminal to pause (or resume) or may transmit a pause instruction request to node 1 for the instructed QoE IDs. For this purpose, negotiation may be performed between node 1 and node 2 for instructing the terminal to pause (or resume) in the above-described embodiment.

[0134] According to one embodiment of the present disclosure, when a QoE measurement session starts or ends (for each configured QoE ID), the terminal can transmit the QoE session status information (e.g., appLayerSessionStatus) with a configuration value of "start" or "stop" to the base station. The base station, which receives the QoE session status information from the terminal, can determine whether the QoE measurement session corresponding to the QoE ID has started and is in progress or has ended for the terminal. The QoE session status information can be useful information for the base station to manage the QoE measurement report of the terminal. For example, when the QoE measurement session of the terminal is in progress, the base station can select the terminal in progress with the QoE measurement session as a terminal for MDT (Minimization of Drive tests) measurement and provide the MDT configuration. By being provided with MDT settings, a terminal conducting a QoE measurement session can perform QoE measurement and MDT measurement simultaneously and transmit two types of measurement reports (QoE and MDT) to the OAM, TCE, or MCE, so that the OAM, TCE, or MCE can collect / combine / link the two pieces of information, interpret the results, and ultimately perform network optimization-related actions. The operation of the OAM, TCE, or MCE collecting / combining / linking the two pieces of information of QoE and MDT, interpreting the results, and ultimately performing network optimization-related actions can be referred to as alignment of QoE and MDT measurements.

[0135] When a configured QoE measurement session starts, a DC (Dual connectivity) terminal can transmit session status information (e.g., by setting it to "start") to Node 1 (MN or SN) indicated by the reporting leg. Therefore, Node 1 can provide MDT configuration to the terminal (e.g., for alignment of QoE and MDT measurements). Meanwhile, Node 2 (SN or MN) may not be aware that the QoE measurement session of the terminal has started and may not be able to provide MDT configuration to the terminal (e.g., for alignment of QoE and MDT measurements). In order to solve the problem that Node 2 (SN or MN) may not be aware that the QoE measurement session of the terminal has started and may not be able to provide MDT configuration to the terminal (e.g., for alignment of QoE and MDT measurements), when the terminal AS receives session status information from the terminal APP, the terminal AS may transmit session status information to Node 2 as well as Node 1 indicated by the reporting leg. At this time, if the reporting leg (SRB) corresponding to the session status information transmission is not set, the terminal can store the session status information and transmit it later when the corresponding SRB is set.

[0136] In addition, according to one embodiment of the present disclosure, when the terminal AS receives session status information from the terminal APP, the terminal AS transmits the session status information to the node 1 (MN or SN) instructed by the reporting leg, and the node 1 that receives the session status information can transmit the session status information to the node 2 (SN or MN) (e.g., via Xn interface signaling).

[0137] According to one embodiment of the present disclosure, when a terminal (in DC state) cannot use an SRB (SRB4 or SRB5) (indicated as a reporting leg) for a QoE measurement report (e.g., when the corresponding SRB is not configured or an MCG or SCG failure occurs), the terminal may store a QoE measurement report corresponding to the unavailable SRB (SRB4 or SRB5). In this case, a memory for storing the QoE measurement report corresponding to the unavailable SRB (SRB4 or SRB5) may be separately defined / configured / set. The memory for storing the QoE measurement report may be a separate memory (e.g., memory A) different from 1) a memory for paused QoE measurement reports and 2) a memory for storing inactive / standby mode or MBS QoE measurement reports. 1) QoE measurement / configuration / reporting for at least one service type and / or 2) QoE measurement / configuration / reporting in (NR-)DC and / or 3) A requirement on the size of memory A for storing QoE measurement reports that a terminal supporting SRB5 must support at a minimum may be defined in the standard. More specifically, for example, the standard may define that a terminal supporting 1) QoE measurement / configuration / reporting for at least one service type and / or 2) QoE measurement / configuration / reporting in (NR-)DC and / or 3) SRB5 must support the new memory A of at least the size (e.g., 64KB). According to one embodiment of the present disclosure, when a (DC state) terminal cannot use an SRB (SRB4 or SRB5) (indicated by the reporting leg) for QoE measurement reporting (e.g., when the corresponding SRB is not configured or due to MCG or SCG failure), the QoE measurement report corresponding to the unavailable SRB (e.g., report 1) can be stored in the same memory as the paused QoE measurement report (e.g., report 2).According to one embodiment of the present disclosure, a requirement for a minimum memory size (e.g., 64 KB) that a terminal must support for the common memory for storing two types of QoE measurement reports (report 1 / 2, i.e., QoE measurement reports corresponding to unavailable SRBs and paused QoE measurement reports) may be defined in the standard.

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

[0139] 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).

[0140] 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.

[0141] 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.

[0142] 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.

[0143] 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).

[0144] 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.

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

[0146] 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).

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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).

[0151] 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). For this purpose, 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 disclosure and the drawings are merely specific examples presented to easily explain the technical contents of the present disclosure and help in the understanding of 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.

[0152] 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.

[0153] 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).

[0154] 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.

[0155] 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 the claims or embodiments of the present disclosure.

[0156] 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.

[0157] 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.

[0158] 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.

[0159] 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.

[0160] 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 configuration information related to a QoE (quality of experience) measurement configuration, wherein the QoE measurement configuration includes first information indicating a signaling radio bearer (SRB) to which a QoE measurement report related to the QoE measurement configuration is transmitted, and second information instructing the terminal to report information on the start or end of a measurement session related to the QoE measurement configuration; and A step of transmitting, to a first node associated with an SRB indicated by the first information, the QoE measurement report including information about the start or end of a measurement session related to the QoE measurement setup, A method in which information about the start or end of a measurement session related to the above QoE measurement setup is forwarded to the first node and the associated second node based on DC (dual connectivity).

2. In paragraph 1, If the first node is a MN (master node), the second node is a SN (secondary node), A method wherein the first node is SN and the second node is MN.

3. In paragraph 2, A method wherein forwarding of information about the start or end of a measurement session related to the QoE measurement setup to the second node is performed by including it in a message based on an interface formed between the first node and the second node.

4. In paragraph 2, A method wherein settings related to MDT (minimization of drive tests) measurements aligned with QoE measurements are transmitted from the second node to the terminal based on information about the start or end of a measurement session related to the QoE measurement settings.

5. A method performed by a first node in a wireless communication system, the method comprising: A step of transmitting configuration information related to QoE (quality of experience) measurement configuration to a terminal, wherein the QoE measurement configuration includes first information indicating a signaling radio bearer (SRB) to which a QoE measurement report related to the QoE measurement configuration is transmitted, and second information instructing the terminal to report information on the start or end of a measurement session related to the QoE measurement configuration. The first node is associated with the SRB indicated by the first information; and A step of receiving, from the terminal, the QoE measurement report including information on the start or end of a measurement session related to the QoE measurement setting, A method in which information about the start or end of a measurement session related to the above QoE measurement setup is forwarded to the first node and the associated second node based on DC (dual connectivity).

6. In paragraph 5, If the first node is a MN (master node), the second node is a SN (secondary node), A method wherein the first node is SN and the second node is MN.

7. In paragraph 6, A method wherein forwarding of information about the start or end of a measurement session related to the QoE measurement setup to the second node is performed by including it in a message based on an interface formed between the first node and the second node.

8. In paragraph 6, A method wherein settings related to MDT (minimization of drive tests) measurements aligned with QoE measurements are transmitted from the second node to the terminal based on information about the start or end of a measurement session related to the QoE measurement settings.

9. In a wireless communication system, the terminal comprises: transceiver; and Including a controller connected to the above transceiver, The above controller, Receives configuration information related to QoE (quality of experience) measurement configuration, wherein the QoE measurement configuration includes first information indicating a signaling radio bearer (SRB) to which a QoE measurement report related to the QoE measurement configuration is transmitted, and second information instructing the terminal to report information on the start or end of a measurement session related to the QoE measurement configuration. A first node associated with an SRB indicated by the first information is configured to transmit the QoE measurement report including information about the start or end of a measurement session related to the QoE measurement setup, A terminal in which information about the start or end of a measurement session related to the above QoE measurement settings is forwarded to the first node and the associated second node based on DC (dual connectivity).

10. In paragraph 9, If the first node is a MN (master node), the second node is a SN (secondary node), If the first node is SN, the second node is MN, the terminal 11. In Article 10, Forwarding of information about the start or end of a measurement session related to the QoE measurement setup to the second node is performed by the terminal by including it in a message based on an interface formed between the first node and the second node.

12. In paragraph 10, A terminal, wherein settings related to MDT (minimization of drive tests) measurements aligned with QoE measurements are transmitted from the second node to the terminal based on information about the start or end of a measurement session related to the QoE measurement settings.

13. In a wireless communication system, in a first node, the first node, transceiver; and Including a controller connected to the above transceiver, The above controller, Transmitting configuration information related to QoE (quality of experience) measurement configuration to a terminal, wherein the QoE measurement configuration includes first information indicating a signaling radio bearer (SRB) to which a QoE measurement report related to the QoE measurement configuration is transmitted, and second information instructing the terminal to report information on the start or end of a measurement session related to the QoE measurement configuration. The above first node is associated with the SRB indicated by the above first information, configured to receive, from the terminal, the QoE measurement report including information about the start or end of a measurement session related to the QoE measurement setting, A first node, wherein information about the start or end of a measurement session related to the above QoE measurement settings is forwarded to a second node associated with the first node based on DC (dual connectivity).

14. In paragraph 13, If the first node is a MN (master node), the second node is a SN (secondary node), A first node, wherein the first node is SN and the second node is MN.

15. In paragraph 14, A first node, wherein forwarding of information about the start or end of a measurement session related to the above QoE measurement setup to the second node is performed by including it in a message based on an interface formed between the first node and the second node.

Images