Method and apparatus for qoe measurement reporting in next generation mobile communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a terminal in a wireless communication system is provided. The method includes receiving a radio resource control (RRC) message including configuration information on application layer measurements from a base station, configuring an identifier (ID) for each application layer measurement, setting an application layer measurement report entry in the application layer measurement report message based on the configuration information, and transmitting the application layer measurement report message to the base station. The application layer measurement report message includes a plurality of application layer measurement configuration IDs and a plurality of application layer measurement report entries associated with the plurality of application layer measurement configuration IDs.

Description

Technical Field

[0001] The present disclosure relates to operations of a terminal and a base station for Quality of Experience (QoE) measurement reporting in a wireless communication system. Background Art

[0002] 5G mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called mmWave including 28 GHz and 39 GHz. In addition, 6G mobile communication technology (called super 5G system) has been considered to be implemented in terahertz frequency bands (e.g., 95 GHz to 3 THz frequency bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine-type communication (mMTC), there is ongoing standardization on the following items: beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves, parameter sets supporting dynamic operations for efficient utilization of millimeter wave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods (such as LDPC (low-density parity check) codes for large-scale data transmission and polar codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services to be supported by 5G mobile communication technology, discussions are ongoing on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as the following: V2X (Vehicle to Everything), for assisting driving determination of autonomous vehicles based on information about the location and status of the vehicle sent by the vehicle and for enhancing user convenience; NR-U (New Radio Unlicensed), for system operation that is intended to comply with various regulatory-related requirements in unlicensed bands; NR UE power saving, non-terrestrial network (NTN), which is UE satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] In addition, in the air interface architecture / protocol, there is already ongoing standardization on technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (two-step RACH for NR) for simplifying the random access procedure. There is also ongoing standardization on a 5G baseline architecture (e.g., a service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and a system architecture / service for mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will be connected to the communication network, and it is accordingly expected that enhanced functions and performance of the 5G mobile communication system and integrated operations of the connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged to effectively support AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., to improve 5G performance and reduce complexity by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, meta-service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a foundation for developing not only new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), and RIS (reconfigurable smart surface), but also full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for achieving services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high performance communication and computing resources.

[0008] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0009] Technical issues

[0010] As wireless communication systems develop, there arises a need for a method and apparatus for more efficiently performing QoE measurement reporting in next generation mobile communication systems.

[0011] Solution to the problem

[0012] In an embodiment, a method performed by a terminal in a wireless communication system is provided. The method includes receiving a radio resource control (RRC) message including configuration information about application layer measurement from a base station, for each application layer measurement configuration identifier (ID), setting an application layer measurement report item in an application layer measurement report message based on the configuration information, and sending an application layer measurement report message to the base station. The application layer measurement report message includes multiple application layer measurement configuration IDs and multiple application layer measurement report items associated with the multiple application layer measurement configuration IDs.

[0013] In an embodiment, a method performed by a base station in a wireless communication system is provided. The method includes sending an RRC message including configuration information about application layer measurement to a terminal, and receiving an application layer measurement report message from the terminal, wherein for each application layer measurement configuration ID, the application layer measurement report message includes an application layer measurement report item set according to the configuration information. The application layer measurement report message includes multiple application layer measurement configuration IDs and multiple application layer measurement report items associated with the multiple application layer measurement configuration IDs.

[0014] In an embodiment, a terminal in a wireless communication system is provided. The terminal includes a transceiver and a controller. The controller is configured to receive an RRC message including configuration information about application layer measurement from a base station via the transceiver, set an application layer measurement report item in an application layer measurement report message based on the configuration information for each application layer measurement configuration ID, and send an application layer measurement report message to the base station via the transceiver. The application layer measurement report message includes multiple application layer measurement configuration IDs and multiple application layer measurement report items associated with the multiple application layer measurement configuration IDs.

[0015] In an embodiment, a base station in a wireless communication system is provided. The base station includes a transceiver and a controller. The controller is configured to send an RRC message including configuration information about application layer measurement to a terminal via the transceiver, and still receive an application layer measurement report message from the terminal via the transceiver, and for each application layer measurement configuration ID, the application layer measurement report message includes an application layer measurement report item set according to the configuration information. The application layer measurement report message includes multiple application layer measurement configuration IDs and multiple application layer measurement report items associated with the multiple application layer measurement configuration IDs.

[0016] Advantageous Effects of the Invention

[0017] According to the embodiments of the present disclosure, a terminal can more effectively perform QoE measurement reporting in a next generation mobile communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:

[0019] Figure 1 The structure of a next generation mobile communication system according to an embodiment of the present disclosure is shown;

[0020] Figure 2 illustrates a radio access state transition in a next generation mobile communication system according to an embodiment of the present disclosure;

[0021] Figure 3 A flowchart illustrating a process for configuring / reporting signaling-based QoE measurements according to an embodiment of the present disclosure;

[0022] Figure 4 A flowchart illustrating a process for configuring / reporting management-based QoE measurements according to an embodiment of the present disclosure;

[0023] Figure 5A illustrates the operation of a UE that has received QoE configuration information according to an embodiment of the present disclosure;

[0024] Figure 5B illustrates the operation of a UE that has received QoE configuration information according to an embodiment of the present disclosure;

[0025] Fig. 6A UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0026] Figure 6B UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0027] Fig. 7A illustrates the operation of a UE that has received QoE configuration information when the appLayerSessionStatus indicator is affected by the pauseReporting configuration according to an embodiment of the present disclosure;

[0028] Figure 7B illustrates the operation of a UE that has received QoE configuration information when the appLayerSessionStatus indicator is affected by the pauseReporting configuration according to an embodiment of the present disclosure;

[0029] Fig. 8AUE operation for reporting QoE measurement results when the appLayerSessionStatus indicator is affected by the pauseReporting configuration according to an embodiment of the present disclosure is shown;

[0030] Figure 8B UE operation for reporting QoE measurement results when the appLayerSessionStatus indicator is affected by the pauseReporting configuration according to an embodiment of the present disclosure is shown;

[0031] Fig.9A UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0032] Fig. 9B UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0033] Fig. 10A UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0034] Fig. 10B UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0035] Fig.11A UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0036] Fig. 11B UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0037] Fig. 11C The structure of a message for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0038] Fig.11D The structure of a message for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0039] Fig.11E The structure of a message for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0040] Fig.11F The structure of a message for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0041] Fig.11G The structure of a message for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0042] Fig.11HThe structure of a message for reporting QoE measurement results according to an embodiment of the present disclosure is shown;

[0043] Fig.12 shows the structure of a UE according to an embodiment of the present disclosure; and

[0044] Fig.13 The configuration of a base station according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0045] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives mean including but not limiting; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, included within, interconnected with, containing, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interleaved, juxtaposed, proximate to, bound to or bound with, having, having the property of, and the like; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0046] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" indicate one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a part thereof suitable for being implemented in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite it later, such as rewritable optical discs or erasable memory devices.

[0047] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. Figures 1 to 13 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0048] When describing the embodiments of the present disclosure, descriptions related to technical contents known in the art and not directly related to the present disclosure will be omitted. Such unnecessary omissions are intended to prevent the main concept of the present disclosure from being obscured and to convey the main concept more clearly.

[0049] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically shown. In addition, the size of each element does not fully reflect the actual size. In the accompanying drawings, the same or corresponding elements are provided with the same reference numerals.

[0050] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will be apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the attached claims. Throughout the specification, the same or similar reference numerals designate the same or similar elements.

[0051] In this article, it will be understood that each box of the flowchart diagram and the combination of boxes in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a component for implementing the function specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-available or computer-readable memory, which can instruct the computer or other programmable data processing device to act in a particular way, so that the instructions stored in the computer-available or computer-readable memory produce an article of instruction components including the functions specified in one or more flowchart boxes. The computer program instructions can also be loaded on a computer or other programmable data processing device so that a series of operating steps are performed on a computer or other programmable device to produce a computer-implemented process so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flowchart boxes.

[0052] In addition, each frame of the flowchart diagram can represent a module, segment or part of a code, which includes one or more executable instructions for implementing a specified logical function (or multiple). It should also be noted that in some alternative embodiments, the functions mentioned in the frame may not occur in order. For example, two frames shown in succession can actually be performed substantially simultaneously, or frames can sometimes be performed in reverse order, depending on the functions involved.

[0053] As used herein, "unit" indicates a software element or hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, "unit" does not always have a meaning limited to software or hardware. "Unit" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segmentation, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and parameters. The elements and functions provided by "unit" can be combined into a smaller number of elements or "units", or divided into a larger number of elements or "units". In addition, elements and "units" can be implemented as one or more CPUs in a reproduction device or a secure multimedia card.

[0054] In the following description of the present disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear. Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0055] Figure 1 A structure of a next generation mobile communication system according to an embodiment of the present disclosure is shown.

[0056] refer to Figure 1 , as shown in the figure, the radio access network of the next generation mobile communication system (new radio (NR)) may include a next generation base station (new radio node B, hereinafter referred to as gNB) 1-10 and AMF (new radio core network) 1-05. User equipment (new radio user equipment, hereinafter referred to as NR UE or terminal) 1-15 can access an external network via gNB 1-10 and AMF 1-05.

