WO2024035119A1

WO2024035119A1 - Method and apparatus for seamless qoe measurement in mobility situation between wireless access technologies in next-generation mobile communication system

Info

Publication number: WO2024035119A1
Application number: PCT/KR2023/011759
Authority: WO
Inventors: 정승범; 정상엽
Original assignee: 삼성전자 주식회사
Priority date: 2022-08-10
Filing date: 2023-08-09
Publication date: 2024-02-15
Also published as: KR20240021480A

Abstract

The present invention relates to a method and an apparatus for seamlessly measuring quality of experience (QoE) in a mobility situation between wireless access technologies in a next-generation mobile communication system, the method comprising the steps of: receiving, from a base station, a message for handover from a first network to a second network, wherein the message includes an indicator indicating to maintain the QoE configuration of the first network; on the basis of completion of the handover, transmitting a handover completion message to the base station; performing QoE measurement on the basis of the first QoE configuration; and transmitting a report message including the result of the QoE measurement to the base station.

Description

Method and apparatus for seamless QOE measurement in mobility situations between wireless access technologies in next-generation mobile communication systems

This disclosure relates to terminal and base station operations in a mobile communication system. More specifically, it relates to a method and device for seamlessly measuring QoE in a mobility situation between wireless access technologies.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss in ultra-high frequency bands and increase radio transmission distance. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets various regulatory requirements in unlicensed bands. ), NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

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

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence are designed to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

As described above, with the development of mobile communication systems, various services can be provided, and a method for seamlessly measuring QoE in mobility situations between wireless access technologies is required.

The disclosed embodiment seeks to provide a method and device that can effectively provide services in a mobile communication system.

The present disclosure relates to a wireless communication system, and its purpose is to provide a method and device for seamlessly measuring QoE in a mobility situation between wireless access technologies.

The present disclosure to solve the above problems is a method performed by a terminal in a wireless communication system, comprising the steps of receiving a message for handover from a first network to a second network from a base station, the message includes an indicator instructing to maintain Quality of Experience (QoE) settings in the first network; Based on completion of the handover, transmitting a handover completion message to the base station; performing QoE measurement based on the first QoE setting; and transmitting a report message including the results of the QoE measurement to the base station.

The present disclosure to solve the above problems is a method performed by a base station in a wireless communication system, comprising the steps of transmitting a message for handover from a first network to a second network to a terminal, the message comprising: 1 Contains an indicator instructing to maintain Quality of Experience (QoE) settings in the network; Receiving a handover completion message from the terminal based on completion of the handover; and receiving a report message including a result of QoE measurement from the terminal, wherein the QoE measurement is performed based on the first QoE setting.

The present disclosure to solve the above problems is to provide a terminal in a wireless communication system, comprising: a transceiver; and a control unit connected to the transceiver unit, wherein the control unit receives a message for handover from a first network to a second network from a base station, and the message sets Quality of Experience (QoE) in the first network. includes an indicator instructing to maintain, based on completion of the handover, transmitting a handover completion message to the base station, performing QoE measurement based on the first QoE setting, and transmitting the QoE to the base station. It is characterized by transmitting a report message containing the results of the measurement.

The present disclosure to solve the above problems is to provide a base station in a wireless communication system, comprising: a transceiver; and a control unit connected to the transceiver unit, wherein the control unit transmits a message for handover from the first network to the second network to the terminal, and the message is configured to determine the Quality of Experience (QoE) in the first network. Contains an indicator instructing to maintain the setting, receives a handover completion message from the terminal based on completion of the handover, and receives a report message including a result of QoE measurement from the terminal, QoE measurement is characterized in that measurement is performed based on the first QoE setting.

According to one embodiment, in a wireless communication system, a method and apparatus for seamlessly measuring QoE in a mobility situation between wireless access technologies are provided.

1 is a diagram showing the structure of a next-generation mobile communication system.

Figure 2 is a diagram for explaining wireless connection state transition in a next-generation mobile communication system.

Figure 3 is a flowchart showing the procedure for setting or reporting signaling-based QoE measurement in the present invention.

Figure 4 is a flowchart showing the procedure for setting or reporting management-based QoE measurement in the present invention.

Figure 5 is a flowchart showing the setting and reporting procedure of RAN visible QoE measurement.

Figure 6 is an embodiment of the present invention, a diagram showing a method of maintaining LTE QoE settings while a terminal performs handover from LTE to NR.

Figure 7 is an embodiment of the present invention, a diagram showing a method of releasing QoE settings of LTE while a terminal performs handover from LTE to NR.

Figure 8 is an embodiment of the present invention, a diagram showing a method of updating and maintaining the LTE QoE settings to the NR QoE settings while the terminal performs a handover from LTE to NR.

Figure 9 is an embodiment of the present invention, a diagram showing a method of releasing QoE settings of LTE while a terminal performs handover from LTE to NR.

Figure 10 is an embodiment of the present invention, a diagram showing a method of maintaining the QoE settings of NR while the terminal performs handover from NR to LTE.

Figure 11 is an embodiment of the present invention, a diagram showing a method of canceling the QoE settings of all NRs while the terminal performs handover from NR to LTE.

Figure 12 is an embodiment of the present invention, a diagram showing a method of updating and maintaining NR's QoE settings to LTE QoE settings while the terminal performs handover from NR to LTE.

Figure 13 is an embodiment of the present invention, a diagram showing a method of canceling the QoE settings of all NRs while the terminal performs handover from NR to LTE.

Figure 14 is a block diagram showing the internal structure of a terminal to which the present invention is applied.

Figure 15 is a block diagram showing the configuration of a base station according to the present invention.

In the following description of the present invention, if a detailed description of a related known function or configuration is judged to unnecessarily obscure the gist of the present invention, the detailed description will be omitted. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.

Referring to FIG. 1, as shown, the wireless access network of the next-generation mobile communication system (New Radio, NR) includes a next-generation base station (New Radio Node B, hereinafter gNB) (1-10) and AMF (Access and Mobility Management Function, 1-05). The user terminal (New Radio User Equipment, hereinafter referred to as NR UE or terminal) (1-15) connects to the external network through gNB (1-10) and AMF (1-05).

In Figure 1, gNB corresponds to eNB (Evolved Node B) of the existing Long Term Evolution (LTE) system. gNB is connected to the NR UE through a wireless channel and can provide superior services than the existing Node B (1-20). In the next-generation mobile communication system, all user traffic is serviced through a shared channel, so a device that collects status information such as buffer status, available transmission power status, and channel status of UEs and performs scheduling is required, which is called gNB (gNB). 1-10) is in charge. One gNB typically controls multiple cells. In order to implement ultra-high-speed data transmission compared to existing LTE, it can have more than the existing maximum bandwidth, and additional beamforming technology can be applied using Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology. . In addition, Adaptive Modulation & Coding (hereinafter referred to as AMC) is applied, which determines the modulation scheme and channel coding rate according to the channel status of the terminal. AMF (1-05) performs functions such as mobility support, bearer setup, and QoS (Quality of Service) setup. AMF is a device that handles various control functions as well as mobility management functions for terminals and is connected to multiple base stations. Additionally, the next-generation mobile communication system can be linked to the existing LTE system, and AMF is connected to the MME (Mobility Management Entity, 1-25) through a network interface. The MME is connected to the existing base station, eNB (1-30). A terminal that supports LTE-NR Dual Connectivity can transmit and receive data while maintaining connectivity to not only the gNB but also the eNB (1-35).

The next-generation mobile communication system has three radio access states (Radio Resource Control state, hereinafter RRC state). Connected mode (RRC_CONNECTED, 2-05) is a wireless connection state in which the terminal can transmit and receive data. Standby mode (RRC_IDLE, 2-30) is a wireless connection state in which the terminal monitors whether paging is transmitted to the terminal. The above two modes are wireless connection states that also apply to the existing LTE system, and the detailed technology is the same as that of the existing LTE system. In the next-generation mobile communication system, a new inactive (RRC_INACTIVE) wireless connection state (2-15) has been defined. In the wireless connection state, the UE context is maintained in the base station and the terminal, and RAN (Radio Access Network)-based paging is supported. The characteristics of the new wireless connection state are listed as follows.

- Cell re-selection mobility;

- CN - NR RAN connection (both C/U-planes) has been established for UE;

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

- Paging is initiated by NR RAN;

- RAN-based notification area is managed by NR RAN;

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

The new INACTIVE wireless connection state can be transitioned to connected mode or standby mode using specific procedures. It switches from INACTIVE mode to connected mode according to the Resume process, and switches from connected mode to INACTIVE mode using the Release procedure including suspend setting information (2-10). In the above procedure, one or more RRC messages are transmitted and received between the terminal and the base station, and may consist of one or more steps. Additionally, you can switch from INACTIVE mode to standby mode through the Resume and Release procedure (2-20). Switching between connected mode and standby mode follows existing LTE technology. That is, switching between the above modes occurs through an establishment or release procedure (2-25).

The AS (Access stratum, 3-05) of the terminal is divided into QoE (Quality of Quality) by service type (e.g. streaming, MTSI (Multimedia Telephony Service for IMS (IP (Internet Protocol) Multimedia Subsystem)), VR (Virtual Reality)). Experience) Information indicating whether measurement is supported (e.g., qoe-Streaming-MeasReport, qoe-MTSI-MeasReport, qoe-VR-MeasReport) is sent to the base station (or NG) through a UE capability message (e.g., UECapabilityInformation). -Can be transmitted to RAN, 3-15) (3-10).

Before sending the UE capability message, the base station may send a message (e.g., UECapabilityEnquiry) regarding a request for the UE capability message. In addition, through the UE capability message, the terminal determines whether RAN visible QoE measurement is supported (e.g., ran-VisibleQoE-Streaming-MeasReport, ran-VisibleQoE-VR-MeasReport) by service type (e.g., streaming, VR). It can be reported to the base station. Additionally, through the UE capability message, the UE can report whether it supports UL (UpLink) RRC segmentation for the QoE report message (e.g., ul-MeasurementReportAppLayer-Seg). The UE capability message may include ASN.1 information and related parameter descriptions as shown in Tables 1 and 2 below.

Table 2 above relates to QoE measurement parameters. Service types that can be supported in LTE include streaming and MTSI (Multimedia Telephony Service for IMS (IP Multimedia Subsystem)), and NR additionally defines support for VR (Virtual Reality) in Rel-17, which will be released in a later release. MBMS (Multimedia Broadcast Multicast Services) and XR (Extended Reality) can be additionally supported.

OAM (Operations Administration and Maintenance, 3-20) provides QoE measurement setting information to CN (Core Network, 3-25) (3-30).

The CN that has received the configuration information can activate QoE measurement by transmitting the configuration information to the base station (3-35).

The base station that has received the configuration information can deliver the QoE configuration information to the terminal AS through an RRC message (e.g., RRCReconfiguration or RRCResume message) (3-40).

The RRC message may include IE (Information Elements) (APPLayerMeasConfig) as shown below, and related parameter descriptions may be as shown in Tables 3 and 4 below.

The operation of the terminal AS that receives this may be as shown in Table 5 below.

As described above, in the case of QoE measurement settings included in measConfigAppLayerToAddModList, the AS layer of the terminal can transmit the configuration information to the upper layer or application layer (UE APP, 3-45) of the terminal through AT Command (3-50) ).

Regarding the QoE measurement settings included in measConfigAppLayerToAddReleaseList, the AS layer of the terminal can send an AT Command to delete the saved configuration information to the APP of the terminal. The terminal APP can perform QoE measurement according to the received configuration information. Additionally, the measurement results can be reported to the terminal AS through AT commands according to the setting information (3-55).

The terminal AS that received this can report the measurement result to the base station through an RRC Message (e.g., MeasurementReportAppLayer message) (3-60). SRB4 can be used to report QoE measurement results.

The MeasurementReportAppLayer message may include ASN.1 information and related parameter descriptions as shown in Tables 6 and 7 below.

The specific UE AS procedure for reporting this may be as shown in Table 8 below.

The base station may transmit the measurement result report to the final server that collects the measurement report (TCE (Trance Collection Entity) or MCE (Measurement Collection Entity), 3-65) (3-70).

The management-based QoE setting or reporting procedure is largely similar to the signaling-based procedure (Figure 3). Therefore, in this specification, only the differences in the management-based method are described below, and other procedures and explanations can be considered the same as those for FIG. 3.

In the management-based method, QoE measurement can be activated by the OAM (4-05) directly sending the QoE measurement settings to the base station (4-10) without going through the CN (4-15).

The base station that receives this searches for single or multiple terminals that meet various conditions (e.g., area scope, application layer capability, service type). And the base station can transmit the QoE measurement configuration to each of the terminals through an RRC message (eg, RRCReconfiguration message or RRCResume) (4-20).

Other procedures and message types can be seen as the same as the description of FIG. 3 (signaling-based method).

The QoE measurements shown in Figures 3 and 4 are set by the OAM, and the QoE measurement reports generated accordingly are collected into TCE or MCE, so the operator can use the QoE measurement reports for network optimization. When the terminal transmits a report on the OAM-based QoE measurement to the base station and the base station receives it, the base station cannot read or understand the measurement report. The MeasurementReportAppLayer message includes a measurement report generated by the application layer of the terminal in the measurementReportAppLayerContainer, but because it is stored in the form of OCTET STRING, it cannot be read or understood by the base station or the RRC layer of the base station. To solve this problem, RAN visible QoE (RVQoE) measurement was defined and introduced in 3GPP in order for the base station to read the QoE measurement report and use it for network optimization such as radio resource management.

First, the terminal can report to the base station whether it supports RVQoE measurement by service type (e.g., streaming, VR) (5-05). At this time, the UECapabilityInformation message can be used.

For streaming services, the terminal can set the ran-VisibleQoE-Streaming-MeasReport-r17 parameter, and for VR services, the terminal can set the ran-VisibleQoE-VR-MeasReport-r17 parameter. RVQoE measurement settings are created by the base station and can be set to the terminal (5-10). At this time, the RVQoE measurement settings may be delivered together with the OAM-based QoE measurement settings.

RVQoE measurement settings can be turned on or off with the ran-VisibleParameters-r17 parameter. The parameters may include RAN-VisibleParameters IE, through which the base station reports to the terminal or the terminal's APP the RVQoE measurement reporting period (ran-VisiblePeriodicity), the maximum number of reportable buffer levels (numberOfBufferLevelEntries), and the initial Playout delay of the terminal. You can set or indicate whether (reportInitialPlayoutDelay), etc. The AS layer of the terminal can transmit this setting information to the APP layer of the terminal (5-15). At this time, the RVQoE measurement settings may be delivered together with the OAM-based QoE measurement settings.

The APP of the terminal may perform QoE measurement based on the RVQoE measurement configuration information, generate an RVQoE measurement report, and transmit it to the AS layer of the terminal (5-20). At this time, the RVQoE measurement report may be delivered together with the OAM-based QoE measurement report.

The AS layer of the terminal that received this can forward it to the base station (5-25). At this time, the RVQoE measurement report may be delivered together with the OAM-based QoE measurement report. In 5-25, the RVQoE measurement report may be transmitted via RAN-VisibleMeasurements IE in the MeasurementReportAppLayer message.

