Method and apparatus relating to quality of experience (QOE) measurement in wireless mobile communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a terminal according to the present disclosure may comprise the steps of: receiving, from a base station, a message including configuration information regarding quality of experience (QoE); and transmitting a message for reporting a result of QoE measurement on the basis of the configuration information, wherein the configuration information includes information indicating a first signaling radio bearer (SRB) for an encapsulated QoE measurement report and information indicating a second SRB for a radio access network (RAN) visible QoE measurement report.

Description

Method and device for measuring QOE (QUALITY OF EXPERIENCE) in a wireless mobile communication system

[0001] The present disclosure relates to a communication method and device for a wireless communication system, and to a method and device for QoE measurement.

[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 band (for example, the 3 terahertz (3THz) 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] As a result of the development of mobile communication systems and the aforementioned advancements in technology, various services have become available, and methods for effectively providing these services are required. In particular, methods for providing an efficient DRX configuration method are required.

[0009] The present disclosure aims to provide an effective method and device for measuring QoE (Quality of Experience) in a wireless communication system.

[0010] A control signal processing method in a wireless communication system, characterized in that it includes an operation of receiving a first control signal transmitted from a base station, an operation of processing the received first control signal, and an operation of transmitting a second control signal generated based on the processing to the base station.

[0011] The present disclosure provides a device and method capable of effectively measuring QoE (Quality of Experience) in a wireless communication system.

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

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

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

[0015] FIG. 4 is a flowchart illustrating a procedure for setting / reporting Management-based QoE measurement in one embodiment of the present disclosure.

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

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

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

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

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

[0021] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Furthermore, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. The terms described below are defined based on their functions in the present disclosure, and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0022] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described in detail below 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 solely 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 invention, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0023] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings 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 flowchart 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 flowchart 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).

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

[0025] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' 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 '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

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

[0027] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, 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 with equivalent technical meanings may be used.

[0028] In the following description, the terms "physical channel" and "signal" may be used interchangeably with data or control signals. For example, while PDSCH (physical downlink shared channel) refers to a physical channel through which data is transmitted, PDSCH can also be used to refer to data. That is, in the present disclosure, the expression "transmitting a physical channel" can be interpreted equivalently to the expression "transmitting data or a signal through a physical channel."

[0029] Hereinafter, in the present disclosure, upper signaling refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of the physical layer, or a terminal transmits a signal to a base station using an uplink data channel of the physical layer. Upper signaling can be understood as radio resource control (RRC) signaling or a media access control (MAC) control element (CE).

[0030] For the convenience of explanation below, this disclosure uses terms and names defined in the 3rd Generation Partnership Project NR (New Radio) or 3rd Generation Partnership Project Long Term Evolution (LTE) standards. However, this disclosure is not limited by the terms and names, and can be equally applied to systems conforming to other standards. In this disclosure, gNB may be used interchangeably with eNB for the convenience of explanation. That is, a base station described as an eNB may represent a gNB. In addition, the term terminal may represent not only a mobile phone, an MTC device, an NB-IoT device, a sensor, but also other wireless communication devices.

[0031] Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNodeB (gNB), an eNode B (eNB), a NodeB, a BS (Base Station), 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. However, the base station is not limited to the examples above.

[0032] In particular, the present disclosure can be applied to 3GPP NR (5th generation mobile communication standard). Furthermore, the present disclosure can be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. In the present disclosure, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB. Furthermore, the term "terminal" may refer to other wireless communication devices as well as mobile phones, NB-IoT devices, and sensors.

[0033] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0034] As a representative example of a broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment; UE or MS; Mobile Station) transmits data or control signals to a base station (eNode B or BS; Base Station), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. This multiple access method distinguishes the data or control information of each user by allocating and operating the time-frequency resources to be transmitted for each user so that they do not overlap, that is, so as to achieve orthogonality.

[0035] As the future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0036] In some embodiments, eMBB may aim to provide data rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB should be able to provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, a 5G communication system may need to provide both the peak data rate and an increased user-perceived data rate for a terminal. To meet these requirements, a 5G communication system may require improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology. Furthermore, while current LTE transmits signals using a maximum 20 MHz transmission bandwidth in the 2 GHz band, a 5G communication system can use a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band, thereby meeting the data rates required by the 5G communication system.

[0037] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC may require support for large-scale terminal connections within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, which may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC should be comprised of low-cost terminals, and since frequent battery replacement is unlikely, extremely long battery lifespans, such as 10 to 15 years, may be required.

[0038] Finally, URLLC is a cellular-based wireless communication service used for specific purposes (mission-critical), such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, the communication provided by URLLC may need to provide very low latency (ultra-low latency) and very high reliability (ultra-reliability). For example, a service supporting URLLC may have to satisfy an air interface latency of less than 0.5 milliseconds and may also have a requirement for a packet error rate (PER) of 10-5 or less. Therefore, for services supporting URLLC, 5G systems may be required to provide a smaller Transmit Time Interval (TTI) than other services, while simultaneously allocating a wide range of resources in the frequency band to ensure the reliability of the communication link.

[0039] The three services considered in the aforementioned 5G communication system—eMBB, URLLC, and mMTC—can be multiplexed and transmitted in a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters may be used between the services. However, the aforementioned mMTC, URLLC, and eMBB are merely examples of different service types, and the service types applicable to this disclosure are not limited to the aforementioned examples.

[0040] Furthermore, while the embodiments of the present disclosure are described below using LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) systems as examples, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

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

[0042] Referring to FIG. 1, a wireless access network of a mobile communication system (New Radio, NR) may be composed of a base station (New Radio Node B, hereinafter referred to as gNB) (110) and an AMF (105, New Radio Core Network). The wireless communication system is not limited to the configuration illustrated in FIG. 1 and may include more or fewer components. A user terminal (New Radio User Equipment, hereinafter referred to as NR UE or 0) (115) may access an external network through the gNB (110) and the AMF (105).

