System and method for core network based idle quality of experience configuration retrieval

Abstract

Systems and methods for core network (CN)-based idle quality of experience (QoE) configuration retrieval are presented. In response to a handover to a radio resource control idle (RRCIdle) state or prior to a wireless communication device, a wireless communication entity may store quality of experience (QoE) related information.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, including but not limited to systems and methods for core network (CN) based idle quality of experience (QoE) configuration retrieval. Background Art

[0002] The 3rd Generation Partnership Project (3GPP), a standards organization, is currently specifying a new radio interface called 5G New Radio (5GNR) and the Next Generation Packet Core (NG-CN or NGC). 5G NR will have three main components: the 5G Access Network (5G-AN), the 5G Core (5GC), and the User Equipment (UE). To facilitate the implementation of different data services and requirements, the elements of the 5GC (also known as network functions) have been simplified, with some being software-based and some being hardware-based so that they can be adjusted as needed. Summary of the Invention

[0003] The example embodiments disclosed herein are directed to solving problems associated with one or more of the problems presented in the prior art, as well as providing additional features that will become apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications can be made to the disclosed embodiments while remaining within the scope of the present disclosure as will be apparent to those skilled in the art reading this disclosure.

[0004] At least one aspect relates to the following systems, methods, apparatuses, or computer-readable media. In response to or prior to a wireless communication device (e.g., a UE) switching to a radio resource control idle (RRC_IDLE) state, a wireless communication entity (e.g., a core network (CN)) may store quality of experience (QoE) related information. The stored QoE related information may include only a QoE reference identifier of a QoE configuration and a RAN-visible QoE (RVQoE) configuration received from a wireless communication node.

[0005] In some embodiments, the wireless communication entity may determine to retrieve QoE-related information. The wireless communication entity may request QoE-related information from an operation, administration, and maintenance (OAM) entity. The QoE configuration may be associated with the wireless communication device and one or more other wireless communication devices. The QoE-related information may include the entirety of the QoE configuration. The entirety of the QoE configuration may include at least one of the following: a QoE reference identifier; a service type; an area scope; an MCEIP address; a QoE configuration container; MDT alignment information; a RAN-visible configuration; an RRC level identifier; UE information associated with the wireless communication device; or a RAN identifier associated with a wireless communication node.

[0006] In some embodiments, in response to identifying that a wireless communication node or wireless communication device is to retrieve QoE related information, the wireless communication entity may send QoE related information to the wireless communication node. A QoE configuration may be associated with the wireless communication device and one or more other wireless communication devices.

[0007] In some embodiments, the QoE-related information may include an identifier of the wireless communication device (e.g., UE ID) and a list of multiple QoE configurations. The list may include the entirety of at least one of the QoE configurations that have been configured for the wireless communication device. The QoE-related information may include an identifier of the wireless communication device (e.g., UE ID) and a list of multiple QoE configurations. The list may include at least one of a QoE reference identifier of the QoE configuration or a RAN-visible QoE (RVQoE) configuration that has been configured for the wireless communication device.

[0008] In some embodiments, a wireless communication entity may send a first message including an indicator for stored QoE-related information to a wireless communication node. The indicator for stored QoE-related information may indicate that the CN has stored the QoE configuration. The wireless communication entity may receive a second message from the wireless communication node. The first message and the second message may each be a Next Generation Application Protocol (NGAP) message. The second message may include at least one of the following: a QoE reference identifier; a service type; an area range; an MCE IP address; a QoE configuration container; MDT alignment information; a RAN-visible configuration; an RRC level identifier; UE information associated with the wireless communication device; or a RAN identifier associated with the wireless communication node.

[0009] In some embodiments, before the wireless communication device switches to the RRC_IDLE state, the process further includes: receiving, by the wireless communication entity, a message including QoE-related information from the wireless communication node. The message may be a Next Generation Application Protocol (NGAP) message. The message may also include at least one of the following: QoE configuration; QoE reference identifier; service type; area range; MCEIP address; QoE measurement status; QoE configuration container; MDT alignment information; RAN visibility configuration; RRC level identifier; NW slice information; or a RAN identifier associated with the wireless communication node.

[0010] In some embodiments, a wireless communication entity may receive a first message from a wireless communication node. The first message may include at least one of: UE information associated with the wireless communication device or stored QoE-related information. The wireless communication entity may send a second message to the wireless communication node confirming the first message. The first message and the second message may each be a Next Generation Application Protocol (NGAP) message. The QoE-related information may be configured to indicate that the QoE configuration should be released. The UE information may be configured to indicate that the wireless communication device is associated with the QoE configuration to be released. The UE information may only indicate the wireless communication device. The QoE configuration may indicate a list of QoE reference identifiers. In some embodiments, the UE information may indicate a list of UE identifiers. The QoE configuration may indicate a list of QoE reference identifiers.

[0011] In some embodiments, a wireless communication entity may receive a message from a wireless communication node that includes an update to QoE-related information. The message may be a Next Generation Application Protocol (NGAP) message. In response to a wireless communication device accessing a network of the wireless communication entity, the method further includes: transmitting, by the wireless communication entity, a message to the wireless communication node that includes the QoE-related information. The message may be a Next Generation Application Protocol (NGAP) message.

[0012] In some embodiments, the message may also include at least one of the following: an indicator of QoE-related information; a QoE reference identifier; a service type; an area range; an MCE IP address; a QoE measurement status; a QoE configuration container; MDT alignment information; a RAN-visible configuration; an RRC level identifier; NW slice information; or a RAN identifier associated with the wireless communication node.

