Method and apparatus for measuring qoe in inactive mode and standby mode in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the present disclosure relates to a method performed by a terminal in a wireless communication system, and the method may comprise the steps of: receiving, from a base station, a message including configuration information related to a quality of experience (QoE) measurement; and, if the configuration information includes indication information indicating whether to permit transmission of a QoE measurement report collected in a radio resource control (RRC) idle state and / or an RRC inactive state and whether to permit transmission of a QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state, transmitting, to the base station, a QoE measurement report collected in the RRC idle state and / or the RRC inactive state, and / or a QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state.

Description

Method and device for measuring QOE in inactive mode and standby mode in wireless communication system

[0001] The present disclosure relates to a wireless communication system (or mobile communication system). Specifically, the present disclosure relates to a method for measuring quality of experience (QoE) in a radio resource control (RRC) inactive mode or RRC standby (or idle) mode in a wireless communication system (or mobile communication system).

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

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

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

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

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

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

[0008] Meanwhile, with the recent development of communication systems, the demand for methods to efficiently measure and report QoE is increasing day by day.

[0009] The present disclosure is intended to improve the QoE measurement process, and in particular, to propose a process for efficiently measuring QoE in RRC inactive mode or RRC idle mode.

[0010] In a method performed by a terminal in a wireless communication system according to one embodiment of the present disclosure, the method may include: receiving, from a base station, a message including configuration information related to quality of experience (QoE) measurement; and, if the configuration information includes indication information indicating whether to allow transmission of a quality of experience (QoE) measurement report collected in a radio resource control (RRC) idle state and / or an RRC inactive state and whether to allow transmission of a QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state, the method may include: transmitting, to the base station, a QoE measurement report collected in the RRC idle state and / or the RRC inactive state and / or a QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state.

[0011] In a method performed by a base station in a wireless communication system according to one embodiment of the present disclosure, the method may include the steps of: transmitting, to a terminal, a message including configuration information related to quality of experience (QoE) measurement; and, if the configuration information includes indication information indicating whether to allow transmission of a quality of experience (QoE) measurement report collected in a radio resource control (RRC) idle state and / or an RRC inactive state and whether to allow transmission of a QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state, performing the step of receiving, from the terminal, a QoE measurement report collected in the RRC idle state and / or the RRC inactive state and / or a QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state.

[0012] In a wireless communication system according to one embodiment of the present disclosure, a terminal includes a transceiver; and a controller connected to the transceiver, wherein the controller is configured to receive, from a base station, a message including configuration information related to quality of experience (QoE) measurement, and, when the configuration information includes instruction information indicating whether to allow transmission of a quality of experience (QoE) measurement report collected in a radio resource control (RRC) idle state and / or an RRC inactive state and whether to allow transmission of a QoE measurement setting applicable to the RRC idle state and / or the RRC inactive state, transmit to the base station the QoE measurement report collected in the RRC idle state and / or the RRC inactive state and / or the QoE measurement setting applicable to the RRC idle state and / or the RRC inactive state.

[0013] In a wireless communication system according to one embodiment of the present disclosure, a base station comprises: a transceiver; and a controller connected to the transceiver, wherein the controller is configured to transmit, to a terminal, a message including configuration information related to quality of experience (QoE) measurement, and when the configuration information includes instruction information indicating whether to allow transmission of a quality of experience (QoE) measurement report collected in a radio resource control (RRC) idle state and / or an RRC inactive state and whether to allow transmission of a QoE measurement setting applicable to the RRC idle state and / or the RRC inactive state, the controller may be configured to receive, from the terminal, a QoE measurement report collected in the RRC idle state and / or the RRC inactive state and / or a QoE measurement setting applicable to the RRC idle state and / or the RRC inactive state.

[0014] According to various embodiments proposed in the present disclosure, the process of measuring and reporting QoE in RRC inactive mode and RRC idle mode can be performed efficiently.

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

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

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

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

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

[0020] FIG. 6 is a flowchart illustrating a setup and reporting procedure for a terminal to support QoE measurement in connected mode as well as inactive and standby mode according to one embodiment of the present disclosure.

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

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

[0023] Figure 9 illustrates the configuration of a terminal according to one embodiment of the present disclosure.

[0024] FIG. 10 illustrates a configuration of a base station according to an embodiment of the present disclosure.

[0025] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0026] The various embodiments of the present disclosure described below may illustrate a hardware-based approach. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0027] In the following description, terms referring to components of the device (control unit, processor, artificial intelligence (AI) model, encoder, decoder, autoencoder (AE), neural network (NN) model, etc.) and terms referring to data (signal, feedback, report, reporting, information, parameter, value, bit, codeword, etc.) are examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

[0028] Additionally, while this disclosure describes various embodiments using terminology used in certain communication standards (e.g., 3rd Generation Partnership Project (3GPP)), these are merely illustrative examples. The various embodiments of this disclosure can be easily modified and applied to other communication systems.

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

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

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

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

[0033] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, 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 can create a means for performing the functions described in the flow diagram block(s).

[0034] These computer program instructions may also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing device to implement a function in a particular manner, so that the instructions stored in the computer-available or computer-readable memory can also produce an article of manufacture that includes instruction means for performing the function described in the flowchart block(s).

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

[0036] 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 mentioned 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.

[0037] Here, the term "~unit" used in this embodiment refers to software or hardware components such as FPGAs or ASICs, and the "~unit" can perform certain roles. However, the "~unit" is not limited to software or hardware. The "~unit" may be configured to reside on an addressable storage medium or may be configured to play one or more processors.

[0038] Thus, as an example, '~bu' may include components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.

[0039] The functionality provided within the components and '~sub-units' may be combined into a smaller number of components and '~sub-units' or further separated into additional components and '~sub-units'. Furthermore, the components and '~sub-units' may be implemented to activate one or more CPUs within the device or secure multimedia card. Furthermore, in an embodiment, the '~sub-unit' may include one or more processors.

[0040] 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, and terms referring to various identification information 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.

[0041] For convenience of explanation, this disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) LTE (Long Term Evolution) standard or the New Radio (NR) standard. However, this disclosure is not limited to these terms and names and can be equally applied to systems conforming to other standards.

