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

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Specifically, the disclosure provides a method performed by a terminal in a wireless communication system, the method including the steps of: receiving a first radio resource control (RRC) message, the first RRC message including a first application layer measurement configuration applied to RRC idle and RRC inactive; storing the first application layer measurement configuration; receiving an RRC setup message from a base station; if the terminal does not transmit a second application layer measurement configuration included in a measurement report application layer message after receiving the RRC setup message, setting parameters of the second application layer measurement configuration based on a value stored in a terminal variable; and transmitting the measurement report application layer message to the base station.

Description

Technical Field

[0001] This disclosure relates to the operation of terminals and base stations in inactive and idle modes in wireless communication systems. Additionally, this disclosure relates to the operation of quality of experience (QoE) measurement in inactive and idle modes. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and it can be implemented not only in the sub-6GHz band such as 3.5 GHz, but also in ultra-high frequency bands (“above 6GHz”) such as 28 GHz and 39 GHz, also known as millimeter wave (mmWave). Additionally, 6G mobile communication technology, known as Super 5G communication systems, is considered to be implemented in the terahertz (THz) band (e.g., from 95 GHz to 3 THz) to achieve transmission speeds up to 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] The early goal of 5G mobile communication technology was to support and meet the performance requirements of services such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). To achieve this goal, standardization is underway for the following technologies: beamforming and massive MIMO to mitigate radio wave path loss and increase propagation range in the UHF band; support for various parameter sets (such as operation of multiple subcarrier spacing) and dynamic operation of time slot formats to efficiently utilize UHF resources; initial access technologies to support multi-beam transmission and broadband; definition and operation of the bandwidth portion (BWP); new channel coding methods, such as low-density parity-check (LDPC) codes for high-capacity data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing to provide dedicated networks for specific services.

[0004] Currently, improvements and performance enhancements to the initial 5G mobile communication technology are being discussed, considering the services it aims to support. Technologies undergoing physical layer standardization include: Vehicle-to-Everything (V2X), which assists autonomous vehicles in making driving decisions and enhances user convenience based on the vehicle's own location and status information; New Radio Unlicensed (NR-U), designed to meet various regulatory requirements for system operation in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Network (NTN), which ensures coverage in areas where communication with terrestrial networks is impossible via direct UE-satellite communication; and positioning.

[0005] Furthermore, standardization is underway in the areas of wireless interface architecture / protocols for technologies such as: smart factories (Industrial Internet of Things (IIoT)) supporting new services through integration and convergence with other industries; Integrated Access and Backhaul (IAB) providing nodes for extending network service areas by integrating and supporting wireless backhaul and access links; mobility enhancement technologies including conditional handover and Dual Active Protocol Stack (DAPS) handover; and two-step random access (2-step RACH for NR) to simplify the random access process. Standardization is also underway in the areas of system architecture / services for 5G baseline architectures combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies (e.g., service-based architecture, service-based interfaces) and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0006] When such 5G mobile communication systems are commercialized, an explosive growth in connected devices will link to the communication network. Therefore, it is anticipated that the functionality and performance of 5G mobile communication systems, as well as the integrated operation of connected devices, will need to be enhanced. To this end, new research is planned on extended reality (XR) to efficiently support augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., by leveraging artificial intelligence (AI) and machine learning (ML) to enhance 5G performance and reduce complexity, supporting AI services, metaverse services, and drone communications, among others.

[0007] Furthermore, advancements in 5G mobile communication systems not only provide the foundation for 6G mobile communication technologies (including multi-antenna transmission technologies such as new waveforms to ensure terahertz band coverage, full-dimensional multiple-input multiple-output (FD-MIMO), array antennas and massive MIMO, metamaterial-based lenses and antennas to enhance terahertz band signal coverage, high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS) technologies), but also for 6G mobile communication technologies (including full-duplex technologies to improve frequency efficiency and enhance system networks, AI-based communication technologies that leverage satellites and artificial intelligence (AI) from the design phase and combine them with end-to-end AI support to achieve system optimization, and next-generation distributed computing technologies that utilize ultra-high-performance communication and computing resources to achieve highly complex services that exceed the computing power limitations of UEs). Summary of the Invention

[0008] Technical issues

[0009] Various embodiments of this disclosure are intended to provide efficient operation of terminals and base stations. Furthermore, various embodiments of this disclosure are intended to provide improved operation of terminals and base stations in inactive and idle modes in wireless communication systems. Further, various embodiments of this disclosure are intended to provide improved operation for measuring QoE in inactive and idle modes.

[0010] Technical solution

[0011] According to various embodiments of this disclosure, a method performed by a terminal in a wireless communication system includes: receiving a first Radio Resource Control (RRC) message, the first RRC message including a first application layer measurement configuration applied to RRC idle and RRC inactive; storing the first application layer measurement configuration; receiving an RRC establishment message from a base station; if the terminal does not send a second application layer measurement configuration after receiving the RRC establishment message, setting parameters of the second application layer measurement configuration included in a measurement report application layer message based on values ​​stored in terminal variables; and sending a measurement report application layer message to the base station.

[0012] Additionally, according to various embodiments of this disclosure, a method performed by a base station in a wireless communication system includes: sending a Radio Resource Control (RRC) establishment message to a first terminal storing a first RRC message, the first RRC message including a first application layer measurement configuration applied to RRC idle and RRC inactive; and if the terminal does not send a second application layer measurement configuration after receiving the RRC establishment message, receiving from the terminal a measurement report application layer message including the second application layer measurement configuration, the second application layer measurement configuration including parameters set based on values ​​stored in terminal variables.

[0013] Additionally, according to various embodiments of this disclosure, a terminal of a wireless communication system includes a transceiver and a controller configured to: receive a first Radio Resource Control (RRC) message, the first RRC message including a first application layer measurement configuration applied to RRC idle and RRC inactive; store the first application layer measurement configuration; receive an RRC establishment message from a base station; if the terminal does not send a second application layer measurement configuration after receiving the RRC establishment message, set parameters of the second application layer measurement configuration included in a measurement report application layer message based on values ​​stored in terminal variables; and send a measurement report application layer message to the base station.

[0014] Additionally, according to various embodiments of this disclosure, a base station in a wireless communication system includes: a transceiver; and a controller configured to: send a Radio Resource Control (RRC) establishment message to a first terminal storing a first RRC message, the first RRC message including a first application layer measurement configuration applied to RRC idle and RRC inactive; and if the terminal does not send a second application layer measurement configuration after receiving the RRC establishment message, receive from the terminal a measurement report application layer message including a second application layer measurement configuration, the second application layer measurement configuration including parameters set based on values ​​stored in terminal variables.

[0015] Beneficial effects

[0016] According to various embodiments of this disclosure, efficient operation of terminals and base stations can be provided.

[0017] Furthermore, various embodiments of this disclosure can provide improved operation of terminals and base stations in inactive and idle modes in wireless communication systems.

[0018] Additionally, according to various embodiments of this disclosure, improved operation for measuring QoE can be provided in inactive and idle modes. Attached Figure Description

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

[0020] Figure 2 This is a diagram illustrating radio access state transitions in a mobile communication system according to an embodiment of the present disclosure.

[0021] Figure 3 This is a flowchart illustrating a signaling-based QoE measurement configuration and reporting process according to an embodiment of the present disclosure.

[0022] Figure 4 This is a flowchart illustrating a managed QoE measurement configuration and reporting process according to an embodiment of the present disclosure.

[0023] Figure 5 This is a flowchart illustrating the RAN visible QoE measurement configuration and reporting process according to an embodiment of the present disclosure.