[0013] In some embodiments, in response to a wireless communication node receiving a first message from a wireless communication device, the first message may include at least one of an identifier of the wireless communication device or an indicator of stored QoE-related information. The wireless communication entity may receive a second message from the wireless communication node including an indicator of the stored QoE-related information. The wireless communication entity sends a third message to the wireless communication node including an acknowledgement of the second message. The second message and the third message may each be a Next Generation Application Protocol (NGAP) message. The third message may also include at least one of: an indicator of QoE-related information; a QoE reference identifier; a service type; an area range; an MCE IP address; a QoE measurement status; a QoE configuration container; MDT alignment information; a RAN-visible configuration; an RRC level identifier; NW slice information; or a RAN identifier associated with the wireless communication node. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Various example embodiments of the present solution are described in detail below with reference to the following diagrams or drawings. The drawings are provided for illustrative purposes only and depict only example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered limiting of the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

[0015] Figure 1 An example cellular communication network according to an embodiment of the present disclosure is shown, in which the techniques disclosed herein may be implemented;

[0016] Figure 2 shows a block diagram of example base stations and user equipment apparatus according to some embodiments of the present disclosure;

[0017] Figure 3 A sequence diagram illustrating Next Generation Application Protocol (NGAP) enhancements according to some embodiments of the present disclosure;

[0018] Figure 4 shows a sequence diagram for upload quality of experience (QoE) configuration according to some embodiments of the present disclosure;

[0019] Figure 5 A sequence diagram illustrating Next Generation Application Protocol (NGAP) enhancements according to some embodiments of the present disclosure;

[0020] Figure 6 shows a sequence diagram of Xn Application Protocol (XnAP) enhancements according to some embodiments of the present disclosure;

[0021] Figure 7 A sequence diagram illustrating core network (CN) based idle quality of experience (QoE) configuration retrieval according to some embodiments of the present disclosure is shown;

[0022] Figure 8 A sequence diagram illustrating core network (CN) based idle quality of experience (QoE) configuration retrieval according to some embodiments of the present disclosure; and

[0023] Figure 9 A flowchart of core network (CN)-based idle quality of experience (QoE) configuration retrieval according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0024] 1. Mobile Communication Technology and Environment

[0025] Figure 1 An example wireless communication network and / or system 100 is shown in accordance with an embodiment of the present disclosure, in which the techniques disclosed herein may be implemented. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100." Such an example network 100 includes a base station 102 (hereinafter "BS 102"; also referred to as a wireless communication node) and a user equipment device 104 (hereinafter "UE 104"; also referred to as a wireless communication device) that are capable of communicating with each other via a communication link 110 (e.g., a wireless communication channel), and cell groups 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 1 , BS 102 and UE 104 are contained within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating within its allocated bandwidth to provide adequate wireless coverage to its intended users.

[0026] For example, BS 102 may operate with an allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In the present disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes," which are generally capable of practicing the methods disclosed herein. According to various embodiments of the present solution, such communication nodes may be capable of wireless and / or wired communication.

[0027] Figure 2A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of the present solution is shown. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, the system 200 may be used in applications such as those described above. Figure 1 Data symbols are communicated (eg, transmitted and received) in the wireless communication environment 100 of FIG.

[0028] System 200 generally includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment device 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled to and interconnected with each other via a data communication bus 220 as needed. UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled to and interconnected with each other via a data communication bus 240 as needed. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmitting data as described herein.

[0029] As will be understood by those skilled in the art, the system 200 may also include Figure 2 Any number of modules outside the modules shown. It will be understood by those skilled in the art that the various illustrative blocks, modules, circuits and processing logic described in conjunction with the embodiments disclosed herein can be implemented with hardware, computer-readable software, firmware or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware and software, various illustrative components, blocks, modules, circuits and steps are usually described according to their functions. Whether such functions are implemented in hardware, firmware or software can depend on specific applications and the design constraints imposed on the entire system. Personnel familiar with the concepts described herein can implement this function in an appropriate manner for each specific application, but this implementation decision should not be interpreted as limiting the scope of this disclosure.

[0030] According to some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 and includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time-duplexed manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 and includes an RF transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 212. The downlink duplex switch may alternately couple the downlink transmitter or receiver to the downlink antenna 212 in a time-duplexed manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time so that the downlink transmitter is coupled to the downlink antenna 212 while the uplink receiver circuitry is coupled to the uplink antenna 232 to receive transmissions on the wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time so that the downlink receiver is coupled to the downlink antenna 212 while the uplink transmitter is coupled to the uplink antenna 232 to receive transmissions on the wireless transmission link 250. In some embodiments, there is tight time synchronization with minimal guard times between changes in duplex direction.

[0031] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via a wireless data communication link 250 and to cooperate with an appropriately configured RF antenna arrangement 212 / 232 that can support a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited in application to specific standards and related protocols. Instead, the UE transceiver 230 and the base station transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0032] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, UE 204 may be embodied as various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet, a laptop, a wearable computing device, or the like. Processor modules 214 and 236 may be implemented or realized by a general-purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this manner, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, or the like. The processor may also be implemented as a combination of computing devices, for example, a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a digital signal processor core, or any other such configuration.

[0033] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be embodied directly in hardware, firmware, or software modules executed by processor modules 214 and 236, respectively, or in any practical combination thereof. Memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230, respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include a cache for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0034] The network communication module 218 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communication between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communication module 218 can be configured to support Internet or WiMAX services. In a typical deployment, without limitation, the network communication module 218 provides an 802.3 Ethernet interface, enabling the base station transceiver 210 to communicate with a conventional Ethernet-based computer network. In this manner, the network communication module 218 can include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). The terms "configured for," "configured to," and their conjunctions (as used herein with respect to a specified operation or function) refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0035] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnection and communication with other systems. The model is divided into seven subcomponents or layers, each of which represents a conceptual set of services provided to the layers above and below it. The OSI model also defines a logical network and effectively describes computer data packet transmission by using different layer protocols. The OSI model may also be referred to as a seven-layer OSI model or a seven-layer model. In some embodiments, the first layer may be a physical layer. In some embodiments, the second layer may be a medium access control (MAC) layer. In some embodiments, the third layer may be a radio link control (RLC) layer. In some embodiments, the fourth layer may be a packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be a radio resource control (RRC) layer. In some embodiments, the sixth layer may be a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is other layers.