[0042] Hereinafter, a base station (BS) is an entity that performs resource allocation of a terminal, and may be at least one of a radio access network (RAN) node, a next generation node B (gNB), an evolved node B (eNB), a Node B, a wireless access unit, a base station controller, or a node on a network. In the present disclosure, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as an eNB may represent a gNB.

[0043] Hereinafter, a 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 communication functions. Of course, the above examples are not limited thereto.

[0044] In particular, the present disclosure is applicable to 3GPP NR (the 5th generation mobile communications standard). Furthermore, the present disclosure may be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart or connected cars, healthcare, digital education, retail, security, and safety-related services) based on 5G communication technology and IoT (Internet of Things)-related technologies. Furthermore, the term "terminal" may refer to not only mobile phones, NB-IoT devices, and sensors, but also other wireless communication devices.

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

[0046] 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 (or UE) transmits data or control signals to a base station (or eNB, gNB), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method distinguishes the data or control information of each user by allocating and operating the time-frequency resources to be transmitted to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0047] As a future communications system beyond LTE, 5G communications 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 communications systems include enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable low-latency communications (URLLC).

[0048] In one embodiment, eMBB may aim to provide data transmission 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 the increased user-perceived data rate of a terminal. To meet these requirements, a 5G communication system may require improvements in various transmission and reception technologies, including improved multiple-input multiple-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 transmission rates required by the 5G communication system.

[0049] 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 / km^2) 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, very long battery lifespans, such as 10 to 15 years, may be required.

[0050] 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 of a packet error rate (PER) of 10^-5 or less. Therefore, for services supporting URLLC, 5G systems may be required to provide a smaller transmission 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.

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

[0052] Furthermore, although embodiments of the present disclosure are described below using LTE, LTE-A, LTE Pro, 5G (or NR), or 6G systems as examples, the embodiments of the present disclosure may also be applied to other communication systems having 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.

[0053] Hereinafter, a / b may mean a and / or b.

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

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

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

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

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

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

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

[0061] - Cell re-selection mobility;

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

[0063] - The UE AS (Access Stratum) context is stored in at least one gNB and the UE;

[0064] - Paging is initiated by NR RAN;

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

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

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

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

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

[0070]

[0071]

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

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

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

[0075]

[0076]

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

[0078]

[0079]

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

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

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

[0083]

[0084]

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

[0086]

[0087]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0105] According to one embodiment of the present disclosure, the QoE configuration information (e.g., 335 or 415) received by the base station may include area scope information (e.g., AreaScope). The base station can use this information to determine the area scope in which the terminal should perform QoE measurements in connected mode. For example, if the terminal moves out of the area scope, the base station can cancel the QoE configuration, thereby suspending the terminal's QoE measurements.

[0106] According to one embodiment of the present disclosure, the QoE configuration information (e.g., 350 or 430) received by the terminal application layer (terminal APP or UE APP) may include area range information (e.g., LocationFilter). The terminal APP can use the information to determine the area range in which the terminal should perform QoE measurements. For example, if the terminal APP moves out of the area range, a new QoE measurement session may not be initiated. However, the terminal may continue the ongoing QoE measurement session (e.g., unless it requests QoE configuration from the base station).

[0107] FIG. 6 is a flowchart illustrating a setup and reporting procedure for a terminal to support QoE measurement in connected mode as well as inactive and standby mode according to one embodiment of the present disclosure.

[0108] 3GPP standardized support for QoE measurements in connected mode in Release 17. Expanding on this, 3GPP is currently standardizing a method to support QoE measurements in not only connected mode (RRC_CONNECTED), but also inactive mode (RRC_INACTIVE) and idle (RRC_IDLE) modes in Release 18 to support QoE measurements for Multicast Broadcast Service (MBS) services. For Multicast Broadcast Service (MBS) services, the QoE configuration / measurement / reporting procedures between UEs and eNBs in not only connected mode (RRC_CONNECTED), but also inactive mode (RRC_INACTIVE) and idle (RRC_IDLE) modes can be as follows.

[0109] At step 615, the base station (605) and the terminal AS (610) may establish (or establish) an RRC connection.

[0110] In step 620, the base station may transmit a UE Capability request message (e.g., UECapabilityEnquiry) to the terminal, and the terminal, upon receiving the message, may transmit a UE Capability message (e.g., UECapabilityInformation) to the base station. The terminal may include a QoE measurement-related support capability indicator in the UE Capability message and transmit it. For example, the terminal may transmit to the base station whether it supports QoE measurement for an MBS (e.g., broadcast) service. For example, the terminal may transmit to the base station whether it supports QoE measurement in not only a connected mode (RRC_CONNECTED), but also an inactive mode (RRC_INACTIVE) and an idle mode (RRC_IDLE). Step 620 may correspond to step 425 or step 310.

[0111] In steps 625 and 627, the base station may provide QoE configuration information to the terminal. Step 625 may correspond to steps 420 and 430, or steps 340 and 350. For example, the QoE configuration information may include QoE measurement configuration information for an MBS (e.g., broadcast) service. For example, the QoE configuration information may include configuration information for QoE measurement in connected mode (RRC_CONNECTED), inactive mode (RRC_INACTIVE), and standby (RRC_IDLE) mode.

[0112] In step 630, when the terminal AS is in a connection mode, the terminal APP can perform QoE measurement for the MBS service using the QoE setting information (e.g., when the MBS service is received).

[0113] In step 632, the terminal APP may transmit QoE measurement results or measurement reports for the MBS service to the terminal AS layer. Step 632 may correspond to step 355 or 435.

[0114] In step 635, the terminal AS may report the QoE measurement report received from the terminal APP layer to the base station. For example, if the terminal is in connected mode and the base station has configured an SRB (SRB4 or SRB5) for QoE measurement reporting, the QoE measurement report may be reported to the base station immediately. Step 635 may correspond to step 360 or 440.

[0115] In step 640, the base station sends an RRC Release message to the terminal, and the terminal receiving the message can transition to inactive mode or standby mode. The terminal can receive MBS services even in inactive mode or standby mode.

