Method and apparatus for measuring QOE in inactive mode and idle mode in wireless communication system
By configuring and reporting quality of experience (QoE) in RRC idle or inactive modes in 5G mobile communication systems, the measurement and storage problems of terminals in these modes are solved, and resource utilization efficiency and user experience are improved.
Patent Information
- Application Number
- CN202410572794.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-12
AI Technical Summary
In 5G mobile communication systems, it is difficult for the terminal to effectively measure, store and report quality of experience (QoE) in radio resource control (RRC) inactive mode and/or RRC idle mode, resulting in low resource utilization efficiency and increased processing load, affecting users Experience.
By sending and receiving specific messages between the terminal and the base station, configuring and supporting memory sizes for QoE measurements in the RRC idle or inactive state, QoE measurements and reporting in these modes are achieved, reducing the processing load of the base station and the terminal, And improve user experience.
It improves the efficiency of wireless resources utilization, reduces the processing load of base stations and terminals, enhances the quality of experience (QoE) of application users, and enables communication service providers to support user needs more effectively.
Smart Images

Figure CN118945719A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a wireless communication system. More specifically, the present disclosure relates to a method and apparatus for a terminal in a wireless communication system to measure, store and report quality of experience (QoE) in a radio resource control (RRC) inactive mode and / or an RRC idle mode. Background Art
[0002] The fifth generation (5G) mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, which can be realized not only in the "below 6 GHz" frequency band (e.g., 3.5 GHz) but also in the "above 6 GHz" frequency band including 28 GHz and 39 GHz, which is called millimeter wave. In addition, the implementation of 6G mobile communication technology (called super 5G system) in the terahertz frequency band (e.g., 95 GHz to 3 THz frequency band) has been considered to achieve a transmission rate 50 times faster than that of 5G mobile communication technology and an ultra-low latency of one tenth of that of 5G mobile communication technology.
[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements regarding enhanced mobile broadband (eMBB), ultra-reliability low latency communication (URLLC), and massive machine type communication (mMTC), work is underway on beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves, dynamic operation support numerology for efficient utilization of millimeter wave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods such as LDPC (low-density parity check) codes for large-volume data transmission and polar codes for high-reliability transmission of control information, L2 preprocessing, and standardization of network slicing for providing dedicated networks dedicated to specific services.
[0004] Currently, discussions are underway on improvements and performance enhancements to initial 5G mobile communication technologies for services supported by 5G mobile communication technologies, and physical layer standardization has been conducted on technologies such as V2X (Vehicle to Everything) that assists driving determination of autonomous vehicles and enhances user convenience based on location and status information of vehicles transmitted by vehicles, NR-U (New Radio Unlicensed) that aims to operate systems that comply with various rule-related requirements in unlicensed bands, NR UE energy saving, Non-Terrestrial Networks (NTNs) that are UE satellite direct communications that provide coverage in areas where communication with terrestrial networks is unavailable, and positioning.
[0005] In addition, in the air interface architecture / protocol, standardization is being conducted on technologies such as the Industrial Internet of Things (IIoT) that supports new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (two-step RACH for NR) for simplifying the random access procedure. In the system architecture / service, standardization is also being conducted on a 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.
[0006] With the commercialization of 5G mobile communication systems, the exponentially growing number of networked devices will be connected to the communication network, so it is expected that enhanced functions and performance of 5G mobile communication systems and integrated operations of networked devices will be necessary. To this end, new research is planned related to extended reality (XR) for effectively supporting AR (augmented reality), VR (virtual reality), and MR (mixed reality), 5G performance improvement and complexity reduction using artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.
[0007] In addition, this development of 5G mobile communication systems will not only serve as a basis for developing new waveforms that provide coverage in the terahertz band of 6G mobile communication technology, such as multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), and RIS (reconfigurable smart surface), but will also serve as a basis for developing full-duplex technology that improves the frequency efficiency of 6G mobile communication technology and improves system networks, AI-based communication technology for achieving system optimization using satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services with complexity that exceeds the limits of UE operating capabilities using ultra-high performance communication and computing resources. Summary of the invention
[0008] As discussions on QoE measurement reporting in wireless communication systems increase, there is an increasing need for methods for terminals to more effectively measure, store, and report QoE in RRC inactive mode and / or RRC idle mode.
[0009] According to the embodiments of the present disclosure, the efficiency of wireless resources can be improved, and the processing load of base stations and / or terminals can be reduced. In addition, according to the embodiments of the present disclosure, communication service providers can more effectively improve the QoE of application users.
[0010] According to an embodiment of the present disclosure, a terminal in a wireless communication system includes: a transceiver; and at least one processor connected to the transceiver. The at least one processor is configured to: send a first message including at least one of the first information or the second information to a base station, the first information indicating whether the terminal supports quality of experience (QoE) measurement in a radio resource control (RRC) idle state or an RRC inactive state, and the second information indicating a memory size for performing QoE measurement in an RRC idle state or an RRC inactive state; and receive a second message from the base station, the second message including configuration information about application layer measurement. The terminal supports a memory size greater than the minimum memory size for performing QoE measurement in an RRC idle state or an RRC inactive state.
[0011] According to an embodiment of the present disclosure, a base station in a wireless communication system includes: a transceiver; and at least one processor connected to the transceiver. The at least one processor is configured to: receive a first message including at least one of the first information or the second information from a terminal, the first information indicating whether the terminal supports quality of experience (QoE) measurement in a radio resource control (RRC) idle state or an RRC inactive state, and the second information indicating a memory size for performing QoE measurement in an RRC idle state or an RRC inactive state; and send a second message to the terminal, the second message including configuration information about application layer measurement. The terminal supports a memory size greater than the minimum memory size for performing QoE measurement in an RRC idle state or an RRC inactive state.
[0012] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used in this patent document: the terms "include" and "comprising" and their derivatives mean including but not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, included, interconnected with, containing, contained within, connected to or connected with, coupled to or connected with, communicable with, cooperating with, interleaved, juxtaposed, adjacent, bound to or bound with, having, having the property of, etc.; and the term "controller" refers to any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or at least some combination of the two. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether local or remote.
[0013] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data, or parts thereof suitable for implementation in appropriate computer-readable program codes. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other transmission temporary electrical or other signal communication links. A non-transitory computer-readable medium includes a medium that can permanently store data, and a medium that can store data and then rewrite data, such as a rewritable optical disk or an erasable storage device.
[0014] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:
[0016] Figure 1A The structure of a wireless communication system according to an embodiment of the present disclosure is shown.
[0017] Figure 1B The RRC state transition in a wireless communication system according to an embodiment of the present disclosure is shown.
[0018] Figure 1C A flowchart of a process for configuring and / or reporting signaling-based QoE measurements according to an embodiment of the present disclosure is shown.
[0019] Figure 1D A flow chart of a process for configuring and / or reporting management-based QoE measurements according to an embodiment of the present disclosure is shown.
[0020] Figure 1E A flowchart of a method for configuration and reporting procedures of RAN visible QoE measurements according to an embodiment of the present disclosure is shown.
[0021] Figure 1F A UE according to an embodiment of the present disclosure is shown.
[0022] Figure 1G A base station according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0023] The following discussion Figures 1A to 1G , and the various embodiments used to describe the principles of the present disclosure in this application document are only exemplary and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.
[0024] The terms used in the present disclosure are only used to describe specific embodiments and are not intended to limit the scope of other embodiments. Unless the context clearly stipulates otherwise, a singular expression may include a plural expression. The terms used herein, including technical or scientific terms, may have the same meanings as those generally understood by those of ordinary skill in the art described in the present disclosure. Among the terms used in the present disclosure, the terms defined in a general dictionary may be interpreted with the same or similar meanings as those in the context of the relevant technology, and unless clearly defined in the present disclosure, they should not be interpreted as ideal or overly formal meanings. In some cases, even the terms defined in the present disclosure cannot be interpreted as excluding embodiments of the present disclosure.
[0025] In each embodiment of the present disclosure described below, a hardware method will be described as an example. However, since each embodiment of the present disclosure includes a technique using both hardware and software, each embodiment of the present disclosure does not exclude a software-based method.
[0026] The terms used in the following description involving device components (control unit, processor, artificial intelligence (AI) model, encoder, decoder, autoencoder (AE), neural network (NN) model, etc.) and terms involving data (signal, feedback, report, report, information, parameter, value, bit, codeword, etc.) are examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms with equivalent technical meanings may be used.
[0027] In addition, the present disclosure describes various embodiments using terms used in some communication standards (eg, the 3rd Generation Partnership Project (3GPP)), but this is only an example for explanation. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.
[0028] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that in the accompanying drawings, identical elements are indicated by identical reference numerals as much as possible. In addition, detailed descriptions of well-known functions and elements that may obscure the subject matter of the present disclosure will be omitted. When describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure will be omitted. This is to convey the subject matter of the present disclosure more clearly, rather than obscuring it by omitting unnecessary descriptions.
[0029] For the same reason, some elements are enlarged, omitted or schematically shown in the accompanying drawings. In addition, the size of each element described does not fully reflect the actual size. In the drawings, the same or corresponding elements are given the same reference numerals.
[0030] The advantages and features of the present disclosure and the ways to achieve them will become apparent through the embodiments described below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as being limited to the embodiments described herein. On the contrary, these embodiments are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. The present disclosure is limited only by the scope of the appended claims. Throughout the specification, the same reference numerals represent the same elements.
[0031] It should be understood that each block of the flowchart diagram and the combination of blocks in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate a method for implementing the functions specified in the flowchart block.
[0032] These computer program instructions may also be stored in a computer-usable or computer-readable memory, which may direct a computer or other programmable data processing device to operate in a specific manner so that the instructions stored in the computer-usable or computer-readable memory produce a product including an instruction method for implementing the functions specified in the flowchart block.
[0033] The computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operating steps are performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the flowchart block.
[0034] In addition, each box of the flow chart may represent a module, segment or part of a code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some optional embodiments, the functions recorded in the box may not occur in order. For example, two boxes shown in succession may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions involved.
[0035] As used herein, the term "unit" refers to a software element or a hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, the term "unit" does not always have a meaning limited to software or hardware. A "unit" can be configured to be stored in an addressable storage medium or to execute one or more processors.
[0036] Thus, a “unit” includes, for example, a software element, an object-oriented software element, a class element or task element, a process, a function, a property, a procedure, a subroutine, a segment of program code, a driver, firmware, microcode, a circuit, data, a database, a data structure, a table, an array, and a variable.
[0037] The functions provided by the elements and "units" may be combined into the functions of a smaller number of elements and "units", or separated into the functions of a larger number of elements and "units". In addition, the elements and "units" may be implemented as one or more central processing units (CPUs) operating within a device or secure multimedia card.
[0038] In the following description, for the convenience of description, terms used to identify access nodes, terms related to network entities, terms related to messages, terms related to interfaces between network entities, terms related to various identification information, etc. are exemplified. Therefore, the present disclosure is not limited to the terms described below, and other terms with equivalent technical meanings may be used.
[0039] In the following, for ease of description, the present disclosure will use terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard or the New Radio (NR) standard. However, the present disclosure is not limited to such terms and names and can be equally applied to systems conforming to other standards.
[0040] In the following, a base station (BS) is a subject that performs resource allocation of a terminal and may be at least one of a radio access network (RAN) node, a next generation node B (gNode B or gNB), an evolved node B (eNode B or eNB), a node B, a radio access unit, a base station controller, or a node on a network. In the present disclosure, for ease of description, eNB may be used interchangeably with gNB. That is, a base station described as an eNB may indicate a gNB.
[0041] Hereinafter, the terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. Of course, the terminal is not limited to this example.
[0042] Specifically, the present disclosure may be applied to 3GPP NR (fifth generation mobile communication standard). In addition, based on 5G communication technology and IoT (Internet of Things) related technology, the present disclosure may be applied to smart services (e.g., smart homes, smart buildings, smart cities, smart or connected cars, health care, digital education, retail, security and safety related services, etc.). In addition, the term terminal may refer to other wireless communication devices as well as mobile phones, NB-IoT devices and sensors.
[0043] Wireless communication systems are evolving from providing traditional voice-oriented services to broadband wireless communication systems that provide high-speed and high-quality packet data services as in communication standards (e.g., High Speed Packet Access (HSPA), Long Term Evolution (LTE) (or Evolved Universal Terrestrial Radio Access (E-UTRA)), or 3GPP's LTE-A (Advanced), High Rate Packet Data (HRPD), or 3GPP2's Ultra Mobile Broadband (UMB), and IEEE 802.16e).
[0044] As a typical example of a broadband wireless communication system, the LTE system adopts an orthogonal frequency division multiplexing (OFDM) scheme in the downlink (DL) and a single carrier frequency division multiple access (SC-FDMA) scheme in the uplink (UL). The uplink indicates a wireless link through which a user equipment (UE) sends data or a control signal to a base station (BS) (or eNB, gNB), and the downlink indicates a wireless link through which a base station sends data or a control signal to a UE. The above-mentioned multiple access scheme can separate the data or control information of each user by allocating and operating time-frequency resources for sending data or control information to each user to avoid overlapping with each other, that is, in order to establish orthogonality.
[0045] Since the 5G communication system, which is a communication system after LTE, can freely reflect various needs of users, service providers, etc., it can support services that meet various needs. Services considered in the 5G communication system include enhanced mobile broadband (eMBB) communication, massive machine type communication (mMTC), ultra-reliable low latency communication (URLLC), etc.
[0046] eMBB aims to provide higher data rates than those supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must provide a peak data rate of 20Gbps in the downlink and a peak data rate of 10Gbps in the uplink for a single base station. In addition, the 5G communication system must provide an increased user-perceived data rate as well as a maximum data rate to the UE. In order to meet this requirement, it is necessary to improve the transmission / reception technology including further enhanced multiple-input multiple-output (MIMO) transmission technology. In addition, the data rate required by the 5G communication system can be obtained using a frequency bandwidth greater than 20MHz in a frequency band of 3 to 6GHz or 6GHz or higher, instead of using a transmission bandwidth of up to 20MHz in a frequency band of 2GHz used in LTE to send signals.
[0047] In addition, mMTC is considered to support application services such as the Internet of Things (IoT) in a 5G communication system. mMTC has requirements such as supporting the connection of a large number of UEs in a cell, enhanced coverage of UEs, improved battery time, and reduced cost of UEs in order to effectively provide IoT. Since IoT provides communication functions while providing to various sensors and various devices, it can support a large number of UEs in a cell (e.g., 1,000,000 UEs / km). 2). In addition, because the UE may be located in a blind spot such as a basement of a building, which is not covered by a cell due to the characteristics of the service, the UE supporting mMTC may require a wider coverage than the coverage of other services provided by the 5G communication system. The UE supporting mMTC may be configured to be inexpensive, and because it is difficult to frequently replace the battery of the UE, a very long battery life, such as 10 to 15 years, may be required.
[0048] Finally, URLLC is a cellular-based mission-critical wireless communication service that can be used for remote control of robots or machines, industrial automation, drones, remote health care, emergency alerts, etc. Therefore, URLLC can provide communications with ultra-low latency and ultra-high reliability. For example, a URLLC-enabled service can meet an air interface latency of less than 0.5ms and also require 10 -5 Or lower packet error rate. Therefore, for services supporting URLLC, the 5G system can provide a transmission time interval (TTI) shorter than that of other services, and may also require a design for allocating a large amount of resources in the frequency band to ensure the reliability of the communication link.
[0049] The three services in 5G, namely eMBB, URLLC and mMTC, can be multiplexed and transmitted in a single system. In this case, different transmission / reception technologies and transmission / reception parameters can be used between services in order to meet the different requirements of each service. Of course, 5G is not limited to the above three services.
[0050] In the specification, LTE, LTE-A, LTE Pro, 5G (or NR) or 6G systems will be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. In addition, based on the determination of those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.
[0051] Figure 1A The structure of a wireless communication system according to an embodiment of the present disclosure is shown.
[0052] refer to Figure 1A As shown in the figure, the radio access network of the wireless communication system (new radio, NR) can be composed of a next-generation base station (next-generation node B, hereinafter referred to as gNB) 1a-10 and an access and mobility management function (AMF) 1a-05. The user terminal (new radio user equipment, hereinafter referred to as NR UE or terminal) 1a-15 can access the external network through the gNB 1a-10 and the AMF 1a-05.
[0053] exist Figure 1AIn the present invention, the gNB may correspond to the evolved Node B (eNB) of the existing LTE system. The gNB is capable of connecting to the NR UE through a wireless channel and is capable of providing services superior to those of the existing Node B (e.g., eNB) (1a-20). In a wireless communication system, all user services may be served through a shared channel, so a device may be required to collect status information such as the buffer status of the UE, the available transmission power status, and the channel status, and perform scheduling. This may be performed by the gNB 1a-10. Typically, one gNB is capable of controlling multiple cells. Compared to the existing LTE, in order to achieve ultra-high data transmission, the gNB may have a bandwidth larger than the existing maximum bandwidth, and further, orthogonal frequency division multiplexing (OFDM) may be used as a wireless access technology to perform beamforming technology. In addition, an adaptive modulation and coding (AMC) scheme that determines the modulation scheme and channel coding rate according to the channel status of the UE may be applied. The AMF 1a-05 is capable of performing functions such as mobility support, bearer configuration, and quality of service (QoS) configuration.
[0054] AMF is a device that processes various control functions of UE and mobility management functions, and can be connected to multiple base stations. In addition, the wireless communication system can be linked to the existing LTE system, and AMF can be connected to MME 1a-25 through a network interface. MME can be connected to the existing base station eNB 1a-30. UE supporting LTE-NR dual connectivity can send and / or receive data while maintaining not only a connection to the gNB but also a connection to the eNB (1a-35).
[0055] Figure 1B The RRC state transition in a wireless communication system according to an embodiment of the present disclosure is shown.
[0056] refer to Figure 1B , a wireless communication system may have three radio resource control (RRC) states or RRC modes. Connected mode (RRC_CONNECTED) 1b-05 may be an RRC state in which the UE is able to send and / or receive data. Idle mode (RRC_IDLE) 1b-30 may be an RRC state in which the UE monitors whether paging is sent to the UE. Both modes are RRC states that are also applied to existing LTE systems, and the detailed techniques may be the same as those of existing LTE systems. In a wireless communication system, an inactive mode (RRC_INACTIVE) 1b-15 may be newly defined. In inactive mode, the UE context may be maintained in the base station and the UE, and paging based on the radio access network (RAN) may be supported. The features of the new inactive mode may be as follows.
[0057] -Cell reselection mobility;
[0058] - A CN-NR RAN connection (both control plane and user plane) has been established for the UE;
[0059] - The UE AS context is stored in at least one gNB and the UE;
[0060] -Paging initiated by NR RAN;
[0061] - the RAN based notification area is managed by the NR RAN; and / or
[0062] - The NR RAN is aware of the RAN based notification area to which the UE belongs.
[0063] The new inactive mode can be switched to connected mode or idle mode using a specific process. The inactive mode can be switched to connected mode through a recovery process, and the connected mode can be switched to inactive mode through a release process including suspension configuration information (1b-10). In these processes, one or more RRC messages can be sent and / or received between the UE and the base station, which can consist of one or more steps. In addition, the inactive mode can be switched to idle mode through a release process after recovery (1b-20). The switching between connected mode and idle mode can follow the existing LTE technology. That is, the switching between modes can be achieved through an establishment or release process (1b-25).
[0064] Figure 1C A flowchart of a process for configuring and / or reporting signaling-based QoE measurements according to an embodiment of the present disclosure is shown.
[0065] refer to Figure 1CIn step 1c-10, the UE or the access stratum (AS) 1c-05 of the UE may send information (e.g., at least one of qoe-Streaming-MeasReport, qoe-MTSI-MeasReport, or qoe-VR-MeasReport) indicating whether the measurement of quality of experience (QoE) is supported by the service type (e.g., at least one of streaming, MTSI, or VR) to the base station (or NG-RAN) 1c-15 through a UE capability message (e.g., UECapabilityInformation). Before the UE 1c-05 sends the UE capability message, the base station 1c-15 may send a message requesting the UE capability message (e.g., UECapabilityEnquiry) to the UE 1c-05. In addition, through the UE capability message, UE 1c-05 can report to the base station 1c-15 by service type (e.g., streaming, VR) whether UE 1c-05 supports QoE measurements (RAN visible QoE measurements) that the base station (or RAN) can read and use (e.g., at least one of ran-VisibleQoE-Streaming-MeasReport or ran-VisibleQoE-VR-MeasReport). In addition, through the UE capability message, UE 1c-05 can report whether UE 1c-05 supports the uplink RRC message segmentation function (UL RRC segmentation) for QoE report messages (e.g., ul-MeasurementReportAppLayer-Seg). The UE capability message may include the ASN.1 information in Table 1 below and the related parameter descriptions in Table 2.
[0066] [Table 1]
[0067]
[0068] [Table 2]
[0069]
[0070]
[0071] The service types that can be supported in LTE may include streaming and MTSI (Multimedia Telephony Service for IMS (IP Multimedia Subsystem)). The NR system additionally defines support for Virtual Reality (VR), and may also support Multimedia Broadcast Multicast Service (MBMS), Extended Reality (XR), etc. Of course, the present disclosure is not limited to the above examples.
[0072] According to an embodiment of the present disclosure, in step 1c-30, the operation administration and maintenance (OAM) 1c-20 may provide QoE measurement configuration information to the core network (CN) 1c-25. In step 1c-35, the CN1c-25 that has received the QoE measurement configuration information may activate QoE measurement by sending the QoE measurement configuration information to the base station. In step 1c-40, the base station 1c-15 that has received the QoE measurement configuration information passes the QoE measurement configuration information to the UE AS1c-05 via an RRC message (e.g., an RRC reconfiguration or an RRC recovery message). The RRC message may include an information element (IE) (e.g., APPLayerMeasConfig) as shown in Table 3 below, and the related parameter descriptions may be as shown in Tables 4 and 5.
[0073] [Table 3]
[0074]
[0075]
[0076]
[0077] [Table 4]
[0078]
[0079]
[0080] [Table 5]
[0081]
[0082] The operation of UE AS1c-05 which has received the QoE measurement configuration information can be represented as in the following Table 6.
[0083] [Table 6]
[0084]
[0085]
[0086]
[0087] As described above, in the case where the QoE measurement configuration is included in measConfigAppLayerToAddModList, in step 1c-50, the UE AS layer 1c-05 may pass the QoE measurement configuration information to the upper layer or application layer of the UE (UE APP) 1c-45 via an AT command. In one example, for the QoE measurement configuration included in measConfigAppLayerToAddReleaseList, the UE AS layer 1c-05 may send an AT command to the UE APP 1c-45 to delete the stored QoE measurement configuration information.
[0088] UE APP 1c-45 may perform QoE measurement according to the received configuration information. In addition, in step 1c-55, UE APP 1c-45 may report the measurement result to UE AS through an AT command according to the configuration information. In step 1c-60, UE AS1c-05 having received the AT command may report the measurement result to base station 1c-15 through an RRC message (e.g., a MeasurementReportAppLayer message). UE AS1c-05 may use SRB4 (Signaling Radio Bearer 4) to report the QoE measurement result. The MeasurementReportAppLayer message may include ASN.1 information according to the following Table 7. In addition, the parameters included in the MeasurementReportAppLayer message may refer to the description according to Table 8.
[0089] [Table 7]
[0090]
[0091]
[0092] [Table 8]
[0093]
[0094] The QoE measurement result reporting process of UE AS1c-05 can be expressed as shown in the following Table 9.
[0095] [Table 9]
[0096]
[0097]
[0098]
[0099] In step 1c-70, the base station 1c-15 may send the QoE measurement result report to the final server (TCE or MCE) 1c-65 that collects the measurement reports.
[0100] Figure 1D A flow chart of a process for configuring and / or reporting management-based QoE measurements according to an embodiment of the present disclosure is shown.
[0101] refer to Figure 1D , the management-based QoE configuration and / or reporting process can be similar to Figure 1C The signaling-based QoE configuration and / or reporting process described in . Therefore, in this figure, only the differences in the management-based solution are described, and other processes and descriptions can refer to Figure 1C process and description.
[0102] In the management-based solution, in step 1d-15, QoE measurement can be activated by OAM 1d-05, and the QoE measurement configuration can be sent directly to the base station 1d-10 without passing through the CN. The base station that has received the QoE measurement configuration can find a single or multiple UEs that meet a single or multiple conditions (e.g., at least one of the area range, application layer capability, or service type). In step 1d-20, the base station can send the QoE measurement configuration to each UE via an RRC message (e.g., an RRC reconfiguration message or an RRC recovery). For other procedures and message types, refer to Figure 1C Description of (signaling-based scheme).
[0103] Figure 1E A flowchart of a method for configuration and reporting procedures of RAN visible QoE measurements according to an embodiment of the present disclosure is shown.
[0104] refer to Figure 1E ,like Figure 1C and Figure 1D As shown, the QoE measurement configuration may be provided by OAM, the QoE measurement report generated according to the OAM configuration may be collected by TCE / MCE, and the operator may use the QoE measurement report to perform network optimization.
[0105] In this case, the UE may send a report about OAM-based QoE measurement to the base station, and when the base station receives the report about OAM-based QoE measurement, the base station may have difficulty reading or understanding the measurement report. For example, in the MeasurementReportAppLayer message, the measurement report generated by the application layer of the UE may be included in the measurementReportAppLayerContainer, but since the measurement report is stored in the form of OCTEC STRING, the base station or the RRC layer of the base station may have difficulty reading or understanding the measurement report. To solve this problem, RAN visible QoE (RVQoE) measurement may be defined so that the base station can read the QoE measurement report and use the QoE measurement report for network optimization, such as radio resource management.
[0106] RVQoE measurement may be defined as limited to a specific service type (e.g., at least one of streaming or VR). In step 1e-05, the UE may first report to the base station whether RVQoE measurement is supported by the service type (e.g., at least one of streaming or VR). At this time, a UE capability message (e.g., UECapabilityInformation message) may be used. For example, for streaming services, the UE may include or configure a ran-VisibleQoE-Streaming-MeasReport parameter in the UECapabilityInformation message, and for VR services, the UE may include or configure a ran-VisibleQoE-VR-MeasReport parameter.
[0107] In step 1e-10, by including or configuring the UE with the above parameters, the base station is able to understand whether the UE supports RVQoE measurement for each service type, and therefore, the base station can generate an RVQoE measurement configuration and send the RVQoE measurement to the UE. At this time, the RVQoE measurement configuration can be delivered together with the OAM-based QoE measurement configuration. The RVQoE measurement configuration can be included in an RRC message (e.g., an RRCReconfiguration or RRCResume message). The base station can instruct the UE to set or release the RVQoE measurement by establishing or releasing the RAN-VisibleParameters parameter in the AppLayerMeasConfig IE included in the RRC message. These parameters may include the RAN-VisibleParameters IE, and the base station may provide some or all of the following parameters to the UE through the RAN-VisibleParameters IE.
[0108] -RVQoE measurement report periodicity (e.g., ran-VisiblePeriodicity): UE AS or UE APP may send RVQoE measurement reports at each configured period;
[0109] - Maximum number of reportable buffer levels (e.g., numberOfBufferLevelEntries): When reporting RVQoE measurements, the UE AS or UE APP may include multiple buffer levels, the number of which may be less than or equal to the configured value; and
[0110] -Whether to report playout delay at media start (e.g., reportPlayoutDelayForMediaStartup): If the value of whether to report playout delay at media start is indicated as "true", the UE AS or UE APP may include the playout delay at media start in the RVQoE report and send it. If the value of whether to report playout delay at media start is indicated as "false", the UE may not include the playout delay at media start in the RVQoE report.
[0111] In step 1e-15, the AS layer of the UE may send the above configuration information to the APP layer of the UE. At this time, the RVQoE measurement configuration may be delivered together with the OAM-based QoE measurement configuration.
[0112] In step 1e-20, the APP of the UE may generate an RVQoE measurement report by performing QoE measurement based on the RVQoE measurement configuration information, and send the generated RVQoE measurement report to the AS layer of the UE. At this time, the RVQoE measurement report may be delivered together with the OAM-based QoE measurement report.
[0113] In step 1e-25, the AS layer of the UE that has received the RVQoE measurement report may deliver the RVQoE measurement report to the base station. At this time, the RVQoE measurement report may be delivered together with the OAM-based QoE measurement report. At this time, the RVQoE measurement report may be sent via the RAN-VisibleMeasurements IE in the MeasurementReportAppLayer message, and the RAN-VisibleMeasurements IE may include some or all of the following parameters;
[0114] - APP layer buffer level list (e.g., appLayerBufferLevelList): The APP layer buffer level list may include multiple buffer levels measured by the UE APP. The number of numberOfBufferLevelEntries included in the RVQoE configuration may be limited;
[0115] - Playout Delay (e.g., Playout DelayForMediaStartup): The playout delay may indicate the playout delay in ms when the media starts. In case reportPlayoutDelayForMediaStartup is set to "true" in the RVQoE configuration, the UE may include the playout delay parameter; and / or
[0116] -PDU session ID list (e.g., pdu-SessionIdList): The PDU session ID list may indicate a PDU session used in an application data flow that is a target of RVQoE measurement. Through the PDU session ID list, the base station can know for which PDU session the RVQoE value (e.g., buffer level and playout delay) is measured, and can optimize resource allocation and scheduling for the corresponding PDU session according to which RVQoE value (e.g., buffer level and playout delay) is measured for the PDU session.
[0117] The base station can read the RVQoE report and use the RVQoE report to perform network optimization. For example, the base station can improve the QoE of the UE by allocating relatively more radio resources to the UE experiencing low QoE for a specific service identified based on the PDU session ID.
[0118] In one embodiment of the present disclosure, in order to suspend (or pause) the QoE measurement report configured for the UE in a specific situation (for example, in the case of RAN overload), the base station may instruct the UE to do so. For example, the base station may instruct the UE to suspend (or pause) the QoE measurement report configured for the UE through the pauseReporting indicator in AppLayerMeasConfig. The indicator (for example, pauseReporting) may be indicated for each QoE configuration ID (for example, measConfigAppLayerId) to suspend each QoE measurement report according to each QoE configuration.
[0119] In the case where the UE AS layer receives a pauseReporting indicator set to "true" from the base station, the UE AS layer may suspend the QoE measurement report for the QoE configuration ID (e.g., measConfigAppLayerId) associated with the pauseReporting indicator. On the other hand, since the UE APP layer may not be aware of the suspension of the QoE measurement report, the UE AS layer may continue to perform QoE measurements for the corresponding QoE configuration ID (e.g., measConfigAppLayerId) and pass the measurement results or reports to the UE AS layer. However, the UE AS layer may suspend sending the measurement results or reports to the base station and store the measurement results or reports received from the APP layer in the memory of the UE AS layer.
[0120] In order to support the suspension function of the QoE measurement report indicated by the base station, the minimum memory size (e.g., 64KB) required by the UE supporting QoE (e.g., a UE sending a QoE-Streaming-MeasReport-r17 and / or a qoe-MTSI-MeasReport-r17 and / or a qoe-VR-MeasReport-r17) (mandatory or optional) may be defined. If the minimum memory size (e.g., 64KB) required by the UE supporting QoE is defined, the UE capability report for the memory size may not be necessary. For example, the minimum memory size required by the UE supporting QoE (mandatory or optional) may be defined by a statement such as the following Table 10.
[0121] [Table 10]
[0122]
[0123] The UE (or UE AS) may receive an indicator from the base station to resume the QoE measurement report. For example, the base station may set the pauseReporting indicator in the AppLayerMeasConfig to "false" and send the indicator to the UE. The UE may perform a process of reporting the QoE measurement report stored in the memory to the base station.
[0124] refer to Figure 1C and Figure 1DAccording to the description, in the LTE system, QoE measurement can be supported only in the connected mode (RRC_CONNECTED). On the other hand, the NR system can support QoE measurement in the inactive mode (RRC_INACTIVE) or idle mode (RRC_IDLE) for the Multimedia Broadcast Multicast Service (MBMS) or the Multicast / Broadcast Service (MBS). In the future, the NR system may support QoE measurement in the inactive mode and idle mode for various service types as well as the MBS. In the present disclosure, QoE measurement is described only for the MBS service, but it is not limited thereto and may be applied to various service types that may be supported in the connected mode and / or the inactive mode and / or the idle mode.
[0125] In one embodiment of the present disclosure, in order to store the QoE measurement results in the connected mode and / or the inactive mode and / or the idle mode, the UE may use the memory of the AS layer to store the paused QoE measurement report (by the pauseReporting indicator). For example, the memory may be used to store the QoE results measured in the connected mode and / or the inactive mode and / or the idle mode and the paused QoE measurement report, and the two types of QoE measurement results and reports (1. the suspended QoE measurement report, and 2. the QoE results measured in the connected mode and / or the inactive mode and / or the idle mode) may coexist in the memory.
[0126] In order to support the suspension function of the QoE measurement report indicated by the base station and the QoE measurement (or QoE measurement for MBS service) function in the inactive mode and / or idle mode, the minimum memory size (e.g., 64KB) required by the UE supporting QoE (e.g., a UE sending UE capabilities, the UE capabilities include qoe-Streaming-MeasReport-r17 and / or qoe-MTSI-MeasReport-r17 and / or qoe-VR-MeasReport-r17 and / or an inactive / idle QoE measurement capability indicator (e.g., qoe-IdleInactive-r18) and / or a QoE measurement capability indicator for MBS services (e.g., qoe-MBS-MeasReport-r18)) (mandatory or optional) may be defined. If the minimum memory size (e.g., 64KB) required by the UE supporting QoE is defined, the UE capability report of the UE for the memory size may not be necessary. For example, the minimum memory size required by a UE (mandatory or optional) to support QoE may be defined by a statement such as Table 11 below.
[0127] [Table 11]
[0128]
[0129] In an optional example, the minimum memory size required by a UE (mandatory or optional) to support QoE may be defined by a statement such as Table 12 below.
[0130] [Table 12]
[0131]
[0132] In one embodiment of the present disclosure, the UE supporting QoE in the above embodiment may be defined as supporting a minimum memory size of a specific capacity (e.g., 64KB) or more. Alternatively, it may be a fixed value such as 128KB, 256KB, 512KB, 1MB, 2MB, etc. This may be a capability required by the UE (mandatory or optional). If it is a mandatory capability for the UE supporting QoE to support a minimum memory size of a specific capacity (e.g., 64KB) or more, the UE capability report may not be required. For example, the minimum memory size required by the UE supporting QoE (mandatory or optional) may be defined by a statement such as the following Table 13.
[0133] [Table 13]
[0134]
[0135] In an optional example, the minimum memory size required by a UE (mandatory or optional) to support QoE may be defined by a statement such as Table 14 below.
[0136] [Table 14]
[0137]
[0138] In one embodiment of the present disclosure, the UE may report to the base station whether the UE supports a supportable (minimum or maximum) memory size (for example, to store QoE measurement results in an inactive mode and / or an idle mode or QoE measurement results for MBS services). In order to store suspended QoE measurement results, the memory may also be used / shared. For example, through indicator A in a UE capability message (e.g., UECapabilityinformation), the UE may report whether the UE supports a memory size of a predetermined value (minimum or maximum value) (e.g., 128KB). If the UE sends a UE capability message including indicator A to the base station, this may mean that the UE supports a memory size of a predetermined value (minimum or maximum value) (e.g., 128KB). If the UE sends a UE capability message to the base station without including indicator A, this may mean that the UE does not support a memory size of a predetermined value (minimum or maximum value) (e.g., 128KB). If the UE sends a UE capability message to the base station without including indicator A, this may mean that the UE only supports the minimum memory size required by the UE (e.g., 64KB).
[0139] In one embodiment of the present disclosure, the UE may report a supportable (minimum or maximum) memory size (e.g., to store QoE measurement results in inactive mode and / or idle mode or QoE measurement results for MBS services). In order to store suspended QoE measurement results, the memory may also be used / shared. For example, the UE may select its supportable (minimum or maximum) memory size value from the memory size values (e.g., 128KB, 256KB, 512KB, etc.), indicate the selected value through an indicator B in a UE capability message (e.g., UECapabilityinformation), and report the value to the base station. If the UE sends a UE capability message to the base station in a manner indicating a value through indicator B, this may mean that the UE supports the memory size of the corresponding (minimum or maximum) value (e.g., 128KB). If the UE sends a UE capability message to the base station without including indicator B, this may mean that the UE only supports the minimum memory size required by the UE (e.g., 64KB).
[0140] In one embodiment of the present disclosure, the UE may separate and use differently a memory (e.g., memory 2) for storing QoE measurement results in an inactive mode and / or an idle mode and QoE measurement results for MBS services from a memory (e.g., memory 1, minimum 64KB) for storing suspended QoE measurement results.
[0141] In one embodiment of the present disclosure, the UE may define a minimum or maximum memory size for the memory 2 to be supported. For example, the memory size may be a predetermined value among 64KB, 128KB, 256KB, 512KB, 1MB, 2MB, etc. This may be a capability required by the UE (mandatory or optional). If it is a mandatory capability for the UE to support a minimum or maximum memory size with a predetermined value for the memory 2, a UE capability report by the UE on this point may not be necessary. For example, the minimum or maximum memory size of the memory 2 supported by the UE may be defined by a statement such as the following Table 15.
[0142] [Table 15]
[0143]
[0144] In an optional example, the minimum or maximum memory size of memory 2 supported by the UE may be defined by, for example, the expression in Table 16 below.
[0145] [Table 16]
[0146]
[0147] In one embodiment of the present disclosure, the UE may send a UE capability message including an indicator C to the base station, the indicator C indicating whether the UE supports a memory 2 having a size of a predetermined value (e.g., 25 GKB). For example, if the UE supports a memory 2 having a predetermined value size, the UE may report by including the indicator C in the UECapabilityInformation message or setting the indicator C to "true". If the UE does not support a memory 2 having a predetermined value size, the UE may report by omitting the indicator C in the UECapabilityInformation message or setting the indicator C to "false". In this way, in the case where the indicator C is omitted or the indicator C is set to "false" in the UECapabilityInformation message, this may mean that the UE (e.g., a UE supporting QoE measurement in an inactive mode and / or an idle mode or supporting QoE measurement for MBS services) may share / use the memory 1 to store the QoE measurement results in the inactive mode and / or the idle mode or the QoE measurement results for the MBS services. In another embodiment, when indicator C is omitted or set to "false" in the UECapabilityInformation message, this may mean that the UE (e.g., a UE supporting QoE measurement in inactive mode and / or idle mode or supporting QoE measurement for MBS services) only supports the mandatory minimum memory size for memory 2 (e.g., 64KB).
[0148] In one embodiment of the present disclosure, the UE may report the supportable (minimum or maximum) memory size for memory 2 to the base station. For example, the UE may select its supportable (minimum or maximum) memory size value for memory 2 from memory size values (e.g., 64KB, 128KB, 256KB, 512KB, etc.), indicate the selected value through an indicator D in a UE capability message (e.g., UECapabilityinformation), and report the value to the base station. If the UE sends a UE capability message to the base station in a manner of indicating a value through indicator D, this may mean that, for memory 2, the UE supports the memory size of the corresponding (minimum or maximum) value (e.g., 128KB). If the UE (e.g., a UE that supports QoE measurement in an inactive mode and / or an idle mode or supports QoE measurement for MBS services) sends the UE capability message to the base station without including indicator D, this may mean that, for memory 2, the UE only supports the minimum memory size (e.g., 64KB) that is mandatory for the UE. In another embodiment, if a UE (e.g., a UE supporting QoE measurement in inactive mode and / or idle mode or supporting QoE measurement for MBS services) sends a UE capability message to a base station without including indicator D, this may mean that the UE may share / use memory 1 to store QoE measurement results in inactive mode and / or idle mode or QoE measurement results for MBS services. In one embodiment of the present disclosure, if the UE supports QoE measurement in inactive mode and / or idle mode and / or QoE measurement for MBS (broadcast) services, the UE may send a UE capability message that (always) includes indicator D. In one embodiment of the present disclosure, if the UE does not support QoE measurement in inactive mode and / or idle mode and / or QoE measurement for MBS (broadcast) services, the UE may not (always) include indicator D in the UE capability message.
[0149] In one embodiment of the present disclosure, in the case where the UE supports QoE measurement in inactive mode and / or idle mode or QoE measurement for MBS (broadcast) service, the UE capability information of the UE discussed in the present disclosure may be defined or used. If the UE does not support QoE measurement in inactive mode and / or idle mode or QoE measurement for MBS (broadcast) service, the corresponding capability may not be defined / used.
[0150] In one embodiment of the present disclosure, the UE may use / share one memory to store two different types (eg, type 1 and type 2 below) of QoE measurement results.
[0151] - Type 1) suspended QoE measurements; and
[0152] - Type 2) QoE measurement results in inactive mode and / or idle mode or QoE measurement results for MBS services
[0153] For example, the UE may receive QoE configuration 1 (QoE measurement in connected mode) and QoE configuration 2 (QoE measurement in connected mode / inactive mode / idle mode) from the base station, and perform QoE measurement in connected mode. Thereafter, the base station may suspend the QoE measurement report for the UE of QoE configuration 1. When the QoE measurement report for QoE configuration 1 is suspended, the UE AS may store the QoE measurement results for QoE configuration 1 in a memory. Thereafter, the UE may switch to inactive mode. At this time, the UE may still store the measurement results of the suspended QoE configuration 1 in a memory. In addition, the UE may perform QoE measurement for QoE configuration 2 and store the measurement results in the same memory. That is, the QoE measurement results for type 1 and type 2 may be stored in the same memory at the same time.
[0154] In another example, the UE may receive QoE configuration 2 (QoE measurement in connected mode / inactive mode / idle mode) from the base station. Thereafter, the UE may transition to inactive mode or idle mode. In inactive mode or idle mode, the UE may perform QoE measurement and store the measurement result in a memory. Thereafter, the UE may transition to connected mode. However, the UE may not be able to perform a QoE measurement report to the connected base station in inactive or idle mode. For example, the UE may not be able to perform a QoE measurement report in inactive mode or idle mode for a base station that does not support QoE measurement reporting in inactive mode or idle mode. Therefore, the UE may continue to store the measurement results for QoE configuration 2 in the memory. Thereafter, the base station may configure QoE configuration 1 (QoE measurement in connected mode) to the UE, so that the UE can perform QoE measurement. In the case where the base station indicates to suspend the QoE measurement report for QoE configuration 1, the UE may store the QoE measurement report for QoE configuration 1 in the same memory mentioned above. That is, the QoE measurement results for type 1 and type 2 may be stored in the same memory at the same time.
[0155] In one embodiment of the present disclosure, when the UE uses / shares one memory to store two different types (e.g., type 1 and type 2) of QoE measurement results, and when the memory is full, the UE may operate based on at least one or a combination of the following options.
[0156] - Option 1: Regardless of the type, the UE may remove (or discard) the oldest QoE measurement result stored in the memory and store the new QoE measurement result. This option may also be used when the memory is only used / shared by QoE measurement results of a single type (e.g., Type 1 or Type 2).
[0157] -Option 2-1: Measurement results of type 1 may take precedence over measurement results of type 2. Measurement results of type 1 are measurement results in connected mode, so they may be relatively important data for communication operators. Therefore, the UE may remove (or discard) measurement results of type 2 from the memory and store new QoE measurement results. If the memory is full of measurement results of type 1 only, the newly measured measurement results of type 2 may not be stored and may be removed immediately. A specific priority example may be as follows, and data with a lower priority (higher priority number) may be removed first.
[0158] ■Priority 1: Relatively recently stored type 1 measurement results;
[0159] ■Priority 2: Type 1 measurements that were stored relatively long ago;
[0160] ■ Priority 3: Type 2 measurements that were stored relatively recently; and
[0161] ■Priority 4: Type 2 measurement results that were stored relatively long ago.
[0162] -Option 2-2: Measurement results of type 2 may take precedence over measurement results of type 1. Measurements of type 2 are performed over a relatively long period of time, so the operator may require uninterrupted measurement results. Therefore, the UE may remove (or discard) measurement results of type 1 from the memory and store new QoE measurement results. If the memory is full of measurement results of type 2 only, the newly measured measurement results of type 1 may not be stored and may be removed immediately. A specific priority example may be as follows, and data with a lower priority (higher priority number) may be removed first.
[0163] ■Priority 1: Relatively recently stored type 2 measurement results;
[0164] ■Priority 2: Type 2 measurements that were stored relatively long ago;
[0165] ■ Priority 3: Type 1 measurements that were stored relatively recently; and
[0166] ■Priority level 4. Relatively long-term storage of type 1 measurement results.
[0167] - Option 3: The base station may configure the priority of type 1 and type 2 for the UE. If the UE is configured with a high priority for type 1, the UE may perform the operation of option 2-1. If the UE is configured with a high priority for type 2, the UE may perform the operation of option 2-2.
[0168] - Option 4-1: The base station may configure the priority of each QoE ID (e.g., measConfigAppLayerId) for the UE. For example, if the UE is configured to prioritize QoE ID 1 over QoE ID 2, the UE may determine the priority as follows, regardless of whether the measurement results stored with QoE ID 1 or QoE ID 2 are of type 1 or type 2. In this case, the measurement results with lower priority (higher priority number) may be removed first. This option may also be used when the memory is only used / shared by QoE measurement results of a single type (e.g., type 1 or type 2).
[0169] Priority 1: Relatively recently stored measurement results of QoE ID 1;
[0170] ■Priority 2: Measurement results of QoE ID 1 that were stored relatively long ago;
[0171] ■ Priority 3: relatively recently stored measurements of QoE ID 2; and
[0172] ■ Priority 4: Measurement results of QoE ID 2 that were stored relatively long ago.
[0173] - Option 4-2: The base station may configure the priority of each QoE measurement service type (e.g., serviceType) for the UE. For example, if the UE is configured to have a higher priority of service type 1 than service type 2, the UE may determine the priority as follows, regardless of whether the measurement results stored using service type 1 or service type 2 are of type 1 or type 2. In this case, the measurement results with a lower priority (higher priority number) may be removed first. This option may also be used when the memory is used / shared by QoE measurement results of only a single type (e.g., type 1 or type 2) together.
[0174] ■Priority 1: relatively recently stored measurement results of service type 1;
[0175] ■Priority 2: Measurement results of service type 1 that were stored relatively long ago;
[0176] ■ Priority 3: relatively recently stored measurements of service type 2; and
[0177] ■ Priority 4: Measurement results of service type 2 that were stored relatively long ago.
[0178] - Option 5: The base station can configure the memory size (minimum or maximum value) that the UE can use individually in the shared memory by type, QoE ID (e.g., measConfigAppLayerId), or service type (e.g., serviceType). According to the configuration, the UE can divide / allocate the configured set size in the shared memory for each type, QoE ID, or service type, and store the measurement results separately. If the latest measurement result is generated in each separate memory but the memory is full, the UE can remove the oldest measurement result.
[0179] - Option 6: The UE may prioritize QoE measurement results for signaling-based QoE measurement configuration over QoE measurement results for management-based QoE measurement configuration. For example, the UE may define priorities as follows, and may remove data with lower priorities (higher priority numbers) first. This option may also be used when the memory is only used / shared by QoE measurement results of a single type (e.g., Type 1 or Type 2) together.
[0180] Priority 1: Relatively recently stored signaling-based QoE measurements;
[0181] ■Priority 2: Signaling-based QoE measurements stored relatively long ago;
[0182] ■ Priority 3: Relatively recently stored management-based QoE measurements; and
[0183] ■ Priority 4: Management-based QoE measurements stored relatively long ago.
[0184] In one embodiment of the present disclosure, the maximum memory size supported for the UE in the above embodiment may be defined instead of the minimum memory size.
[0185] In one embodiment of the present disclosure, the UE may report to the base station whether the result of the QoE measurement (e.g., for the MBS broadcast service) in the inactive mode and / or idle mode is stored. For example, if the UE stores the result of the QoE measurement (e.g., for the MBS broadcast service) in the inactive mode and / or idle mode, the UE may include an indicator (e.g., indicator E) in the RRC message (e.g., RRCSetupComplete, RRCResumeComplete, RRCResetumentComplete, RRCReconfigurationComplete message) or set the indicator E to "true". If the UE does not store the result of the QoE measurement (e.g., for the MBS broadcast service) in the inactive mode and / or idle mode, the UE may omit the indicator E in the RRC message (e.g., RRCSetupComplete or RRCResumeComplete or RRCResetumComplete or RRCReconfigurationComplete message) or set the indicator E to "false".
[0186] In one embodiment of the present disclosure, the UE may report to the base station whether a QoE measurement report that was not sent in the connected mode is stored (for example, due to a suspension indicated by the base station). If the UE stores the QoE measurement results that were not sent in the connected mode, the UE may include an indicator (for example, indicator F) in the RRC message (for example, RRCSetupComplete, RRCResumeComplete, RRCResetumComplete, RRCReconfigurationComplete message) or set indicator F to "true". If the UE does not store the QoE measurement results that were not sent in the connected mode, the UE may omit indicator F in the RRC message (for example, RRCSetupComplete or RRCResumeComplete or RRCResetumComplete or RRCReconfigurationComplete message) or set indicator F to "false".
[0187] In one embodiment of the present disclosure, in the case where 1) the UE stores the result of QoE measurement (e.g., QoE measurement for MBS broadcast service) in inactive mode and / or idle mode, or 2) the UE stores the QoE measurement result that is not sent in connected mode (e.g., due to suspension indicated by the base station), the UE may include an indicator (e.g., indicator G) in an RRC message (e.g., RRCSetupComplete, RRCResumeComplete, RRCResetumComplete, RRCReconfigurationComplete message) or set the indicator G to "true". In the case where 1) the UE does not store the result of QoE measurement (e.g., QoE measurement for MBS broadcast service) in inactive mode and / or idle mode, and 2) the UE does not store the QoE measurement result that is not sent in connected mode (e.g., due to suspension indicated by the base station), the UE may omit the indicator G in the RRC message (RRCSetupComplete or RRCResumeComplete or RRCReconfigurationComplete message) or set the indicator G to "false".
[0188] In one embodiment of the present disclosure, the UE may not report to the base station whether the QoE measurement report that is not sent in the connected mode (for example, due to a suspension indicated by the base station) is stored. However, the UE may report to the base station through an RRC message (for example, an RRCSetupComplete or RRCResumeComplete or RRCResetumComplete or RRCResetumComplete or RRCReconfigurationComplete message) whether the result of the QoE measurement in the inactive mode and / or idle mode (for example, the QoE measurement for the MBS broadcast service) is stored. If the UE stores 1) (for example, due to a suspension indicated by the base station) not sent in the connected mode (the first QoE measurement result), and 2) the QoE measurement result in the inactive mode and / or idle mode (for example, the QoE measurement result for the MBS broadcast service) (the second QoE measurement result) in the same memory, the UE can distinguish the first QoE measurement result and the second QoE measurement result in the same memory. In this way, if the UE recognizes that only the first QoE measurement result is stored in the memory but not the second QoE measurement result, the UE may not report to the base station whether the first QoE measurement result is stored in the memory. If the UE recognizes that the second QoE measurement result is stored in the memory, the UE may report to the base station whether the second QoE measurement result is stored in the memory.
[0189] In one embodiment of the present disclosure, if the UE stores the QoE measurement result in a memory and reports it to the base station via an RRC message (e.g., RRCSetupComplete or RRCResumeComplete or RRCRepresentation Complete or RRCReconfigurationComplete message), the base station may trigger the transmission of the corresponding QoE result report to the UE in order to receive the stored QoE measurement result. For example, the base station may configure the SRB resources for the QoE measurement result report to the UE, and the UE having received the SRB resources may send the stored QoE measurement report. For example, the UE may send a MeasurementReportAppLayer or a UEInformationResponse message containing a QoE measurement report to the base station via the configured SRB resources. In another example, the base station may (explicitly) configure an indicator for requesting a QoE measurement result report to the UE. For example, the base station may send an RRCReconfiguration or a UEInformationRequest message containing an indicator for requesting a QoE measurement result report to the UE. The UE having received the indicator may send the stored QoE measurement report. For example, the UE may send a MeasurementReportAppLayer or a UEInformationResponse message including a QoE measurement report to the base station.
[0190] Figure 1F A UE according to an embodiment of the present disclosure is shown.
[0191] refer to Figure 1F , the UE may include a radio frequency (RF) processor 1f-10, a baseband processor 1f-20, a memory 1f-30 and a controller 1f-40.
[0192] The RF processor 1f-10 can perform functions for sending and / or receiving signals through a wireless channel (e.g., frequency band conversion and amplification of signals). That is, the RF processor 1f-10 can up-convert the baseband signal provided by the baseband processor 1f-20 into an RF band signal, send the RF band signal through an antenna, and down-convert the RF band signal received by the antenna into a baseband signal. For example, the RF processor 1f-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Although only one antenna is shown in the figure, the UE may include multiple antennas. Moreover, the RF processor 1f-10 may include multiple RF chains. In addition, the RF processor 1f-10 can perform beamforming. For beamforming, the RF processor 1f-10 can adjust the phase and amplitude of the signal sent and / or received by multiple antennas or antenna elements. In addition, the RF processor can perform multiple-input multiple-output (MIMO), and multiple layers can be received when performing MIMO operations.
[0193] The baseband processor 1f-20 can perform the conversion function between the baseband signal and the bit stream according to the physical layer standard of the system. For example, when data is transmitted, the baseband processor 1f-20 can generate complex symbols by encoding and modulating the transmission bit stream. In addition, when data is received, the baseband processor 1f-20 can recover the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1f-10. For example, in the case of an orthogonal frequency division multiplexing (OFDM) scheme, when data is transmitted, the baseband processor 1f-20 can generate complex symbols by encoding and modulating the transmission bit stream, map the complex symbols to subcarriers, and configure OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when data is received, the baseband processor 1f-20 can divide the baseband signal provided from the RF processor 1f-10 into OFDM symbol units, recover the signal mapped to the subcarrier through a fast Fourier transform (FFT) operation, and recover the received bit stream through demodulation and decoding.
[0194] As described above, the baseband processor 1f-20 and the RF processor 1f-10 can send and receive signals. Therefore, the baseband processor 1f-20 and the RF processor 1f-10 can be referred to as a transmitter, a receiver, a transceiver or a communication unit. In addition, at least one of the baseband processor 1f-20 and the RF processor 1f-10 may include a plurality of communication modules to support a variety of different wireless access technologies. In addition, at least one of the baseband processor 1f-20 and the RF processor 1f-10 may include different communication modules to process signals of different frequency bands. For example, different radio access technologies may include wireless LAN (e.g., IEEE802.11), cellular networks (e.g., LTE), etc. In addition, different frequency bands may include ultra-high frequency (SHF) (e.g., 2.NRHz, NRHz) bands and millimeter wave (e.g., 60GHz) bands.
[0195] The memory 1f-30 may store default programs, applications, and data such as configuration information for the operation of the UE. In addition, the memory 1f-30 may provide the stored data in response to a request of the controller 1f-40.
[0196] The controller 1f-40 can control the overall operation of the UE. The controller 1f-40 can control the UE to perform at least one or a combination of the methods corresponding to the above-mentioned embodiments. For example, the controller 1f-40 can send and / or receive signals through the baseband processor 1f-20 and the RF processor 1f-10. In addition, the controller 1f-40 can write data in the memory 1f-30 and read data from the memory 1f-30. To this end, the controller 1f-40 may include at least one processor. For example, the controller 1f-40 may include a communication processor (CP) for controlling communications and an application processor (AP) for controlling higher layers such as applications. In addition, the controller 1f-40 may also include a multi-connection processor 1f-42 that supports multiple connections.
[0197] Figure 1G A base station according to an embodiment of the present disclosure is shown.
[0198] refer to Figure 1G , the base station can be configured to include an RF processor 1g-10, a baseband processor 1g-20, a backhaul communication unit 1g-30, a memory 1g-40 and a controller 1g-50.
[0199] The RF processor 1g-10 can perform functions for sending and / or receiving signals through a wireless channel (e.g., frequency band conversion and amplification of signals). That is, the RF processor 1g-10 can up-convert the baseband signal provided by the baseband processor 1g-20 into an RF band signal, send the RF band signal through an antenna, and down-convert the RF band signal received by the antenna into a baseband signal. For example, the RF processor 1g-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. Although only one antenna is shown in the figure, the first access node may include multiple antennas. Moreover, the RF processor 1g-10 may include multiple RF chains. In addition, the RF processor 1g-10 can perform beamforming. For beamforming, the RF processor 1g-10 can adjust the phase and amplitude of the signal sent and received through multiple antennas or antenna elements. The RF processor can perform downward MIMO operations by sending one or more layers.
[0200] The baseband processor 1g-20 can perform a conversion function between a baseband signal and a bit stream according to the physical layer standard of the first radio access technology. For example, when data is transmitted, the baseband processor 1g-20 can generate complex symbols by encoding and modulating the transmission bit stream. In addition, when data is received, the baseband processor 1g-20 can recover the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1g-10. For example, in compliance with the OFDM scheme, when data is transmitted, the baseband processor 1g-20 can generate complex symbols by encoding and modulating the transmission bit stream, map the complex symbols to subcarriers, and configure OFDM symbols through IFFT operations and CP insertion. In addition, when data is received, the baseband processor 1g-20 can divide the baseband signal provided from the RF processor 1g-10 into OFDM symbol units, recover the signal mapped to the subcarrier through FFT operations, and recover the received bit stream through demodulation and decoding. As described above, the baseband processor 1g-20 and the RF processor 1g-10 can send and receive signals. Therefore, the baseband processor 1g-20 and the RF processor 1g-10 can be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.
[0201] The backhaul communication unit 1g-30 may provide an interface for communicating with other nodes in the network. That is, the backhaul communication unit 1g-30 may convert a bit stream sent from the main base station to another node (e.g., an auxiliary base station, a core network, etc.) into a physical signal, and convert a physical signal received from another node into a bit stream.
[0202] The memory 1g-40 may store default programs, applications, and data such as configuration information for the operation of the main base station. In addition, the memory 1g-40 may provide the stored data in response to a request of the controller 1g-50.
[0203] The controller 1g-50 can control the overall operation of the main base station. The controller 1g-50 can control the base station to perform at least one or a combination of the methods corresponding to the above-mentioned embodiments. For example, the controller 1g-50 can send and / or receive signals through the baseband processor 1g-20 and the RF processor 1g-10 or through the backhaul communication unit 1g-30. In addition, the controller 1g-50 can write data in the memory 1f-40 and read data from the memory 1f-40. To this end, the controller 1g-50 may include at least one processor. In addition, the controller 1g-50 may also include a multi-connection processor 1g-52 to support multiple connections.
[0204] The methods according to the embodiments set forth in the claims or the specification of the present disclosure may be implemented in the form of hardware, software, or a combination thereof.
[0205] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. One or more programs include instructions for causing an electronic device to perform a method according to an embodiment described in the claims or specification of the present disclosure.
[0206] Such a program (software module, software) may be stored in a random access memory, a non-volatile memory (including flash memory, a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), a magnetic disk storage device, a compact disk ROM (CD-ROM), a digital versatile disk (DVD), other types of optical storage devices, or a magnetic tape cassette). Alternatively, such a program may be stored in a memory configured with a combination of some or all of them. Furthermore, each configured memory may be included in the plural.
[0207] In addition, the program can be stored in an attachable storage device that can be accessed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a communication network configured with a combination thereof. Such a storage device can access the device implementing the embodiments of the present disclosure through an external port. In addition, a separate storage device on a communication network can access the device implementing the embodiments of the present disclosure.
[0208] In the specific embodiments of the above disclosure, the components included in the disclosure are expressed as single or multiple, depending on the specific embodiments presented. However, for ease of description, the expression of single or multiple is appropriately selected for the presented situation, and the present disclosure is not limited to single or multiple components, and even if a component is expressed as multiple, the component can also be configured with a single, or even if a component is expressed as a single, the component can also be configured with a plurality.
[0209] Although specific embodiments have been described in the detailed description of the present disclosure, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth and the equivalent forms of the claims.
[0210] Although the present disclosure has been described by various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to include such changes and modifications as fall within the scope of the appended claims.
Claims
1. A method performed by a terminal in a wireless communication system, the method include: Sending a first message including at least one of first information or second information to a base station, wherein the first information indicates whether the terminal supports quality of experience (QoE) measurement in a radio resource control (RRC) idle state or an RRC inactive state, and the second information indicates a memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state; as well as receiving a second message from the base station, the second message including configuration information about application layer measurement; The terminal supports a memory size that is greater than or equal to a minimum memory size and is used to perform the QoE measurement in the RRC idle state or the RRC inactive state.
2. The method according to claim 1, in, In a case where the terminal supports the minimum memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state, the first message does not include the second information indicating the memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state, The minimum memory size is 64 kilobytes (KB).
3. The method according to claim 1, further comprising: include: In case a memory for storing application layer measurement reports becomes full, discarding the application layer measurement reports based on at least one of information related to a priority or a relative time associated with the application layer measurement, The configuration information about the application layer measurement includes information related to the priority associated with the application layer measurement.
4. The method according to claim 3, further comprising: include: In the case where at least one of the application layer measurement reports has the same priority or has no priority, an older application layer measurement report is discarded first.
5. A method performed by a base station in a wireless communication system, the method include: receiving, from a terminal, a first message including at least one of first information or second information, wherein the first information indicates whether the terminal supports quality of experience (QoE) measurement in a radio resource control (RRC) idle state or an RRC inactive state, and the second information indicates a memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state; as well as Sending a second message to the terminal, where the second message includes configuration information about application layer measurement; The terminal supports a memory size that is greater than or equal to a minimum memory size and is used to perform the QoE measurement in the RRC idle state or the RRC inactive state.
6. The method according to claim 5, in, In a case where the terminal supports the minimum memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state, the first message does not include the second information indicating the memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state, The minimum memory size is 64 kilobytes (KB).
7. The method according to claim 5, in, In case a memory for storing application layer measurement reports becomes full, discarding the application layer measurement reports based on at least one of information related to a priority or a relative time associated with the application layer measurement, Wherein, in the case where at least one of the application layer measurement reports has the same priority or has no priority, the older application layer measurement report is discarded first, The configuration information about the application layer measurement includes information related to the priority associated with the application layer measurement.
8. A terminal in a wireless communication system, the terminal include: Transceiver; as well as At least one processor coupled to the transceiver, the at least one processor being configured to: Sending a first message including at least one of first information or second information to a base station, wherein the first information indicates whether the terminal supports quality of experience (QoE) measurement in a radio resource control (RRC) idle state or an RRC inactive state, and the second information indicates a memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state; as well as receiving a second message from the base station, the second message including configuration information about application layer measurement, The terminal supports a memory size that is greater than or equal to a minimum memory size and is used to perform the QoE measurement in the RRC idle state or the RRC inactive state.
9. The terminal according to claim 8, in, In a case where the terminal supports the minimum memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state, the first message does not include the second information indicating the memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state, The minimum memory size is 64 kilobytes (KB).
10. The terminal according to claim 8, in, The at least one processor is configured to: In case a memory for storing application layer measurement reports becomes full, discarding the application layer measurement reports based on at least one of information related to a priority or a relative time associated with the application layer measurement, The configuration information about the application layer measurement includes information related to the priority associated with the application layer measurement.
11. The terminal according to claim 10, in, The at least one processor is configured to: In the case where at least one of the application layer measurement reports has the same priority or has no priority, an older application layer measurement report is discarded first.
12. A base station in a wireless communication system, the base station include: Transceiver; as well as At least one processor coupled to the transceiver, the at least one processor being configured to: receiving, from a terminal, a first message including at least one of first information or second information, wherein the first information indicates whether the terminal supports quality of experience (QoE) measurement in a radio resource control (RRC) idle state or an RRC inactive state, and the second information indicates a memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state; as well as Sending a second message to the terminal, where the second message includes configuration information about application layer measurement; The terminal supports a memory size that is greater than or equal to a minimum memory size and is used to perform the QoE measurement in the RRC idle state or the RRC inactive state.
13. The base station according to claim 12, in, In a case where the terminal supports the minimum memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state, the first message does not include the second information indicating the memory size for performing the QoE measurement in the RRC idle state or the RRC inactive state, The minimum memory size is 64 kilobytes (KB).
14. The base station according to claim 12, in, In case a memory for storing application layer measurement reports becomes full, discarding the application layer measurement reports based on at least one of information related to a priority or a relative time associated with the application layer measurement, The configuration information about the application layer measurement includes information related to the priority associated with the application layer measurement.
15. The base station according to claim 14, in, In the case where at least one of the application layer measurement reports has the same priority or has no priority, an older application layer measurement report is discarded first.
Citation Information
Cited By
QoE configuration method and apparatus during RRC resuming process
US12726858B2