[0036] Various example embodiments of the present solution are described below with reference to the accompanying drawings to enable one of ordinary skill in the art to complete and use the present solution. It will be apparent to one of ordinary skill in the art that, after reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present solution. Therefore, one of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless expressly stated otherwise, the present solution is not limited to the specific order or hierarchy presented.

[0037] 2. System and method for core network (CN) based idle quality of experience (QoE) configuration retrieval

[0038] Inactive / idle QoE can be supported. Based on the current mechanism, QoE can be activated and collect data when the UE is in the RRC_CONNECTED state. In order to support a new QoE service type (e.g., Multicast and Broadcast Service (MBS)), in some cases, it may be necessary to perform QoE in any RRC state. In some embodiments, a new QoE (e.g., logged QoE) that can be performed in the non-connected state in some cases can be introduced. The following discusses the configuration and reporting of logged QoE.

[0039] In the present disclosure, when a UE switches from RRC_IDLE to RRC_CONNECTED, a CN-based approach allows the RAN node and / or UE to retrieve a previously configured idle QoE configuration. For example, when the UE is in RRC_IDLE, the CN may store the configured idle QoE configuration on the CN side. When the UE reconnects to the network, the CN may resend the stored idle QoE configuration to the RAN node and / or UE for configuration retrieval.

[0040] New Radio (NR) Quality of Experience (QoE) (introduced in Release 17) can only perform QoE measurements when the UE is in RRC_CONNECTED. When the UE is in RRC_CONNECTED, the network (NW) can configure QoE for specific applications of the UE. When the UE starts the application, QoE can be activated and QoE data can be measured. QoE functions that can be performed when the UE is in RRC_IDLE can be introduced.

[0041] Implementation Example 1: When the UE is in RRC_IDLE, the CN can store the idle QoE configuration

[0042] Idle QoE may indicate / mean that QoE-related measurements may be performed when the UE is in a radio resource control idle (RRC_IDLE) state (e.g., CM_IDLE). The core network (CN) may have the capability to store idle QoE (e.g., management-based idle QoE and signaling-based idle QoE) information when the UE is in the RRC_IDLE (e.g., CM_IDLE) state.

[0043] For management-based idle QoE, the CN can receive QoE-related configurations via the RAN node side or the Operation, Administration, and Maintenance (OAM) side. For signaling-based idle QoE, the CN can receive QoE-related configurations via OAM. Considering that RAN-visible QoE (e.g., RAN-visible QoE (RVQoE)) can be configured by the RAN node, after the RVQoE configuration is configured for the UE, the RVQoE configuration can be sent from the RAN node to the CN for storage.

[0044] In some embodiments, there may be four alternatives for the CN to store the configured idle QoE configuration:

[0045] (1) The CN may store only the QoE reference ID of a QoE configuration received from the RAN node and its RVQoE configuration. When the CN needs to retrieve the QoE configuration, the CN may send a request message to the OAM. The OAM may send the QoE configuration to the CN.

[0046] (2) The CN can store the entire QoE configuration. When the UE or RAN node retrieves the QoE configuration, the CN can directly send the stored QoE configuration to the RAN node.

[0047] For each stored idle QoE on the CN side, the list of UEs that have been configured to measure this idle QoE can be linked. The structure of this relationship is shown in Table 1.

[0048] CN Storage QoE Configuration UE information Overall QoE configuration List of UE information …… …… QoE reference ID and (optional) RVQoE configuration List of UE information

[0049] Table 1

[0050] (3) The CN may store a list of UE IDs and one or more configured idle QoE configurations. The list may contain at least one of the overall idle QoE configurations that have been configured for the UE with the UE ID.

[0051] (4) The CN may store a list of UE IDs and one or more configured idle QoE configurations. The list may contain at least one of the following: a QoE reference ID and an optional RVQoE configuration in the QoE configurations that have been configured for the UE with the UE ID.

[0052]

[0053] Table 2

[0054] Implementation Example 2: NGAP Enhancement for Idle QoE Configuration Upload

[0055] Figure 3 A sequence diagram illustrating Next Generation Application Protocol (NGAP) enhancements according to some embodiments of the present disclosure is shown.

[0056] In step 1a, OAM can configure signaling-based QoE to CN.

[0057] Step 1b: The CN may receive the QoE configuration. The CN may send NGAP message 1 to the RAN node. This message may include at least one of the following: a list of the following: a QoE configuration and a configuration indicator stored for this QoE configuration. The stored configuration indicator may be used to indicate whether the QoE configuration is already stored on the CN side. If the RAN node receives the QoE configuration and the indicator, the RAN node may be notified that the RAN-defined QoE configuration may be uploaded to the CN. If the RAN node only receives the QoE configuration, the RAN node may upload the overall configured QoE configuration and the RAN-defined QoE configuration to the CN.

[0058] In step 1c, OAM can configure management-based QoE directly to the RAN node.

[0059] In some embodiments, the OAM in step 1a and step 1c may not be the same. The transmission message from the OAM to other entities (eg, CN, RAN node) may not be a standard message.

[0060] In steps 2 and 3, the RAN node may configure the QoE configuration to the UE via the RRC procedure. In this procedure, RAN-defined configurations (e.g., RAN-visible QoE, RRC level ID) may also be forwarded to the UE.