[0043] In Fig. 1, the gNB can correspond 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 that is superior to the existing Node B (120). In a mobile communication system, 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 the gNB (110) can be in charge of this. One gNB can typically control multiple cells. The method and device according to one embodiment of the present disclosure can utilize more than the existing maximum bandwidth to implement ultra-high-speed data transmission compared to LTE, and additionally graft beamforming technology using Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology. Additionally, an adaptive modulation and coding (AMC) method that determines the modulation scheme and channel coding rate according to the channel status of the terminal may be applied.

[0044] The core network, which handles various control functions as well as mobility management for terminals, can be connected to multiple base stations. 5GC can also be integrated with existing LTE systems.

[0045] A wireless communication system (or network) according to one embodiment of the present disclosure may be configured to be divided into a user plane (UP) related to transmission of actual user data and a control plane (CP) for connection management, etc., and a gNB (110) may use UP and CP technologies defined in NR technology, and an eNB (130) may use UP and CP technologies defined in LTE (Long Term Evolution) technology even when connected to 5GC.

[0046] 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 wireless mobile communication system according to one embodiment of the present disclosure can be interoperable with the LTE system, and the AMF can be connected to the MME (125) through a network interface. The MME can be 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).

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

[0048] Mobile communication systems have three radio resource control (RRC) states. Connected mode (RRC_CONNECTED, 205) is a radio connection state in which the terminal can transmit and receive data. Idle mode (RRC_IDLE, 230) is a radio connection state in which the terminal monitors whether paging is being sent to it. These two modes are also applied to existing LTE systems, and the detailed technology may be identical to that of the LTE system.

[0049] In a mobile communication system, an inactive (RRC_INACTIVE) radio connection state (215) can be defined. In this inactive radio connection state, the UE context is maintained between the base station and the terminal, and RAN (radio access network)-based paging is supported. The characteristics of the inactive radio connection state are listed below.

[0050] - Cell re-selection mobility;

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

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

[0053] - Paging is initiated by NR RAN;

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

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

[0056] An inactive (INACTIVE) wireless connection state can be transitioned to connected mode or standby mode using specific procedures. The transition from INACTIVE mode to connected mode is performed through the Resume procedure, and the transition from connected mode to INACTIVE mode is performed through the Release procedure including suspend configuration information (210). The procedure is performed by transmitting and receiving one or more RRC messages between the terminal and the base station and may consist of one or more steps. Furthermore, transition from INACTIVE mode to standby mode may be possible through the Release procedure after Resume (220). The transition between connected mode and standby mode may follow LTE technology. That is, transition between modes may be performed through the establishment or release procedure (225).

[0057] FIG. 3 is a flowchart illustrating a procedure for setting / reporting signaling-based QoE measurement in an example 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, VR) to a base station (or NG-RAN, 315) via a UE capability message (e.g., UECapabilityInformation) (310). Before sending the UE capability message, the base station may send a message (e.g., UECapabilityEnquiry) for requesting a UE capability message. In addition, the terminal can report (or transmit) to the base station whether it supports RAN visible QoE measurement by service type (e.g., streaming, VR) via the UE capability message (e.g., ran-VisibleQoE-Streaming-MeasReport, ran-VisibleQoE-VR-MeasReport). In addition, the terminal can report (or transmit) to the base station whether it supports UL RRC segmentation for the QoE report message (e.g., ul-MeasurementReportAppLayer-Seg) via the UE capability message. The UE capability message includes ASN.1 information as shown in [Table 1] below, and the description of the related parameters is as shown in [Table 2] below.

[0058]

[0059]

[0060] 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 these, it may support VR (Virtual Reality) services, MBMS (Multimedia Broadcast Multicast Services), XR (Extended Reality), etc.

[0061] OAM (Operations Administration and Maintenance, 320) can provide QoE measurement configuration information to CN (Core Network, 325) (330). The CN (325) that has received the configuration information can activate QoE measurement by transmitting the configuration information to the base station (315) (335).

[0062] The base station (315) that has received configuration information from the CN (325) can 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 can include an IE (APPLayerMeasConfig) as in [Table 3] below, and the description of the related parameters is as in [Table 4] below.

[0063]

[0064]

[0065] In addition, the operation of the terminal AS (305) that received this may be performed according to the description in [Table 5] below.

[0066]

[0067]

[0068] As described above, for the QoE measurement settings included in measConfigAppLayerToAddModList, the AS layer (305) of the terminal can transmit (or send) 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 can send an AT Command to the APP (345) of the terminal to delete the stored configuration information for the QoE measurement settings included in measConfigAppLayerToAddReleaseList.

[0069] QoE measurement can be performed based on the received configuration information. In addition, the terminal APP (345) can report (or transmit) the results of the measurement based on the configuration information to the terminal AS (305) via an AT command (355).

[0070] The terminal AS (305) that receives this can report the measurement result to the base station (315) via an RRC message (e.g., MeasurementReportAppLayer message) (360). SRB (signaling radio bearer) 4 can be used to report the QoE measurement result. The MeasurementReportAppLayer message can include ASN.1 information as in [Table 6] below, and the description of the related parameters is as in [Table 7] below.

[0071]

[0072]

[0073]

[0074] In addition, the specific procedure of the terminal AS reporting the above measurement results can follow the operation described in [Table 8] below.

[0075]

[0076]

[0077] The base station (315) can transmit the measurement result report to the final server (TCE (trace collection entity) or MCE (measurement collection entity), 365) that collects the measurement report (370).

[0078] FIG. 4 is a flowchart illustrating a procedure for setting / reporting Management-based QoE measurement according to an example of the present disclosure.

[0079] The management-based QoE configuration / reporting procedure may be substantially similar to the signaling-based procedure described in FIG. 3. Therefore, FIG. 4 will only describe the differences from the aforementioned signaling-based procedure, and any procedures and descriptions that overlap with those described in FIG. 3 will be omitted.

[0080] In the management-based method, QoE measurement can be activated by having the OAM (405) directly send the QoE measurement settings to the base station (410) without going through the CN (415). The base station (410) that receives this searches for one or more terminals that meet various conditions (e.g., area scope, application layer capability, service type). Then, the base station (410) can transmit the QoE measurement settings to each of the terminals via an RRC message (e.g., an RRCReconfiguration message or an RRCResume) (420). Each terminal that receives the RRC message can transmit and receive settings and measurement results for QoE measurement via an AT Command between the AS layer and the APP, as described above in FIG. 3. Then, 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 these to the TCE / MCE.

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

