Collecting and reporting quality of experience information

Abstract

[0001] This application relates to methods, systems, and devices related to digital wireless communications, and more particularly to techniques related to quality of experience (QoE) measurement collection. In one example aspect, a method for wireless communications includes receiving, by a terminal, from a network node, a first message including a configuration for collecting quality of experience information. The method also includes transmitting, by the terminal to the network node, a second message including a set of quality of experience information collected by the terminal and transmitted in accordance with the configuration for collecting quality of experience information received in the first message.

Description

[Technical field]

[0001] This patent document is generally directed to wireless communications. [Background technology]

[0002] Mobile communication technologies are moving the world towards an increasingly connected and networked society. The rapid growth of mobile communication and technological advances are leading to further demands for capacity and connectivity. Other aspects such as energy consumption, device costs, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios. Various techniques are being discussed, including new methods to provide a higher quality of service. Summary of the Invention [Means for solving the problem]

[0003] This document relates to methods, systems, and devices relating to digital wireless communications, and more particularly to techniques relating to Quality of Experience (QoE) measurement collection.

[0004] In one example aspect, a method for wireless communication is disclosed. The method includes receiving, by a terminal, a first message from a network node, the first message including a configuration for collecting quality of experience information. The method also includes transmitting, by the terminal to the network node, a second message including a set of quality of experience information collected by the terminal and transmitted in accordance with the configuration for collecting quality of experience information received in the first message.

[0005] In another example aspect, a method for wireless communication is disclosed. The method includes transmitting, by a network node, a first message to a terminal, the first message including a configuration for collecting quality of experience information. The method also includes receiving, by the network node, from the terminal, a second message including a set of quality of experience information collected by the terminal, the second message being transmitted in accordance with the configuration for collecting quality of experience information received in the first message.

[0006] In another exemplary aspect, a wireless communication apparatus is disclosed that includes a processor configured to implement the methods described herein.

[0007] In yet another illustrative aspect, the various techniques described herein may be embodied as processor-executable code and stored on a computer-readable program medium.

[0008] Some embodiments may implement the following solution, preferably written in appendix format.

[0009] 1. A solution for wireless communication comprising: receiving, by a terminal, from a network node, a first message including a configuration for collecting quality of experience information; and transmitting, by the terminal to the network node, a second message including a set of quality of experience information collected by the terminal and transmitted in accordance with the configuration for collecting quality of experience information received in the first message.

[0010] 2. The solution of claim 1, further comprising collecting, by the terminal, a set of quality of experience information.

[0011] 3. The solution of claim 1, wherein either the configuration for collecting quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes quality of service (QoS) information.

[0012] 4. The solution of claim 3, wherein the QoS information includes any of a QoS flow identifier (QFI), a protocol data unit (PDU) session identifier, an Evolved Universal Terrestrial Access Network (E-UTRAN) Radio Access Bearer Identifier (E-RAB ID), and QoS profile information.

[0013] 5. The solution of claim 1, wherein either the configuration for collecting quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes a network slice identifier.

[0014] 6. The solution of claim 1, wherein either the configuration for collecting quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes information identifying a target radio access technology (RAT) for collecting the set of quality of experience information therein.

[0015] 7. The solution of claim 6, wherein the information identifying the target RAT includes either a cell identification list of at least one RAT, or a tracking area code list of at least one RAT or RAT type.

[0016] 8. The solution of claim 1, wherein either the configuration for collecting quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes node information indicating a target node for collecting the set of quality of experience information therein.

[0017] 9. The solution of claim 1, wherein either the configuration for collecting quality of experience information included in the first message and the collected set of quality of experience information included in the second message includes a bearer type indicator indicating a target bearer type for collecting the set of quality of experience information.

[0018] 10. The solution as set forth in Appendix 9, wherein the bearer type indicator may indicate either a master cell group (MCG) bearer, a secondary cell group (SCG) bearer, a split bearer, a master node (MN) terminated MCG bearer, a MN terminated SCG bearer, a MN terminated split bearer, a secondary node (SN) terminated MCG bearer, a SN terminated SCG bearer, or a SN terminated split bearer.

[0019] 11. The solution of claim 1, wherein the configuration for collecting quality of experience information includes several application configuration containers, each application configuration container applying to a specific RAT.

[0020] 12. The solution of claim 2, wherein collecting a set of quality of experience information includes logging bearer type and timestamp information of the service collected in accordance with a configuration for collecting quality of experience information.

[0021] 13. The solution of Appendix 1, further comprising: receiving, by the terminal, a plurality of configurations for measuring quality of experience information from each of a master node (MN) and a secondary node (SN); measuring, by the terminal, a first set of quality of experience information when a bearer is established via a master cell group (MCG) radio interface, and a second set of quality of experience information when a bearer is established via a secondary cell group (SCG) radio interface; and transmitting, by the terminal, a first report to the MN including the first set of quality of experience information and a second report to the SN including the second set of quality of experience information.

[0022] 14. The solution of claim 1, wherein the second message is transmitted in response to the terminal measuring a set of quality of experience information.

[0023] 15. The solution of Appendix 1, further comprising: transmitting, by the terminal, a quality of experience information indication to the network node, indicating that the terminal has collected a set of quality of experience information; and receiving, by the terminal, a quality of experience information response from the network node, wherein the second message is transmitted by the terminal in response to receiving the quality of experience information response from the network node.

[0024] 16. The solution of claim 1, further comprising transmitting, by the terminal, to the network node, a one-bit quality of experience information result available indication indicating that the terminal has measured a set of quality of experience information.

[0025] The solution of claim 16, wherein the 1-bit quality of experience information result available indication is transmitted to the network node via one of a radio resource control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC configuration complete message, and an RRC resume complete message.

[0026] 18. The solution of any of Supplementary Notes 16 and 17, further comprising receiving, by the terminal, an RRC message from the network node, including a request for a set of quality of experience information, when network load falls below a threshold level, wherein the terminal transmits a second message to the network node in response to receiving the RRC message from the network node.

[0027] 19. The solution of claim 1, further comprising receiving, by the terminal, a pause indication from the network node, the pause indication including an indication that the terminal pauses transmission of the second message and / or stops measuring the set of quality of experience information.

[0028] 20. The solution of claim 20, further comprising receiving, by the terminal, a resume indication from the network node, and the second message being transmitted by the terminal in response to receiving the resume indication from the network node.

[0029] 21. The solution of claim 19, further comprising starting, by the terminal, a timer with a duration indicated in the pause indication in response to either receiving a pause indication or completing collection of the set of quality of experience information, and, upon expiration of the timer, releasing, by the terminal, the set of quality of experience information collected by the terminal.

[0030] 22. The solution of any of Supplementary Notes 1 and 19, further comprising: determining, by the terminal, that a power consumption level of the terminal exceeds a threshold power level; and in response to determining that the power consumption level of the terminal exceeds the threshold power level, transmitting, by the terminal to a network node, a power save message that initiates a power save operation, wherein a pause indication is received by the terminal in response to transmitting the power save message.

[0031] 23. A solution for wireless communication comprising: transmitting, by a network node, a first message to a terminal, the first message including a configuration for collecting quality of experience information; and receiving, by the network node, from the terminal, a second message including a set of quality of experience information collected by the terminal, the second message being transmitted in accordance with the configuration for collecting quality of experience information received in the first message.

[0032] 24. The solution of claim 23, further comprising receiving, by the network node, a configuration for collecting quality of experience information from a core network node or an operations and maintenance (OAM) entity.

[0033] 25. The solution of any of Addendum 23 and 24, further comprising forwarding the second message by the network node to the QoE collection node.

[0034] 26. The solution of any of Addendums 24 and 25, wherein the core network node includes any of a core access and mobility management function (AMF) node and a mobility management entity (MME) node.

[0035] 27. The solution described in Appendix 23, further comprising forwarding, by the network node, a configuration for collecting quality of experience information to a secondary network node, the secondary network node being configured to modify and / or transmit the configuration for collecting quality of experience information to the terminal.

[0036] 28. The solution of claim 23, wherein the network node includes a central unit (CU), and the network node transmits a configuration for collecting quality of experience information to the distributed unit (CU), and the configuration for collecting the quality of experience information includes any of a requested service type for the set of quality of experience information, dedicated radio bearer (DRB) information for the requested service type, and an indication to start, stop, or pause measurement of the set of quality of experience information by the terminal.