[0116] In step 645, the terminal APP can perform QoE measurement (using the QoE configuration information received in step 625) on the MBS service while the AS is in an inactive or standby mode.

[0117] In step 647, the terminal APP can transmit the QoE measurement result or measurement report generated through QoE measurement to the terminal AS.

[0118] In step 648, the terminal AS may store the QoE measurement report without immediately transmitting it to the base station because it is in an inactive or standby mode. For example, the terminal APP may transmit the generated QoE measurement report to the terminal AS, and the terminal AS may store it.

[0119] At step 650, the terminal may establish (or establish) an RRC connection with the (new) base station (e.g., RRC Setup or RRC resume).

[0120] In step 655, when the terminal establishes the RRC connection in step 650, the terminal may indicate to the base station that it is storing (e.g., availability) QoE measurement reports (e.g., measured in inactive / standby mode) via the RRCSetupComplete or RRCResumeComplete message.

[0121] In step 660, the base station that has received the availability may allow the terminal to perform QoE measurement reporting by setting an SRB (e.g., SRB4 or SRB5) for transmitting a QoE measurement report to the terminal, and the terminal may perform QoE measurement reporting.

[0122] In one embodiment of the present disclosure, the terminal may transition to a standby mode at step 640. The terminal transitioned to the standby mode may store / maintain QoE settings even in the standby mode in order to perform MBS QoE measurement (645). However, when the terminal establishes an RRC connection with a new base station (650), the base station may not have the MBS QoE settings of the terminal. Therefore, the base station may need to retrieve the QoE settings of the terminal. The base station may retrieve the QoE settings of the terminal from the terminal or the AMF (CN). In a method for the base station to retrieve QoE settings information from the terminal (UE-based solution), the terminal may store the QoE settings information (625) provided by the previous base station, and then transfer the same to the new base station after going through the standby mode and establishing an RRC connection with the new base station (650). In a method in which a base station retrieves QoE configuration information from a CN (CN-based solution), the CN stores the QoE configuration information and, after a terminal enters standby mode and establishes an RRC connection (650) with a new base station, the CN can transfer the information to the new base station. Each QoE configuration information of the terminal retrieved by the new base station may include some or all of the following.

[0123] - QoE reference

[0124] - TCE or MCE address or ID

[0125] - RRC level QoE configuration ID (e.g. measConfigAppLayerId)

[0126] - Service type

[0127] - QoE measurement type (whether signaling-based QoE setting or management-based QoE setting).

[0128] - Available RAN visible QoE indicator information

[0129] - Area information where new QoE measurements can be performed or initiated

[0130] By retrieving the above information or by obtaining information about the QoE settings set for the terminal, the new base station can add / change / release the QoE settings of the terminal thereafter, and can forward the QoE measurement report received from the terminal to the correct TCE / MCE.

[0131] The first issue to be solved in the present disclosure is as follows. When a standby mode terminal establishes an RRC connection with a new base station (650), the terminal can indicate to the base station (655) that it is storing (e.g., availability) QoE measurement reports (e.g., measured in standby mode) through RRCSetupComplete. And when using a UE-based solution, the terminal can provide MBS QoE settings to the base station. However, the base station may be a base station that does not support MBS QoE measurement (or QoE measurement in inactive / standby mode). For example, the MBS QoE measurement (or QoE measurement in inactive / standby mode) function is a technology introduced in Release 18, and a Release 17 base station may not support the function. Furthermore, a Release 18 base station may not support the function. Alternatively, the base station may be a base station that does not require the information even if it supports MBS QoE measurement (or QoE measurement in inactive / standby mode). In such cases, the UE providing the BS with MBS QoE settings can be a waste of radio resources and UE energy. This is because BSs that do not support or require MBS QoE measurement (or QoE measurement in inactive / standby mode) may not understand or use the MBS QoE settings provided by the UE. Furthermore, since the MBS QoE settings provided by the UE to the BS may include various information as listed above, the size of the information may be large, which may lead to significant waste of radio resources and UE energy.

[0132] To address the above issue, in one embodiment of the present disclosure, the base station may instruct the terminal on some or all of the following information.

[0133] - Support for Release 18 QoE measurement at base stations

[0134] - Support for MBS QoE measurement at base stations

[0135] - Support for QoE measurement in base station inactive / standby mode

[0136] - Whether to allow transmission of MBS QoE settings of the terminal

[0137] - Whether to allow transmission of QoE settings for the terminal's inactive / standby mode

[0138] - Whether to request a recall of the base station's MBS QoE settings

[0139] - Whether to request recall of base station's inactive / standby mode QoE settings

[0140] For example, if the base station transmits the indicator (e.g., indicator A) to the terminal by including it or setting it to "true", it may mean the support or transmission permission or recovery request. The terminal receiving this may transmit the MBS QoE (or QoE in inactive / standby mode) setting to the base station. Conversely, if the base station does not include the indicator (e.g., indicator A) or sets it to "false" and transmits it to the terminal, it may mean the support is not possible or transmission is not permitted or recovery is not requested. The terminal receiving this may not transmit the MBS QoE (or QoE in inactive / standby mode) setting to the base station. This can prevent unnecessary waste of radio resources and unnecessary energy usage of the terminal.

[0141] In one embodiment of the present disclosure, the indicator A may be included in an RRCSetup message (650) or a system information message (SIB, receivable before transitioning to connected mode). In this case, if the base station does not include the indicator A in the message or sets it to “false” and transmits it to the terminal, the terminal may not transmit the MBS QoE (or QoE in inactive / standby mode) configuration to the base station, and may not transmit the availability indicator either. This is because a base station that does not support or does not require MBS QoE measurement (or QoE measurement in inactive / standby mode) may not require the availability indicator either.

[0142] In one embodiment of the present disclosure, the indicator A may be defined in an RRCReconfiguration message or a UEInformationRequest message.