[0061] In step 4, the RAN node may send an NGAP message (e.g., NGAP message 2) to the CN and may send the configured QoE information to the CN. The message may include at least one of the following information: a QoE reference identifier; a service type; an area scope; a multi-cell / multicast coordination entity (MCE) IP address; a QoE configuration container; a QoE measurement status; NW slice information; minimization of drive test (MDT) alignment information; a RAN-visible configuration; an RRC level identifier; UE information associated with the wireless communication device; or a RAN identifier associated with the wireless communication node. The QoE reference identifier may be defined by OAM and may be used to identify the QoE configuration. The service type may indicate the service type for this QoE measurement. The area scope may be the operating area of this QoE session. This QoE measurement can only be triggered when the UE is located in this area. The area scope may be a cell ID list, a tracking area (TA) list, a public land mobile network (PLMN) list, or a tracking area identity (TAI) list. The MCE IP address may be the IP address of the entity that receives the QoE measurement report. The QoE measurement status may indicate the QoE measurement status (e.g., in progress, or not started). The QoE configuration container may include application layer measurement configuration. NW slice information may indicate which NW slice the QoE can measure. MDT alignment information may be used by the NW to perform MDT and QoE alignment functions. One or more MDT IDs may be included here. The RAN node may determine and configure the RAN-visible QoE configuration to the UE. The RRC level ID may be defined by the RAN node and may be used to distinguish / mark QoE sessions on the RAN side. If the message is a UE-associated message, the UE information may be the Access and Mobility Management Function (AMF) UE NGAPID IE and / or the RAN UE NGAP ID IE. If this message is a non-UE-associated message, the UE information may be the UE group ID, which is used to identify the UE that can be configured with this QoE configuration. The RAN identity associated with the wireless communication node may be used to identify the NG-RAN node. If this message is a UE-associated message, this ID may not be required. If this message is a non-UE-associated message, this ID may be required.

[0062] In some embodiments, step 4 may be triggered before, during, or after steps 2 and 3. The information in step 4 may not always be transmitted. In some embodiments, only some of the above information may be forwarded to the CN. In some embodiments, all of the above information may have to be transmitted to the CN.

[0063] The transmission sequence for signaling-based QoE can be OAM => CN => RAN node => UE. Therefore, when the CN receives a signaling-based QoE configuration from OAM, it can store the configuration and send it to the RAN node. In this case, the RAN node can only transmit RAN-defined QoE configuration (e.g., RVQoE configuration, RRC Level ID) to the CN.

[0064] The transmission sequence for management-based QoE can be OAM => RAN node => UE. Therefore, when the RAN node receives the management-based QoE configuration from OAM, the RAN can transmit the entire configuration of the QoE measurement to the CN. In addition, if OAM can directly transmit management-based QoE to the CN for idle QoE, the RAN node can only transmit the RAN-defined QoE configuration (e.g., RVQoE configuration, RRC level ID) to the CN.

[0065] In step 5, the CN may store the received QoE configuration information.

[0066] Implementation Example 3: RAN can upload idle QoE configuration before releasing UE

[0067] In embodiment example 2, after the RAN sends the QoE configuration to the UE, the RAN can upload all configured QoE configurations (which can be complete or partial) to the CN. This configuration can depend on the CN's behavior in the previous steps. In other words, whenever an idle QoE configuration is configured for the UE, the CN can be aware of the configured QoE configuration.

[0068] Figure 4 A sequence diagram for upload quality of experience (QoE) configuration according to some embodiments of the present disclosure is shown.

[0069] In this embodiment example, the RAN node may upload only the configured idle QoE configuration before the UE switches to the RRC_IDLE state. Before the RAN node completes the RRC release procedure, the RAN node may send NGAP message 1 to the CN. At least one of the following information may be included in this message: UE information; RAN node ID; or configured QoE configuration. The UE information may be used to identify the UE. The RAN node ID may be used to identify the NG-RAN node. The configured QoE configuration may be a list of configured QoE configurations that are still valid and have been configured for the UE. For each configured QoE configuration, at least one of the following information may be included: QoE reference ID; service type; area scope; MCE IP address; QoE measurement status; QoE configuration container; NW slice information; MDT alignment information; RAN-visible configuration; or RRC level ID. The QoE reference ID may be defined by OAM and may be used to identify the QoE configuration. The service type may indicate the service type for this QoE measurement. The area scope may be the operating area of the QoE session. QoE measurement can only be triggered when the UE is located in this area. The area scope can be a cell ID list, a TA list, a PLMN list, or a TAI list. The MCE IP address can be the IP address of the entity that receives the QoE measurement report. The QoE measurement status can indicate the QoE measurement status (e.g., in progress, not started). The QoE configuration container can include application layer measurement configuration. The NW slice information can indicate which NW slice the QoE can measure. MDT alignment information can be used by the NW to perform MDT and QoE alignment functions. One or more MDT IDs can be added here. The RAN node can determine and configure the RAN visible QoE configuration to the UE. The RRC level ID can be defined by the RAN node and can be used to distinguish / mark QoE sessions at the RAN side.

[0070] When the CN receives the NGAP message 1, the CN may store the received information and may reply with ACK information.

[0071] Implementation Example 4: NGAP Enhancement for Idle QoE Configuration Release

[0072] Figure 5 A sequence diagram illustrating Next Generation Application Protocol (NGAP) enhancements according to some embodiments of the present disclosure is shown.

[0073] This procedure can be used by a RAN node to release a QoE configuration stored on the CN side. The RAN node can send NGAP message 1 to the CN. This message can include at least one of the following information: UE-related information or QoE-related information. The UE information can indicate the UE whose QoE configuration can be released. The QoE information can also indicate which QoE configuration can be released.