[0024] Figure 6 This is a flowchart illustrating a configuration and reporting process for a UE to support QoE measurements in connected mode, as well as inactive and idle modes, according to an embodiment of this disclosure.

[0025] Figure 7 The illustration shows the configuration of a terminal applied to an embodiment of this disclosure.

[0026] Figure 8 The illustration shows the configuration of a base station applied to an embodiment of this disclosure. Detailed Implementation

[0027] In the following, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals denote the same components in the drawings. Furthermore, detailed descriptions relating to well-known functions or configurations will be excluded so as not to unnecessarily obscure the subject matter of the disclosure.

[0028] In describing the embodiments in this specification, descriptions of technical content known in the art to which this disclosure pertains and not directly related to this disclosure will be omitted. The reason for omitting unnecessary descriptions is to keep the main points of this disclosure clear.

[0029] For the same reason, some components in the accompanying drawings are exaggerated, omitted, or shown schematically. Additionally, the size of each component does not perfectly reflect its actual size. In each drawing, the same reference numerals are assigned to the same or corresponding components.

[0030] The advantages and features of this disclosure, as well as methods of implementing them, will be illustrated below with reference to the accompanying drawings and detailed embodiments. However, this disclosure is not limited to the exemplary embodiments described below, but can be implemented in various different forms. These exemplary embodiments are provided only to complete this disclosure and to allow those skilled in the art to fully appreciate its scope, which will be defined by the scope of the claims. Throughout this specification, the same reference numerals denote the same components.

[0031] In this context, it should be understood that each block and combination of blocks in the flowchart can be executed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, these computer program instructions, executed by the processor of the computer or other programmable data processing apparatus, create components that perform the functions described in the blocks(s) of the flowchart. Since these computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can instruct the computer or other programmable data processing apparatus to implement functions in a particular manner, the instructions stored in the computer-usable or computer-readable storage medium can produce an article of art that includes instruction components that perform the functions described in the blocks(s) of the flowchart. Since the computer program instructions can also be mounted on a computer or other programmable data processing apparatus, the instructions perform a series of operational steps on the computer or other programmable data processing apparatus to create a process executed by the computer, thereby performing steps that the computer or other programmable data processing apparatus can also provide for performing the functions described in the blocks(s) of the flowchart.

[0032] Additionally, each box may represent some of a module, segment, or code comprising one or more executable instructions for performing a specific logical function(s). Furthermore, it should be noted that in some alternative embodiments, the functions mentioned in the boxes occur regardless of their order. For example, two boxes illustrated consecutively may actually execute simultaneously, or, depending on the corresponding functions, execute in reverse order.

[0033] In this context, the term "~unit" as used in this embodiment refers to a software or hardware component, such as an FPGA or ASIC, and the "~unit" performs a specific function. However, "~unit" is not intended to be limited to software or hardware. A "~unit" can be configured to be stored in an addressable storage medium or can be configured to reproduce one or more processors. Accordingly, as examples, a "~unit" includes components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. Components and functions provided within a "~unit" can be combined into a smaller number of components and "~units," or can be further separated into additional components and "~units." Additionally, components and "~units" can be implemented as one or more CPUs in a reproduction device or secure multimedia card.

[0034] In the following text, a base station is an entity that performs resource assignment for a terminal and can be at least one of a Node B, a base station (BS), an eNode B (eNB), a gNode B (gNB), a radio access unit, a base station controller, or a node on a network. A terminal can include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Furthermore, embodiments of this disclosure can be applied to other communication systems with similar technical backgrounds or channel formats to the embodiments of this disclosure described below. Additionally, embodiments of this disclosure can be applied to other communication systems with certain modifications that can be determined by those skilled in the art without significantly departing from the scope of this disclosure. For example, fifth-generation (5G) mobile communication technology (New Radio (NR)) developed after LTE-A can be included in such other communication systems, and 5G as described below can also be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, this disclosure can be applied to other communication systems with certain modifications that can be determined by those skilled in the art without significantly departing from the scope of this disclosure.

[0035] In the following description, terms used to identify access nodes, to refer to network entities or network functions (NFs), to refer to messages, to refer to interfaces between network entities, and to refer to various types of identification information are given as examples for ease of description. Accordingly, this disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0036] For ease of description, some terms and names defined in the 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) standard and / or the 3GPP NR (New Radio) standard may be used. However, this disclosure is not limited to these terms and names and may be equally applied to systems conforming to other standards.

[0037] Figure 1 This is a diagram illustrating the structure of a mobile communication system according to an embodiment of the present disclosure.

[0038] refer to Figure 1 As shown in the figure, the radio access network of the mobile communication system (New Radio (NR)) according to an embodiment of the present disclosure consists of base stations (Next Generation Node Bs, hereinafter referred to as gNBs) 1-10 and Access and Mobility Management Entities (AMFs) (New Radio Core Networks) 1-05. User equipment (New Radio User Equipment, hereinafter referred to as NR UEs or terminals) 1-15 accesses external networks via gNBs 1-10 and AMFs 1-05. The mobile communication system according to an embodiment of the present disclosure can be a next-generation mobile communication system, and the base stations can be next-generation base stations.

[0039] exist Figure 1 In this context, gNBs 1-10 correspond to Evolved Node Bs (eNBs) in existing LTE systems. gNBs 1-10 are connected to NR UEs 1-15 via radio channels and can provide superior service compared to existing Node Bs (1-20). In next-generation mobile communication systems according to embodiments of this disclosure, all user services are served through a shared channel. Therefore, a device is needed to collect UE state information for scheduling, such as buffer state, available transmit power state, and channel state, which is handled by gNBs 1-10. A gNB typically controls multiple cells. To achieve ultra-high-speed data transmission compared to existing LTE, bandwidths greater than or equal to the existing maximum bandwidth can be supported, and beamforming techniques can be additionally combined using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as the radio access technology. Furthermore, an Adaptive Modulation and Coding (hereinafter referred to as AMC) scheme that determines the modulation scheme and channel coding rate based on the UE's channel state is applied.

[0040] AMF 1-05 can perform functions such as mobility support, bearer configuration, and quality of service (QoS) configuration. AMF 1-05 is the device responsible for the UE's mobility management functions and various control functions, and is connected to multiple base stations. Furthermore, the mobile communication system according to embodiments of this disclosure can be linked to an existing LTE system, and AMF 1-05 is connected to MME 1-25 via a network interface. MME 1-25 is connected to eNB 1-30, which serves as an existing base station. A UE supporting LTE-NR dual connectivity (DC) can send and receive data (1-35) while maintaining connections with eNB 1-30 and gNB 1-10.

[0041] Figure 2 This is a diagram illustrating radio access state transitions in a mobile communication system according to an embodiment of the present disclosure.

[0042] The mobile communication system according to embodiments of this disclosure has three radio access states (Radio Resource Control (RRC) states) or RRC modes. Connected mode (RRC_CONNECTED) 2-05 is a radio access state in which the UE can transmit and receive data. Idle mode (RRC_IDLE) 2-30 is a radio access state in which the UE monitors and sends paging messages for the UE. These two modes are radio access states that are also used in existing LTE systems, and their detailed descriptions are the same as those of existing LTE systems. The mobile communication system according to embodiments of this disclosure can be a next-generation mobile communication system.