The IE may include information such as the APP layer's buffer level list (applicationLayerBufferLevelList), initial playout delay (initialPlayoutDelay), and involved PDU session ID list (pdu-SessionIdList).

The base station can read the RVQoE report and use it to perform network optimization. For example, the QoE of a terminal that is experiencing poor QoE for a specific service can be improved by allocating a larger amount of wireless resources.

A detailed description related to RAN visible QoE measurement may be as follows.

The following is specified in the 3GPP Release 18 Work Item Description (WID, RP-221803) document.

Among the WIDs, the part titled “Support the continuity of legacy QoE measurement job for streaming and MTSI service during intra-5GC inter-RAT handover process [RAN2, RAN3]” indicates that the UE supports inter-RAT handover within 5GC (5G core network). An objective that must be supported in Rel-18 so that legacy QoE measurements for streaming services and MTSI services can be performed seamlessly while performing handover (i.e., handover from an LTE base station to an NR base station, or from an NR base station to an LTE base station). It is specified.

Here, legacy QoE measurement may mean QoE measurement excluding RAN visible QoE measurement. In other words, even if the terminal receives QoE setting information for a streaming service or MTSI service from an LTE base station connected to 5GC and performs QoE measurement, and performs a handover to an NR base station connected to 5GC, the QoE measurement is maintained and The results are reported to the NR base station, and finally the QoE measurement report can be collected up to TCE or MCE.

Conversely, even if the terminal receives QoE setting information for a streaming service or MTSI service from an NR base station connected to 5GC and performs QoE measurement, even if handover is performed to an LTE base station connected to 5GC, the QoE measurement is maintained. The results are reported to the LTE base station, and ultimately the QoE measurement report can be collected up to TCE or MCE. Through this, the network operator or operator can collect the QoE results experienced by the terminal not only before and after the handover, but also while performing the handover, and use it to optimize the network.

The following shows the ASN.1 code of the RRC IE or message regarding QoE measurement setup and reporting in LTE and NR.

The ASN.1 code of RRC IE (measConfigAppLayer) used to set up QoE measurement in LTE is defined in the standard document TS 36.331 as shown in Table 9 below.

The ASN.1 code of the RRC message (MeasReportAppLayer) used for QoE measurement reporting in LTE is defined in the standard document TS 36.331 as shown in Table 10 below.

The ASN.1 code of RRC IE (AppLayerMeasConfig) used to set up QoE measurement in NR is defined in the standard document TS 38.331 as shown in Table 11 below.

The ASN.1 code of the RRC message (MeasurementReportAppLayer) used in NR to report QoE measurement is defined in the standard document TS 38.331 as follows.

- MeasurementReportAppLayer

The MeasurementReportAppLayer message is used for sending application layer measurement report.

Signaling radio bearer: SRB4

RLC-SAP:AM

Logical channel: DCCH

Direction: UE to Network

Currently, the maximum number of QoE measurement settings that a terminal can perform simultaneously in LTE is 1, which is specified below in the description of measConfigAppLayerContainer in TS 36.331.

Therefore, the base station can set up only one QoE setting for the terminal through RRC IE (measConfigAppLayer), which is used to set up QoE measurement in LTE. This can be achieved by indicating "setup" in the ASN.1 code of measConfigAppLayer. Using measConfigAppLayer, the base station can store QoE configuration information transmitted to the application layer of the terminal during QoE setup setup in measConfigAppLayerContainer, and store it by specifying the serviceType parameter to indicate what service type the application layer is. Conversely, to release QoE configuration information, the base station can indicate "release" in the ASN.1 code of measConfigAppLayer. Since the maximum number of QoE measurement settings that can be set to the terminal is one, the terminal that has received the “release” instruction can release the set QoE measurement settings (if any). To report QoE measurement results in LTE, the terminal can include the QoE measurement result report received from the application layer through the measReportAppLayerContainer parameter in the MeasReportAppLayer message. Since the maximum number of QoE measurement settings that can be set to a terminal in LTE is one, it was defined so that only one measReportAppLayerContainer can be stored in the MeasReportAppLayer message without the need to include multiple measReportAppLayerContainers.

On the other hand, the maximum number of QoE measurement settings that a UE can perform simultaneously in NR is 16, and this is specified in TS 38.331 as follows.

Therefore, through RRC IE (AppLayerMeasConfig) used to set up QoE measurement in NR, the base station can set up up to 16 (or maxNrofAppLayerMeas) QoE settings for the UE at the same time. This can be achieved by setting up to 16 MeasConfigAppLayer IEs (or maxNrofAppLayerMeas) through the measConfigAppLayerToAddModList parameter in AppLayerMeasConfig. Using each MeasConfigAppLayer, the base station can store QoE configuration information transmitted to the application layer of the terminal when establishing or modifying each QoE configuration in measConfigAppLayerContainer, and store it by specifying the serviceType parameter to indicate what service type the application layer is. can do. Additionally, the base station may indicate a QoE setting ID for each MeasConfigAppLayer (for each QoE setting) through the measConfigAppLayerId parameter to distinguish a plurality of QoE settings set for the terminal. Therefore, when the base station releases the QoE setting information of the terminal, by indicating a plurality of measConfigAppLayerId through the measConfigAppLayerToReleaseList parameter, the terminal can cancel a plurality of QoE settings previously established with the corresponding measConfigAppLayerId.

In NR, the terminal can transmit a QoE measurement result report generated for each measConfigAppLayerId (for each QoE setting) through one message (MeasurementReportAppLayer message). To this end, the MeasurementReportAppLayer message can store multiple MeasReportAppLayer IEs, and each MeasReportAppLayer IE can indicate which QoE setting the QoE report is generated by storing measConfigAppLayerId. Additionally, MeasReportAppLayer IE can store QoE measurement result information generated at the application layer according to specific QoE settings indicated by measConfigAppLayerId through measReportAppLayerContainer. In NR, the maximum number of QoE measurement settings that a terminal can simultaneously perform (or receive) is 16 (or maxNrofAppLayerMeas), so the MeasurementReportAppLayer message is also defined to accommodate up to 16 (or maxNrofAppLayerMeas) MeasReportAppLayer IEs.

The terminal's AS (Access Stratum layer) (6-05) and the terminal's APP (application layer) (6-10) receive LTE QoE measurement configuration information (e.g., QoE config 1) through the LTE base station or cell. It can be a state (6-15, 6-20).

In LTE, a terminal (AS and/or APP) can store and measure only up to one piece of QoE setting information, so a separate ID to distinguish multiple QoE setting information may not be required (in NR, A separate ID may be required to distinguish multiple QoE setting information). Only the terminal (AS and/or APP) can receive information about what service type the QoE configuration information relates to as an indicator (for example, serviceType) and store this indicator or information (6-15, 6 -20).

A terminal with LTE QoE settings (e.g., QoE config 1) may be in RRC connection mode with an LTE base station or cell (6-23). The LTE base station or cell may initiate handover of the terminal. For this purpose, the source LTE base station or cell (s-eNB) (6-23) provides the information necessary for the target NR base station (t-gNB) (6-25) to prepare for handover through a handover preparation information message or HANDOVER REQUEST message. Can be transmitted to t-gNB (6-30). At this time, the message and information can be sent in the format required for the target RAT (Radio access technology) (i.e., NR).

Based on the above information, the t-gNB can generate an RRC reconfiguration message (e.g., RRCReconfiguration) and deliver it to the s-eNB in a handover command message or HANDOVER REQUEST ACKNOWLEDGEMENT message (6-35).

The s-eNB that has received this can transmit the t-gNB's RRC reconfiguration message to the UE in a MobilityFromEUTRACommand message (6-40).

Below is the ASN.1 code of the MobilityFromEUTRACommand message.

The s-eNB can specify that it transmits the MobilityFromEUTRACommand message to the UE for handover by indicating the value of the purpose parameter as handover. The s-eNB can set the internal parameter values of Handover IE as follows.

1) By setting targetRAT-Type: nr, you can indicate that the target RAT is NR.

2) targetRAT-MessageContainer: Can contain the RRC reconfiguration message generated by the t-gNB.

3) nas-SecurityParamFromEUTRA: Can be omitted when handover to NR.

4) systemInformation: Can be omitted when handover to NR.

In one embodiment of the present invention, during handover, the base station provides an indicator (e.g., indicator A) to maintain or release the QoE settings (e.g., QoE config 1) in LTE held by the terminal after handover to NR. can be defined and/or used.

Indicator A can be defined in the MobilityFromEUTRACommand message or RRC Reconfiguration message (6-40). For example, if indicator A is defined in the MobilityFromEUTRACommand message, the s-eNB can set indicator A, and if indicator A is defined in the RRC Reconfiguration message, the t-gNB can set indicator A.

Even when handover is performed, the base station (s-eNB or t-gNB) may want to perform continuous QoE measurement without interruption in the terminal, and can maintain LTE QoE settings through indicator A. For example, t-gNB supports QoE measurement of the service type set for the UE, and can maintain QoE settings because it is a base station or cell included in the QoE measurement area range (e.g., areaScope) set by the OAM.

For an embodiment in which the s-eNB determines or generates the settings of indicator A (e.g., if indicator A is defined in the MobilityFromEUTRACommand message), an indicator for maintaining QoE settings from the t-gNB (e.g., indicator B) You can receive (6-35).

For example, the By receiving B (6-35), maintenance of the terminal's QoE settings can be instructed through indicator A transmitted to the terminal (6-40).

In one embodiment of the present invention, the base station can cancel the QoE settings and then transmit the same settings to the terminal again. However, for this to happen, the base station must store the terminal's QoE settings information (e.g., measConfigAppLayerContainer), which is then sent back to the terminal. It must be transmitted to , and the terminal AS must also transmit it back to the terminal APP. Considering that the size of the RRC message of QoE configuration information is not small, this may be very inefficient in terms of signaling and energy consumption for the terminal or base station. For example, measConfigAppLayerContainer can occupy up to 1000 bytes in LTE and up to 8000 bytes in NR. In addition, the method of canceling and resetting the QoE settings described above does not allow QoE measurement to be performed continuously. Therefore, in the present invention, continuous QoE measurement is achieved by maintaining (or reusing) the terminal's QoE configuration information (for example, measConfigAppLayerContainer) rather than releasing it during inter-RAT handover, while reducing signaling overhead and maintaining the communication between the terminal and the base station. It can help reduce energy consumption.

After successfully completing the handover, the UE can transmit an RRC Reconfiguration complete message to the t-gNB (6-45).

The terminal AS may release radio resources and/or settings of LTE after successfully completing handover or transmitting an RRC Reconfiguration complete message. However, at this time, the terminal AS may maintain QoE resources and/or settings without exceptionally releasing them according to the indicator A received at 6-40 (6-50). In other words, even if the terminal performs handover to NR, the LTE QoE settings may be stored and maintained (separately from the NR settings).

QoE settings are still maintained in the terminal APP and QoE measurement can be performed (6-55).

Accordingly, the terminal APP can generate a QoE report and deliver it to the terminal AS. At this time, the LTE AT command can be used, and the QoE measurement result generated by measurement by the terminal APP can be reported and include the service type being stored (for example, the service type of QoE config 1) (6-60).

The terminal AS that has received the QoE report from the terminal APP can transmit the QoE report to the base station (t-gNB) that has completed the handover (6-65). At this time, the QoE reporting message defined in NR (eg, MeasurementReportAppLayer message) can be used. SRB3 or SRB4 can be used to transmit the message. The QoE report message (e.g., MeasurementReportAppLayer message) defined in conventional NR may include a container (e.g., measurementReportAppLayerContainer) that stores the QoE report made in the APP with NR QoE settings, and the service type (e.g., serviceType) may include a QoE configuration ID (e.g., measConfigAppLayerId).

In one embodiment of the present invention, a container (e.g., measurementReportAppLayerContainer-EUTRA) and/or service type that stores a QoE report created in an APP with LTE QoE settings within a QoE report message (e.g., MeasurementReportAppLayer message) defined in NR. (For example, serviceType-EUTRA) can be additionally defined and set using the information received in 6-60.

In one embodiment of the present invention, the terminal transmits information received from 6-60 to the base station (e.g., t-gNB) using a QoE reporting message (e.g., MeasReportAppLayer message) defined in LTE at 6-65. ) can be reported to. The t-gNB can forward the QoE report received at 6-65 to the TCE or MCE (6-70).

As an embodiment of the present invention, if the RRC Reconfiguration message included in MobilityFromEUTRACommand may contain setup information for new NR QoE settings (6-40), in this case, the AS and APP of the terminal (LTE QoE setup and measurement) (regardless of whether to maintain or not) can save the NR QoE settings and perform and report QoE measurements according to the NR QoE settings, this process can follow 8-65/8-70/8-75/8-80.

In an embodiment of the present invention, in step 6-40, the base station may set the timer length for which the terminal must maintain the LTE QoE settings. The timer settings can be defined in the MobilityFromEUTRACommand message or RRC Reconfiguration message. After successfully performing handover or receiving the message, the terminal can start the timer and maintain LTE QoE settings and measurements while the timer is running. When the timer expires, you can stop measuring LTE QoE and turn off the setting (both in AS and APP). If another handover is performed, the timer can be reset and restarted, or stopped.

The terminal's AS (Access Stratum layer) (7-05) and the terminal's APP (application layer) (7-10) receive LTE QoE measurement configuration information (e.g., QoE config 1) through the LTE base station or cell. It can be a state (7-15, 7-20).

In LTE, a terminal (AS and/or APP) can store and measure only up to one piece of QoE setting information, so a separate ID to distinguish multiple QoE setting information may not be required (in NR, A separate ID may be required to distinguish multiple QoE setting information). Only the terminal (AS and/or APP) can receive information about what service type the QoE configuration information relates to as an indicator (for example, serviceType) and store this indicator or information (7-15, 7 -20).

A terminal with LTE QoE settings (e.g., QoE config 1) may be in RRC connection mode with an LTE base station or cell (7-23). The LTE base station or cell may initiate handover of the terminal. For this purpose, the source LTE base station or cell (s-eNB) (7-23) provides the information necessary for the target NR base station (t-gNB) (7-25) to prepare for handover through a handover preparation information message or HANDOVER REQUEST message. Can be transmitted to t-gNB (7-30). At this time, the message and information can be sent in the format required for the target RAT (Radio access technology) (i.e., NR).

Based on the above information, the t-gNB can generate an RRC reconfiguration message (e.g., RRCReconfiguration) and deliver it to the s-eNB in a handover command message or HANDOVER REQUEST ACKNOWLEDGEMENT message (7-35).

The s-eNB that has received this can transmit the t-gNB's RRC reconfiguration message to the UE in a MobilityFromEUTRACommand message (7-40).

Below is the ASN.1 code of the MobilityFromEUTRACommand message.

The s-eNB can specify that it transmits the MobilityFromEUTRACommand message to the UE for handover by indicating the value of the purpose parameter as handover.

The s-eNB can set the internal parameter values of Handover IE as follows.

