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

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to a method performed by a terminal in a wireless communication system, the method comprising the steps of: storing a first application layer measurement report container corresponding to a first measurement configuration and a second application layer measurement report container corresponding to a second measurement configuration on the basis of a first application layer measurement configuration in a radio resource control (RRC) idle mode or an RRC inactive mode; receiving a second application layer measurement configuration from a base station after the terminal transitions to an RRC-connected state; and transmitting an application layer measurement report message to the base station on the basis of the first application layer measurement configuration and the second application layer measurement configuration, wherein a pause reporting indicator for the first measurement configuration is configured as first information in the second application layer measurement configuration, and the application layer measurement report message does not include the first application layer measurement report container and includes the second application layer measurement report container.

Description

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

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. In addition, the present disclosure relates to a method and device for measuring quality of experience (QoE) in an RRC (radio resource control) inactive mode and / or an RRC idle mode.

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

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

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

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

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

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

[0008] A technical problem to be achieved in various embodiments of the present disclosure is to provide improved operation of a terminal and a base station in a wireless communication system.

[0009] In addition, a technical problem to be achieved in various embodiments of the present disclosure is to provide an improved method and device for measuring QoE in RRC disabled mode and / or RRC standby mode in a wireless communication system.

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

[0011] According to one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may be provided, the method including the steps of transmitting terminal performance information including a quality of experience (QoE) measurement-related capability indicator to a base station, receiving configuration information for QoE measurement from the base station, receiving an RRC (radio resource control) release message from the base station, performing QoE measurement based on the configuration information for QoE measurement in an RRC deactivation mode or an RRC standby mode after receiving the RRC release message, storing a QoE measurement report based on the QoE measurement, and when the terminal establishes an RRC connection with a new base station, transmitting information on the stored QoE measurement report to the new base station.

[0012] In addition, according to one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may be provided, including the steps of: storing a first application layer measurement report container corresponding to a first measurement configuration and a second application layer measurement report container corresponding to a second measurement configuration based on a first application layer measurement configuration in an RRC (radio resource control) standby mode or an RRC inactive mode; receiving a second application layer measurement configuration from a base station after the terminal transitions to an RRC connected state; and transmitting an application layer measurement report message to the base station based on the first application layer measurement configuration and the second application layer measurement configuration, wherein a pause reporting indicator for the first measurement configuration is set as first information in the second application layer measurement configuration, and the application layer measurement report message does not include the first application layer measurement report container, but includes the second application layer measurement report container.

[0013] In addition, according to one embodiment of the present disclosure, a method performed by a base station in a wireless communication system may be provided, including the steps of establishing an RRC connection with a terminal in an RRC (radio resource control) standby mode or an RRC deactivation mode, transmitting a second application layer measurement configuration for application layer measurement reporting of the terminal, which stores a first application layer measurement reporting container corresponding to a first measurement configuration and a second application layer measurement reporting container corresponding to a second measurement configuration based on a first application layer measurement configuration in the RRC standby mode or the RRC deactivation mode, to the terminal, and receiving an application layer measurement report message from the terminal based on the first application layer measurement configuration and the second application layer measurement configuration, wherein a pause reporting indicator for the first measurement configuration is set as first information in the second application layer measurement configuration, and the application layer measurement report message does not include the first application layer measurement report container, but includes the second application layer measurement report container.

[0014] In addition, according to one embodiment of the present disclosure, a terminal of a wireless communication system, comprising a transceiver and at least one processor connected to the transceiver, wherein the at least one processor stores a first application layer measurement report container corresponding to a first measurement configuration and a second application layer measurement report container corresponding to a second measurement configuration based on a first application layer measurement configuration in an RRC (radio resource control) standby mode or an RRC inactive mode, receives a second application layer measurement configuration from a base station after the terminal transitions to an RRC connected state, and controls to transmit an application layer measurement report message to the base station based on the first application layer measurement configuration and the second application layer measurement configuration, and a pause reporting indicator for the first measurement configuration is set as first information in the second application layer measurement configuration, and the application layer measurement report message does not include the first application layer measurement report container, but includes the second application layer measurement report container.

[0015] In addition, according to one embodiment of the present disclosure, a base station of a wireless communication system may provide a base station including a transceiver and at least one processor connected to the transceiver, wherein the at least one processor establishes an RRC connection with a terminal in an RRC (radio resource control) standby mode or an RRC inactive mode, transmits a second application layer measurement configuration for application layer measurement reporting of the terminal, storing a first application layer measurement report container corresponding to a first measurement configuration and a second application layer measurement report container corresponding to a second measurement configuration based on a first application layer measurement configuration in the RRC standby mode or the RRC inactive mode, and controls to receive an application layer measurement report message from the terminal based on the first application layer measurement configuration and the second application layer measurement configuration, wherein a pause reporting indicator for the first measurement configuration is set as first information in the second application layer measurement configuration, and the application layer measurement report message does not include the first application layer measurement report container, but includes the second application layer measurement report container.

[0016] According to various embodiments of the present disclosure, improved terminal and base station operations can be provided in a wireless communication system.

[0017] Additionally, according to various embodiments of the present disclosure, an improved method and device for measuring QoE in an RRC disabled mode and / or an RRC standby mode in a wireless communication system can be provided.

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

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

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

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

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

[0023] FIG. 5 is a flowchart illustrating a setup and reporting procedure for RAN (radio access network) visible QoE measurement according to one embodiment of the present disclosure.

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

[0025] FIG. 7 is a flowchart illustrating a procedure for pausing and / or resuming QoE measurement of a terminal in a connected mode according to one embodiment of the present disclosure.

[0026] FIG. 8 is a diagram showing the configuration of a terminal applied to embodiments of the present disclosure.

[0027] FIG. 9 is a diagram showing the configuration of a base station applied to embodiments of the present disclosure.

[0028] FIG. 10 is a diagram illustrating an application layer measurement reporting procedure of a terminal applied to various embodiments of the present disclosure.

[0029] Hereinafter, preferred embodiments of the present invention 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 invention will be omitted.