[0143] The second issue to be solved in the present disclosure is as follows. A terminal in an inactive mode or standby mode can transition to a connected mode while maintaining MBS QoE (or QoE in inactive / standby mode) measurement / configuration at 650. In the case of a terminal in an inactive mode, the base station can restore the MBS QoE (or QoE in inactive / standby mode) configuration for the terminal. Even in the case of a terminal in an standby mode, the base station can retrieve / restore the MBS QoE (or QoE in inactive / standby mode) configuration for the terminal through a UE-based or CN-based solution. However, if the base station is a base station that does not support or does not require MBS QoE measurement (or QoE measurement in inactive / standby mode), the MBS QoE (or QoE in inactive / standby mode) configuration for the terminal may or may not be retrieved or restored. However, since the terminal has MBS QoE (or QoE in inactive / standby mode) settings, it can perform QoE measurements and report QoE measurements to the base station. Since such base stations do not support or require MBS QoE measurements (or QoE measurements in inactive / standby mode), QoE measurements and reports of such terminals may be unnecessary, which may waste energy of the terminal and radio resources.

[0144] To address the above issue, in a first embodiment of the present disclosure, when a terminal receives a message from a base station that does not include the indicator A or is set to “false” (e.g., meaning that the base station does not support or does not require MBS QoE measurement (or QoE measurement in inactive / standby mode)), the terminal may release or erase the MBS QoE measurement (or QoE measurement in inactive / standby mode) setting it has. This allows the terminal to no longer perform MBS QoE measurement (or QoE measurement in inactive / standby mode) and to no longer perform QoE measurement reporting to the base station. This allows the terminal and the base station to have the same QoE setting.

[0145] To address the above issue, in a second embodiment of the present disclosure, if the terminal receives a message from the base station that does not include the indicator A or is set to “false” (e.g., meaning that the base station does not support or does not require MBS QoE measurement (or QoE measurement in inactive / standby mode)), the terminal may maintain MBS QoE measurement (or QoE measurement in inactive / standby mode) and configuration, but may not transmit a QoE report accordingly to the base station. Instead, the terminal may store a QoE report generated as a result of the QoE measurement. In this case, although the terminal and the base station may not have the same QoE settings (because the base station cannot have / retrieve the MBS QoE settings; the problems and solutions arising from this are described later), the terminal can continuously perform MBS QoE measurements (or QoE measurements in inactive / standby mode) even when connected to a new cell or base station, and has the advantage of storing QoE measurement reports (even if they cannot be reported immediately) and transmitting them later when an RRC connection is established with another base station that supports or requires MBS QoE measurements. As a result, the TCE / MCE side that collects QoE measurement results can collect QoE measurement reports measured without interruption and utilize them for network optimization. The QoE measurement reports stored above may be measurement reports that the terminal stores in a connected mode, and these measurement reports may be stored together in the memory that the terminal uses to store QoE measurement reports (648) in the inactive / standby mode.

[0146] The above two embodiments assume not only a case where a standby mode terminal transitions to a connected mode, but also a case where an inactive mode terminal transitions to a connected mode. Accordingly, indicator A can be used not only when a standby mode terminal transitions to a connected mode, but also when an inactive mode terminal transitions to a connected mode. Accordingly, in one embodiment of the present disclosure, indicator A can be defined in an RRCSetup message (650) as well as an RRCResume message (650).

[0147] In the second embodiment, the terminal maintains the MBS QoE settings, but the base station cannot retain / retrieve the settings. This may cause the following issues: the base station does not know the ID (e.g., measConfigAppLayerId) for the MBS QoE settings of the terminal, and if the base station needs to configure new QoE settings for the terminal from OAM or CN, it may configure a duplicate ID.

[0148] For example, a terminal can establish an RRC connection with a base station at 650, and perform measurements by having / maintaining MBS QoE configuration 1 (measConfigAppLayerId=1) and MBS QoE configuration 2 (measConfigAppLayerId=2) that were held / measured in inactive / standby mode. However, the newly connected base station does not support Release-18 MBS QoE measurement and can only support Release 17 connection mode QoE measurement. At this time, the base station may not know that the terminal has MBS QoE configuration 1 (measConfigAppLayerId=1) and MBS QoE configuration 2 (measConfigAppLayerId=2), and may set measConfigAppLayerId to 1 when configuring Release 17 connection mode QoE configurations to the terminal. In other words, duplication / conflict of QoE configuration ID (=1) may occur.

[0149] In this case, the terminal may end up with two different QoE settings for one measConfigAppLayerId=1, or the MBS QoE setting 1 may be overwritten with the Release 17 connection mode QoE setting. In the former case, an issue may arise where measConfigAppLayerId does not function as an ID to distinguish QoE settings, and in the latter case, an issue may arise where the MBS QoE setting 1 disappears / is released (without OAM instruction).

[0150] Another issue with the second embodiment is that the maximum number of QoE settings that can be set simultaneously for a terminal is limited, and the base station may not be aware of the number of QoE settings set for the terminal and may provide the terminal with new QoE settings that have a larger number of QoE settings. In this case, the terminal may overwrite some of the QoE settings, resulting in the loss / release of existing QoE settings (without OAM instruction).

