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

Abstract

The present invention relates to a method and a device for measuring quality of experience (QoE) in an inactive mode and an idle mode. The method performed by a terminal comprises the steps of: receiving a first RRC reconfiguration message including application layer measurement configuration information, the measurement configuration information including parameter information related to a RAN visible application layer measurement report; on the basis of the parameter information, transmitting, to a base station, an application layer measurement report message including the RAN visible application layer measurement report; and discarding the RAN visible application layer measurement report when a second RRC reconfiguration message for configuring to release the parameter information related to the measurement report is received.

Description

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

[0001] The present invention relates to the operation of terminals and base stations in mobile communication systems. More specifically, the present invention relates to a method and device for measuring Quality of Experience (QoE) in inactive and standby modes.

[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 meet 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 goes beyond the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The present disclosure proposes a method for a terminal to measure Quality of Experience (QoE) in inactive mode and standby mode.

[0009] The technical problems to be achieved in the embodiments of the present disclosure 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 disclosure belongs from the description below.

[0010] In order to solve the above-mentioned problem, the present disclosure proposes a method performed by a terminal in a wireless communication system. More specifically, the method comprises the steps of: receiving, from a base station, a first Radio Resource Control (RRC) reconfiguration message including application layer (Application Layer) measurement configuration information, wherein the Application Layer measurement configuration information includes parameter information related to a RAN Visible Application Layer measurement report; transmitting, to the base station, an application layer measurement report message including a measurement report of a RAN Visible Application Layer based on the parameter information related to the RAN Visible Application Layer measurement report; and, when receiving, from the base station, a second RRC reconfiguration message that sets to release the parameter information related to the RAN Visible Application Layer measurement report, discarding the measurement report of the RAN Visible Application Layer.

[0011] In order to solve the above-mentioned problem, the present disclosure proposes a method performed by a base station in a wireless communication system. More specifically, the method comprises the steps of: transmitting, to a terminal, a first Radio Resource Control (RRC) reconfiguration message including application layer (Application Layer) measurement configuration information, wherein the Application Layer measurement configuration information includes parameter information related to a RAN Visible Application Layer measurement report; and receiving, from the terminal, an application layer measurement report message including a measurement report of a RAN Visible Application Layer based on the parameter information related to the RAN Visible Application Layer measurement report, wherein when transmitting, to the terminal, a second RRC message configured to release parameter information related to the RAN Visible Application Layer measurement report, the second RRC reconfiguration message configured to release parameter information related to the RAN Visible Application Layer measurement report is characterized in that it is related to discarding the measurement report of the RAN Visible Application Layer.

[0012] In order to solve the above-mentioned problem, the present disclosure proposes a terminal in a wireless communication system. More specifically, the terminal includes a transceiver for transmitting and receiving a signal, and a control unit coupled with the transceiver, wherein the control unit receives, from a base station, a first Radio Resource Control (RRC) reconfiguration message including application layer (Application Layer) measurement configuration information, wherein the Application Layer measurement configuration information includes parameter information related to a RAN Visible Application Layer measurement report, and transmits, to the base station, an application layer measurement report message including a measurement report of a RAN Visible Application Layer based on the parameter information related to the RAN Visible Application Layer measurement report, and when receiving a second RRC reconfiguration message from the base station that sets to release parameter information related to the RAN Visible Application Layer measurement report, the terminal discards the measurement report of the RAN Visible Application Layer.

[0013] In order to solve the above-mentioned problem, the present disclosure proposes a base station in a wireless communication system. More specifically, the base station includes a transceiver for transmitting and receiving a signal, and a control unit coupled with the transceiver, wherein the control unit comprises: a step of transmitting, to a terminal, a first Radio Resource Control (RRC) reconfiguration message including application layer (Application Layer) measurement configuration information, wherein the Application Layer measurement configuration information includes parameter information related to a RAN Visible Application Layer measurement report; and a step of receiving, from the terminal, an application layer measurement report message including a measurement report of a RAN Visible Application Layer based on the parameter information related to the RAN Visible Application Layer measurement report, wherein when transmitting a second RRC reconfiguration message for setting to release the parameter information related to the RAN Visible Application Layer measurement report to the terminal, the second RRC message for setting to release the parameter information related to the RAN Visible Application Layer measurement report is characterized in that it is related to discarding the measurement report of the RAN Visible Application Layer.

[0014] According to a method for measuring Quality of Experience (QoE) in an inactive mode and a standby mode according to an embodiment of the present disclosure, QoE can be improved.

[0015] More specifically, the base station can improve QoE by allocating more radio resources to terminals experiencing poor QoE based on QoE reports.

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

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

[0018] FIG. 1b is a diagram for explaining a wireless connection state transition in a mobile communication system according to an embodiment of the present disclosure.

[0019] FIG. 1c is a flowchart illustrating a procedure for setting up and / or reporting signaling-based Quality of Experience (QoE) measurements according to one embodiment of the present disclosure.

[0020] FIG. 1d is a flowchart illustrating a procedure for setting up and / or reporting a Management-based Quality of Experience (QoE) measurement according to one embodiment of the present disclosure.

[0021] FIG. 1e is a flowchart illustrating a procedure for setting up and / or reporting radio access network (RAN) visible Quality of Experience (QoE) measurements according to one embodiment of the present disclosure.

[0022] FIG. 1f is a flowchart illustrating a setup and / or reporting procedure for a terminal to support Quality of Experience (QoE) measurement in inactive and standby mode according to one embodiment of the present disclosure.

[0023] FIG. 1g is a block diagram illustrating the internal structure of a terminal applied to an embodiment of the present disclosure.

[0024] FIG. 1h is a block diagram illustrating the structure of a base station applied to an embodiment of the present disclosure.

[0025] Hereinafter, the operating principles of the present invention will be described in detail with reference to the attached drawings. In the following description of the present invention, if a detailed description of a related known function or configuration is judged to unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present invention, and these may vary depending on the intention or custom of the user or operator. Therefore, the definitions should be made based on the contents throughout this specification. Terms used in the following description, such as terms for identifying connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information, are examples for the 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.

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

[0027] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0028] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which the embodiments of the present disclosure may be applied, and 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure. It will be appreciated that each block of the processing flow diagrams and combinations of the flow diagrams can be executed by computer program instructions.

[0029] These computer program instructions may be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, so that the instructions executed by the processor of the computer or other programmable data processing apparatus create means for performing the functions described in the flowchart block(s). These computer program instructions may also be stored in a computer-available or computer-readable memory that can be directed to a computer or other programmable data processing apparatus to implement functions in a particular manner, so that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes instruction means for performing the functions described in the flowchart block(s). The computer program instructions may also be installed on a computer or other programmable data processing apparatus, so that a series of operational steps are performed on the computer or other programmable data processing apparatus to create a computer-implemented process, so that the instructions executing on the computer or other programmable data processing apparatus can provide steps for performing the functions described in the flowchart block(s).