[0082] According to the method described in FIGS. 3 and 4, QoE measurement is set by OAM, and QoE measurement reports generated according to the settings are collected by TCE / MCE, and the QoE measurement reports can be used by operators for network optimization. Meanwhile, the base station cannot read or understand the report on the OAM-based QoE measurement transmitted by the terminal. More specifically, although the MeasurementReportAppLayer message includes the measurement report generated by the application layer of the terminal in the measurementReportAppLayerContainer, it is stored in the form of OCTEC STRING, so the base station or the RRC layer of the base station cannot read or understand it. To solve this problem, that is, to enable the base station to read the QoE measurement report and utilize it for network optimization such as radio resource management, RAN visible QoE (RVQoE) measurement can be defined and introduced in 3GPP.

[0083] RVQoE measurement can be defined to be limited to specific service types (e.g., streaming, VR). First, the terminal can report to the base station whether it supports RVQoE measurement by service type (e.g., streaming, VR) (505). The UECapabilityInformation message can be used at this time. For example, the terminal can 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 can include or set the ran-VisibleQoE-VR-MeasReport parameter in the UECapabilityInformation message and transmit it to the base station for a VR service.

[0084] Through this, the base station can determine whether the terminal supports RVQoE measurement for each service type, and based on this, can create an RVQoE measurement setting and transmit it to the terminal (510). At this time, the RVQoE measurement setting can be transmitted together with the OAM-based QoE measurement setting. The RVQoE measurement setting 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 (setup) or releasing (release) the ran-VisibleParameters parameter in the AppLayerMeasConfig IE. The parameter can include the RAN-VisibleParameters IE, through which some or all of the following parameters can be provided from the base station to the terminal. The names of the parameters (fields, information, etc.) described in the present disclosure can be referred to in various ways in consideration of the characteristics of the information contained in the corresponding parameter.

[0085] - RVQoE measurement report cycle (ran-VisiblePeriodicity): Terminal AS or terminal APP can periodically transmit RVQoE measurement reports according to the RVQoE measurement report cycle.

[0086] - Maximum number of reportable buffer levels (numberOfBufferLevelEntries): Terminal AS or terminal APP can include multiple buffer levels when reporting RVQoE measurements, but can include buffer levels in numbers less than or equal to the maximum number of reportable buffer levels setting.

[0087] - Report playout delay at media start (reportPlayoutDelayForMediaStartup): If the value is set to 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 is set to false, the terminal may not include the playout delay at media start in the RVQoE report.

[0088] The AS layer of the terminal can transmit such configuration information to the APP layer of the terminal (515). At this time, the RVQoE measurement configuration can be transmitted together with the OAM-based QoE measurement configuration. The APP of the terminal can perform QoE measurement based on the RVQoE measurement configuration information, 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 together with the OAM-based QoE measurement report.

[0089] The AS layer of the terminal receiving this can forward the transmitted RVQoE measurement report to the base station (525). At this time, the RVQoE measurement report can be forwarded 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.

[0090] - APP layer buffer level list (appLayerBufferLevelList): The APP layer buffer level list may include multiple buffer levels measured by the terminal APP. The number included may be limited by numberOfBufferLevelEntries during RVQoE configuration.

[0091] - playout delay (playoutDelayForMediaStartup): This parameter can indicate the playout delay in ms when media starts. The terminal can include this parameter if reportPlayoutDelayForMediaStartup is set to true during RVQoE configuration.

[0092] - PDU session ID list (pdu-SessionIdList): This parameter can indicate the PDU session(s) used in the application data flow that is the target of RVQoE measurement. Through this, the base station can know which PDU session(s) have RVQoE values ​​(e.g., buffer level and playout delay) measured, and can optimize resource allocation and scheduling for the corresponding PDU session(s) accordingly.

[0093] Base stations can read RVQoE reports and utilize them to optimize their networks. For example, if a base station determines, based on an RVQoE report, that a particular terminal is experiencing poor QoE for a particular service, it can improve the terminal's QoE by allocating more radio resources to that terminal.

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

[0095] A terminal can be connected to a network in a standalone (SA) 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 between the base station and the terminal to transmit an RRC message or a non-access stratum (NAS) message. In the SA state, for example, SRB0, SRB1, SRB2, and SRB4 can be configured / used. Here, SRB4 can be used to transmit a QoE measurement report message (or an App layer measurement report message) of the terminal.

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

[0097] The terminal can be connected to the network in a DC (dual connectivity) (e.g., NR-DC) state. That is, the terminal (705) can establish a connection with two base stations (710 and 715) and communicate with both base stations simultaneously. Each base station may be referred to as a Master node (MN) 710 and a Secondary node (SN) 715. At this time, a Signaling Radio Bearer (SRB) may be defined / used between the base station and the terminal for transmitting an RRC message or an NAS message. Here, SRB0, SRB1, SRB2, and SRB4 may be configured / used for communication between the terminal and the MN. In addition, SRB4 may be used for transmitting a QoE measurement report message (or an App layer measurement report message) of the terminal. Among these, 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. 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. If both the RLC / MAC / PHY layers of the MN and the SN are used (duplication), the reliability of transmission can be increased through duplicate transmission of packets. Meanwhile, SRB3 and SRB5 can be set / used for communication between the terminal and the SN.

