Method and apparatus for handling quality of experience report and configuration when secondary cell group is released or deactivated in next generation mobile communication system

Abstract

A method and apparatus for handling quality of experience reporting and configuration when a secondary cell group is released or deactivated in a next generation mobile communication system are provided. A method of a UE in a wireless communication system includes: receiving at least one piece of application layer measurement configuration information included in first radio resource control (RRC) reconfiguration information for MCG or second RRC reconfiguration information for SCG; sending a report message for an application layer measurement report based on the at least one piece of application layer measurement configuration information; and receiving a second RRC reconfiguration message for releasing the SCG; and for first application layer measurement configuration information included in second RRC reconfiguration information for SCG, informing an upper layer of release of the first application layer measurement configuration information and discarding a first application layer measurement report which is not completely submitted to a lower layer for transmission and is associated with the first application layer measurement configuration information.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority under USC §119 to Korean Patent Application No. 10-2023-0089107 filed in the Korean Intellectual Property Office on July 10, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure generally relates to a mobile communication system terminal and a base station, and more particularly to a method and apparatus for processing quality of experience (QoE) when a terminal releases or deactivates a secondary cell group (SCG) in a mobile communication system. Background Art

[0004] The fifth generation (5G) mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and can be implemented not only in frequency bands below 6 gigahertz (GHz), such as 3.5 GHz, but also in frequency bands above 6 GHz, called millimeter wave (mmWave) bands, including 28 GHz and 39 GHz. In addition, the sixth generation (6G) mobile communication technology, called a super 5G system, has been considered to be implemented in terahertz (THz) bands such as 95 GHz to 3 THz bands, to achieve a transmission rate fifty times that of 5G mobile communication technology and an ultra-low latency of one tenth of 5G mobile communication technology.

[0005] Since the development of 5G mobile communication technology began, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC) and massive machine type communications (mMTC), standardization has been ongoing on the following items: beamforming and massive multiple-input multiple-output (MIMO) for mitigating radio wave path loss and increasing radio wave transmission distance in mmWave; dynamic operation of supporting parameter sets (e.g., operating multiple subcarrier spacings) to efficiently utilize mmWave resources and time slot formats; initial access technology for supporting multi-beam transmission and broadband; definition and operation of bandwidth parts (BWP); new channel coding methods such as low-density parity-check (LDPC) codes for large-scale data transmission and polarization codes for highly reliable transmission of control information; layer 2 (L2) preprocessing; and network slicing for providing dedicated networks dedicated to specific services.

[0006] In view of discussions on improvements and performance enhancements of initial 5G mobile communication technologies for services to be supported by the 5G mobile communication technologies, physical layer standardization has been ongoing regarding technologies such as: vehicle-to-everything (V2X) for assisting autonomous vehicles in making driving decisions based on information about the location and status of the vehicle transmitted by the vehicle and for enhancing user convenience; unlicensed new radio (NR-U) for the purpose of making system operations compliant with various regulatory-related requirements in unlicensed bands; NR user equipment (UE) power saving; non-terrestrial network (NTN) for UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0007] Standardization is also being conducted on air interface architecture / protocols for technologies such as: Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries; Integrated Access and Backhaul (IAB) for providing nodes for network service area extension by supporting wireless backhaul links and access links in an integrated manner; Mobility enhancements including conditional handover and dual active protocol stack (DAPS) handover; and two-step random access (2-step RACH) for NR to simplify the random access procedure. Standardization is also being conducted on system architecture / services for the following items: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies; and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0008] As 5G mobile communication systems are commercialized, the number of connected devices, which has been increasing exponentially, will be connected to the communication network, and therefore, it is expected that enhanced functions and performance of the 5G mobile communication systems and integrated operations of the connected devices will be necessary. To this end, new research is planned in the following areas: extended reality (XR) for efficiently supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communication.

[0009] This development of 5G mobile communication systems will serve as the basis for developing not only new waveforms for providing coverage in the terahertz band of 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 the coverage of THz band signals, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM) and reconfigurable smart surfaces (RIS), 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 from the design stage by utilizing satellites and AI and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high performance communication and computing resources. Summary of the invention

[0010] The present disclosure has been made to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below.

[0011] Therefore, one aspect of the present disclosure is to provide an improved QoE measurement and reporting method in the case where the SCG is released or deactivated.

[0012] According to one aspect of the present disclosure, a method performed by a UE in a wireless communication system is provided. The method includes: receiving at least one application layer measurement configuration information included in a first radio resource control (RRC) reconfiguration information for an SCG or included in a second RRC reconfiguration information for an SCG; based on the at least one application layer measurement configuration information, sending a report message for an application layer measurement report; and receiving a second RRC reconfiguration message for releasing the SCG; for the first application layer measurement configuration information included in the second RRC reconfiguration message for the SCG, informing the upper layer of the release of the first application layer measurement configuration information and discarding the first application layer measurement report associated with the first application layer measurement configuration information that has not been fully submitted to the lower layer for transmission.

[0013] According to one aspect of the present disclosure, a method performed by a first base station associated with an MCG in a wireless communication system is provided. The method includes: sending at least one application layer measurement configuration information included in a first radio resource control (RRC) reconfiguration information for an MCG or included in a second RRC reconfiguration information for a secondary cell group (SCG) to a user equipment; and sending a second RRC reconfiguration message for releasing the SCG to the UE, wherein, for the first application layer measurement configuration information included in the second RRC reconfiguration information for the SCG, the release of the first application layer measurement configuration information is notified to the upper layer and the first application layer measurement report associated with the first application layer measurement configuration information that has not been fully submitted to the lower layer for transmission is discarded.

[0014] According to one aspect of the present disclosure, a UE in a wireless communication system is provided. The UE includes: a transceiver; and a controller, the controller being configured to: receive at least one application layer measurement configuration information included in a first radio resource control (RRC) reconfiguration information for an MCG or included in a second RRC reconfiguration information for an SCG; based on the at least one application layer measurement configuration information, send a report message for an application layer measurement report, and receive a second RRC reconfiguration message for releasing the SCG; for the first application layer measurement configuration information included in the second RRC reconfiguration information for the SCG, inform the upper layer of the release of the first application layer measurement configuration information and discard the first application layer measurement report associated with the first application layer measurement configuration information that has not been fully submitted to the lower layer for transmission.

[0015] According to one aspect of the present disclosure, a base station associated with a master cell group (MCG) in a wireless communication system is provided. The base station includes: a transceiver; and a controller, the controller being configured to: send at least one application layer measurement configuration information included in a first radio resource control (RRC) reconfiguration information for the MCG or included in a second RRC reconfiguration information for a secondary cell group (SCG) to a user equipment, and send a second RRC reconfiguration message for releasing the SCG to the UE, wherein, for the first application layer measurement configuration information included in the second RRC reconfiguration information for the SCG, the release of the first application layer measurement configuration information is notified to the upper layer and the first application layer measurement report associated with the first application layer measurement configuration information that has not been fully submitted to the lower layer for transmission is discarded. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] Figure 1The structure of a long term evolution (LTE) system to which the present disclosure is applicable is shown;

[0018] Figure 2 The structure of the wireless protocol in the LTE system to which the present disclosure is applicable is shown;

[0019] Figure 3 The structure of the next generation mobile communication system to which the present disclosure is applicable is shown;

[0020] Figure 4 The structure of the wireless protocol of the next generation mobile communication system to which the present disclosure is applicable is shown;

[0021] Figure 5 A process for configuring and / or reporting signaling-based QoE measurements according to an embodiment is shown;

[0022] Figure 6 A process for configuring and / or reporting management-based QoE measurements according to an embodiment is shown;

[0023] Figure 7 A method for configuring dual connectivity (DC) in a terminal according to an embodiment is shown;

[0024] Fig. 8A A method for a terminal configured with DC to report QoE measurement results according to an embodiment is shown;

[0025] Figure 8B A method for a terminal configured with DC to report QoE measurement results according to an embodiment is shown;

[0026] Fig. 9A A method for a terminal configured with DC to report QoE measurement results according to an embodiment is shown;

[0027] Fig. 9B A method for a terminal configured with DC to report QoE measurement results according to an embodiment is shown;

[0028] Fig.10 A method for processing QoE configuration information and QoE measurement results related thereto when a terminal configured with a DC releases an SCG according to an embodiment is shown;

[0029] Fig.11 A method for processing QoE configuration information and QoE measurement results related thereto when a terminal configured with DC deactivates SCG according to an embodiment is shown;

[0030] Fig.12 shows an internal structure of a terminal according to an embodiment; and

[0031] Fig.13The structure of an NR base station according to an embodiment is shown. DETAILED DESCRIPTION

[0032] The following description is provided with reference to the accompanying drawings to assist in a comprehensive understanding of the embodiments of the present disclosure.

[0033] Therefore, those skilled in the art will recognize that many changes and modifications to the embodiments described herein may be made without departing from the scope and spirit of the present disclosure.For the sake of clarity and conciseness, descriptions of known functions and constructions will be omitted.

[0034] In the following description, for the sake of convenience, terms for identifying access nodes, for network entities, for messages, for interfaces between network entities, for various identification information, etc. are illustratively used. Therefore, the present disclosure is not limited to the terms used below, and other terms about subjects with equivalent technical meanings may be used.

[0035] Here, the elements according to the specific embodiments of the present application can be expressed in singular or plural. However, the singular form or plural form is selected to be suitable for the situation of the present application for the convenience of description, and the present disclosure is not limited to the elements expressed in singular or plural. Therefore, the elements expressed in plural form also include a single element, or the elements expressed in singular form also include multiple elements.