[0043] In a mobile communication system according to embodiments of this disclosure, a new inactive (RRC_INACTIVE) radio access state 2-15 is defined. In the inactive radio access state, the UE context is maintained between the base station and the UE, and paging based on the radio access network (RAN) is supported. The characteristics of the new radio access state (RRC inactive) are listed below: - Cell reselection mobility; - A CN-NR RAN connection has been established for the UE (both are C / U plane (control plane / user plane)); - The UE AS (access stratum) context is stored in at least one gNB and UE; - Paging is initiated by NR RAN; - RAN-based notification areas are managed by NR RAN; - The NR RAN knows the RAN-based notification area to which the UE belongs; According to embodiments of this disclosure, a UE in an inactive radio access state can transition to connected mode or idle mode using specific procedures. The UE transitions from INACTIVE mode to connected mode according to a recovery procedure, and from connected mode to INACTIVE mode using a release procedure (2-10) including pause configuration information. This procedure is performed by sending and receiving one or more RRC messages between the UE and the base station, and consists of one or more steps. Alternatively, the UE can transition from INACTIVE mode to idle mode via a release procedure (2-20) after recovery. The transition between connected mode and idle mode follows existing LTE technology. That is, the transition between modes is performed via an establishment or release procedure (2-25).

[0044] Figure 3 This is a flowchart illustrating a signaling-based Quality of Experience (QoE) measurement configuration and reporting process according to an embodiment of this disclosure.

[0045] exist Figure 3 In the embodiments described herein, for ease of description, UE AS 3-05 and UE APP 3-45 are described separately; however, UE AS 3-05 and UE APP 3-45 are included in the UE, and the operation of UE AS 3-05 and UE APP 3-45 can be understood as the operation of the UE. UE AS 3-05 can be interpreted as the AS of the UE or the AS layer of the UE, and UE APP 3-45 can be interpreted as the APP of the UE or the APP layer of the UE. This relationship between UE AS, UE APP, and UE can be applied and interpreted in the same way as in this disclosure. Figure 3 The embodiments described herein can also be applied and interpreted in the same way as those described in this disclosure. Figure 4 , Figure 5 and Figure 6 Examples of implementations.

[0046] refer to Figure 3According to embodiments of this disclosure, UE AS 3-05 may send information (e.g., qoe-Streaming-MeasReport, qoe-MTSI-MeasReport, qoe-VR-MeasReport) to base station (or NG-RAN) 3-15 indicating whether UE AS 3-05 supports Quality of Experience (QoE) measurements for each service type (e.g., streaming media, multimedia telephony services for Internet Protocol (IP) Multimedia Subsystem (IMS) (MTSI), virtual reality (VR)). For example, UE may send a UE capability message (e.g., UECapabilityInformation) (3-10) to base station containing information indicating whether UE supports QoE measurements. Before UE sends the UE capability message, base station 3-15 may send a message requesting UE capability information (e.g., UECapabilityEnquiry) to UE. Additionally, the UE can report to the base station via UE capability messages whether it supports RAN-visible QoE measurements for each service type (e.g., ran-VisibleQoE-Streaming-MeasReport and ran-VisibleQoE-VR-MeasReport). Furthermore, the UE can report to the base station via UE capability messages whether it supports uplink (UL) RRC segments used for QoE reporting messages (e.g., ul-MeasurementReportAppLayer-Seg). UE capability messages include Abstract Syntax Symbol 1 (ASN.1) information as shown in Table 1 below, and descriptions of the information in Table 1 and related parameters (i.e., QoE measurement parameters) are referenced in Table 2 below.

[0047] [Table 1]

[0048] [Table 2]

[0049] The types of services that can be supported in LTE can include streaming media and MTSI. In the case of NR, Rel-17 has defined additional support for virtual reality (VR) services in addition to the types of services that can be supported in LTE, and further versions have defined additional support for services such as Multimedia Broadcast Multicast Service (MBMS) and Extended Reality (XR).

[0050] According to embodiments of this disclosure, Operation Management and Maintenance (OAM) 3-20 can provide QoE measurement configuration information (3-30) to the Core Network (CN) 3-25. CN 3-25, having received the QoE measurement configuration information, can send the QoE measurement configuration information to the base station 3-15 and activate QoE measurement based on the QoE measurement configuration information (3-35).

[0051] According to embodiments of this disclosure, base station 3-15, which has received configuration information from CN 3-25, can deliver the QoE configuration information to UE AS 3-05 (3-40) via RRC messages (e.g., RRCReconfiguration or RRCResume messages). The RRC message may include IE (APPLayerMeasConfig) as shown in Table 3 below, and the description of the relevant parameters is shown in Table 4 below.

[0052] [Table 3]

[0053] [Table 4]

[0054] Additionally, according to embodiments of this disclosure, the operation of UE AS 3-05, which has received QoE configuration information from the base station via RRC messages, can follow the description in Table 5 below.

[0055] [Table 5]

[0056]

[0057] As described above, for the QoE measurement configuration included in measConfigAppLayerToAddModList, UEAS layer 3-05 can deliver some or all of the configuration information to the upper layer or UE application layer (UE APP 3-45) (3-50) via AT commands. Additionally, UEAS layer 3-05 can send an AT command to UE APP 3-45, which instructs / commands the deletion of the configuration information stored for the QoE measurement configuration included in measConfigAppLayerToAddReleaseList.

[0058] According to embodiments of this disclosure, UE APP 3-45 can perform QoE measurements based on received configuration information. Additionally, UE APP 3-45 can report measurement results (3-55) based on the configuration information to UE AS 3-05 via AT commands.

[0059] According to embodiments of this disclosure, UE AS 3-05, having received a measurement result report from the UE APP, can report the measurement result (3-60) to base station 3-15 via an RRC message (e.g., a MeasurementReportAppLayer message). Signaling radio bearer (SRB) 4 can be used for QoE measurement result reporting. The MeasurementReportAppLayer message may include ASN.1 information as shown in Table 6 below, and descriptions of the relevant parameters are referenced in Table 7 below.

[0060] [Table 6]

[0061]

[0062] [Table 7]

[0063] In addition, according to embodiments of this disclosure, the specific process by which the UE AS reports measurement results can follow the operations described in Table 8 below.

[0064] [Table 8]

[0065]

[0066] According to embodiments of this disclosure, base station 3-15 can deliver measurement result reports received from the UE to the final server (Tracking Collection Entity (TCE) or Measurement Collection Entity (MCE)) 3-65 (3-70) that collects measurement reports.

[0067] Figure 4 This is a flowchart illustrating a managed QoE measurement configuration and reporting process according to an embodiment of the present disclosure.

[0068] In the operations performed during the management-based QoE configuration and reporting process, for those related to Figure 3 Operations that are identical, similar, or repetitive to those performed during the signaling-based QoE configuration and reporting process described herein are omitted from separate description. (See references.) Figure 4 This section focuses on describing the management-based QoE configuration and reporting process, highlighting its differences from signaling-based processes. It includes references to the base station's request for the UE to report its capabilities and the UE's reporting of its capabilities to the base station (reference 4-25). Figure 3 The operations described in [the document]. Regarding [the specific operations]... Figure 3 For the same message, as well as the information, parameters and their interpretation contained in the message, please refer to [reference]. Figure 3 The corresponding configuration.

[0069] According to embodiments of this disclosure, in a scheme related to a managed QoE configuration and reporting process, OAM 4-05 can directly send the QoE measurement configuration to base station 4-10 without going through CN, and can instruct the base station to activate the UE's QoE measurement based on the QoE measurement configuration (4-15). Base station 4-10, having received the QoE measurement configuration, can search for single or multiple UEs that meet at least one condition (e.g., area range, application layer capability, and service type). Base station 4-10 can send / deliver the QoE measurement configuration (4-20) to at least one of the searched single or multiple UEs via RRC messages (e.g., RRCReconfiguration messages or RRCResume). Specific operation is described in operation 3-40. Each UE that has received the RRC message can exchange configurations and measurement results for QoE measurement between UE AS 4-50 and UE APP 4-55 via AT commands between UE AS 4-50 and UE APP 4-55, as described above. Figure 3 As described in [the document]. For specific operations, refer to operations 3-50 and 3-55. UE AS 4-50 reports the measurement results obtained from UE APP 4-55 to base station 4-10 via RRC message. For specific operations, refer to operation 3-60. Base station 4-10 can deliver the measurement results obtained from the UE to TCE / MCE 4-60. For specific operations, refer to operation 3-65.