[0151] To address the above issue, as an embodiment of the present disclosure, a new QoE ID (e.g., measConfigAppLayerIdExt) may be introduced separately from the conventional QoE ID (e.g., measConfigAppLayerId). The new QoE ID may be defined in an RRC QoE configuration (e.g., MeasConfigAppLayer). The base station may provide the terminal with the new QoE ID by including it (indicating a single value) in the RRC QoE configuration (e.g., MeasConfigAppLayer) when configuring QoE for MBS QoE (or inactive / standby mode QoE). The base station may not include the new QoE ID in the RRC QoE configuration (e.g., MeasConfigAppLayer) when configuring connected mode QoE (e.g., Release 17 QoE). The terminal may ignore the conventional QoE ID when the new QoE ID is included. For QoE configuration, the existing QoE ID and the new QoE ID can be defined with different configuration value ranges. For example, the existing QoE ID can be indicated by an integer value between 1 and 16 (inclusive), and the new QoE ID can be indicated by an integer value between 17 and 24 (inclusive). Through this, even if, for example, a terminal has MBS QoE configuration 1 (measConfigAppLayerIdExt=17) and MBS QoE configuration 2 (measConfigAppLayerIdExt=18), and the base station does not know this and sets the Release 17 connection mode QoE configuration (measConfigAppLayerId=1), no ID duplication / collision occurs. As in the above example (where the range of new QoE IDs is from 17 to 24 (inclusive), the number of MBS QoEs (or inactive / standby mode QoEs) that can be set simultaneously to a terminal (e.g., 8) may be limited.

[0152] In one embodiment of the present disclosure, the conventional QoE ID and the new QoE ID may be defined as different overlapping range values ​​for QoE settings. For example, if a terminal has MBS QoE setting 1 (measConfigAppLayerIdExt=1) and MBS QoE setting 2 (measConfigAppLayerIdExt=2), and the base station does not know this and sets the Release 17 connection mode QoE setting (measConfigAppLayerId=1), the terminal determines that ID 1 set to measConfigAppLayerIdExt and ID 1 set to measConfigAppLayerId are different QoE settings, and manages them (storing QoE settings, transmitting settings to terminal APP, and measuring and reporting, etc.) by distinguishing them as two different QoE settings without overwriting the settings.

[0153] According to the above embodiment, when a new QoE ID (e.g., measConfigAppLayerIdExt) is introduced, the new QoE ID (e.g., measConfigAppLayerIdExt) can be defined / used (in place of the existing QoE ID) not only in signaling between a base station and a terminal AS (e.g., 340, 360) where the existing QoE ID is defined / used, but also in signaling between a terminal AS and a terminal APP (e.g., 350, 1c55).

[0154] As an example of an embodiment of the present disclosure, the following terminal operation can be defined without introducing a new QoE ID. When the terminal receives a new QoE setting (e.g., a connected mode QoE setting, a QoE setting that does not include an indicator indicating that it is applicable in inactive / standby mode or is set to false) from a base station, if the QoE setting ID is the same as that of an MBS QoE setting it owns (e.g., a QoE setting applicable in inactive / standby mode, a QoE setting that includes an indicator indicating that it is applicable in inactive / standby mode or is set to true) (i.e., if an ID collision occurs), even if the existing QoE IDs are the same, the terminal can distinguish between the two QoE settings as a connected mode QoE setting or a QoE setting applicable to inactive / standby mode (e.g., distinguish by the presence or absence of an indicator indicating that it is applicable in inactive / standby mode or a set value) and manage them (e.g., store QoE settings, transfer settings to a terminal APP, and measure and report, etc.).

[0155] The terminal AS can also transmit a specific indicator (e.g., an indicator indicating whether it is applicable in inactive / standby mode or not) along with each QoE setting so that the terminal APP can distinguish between two QoE settings having the same QoE ID. When transmitting a QoE measurement report to the terminal AS, the terminal APP can transmit a specific indicator (e.g., an indicator indicating whether it is applicable in inactive / standby mode or not) along with each QoE report so that the two QoE settings having the same QoE ID can be distinguished. When transmitting a QoE measurement report to the base station, the terminal AS can transmit a specific indicator (e.g., an indicator indicating whether it is applicable in inactive / standby mode or not) along with each QoE report so that the two QoE settings having the same QoE ID can be distinguished.

[0156] In one embodiment of the present disclosure, when a terminal receives a new QoE configuration (e.g., a connected mode QoE configuration, a QoE configuration that does not include an indicator indicating that it is applicable in inactive / standby mode or is set to false) from a base station, if the QoE configuration ID is the same as an MBS QoE configuration it owns (e.g., a QoE configuration applicable in inactive / standby mode, a QoE configuration that includes an indicator indicating that it is applicable in inactive / standby mode or is set to true), the terminal may ignore the new QoE configuration (e.g., a connected mode QoE configuration) and operate as if it had not received it to avoid duplicate ID configurations.

[0157] As an example of the present disclosure, a terminal may perform the following procedures. The terminal may perform the procedures by modifying, omitting, or reordering some of the procedures below, or may perform the procedures by including additional steps not described below.

[0158] 1) The terminal may perform some or all of the procedures from steps 615 to 648. Among these, the operations of the steps indicated below may be additionally included.

[0159] A. In step 625, the terminal AS may receive QoE settings from the base station (e.g., gNB1), which may include MBS QoE (or inactive / standby mode QoE) settings including a new QoE ID.

[0160] B. In step 627, the terminal AS can transmit the MBS QoE (or inactive / standby mode QoE) setting and new QoE ID to the terminal APP.

[0161] C. In step 632, the terminal APP may transmit a QoE measurement report generated by the MBS QoE (or inactive / standby mode QoE) setting to the terminal AS, including a new QoE ID.

[0162] D. In step 635, the terminal AS can transmit the received QoE measurement report and new QoE ID to the base station.

[0163] E. In step 647, the terminal APP may transmit a QoE measurement report generated by the MBS QoE (or inactive / standby mode QoE) setting to the terminal AS, including a new QoE ID.

[0164] F. In step 648, the terminal AS can store the received QoE measurement report and new QoE ID.

[0165] 2) The terminal may have transitioned to inactive or standby mode at 640.

[0166] A. If the terminal transitioned to inactive mode at 640, the terminal can perform an RRC connection resume procedure with a new base station (e.g., gNB2) at 650.

[0167] i. The terminal may receive a configuration including the indicator A or indicated as “true” from gNB2. This may be received via a system information block (SIB) or an RRCResume or RRCReconfiguration message, and may be received as part of the RRC connection resume procedure (e.g., in the case of RRCResume), before the RRC connection resume procedure (e.g., in the case of SIB), or after the RRC connection resume procedure (e.g., in the case of RRCReconfiguration).

[0168] 1. If the terminal receives a setting including the indicator A or indicated as “true” from the base station (e.g., gNB2), the terminal may transmit a QoE measurement report (e.g., measured or generated in connected mode) to the base station (e.g., gNB2).

[0169] ii. The terminal may receive a configuration from gNB2 that does not include the indicator A or is indicated as “false”. This may be received via a SIB or an RRCResume or RRCReconfiguration message, and may be received as part of the RRC connection resume procedure (e.g., in the case of RRCResume), before the RRC connection resume procedure (e.g., in the case of SIB), or after the RRC connection resume procedure (e.g., in the case of RRCReconfiguration).