[0037] 29. The solution of claim 23, further comprising receiving, by the network node, from the secondary network node, a configuration indication of whether the network node is capable of configuring the terminal to collect quality of experience information.

[0038] 30. The solution of claim 29, wherein the configuration indication is received by the network node in response to the secondary network node determining that the terminal supports quality of experience information measurement and reporting via a radio access technology (RAT) associated with the secondary network node.

[0039] 31. The solution of claim 29, wherein the configuration indication is received by the network node in response to a secondary network node supporting and reporting quality of experience information measurement towards the terminal.

[0040] 32. The solution of any of Supplementary Note 23 and Supplementary Note 24, wherein any of the configuration for collecting quality of experience information included in the first message, the measured set of quality of experience information included in the second message, and the configuration for collecting quality of experience information from a core network node includes any of quality of service (QoS) information, a network slice selection identifier, information identifying a target radio access technology (RAT) for measuring the set of quality of experience information therein, node information indicating a target node for measuring the set of quality of experience information therein, and a bearer type indicator indicating a target bearer type for measuring the set of quality of experience information therein.

[0041] 33. The solution of claim 23, further comprising: transmitting, by the network node, to the terminal, one of a plurality of configurations for measuring quality of experience information; receiving, by the network node, from the terminal, a first report including a first set of quality of experience information measured by the terminal when the bearer is established via a master cell group (MCG) radio interface; and receiving, by the network node, from the terminal, a second report including a second set of quality of experience information measured by the terminal when the bearer is established via a secondary cell group (SCG) radio interface.

[0042] 34. The solution of claim 23, further comprising receiving, by the network node, a quality of experience information indication from the terminal indicating that the terminal has measured a set of quality of experience information; and transmitting, by the network node, a quality of experience information response to the terminal, wherein the second message is transmitted by the terminal in response to receiving the quality of experience information response from the network node.

[0043] 35. The solution of claim 23, further comprising receiving, by the network node, from the terminal a one-bit quality of experience information result available indication indicating that the terminal has measured a set of quality of experience information.

[0044] 36. The solution of claim 35, wherein the 1-bit quality of experience information results in an availability indication received by the network node via any of a radio resource control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC configuration complete message, and an RRC resume complete message.

[0045] 37. The solution described in any of notes 35 and 36, further comprising transmitting, by the network node to the terminal when network load falls below a threshold level, an RRC message including a request for a set of quality of experience information, and in response to receiving the RRC message from the network node, the terminal transmitting a second message to the network node.

[0046] 38. The solution of claim 23, further comprising transmitting, by the network node, a pause indication to the terminal, the pause indication including an indication to the terminal to pause transmission of the second message and / or to stop measuring the set of quality of experience information.

[0047] 39. The solution of claim 38, further comprising transmitting, by the network node, a resume indication to the terminal, the second message being transmitted by the terminal in response to receiving the resume indication from the network node.

[0048] 40. The solution of any of Supplementary Notes 23 and 39, further comprising receiving, by the network node, from the terminal in response to the terminal determining that the terminal's power consumption level exceeds a threshold power level, a power save message that initiates a power save operation, and a pause indication is received by the terminal in response to transmission of the power save message.

[0049] 41. An apparatus for wireless communication comprising a processor configured to execute the solution described in any of Supplementary Notes 1-40.

[0050] 42. A non-transitory computer readable medium having code stored thereon, the code, when executed by a processor, causing the processor to implement the solution described in any of Notes 1-40.

[0051] Details of one or more implementations are set forth in the accompanying attachments, drawings, and description below. Other features will be apparent from the description and drawings, and from the attachments. For example, the present application provides the following: (Item 1) 1. A method for wireless communication, comprising: receiving, by the terminal, from a network node, a first message including a configuration for collecting quality of experience information; transmitting, by the terminal, to the network node, a second message including a set of quality of experience information collected by the terminal and transmitted in accordance with a configuration for collecting the quality of experience information received in the first message; A method comprising: (Item 2) measuring said set of quality of experience information by said device; The method of claim 1, further comprising: (Item 3) 2. The method of claim 1, wherein either the configuration for collecting the quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes quality of service (QoS) information. (Item 4) The method of claim 3, wherein the QoS information includes any one of a QoS flow identifier (QFI), a protocol data unit (PDU) session identifier, an evolved universal terrestrial access network (E-UTRAN) radio access bearer identifier (E-RAB ID), and QoS profile information. (Item 5) 2. The method of claim 1, wherein either the configuration for collecting the quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes a network slice identifier. (Item 6) 2. The method of claim 1, wherein either the configuration for collecting the quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes information identifying a target radio access technology (RAT) for collecting the set of quality of experience information therein. (Item 7) 7. The method according to item 6, wherein the information identifying the target RAT includes either a cell identification list of at least one RAT or a tracking area code list of at least one RAT or RAT type. (Item 8) 2. The method of claim 1, wherein either the configuration for collecting the quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes node information indicating a target node for collecting the set of quality of experience information therein. (Item 9) 2. The method of claim 1, wherein either the configuration for collecting the quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes a bearer type indicator indicating a target bearer type for collecting the set of quality of experience information. (Item 10) The method according to item 9, wherein the bearer type indicator can indicate any of a master cell group (MCG) bearer, a secondary cell group (SCG) bearer, a split bearer, a master node (MN) terminated MCG bearer, a MN terminated SCG bearer, a MN terminated split bearer, a secondary node (SN) terminated MCG bearer, a SN terminated SCG bearer, or a SN terminated split bearer. (Item 11) The method according to item 1, wherein the configuration for collecting the quality of experience information includes several application configuration containers, each of which applies to a specific RAT. (Item 12) 3. The method of claim 2, wherein collecting the set of quality of experience information includes logging bearer type and timestamp information of the service collected according to a configuration for collecting the quality of experience information. (Item 13) receiving, by the terminal, a plurality of configurations for measuring quality of experience information from a master node (MN) and a secondary node (SN), respectively; measuring, by the terminal, a first set of quality of experience information when a bearer is established over a master cell group (MCG) air interface and a second set of quality of experience information when the bearer is established over a secondary cell group (SCG) air interface; transmitting, by said terminal, a first report to said MN, said first set of quality of experience information, and transmitting, by said terminal, a second report to said SN, said second set of quality of experience information; The method of claim 1, further comprising: (Item 14) 2. The method of claim 1, wherein the second message is transmitted in response to the terminal measuring the set of quality of experience information. (Item 15) transmitting, by the terminal, to the network node, a quality of experience information indication indicating that the terminal has collected the set of quality of experience information; receiving, by the terminal, a quality of experience information response from the network node, the second message being transmitted by the terminal in response to receiving the quality of experience information response from the network node; The method of claim 1, further comprising: (Item 16) transmitting, by the terminal, to the network node, a one-bit quality of experience information result available indication indicating that the terminal has measured the set of quality of experience information; The method of claim 1, further comprising: (Item 17) The method according to item 16, wherein the 1-bit quality of experience information result availability indication is transmitted to the network node via any one of a radio resource control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC configuration complete message, and an RRC resume complete message. (Item 18) receiving, by the terminal, from the network node an RRC message including a request for the set of quality of experience information when network load falls below a threshold level, the terminal transmitting the second message to the network node in response to receiving the RRC message from the network node. 18. The method according to any one of items 16 and 17, further comprising: (Item 19) receiving, by the terminal, from the network node, a pause indication, the pause indication including an indication for the terminal to pause transmission of the second message and / or stop measuring the set of quality of experience information. The method of claim 1, further comprising: (Item 20) receiving, by the terminal, a resume indication from the network node, the second message being transmitted by the terminal in response to receiving the resume indication from the network node; 20. The method of claim 19, further comprising: (Item 21) starting, by the terminal, in response to either receiving the pause indication or completing collection of the set of quality of experience information, a timer with a duration indicated in the pause indication; releasing, by the terminal, the set of quality of experience information collected by the terminal when the timer expires; 20. The method of claim 19, further comprising: (Item 22) determining, by the terminal, that a power consumption level of the terminal exceeds a threshold power level; transmitting, by the terminal to the network node in response to determining that a power consumption level of the terminal exceeds the threshold power level, a power save message initiating a power save operation, the suspend indication being received by the terminal in response to transmitting the power save message; 20. The method of any one of items 1 and 19, further comprising: (Item 23) 1. A method for wireless communication, comprising: transmitting, by the network node, a first message to the terminal, the first message including a configuration for collecting quality of experience information; receiving, by the network node, from the terminal, a second message including a set of quality of experience information collected by the terminal, the second message being transmitted according to a configuration for collecting the quality of experience information received in the first message; A method comprising: (Item 24) receiving, by said network node, from a core network node, a configuration for collecting said quality of experience information; 24. The method of claim 23, further comprising: (Item 25) forwarding said second message by said network node to a QoE collection node; 25. The method according to any one of items 23 and 24, further comprising: (Item 26) 26. The method according to any one of items 24 and 25, wherein the core network node includes any one of a core access and mobility management function (AMF) node and a mobility management entity (MME) node. (Item 27) forwarding, by said network node, a configuration for collecting said quality of experience information to a secondary network node, said secondary network node being configured to modify and / or transmit said configuration for collecting said quality of experience information to said terminal; 24. The method of claim 23, further comprising: (Item 28) The method according to item 23, wherein the network node includes a central unit (CU), and the network node transmits a configuration for collecting the quality of experience information to the distributed unit (CU), and the configuration for collecting the quality of experience information includes any one of a requested service type for the set of quality of experience information, dedicated radio bearer (DRB) information for the requested service type, and an indication to start, stop, or pause measurement of the set of quality of experience information by the terminal. (Item 29) receiving, by the network node, from the secondary network node, a configuration indication of whether the network node is capable of configuring the terminal to collect the quality of experience information; 24. The method of claim 23, further comprising: (Item 30) 30. The method of claim 29, wherein the configuration indication is received by the network node in response to the secondary network node determining that the terminal supports quality of experience information measurement and reporting via a radio access technology (RAT) associated with the secondary network node. (Item 31) 30. The method of claim 29, wherein the configuration indication is received by the network node in response to the secondary network node supporting and reporting quality of experience information measurement towards the terminal. (Item 32) A method according to any one of items 23 and 24, wherein any one of the configuration for collecting the quality of experience information included in the first message, the measured set of quality of experience information included in the second message, and the configuration for collecting the quality of experience information from a core network node includes any one of quality of service (QoS) information, a network slice selection identifier, information identifying a target radio access technology (RAT) for measuring the set of quality of experience information, node information indicating a target node for measuring the set of quality of experience information, and a bearer type indicator indicating a target bearer type for measuring the set of quality of experience information. (Item 33) transmitting, by the network node, to the terminal, one of a plurality of configurations for measuring quality of experience information; receiving, by the network node, a first report from the terminal when a bearer is established over a master cell group (MCG) air interface, the first report including a first set of quality of experience information measured by the terminal; receiving, by the network node, a second report from the terminal when the bearer is established over a secondary cell group (SCG) air interface, the second report including a second set of quality of experience information measured by the terminal; 24. The method of claim 23, further comprising: (Item 34) receiving, by the network node, a quality of experience information indication from the terminal indicating that the terminal has measured the set of quality of experience information; transmitting, by the network node, a quality of experience information response to the terminal, the second message being transmitted by the terminal in response to receiving the quality of experience information response from the network node; 24. The method of claim 23, further comprising: (Item 35) receiving, by the network node, from the terminal a one-bit quality of experience information results available indication indicating that the terminal has measured the set of quality of experience information; 24. The method of claim 23, further comprising: (Item 36) Item 36. The method of item 35, wherein the one-bit quality of experience information results in an availability indication received by the network node via any one of a radio resource control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC configuration complete message, and an RRC resume complete message. (Item 37) transmitting, by the network node, an RRC message including a request for the set of quality of experience information to the terminal when network load falls below a threshold level, the terminal transmitting the second message to the network node in response to receiving the RRC message from the network node. 37. The method according to any one of items 35 and 36, further comprising: (Item 38) transmitting, by the network node, to the terminal, a pause indication, the pause indication including an indication that the terminal pauses transmission of the second message and / or stops measuring the set of quality of experience information. 24. The method of claim 23, further comprising: (Item 39) transmitting, by the network node, a resume indication to the terminal, the second message being transmitted by the terminal in response to receiving the resume indication from the network node. 39. The method of claim 38, further comprising: (Item 40) receiving, by the network node, a power save message from the terminal in response to the terminal determining that a power consumption level of the terminal exceeds a threshold power level, the power save message initiating a power save operation, the suspend indication being received by the terminal in response to transmission of the power save message; 40. The method of any one of items 23 and 39, further comprising: (Item 41) Item 41. An apparatus for wireless communication comprising a processor configured to perform the method according to any one of items 1-40. (Item 42) A non-transitory computer readable medium having code stored thereon that, when executed by a processor, causes the processor to implement a method according to any of items 1-40. [Brief description of the drawings]