[0098] Meanwhile, the UE may need to set up an SRB with the SN as well as the MN to transmit the QoE measurement report message. The UE may use SRB4 to transmit the QoE measurement report message to the MN (the RRC layer of the MN). Alternatively, the UE 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 UE may use SRB3 to transmit the QoE measurement report message to the SN (the RRC layer of the SN). Here, the QoE measurement report message may be a message with a lower priority than the RRC message transmitted in the conventional SRB3. This is because the QoE report may be used to optimize network operation but may not be essential for network operation. Therefore, for transmitting QoE measurement report messages to the SN (the RRC layer of the SN), a new SRB (e.g., SRB5 with a 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.

[0099] To receive QoE configuration information from the MN (the RRC layer of the MN), the terminal may configure and use SRB1 (or Split SRB1). Additionally, the terminal may configure and use SRB3 to receive QoE configuration information from the SN (the RRC layer of the SN). Alternatively, the terminal may receive QoE configuration information in the form of an SN message (including SN QoE configuration information) included in an SRB1 message.

[0100] In one embodiment of the present disclosure, a terminal in NR-DC state can receive an instruction from the network regarding which reporting leg to use when reporting QoE measurements (e.g., whether to transmit to MN or SN, or whether to use SRB4 or SRB5). The terminal can use the indicated reporting leg to transmit the QoE measurement report to the base station.

[0101] Although the embodiments of the present disclosure are written assuming NR-DC, the same method can be applied to various types of DC situations (e.g., MR (multi-radio access technology (RAT)-DC).

[0102] In one embodiment of the present disclosure, the MN or MCG may transmit QoE settings to the terminal via SRB1, and the SN or SCG may transmit QoE settings to the terminal via SRB3.

[0103] In one embodiment of the present disclosure, the MN or MCG may convey QoE settings (e.g., in the form of an encapsulated message) to the SN or SCG, and the SN or SCG may configure them to the UE via SRB3.

[0104] In one embodiment of the present disclosure, the SN or SCG may convey QoE settings (e.g., in the form of an encapsulated message) to the MN or MCG, and the MN or MCG may configure them to the terminal via SRB1.

[0105] In one embodiment of the present disclosure, the terminal may transmit a QoE measurement report to the MN or MCG via SRB4, and may transmit a QoE measurement report to the SN or SCG via SRB5.

[0106] In one embodiment of the present disclosure, a terminal may transmit a QoE measurement report to an MN or MCG via SRB4, and the MN or MCG that receives the QoE measurement report may transmit the QoE measurement report to a TCE or MCE (via a CN).

[0107] In one embodiment of the present disclosure, a terminal may transmit a QoE measurement report to an MN or MCG via SRB4, and the MN or MCG that receives the QoE measurement report may transmit the QoE measurement report to an SN or SCG (e.g., in the form of an encapsulated message).

[0108] In one embodiment of the present disclosure, a terminal may transmit a QoE measurement report to an SN or SCG via SRB5, and the SN or SCG that receives the QoE measurement report may transmit the QoE measurement report to a TCE or MCE (via a CN).

[0109] In one embodiment of the present disclosure, a terminal may transmit a QoE measurement report to an SN or SCG via SRB5, and the SN or SCG that receives the QoE measurement report may transmit the QoE measurement report to an MN or MCG (e.g., in the form of an encapsulated message).

[0110] In one embodiment of the present disclosure, when a terminal reports a QoE measurement, if the size of a QoE measurement report message (e.g., MeasurementReportAppLayer message) generated (encoded) for the report is larger than the maximum PDCP SDU size supported by the PDCP layer, the terminal may perform UL (Uplink) RRC segmentation on the QoE measurement report message. That is, the terminal RRC layer may divide the encoded QoE measurement report message into multiple segments and then include each segment in a container (e.g., rrc-MessageSegmentContainer) within a segment message (e.g., ULDedicatedMessageSegment message) and transmit it to the PDCP layer, thereby allowing the PDCP layer to process / transmit each segment message.

[0111] In one embodiment of the present disclosure, when reporting a UE capability message to a base station (e.g., 310), the terminal may report to the base station that it supports UL RRC segmentation for a QoE measurement report message (e.g., MeasurementReportAppLayer message). For example, the terminal may indicate to the base station that it supports UL RRC segmentation for the QoE measurement report message by including a ul-MeasurementReportAppLayer-Seg indicator in the UE capability message. Conversely, the terminal may indicate to the base station that it does not support UL RRC segmentation for the QoE measurement report message by not including a ul-MeasurementReportAppLayer-Seg indicator in the UE capability message.

[0112] In one embodiment of the present disclosure, the base station may allow or configure UL RRC segmentation for the terminal through a QoE measurement configuration (e.g., 340) (e.g., after receiving a report that the terminal supports UL RRC segmentation). For example, the base station may indicate to the terminal that UL RRC segmentation is allowed by including an rrc-SegAllowed indicator in the QoE measurement configuration, and conversely, may indicate to the terminal that UL RRC segmentation is not allowed by omitting the indicator.

[0113] As an embodiment of the present disclosure, a terminal may perform UL (Uplink) RRC segmentation for a QoE measurement report message if some or all of the following conditions are satisfied.

[0114] 1) When the terminal reports QoE measurement, if the size of the QoE measurement report message (e.g., MeasurementReportAppLayer message) generated (encoded) for reporting is larger than the maximum PDCP SDU size supported by the PDCP layer.

[0115] 2) If the terminal supports UL RRC segmentation

[0116] 3) When the base station allows UL RRC segmentation to the terminal

[0117] If the terminal satisfies condition 1) but does not satisfy condition 2) or / and condition 3), the terminal may delete or discard the QoE measurement report.

[0118] In one embodiment of the present disclosure, a terminal may be instructed by a base station to perform a reporting leg, but may not be permitted to perform UL RRC segmentation for the instructed leg. For example, a terminal may be instructed by a base station (MN or SN) to perform a reporting leg as MN or SRB4, but may not be permitted to perform UL RRC segmentation for QoE measurement reporting to the MN or through SRB4. Conversely, a terminal may be instructed by a base station (MN or SN) to perform a reporting leg as SN or SRB5, but may not be permitted to perform UL RRC segmentation for QoE measurement reporting to the SN or through SRB5. In this case, if a size of a QoE measurement report message (e.g., MeasurementReportAppLayer message) generated (encoded) using a QoE measurement report (e.g., 355) received from a terminal APP is larger than the maximum PDCP SDU size supported by the PDCP layer, the terminal AS may not transmit the QoE measurement report message to the base station and may delete or discard the QoE measurement report message.