[0036] For ease of description, the present disclosure will be described using terms and names defined in the 3rd Generation Partnership Project (3GPP) LTE standard. However, the present disclosure is not limited by these terms and names and can be applied to systems conforming to other standards in the same manner. In the present disclosure, for ease of description, the term eNB may be used interchangeably with the term gNB. That is, a base station described as an eNB may indicate a gNB.

[0037] Figure 1 The structure of the LTE system to which the present disclosure is applicable is shown.

[0038] Reference Figure 1 As shown in the figure, the wireless access network of the LTE system includes next-generation base stations (e.g., evolved Node Bs (ENBs), Node Bs, or base stations) 105, 110, 115, and 120, a mobility management entity (MME) 125, and a serving gateway (S-GW) 130. User equipment 135 (hereinafter, referred to as UE or terminal) can access external networks through the ENBs 105 to 120 and the S-GW 130.

[0039] exist Figure 1In the LTE system, ENBs 105 to 120 correspond to conventional Node Bs of a Universal Mobile Telecommunications Service (UTMS) system. ENBs are connected to UEs 1-35 through wireless channels and perform a more complex role than conventional Node Bs. In an LTE system, since all user services including real-time services such as Voice over Internet Protocol (VoIP) are served through a shared channel, a device for collecting and scheduling state information about a buffer state, an available transmission power state, and a channel state of a UE is required, and ENBs 105 to 120 serve as such a device. One ENB can control multiple cells. For example, to achieve a transmission rate of 100 Mbps, an LTE system can use Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology within a bandwidth of 20 MHz. An Adaptive Modulation and Coding (AMC) scheme that determines a modulation scheme and a channel coding rate is applied depending on the channel state of the UE. S-GW 130 is a device for providing data bearers, and generates or discards data bearers under the control of MME 125. MME performs not only a function of managing the mobility of UEs but also various control functions, and can be connected to multiple ENBs.

[0040] Figure 2 The structure of a wireless protocol in an LTE system to which the present disclosure is applicable is shown.

[0041] Reference Figure 2 In the wireless protocol of the LTE system, each of the UE and the ENB includes a packet data convergence protocol (PDCP) 205 and 240, a radio link control (RLC) 210 and 235, and a medium access control (MAC) 215 and 230. The PDCP 205 and 240 perform an operation of compressing / reconstructing an IP header. The main functions of the PDCP are described below.

[0042] Robust header compression and decompression

[0043] User data transmission

[0044] In-sequence delivery of upper layer packet data units (PDUs) during PDCP re-establishment procedure for Radio Link Control Acknowledged Mode (RLC AM)