[0057] exist Figure 1 In the present invention, the gNB corresponds to the evolved Node B (eNB) of the existing LTE system. The gNB is connected to the NR UE via a radio channel and can provide excellent services compared with the existing Node B (indicated by reference numerals 1-20). In the next generation mobile communication system, since all types of user traffic are served through a shared channel, a device for performing scheduling by collecting status information such as the buffer status, available transmission power status, and channel status of the UE is required.

[0058] In addition, gNB 1-0 is responsible for this function of the device. Generally speaking, one gNB usually controls multiple cells. In order to achieve ultra-high-speed data transmission compared to the existing LTE, the gNB can have an existing maximum bandwidth or a larger bandwidth, and can additionally adopt a beamforming technology using orthogonal frequency division multiplexing (OFDM) as a radio access technology. In addition, the gNB adopts an adaptive modulation and coding (AMC) scheme that determines the modulation scheme and channel coding rate based on the channel state of the UE. AMF 1-05 performs functions such as mobility support, bearer configuration, QoS configuration, etc. AMF is a device that is responsible for various control functions in addition to the mobility management function of the UE, and is connected to multiple base stations.

[0059] In addition, the next generation mobile communication system may also operate in conjunction with the existing LTE system, and the AMF may be connected to the MME 1-25 via a network interface. The MME is connected to the eNB 1-30, that is, to the existing base station. A UE supporting LTE-NR dual connectivity may send and receive data while maintaining a connection with the eNB and the gNB (indicated by reference numeral 1-35).

[0060] Figure 2 A radio access state transition in a next generation mobile communication system according to an embodiment of the present disclosure is illustrated.

[0061] In the next generation mobile communication system, there are three radio access states (RRC states). The connected mode (RRC_CONNECTED, 2-05) is a radio access state in which the UE can send and receive data. The idle mode (RRC_IDLE, 2-30) is a radio access state in which the UE monitors whether paging is sent to the UE itself. The above two modes are in radio access states that are also applied to the existing LTE system, and their details are the same as those of the existing LTE system. In the next generation mobile communication system, the RRC INACTIVE radio access state 2-15 is newly defined. In the radio access state, the UE context is maintained in the gNB and the UE, and RAN-based paging is supported. The characteristics of the new radio access state are as follows:

[0062] -Cell reselection mobility;

[0063] - A CN-NR RAN connection (both C / U plane) has been established for the UE;

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

[0065] -Paging is initiated by NR RAN;

[0066] - RAN based notification areas are managed by the NR RAN; and

[0067] - The NR RAN is aware of the RAN based notification area to which the UE belongs.

[0068] The new INACTIVE radio access state can be converted to connected mode or idle mode through a specific process. The recovery process is used to convert from INACTIVE mode to connected mode, and the release process including suspension information is used to convert from connected mode to INACTIVE mode (indicated by reference numeral 2-10). The recovery / release process is performed by at least one RRC message sent and received between the UE and the gNB, and includes at least one operation. In addition, a transition from INACTIVE mode to idle mode through a release process after performing the recovery process is possible (indicated by reference numeral 2-20). The transition between connected mode and idle mode conforms to the existing LTE technology. That is, this transition between modes is performed by an establishment or release process (indicated by reference numeral 2-25).

[0069] Figure 3 A flow chart showing a process for configuring / reporting signaling-based QoE measurements according to an embodiment of the present disclosure is shown.

[0070] The UE access layer (AS) 3-05 may send information indicating whether quality of experience (QoE) measurement is supported for each service type to the base station (or NG-RAN) 3-15 through a UE capability message (indicated by reference numeral 3-10). The message may contain ASN.1 information and related parameter descriptions, as shown in Tables 1 to 2 below.

[0071]

Table 1

[0072]

[0073]

Table 2

[0074]

[0075] As in the above example, LTE can support streaming and multimedia telephony services for IP Multimedia Subsystem (IMS) (MTSI), and NR can support virtual reality (VR), multimedia broadcast multicast service (MBMS), extended reality (XR), etc.

[0076] Operation Administration and Maintenance (OAM) 3-20 provides QoE measurement configuration information (indicated by reference numeral 3-30) to a core network (CN) 3-25. The CN having received the configuration information may activate QoE measurement by sending the configuration information to a base station (indicated by reference numeral 3-35). The base station having received the configuration information may transmit the configuration information to the UE AS (indicated by reference numeral 3-40) through an RRC message (e.g., an RRC connection reconfiguration message). The RRC message may include ASN.1 information and related parameter descriptions, as shown in Tables 3 to 4 below.

[0077]

Table 3

[0078]

[0079]

Table 4

[0080]

[0081] Upon receiving the message, in the case where the message corresponds to a message for establishing a configuration, the UE AS may transmit the configuration information to the UE application layer (UE APP) 3-45 through an AT command (indicated by reference numeral 3-50). In the case where the message corresponds to a message for releasing a configuration, the UE AS may send an AT command to the UE APP to delete the stored configuration information. The specific operation of the UE AS having received the RRC message may be represented as shown in Table 5 below.

[0082]

Table 5

[0083]

[0084]

[0085] UE APP can perform QoE measurement according to the received configuration information. In addition, UE APP can report the measurement result to UE AS through AT command according to the configuration information (indicated by reference numeral 3-55). Upon receiving the measurement result, UE AS can report the measurement result to the base station through RRC message (e.g., measReportAPlayer message) (indicated by reference numeral 3-60). SRB4 can be used to report QoE measurement results. RRC message may include ASN.1 information and related parameter descriptions, as shown in Tables 6 to 7 below.

[0086]

Table 6

[0087]

[0088]

Table 7

[0089]

[0090]

[0091] The detailed UE AS procedure for reporting QoE measurement results can be expressed as shown in Table 8 below.

[0092]

Table 8

[0093]

[0094] The base station may transmit the measurement result report to the configured final destination (TCE or MCE) 3-65 (indicated by reference numeral 3-70).

[0095] Figure 4 A flow chart illustrating a process for configuring / reporting management-based QoE measurements according to an embodiment of the present disclosure.

[0096] The management-based QoE configuration / reporting process is similar to the signaling-based process ( Figure 3 ). Therefore, in this specification, only the differences in the management-based method are described below, and the differences can be based on Figure 3The other processes and descriptions can be understood from the description of FIG. 4. In the management-based method, OAM 4-05 can send the QoE measurement configuration directly to the base station 4-10 without going through the CN to activate the QoE measurement (indicated by reference numeral 4-15). Upon receiving the QoE measurement configuration, the base station can find a single or multiple UEs that meet various conditions (e.g., area range, application layer capabilities, service type). In addition, the base station can send the QoE measurement configuration (indicated by reference numeral 4-20) to each UE via an RRC message (e.g., an RRC connection reconfiguration message). It can be based on Figure 3 description (signaling-based approach) to understand other procedures and message types.

[0097] To support QoE measurement in NR, the following procedures and operations may be performed.

[0098] 1) First, when receiving the QoE configuration information, the UE operation can be represented as shown in Table 9 below.

[0099]

Table 9

[0100]

[0101]

[0102] 2) Next, the process for performing QoE reporting of UE in connected mode can be expressed as shown in Table 10 below.

[0103]

Table 10

[0104]

[0105]

[0106]

[0107] 3) The ASN.1 definition of AppLayerMeasConfig as an RRC information element (IE) including QoE configuration information and the description of the lower IEs may be as shown in Tables 11 to 13 below.

[0108]

Table 11

[0109]

[0110]

Table 12

[0111]

[0112]

[0113]

Table 13

[0114]

[0115]

[0116] 4) The ASN.1 definition of the MeasurementReportAppLayer message as an RRC message including QoE report information and the description of the lower IEs may be as shown in Tables 14 to 16 below.

[0117]

Table 14

[0118]

[0119]

Table 15

[0120]

[0121]

[0122]

[0123]

Table 16

[0124]

[0125] The base station can stop (by configuring the indicator to "true") or resume (by configuring the indicator to "false") the reporting of the QoE measurement results of the UE through the pauseReporting indicator. When RAN overload occurs, the base station can stop the QoE reporting of the UE by using the indicator. Even if the UE access stratum (AS) layer configured with the indicator "true" receives a QoE measurement report from the UE application (or APP) layer, the UE AS layer can store the received QoE measurement report instead of transmitting the QoE measurement report to the base station. When the RAN overload is resolved, the base station can resume the QoE reporting of the UE by using the indicator. When the UE access stratum (AS) layer configured with the indicator "false" receives a QoE measurement report from the UE application (or APP) layer, the UE AS layer can resume the operation of sending the QoE measurement report to the base station and can transmit the QoE measurement report that has been stored so far to the base station.

[0126] Figure 5A and Figure 5B Operations of a UE that has received QoE configuration information according to an embodiment of the present disclosure are illustrated.

[0127] In operation 5-05, the UE may receive system information (SIB) transmitted by the base station.

[0128] In operation 5-10, the UE may camp on a specific base station or cell based on the received SIB.

[0129] In operation 5-15, the UE may establish an RRC connection with the cell or base station in which it resides.

[0130] In operation 5-20, the UE in the connected mode may receive the QoE configuration information from the base station. The QoE configuration information may be included in the RRCReconfiguration message and transmitted. Alternatively, the UE in the inactive mode may receive the QoE configuration information through the RRCResume message.