[0119] However, the deletion of these QoE measurement reports means the loss of QoE or RVQoE measurement reports. That is, since the QoE information measured by the terminal APP (using computing resources) cannot be transmitted to the TCE / MCE and the base station, the QoE information cannot be used for network optimization. To solve this problem, in one embodiment of the present disclosure, the terminal can perform QoE measurement reporting using RRC segmentation using a leg (e.g., leg 2) other than the designated reporting leg (e.g., leg 1). To this end, the terminal may need to satisfy some or all of the following conditions.

[0120] 1) When the terminal reports QoE measurement, if the size of the QoE measurement report message (e.g., MeasurementReportAppLayer message) generated (encoded) for reporting is larger than the maximum PDCP SDU size supported by the PDCP layer.

[0121] 2) If the terminal does not receive permission from the base station for the UL RRC segmentation of the QoE measurement report for the reporting leg (e.g., leg 1) indicated by the base station.

[0122] 3) If the terminal receives UL RRC segmentation of QoE measurement report for leg 2 from the base station.

[0123] 4) If the terminal receives / is permitted to use a leg (e.g., leg 2) other than the reporting leg (e.g., leg 1) indicated by the base station.

[0124] For example, even if conditions 1) and 2) are satisfied, if conditions 3) or 4) are not satisfied, the terminal may not transmit the QoE measurement report message to the base station and may delete or discard it.

[0125] In one embodiment of the present disclosure, if a terminal performs QoE measurement reporting using a leg (e.g., leg 2) other than the instructed reporting leg (e.g., leg 1), the terminal may transmit to the base station a reason (cause value) for using leg 2 instead of leg 1. For example, the terminal may indicate that leg 2 is used because RRC segmentation is not allowed in leg 1 if the size of the QoE measurement report message (e.g., MeasurementReportAppLayer message) generated (encoded) for reporting is larger than the maximum PDCP SDU size supported by the PDCP layer. This is because the base station may not know the reason why leg 2 is used instead of leg 1 as instructed by the terminal, and thus it needs to inform the base station of this.

[0126] In one embodiment of the present disclosure, a terminal may send a request or preference to a base station to change a reporting leg (e.g., from leg 1 to leg 2). For example, if RRC segmentation is not allowed in a reporting leg (e.g., leg 1) in which the terminal is instructed, causing QoE measurement reports larger than the maximum PDCP SDU size supported by the PDCP layer to be deleted or discarded, the terminal may send a request or preference to the base station to change a reporting leg (e.g., from leg 1 to leg 2). The terminal may include this in a UAI (UE Assistance Information) message or a QoE measurement report message and transmit it. The base station may change the reporting leg after receiving this. When using a UAI (UE Assistance Information) message, the base station may set a prohibit timer to prevent excessive transmission of requests or preferences by the terminal. The terminal can recognize that the reporting leg change request is allowed / configured and transmit the reporting leg change request to the base station only when it receives configuration information (e.g., prohibit timer length) regarding the reporting leg change request from the base station.

[0127] In one embodiment of the present disclosure, a terminal AS may receive an instruction from a base station to change a reporting leg while transmitting a QoE measurement report via RRC segmentation, because the base station may not be aware that the terminal is transmitting via RRC segmentation.

[0128] In one embodiment of the present disclosure, if a terminal AS (RRC layer) generates a QoE measurement report message without RRC segmentation (RRC segmentation is not required) and before transmitting it to a lower layer, or after transmitting or submitting it to a lower layer and not receiving confirmation of successful transmission of the message (e.g., using leg 1) from the lower layer, and receives an instruction from the base station to change the reporting leg (e.g., from leg 1 to leg 2), the terminal AS can (re)transmit the QoE measurement report message without RRC segmentation using the newly instructed reporting leg (e.g., leg 2), and for this purpose, transmit or submit it to a lower layer.

[0129] In one embodiment of the present disclosure, if a terminal AS (RRC layer) receives an instruction from a base station to change a reporting leg (e.g., change from leg 1 to leg 2) while performing an RRC segmentation-related operation for transmitting a QoE measurement report message, and if RRC segmentation for leg 2 is allowed, the terminal may transmit all segment messages (from the first segment message to the last segment message) corresponding to the QoE measurement report message using the new reporting leg (e.g., leg 2). Even if the terminal RRC layer has transmitted some of the segment messages to a lower layer through leg 1 or has received confirmation of successful transmission from a lower layer, the terminal may transmit all segment messages (from the first segment message to the last segment message) using the new reporting leg (e.g., leg 2). In this case, it may result in a waste of resources due to duplicate transmission in which the terminal transmits some segment messages through both leg 1 and leg 2. However, since a node (MN or SN) (e.g., node 1) receiving a QoE measurement report of a terminal using leg 1 may not be able to transmit some of the segment messages it received to the node (SN or MN) (e.g., node 2) receiving it using leg 2, the terminal may transmit the first segment to node 2 using leg 2.Also, even if the terminal RRC layer has transmitted some segment messages to lower layers for transmission to leg 1, the terminal cannot guarantee that these will be successfully transmitted to node 1 at that point in time (when the terminal RRC layer receives a reporting leg change instruction from the base station while performing RRC segmentation-related operations for transmitting QoE measurement report messages). Therefore, the terminal can transmit to node 2 using leg 2 from the first segment.

[0130] In one embodiment of the present disclosure, in order to prevent waste of resources through the above-described duplicate transmission, if a terminal AS (RRC layer) receives an instruction from a base station to change a reporting leg (e.g., change from leg 1 to leg 2) while performing an RRC segmentation-related operation for transmitting a QoE measurement report message, and if RRC segmentation for leg 2 is allowed, the terminal may transmit only segment message(s) that could not be transmitted to a lower layer or whose transmission success was not confirmed by a lower layer using the new reporting leg (e.g., leg 2), excluding segment message(s) that were transmitted to a lower layer using the existing reporting leg (e.g., leg 1) or whose transmission success was confirmed by a lower layer. For the operation of the present embodiment, when the network instructs the terminal to perform a reporting leg (e.g., through consultation between the MN and the SN), node 2 may request node 1 to transmit the segment message(s) that it has received so far to node 2. Upon receiving such a request, or even without receiving such a request, node 1 can forward the segment message(s) it has received to node 2 (e.g., via the Xn interface). Consequently, node 2 can assemble the original QoE measurement report message by combining the segment message(s) it received from node 1 and the segment message(s) it received from the terminal via leg 2. In another embodiment, node 1, not node 2, can assemble the original QoE measurement report message by collecting all segment messages.That is, node 1 stores the segment message(s) it has received, and node 2 can use leg 2 to receive the remaining segment message(s) (up to the last segment message) and forward them to node 1 (e.g., via the Xn interface). Then, node 1 can assemble all segment messages into the original QoE measurement report message.