[0030] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the corresponding function. In this case, the term '~unit' used in the present embodiment means software or a hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the '~unit' may perform 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 execute one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality 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'. In addition, the components and '~ units' may be implemented to reproduce one or more CPUs within a device or a secure multimedia card. Also, in an embodiment, the '~ unit' may include one or more processors.

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

[0032] Referring to FIG. 1a, a wireless access network of a mobile communication system (New Radio, NR) according to an embodiment of the present disclosure, as illustrated in FIG. 1a, is composed of a base station (next generation Node B, hereinafter referred to as gNB) (1a-10) and a mobility management function (access and mobility management function, AMF) (1a-05, New Radio Core Network). A user equipment (New Radio User Equipment, hereinafter referred to as NR UE or terminal) (1a-15) can access an external network through the gNB (1a-10) and the AMF (1a-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.

[0033] In Fig. 1a, the gNB corresponds to an eNB (Evolved Node B) of a conventional long-term evolution (LTE) system. The gNB is connected to NR UEs via a wireless channel and can provide superior services than conventional Node Bs (1a-20). In a 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 is required to collect status information such as buffer status, available transmission power status, and channel status of UEs and perform scheduling, and this is handled by the gNB (1a-10). One gNB typically controls multiple cells.

[0034] In order to implement ultra-high-speed data transmission compared to existing LTE, it can have a bandwidth exceeding the existing maximum, and beamforming technology can be additionally applied using orthogonal frequency division multiplexing (OFDM) as a wireless access technology.

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

[0036] The access and mobility management function (AMF) (1a-05) performs functions such as mobility support, bearer setup, and quality of service (QoS) setup. The AMF is a device that is responsible for various control functions as well as the mobility management function for the terminal and can be connected to multiple base stations. In addition, the mobile communication system according to one embodiment of the present disclosure can be interoperable with the existing LTE system, and the AMF can be connected to the mobility management emtity (MME) (1a-25) through a network interface. The MME is connected to the eNB (1a-30), which is an existing base station. A terminal that supports LTE-NR Dual Connectivity can transmit and receive data while maintaining a connection to not only the gNB but also the eNB (1a-35).

[0037] FIG. 1b is a diagram for explaining a wireless connection state transition in a mobile communication system according to an embodiment of the present disclosure.

[0038] A mobile communication system according to one embodiment of the present disclosure has three radio access states (RRC (radio resource control) states) or RRC modes.

[0039] Connected mode (RRC_CONNECTED, 1b-05) is a wireless connection state in which the terminal can transmit and receive data.

[0040] Standby mode (RRC_IDLE, 1b-30) is a wireless connection state in which the terminal monitors whether paging is being transmitted to it. The above-mentioned connected mode and standby mode are wireless connection states also applicable to existing long-term evolution (LTE) systems, and the detailed technology is identical to that of existing LTE systems. A mobile communication system according to an embodiment of the present disclosure may be a next-generation mobile communication system.

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

[0042] - Cell re-selection mobility;

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

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

[0045] - Paging is initiated by NR RAN;

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

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

[0048] Referring to 1b-10, a terminal in an inactive wireless connection state according to one embodiment of the present disclosure can transition to a connected mode or an idle mode using a specific procedure. The terminal transitions from an inactive mode to a connected mode using a resume procedure, and transitions from a connected mode to an inactive mode using a release procedure including suspend configuration information.

[0049] This state transition procedure is performed by transmitting and receiving one or more radio resource control (RRC) messages between the terminal and the base station, and consists of one or more steps.

[0050] Referring to 1b-20, the terminal can transition from inactive mode (INACTIVE) to standby mode (IDLE) through the Resume and Release procedures.

[0051] Referring to Step 1b-25, the terminal can transition between connected mode (CONNECTED) and idle mode (IDLE). This transition between connected mode (CONNECTED) and idle mode (IDLE) follows existing LTE technology. That is, the transition between connected mode (CONNECTED) and idle mode (IDLE) is accomplished through an establishment or release procedure.

[0052] FIG. 1c is a flowchart illustrating a procedure for setting up and / or reporting signaling-based Quality of Experience (QoE) measurements according to one embodiment of the present disclosure.

[0053] Referring to FIG. 1c, in step 1c-10, the AS (Access stratum, 1c-05) of the terminal can transmit terminal capability information to the base station (or NG-RAN, 1c-15).

[0054] More specifically, the AS (1c-05) of the terminal can transmit information indicating whether it supports QoE (quality of experience) measurement for each service type to the base station (or NG-RAN, 1c-15) through a UE capability message (e.g., UECapabilityInformation).

[0055] The above service may include streaming, MTSI (Multimedia Telephony Service for IMS (IP (internet protocol) Multimedia Subsystem)), or VR (virtual reality), and information indicating whether QoE measurement is supported for each service type may be qoe-Streaming-MeasReport, qoe-MTSI-MeasReport, or qoe-VR-MeasReport.

[0056] Before a terminal transmits a UE capability message, the base station may transmit a message (e.g., UECapabilityEnquiry) to the terminal to request a UE capability message.

[0057] Additionally, the terminal or the AS (1c-05) of the terminal can report to the base station (1c-15) whether or not RAN visible QoE measurement is supported for each service type through a UE capability message.

[0058] The above service may include streaming or VR, and the information indicating whether RAN visible QoE measurement is supported for each service type may be ran-VisibleQoE-Streaming-MeasReport or ran-VisibleQoE-VR-MeasReport.

[0059] Additionally, the terminal or the AS (1c-05) of the terminal can report to the base station whether it supports UL RRC segmentation for QoE report messages (e.g., ul-MeasurementReportAppLayer-Seg) via a UE capability message.

[0060] The above UE capability message includes ASN.1 (Abstract Syntax Notation One) information as shown in Table 1 below, and the description of the related parameters (i.e., QoE measurement parameters) is as shown in Table 2 below.

[0061] [Table 1]

[0062]

[0063] [Table 2]

[0064]

[0065] Long term evolution (LTE) can support streaming and MTSI (Multimedia Telephony Service for IMS (IP Multimedia Subsystem)). In the case of New radio (NR), in addition to the services supported by LTE, support for VR (Virtual Reality) services was defined in Rel-17. It was also defined that additional services such as MBMS (Multimedia Broadcast Multicast Services) and XR (Extended Reality) can be supported in future releases.

[0066] In step 1c-30, OAM (Operations Administration and Maintenance, 1c-20) can provide QoE (quality of experience) measurement configuration information to CN (Core Network, 1c-25).

[0067] In step 1c-35, the CN (1c-25) that has received QoE measurement configuration information can activate QoE measurement by transmitting the QoE measurement configuration information to the base station (1c-15).

[0068] In step 1c-40, the base station (1c-15) that has received configuration information from the CN (1c-25) can transmit QoE configuration information to the terminal's AS (1c-05) through a radio resource control (RRC) message (1c-40).

[0069] The above RRC message may include an RRCReconfiguration message or an RRCResume message.

[0070] Additionally, the RRC message may include an IE (APPLayerMeasConfig) as in Table 3 below, and the description of the related parameters is as in Table 4 below.

[0071] [Table 3]

[0072]

[0073] [Table 4]

[0074]

[0075] In addition, according to one embodiment of the present disclosure, a terminal AS (1c-05) that has received QoE setting information from a base station through an RRC message can operate according to the procedure described in Table 5 below.

[0076] [Table 5]

[0077]

[0078] As previously mentioned, in step 1c-50, for QoE measurement settings included in measConfigAppLayerToAddModList, the AS layer (1c-05) of the terminal can transmit part or all of the setting information to the upper layer or application layer (UE APP, 1c-45) of the terminal via AT Command.

[0079] Additionally, the AS layer (1c-05) of the terminal may send an AT Command to the APP (1c-45) of the terminal to instruct and / or command the terminal to delete stored configuration information for QoE measurement configuration included in measConfigAppLayerToAddReleaseList.

[0080] In step 1c-55, the terminal APP (1c-45) can perform QoE measurement based on the received configuration information. In addition, the terminal APP (1c-45) can report the results of the measurement based on the configuration information to the terminal AS (1c-05) via an AT command.

[0081] In step 1c-60, the terminal AS (1c-05) that has received the measurement result report from the APP (1c-45) of the terminal can report the measurement result to the base station (1c-15) through an RRC message.

[0082] The above RRC message may include a MeasurementReportAppLayer message.

[0083] SRB (signaling radio bearer) 4 can be used to report QoE measurement results. 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.

[0084] [Table 6]

[0085]

[0086] [Table 7]

[0087]

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

[0089] [Table 8]

[0090]

[0091] In step 1c-70, the base station (1c-15) can transmit the measurement result report received from the terminal to the final server (trace collection entity, TCE) or measurement collection entity (MCE), 1c-65) that collects the measurement report.