[0045] For resequence of split bearers in DC (supported only for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception

[0046] Duplicate detection of lower layer SDUs during PDCP re-establishment for RLC AM

[0047] Retransmission of PDCP SDUs at handover and, for split bearers in DC, retransmission of PDCP PDUs during PDCP data recovery procedure for RLC AM

[0048] Encryption and Decryption

[0049] Timer based SDU discard in uplink.

[0050] The RLC 210 and 235 reconfigures the PDCP PDU to an appropriate size and performs an Automatic Repeat Request (ARQ) operation. The main functions of the RLC are summarized below.

[0051] Data transmission of upper layer PDU

[0052] Error correction via ARQ for AM data transmission

[0053] Concatenation, segmentation, and reassembly of RLC SDUs for Unacknowledged Mode (UM) and AM data transfer

[0054] Re-segmentation of RLC data PDUs for AM data transmission

[0055] Reordering of RLC data PDUs for UM and AM data transfer

[0056] Duplicate detection for UM and AM data transmission

[0057] Protocol error detection for AM data transmission

[0058] RLC SDU discard for UM and AM data transmission

[0059] RLC Reconstruction

[0060] MAC 215 and 230 are connected to various RLC layer devices configured in one UE, and perform operations for multiplexing and demultiplexing RLC PDUs to and from MAC PDUs. Main functions of MAC are summarized below.

[0061] Mapping between logical channels and transport channels

[0062] Multiplexing and demultiplexing of MAC SDUs belonging to one or different logical channels into and from transport blocks (TBs) delivered to the physical layer on transport channels

[0063] Dispatch Information Report

[0064] Error correction via Hybrid ARQ (HARQ)

[0065] Priority handling between logical channels of a UE

[0066] Prioritize UEs with dynamic scheduling

[0067] Multimedia Broadcast Multicast Service (MBMS) Identification

[0068] Transmission format selection

[0069] filling

[0070] The PHY layers 220 and 225 perform operations for channel coding and modulating higher layer data to generate OFDM symbols and transmitting the OFDM symbols through a wireless channel or demodulating and channel decoding OFDM symbols received through a wireless channel and delivering the demodulated and channel-decoded OFDM symbols to a higher layer.

[0071] Figure 3 The structure of the next generation mobile communication system to which the present disclosure is applicable is shown.

[0072] Reference Figure 3 As shown in the figure, the wireless access network of the next generation mobile communication system (hereinafter referred to as NR or 2G) includes a next generation base station 310 (new wireless node B, hereinafter referred to as gNB or NR NB) and a new wireless core network (NRCN) 305. The user terminal 315 (new wireless user equipment, hereinafter referred to as NR UE or terminal) accesses the external network through the NR gNB 310 and the NRCN 305.

[0073] exist Figure 3 In the present invention, NR gNB 310 corresponds to an evolved Node B (eNB) in a conventional LTE system. NR gNB can be connected to NR UE 315 through a wireless channel and can provide better service than a conventional Node B. Since all user services are served through shared channels in the next generation mobile communication system, a device is required for collecting and scheduling status information of the buffer status, the available transmission power status, and the channel status of the UE, and NR NB 310 is used as this device. One NRgNB typically controls multiple cells. NR gNB can have a bandwidth wider than the conventional maximum bandwidth in order to achieve ultra-high-speed data transmission compared to the current LTE, OFDM can be applied through wireless access technology, and beamforming technology can be further applied. In addition, an AMC scheme that determines the modulation scheme and channel coding rate is applied according to the channel status of the UE.

[0074] NR CN 305 performs the functions of supporting mobility, configuring bearers, and configuring QoS. NR CN is a device for managing the mobility of UE and various control functions and is connected to multiple base stations. The next generation mobile communication system can be linked to the conventional LTE system, and NR CN is connected to MME 325 through a network interface. MME is connected to eNB 330 which is a conventional base station.

[0075] Figure 4 The structure of a wireless protocol of a next-generation mobile communication system to which the present disclosure is applicable is shown.

[0076] Reference Figure 4 In the wireless protocol of the next generation mobile communication system, each of the UE and the NR base station includes NR Service Data Association Protocol (SDAP) 401 and 445, NR PDCP 405 and 440, NR RLC 410 and 435, and NR MAC 415 and 430.

[0077] The main functions of NR SDAP 401 and 445 may include some of the following functions.

[0078] User plane data transmission

[0079] Mapping uplink and downlink QoS flows to data bearers

[0080] QoS flow IDs that mark uplink and downlink packets, and

[0081] Mapping of reflective QoS flows to data bearers for uplink SDAP PDUs

[0082] Regarding the SDAP layer device, the UE may receive configuration regarding whether to use the header of the SDAP layer device or the function of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel through an RRC message. When the SDAP header is configured, the 1-bit indicator of NAS reflective QoS and the 1-bit indicator of AS reflective QoS of the SDAP header may indicate that the UE updates or reconfigures information about the mapping of QoS flows and data bearers in the uplink and downlink. The SDAP header may include QoS flow ID information indicating QoS. QoS information may be used as data processing priority or scheduling information to support seamless services.

[0083] The main functions of NR PDCP 405 and 440 may include some of the following functions.

[0084] Robust header compression and decompression

[0085] User data transmission

[0086] In-order delivery of upper layer PDUs

[0087] Out-of-order delivery of upper layer PDUs

[0088] Reordering of received PDCP PDUs

[0089] Duplicate detection of lower layer SDUs

[0090] Retransmission of PDCP SDU

[0091] Encryption and Decryption

[0092] Timer based SDU discard in uplink.

[0093] The reordering function of the NR PDCP device is a function of sequentially reordering the PDCP PDUs received by the lower layer based on the PDCP sequence number, and may include a function of sequentially delivering the reordered data to a higher layer, a function of directly delivering the reordered data regardless of the order, a function of recording the PDCP PDUs lost due to reordering, a function of reporting the status of the lost PDCP PDUs to the transmitting side, and a function of making a request for retransmission of the lost PDCP PDUs.

[0094] The main functions of NR RLC 410 and 435 may include some of the following functions.

[0095] Data transmission of upper layer PDU

[0096] In-order delivery of upper layer PDUs

[0097] Out-of-order delivery of upper layer PDUs

[0098] Error correction via ARQ

[0099] Concatenation, segmentation, and reassembly of RLC SDUs

[0100] Re-segmentation of RLC data PDUs

[0101] Reordering of RLC data PDUs

[0102] Duplicate Detection

[0103] Protocol error detection

[0104] RLC SDU discarded

[0105] RLC Reconstruction

[0106] The in-sequence delivery of the NR RLC device is a function of sequentially delivering the RLC PDU received from the lower layer to the higher layer, and may include: when an original RLC SDU is divided into multiple RLC SDUs and then received, the function of reassembling and delivering the RLC SDU, the function of reordering the received RLC PDU based on the RLC or PDCP sequence number, the function of recording the RLC PDU lost due to reordering, the function of reporting the status of the lost RLC PDU to the transmitting side, and the function of making a request for retransmission of the lost RLC PDU; when there is a lost RLC SDU, the function of sequentially delivering only the RLC SDU before the lost RLC SDU to the higher layer; or if a predetermined timer expires even when there is a lost RLC SDU, the function of sequentially delivering to the higher layer all RLC SDUs received before the timer starts; or if the predetermined timer expires even when there is a lost RLC SDU, the function of sequentially delivering to the higher layer all RLC SDUs received until that point in time. The NR RLC device may process the RLC PDUs sequentially in the order in which they are received (according to the order of arrival regardless of the sequence number or sequence number) and may deliver the RLC PDUs to the PDCP device regardless of their order (out-of-order delivery). In the case of segmentation, the NR RLC device may receive segments stored in a buffer or to be received in the future, reconfigure the segments into one RLC PDU, process the RLC PDU, and then deliver it to the PDCP device. The NR RLC layer may not include a cascading function, and the function may be performed by the NR MAC layer, or may be replaced by a multiplexing function of the NR MAC layer.

[0107] The out-of-sequence delivery of the NR RLC device is a function of directly delivering the RLC SDU received from the lower layer to the higher layer regardless of the order of the RLC SDU, and may include a function of reassembling and delivering the RLC PDU when one original RLC SDU is divided into multiple RLC SDUs and then received, as well as a function of storing the RLC SN or PDCP SN of the received RLC PDU, reordering the RLC PDU, and recording the lost RLC PDU.

[0108] The NR MAC 415 and 430 may be connected to a plurality of NR RLC layer devices configured in one UE, and the main functions of the NR MAC may include some of the following functions:

[0109] Mapping between logical channels and transport channels

[0110] MAC SDU multiplexing and demultiplexing

[0111] Dispatch Information Report

[0112] Error correction through HARQ

[0113] Priority handling between logical channels of a UE

[0114] Prioritize UEs with dynamic scheduling

[0115] MBMS Service Identification

[0116] Transmission format selection

[0117] filling

[0118] The NR PHY layers 420 and 425 perform operations for channel coding and modulating higher layer data to generate OFDM symbols and transmitting the OFDM symbols through a wireless channel or demodulating and channel decoding OFDM symbols received through a wireless channel and delivering the demodulated and channel-decoded OFDM symbols to a higher layer.

[0119] Figure 5 A process for configuring and / or reporting signaling-based QoE measurements according to an embodiment is shown.

[0120] Reference Figure 5 In step 510, the UE access stratum (AS) 505 may embed information indicating which QoE measurements are supported through application layer measurements in a UE capability information message (eg, UECapabilityInformation) and send it to the base station 515 (510).

[0121] The UE capability information message may also embed capability information on whether the UE AS 505 can segment an RRC message (eg, MeasurementReportAppLayer) reporting QoE measurement results and send it to the base station 515. For example, the UE capability information message may embed parameters shown in Table 1 below.

[0122] Table 1

[0123]

[0124] The UE capability information message may embed whether the UE supports QoE measurement through application layer measurement for MBMS, extended reality (XR), etc. In this case, the UE capability information message may embed whether separate QoE measurement is supported for multimedia broadcast services, multimedia multicast services, etc., or whether QoE measurement is supported together without distinguishing between multimedia broadcast services and multimedia multicast services.

[0125] Whether QoE measurement is supported for the multimedia broadcast service according to the RRC state may be included in the message. For example, the UE may support QoE measurement for the multimedia broadcast service only in the RRC connected mode (RRC_CONNECTED), or may support QoE measurement for the multimedia broadcast service only in the RRC idle mode (RRC_IDLE) and the RRC inactive mode (RRC_INACTIVE). Alternatively, the UE may support QoE measurement for the multimedia broadcast service regardless of the RRC state.

[0126] In step 530 , operations administration and maintenance (OAM) 520 may provide QoE measurement configuration information to core network (CN) 525 .

[0127] In step 535 , the CN 525 may activate the QoE measurement by sending the QoE measurement configuration information received in step 530 to the base station 515 .

[0128] In step 540 , the base station 515 may embed the QoE measurement configuration information received from the CN in step 535 in a predetermined RRC message (eg, RRCReconfiguration or RRCResume) and send it to the UE AS 515 .

[0129] The QoE measurement configuration information (AppLayerMeasConfig) embedded in the predetermined RRC message may include the parameters shown in Table 2 and Table 3 below.

[0130] Table 2

[0131]

[0132] Table 3

[0133]

[0134]

[0135] AppLayerMeasConfig may also include QoE measurement configuration information for multimedia broadcast services. For example, a multimedia broadcast service may be indicated in the serviceType included in AppLayerMeasConfig, or a separate indicator may be inserted to include QoE measurement configuration information for multimedia broadcast services. Alternatively, it may include an indicator (e.g., mbs-SessionList) as to whether QoE is measured for each MBS session.

[0136] For multimedia broadcast services, the QoE measurement configuration information may be applied to all RRC states (RRC_IDLE, RRC_INACTIVE, RRC_CONNECTED) of the UE, or may be applied to at least one RRC state. That is, AppLayerMeasConfig may indicate which RRC states (any combination of RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED) the QoE measurement configuration information for multimedia broadcast services is applied to.

[0137] Alternatively, a new timer value may be included to indicate a QoE measurement execution period for a multimedia broadcast service. That is, when a new timer value is included, the UE may start or restart a new timer with a new timer value received when receiving AppLayerMeasConfig from a base station. Alternatively, the UE may start or restart a new timer with a new timer value received when transitioning to RRC idle mode or RRC deactivation mode. When the started new timer expires, the UE may release the QoE measurement configuration information for the multimedia broadcast service. The UE AS that has received AppLayerMeasConfig may perform the process described in Table 4 below.

[0138] Table 4

[0139]

[0140]

[0141]

[0142] In step 550, the UE AS (505) having received the AppLayerMeasConfig may deliver the QoE measurement configuration information to the UE application layer (UE APP) 545 through an AT command.

[0143] In step 555, the UE APP 545 may perform QoE measurement according to the QoE measurement configuration information received in step 550, and report the measurement result to the UE AS 505 through an AT command according to the configuration information.

[0144] In step 560, UE AS 505 may report the measurement result to base station 515 through a predetermined RRC message (eg, MeasReportAppLayer) based on the information received in step 555. SRB4 may be used to report the QoE measurement result. The predetermined RRC message may include parameters as shown in Table 5 below.

[0145] Table 5

[0146]

[0147] The UE AS 505 may send a predetermined RRC message including a QoE measurement result report to the base station 515 based on the process shown in Table 6 below.

[0148] Table 6

[0149]

[0150]

[0151]

[0152] In step 570 , the base station 515 may deliver the measurement result report received in step 565 to the configured final destination (trace collection entity (TCE) or measurement collection entity (MCE)) 565 .

[0153] Figure 6 A process for configuring and / or reporting management-based QoE measurements according to an embodiment is shown.

[0154] The management-based QoE configuration and reporting process can be similar to the one above. Figure 5 ( Figure 5 ) is substantially similar to the signaling-based QoE configuration and / or reporting process described in . Therefore, in this specification, only the differences in the management-based method are described below, and other processes and descriptions can refer to the relevant Figure 5 Description.

[0155] In the management-based approach, in step 615, the OAM 605 may activate the QoE measurement by directly sending the QoE measurement configuration to the base station 610 without going through the CN (615).

[0156] The base station 610 that has received the QoE measurement configuration searches for a single or multiple UEs that meet various conditions (e.g., area range, application layer capability, service type). Similarly, in step 620, the base station 610 can deliver the QoE measurement configuration to each UE through an RRC message (e.g., RRCReconfiguration or RRCResume) (620).

[0157] Other procedures and message formats may be considered similar to those described in Figure 5 The description of (signaling based method) is the same.

[0158] Figure 7 A method for configuring DC in a UE according to an embodiment is shown.

[0159] More specifically, Figure 7 An overall flow chart is shown in which NE-DC or NR-DC is configured for a UE.

[0160] Reference Figure 7 In step 710, the user equipment (UE) 701 may establish an RRC connection with the primary cell (PCell) or special cell (SpCell) of the primary node of the source MN 702, and may be in RRC connection mode (RRC_CONNECTED). The PCell of the source MN is connected to the 5G CN, so the UE can receive services from the 5G CN.

[0161] In step 715, the source MN 702 may initiate a secondary node (SN) adding procedure to add the SN 703. For example, in step 715, the source MN may send an SN adding request message (eg, SgNB adding request or SN adding request) to the SN 703.

[0162] In step 720, the SN 703 may send an SN add request confirm message (e.g., SgNB add request confirm or SN add request confirm) to the MN 702 in response to step 715. The SN add request confirm message may be embedded in an RRC connection reconfiguration message (RRCReconfiguration in NR or RRCConnectionReconfiguration in LTE).

[0163] In step 725, MN 702 may send the RRC connection reconfiguration message received in step 720 to UE 701 through signaling radio bearer 1 (SRB1).

[0164] In step 730, UE 701 may apply the RRC connection reconfiguration message received in step 720 and send an RRC connection reconfiguration complete message (e.g., RRCReconfigurationComplete in NR or RRCConnectionReconfigurationComplete in LTE) to MN 702 through SRB1. The RRC connection reconfiguration complete message may be embedded in an SN connection reconfiguration complete message (e.g., SgNB reconfiguration complete or SN reconfiguration complete).

[0165] In step 731, MN 702 may deliver an SN connection reconfiguration complete message to SN 703 (731).

[0166] In step 735, the RRC layer device of UE 701 may initiate a random access procedure with the primary and secondary cells (PSCell) of SN 703. For reference, the order of steps 730, 731, and 735 may be changed according to the UE implementation. For example, UE 701 may send an RRC connection reconfiguration complete message to MN 702 after initiating or successfully completing the random access procedure for the PSCell.

[0167] In step 740, UE 701 may operate in a configuration where NR-DC (PSCell is an NR cell) or NE-DC (PSCell is an LTE cell).

[0168] Fig. 8A and Figure 8B A method for a UE configured with DC to report QoE measurement results according to an embodiment is shown.

[0169] More specifically, Fig. 8A and Figure 8B A process is shown in which a UE configured with NR-DC or NE-DC reports a QoE measurement result to a base station based on a QoE measurement configuration.

[0170] Reference Fig. 8A and Figure 8B , UE AS 802 and UE application layer (UE APP) 803 may be collectively referred to as UE 801. Base station 804 may be referred to as MN.

[0171] UE 801 is not limited to a MN in NE-DC or NR-DC, and may receive QoE configuration information from the MN and / or SN, and may include information that may report QoE measurement results to the MN and / or SN.

[0172] In step 810, the user equipment (UE) 801 may establish an RRC connection with the base station 804 to be in an RRC connected mode (RRC_CONNECTED) (810).

[0173] In step 815, the UE AS 802 may send a UE capability information message (eg, UECapabilityInformation) to the base station 804. The information embedded in the UE capability information message may be the same as in the above-mentioned embodiments.

[0174] The UE capability information message may include information indicating whether NE-DC or NR-DC is supported. The UE capability information message is not limited to a MN in NE-DC or NR-DC, and may receive QoE configuration information from the MN and / or SN, and may include information that may report QoE measurement results to the MN and / or SN.

[0175] In step 820, UE 801 may be configured for NR-DC or NE-DC. UE 801 in NR-DC or NE-DC may send and receive data from MN 804 and SN 805. The flowchart for configuring NR-DC or NE-DC for UE 801 may follow the above-mentioned embodiment.

[0176] In step 825, OAM 807 may provide QoE measurement configuration information to MN 804 to activate QoE measurement. The QoE measurement configuration information may include at least one of a service type (serviceType) for which QoE measurement is to be performed, a management collection entity (MCE) IP address, QoE configuration information (measConfigAppLayerContainer), and a QoE reference. The above information may be in the form of one or more items.

[0177] In step 830 , the MN 804 may deliver at least one of the QoE measurement configuration information received from the OAM 807 to the SN 805 .

[0178] As disclosed herein, the MN 804 delivers the measConfigAppLayerId mapped to each measReportAppLayerContainer to the SN 805. This is to prevent the same measConfigAppLayerId from being assigned to the UE AS 802 when the SN 805 receives the QoE measurement configuration from the OAM in the future. When the same measConfigAppLayerId is assigned to the UE AS 802, even if the MN 804 or the SN 805 receives a QoE report from the UE AS 802, it cannot be determined to which QoE reference or MCE IP address the measConfigAppLayerId is mapped, because the message may not be properly delivered to the final destination TCE or MCE 808. Therefore, the MN 804 may deliver at least one of the serviceType, MCEIP address, QoE reference, and measConfigAppLayerContainer mapped to each measConfigAppLayerId together with the measConfigAppLayerId to the SN 805.

[0179] MN 804 may inform SN 805 of an explicit information element or inform UE AS 802 to report the QoE report to MN 804 without a separate indicator. Alternatively, for each measConfigAppLayerId indicating that the reporting branch is changed from MN 804 to SN 805 (or from SN 805 to MN 804), the UE may send MeasReportAppLayer to MN 804 and SN805 accordingly.

[0180] As an example, when the UE is configured to report a specific measConfigAppLayerId to the MN 804, the UE may send the QoE measurement result for the measConfigAppLayerId configured to be reported to the MN to the MN 804. When other specific MeasConfigAppLayerId is configured to be reported to the SN 805, the UE may send the QoE measurement result for the measConfigAppLayerId configured to be reported to the SN to the SN 805. The MN 804 may configure the UE to report the entire QoE report (i.e., MeasReportAppLayer) to the SN 805, so the MN 804 may need to deliver the above information to the SN 805.

[0181] In step 835, MN 804 may embed QoE measurement configuration information (AppLayerMeasConfig) in a predetermined RRC message (eg, RRCReconfiguration or RRCResume) through SRB1 and send it to UE AS 802. UE operations for AppLayerMeasConfig configuration and reception of the configuration may be the same as in the above embodiments.

[0182] In step 840 , the UE AS 802 may deliver all or some of the AppLayerMeasConfig received through the AT command to the UE APP 803 .

[0183] In step 845, UE APP 803 may perform QoE measurement according to the configuration information received in step 840, and report the QoE measurement result to UE AS 802 through an AT command according to the configuration information.

[0184] In step 850, UE AS 802 may report the QoE measurement result to MN 804 through a predetermined RRC message (e.g., MeasReportAppLayer) based on the information received in step 845. UE AS 802 may report the QoE measurement result using signaling radio bearer 4 (SRB4). The information included in the predetermined RRC message and the process for sending the information may be the same as in the above-mentioned embodiment.

[0185] In step 855 , the MN 804 may deliver the QoE measurement result information received in step 850 to the final destination TCE or MCE 808 .

[0186] In step 860 , MN 804 may send an RRC message to be configured to instruct UE AS 802 to report MeasReportAppLayer to SN 805 .

[0187] For example, when congestion occurs due to a large load (eg, when many UEs need to be served), the MN 804 may send a predetermined RRC message to the UE AS 802 to instruct the UE AS 802 to report MeasReportAppLayer to the SN 805 .

[0188] For example, the predetermined RRC message may refer to an RRC connection reconfiguration message (RRCReconfiguration message) or an RRC connection resumption message (RRCResume message).

[0189] By instructing the UE AS 802 to change the reporting branch from the MN 804 to the SN 805 for each measConfigAppLayerId, the UE AS 802 may accordingly send MeasReportAppLayer to the MN 804 and the SN 805. That is, in the case where the UE is configured to report a specific measConfigAppLayerId to the MN 804, the UE may send the QoE measurement result for the measConfigAppLayerId configured to be reported to the MN to the MN 804. In the case where the UE is configured to report another specific measConfigAppLayerId to the SN 805, the UE may send the QoE measurement result for the measConfigAppLayerId configured to be reported to the SN to the SN 805.

[0190] Before step 860, MN 804 may inform SN 905 that it configures UE AS 802 to report MeasReportAppLayer to SN 805. Therefore, SN 805 may inform MN 804 whether to confirm.

[0191] Alternatively, step 860 may be performed in step 835. For example, MN 804 may configure UE AS 802 to report to SN 805 when AppLayerMeasConfig is first configured. Alternatively, by indicating that the reporting branch is to be changed from MN 804 to SN 805 for each measConfigAppLayerId, the UE may send MeasReportAppLayer to MN 804 and SN 805 accordingly. As an example, when the UE is configured to report a specific measConfigAppLayerId to MN 804, the UE may send to MN 804 the QoE measurement results for the measConfigAppLayerId configured to be reported to the MN. When the UE is configured to report another specific MeasConfigAppLayerId to SN 805, the UE may send to SN 805 the QoE measurement results for the measConfigAppLayerId configured to be reported to the SN.

[0192] MN 804 may configure the UE to report the entire QoE report (ie, MeasReportAppLayer) to SN 805 , so MN 804 may need to deliver the above information to SN 805 .

[0193] In step 865, UE APP 803 may perform QoE measurement according to the configuration information received in step 840, and report the QoE measurement result to UE AS 802 through an AT command according to the configuration information.

[0194] In step 870, UE AS 802 may report the QoE measurement result to SN 805 through a predetermined RRC message (e.g., MeasReportAppLayer) based on the information received in step 865. A new SRBx (new signaling radio bearer x, i.e., SRB5) may be used to report the QoE measurement result. Split SRB4 or SRB3 or SRB2 or a new split SRBx may also be used.

[0195] In step 873 , the SN 805 may deliver the QoE measurement result information received in step 870 directly to the final destination (TCE or MCE) 808 .

[0196] In step 880 , the SN 805 may deliver the MeasReportAppLayer ( 875 ) received in step 870 to the MN 804 , and deliver the measurement result information received by the MN to the final destination (TCE or MCE) 808 .

[0197] A method for coordinating each node so that the measConfigAppLayerId assigned to the UE does not have the same value for all MNs and SNs or all cell groups (ie, the measConfigAppLayerId is unique in the cell group) is disclosed.

[0198] This document discloses a method in which a UE configured to report MeasReportAppLayer to a MN reports MeasReportAppLayer to a SN when congestion occurs in the MN or the SN (a method in which a UE configured to report MeasReportAppLayer to a SN reports MeasReportAppLayer to a MN), and accordingly proposes signaling procedures and necessary elements of the MN and the SN.

[0199] Fig. 9A and Fig. 9B A method for a UE configured with DC to report QoE measurement results according to an embodiment is shown.

[0200] Reference Fig. 9A and Fig. 9B , provides a process in which a UE configured with NR-DC or NE-DC reports QoE measurement results to a base station based on a QoE measurement configuration.

[0201] Both the UE AS 902 and the UE application layer (APP) 903 may be collectively referred to as a UE 901. The base station 904 may be referred to as a MN.

[0202] In step 910, UE 901 may establish an RRC connection with base station 904 to be in an RRC connected mode (RRC_CONNECTED).

[0203] In step 915, the UE AS 902 may send a UE capability information message (eg, UECapabilityInformation) to the base station 904. The information embedded in the UE capability information message may be the same as in the above-mentioned embodiments.

[0204] In step 920, the UE 901 may be configured for NR-DC or NE-DC. The UE 901 in NR-DC or NE-DC may send and receive data from the MN 904 and the SN 905. Configuring NR-DC or NE-DC for the UE 901 may follow the above-described embodiments.

[0205] In step 925, OAM 907 may provide QoE measurement configuration information to SN 905 to activate QoE measurement. The QoE measurement configuration information may include at least one of a service type (serviceType) for which QoE measurement is to be performed, a management collection entity (MCE) IP address, QoE configuration information (measConfigAppLayerContainer), and a QoE reference. For reference, the above information may be in one or more pieces.

[0206] In step 930, the SN 905 may deliver at least one of the QoE measurement configuration information received from the OAM 907 to the MN 904. The SN 905 delivers the measConfigAppLayerId mapped to each measReportAppLayerContainer to the MN 904. This is to prevent the same measConfigAppLayerId from being assigned to the UE AS 902 when the MN 904 receives the QoE measurement configuration from the OAM 907 in the future. When the same measConfigAppLayerId is assigned to the UE AS 902, even if the MN 904 or the SN 905 receives a QoE report from the UE AS 902, it cannot be determined to which QoE reference or MCE IP address the measConfigAppLayerId is mapped because it may not be properly delivered to the final destination TCE or measurement collection entity MCE 908. Therefore, the SN 905 may deliver at least one of the serviceType, the MCE IP address, the QoE reference, and the measConfigAppLayerContainer mapped to each measConfigAppLayerId to the MN 904 together with the measConfigAppLayerId.

[0207] SN 905 may inform MN 904 of an explicit information element or inform UE AS 902 to report QoE report to SN 905 without a separate indicator. Alternatively, for each measConfigAppLayerId indicating that the reporting branch is changed from SN 905 to MN 904 (or from MN 904 to SN 905), the UE may send MeasReportAppLayer to MN 904 and SN 905 accordingly.

[0208] As an example, when a specific measConfigAppLayerId is configured to be reported to the MN 904, the UE may send the QoE measurement result for the measConfigAppLayerId configured to be reported to the MN to the MN 904. When other specific MeasConfigAppLayerId is configured to be reported to the SN 905, the UE may send the QoE measurement result for the measConfigAppLayerId configured to be reported to the SN to the SN 905. The SN 905 may configure the UE to report the QoE report (i.e., MeasReportAppLayer) to the MN 904, and thus the SN 905 may need to deliver the above information to the MN 904.

[0209] In step 935, the MN 904 may embed the QoE measurement configuration information (AppLayerMeasConfig) in a predetermined RRC message (e.g., RRCReconfiguration or RRCResume) through SRB1 based on the information received from the SN and directly send it to the UE AS 902. The UE AS 902 may identify whether the SN 905 has provided the QoE measurement configuration information through a predetermined RRC message. Through the predetermined RRC message, the UE may be configured to report the QoE report (i.e., MeasReportAppLayer) to the MN 904 or the SN 905, as in the above-described embodiment.

[0210] Alternatively, without performing step 935, through step 937, the SN 905 may embed the AppLayerMeasConfig in a predetermined RRC message (e.g., RRCReconfiguration) through SRB3 and send it to the UE AS 902. Through the predetermined RRC message, the UE may be configured to report the QoE report (i.e., MeasReportAppLayer) to the MN 904 or the SN 905, as in the above-mentioned embodiment.

[0211] In step 940, the UE AS 902 may deliver to the UE APP 903 all or some of the AppLayerMeasConfig received from the MN 904 or the SN 905 through the AT command.

[0212] In step 945, UE APP 903 may perform QoE measurement according to the configuration information received in step 940, and report the QoE measurement result to UE AS 902 through an AT command according to the configuration information.

[0213] In step 950, when the UE AS is configured to report the QoE measurement result to the MN, the UE AS 902 configured to report the QoE measurement result to the MN 904 may report the measurement result to the MN 904 through a predetermined RRC message (e.g., MeasReportAppLayer) based on the information received in step 945. The UE AS 902 may report the QoE measurement result using SRB4. The information included in the predetermined RRC message and the process for sending the information may be the same as in the above-mentioned embodiment.

[0214] In step 955 , the MN 904 may deliver the measurement result information received in step 950 to the final destination (TCE or MCE) 908 .

[0215] Alternatively, in step 960 , without executing step 955 , the MN 904 may deliver the measurement result information received in step 950 to the SN 905 , and in step 965 , the SN 905 may also deliver the information directly to the final destination TCE or MCE 908 .

[0216] Alternatively, in step 970, when the UE AS is configured to report the QoE measurement result to the SN, the UE AS 902 configured to report the QoE measurement result to the SN 905 may directly report the measurement result to the SN 905 through a predetermined RRC message (e.g., MeasReportAppLayer) based on the information received in step 945. For example, the AS UE does not perform step 950, but in step 970, the QoE measurement result may be directly reported to the SN 905 through a predetermined RRC message (e.g., MeasReportAppLayer) based on the information received in step 945. In this case, at least one of the split SRB4, the new SRB (SRB5), the split new SRB, SRB2, and SRB3 may be used to report the QoE measurement result. In step 975, the SN 905 may directly deliver the received information to the final destination (TCE or MCE) 908. For reference, when step 970 is performed, steps 955, 960, and 965 may be omitted.

[0217] When UE AS 902 is configured to send a MeasReportAppLayer message to MN 904, MN 905 may configure UE to send it to SN 905 via a predetermined RRC message (e.g., RRCReconfiguration or AppLayerMeasConfig), as described in the above embodiments. For reference, this may be configured for each MeasConfigAppLayerId.

[0218] When the UE AS 902 is configured to send a MeasReportAppLayer message to the SN 905, the SN 905 may configure the UE to send it to the MN 904 through a predetermined RRC message (e.g., RRCReconfiguration or AppLayerMeasConfig). For example, the predetermined RRC message may refer to an RRC connection reconfiguration message (RRCReconfiguration message) or an RRC connection recovery message (RRCResume message).

[0219] Obviously, by indicating that the reporting branch is to be changed from SN to MN for each measConfigAppLayerId, the UE can send MeasReportAppLayer to the MN and the SN accordingly. That is, when the UE is configured to report a specific measConfigAppLayerId to the MN, the UE can send the QoE measurement result for the measConfigAppLayerId configured to be reported to the MN to the MN. When another specific MeasConfigAppLayerId is configured to be reported to the SN, the UE can send the QoE measurement result for the measConfigAppLayerId configured to be reported to the SN to the SN.

[0220] A method for coordinating each node so that the measConfigAppLayerId assigned to the UE does not have the same value for all MNs and SNs or all cell groups (that is, the measConfigAppLayerId is unique in the cell group) is disclosed. A method in which a UE configured to report MeasReportAppLayer to a MN reports MeasReportAppLayer to the SN when congestion occurs in the MN or the SN is disclosed (a method in which a UE configured to report MeasReportAppLayer to the SN reports MeasReportAppLayer to the MN), and signaling procedures and necessary elements of the MN and the SN are proposed accordingly.

[0221] Fig.10 A method for processing QoE configuration information and QoE measurement results related thereto when a UE configured with DC releases an SCG according to an embodiment is shown.

[0222] Reference Fig.10 , shows a process for processing QoE configuration information and QoE measurement results related thereto when a UE configured with NR-DC or NE-DC releases an SCG.

[0223] UE AS 1002 and UE APP 1003 may be collectively referred to as UE 1001. , base station 1004 may be referred to as MN.

[0224] In step 1010, UE 1001 may establish an RRC connection with base station 1004 and be in an RRC connected mode (RRC_CONNECTED).

[0225] In step 1015, the UE AS 1002 may send a UE capability information message (eg, UECapabilityInformation) to the base station 1004. The information embedded in the message may be the same as in the above-mentioned embodiments.

[0226] In step 1020, the UE 1001 may be configured for NR-DC or NE-DC. The UE in NR-DC or NE-DC may send and receive data from the MN 1004 and the SN 1005. Configuring NR-DC or NE-DC for the UE may be performed as in the above-described embodiments.

[0227] In step 1025, UE AS 1002 may receive a predetermined RRC message (eg, RRCReconfiguration or RRCResume) embedded with QoE measurement configuration information (AppLayerMeasConfig) from MN 1004. AppLayerMeasConfig may include QoE measurement configuration information associated with MCG and / or QoE measurement configuration information associated with SCG.

[0228] Through the RRC message, the UE 1002 may be configured to report the QoE report for each measConfigAppLayerId for each QoE configuration to the MN 1004 or the SN 1005. That is, the UE 1002 may be configured to report the QoE report for each measConfigAppLayerId configured in association with the MN 1004 to the MN 1004 or the SN 1005, or may be configured to report the QoE report for each measConfigAppLayerId configured in association with the SN 1005 to the MN 1004 or the SN 1005. The UE 1002 may be configured to report the entire QoE configuration configured in association with the MN 1004 to the MN 1004 or the SN 1005, and / or may be configured to report the entire QoE configuration configured in association with the SN 1005 to the MN 1004 or the SN 1005.

[0229] In step 1030, UE AS 1002 may receive a predetermined RRC message (e.g., RRCReconfiguration) embedded with QoE measurement configuration information (AppLayerMeasConfig) from SN 1005. AppLayerMeasConfig may include QoE measurement configuration information associated with MCG and / or QoE measurement configuration information associated with SCG. The specific process may be the same as in the above-mentioned embodiment.

[0230] Through the RRC message, the UE 1002 may be configured to report the QoE report for each measConfigAppLayerId (i.e., for each QoE configuration) to the MN 1004 or SN 1005. That is, the UE 1002 may be configured to report the QoE report for each measConfigAppLayerId configured in association with the MN 1004 to the MN 1004 or SN 1005, or may be configured to report the QoE report for each measConfigAppLayerId configured in association with the SN 1005 to the MN 1004 or SN 1005. The UE 1002 may be configured to report the entire QoE configuration configured in association with the MN 1004 to the MN 1004 or SN 1005, and / or may be configured to report the entire QoE configuration configured in association with the SN 1005 to the MN 1004 or SN 1005.

[0231] Both steps 1025 and 1030 may be performed, or only step 1025 may be performed and step 1030 may be omitted.

[0232] In step 1035, UE AS 1002 may send a MeasReportAppLayer message including a QoE measurement result to MN 1004 via SRB4. The QoE measurement result may refer to a QoE report for (one or more) QoE configuration information associated with an MCG configured to be sent to MN 1004 and / or a QoE report for (one or more) QoE configuration information associated with an SCG configured to be sent to MN 1004.

[0233] The UE may send, to the MN 1004 through SRB4, a ULInformationTransferMRDC message in which a QoE report for (one or more) QoE configuration information associated with the SCG configured to be sent to the MN 1004 is embedded. That is, the UE may embed a QoE report on (one or more) QoE configuration information associated with the SCG configured to be sent to the MN 1004 in a MeasReportAppLayer message or in a separate ULInformationTransferMRDC message. Alternatively, the UE may include the QoE report in a separate ULInformationTransferMRDC message, and the ULInformationTransferMRDC message may be embedded in a MeasReportAppLayer message and sent.

[0234] In step 1040, the terminal AS1002 may send a MeasReportAppLayer message including a QoE measurement result to the SN 1005 via SRB5. The QoE measurement result may refer to a QoE report for (one or more) QoE configuration information associated with the MCG configured to be sent to the SN 1005 and / or a QoE report for (one or more) QoE configuration information associated with the SCG configured to be sent to the SN 1005.

[0235] The UE may send, to the SN 1005 through SRB5, a ULInformationTransferMRDC message in which a QoE report for (one or more) QoE configuration information associated with the MCG configured to be sent to the SN 1005 is embedded. That is, the UE may embed a QoE report on (one or more) QoE configuration information associated with the MCG configured to be sent to the SN 1005 in a MeasReportAppLayer message or in a separate ULInformationTransferMRDC message. Alternatively, the UE may include the QoE report in a separate ULInformationTransferMRDC message, and the ULInformationTransferMRDC message may be embedded in a MeasReportAppLayer message and sent.

[0236] In step 1045, the MN 1004 may send a predetermined RRC message (eg, RRCReconfiguration) to release the SN or SCG 1005 configured to the UE 1001. As an example, the SCG may be released through mrdc-SecondaryCellGroupConfig.

[0237] In step 1050, the UE 1001 determines a manner to process the QoE configuration report that was configured to be reported via SRB5. In this regard, at least one of the following methods may be combined and performed.

[0238] Method 1: When releasing the SCG, UE 1001 may release the QoE configuration information associated with the SCG 1005 and the QoE measurement results associated therewith without a separate base station instruction.

[0239] Method 2: When releasing the SCG, the UE 1001 may release the QoE configuration information associated with the SCG configured to report the QoE measurement results to the SN 1005 (ie, via SRB5) and the QoE measurement results therefor without a separate base station indication.

[0240] In method 2, the QoE configuration and the associated QoE measurement results associated with the SCG configured to report the QoE measurement results to the MN 1004 are not released. Specifically, even if the MN 1004 receives the QoE measurement results from the UE 1001, the MN 1004 may deliver the QoE measurement results to the TCE or SN.

[0241] Method 3: When releasing the SCG, the UE 1001 may release the QoE configuration information and the QoE measurement results associated with the SCG 1005 according to the base station instruction. For example, in step 1045, the MN 1004 may indicate to the UE 1001 whether to release the QoE configuration information and the QoE measurement results associated with the SCG 1005. Therefore, the UE 1001 may determine whether to release the QoE configuration information and the QoE measurement results associated with the SCG 1005.

[0242] Method 4: When releasing the SCG, UE 1001 may release each type of QoE configuration information and the QoE measurement results associated with the SCG 1005 according to the base station instruction.

[0243] In method 4, the base station can indicate to the UE whether to release the QoE configuration information and the QoE measurement result for each measConfigAppLayerId associated with the SCG.

[0244] Method 5: When releasing the SCG, the UE 1001 may maintain the QoE configuration information associated with the MCG configured to be sent to the SN 1005 without a separate base station indication, and send a QoE report for this to the MN 1004 through SRB4.

[0245] Method 6: When releasing the SCG, the UE 1001 may maintain the QoE configuration information associated with the MCG configured to be sent to the SN 1005 according to the base station instruction, and determine whether to send a QoE report for this to the MN 1004 through SRB4.

[0246] In method 6, the base station indication may be applied to each QoE configuration associated with the MCG. That is, when the base station indicates that a specific QoE configuration is to be sent to the MN, the UE may send a corresponding QoE report to the MN 1004. In this case, for a QoE configuration for which there is no separate indication, the UE may release the QoE configuration together with the QoE report or maintain the QoE configuration (this is because the UE may send a corresponding QoE report to the MN later according to the base station indication).

[0247] When the UE 1001 releases a specific QoE configuration, information about this may be notified to the UE APP 1003. Therefore, the UE APP 1003 may no longer perform QoE measurement for the corresponding QoE configuration.

[0248] In step 1055 , the UE AS 1002 may send a MeasReportAppLayer message or a ULInformationTransferMRDC message including the QoE measurement result to the MN 1004 through SRB4, as in the above step 1035 .

[0249] Fig.11 A method for processing QoE configuration information and QoE measurement results related thereto when a UE configured with DC deactivates SCG according to an embodiment is shown.

[0250] Reference Fig.11 , shows a process for processing QoE configuration information and QoE measurement results related thereto when a UE configured with NR-DC or NE-DC deactivates SCG.

[0251] The UE AS 1102 and the UE application layer (APP) 1103 may be collectively referred to as a UE 1101. The base station 1104 may be referred to as a MN.

[0252] In step 1110, UE 1101 may establish an RRC connection with base station 1104 and be in RRC connected mode (RRC_CONNECTED). In step 1115, UE AS 1102 may send a UE capability information message (eg, UECapabilityInformation) to base station 1104. The information embedded in the message may be the same as in the above embodiment.

[0253] In step 1120, UE 1101 may be configured for NR-dual connectivity (DC) or NE-DC. UE 1101 in NR-DC or NE-DC may send and receive data from MN 1104 and SN 1105, as in the above-described embodiments.

[0254] In step 1125, UE AS 1102 may receive a predetermined RRC message (e.g., RRCReconfiguration or RRCResume) embedding QoE measurement configuration information (AppLayerMeasConfig) from MN 1104. AppLayerMeasConfig may include QoE measurement configuration information associated with the MCG and / or QoE measurement configuration information associated with the SCG, as in the above embodiments.

[0255] Through the RRC message, the UE 1102 may be configured to report the QoE report for each measConfigAppLayerId (i.e., for each QoE configuration) to the MN 1104 or the SN 1105. That is, the UE 1102 may be configured to report the QoE report for each measConfigAppLayerId configured in association with the MN 1104 to the MN 1104 or the SN 1105, or may be configured to report the QoE report for each measConfigAppLayerId configured in association with the SN 1105 to the MN 1104 or the SN 1105. The UE 1102 may be configured to report the entire QoE configuration configured in association with the MN 1104 to the MN 1104 or the SN 1105, and / or may be configured to report the entire QoE configuration configured in association with the SN 1105 to the MN 1104 or the SN 1105.

[0256] In step 1130, UE AS 1102 may receive a predetermined RRC message (e.g., RRCReconfiguration) embedded with QoE measurement configuration information (AppLayerMeasConfig) from SN 1105. AppLayerMeasConfig may include QoE measurement configuration information associated with MCG and / or QoE measurement configuration information associated with SCG, as in the above embodiments.

[0257] Through the RRC message, the UE 1102 may be configured to report the QoE report for each measConfigAppLayerId (i.e., for each QoE configuration) to the MN 1104 or the SN 1105. That is, the UE 1102 may be configured to report the QoE report for each measConfigAppLayerId configured in association with the MN 1104 to the MN 1104 or the SN 1105, or may be configured to report the QoE report for each measConfigAppLayerId configured in association with the SN 1105 to the MN 1104 or the SN 1105. The UE 1102 may be configured to report the entire QoE configuration configured in association with the MN 1104 to the MN 1104 or the SN 1105, and / or may be configured to report the entire QoE configuration configured in association with the SN 1105 to the MN 1104 or the SN 1105.

[0258] Both steps 1125 and 1130 may be performed, or only step 1125 may be performed and step 1130 may be omitted.

[0259] In step 1135, UE AS 1102 may send a MeasReportAppLayer message including a QoE measurement result to MN 1104 via SRB4. The QoE measurement result may refer to a QoE report for (one or more) QoE configuration information associated with an MCG configured to be sent to MN 1104 and / or a QoE report for (one or more) QoE configuration information associated with an SCG configured to be sent to MN 1104.

[0260] The UE may send, to the MN 1104 through SRB4, a ULInformationTransferMRDC message in which a QoE report on (one or more) QoE configuration information associated with the SCG configured to be sent to the MN 1104 is embedded. That is, the UE may embed a QoE report on (one or more) QoE configuration information associated with the SCG configured to be sent to the MN 1104 in a MeasReportAppLayer message or in a separate ULInformationTransferMRDC message.

[0261] In step 1140, the terminal AS1102 may send a MeasReportAppLayer message including a QoE measurement result to the SN 1105 via SRB5. The QoE measurement result may refer to a QoE report for (one or more) QoE configuration information associated with the MCG configured to be sent to the SN 1105 and / or a QoE report for (one or more) QoE configuration information associated with the SCG configured to be sent to the SN 1105.

[0262] The UE may send, to the SN 1105 through SRB5, a ULInformationTransferMRDC message in which a QoE report on (one or more) QoE configuration information associated with the MCG configured to be sent to the SN 1105 is embedded. That is, the UE may embed a QoE report on (one or more) QoE configuration information associated with the MCG configured to be sent to the SN 1105 in a MeasReportAppLayer message or in a separate ULInformationTransferMRDC message.

[0263] In step 1145, the MN 1104 may send a predetermined RRC message (eg, RRCReconfiguration) to deactivate the SN or SCG 1105 configured to the UE 1101. As an example, the SCG may be deactivated through scg-State.

[0264] In step 1150, the UE 1101 according to the present disclosure may perform at least one method proposed below. That is, the following methods may be combined and performed, and only one method may be performed.

[0265] Method 7: When the SCG is deactivated, the UE 1101 may send all QoE measurement results that have been configured to be sent to the SN 1105 through SRB5 to the MN 1104 through SRB4 without a separate base station indication.

[0266] Method 8: When deactivating SCG, UE 1101 may send all QoE measurement results that have been configured to be sent to SN 1105 via SRB5 to MN 1104 via SRB4 according to base station indication. The base station indication may be performed by step 1145, the previous operation (1125 or 1130), or a later RRCReconfiguration message.

[0267] Method 9: When deactivating the SCG, the base station may instruct the UE to send the QoE measurement results for some of the QoE configuration information that has been configured to be sent to the SN 1105 through SRB5 to the MN 1104 through SRB4. That is, the UE may be instructed to send the QoE measurement results for each measConfigAppLayerId to the MN 1104 through SRB4. The base station instruction may be performed through step 1145, the previous operation (1125 or 1130), or a later RRCReconfiguration message.

[0268] In step 1155 , the UE AS 1102 may send a MeasReportAppLayer message or a ULInformationTransferMRDC message including the QoE measurement result to the MN 1104 through SRB4. This may be the same as in step 1135 .

[0269] In step 1160, the MN 1104 may send a predetermined RRC message (e.g., RRCReconfiguration) to activate the SN or SCG 1105 configured to the UE 1101. As an example, the SCG may be activated by not including the scg-State in the RRC message. When activating the SCG, the UE 1101 according to the present disclosure may perform at least one method proposed below. That is, the following methods may be combined and performed, or only one method may be performed.

[0270] Method 10: When SCG is activated, UE 1101 may retransmit to SN 1105 through SRB5 all QoE measurement results that have been configured to be sent to SN 1105 through SRB5 (before step 1160) without a separate base station indication.

[0271] Method 11: When the SCG is activated, the UE 1101 may retransmit to the SN 1105 via SRB5 all the QoE measurement results that have been configured to be sent to the SN 1105 via SRB5 (before step 1160) according to the base station instruction.

[0272] The base station may instruct the UE to retransmit the QoE measurement result for each QoE configuration to the SN 1105 via SRB5.

[0273] Method 12: When UE 1101 sends all QoE measurement results that have been configured to be sent to SN 1105 via SRB5 before SCG deactivation to MN 1104 via SRB4 during the SCG deactivation period, UE 1101 can retransmit the corresponding QoE measurement results to SN 1105 via SRB5 without a separate base station indication.

[0274] Method 13: When UE 1101 sends all QoE measurement results that have been configured to be sent to SN 1105 via SRB5 before SCG deactivation to MN 1104 via SRB4 during the SCG deactivation period, UE 1101 may retransmit the corresponding QoE measurement results to SN 1105 via SRB5 according to the base station instruction.

[0275] The base station may instruct the UE to retransmit the QoE measurement result for each QoE configuration to the SN 1105 via SRB5.

[0276] Method 14: When the base station instructs the UE to send QoE measurement results for some QoE configuration information among the QoE configuration information that has been configured to be sent to SN 1105 via SRB5 to MN 1104 via SRB4 before deactivating SCG, UE1101 can retransmit the corresponding QoE measurement results to SN 1105 via SRB5 according to the instruction of the base station.

[0277] The base station may instruct the UE to retransmit the QoE measurement result for each QoE configuration to the SN 1105 via SRB5.

[0278] The UE may apply at least one method proposed with respect to the QoE measurement result for the QoE configuration that is not transmitted to the MN 1104 through SRB4.

[0279] Fig.12 The internal structure of the UE according to the embodiment is shown.

[0280] Reference Fig.12 , the UE may include a radio frequency (RF) processor 1210 , a baseband processor 1220 , a storage unit 1230 , and a controller 1240 .

[0281] The RF processor 1210 may perform functions for sending and receiving signals through a wireless channel, such as frequency band conversion and amplification of signals. That is, the RF processor 1210 may up-convert the baseband signal provided from the baseband processor 1220 into an RF band signal, transmit the RF band signal through an antenna, and then down-convert the RF band signal received by the antenna into a baseband signal. For example, the RF processor 1210 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), etc. Although the accompanying drawings show only one antenna, the UE may include multiple antennas. The RF processor 1210 may include multiple RF chains. In addition, the RF processor 1210 may perform beamforming. For beamforming, the RF processor 1210 may control the phase and size of each signal sent / received by multiple antennas or antenna elements. The RF processor may perform MIMO and receive multiple layers when performing MIMO operations.