[0131] In operation 5-25, the UE may determine whether the pauseReporting indicator is configured.

[0132] In operation 5-30, when the pauseReporting indicator is configured as true, the UE may determine whether some segments have been transmitted after performing RRC segmentation on the MeasurementReportAppLayer message.

[0133] In operation 5-35, when the UE sends only some segments after performing RRC segmentation on the MeasurementReportAppLayer message, the UE may send the remaining unsent segments.

[0134] In operation 5-40, the UE may suspend transmission of the QoE report container (measReportApLayerContainer). In addition, when the UE has not sent only some segments (ie, no remaining segments) after RRC segmentation of the MeasurementReportAppLayer message in operation 5-30, the UE may suspend transmission of the QoE container (measReportApLayerContainer).

[0135] In operation 5-45, the UE may store containers that have been previously received or are to be received later.

[0136] In case the pauseReporting indicator is configured as false in operation 5-25, the UE may identify whether transmission of the QoE container has been paused in operation 5-50.

[0137] In operation 5-55, when the transmission of the QoE container has been suspended, the UE may start the transmission of the stored QoE container.

[0138] In operation 5-60, the UE may resume transmission of the QoE container.

[0139] In the event that the UE has not suspended transmission of the QoE container in operation 5-50, the UE may not perform any further actions in operation 5-65.

[0140] Fig. 6A and Figure 6B UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is illustrated.

[0141] In operation 6-05, the UE may receive system information (SIB) transmitted by the base station.

[0142] In operation 6-10, the UE may camp on a specific base station or cell based on the received SIB.

[0143] In operation 6-15, the UE may establish an RRC connection with the camped cell or base station.

[0144] In operation 6-20, the UE in the connected mode may receive QoE configuration information from the base station. The QoE configuration information may be included in an RRCReconfiguration message and sent. Alternatively, the UE in the inactive mode may receive the QoE configuration information through an RRCResume message.

[0145] In operation 6-25, the UE in the connected mode may determine whether the QoE configuration and SRB4 for QoE report message transmission have been configured.

[0146] In operation 6-30, if the QoE configuration and SRB4 have been configured, the UE may repeatedly perform operations 6-35 to 6-55 for each measConfigAppLayerId to send a QoE report message (MeasurementReportAppLayer).

[0147] In operation 6-35, when there is a QoE report that the UE AS layer has received from the app layer but has not yet sent and the QoE report has not been suspended, the UE can configure the QoE report container (MeasReportApLayerContainer) in the MeasurementReportAppLayer message to the QoE report information that has been received from the app layer.

[0148] In operation 6-40, the UE AS layer may configure the measConfigAppLayerId in the MeasurementReportAppLayer message to the measConfigAppLayerId that has been received from the app layer together with the QoE measurement result.

[0149] In operation 6-45, in a case where the UE AS layer has received session measurement start and stop information from the app layer, the UE may configure appLayerSessionStatus in the MeasurementReportAppLayer message to the received value.

[0150] In operation 6-50, in the case where the UE AS layer has received the RAN visible QoE measurement result from the app layer, the UE may configure the ran-VisibleMeasurements in the MeasurementReportAppLayer message to the received value.

[0151] In operation 6-55, the UE may send a MeasurementReportAppLayer message.

[0152] In the case where operations for all measConfigAppLayerIds are ended in operation 6-30, the UE operation may end in operation 6-60.

[0153] In case that QoE is configured or SRB4 is not configured in operation 6-25, the UE may neither configure nor send a MeasurementReportAppLayer message in operation 6-65.

[0154] Among the four IEs (measConfigAppLayerId, measReportAppLayerContainer, appLayerSessionStatus, and ran-VisibleMeasurements-r17) included in the QoE report message (i.e., MeasurementReportAppLayer message), three IEs (measReportAppLayerContainer, appLayerSessionStatus, and ran-VisibleMeasurements) are optional IEs, so they may be included or not included when the UE sends the ReportAppLayer message.

[0155] 1) measReportTappLayerContainer may be a container containing QoE measurement result information received from the app layer. When pauseReporting is configured as true, the UE may stop the transmission of MeasReportApLayerContainer and may store the QoE measurement results (included in MeasReportApLayerContainer) previously or subsequently received from the app layer. For example, the UE operation may be represented as shown in Table 17 below.

[0156]

Table 17

[0157]

[0158] In addition, when pauseReporting is configured as false, the UE may resume the transmission of measReportApLayerContainer and may start the transmission of the stored QoE measurement results (included in measReportApLayerContainer) already received from the app layer. For example, the UE operation may be represented as shown in Table 18 below.

[0159]

Table 18

[0160]

[0161] In summary, the UE can stop or resume the reporting of MeasReportApLayerContainer according to the pauseReporting configuration of the base station.

[0162] 2) In the case of measReportApLayerContainer, even if the UE provides a report to the base station, the base station cannot read or use the report and can only transmit the report to OAM or TCE. Ran-VisibleMeasurements is an IE used to report QoE measurement results (RAN-visible measurement results) that the base station (or RAN) can read and use. Even if the base station configures pauseReporting to true, the reporting of RAN-visible measurement results may not be stopped (when pauseReporting is set to true, the transmission of RAN-visible reports is not suspended). That is, the UE can always report ran-VisibleMeasurements regardless of the pauseReporting configuration of the base station.

[0163] 3) The appLayerSessionStatus indicator can be used by the UE APP layer to notify the base station that a QoE session or application session has started (by configuring the indicator as "started"). In addition, the appLayerSessionStatus indicator can be used by the UE APP layer to notify the base station that a QoE session or application session has stopped (by configuring the indicator as "stopped"). However, the existing method does not define whether the appLayerSessionStatus report is affected by the pauseReporting configuration (such as MeasReportApLayerContainer) (such as ran-VisibleMeasurements).

[0164] Therefore, according to the existing method, when pauseReporting is indicated as true, when the UE AS layer receives session start or stop information from the UE APP layer, it is unclear whether the information can be reported to the base station by being included in appLayerSessionStatus, and therefore the UE operation for the information needs to be clearly defined. Otherwise, even if the same base station configuration is used (for example, when pauseReporting is configured as true), different terminals may perform different operations according to the implementation (for example, UE A continuously reports appLayerSessionStatus to the base station, while UE B stops reporting appLayerSessionStatus to the base station), and therefore, the base station may not be able to predict the UE operation for pauseReporting.

[0165] As an embodiment of the present disclosure, UE operation may be defined such that the appLayerSessionStatus indicator is affected by the pauseReporting of the base station. That is, when the base station configures pauseReporting to true, the UE may not report the appLayerSessionStatus indicator. In addition, when the base station configures pauseReporting to false, the UE may resume reporting of the appLayerSessionStatus indicator. The reasons for defining the UE operation such that the appLayerSessionStatus indicator is affected by the pauseReporting of the base station may be as follows.

[0166] 1) In the case of RAN overload, services related to QoE measurement may have a lower priority so that the base station performs other services and resource scheduling, and the process of sending / receiving and processing appLayerSessionStatus indicators may be wasteful for the base station and UE in terms of computing resource usage, radio resource usage, and energy usage. In particular, the base station is in an overload situation, which may cause more problems.

[0167] 2) RAN visible measurements can be used to optimize the network and thus help resolve RAN overload issues, whereas the appLayerSessionStatus indicator may not help resolve RAN overload issues.

[0168] Fig. 7A and Figure 7B Operation of a UE that has received QoE configuration information in a case where an appLayerSessionStatus indicator is affected by a pauseReporting configuration according to an embodiment of the present disclosure is illustrated.

[0169] In operation 7-05, the UE may receive system information (SIB) transmitted by the base station.

[0170] In operation 7-10, the UE may camp on a specific base station or cell based on the received SIB.

[0171] In operation 7-15, the UE may establish an RRC connection with the cell or base station in which it resides.

[0172] In operation 7-20, the UE in the connected mode may receive QoE configuration information from the base station. The QoE configuration information may be included in an RRCReconfiguration message and sent. Alternatively, the UE in the inactive mode may receive the QoE configuration information through an RRCResume message.

[0173] In operation 7-25, the UE may determine whether the pauseReporting indicator is configured.

[0174] In operation 7-30, according to an embodiment of the present disclosure, in a case where the pauseReporting indicator is configured as true, the UE may perform RRC segmentation on a MeasurementReportAppLayer message including measReportAppLayerContainer or appLayerSessionStatus, and may then determine whether only some segments have been transmitted.

[0175] In operation 7-35, according to an embodiment of the present disclosure, in a case where the UE transmits only some segments after performing RRC segmentation on the MeasurementReportAppLayer message including measReportAppLayerContainer or appLayerSessionStatus, the remaining untransmitted segments may be transmitted.

[0176] In operation 7-40, according to an embodiment of the present disclosure, the UE may suspend transmission of a QoE report container (measReportApLayerContainer) and appLayerSessionStatus. In addition, in operation 7-30, according to an embodiment of the present disclosure, when the UE has not yet sent only some segments after performing RRC segmentation on a MeasurementReportAppLayer message including measReportApLayerContainer or appLayerSessionStatus (i.e., when there are no remaining segments), the UE may suspend transmission of a QoE container (measReportApLayerContainer).

[0177] In operation 7-45, according to an embodiment of the present disclosure, the UE may store the container and appLayerSessionStatus to be previously received or later received.