[0030] In describing the embodiments herein, descriptions of technical details that are well-known in the technical field to which the present invention pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present invention by omitting unnecessary explanations and to convey the gist more clearly.

[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 invention, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Like reference numerals designate 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, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

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

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

[0036] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

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

[0038] For convenience of explanation below, some terms and names defined in the 3rd generation partnership project (3GPP) LTE (long term evolution) standard and / or 3GPP NR (new radio) standard may be used. However, the present invention is not limited to the above terms and names, and can be equally applied to systems conforming to other standards.

[0039] In various embodiments of the present disclosure, the AS layer of a terminal may be used with the same meaning as the UE AS, and the application layer of the terminal may be used with the same meaning as the UE APP. In addition, the operations of the UE AS and the UE APP may be interpreted as the operations of the terminal.

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

[0041] 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) (1-10) and an access and mobility management function (AMF) (1-05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter referred to as NR UE or terminal, UE) (1-15) accesses an external network through the gNB (1-10) and the AMF (1-05). 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.

[0042] In Fig. 1, gNB (1-10) corresponds to an eNB (Evolved Node B) of an existing LTE system. gNB (1-10) is connected to NR UE (1-15) via a wireless channel and can provide a service superior to that of an existing Node B (1-20). 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 buffer status, available transmission power status, and channel status of UEs and performs scheduling is required, and this is handled by gNB (1-10). 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 Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology. In addition, an adaptive modulation and coding (AMC) method is applied, which determines the modulation scheme and channel coding rate according to the channel status of the terminal.

[0043] AMF (1-05) performs functions such as mobility support, bearer setup, and QoS (quality of service) setup. AMF (1-05) is a device that is responsible for 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 AMF (1-05) is connected to MME (1-25) through a network interface. MME (1-25) is connected to eNB (1-30), which is an existing base station. A terminal (1-15) supporting LTE-NR Dual Connectivity can transmit and receive data while maintaining a connection to not only gNB (1-10) but also eNB (1-30) (1-35).

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

[0045] A mobile communication system according to an embodiment of the present disclosure has three radio connection states (RRC states) or RRC modes. The connected mode (RRC_CONNECTED, 2-05) is a radio connection state in which a terminal can transmit and receive data. The idle mode (RRC_IDLE, 2-30) 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 existing LTE systems, 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.

[0046] In a mobile communication system according to one embodiment of the present disclosure, a new inactive (RRC_INACTIVE) radio connection state (2-15) 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.

[0047] - Cell re-selection mobility;

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

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

[0050] - Paging is initiated by NR RAN;

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

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

[0053] According to one embodiment of the present disclosure, a terminal in an INACTIVE wireless connection state can transition to a connected mode or a standby mode using a specific procedure. The transition from INACTIVE mode (2-15) to connected mode (2-05) is performed through a Resume procedure, and the transition from connected mode (2-05) to INACTIVE mode (2-15) is performed through a Release procedure including suspend configuration information (2-10). The above procedure is performed by transmitting and receiving one or more RRC messages between the terminal and the base station, and consists of one or more steps. Furthermore, transitioning from INACTIVE mode (2-15) to standby mode (2-30) is possible through a Release procedure after Resume (2-20). The transition between connected mode (2-05) and standby mode (2-30) follows existing LTE technology. That is, it is possible to switch from standby mode (2-30) to connected mode (2-05) through the establishment procedure, and from connected mode (2-05) to standby mode (2-30) through the release procedure (2-25).

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

[0055] In the embodiment of the present disclosure, for convenience of explanation, the UE AS (access stratum) (3-05) and the UE APP (3-45) are described separately, but this is for convenience of explanation, and the operation of the UE AS (3-05) and the operation of the UE APP (3-45) can both be interpreted as the operation of the terminal. Referring to FIG. 3, according to one embodiment of the present disclosure, the AS (3-05) of the 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 the base station (or NG-RAN, 3-15) via a UE capability message (e.g., UECapabilityInformation) (3-10). Before the terminal transmits the UE capability message, the base station (1c-15) may transmit a message (e.g., UECapabilityEnquiry) to the terminal for requesting the UE capability message. Additionally, the terminal can report to the base station (1c-15) whether it supports RAN visible QoE measurement by service type (e.g., streaming, VR) through a UE capability message (e.g., ran-VisibleQoE-Streaming-MeasReport, ran-VisibleQoE-VR-MeasReport).Additionally, the terminal can report to the base station whether it supports UL (uplink) RRC segmentation for QoE report message (e.g., ul-MeasurementReportAppLayer-Seg) through UE capability message. The UE capability message includes ASN.1 (Abstract Syntax Notation One) information as shown in Table 1 below, and the description of related parameters (i.e., QoE measurement parameters) is as shown in Table 2 below.

[0056] [Table 1]

[0057]

[0058] [Table 2]

[0059]

[0060] The types of services that can be supported in LTE may include Streaming and MTSI (Multimedia Telephony Service for IMS (IP Multimedia Subsystem)), and in the case of NR, in addition to the types of services that can be supported in LTE, it was defined in Rel-17 that VR (Virtual Reality) service is 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.

[0061] According to one embodiment of the present disclosure, an operations administration and maintenance (OAM, 3-20) can provide QoE measurement configuration information to a core network (CN, 3-25) (3-30). Upon receiving the configuration information, the CN (3-25) transmits the configuration information to a base station (3-15). Through this, the OAM (3-20) can activate QoE measurement (3-35).

[0062] According to one embodiment of the present disclosure, a base station (3-15) that has received configuration information from a CN (3-25) may transmit QoE configuration information to an AS (3-05) of a terminal via an RRC message (e.g., an RRCReconfiguration or RRCResume message) (3-40). The RRC message may include an IE (APPLayerMeasConfig) as in Table 3 below, and descriptions of related parameters are as in Table 4 below.

[0063] [Table 3]

[0064]

[0065] [Table 4]

[0066]

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

[0068] [Table 5]

[0069]

[0070]