[0282] The baseband processor 1220 can perform functions for converting between baseband signals and bit streams according to the physical layer standard of the system. For example, when sending data, the baseband processor 1220 can generate complex symbols by encoding and modulating the transmission bit stream. In addition, when receiving data, the baseband processor 1220 can reconstruct the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1210. For example, in the OFDM scheme, when sending data, the baseband processor 1220 can generate complex symbols by encoding and modulating the transmission bit stream, map these complex symbols to subcarriers, and then configure OFDM symbols by inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processor 1220 can divide the baseband signal provided from the RF processor 1210 in units of OFDM symbols, reconstruct the signal mapped to the subcarrier by FFT operation, and then reconstruct the received bit stream by demodulation and decoding.

[0283] The baseband processor 1220 and the RF processor 1210 can send and receive signals as described above. Therefore, the baseband processor 1220 and the RF processor 1210 can be referred to as a transmitter, a receiver, a transceiver, or a communication unit. In addition, at least one of the baseband processor 1220 and the RF processor 1210 may include multiple communication modules to support a variety of different wireless access technologies. In addition, at least one of the baseband processor 1220 and the RF processor 1210 may include different communication modules to process signals of different frequency bands. For example, different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), cellular networks (e.g., LTE), etc. In addition, different frequency bands may include ultra-high frequency (SHF) bands and millimeter (mm) wave (e.g., 60GHz) bands.