[0070] Figure 5 This is a flowchart illustrating the RAN visible QoE measurement configuration and reporting process according to an embodiment of the present disclosure.

[0071] According to embodiments of this disclosure, the RAN visible QoE measurement configuration and reporting process can respectively follow the above description. Figure 3 and Figure 4The schemes described herein relate to signaling-based QoE configuration and reporting procedures as well as management-based QoE configuration and reporting procedures. In this case, QoE measurements are configured by OAM, and the QoE measurement reports generated according to the configuration are collected by TCE / MCE, and the QoE measurement reports can be used by the operator for network optimization. However, the base station may not read or understand the reports on OAM-based QoE measurements sent by the UE. More specifically, in the MeasurementReportAppLayer message, the measurement reports generated by the UE application layer are included in the measurementReportAppLayerContainer, but because the measurement reports generated by the UE application layer are stored as octet strings, the base station or the base station's RRC layer may not read or interpret the measurement reports generated by the UE application layer. To address these issues, i.e., to enable the base station to read the UE's QoE measurement reports and use them for network optimization (such as radio resource management), RAN-visible QoE (RVQoE) measurements can be used.

[0072] According to embodiments of this disclosure, RVQoE measurement can be defined as limited to a specific service type (e.g., streaming, VR). The UE can report to the base station whether it supports RVQoE measurement for each service type (e.g., streaming, VR) (5-05). In this case, the UECapabilityInformation message can be used. For example, for streaming services, the UE can include or set the ran-VisibleQoE-Streaming-MeasReport parameter in the UECapabilityInformation message and send the ran-VisibleQoE-Streaming-MeasReport parameter to the base station; and for VR services, the UE can include or set the ran-VisibleQoE-VR-MeasReport parameter in the UECapabilityInformation message and send the ran-VisibleQoE-VR-MeasReport parameter to the base station.

[0073] According to embodiments of this disclosure, based on RVQoE measurements sent by the UE to the base station regarding whether the UE supports each service type (e.g., streaming media, VR), the base station can determine whether the UE supports RVQoE measurements for each service type. Based on the information received from the UE regarding whether RVQoE measurements are supported, the base station can generate an RVQoE measurement configuration and send the generated RVQoE measurement configuration to the UE (5-10). In this case, the RVQoE measurement configuration can be sent together with an OAM-based QoE measurement configuration. (See OAM-based QoE measurement configuration reference.) Figure 3 or Figure 4 The corresponding configuration. RVQoE measurement configuration can be included within the RRCReconfiguration or RRCResume message. The base station can instruct the UE to configure or release RVQoE measurements by setting or releasing the ran-VisibleParameters parameter within the AppLayerMeasConfig information element (IE). The ran-VisibleParameters parameter can include the RAN-VisibleParameters IE. Therefore, some or all of the following parameters can be provided to the UE from the base station.

[0074] - RVQoE Measurement Report Periodicity (ran-Visible Periodicity): The UE AS or UE APP can send RVQoE measurement reports periodically.

[0075] - Maximum number of reportable buffer levels (numberOfBufferLevelEntries): When reporting RVQoE measurements, the UE AS or UEAPP may include multiple buffer levels, and the number of buffer levels less than or equal to the set value of numberOfBufferLevelEntries can be included in the RVQoE measurement report.

[0076] - Whether to report playback delay at media startup (reportPlayoutDelayForMediaStartup): When the value of reportPlayoutDelayForMediaStartup is indicated as true, the UE AS or UE APP can send an RVQoE report that includes the playback delay at media startup. If the value of reportPlayoutDelayForMediaStartup is indicated as false, the UE may not include the playback delay at media startup in the RVQoE report.

[0077] According to embodiments of this disclosure, the UE AS layer can deliver configuration information (such as the aforementioned ran-VisiblePeriodicity) to the UE APP layer (5-15). In this case, the RVQoE measurement configuration can be delivered to the APP layer together with the OAM-based QoE measurement configuration. The delivery reference for the OAM-based QoE measurement configuration is as follows: Figure 3 or Figure 4The corresponding configuration. The UE APP can perform QoE measurements based on the RVQoE measurement configuration information to generate an RVQoE measurement report, and send the generated RVQoE measurement report to the UE AS layer (5-20). In this case, the RVQoE measurement report can be delivered to the AS layer together with the OAM-based QoE measurement report. OAM-based QoE measurement report reference. Figure 3 or Figure 4 The corresponding configuration.

[0078] The UE AS layer that has received the RVQoE measurement report can deliver / send / report the delivered RVQoE measurement report to the base station (5-25). In this case, the RVQoE measurement report can be delivered / send / reported to the base station together with the OAM-based QoE measurement report. In step 5-25, the RVQoE measurement report can be sent via the RAN-VisibleMeasurements IE within the MeasurementReportAppLayer message, and this IE can include some or all of the following parameters.

[0079] - App Layer Buffer Level List: The UE can include / report multiple buffer levels measured by the UE App using this parameter. The number included may be limited by the numberOfBufferLevelEntries configuration in the RVQoE settings.

[0080] - Playout Delay For Media Startup: The UE can include / report the playback delay at media startup using this parameter, and the value can be indicated in milliseconds. If reportPlayoutDelayForMediaStartup is set to true in the RVQoE configuration, the UE can include this parameter in the RVQoE measurement report.

[0081] - PDU Session ID List (pdu-SessionIdList): This parameter allows the UE to indicate the (multiple) Protocol Data Unit (PDU) sessions used in the application data stream as the subject of RVQoE measurement. After receiving the RVQoE measurement report from the UE, the base station can identify, based on this parameter, which PDU(s) session the RVQoE value (e.g., buffer level and playback delay) layer was measured for, and can optimize resource allocation and scheduling for the (multiple) PDU(s) indicated by this parameter based on the identification results.

[0082] According to embodiments of this disclosure, a base station can read RVQoE reports and perform network optimization using the read RVQoE reports. For example, if the base station determines, based on the RVQoE report, that a particular UE is experiencing an unsatisfactory / poor QoE for a particular service, the base station allocates a larger amount of radio resources to the UE identified as experiencing an unsatisfactory / poor QoE, thereby improving the QoE of the UE identified as experiencing an unsatisfactory / poor QoE.

[0083] According to embodiments of this disclosure, the QoE configuration information (e.g., 3-35 or 4-15) received by the base station may include area scope information (e.g., AreaScope). The base station can use the corresponding information to determine the range of the area where the UE should perform QoE measurements in connected mode. For example, when the UE moves out of the corresponding area scope, the base station can stop the UE's QoE measurements by releasing the QoE configuration.

[0084] According to embodiments of this disclosure, the QoE configuration information (e.g., 3-50 or 4-30) received by the UE application layer (terminal APP or UE APP) may include area range information (e.g., LocationFilter). The UE APP can use the corresponding information to confirm the range of the area where the UE should perform QoE measurements. For example, when the UE APP moves out of the corresponding area range, the UE APP may not initiate a new QoE measurement session. However, the UE may continue to maintain the ongoing QoE measurement session (e.g., unless the UE requests QoE configuration from the base station).

[0085] Figure 6 This is a flowchart illustrating a configuration and reporting process for a UE to support QoE measurements in connected mode, as well as inactive and idle modes, according to an embodiment of this disclosure.