[0052] [Figure 1] FIG. 1 is an example signaling process for signaling-based QoE measurement.

[0053] [Diagram 2]FIG. 2 is an exemplary signaling process for management-based QoE measurement.

[0054] [Diagram 3] FIG. 3 is an example signaling process for QoE measurement configuration for an MR-DC UE.

[0055] [Figure 4] FIG. 4 is an example signaling process for QoE measurement reporting for an MR-DC UE.

[0056] [Diagram 5] FIG. 5 is an example signaling process for SN QoE measurable indication.

[0057] [Figure 6] FIG. 6 is an example signaling process for SN QoE measurement permission indication.

[0058] [Figure 7] FIG. 7 is a block diagram of an example method for quality of experience (QoE) measurement collection.

[0059] [Figure 8] FIG. 8 illustrates an example of a wireless communication system in which techniques according to one or more embodiments of the present technology may be applied.

[0060] [Figure 9] FIG. 9 is a block diagram representation of a portion of the hardware platform. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0061] Detailed Description The development of a new generation of wireless communication, namely 5G New Radio (NR) communication, is part of the continuous mobile broadband evolution process to meet the requirements of increasing network demand. NR will provide higher throughput to allow more users to be connected simultaneously. Other aspects such as energy consumption, device cost, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios.

[0062] In various wireless communication systems, a quality of experience (QoE) measurement collection framework can support multiple triggering scenarios, examples of which can include signaling-based QoE measurements and management-based QoE measurements.

[0063] For signaling-based QoE measurement, the core network may trigger QoE collection towards a specific UE, and the core network may deliver the QoE measurement configuration to the network via UE-specific signaling. For management-based QoE measurement, an operation, administration, and maintenance (OAM) node may deliver a QoE collection mission to a radio access network (RAN) node, and the RAN node may select one or more suitable UEs to perform QoE measurement collection and reporting.

[0064] In addition, the UE can inform the network whether it supports QoE measurement collection. More specifically, the UE can indicate separate capabilities for streaming services and Multimedia Telephony Services (MTSI) for IP Multimedia Subsystem (IMS) services. Furthermore, the network can deliver the UE's QoE capabilities to the core network so that the core network can decide whether to trigger signaling-based QoE measurements for the UE based on the UE capabilities, together with the QoE capabilities of the RAN nodes.

[0065] For both signaling-based and management-based QoE measurements, the network can deliver a QoE measurement configuration to the UE, which can include an application layer QoE measurement configuration container and a requested service type. Based on the configuration, the application layer of the UE can collect and log experience information and send a QoE measurement report to the network. The report can include a QoE measurement report container and a service type. The network can then deliver the UE's QoE report to a collection center.

[0066] In many cellular mobile communication systems, a network can provide users with various services, such as streaming services, voice / video calls, interactive games, AR / VR, etc. Each type of service can be standardized with quality of service (QoS) requirements, such as packet delay amount, packet error rate, latency, etc. However, due to different types of services and different types of users, the service requirements may not be sufficient to provide a good user experience to all users. Therefore, network resources may be designed and optimized to provide users with a better service experience.

[0067] In many systems, a QoE measurement collection mechanism is introduced. The main purpose of QoE measurement is to collect UE experience information for a specific service type at the application layer. The collected information can be transported from the UE to the network or collection center for further analysis. In 5G NR systems, a similar approach will be introduced. However, considering the new QoS framework and characteristics of 5G systems, many aspects may need to be further studied regarding QoE measurement in 5G systems.