[0131] In one embodiment of the present disclosure, in order to prevent waste of resources through duplicate transmission, if the network instructs the terminal to change the reporting leg (e.g., change from leg 1 to leg 2) while the terminal AS (RRC layer) is performing an operation related to RRC segmentation for transmitting a QoE measurement report message and allows the terminal to perform RRC segmentation for leg 2, the network (node ​​1 or node 2) may indicate to the terminal through leg 1 which segment message it has successfully received so far (e.g., by indicating a segment sequence number (segmentNumber)). Alternatively, the network may instruct the terminal through leg 2 from which segment message it should transmit (e.g., by indicating a segment sequence number (segmentNumber)). The terminal that has received this instruction may sequentially transmit through leg 2, starting from a segment message successfully transmitted through leg 1 or from the instructed segment message, in accordance with the sequence number.

[0132] In one embodiment of the present disclosure, if a terminal AS (RRC layer) receives an instruction from a base station to change a reporting leg (e.g., change from leg 1 to leg 2) while performing an RRC segmentation-related operation for transmitting a QoE measurement report message, and if RRC segmentation for leg 2 is not permitted, all (remaining) segments messages corresponding to the QoE measurement report message can be deleted.

[0133] In one embodiment of the present disclosure, if a terminal AS (RRC layer) receives an instruction from a base station to change a reporting leg (e.g., change from leg 1 to leg 2) while performing an RRC segmentation-related operation for transmitting a QoE measurement report message, and RRC segmentation for leg 2 is not permitted, the terminal may operate by referring to the embodiment described above. For example, even if leg 2 is instructed, the terminal may autonomously select leg 1, in which RRC segmentation is permitted, and perform a QoE measurement report. For example, the terminal may request the base station to change the reporting leg.

[0134] In one embodiment of the present disclosure, when a terminal transmits a QoE measurement report to SRB5 (SN) using RRC segmentation (e.g., a reporting leg is indicated as SN or SRB5), and the SCG (Secondary cell group) setting is released or deactivated, if RRC segmentation for SRB4 or MN is allowed to the terminal, the terminal may stop transmitting the segment message for the QoE measurement report message and store it. This may be for the purpose of temporarily storing it so that the terminal can transmit it to the MN later when the base station changes the reporting leg to the MN, or for the purpose of temporarily storing it so that the terminal can transmit it to the SN later when the base station (re)activates the SCG.

[0135] In the former case, when the base station changes the reporting leg to MN or SRB4, the terminal may transmit to the MN all segment messages corresponding to the QoE measurement report message or only some messages (those that were not transmitted to the lower layer or whose transmission success was not confirmed by the lower layer) according to the preceding embodiment. For detailed contents of the related invention, please refer to the preceding embodiment.

[0136] In one embodiment of the present disclosure, when a terminal transmits a QoE measurement report using RRC segmentation to SRB5 (to SN) (e.g., when the reporting leg is indicated as SN or SRB5), and the SCG (Secondary cell group) setting is released or deactivated, if RRC segmentation for SRB4 or MN is allowed to the terminal, the terminal may operate with reference to the embodiment described above. For example, even though the reporting leg is indicated as SN or SRB5, the terminal may autonomously change / select a reporting leg in which RRC segmentation is allowed to MN or SRB4 to perform a QoE measurement report. For example, the base station may request a change in the reporting leg.

[0137] In one embodiment of the present disclosure, when the SCG (Secondary cell group) setting is released or deactivated during the process of transmitting a QoE measurement report using RRC segmentation to SRB5 (to SN) by the terminal (e.g., when the reporting leg is indicated to SN or SRB5), if RRC segmentation for SRB4 or MN is not allowed to the terminal, the terminal may delete or discard all (remaining) segment messages.

[0138] In one embodiment of the present disclosure, a separate reporting leg can be defined for RAN visible QoE (RVQoE) measurement reporting. For example, a base station can configure one reporting leg for encapsulated QoE measurement reporting (a QoE measurement report using a conventional container, not an RVQoE QoE measurement report) to a terminal, and can also configure a separate reporting leg for RVQoE measurement reporting. In one embodiment of the present disclosure, the base station can designate each reporting leg as a different leg, or can designate a common leg. In one embodiment of the present disclosure, each reporting leg can be configured by a different node (MN or SN), or a single node can configure both reporting legs. In one embodiment of the present disclosure, negotiation can be performed between the MN and the SN to configure each reporting leg.

[0139] The terminal can report to the base station some or all of the following parameters using the reporting leg for encapsulated QoE measurement reporting.

[0140] 1) QoE configuration or measurement ID (e.g. measConfigAppLayerId)

[0141] 2) A container containing the QoE measurement report (e.g., measReportAppLayerContainer)

[0142] 3) Parameters that indicate the start or end of a QoE measurement session (e.g., appLayerSessionStatus)

[0143] The terminal can report to the base station some or all of the following parameters using the reporting leg for RVQoE measurement reporting.

[0144] 1) QoE configuration or measurement ID (e.g. measConfigAppLayerId)

[0145] 2) Parameters containing RVQoE measurement reports (e.g., ran-VisibleMeasurements, appLayerBufferLevelList, playoutDelayForMediaStartup, pdu-SessionIdList)

[0146] 3) Parameters that indicate the start or end of a QoE measurement session (e.g., appLayerSessionStatus)

[0147] If the reporting leg for RVQoE measurement report is not configured, or if the reporting leg for encapsulated QoE measurement report and the reporting leg for RVQoE measurement report point to a common leg, the terminal may report to the base station some or all of the following parameters.