[0071] As described above, for the QoE measurement settings included in measConfigAppLayerToAddModList, the AS layer (3-05) of the terminal can transfer part or all of the configuration information to the upper layer or application layer (UE APP, 3-45) of the terminal via an AT Command (3-50). In addition, the AS layer (3-05) of the terminal can send an AT Command to the APP (3-45) of the terminal to instruct / command to delete the stored configuration information for the QoE measurement settings included in measConfigAppLayerToAddReleaseList. The AT command can include a QoE measurement configuration.

[0072] According to one embodiment of the present disclosure, the terminal APP (3-45) can perform QoE measurement based on received configuration information. In addition, the terminal APP (3-45) can report the results of the measurement based on the configuration information to the terminal AS (3-05) via an AT command (3-55).

[0073] According to one embodiment of the present disclosure, a terminal AS (3-05) that receives a measurement result report from a terminal APP (3-45) can report the measurement result to a base station (3-15) via an RRC message (e.g., a MeasurementReportAppLayer message) (3-60). SRB (signaling radio bearer) 4 can be used for reporting the QoE measurement result. The MeasurementReportAppLayer message can include ASN.1 information as shown in Table 6 below, and the description of the related parameters is as shown in Table 7 below.

[0074] [Table 6]

[0075]

[0076]

[0077] [Table 7]

[0078]

[0079] In addition, according to one embodiment of the present disclosure, a specific procedure of the terminal AS (3-05) reporting the measurement result may follow the operation described in Table 8 below.

[0080] [Table 8]

[0081]

[0082]

[0083] The procedure in Table 8 refers to FIG. 10. FIG. 10 is a diagram illustrating an application layer measurement reporting procedure of a terminal applied to various embodiments of the present disclosure.

[0084] Referring to Figure 10, the terminal can perform an RRC reconfiguration procedure with the network (base station). Following the above procedure, the terminal can receive and apply settings for QoE measurement. If the preset conditions are met, the terminal can transmit an application layer measurement report to the network.

[0085] According to one embodiment of the present disclosure, the base station (3-15) can transmit the measurement result report received from the terminal to the final server (TCE (trace collection entity) or MCE (measurement collection entity), 3-65) that collects the measurement report (3-70).

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

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

[0088] According to one embodiment of the present disclosure, in a method related to a Management-based QoE configuration / reporting procedure, an OAM (4-05) directly transmits QoE measurement configuration to a base station (4-10) without going through a CN, thereby instructing the base station (4-10) to activate QoE measurement of a terminal (4-15). The terminal reports capability information to the base station (4-25). Operation 4-25 refers to operation 3-10 of FIG. 3. Operation 4-25 may be performed before operation 4-15 or after operation 4-15. The base station (4-10) that has received the QoE measurement configuration may 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 (4-10) can transmit / forward QoE measurement settings to one of the searched single or multiple terminals via an RRC message (e.g., RRCReconfiguration message or RRCResume) (4-20). For specific operations of operation 4-20, refer to operation 3-40. Each terminal that receives the RRC message can exchange settings and measurement results for QoE measurements between the AS layer and the APP via AT Commands between the UE AS and the UE APP as described above in FIG. 3 (4-30, 4-35). The AS layer of the terminal reports the measurement results obtained from the APP to the base station (4-10) via an RRC message (4-40), and the base station (4-10) can transmit the same to the TCE / MCE (4-45). For specific operations of 4-30 to 4-45, refer to operations 3-50 to 3-70 of FIG. 3.

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

[0090] 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 OCTET 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, RAN visible QoE (RVQoE) measurements were defined and introduced to enable base stations to read QoE measurement reports from terminals and utilize them for network optimization, such as radio resource management.

[0091] 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) (5-05). 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.

[0092] 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. The base station can generate an RVQoE measurement configuration based on information received from the terminal and transmit the RVQoE measurement configuration to the terminal (5-10). At this time, the RVQoE measurement configuration can be transmitted together with an 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 above ran-VisibleParameters parameter may include a RAN-VisibleParameters IE, through which some or all of the parameters below may be provided from the base station to the terminal.

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

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

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

[0096] 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 (5-15). 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 (5-20). At this time, the RVQoE measurement report can be transmitted to the AS layer together with the OAM-based QoE measurement report.

[0097] The AS layer of a terminal that has received an RVQoE measurement report can forward / transmit / report the forwarded RVQoE measurement report to the base station (5-25). At this time, the RVQoE measurement report can be forwarded / transmitted / reported to the base station together with an OAM-based QoE measurement report. In 5-25, 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.

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

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

[0100] - PDU session ID list (pdu-SessionIdList): The terminal can indicate the PDU (protocol data unit) session(s) used in 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. Based on the identification result, the base station can optimize resource allocation and scheduling for the PDU session(s) indicated by this parameter.

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

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

[0103] According to one embodiment of the present disclosure, the QoE configuration information (e.g., 3-50 or 4-30) 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).

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

[0105] 3GPP standardized support for QoE measurements in connected mode in Release 17. Expanding on this, 3GPP is 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 MBS (Multicast Broadcast Service) services, the QoE configuration / measurement / reporting procedures between UEs and base stations in not only connected mode (RRC_CONNECTED), but also inactive mode (RRC_INACTIVE) and idle (RRC_IDLE) modes can be as follows.

[0106] In step 6-15, the base station (6-05, NG-RAN) (e.g., base station 1) and the terminal AS (6-10) can establish (or establish) an RRC connection.

[0107] In step 6-20, the base station (6-05) may transmit a UE Capability request message (e.g., UECapabilityEnquiry) to the terminal. The terminal, which receives the UE Capability request 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 / or an idle (RRC_IDLE) mode. Step 6-20 may correspond to step 4-25 or step 3-10.

[0108] In step 6-25, the base station may provide QoE configuration information to the terminal. The UE AS of the terminal that has received the QoE configuration information may forward the QoE configuration information to the UE APP (6-27). Step 6-25 may correspond to steps 4-20 and 4-30, or steps 3-40 and 3-50. 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 a connected mode (RRC_CONNECTED), an inactive mode (RRC_INACTIVE), and / or an idle mode (RRC_IDLE).