1) By setting targetRAT-Type: nr, you can indicate that the target RAT is NR.

3) nas-SecurityParamFromEUTRA: Can be omitted when handover to NR.

4) systemInformation: Can be omitted when handover to NR.

Indicator A can be defined in the MobilityFromEUTRACommand message or RRC Reconfiguration message (7-40). For example, if indicator A is defined in the MobilityFromEUTRACommand message, the s-eNB can set indicator A, and if indicator A is defined in the RRC Reconfiguration message, the t-gNB can set indicator A.

The base station (s-eNB or t-gNB) may wish to cancel QoE measurement and settings in the terminal when performing handover, and may cancel QoE settings of LTE through indicator A. For example, the t-gNB may not support QoE measurement for the service type set for the UE, or the t-gNB may not support QoE measurement because it is a base station or cell outside the QoE measurement area range (e.g., areaScope) set by the OAM. can be released. In addition, new QoE measurements can be set for the terminal immediately after release.

For an embodiment in which the s-eNB determines or generates the configuration of indicator A (e.g., if indicator A is defined in the MobilityFromEUTRACommand message), an indicator for de-configuring QoE from the t-gNB (e.g., indicator B) You can receive (7-35). For example, the By receiving B (7-35), the indicator A transmitted to the terminal can be indicated to cancel the QoE setting (7-40).

After successfully completing the handover, the UE can transmit an RRC Reconfiguration complete message to the t-gNB (7-45).

The terminal AS may release LTE radio resources and/or configuration information after successfully completing handover or transmitting an RRC Reconfiguration complete message. At this time, the terminal AS may also release QoE resources and/or configuration information (e.g., QoE config 1) according to the indicator A received at 7-40. (7-50).

Afterwards, the terminal AS may instruct cancellation of QoE settings in the terminal APP (7-55).

For this purpose, the LTE AT command can be used, which may include an indicator indicating termination and the service type of QoE configuration (for example, the service type of QoE config 1). After this, the terminal APP can stop performing QoE measurement because it no longer has LTE QoE settings (7-60).

As an embodiment of the present invention, if the RRC Reconfiguration message included in MobilityFromEUTRACommand may contain setup information for new NR QoE settings (7-40), in this case, the AS and APP of the terminal (LTE QoE setup and measurement) You can save the NR QoE settings (regardless of whether they are turned off or not) and perform and report QoE measurements according to the NR QoE settings, and this process can follow 8-65/8-70/8-75/8-80.

Indicator A proposed in FIGS. 6 and 7 may be the same indicator, and may be interpreted as one of the following options or a combination thereof. In one embodiment, indicator A may be defined in the MobilityFromEUTRACommand message or RRC Reconfiguration message. “Terminal” referred to in the following options may refer to both AS and APP. Alternatively, it may refer to only one of AS or APP. The procedure for maintaining QoE measurements below can be referred to Figure 6.

The procedure for disabling QoE measurement below can refer to FIG. 7.

- Option 1: This is an OPTIONAL parameter. If this parameter is included, the terminal can maintain (if maintained) the QoE settings in LTE when performing handover to NR. If the corresponding parameter is absent, the terminal can cancel the QoE settings in LTE (if it has them) when performing handover to NR. In one embodiment, the parameter may include sub-parameters.

- Option 2: This is an OPTIONAL parameter. If this parameter is included, the terminal can cancel the QoE setting in LTE (if it has one) when performing handover to NR. If the corresponding parameter is absent, the UE can maintain (if maintained) the QoE settings in LTE when performing handover to NR. In one embodiment, the parameter may include sub-parameters.

- Option 3: This is an OPTIONAL parameter. If this parameter is set to true, the terminal can maintain the QoE settings in LTE when performing handover to NR. If the parameter is set to false, the terminal can cancel the QoE settings in LTE when performing handover to NR. If the corresponding parameter is absent, the terminal may not perform any operation. For example, if the terminal does not have QoE settings, the corresponding parameter may be absent because there are no settings to maintain or release.

- Option 4: This is an OPTIONAL parameter. If this parameter is set to true, the terminal can cancel the QoE settings in LTE when performing handover to NR. If the parameter is set to false, the terminal can maintain QoE settings in LTE when performing handover to NR. If the corresponding parameter is absent, the terminal may not perform any operation. For example, if the terminal does not have QoE settings, the corresponding parameter may be absent because there are no settings to maintain or release.

- Option 5: This is a MANDATORY parameter. If the parameter is set to true, the terminal can maintain the QoE settings in LTE when performing handover to NR. If the parameter is set to false, the terminal can cancel the QoE settings in LTE when performing handover to NR. If the terminal does not have QoE settings, the parameter may be ignored or no operation may be performed regardless of the parameter.

- Option 6: This is a MANDATORY parameter. If the parameter is set to true, the terminal can cancel the QoE settings in LTE when performing handover to NR. If the parameter is set to false, the terminal can maintain QoE settings in LTE when performing handover to NR. If the terminal does not have QoE settings, it may ignore the above parameters or may not perform any operation regardless of the parameters. -

Option 7: As a CHOICE type parameter, you can set “release” and “setup”.

If "release" is set, the terminal can release QoE settings in LTE when performing handover to NR.

If "setup" is set and measConfigAppLayerContainer and/or serviceType in "setup" are set, the terminal can use the corresponding information to cancel the existing LTE QoE settings and set up with the new QoE setting information provided above. That is, the UE can change or modify the existing QoE settings when performing handover to NR. In this case, the terminal's operation to cancel the existing LTE QoE setting may be the same as the operation in 7-50 and 7-55, and some or all of the following operations may be added to set the new QoE.

1) In addition to 7-50, the procedure for the AS to set or save new QoE settings in the AS

2) In addition to 7-55, the procedure for AS to transmit new QoE setting information to APP

3) Using the 6-55/6-60/6-65/6-70 (or 8-65/8-70/8-75/8-80) procedure, the APP sets new QoE setting information and uses it based on this. Procedure for performing and reporting QoE measurements

If the setting for indicator A is defined as an operation by the s-eNB (for example, if indicator A is set in the MobilityFromEUTRACommand message rather than the RRC Reconfiguration message), the new QoE setting may be an LTE QoE setting. If the configuration for indicator A is defined as an operation by the t-gNB (for example, if indicator A is configured in the RRC Reconfiguration message included in the MobilityFromEUTRACommand message), the new QoE configuration may be an NR QoE configuration.

If "setup" is set but measConfigAppLayerContainer and/or serviceType in "setup" are not set, the terminal can maintain the existing LTE QoE settings when performing handover to NR. If indicator A is absent or the terminal does not have QoE settings, the parameter may be ignored or no operation may be performed regardless of the parameter.

For Options 1 and 2, for example, the ASN.1 code for indicator A (e.g., indicatorA) can be defined in Handover IE in MobilityFromEUTRACommand as follows.

For Options 3 and 4, for example, the ASN.1 code for indicator A (e.g., indicatorA) can be defined in Handover IE in MobilityFromEUTRACommand as follows.

For Options 5 and 6, for example, the ASN.1 code for indicator A (e.g., indicatorA) can be defined in Handover IE in MobilityFromEUTRACommand as follows.

For Option 7, for example, the ASN.1 code for indicator A (e.g., indicatorA) can be defined in Handover IE in MobilityFromEUTRACommand as follows.

Indicator B proposed in FIGS. 6 and 7 may be the same indicator, and may be interpreted as one of the following options or a combination thereof. In one embodiment, indicator B may be defined in the HANDOVER REQUEST ACKNOWLEDGEMENT or Handover Command message. The procedure for maintaining QoE measurements below can be referred to Figure 6. The procedure for disabling QoE measurement below can refer to FIG. 7.

- Option 1: This is an OPTIONAL parameter. If the parameter is included, the s-eNB can instruct the UE to maintain (if it has) the QoE settings in LTE when performing handover to NR (e.g. indicator via A). If the parameter is absent, the s-eNB may instruct the UE to release (if retained) QoE settings in LTE when performing handover to NR (e.g., through indicator A). In one embodiment, the parameter may include sub-parameters.

- Option 2: This is an OPTIONAL parameter. If the parameter is included, the s-eNB can instruct the UE to release (if present) the QoE settings in LTE when performing handover to NR (e.g. indicator via A). If the corresponding parameter is absent, the s-eNB may instruct the UE to maintain (if retained) the QoE settings in LTE when performing handover to NR (e.g., through indicator A). In one embodiment, the parameter may include sub-parameters.

- Option 3: This is an OPTIONAL parameter. If the parameter is set to true, the s-eNB can instruct the UE to maintain (if it maintains) the QoE settings in LTE when performing handover to NR (e.g. via indicator A). If the parameter is set to false, the s-eNB may instruct the UE to release (if retained) QoE settings in LTE when performing handover to NR (e.g., through indicator A). If the corresponding parameter is absent, the s-eNB may not set or transmit indicator A to the UE. (i.e. absence of indicator A)

- Option 4: This is an OPTIONAL parameter. If the parameter is set to true, the s-eNB can instruct the UE to release (if present) the QoE settings in LTE when performing handover to NR (e.g. via indicator A). If the parameter is set to false, the s-eNB may instruct the UE to maintain (if maintained) the QoE settings in LTE when performing handover to NR (for example, through indicator A). If the corresponding parameter is absent, the s-eNB may not set or transmit indicator A to the UE. (i.e. absence of indicator A)

- Option 5: This is a MANDATORY parameter, and if the parameter is set to true, the s-eNB can instruct the UE to maintain (if maintained) the QoE settings in LTE when performing handover to NR (e.g. via indicator A). If the parameter is set to false, the s-eNB may instruct the UE to release (if retained) QoE settings in LTE when performing handover to NR (e.g., through indicator A).

- Option 6: This is a MANDATORY parameter. If the parameter is set to true, the s-eNB may instruct the UE to release (if present) QoE settings in LTE when performing handover to NR (e.g. via indicator A). If the parameter is set to false, the s-eNB may instruct the UE to maintain (if maintained) the QoE settings in LTE when performing handover to NR (for example, through indicator A).

- Option 7: This is a CHOICE type parameter where you can set “release” and “setup”.

If "release" is set, the s-eNB may instruct the UE to release (if retained) QoE settings in LTE when performing handover to NR.

If "setup" is set and the QoE setting information of the application layer (information included in measConfigAppLayerContainer in the RRC layer) and/or service type (information included in serviceType in the RRC layer) within "setup" are set, s- The eNB may instruct the terminal to use the information to cancel the existing LTE QoE settings and set up with the new QoE settings information provided above. That is, the s-eNB can instruct the UE to change or modify existing QoE settings when performing handover to NR.

If "setup" is set, but the QoE setting information (information included in measConfigAppLayerContainer in the RRC layer) and/or service type (information included in serviceType in the RRC layer) of the application layer within "setup" are not set, s -eNB may instruct the UE to maintain the existing LTE QoE settings when performing handover to NR.

This option can be defined or used together with option 7 for indicator A.

The terminal's AS (Access Stratum layer) (8-05) and the terminal's APP (application layer) (8-10) receive LTE QoE measurement configuration information (e.g., QoE config 1) through the LTE base station or cell. It can be a state (8-15, 8-20).

In LTE, a terminal (AS and/or APP) can store and measure only up to one piece of QoE setting information, so a separate ID to distinguish multiple QoE setting information may not be required (in NR, A separate ID may be required to distinguish multiple QoE setting information). Only the terminal (AS and/or APP) can receive information about what service type the QoE configuration information relates to as an indicator (for example, serviceType) and store this indicator or information (8-15, 8 -20).

A terminal with LTE QoE settings (e.g., QoE config 1) may be in RRC connection mode with an LTE base station or cell (8-23). The LTE base station or cell may initiate handover of the terminal. For this purpose, the source LTE base station or cell (s-eNB) (8-23) provides the information necessary for the target NR base station (t-gNB) (8-25) to prepare for handover through a handover preparation information message or HANDOVER REQUEST message. Can be transmitted to t-gNB (8-30).

At this time, the message and information can be sent in the format required for the target RAT (Radio access technology) (i.e., NR). Based on the above information, the t-gNB can generate an RRC reconfiguration message (e.g., RRCReconfiguration) and deliver it to the s-eNB in a handover command message or HANDOVER REQUEST ACKNOWLEDGEMENT message (8-35).

The s-eNB that has received this can transmit the t-gNB's RRC reconfiguration message to the UE in a MobilityFromEUTRACommand message (8-40).

Below is the ASN.1 code of the MobilityFromEUTRACommand message.

The s-eNB can set the internal parameter values of Handover IE as follows.

1) By setting targetRAT-Type: nr, you can indicate that the target RAT is NR.

3) nas-SecurityParamFromEUTRA: Can be omitted when handover to NR.

4) systemInformation: Can be omitted when handover to NR.

In one embodiment of the present invention, at the time of handover, the base station updates the QoE settings (e.g., QoE config 1) in LTE held by the terminal to the QoE settings of NR after handover to NR, and provides an indicator ( For example, the directive C) may be defined and/or used. The base station may instruct the base station to update and maintain the QoE settings in LTE (e.g., QoE config 1) to the QoE settings in NR through indicator C (8-40).

Unlike LTE QoE settings, in NR QoE settings, ID (e.g., measConfgiAppLayerID) and additional setting information (e.g., pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) can be set together. Considering that the terminal stores this, if the base station instructs the base station to update and maintain the QoE settings in LTE (e.g., QoE config 1) to the QoE settings in NR through indicator C, the QoE setting ID (e.g. For example, measConfgiAppLayerID) and/or additional setting information (e.g., pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) can be newly defined and assigned (8-40).

Alternatively, for this purpose, the measConfigAppLayerId of the conventional RRCReconfiguration and/or parameters for additional configuration information can be reused. At this time, the terminal can maintain or reuse the APP QoE measurement setting information (e.g., measConfigAppLayerContainer) and/or service type (e.g., serviceType) set in LTE, so the base station maintains the APP's QoE measurement setting information and/or service. The type may not be set to the terminal. The indicator C and/or QoE configuration ID and/or additional configuration information may be defined in the MobilityFromEUTRACommand message or RRC Reconfiguration message (8-40).

For example, if the indicator C and/or QoE configuration ID and/or additional configuration information are defined in the MobilityFromEUTRACommand message, the s-eNB may set the indicator C and/or QoE configuration ID and/or additional configuration information. If the indicator C and/or QoE configuration ID and/or additional configuration information are defined in the RRC Reconfiguration message, the t-gNB may set the indicator C and/or QoE configuration ID and/or additional configuration information.

The base station (s-eNB or t-gNB) may want to perform continuous QoE measurement without interruption in the terminal even if handover is performed, and can maintain the LTE QoE settings by updating them to NR QoE settings through indicator C. For example, t-gNB supports QoE measurement of the service type set for the UE, and can maintain QoE settings because it is a base station or cell included in the QoE measurement area range (e.g., areaScope) set by the OAM.

For an embodiment in which the s-eNB determines or generates the settings of indicator C (e.g., if indicator C is defined in the MobilityFromEUTRACommand message), an indicator for maintaining QoE settings from the t-gNB (e.g., indicator D) You can receive (8-35).