[0086] 3GPP standardized support for QoE measurement in connected mode in Release 17. Extending this, a method is needed to support QoE measurement not only for connected mode (RRC_CONNECTED) but also for inactive mode (RRC_INACTIVE) and idle mode (RRC_IDLE) of Multicast Broadcast Service (MBS). For MBS service, the QoE configuration / measurement / reporting process between the UE and the base station in connected mode (RRC_CONNECTED) and inactive mode (RRC_INACTIVE) and idle mode (RRC_IDLE) can be as follows.

[0087] In step 6-15, base station 6-05 and UE AS 6-10 can establish (or configure) an RRC connection.

[0088] In step 6-20, base station 6-05 may send a UE capability query message (e.g., UECapabilityEnquiry) to the UE (UE AS 6-10). Upon receiving the UE capability query message, the UE may send a UE capability message (e.g., UECapabilityInformation) to base station 6-05. The UE may send a UE capability message that includes a support capability indicator related to QoE measurement. For example, the UE may send a UE capability message to base station 6-05 that includes information indicating whether QoE measurement is supported for MBS (e.g., broadcast) service. For example, the UE may send information to base station 6-05 indicating whether QoE measurement is supported not only in connected mode (RRC_CONNECTED) but also in inactive mode (RRC_INACTIVE) and idle mode (RRC_IDLE). Figure 6 Steps 6-20 can correspond to Figure 4 Steps 4-25 or Figure 3 Steps 3-10. For specific instructions, please refer to [link / reference]. Figure 3 and Figure 4 The corresponding operation.

[0089] In step 6-25, base station 6-05 can provide QoE configuration information to UE AS 6-10. Figure 6 Steps 6-25 can correspond to Figure 4 Steps 4-20 or Figure 3 Steps 3-40. For example, the QoE configuration information may include QoE measurement configuration information for MBS (e.g., broadcast) services. For example, the QoE configuration information may include configuration information for QoE measurements not only in connected mode (RRC_CONNECTED), but also in inactive mode (RRC_INACTIVE) and idle mode (RRC_IDLE). UE AS 6-10 may deliver the QoE configuration information received from base station 6-05 to UE APP 6-12 (step 6-27). Figure 6 Steps 6-27 can correspond to Figure 4 Steps 4-30 or Figure 3 Steps 3-50. For specific instructions, please refer to [link / reference]. Figure 3 and Figure 4 The corresponding operation.

[0090] In step 6-30, when UE AS 6-10 is in connected mode, UE APP 6-12 can use QoE configuration information to perform QoE measurements for MBS services (e.g., when MBS services are received).

[0091] In step 6-32, UE APP 6-12 can deliver the QoE measurement results or measurement report for MBS service to UE AS 6-10. Figure 6 Steps 6-32 can correspond to Figure 3 Steps 3-55 or Figure 4 Steps 4-35. For specific instructions, please refer to [link / reference]. Figure 3 and Figure 4 The corresponding operation.

[0092] In step 6-35, UE AS 6-10 can report the QoE measurement report received from UE APP 6-12 to base station 6-05. For example, if the UE is in connected mode and base station 6-05 is configured with an SRB (SRB4 or SRB5) for reporting QoE measurements, the UE can report the QoE measurement report to the base station. When the above conditions are met, the UE can immediately report the QoE measurement report to the base station. Figure 6 Steps 6-35 can correspond to Figure 3 Steps 3-60 or Figure 4 Steps 4-40. For specific instructions, please refer to [link / reference]. Figure 3 and Figure 4 The corresponding operation.

[0093] In step 6-40, base station 6-05 sends an RRC release message to the UE, and the UE that has received the RRC release message can switch to inactive mode or idle mode. Even in inactive mode or idle mode, the UE can still receive MBS service.

[0094] In step 6-45, UE APP 6-12 can perform measurements for the MBS service. UE AS 6-10 receives the MBS service when in inactive or idle mode, and UE APP 6-12 can perform QoE measurements for the received MBS service. The QoE measurements can be performed using the QoE configuration information received in step 6-25.

[0095] In step 6-47, UE APP 6-12 can deliver the QoE measurement results or measurement report generated by the QoE measurement to UE AS 6-10.

[0096] In step 6-48, since UE AS 6-12 is in inactive or idle mode, UE AS 6-12 may not immediately send the QoE measurement report to the base station, but may instead store the QoE measurement report. For example, UE APP 6-12 may deliver the generated QoE measurement report to UE AS 6-10, and UE AS 6-10 may store the QoE measurement report.

[0097] In steps 6-50, the UE may establish (or configure) an RRC connection with the previous base station 6-05 that sent the RRC release message or with the new base station (e.g., RRC establishment or RRC recovery). When the UE establishes an RRC connection with the new base station, the base station operations or operations toward the base station described below can be interpreted as operations toward the base station with which a new connection was established.

[0098] In steps 6-55, when the UE establishes an RRC connection in step 6-50, the UE can indicate to the base station via the RRCSetupComplete or RRCResumeComplete message that the UE is storing QoE measurement reports (e.g., measurements taken in inactive / idle mode) or MBS QoE configuration information (e.g., availability). The RRC messages used for measurement reports are not limited to these, and a UE transitioning from an RRC inactive or idle state to a connected state can send information to the base station indicating that the UE is storing QoE configuration information for the base station used for connection.

[0099] Base station 6-05, having already received availability information, can configure an SRB (e.g., SRB4 or SRB5) for sending QoE measurement reports, thereby allowing the UE to send QoE measurement reports. The UE can perform QoE measurement reporting based on the SRB configuration used for sending QoE measurement reports. Additionally, the UE can send stored MBS QoE configuration information to base station 6-05.

[0100] In embodiments of this disclosure, the UE can transition to idle mode in steps 6-40. Even while in idle mode, the UE can store / maintain its QoE configuration to perform MBS QoE measurements (6-45). However, if the UE establishes an RRC connection with a new base station (hereinafter referred to as the base station) via receiving an RRCSetup message (6-50), the base station may not have the MBS QoE configuration possessed by the UE. Therefore, the base station may need to retrieve the UE's QoE configuration. The base station can retrieve the UE's QoE configuration from either the UE or the AMF (CN). In a method for the base station to retrieve QoE configuration information from the UE (a UE-based scheme), the UE can store the QoE configuration information provided by the previous base station (6-25) and then send the QoE configuration information to the new base station after establishing an RRC connection with the new base station via idle mode (6-50). In the method for a base station to retrieve QoE configuration information from a CN (CN-based scheme), the CN may store the QoE configuration information and then deliver the QoE configuration information to the new base station after the UE establishes an RRC connection with the new base station in idle mode (6-50). Each QoE configuration information of the UE retrieved by the new base station may include some or all of the following.

[0101] -QoE Reference

[0102] -TCE or MCE address or ID

[0103] - RRC-level QoE configuration ID (e.g., measConfigAppLayerID)

[0104] -Service Type

[0105] -QoE measurement type (whether it is a signaling-based QoE configuration or a management-based QoE configuration).

[0106] -Information regarding available RAN-visible QoE indicators

[0107] - Area information where new QoE measurements can be performed or started.

[0108] The new base station can retrieve this information or obtain information about the QoE configuration configured for the UE, thereby adding / changing / releasing the UE's QoE configuration and delivering the QoE measurement reports received from the UE to the correct TCE / MCE.

[0109] Table 9 shows a portion of the operation in which the UE generates / configures the QoE Measurement Report AppLayer for transmission in the CR (R2-2314024) agreed in the 3GPP RAN2 working group for TS 38.331.

[0110] [Table 9]