[0092] FIG. 1d is a flowchart illustrating a procedure for setting up and / or reporting a Management-based Quality of Experience (QoE) measurement according to one embodiment of the present disclosure.

[0093] Among the operations performed in the management-based QoE setup and / or reporting procedure, operations that are identical / similar to and overlapping with the operations performed in the signaling-based QoE setup and / or reporting procedure described in FIG. 1c will be omitted for separate description, and the differences between the management-based QoE setup and / or reporting procedure and the signaling-based procedure will be mainly described with reference to FIG. 1d.

[0094] In a manner related to a Management-based Quality of Experience (QoE) configuration and / or reporting procedure according to one embodiment of the present disclosure, an Operations Administration and Maintenance (OAM, 1d-05) may directly transmit QoE measurement configuration information (or QoE measurement configuration) to a base station (NG-RAN, 1d-10).

[0095] More specifically, in step 1d-15, OAM (Operations Administration and Maintenance, 1d-05) can instruct the base station (1d-10) to activate QoE measurement of the terminal by directly transmitting QoE measurement settings to the base station without going through the core network (CN).

[0096] The base station (1d-10) that receives the above QoE measurement settings can search for a single or multiple terminals that meet at least one condition. The condition may be related to at least one of area scope, application layer capability, and service type.

[0097] In step 1d-20, the base station (1d-10) may transmit (or forward) QoE measurement settings to one of the single or multiple terminals found via a radio resource control (RRC) message. The RRC message may include an RRCReconfiguration message or an RRCresume message.

[0098] Each terminal that receives the above RRC message can exchange settings and measurement results for QoE measurement through AT Command between the AS layer and the APP, as described above in FIG. 1c.

[0099] In step 1d-40, the AS layer of the terminal can report the measurement results for QoE measurement obtained from the APP of the terminal to the base station (1d-10) via an RRC message.

[0100] Thereafter, in step 1d-45, the base station (1d-10) can transmit the measurement result for QoE measurement to the final server (trace collection entity, TCE) or measurement collection entity (MCE).

[0101] FIG. 1e is a flowchart illustrating a procedure for setting up and / or reporting radio access network (RAN) visible Quality of Experience (QoE) measurements according to one embodiment of the present disclosure.

[0102] In accordance with the signaling-based QoE configuration and / or reporting procedure described in FIG. 1c and the management-based QoE configuration and / or reporting procedure described in FIG. 1d, Quality of Experience (QoE) measurements are configured by Operations Administration and Maintenance (OAM). In addition, QoE measurement reports generated according to the above configurations are collected in a trace collection entity (TCE) and / or a measurement collection entity (MCE), and the QoE measurement reports can be used by operators for network optimization.

[0103] Meanwhile, the base station cannot read or understand the report regarding the OAM-based QoE measurement transmitted by the terminal. More specifically, the MeasurementReportAppLayer message includes the measurement report generated by the application layer of the terminal in the measurementReportAppLayerContainer, but since it is stored in the form of OCTEC STRING, the base station (or the RRC layer of the base station) cannot read or understand the measurement report generated by the application layer of the terminal. To solve this problem, that is, to enable the base station to read the QoE measurement report of the terminal and utilize it for network optimization such as radio resource management, the 3rd Generation Partnership Project (3GPP) defined and introduced RAN visible QoE (RVQoE) measurement.

[0104] According to one embodiment of the present disclosure, RVQoE measurements may be defined to be limited to specific service types (e.g., streaming, VR).

[0105] At step 1e-05, the terminal can report to the base station whether it supports RVQoE measurement by service type (1e-05).

[0106] The above service may include streaming or VR. In this case, the message transmitted by the terminal to the base station may use the UECapabilityInformation message. 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 the streaming service. The terminal may include or set the ran-VisibleQoE-VR-MeasReport parameter in the UECapabilityInformation message and transmit it to the base station for the VR service.

[0107] In step 1e-10, the base station may transmit a radio resource control (RRC) message including Quality of Experience (QoE) measurement settings and / or RVQoE measurement settings to the terminal (or AS of the terminal).

[0108] More specifically, the base station can determine whether the terminal supports RVQoE measurement for each service type based on whether the terminal supports RVQoE measurement for each service type transmitted to the base station by the terminal (e.g., streaming, VR). Based on this, the base station can generate an RVQoE measurement configuration and transmit it to the terminal. At this time, the RVQoE measurement configuration can be transmitted together with an Operations Administration and Maintenance (OAM)-based QoE measurement configuration.

[0109] RVQoE measurement settings can be included in the RRCReconfiguration or RRCResume message. The base station can instruct the terminal to set up or release RVQoE measurements by setting or releasing the ran-VisibleParameters parameter in the AppLayerMeasConfig information element (IE).