[0170] 1. If the terminal receives a setting from the base station (e.g., gNB2) that does not include the above indicator A or is indicated as “false”, the terminal may release the corresponding MBS QoE (or inactive / standby mode QoE) setting and stop the corresponding QoE measurement and reporting.

[0171] 2. Alternatively, if the terminal receives a configuration from the base station (e.g., gNB2) that does not include the indicator A or is indicated as “false”, the terminal may maintain the corresponding QoE measurement while maintaining the corresponding MBS QoE (or inactive / standby mode QoE) configuration. The terminal APP may forward the generated QoE measurement report together with the new QoE ID to the terminal AS, and the terminal AS may store the QoE measurement report together with the new QoE ID. At this time, the terminal AS may use the memory that stores the MBS QoE (or inactive / standby mode QoE) measurement report in the inactive / standby mode to store the QoE measurement report and the new QoE ID even though it is in the connected mode.

[0172] B. Alternatively, if the terminal transitioned to standby mode at 640, the terminal may perform an RRC connection setup procedure with a new base station (e.g., gNB2) at 650.

[0173] i. The terminal may receive a configuration from gNB2 that includes the indicator A or is indicated as “true”. This may be received via a SIB or an RRCSetup or RRCReconfiguration message, and may be received as part of the RRC connection setup procedure (e.g., in the case of RRCSetup), before the RRC connection setup procedure (e.g., in the case of SIB), or after the RRC connection setup procedure (e.g., in the case of RRCReconfiguration).

[0174] 1. When the terminal receives a configuration from the base station (e.g., gNB2) that includes the indicator A or is indicated as “true”, the terminal transmits the MBS QoE (or inactive / standby mode QoE) configuration to the base station (e.g., via a MeasurementReportAppLayer message or a UEInformationResponse message) so that the base station can retrieve the MBS QoE configuration (or inactive / standby mode QoE).

[0175] 2. If the terminal receives a setting including the indicator A or indicated as “true” from the base station (e.g., gNB2), the terminal may transmit a QoE measurement report (e.g., measured or generated in connected mode) to the base station (e.g., gNB2).

[0176] ii. The terminal may receive a configuration from gNB2 that does not include the indicator A or is indicated as “false”. This may be received via a SIB or an RRCSetup or RRCReconfiguration message, and may be received as part of the RRC connection setup procedure (e.g., in the case of RRCSetup), before the RRC connection setup procedure (e.g., in the case of SIB), or after the RRC connection setup procedure (e.g., in the case of RRCReconfiguration).

[0177] 1. If the terminal receives a setting from the base station (e.g., gNB2) that does not include the indicator A or is indicated as “false”, the terminal may not transmit the MBS QoE (or inactive / standby mode QoE) setting to the base station.

[0178] 2. If the terminal receives a setting from the base station (e.g., gNB2) that does not include the above indicator A or is indicated as “false”, the terminal may release the corresponding MBS QoE (or inactive / standby mode QoE) setting and stop the corresponding QoE measurement and reporting.

[0179] 3. Alternatively, if the terminal receives a configuration from the base station (e.g., gNB2) that does not include the indicator A or is indicated as “false”, the terminal may maintain the corresponding QoE measurement while maintaining the corresponding MBS QoE (or inactive / standby mode QoE) configuration. The terminal APP may forward the generated QoE measurement report together with the new QoE ID to the terminal AS, and the terminal AS may store the QoE measurement report together with the new QoE ID. At this time, the terminal AS may use the memory that stores the MBS QoE (or inactive / standby mode QoE) measurement report in the inactive / standby mode to store the QoE measurement report and the new QoE ID even though it is in the connected mode.

[0180] In one embodiment of the present disclosure, for a connected mode QoE measurement (e.g., Release 17 QoE measurement), if a terminal AS receives a QoE measurement report from a terminal APP (e.g., 355, 435), but the base station or the network does not configure a resource (e.g., SRB4 or SRB5) for the QoE measurement report to the terminal, the terminal may store the QoE measurement report in the connected mode. The terminal may store the QoE measurement report in the memory (e.g., memory 1) where the QoE measurement report is temporarily paused, rather than in the memory (e.g., memory 2) where the MBS QoE (or inactive / standby mode QoE) measurement report is stored in the inactive / standby mode. This is because the terminal (e.g., Release 17 terminal) may not support MBS QoE (or inactive / standby mode QoE) (e.g., Release 18 feature) and therefore may not have memory 2.

[0181] In one embodiment of the present disclosure, for MBS QoE measurement (e.g., Release 18 QoE measurement), if a terminal AS receives a QoE measurement report from a terminal APP in a connected mode (e.g., 632), but the base station or the network does not configure a resource (e.g., SRB4 or SRB5) for the QoE measurement report to the terminal, the terminal may store the QoE measurement report in the connected mode. The terminal may store the QoE measurement report in a memory (e.g., memory 2) that stores MBS QoE (or inactive / standby mode QoE) measurement reports in the inactive / standby mode. This is because the terminal may have memory 2 since it can support MBS QoE (or inactive / standby mode QoE) (e.g., Release 18 feature).

[0182] The terminal may transmit availability at step 655. This may be to inform the base station that the terminal is performing QoE measurements in inactive or standby mode and storing the generated QoE reports. However, if a UE-based solution is used for the base station to retrieve QoE configuration information of the standby mode terminal, the standby mode terminal needs to transmit to the base station not only whether it has stored QoE reports but also whether it has MBS QoE (or inactive / standby mode QoE) measurement configurations. This is because even if the terminal does not store QoE measurement reports, if the base station has MBS QoE (or inactive / standby mode QoE) measurement configurations, it can request retrieval of the corresponding QoE configurations or allocate resources necessary for retrieval, and through retrieval, it can add a new QoE configuration to the terminal (by setting a QoE ID that does not overlap with a QoE configuration ID that the terminal already has), or change or release an existing QoE configuration of the terminal.

[0183] To this end, in one embodiment of the present disclosure, the (standby mode) terminal may, at step 655, include an availability indicator or set it to “true” (e.g., via RRCSetupComplete) to transmit to the base station if it 1) has stored a QoE report or 2) has an MBS QoE (or inactive / standby mode QoE) measurement configuration.