[0068] The first aspect may include a given service type (e.g., streaming, VR, etc.) in an NR system, which may have different QoS profiles (e.g., ultra-reliable low latency (URLLC), enhanced mobile broadband (eMBB), vehicular, etc.) for different users. From a network perspective, if only the service type is indicated in the QoE measurement configuration, it may be difficult to optimize the network for a specific user group. In addition, the NR system supports network slicing, which may enable differentiated processing depending on the requirements for the customer. Therefore, with regard to QoE measurement in an NR system, the network slicing should also be considered so that the operator can collect user experience for a given slice.

[0069] In the second aspect, unlike various wireless communication systems, the 5G NR system may have higher power consumption on both the UE and network side. This may be particularly important with the wide deployment of 5G networks. Furthermore, due to the wide use of 5G systems, the number of connected users may be extremely high. Therefore, in cases when the network is overloaded, the network may want to pause and resume ongoing QoE measurements until the network load is reduced. On the other hand, the UE may also want to stop / pause ongoing QoE measurements when the UE faces an overheating problem. These do not support existing QoE measurement mechanisms.

[0070] In the third aspect, in addition to NR independent UEs, 5G systems can also support Multi-Radio Dual Connectivity (MR-DC) operation. In this case, the UE can connect to two nodes, one acting as a master node (MN) and the other acting as a secondary node (SN). The MN and SN may belong to the same RAT (e.g., NR-DC), or they may belong to different RATs (e.g., E-UTRAN New Radio Dual Connectivity (EN-DC), NR-E-UTRA Dual Connectivity (NE-DC), NG-RAN-E-UTRA Dual Connectivity (NGEN-DC)). However, there is no solution for QoE measurement for MR-DC UEs. Therefore, in many cases, QoE information cannot be collected for MR-DC UEs.

[0071] System Overview

[0072] This application relates to techniques that may be implemented for QoE measurement collection. In some embodiments, the MN may be an eNB, an ng-eNB, or a gNB, and the SN may be an eNB, an ng-eNB, or a gNB. In this application, the "RAN node" may also be referred to as the "network" and may be an eNB, an ng-eNB, or a gNB.

[0073] Regarding the QoE measurement configuration, the QoE measurement configuration may include any of QoS information, network slice information, RAT information, Node information, and bearer type information. For an MR-DC UE, the network can determine the bearer type of the requested service based on the RAT / Node information or bearer type received in the QoE configuration.

[0074] For MR-DC UE, the MN may forward the QoE measurement configuration to the SN. For CU-DU split, the CU may inform the DU about the configured QoE measurement, which may include any of the service type, dedicated radio bearer (DRB) ID, and start / stop / pause / resume indication for the QoE measurement.

[0075] For QoE measurement logging, the UE may log bearer type and timestamp information for the requested service, which may be included in the QoE measurement report sent to the network. The network may log bearer type and timestamp information for the requested service, include this information with the UE's QoE measurement report, and send it to the collection node. For MR-DC UEs, the UE may depend on the bearer type to record two separate QoE logs and send it separately to the MN and SN.

[0076] Regarding the QoE measurement report, the QoE report may include QoS information, network slice information, and / or bearer type, and timestamp information. The UE may send a QoE result available indication to the network, and the network may obtain the QoE report via an independent procedure. The SN may forward the UE's QoE report to the MN. The MN may forward the QoE result to the SN, and the CU may forward the QoE result to the DU.

[0077] Regarding QoE capability negotiation, the SN can inform the MN about the possibility of QoE measurement configuration / reporting via the SN. The MN can inform the SN whether the SN is enabled to configure QoE measurements towards the UE. The MN and SN can exchange configured QoE measurement information.

[0078] To consider power saving and network overload, the network can send a QoE pause / resume indication to the UE. The network can send a timer value to the UE, which can be used to provide a validity time for the QoE results collected by the UE. The UE can send an indication to the network to ask the network to pause or stop the QoE measurements. During intra-RAT handover, the source cell can transfer the QoE measurement configuration to the target cell. During inter-RAT or inter-system handover, the UE can locally stop the QoE measurements.

[0079] QoE measurement configuration

[0080] For QoE measurement collection activation, the core network (e.g., Access and Management Function (AMF), MME, OAM) can transmit a QoE measurement configuration to the RAN node (e.g., gNB, ng-eNB, eNB). For each QoE collection mission, besides the requested service type and application configuration container, the QoE measurement configuration can include one or more parameters.

[0081] The parameters may include QoS information, which may include any of a QoS flow identifier (QFI), a PDU session ID, an E-RAB ID, QoS profile information (e.g., 5QI, ARP), a service type ID, and the like.

[0082] The parameters may include network slice information (e.g., a single network slice selection assistance information (S-NSSAI) identifier).

[0083] The parameters may include RAT information. The RAT information may be used to indicate a target RAT for which QoE information is expected to be collected. Values ​​included in the RAT information may include an indicator of the communication system type (e.g., LTE only, NR only, both), a cell list for one RAT or multiple RATs, a tracking area code list for one RAT or multiple RATs, etc.

[0084] The parameters may include node information that may be used to indicate the target node for which QoE information is expected to be collected, and may include values ​​for node information such as values ​​indicating MN only, SN only, or both MN and SN.

[0085] Parameters may include bearer type, which may be used to indicate the target bearer type for which QoE information is expected to be collected. The bearer type may be MCG bearer, SCG bearer, split bearer, MN terminated MCG bearer, MN terminated SCG bearer, MN terminated split bearer, SN terminated MCG bearer, SN terminated SCG bearer, SN terminated split bearer, etc. The expected bearer type may also be a combination of bearer types.

[0086] In some events, a core network node or OAM may activate multiple QoE measurement missions, where each QoE measurement mission may be identified by an identifier, which may be included in the QoE measurement configuration allocated by the core network or OAM and transmitted to the RAN node. In some embodiments, the identifier may be included in the QoE measurement configuration allocated by the RAN node and transmitted to the UE.

[0087] In some embodiments, the core network, OAM, or gNB may dynamically add, modify, or release one or more of the QoE measurement missions.

[0088] In some embodiments, for an MR-DC UE, the QoE measurement configuration sent from the core network or OAM may include multiple application configuration containers, each of which may apply to a specific RAT.

[0089] In response to receiving the QoE measurement configuration from the core network or the OAM, the RAN node may transmit the QoE measurement configuration to the UE via the Uu interface. The QoE measurement configuration may include the above-mentioned QoS information, network slice information, RAT information, and / or node information, bearer type information.

[0090] In some embodiments, if the UE is an MR-DC UE, after the MN receives the QoE measurement configuration from the core network or OAM, the MN can forward the QoE configuration to the SN. The SN can then transmit the QoE measurement configuration to the UE.

[0091] In some embodiments, the MN may forward the QoE configuration to the SN when the MN receives RAT information indicating the SN's RAT or both the MN and the SN, or when the MN receives Node information indicating the SN or both the MN and the SN.

[0092] In some embodiments, for an MR-DC UE, in response to receiving the QoE configuration, the RAN node (i.e., MN and / or SN) may determine a bearer type for the requested service, which may be done based on the information indicated in the QoE configuration. The bearer type may include one of MN terminated MCG bearer, MN terminated SCG bearer, MN terminated split bearer, SN terminated MCG bearer, SN terminated SCG bearer, SN terminated split bearer, etc.

[0093] In some embodiments, for a CU-DU split scenario, once the RAN node configures QoE measurement towards the UE, the CU can provide the DU with various information, such as a requested service type for the QoE measurement, DRB information for the requested service type such as a DRB identifier, start or stop or pause or resume indication for the QoE measurement, etc.

[0094] 1 is an example signaling process 100 for signaling-based QoE measurement. A core network node 124 may send a QoE measurement activation command 102 to a RAN node. The QoE measurement activation command 102 may include a QoE measurement configuration, an IP address of a QoE collection node, etc.

[0095] The RAN node 122 may send the QoE measurement configuration 104 to the UE 120. The UE may perform collection and logging of the QoE results 106. The UE 120 may send the QoE measurement report 108 to the RAN node 122. The RAN node 122 may send the QoE measurement report 110 to the QoE collection node.

[0096] 2 is an example signaling process 200 for management-based QoE measurement. The OAM 224 can send a QoE measurement activation command 202 to the RAN node 222. The QoE measurement activation command 202 can include the QoE measurement configuration, IP address of the QoE collection node, etc.

[0097] The RAN node 222 may perform the UE selection 204. The RAN node 222 may send the QoE measurement configuration 206 to the UE 220. The UE 220 may perform the collection and logging of the QoE results 208. The UE 220 may send the QoE measurement report 210 to the RAN node 222. The RAN node 222 may send the QoE measurement report 212 to the QoE collection node. (Example)