[0284] The storage unit 1230 stores data such as basic programs, applications, and setting information for the operation of the UE. In particular, the storage unit 1230 may store information related to a second access node that performs wireless communication using a second radio access technology. The storage unit 1230 may provide the stored data according to a request of the controller 1240.

[0285] The controller 1240 may control the overall operation of the UE. For example, the controller 1240 may send / receive signals through the baseband processor 1220 and the RF processor 1210. In addition, the controller 1240 may record data in the storage unit 1230 and read data. For this purpose, the controller 1240 may include at least one processor. For example, the controller 1240 may include a communication processor that performs control for communication and an application processor (AP) that controls an upper layer such as an application. The controller 1240 may also include a multi-connection processor 1242 to support multiple connections. The controller 1240 may control the operation of the UE according to various embodiments of the present disclosure. In addition, the controller 1240 may control the operation of the UE AS and the UE APP according to various embodiments of the present disclosure.

[0286] Fig.13 The structure of the NR base station according to this embodiment is shown.

[0287] Reference Fig.13 , the base station may include an RF processor 1310 , a baseband processor 1320 , a backhaul communication unit 1330 , a storage device 1340 , and a controller 1350 .

[0288] The RF processor 1310 may perform functions for sending and receiving signals through a wireless channel, such as frequency band conversion and amplification of signals. That is, the RF processor 1310 may up-convert the baseband signal provided from the baseband processor 1320 into an RF band signal, then transmit the converted signal through an antenna, and down-convert the RF band signal received by the antenna into a baseband signal. For example, the RF processor 1310 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although the accompanying drawings show only one antenna, the first access node may include multiple antennas. The RF processor 1310 may include multiple RF chains. In addition, the RF processor 1310 may perform beamforming. For beamforming, the RF processor 1310 may control the phase and size of each signal sent and received by multiple antennas or antenna elements. The RF processor may perform downlink MIMO operations by sending one or more layers.