[0110] The above ran-VisibleParameters parameter may include a RAN-VisibleParameters IE, through which some or all of the following parameters may be provided to the terminal.

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

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

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

[0114] In step 1e-15, the AS layer of the terminal can transmit configuration information such as the previously described ran-VisiblePeriodicity to the APP layer of the terminal. At this time, the RVQoE measurement configuration can be transmitted to the APP layer together with the OAM-based QoE measurement configuration. In addition, the AS layer of the terminal can transmit the QoE measurement configuration and / or the RVQoE measurement configuration to the UE App layer via an AT command.

[0115] At step 1e-20, the APP of the terminal can perform QoE measurement based on the RVQoE measurement configuration information, generate an RVQoE measurement report, and transmit it to the AS layer of the terminal (1e-20). At this time, the RVQoE measurement report can be transmitted to the AS layer together with the OAM-based QoE measurement report. The APP of the terminal can transmit the QoE measurement report and / or the RVQoE measurement report to the UE AS through an AT command.

[0116] At step 1e-25, the AS layer of the terminal that received the RVQoE measurement report can forward / transmit / report the forwarded RVQoE measurement report to the base station. At this time, the RVQoE measurement report can be forwarded / transmitted / reported to the base station together with the OAM-based QoE measurement report. At this time, 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.

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

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

[0119] - 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, and based on the identification result, can optimize resource allocation and scheduling for the PDU session(s) indicated by this parameter.

[0120] 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 more radio resources to the terminal determined to be experiencing poor QoE.

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

[0122] According to one embodiment of the present disclosure, QoE configuration information (e.g., 1c-50 or 1d-30) received by a terminal application layer (terminal APP or UE APP) may include area range information (e.g., LocationFilter). The terminal APP can use the area range information (LocationFilter) to determine the area range in which the terminal should perform QoE measurement. 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 to maintain an ongoing QoE measurement session. For example, as long as the terminal does not request QoE configuration from the base station, the terminal may continue to maintain an ongoing QoE measurement session.

[0123] FIG. 1f is a flowchart illustrating a setup and / or reporting procedure for a terminal to support Quality of Experience (QoE) measurement in inactive and standby mode according to one embodiment of the present disclosure.

[0124] The 3rd Generation Partnership Project (3GPP) standardized support for Quality of Experience (QoE) measurements in connected mode in Release 17. Since then, 3GPP has expanded its QoE measurement support to support QoE measurements for Multicast Broadcast Service (MBS) services in Release 18, and is currently standardizing methods to support QoE measurements in not only connected mode (RRC_CONNECTED), but also in inactive mode (RRC_INACTIVE) and idle (RRC_IDLE) modes.

[0125] The QoE setup / measurement / reporting procedure between a terminal and a base station in the connected mode (RRC_CONNECTED) as well as the inactive mode (RRC_INACTIVE) and standby (RRC_IDLE) mode for the MBS (Multicast Broadcast Service) service supported by the present disclosure may be as follows.

[0126] At step 1f-15, a base station (1f-05) (e.g., base station 1) and a terminal AS (1f-10) can establish (or establish) a radio resource control (RRC) connection.

[0127] In step 1f-20, the base station (1f-05) can transmit a UE Capability request message (e.g., UECapabilityEnquiry) to the terminal, and the terminal (or the terminal's AS, 1f-10) receiving the message can transmit a UE Capability message (e.g., UECapabilityInformation) to the base station. At this time, the UE Capability request message can be UECapabilityEnquiry, and the UE Capability message can be UECapabilityInformation.

[0128] The terminal may transmit a UE Capability message including a QoE measurement-related support capability indicator. For example, the terminal may transmit to the base station whether it supports QoE measurement for MBS (e.g., broadcast) services. Alternatively, the terminal may transmit to the base station whether it supports QoE measurement in connected mode (RRC_CONNECTED), inactive mode (RRC_INACTIVE), and standby (RRC_IDLE) mode. Steps 1f-20 may correspond to steps 1d-25 or 1c-10.

[0129] In steps 1f-25 and 1f-27, the base station may provide QoE setting information (or QoE measurement configuration) to the terminal (which may include a UE AS or a UE APP). Step 1f-25 may correspond to steps 1d-20 and 1d-30, or steps 1c-40 and 1c-50.

[0130] For example, the QoE configuration information may include QoE measurement configuration information for an MBS (e.g., broadcast) service. Alternatively, the QoE configuration information may include configuration information for QoE measurement in a connected mode (RRC_CONNECTED), an inactive mode (RRC_INACTIVE), and a standby mode (RRC_IDLE).

[0131] At step 1f-30, when the terminal AS (1f-10) is in a connection mode, the terminal APP (1f-12) can perform QoE measurement for the MBS service using the QoE setting information (e.g., when the MBS service is received).

[0132] In step 1f-32, the terminal APP (1f-12) can transmit QoE measurement results or measurement reports for the MBS service to the terminal AS layer (1f-10). Step 1f-32 may correspond to step 1c-55 or step 1d-35.

[0133] In step 1f-35, the terminal AS (1f-10) can report the QoE measurement report received from the terminal APP layer to the base station (gNB1, 1f-01). More specifically, if the terminal is in a connected mode and the base station has set an SRB (e.g., SRB4 or SRB5) for the QoE measurement report, the QoE measurement report can be reported to the base station immediately. Step 1f-35 may correspond to step 1c-60 or step 1d-40.

[0134] In step 1f-40, the base station (gNB1, 1f-01) can transmit an RRC Release message to the terminal, and the terminal that receives the RRC Release message can transition to an inactive mode or standby mode. The terminal can receive MBS service even in the inactive mode or standby mode.

[0135] In step 1f-45, the terminal APP (1f-12) can perform QoE measurement for the MBS service based on (or using) the QoE setting information received in step 1f-25 while the AS receives the MBS service in an inactive or standby mode.

[0136] At step 1f-47, the terminal APP (1f-12) can transmit the QoE measurement result or measurement report generated through QoE measurement to the terminal AS (1f-10).

[0137] In step 1f-48, the terminal AS (1f-10) is in an inactive or standby mode, and thus may not immediately transmit the QoE measurement report to the base station, but may instead store it. For example, the terminal APP may transmit the generated QoE measurement report to the terminal AS, which may then store it.

[0138] At step 1f-50, the terminal can establish (or establish) an RRC connection with a (new) base station (1f-49) (e.g., base station 2 or the second base station).

[0139] More specifically, the terminal can establish an RRC connection with a new base station (gNB2, 1f-49) by receiving an RRC Setup or RRC resume message.

[0140] At step 1f-55, the terminal (1f-10) may transmit (or indicate) to base station 2 (1f-49) that the terminal is storing QoE measurement report or MBS QoE configuration information (availability).

[0141] More specifically, when the terminal (1f-10) establishes an RRC connection in step 1f-50, the terminal can indicate to the base station (e.g., base station 2) that the terminal is storing QoE measurement report (e.g., QoE measured by the terminal in inactive / standby mode) or MBS QoE configuration information (e.g., availability) through the RRCSetupComplete or RRCResumeComplete message.

[0142] In step 1f-60, base station 2 (1f-49) that has received availability from the terminal can set up a signaling radio bearer (SRB) to the terminal.

[0143] More specifically, base station 2 (1f-49) that has received the availability may set up an SRB for transmitting QoE measurement reports and / or configurations to the terminal. The SRB may include SRB4 or SRB5.

[0144] For the above SRB setup, the RRC Reconfiguration or RRC Resume message can be used.

[0145] In step 1f-60, if the RRC Resume message is used, step 1f-55 (e.g., transmitting availability via the RRCResumeComplete message of the terminal) may be performed after step 1f-60. If the RRC Resume message is used, this may include a case where the base station transmits the RRC Resume message to resume the RRC connection of the terminal in the inactive mode.

[0146] At step 1f-65, the terminal can transmit QoE setting information to base station 2 (1f-49).

[0147] More specifically, a newly connected base station (e.g., base station 2, 1f-49) may not have QoE configuration information set for the terminal.

[0148] A case where base station 2 does not include QoE configuration information set for a terminal may include a case where an inactive / standby mode terminal receives an RRC Setup message and establishes an RRC connection in 1f-50. In this case, the QoE configuration information set for the terminal may include QoE configuration information for an MBS service or QoE configuration information that is applied not only in the connection mode of the terminal but also in the inactive / standby mode. 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 information.

[0149] - QoE reference

[0150] - TCE or MCE address or ID

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

[0152] - Service type

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

[0154] - Available RAN visible QoE indicator information

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

[0156] - Priority value of the corresponding QoE setting

[0157] The new base station 2 (gNB2, 1f-19) can add / change / release the QoE settings of the terminal by retrieving the above information or by obtaining information about the QoE settings set for the terminal. In addition, the base station 2 (gNB2, 1f-19) can forward the QoE measurement report received from the terminal to the correct TCE / MCE.

[0158] At step 1f-70, the terminal (or its AS, 1f-10) can transmit a QoE measurement report (measured and stored in inactive / standby mode) (e.g., a QoE measurement report stored in 1f-48) to the base station.

[0159] At step 1f-75, the APP (1f-12) of the terminal can perform QoE measurements (even in connected mode).

[0160] At step 1f-80, the APP (1f-12) of the terminal can transmit QoE measurement report information generated according to QoE measurement to the AS (1f-10) of the terminal.

[0161] At step 1f-85, the AS (1f-10) of the terminal can report QoE measurement report information received from the APP of the terminal (in connected mode) to the base station.

[0162] An RRC message format for QoE measurement report used when a terminal transmits a QoE measurement report (e.g., step 1f-35 or step 1f-70) defined in standard document TS 38.331 according to an embodiment of the present disclosure may be as shown in Table 9 below.

[0163] [Table 9]

[0164]

[0165]

[0166]

[0167]

[0168]

[0169] When a terminal transmits a QoE measurement report (e.g., a QoE measurement report measured and stored by the terminal in an inactive or standby mode) (e.g., 1f-70), the terminal may include multiple QoE measurement report parameters in a single QoE measurement report message. The QoE measurement report message may include a MeasurementReportAppLayer message, and the QoE measurement report parameters may include MeasReportAppLayer or MeasReportAppLayer-r17 or MeasReportAppLayer-v1800).