[0098] Example 1

[0099] In a first example, with an NR independent (SA) UE in RRC_CONNECTED mode, the core network (i.e., AMF) may trigger a signaling-based QoE measurement for the UE, and the requested service type may include a streaming service. The AMF may then send a QoE measurement activation command to the gNB, including a QoE measurement configuration container, a service type equal to streaming, a QFI equal to 2, and a 5QI equal to 6.

[0100] In response to receiving the QoE command, the gNB may generate a QoE measurement configuration message and send it to the UE. The measurement configuration may include a QoE measurement configuration container, a service type equal to streaming, a QFI equal to 2, and a 5QI equal to 6. Furthermore, when the gNB establishes a corresponding radio bearer (e.g., a DRB ID equal to 3) for this QoS flow, the gNB-CU may also indicate to the gNB-DU that the UE is configured with QoE measurements for streaming services, and the corresponding DRB ID may be 3. Based on this information, the gNB-DU may prioritize scheduling for this DRB.

[0101] Example 2

[0102] In a second example, the OAM triggers a management-based QoE measurement to a serving cell and the requested service type is a streaming service. The OAM can then send a QoE measurement activation command to the gNB, including a QoE measurement configuration container, a service type equal to streaming, and an S-NSSAI equal to 5.

[0103] In response to receiving the QoE command, the gNB may first select a suitable UE based on the received S-NSSAI. The gNB may then select UE1, which is operating on NRSA mode and the UE's registered S-NSSAI is equal to 5. The gNB may then generate and send a QoE measurement configuration message to the UE, where the measurement configuration includes a QoE measurement configuration container and the service type is equal to streaming.

[0104] Example 3

[0105] In a third example, an EN-DC UE is connected to both an eNB (MN) and a gNB (SN), and the core network (i.e., MME) triggers a signaling-based QoE measurement for the UE, the requested service type is VR, and the core network only wants to collect experience information via the NR RAT. The MME can send a QoE Measurement Activation Command to the MN, including a QoE Measurement Configuration Container, Service Type equal to VR, RAT Information equal to NR, or Node Information equal to SN, or Bearer Type equal to SN terminated SCG bearer.

[0106] In response to receiving the QoE command, the MN may generate a QoE measurement configuration message and send it to the UE, where the measurement configuration includes a QoE measurement configuration container and the service type is equal to VR. Meanwhile, when establishing the service, the network may establish a bearer with a bearer type equal to SN terminated SCG bearer. Thus, downlink and uplink transmissions of the service may pass through the SN radio interface (i.e., NR RAT).

[0107] In some instances, the MN may forward the QoE measurement configuration to the SN, and the SN CU may then inform the SN DU to perform appropriate scheduling optimization.

[0108] Example 4

[0109] In a fourth example, an EN-DC UE is connected to both an eNB (MN) and a gNB (SN), and the core network (i.e., MME) triggers a signaling-based QoE measurement for the UE, the requested service type is VR, and the core network wants to collect only experience information via both the MN's RAT and the SN's RAT. The MME can send a QoE measurement activation command to the MN, which can include a QoE measurement configuration container, service type equal to VR, RAT information equal to both, or Node information equal to both.

[0110] In response to receiving the QoE command, the MN may forward a QoE measurement configuration to the SN, and both the MN and the SN may generate QoE measurement configuration messages and send them to the UE. The measurement configuration may include a QoE measurement configuration container, a service type equal to VR, RAT information equal to both, or Node information equal to both.

[0111] In addition, for both MN and SN, the CU may inform the DU about the QoE measurement information, and then the DU may perform appropriate scheduling optimization.

[0112] Example 5

[0113] In a fifth example, an NR SA UE may be connected to a gNB, and a core network (i.e., AMF) may trigger a first QoE measurement activation procedure, and the requested service type is VR. The AMF may send a QoE measurement activation command to the gNB, which includes a QoE application configuration container, a service type equal to VR, and a QoE mission ID equal to 1.

[0114] In response to receiving the QoE command, the gNB may generate and send a QoE measurement configuration message to the UE. The measurement configuration may include a QoE application configuration container, a service type equal to VR, and a QoE mission ID equal to 1.

[0115] After some time, the AMF may trigger a second measurement activation procedure, where the requested service type is streaming. Further, the AMF may decide to delete the first QoE measurement for the VR service. The AMF may send another QoE measurement activation command to the gNB, including a QoE application configuration container (for the streaming service), a service type equal to streaming, a QoE mission ID equal to 2, and a deletion list with one entry of QoE mission ID equal to 1.

[0116] In response to receiving this QoE command, the gNB may generate and send another QoE Measurement Configuration message to the UE. The measurement configuration may include a QoE Configuration Container (for streaming services), a Service Type equal to Streaming, a QoE Mission ID equal to 2, and a deletion list with one entry for QoE Mission ID equal to 1.

[0117] In response to receiving this QoE measurement configuration, the UE may stop QoE collection for the VR service and start QoE collection for the streaming service.

[0118] QoE Measurement Logging

[0119] From the UE's perspective, in response to receiving the QoE measurement configuration from the RAN node, the UE can log experience information for the indicated service type. In addition, the UE can record bearer type, timestamp information along with the QoE measurement result. The UE can deliver the bearer type and timestamp information to the network in a QoE measurement report.

[0120] The bearer type and timestamp information may represent the bearer type of the collected service until the service is released. In some embodiments, the network may record the bearer type and timestamp information for the requested service. After receiving the QoE measurement report from the UE, the network may deliver the bearer type and timestamp information to the collection node together with the QoE measurement report of the UE.

[0121] In some embodiments, the UE or RAN node may only record bearer type and timestamp information when "RAT Information" is set to "Both" or when "Node Information" is set to "Both".

[0122] In some embodiments, for a given service, if both the MN and the SN configure the UE for QoE measurements at the same time, the UE may log the QoE results when a bearer is established over the MCG air interface and log the QoE results when a bearer is established over the SCG air interface. The UE may deliver separate QoE reports to the MN and the SN.

[0123] 3 is an example signaling process 300 for QoE measurement configuration for an MR-DC UE. A core network node 326 may send a QoE measurement activation command 302 to a master node (MN) 322. The MN 322 may determine whether the MN and / or the SN 324 need to trigger a QoE measurement 304. The MN may send a QoE measurement configuration 306 to the UE 320. The MN 324 may also send a QUE measurement configuration 308 to the SN 322, which may modify the configuration and / or forward the configuration 312 to the UE 320.

[0124] The UE 320 may perform collection and logging of the QoE results 312. The UE 320 may send a QoE measurement report 314 to the MN 322. The UE may send a QoE measurement report 316 to the SN 324.

[0125] Example 1

[0126] In a first embodiment, an EN-DC UE can be connected to both an eNB (MN) and a gNB (SN). The UE can receive a QoE measurement configuration from the MN, which includes a QoE measurement configuration container, service type=VR, RAT information=both, or Node information=both.

[0127] While the UE logs the QoE experience information, the UE may also record the bearer type for this service. Because the network may dynamically change the bearer type, the bearer type may be recorded along with a timestamp. The timestamp may be an absolute time or a relative time.

[0128] For example, a first record may include an MCG bearer with a master key with a time from 03:10:20 to 03:11:05. A second record may include an SCG bearer with a secondary key with a time from 03:11:06 to 03:15:30. A third record may include an SCG bearer with a master key with a time from 03:15:31 to 03:17:48.

[0129] When the UE sends a QoE measurement report to the network, the UE may include the above bearer type information together with a timestamp in the QoE measurement report.

[0130] Example 2

[0131] In a second embodiment, an EN-DC UE is connected to both an eNB (MN) and a gNB (SN). The UE may receive a QoE measurement configuration from the MN, which may include a QoE measurement configuration container, service type=VR, RAT information=both, or Node information=both.

[0132] While the UE logs the QoE experience information, the MN may record the bearer type for this service, and the bearer type is recorded along with a timestamp because the network may dynamically change the bearer type. The timestamp may be an absolute time or a relative time. For example, a first record may include an MCG bearer with a master key with a time from 03:10:20 to 03:11:05. A second record may include an SCG bearer with a secondary key with a time from 03:11:06 to 03:15:30. A third record may include an SCG bearer with a master key with a time from 03:15:31 to 03:17:48.