[0289] The baseband processor 1320 can perform the function of conversion between the baseband signal and the bit stream according to the physical layer standard of the first wireless access technology. For example, when sending data, the baseband processor 1320 can generate complex symbols by encoding and modulating the transmission bit stream. In addition, when receiving data, the baseband processor 1320 can reconstruct the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1310. For example, in the OFDM scheme, when sending data, the baseband processor 1320 can generate complex symbols by encoding and modulating the transmission bit stream, map these complex symbols to subcarriers, and then configure OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processor 1320 can divide the baseband signal provided from the RF processor 1310 in units of OFDM symbols, recover the signal mapped with the subcarrier by FFT operation, and then recover the received bit stream by demodulation and decoding. The baseband processor 1320 and the RF processor 1310 can send and receive signals as described above. Therefore, the baseband processor 1320 and the RF processor 1310 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0290] The backhaul communication unit 1330 may provide an interface for communicating with other nodes within the network. That is, the backhaul communication unit 1330 may convert a bit string sent from the master base station to other nodes (e.g., a secondary base station, a core network, etc.) into a physical signal, and convert a physical signal received from other nodes into a bit string.

[0291] The storage unit 1340 may store data such as basic programs, applications, and configuration information for the operation of the master base station. In particular, the storage unit 1340 may store information about bearers allocated to the accessed UE, measurement results reported from the accessed UE, etc. The storage unit 1340 may store information about a reference for determining whether to provide multiple connections to the UE or stop multiple connections. The storage unit 1340 may provide the data stored therein according to a request from the controller 1350.