[0074] After the CN receives the NGAP message 1, the CN may release the QoE configuration of the UE. In some embodiments, the structures of the UE information and the QoE information may be various.

[0075] If the NGAP message is a UE-associated message, the UE information may be a defined IE that can identify a related UE in this procedure. The QoE information may be a list of one or more QoE reference IDs.

[0076] If the NGAP message is not UE-associated, the UE information may be a list of UE information and a table of QoE information. For each associated QoE, a QoE reference ID may be provided. A list of one or more UE IDs may be used to identify UEs configured with a QoE reference ID. Table 3 shows the relationship between QoE information and UE information.

[0077] CN Storage QoE Configuration UE information QoE Reference ID List of UE IDs …… …… QoE Reference ID List of UE IDs

[0078] Table 3

[0079] In addition to this procedure, a timer or a specific time can be used at the CN side for the configured QoE configuration. After the timer expires or a certain time has passed, the CN can automatically trigger the QoE configuration release procedure. Implementation Example 5: NGAP Enhanced RAN Node Can Update QoE Configuration

[0080] As explained in embodiment example 2, part of the QoE configuration (e.g., RVQoE or RRC Level ID) may be determined and configured by the UE's serving RAN node. Therefore, if the RAN node decides to modify this part of the QoE configuration, the RAN node may send the updated QoE configuration to the CN.

[0081] The NGAP message used in step 4, implementation example 2, may also be used to transmit any updates to the configured QoE configuration of the RAN node.

[0082] Implementation Example 6: XnAP Enhanced Node 1 can send idle QoE configuration status to Node 2

[0083] Figure 6 A sequence diagram for Xn Application Protocol (XnAP) enhancements according to some embodiments of the present disclosure is shown.

[0084] This procedure can be used during a UE handover scenario. Node 1 can be the source node, and Node 2 can be the target node. Node 1 can send XnAP message 1 to Node 2. For each configured idle QoE configuration in this message, an indicator can be used to indicate either: this QoE configuration has been transmitted and stored on the CN side; or this QoE configuration has not yet been transmitted and stored on the CN side.

[0085] The UE information can be used to identify which UE is relevant to this procedure. The QoE information can include multiple or one idle QoE configurations that have been configured for this UE.

[0086] When node 2 receives XnAP message 1, node 2 may reply with XnAP message 2 as an ACK message.

[0087] In some embodiments, the procedure can also be used in a DC scenario. In this case, if node 1 is a MN, node 2 can be a SN. If node 1 is a SN, node 2 can be a MN.

[0088] The two meanings of the indicator shown in this embodiment are alternative. In the final protocol, the indicator may have only one meaning: marking the QoE that has not been delivered or marking the QoE that has been delivered.

[0089] Implementation Example 7: CN can proactively detect idle QoE configuration retrieval

[0090] Figure 7 A sequence diagram illustrating core network (CN) based idle quality of experience (QoE) configuration retrieval according to some embodiments of the present disclosure is shown. The UE may be in RRC_IDLE and may trigger an initial access procedure.

[0091] In step 1, the UE may perform normal initial access procedures.

[0092] In step 2, when the CN receives the UE information, the CN may proactively check / detect the stored QoE configuration table (eg, list, container). The CN may look up / detect the UE information in the table.

[0093] In step 3, for each QoE configuration identified by the UE information, the CN may send the retrieved QoE configuration to the RAN node. At least one of the following information may be included in the NGAP message: QoE reference ID, service type, area scope, MCE IP address, QoE measurement status, QoE configuration container, NW slice information, MDT alignment information, RAN-visible configuration, RRC level ID, RAN node ID, retrieved QoE configuration indicator, defined QoE configuration, or retrieved QoS configuration indicator. The QoE reference ID may be defined by OAM and may be used to identify the QoE configuration. The service type may indicate the service type for the QoE measurement. The area scope may be the operating area of the QoE session. This QoE measurement can only be triggered when the UE is located in this area. The area scope may be a cell ID list, a TA list, a PLMN list, or a TAI list. The MCE IP address may be the IP address of the entity receiving the QoE measurement report. The QoE measurement status may indicate the QoE measurement status (e.g., in progress, not started). The QoE configuration container may include application layer measurement configuration. NW slice information may indicate which NW slice QoE can be measured on. MDT alignment information may be used by the NW to perform MDT and QoE alignment functions. One or more MDT IDs may be added here. The RAN node may determine and configure the RAN-visible QoE configuration to the UE. The RRC level ID may be defined by the RAN node and may be used to distinguish / mark QoE sessions at the RAN side. The UE information may be the AMF UE NGAP ID IE and / or the RAN UE NGAP ID IE. The RAN node ID may be used to identify the last serving NG-RAN node before the UE enters the RRC_IDLE state. The retrieved QoE configuration indicator may be used to indicate that the QoE configuration has been configured for the UE. The information contained here may be used for configuration retrieval. The NGAP message may be a response message.

[0094] In step 4 (optional), the RAN node may forward the received QoE configuration to the UE. For each configured idle QoE configuration, at least one of the following information may be included in the RRC message: a defined QoE configuration or a retrieved QoE setting indicator. The defined QoE configuration may reuse the defined QoS configuration format. The retrieved QoE configuration indicator may be used to indicate that the QoE configuration has been configured for the UE. The information contained here may be used for configuration retrieval.

[0095] Implementation Example 8: Retrieving Configured QoE Using Indicators

[0096] Figure 8A sequence diagram illustrating core network (CN) based idle quality of experience (QoE) configuration retrieval according to some embodiments of the present disclosure is shown. The UE may be in RRC_IDLE state and may trigger an initial access procedure.