[0111] According to Table 9, "Each stored configforRRC-IdleInactive is set to true for application layer measurement configurations" can indicate each MBS QoE measurement configuration stored in the UE. For each QoE configuration, if the UE has not sent the stored QoE configuration information ("appLayerIdleInactiveConfig") to the base station since switching to connected mode, the UE can configure / include the stored QoE configuration information ("appLayerIdleInactiveConfig") in the QoE measurement report message (MeasurementReportAppLayer) to be sent, and send that QoE configuration information.

[0112] In embodiments of this disclosure, after transitioning to inactive mode in steps 6-40, the UE can send an RRCresumeRequest in steps 6-50 and receive an RRCresume message from the new base station to transition to connected mode. According to Table 9, after transitioning to connected mode, the UE can then send MBS QoE measurement configuration to the base station. However, this configuration information may already be available to the base station. This is because the base station may have successfully retrieved all of the UE's configuration information (including MBS QoE configuration information) from a previous base station (e.g., the base station that transitioned the UE to inactive mode in step 6-40) and sent an RRCresume message to the UE. Therefore, the UE may not need to send the MBS QoE measurement configuration to the base station, potentially leading to a waste of radio resources and energy for both the UE and the base station. In embodiments of this disclosure, if the inactive mode UE transitions to connected mode by receiving an RRCresume message after sending an RRCresumeRequest, the MBS QoE configuration information may not be sent to the base station.

[0113] In embodiments of this disclosure, after transitioning to inactive mode in steps 6-40, the UE may send an RRCResumeRequest in steps 6-50, but receive an RRCSetup message from the new base station to transition to connected mode. In this case, unlike the UE, the base station may not have MBS QoE measurement configuration. This is because the base station may have failed to retrieve the UE's configuration information (including MBS QoE configuration information) from the previous base station (e.g., the base station that transitioned the UE to inactive mode in step 6-40), and therefore may have already sent an RRCSetup message instead of an RRCResume message. Therefore, the UE may need to send MBS QoE measurement configuration to the base station. In embodiments of this disclosure, if the inactive mode UE has not yet sent MBS QoE configuration information to the base station since transitioning to connected mode by receiving an RRCSetup message after sending an RRCResumeRequest, the UE may send MBS QoE configuration information to the base station.

[0114] In embodiments of this disclosure, the connected mode UE in steps 6-30 may perform an RRC connection reconstruction operation due to reasons such as radio link failure (RLF) detection, handover failure, integrity check failure, RRC connection reconfiguration failure, SCG change failure, and SCG configuration failure. To maintain the RRC connection, the UE may send an RRCReestablishmentRequest message to the base station. If the base station that has received the RRCReestablishmentRequest message has valid configuration information or context for the UE (e.g., including MBS QoE configuration information) or has successfully retrieved valid configuration information or context for the UE, the base station may send an RRCReestablishment message to the UE. If the base station does not have valid configuration information or context for the UE (e.g., including MBS QoE configuration information) or has failed to retrieve valid configuration information or context, the base station may send an RRCSetup message to the UE. According to Table 9, if the UE has previously sent MBS QoE configuration to the base station after switching to connected mode, the UE may not need to send MBS QoE configuration to the base station. However, even if the UE sends MBS QoE configuration while in connected mode, when the UE sends an RRCReestablishmentRequest message for the same reason as RLF and receives an RRCSetup message in response to the RRCReestablishmentRequest message, the base station may not have the MBS QoE configuration information. Therefore, the UE may need to send the stored MBS QoE configuration information to the base station again. In embodiments of this disclosure, when a UE in connected mode receives an RRCSetup message after sending an RRCReestablishmentRequest, the UE can send the MBS QoE configuration to the base station (even if the MBS QoE configuration has been sent previously). In embodiments of this disclosure, when a UE in connected mode receives an RRCReestablishment message after sending an RRCReestablishmentRequest, the UE may not send the MBS QoE configuration to the base station. This is because the base station may already have the MBS QoE configuration information.

[0115] In embodiments of this disclosure, when a UE in connected mode receives an RRCSetup after sending an RRCReestablishmentRequest, the UE can release the MBS QoE configuration and may not send the MBS QoE configuration to the base station. This is because the base station may not have the MBS QoE configuration information.

[0116] Table 10 illustrates a portion of the operations in which the UE generates / configures the QoE measurement report message (MeasurementReportAppLayer) for transmission, as an example embodiment of this disclosure.

[0117] [Table 10]

[0118] Table 11 shows some of the QoE configuration-related operations when the UE switches to an inactive mode (e.g., steps 6-40).

[0119] [Table 11]

[0120] According to Table 11, when transitioning to inactive mode (or prior to that), the UE can store QoE configuration information (“Application Layer Measurement Configuration”) in the UE inactive AS context. The QoE configuration information may include MBS QoE configuration information and / or MBSRAN-visible QoE configuration information. This is to allow the UE to reuse the QoE configuration information in the future when connecting to a new base station (6-50). The new base station can also store, restore, and use the QoE configuration information.

[0121] Table 12 shows some of the QoE configuration-related operations when the UE switches to idle mode (e.g., 6-40).

[0122] [Table 12]

[0123] According to Table 12, when the UE transitions to idle mode (or prior to it), the UE can release each QoE configuration information that is not used in inactive / idle mode (used only in connected mode) or that does not involve MBS services ("for each application layer measurement configuration that is not set to true for configForRRC-IdleInactive"). The UE can retain / store the QoE configuration information or MBS QoE configuration information to be used in inactive / idle mode without releasing it. MBS QoE configuration information may include MBS RAN-visible QoE configuration information. This is to allow the UE to reuse QoE configuration information in the future when connecting to a new base station (6-50). The new base station can also store QoE configuration information and restore and use it.

[0124] In embodiments of this disclosure, MBS RAN Visible QoE configuration information may not be reused by the new base station in the future. The MBS RAN Visible QoE configuration information configured by the previous base station may be information necessary only for network optimization of the cells managed by that previous base station. When the UE establishes an RRC connection with the new base station after switching to inactive / idle mode, the MBS RAN Visible QoE configuration information may be unused. This is because the new base station may not require RVQoE measurements, and even if it does, the new base station can configure the RVQoE measurements for the UE itself according to the desired configuration. Therefore, saving the MBS RAN Visible QoE (RVQoE) configuration when the UE switches to inactive or idle mode may be a waste of resources. For example, when the UE switches to inactive / idle mode, the memory used by both the UE and the base station to store the above configuration may be wasted. Additionally, when a UE connects to a new base station after transitioning to idle mode, radio resources may be wasted not only restoring the MBS QoE configuration to the new base station but also the MBS RAN Visible QoE (RVQoE) configuration. Accordingly, in embodiments of this disclosure, when a UE transitions to inactive or idle mode, the MBS QoE measurement configuration (excluding the RVQoE configuration) can be maintained, but the MBS RVQoE measurement configuration can be released. For this purpose, the UE AS can instruct the upper layer (UE APP) to release the MBS RVQoE measurement.