[0148] 1) QoE configuration or measurement ID (e.g. measConfigAppLayerId)

[0149] 2) A container containing the QoE measurement report (e.g., measReportAppLayerContainer)

[0150] 3) Parameters that indicate the start or end of a QoE measurement session (e.g., appLayerSessionStatus)

[0151] 4) Parameters containing RVQoE measurement reports (e.g., ran-VisibleMeasurements, appLayerBufferLevelList, playoutDelayForMediaStartup, pdu-SessionIdList)

[0152] In one embodiment of the present disclosure, a base station may provide an indicator A to a terminal to indicate a reporting leg for RVQoE measurement reporting. Indicator A may be included in a QoE configuration or an RVQoE configuration (e.g., 420 or 510). Indicator A may be configured (with different values) for each QoE configuration ID. If the terminal does not receive indicator A, an encapsulated QoE measurement reporting reporting leg may be used for RVQoE measurement reporting. If the terminal receives a value where the indicator A is set to value 1 (e.g., "otherLeg), it may use a different leg for reporting encapsulated QoE measurement reports (for the corresponding QoE configuration ID). If the terminal receives a value where the indicator A is set to value 2 (e.g., "bothLeg), it may transmit the RVQoE measurement reports (for the corresponding QoE configuration ID) to both the MN and the SN. This is because both the MN and the SN may be interested in the RVQoE measurements (for the corresponding QoE configuration ID). For example, the MN and the SN may simultaneously set up a bearer and provide the service together to provide a VR service to the terminal for the corresponding application. In one embodiment, the indicator A may be provided to the terminal by one of the nodes through an agreement between the MN and the SN.

[0153] In one embodiment of the present disclosure, a base station may provide an indicator B to a terminal to indicate a reporting leg for an RVQoE measurement report to the terminal. The indicator B may be included in a QoE configuration or an RVQoE configuration (e.g., 420 or 510). The indicator B may be configured (with different values) for each QoE configuration ID. If the terminal receives the indicator B from the MN, the terminal may transmit a corresponding RVQoE report to the MN (via SRB4) (meaning that the reporting leg for the RVQoE measurement report is the MN or SRB4). The MN may transmit the indicator B directly via SRB1 or may forward it to the terminal through the SN in the form of an encapsulated message to the SN to SRB3. If the terminal receives the indicator B from the SN, the terminal may transmit a corresponding RVQoE report to the SN (via SRB5) (meaning that the reporting leg for the RVQoE measurement report is the SN or SRB5). The SN can transmit the indicator B directly over SRB3 or can forward it to the terminal through the MN over SRB1 in the form of an encapsulated message.

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

[0155] 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). The configuration of the terminal is not limited to the exemplary configuration illustrated in FIG. 8, and may include fewer or more configurations than the configuration illustrated in FIG. 8.

[0156] 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 then 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 beamforming, the RF processing unit (810) can adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO and receive multiple layers when performing the MIMO operation. The RF processing unit (810) can perform reception beam sweeping by appropriately setting multiple antennas or antenna elements according to the control of the control unit, or adjust the direction and beam width of the reception beam so that the reception beam is coordinated with the transmission beam.

[0157] According to one embodiment of the present disclosure, 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 orthogonal frequency division multiplexing (OFDM) 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.

[0158] According to one embodiment of the present disclosure, 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 wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, different frequency bands may include super high frequency (SHF) (e.g., 2.NRHz, NRhz) bands, millimeter wave (mm wave) (e.g., 60GHz) bands.

[0159] According to one embodiment of the present disclosure, 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) may store information related to a second access node that performs wireless communication using wireless access technology. Furthermore, the storage unit (830) provides the stored data upon request from the control unit (840). Furthermore, the storage unit (830) may also store a program for performing a method according to the present disclosure.

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

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

[0162] 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). The configuration of the base station is not limited to the exemplary configuration illustrated in FIG. 9, and may include fewer or more configurations than the configuration illustrated in FIG. 9. In addition, according to an embodiment of the present disclosure, a network entity (or network function) may have the same or similar configuration as the base station of FIG. 9. For example, an AMF entity may have the same or similar configuration as the base station of FIG. 9.

[0163] According to one embodiment of the present disclosure, 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 a baseband signal provided from the baseband processing unit (920) into an RF band signal and transmits it through an antenna, and down-converts an 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 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 RF processing unit can perform downlink MIMO operations by transmitting one or more layers.

[0164] According to one embodiment of the present disclosure, the baseband processing unit (920) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of a 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 an 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 the 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.

[0165] According to one embodiment of the present disclosure, the backhaul communication unit (930) provides an interface for performing communication with other nodes within the network. That is, the backhaul communication unit (930) converts a bit stream transmitted from a primary base station to other nodes, such as an auxiliary base station or a core network, into a physical signal, and converts a physical signal received from other nodes into a bit stream.

[0166] According to one embodiment of the present disclosure, the storage unit (940) stores data such as basic programs, application programs, and configuration information for the operation of the primary base station. In particular, the storage unit (940) may store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (940) may store information that serves as a basis for determining whether to provide or terminate multiple connections to the terminal. In addition, the storage unit (940) provides the stored data upon request from the control unit (950). In addition, the storage unit (930) may also store a program for performing a method according to the present disclosure.

[0167] 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, as illustrated in the drawing, may include a multi-connection processing unit (952).

[0168] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0169] 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 embodiments described in the claims or specification of the present disclosure.

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

[0171] Additionally, the program may be stored on 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.

[0172] In this disclosure, the term "computer program product" or "computer-readable medium" is used to collectively refer to media such as memory, a hard disk installed in a hard disk drive, and signals. These "computer program products" or "computer-readable mediums" are components provided in a method for reporting terminal capabilities in a wireless communication system according to the present disclosure.

[0173] A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory storage medium" simply means a tangible device that does not contain signals (e.g., electromagnetic waves). This term does not distinguish between cases where data is permanently stored in the storage medium and cases where data is temporarily stored. For example, a "non-transitory storage medium" may include a buffer in which data is temporarily stored.