[0184] However, in the above embodiment, for example, the base station may not be able to distinguish between the two cases below because the terminal commonly uses one availability indicator for 1) storing QoE reports and 2) having MBS QoE (or inactive / standby mode QoE) measurement settings.

[0185] - Case 1) If the terminal has MBS QoE (or inactive / standby mode QoE) measurement settings and the terminal also stores QoE measurement reports.

[0186] - Case 2) If the terminal has MBS QoE (or inactive / standby mode QoE) measurement settings, but does not store QoE measurement reports.

[0187] In both cases, since the (standby mode) UE transmits the availability indicator to the base station (e.g., via RRCSetupComplete) with it included or set to "true", the receiving base station may not be able to distinguish whether the UE is in Case 1 or Case 2. The base station may perform different actions for each case. For example, in Case 1, the base station may not configure SRB4 for the UE because there is no QoE measurement report to collect immediately. On the other hand, in Case 2, the base station may configure SRB4 for QoE measurement report collection and perform additional resource configuration or related actions for QoE configuration collection (e.g., requesting QoE configuration collection).

[0188] To address the above issue, in one embodiment of the present disclosure, in step 655, the (standby mode) terminal may transmit to the base station (e.g., via RRCSetupComplete) 1) if it stores QoE reports, including availability indicator 1 or setting it to "true", and 2) if it has MBS QoE (or inactive / standby mode QoE) measurement configuration, including availability indicator 2 (separate from availability indicator 1) or setting it to "true". In step 655, the (standby mode) terminal may not transmit to the base station (e.g., via RRCSetupComplete) 1) if it does not store QoE reports, including availability indicator 1 or setting it to "false", and 2) if it does not have MBS QoE (or inactive / standby mode QoE) measurement configuration, including availability indicator 2 (separate from availability indicator 1) or setting it to "false".

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

[0190] Referring to FIG. 7, the terminal includes an RF (Radio Frequency) processing unit (710), a baseband processing unit (720), a storage unit (730), and a control unit (740).

[0191] The RF processing unit (710) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (710) up-converts the baseband signal provided from the baseband processing unit (720) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (710) 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 (710) may include multiple RF chains. Furthermore, the RF processing unit (710) may perform beamforming. For the above beamforming, the RF processing unit (710) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO and can receive multiple layers when performing the MIMO operation.

[0192] The baseband processing unit (720) 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 (720) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (720) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (710). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (720) 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 (720) divides the baseband signal provided from the RF processing unit (710) 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.

[0193] The baseband processing unit (720) and the RF processing unit (710) transmit and receive signals as described above. Accordingly, the baseband processing unit (720) and the RF processing unit (710) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (720) and the RF processing unit (710) 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 (720) and the RF processing unit (710) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (mm wave) (e.g., 60GHz) band.

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

[0195] The control unit (740) controls the overall operations of the terminal. For example, the control unit (740) transmits and receives signals through the baseband processing unit (720) and the RF processing unit (710). In addition, the control unit (740) records and reads data in the storage unit (730). For this purpose, the control unit (740) may include at least one processor. For example, the control unit (740) 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 (742) as illustrated in the drawing.

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

[0197] Referring to FIG. 8, a base station according to an example of the present disclosure is configured to include an RF processing unit (810), a baseband processing unit (820), a backhaul communication unit (830), a storage unit (840), and a control unit (850).

[0198] The RF processing unit (810) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (810) up-converts the baseband signal provided from the baseband processing unit (820) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (810) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a 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 (810) may include multiple RF chains. Furthermore, the RF processing unit (810) may perform beamforming. For the beamforming, the RF processing unit (810) may adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The above RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.

[0199] 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 wireless access technology. 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 OFDM, 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 IFFT operation and 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 operation, and then restores the received bit string through demodulation and decoding. 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, a communication unit, or a wireless communication unit.

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

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

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

[0203] Figure 9 illustrates the configuration of a terminal according to one embodiment of the present disclosure.

[0204] As illustrated in FIG. 9, the terminal of the present disclosure may include a control unit (control unit) (930), a transceiver (910), and a storage unit (memory) (920). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the control unit (930), the transceiver (910), and the storage unit (920) may be implemented in the form of a single chip. According to one embodiment, the control unit (930) of FIG. 9 may include at least one processor or controller.

[0205] According to one embodiment, the control unit (930) may control a series of processes that enable the terminal to operate according to the embodiments of the present disclosure described above. For example, according to the embodiments of the present disclosure, the components of the terminal may be controlled to perform a transmission and reception method of the terminal depending on whether the base station mode is the base station energy saving mode or the base station normal mode. There may be one or more control units (930), and the control units (930) may perform transmission and reception operations of the terminal in a wireless communication system that applies the carrier bundle of the present disclosure described above by executing a program stored in the storage unit (920).

[0206] The transceiver (910) can transmit and receive signals with the base station. The signals transmitted and received with the base station can include control information and data. The transceiver (910) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies the received signal, and down-converts the frequency, etc. However, the transceiver (910) is only one embodiment, and the components of the transceiver (910) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (910) can receive a signal through a wireless channel and output it to the control unit (930), and transmit the signal output from the control unit (930) through the wireless channel.

[0207] According to one embodiment, the storage unit (920) can store programs and data necessary for the operation of the terminal. In addition, the storage unit (920) can store control information or data included in signals transmitted and received by the terminal. The storage unit (920) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, the storage unit (920) can be provided in multiple numbers. According to one embodiment, the storage unit (920) can store a program for performing transmission and reception operations of the terminal depending on whether the base station mode of the embodiments of the present disclosure described above is a base station energy saving mode or a base station normal mode.

[0208] FIG. 10 illustrates a configuration of a base station according to an embodiment of the present disclosure.

[0209] As illustrated in FIG. 10, the base station of the present disclosure may include a control unit (control unit) (1030), a transceiver (1010), and a storage unit (memory) (1020). However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the control unit (1030), the transceiver (1010), and the storage unit (1020) may be implemented in the form of a single chip. The control unit (1030) of FIG. 10 may include at least one processor or controller.