[0109] In step 6-30, while the terminal AS (6-10) is in a connected mode, the terminal APP (6-12) can perform QoE measurement for the MBS service using the QoE setting information (e.g., when the MBS service is received).

[0110] In step 6-32, the terminal APP may transmit QoE measurement results or measurement reports for the MBS service to the terminal AS layer. Step 6-32 may correspond to step 3-55 or 4-35.

[0111] In step 6-35, the terminal AS can 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 can be reported to the base station immediately. Step 6-35 can correspond to steps 3-60 or 4-40.

[0112] In step 6-40, the base station sends an RRC Release message to the terminal, and the terminal that receives the message can transition to inactive mode or standby mode. The terminal can receive MBS services even in inactive or standby mode.

[0113] In step 6-45, the terminal APP can perform QoE measurement (using the QoE configuration information received in step 6-25) on the MBS service while the AS is in an inactive or standby mode.

[0114] In step 6-47, the terminal APP can transmit the QoE measurement result or measurement report generated through QoE measurement to the terminal AS.

[0115] In step 6-48, the terminal AS may store the QoE measurement report instead of immediately transmitting it to the base station because it is in an inactive or standby mode. For example, the terminal APP may forward the generated QoE measurement report to the terminal AS, which may then store it.

[0116] In step 6-50, the terminal may establish (or establish) an RRC connection with a (new) base station (e.g., base station 2) (e.g., by receiving an RRC Setup or RRC resume message). The base station (base station 2) with which the terminal in the inactive or standby mode establishes an RRC connection may be the same base station as the base station (base station 1) that transmitted the RRC release message in step 6-40, or may be a new base station different from the base station (base station 1) that transmitted the RRC release message in step 6-40.

[0117] In step 6-55, the terminal may transmit information to the base station indicating that it is storing QoE measurement report and / or MBS QoE configuration information. When the terminal establishes an RRC connection based on step 6-50, the terminal may transmit an RRCSetupComplete message (when the terminal in standby mode switches to connected mode) or an RRCResumeComplete message (when the terminal in inactive mode switches to connected mode) to the base station, thereby indicating to the base station (e.g., base station 2) that the terminal is storing QoE measurement report (e.g., measured in inactive / standby mode) or MBS QoE configuration information (e.g., availability).

[0118] In steps 6-60, the base station (e.g., base station 2) that received the availability may configure an SRB (e.g., SRB4 or SRB5) for transmitting QoE measurement report / configuration to the terminal. For this purpose, an RRC Reconfiguration or RRC Resume message may be used.

[0119] In one embodiment of the present disclosure, in step 6-50, when the terminal establishes an RRC connection by receiving an RRC resume message (e.g., when the base station resumes an RRC connection for an inactive mode terminal), the SRB (e.g., SRB4 or SRB5) for transmitting QoE measurement reports / configurations may be simultaneously configured through the RRC resume message. In this case, in step 6-55, the terminal may transmit availability through an RRCResumeComplete message, and the step 6-60 procedure may be omitted.

[0120] In step 6-65, the newly connected base station (e.g., base station 2) may not have QoE configuration information set for the terminal (e.g., QoE configuration information for the MBS service and / or QoE configuration information applicable not only in the connected mode but also in the inactive / standby mode) (e.g., when the inactive / standby mode terminal receives the RRC Setup message and establishes the RRC connection in step 6-50). In this case, the terminal may transmit the QoE configuration information to the base station. Using this, the base station may retrieve or obtain the QoE configuration information set for the terminal. Each QoE configuration information of the terminal retrieved by the base station may include some or all of the following.

[0121] - QoE reference

[0122] - TCE or MCE address or ID

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

[0124] - Service type

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

[0126] - Available RAN visible QoE indicator information

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

[0128] - Priority value of the corresponding QoE setting

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

[0130] In step 6-70, the terminal may transmit a QoE measurement report (measured and stored in inactive / standby mode) (e.g., the QoE measurement report stored in 6-48) to the base station.

[0131] In step 6-75, the terminal APP can perform QoE measurements (even in connected mode).

[0132] In step 6-80, the terminal APP can transmit QoE measurement report information generated according to QoE measurement to the terminal AS.

[0133] In step 6-85, the terminal AS can report QoE measurement report information received from the terminal APP (in connected mode) to the base station.

[0134] FIG. 7 is a flowchart illustrating a procedure for pausing and / or resuming QoE measurement of a terminal in a connected mode according to one embodiment of the present disclosure.

[0135] Descriptions of steps 7-05 through 7-35 may refer to the corresponding steps and related descriptions in the drawings described above (e.g., 3, 4, 5, 6).

[0136] In step 7-40, the base station (7-05) may temporarily pause or suspend the QoE measurement report of the terminal. For example, the base station (7-05) may want to temporarily pause the reception of QoE measurement reports in case of RAN overload. To this end, the base station (7-05) may instruct the terminal to pause or suspend the QoE measurement report by setting a specific indicator (e.g., pauseReporting in AppLayerMeasConfig) to true.

[0137] In step 7-45, the terminal APP (7-12) can (still) perform QoE measurement and transmit the generated QoE measurement report to the terminal AS (7-10).

[0138] In step 7-50, the terminal AS (7-10) may no longer report QoE measurement reports to the base station (7-05) because it has been instructed by the base station (7-05) to stop QoE measurement reports. Instead, the terminal AS (7-10) may store the QoE measurement reports received from the terminal APP (7-12). This may be to transmit the stored QoE measurement reports when the base station (7-05) instructs it to resume QoE measurement reports later (e.g., 7-55).

[0139] In step 7-55, the base station (7-05) may temporarily resume the QoE measurement reporting of the terminal that was temporarily suspended. For example, the base station may want to resume receiving QoE measurement reports when RAN overload is resolved. To this end, the base station (7-05) may instruct the terminal to resume QoE measurement reporting by setting a specific indicator (e.g., pauseReporting in AppLayerMeasConfig) to false.