For example, the By receiving D (8-35), maintenance of the QoE settings of the terminal can be instructed through the indicator C transmitted to the terminal (8-40).

For embodiments where the s-eNB determines or generates settings of a QoE configuration ID (e.g., measConfgiAppLayerID) and/or additional configuration information (e.g., pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) (e.g., MobilityFromEUTRACommand message (if the QoE configuration ID and/or additional configuration information are defined), the QoE configuration ID and/or additional configuration information may be received from the t-gNB (8-35).

For example, the The corresponding band can define parameters), and the s-eNB receives the information from the t-gNB through a HANDOVER REQUEST ACKNOWLEDGEMENT or Handover Command message (8-35), and provides a QoE configuration ID (e.g., measConfgiAppLayerID) to the terminal. ) and/or additional configuration information (e.g., pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) may be passed (8-40).

In an embodiment of the present invention, the base station may cancel the LTE QoE settings and then transmit the same NR QoE settings (e.g., the same measConfigAppLayerContainer) to the terminal, but for this, the base station may transmit the terminal's QoE settings information (e.g. For example, measConfigAppLayerContainer) must be stored and transmitted back to the terminal, and the terminal AS must also transmit it back to the terminal APP. Considering that the size of the RRC message of QoE configuration information is not small, this may be very inefficient in terms of signaling and energy consumption for the terminal or base station. For example, measConfigAppLayerContainer can occupy up to 1000 bytes in LTE and up to 8000 bytes in NR. In addition, the method of canceling and resetting the QoE settings described above does not allow QoE measurement to be performed continuously. Therefore, in the present invention, continuous QoE measurement is achieved by maintaining (or reusing) the terminal's QoE configuration information (for example, measConfigAppLayerContainer) rather than releasing it during inter-RAT handover, while reducing signaling overhead and maintaining the communication between the terminal and the base station. It can help reduce energy consumption.

In one embodiment of the present invention, indicator C may not be defined in 8-40, and indicator D may not be defined in 8-35. Instead, in 8-40, the base station may use a QoE configuration ID (e.g., measConfgiAppLayerID) and/or additional configuration information (e.g., measConfgiAppLayerID) without APP QoE measurement configuration information (e.g., measConfigAppLayerContainer) and/or service type (e.g., serviceType). For example, only pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) can be newly set to the terminal, and the terminal maintains or reuses the existing LTE QoE settings (APP QoE measurement setting information and service type) and sets the QoE setting ID and/or Alternatively, it can be understood to mean updating the LTE QoE settings to NR QoE settings using additional setting information.

After successfully completing the handover, the UE can transmit an RRC Reconfiguration complete message to the t-gNB (8-45). The terminal AS may release LTE radio resources and/or configuration information after successfully completing handover or transmitting an RRC Reconfiguration complete message. At this time, the terminal AS may also release LTE QoE resources and/or configuration information (e.g., QoE config 1) (8-50).

Afterwards, the terminal is instructed to update the QoE settings of LTE to NR QoE settings through indicator C and/or QoE setting ID (e.g., measConfgiAppLayerID) and/or additional setting information (e.g., pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters). Able to understand instructions from the base station, and accordingly set NR QoE configuration information, including QoE configuration ID (e.g., measConfgiAppLayerID) and/or additional configuration information (e.g., pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) to the AS; or Can be saved (8-52).

Afterwards, the terminal AS can transmit the QoE configuration ID and/or additional configuration information to the APP through the NR AT command (8-55).

In addition, a new indicator The indicator ).

The terminal that received the NR AT command and the information (indicator (e.g., measConfigAppLayerContainer) and/or service type (e.g., serviceType), but also include a QoE configuration ID (e.g., measConfgiAppLayerID) and/or additional configuration information (e.g., pauseReporting, transmissionOfSessionStartStop, The LTE QoE settings can be updated to the NR QoE settings by adding ran-VisibleParameters (8-60).

Afterwards, the terminal can perform QoE measurement using the NR QoE settings (8-65).

Accordingly, the terminal APP can generate a QoE report and deliver it to the terminal AS. At this time, the NR AT command can be used, and the QoE measurement result generated by measurement by the terminal APP may be reported and may include the stored QoE setting ID (for example, measConfgiAppLayerID) (8-70).

In addition, it may include an indicator indicating whether to start or end an APP session according to the transmissionOfSessionStartStop setting and/or RAN visible QoE measurement result reporting information according to the ran-VisibleParameters setting. The terminal AS that has received the QoE report including the above information from the terminal APP can transmit the QoE report to the base station (t-gNB) that has completed the handover (8-75).

At this time, the QoE reporting message defined in NR (eg, MeasurementReportAppLayer message) can be used. SRB3 or SRB4 can be used to transmit the message. The QoE report message (e.g., MeasurementReportAppLayer message) defined in NR may include a container (e.g., measurementReportAppLayerContainer) that stores the QoE report made in the APP with NR QoE settings, and the service type (e.g., serviceType ) may instead include a QoE configuration ID (e.g., measConfigAppLayerId). In addition, it includes an indicator indicating whether to start or end an APP session according to the transmissionOfSessionStartStop setting (e.g., appLayerSessionStatus) and/or RAN visible QoE measurement result reporting information (e.g., ran-VisibleMeasurements) according to the ran-VisibleParameters setting. You may. The t-gNB can forward the QoE report received at 8-65 to the TCE or MCE (8-80).

As an example of the present invention, setup information for new NR QoE settings may be included in the RRC Reconfiguration message included in MobilityFromEUTRACommand (8-40). In this case, the terminal's AS and APP save the new NR QoE settings (regardless of whether the LTE QoE settings and measurements are maintained and updated to NR settings) and (additionally) perform and report QoE measurements according to the new NR QoE settings. (Multiple NR QoE settings are possible), and this process can follow 8-65/8-70/8-75/8-80.

In an embodiment of the present invention, in step 8-40, the base station may set the timer length for which the terminal must maintain the LTE QoE settings. The timer settings can be defined in the MobilityFromEUTRACommand message or RRC Reconfiguration message. After successfully performing a handover or receiving the message, the terminal can start the timer, maintain the NR QoE settings with updated LTE QoE settings while the timer is running, and perform measurements accordingly. Afterwards, when the timer expires, NR QoE measurement can no longer be stopped and the corresponding setting can be canceled (in both AS and APP). If another handover is performed, the timer can be reset and restarted, or stopped.

The terminal's AS (Access Stratum layer) (9-05) and the terminal's APP (application layer) (9-10) receive LTE QoE measurement configuration information (e.g., QoE config 1) through the LTE base station or cell. It can be a state (9-15, 9-20). In LTE, a terminal (AS and/or APP) can store and measure only up to one piece of QoE setting information, so a separate ID to distinguish multiple QoE setting information may not be required (in NR, A separate ID may be required to distinguish multiple QoE setting information). Only the terminal (AS and/or APP) can receive information about what service type the QoE configuration information relates to as an indicator (for example, serviceType) and store this indicator or information (9-15, 9 -20). A terminal with LTE QoE settings (e.g., QoE config 1) may be in RRC connection mode with an LTE base station or cell (9-23).

The LTE base station or cell may initiate handover of the terminal. For this purpose, the source LTE base station or cell (s-eNB) (9-23) provides the information necessary for the target NR base station (t-gNB) (9-25) to prepare for handover through a handover preparation information message or HANDOVER REQUEST message. Can be transmitted to t-gNB (9-30). At this time, the message and information can be sent in the format required for the target RAT (Radio access technology) (i.e., NR).

Based on the above information, the t-gNB can generate an RRC reconfiguration message (e.g., RRCReconfiguration) and deliver it to the s-eNB in a handover command message or HANDOVER REQUEST ACKNOWLEDGEMENT message (9-35). The s-eNB that has received this can transmit the t-gNB's RRC reconfiguration message to the UE in a MobilityFromEUTRACommand message (9-40). Below is the ASN.1 code of the MobilityFromEUTRACommand message.

The s-eNB can set the internal parameter values of Handover IE as follows.

1) By setting targetRAT-Type: nr, you can indicate that the target RAT is NR.

3) nas-SecurityParamFromEUTRA: Can be omitted when handover to NR.

4) systemInformation: Can be omitted when handover to NR. In one embodiment of the present invention, at the time of handover, the base station updates the QoE settings (e.g., QoE config 1) in LTE held by the terminal to the QoE settings of NR after handover to NR, and provides an indicator ( For example, the directive C) may be defined and/or used. The base station may instruct to release QoE settings (e.g., QoE config 1) in LTE through indicator C (9-40). Unlike LTE QoE settings, in NR QoE settings, ID (e.g., measConfgiAppLayerID) and additional setting information (e.g., pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) can be set together.

When the base station instructs to release the QoE setting (e.g., QoE config 1) in LTE through indicator C, the QoE setting ID (e.g., measConfgiAppLayerID) and/or additional configuration information (e.g., pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) can be omitted because there is no need to allocate (9-40). That is, the parameters are defined to maintain the LTE settings as shown in FIG. 8, but in case of cancellation of the LTE settings as shown in FIG. 9, the parameters may not be assigned (e.g., the parameters are defined as optional fields. and may not be included in 9-40).

The indicator C can be defined in the MobilityFromEUTRACommand message or RRC Reconfiguration message (9-40). For example, if the indicator C is defined in the MobilityFromEUTRACommand message, the s-eNB can set the indicator C, and if the indicator C is defined in the RRC Reconfiguration message, the t-gNB can set the indicator C.

The base station (s-eNB or t-gNB) may wish to cancel QoE measurement and settings in the terminal when performing handover, and may cancel QoE settings of LTE through indicator C. For example, the t-gNB may not support QoE measurement for the service type set for the UE, or the t-gNB may not support QoE measurement because it is a base station or cell outside the QoE measurement area range (e.g., areaScope) set by the OAM. can be released. Additionally, a new QoE measurement can be set for the terminal immediately after release.

For an embodiment in which the s-eNB determines or generates the configuration of indicator C (e.g., if indicator C is defined in the MobilityFromEUTRACommand message), an indicator for QoE release from the t-gNB (e.g., indicator D) You can receive (9-35).

For example, the By receiving D (9-35), the indicator C transmitted to the terminal can indicate cancellation of the terminal's QoE settings (9-40).

When the t-gNB instructs the s-eNB to release QoE settings (e.g., QoE config 1) in LTE through indicator D, the QoE configuration ID (e.g., measConfgiAppLayerID) and/or additional configuration information ( For example, pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) may not be assigned because they do not need to be assigned (9-35).

In one embodiment of the present invention, indicator C may not be defined at 9-40, and indicator D may not be defined at 9-35. Instead, in 9-40 a QoE configuration ID (e.g. measConfgiAppLayerID) and/or additional configuration information (e.g. pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) are defined, but the base station does not set these parameters (e.g. , the parameters are defined as optional fields and the base station does not include the parameters), and the terminal can understand this to mean canceling the existing LTE QoE settings (APP QoE measurement setting information and service type).

After successfully completing the handover, the UE can transmit an RRC Reconfiguration complete message to the t-gNB (9-45). The terminal AS may release radio resources and/or settings of LTE after successfully completing handover or transmitting an RRC Reconfiguration complete message. At this time, the terminal AS may also release QoE resources and/or settings according to the indicator A received at 9-40. (9-50).

Likewise, the terminal AS can instruct cancellation of QoE settings in the terminal APP (9-55). For this purpose, the LTE AT command can be used, which may include an indicator indicating termination and the service type of QoE configuration (for example, the service type of QoE config 1).

After this, the terminal APP can stop performing QoE measurement because it no longer has LTE QoE settings (9-60).

As an example of the present invention, setup information for new NR QoE settings may be included in the RRC Reconfiguration message included in MobilityFromEUTRACommand (9-40). In this case, the terminal's AS and APP can save the new NR QoE settings (regardless of whether the LTE QoE settings and measurements are released) and (additionally) perform and report QoE measurements according to the new NR QoE settings, and this process can follow 8-65/8-70/8-75/8-80.

The indicator C proposed in FIGS. 8 and 9 may be the same indicator, and may be interpreted as one of the following options or a combination thereof. In one embodiment, indicator C may be defined in the MobilityFromEUTRACommand message or RRC Reconfiguration message. “Terminal” referred to in the following options may refer to both AS and APP. Alternatively, it may refer to only one of AS or APP. In the following, the procedure for maintaining and updating QoE measurements (meaning updating to NR QoE settings) may refer to FIG. 8. The procedure for disabling QoE measurement below can refer to FIG. 9.

- Option 1: This is an OPTIONAL parameter. If this parameter is included, the terminal can maintain or update (if present) the QoE settings in LTE when performing handover to NR. If the corresponding parameter is absent, the terminal can cancel the QoE settings in LTE (if it has them) when performing handover to NR. In one embodiment, the parameter may include sub-parameters.

- Option 2: This is an OPTIONAL parameter. If this parameter is included, the terminal can cancel the QoE setting in LTE (if it has one) when performing handover to NR. If the parameter is absent, the UE can maintain or update (if it has) QoE settings in LTE when performing handover to NR. In one embodiment, the parameter may include sub-parameters.

- Option 3: This is an OPTIONAL parameter. If this parameter is set to true, the terminal can maintain or update the QoE settings in LTE when performing handover to NR. If the parameter is set to false, the terminal can cancel the QoE settings in LTE when performing handover to NR. If the corresponding parameter is absent, the terminal may not perform any operation. For example, if the terminal does not have QoE settings, the corresponding parameter may be absent because there are no settings to maintain, update, or release.

- Option 4: This is an OPTIONAL parameter. If this parameter is set to true, the terminal can cancel the QoE settings in LTE when performing handover to NR. If the parameter is set to false, the terminal can maintain or update QoE settings in LTE when performing handover to NR. If the corresponding parameter is absent, the terminal may not perform any operation. For example, if the terminal does not have QoE settings, the corresponding parameter may be absent because there are no settings to maintain, update, or release.

- Option 5: This is a MANDATORY parameter. If the parameter is set to true, the terminal can maintain or update the QoE settings in LTE when performing handover to NR. If the parameter is set to false, the terminal can cancel the QoE settings in LTE when performing handover to NR. If the terminal does not have QoE settings, the parameter may be ignored or no operation may be performed regardless of the parameter.

- Option 6: This is a MANDATORY parameter. If the parameter is set to true, the terminal can cancel the QoE settings in LTE when performing handover to NR. If the parameter is set to false, the terminal can maintain or update QoE settings in LTE when performing handover to NR. If the terminal does not have QoE settings, the parameter may be ignored or no operation may be performed regardless of the parameter.

If "setup" is set and measConfigAppLayerContainer and/or serviceType in "setup" are set, the terminal can use the corresponding information to cancel the existing LTE QoE settings and setup with the new QoE setting information provided above. That is, the UE can change or modify the existing QoE settings when performing handover to NR. In this case, the terminal's operation to cancel the existing LTE QoE settings may be the same as the operations in 9-50 and 9-55, and some or all of the operations below may be added for new QoE settings.

4) In addition to 9-50, the procedure for the AS to set or save new QoE settings in the AS