[0292] The controller 1350 may control the overall operation of the master base station. For example, the controller 1350 may send and receive signals through the baseband processor 1320 and the RF processor 1310 or through the backhaul communication unit 1330. The controller 1350 may record data in the storage unit 1340 and read data. For this purpose, the controller 1350 may include at least one processor. In addition, the controller 1350 may also include a multi-connection processor 1342 to support multiple connections. The controller 1350 may control the operation of the base station and / or the operation of the NG-RAN according to various embodiments of the present disclosure.

[0293] The methods disclosed herein can be implemented by hardware, software, or a combination of hardware and software.

[0294] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be run by one or more processors in the electronic device. At least one program may include instructions that cause the electronic device to perform the method according to various embodiments of the present disclosure.

[0295] The program (software module or software) may be stored in a non-volatile memory including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage device, compact disk-ROM (CD-ROM), digital versatile disk (DVD) or other type of optical storage device or magnetic cassette. Alternatively, any combination of some or all of them may form a memory in which the program is stored. A plurality of such memories may be included.

[0296] The program may be stored in an attachable storage device that can be accessed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), and a storage area network (SAN), or a combination thereof. Such a storage device may access the apparatus for executing the embodiments of the present disclosure via an external port. In addition, a separate storage device on a communication network may access the apparatus for executing the embodiments of the present disclosure.