[0140] In step 7-60, the terminal AS (7-10) can resume QoE measurement reporting. At this time, the terminal AS (7-10) can transmit the QoE measurement report saved in step 7-50 to the base station (7-05). The terminal APP (7-12) can perform QoE measurement and report the QoE measurement report to the terminal AS (7-10), and the terminal AS (7-10) can report the QoE measurement report received from the terminal APP (7-12) to the base station (7-05).

[0141] In one embodiment of the present disclosure, the pauseReporting directive may be indicated by QoE configuration ID (e.g., measConfigAppLayerId). For example, the terminal may be configured with multiple QoE configurations (e.g., 7-25, 7-27) and independently perform QoE measurement according to each configuration (e.g., 7-30). To distinguish each configuration, each QoE configuration may include one QoE configuration ID. The terminal may independently generate a QoE measurement report for each QoE configuration, and may include the corresponding QoE configuration ID when transmitting the measurement report (e.g., 7-32, 7-35) to distinguish which QoE measurement configuration each QoE measurement report was generated according to. In 7-40 and / or 7-55, the base station (7-05) may indicate pauseReporting according to the QoE configuration ID. That is, the base station (7-05) can selectively pause or resume only some of the multiple QoE settings set for the terminal.

[0142] The following describes the suspension of measurement reporting for QoE measurements in RRC disabled / standby mode, which corresponds to an additional operation for the embodiment of FIG. 6.

[0143] In one embodiment of the present disclosure, in FIG. 6, a base station (e.g., base station 2) may want to temporarily suspend transmission (e.g., 6-70) of a QoE measurement report (e.g., 6-48) measured / stored by a terminal while in an inactive or standby mode (e.g., when the base station is experiencing RAN overload). The terminal may remain in the inactive or standby mode for a long time (e.g., 48 hours) and the size of the QoE measurement report stored during that time may be quite large (compared to the terminal performing a short time measurement in a connected mode and reporting the result immediately, as in 6-40). Therefore, allocating radio resources for this and receiving it while the base station is experiencing RAN overload may be a significant burden to the base station.

[0144] Accordingly, in one embodiment of the present disclosure, the base station can temporarily suspend QoE measurement reporting of the terminal (e.g., by QoE configuration ID) before steps 6-70 (e.g., after steps 6-65) (e.g., by sending to the terminal an indicator pauseReporting set to true for each QoE configuration ID to be suspended). Upon receiving this, the terminal can temporarily suspend transmission (e.g., 6-70) of stored QoE measurement reports (e.g., QoE measurement reports that the terminal stored in inactive / standby mode but could not transmit to base station 2 since receiving an RRC Setup message from base station 2). If the base station (e.g., base station 2) later sets pauseReporting to false for the suspended QoE configuration ID, the terminal can resume transmission of the QoE measurement reports. The terminal may include the stored QoE measurement report only for QoE settings that are not paused or suspended in the QoE measurement report message (to be transmitted from the terminal to the base station), and may not include the stored QoE measurement report for QoE settings that are paused or suspended in the QoE measurement report message (to be transmitted from the terminal to the base station). The specific operation may be described as in Table 9.

[0145] [Table 9]

[0146]

[0147] For the procedure for reporting application layer measurements of the terminal in relation to Table 9, refer to the procedure of FIG. 10.

[0148] In one embodiment of the present disclosure, the transmission (e.g., 6-70) of the QoE measurement report (e.g., 6-48) measured / stored by the terminal in the inactive or standby mode in FIG. 6 may not be stopped (even if the base station indicates pause). This may be because the pauseReporting indicator is intended to be used as an indicator for the base station to control (pause or resume) only reporting according to QoE measurements in the connected mode. In addition, this may be because, if the base station wants to temporarily not receive the QoE measurement report (e.g., 6-48) measured / stored by the terminal in the inactive / standby mode when RAN is overloaded, the base station may stop the transmission of the QoE measurement report of the terminal by providing or releasing an SRB (e.g., SRB4 or SRB5) setting required for the QoE measurement report to the terminal. (However, transmission control of the QoE measurement report of the terminal using the SRB setting of the base station may not be performed for each QoE setting.) The transmission of the QoE measurement report (e.g., 6-48) measured / stored by the terminal in the inactive or standby mode (e.g., QoE measurement report stored by the terminal in the inactive / standby mode but not transmitted to base station 2 since receiving the RRC Setup message from base station 2) (e.g., 6-70) may not be stopped (even if the base station instructs pause), as described in Table 10 or Table 11 below.

[0149] [Table 10]

[0150]

[0151] [Table 11]

[0152]

[0153] In one embodiment of the present disclosure, a terminal / base station may operate according to FIG. 6, and a base station (e.g., base station 1) may temporarily suspend QoE measurement reporting of a terminal (for some or all QoE configurations or IDs) (e.g., by transmitting an RRCReconfiguration message with pauseReporting set to true between steps 6-27 and 6-35). The base station may then transition the terminal to an inactive or standby mode (e.g., by transmitting an RRC Release message at step 6-40) without resuming QoE measurement reporting of the terminal. The terminal may then establish an RRC connection with a new base station (e.g., base station 2) (e.g., step 6-50). The terminal may then transfer its QoE configurations to base station 2 (step 6-65). At this time, the terminal may still have its QoE measurement reporting suspended (for some or all QoE configurations or IDs). However, base station 2 may not be aware that the terminal's QoE measurement reporting has been suspended. Therefore, even if base station 2 sets up an SRB (e.g., SRB4 or SRB5) for QoE measurement reporting to the UE, the UE may not be able to transmit the corresponding QoE measurement report to the base station, and the base station may not resume the QoE measurement reporting (even if there is no RAN overload situation) because it is unaware that the QoE measurement reporting has been stopped. As a result, a problem may occur in which the UE continues to perform QoE measurements, but only stores the corresponding reports and fails to transmit them to the base station.