[0174] According to one embodiment, the method according to various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., a downloadable app) may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0175] In the specific embodiments of the present disclosure described above, components included in the invention are expressed in the singular or plural form, 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. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.

[0176] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modified examples based on the technical idea of ​​the present disclosure are possible. In addition, each embodiment can be combined and operated as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined to operate a base station and a terminal. In addition, the embodiments of the present disclosure can be applied to other communication systems, and other modified examples based on the technical idea of ​​the embodiments can also be implemented. For example, the embodiments can 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 determined not only by the scope of the following claims but also by equivalents of the claims.

Claims

1. A method performed by a terminal of a wireless communication system, A step of receiving a message including setting information regarding QoE (Quality of Experience) from a base station; and A step of transmitting a message for reporting QoE measurement results based on the above setting information is included, The above setting information is, Including information indicating a first SRB (signaling radio bearer) for encapsulated QoE measurement reporting and information indicating a second SRB for RAN (radio access network) visible QoE measurement reporting. method.

2. In paragraph 1, When the above first SRB and the above second SRB are the same: A message for reporting the above QoE measurement result is transmitted through the first SRB or the second SRB, The message for reporting the above QoE measurement results is: Containing at least one of identifier information for the above configuration information, container information for the encapsulated QoE measurement report, information indicating start or end for a QoE measurement session, and information for the RAN visible QoE measurement report. method.

3. In paragraph 1, If the above first SRB and the above second SRB are different: The step of sending a message to report the above QoE measurement results is: A step of transmitting a first message for the encapsulated QoE measurement report through the first SRB; and A step of transmitting a second message for reporting the above RAN (radio access network) visible QoE measurement through the second SRB, method.

4. In paragraph 3, The first message above is, Contains at least one of identifier information for the above configuration information, container information for the encapsulated QoE measurement report, and information indicating start or end of a QoE measurement session; The second message above is, Contains identifier information for the above setting information and information for the RAN visible QoE measurement report, The above base station includes a master base station or a secondary base station of NR-DC (new radio dual connectivity). method.

5. A method performed by a base station of a wireless communication system, A step of transmitting a message including setting information regarding QoE (Quality of Experience) to a terminal; and A step of receiving a message for reporting a QoE measurement result based on the setting information from the terminal, The above setting information is, Including information indicating a first SRB (signaling radio bearer) for encapsulated QoE measurement reporting and information indicating a second SRB for RAN (radio access network) visible QoE measurement reporting. method.

6. In paragraph 5, When the above first SRB and the above second SRB are the same: A message for reporting the above QoE measurement result is received through the first SRB or the second SRB, The message for reporting the above QoE measurement results is: Containing at least one of identifier information for the above configuration information, container information for the encapsulated QoE measurement report, information indicating start or end for a QoE measurement session, and information for the RAN visible QoE measurement report. method.

7. In paragraph 5, If the above first SRB and the above second SRB are different: The step of receiving a message for reporting the above QoE measurement results is: A step of receiving a first message for the encapsulated QoE measurement report through the first SRB or a second message for the RAN visible QoE measurement report through the second SRB, method.

8. In paragraph 7, The first message above is, Contains at least one of identifier information for the above configuration information, container information for the encapsulated QoE measurement report, and information indicating start or end of a QoE measurement session; The second message above is, Containing identifier information for the above setting information and information for the RAN visible QoE measurement report, method.

9. In the terminal of a wireless communication system, Transmitter and receiver; and Including a control unit connected to the above transmitter and receiver, The above control unit: Receive a message from a base station containing configuration information regarding QoE (Quality of Experience), It is set to transmit a message for reporting QoE measurement results based on the above setting information, The above setting information is, Including information indicating a first SRB (signaling radio bearer) for encapsulated QoE measurement reporting and information indicating a second SRB for RAN (radio access network) visible QoE measurement reporting. Terminal.

10. In paragraph 9, When the above first SRB and the above second SRB are the same: A message for reporting the above QoE measurement result is transmitted through the first SRB or the second SRB, The message for reporting the above QoE measurement results is: Containing at least one of identifier information for the above configuration information, container information for the encapsulated QoE measurement report, information indicating start or end for a QoE measurement session, and information for the RAN visible QoE measurement report. Terminal.

11. In paragraph 9, If the above first SRB and the above second SRB are different: the control unit, Reporting the first message for the encapsulated QoE measurement report through the first SRB, A second message for reporting the above RAN (radio access network) visible QoE measurement is set to be reported through the second SRB. Terminal.

12. In paragraph 11, The first message above is, Contains at least one of identifier information for the above configuration information, container information for the encapsulated QoE measurement report, and information about the start or end of the QoE measurement session, The second message above is, Contains identifier information for the above setting information and information for the RAN visible QoE measurement report, The above base station includes a master base station or a secondary base station of NR-DC (new radio dual connectivity). Terminal.

13. In a base station of a wireless communication system, Transmitter and receiver; and Including a control unit connected to the above transmitter and receiver, The above control unit: Transmits a message containing setting information regarding QoE (Quality of Experience) to the terminal, It is configured to receive a message for reporting QoE measurement results based on the above setting information from the terminal, The above setting information is, Including information indicating a first SRB (signaling radio bearer) for encapsulated QoE measurement reporting and information indicating a second SRB for RAN (radio access network) visible QoE measurement reporting. Base station.

14. In paragraph 13, When the above first SRB and the above second SRB are the same: A message for reporting the above QoE measurement result is received through the first SRB or the second SRB, The message for reporting the above QoE measurement results is: Containing at least one of identifier information for the above configuration information, container information for the encapsulated QoE measurement report, information indicating start or end for a QoE measurement session, and information for the RAN visible QoE measurement report. Base station.

15. In paragraph 13, If the above first SRB and the above second SRB are different: the control unit, The first message for the encapsulated QoE measurement report is set to be received through the first SRB, or the second message for the RAN (radio access network) visible QoE measurement report is set to be received through the second SRB, The first message above is, Contains at least one of identifier information for the above setting information, container information for the QoE measurement result, and start or end information for the QoE measurement session, The second message above is, Containing identifier information for the above setting information and information for the RAN visible QoE measurement report, Base station.

Images