[0170] Each MeasReportAppLayer may include, for one QoE ID (e.g., measConfigappLayerId), a container (e.g., measReportAppLayerContainer) containing one QoE measurement report received from the terminal APP, or a list of containers (e.g., measReportAppLayerContainerList) containing multiple QoE measurement reports received from the terminal APP.

[0171] According to one embodiment of the present disclosure, a QoE measurement report container list (e.g., measReportAppLayerContainerList) may include QoE measurement reports measured and stored in an inactive mode or a standby mode.

[0172] More specifically, in step 1f-48, the terminal AS (1f-10) in the inactive mode or standby mode can store the QoE measurement report A (e.g., the QoE report received in step 1f-47) received from the terminal APP at time t1.

[0173] Additionally, in step 1f-48, the terminal AS in the inactive mode or standby mode can store the QoE measurement report B (e.g., the QoE report received in 1f-47) received from the terminal APP at time t2.

[0174] Afterwards, the terminal can transition to a connected mode at time t3 (e.g., step 1f-50), and when generating a QoE measurement report message (e.g., MeasurementReportAppLayer message) for transmitting a QoE measurement report (e.g., 1f-70), the terminal can include QoE measurement report A and QoE measurement report B as entries in the container list (e.g., measReportAppLayerContainerList). The terminal can transmit the container list to the base station by transmitting the QoE measurement report message, and the container list can be transmitted to OAM or TCE or MCE.

[0175] Meanwhile, the base station, OAM, TCE, or MCE that receives the container list may not know when each entry (i.e., each container) included in the container list was measured or generated. This may be because two QoE measurement reports A and B are transmitted together in the same container list. For example, time t1 may be 24 hours prior to time t3, and time t2 may be 1 minute prior to time t3. However, the base station, OAM, TCE, or MCE may not know these times.

[0176] More specifically, QoE measurement report A may include measurement result values ​​indicating that the QoE of the terminal is poor, and QoE measurement report B may include measurement result values ​​indicating that the QoE of the terminal is good. Conversely, QoE measurement report B may include measurement result values ​​indicating that the QoE of the terminal is poor, and QoE measurement report A may include measurement result values ​​indicating that the QoE of the terminal is good. In this case, poor QoE of the terminal may mean a case where it has a high service delay value, and good QoE may mean a case where it has a low service delay value.

[0177] In this case, when the base station or OAM or TCE or MCE receives the container list, it can know that two conflicting QoE measurement result values ​​exist as each entry. However, it cannot distinguish whether the QoE measurement result of the terminal was poor a relatively long time ago (e.g., time point t1) and then improved relatively recently (e.g., time point t2), or whether the QoE measurement result was good a relatively long time ago (e.g., time point t1) and then worsened relatively recently (e.g., time point t2).

[0178] As a result, the base station, OAM, TCE, or MCE may perform network optimization incorrectly. More specifically, even if the terminal actually has good recent QoE measurements, the base station, OAM, TCE, or MCE may determine that the results are poor and perform unnecessary network resource optimization.

[0179] According to one embodiment of the present disclosure, in order to solve the above-described problem, time information for each entry in a container list within a QoE measurement report message may be included within the QoE measurement report message. The QoE measurement report message may indicate a MeasurementReportAppLayer message, and the container list may indicate a measReportAppLayerContainerList. More specifically, one of the following methods 1 to 5 or a combination thereof may be used.