[0154] In one embodiment of the present disclosure, to solve the above problem, the terminal may indicate / include in the QoE configuration information (e.g., 6-65) transmitted to the base station (e.g., base station 2) whether the terminal is in a pause state (e.g., whether QoE measurement reporting is paused or resumed, or whether QoE measurement reporting is paused or not) or a pauseReporting value set for the terminal (e.g., true or false). This may be indicated per QoE configuration (ID). Through this, base station 2 can determine whether the QoE measurement reporting of the terminal is paused or not (for some or all QoE configurations or IDs). If the terminal is in a paused state of QoE measurement reporting, base station 2 may resume the paused QoE measurement reporting (e.g., by transmitting an RRC Reconfiguration message with the pauseReporting value set to false to the terminal after step 6-65). When a terminal transmits QoE settings (e.g., MBS QoE settings or QoE settings applicable in inactive / standby mode as well as connected mode) to a base station (e.g., 6-65), it can be described as in Table 12 below so that the terminal can indicate / include a pauseReporting value (e.g., true or false) set to it.

[0155] [Table 12]

[0156]

[0157] In one embodiment of the present disclosure, to solve the above problem, a base station (e.g., base station 2) can always set a new pauseReporting value to true or false and transmit it to the terminal (e.g., via an RRCReconfiguration message) after retrieving (e.g., 6-65) a QoE configuration (e.g., an MBS QoE configuration or a QoE configuration applicable not only in connected mode but also in inactive / standby mode) from the terminal. Since the base station cannot retrieve the pauseReporting value as a QoE configuration, it does not know the pauseReporting value set in the terminal. Therefore, instead of performing an operation of transmitting the pauseReporting value (e.g., in MeasConfigAppLayer-r17) to the terminal with the purpose of maintaining the previously set value, the base station can always instruct / set a new pauseReporting value to the terminal on its own. Through this, the same configuration information (pauseReporting) can be matched between the terminal and the base station. The operation of the base station can be described as shown in Table 13 below.

[0158] [Table 13]

[0159]

[0160]

[0161] In one embodiment of the present disclosure, to address the above problem, after a base station (e.g., base station 2) retrieves (e.g., 6-65) a QoE configuration (e.g., an MBS QoE configuration or a QoE configuration applicable not only in connected mode but also in inactive / standby mode) from a terminal, the base station may assume that the QoE configuration is not paused (e.g., pauseReporting is set to false for the terminal, or pauseReporting has never been set to true). This is because the possibility that the base station (e.g., base station 2) to which the terminal is newly connected may be under RAN overload may be low. Similarly, the terminal may assume that the QoE configuration is not paused (e.g., pauseReporting is set to false for the terminal, or pauseReporting has never been set to true) even if the QoE measurement reporting is paused by base station 1 (e.g., after some point between 6-40 and 6-70). Compared to the previous embodiment, where the base station always resets the pauseReporting value, there may be an advantage in that the base station does not need to send a message (e.g., an RRC Reconfiguration message) to the terminal to set the pauseReporting value after retrieving the QoE settings. If the base station experiences RAN overload, the base station can transmit the pauseReporting value set to false. The operations of the terminal and the base station can be described as shown in Table 14 below.

[0162] [Table 14]

[0163]

[0164]

[0165] In one embodiment of the present disclosure, to address the above problem, a base station (e.g., base station 1) may instruct the resume of a paused QoE configuration (e.g., an MBS QoE configuration or a QoE configuration applicable not only in connected mode but also in inactive / standby mode) before the terminal transitions to inactive / standby mode (or before the base station transmits an RRC Release message) (e.g., before 6-40). To this end, the base station may transmit a message (e.g., RRCReconfiguration) to the terminal with a pauseReporting value set to false for the paused QoE configuration before transmitting the RRC Release message. As a result, the terminal may be in a non-paused state for all QoE configurations before transitioning to inactive / standby mode. Accordingly, a new base station (e.g., base station 2) connected to the terminal may know that all QoE configurations held and transmitted by the terminal are not paused. The operation of the base station may be described as shown in Table 15 below.

[0166] [Table 15]

[0167]

[0168]

[0169] In one embodiment of the present disclosure, a terminal and a base station can perform operations according to FIG. 6. In a connected mode, a terminal AS can transmit a QoE measurement report (e.g., 6-32) received from a terminal APP to a base station (e.g., 6-35). The terminal AS can transmit the QoE measurement report received from the terminal APP by including it in a container (e.g., measReportAppLayerContainer) within a QoE measurement report message (e.g., MeasurementReportAppLayer message).

[0170] Meanwhile, in inactive or standby mode, the terminal AS can store QoE measurement reports (e.g., 6-47) received from the terminal APP. This storage may be to prevent loss of QoE measurement reports. The terminal can transmit the stored QoE measurement reports (e.g., 6-70) when connecting to a new base station later (e.g., 6-50). The terminal AS can store the corresponding QoE measurement report or container if one of the following conditions is satisfied.

[0171] - Condition 1. If the terminal AS does not perform RRC segmentation on the QoE measurement report message (e.g., MeasurementReportAppLayer message) generated (encoded) using the QoE measurement report received from the terminal APP (or upper layer) and does not transmit and / or submit the QoE measurement report message (e.g., MeasurementReportAppLayer message) to the lower layer (e.g., PDCP layer).

[0172] - Condition 2. If the terminal AS performs RRC segmentation to divide a QoE measurement report message (e.g., MeasurementReportAppLayer message) generated (encoded) using the QoE measurement report received from the terminal APP (or upper layer) into multiple RRC segments, and does not transmit and / or submit some or all of the RRC segments to the lower layer (e.g., PDCP layer).

[0173] An example of the above terminal operation can be described as in Table 16 below.

[0174] [Table 16]

[0175]

[0176] In one embodiment of the present disclosure, a terminal and a base station can perform operations according to FIG. 7. For a non-paused QoE configuration, the terminal AS can transmit a QoE measurement report (e.g., 7-32) received from the terminal APP to the base station (e.g., 7-35). The terminal AS can transmit the QoE measurement report received from the terminal APP by including it in a container (e.g., measReportAppLayerContainer) within a QoE measurement report message (e.g., MeasurementReportAppLayer message).