5) In addition to 9-55, the procedure for AS to transmit new QoE setting information (including measConfigAppLayerContainer) to APP

6) Procedure for APP to set new QoE setting information (including measConfigAppLayerContainer) and perform and report QoE measurement based on this

If the setting for indicator C is defined as an operation by the s-eNB (for example, if the indicator C is set in the MobilityFromEUTRACommand message rather than the RRC Reconfiguration message), the new QoE setting may be an LTE QoE setting. If the configuration for indicator C is defined as an operation by the t-gNB (for example, if indicator C is configured in the RRC Reconfiguration message included in the MobilityFromEUTRACommand message), the new QoE configuration may be an NR QoE configuration.

If "setup" is set but measConfigAppLayerContainer and/or serviceType in "setup" are not set, the terminal can maintain or update the existing LTE QoE settings when performing handover to NR. If indicator C is absent or the terminal does not have QoE settings, the parameter may be ignored or no operation may be performed regardless of the parameter.

For Options 1 and 2, for example, the ASN.1 code for indicator C (e.g., indicatorC) can be defined in Handover IE in MobilityFromEUTRACommand as follows.

For Options 3 and 4, for example, the ASN.1 code for indicator C (e.g., indicatorC) can be defined in Handover IE in MobilityFromEUTRACommand as follows.

For Options 5 and 6, for example, the ASN.1 code for indicator C (e.g., indicatorC) can be defined in Handover IE in MobilityFromEUTRACommand as follows.

For Option 7, for example, an ASN.1 code for indicator C (e.g., indicatorC) can be defined in Handover IE in MobilityFromEUTRACommand as follows.

The indicator D proposed in FIGS. 8 and 9 may be the same indicator, and may be interpreted as one of the following options or a combination thereof. In one embodiment, indicator D may be defined in the HANDOVER REQUEST ACKNOWLEDGEMENT or Handover Command message. In the following, the procedure for maintaining or updating QoE measurements (meaning updating LTE QoE settings to NR settings) can refer to FIG. 8. The procedure for disabling QoE measurement below can refer to FIG. 9.

- Option 1: This is an OPTIONAL parameter. If the parameter is included, the s-eNB can instruct the UE to maintain or update (if present) the QoE settings in LTE when performing handover to NR (e.g. For (via directive C). If the corresponding parameter is absent, the s-eNB may instruct the UE to release (if retained) QoE settings in LTE when performing handover to NR (e.g., through indicator C). In one embodiment, the parameter may include sub-parameters.

- Option 2: This is an OPTIONAL parameter. If the parameter is included, the s-eNB can instruct the UE to release (if present) the QoE settings in LTE when performing handover to NR (e.g. indicator via C). If the corresponding parameter is absent, the s-eNB may instruct the UE to maintain or update (if present) the QoE settings in LTE when performing handover to NR (e.g., through indicator C). In one embodiment, the parameter may include sub-parameters.

- Option 3: This is an OPTIONAL parameter. If the parameter is set to true, the s-eNB can instruct the UE to maintain or update (if present) the QoE settings in LTE when performing handover to NR (e.g. For example via directive C). If the parameter is set to false, the s-eNB may instruct the UE to release (if retained) QoE settings in LTE when performing handover to NR (e.g., through indicator C). If the corresponding parameter is absent, the s-eNB may not set or transmit indicator C to the UE. (i.e. absence of indicator C)

- Option 4: This is an OPTIONAL parameter. If the parameter is set to true, the s-eNB can instruct the UE to release (if present) the QoE settings in LTE when performing handover to NR (e.g. via indicator C). If the parameter is set to false, the s-eNB may instruct the UE to maintain or update (if present) the QoE settings in LTE when performing handover to NR (e.g., through indicator C). If the corresponding parameter is absent, the s-eNB may not set or transmit indicator C to the UE. (i.e. absence of indicator C)

- Option 5: This is a MANDATORY parameter. If the parameter is set to true, the s-eNB can instruct the UE to maintain or update (if present) the QoE settings in LTE when performing handover to NR (e.g. For example via directive C). If the parameter is set to false, the s-eNB may instruct the UE to release (if retained) QoE settings in LTE when performing handover to NR (e.g., through indicator C).

- Option 6: This is a MANDATORY parameter. If the parameter is set to true, the s-eNB may instruct the UE to release (if present) QoE settings in LTE when performing handover to NR (e.g. via indicator C). If the parameter is set to false, the s-eNB may instruct the UE to maintain or update (if present) the QoE settings in LTE when performing handover to NR (e.g., through indicator C).

If "setup" is set and the QoE setting information of the application layer (information included in measConfigAppLayerContainer in the RRC layer) and/or service type (information included in serviceType in the RRC layer) within "setup" are set, s- The eNB may instruct the terminal to use the information to cancel the existing LTE QoE settings and set up with the new QoE settings information provided above. That is, the s-eNB can instruct the UE to change or modify existing QoE settings (including measConfigAppLayerContainer) when performing handover to NR.

If "setup" is set, but the QoE setting information (information included in measConfigAppLayerContainer in the RRC layer) and/or service type (information included in serviceType in the RRC layer) of the application layer within "setup" are not set, s -eNB may instruct the UE to maintain existing LTE QoE settings (including measConfigAppLayerContainer) when performing handover to NR.

This option can be defined or used together with option 7 for indicator C.

The AS (Access Stratum layer) (10-05) of the terminal and the APP (application layer) (10-10) of the terminal provide one or more NR QoE measurement setting information (e.g., QoE config 1, QoE config 2, QoE config 3) may have been set (10-15, 10-20). In NR, a terminal (AS and/or APP) can store multiple QoE configuration information and perform measurements independently, so define a separate ID (e.g., measConfigAppLayerId) to distinguish multiple QoE configuration information and /or can be used. (In LTE, only a single QoE setting is possible for the terminal, so a separate ID that distinguishes multiple QoE setting information may not be used.) The terminal (AS and/or APP) can store the QoE setting ID for each QoE setting (10-15, 10-20). A UE with NR QoE settings (e.g., QoE config 1/2/3) may be in RRC connected mode with an NR base station or cell (10-23). The NR base station or cell can initiate handover of the terminal. For this purpose, the source NR base station or cell (s-gNB) (10-23) provides the information necessary for the target LTE base station (t-eNB) (10-25) to prepare for handover through a handover preparation information message or a HANDOVER REQUEST message. Can be transmitted to t-eNB (10-30). At this time, the message and information can be sent in the format required for target RAT (Radio access technology) (i.e., LTE).

Based on the above information, the t-eNB can generate an RRC Connection Reconfiguration message (e.g., RRCConnectionReconfiguration) and deliver it to the s-gNB in a handover command message or HANDOVER REQUEST ACKNOWLEDGEMENT message (10-35).

The s-gNB that has received this can transmit the t-eNB's RRC Connection Reconfiguration message to the UE in a MobilityFromNRCommand message (10-40). Below is the ASN.1 code of the MobilityFromNRCommand message.

The s-gNB can instruct the UE by transmitting a MobilityFromNRCommand message.

The s-gNB can set parameter values within the MobilityFromNRCommand message as follows.

1) By setting targetRAT-Type: eutra, you can indicate that the target RAT is EUTRA (i.e. LTE).

2) targetRAT-MessageContainer: Can contain the RRC Connection Reconfiguration message generated by the t-eNB.

3) nas-SecurityParamFromNR: Can be omitted during Intra-5GC handover.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. A QoE configuration ID (e.g., measConfigAppLayerId) may be defined and/or used to instruct the terminal about one QoE configuration (e.g., QoE config 2) to be maintained. For example, QoE config 2 may be a QoE setting with measConfigAppLayerId=2, and the base station (s-gNB or t-eNB) may set QoE settings in a plurality of NRs held by the UE (e.g., QoE config 1/2/ 3) In order to indicate to the terminal one QoE setting (e.g., QoE config 2) to be maintained after handover to LTE, a QoE configuration ID (e.g., measConfigAppLayerId=2) can be indicated or set (10- 40). In one embodiment of the present invention, the base station can indicate a plurality of QoE setting IDs, and in this case, the terminal can maintain the plurality of QoE settings indicated after handover to LTE.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. Afterwards, a QoE configuration ID (e.g., measConfigAppLayerId) can be defined and/or used to instruct the terminal about the QoE configuration (QoE config 1/3) to be released. Alternatively, for this purpose, the measConfigAppLayerId of the existing RRCConnectionReconfiguration can be reused. For example, QoE config 1/3 may be a QoE setting with measConfigAppLayerId=4/6, and the base station (s-gNB or t-eNB) may set QoE settings in a plurality of NRs held by the UE (e.g., QoE Instructs the QoE setting ID (e.g., measConfigAppLayerId=4/6) to instruct the terminal which QoE setting (e.g., QoE config 1/3) to be released after handover to LTE among config 1/2/3) Or you can set it.

The QoE configuration ID can be defined in the MobilityFromNRCommand message or RRC Connection Reconfiguration message (10-40). For example, if the QoE configuration ID is defined in the MobilityFromNRCommand message, the s-gNB can set the QoE configuration ID, and if the QoE configuration ID is defined in the RRC Connection Reconfiguration message, the t-eNB can set the QoE configuration ID. there is.

Even if handover is performed, the base station (s-gNB or t-eNB) may want to perform continuous QoE measurement without interruption in the terminal, and can maintain the QoE settings of the NR through the indication of the QoE setting ID. For example, t-eNB supports QoE measurement of the service type set for the UE, and can maintain QoE settings because it is a base station or cell included in the QoE measurement area range (e.g., areaScope) set by the OAM.

In one embodiment of the present invention, in the case of an embodiment in which the s-gNB determines or generates the setting of the QoE setting ID (e.g., when the QoE setting ID is defined in the MobilityFromNRCommand message), the QoE setting is maintained from the t-eNB You can receive the desired QoE setting ID (for example, measConfigAppLayerId=2) (10-35). For example, the The s-gNB receives the QoE setting ID for which QoE settings are desired to be maintained from the t-eNB through a HANDOVER REQUEST ACKNOWLEDGEMENT or Handover Command message (10-35) and maintains the specific QoE settings of the terminal through the QoE setting ID transmitted to the terminal. Can be indicated (10-40).

In one embodiment of the present invention, in the case of an embodiment in which the s-gNB determines or generates the setting of the QoE setting ID (for example, when the QoE setting ID is defined in the MobilityFromNRCommand message), the QoE setting is released from the t-eNB You can receive the desired QoE setting ID (for example, measConfigAppLayerId=4/6) (10-35). For example, the By receiving the QoE setting ID for which the setting is to be canceled (10-35), cancellation of the specific QoE setting of the terminal can be instructed through the QoE setting ID transmitted to the terminal (10-40).

In one embodiment of the present invention, the base station may cancel all QoE settings (e.g., QoE config 1/2/3) and then transmit some of the same settings (e.g., QoE config 2) to the terminal. To do this, the base station must store QoE setting information (for example, measConfigAppLayerContainer) for each QoE setting of the terminal and transmit it back to the terminal, and the terminal AS must also transmit it back to the terminal APP. Considering that the size of the RRC message of QoE configuration information is not small, this may be very inefficient in terms of signaling and energy consumption for the terminal or base station. For example, measConfigAppLayerContainer can occupy up to 1000 bytes in NR and up to 8000 bytes in LTE. In addition, the method of canceling and resetting the QoE settings described above does not allow QoE measurement to be performed continuously. Therefore, in the present invention, continuous QoE measurement is achieved by maintaining (reusing) the terminal's QoE configuration information (for example, measConfigAppLayerContainer) rather than releasing it during inter-RAT handover, while reducing signaling overhead and energy consumption of the terminal and base station. It can help reduce consumption.

After successfully completing the handover, the UE can transmit an RRC Connection Reconfiguration complete message to the t-eNB (10-45). The terminal AS may release the radio resources and/or settings of the NR after successfully completing handover or sending an RRC Connection Reconfiguration complete message (e.g., QoE config 1/3). However, at this time, the terminal AS may use exceptional QoE resources and/or settings (e.g., one or multiple QoE settings instructed) (e.g., QoE config 2) depending on the presence of the QoE configuration ID received from 10-40. You can maintain it without releasing it (10-50). In other words, even if the terminal performs handover to LTE, the NR QoE settings may be stored and maintained. The terminal can maintain the NR QoE settings (multiple possible) separately from the LTE QoE settings (maximum 1). Alternatively, the terminal can maintain only a maximum of one NR QoE setting and LTE QoE setting combined. Afterwards, the terminal AS may notify the terminal APP of the release of QoE settings (e.g., QoE config 1/3) that it has not been instructed to maintain (10-55). At this time, the NR AT command can be used, and the QoE configuration ID of QoE settings that are not instructed to be maintained (e.g., QoE config 1/3) can be indicated (10-55). Accordingly, the terminal APP can release QoE settings that it has not been instructed to maintain (for example, QoE config 1/3). In the terminal APP, the QoE settings instructed to be maintained (e.g., QoE config 2) are maintained and QoE measurement can be performed accordingly (10-60). Accordingly, the terminal APP can generate a QoE report and deliver it to the terminal AS (10-65). At this time, the NR AT command can be used, which includes reporting the QoE measurement results generated by measuring according to the QoE settings that the terminal APP has been instructed to maintain (e.g., QoE config 2) and the ID of the QoE settings (e.g. , measConfigAppLayerId=2) (10-65). The terminal AS that has received the QoE report from the terminal APP can transmit the QoE report to the base station (t-eNB) that has completed the handover (10-70). At this time, the QoE reporting message defined in LTE (for example, MeasReportAppLayer message) can be used. SRB3 or SRB4 can be used to transmit the message. The QoE report message (e.g., MeasReportAppLayer message) defined in conventional LTE may include a container (e.g., measReportAppLayerContainer) that stores the QoE report created in the APP with LTE QoE settings, and the service type (e.g., serviceType). In one embodiment of the present invention, a container (e.g., measReportAppLayerContainer-NR) and/or QoE settings for storing QoE reports made in an APP with NR QoE settings within a QoE report message (e.g., MeasReportAppLayer message) defined in LTE You can additionally define an ID (e.g., measConfigAppLayerId-NR) and set it using the information received in 10-65. In one embodiment of the present invention, the terminal transmits the information received at 10-65 to the base station (e.g., t-eNB) using the QoE reporting message (e.g., MeasurementReportAppLayer message) defined in NR at 10-70. ) can be reported to. The t-eNB can forward the QoE report received at 10-70 to the TCE or MCE (10-75).