[0097] In step 1, the UE may access the NW.

[0098] In step 2, the UE may send an RRC message to the RAN node for QoE configuration retrieval. At least one of the following information may be included in the message: UE ID, configured idle QoE indicator, or short IP information. The UE ID may indicate the relevant UE (e.g., UE). The configured idle QoE indicator may be used to indicate that the UE has been configured with QoE that can be performed in the RRC_IDLE state. In some embodiments, step 2 may be optional. If the UE does not perform step 2, step 3 is still valid. The information sent in step 2 may be sent to the RAN node during the initial access procedure or after the UE completes the initial access procedure.

[0099] In step 3, when the RAN node receives this message in step 2 or after the UE accesses the NW, the RAN node may send NGAP message 1 to the CN. At least one of the following information may be included in this message: UE information or a configured idle QoE indicator. The configured idle QoE indicator may be used to indicate that the UE has been configured with QoE that can be performed in the RRC_IDLE state.

[0100] In step 4, based on the information received in step 3 and the QoE configuration table stored by the CN, the CN may send the retrieved QoE configuration to the RAN node. This message may include at least one of the following information: a QoE reference ID, service type, area scope, MCE IP address, QoE measurement status, QoE configuration container, NW slice information, MDT alignment information, RAN-visible configuration, RRC level ID, RAN node ID, or a retrieved QoE configuration indicator. The QoE reference ID may be defined by OAM and may be used to identify the QoE configuration. The service type may indicate the service type for the QoE measurement. The area scope may be the operating area of the QoE session. QoE measurements can only be triggered when the UE is in this area. The area scope may be a cell ID list, a TA list, a PLMN list, or a TAI list. The MCE IP address may be the IP address of the entity that receives the QoE measurement report. The QoE measurement status may indicate the QoE measurement status (e.g., in progress, not started). The QoE configuration container may include application layer measurement configuration. NW slice information may indicate which NW slice QoE can be measured on. MDT alignment information may be used by the NW to perform MDT and QoE alignment functions. One or more MDT IDs may be added here. The RAN node may determine and configure the RAN-visible QoE configuration to the UE. The RRC level ID may be defined by the RAN node and may be used to distinguish / mark QoE sessions at the RAN side. The UE information may be the AMF UE NGAP ID IE and / or the RAN UE NGAP ID IE. The RAN node ID may be used to identify the last serving NG-RAN node before the UE enters the RRC_IDLE state. The retrieved QoE configuration indicator may be used to indicate that the QoE configuration has been configured for the UE. The information contained here may be used for configuration retrieval. The NGAP message may be a response message.

[0101] In step 5 (optional), the RAN node may forward the received QoE configuration to the UE. For each configured idle QoE configuration, at least one of the following information may be included in the NGAP message: a defined QoE configuration or a retrieved QoE setting indicator. The defined QoE configuration may reuse the defined QoS configuration format. The retrieved QoE configuration indicator may be used to indicate that the QoE configuration has been configured for the UE. The information contained here may be used for configuration retrieval.

[0102] In some embodiments, the definition of short IP information can be used in several example implementations of this disclosure. Short IP information can be a marker used to inform the UE of the destination of the generated logged QoE report. Short IP information can be a bit string or a number. Before logging QoE is configured, OAM may have already configured the mapping between short IP information and real IP addresses to the relevant NG-RAN node. The NG-RAN node may store the mapping locally.

[0103] Table 4 shows an example mapping relationship between short IP information and real IP addresses (bit strings).

[0104] Short IP information IP address "…01” 192.168.0.1 "…10” 192.168.0.2 … …

[0105] Table 4

[0106] Table 5 shows an example mapping relationship between short IP information and real IP addresses (numbers).

[0107] Short IP information IP address Integer: 1 192.168.1.1 Floating point number: 123 192.168.1.2 … …

[0108] Table 5

[0109] It should be understood that one or more features from the above-described implementation examples are not exclusive to a particular implementation example, but may be combined in any manner (eg, in any priority and / or order, simultaneously or otherwise).

[0110] Figure 9 A flow chart of a method 900 for retrieving idle quality of experience (QoE) configuration based on a core network (CN) is shown. The method 900 may be used in conjunction with the Figures 1 to 2 The method 900 may be implemented by one or more of any of the components and devices described in detail herein. In general, in some embodiments, the method 900 may be performed by a wireless communication entity. Additional, fewer, or different operations may be performed in the method 900 depending on the embodiment. At least one aspect of the operations may relate to a system, method, apparatus, or computer-readable medium.

[0111] In response to or prior to a wireless communication device (e.g., UE) switching to a radio resource control idle (RRC_IDLE) state, a wireless communication entity (e.g., a core network (CN)) may store information related to quality of experience (QoE). The stored QoE-related information may include only a QoE reference identifier of a QoE configuration and a RAN-visible QoE (RVQoE) configuration received from a wireless communication node.

[0112] In some embodiments, the wireless communication entity may determine to retrieve QoE-related information. The wireless communication entity may request QoE-related information from an operation, administration, and maintenance (OAM) entity. The QoE configuration may be associated with the wireless communication device and one or more other wireless communication devices. The QoE-related information may include the entirety of the QoE configuration. The entirety of the QoE configuration may include at least one of the following: a QoE reference identifier; a service type; an area scope; an MCEIP address; a QoE configuration container; MDT alignment information; a RAN-visible configuration; an RRC level identifier; UE information associated with the wireless communication device; or a RAN identifier associated with a wireless communication node.

[0113] In some embodiments, in response to identifying that a wireless communication node or wireless communication device is to retrieve QoE related information, the wireless communication entity may send QoE related information to the wireless communication node. A QoE configuration may be associated with the wireless communication device and one or more other wireless communication devices.