[0210] The control unit (1030) can control a series of processes so that the base station can operate according to the above-described embodiment of the present disclosure. For example, the control unit (1030) can control the components of the base station to perform a method for scheduling a terminal according to whether the base station mode is the base station energy saving mode or the base station normal mode according to the embodiment of the present disclosure. There can be one or more control units (1030), and the control units (1030) can perform a method for scheduling a terminal according to whether the base station mode of the above-described present disclosure is the base station energy saving mode or the base station normal mode by executing a program stored in the storage unit (1020).

[0211] The transceiver (1010) can transmit and receive signals with the terminal. The signals transmitted and received with the terminal can include control information and data. The transceiver (1010) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies the received signal and down-converts the frequency, etc. However, the transceiver (1010) is only one embodiment, and the components of the transceiver (1010) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1010) can receive a signal through a wireless channel and output it to the control unit (1030), and transmit a signal output from the control unit (1030) through the wireless channel.

[0212] According to one embodiment, the storage unit (1020) can store programs and data required for the operation of the base station. In addition, the storage unit (1020) can store control information or data included in signals transmitted and received by the base station. The storage unit (1020) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, the storage unit (1020) can be provided in multiple numbers. According to one embodiment, the storage unit (1020) can store a program for performing a method for scheduling a terminal depending on whether the base station mode of the above-described embodiments of the present disclosure is a base station energy saving mode or a base station normal mode.

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

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

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

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

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

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

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

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

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

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: A step of receiving a message including setting information related to QoE (quality of experience) measurement from a base station; and A method comprising: performing, to the base station, transmission of the QoE measurement report collected in the RRC idle state and / or the RRC inactive state and / or the QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state, when the above configuration information includes indication information indicating whether to allow transmission of a quality of experience (QoE) measurement report collected in the RRC idle state and / or the RRC inactive state and / or the QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state.

2. In paragraph 1, A method wherein, if the above configuration information does not include the above instruction information, the transmission of the QoE measurement report and the QoE measurement configuration for the RRC idle state and the RRC inactive state is not permitted.

3. In paragraph 2, If the above configuration information does not include the above instruction information: The QoE measurement settings applicable to the above RRC idle state and / or the above RRC inactive state are released, QoE measurement reports collected in the RRC idle state and / or the RRC inactive state are discarded, A method wherein QoE measurement reports in the RRC idle state and / or the RRC disabled state are set not to be transmitted.

4. In paragraph 3, A method wherein the above instruction information is included in an RRC reconfiguration message or an RRC resume message.

5. A method performed by a base station in a wireless communication system, the method comprising: A step for transmitting a message including setting information related to QoE (quality of experience) measurement to a terminal; and A method comprising: receiving, from the terminal, a QoE measurement report collected in the RRC idle state and / or the RRC inactive state and / or the QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state, when the above configuration information includes indication information indicating whether to allow transmission of a quality of experience (QoE) measurement report collected in the RRC idle state and / or the RRC inactive state and / or whether to allow transmission of a QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state.

6. In paragraph 5, A method wherein, if the above configuration information does not include the above instruction information, the transmission of the QoE measurement report and the QoE measurement configuration for the RRC idle state and the RRC inactive state is not permitted.

7. In paragraph 6, If the above configuration information does not include the above instruction information: The QoE measurement settings applicable to the above RRC idle state and / or the above RRC inactive state are released, QoE measurement reports collected in the RRC idle state and / or the RRC inactive state are discarded, A method wherein QoE measurement reports in the RRC idle state and / or the RRC disabled state are set not to be transmitted.

8. In paragraph 7, A method wherein the above instruction information is included in an RRC reconfiguration message or an RRC resume message.

9. In a wireless communication system, the terminal comprises: transceiver; and Including a controller connected to the above transceiver, The above controller, Receive a message from a base station containing configuration information related to QoE (quality of experience) measurement, A terminal configured to perform transmission, to the base station, of the QoE measurement report collected in the RRC idle state and / or the RRC inactive state and / or the QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state, when the above configuration information includes indication information indicating whether to allow transmission of a quality of experience (QoE) measurement report collected in the RRC idle state and / or the RRC inactive state and / or the QoE measurement configuration applicable to the RRC idle state and / or the RRC inactive state.

10. In paragraph 9, If the above configuration information does not include the above instruction information, the terminal is not allowed to transmit QoE measurement reports and QoE measurement configurations for the RRC idle state and the RRC inactive state.

11. In Article 10, If the above configuration information does not include the above instruction information: The QoE measurement settings applicable to the above RRC idle state and / or the above RRC inactive state are released, QoE measurement reports collected in the RRC idle state and / or the RRC inactive state are discarded, A terminal configured so that QoE measurement reports in the RRC idle state and / or RRC inactive state are not transmitted.

12. In paragraph 11, The above instruction information is included in the RRC reconfiguration message or the RRC resume message.

13. In a wireless communication system, at a base station, the base station, transceiver; and Including a controller connected to the above transceiver, The above controller, Transmits a message containing configuration information related to QoE (quality of experience) measurement to the terminal, A base station configured to perform reception of, from the terminal, a QoE measurement report collected in the RRC idle state and / or the RRC inactive state and / or a QoE measurement setting applicable to the RRC idle state and / or the RRC inactive state, when the above configuration information includes indication information indicating whether to allow transmission of a quality of experience (QoE) measurement report collected in the RRC idle state and / or the RRC inactive state and / or whether to allow transmission of a QoE measurement setting applicable to the RRC idle state and / or the RRC inactive state.

14. In paragraph 13, A base station, where if the above configuration information does not include the above instruction information, transmission of QoE measurement reports and QoE measurement configurations for the RRC idle state and the RRC inactive state is not permitted.

15. In paragraph 14, If the above configuration information does not include the above instruction information: The QoE measurement settings applicable to the above RRC idle state and / or the above RRC inactive state are released, QoE measurement reports collected in the RRC idle state and / or the RRC inactive state are discarded, A base station, wherein QoE measurement reports in the RRC idle state and / or the RRC inactive state are set not to be transmitted.

Images