As an embodiment of the present invention, if the RRC Connection Reconfiguration message included in MobilityFromNRCommand may contain setup information for new LTE QoE settings (10-40), in this case, the AS and APP of the terminal (NR QoE setup and measurement (regardless of whether to maintain or not) can save the LTE QoE settings and perform and report QoE measurements according to the LTE QoE settings, this process can follow 12-65/12-70/12-75/12-80 .

In an embodiment of the present invention, in steps 10-40, the base station may set the timer length for which the terminal must maintain the NR QoE settings. The timer setting can be defined in the MobilityFromNRCommand message or RRC Connection Reconfiguration message. After successfully performing a handover or receiving the above message, the terminal can start the timer and maintain NR QoE settings and measurements while the timer is running. When the timer expires, it no longer stops measuring NR QoE and You can turn off the setting (both in AS and APP). If another handover is performed, the timer can be reset and restarted, or stopped.

The AS (Access Stratum layer) (11-05) of the terminal and the APP (application layer) (11-10) of the terminal provide one or more NR QoE measurement configuration information (e.g., QoE config 1, QoE config 2, QoE config 3) may have been set (11-15, 11-20). In NR, a terminal (AS and/or APP) can store multiple QoE configuration information and perform measurements independently, so define a separate ID (e.g., measConfigAppLayerId) to distinguish multiple QoE configuration information and /or can be used. (In LTE, only a single QoE setting is possible for the terminal, so a separate ID that distinguishes multiple QoE setting information may not be used.)

The terminal (AS and/or APP) can store the QoE setting ID for each QoE setting (11-15, 11-20). A UE with NR QoE settings (e.g., QoE config 1/2/3) may be in RRC connected mode with an NR base station or cell (11-23).

The NR base station or cell can initiate handover of the terminal. For this purpose, the source NR base station or cell (s-gNB) (11-23) provides the information necessary for the target LTE base station (t-eNB) (11-25) to prepare for handover through a handover preparation information message or HANDOVER REQUEST message. Can be transmitted to t-eNB (11-30). At this time, the message and information can be sent in the format required for target RAT (Radio access technology) (i.e., LTE).

Based on the above information, the t-eNB can generate an RRC Connection Reconfiguration message (e.g., RRCConnectionReconfiguration) and deliver it to the s-gNB in a handover command message or HANDOVER REQUEST ACKNOWLEDGEMENT message (11-35). The s-gNB that has received this can transmit the t-eNB's RRC Connection Reconfiguration message to the UE in a MobilityFromNRCommand message (11-40). Below is the ASN.1 code of the MobilityFromNRCommand message.

The s-gNB can instruct the UE by transmitting a MobilityFromNRCommand message.

3) nas-SecurityParamFromNR: Can be omitted during Intra-5GC handover.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal to LTE. Afterwards, you can use the QoE setting ID (for example, measConfigAppLayerId) to cancel it all, and you can indicate the QoE setting ID you want to release. For example, QoE config 1/2/3 held by the terminal may be a QoE setting with measConfigAppLayerId of 4/2/6, respectively, and the base station (s-gNB or t-eNB) can configure A plurality of QoE setting IDs to instruct the terminal which QoE settings (e.g., QoE config 1/2/3) to be released after handover to LTE among the QoE settings (e.g., QoE config 1/2/3) (For example, measConfigAppLayerId=4/2/6) can be indicated or set.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal to LTE. You can then indicate the QoE setting ID you want to maintain. At this time, in order to cancel the QoE setting in all NRs, the QoE setting ID (e.g., measConfigAppLayerId) may not be included (i.e., the QoE setting ID must be entered in the OPTIONAL field). defined as ). For example, in order to release all QoE config 1/2/3 held by the terminal, the base station may not include the QoE configuration ID (11-40).

The QoE configuration ID can be defined in the MobilityFromNRCommand message or RRC Connection Reconfiguration message (11-40). For example, if the QoE configuration ID is defined in the MobilityFromNRCommand message, the s-gNB can set the QoE configuration ID, and if the QoE configuration ID is defined in the RRC Connection Reconfiguration message, the t-eNB can set the QoE configuration ID. there is.

When performing a handover, the base station (s-gNB or t-eNB) may wish to cancel the QoE measurement and settings in the terminal, and may cancel the QoE settings of the NR through the indication of the QoE setting ID. For example, the t-eNB may not support QoE measurement for the service type set for the UE, or the t-eNB may not support QoE measurement because it is a base station or cell outside the QoE measurement area range (e.g., areaScope) set by the OAM. can be released. In addition, new QoE measurements can be set for the terminal immediately after release.

In one embodiment of the present invention, in the case of an embodiment in which the s-gNB determines or generates the setting of the QoE setting ID (e.g., when the QoE setting ID is defined in the MobilityFromNRCommand message), QoE setting from the t-eNB You may receive a message without the QoE setting ID you want to maintain (11-35). For example, the A HANDOVER REQUEST ACKNOWLEDGEMENT or Handover Command message can be received (11-35), and accordingly, the cancellation of all QoE settings transmitted to the terminal can be instructed (11-40).

In one embodiment of the present invention, in the case of an embodiment in which the s-gNB determines or generates the setting of the QoE setting ID (e.g., when the QoE setting ID is defined in the MobilityFromNRCommand message), QoE setting from the t-eNB You can receive a message containing the QoE setting ID you want to cancel (11-35). For example, the For example, a HANDOVER REQUEST ACKNOWLEDGEMENT or Handover Command message containing (measConfigAppLayerId=4/2/6) can be received (11-35), and accordingly, the cancellation of all QoE settings transmitted to the terminal can be instructed (11 -40).

After successfully completing the handover, the UE can transmit an RRC Connection Reconfiguration complete message to the t-eNB (11-45). The terminal AS may release the NR's radio resources and/or configuration information after successfully completing handover or sending an RRC Connection Reconfiguration complete message. At this time, the terminal AS also releases all QoE resources and/or configuration information (e.g., QoE config 1/2/3) according to the information received from 11-40 (e.g., absence of QoE setting ID to maintain). You can. (11-50). Afterwards, the terminal AS may instruct cancellation of QoE settings in the terminal APP (e.g., QoE config 1/2/3) (11-55). For this purpose, the NR AT command can be used, which may include an indicator indicating termination and a QoE configuration ID (e.g., QoE config 1/2/3). Accordingly, the terminal APP can release all QoE settings (eg, QoE config 1/2/3). After this, the terminal APP can stop performing QoE measurement because it no longer has NR QoE settings (11-60).

As an embodiment of the present invention, if the RRC Connection Reconfiguration message included in MobilityFromNRCommand may contain setup information for new LTE QoE settings (11-40), in this case, the AS and APP of the terminal (NR QoE setup and measurement can save LTE QoE settings (regardless of whether the .

The AS (Access Stratum layer) (12-05) of the terminal and the APP (application layer) (12-10) of the terminal provide one or more NR QoE measurement configuration information (e.g., QoE config 1, QoE config 2, QoE config 3) may have been set (12-15, 12-20). In NR, a terminal (AS and/or APP) can store multiple QoE configuration information and perform measurements independently, so define a separate ID (e.g., measConfigAppLayerId) to distinguish multiple QoE configuration information and /or can be used. (In LTE, only a single QoE setting is possible for the terminal, so a separate ID that distinguishes multiple QoE setting information may not be used.) The terminal (AS and/or APP) can store the QoE setting ID for each QoE setting (12-15, 12-20). A terminal with NR QoE settings (e.g., QoE config 1/2/3) may be in RRC connected mode with an NR base station or cell (12-23). The NR base station or cell can initiate handover of the terminal. For this purpose, the source NR base station or cell (s-gNB) (12-23) provides the information necessary for the target LTE base station (t-eNB) (12-25) to prepare for handover through a handover preparation information message or a HANDOVER REQUEST message. Can be transmitted to t-eNB (12-30). At this time, the message and information can be sent in the format required for target RAT (Radio access technology) (i.e., LTE). Based on the above information, the t-eNB can generate an RRC Connection Reconfiguration message (e.g., RRCConnectionReconfiguration) and deliver it to the s-gNB in a handover command message or HANDOVER REQUEST ACKNOWLEDGEMENT message (12-35). The s-gNB that has received this can transmit the t-eNB's RRC Connection Reconfiguration message to the UE in a MobilityFromNRCommand message (12-40). Below is the ASN.1 code of the MobilityFromNRCommand message.

The s-gNB can instruct the UE by transmitting a MobilityFromNRCommand message.

3) nas-SecurityParamFromNR: Can be omitted during Intra-5GC handover.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. You can define and/or use one service type (e.g., serviceType) to instruct the terminal to maintain one QoE setting (e.g., QoE config 2). Alternatively, for this purpose, the serviceType of the conventional RRCConnectionReconfiguration can be reused. In addition, during handover, update one of the QoE settings in NR (e.g., QoE config 1/2/3) to the QoE setting in LTE and maintain it, or newly define an indicator (e.g., indicator E) to release it altogether. Or you can use The base station converts the QoE settings with the indicated service type among the QoE settings in NR (e.g., QoE config 1/2/3) to the QoE settings of LTE through the service type and indicator E (instructing update and maintenance). You can instruct it to be updated and maintained (12-40). For example, QoE config 2 may be a QoE configuration whose service type is a streaming service, and the base station (s-gNB or t-eNB) configures QoE settings in a plurality of NRs held by the terminal (e.g., QoE config 1/ 2/3) After handover to LTE, set the service type (e.g., serviceType= streaming) to indicate to the terminal one QoE setting (e.g., QoE config 2) to be maintained by updating with the QoE settings of LTE. It can be indicated or set, and through indicator E, it can be instructed to update and maintain one of the QoE settings in NR (e.g., QoE config 1/2/3) to the QoE settings of LTE during handover. If the service type instructed by the terminal corresponds to multiple QoE settings (e.g., QoE config 2/3), the terminal updates one QoE setting to be maintained by updating it with the QoE settings of LTE (e.g., QoE config 2) ) can be selected (e.g., arbitrarily). The indicator E can be defined in the MobilityFromNRCommand message or RRC Connection Reconfiguration message (12-40). For example, if the indicator is defined in the MobilityFromNRCommand message, the s-gNB can set the indicator E, and if the indicator E is defined in the RRC Connection Reconfiguration message, the t-eNB can set the indicator E.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. You can define and/or use one service type (e.g., serviceType) to instruct the terminal to maintain one QoE setting (e.g., QoE config 2). Alternatively, for this purpose, the serviceType of the conventional RRCConnectionReconfiguration can be reused. The base station may instruct the base station to update and maintain the QoE settings with the indicated service type among the QoE settings in NR (e.g., QoE config 1/2/3) through the service type to the QoE settings of LTE (12 -40). For example, QoE config 2 may be a QoE configuration whose service type is a streaming service, and the base station (s-gNB or t-eNB) configures QoE settings in a plurality of NRs held by the terminal (e.g., QoE config 1/ 2/3) After handover to LTE, set the service type (e.g., serviceType= streaming) to indicate to the terminal one QoE setting (e.g., QoE config 2) to be maintained by updating with the QoE settings of LTE. It can be instructed or set. If the service type instructed by the terminal corresponds to multiple QoE settings (e.g., QoE config 2/3), the terminal updates one QoE setting to be maintained by updating it with the QoE settings of LTE (e.g., QoE config 2) ) can be selected (e.g., arbitrarily).

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. Afterwards, one QoE setting ID (e.g., measConfigAppLayerId) can be defined and/or used to instruct the terminal to maintain one QoE setting (e.g., QoE config 2). In addition, during handover, update one of the QoE settings in NR (e.g., QoE config 1/2/3) to the QoE setting in LTE and maintain it, or newly define an indicator (e.g., indicator E) to release it altogether. Or you can use The base station configures the QoE setting with the QoE setting ID indicated among the QoE settings in NR (e.g., QoE config 1/2/3) through the QoE setting ID and indicator E (instructing update and maintenance) to the QoE of LTE. You can instruct it to be maintained by updating it with the settings (12-40). For example, QoE config 2 may be a QoE setting for a service with measConfigAppLayerId=2, and the base station (s-gNB or t-eNB) may set QoE settings in a plurality of NRs held by the UE (e.g., QoE config 1/ 2/3) After handover to LTE, a QoE setting ID (e.g., measConfigAppLayerId=2) to instruct the terminal one QoE setting (e.g., QoE config 2) to be maintained by updating with the QoE settings of LTE. can be indicated or set, and through indicator E, one of the QoE settings (e.g., QoE config 1/2/3) in NR can be updated and maintained with the QoE settings of LTE during handover.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. Afterwards, one QoE setting ID (e.g., measConfigAppLayerId) can be defined and/or used to instruct the terminal to maintain one QoE setting (e.g., QoE config 2). The base station may instruct the base station to update and maintain the QoE configuration with the indicated QoE configuration ID among the QoE configuration in NR (e.g., QoE config 1/2/3) through the QoE configuration ID to the QoE configuration of LTE. (12-40). For example, QoE config 2 may be a QoE setting for a service with measConfigAppLayerId=2, and the base station (s-gNB or t-eNB) may set QoE settings in a plurality of NRs held by the UE (e.g., QoE config 1/ 2/3) After handover to LTE, a QoE setting ID (e.g., measConfigAppLayerId=2) to instruct the terminal one QoE setting (e.g., QoE config 2) to be maintained by updating with the QoE settings of LTE. can be instructed or set.

The base station (s-gNB or t-eNB) may want to perform continuous QoE measurement without interruption in the terminal even if handover is performed, and can maintain the NR's QoE settings by updating them to LTE QoE settings through indicator E. For example, t-eNB supports QoE measurement of the service type set for the UE, and can maintain QoE settings because it is a base station or cell included in the QoE measurement area range (e.g., areaScope) set by the OAM.