[0297] While the present disclosure has been illustrated and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by a user equipment UE supporting a primary cell group MCG and a secondary cell group SCG in a wireless communication system, the method comprising: Receiving at least one application layer measurement configuration information included in the first radio resource control RRC reconfiguration information for the MCG or included in the second RRC reconfiguration information for the SCG; Sending a report message for application layer measurement reporting based on the at least one application layer measurement configuration information; as well as receiving a second RRC reconfiguration message for releasing the SCG, For the first application layer measurement configuration information included in the second RRC reconfiguration information for the SCG, inform the upper layer of the release of the first application layer measurement configuration information and discard the first application layer measurement report associated with the first application layer measurement configuration information that has not been fully submitted to the lower layer for transmission.

2. The method according to claim 1, further comprising: For the second application layer measurement configuration information included in the first RRC reconfiguration information for the MCG, discard the second application layer measurement report associated with the second application layer measurement configuration information, which is configured to be reported via signaling radio bearer 5SRB5 and has not yet been fully submitted to the lower layer for transmission.

3. The method according to claim 2, further comprising: receiving a third RRC message, wherein the third RRC message includes configuration information for indicating that the second application layer measurement report is reported via signaling radio bearer 4 SRB4; as well as Based on the configuration information, the second application layer measurement report is sent via the SRB4.

4. The method according to claim 2, further comprising: In a case where the second application layer measurement configuration information is included in the first RRC reconfiguration information for the MCG, changing the SRB used for the second application layer measurement report from the SRB5 to the SRB4; as well as The second application layer measurement report is reported via the SRB4.

5. The method according to claim 1, in, The at least one application layer measurement is associated with Quality of Experience (QoE).

6. The method according to claim 1, further comprising: A UE capability information message is sent, wherein the UE capability information message includes at least one of first information about a QoE flow measurement report, second information about a QoE multimedia telephone service MTSI measurement report for an international mobile subscriber identity IMS, and third information about a QoE virtual reality VR measurement report.

7. A method performed by a base station associated with a master cell group (MCG) in a wireless communication system, the method comprising: Sending to the user equipment at least one application layer measurement configuration information included in the first radio resource control RRC reconfiguration information for the MCG or included in the second RRC reconfiguration information for the secondary cell group SCG; and sending a second RRC reconfiguration message for releasing the SCG to the UE, Among them, for the first application layer measurement configuration information included in the second RRC reconfiguration information for the SCG, the release of the first application layer measurement configuration information is notified to the upper layer and the first application layer measurement report associated with the first application layer measurement configuration information that has not yet been fully submitted to the lower layer for transmission is discarded.

8. The method according to claim 7, in, For the second application layer measurement configuration information included in the first RRC reconfiguration information for the MCG, the second application layer measurement report associated with the second application layer measurement configuration information, which is configured to be reported via signaling radio bearer 5SRB5 and has not yet been fully submitted to the lower layer for transmission, is discarded.

9. The method according to claim 8, further comprising: Sending a third RRC message to the UE, where the third RRC message includes configuration information for indicating that the second application layer measurement report is reported via signaling radio bearer 4 SRB4; as well as Based on the configuration information, the second application layer measurement report is received from the UE via the SRB4.

10. The method according to claim 7, further comprising: receiving a UE capability information message from the UE, the UE capability information message comprising at least one of first information about a QoE flow measurement report, second information about a QoE multimedia telephony service for international mobile subscriber identity IMS MTSI measurement report, and third information about a QoE virtual reality VR measurement report, The at least one application layer measurement is associated with Quality of Experience (QoE).

11. A user equipment UE supporting a primary cell group MCG and a secondary cell group SCG in a wireless communication system, the UE comprising: Transceiver; as well as A controller, the controller being configured to: Receiving at least one application layer measurement configuration information included in the first radio resource control RRC reconfiguration information for the MCG or included in the second RRC reconfiguration information for the SCG; Sending a report message for application layer measurement reporting based on the at least one application layer measurement configuration information; as well as receiving a second RRC reconfiguration message for releasing the SCG, For the first application layer measurement configuration information included in the second RRC reconfiguration information for the SCG, inform the upper layer of the release of the first application layer measurement configuration information and discard the first application layer measurement report associated with the first application layer measurement configuration information that has not been fully submitted to the lower layer for transmission.

12. The UE according to claim 11, wherein: The controller is also configured to: For the second application layer measurement configuration information included in the first RRC reconfiguration information for the MCG, discard the second application layer measurement report associated with the second application layer measurement configuration information, which is configured to be reported via signaling radio bearer 5SRB5 and has not yet been fully submitted to the lower layer for transmission.

13. The UE according to claim 11, wherein: The controller is also configured to: receiving a third RRC message, the third RRC message including configuration information for indicating that the second application layer measurement report is reported via signaling radio bearer 4 SRB4; and Based on the configuration information, the second application layer measurement report is sent via the SRB4.

14. The UE according to claim 11, wherein: The controller is also configured to: In a case where the second application layer measurement configuration information is included in the first RRC reconfiguration information for the MCG, changing the SRB used for the second application layer measurement report from the SRB5 to the SRB4; as well as The second application layer measurement report is reported via the SRB4.

15. The UE according to claim 11, in, The at least one application layer measurement is associated with Quality of Experience (QoE).

16. The UE according to claim 11, wherein: The controller is also configured to: A UE capability information message is sent, wherein the UE capability information message includes at least one of first information about a QoE flow measurement report, second information about a QoE multimedia telephone service MTSI measurement report for an international mobile subscriber identity IMS, and third information about a QoE virtual reality VR measurement report.

17. A base station associated with a master cell group (MCG) in a wireless communication system, the base station comprising: Transceiver; as well as A controller, the controller being configured to: sending to a user equipment UE at least one application layer measurement configuration information included in the first radio resource control RRC reconfiguration information for the MCG or included in the second RRC reconfiguration information for the secondary cell group SCG, and sending a second RRC reconfiguration message for releasing the SCG to the UE, Among them, for the first application layer measurement configuration information included in the second RRC reconfiguration information for the SCG, the release of the first application layer measurement configuration information is notified to the upper layer and the first application layer measurement report associated with the first application layer measurement configuration information that has not yet been fully submitted to the lower layer for transmission is discarded.

18. The base station according to claim 17, in, For the second application layer measurement configuration information included in the first RRC reconfiguration information for the MCG, the second application layer measurement report associated with the second application layer measurement configuration information, which is configured to be reported via signaling radio bearer 5SRB5 and has not yet been fully submitted to the lower layer for transmission, is discarded.

19. The base station according to claim 17, wherein: The controller is also configured to: Sending a third RRC message to the UE, where the third RRC message includes configuration information for indicating that the second application layer measurement report is reported via signaling radio bearer 4 SRB4; as well as Based on the configuration information, the second application layer measurement report is received from the UE via the SRB4.

20. The base station according to claim 17, wherein: The controller is also configured to: receiving a UE capability information message from the UE, the UE capability information message comprising at least one of first information about a QoE flow measurement report, second information about a QoE multimedia telephony service for international mobile subscriber identity IMS MTSI measurement report, and third information about a QoE virtual reality VR measurement report, The at least one application layer measurement is associated with Quality of Experience (QoE).

Images