[0133] After receiving the QoE measurement report sent from the UE, the MN can include the above bearer type information together with a timestamp accompanying the QoE measurement report of the UE and send it to the collection node.

[0134] Example 3

[0135] In a third embodiment, an EN-DC UE is connected to both an eNB (MN) and a gNB (SN). The UE can receive a QoE measurement configuration from both the MN and the SN, which can include a QoE measurement configuration container, service type=VR.

[0136] Because the UE receives QoE measurement configurations from both nodes, the UE can log the QoE experience separately. More specifically, the UE may generate two separate QoE logging reports, where a first log report may include experience information when the VR service is established as an MCG bearer or a split bearer. A second log report may include experience information when the VR service is established as an SCG bearer or a split bearer. The UE may deliver the first log report to the MN via a QoE measurement report sent to the MN and the second one to the SN via a QoE measurement report sent to the SN.

[0137] QoE Measurement Report

[0138] A QoE measurement report may be sent from the UE to the network node, and a QoE measurement report may be sent from the network node to the collection node. The QoE measurement report may include experience information and any other information. Examples of such other information may include QoS information (e.g., QFI, E-RAB ID, QoS profile information (e.g., 5QI, ARP)), network slice information (e.g., S-NSSAI identifier), bearer type of the logged service, etc. The bearer type of the logged service may be transmitted together with the timestamp information. The bearer type may include any of MCG bearer, SCG bearer, split bearer, etc.

[0139] In some embodiments, the content of the QoE measurement report from the UE to the network may be different from the content of the QoE measurement report from the network to the collecting node.

[0140] Regarding the QoE measurement report from the UE to the network, the UE can send the QoE measurement report. This may include the UE sending the QoE measurement report directly to the network when the result is available on the UE side. This may also include the UE first sending an available indication to the network, indicating that the UE has the QoE measurement result available. The network may trigger a result read procedure by sending a request to the UE, and then the UE may deliver the QoE measurement report to the network.

[0141] In some embodiments, for an MR-DC UE, if the QoE measurement configuration is configured by the SN, after receiving the QoE measurement report from the UE, the SN may deliver the report directly to the collection node, or the SN may forward the report to the MN, which may then deliver the QoE report to the collection node.

[0142] In some embodiments, for MR-DC UEs, when the MN receives a QoE measurement report from the UE, the MN can forward the QoE measurement result to the SN side. The forwarding result can be the entire QoE measurement report, a one-bit indication to indicate whether the UE meets the current QoE / latency, or explicit aiding information for scheduling optimization.

[0143] In some embodiments, in the case of CU-DU split, when the network receives a QoE measurement report from the UE, the CU can forward the QoE measurement result to the DU. The forwarding result can be the entire QoE measurement report, a one-bit indication to indicate whether the UE meets the current QoE / latency, or explicit auxiliary information for scheduling optimization.

[0144] 4 is an example signaling process 400 for QoE measurement reporting for an MR-DC UE. The SN 424 may send a QoE measurement configuration 402 to the UE 420. The UE may perform collection and logging of QoE results 404. The UE may send a QoE measurement report 406 to the SN.

[0145] In the first case 408, the SN may not know the IP address of the collection node. In this case, the SN can send a QoE measurement report 410 to the MN 422. The MN can forward the QoE measurement report 412 to the QoE collection node 426.

[0146] In the second case 414 , the SN learns the IP address of the collection node and sends the QoE measurement report 416 to the QoE collection node 426 .

[0147] Example 1

[0148] In a first embodiment, an NR SA UE may be connected to a gNB and the UE may be configured with QoE measurements. If the UE already has available QoE measurement results, the UE may first send a one-bit QoE result available indication to the network. This available indication may be included in the next RRC message or one of the newly defined RRC messages, such as an RRC reconfiguration complete message, a UE assistance information message, an RRC configuration complete message, or an RRC resume complete message.

[0149] After the network node receives the available indication from the UE, the network node can trigger a QoE retrieval procedure when the network load is low. The network node can send an RRC message to the UE to retrieve the stored QoE report. The RRC message can be a UE Information Request message or a newly defined RRC message. In this RRC message, the network can include an indication for QoE acquisition. The UE can then send a QoE measurement report to the network node.

[0150] Example 2

[0151] In a second embodiment, an EN-DC UE is connected to both an eNB (MN) and a gNB (SN), and the core network (i.e., MME) triggers a signaling-based QoE measurement for the UE. In response to receiving a QoE command, the MN may forward a QoE measurement configuration to the SN, and the QoE command may also include an IP address of a collection node. The SN may then generate a QoE measurement configuration message and send it to the UE.

[0152] Since the QoE measurements are configured by the SN, the UE can deliver the QoE measurement report to the SN. After the SN receives the QoE measurement report from the UE, the SN can identify that the SN node is not associated with the collection node (e.g., unknown IP address). The SN can forward the UE's QoE measurement report to the MN, which can forward the report to the collection node.

[0153] QoE Capability Negotiation

[0154] For MR-DC UEs, the SN may inform the MN whether the SN is able to configure QoE measurements for the UE. The SN may indicate that QoE measurements are possible if the following conditions are met:

[0155] The first condition may include the UE supporting QoE measurement and reporting via the SN's RAT, and the second condition may include the SN node supporting QoE measurement and reporting towards the UE.

[0156] In some embodiments, the SN may inform the MN of its QoE measurement capabilities on a per service type level, or per network slice level, per UE level, per node level, etc.

[0157] In some embodiments, the SN QoE measurement capability may be conveyed in an inter-node RRC message (eg, CG-Config) or indicated by a parameter in the Xn / X2 message.

[0158] In addition, in response to an SN addition, SN modification, or SN change, the MN may inform the SN whether the SN is enabled to configure QoE measurements towards the UE.

[0159] In some embodiments, for management-based QoE measurement, when the MN triggers QoE measurement towards the UE, the MN can inform the SN about the continuous QoE measurement configuration and the corresponding service type. Similarly, in the case where the SN triggers QoE measurement towards the UE, the SN can inform the MN about the continuous QoE measurement configuration and the corresponding service type.

[0160] 5 is an example signaling process 500 for SN QoE measurement capability indication. The SN 522 can determine whether the SN and UE support QoE measurement via the SN interface 502. The SN 522 can send an SN configured QoE measurement 504 capability indication to the MN 520.

[0161] 6 is an example signaling process 600 for SN QoE measurement permission indication. The MN 620 can determine whether the SN is enabled to configure QoE measurements 602. The MN 620 can send an indication of SN configured QoE measurements 604 to the SN 622.

[0162] Power saving or network overload considerations

[0163] In case of specific network scenarios (e.g. network overload, UE overheating), the network may trigger a temporary suspension of QoE measurements, which may be resumed once the situation is alleviated.

[0164] A network node may send a pause indication to the UE, informing the UE that the QoE measurements configured thereon have been paused. After receiving the indication, the UE may not be enabled to deliver QoE measurement reports to the network. From the UE's perspective, the UE may continue logging QoE experience information at the application layer or pause the logging behavior. In response to receiving a resume indication from the network, the UE may resume the logging behavior, if paused, and deliver QoE measurement reports to the network.

[0165] In some embodiments, the network may indicate a timer value to the UE together with the pause indication. After receiving the timer value, the UE may start the timer immediately or when the UE stops logging (e.g., the logging memory is full and the requested service is released). If the UE does not receive a QoE measurement resume indication from the network before the timer expires, the UE may locally delete the logged QoE measurement results.

[0166] In some embodiments, the network node may trigger the suspension behavior by receiving an indication from the UE. The indication may be included in the UE assistance information. The UE may send this indication when the UE is overheating or when the UE wants to enable power savings.

[0167] In some embodiments, the UE may send an indication to the network to ask the network to stop QoE measurements. The MN may need to forward this indication to the SN or the SN to the MN.

[0168] In some embodiments, the UE may include sending an indication to the network to inform the network that the QoE measurements have been stopped, and optionally stopping the measurements.

[0169] In some embodiments, during an intra-RAT handover, the source cell may inform the target cell that the UE is configured with QoE measurements and whether the QoE measurements are suspended. In addition, the source cell may also forward the QoE measurement configuration to the target cell.

[0170] In some embodiments, upon inter-RAT or inter-system handover, the UE may locally stop configured QoE measurements and remove the logged results.

[0171] Exemplary Methods for QoE Measurement Collection