[0180] Method 1. The time (absolute time point or relative time point) at which the terminal APP generates the QoE measurement report for each entry may be specified and / or included in the QoE measurement report message.

[0181] Method 2. The order in which the terminal APP generates QoE measurement reports for each entry may be specified and / or included in the QoE measurement report message. For example, 1 may be the first generated QoE measurement report, 2 may be the second generated QoE measurement report, and 쪋, N may be the Nth generated QoE measurement report.

[0182] Method 3. The time point (absolute time point or relative time point) at which the terminal AS receives the QoE measurement report for each entry from the terminal APP may be specified and / or included in the QoE measurement report message.

[0183] Method 4. The order in which the terminal AS receives QoE measurement reports for each entry from the terminal APP can be explicitly included in the QoE measurement report message. For example, 1 can be explicitly included in the QoE measurement report message to indicate the first received QoE measurement report, 2 can be the second received QoE measurement report, and N can be the Nth received QoE measurement report.

[0184] Method 5. The terminal AS can include and / or set the corresponding entry in the container list (e.g., measReportAppLayerContainerList) in the order in which the QoE measurement report for each entry is received from the terminal APP.

[0185] For example, the terminal AS can set the QoE measurement report that it receives first (e.g., received the oldest) from the terminal APP as the first entry in the container list, the QoE measurement report that it receives second (e.g., received the second oldest) as the second entry in the container list, and the QoE measurement report that it receives Nth (e.g., received the Nth oldest) as the Nth entry in the container list.

[0186] Conversely, the terminal AS can set the QoE measurement report most recently received from the terminal APP as the first entry in the container list, the second most recently received QoE measurement report as the second entry in the container list, and the Nth most recently received QoE measurement report as the Nth entry in the container list. This can be described in the standard document TS 38.331 as shown in Table 10 below.

[0187] [Table 10]

[0188]

[0189] As an example of the present disclosure, when a terminal AS transmits a QoE measurement report (e.g., 1f-35, 1f-70, 1f-85), a container (e.g., measReportAppLayerContainer-r17) or a container list (e.g., measReportAppLayerContainerList-r18) may be used to include a QoE measurement report received from a terminal APP in a QoE measurement report message.

[0190] According to one embodiment of the present disclosure, a terminal may be in an RRC connection state with a base station. At this time, the terminal may include a Release 18 terminal, a terminal that supports QoE measurement for MBS services, or a terminal that supports QoE measurement in an inactive / standby mode, and the base station may include a Release 17 base station, a base station that does not support QoE measurement for MBS services, or a base station that does not support QoE measurement in an inactive / standby mode.

[0191] The terminal and base station may be terminals and base stations that support QoE measurement (Release 17 QoE measurement) in connected mode. The base station may configure QoE measurement for connected mode for the terminal. Accordingly, the terminal may perform QoE measurement in connected mode and generate a QoE measurement report message to transmit a QoE measurement report generated according to the QoE measurement to the base station.

[0192] The terminal AS may transmit the QoE measurement report received from the terminal APP to the base station by putting it in a container list (e.g., measReportAppLayerContainerList-r18). However, the base station may not understand it. More specifically, since the base station is a Release 17 base station, even if it receives the container list (e.g., measReportAppLayerContainerList-r18), which is a Release 18 parameter, it may not understand it and may ignore it, which may result in loss of the QoE measurement report.

[0193] According to one embodiment of the present disclosure, in order to solve the above-described problem, when the terminal performs a QoE measurement report, the terminal may restrict the container list (e.g., measReportAppLayerContainerList-r18) to include only QoE measurement reports generated for QoE measurement configurations for MBS services or QoE configurations that can be measured in inactive and / or standby mode (not only in connected mode) (e.g., QoE configurations with appLayerIdleInactiveConfig set). In other words, the terminal may store QoE measurement reports generated for QoE measurement configurations for connected mode (e.g., Release 17 QoE measurement configurations or QoE measurement configurations without appLayerIdleInactiveConfig set) in a container (e.g., measReportAppLayerContainer-r17) rather than in the container list (e.g., measReportAppLayerContainerList-r18). The reason that the terminal has QoE measurement settings for MBS service or QoE settings that can be measured even in inactive and / or standby mode (e.g., QoE settings with appLayerIdleInactiveConfig set) is because the RRC connected base station can be a Release 18 base station or a base station that supports QoE measurement function for MBS service or a base station that supports QoE measurement function in inactive and / or standby mode. The operation for the above embodiment can be described in the standard document TS 38.331 as shown in Table 11 and / or Table 12 below.

[0194] [Table 11]

[0195]

[0196]

[0197] [Table 12]

[0198]

[0199] The operation of a terminal and a base station according to one embodiment of the present disclosure may be as follows.

[0200] The base station can transmit RVQoE (RAN visible QoE) measurement settings to the terminal AS in connected mode (e.g., see step 1e-10 of Fig. 1e). The base station can configure RVQoE measurements for the terminal by setting the ran-VisibleParameters parameter in the AppLayerMeasConfig information element (IE) to setup.

[0201] The terminal AS can transmit the received RVQoE settings to the terminal APP (e.g., see step 1e-15 of Fig. 1e).

[0202] The terminal APP can perform RVQoE measurement according to the received RVQoE, and the terminal APP can transmit RVQoE report information generated as a measurement result to the terminal AS (e.g., see step 1e-20 of FIG. 1e).

[0203] The terminal AS can include the received RVQoE report information in a QoE measurement report message and transmit it to the base station (e.g., see step 1e-25 of FIG. 1e).

[0204] Afterwards, the base station can release the RVQoE settings. The base station can release the RVQoE settings of the terminal by setting the ran-VisibleParameters parameter in the AppLayerMeasConfig information element (IE) to release.

[0205] The AS of a terminal that has been instructed to release the RVQoE setting of the base station can instruct the APP of the terminal to release the RVQoE setting. However, at this time, the AS of the terminal may be storing an RVQoE measurement report (e.g., a remaining RVQoE measurement report) that was received from the APP of the terminal but has not yet been transmitted to the base station.

[0206] The terminal's APP can stop RVQoE measurement and disable the corresponding setting through an instruction from the terminal AS. However, the terminal can then transmit the remaining RVQoE measurement report to the base station. This is because the terminal stores the remaining RVQoE measurement report, and if an SRB for QoE reporting is configured, it can transmit it to the base station. However, since the base station has already instructed the terminal to disable the RVQoE setting, the remaining RVQoE measurement report transmitted by the terminal may no longer be useful information to the base station. Therefore, the terminal's remaining RVQoE measurement report is a waste of radio resources and may result in energy waste for both the terminal and the base station due to transmission and reception.