[0178] According to an embodiment of the present disclosure, in a case where the pauseReporting indicator is configured as false in operation 7-25, the UE may identify whether transmission of the QoE container and appLayerSessionStatus has been paused in operation 7-50.

[0179] In operation 7-55, if the transmission of the QoE container and appLayerSessionStatus has been suspended, the UE may start the transmission of the stored QoE container and appLayerSessionStatus.

[0180] In operation 7-60, the UE may resume transmission of the QoE container and appLayerSessionStatus.

[0181] In the event that the UE has not suspended the QoE container and appLayerSessionStatus transmission in operation 7-50, the UE may not perform any further operations in operation 7-65.

[0182] As mentioned above, through FIG. 7A to FIG. 7BThe operations of the present disclosure provided with the related description can be expressed as, for example, the following Tables 19 to 20.

[0183]

Table 19

[0184]

[0185]

[0186]

[0187]

Table 20

[0188]

[0189]

[0190] Fig. 8A and Figure 8B A UE operation for reporting a QoE measurement result in a case where the appLayerSessionStatus indicator is affected by the pauseReporting setting is illustrated as an example of an embodiment of the present disclosure.

[0191] In operation 8-05, the UE may receive system information (SIB) transmitted by the base station.

[0192] In operation 8-10, the UE may camp on a specific base station or cell based on the received SIB.

[0193] In operation 8-15, the UE may establish an RRC connection with the camped cell or base station.

[0194] In operation 8-20, the UE in the connected mode may receive QoE configuration information from the base station. The QoE configuration information may be included in an RRCReconfiguration message and sent. Alternatively, the UE in the inactive mode may receive the QoE configuration information through an RRCResume message.

[0195] In operation 8-25, the UE in the connected mode may determine whether the QoE configuration and SRB4 for QoE report message transmission have been configured.

[0196] In operation 8-30, when the QoE configuration and SRB4 have been configured, the UE may repeatedly perform operations 8-35 to 8-55 for each measConfigAppLayerId to send a QoE report message (MeasurementReportAppLayer).

[0197] In operation 8-35, according to an embodiment of the present disclosure, when there is a QoE container (measReportAppLayerContainer) that the UE AS layer has received from the app layer but has not yet sent and the QoE container report has not yet been suspended, the QoE report container in the MeasReportAppLayer message (measReportAppLayerContainer) can be configured as the QoE report information received from the app layer.

[0198] In operation 8-40, the UE AS layer may configure the measConfigAppLayerId in the MeasurementReportAppLayer message to the measConfigAppLayerId that has been received from the app layer together with the QoE measurement result.

[0199] In operation 8-45, according to an embodiment of the present disclosure, when the UE AS layer has received session measurement start and stop information (appLayerSessionStatus) from the app layer and the transmission of appLayerSessionStatus has not been suspended, the UE can configure the appLayerSessionStatus in the MeasurementReportAppLayer message to the received value.

[0200] In operation 8-50, in the case where the UE AS layer has received the RAN visible QoE measurement result from the app layer, the UE may configure the ran-VisibleMeasurements in the MeasurementReportAppLayer message to the received value.

[0201] In operation 8-55, the UE may send a MeasurementReportAppLayer message.

[0202] In the case where operations for all measConfigAppLayerIds are ended in operation 8-30, the UE operation may end in operation 8-60.

[0203] In case that QoE is configured or SRB4 is not configured in operation 8-25, the UE may neither configure nor send a MeasurementReportAppLayer message in operation 8-65.

[0204] As mentioned above, through FIG. 8A to FIG. 8B The operations of the present disclosure provided with the related description can be expressed as, for example, Table 21 below.

[0205]

Table 21

[0206]

[0207]

[0208] The problem to be solved by the present disclosure is that the UE can generate and send a MeasurementReportAppLayer message for each measConfigAppLayerId (in operation 6-30). In the case where the UE receives multiple pieces of QoE configuration information from the base station, the UE can generate a QoE measurement result report for each measConfigAppLayerId (QoE configuration information ID). The QoE measurement result report (e.g., measReportAppLayerContainer, appLayerSessionStatus, ran-VisibleMeasurements) generated for each measConfigAppLayerId can be included in one MeasurementReportAppLayer message and sent. That is, multiple MeasurementReportAppLayer messages are generated for multiple MeasConfigAppLayerIDs, and the UE can send multiple MeasurementReportAppLayer messages.

[0209] In case a single QoE measurement result report for one measConfigAppLayerId is received from the app layer, the UE may send a MeasurementReportAppLayer message, while only one entry (MeasurementReportAppLayer-r17-IEs) in the measurementReportAppLayerList within one MeasurementReportAppLayer message contains the QoE measurement result.

[0210] In the case where multiple QoE measurement result reports about one measConfigAppLayerId are received from the app layer, the UE may include reporting multiple QoE measurement results to multiple MeasurementReportAppLayer-r17-IEs, and each entry (MeasurementReportAppLayer-r17-IEs) in the measurementReportAppLayerList within one MeasurementReportAppLayer message includes the same measConfigAppLayerId. That is, the UE may include multiple measurementReportAppLayer-r17-IEs configured with the same measConfigAppLayerId in one MeasurementReportAppLayer message and send it to the base station.

[0211] Considering that the measurementReportAppLayerList in the MeasurementReportAppLayer message may include multiple MeasurementReportAppLayer-r17-IEs, it may be inefficient to only include QoE measurement result reports configured by the same measConfigAppLayerId in the MeasurementReportAppLayer message. That is, in the event of a report of QoE measurement results for multiple MeasConfigAppLayerIDs, generating / configuring / sending multiple MeasurementReportAppLayer messages (the same number as the number of MeasConfigAppLayerIds) may result in a waste of computing power usage and power usage of the UE and the base station, not only in terms of radio resource usage, but also in terms of generating / processing / sending or receiving multiple messages. In order to solve the above problem, the present disclosure proposes a method that enables QoE measurement result reports for multiple MeasConfigAppLayerIds to be included in one MeasurementReportAppLayer message, and this can be regarded as more efficient in terms of radio resource usage, computing power usage and power usage of the UE and the base station.

[0212] Fig.9A and Fig. 9B UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is illustrated.

[0213] Fig.9A and Fig. 9BExample methods that can be implemented according to the principles of the present disclosure are shown, and various changes can be made to the methods shown in the flowcharts herein. For example, although shown as a series of operations, the various operations in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, an operation can be omitted or replaced by other operations.

[0214] In operation 9-05, the UE may receive system information (SIB) transmitted by the base station.

[0215] In operations 9-10, the UE may camp on a specific base station or cell based on the received SIB.

[0216] In operation 9-15, the UE may establish an RRC connection with the cell or base station in which it resides.

[0217] In operation 9-20, the UE in the connected mode may receive QoE configuration information from the base station. The QoE configuration information may be included in an RRCReconfiguration message and sent. Alternatively, the UE in the inactive mode may receive the QoE configuration information through an RRCResume message.

[0218] In operation 9-25, the UE in the connected mode may determine whether the QoE configuration and SRB4 for QoE report message transmission have been configured.

[0219] In operation 9-30, when the QoE configuration and SRB4 have been configured according to an embodiment of the present disclosure, the UE may repeatedly perform operations 9-35 to 9-50 for each measConfigAppLayerId to send a QoE report message (MeasurementReportAppLayer). According to the parameter configuration operation for each measConfigAppLayerId in operations 9-35 to 9-50, each MeasurementReportAppLayer-r17-IEs may be configured in the same MeasurementReportAppLayer message. According to the repeated parameter configuration operation for multiple measConfigAppLayerIds in operations 9-35 to 9-50, multiple MeasurementReportAppLayer-r17-IEs may be configured in the same MeasurementReportAppLayer message.

[0220] In operation 9-35, when there is a QoE container (measReportApLayerContainer) that the UE AS layer has received from the app layer but has not yet sent, and the QoE container report has not been suspended, the QoE report container in the MeasurementReportAppLayer message (measReportApLayerContainer) can be configured as the QoE report information received from the app layer.

[0221] In operation 9-40, the UE AS layer may configure the measConfigAppLayerId in the MeasurementReportAppLayer message to the measConfigAppLayerId that has been received from the app layer together with the QoE measurement result.

[0222] In operation 9-45, in a case where the UE AS layer has received session measurement start and stop information from the app layer, the UE may configure appLayerSessionStatus in the MeasurementReportAppLayer message to the received value.

[0223] In operation 9-50, in the case where the UE AS layer has received the RAN visible QoE measurement result from the app layer, the UE may configure the ran-VisibleMeasurements in the MeasurementReportAppLayer message to the received value.

[0224] According to an embodiment of the present disclosure, the operations for all measConfigAppLayerIds are ended in operation 9-30, and the UE may send a MeasurementReportAppLayer message in operation 9-55. For multiple measConfigAppLayerIds, only a single MeasurementReportAppLayer message may be configured and sent.

[0225] In case QoE is configured or SRB4 is not configured in operation 9-25, the UE may neither configure nor send a MeasurementReportAppLayer message in operation 9-60.

[0226] As mentioned above, through FIG. 9A to FIG. 9B The operations of the present disclosure provided with the related description can be expressed as, for example, Table 22 below.

[0227]

Table 22