[0125] In embodiments of this disclosure, when the UE transitions to idle mode, the MBS QoE measurement configuration (excluding the RVQoE configuration) can be maintained, but the MBS RVQoE measurement configuration can be released. To this end, the UE AS can instruct the upper layer (UE APP) to release the MBS RVQoE measurement. When transitioning to inactive mode, the UE can maintain both the MBS QoE and MBS RVQoE measurement configurations without releasing them. This is to allow a new base station to reuse the MBS RVQoE measurement configuration only when transitioning to inactive mode. After transitioning to inactive mode, the UE AS can move to another base station or cell via cell reselection. Even if the UE performs RVQoE measurements in inactive mode, this may not be immediately reported to the current base station or cell, but may be reported later when an RRC connection is established with the new base station. However, considering that RVQoE measurement reports are used for real-time network optimization, such delayed reporting may be unnecessary. Furthermore, the new base station may not be interested in RVQoE measurements obtained by the UE from another base station or cell other than the new base station itself when it is in inactive mode. Therefore, when transitioning to inactive mode, the UE AS can instruct the UE APP to stop RVQoE measurements without releasing the RVQoE configuration (e.g., by defining / using a new AT command). Subsequently, when the UE AS transitions from inactive mode to connected mode (e.g., upon receiving an RRCresume), it can instruct the UE APP to resume RVQoE measurements (e.g., by defining / using a new AT command) (unless the new base station releases MBS(RV)QoE).

[0126] In embodiments of this disclosure, when transitioning to inactive / idle mode, the UE can maintain the MBS QoE measurement configuration and the MBS RVQoE measurement configuration without releasing them. This is to allow the new base station to reuse the MBS RVQoE measurement configuration. After the UE AS transitions to inactive / idle mode, the UE can move to another base station or cell via cell reselection. Even if the UE performs RVQoE measurements in inactive / idle mode, this may not be immediately reported to the current base station or cell, but may be reported later when an RRC connection is established with the new base station. However, considering that RVQoE measurement reports are used for real-time network optimization, such delayed reporting may be unnecessary. Furthermore, the new base station may not be interested in RVQoE measurement results obtained by the UE from another base station or cell other than itself while in inactive mode. Therefore, when transitioning to inactive / idle mode, the UE AS can instruct the UE APP to stop RVQoE measurements without releasing the RVQoE configuration (e.g., by defining / using a new AT command). Subsequently, when the UE AS transitions from inactive / idle mode to connected mode (e.g., upon receiving RRCResume / RRCSetup), it can instruct the UE APP to resume RVQoE measurements (e.g., by defining / using a new AT command) (unless the new base station releases MBS(RV)QoE). In embodiments of this disclosure, the UE AS may not instruct the UE APP to stop / resume RVQoE measurements, and the UE APP can continue performing RVQoE measurements even in inactive / idle mode. Therefore, the generated RVQoE measurement results can be delivered to the UE AS. The UE AS may discard RVQoE measurement results received in inactive / idle mode without storing them. This is because the RVQoE measurement results may not be useful for new base stations to be connected later.

[0127] In embodiments of this disclosure, the UE can send the aforementioned availability to the new base station via an RRCReconfigurationComplete message during handover. This is because even if the UE has already indicated availability to the previous base station (e.g., RRCResumeComplete or RRCSetupComplete), the new base station connected via the handover connection may not be aware of the UE's availability. In this case, the new base station may not configure an SRB (e.g., SRB4 / 5) to retrieve the QoE measurement report or MBSQoE measurement configuration from the UE. In embodiments of this disclosure, the previous base station can deliver availability to the new base station during handover (e.g., via the Xn interface).

[0128] Figure 7 The illustration shows the configuration of a terminal used in an example of this disclosure.

[0129] refer to Figure 7 The terminal includes a radio frequency (RF) processing unit 7-10, a baseband processing unit 7-20, a storage unit 7-30, and a controller 7-40.

[0130] RF processing unit 7-10 can perform functions for transmitting and receiving signals via a radio channel, such as signal band conversion and amplification. Specifically, RF processing unit 7-10 can up-convert the baseband signal provided by baseband processing unit 7-20 into an RF band signal, and then transmit the RF band signal via an antenna, and down-convert the RF band signal received via the antenna back into a baseband signal. For example, RF processing unit 7-10 may include a transmit filter, receive filter, amplifier, mixer, oscillator, digital-to-analog converter (DAC), analog-to-digital converter (ADC), etc. Although only one antenna is illustrated in the figures, the terminal may have multiple antennas. Additionally, RF processing unit 7-10 may include multiple RF chains. Furthermore, RF processing unit 7-10 can perform beamforming. For beamforming, RF processing unit 7-10 can adjust the phase and amplitude of each signal transmitted and received through multiple antennas or antenna elements. Additionally, the RF processing unit can perform MIMO and receive multiple layers during MIMO operation.

[0131] The baseband processing unit 7-20 can perform the conversion function between baseband signals and bitstreams according to the physical layer specifications of the system. For example, during data transmission, the baseband processing unit 7-20 can encode and modulate the transmitted bit string to generate complex symbols. Additionally, during data reception, the baseband processing unit 7-20 can demodulate and decode the baseband signal provided from the RF processing unit 7-10 to reconstruct the received bit string. For example, according to the Orthogonal Frequency Division Multiplexing (OFDM) scheme, during data transmission, the baseband processing unit 7-20 can encode and modulate the transmitted bit string to generate complex symbols, map the complex symbols to subcarriers, and then construct OFDM symbols through inverse Fast Fourier Transform (IFFT) operations and cyclic prefix (CP) insertion. Furthermore, during data reception, the baseband processing unit 7-20 can segment the baseband signal provided from the RF processing unit 7-10 into OFDM symbol units, reconstruct the signal mapped to the subcarriers through Fast Fourier Transform (FFT) operations, and then reconstruct the received bit string through demodulation and decoding.

[0132] The baseband processing unit 7-20 and the RF processing unit 7-10 can transmit and receive signals as described above. Accordingly, the baseband processing unit 7-20 and the RF processing unit 7-10 can be referred to as a transmitting unit, a receiving unit, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit 7-20 and the RF processing unit 7-10 may include multiple communication modules to support various different radio access technologies. Additionally, at least one of the baseband processing unit 7-20 and the RF processing unit 7-10 may include different communication modules to process signals in different frequency bands. For example, different radio access technologies may include wireless LAN (e.g., IEEE 802.11), cellular networks (e.g., LTE), etc. Furthermore, different frequency bands may include ultra-high frequency (SHF) bands (e.g., 2.0 NRHz, NRhz) and millimeter wave (mmWave) bands (e.g., 60 GHz).

[0133] Storage unit 7-30 can store data such as basic programs, application programs, and configuration information for terminal operation. Specifically, storage unit 7-30 can store information related to a second access node performing wireless communication using radio access technology. Furthermore, storage unit 7-30 can provide the stored data upon request from controller 7-40.

[0134] Controller 7-40 controls the overall operation of the terminal. For example, controller 7-40 can send and receive signals via baseband processing unit 7-20 and RF processing unit 7-10. Additionally, controller 7-40 can write data to and read data from storage unit 7-30. For this purpose, controller 7-40 may include at least one processor. For example, controller 7-40 may include a communication processor (CP) that performs communication control and an application processor (AP) that controls upper layers such as applications, and may include a multi-connection processing unit 7-42 as illustrated in the figures. According to various embodiments of this disclosure, controller 7-40 can control the operation of the terminal. According to various embodiments of this disclosure, controller 7-40 can perform the operation of terminal AS and / or terminal APP.

[0135] Figure 8 The illustration shows the configuration of a base station applied to an example of this disclosure.

[0136] refer to Figure 8 The base station according to the example of this disclosure is configured to include an RF processing unit 8-10, a baseband processing unit 8-20, a backhaul communication unit 8-30, a storage unit 8-40, and a controller 8-50.