[0207] According to one embodiment of the present disclosure, in order to solve the above-described problem, when the AS of the terminal receives an instruction to release an RVQoE setting from the base station, the AS may delete the remaining RVQoE measurement report for the RVQoE setting for which the release was instructed (or the QoE setting ID corresponding to the RVQoE setting for which the release was instructed). This is to prevent the terminal from unnecessarily transmitting the remaining RVQoE measurement report to the base station in the future.

[0208] The operation of the terminal for the above embodiment can be described in the standard document TS 38.331 as shown in Table 13 below.

[0209] [Table 13]

[0210]

[0211] According to one embodiment of the present disclosure, the operations of the terminal and the base station may be as follows.

[0212] The terminal and the base station can perform operations from steps 1f-15 to 1f-40 in FIG. 1f. The above operations may be referred to in the description above.

[0213] In steps 1f-25 and 1f-27, the base station (e.g., base station 1) transmits the RVQoE configuration for the QoE measurement configuration for the MBS service, or the QoE configuration that can be measured in inactive mode and / or standby mode (not only in connected mode) (e.g., QoE configuration with appLayerIdleInactiveConfig set), to the AS of the terminal, which can be forwarded to the APP of the terminal.

[0214] In step 1f-40, the base station may transmit an RRC Release message to the terminal, and the terminal that receives the RRC Release message may transition to an inactive mode or a standby mode. At this time, the AS of the terminal may instruct the terminal APP to release the RVQoE settings for the QoE measurement settings for the MBS service, or the RVQoE settings for the QoE settings that can be measured in the inactive and / or standby mode (not only in the connected mode) (e.g., the QoE settings for which appLayerIdleInactiveConfig is set). This may be to prevent the terminal from performing RVQoE measurements in the inactive and / or standby mode. However, at this time, the terminal AS may be storing RVQoE measurement reports (e.g., remaining RVQoE measurement reports) that it has received from the terminal APP but has not yet transmitted to the base station.

[0215] The terminal's APP can stop RVQoE measurement and disable the setting through instructions from the terminal's AS.

[0216] However, the AS of the terminal can then transmit a residual RVQoE measurement report to a new base station (e.g., base station 2) (e.g., see step 1f-70 or step 1f-85 of FIG. 1f). This is because the AS of the terminal stores the residual RVQoE, and the terminal can transmit the residual RVQoE to the new base station (e.g., base station 2) if an SRB for QoE reporting is configured. However, the residual RVQoE measurement report may not be useful to the new base station (e.g., base station 2). This is because the corresponding RVQoE measurement configuration is information generated and / or configured by the previous base station (e.g., base station 1). Therefore, the residual RVQoE measurement report of the terminal may be a waste of radio resources and may result in energy waste of the terminal and the base station due to transmission and reception.

[0217] According to one embodiment of the present disclosure, in order to solve the above-described problem, when the AS of the terminal transitions to an inactive mode or a standby mode (e.g., see step 1f-40), the AS may instruct the terminal APP to release a QoE measurement setting for the MBS service, or a QoE setting that is measurable in the inactive and / or standby mode (not only in the connected mode) (e.g., a QoE setting with appLayerIdleInactiveConfig set), and may also delete remaining RVQoE measurement reports for the corresponding setting.

[0218] This is to prevent the terminal from unnecessarily transmitting remaining RVQoE measurement reports to the base station (e.g., base station 2) in the future.

[0219] The operation of the terminal for the above embodiment may be described in the following standard document TS 38.331. Table 14 may relate to the operation when the terminal transitions to an inactive mode, and Table 15 may relate to the operation when the terminal transitions to a standby mode.

[0220] [Table 14]

[0221]

[0222] [Table 15]

[0223]

[0224] FIG. 1g is a block diagram illustrating the internal structure of a terminal applied to an embodiment of the present disclosure.

[0225] Referring to FIG. 1g, the terminal may include an RF (Radio Frequency) processing unit (1g-10), a baseband processing unit (1g-20), a storage unit (1g-30), and a control unit (1g-40).

[0226] The RF processing unit (1g-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1g-10) may up-convert a baseband signal provided from the baseband processing unit (1g-20) into an RF band signal and transmit the up-converted signal through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1g-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 illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (1g-10) may include multiple RF chains.

[0227] Furthermore, the RF processing unit (1g-10) can perform beamforming. For the beamforming, the RF processing unit (1g-10) can adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO (multiple-input and multiple-output) and can receive multiple layers when performing the MIMO operation.

[0228] The baseband processing unit (1g-20) can perform 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 (1g-20) can generate complex symbols by encoding and modulating the transmission bit stream. In addition, when receiving data, the baseband processing unit (1g-20) can restore the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (1g-10).