[0177] On the other hand, for a paused QoE configuration, the terminal AS can store the QoE measurement report (e.g., 7-50) received from the terminal APP. The reason for storing this may be to prevent loss of the QoE measurement report. The terminal can transmit the stored QoE measurement report (e.g., 7-60) when the base station later resumes the QoE measurement report (e.g., 7-55). The terminal AS can store the corresponding QoE measurement report or container if either of the above-mentioned conditions 1 and 2 are satisfied. An example of the terminal operation may be described as shown in Table 17 below.

[0178] [Table 17]

[0179]

[0180] However, the embodiments according to Tables 16 and 17 above may not completely prevent the loss of QoE measurement reports. For example, QoE measurement report A that satisfies conditions 3 or 4 below may not be stored because it does not satisfy conditions 1 and 2, which may result in the loss of QoE measurement reports.

[0181] - Condition 3. If the terminal AS does not perform RRC segmentation on a QoE measurement report message (e.g., MeasurementReportAppLayer message) generated (encoded) using a QoE measurement report received from the terminal APP (or upper layer), and transmits and / or submits the QoE measurement report message (e.g., MeasurementReportAppLayer message) to a lower layer (e.g., PDCP layer), but does not receive confirmation of successful transmission of the QoE measurement report message from the lower layer.

[0182] - Condition 4. If the terminal AS performs RRC segmentation to divide a QoE measurement report message (e.g., MeasurementReportAppLayer message) generated (encoded) using the QoE measurement report received from the terminal APP (or upper layer) into multiple RRC segments, and transmits and / or submits all RRC segments to the lower layer (e.g., PDCP layer), but does not receive confirmation of successful transmission for at least one segment from the lower layer.

[0183] That is, even if a QoE measurement report message or RRC segment is submitted to a lower layer, it cannot be guaranteed that it has been successfully transmitted to the base station if a confirmation of successful transmission is not received from the lower layer. Therefore, in one embodiment of the present disclosure, even if conditions 1 and 2 as well as conditions 3 and 4 are satisfied, the terminal can store the corresponding QoE measurement report (for future transmission). Examples of the terminal operation can be described as in Tables 18 and 19 below.

[0184] [Table 18]

[0185]

[0186] [Table 19]

[0187]

[0188] FIG. 8 is a diagram showing the configuration of a terminal applied to examples of the present disclosure.

[0189] Referring to FIG. 8, the terminal includes an RF (Radio Frequency) processing unit (8-10), a baseband processing unit (8-20), a storage unit (8-30), and a control unit (8-40).