For embodiments where the s-gNB determines or generates the setting of indicator E and/or service type to maintain and/or QoE to maintain setting ID (e.g., indicator E and/or service type to maintain and/or QoE to maintain in the MobilityFromNRCommand message (if the configuration ID is defined), an indicator F indicating maintenance and/or a service type to maintain and/or a QoE configuration ID to maintain may be received from the t-eNB (12-35). For example, the By receiving an indicator F indicating maintenance of QoE settings and/or a service type to maintain and/or a QoE configuration ID to maintain from the t-eNB (12-35), an indicator E transmitted to the terminal and/or a service type to maintain and/ Alternatively, the QoE settings to be maintained by the terminal can be indicated through the QoE settings ID to be maintained (12-40).

In one embodiment of the present invention, the base station may cancel all QoE settings (e.g., QoE config 1/2/3) and then transmit some of the same settings (e.g., QoE config 2) to the terminal. To do this, the base station must store QoE setting information (for example, measConfigAppLayerContainer) for each QoE setting of the terminal and transmit it back to the terminal, and the terminal AS must also transmit it back to the terminal APP. Considering that the size of the RRC message of QoE configuration information is not small, this may be very inefficient in terms of signaling and energy consumption for the terminal or base station. For example, measConfigAppLayerContainer can occupy up to 1000 bytes in NR and up to 8000 bytes in LTE. In addition, the method of canceling and resetting the QoE settings described above does not allow QoE measurement to be performed continuously. Therefore, in the present invention, continuous QoE measurement is achieved by maintaining (or reusing) the terminal's QoE configuration information (for example, measConfigAppLayerContainer) rather than releasing it during inter-RAT handover, while reducing signaling overhead and maintaining the communication between the terminal and the base station. It can help reduce energy consumption.

After successfully completing the handover, the UE can transmit an RRC Connection Reconfiguration complete message to the t-eNB (12-45).

The terminal AS may release the NR's radio resources and/or configuration information after successfully completing handover or sending an RRC Connection Reconfiguration complete message (e.g., QoE config 1/3). However, at this time, the terminal AS sets specific QoE resources and/or settings (e.g., one instructed QoE setting) according to the existence of the indicator E and/or QoE setting ID and/or service type received at 12-40 (e.g. For example, QoE config 2) can be maintained without being released as an exception (12-50).

In addition, the base station's instruction to update the QoE settings of the NR to the LTE QoE settings can be understood through the indicator E and/or the QoE setting ID and/or the service type received at 12-40, and the base station instructed to maintain or update accordingly For QoE settings (e.g., QoE config 2), saved NR specific QoE setting information (e.g., measConfgiAppLayerID, pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) can be cleared (12-52), and LTE specific QoE settings Only information (e.g. serviceType) can be set or saved. Afterwards, the terminal AS may notify the terminal APP of the release of QoE settings (e.g., QoE config 1/3) that it has not been instructed to maintain (12-55).

At this time, the NR AT command can be used, and the QoE configuration ID of QoE settings that are not instructed to be maintained (e.g., QoE config 1/3) can be indicated (12-55). In addition, a new indicator Y is defined in the NR AT command and may be included along with the information (e.g., QoE setting ID), and the indicator Y is an indicator corresponding to indicator E, and is used to determine QoE settings in NR (e.g. For example, instructions may be given to maintain or reuse QoE config 2) but update it to LTE QoE settings (12-55).

Accordingly, the terminal APP can release QoE settings that it has not been instructed to maintain (e.g., QoE config 1/3) and update the instructed QoE settings (e.g., QoE config 2) to LTE QoE settings. NR specific QoE setting information (e.g., measConfgiAppLayerID, pauseReporting, transmissionOfSessionStartStop, ran-VisibleParameters) can be deleted among the QoE settings (e.g., QoE config 2) instructed for this purpose (12-60).

In this way, in the terminal APP, the NR QoE settings (e.g., QoE config 2) that are instructed to be maintained are updated with the LTE QoE setting information and QoE measurement can be performed accordingly (12-65).

Accordingly, the terminal APP can generate a QoE report and deliver it to the terminal AS (12-70). At this time, the LTE AT command can be used, which includes reporting the QoE measurement results generated by measuring according to the QoE settings that the terminal APP is instructed to maintain (e.g., QoE config 2) and the service type of the QoE settings (e.g. For example, serviceType) (12-70).

The terminal AS that has received the QoE report from the terminal APP can transmit the QoE report to the base station (t-eNB) that has completed the handover (12-75). At this time, the QoE reporting message defined in LTE (for example, MeasReportAppLayer message) can be used.

SRB3 or SRB4 can be used to transmit the message. The QoE report message (e.g., MeasReportAppLayer message) defined in conventional LTE may include a container (e.g., measReportAppLayerContainer) that stores the QoE report created in the APP with LTE QoE settings, and the service type (e.g., serviceType). The terminal AS can set these values using the information received in 12-70. The t-eNB can forward the QoE report received at 12-75 to the TCE or MCE (12-80).

In an embodiment of the present invention, in steps 12-40, the base station may set the timer length for which the terminal must maintain the NR QoE settings. The timer setting can be defined in the MobilityFromNRCommand message or RRC Connection Reconfiguration message. After successfully performing handover or receiving the above message, the terminal can start the corresponding timer, maintain the LTE QoE settings with updated NR QoE settings while the timer is running, and perform measurements accordingly. Afterwards, when the timer expires, LTE QoE measurement can no longer be stopped and the corresponding setting can be canceled (in both AS and APP). If another handover is performed, the timer can be reset and restarted, or stopped.

The UE's AS (Access Stratum layer) 13-05 and the UE's APP (application layer) 13-10 provide one or more NR QoE measurement configuration information (e.g., QoE config 1, QoE config 2, QoE config 3) may have been set (13-15, 13-20). In NR, a terminal (AS and/or APP) can store multiple QoE configuration information and perform measurements independently, so define a separate ID (e.g., measConfigAppLayerId) to distinguish multiple QoE configuration information and /or can be used. (In LTE, only a single QoE setting is possible for the terminal, so a separate ID that distinguishes multiple QoE setting information may not be used.) The terminal (AS and/or APP) can store the QoE setting ID for each QoE setting (13-15, 13-20). A UE with NR QoE settings (e.g., QoE config 1/2/3) may be in RRC connected mode with an NR base station or cell (13-23). The NR base station or cell can initiate handover of the terminal.

For this purpose, the source NR base station or cell (s-gNB) (13-23) provides the information necessary for the target LTE base station (t-eNB) (13-25) to prepare for handover through a handover preparation information message or HANDOVER REQUEST message. Can be transmitted to t-eNB (13-30). At this time, the message and information can be sent in the format required for target RAT (Radio access technology) (i.e., LTE).

Based on the above information, the t-eNB can generate an RRC Connection Reconfiguration message (e.g., RRCConnectionReconfiguration) and deliver it to the s-gNB in a handover command message or HANDOVER REQUEST ACKNOWLEDGEMENT message (13-35). The s-gNB that has received this can transmit the t-eNB's RRC Connection Reconfiguration message to the UE in a MobilityFromNRCommand message (13-40). Below is the ASN.1 code of the MobilityFromNRCommand message.

The s-gNB can instruct the UE by transmitting a MobilityFromNRCommand message.

3) nas-SecurityParamFromNR: Can be omitted during Intra-5GC handover.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. One service type (e.g., serviceType) can be defined and/or used to instruct the terminal about the QoE settings (e.g., QoE config 1/3) to be maintained. If the base station wants to cancel all QoE settings (e.g., QoE config 1/2/3) in NR, the service type can be set to absent. That is, the service type (eg, serviceType) may be defined as an OPTIONAL field. In addition, during handover, update one of the QoE settings in NR (e.g., QoE config 1/2/3) to the QoE setting in LTE and maintain it, or newly define an indicator (e.g., indicator E) to release it altogether. Or you can use The base station instructs the terminal to release all QoE settings (e.g., QoE config 1/2/3) in NR through the absence of the service type and indicator E (e.g., indication of release). (13-40). For example, the base station (s-gNB or t-eNB) performs handover to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs owned by the terminal, and then switches to LTE's QoE settings. In order to indicate to the terminal that there are no QoE settings to be updated and maintained (i.e., release all), the service type may not be included (set to absent), and all QoE settings in NR at the time of handover through indicator E (e.g. For example, you can instruct to disable QoE config 1/2/3). The indicator E can be defined in the MobilityFromNRCommand message or RRC Connection Reconfiguration message (13-40). For example, if the indicator is defined in the MobilityFromNRCommand message, the s-gNB can set the indicator E, and if the indicator E is defined in the RRC Connection Reconfiguration message, the t-eNB can set the indicator E.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. One service type (e.g., serviceType) can be defined and/or used to instruct the terminal about the QoE settings (e.g., QoE config 1/3) to be maintained. If the base station wants to cancel all QoE settings (e.g., QoE config 1/2/3) in NR, the service type can be set to absent. That is, the service type (eg, serviceType) may be defined as an OPTIONAL field. The base station may instruct the terminal to release all QoE settings (e.g., QoE config 1/2/3) in NR through the absence of the service type (13-40). For example, the base station (s-gNB or t-eNB) performs handover to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs owned by the terminal, and then switches to LTE's QoE settings. The service type may not be included (set to absent) to indicate to the terminal that there are no QoE settings to be updated and maintained (i.e., disable all).

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. Afterwards, one QoE setting ID (e.g., measConfigAppLayerId) can be defined and/or used to instruct the terminal about the QoE setting (e.g., QoE config 1/3) to be maintained. If the base station wants to cancel all QoE settings (e.g., QoE config 1/2/3) in NR, the QoE configuration ID can be set to absent. That is, the QoE configuration ID (eg, measConfigAppLayerId) may be defined as an OPTIONAL field. In addition, during handover, update one of the QoE settings in NR (e.g., QoE config 1/2/3) to the QoE setting in LTE and maintain it, or newly define an indicator (e.g., indicator E) to release it altogether. Or you can use The base station may instruct the terminal to release all QoE settings (e.g., QoE config 1/2/3) in NR through the absence of the QoE configuration ID and indicator E (instruction to release) ( 13-40). For example, the base station (s-gNB or t-eNB) performs handover to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs owned by the terminal, and then switches to LTE's QoE settings. In order to indicate to the terminal that there are no QoE settings to be updated and maintained (i.e., release all), the QoE setting ID may not be included (set to absent), and all QoE settings in NR at the time of handover through indicator E ( For example, you can instruct to disable QoE config 1/2/3). The indicator E can be defined in the MobilityFromNRCommand message or RRC Connection Reconfiguration message (13-40). For example, if the indicator is defined in the MobilityFromNRCommand message, the s-gNB can set the indicator E, and if the indicator E is defined in the RRC Connection Reconfiguration message, the t-eNB can set the indicator E.

In an embodiment of the present invention, during handover, the base station (s-gNB or t-eNB) hands over to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs held by the terminal. Afterwards, one QoE setting ID (e.g., measConfigAppLayerId) can be defined and/or used to instruct the terminal about the QoE setting (e.g., QoE config 1/3) to be maintained. If the base station wants to cancel all QoE settings (e.g., QoE config 1/2/3) in NR, the QoE configuration ID can be set to absent. That is, the QoE configuration ID (eg, measConfigAppLayerId) may be defined as an OPTIONAL field. The base station may instruct the terminal to release all QoE settings (e.g., QoE config 1/2/3) in NR through the absence of the QoE configuration ID (13-40). For example, the base station (s-gNB or t-eNB) performs handover to LTE among the QoE settings (e.g., QoE config 1/2/3) in the plurality of NRs owned by the terminal, and then switches to LTE's QoE settings. The QoE setting ID may not be included (set to absent) to indicate to the terminal that there are no QoE settings to be updated and maintained (i.e., disable all).

The base station (s-gNB or t-eNB) may wish to cancel QoE measurement and settings in the UE when performing handover, and may cancel the QoE settings of NR through indicator E. For example, the t-eNB may not support QoE measurement for the service type set for the UE, or the t-eNB may not support QoE measurement because it is a base station or cell outside the QoE measurement area range (e.g., areaScope) set by the OAM. can be released. In addition, new QoE measurements can be set for the terminal immediately after release.

For embodiments where the s-gNB determines or generates the setting of indicator E and/or service type to maintain and/or QoE to maintain setting ID (e.g., indicator E and/or service type to maintain and/or QoE to maintain in the MobilityFromNRCommand message (when the configuration ID is defined), an indicator (e.g., indicator F) indicating cancellation of the QoE configuration may be received from the t-eNB, and a message in which the service to be maintained and/or the QoE configuration ID to be maintained may be absent may be received ( 13-35). For example, the By receiving an indicator F indicating release of QoE settings from the t-eNB and/or a service type to be absent and/or a QoE setting ID to be absent (13-35), an indicator E transmitted to the terminal (instructs release) ) and/or the cancellation of all QoE settings of the terminal may be instructed through setting the service type to be absent and/or the QoE setting ID to be absent (13-40).

After successfully completing the handover, the UE can transmit an RRC Connection Reconfiguration complete message to the t-eNB (13-45). The terminal AS may release the radio resources and/or settings of the NR after successfully completing handover or sending an RRC Connection Reconfiguration complete message. At this time, the terminal AS configures all QoE resources and/or settings (e.g., QoE config 1/2/ 3) It can also be turned off. (13-50). Likewise, the terminal AS can instruct cancellation of all QoE settings in the terminal APP (13-55). For this purpose, the NR AT command can be used, which can include an indicator indicating termination and all QoE configuration IDs (e.g., each measConfigAppLayerId in QoE config 1/2/3). After this, the terminal APP can stop performing QoE measurement because it no longer has NR QoE settings (13-60).

As an embodiment of the present invention, if the RRC Connection Reconfiguration message included in MobilityFromNRCommand may contain setup information for new LTE QoE settings (13-40), in this case, the AS and APP of the terminal (NR QoE setup and measurement can save new LTE QoE settings and (additionally) perform and report QoE measurements based on the new LTE QoE settings (regardless of whether the -80 can be followed.

The indicator E proposed in FIGS. 12 and 13 may be the same indicator, and may be interpreted as one of the following options or a combination thereof. In one embodiment, indicator E may be defined in the MobilityFromNRCommand message or RRC Connection Reconfiguration message. “Terminal” referred to in the following options may refer to both AS and APP. Alternatively, it may refer to only one of AS or APP. In the following, the procedure for maintaining and updating QoE measurements (meaning updating to LTE QoE settings) may refer to FIG. 12. The procedure for disabling QoE measurement below can refer to FIG. 13.

- Option 1: This is an OPTIONAL parameter. If this parameter is included, the terminal can maintain or update (if present) the QoE settings in NR when performing handover to LTE. If the corresponding parameter is absent, the terminal can cancel all QoE settings in NR (if retained) when performing handover to LTE. In one embodiment, the parameter may include sub-parameters.

- Option 2: This is an OPTIONAL parameter. If this parameter is included, the terminal can cancel all QoE settings in NR (if retained) when performing handover to LTE. If the corresponding parameter is absent, the terminal can maintain or update (if present) the QoE settings in NR when performing handover to LTE. In one embodiment, the parameter may include sub-parameters.

- Option 3: This is an OPTIONAL parameter. If the parameter is set to true, the terminal can maintain or update the QoE settings in NR when performing handover to LTE. If the parameter is set to false, the terminal can cancel all QoE settings in NR when performing handover to LTE. If the corresponding parameter is absent, the terminal may not perform any operation. For example, if the terminal does not have QoE settings, the corresponding parameter may be absent because there are no settings to maintain, update, or release.

- Option 4: This is an OPTIONAL parameter. If this parameter is set to true, the terminal can cancel all QoE settings in NR when performing handover to LTE. If the parameter is set to false, the terminal can maintain or update QoE settings in NR when performing handover to LTE. If the corresponding parameter is absent, the terminal may not perform any operation. For example, if the terminal does not have QoE settings, the corresponding parameter may be absent because there are no settings to maintain, update, or release.

- Option 5: This is a MANDATORY parameter. If the parameter is set to true, the terminal can maintain or update the QoE settings in NR when performing handover to LTE. If the parameter is set to false, the terminal can cancel all QoE settings in NR when performing handover to LTE. If the terminal does not have QoE settings, the parameter may be ignored or no operation may be performed regardless of the parameter.

- Option 6: This is a MANDATORY parameter. If this parameter is set to true, the terminal can cancel all QoE settings in NR when performing handover to LTE. If the parameter is set to false, the terminal can maintain or update QoE settings in NR when performing handover to LTE. If the terminal does not have QoE settings, the parameter may be ignored or no operation may be performed regardless of the parameter.

If "release" is set, the terminal can cancel all QoE settings in NR when performing handover to LTE.

If "setup" is set and measConfigAppLayerContainer and/or serviceType and/or mesaConfigAppLayerID in "setup" are set, the terminal can use the corresponding information to cancel the existing NR QoE settings and setup with the new QoE setting information provided above. there is. That is, the terminal can change or modify existing QoE settings when performing handover to LTE. In this case, the UE's operation to cancel the existing NR QoE setting may be the same as the operation in 13-50 and 13-55, and some or all of the following operations may be added to set the new QoE.

7) Procedure for AS to set or save new QoE settings in AS

8) Procedure for AS to transmit new QoE settings information (including measConfigAppLayerContainer) to APP