[0114] In some embodiments, the QoE-related information may include an identifier of the wireless communication device (e.g., UE ID) and a list of multiple QoE configurations. The list may include the entirety of at least one of the QoE configurations that have been configured for the wireless communication device. The QoE-related information may include an identifier of the wireless communication device (e.g., UE ID) and a list of multiple QoE configurations. The list may include at least one of a QoE reference identifier of the QoE configuration or a RAN-visible QoE (RVQoE) configuration that has been configured for the wireless communication device.

[0115] In some embodiments, a wireless communication entity may send a first message including an indicator for stored QoE-related information to a wireless communication node. The indicator for stored QoE-related information may indicate that the CN has stored the QoE configuration. The wireless communication entity may receive a second message from the wireless communication node. The first message and the second message may each be a Next Generation Application Protocol (NGAP) message. The second message may include at least one of the following: a QoE reference identifier; a service type; an area range; an MCE IP address; a QoE configuration container; MDT alignment information; a RAN-visible configuration; an RRC level identifier; UE information associated with the wireless communication device; or a RAN identifier associated with the wireless communication node.

[0116] In some embodiments, before the wireless communication device switches to the RRC_IDLE state, the process further includes: receiving, by the wireless communication entity, a message including QoE-related information from the wireless communication node. The message may be a Next Generation Application Protocol (NGAP) message. The message may also include at least one of the following: QoE configuration; QoE reference identifier; service type; area range; MCEIP address; QoE measurement status; QoE configuration container; MDT alignment information; RAN visibility configuration; RRC level identifier; NW slice information; or a RAN identifier associated with the wireless communication node.

[0117] In some embodiments, a wireless communication entity may receive a first message from a wireless communication node. The first message may include at least one of the following: UE information associated with the wireless communication device or stored QoE-related information. The wireless communication entity may send a second message to the wireless communication node confirming the first message. The first message and the second message may each be a Next Generation Application Protocol (NGAP) message. The QoE-related information may be configured to indicate that the QoE configuration should be released. The UE information may be configured to indicate that the wireless communication device is associated with the QoE configuration to be released. The UE information may only indicate the wireless communication device. The QoE configuration may indicate a list of QoE reference identifiers. In some embodiments, the UE information may indicate a list of UE identifiers. The QoE configuration may indicate a list of QoE reference identifiers.

[0118] In some embodiments, a wireless communication entity may receive a message from a wireless communication node that includes an update to QoE-related information. The message may be a Next Generation Application Protocol (NGAP) message. In response to a wireless communication device accessing a network of the wireless communication entity, the method further includes: transmitting, by the wireless communication entity, a message to the wireless communication node that includes the QoE-related information. The message may be a Next Generation Application Protocol (NGAP) message.

[0119] In some embodiments, the message may also include at least one of the following: an indicator of QoE-related information; a QoE reference identifier; a service type; an area range; an MCE IP address; a QoE measurement status; a QoE configuration container; MDT alignment information; a RAN-visible configuration; an RRC level identifier; NW slice information; or a RAN identifier associated with the wireless communication node.

[0120] In some embodiments, in response to a wireless communication node receiving a first message from a wireless communication device, the first message may include at least one of an identifier of the wireless communication device or an indicator of stored QoE-related information. The wireless communication entity may receive a second message from the wireless communication node including an indicator of the stored QoE-related information. The wireless communication entity sends a third message to the wireless communication node including an acknowledgement of the second message. The second message and the third message may each be a Next Generation Application Protocol (NGAP) message. The third message may also include at least one of: an indicator of QoE-related information; a QoE reference identifier; a service type; an area range; an MCE IP address; a QoE measurement status; a QoE configuration container; MDT alignment information; a RAN-visible configuration; an RRC level identifier; NW slice information; or a RAN identifier associated with the wireless communication node.

[0121] Although various embodiments of the present solution have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, the various figures may depict example architectures or configurations that are provided to enable one of ordinary skill in the art to understand the example features and functionality of the present solution. However, such persons will understand that the present solution is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. In addition, as one of ordinary skill in the art will understand, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the illustrative embodiments described above.

[0122] It should also be understood that any reference to an element herein using names such as "first," "second," etc. does not generally limit the number or order of those elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, reference to a first element and a second element does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.

[0123] Furthermore, those skilled in the art will appreciate that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0124] Those of ordinary skill in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design code containing instructions (which, for convenience, can be referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been generally described above with respect to their functions. Whether such functions are implemented in hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions do not result in a departure from the scope of this disclosure.

[0125] In addition, it will be understood by those skilled in the art that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented within or performed by an integrated circuit (IC) that includes a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits can further include an antenna and / or a transceiver to communicate with various components within a network or within a device. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other suitable configuration that performs the functions described herein.

[0126] If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, and communication media include any media that enables a computer program or code to be transferred from one place to another. The storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage device, or any other medium that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0127] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements used to perform the relevant functions described herein. In addition, for ease of discussion, various modules are described as separate modules; however, it is obvious to those skilled in the art that two or more modules can be combined to form a single module that performs the relevant functions according to embodiments of the present solution.

[0128] In addition, in embodiments of the present solution, memories or other memories and communication components may be employed. It will be understood that, for the sake of clarity, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the present solution. For example, functions shown as being performed by different processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to appropriate means for providing the described functionality, rather than an indication of a strict logical or physical structure or organization.

[0129] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, the present disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims.

Claims

1. A wireless communication method, the method comprising: In response to or before the wireless communication device switches to a radio resource control idle (RRC_Idle) state, the wireless communication entity stores information related to quality of experience (QoE).