[0172] 7 is a block diagram of an example method for quality of experience (QoE) measurement collection 700. The method may include receiving a first message from a network node that includes a configuration for collecting quality of experience information (block 702).

[0173] The method may also include transmitting a second message to the network node including the set of quality of experience information collected by the terminal and transmitted in accordance with the configuration for collecting quality of experience information received in the first message (block 704).

[0174] In some embodiments, the method includes collecting, by the terminal, a set of quality of experience information.

[0175] In some embodiments, either the configuration for collecting quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes quality of service (QoS) information.

[0176] In some embodiments, the QoS information includes any of a QoS flow identifier (QFI), a protocol data unit (PDU) session identifier, an Evolved Universal Terrestrial Access Network (E-UTRAN) Radio Access Bearer Identifier (E-RAB ID), and QoS profile information.

[0177] In some embodiments, either the configuration for collecting quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes a network slice identifier.

[0178] In some embodiments, either the configuration for collecting quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes information identifying a target radio access technology (RAT) for collecting the set of quality of experience information therein.

[0179] In some embodiments, the information identifying the target RAT includes either a cell identification list of at least one RAT or a tracking area code list of at least one RAT or RAT type.

[0180] In some embodiments, either the configuration for collecting quality of experience information included in the first message or the collected set of quality of experience information included in the second message includes node information indicating a target node for collecting the set of quality of experience information therein.

[0181] In some embodiments, either the configuration for collecting quality of experience information included in the first message and the collected set of quality of experience information included in the second message includes a bearer type indicator indicating a target bearer type for collecting the set of quality of experience information.

[0182] In some embodiments, the bearer type indicator may indicate any of a master cell group (MCG) bearer, a secondary cell group (SCG) bearer, a split bearer, a master node (MN) terminated MCG bearer, a MN terminated SCG bearer, a MN terminated split bearer, a secondary node (SN) terminated MCG bearer, a SN terminated SCG bearer, or a SN terminated split bearer.

[0183] In some embodiments, the configuration for collecting quality of experience information includes several application configuration containers, each of which applies to a specific RAT.

[0184] In some embodiments, collecting the set of quality of experience information includes logging bearer type and timestamp information of the services collected according to a configuration for collecting the quality of experience information.

[0185] In some embodiments, the method includes receiving, by a terminal, a plurality of configurations for measuring quality of experience information from a master node (MN) and a secondary node (SN), respectively; measuring, by the terminal, a first set of quality of experience information when a bearer is established over a master cell group (MCG) radio interface and a second set of quality of experience information when the bearer is established over a secondary cell group (SCG) radio interface; and transmitting, by the terminal, a first report to the MN including the first set of quality of experience information and a second report to the SN including the second set of quality of experience information.

[0186] In some embodiments, the second message is transmitted in response to the terminal measuring the set of quality of experience information.

[0187] In some embodiments, the method includes transmitting, by the terminal, a quality of experience information indication to a network node indicating that the terminal has collected a set of quality of experience information, and receiving, by the terminal, a quality of experience information response from the network node, wherein the second message is transmitted by the terminal in response to receiving the quality of experience information response from the network node.

[0188] In some embodiments, the method includes transmitting, by the terminal, to the network node a one-bit quality of experience information results available indication indicating that the terminal has measured a set of quality of experience information.

[0189] In some embodiments, the 1-bit quality of experience information result available indication is transmitted to the network node via any of a Radio Resource Control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC configuration complete message, and an RRC resume complete message.

[0190] In some embodiments, the method includes receiving, by the terminal, an RRC message from a network node when network load falls below a threshold level, the RRC message including a request for a set of quality of experience information, and in response to receiving the RRC message from the network node, the terminal transmitting a second message to the network node.

[0191] In some embodiments, the method includes receiving, by the terminal, a pause indication from the network node, the pause indication including an indication that the terminal pauses transmission of the second message and / or stops measuring the set of quality of experience information.

[0192] In some embodiments, the method includes receiving, by the terminal, a resume indication from the network node, wherein the second message is transmitted by the terminal in response to receiving the resume indication from the network node.

[0193] In some embodiments, the method includes starting, by the terminal, in response to either receiving a pause indication or completing collection of the set of quality of experience information, a timer with a duration indicated in the pause indication, and upon expiration of the timer, releasing, by the terminal, the set of quality of experience information collected by the terminal.

[0194] In some embodiments, the method includes determining, by the terminal, that a power consumption level of the terminal exceeds a threshold power level; and in response to determining that the power consumption level of the terminal exceeds the threshold power level, transmitting, by the terminal to a network node, a power save message initiating a power save operation, wherein the pause indication is received by the terminal in response to transmitting the power save message.

[0195] In another embodiment, a method for wireless communication includes transmitting, by a network node, a first message to a terminal, the first message including a configuration for collecting quality of experience information. The method may also include receiving, by the network node, from the terminal, a second message including a set of quality of experience information collected by the terminal, the second message being transmitted in accordance with the configuration for collecting quality of experience information received in the first message.

[0196] In some embodiments, the method includes receiving, by the network node, a configuration from a core network node or an Operations and Maintenance (OAM) node for collecting quality of experience information.

[0197] In some embodiments, the method includes forwarding, by the network node, the second message to the QoE collection node.

[0198] In some embodiments, the core network node includes any of a core Access and Mobility Management Function (AMF) node and a Mobility Management Entity (MME) node.

[0199] In some embodiments, the method includes forwarding, by the network node, a configuration for collecting quality of experience information to a secondary network node, the secondary network node configured to modify and / or transmit the configuration for collecting the quality of experience information to the terminal.

[0200] In some embodiments, the network node includes a central unit (CU), and the network node transmits a configuration for collecting quality of experience information to the distributed unit (CU), the configuration for collecting quality of experience information including any of a requested service type for the set of quality of experience information, dedicated radio bearer (DRB) information for the requested service type, and an indication to start, stop, or pause measurement of the set of quality of experience information by the terminal.

[0201] In some embodiments, the method includes receiving, by the network node, from a secondary network node, a configuration indication of whether the network node is capable of configuring the terminal for collecting quality of experience information.

[0202] In some embodiments, the configuration indication is received by the network node in response to the secondary network node determining that the terminal supports quality of experience information measurement and reporting via a Radio Access Technology (RAT) associated with the secondary network node.

[0203] In some embodiments, the configuration indication is received by the network node in response to a secondary network node supporting and reporting quality of experience information measurement towards the terminal.

[0204] In some embodiments, any of the configuration for collecting quality of experience information included in the first message, the measured set of quality of experience information included in the second message, and the configuration for collecting quality of experience information from a core network node include any of quality of service (QoS) information, a network slice selection identifier, information identifying a target radio access technology (RAT) within which to measure the set of quality of experience information, node information indicating a target node within which to measure the set of quality of experience information, or a bearer type indicator indicating a target bearer type within which to measure the set of quality of experience information.

[0205] In some embodiments, the method includes transmitting, by the network node, to the terminal one of a plurality of configurations for measuring quality of experience information; receiving, by the network node, a first report from the terminal when the bearer is established over a master cell group (MCG) radio interface, the first report including a first set of quality of experience information measured by the terminal; and / or receiving, by the network node, a second report from the terminal when the bearer is established over a secondary cell group (SCG) radio interface, the second report including a second set of quality of experience information measured by the terminal.

[0206] In some embodiments, the method includes receiving, by the network node, a quality of experience information indication from the terminal indicating that the terminal has measured a set of quality of experience information, and transmitting, by the network node, a quality of experience information response to the terminal, wherein the second message is transmitted by the terminal in response to receiving the quality of experience information response from the network node.

[0207] In some embodiments, the method includes receiving, by the network node, from the terminal a one-bit quality of experience information results available indication indicating that the terminal has measured a set of quality of experience information.

[0208] In some embodiments, the 1-bit quality of experience information results in an availability indication received by the network node via any of a Radio Resource Control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC configuration complete message, and an RRC resume complete message.

[0209] In some embodiments, the method includes transmitting, by the network node, an RRC message to the terminal when network load falls below a threshold level, the RRC message including a request for a set of quality of experience information, and the terminal transmitting a second message to the network node in response to receiving the RRC message from the network node.

[0210] In some embodiments, the method includes transmitting, by the network node, a pause indication to the terminal, the pause indication including an indication that the terminal pauses transmission of the second message and / or stops measuring the set of quality of experience information.