9) Procedure for APP to set new QoE setting information (including measConfigAppLayerContainer) and perform and report QoE measurement based on this

If the setting for indicator E is defined as an operation by the s-gNB (for example, if the indicator E is set in the MobilityFromNRCommand message rather than the RRC Connection Reconfiguration message), the new QoE setting may be an NR QoE setting. If the setting for indicator E is defined as an operation by the t-eNB (for example, if the indicator E is set in the RRC Connection Reconfiguration message included in the MobilityFromNRCommand message), the new QoE setting may be an LTE QoE setting.

If "setup" is set but measConfigAppLayerContainer and/or serviceType and/or mesaConfigAppLayerID in "setup" are not set, the terminal may maintain or update the existing NR QoE settings when performing handover to LTE. If indicator E is absent or the terminal does not have QoE settings, the parameter may be ignored or no operation may be performed regardless of the parameter.

For Options 1 and 2, for example, an ASN.1 code for indicator E (e.g., indicatorE) may be defined in MobilityFromNRCommand as follows.

For Options 3 and 4, for example, an ASN.1 code for indicator E (e.g., indicatorE) can be defined in MobilityFromNRCommand as follows.

For Options 5 and 6, for example, an ASN.1 code for indicator E (e.g., indicatorE) can be defined in MobilityFromNRCommand as follows.

For Option 7, for example, an ASN.1 code for indicator E (e.g., indicatorE) may be defined in MobilityFromNRCommand as follows.

The indicator F proposed in FIGS. 12 and 13 may be the same indicator, and may be interpreted as one of the following options or a combination thereof. In one embodiment, indicator F may be defined in the HANDOVER REQUEST ACKNOWLEDGEMENT or Handover Command message. In the following, the procedure for maintaining or updating QoE measurements (meaning updating NR QoE settings to LTE settings) can refer to FIG. 12. The procedure for releasing all NR QoE measurements below can refer to FIG. 13.

- Option 1: This is an OPTIONAL parameter. If the parameter is included, the s-gNB can instruct the UE to maintain or update (if present) the QoE settings in NR when performing handover to LTE (e.g. For (via indicator E). If the corresponding parameter is absent, the s-gNB may instruct the UE to release (if retained) all QoE settings in NR when performing handover to LTE (for example, through indicator E). In one embodiment, the parameter may include sub-parameters.

- Option 2: This is an OPTIONAL parameter. If this parameter is included, the s-gNB can instruct the UE to cancel all QoE settings in NR (if any) when performing handover to LTE (e.g. via indicator E). If the corresponding parameter is absent, the s-gNB may instruct the UE to maintain or update (if present) the QoE settings in NR when performing handover to LTE (for example, through indicator E). In one embodiment, the parameter may include sub-parameters.

- Option 3: This is an OPTIONAL parameter. If the parameter is set to true, the s-gNB can instruct the UE to maintain or update (if present) the QoE settings in NR when performing handover to LTE (e.g. For example via indicator E). If the parameter is set to false, the s-gNB may instruct the UE to release (if retained) all QoE settings in NR when performing handover to LTE (for example, through indicator E). If the corresponding parameter is absent, the s-gNB may not set or transmit indicator E to the UE. (i.e. absence of indicator E)

- Option 4: This is an OPTIONAL parameter. If the parameter is set to true, the s-gNB can instruct the UE to cancel all QoE settings in NR (if any) when performing handover to LTE (e.g. For (via indicator E). If the parameter is set to false, the s-gNB may instruct the UE to maintain or update (if present) the QoE settings in NR when performing handover to LTE (e.g., through indicator E). If the corresponding parameter is absent, the s-gNB may not set or transmit indicator E to the UE. (i.e. absence of indicator E)

- Option 5: This is a MANDATORY parameter. If the parameter is set to true, the s-gNB can instruct the UE to maintain or update (if present) the QoE settings in NR when performing handover to LTE (e.g. For example via indicator E). If the parameter is set to false, the s-gNB may instruct the UE to release (if retained) all QoE settings in NR when performing a handover to LTE (for example, through indicator E).

- Option 6: This is a MANDATORY parameter. If the parameter is set to true, the s-gNB can instruct the UE to cancel all QoE settings in NR (if any) when performing handover to LTE (e.g. For (via indicator E). If the parameter is set to false, the s-gNB may instruct the UE to maintain or update (if present) the QoE settings in NR when performing handover to LTE (e.g., through indicator E).

If "release" is set, the s-gNB may instruct the UE to release (if retained) all QoE settings in NR when performing handover to LTE.

If "setup" is set and the QoE setting information of the application layer in "setup" (information included in measConfigAppLayerContainer in the RRC layer) and/or service type (information included in serviceType in the RRC layer) and/or QoE setting ID are set If so, the s-gNB may instruct the UE to use the corresponding information to cancel the existing NR QoE settings and set up with the new QoE setting information provided. That is, the s-gNB can instruct the UE to change or modify existing QoE settings (including measConfigAppLayerContainer) when performing handover to LTE.

If "setup" is set, but the QoE setting information of the application layer in "setup" (information included in measConfigAppLayerContainer in the RRC layer) and/or service type (information included in serviceType in the RRC layer) and/or QoE setting ID are not set If not, the s-gNB may instruct the UE to maintain the existing NR QoE settings (including measConfigAppLayerContainer) when performing handover to LTE.

This option can be defined or used together with option 7 for indicator E.

All embodiments of the present disclosure are prepared assuming an intra 5GC handover (i.e., handover between base stations sharing the same 5GC) situation for convenience of writing, but the content of the invention is not limited thereto and includes inter-5GC handover and It can also be applied to handovers involving other types of core networks (e.g., EPC, or 6G core).

All embodiments of the present disclosure are written assuming a handover situation from NR to LTE or LTE to NR for convenience of writing, but the content of the invention is not limited thereto and can be applied to all handovers between different RATs.

All embodiments of the present disclosure may be limited to specific service types (e.g., streaming or MTSI), but may also be applied to VR and service types to be defined in 3GPP in the future (e.g., XR, Cloud gaming).

Referring to the drawing, the terminal includes an RF (Radio Frequency) processing unit 14-10, a baseband processing unit 14-20, a storage unit 14-30, and a control unit 14-40. .

The RF processing unit 14-10 performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. That is, the RF processing unit 14-10 up-converts the baseband signal provided from the baseband processing unit 14-20 into an RF band signal and transmits it through an antenna, and the RF band signal received through the antenna Downconvert to a baseband signal. For example, the RF processing unit 14-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. You can. In the drawing, only one antenna is shown, but the terminal may be equipped with multiple antennas. Additionally, the RF processing unit 14-10 may include multiple RF chains. Furthermore, the RF processing unit 14-10 can perform beamforming. For the beamforming, the RF processing unit 14-10 can adjust the phase and size of each signal transmitted and received through a plurality of antennas or antenna elements. Additionally, the RF processing unit can perform MIMO and can receive multiple layers when performing a MIMO operation.

The baseband processing unit 14-20 performs a conversion function between baseband signals and bit streams according to the physical layer standard of the system. For example, when transmitting data, the baseband processing unit 14-20 generates complex symbols by encoding and modulating the transmission bit stream. Additionally, when receiving data, the baseband processing unit 14-20 restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 14-10. For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit 14-20 generates complex symbols by encoding and modulating the transmission bit stream, and transmits the complex symbols to subcarriers. After mapping, OFDM symbols are configured through IFFT (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. In addition, when receiving data, the baseband processing unit 14-20 divides the baseband signal provided from the RF processing unit 14-10 into OFDM symbols and divides the baseband signal into subcarriers through FFT (fast Fourier transform) operation. After restoring the mapped signals, the received bit string is restored through demodulation and decoding.

The baseband processing unit 14-20 and the RF processing unit 14-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 14-20 and the RF processing unit 14-10 may be referred to as a transmitting unit, a receiving unit, a transceiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit 14-20 and the RF processing unit 14-10 may include multiple communication modules to support multiple different wireless access technologies. Additionally, at least one of the baseband processing unit 14-20 and the RF processing unit 14-10 may include different communication modules to process signals in different frequency bands. For example, the different wireless access technologies may include wireless LAN (eg, IEEE 802.11), cellular network (eg, LTE), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (e.g., 60GHz) band.

The storage unit 14-30 stores data such as basic programs, application programs, and setting information for operation of the terminal. In particular, the storage unit 14-30 may store information related to a second access node that performs wireless communication using a second wireless access technology. Additionally, the storage unit 14-30 provides stored data upon request from the control unit 14-40.

The control unit 14-40 controls overall operations of the terminal. For example, the control unit 14-40 transmits and receives signals through the baseband processing unit 14-20 and the RF processing unit 14-10. Additionally, the control unit 14-40 writes and reads data into the storage unit 14-40. For this purpose, the control unit 14-40 may include at least one processor. For example, the control unit 14-40 may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

As shown in the figure, the base station includes an RF processing unit 15-10, a baseband processing unit 15-20, a backhaul communication unit 15-30, a storage unit 15-40, and a control unit 15-50. It is composed including.

The RF processing unit 15-10 performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. That is, the RF processing unit 15-10 upconverts the baseband signal provided from the baseband processing unit 15-20 into an RF band signal and transmits it through an antenna, and the RF band signal received through the antenna Downconvert to a baseband signal. For example, the RF processing unit 15-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is shown, but the first access node may be equipped with multiple antennas. Additionally, the RF processing unit 15-10 may include multiple RF chains. Furthermore, the RF processing unit 15-10 can perform beamforming. For the beamforming, the RF processing unit 15-10 can adjust the phase and size of each signal transmitted and received through a plurality of antennas or antenna elements. The RF processing unit can perform downlink MIMO operation by transmitting one or more layers.

The baseband processing unit 15-20 performs a conversion function between baseband signals and bit strings according to the physical layer standard of the first wireless access technology. For example, when transmitting data, the baseband processing unit 15-20 generates complex symbols by encoding and modulating the transmission bit stream. Additionally, when receiving data, the baseband processing unit 15-20 restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 15-10. For example, in the case of OFDM, when data is transmitted, the baseband processing unit 15-20 generates complex symbols by encoding and modulating the transmission bit stream, maps the complex symbols to subcarriers, and performs IFFT. OFDM symbols are constructed through operations and CP insertion. In addition, when receiving data, the baseband processing unit 15-20 divides the baseband signal provided from the RF processing unit 15-10 into OFDM symbols and restores signals mapped to subcarriers through FFT operation. After that, the received bit string is restored through demodulation and decoding. The baseband processing unit 15-20 and the RF processing unit 15-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 15-20 and the RF processing unit 15-10 may be referred to as a transmitting unit, a receiving unit, a transceiving unit, a communication unit, or a wireless communication unit.

The backhaul communication unit 15-30 provides an interface for communicating with other nodes in the network. That is, the backhaul communication unit 15-30 converts a bit string transmitted from the main base station to another node, for example, an auxiliary base station, a core network, etc., into a physical signal, and converts the physical signal received from the other node into a bit string. Convert to heat.

The storage unit 15-40 stores data such as basic programs, application programs, and setting information for operation of the main base station. In particular, the storage unit 15-40 can store information about bearers assigned to the connected terminal, measurement results reported from the connected terminal, etc. Additionally, the storage unit 15-40 can store information that serves as a criterion for determining whether to provide or suspend multiple connections to the terminal. Additionally, the storage unit 15-40 provides stored data upon request from the control unit 15-50.

The control unit 15-50 controls overall operations of the main base station. For example, the control unit 15-50 transmits and receives signals through the baseband processing unit 15-20 and the RF processing unit 15-10 or through the backhaul communication unit 15-30. Additionally, the control unit 15-50 writes and reads data into the storage unit 15-40. For this purpose, the control unit 15-50 may include at least one processor.

Claims

In a method performed by a terminal in a wireless communication system,

Receiving a message for handover from a first network to a second network from a base station, the message including an indicator instructing to maintain Quality of Experience (QoE) settings in the first network;

Based on completion of the handover, transmitting a handover completion message to the base station;

performing QoE measurement based on the first QoE setting; and

A method comprising transmitting a report message including results of the QoE measurement to the base station.
The method of claim 1, wherein the QoE configuration information includes a QoE configuration identifier (ID).
The method of claim 1, wherein the report message includes the QoE configuration ID.
According to paragraph 1,

Updating the QoE setting information from the QoE setting information of the LTE to the QoE setting information of the NR; and

The method further comprising releasing QoE setting information in the LTE.
In a method performed by a base station in a wireless communication system,

Transmitting a message for handover from a first network to a second network to a terminal, the message including an indicator instructing to maintain Quality of Experience (QoE) settings in the first network;

Receiving a handover completion message from the terminal based on completion of the handover; and

Comprising the step of receiving a report message containing the results of QoE measurement from the terminal,

A method wherein the QoE measurement is performed based on the first QoE setting.
The method of claim 5, wherein the QoE setting information includes a QoE setting identifier (ID).
The method of claim 5, wherein the report message includes the QoE configuration ID.
The method of claim 5, wherein the QoE setting information is updated from the QoE setting information of the LTE to the QoE setting information of the NR, and

A method characterized in that QoE setting information in LTE is released.
In a terminal in a wireless communication system,

Transmitter and receiver; and

It includes a control unit connected to the transceiver unit,

The control unit

A message for handover from a first network to a second network is received from a base station, and the message includes an indicator instructing to maintain Quality of Experience (QoE) settings in the first network,

Based on completion of the handover, transmitting a handover completion message to the base station,

Perform QoE measurement based on the first QoE setting, and

A terminal characterized in that it transmits a report message containing the results of the QoE measurement to the base station.
The terminal of claim 9, wherein the QoE configuration information includes a QoE configuration identifier (ID).
The terminal according to claim 9, wherein the report message includes the QoE configuration ID.
The method of claim 9, wherein the control unit,

Update the QoE setting information from the QoE setting information of the LTE to the QoE setting information of the NR, and

A terminal characterized in that the QoE setting information in the LTE is released.
In a base station in a wireless communication system,

Transmitter and receiver; and

It includes a control unit connected to the transceiver unit,

The control unit,

A message for handover from a first network to a second network is sent to the terminal, and the message includes an indicator instructing to maintain Quality of Experience (QoE) settings in the first network,

Based on completion of the handover, receive a handover completion message from the terminal, and

Receive a report message containing the results of QoE measurement from the terminal,

A base station wherein the QoE measurement is performed based on the first QoE setting.
The base station of claim 13, wherein the QoE configuration information includes a QoE configuration identifier (ID).
The base station of claim 13, wherein the report message includes the QoE configuration ID.
The method of claim 13, wherein the QoE setting information is updated from the QoE setting information of the LTE to the QoE setting information of the NR, and

A base station wherein the QoE setting information in LTE is released.