[0190] The RF processing unit (8-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (8-10) up-converts the baseband signal provided from the baseband processing unit (8-20) 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 (8-10) 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 shown, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (8-10) may include multiple RF chains. Furthermore, the RF processing unit (8-10) may perform beamforming. For the above beamforming, the RF processing unit (8-10) 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.

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

[0192] The baseband processing unit (8-20) and the RF processing unit (8-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (8-20) and the RF processing unit (8-10) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (8-20) and the RF processing unit (8-10) 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 (8-20) and the RF processing unit (8-10) 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.

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

[0194] The above control unit (8-40) controls the overall operations of the terminal. For example, the control unit (8-40) transmits and receives signals through the baseband processing unit (8-20) and the RF processing unit (8-10). In addition, the control unit (8-40) records and reads data in the storage unit (8-30). For this purpose, the control unit (8-40) may include at least one processor. For example, the control unit (8-40) 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 (8-42) as illustrated in the drawing.

[0195] FIG. 9 is a diagram showing the configuration of a base station applied to examples of the present disclosure.

[0196] Referring to FIG. 9, a base station according to an example of the present disclosure is configured to include an RF processing unit (9-10), a baseband processing unit (9-20), a backhaul communication unit (9-30), a storage unit (9-40), and a control unit (9-50).

[0197] The RF processing unit (9-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (9-10) up-converts the baseband signal provided from the baseband processing unit (9-20) 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 (9-10) 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 shown, but the base station may have multiple antennas. In addition, the RF processing unit (9-10) may include multiple RF chains. Furthermore, the RF processing unit (9-10) may perform beamforming. For the beamforming, the RF processing unit (9-10) may adjust the phase and magnitude of each of the signals 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.

[0198] The baseband processing unit (9-20) above 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 (9-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (9-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (9-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (9-20) 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 (9-20) divides the baseband signal provided from the RF processing unit (9-10) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (9-20) and the RF processing unit (9-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (9-20) and the RF processing unit (9-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0199] The above backhaul communication unit (9-30) provides an interface for performing communication with other nodes within the network. That is, the backhaul communication unit (9-30) converts a bit string transmitted from the main base station to other nodes, such as auxiliary base stations and core networks, into a physical signal, and converts a physical signal received from the other nodes into a bit string.

[0200] The storage unit (9-40) stores data such as basic programs, application programs, and configuration information for the operation of the base station. In particular, the storage unit (9-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (9-40) 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 (9-40) provides the stored data at the request of the control unit (9-50).

[0201] The control unit (9-50) controls the overall operations of the base station. For example, the control unit (9-50) transmits and receives signals through the baseband processing unit (9-20) and the RF processing unit (9-10) or through the backhaul communication unit (9-30). In addition, the control unit (9-50) records and reads data in the storage unit (9-40). For this purpose, the control unit (9-50) may include at least one processor and, as illustrated in the drawing, may include a multi-connection processing unit (9-52).

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

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

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

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

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

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

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

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

[0210] 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. In a method performed by a terminal in a wireless communication system, A step of storing a first application layer measurement report container corresponding to the first measurement setting and a second application layer measurement report container corresponding to the second measurement setting based on the first application layer measurement setting in an RRC (radio resource control) standby mode or an RRC inactive mode; A step of receiving a second application layer measurement setting from a base station after the terminal transitions to an RRC connection state; and A step of transmitting an application layer measurement report message to the base station based on the first application layer measurement setting and the second application layer measurement setting, A method in which a pause reporting indicator for the first measurement configuration is set as first information in the second application layer measurement configuration, and the application layer measurement reporting message does not include the first application layer measurement reporting container, but includes the second application layer measurement reporting container.

2. In paragraph 1, A step of receiving a third application layer measurement setting from the base station; and A method comprising the step of transmitting an application layer measurement report message including the first application layer measurement report container to the base station when the interruption report indicator for the first measurement setting is set to second information in the third application layer measurement setting.

3. In paragraph 1, A method for storing an application layer measurement reporting container associated with a measurement setup for which successful transmission of a message or at least one segment of the message from a lower layer has not been confirmed.

4. In paragraph 2, The above 1 measurement setting is identified based on the measurement setting application layer ID (measConfigAppLayerID), The above interruption reporting indicator is set for each measurement setting identified based on the above measurement setting application layer ID, A method in which the first information corresponds to True and the second information corresponds to False.

5. In paragraph 1, A method in which the terminal stores the first application layer measurement reporting container, but does not provide the application layer measurement reporting container to a lower layer, while the pause reporting indicator for the first measurement setting is set to the first information.

6. In a method performed by a base station in a wireless communication system, A step of establishing an RRC connection with a terminal in RRC (radio resource control) standby mode or RRC inactive mode; A step of transmitting a second application layer measurement configuration for application layer measurement reporting of the terminal, wherein the terminal stores a first application layer measurement report container corresponding to the first measurement configuration and a second application layer measurement report container corresponding to the second measurement configuration based on the first application layer measurement configuration in the RRC standby mode or the RRC inactive mode; and A step of receiving an application layer measurement report message from the terminal based on the first application layer measurement setting and the second application layer measurement setting, A method in which a pause reporting indicator for the first measurement configuration is set as first information in the second application layer measurement configuration, and the application layer measurement reporting message does not include the first application layer measurement reporting container, but includes the second application layer measurement reporting container.

7. In paragraph 6, A step of transmitting a third application layer measurement setting to the terminal; and If the interruption report indicator for the first measurement setting is set to second information in the third application layer measurement setting, a step of receiving an application layer measurement report message including the first application layer measurement report container from the terminal is included. The terminal stores the first application layer measurement reporting container, but does not provide the application layer measurement reporting container to a lower layer, and the pause reporting indicator for the first measurement setting is set to the first information. The above 1 measurement setting is identified based on the measurement setting application layer ID (measConfigAppLayerID), The above interruption reporting indicator is set for each measurement setting identified based on the above measurement setting application layer ID, A method in which the first information corresponds to True and the second information corresponds to False.

8. In paragraph 6, A method for storing an application layer measurement reporting container associated with a measurement setup for which successful transmission of a message or at least one segment of the message from a lower layer has not been confirmed.

9. In the terminal of a wireless communication system, Transmitter and receiver; and At least one processor connected to the transceiver, At least one processor, Store a first application layer measurement report container corresponding to the first measurement setting and a second application layer measurement report container corresponding to the second measurement setting based on the first application layer measurement setting in RRC (radio resource control) standby mode or RRC disabled mode, After the terminal transitions to the RRC connection state, it receives the second application layer measurement settings from the base station, and Based on the first application layer measurement setting and the second application layer measurement setting, control is provided to transmit an application layer measurement report message to the base station, A terminal in which a pause reporting indicator for the first measurement configuration is set as first information in the second application layer measurement configuration, and the application layer measurement reporting message does not include the first application layer measurement reporting container, but includes the second application layer measurement reporting container.

10. In paragraph 9, At least one processor, Receives third application layer measurement settings from the above base station, and A terminal that controls to transmit an application layer measurement report message including the first application layer measurement report container to the base station when the interruption report indicator for the first measurement setting is set to second information in the third application layer measurement setting.

11. In paragraph 9, The terminal stores an application layer measurement report container related to a measurement setup for which successful transmission of a message or at least one segment of the message from a lower layer has not been confirmed.

12. In paragraph 10, The above 1 measurement setting is identified based on the measurement setting application layer ID (measConfigAppLayerID), The above interruption reporting indicator is set for each measurement setting identified based on the above measurement setting application layer ID, A terminal in which the first information corresponds to True and the second information corresponds to False.

13. In paragraph 9, The terminal is a terminal in which the pause reporting indicator for the first measurement setting is set to the first information, and stores the first application layer measurement reporting container, but does not provide the application layer measurement reporting container to a lower layer.

14. In a base station of a wireless communication system, Transmitter and receiver; and At least one processor connected to the transceiver, At least one processor, Establish an RRC connection with a terminal in RRC (radio resource control) standby mode or RRC inactive mode, In the RRC standby mode or the RRC inactive mode, the terminal transmits a second application layer measurement configuration for application layer measurement reporting of the terminal, storing a first application layer measurement report container corresponding to the first measurement configuration and a second application layer measurement report container corresponding to the second measurement configuration, based on the first application layer measurement configuration, to the terminal, and Based on the first application layer measurement setting and the second application layer measurement setting, control to receive an application layer measurement report message from the terminal, A base station in which a pause reporting indicator for the first measurement configuration is set as first information in the second application layer measurement configuration, and the application layer measurement reporting message does not include the first application layer measurement reporting container, but includes the second application layer measurement reporting container.

15. In paragraph 14, The at least one processor transmits a third application layer measurement configuration to the terminal, and if the interruption report indicator for the first measurement configuration is set to second information in the third application layer measurement configuration, controls receiving an application layer measurement report message including the first application layer measurement report container from the terminal, The terminal stores the first application layer measurement reporting container, but does not provide the application layer measurement reporting container to a lower layer, and the pause reporting indicator for the first measurement setting is set to the first information. The above 1 measurement setting is identified based on the measurement setting application layer ID (measConfigAppLayerID), The above interruption reporting indicator is set for each measurement setting identified based on the above measurement setting application layer ID, A base station where the first information corresponds to True and the second information corresponds to False.

Images