[0211] In some embodiments, the method includes transmitting, by the network node, a resume indication to the terminal, wherein the second message is transmitted by the terminal in response to receiving the resume indication from the network node.

[0212] In some embodiments, the method includes receiving, by the network node, a power save message from the terminal in response to the terminal determining that a power consumption level of the terminal exceeds a threshold power level, the power save message initiating a power save operation, and a pause indication being received by the terminal in response to transmission of the power save message.

[0213] Exemplary Wireless System

[0214] 8 illustrates an example of a wireless communication system in which techniques according to one or more embodiments of the present technology may be applied. The wireless communication system 800 may include one or more base stations (BSs) 805a, 805b, one or more wireless devices 810a, 810b, 810c, 810d, and a core network 825. The base stations 805a, 805b may provide wireless services to the wireless devices 810a, 810b, 810c, and 810d in one or more wireless sectors. In some implementations, the base stations 805a, 805b include directional antennas for generating two or more directional beams to provide wireless coverage in different sectors.

[0215] The core network 825 can communicate with one or more base stations 805a, 805b. The core network 825 provides connectivity with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases for storing information related to the subscribed wireless devices 810a, 810b, 810c, and 810d. The first base station 805a can provide wireless services based on a first wireless access technology, while the second base station 805b can provide wireless services based on a second wireless access technology. The base stations 805a and 805b may be co-configured or separately located in the field according to a deployment scenario. The wireless devices 810a, 810b, 810c, and 810d can support multiple different wireless access technologies.

[0216] In some implementations, a wireless communication system can include multiple networks that use different wireless technologies. A dual-mode or multi-mode wireless device includes two or more wireless technologies that can be used to connect to different wireless networks.

[0217] FIG. 9 is a block diagram representation of a portion of a hardware platform. A hardware platform 905, such as a network device or base station or wireless device (or UE), can include processor electronics 910, such as a microprocessor, that implements one or more of the techniques presented herein. The hardware platform 905 includes transceiver electronics 915 and can transmit and / or receive wired or wireless signals via one or more communication interfaces, such as an antenna 920 or a wired interface. The hardware platform 905 can implement other communication interfaces with defined protocols for transmitting and receiving data. The hardware platform 905 can include one or more memories (not explicitly shown) configured to store information, such as data and / or instructions. In some implementations, the processor electronics 910 can include at least a portion of the transceiver electronics 915. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the hardware platform 905.

[0218] conclusion

[0219] From the foregoing, it should be understood that, although specific embodiments of the disclosed technology have been described herein for purposes of illustration, various modifications may be made without departing from the scope of the invention. Accordingly, the disclosed technology is not limited, except as by the appended claims.

[0220] The disclosed embodiments, modules, and functional operations described herein can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed herein and their structural equivalents, or in a combination of one or more of them. The disclosed embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by or to control the operation of a data processing apparatus. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition that produces a machine-readable propagated signal, or a combination of one or more of them. The term "data processing apparatus" encompasses all apparatus, devices, and machines for processing data, including, by way of example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the apparatus can include code that creates an execution environment for the computer program, such as code that constitutes a processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. The propagated signal may be an artificially generated signal, for example a machine-generated electrical, optical, or electromagnetic signal, generated so as to encode information for transmission to a suitable receiver device.

[0221] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored within a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), within a single file dedicated to the program, or within multiple collaborative files (e.g., files that store one or more modules, subprograms, or portions of code). A computer program can be deployed to run on one computer, or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0222] The processes and logic flows described herein may be implemented by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be implemented by, and apparatus may also be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0223] Processors suitable for executing computer programs include, by way of example, both general-purpose and special-purpose microprocessors, and any one or more processors of any kind of digital computer. In general, a processor will receive instructions and data from a read-only memory or a random access memory, or both. The essential elements of a computer are a processor for carrying out instructions, and one or more memory devices for storing instructions and data. In general, a computer will also include, or be operatively coupled to receive data from, or transfer data to, one or more mass storage devices, such as magnetic, magneto-optical, or optical disks, for storing data. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, by way of example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices, magnetic disks, such as internal hard disks or removable disks, magneto-optical disks, and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0224] Although this patent document contains many details, these should not be interpreted as limitations on the scope of any invention or what may be claimed, but rather as descriptions of features that may be specific to certain embodiments of a particular invention. Certain features described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in a combination and may even be initially claimed as such, one or more features from a claimed combination may in some cases be deleted from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination.

[0225] Similarly, although operations are depicted in the figures in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown, or in a sequential order, or that all of the illustrated operations be performed, to achieve desirable results. Further, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

[0226] Only some implementations and examples have been described; other implementations, enhancements, and variations can be made based on what is described and illustrated in this patent document.

Claims

1. 1. A method for wireless communication, the method comprising: A terminal configured to support a dual connectivity (DC) operation with a first network node and a second network node receives a first message from the first network node, the first message including a configuration for collecting Quality of Experience (QoE) information, the configuration including a parameter indicating a target node from which QoE information is expected to be collected, the target node being the first network node or the second network node; transmitting, by the terminal, to the target node, a second message including a set of QoE information collected by the terminal according to a configuration for collecting the QoE information received in the first message; Including, The method, wherein the configuration for collecting the QoE information included in the first message includes a network slice identifier.

2. The method of claim 1 , further comprising: the terminal measuring the set of QoE information.

3. The method of claim 1 , wherein the configuration for collecting the QoE information included in the first message includes a bearer type indicator indicating a target bearer type for collecting the set of QoE information.

4. 4. The method of claim 3, wherein the bearer type indicator indicates a master cell group (MCG) bearer, a secondary cell group (SCG) bearer, a split bearer, a master node (MN) terminated MCG bearer, a MN terminated SCG bearer, a MN terminated split bearer, a secondary node (SN) terminated MCG bearer, a SN terminated SCG bearer, or a SN terminated split bearer.

5. The method of claim 1 , wherein the configuration for collecting the QoE information includes a number of application configuration containers, each application configuration container applying to a specific RAT.

6. The method of claim 2 , wherein collecting the set of QoE information includes logging bearer type and timestamp information of a service according to a configuration for collecting the QoE information.

7. Either the first network node comprises a Master Node (MN) and the second network node comprises a Secondary Node (SN), or the first network node comprises the SN and the second network node comprises the MN; The method comprises: said terminal receiving from said MN and said SN, respectively, a number of configurations for measuring QoE information; The terminal measures a first set of QoE information when a bearer is established via a master cell group (MCG) radio interface, and the terminal measures a second set of QoE information when the bearer is established via a secondary cell group (SCG) radio interface; the terminal transmitting a first report to the MN, the first report including the first set of QoE information, and transmitting a second report to the SN, the second report including the second set of QoE information; The method of claim 1 further comprising:

8. The method of claim 1 , wherein the second message is transmitted in response to the terminal measuring the set of QoE information.

9. The method comprises: The terminal transmits a QoE information indication to the target node, the QoE information indication indicating that the terminal has collected the set of QoE information; the terminal receiving a QoE information response from the target node, the second message being transmitted by the terminal in response to receiving the QoE information response from the target node; The method of claim 1 further comprising:

10. 1. A method for wireless communication, comprising: The method includes: a first network node transmitting a first message to a terminal, the first message including a configuration for collecting Quality of Experience (QoE) information; the terminal is configured to support dual connectivity (DC) operation with the first network node and the second network node; the configuration includes a parameter indicating a target node for which QoE information is expected to be collected, the target node being the first network node or the second network node; a second message from the terminal including a set of QoE information collected by the terminal; The second message is transmitted to the terminal according to the configuration for collecting the QoE information received in the first message.

11. 11. The method of claim 10, further comprising the first network node receiving from the second network node a configuration indication of whether the second network node is capable of configuring the terminal with the configuration for collecting the QoE information.

12. The method of claim 10, wherein either the first network node includes a master node (MN) and the second network node includes a secondary node (SN), or the first network node includes the SN and the second network node includes the MN.

13. The method of claim 10, further comprising the first network node informing the second network node whether the terminal is configured to have a management-based QoE measurement configuration.

14. The method of claim 10, comprising the first network node receiving from the terminal the second message transmitted in accordance with the configuration for collecting the QoE information received in the first message, when the first network node is the target node.

15. The method of claim 10, wherein the set of QoE information collected by the terminal is forwarded to the first network node.

Images