[0228]

[0229]

[0230]

[0231] Another problem to be solved by the present disclosure is that the MeasurementReportAppLayer-r17-IEs in the MeasurementReportAppLayer message sent by the UE may include only measConfigAppLayerId. measReportApLayerContainer is an optional field, and in operation 6-35, if there is no QoE report that the UE AS layer has received but not yet sent from the app layer or the QoE report has been suspended, measReportApLayerContainer may not be included in the MeasurementReportAppLayer-r17-IEs. measConfigAppLayerId is a mandatory field and may therefore always be included in the measurementReportAppLayer-r17-IEs in operation 6-40. appLayerSessionStatus is an optional field, and in operation 6-45, if the UE AS layer has not yet received session measurement start and stop information from the app layer, appLayerSessionStatus may not be included in the MeasurementReportAppLayer-r17-IEs. ran-VisibleMeasurements is an optional field, and in operation 6-50, if the UE AS layer has not received the RAN visible QoE measurement results from the app layer, ran-VisibleMeasurements may not be included in the measurementReportAppLayer-r17-IEs. As a result, the MeasurementReportAppLayer-r17-IEs in the MeasurementReportAppLayer message sent by the UE may only include measConfigAppLayerId. Reporting only measConfigAppLayerId without meaningful QoE information (measReportApLayerContainer, appLayerSessionStatus, or ran-VisibleMeasurements) when reporting QoE measurement results to the base station by the UE may waste radio resources, computing resources, and energy consumption of the UE and the base station. This is because the base station can know the QoE configuration Id (measConfigAppLayerId) that has been configured for the corresponding UE. Since measConfigAppLayerId is an indicator indicating which QoE configuration the meaningful QoE information is generated by, transmission to the base station without the meaningful QoE information may be inefficient.Furthermore, the QoE report thus generated may be transmitted from the base station to the TCE or OAM, and thus resources of the core network may also be wasted.

[0232] In order to solve the above problem, the present disclosure proposes that, in addition to measConfigAppLayerId, at least one other parameter (measReportTappLayerContainer, appLayerSessionStatus or ran-VisibleMeasurements) is also included in MeasurementReportAppLayer-r17-IEs and sent to the base station.

[0233] As another embodiment, in order to prevent the UE AS layer from receiving appLayerSessionStatus from the app layer too frequently and generating and sending QoE reports too frequently, in addition to measConfigAppLayerId and appLayerSessionStatus, at least one other parameter (measReportAppLayerContainer or ran-VisibleMeasurements) is also included in MeasurementReportAppLayer-r17-IEs and sent to the base station.

[0234] Fig. 10A and Fig. 10B UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is illustrated.

[0235] Fig. 10A and Fig. 10B Example methods that can be implemented according to the principles of the present disclosure are shown, and various changes can be made to the methods shown in the flowcharts herein. For example, although shown as a series of operations, the various operations in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, an operation can be omitted or replaced by another operation.

[0236] In operation 10-05, the UE may receive system information (SIB) transmitted by the base station.

[0237] In operation 10-10, the UE may camp on a specific base station or cell based on the received SIB.

[0238] In operation 10-15, the UE may establish an RRC connection with the cell or base station in which it resides.

[0239] In operation 10-20, the UE in the connected mode may receive QoE configuration information from the base station. The QoE configuration information may be included in an RRCReconfiguration message and sent. Alternatively, the UE in the inactive mode may receive the QoE configuration information through an RRCResume message.

[0240] In operation 10-25, the UE in the connected mode may determine whether the QoE configuration and SRB4 for QoE report message transmission have been configured.

[0241] In operation 10-30, according to an embodiment of the present disclosure, when the QoE configuration and SRB4 are configured, the UE may repeatedly perform operations 10-35 to 10-60 for each measConfigAppLayerId to send a QoE report message (MeasurementReportAppLayer).

[0242] In operation 10-35, the UE may determine whether the provided conditions are met according to an embodiment of the present disclosure. The provided conditions may include some or all of the following conditions. Here, an "or" condition may be used between the following conditions:

[0243] 1) The condition of including measReportApLayerContainer: when there is a QoE report that the UE AS layer has received from the app layer but has not yet sent, and the QoE report has not been suspended;

[0244] 2) Conditions including AppLayerSessionStatus: when the UE AS layer has received session measurement start and stop information from the app layer; and / or

[0245] 3) Conditions including RAN-VisibleMeasurements: When the UE AS layer has received RAN-visible QoE measurement results from the app layer.

[0246] As an embodiment of the present disclosure, when all three conditions are included as provided conditions, 1) when there is a QoE report that the UE AS layer has received from the app layer but has not yet sent and the QoE report has not yet been suspended, or 2) when the UE AS layer has received session measurement start and stop information from the app layer, or 3) when the UE AS layer has received the RAN visible QoE measurement result from the app layer, the operation can proceed to operation 10-40. As a result, measReportTappLayerContainer and / or appLayerSessionStatus and / or ran-VisibleMeasurements may be included in operations 10-40, 10-50, and 10-55.

[0247] As an embodiment of the present disclosure, when only the first condition and the third condition are included as the provided conditions, 1) when there is a QoE report that the UE AS layer has received but not yet sent from the app layer and the QoE report has not been suspended, or 3) when the UE AS layer has received the RAN visible QoE measurement result from the app layer, the provided conditions are met and the operation can proceed to operation 10-40. As a result, measReportApLayerContainer and / or ran-VisibleMeasurements can be included in operations 10-40 and 10-55.

[0248] If the provided conditions are not met, the UE operation may proceed to operation 10-30.

[0249] In operation 10-40, when there is a QoE report that the UE AS layer has received from the app layer but has not yet sent, and the QoE report has not been suspended, the QoE report container (measReportAppLayerContainer) in the MeasurementReportAppLayer message can be configured with the QoE report information that has been received from the app layer.

[0250] In operation 10-45, the UE AS layer may configure the measConfigAppLayerId in the MeasurementReportAppLayer message to the measConfigAppLayerId that has been received from the app layer together with the QoE measurement result.

[0251] In operation 10-50, in a case where the UE AS layer has received session measurement start and stop information from the app layer, the UE may configure appLayerSessionStatus in the MeasurementReportAppLayer message to the received value.

[0252] In operation 10-55, in the case where the UE AS layer has received the RAN visible QoE measurement result from the app layer, the UE may configure the ran-VisibleMeasurements in the MeasurementReportAppLayer message to the received value.

[0253] In operation 10-60, the UE may send a MeasurementReportAppLayer message.

[0254] In the case where the operations for all measConfigAppLayerIds are ended in operation 10-30, the UE operation may end in operation 10-65.

[0255] In case that QoE is configured or SRB4 is not configured in operation 10-25, the UE may neither configure nor send a MeasurementReportAppLayer message in operation 10-70.

[0256] As mentioned above, through FIG. 10A to FIG. 10B The operations of the present disclosure provided with the related description can be expressed as, for example, Table 23 below.

[0257]

Table 23

[0258]

[0259]

[0260] The conditions provided in operation 10-35 may be modified in various embodiments as described above.

[0261] Another embodiment may allow the case where MeasurementReportAppLayer-r17-IEs only includes measConfigAppLayerId. However, this case may be defined to indicate that the UE has a QoE configuration for the corresponding measConfigAppLayerId, but has no QoE measurement results or related information to report.

[0262] Fig.11A and Fig. 11B UE operation for reporting QoE measurement results according to an embodiment of the present disclosure is illustrated.

[0263] FIG. 11A to FIG. 11B yes FIG. 9A to FIG. 9B and FIG. 10A to FIG. 10B A detailed description of each operation can be found in FIG. 9A to FIG. 9B and FIG. 10A to FIG. 10B Description.

[0264] pass Fig.11A and Fig. 11B The operations of the present disclosure provided may be represented as, for example, in Table 24 below.

[0265]

Table 24

[0266]

[0267]

[0268]

[0269] As another embodiment of the present disclosure, by FIG. 11A to FIG. 11B The operations provided by the present disclosure can be expressed as, for example, Table 25 below.

[0270]

Table 25

[0271]

[0272]

[0273] That is to say, Fig.11A and Fig. 11B After operation 11-55 in , a method of removing MeasurementReportAppLayer-r17-IEs including only measConfigAppLayerId (and / or appLayerSessionStatus) in the MeasurementReportAppLayer message may be used.

[0274] As another embodiment of the present disclosure, by FIG. 11A to FIG. 11B The operations provided by the present disclosure can be expressed as, for example, Table 26 below.

[0275]

Table 26

[0276]

[0277]

[0278] That is, it may be specified that MeasurementReportAppLayer-r17-IEs including only measConfigAppLayerId (or / and appLayerSessionStatus) is not included in the MeasurementReportAppLayer message.

[0279] FIG. 11C to FIG. 11HThe structure of a message for reporting a QoE measurement result according to an embodiment of the present disclosure is shown.

[0280] In an embodiment, for setting the FIG. 11C to FIG. 11H The information in the message for reporting QoE measurement results and the operation for sending the message can be FIG. 9A to FIG. 9B or FIG. 10A to FIG. 10B For reference.