[0137] RF processing unit 8-10 can perform functions for transmitting and receiving signals via a radio channel, such as signal band conversion and amplification. Specifically, RF processing unit 8-10 can up-convert the baseband signal provided by baseband processing unit 8-20 into an RF band signal, and then transmit the RF band signal via an antenna, and down-convert the RF band signal received via the antenna back into a baseband signal. For example, RF processing unit 8-10 may include transmit filters, receive filters, amplifiers, mixers, oscillators, DACs, ADCs, etc. Although only one antenna is illustrated in the figures, the base station may have multiple antennas. Additionally, RF processing unit 8-10 may include multiple RF chains. Furthermore, RF processing unit 8-10 can perform beamforming. For beamforming, RF processing unit 8-10 can adjust the phase and amplitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform downlink MIMO operation by transmitting one or more layers.

[0138] The baseband processing unit 8-20 can perform the conversion function between baseband signals and bit strings according to the physical layer specifications of the radio access technology. For example, during data transmission, the baseband processing unit 8-20 can encode and modulate the transmitted bit string to generate complex symbols. Additionally, during data reception, the baseband processing unit 8-20 can demodulate and decode the baseband signal provided from the RF processing unit 8-10 to reconstruct the received bit string. For example, in the case of an OFDM scheme, during data transmission, the baseband processing unit 8-20 can encode and modulate the transmitted bit string to generate complex symbols, map the complex symbols to subcarriers, and then construct OFDM symbols through IFFT operations and CP insertion. Additionally, during data reception, the baseband processing unit 8-20 can segment the baseband signal provided from the RF processing unit 8-10 into OFDM symbol units, reconstruct the signal mapped to the subcarriers through FFT operations, and then reconstruct the received bit string through demodulation and decoding. The baseband processing unit 8-20 and the RF processing unit 8-10 can transmit and receive signals as described above. Accordingly, the baseband processing unit 8-20 and the RF processing unit 8-10 can be referred to as a transmitting unit, a receiving unit, a transceiver, a communication unit, or a wireless communication unit.

[0139] The backhaul communication unit 8-30 can provide an interface for communicating with other nodes within the network. That is, the backhaul communication unit 8-30 can convert bit strings sent from the primary base station to another node (e.g., a secondary base station, core network, etc.) into physical signals, and can also convert physical signals received from another node into bit strings.

[0140] Storage unit 8-40 can store data such as basic programs, application programs, and configuration information for main base station operation. Specifically, storage unit 8-40 can store information about bearers allocated to access terminals, measurement results reported from access terminals, etc. Additionally, storage unit 8-40 can store information used as a basis for determining whether to provide or terminate multiple connections to terminals. Furthermore, storage unit 8-40 can provide the stored data upon request from controller 8-50.

[0141] The controller 8-50 controls the overall operation of the main base station. For example, the controller 8-50 can send and receive signals via the baseband processing unit 8-20 and the RF processing unit 8-10 or via the backhaul communication unit 8-30. Additionally, the controller 8-50 can write data to and read data from the storage unit 8-40. For this purpose, the controller 8-50 may include at least one processor and may include a multi-connection processing unit 8-52 as illustrated in the accompanying drawings.

[0142] Furthermore, the embodiments of this disclosure disclosed in this specification and accompanying drawings are merely specific examples presented to facilitate the description of the technical content of this disclosure and to aid in understanding it, and are not intended to limit the scope of this disclosure. That is, it will be apparent to those skilled in the art that other modifications based on the technical spirit of this disclosure are possible. Additionally, each embodiment can be combined and operated with each other as needed. For example, portions of one embodiment and another embodiment of this disclosure can be combined to operate a base station and a terminal. Furthermore, the embodiments of this disclosure can also be applied to other communication systems, and other modifications based on the technical spirit of the embodiments can be implemented. For example, the embodiments can be applied to LTE systems, 5G systems, NR systems, 6G systems, etc. Therefore, the scope of this disclosure should not be construed as limited to the above embodiments, but should be defined by the appended claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, comprising: Receive a first Radio Resource Control (RRC) message, the first RRC message including a first application layer measurement configuration applied to RRC idle and RRC inactive; Store the first application layer measurement configuration; Receive RRC establishment message from the base station; If the terminal does not send the second application layer measurement configuration included in the measurement report application layer message after receiving the RRC setup message, the parameters of the second application layer measurement configuration are set based on the values ​​stored in the terminal variables; as well as Send measurement report application layer messages to the base station.

2. The method according to claim 1, further comprising: In response to receiving an RRC release message, notify the upper layer to release the radio access network (RAN) visible application layer measurement configuration included in the first application layer measurement configuration.

3. The method according to claim 1, further comprising: If the terminal has a first application layer measurement configuration, an RRC reconfiguration complete message is sent, which includes information indicating that the terminal has a first application layer measurement configuration.

4. The method of claim 1, wherein, If an RRC message other than the RRC setup message is received after storing the first application layer measurement configuration, the terminal does not send a measurement report application layer message.

5. The method of claim 2, wherein, In response to receiving the RRC release message, the terminal does not release information included in the first application layer measurement configuration, except for the RAN-visible application layer measurement configuration.

6. The method according to claim 2, further comprising: Based on the received RRC release message, perform Quality of Experience (QoE) measurements according to the first application layer measurement configuration when the RRC is idle or inactive. The measurement report application layer message includes QoE measurement report information and second application layer measurement configuration.

7. A method performed by a base station in a wireless communication system, comprising: Send an RRC establishment message to a first terminal that stores a first Radio Resource Control (RRC) message, the first RRC message including a first application layer measurement configuration applied to RRC idle and RRC inactive; as well as If the terminal does not send the second application layer measurement configuration after receiving the RRC establishment message, then a measurement report application layer message is received from the terminal. The measurement report application layer message includes the second application layer measurement configuration, which includes parameters set based on values ​​stored in terminal variables.

8. A terminal in a wireless communication system, comprising: transceiver; as well as The controller is configured as follows: Receive a first Radio Resource Control (RRC) message, the first RRC message including a first application layer measurement configuration applied to RRC idle and RRC inactive; Store the first application layer measurement configuration; Receive RRC establishment message from the base station; If the terminal does not send the second application layer measurement configuration included in the measurement report application layer message after receiving the RRC setup message, the parameters of the second application layer measurement configuration are set based on the values ​​stored in the terminal variables; as well as Send measurement report application layer messages to the base station.

9. The terminal according to claim 8, wherein The controller is configured to, in response to receiving an RRC release message, notify the upper layer to release the radio access network (RAN) visible application layer measurement configuration included in the first application layer measurement configuration.

10. The terminal according to claim 8, wherein, The controller is configured to send an RRC reconfiguration complete message if the terminal has a first application layer measurement configuration. The RRC reconfiguration complete message includes information indicating that the terminal has a first application layer measurement configuration.

11. The terminal according to claim 8, wherein, If an RRC message other than the RRC setup message is received after storing the first application layer measurement configuration, the terminal does not send a measurement report application layer message.

12. The terminal according to claim 9, wherein, In response to receiving the RRC release message, the terminal does not release information included in the first application layer measurement configuration, except for the RAN-visible application layer measurement configuration.

13. The terminal according to claim 9, wherein, The controller is configured to: upon receiving an RRC release message, control the execution of Quality of Experience (QoE) measurements based on a first application-layer measurement configuration, whether the RRC is idle or inactive. The measurement report application layer message includes QoE measurement report information and second application layer measurement configuration.

14. A base station in a wireless communication system, comprising: transceiver; as well as The controller is configured to: control the transmission of an RRC establishment message to a first terminal storing a first Radio Resource Control (RRC) message, the first RRC message including a first application layer measurement configuration applied to RRC idle and RRC inactive; as well as If the terminal does not send the second application layer measurement configuration after receiving the RRC establishment message, then a measurement report application layer message is received from the terminal. The measurement report application layer message includes the second application layer measurement configuration, which includes parameters set based on values ​​stored in terminal variables.

Images