[0229] For example, in the case of OFDM (orthogonal frequency division multiplexing), when transmitting data, the baseband processing unit (1g-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 (1g-20) divides the baseband signal provided from the RF processing unit (1g-10) into OFDM symbol units, restores signals mapped to subcarriers through an FFT (fast Fourier transform) operation, and then restores the received bit stream through demodulation and decoding.

[0230] The baseband processing unit (1g-20) and the RF processing unit (1g-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1g-20) and the RF processing unit (1g-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 (1g-20) and the RF processing unit (1g-10) may include a plurality of communication modules to support a plurality of different wireless access technologies.

[0231] In addition, at least one of the baseband processing unit (1g-20) and the RF processing unit (1g-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), cellular networks (e.g., LTE), etc. In addition, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band, a millimeter wave (mm wave) (e.g., 60GHz) band.

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

[0233] The control unit (1g-40) can control the overall operations of the terminal. For example, the control unit (1g-40) transmits and receives signals through the baseband processing unit (1g-20) and the RF processing unit (1g-10). In addition, the control unit (1g-40) records and reads data in the storage unit (1g-30). For this purpose, the control unit (1g-40) can include at least one processor. For example, the control unit (1g-40) can include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs, and can include a multi-connection processing unit (1g-42) as illustrated in the drawing.

[0234] FIG. 1h is a block diagram illustrating the structure of a base station applied to an embodiment of the present disclosure.

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

[0236] The RF processing unit (1h-10) may perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1h-10) may up-convert a baseband signal provided from the baseband processing unit (1h-20) into an RF band signal and transmit the up-converted signal through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (1h-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 illustrated, but the base station may be equipped with multiple antennas. In addition, the RF processing unit (1h-10) may include multiple RF chains.

[0237] Furthermore, the RF processing unit (1h-10) can perform beamforming. For the beamforming, the RF processing unit (1h-10) can adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform a downlink MIMO (multiple-input and multiple-output) operation by transmitting one or more layers.

[0238] The baseband processing unit (1h-20) above can perform a conversion function between a baseband signal and a bit stream according to the physical layer specifications of a wireless access technology. For example, when transmitting data, the baseband processing unit (1h-20) can generate complex symbols by encoding and modulating the transmission bit stream. In addition, when receiving data, the baseband processing unit (1h-20) can restore the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (1h-10).

[0239] For example, in the case of OFDM method, when transmitting data, the baseband processing unit (1h-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 (1h-20) divides the baseband signal provided from the RF processing unit (1h-10) into OFDM symbol units, restores signals mapped to subcarriers through FFT operation, and then restores the received bit stream through demodulation and decoding.

[0240] The baseband processing unit (1h-20) and the RF processing unit (1h-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1h-20) and the RF processing unit (1h-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0241] The above backhaul communication unit (1h-30) can provide an interface for performing communication with other nodes within the network. That is, the backhaul communication unit (1h-30) converts a bit string transmitted from the main base station to another node, such as an auxiliary base station or a core network, into a physical signal, and converts a physical signal received from the other node into a bit string.

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

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

[0244] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated as needed. For example, parts of one embodiment of the present disclosure and another embodiment can be combined to operate a base station and a terminal. In addition, the embodiments of the present disclosure can be applied to other communication systems, and other modifications based on the technical idea of ​​the embodiments can also be implemented. For example, the embodiments can be applied to LTE systems, 5G, NR systems, or 6G systems. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the following claims but also by equivalents of the claims.

[0245] 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 within a scope that does not detract 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.

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

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

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

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

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

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

[0252] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious 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 following claims but also by equivalents of the scope of the claims. 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, each of the above 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 embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

[0253] 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 receiving a first Radio Resource Control (RRC) reset message including application layer measurement configuration information from a base station, wherein the application layer measurement configuration information includes parameter information related to RAN Visible Application Layer measurement reporting; A step of transmitting an application layer measurement report message including a measurement report of the RAN Visible Application Layer to the base station based on parameter information related to the RAN Visible Application Layer measurement report; and A method characterized by comprising the step of discarding a measurement report of a RAN Visible Application Layer when receiving a second RRC reset message that sets parameter information related to a RAN Visible Application Layer measurement report to be released from the base station.

2. In paragraph 1, A method characterized in that the above Application Layer measurement setting information further includes setting information for setting Application Layer measurement in an RRC Idle or RRC Inactive state.

3. In paragraph 2, A method characterized in that, when receiving an RRC release message from the base station, the method further includes a step of discarding a measurement report of a RAN Visible Application Layer related to an Application Layer measurement in the RRC Idle or RRC Inactive state.

4. In paragraph 1, A method characterized in that the information related to the RAN Visible Application Layer measurement report includes at least one of first information related to the maximum number of reportable buffer levels, second information related to the cycle of the RAN Visible Application Layer measurement report, or third information related to media start playback delay.

5. In a method performed by a base station in a wireless communication system, A step of transmitting a first Radio Resource Control (RRC) reset message including application layer measurement configuration information to a terminal, wherein the application layer measurement configuration information includes parameter information related to RAN Visible Application Layer measurement reporting; and A step of receiving, from the terminal, an application layer measurement report message including a measurement report of the RAN Visible Application Layer based on parameter information related to the above RAN Visible Application Layer measurement report, A method characterized in that when transmitting a second RRC reset message that sets to release parameter information related to a RAN Visible Application Layer measurement report to the terminal, the second RRC message that sets to release parameter information related to a RAN Visible Application Layer measurement report is related to discarding a measurement report of the RAN Visible Application Layer.

6. In paragraph 5, The above Application Layer measurement setting information further includes setting information for setting Application Layer measurement in RRC Idle or RRC Inactive state. A method characterized in that when an RRC release message is transmitted to the terminal, the RRC Release message is related to discarding a measurement report of a RAN Visible Application Layer related to configuration information that sets up Application Layer measurement in the RRC Idle or RRC Inactive state.

7. In paragraph 5, A method characterized in that the information related to the RAN Visible Application Layer measurement report includes at least one of first information related to the maximum number of reportable buffer levels, second information related to the cycle of the RAN Visible Application Layer measurement report, or third information related to media start playback delay.

8. In a terminal in a wireless communication system, A transceiver for transmitting and receiving signals; and It includes a control unit coupled with the above transmitter and receiver, and the control unit is: Receive a first Radio Resource Control (RRC) reset message from a base station, wherein the first Radio Resource Control (RRC) reset message includes application layer measurement configuration information, wherein the application layer measurement configuration information includes parameter information related to RAN Visible Application Layer measurement reporting, Based on parameter information related to the above RAN Visible Application Layer measurement report, transmit an application layer measurement report message including a measurement report of the RAN Visible Application Layer to the base station, A terminal characterized in that, when receiving a second RRC reset message that sets parameter information related to a RAN Visible Application Layer measurement report to be released from the base station, the terminal discards the measurement report of the RAN Visible Application Layer.

9. In paragraph 8, A terminal characterized in that the above Application Layer measurement setting information further includes setting information for setting Application Layer measurement in an RRC Idle or RRC Inactive state.

10. In paragraph 9, the control unit, A terminal characterized in that, when receiving an RRC release message from the base station, a measurement report of a RAN Visible Application Layer related to an Application Layer measurement in the RRC Idle or RRC Inactive state is discarded.

11. In paragraph 8, A terminal characterized in that the information related to the RAN Visible Application Layer measurement report includes at least one of first information related to the maximum number of reportable buffer levels, second information related to the cycle of the RAN Visible Application Layer measurement report, or third information related to media start playback delay.

12. In a base station in a wireless communication system, A transceiver for transmitting and receiving signals; and It includes a control unit coupled with the above transmitter and receiver, and the control unit is: Transmitting a first Radio Resource Control (RRC) reset message including application layer measurement configuration information to the terminal, wherein the application layer measurement configuration information includes parameter information related to RAN Visible Application Layer measurement reporting, Based on parameter information related to the above RAN Visible Application Layer measurement report, receiving an application layer measurement report message including a measurement report of the RAN Visible Application Layer from the terminal, A base station characterized in that, when transmitting a second RRC reset message that sets to release parameter information related to a RAN Visible Application Layer measurement report to the terminal, the second RRC message that sets to release parameter information related to the RAN Visible Application Layer measurement report is related to discarding a measurement report of the RAN Visible Application Layer.

13. In paragraph 12, A base station characterized in that the above Application Layer measurement setting information further includes setting information for setting Application Layer measurement in an RRC Idle or RRC Inactive state.

14. In paragraph 13, A base station characterized in that, when transmitting an RRC release message to the terminal, the RRC Release message is related to discarding a measurement report of a RAN Visible Application Layer related to configuration information that sets up Application Layer measurement in the RRC Idle or RRC Inactive state.

15. In paragraph 12, A base station, characterized in that the information related to the RAN Visible Application Layer measurement report includes at least one of first information related to the maximum number of reportable buffer levels, second information related to the cycle of the RAN Visible Application Layer measurement report, or third information related to media start playback delay.

Images