[0281] like Fig. 11C As shown in FIG. 1 , the MeasurementReportAppLayer message may include only one MeasurementReportAppLayer-r17-IEs for each measConfigAppLayerId. Fig. 11C As shown, the MeasurementReportAppLayer message may include one MeasurementReportAppLayer-r17-IEs with a measConfigAppLayerId of 8, one MeasurementReportAppLayer-r17-IEs with a measConfigAppLayerId of 3, and one MeasurementReportAppLayer-r17-IEs with a measConfigAppLayerId of 7. In this example, each MeasurementReportAppLayer-r17-IEs includes all four parameters (measConfigAppLayerId, measReportAppLayerContainer, appLayerSessionStatus, ran-VisibleMeasurements), but measReportAppLayerContainer, appLayerSessionStatus, and / or ran-VisibleMeasurements, which are optional fields, may be omitted.

[0282] like Fig.11D As shown, the MeasurementReportAppLayer message can include multiple MeasurementReportAppLayer-r17-IEs for the same measConfigAppLayerId (there can be multiple QoE reports with different measConfigAppLayerIds and multiple QoE reports with the same measConfigAppLayerId in the MeasurementReportAppLayer message). Fig.11D As shown, the MeasurementReportAppLayer message may include two MeasurementReportAppLayer-r17-IEs with a measConfigAppLayerId of 8 and one MeasurementReportAppLayer-r17-IEs with a measConfigAppLayerId of 7. In this example, each MeasurementReportAppLayer-r17-IEs includes all four parameters (measConfigAppLayerId, measReportAppLayerContainer, appLayerSessionStatus, ran-VisibleMeasurements), but measReportAppLayerContainer, appLayerSessionStatus, and / or ran-VisibleMeasurements, which are optional fields, may be omitted.

[0283] The problem to be solved by the present disclosure is that when multiple MeasurementReportAppLayer-r17-IEs are included in the MeasurementReportAppLayer message, the base station, OAM, TCE server or MCE server receiving it may not know the time order in which the MeasurementReportAppLayer message is generated. That is, there is no indication of the generation time of each MeasurementReportAppLayer-r17-IEs, and there is no rule for the UE to store multiple MeasurementReportAppLayer-r17-IEs in the MeasurementReportAppLayer message. In addition, the same problem also exists in the case where multiple MeasurementReportAppLayer-r17-IEs with the same measConfigAppLayerId are included in the MeasurementReportAppLayer message. The generation time (or measurement time) or generation order of the QoE report may be very important for the base station or OAM or TCE server or MCE server. In the case where the received QoE report corresponds to data that occurred a long time ago, the QoE report may be information that is useless for the base station or OAM or TCE server or MCE server to optimize the current network situation.

[0284] In addition, Fig.11DIn the example, regarding two MeasurementReportAppLayer-r17-IEs with the same measConfigAppLayerId8, for example, the base station or OAM or TCE server or MCE server may not know which of the two MeasurementReportAppLayer-r17-IEs is the first or last generated (or measured) data. For example, when appLayerSessionStatus8-1 indicates "started" and appLayerSessionStatus8-2 indicates "stopped", the base station (or OAM or TCE server or MCE server) may not know whether the corresponding application session is started and then stopped or stopped and then started, and accordingly, incorrect interpretation may cause network optimization failure. In addition, in the case where MeasReportTappLayerContainer 8-1 (or ran-VisibleMeasurements8-1) has a good overall QoE performance index and MeasReportTappLayerContainer 8-2 (or ran-VisibleMeasurements 8-2) has a poor overall QoE performance index, for example, without knowing the generation order of MeasurementReportAppLayer-r17-IEs, it is impossible to determine whether the latest network has a problem or whether a relatively old network has a problem.

[0285] In an embodiment provided by the present disclosure for solving the above-mentioned problem, the UE may specify the order of each MeasurementReportAppLayer-r17-IEs in the MeasurementReportAppLayer message through a separate indicator (eg, createdOrder), as shown in Table 27 below.

[0286]

Table 27

[0287]

[0288]

[0289] Here, the order can be one of the following methods.

[0290] Method 1) The order in which the UE AS layer generates MeasurementReportAppLayer-r17-IEs.

[0291] Method 2) The order in which the UE AS layer receives information included in MeasurementReportAppLayer-r17-IEs from the app layer.

[0292] Method 3) The order in which the UE AS layer receives information stored in the measReportApLayerContainer from the app layer. In this case, the order may be indicated only for the MeasurementReportAppLayer-r17-IEs including the MeasReportApLayerContainer.

[0293] Method 4) The order in which the UE AS layer receives the information stored in appLayerSessionStatus from the app layer. In this case, the order can be indicated only for MeasurementReportAppLayer-r17-IEs including appLayerSessionStatus.

[0294] Method 5) The order in which the UE AS layer receives the information stored in ran-VisibleMeasurements from the app layer. In this case, the order can be indicated only for MeasurementReportAppLayer-r17-IEs including ran-VisibleMeasurements.

[0295] Method 6) A combination of some or all of the above methods 3, 4, and 5. For example, when methods 3 and 4 are combined, an indicator for indicating the order of measReportApLayerContainer (e.g., createdOrder1) and an indicator for indicating the order of appLayerSessionStatus (e.g., createdOrder2) may be defined separately.

[0296] A lower order value may indicate a more recent QoE report. Alternatively, a higher order value may indicate a more recent QoE report.

[0297] Only when multiple MeasurementReportAppLayer-r17-IEs are included in the MeasurementReportAppLayer message, the UE can configure the indicator for each MeasurementReportAppLayer-r17-IEs. Alternatively, only when multiple MeasurementReportAppLayer-r17-IEs with the same measConfigAppLayerId are included in the MeasurementReportAppLayer message, the UE can configure the indicator for each MeasurementReportAppLayer-r17-IEs with the same measConfigAppLayerId.

[0298] As a result, the base station or OAM or TCE server or MCE server that has received the indicator can recognize the generation or measurement order of each MeasurementReportAppLayer-r17-IEs (with respect to the same measConfigAppLayerId).

[0299] According to an embodiment provided by the present disclosure, the UE may specify the time information of each MeasurementReportAppLayer-r17-IEs in the MeasurementReportAppLayer message through a separate indicator (eg, a timestamp), as shown in Table 28 below.

[0300]

Table 28

[0301]

[0302]

[0303] Here, the time information can be one of the following methods.

[0304] Method 1) The time when the UE AS layer generates MeasurementReportAppLayer-r17-IEs. Method 2) The time when the UE AS layer receives the information included in MeasurementReportAppLayer-r17-IEs from the app layer.

[0305] Method 3) The time when the UE AS layer receives the information stored in the measReportApLayerContainer from the app layer.

[0306] Method 4) The time when the UE AS layer receives the information stored in appLayerSessionStatus from the app layer.

[0307] Method 5) The time when the UE AS layer receives the information stored in ran-VisibleMeasurements from the app layer.

[0308] Method 6) A combination of some or all of the above methods 3, 4, and 5. For example, when methods 3 and 4 are combined, an indicator (e.g., timestamp1) for indicating the time of MeasReportTappLayerContainer and an indicator (e.g., timerstamp2) for indicating the time of appLayerSessionStatus can be defined separately.

[0309] The time information value may be absolute time information, or may be relative time information based on a specific time (e.g., the time point when a session is started in the App layer, the time point when QoE measurement is started in the App layer, or the time point when the first report is received from the App layer).

[0310] The UE may configure the indicator for each MeasurementReportAppLayer-r17-IEs only when multiple MeasurementReportAppLayer-r17-IEs are included in the MeasurementReportAppLayer message. Alternatively, the UE may configure the indicator for each MeasurementReportAppLayer-r17-IEs having the same measConfigAppLayerId only when multiple MeasurementReportAppLayer-r17-IEs having the same measConfigAppLayerId are included in the MeasurementReportAppLayer message.

[0311] As a result, the base station or OAM or TCE server or MCE server receiving the indicator can determine the generation or measurement time point of each MeasurementReportAppLayer-r17-IEs (relative to the same measConfigAppLayerId).

[0312] According to an embodiment provided by the present disclosure, the UE may specify the order (which may be one of the methods related to the order) by the storage order of each MeasurementReportAppLayer-r17-IEs in the MeasurementReportAppLayer message without introducing a separate indicator. Regardless of the measConfigAppLayerId within the MeasurementReportAppLayer message, the MeasurementReportAppLayer-r17-IEs already stored in the Nth entry of the measurementReportAppLayerList may represent the Nth round of MeasurementReportAppLayer-r17-IEs (e.g., the MeasurementReportAppLayer-r17-IEs have been received from the app layer for the Nth time). For example, in Fig.11E , the first entry (leftmost) in the MeasurementReportAppLayer message can be the MeasurementReportAppLayer-r17-IEs received from the app layer for the first time (time 1). The second entry can be the MeasurementReportAppLayer-r17-IEs received from the app layer for the second time (time 2). The third entry can be the MeasurementReportAppLayer-r17-IEs received from the app layer for the third time (time 3).