2. The wireless communication method according to claim 1, wherein: The stored QoE-related information only includes the QoE reference identifier of the QoE configuration and the RAN-visible QoE (RVQoE) configuration received from the wireless communication node.

3. The wireless communication method according to claim 2, further comprising: Determining, by the wireless communication entity, to retrieve the QoE-related information; as well as The wireless communication entity requests the QoE-related information from an operation, administration, and maintenance (OAM) entity.

4. The wireless communication method according to claim 2, wherein: The QoE configuration is associated with the wireless communication device and one or more other wireless communication devices. The wireless communication method according to claim 1 , wherein: The QoE-related information includes the entire QoE configuration. The wireless communication method according to claim 5 , wherein: The overall QoE configuration includes at least one of the following: QoE reference identifier; Type of service; Regional scope; MCE IP address; QoE configuration container; MDT alignment information; RAN visible configuration; RRC level identification; UE information associated with the wireless communication device; or A RAN identifier associated with the wireless communication node.

7. The wireless communication method according to claim 5, further comprising: In response to identifying that the wireless communication node or the wireless communication device is to retrieve the QoE-related information, the wireless communication entity sends the QoE-related information to the wireless communication node. The wireless communication method according to claim 5 , wherein: The QoE configuration is associated with the wireless communication device and one or more other wireless communication devices.

9. The wireless communication method according to claim 1, wherein: The QoE-related information includes an identification of the wireless communication device and a list including a plurality of QoE configurations, and wherein the list includes an entirety of at least one of the QoE configurations that have been configured for the wireless communication device.

10. The wireless communication method according to claim 1, wherein: The QoE-related information includes an identifier of the wireless communication device and a list including multiple QoE configurations, and wherein the list includes at least one of the following: a QoE reference identifier of the QoE configuration, or a RAN-visible QoE (RVQoE) configuration that has been configured for the wireless communication device.

11. The wireless communication method according to claim 1 , further comprising: Sending, by the wireless communication entity, a first message to the wireless communication node, the first message including an indicator for the stored QoE-related information; as well as receiving, by the wireless communication entity, a second message from the wireless communication node; The first message and the second message are each Next Generation Application Protocol (NGAP) messages.

12. The wireless communication method according to claim 11, wherein: The second message includes at least one of the following: QoE reference identifier; Type of service; Regional scope; MCE IP address; QoE configuration container; MDT alignment information; RAN visible configuration; RRC level identification; UE information associated with the wireless communication device; or A RAN identifier associated with the wireless communication node.

13. The wireless communication method according to claim 1, further comprising: before the wireless communication device switches to the RRC_IDLE state; Receiving, by the wireless communication entity, a message including the QoE-related information from a wireless communication node; The message is a Next Generation Application Protocol (NGAP) message.

14. The wireless communication method according to claim 13, wherein: The message also includes at least one of the following: QoE configuration; QoE reference identifier; Type of service; Regional scope; MCE IP address; QoE measurement status; QoE configuration container; MDT alignment information; RAN visible configuration; RRC level identification; NW slice information; or A RAN identifier associated with the wireless communication node.

15. The wireless communication method according to claim 1, further comprising: Receiving, by the wireless communication entity, a first message from a wireless communication node, the first message including at least one of: UE information associated with the wireless communication device, or stored QoE-related information; and Sending, by the wireless communication entity, a second message confirming the first message to the wireless communication node; The first message and the second message are each Next Generation Application Protocol (NGAP) messages.

16. The wireless communication method according to claim 15, wherein: The QoE-related information is configured to indicate that a QoE configuration should be released, and the UE information is configured to indicate that the wireless communication device is associated with the QoE configuration to be released.

17. The wireless communication method according to claim 16, wherein: The UE information indicates only the wireless communication device, and the QoE configuration indicates a list of QoE reference identifiers.

18. The wireless communication method according to claim 16, wherein: The UE information indicates a list of UE identities, and the QoE configuration indicates a list of QoE reference identities.

19. The wireless communication method according to claim 1, further comprising: receiving, by the wireless communication entity, a message including an update of the QoE-related information from a wireless communication node; The message is a Next Generation Application Protocol (NGAP) message.

20. The wireless communication method according to claim 1, further comprising: in response to the wireless communication device accessing the network of the wireless communication entity; Sending, by the wireless communication entity, a message including the QoE-related information to a wireless communication node; The message is a Next Generation Application Protocol (NGAP) message.

21. The wireless communication method according to claim 20, wherein: The message also includes at least one of the following: an indicator for the QoE-related information; QoE reference identifier; Type of service; Regional scope; MCE IP address; QoE measurement status; QoE configuration container; MDT alignment information; RAN visible configuration; RRC level identification; NW slice information; or A RAN identifier associated with the wireless communication node.

22. The wireless communication method according to claim 1 , in response to a wireless communication node receiving a first message from the wireless communication device, the first message including at least one of an identification of the wireless communication device or an indicator of stored QoE-related information, the method further comprising: receiving, by the wireless communication entity, a second message from the wireless communication node, the second message including an indicator for the stored QoE-related information; as well as Sending, by the wireless communication entity, a third message including confirmation of the second message to the wireless communication node; The second message and the third message are each Next Generation Application Protocol (NGAP) messages.

23. The wireless communication method according to claim 22, wherein: The third message further includes at least one of the following: an indicator for the QoE-related information; QoE reference identifier; Type of service; Regional scope; MCE IP address; QoE measurement status; QoE configuration container; MDT alignment information; RAN visible configuration; RRC level identification; NW slice information; or A RAN identifier associated with the wireless communication node.

24. A wireless communication device comprising a processor and a memory, wherein: The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 23.

25. A computer program product comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to carry out the method according to any one of claims 1 to 23.

Images