[0313] If method 3 (or method 4 or 5) that has been described with respect to the definition of order is applied to this embodiment, the method may be applied only to entries including measReportTappLayerContainer (or appLayerSessionStatus or ran-VisibleMeasurements). For example, when method 4 is applied, regardless of measConfigAppLayerId within the MeasurementReportAppLayer message, the Nth MeasurementReportAppLayer-r17-IEs entry including appLayerSessionStatus within the measurementReportAppLayerList may mean the case where the Nth corresponding appLayerSessionStatus is received from the app layer among the MeasurementReportAppLayer-r17-IEs including appLayerSessionStatus. For example, in Fig.11F, appLayerSessionStatus 8-1 received for the first time may be included as the first entry (in MeasurementReportAppLayer-r17-IEs including appLayerSessionStatus), appLayerSessionStatus7 received for the second time may be included as the second entry (in MeasurementReportAppLayer-r17-IEs including appLayerSessionStatus), and appLayerSessionStatus 8-3 received for the third time may be included as the third entry (in MeasurementReportAppLayer-r17-IEs including appLayerSessionStatus).

[0314] As a result, the base station or OAM or TCE server or MCE server that has received the corresponding appLayerSessionStatus can recognize the order of generation or measurement of MeasReportApLayerContainer (or appLayerSessionStatus or ran-VisibleMeasurements).

[0315] According to an embodiment provided by the present disclosure, the UE may specify the order by the storage order between MeasurementReportAppLayer-r17-IEs having the same measConfigAppLayerId in the MeasurementReportAppLayer message (this may be one of the methods for defining the order) without introducing a separate indicator. The MeasurementReportAppLayer-r17-IEs that have been stored for the Nth time among the MeasurementReportAppLayer-r17-IEs having the same measConfigAppLayerId in the MeasurementReportAppLayer message may indicate the Nth round of MeasurementReportAppLayer-r17-IEs among the MeasurementReportAppLayer-r17-IEs (for example, the MeasurementReportAppLayer-r17-IEs have been received from the app layer for the Nth time). For example, in Fig.11G, the first entry (leftmost) in the MeasurementReportAppLayer message may correspond to the MeasurementReportAppLayer-r17-IEs received from the app layer for the first time (time 1) among the entries with a measConfigAppLayerId value of 8. The second entry may correspond to the MeasurementReportAppLayer-r17-IEs received from the app layer for the first time among the entries with a measConfigAppLayerId value of 7.

[0316] Alternatively, when there are no other entries with a measConfigAppLayerId value of 7, the second entry may not indicate any time information. The entry with a measConfigAppLayerId value of 7 may not indicate the relative order between itself and the entry with a measConfigAppLayerId value of 8. That is, the entry may not indicate the relative order between different measConfigAppLayerIds values. The third entry may correspond to the MeasurementReportAppLayer-r17-IEs received from the app layer for the second time (time 2) among the entries with a measConfigAppLayerId value of 8.

[0317] When method 3 (or 4 or 5) which has been described with respect to the definition of the order in the above-mentioned embodiments is applied to this embodiment, the method may be applied only to entries including measReportTappLayerContainer (or appLayerSessionStatus or ran-VisibleMeasurements). For example, in the case of applying method 4, the Nth MeasurementReportAppLayer-r17-IEs entry including appLayerSessionStatus of the same measConfigAppLayerId within the MeasurementReportAppLayer message may mean the case where the corresponding appLayerSessionStatus is received Nth time from the app layer among the MeasurementReportAppLayer-r17-IEs having the same measConfigAppLayerId including appLayerSessionStatus. For example, in Fig.11H, the first received appLayerSessionStatus8-1 with measConfigAppLayerId of 8 can be included as the first entry (among the MeasurementReportAppLayer-r17-IEs with measConfigAppLayerId of 8 and including appLayerSessionStatus), and the second received appLayerSessionStatus8-3 with measConfigAppLayerId of 8 can be included as the second entry (among the MeasurementReportAppLayer-r17-IEs with measConfigAppLayerId of 8). Similarly, appLayerSessionStatus7-1 received for the first time with measConfigAppLayerId of 7 may not be included as the first entry (in MeasurementReportAppLayer-r17-IEs with measConfigAppLayerId of 7 and including appLayerSessionStatus), and appLayerSessionStatus7-2 received for the second time with measConfigAppLayerId of 7 may be included as the second entry (in MeasurementReportAppLayer-r17-IEs with measConfigAppLayerId of 7 and including appLayerSessionStatus).

[0318] As a result, the base station or OAM or TCE server or MCE server that has received the corresponding appLayerSessionStatus can recognize the order of generation or measurement of MeasReportApLayerContainer (or appLayerSessionStatus or ran-VisibleMeasurements).

[0319] In another embodiment provided by the present disclosure, when the UE AS layer receives appLayerSessionStatus information of the same measConfigAppLayerId from the app layer multiple times, the UE AS layer may include only the latest appLayerSessionStatus in a single MeasurementReportAppLayer-r17-IEs within the MeasurementReportAppLayer message and send it, instead of storing the appLayerSessionStatus information multiple times (e.g., generating multiple MeasurementReportAppLayer-r17-IEs within one MeasurementReportAppLayer message or storing the information in multiple MeasurementReportAppLayer-r17-IEs). Since the base station may only need the current status of the corresponding session of the app layer (whether ongoing or suspended), the previously received appLayerSessionStatus may not be included in the MeasurementReportAppLayer message or may be discarded. When appLayerSessionStatus is repeatedly received in the same measConfigAppLayerId, the UE AS layer may discard the previously received appLayerSessionStatus instead of further storing it, and may store only the new appLayerSessionStatus.

[0320] Fig.12 The internal structure of the UE according to an embodiment of the present disclosure is shown.

[0321] refer to Fig.12 , the UE may include a radio frequency (RF) processor 12-10, a baseband processor 12-20, a memory 12-30, and a controller 12-40.

[0322] The RF processor 12-10 performs functions such as frequency band conversion and signal amplification for transmitting and receiving signals through a radio channel. That is, the RF processor 12-10 up-converts the baseband signal provided by the baseband processor 12-20 into an RF band signal, thereby transmitting the RF band signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processor 12-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Although in Fig.12Only one antenna is shown in the figure, but the UE may have multiple antennas. In addition, the RF processor 12-10 may include multiple RF chains. In addition, the RF processor 12-10 may perform beamforming. In order to perform beamforming, the RF processor 12-10 may adjust the phase and amplitude of the signals sent and received through multiple antennas or antenna elements. In addition, the RF processor may perform MIMO and may receive multiple layers when performing MIMO operations.

[0323] The baseband processor 12-20 performs the conversion function between the baseband signal and the bit string according to the physical layer specification of the system. For example, during data transmission, the baseband processor 12-20 encodes and modulates the transmission bit string to generate a complex symbol. In addition, when receiving data, the baseband processor 12-20 demodulates and decodes the baseband signal provided from the RF processor 12-10 to recover the received bit string. For example, in the case where the orthogonal frequency division multiplexing (OFDM) scheme is applied, when sending data, the baseband processor 12-20 generates a complex symbol by encoding and modulating the transmission bit string, maps the complex symbol to a subcarrier, and then configures the OFDM symbol by an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processor 12-20 divides the baseband signal provided by the RF processor 12-10 into OFDM symbol units, recovers the signal mapped to the subcarrier by a fast Fourier transform (FFT) operation, and then recovers the received bit string by demodulation and decoding.

[0324] As described above, the baseband processor 12-20 and the RF processor 12-10 can send or receive signals. Therefore, the baseband processor 12-20 and the RF processor 12-10 can be referred to as a "transmitter", "receiver", "transceiver", or "communication unit". In addition, at least one of the baseband processor 12-20 and the RF processor 12-10 may include multiple communication modules to support a variety of different radio access technologies. In addition, at least one of the baseband processor 12-20 and the RF processor 12-10 may include different communication modules to process signals in different frequency bands. For example, different radio access technologies may include wireless LANs (e.g., IEEE 802.11), cellular networks (e.g., LTE / NR), etc. In addition, different frequency bands may include ultra-high frequency (SHF) (e.g., 2NRHz or NRHz) bands or millimeter wave (e.g., 60GHz) bands.

[0325] The memory 12-30 may store data such as basic programs, applications, and configuration information for UE operation. In particular, the memory 12-30 may store information related to a second access node that performs wireless communication using a second radio access technology. In addition, the memory 12-30 provides stored data in response to a request from the controller 12-40.

[0326] The controller 12-40 may control the entire UE operation. For example, the controller 12-40 sends and receives signals through the baseband processor 12-20 and the RF processor 12-10. In addition, the controller 12-40 records data in the memory 12-30 and reads data from the memory 12-30. To this end, the controller 12-40 may include at least one processor. For example, the controller 12-40 may include a communication processor (CP) for controlling communication and an application processor (AP) for controlling a high layer such as an application program.

[0327] Fig.13 The configuration of a base station according to an embodiment of the present disclosure is shown.

[0328] like Fig.13 As shown, the base station may include a radio frequency (RF) processor 13-10, a baseband processor 13-20, a backhaul communication unit 13-30, a memory 13-40, and a controller 13-50.

[0329] The RF processor 13-10 may perform functions such as frequency band conversion and signal amplification to transmit and receive signals through a radio channel. That is, the RF processor 13-10 may up-convert a baseband signal provided from the baseband processor 13-20 into an RF band signal, thereby transmitting the RF band signal through an antenna, and may down-convert an RF band signal received through an antenna into a baseband signal. For example, the RF processor 13-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), and the like. Although in Fig.13 Only one antenna is shown in the figure, but the first access node may have multiple antennas. In addition, the RF processor 13-10 may include multiple RF chains. In addition, the RF processor 13-10 may perform beamforming. In order to perform beamforming, the RF processor 13-10 may adjust the phase and amplitude of the signals sent and received through multiple antennas or antenna elements. The RF processor may perform downlink MIMO operations by sending one or more layers.

[0330] The baseband processor 13-20 can perform the function of conversion between the baseband signal and the bit string according to the physical layer standard of the first radio access technology. For example, during data transmission, the baseband processor 13-20 encodes and modulates the transmission bit string to generate a complex symbol. In addition, when receiving data, the baseband processor 13-20 demodulates and decodes the baseband signal provided from the RF processor 13-10 to recover the received bit string. For example, in the case where the OFDM scheme is applied, when transmitting data, the baseband processor 13-20 generates a complex symbol by encoding and modulating the transmission bit string, maps the complex symbol to a subcarrier, and then configures the OFDM symbol by IFFT operation and CP insertion. In addition, when receiving data, the baseband processor 13-20 divides the baseband signal provided by the RF processor 13-10 into OFDM symbol units, recovers the signal mapped to the subcarrier by a fast Fourier transform (FFT) operation, and then recovers the received bit string by demodulation and decoding. As described above, the baseband processor 13-20 and the RF processor 13-10 can transmit or receive signals. Therefore, the baseband processor 13-20 and the RF processor 13-10 can be referred to as a "transmitter", "receiver", "transceiver", "communication unit" or "wireless communication unit".

[0331] The backhaul communication unit 13-30 provides an interface for communicating with other nodes in the network. That is, the backhaul communication unit 13-30 converts a bit string sent from the master base station to another node (eg, an auxiliary base station, a core network, etc.) into a physical signal, and converts a physical signal received from another node into a bit string.

[0332] The memory 13-40 stores data such as basic programs, applications, and configuration information for the operation of the master base station. Specifically, the memory 13-40 may store information about the bearer assigned to the accessed UE, the measurement results reported from the accessed UE, etc. In addition, the memory 13-40 may store information used as a standard for determining whether to provide or stop multiple connections to the UE. In addition, the memory 13-40 provides the stored data according to the request of the controller 13-50.

[0333] The controller 13-50 controls the overall operation of the master base station. For example, the controller 13-50 sends or receives signals through the baseband processor 13-20 and the RF processor 13-10 or through the backhaul communication unit 13-30. In addition, the controller 13-50 records data in the memory 13-40 and reads data from the memory 13-40. To this end, the controller 13-50 may include at least one processor.

[0334] The embodiments of the present disclosure described and shown in the specification and the drawings are merely specific examples that have been presented to easily explain the technical content of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. It is obvious to those skilled in the art that, in addition to the embodiments set forth herein, other variations based on the technical concept of the present disclosure can be implemented. In addition, the above-mentioned various embodiments can be adopted in combination as needed.

[0335] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: receiving, from a base station, a radio resource control (RRC) message including configuration information regarding application layer measurements; For each application layer measurement configuration identifier (ID), setting an application layer measurement report entry in an application layer measurement report message based on the configuration information; as well as Sending an application layer measurement report message to the base station, The application layer measurement report message includes multiple application layer measurement configuration IDs and multiple application layer measurement report items associated with the multiple application layer measurement configuration IDs.

2. The method according to claim 1, further comprising: Initiating an uplink (UL) message segmentation transfer procedure when the size of the encoded application layer measurement report message is larger than the maximum supported size of a packet data convergence protocol (PDCP) service data unit (SDU) and RRC message segmentation is enabled according to configuration information, The application layer measurement report message is sent based on signaling radio bearer 4 (SRB4).

3. The method according to claim 1, wherein: The multiple application layer measurement report entries are included in the application layer measurement report message in the order of generation.

4. The method according to claim 1, wherein: The application layer measurement report message includes timestamp information, which indicates at least one of the following for each application layer measurement configuration ID: The time when the access stratum (AS) layer of the terminal generates an application layer measurement report entry; The time at which the AS layer receives information to be included in an application layer measurement report entry from the application layer of the terminal; The time at which the AS layer receives information to be included in the application layer measurement report container information of the application layer measurement report entry from the application layer; the time at which the AS layer receives from the application layer information to be included in the application layer measurement session state information of the application layer measurement report entry; and The time when the AS layer receives information from the application layer to be included in the radio access network (RAN) visible application layer measurement information of the application layer measurement report entry.

5. A method performed by a base station in a wireless communication system, the method comprising: sending a radio resource control (RRC) message including configuration information about application layer measurements to a terminal; as well as receiving an application layer measurement report message from a terminal, wherein for each application layer measurement configuration identifier (ID), the application layer measurement report message includes an application layer measurement report item set according to the configuration information, The application layer measurement report message includes multiple application layer measurement configuration IDs and multiple application layer measurement report items associated with the multiple application layer measurement configuration IDs.

6. The method according to claim 5, wherein: In a case where the size of the encoded application layer measurement report message is larger than the maximum supported size of a packet data convergence protocol (PDCP) service data unit (SDU) of the terminal and RRC message segmentation is enabled according to configuration information, the application layer measurement report message is received in segments, and The application layer measurement report message is received based on signaling radio bearer 4 (SRB4).

7. The method according to claim 5, wherein: The multiple application layer measurement report entries are included in the application layer measurement report message in the order of generation.

8. The method according to claim 5, wherein: The application layer measurement report message includes timestamp information, which indicates at least one of the following for each application layer measurement configuration ID: The time when the access stratum (AS) layer of the terminal generates an application layer measurement report entry; The time at which the AS layer receives information to be included in an application layer measurement report entry from the application layer of the terminal; The time at which the AS layer receives information to be included in the application layer measurement report container information of the application layer measurement report entry from the application layer; the time at which the AS layer receives from the application layer information to be included in the application layer measurement session state information of the application layer measurement report entry; and The time when the AS layer receives information from the application layer to be included in the radio access network (RAN) visible application layer measurement information of the application layer measurement report entry.

9. A terminal in a wireless communication system, the terminal comprising: Transceiver; as well as The controller is configured as: receiving, via the transceiver, a radio resource control (RRC) message including configuration information regarding application layer measurements from a base station, For each application layer measurement configuration identifier ID, an application layer measurement report item in the application layer measurement report message is set based on the configuration information, and Sending an application layer measurement report message to a base station via a transceiver, The application layer measurement report message includes multiple application layer measurement configuration IDs and multiple application layer measurement report items associated with the multiple application layer measurement configuration IDs.

10. The terminal according to claim 9, wherein: The controller is also configured to: Initiating an uplink (UL) message segmentation transfer procedure when the size of the encoded application layer measurement report message is larger than the maximum supported size of a packet data convergence protocol (PDCP) service data unit (SDU) and RRC message segmentation is enabled according to configuration information, and The application layer measurement report message is sent based on signaling radio bearer 4 (SRB4).

11. The terminal according to claim 9, wherein: The multiple application layer measurement report entries are included in the application layer measurement report message in the order of generation.

12. The terminal according to claim 9, wherein: The application layer measurement report message includes timestamp information, which indicates at least one of the following for each application layer measurement configuration ID: The time when the access stratum (AS) layer of the terminal generates an application layer measurement report entry; The time at which the AS layer receives information to be included in an application layer measurement report entry from the application layer of the terminal; The time at which the AS layer receives information to be included in the application layer measurement report container information of the application layer measurement report entry from the application layer; the time at which the AS layer receives from the application layer information to be included in the application layer measurement session state information of the application layer measurement report entry; and The time when the AS layer receives information from the application layer to be included in the Radio Access Network (RAN) visible application layer measurement information of the application layer measurement report entry.

13. A base station in a wireless communication system, the base station comprising: Transceiver; as well as The controller is configured as: sending a radio resource control (RRC) message including configuration information about application layer measurement to the terminal via the transceiver, and receiving, via the transceiver, an application layer measurement report message from the terminal, wherein for each application layer measurement configuration identifier (ID), the application layer measurement report message includes an application layer measurement report item set according to the configuration information, The application layer measurement report message includes multiple application layer measurement configuration IDs and multiple application layer measurement report items associated with the multiple application layer measurement configuration IDs.

14. The base station according to claim 13, wherein: In a case where the size of the encoded application layer measurement report message is larger than the maximum supported size of a packet data convergence protocol (PDCP) service data unit (SDU) of the terminal and RRC message segmentation is enabled according to configuration information, the application layer measurement report message is received in segments, wherein the application layer measurement report message is received based on signaling radio bearer 4 (SRB4), and The multiple application layer measurement report entries are included in the application layer measurement report message in the order of generation.

15. The base station according to claim 13, wherein: The application layer measurement report message includes timestamp information, which indicates at least one of the following for each application layer measurement configuration ID: The time when the access stratum (AS) layer of the terminal generates an application layer measurement report entry; The time at which the AS layer receives information to be included in an application layer measurement report entry from the application layer of the terminal; The time at which the AS layer receives information to be included in the application layer measurement report container information of the application layer measurement report entry from the application layer; the time at which the AS layer receives from the application layer information to be included in the application layer measurement session state information of the application layer measurement report entry; and The time when the AS layer receives information from the application layer to be included in the radio access network (RAN) visible application layer measurement information of the application layer measurement report entry.

Images