Collection and reporting of quality of experience information

Abstract

This application relates to methods, systems, and devices related to digital wireless communications, and more specifically to techniques related to quality of experience (QoE) measurement collection. In one example aspect, a method for wireless communication 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 sending, by the terminal, a second message to the network node, the second message including a set of quality of experience information collected by the terminal and sent in accordance with the configuration for collecting quality of experience information received in the first message.

Description

TECHNICAL FIELD

[0001] This patent document generally relates to wireless communication. BACKGROUND

[0002] Mobile communication technology is pushing the world towards an increasingly connected and networked society. The rapid growth of mobile communications and advances in technology lead to greater demands for capacity and connectivity. Other aspects such as energy consumption, device cost, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios. Various technologies are being discussed, including new approaches for providing higher quality services. SUMMARY

[0003] This document discloses methods, systems, and devices related to digital wireless communication, and more specifically, techniques related 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 comprising a configuration for collecting quality of experience information. The method further includes transmitting, by the terminal, a second message to the network node, the second message comprising 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 comprising a configuration for collecting quality of experience information. The method further includes receiving, by the network node, a second message from the terminal, the second message comprising 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.

[0006] In another example aspect, a wireless communication apparatus comprising a processor is disclosed. The processor is configured to implement the methods described herein.

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

[0008] Some embodiments can preferably implement the following solutions written in the format of clauses.

[0009] 1. A solution for wireless communication, comprising: receiving, by a terminal, a first message from a network node, the first message comprising a configuration for collecting quality of experience information; transmitting, by the terminal, a second message to the network node, the second message comprising 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 according to clause 1, further comprising collecting, by the terminal, the set of quality of experience information.

[0011] 3. The solution according to clause 1, wherein any of the following comprises quality of service (QoS) information: 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.

[0012] 4. The solution according to clause 3, wherein the QoS information comprises any of the following: a QoS flow identifier (QFI), a PDU session identifier, an evolved universal terrestrial radio access bearer identifier (E-RAB ID), and QoS configuration information.

[0013] 5. The solution according to clause 1, wherein any of the following comprises a network slice identifier: 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.

[0014] 6. The solution according to clause 1, wherein any of the following comprises information identifying a target radio access technology (RAT) for collecting the set of quality of experience information: 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.

[0015] 7. The solution according to clause 6, wherein the information identifying the target RAT comprises any of the following: a list of cell identities of at least one RAT, or a list of tracking area codes of at least one RAT or RAT type.

[0016] 8. The solution according to clause 1, wherein any of the following comprises node information indicating a target network node for collecting the set of quality of experience information: 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.

[0017] 9. The solution according to clause 1, wherein any of the following comprises a bearer type indicator indicating a target bearer for collecting the set of quality of experience information: 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.

[0018] 10. The solution according to clause 9, wherein the bearer type indicator can indicate any of the following: master cell group bearer (MCG bearer), secondary cell group bearer (SCG bearer), split bearer, master node (MN)-terminated MCG bearer, MN-terminated SCG bearer, MN-terminated split bearer, secondary node (SN)-terminated MCG bearer, SN-terminated SCG bearer, or SN-terminated split bearer.

[0019] 11. The solution according to clause 1, wherein the configuration for collecting quality of experience information comprises a plurality of application configuration containers, wherein each application configuration container is applied to a particular RAT.

[0020] 12. The solution according to clause 2, wherein collecting the set of quality of experience information comprises recording the collected bearer type and timestamp information for the service according to the configuration for collecting quality of experience information.

[0021] 13. The solution according to clause 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 master cell group (MCG) radio interface bearer is established and a second set of quality of experience information when a secondary cell group (SCG) radio interface bearer is established; and sending, by the terminal, a first report comprising the first set of quality of experience information to the MN and a second report comprising the second set of quality of experience information to the SN.

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

[0023] 15. The solution according to clause 1, further comprising: sending, by the terminal, a quality of experience information indication to the network node indicating that the terminal has collected the 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 sent by the terminal in response to receiving the quality of experience information response from the network node.

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

[0025] 17. The solution according to clause 16, wherein the 1-bit quality of experience information result available indication is sent to the network node via any of: a radio resource control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC setup complete message, and an RRC resume complete message.

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

[0027] 19. The solution according to clause 1, further comprising: receiving, by the terminal from the network node, a suspension indication, the suspension indication including an indication for the terminal to suspend transmission of the second message and / or to stop measuring the set of quality of experience information.

[0028] 20. The solution according to clause 20, further comprising: receiving, by the terminal from the network node, a resume indication, wherein the second message is sent by the terminal in response to receiving the resume indication from the network node.

[0029] 21. The solution according to clause 19, further comprising: initiating, by the terminal, a timer after receiving the suspension indication or after collection of the set of quality of experience information is complete, the timer representing a duration indicated in the suspension indication; and releasing, by the terminal, the set of quality of experience information collected by the terminal upon expiration of the timer.

[0030] 22. The solution according to any of clauses 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, sending, by the terminal to the network node, a power saving request message to initiate a power saving operation, and receiving, by the terminal, the suspension indication transmitted by the network node in response to the power saving request message.

[0031] 23. A solution for wireless communication, comprising: sending, by a network node to a terminal, a first message, the first message including a configuration for collecting quality of experience information; and receiving, by the network node from the terminal, a second message, the 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.

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

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

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

[0035] 27. The solution of clause 23, further comprising forwarding, by the network node, the configuration for collecting quality of experience information to a secondary network node, wherein the secondary network node is configured to be able to modify the configuration for collecting quality of experience information, and / or to send the configuration for collecting quality of experience information to the terminal.

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

[0037] 29. The solution of clause 23, further comprising receiving, by the network node, a configuration indication from a secondary network node, the configuration indication indicating whether the secondary network node is able to configure the terminal with the configuration for collecting quality of experience information.

[0038] 30. The solution of clause 29, wherein the network node receives the configuration indication when the secondary network node determines that the terminal supports quality of experience information measurement and reporting over a radio access technology (RAT) associated with the secondary network node.

[0039] 31. The solution of clause 29, wherein the network node receives the configuration indication when the secondary network node supports quality of experience information measurement and reporting for the terminal.

[0040] 32. The solution according to any of Clauses 23 and 24, wherein any of the configuration for collecting quality of experience information included in the first message and the set of measured quality of experience information and the configuration for collecting quality of experience information from the core network node included in the second message comprises any of the following: 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 network node for measuring the set of quality of experience information, and a bearer type indicator indicating a target bearer for measuring the set of quality of experience information.

[0041] 33. The solution according to Clause 23, further comprising: sending, 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 comprising a first set of quality of experience information measured by the terminal when a bearer over a master cell group (MCG) radio interface is established; and receiving, by the network node from the terminal, a second report comprising a second set of quality of experience information measured by the terminal when a bearer over a secondary cell group (SCG) radio interface is established.

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

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

[0044] 36. The solution according to Clause 35, wherein the 1-bit quality of experience information result available indication is received by the network node via any of the following: a radio resource control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC setup complete message, and an RRC resume complete message.

[0045] 37. The solution according to any of Clauses 35 and 36, further comprising: sending, by the network node to the terminal, an RRC message including a request for the set of quality of experience information when a network load is below a threshold level, wherein the second message is sent by the terminal to the network node in response to receiving the RRC message from the network node.

[0046] 38. The solution according to Clause 23, further comprising: sending, by the network node to the terminal, a suspension indication including an indication for the terminal to suspend transmission of the second message and / or to stop measuring the set of quality of experience information.

[0047] 39. The solution according to clause 38, further comprising 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.

[0048] 40. The solution according to any of clauses 23 and 39, further comprising receiving, by the network node from the terminal, a power saving request message to initiate a power saving operation in response to the terminal determining that the power consumption level of the terminal exceeds the threshold power level, wherein the suspend indication is received by the terminal in response to transmission of the power saving request message.

[0049] 41. An apparatus for wireless communication, comprising a processor configured to perform a solution according to any of clauses 1 to 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 a solution according to any of clauses 1 to 40.

[0051] The 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 claims. BRIEF DESCRIPTION OF DRAWINGS

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

[0053] Figure 2 is an example signaling procedure for management-based QoE measurement.

[0054] Figure 3 is an example signaling procedure for QoE measurement configuration for MR-DC UE.

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

[0056] Figure 5 is an example signaling procedure for SN QoE measurement capability indication.

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

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

[0059] Figure 8An example of a wireless communication system is shown in which techniques according to one or more embodiments of the technology can be applied.

[0060] Figure 9 Block diagram representation of a portion of a hardware platform. DETAILED DESCRIPTION

[0061] The development of a new generation of wireless communications, 5G New Radio (NR) communications, is part of a continuous evolution of mobile broadband to meet the increasing demand for network capacity. NR will provide greater throughput to allow more users to be connected at the same time. 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 such scenarios can include signaling-based QoE measurement and management-based QoE measurement.

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

[0064] Further, a UE can inform the network whether it supports QoE measurement collection. More specifically, the UE can indicate separate capabilities for streaming service and multimedia telephony service for IP multimedia subsystem (IMS) (MTSI) service. Further, the network can deliver the QoE capability of the UE to the core network, so that the core network can rely on the UE capability as well as the QoE capability of the RAN node and decide whether to trigger signaling-based QoE measurement for the UE.

[0065] For both signaling-based QoE measurement and management-based QoE measurement, the network can send a QoE measurement configuration to the UE. This can include an application layer QoE measurement configuration container and a requested service type. The application layer of the UE can collect and record experience information based on the configuration, 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 QoE report of the UE to a collection center.

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

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

[0068] The first aspect can include that in the NR system, for a given service type (e.g., streaming, VR, etc.), it can have different QoS configuration information (e.g., ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), vehicles, etc.) for different users. From the perspective of the network, if only the service type is indicated in the QoE measurement configuration, it can be difficult to optimize the network for a specific user group. In addition, the NR system can support network slicing, which allows for differentiated treatment according to customer needs. Therefore, for QoE measurement in the NR system, 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 has a high power consumption at both the UE side and the network side. This can become particularly important in the widespread deployment of the 5G network. In addition, due to the widespread use of the 5G system, the number of connected users can be very high. Therefore, in the case of network overload, the network can want to suspend ongoing QoE measurement and resume until the network load decreases. On the other hand, when the UE encounters a heat problem, the UE can also want to stop / suspend ongoing QoE measurement. These are not supported in the existing QoE measurement mechanism.

[0070] In a third aspect, in addition to NR standalone UEs, 5G systems can also support multi-radio dual connectivity (MR-DC) operation. In this case, a UE can be connected to two nodes, one of which acts as a master node (MN) and the other acts as a secondary node (SN). The MN and SN can belong to the same RAT (e.g., NR-DC), or they can belong to different RATs (e.g., EN-DC, NE-DC, NGEN-DC). However, there is no solution for QoE measurement for MR-DC UEs. Thus, in many cases, QoE information cannot be collected for MR-DC UEs.

[0071] System overview

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

[0073] For QoE measurement configuration, the QoE measurement configuration can include any of the following: QoS information, network slice information, RAT information, node information, and bearer type information. For MR-DC UEs, 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 UEs, the MN can forward the QoE measurement configuration to the SN. For CU-DU split, the CU can inform the DU about the configured QoE measurement, which can include any of the following: service type, dedicated radio bearer (DRB) ID, and start / stop / pause / resume indication for QoE measurement.

[0075] For QoE measurement logging, the UE can log the bearer type of the requested service and timestamp information, which can be included in the QoE measurement report sent to the network. The network can log the bearer type of the requested service and timestamp information and include it with the UE’s QoE measurement report and send it to the collection node. For MR-DC UEs, the UE can log two separate QoE logs according to the bearer type and send them to the MN and SN, respectively.

[0076] For QoE measurement reporting, a QoE report can include QoS information, network slice information, and / or bearer type and timestamp information. A UE can send a QoE result available indication to the network, and the network can obtain the QoE report via a separate procedure. The SN can forward the QoE report of the UE to the MN. The MN can forward the QoE result to the SN, and the CU can forward the QoE result to the DU.

[0077] For QoE capability negotiation, the SN can inform the MN about the capability for QoE measurement configuration / reporting through the SN. The MN can inform the SN whether the SN is allowed to configure QoE measurement for the UE. The MN and the SN can exchange the configured QoE measurement information.

[0078] For QoE measurement reporting, a QoE report can include QoS information, network slice information, and / or bearer type and timestamp information. A UE can send a QoE result available indication to the network, and the network can obtain the QoE report via a separate procedure. The SN can forward the QoE report of the UE to the MN. The MN can forward the QoE result to the SN, and the CU can forward the QoE result to the DU.

[0079] QoE measurement configuration

[0080] For QoE measurement collection activation, a core network (e.g., access and mobility function (AMF), MME, OAM) can send a QoE measurement configuration to a RAN node (e.g., gNB, ng-eNB, eNB). For each QoE collection task, the QoE measurement configuration can include one or more parameters in addition to a requested service type and an application configuration container.

[0081] A parameter can include QoS information. The QoS information can include any of the following: a QoS flow identifier (QFI), a PDU session ID, an E-RAB ID, QoS configuration information (e.g., 5QI, ARP), a service type ID, and / or the like.

[0082] A parameter can include network slice information (e.g., a single network slice selection assistance information (S-NSSAI) identifier.

[0083] A parameter can include RAT information. The RAT information can be used to indicate a target RAT for which QoE information is expected to be collected. Values included in the RAT information can include an indicator of a type of communication system (e.g., LTE only, NR only, both LTE and NR), a list of cells for one RAT or multiple RATs, a list of tracking area codes for one RAT or multiple RATs, and / or the like.

[0084] The parameter can include node information, which can be used to indicate a target network node for which QoE information is intended to be collected. The value of the node information can include a value indicating MN only, SN only, both MN and SN, etc.

[0085] The parameter can include a bearer type, which can be used to indicate a target bearer type for which QoE information is intended to be collected. The bearer type can be a MCG bearer, a SCG bearer, a split bearer, a 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. The intended bearer type can also be a combination of bearer types.

[0086] In some cases, the core network node or OAM can activate multiple QoE measurement tasks. In this case, each QoE measurement task can be identified by an identifier, which can be allocated by the core network or OAM and included in the QoE measurement configuration sent to the RAN node. In some embodiments, the identifier can be allocated by the RAN node and included in the QoE measurement configuration sent to the UE.

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

[0088] In some embodiments, for a MR-DC UE, the QoE measurement configuration sent from the core network or OAM can include multiple application configuration containers, where each container can be applied to a specific RAT.

[0089] After receiving the QoE measurement configuration from the core network or OAM, the RAN node can send the QoE measurement configuration to the UE via the Uu interface. The QoE measurement configuration can include the QoS information, network slice information, RAT information, and / or node information, bearer type information described above.

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

[0091] In some embodiments, when the MN receives RAT information indicating the RAT of the SN or both the MN and the SN, or when the MN receives node information indicating the SN or both the MN and the SN, the MN can forward the QoE configuration to the SN.

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

[0093] In some embodiments, for a CU-DU split scenario, when the RAN node configures the QoE measurement for the UE, the CU can provide various information to the DU. Such information can include the requested service type for the QoE measurement, the DRB information (such as the DRB identifier) of the requested service type, the start or stop or pause or resume indication for the QoE measurement, and the like.

[0094] Figure 1 is an example signaling procedure 100 for signaling-based QoE measurement. The core network node 124 can send a QoE measurement activation command 102 to the RAN node. The QoE measurement activation command 102 can include the QoE measurement configuration, the IP address of the QoE collection node, and the like.

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

[0096] Figure 2is an example signaling procedure 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 a QoE measurement configuration, an IP address of a QoE collection node, etc.

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

[0098] Example 1

[0099] In a first example, for an NR standalone (SA) UE in RRC CONNECTED mode, the core network (i.e., AMF) can trigger a signaling-based QoE measurement for the UE, where the requested service type can include a streaming media service. The AMF can then send a QoE measurement activation command to the gNB, which includes a QoE measurement configuration container, a service type equal to streaming media, a QFI equal to 2, and a 5QI equal to 6.

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

[0101] Example 2

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

[0103] Upon receiving the QoE command, the gNB can first select a suitable UE based on the received S-NSSAI. Then the gNB can select UE1 operating in NR SA mode and UE1's S-NSSAI registered is equal to 5. Then the gNB can generate and send a QoE measurement configuration message to the UE, the measurement configuration includes a QoE measurement configuration container and a service type equal to streaming media.

[0104] Example 3

[0105] In a third example, an EN-DC UE is connected to both eNB (MN) and gNB (SN), the core network (i.e., MME) triggers a signaling-based QoE measurement for this UE, the requested service type is VR, and the core network only wants to collect experience information through NR RAT. The MME can send a QoE measurement activation command to the MN, the QoE measurement activation command can include a QoE measurement configuration container, a service type equal to VR, RAT information equal to NR, or node information equal to SN, or a bearer type equal to SN terminated SCG bearer.

[0106] Upon receiving the QoE command, the MN can generate and send a QoE measurement configuration message to the UE, the measurement configuration includes a QoE measurement configuration container and a service type equal to VR. Meanwhile, when establishing this service, the network can establish a bearer with a bearer type equal to SN terminated SCG bearer. Accordingly, the downlink and uplink transmission of this service can be through the SN radio interface (i.e., NR RAT).

[0107] In some cases, the MN can forward the QoE measurement configuration to the SN, and then the SN CU can inform the SN DU to make appropriate scheduling optimization.

[0108] Example 4

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

[0110] Upon receiving the QoE command, the MN can forward the QoE measurement configuration to the SN, and both the MN and the SN generate and send a QoE measurement configuration message to the UE. The measurement configuration can include a QoE measurement configuration container, a service type equal to VR, and RAT information equal to both or node information equal to both.

[0111] In addition, for both MN and SN, its CU can inform the QoE measurement information to its DU, which then can do proper scheduling optimization.

[0112] Example 5

[0113] In the fifth example, a NR SA UE can be connected to a gNB, a core network (i.e., AMF) triggers a first QoE measurement activation procedure, requesting service type is VR. The AMF can send a QoE measurement activation command to the gNB, including QoE application configuration container, service type equal to VR, QoE task ID equal to 1.

[0114] After receiving the QoE command, the gNB can generate a QoE measurement configuration message and send it to the UE. The measurement configuration can include QoE application configuration container, service type equal to VR, QoE task ID equal to 1.

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

[0116] After receiving this QoE command, the gNB can generate another QoE measurement configuration message and send it to the UE. The measurement configuration can include QoE configuration container (for streaming service), service type equal to streaming, QoE task ID equal to 2, and a deletion list of QoE task ID equal to 1 with one entry.

[0117] After receiving this QoE measurement configuration, the UE can stop the QoE collection for VR service, and start the QoE collection for streaming service.

[0118] QoE measurement logging

[0119] From the UE's perspective, after receiving the QoE measurement configuration from the RAN node, the UE can record the experience information of the indicated service type. In addition, the UE can record the bearer type, timestamp information, and QoE measurement results. The UE can deliver the bearer type and timestamp information to the network in the QoE measurement report.

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

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

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

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

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

[0125] Example 1

[0126] In a first example, 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, the QoE measurement configuration including a QoE measurement configuration container, a service type = VR, a RAT information = both, or a node information = both.

[0127] In the process of the UE recording the QoE experience information, the UE can also record the bearer type of the service. Because the network can dynamically change the bearer type, the bearer type can be recorded together with a timestamp. The timestamp can be an absolute time or a relative time.

[0128] For example, the first record can include MCG bearer for the time from 03:10:20 to 03:11:05 for the primary key. The second record can include SCG bearer for the time from 03:11:06 to 03:15:30 for the secondary key. The third record can include SCG bearer for the time from 03:15:31 to 03:17:48 for the primary key.

[0129] When the UE sends the QoE measurement report to the network, the UE can include the above bearer type information along with the time stamp in the QoE measurement report.

[0130] Example 2

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

[0132] In the process of the UE recording the QoE experience information, the MN can record the bearer type for the service, as the network can dynamically change the bearer type, thus the bearer type is recorded along with the time stamp. The time stamp can be absolute time or relative time. For example, the first record can include MCG bearer for the time from 03:10:20 to 03:11:05 for the primary key. The second record can include SCG bearer for the time from 03:11:06 to 03:15:30 for the secondary key. The third record can include SCG bearer for the time from 03:15:31 to 03:17:48 for the primary key.

[0133] After receiving the QoE measurement report sent from the UE, the MN can include the above bearer type information along with the time stamp in the UE's QoE measurement report and send it to the collection node.

[0134] Example 3

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

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

[0137] QoE measurement reporting

[0138] The QoE measurement report can be sent from the UE to the network node, and the QoE measurement report is sent from the network node to the collection node. The QoE measurement report can include experience information as well as any other information. Examples of such other information can include QoS information (e.g., QFI, E-RAB ID; QoS configuration 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 can be sent along with timestamp information. The bearer type can include any of the following: MCG bearer, SCG bearer, split bearer, etc.

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

[0140] For the QoE measurement report from the UE to the network, the UE can send the QoE measurement report. This can include the UE directly sending the QoE measurement report to the network when the results are available at the UE side. This can also include the UE first sending an available indication to the network to indicate that the UE has available QoE measurement results. The network can trigger the result retrieval procedure by sending a request to the UE, and then the UE can deliver the QoE measurement report to the network.

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

[0142] In some embodiments, for MR-DC UE, in case the MN receives the QoE measurement report from the UE, the MN can forward the QoE measurement result to the SN side. The result of the forwarding can be the whole QoE measurement report, a 1-bit indication to indicate whether the UE meets the current QoE / latency, or explicit assistance information for scheduling optimization.

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

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

[0145] In a first case 408, the SN can not know the IP address of the collection node. In this case, the SN can send the 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 a second case 414, the SN knows 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 example, an NR SA UE can be connected to a gNB, and the UE can be configured with QoE measurements. When the UE already has available QoE measurement results, the UE can first send a 1-bit QoE result available indication to the network. The available indication can be included in one of the following: an RRC message or a newly defined RRC message, such as an RRC reconfiguration complete message, a UE assistance information message, an RRC setup complete message, an RRC resume complete message, etc.

[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 obtain the stored QoE report. The RRC message can be a UE information request message, or a newly defined RRC message. Within the RRC message, the network can include an indication for QoE retrieval. The UE can then send the QoE measurement report to the network node.

[0150] Example 2

[0151] In a second example, an EN-DC UE is connected to both an eNB (MN) and a gNB (SN), and a core network (i.e., MME) triggers a signaling-based QoE measurement for the UE. After receiving the QoE command, the MN can forward the QoE measurement configuration to the SN, and the IP address of the collection node can also be included in the QoE command. Then, the SN can generate and send a QoE measurement configuration message to the UE.

[0152] Since the QoE measurement is 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 has no connection with the collection node (e.g., unknown IP address). The SN can forward the QoE measurement report of the UE to the MN, and the MN can forward the report to the collection node.

[0153] QoE capability negotiation

[0154] For MR-DC UEs, the SN can inform the MN whether the SN is capable of configuring QoE measurement for the UE. The SN can indicate the capability of QoE measurement when the following conditions are met.

[0155] The first condition can include that the UE supports QoE measurement and reports over the RAT of the SN. The second condition can include that the SN node supports QoE measurement and reporting for the UE.

[0156] In some embodiments, the SN can inform the MN of the QoE measurement capability 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 can be sent in an inter-node RRC message (e.g., CG-Config) or indicated by a parameter in an Xn / X2 message.

[0158] Additionally, after SN addition, SN modification, or SN change, the MN can inform the SN whether the SN is allowed to configure QoE measurement for the UE.

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

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

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

[0162] Considerations for power saving or network overload

[0163] In certain network scenarios (e.g., network overload, UE overheating), the network can trigger a temporary stop of QoE measurement. When the situation is alleviated, the QoE measurement can be resumed.

[0164] The network node can send a suspension indication to the UE to inform the UE that the configured QoE measurement is suspended. After receiving the indication, the UE can not be allowed to deliver QoE measurement report to the network. From the UE’s perspective, the UE can continue to record QoE experience information at the application layer, or suspend the recording behavior. After receiving a resume indication from the network, if suspended, the UE can resume the recording behavior and deliver the QoE measurement report to the network.

[0165] In some embodiments, the network can indicate a timer value to the UE along with the suspension indication. After receiving the timer value, the UE can start the timer immediately, or start the timer when the UE stops recording (e.g., the recording memory is full, 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 can delete the recorded QoE measurement results locally.

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

[0167] In some embodiments, the UE can send an indication to the network to request the network to stop the QoE measurement. The MN can need to forward the indication to the SN (or SN to MN).

[0168] In some embodiments, the UE can send an indication to the network to inform the network that the QoE measurement is stopped, and optionally include the reason for stopping the measurement.

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

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

[0171] Example method for QoE measurement collection

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

[0173] The method can also include sending, to the network node, a second message including a set of quality of experience information collected by the terminal and sent according to 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, the set of quality of experience information.

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

[0176] In some embodiments, the QoS information includes any of the following: a QoS flow identifier (QFI), a PDU session identifier, an evolved universal terrestrial access network (E-UTRAN) radio access bearer identifier (E-RAB ID), and QoS configuration information.

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

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

[0179] In some embodiments, the information identifying the target RAT includes any of the following: a list of cell identities of at least one RAT or a list of tracking area codes of at least one RAT or RAT type.

[0180] In some embodiments, any of the following includes node information indicating a target network node for which a set of quality of experience information is to be collected: a configuration for collecting quality of experience information included in the first message or the set of collected quality of experience information included in the second message.

[0181] In some embodiments, any of the following includes a bearer type indicator indicating a target bearer for which a set of quality of experience information is to be collected: a configuration for collecting quality of experience information included in the first message or the set of collected quality of experience information included in the second message.

[0182] In some embodiments, the bearer type indicator can indicate any of the following: a MCG bearer, a SCG bearer, a split bearer, a 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 a plurality of application configuration containers, wherein each application configuration container is applied to a particular RAT.

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

[0185] In some embodiments, the method includes 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 over a master cell group, MCG, radio interface is established and a second set of quality of experience information when a bearer over a secondary cell group, SCG, radio interface is established; and sending, by the terminal, a first report including the first set of quality of experience information to the MN and sending, by the terminal, a second report including the second set of quality of experience information to the SN.

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

[0187] In some embodiments, the method includes transmitting, by the terminal to the network node, an indication that the terminal has collected the set of quality of experience information; and receiving, by the terminal from the network node, a quality of experience information response, 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 1-bit quality of experience information result available indication indicating that the terminal has measured the 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 setup complete message, and an RRC resume complete message.

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

[0191] In some embodiments, the method includes receiving, by the terminal from the network node, a suspension indication including an indication for the terminal to suspend transmission of the second message and / or to stop measuring the set of quality of experience information.

[0192] In some embodiments, the method includes receiving, by the terminal from the network node, a resume indication, 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 initiating, by the terminal, a timer after receiving the suspension indication or after completion of collection of the set of quality of experience information, the timer representing a duration indicated in the suspension indication; and releasing, by the terminal, the set of quality of experience information collected by the terminal upon expiration of the timer.

[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 the network node, a power saving request message to initiate a power saving operation, and receiving, by the terminal, a suspension indication transmitted by the network node in response to the power saving request 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 can also include receiving, by the network node, a second message from the terminal, the second message including a set of quality of experience information collected by the terminal and transmitted according to 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, the configuration for collecting quality of experience information from a core network node or an operations and maintenance (OAM).

[0197] In some embodiments, the method includes forwarding, by the network node, the second message to a 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, the configuration for collecting quality of experience information to a secondary network node, wherein the secondary network node is configured to modify and / or transmit the configuration for collecting quality of experience information to the terminal.

[0200] In some embodiments, the network node includes a central unit (CU), and wherein the network node transmits the configuration for collecting quality of experience information to a distributed unit (DU), wherein the configuration for collecting 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 measuring the set of quality of experience information by the terminal.

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

[0202] In some embodiments, the network node receives the configuration indication when the secondary network node determines that the terminal supports quality of experience information measurement and reporting over a radio access technology (RAT) associated with the secondary network node.

[0203] In some embodiments, the network node receives the configuration indication when the secondary network node supports quality of experience information measurement and reporting for the terminal.

[0204] In some embodiments, any of the configuration for collecting quality of experience information included in the first message and the set of measured quality of experience information and the configuration for collecting quality of experience information from the core network node included in the second message 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, node information indicating a target network node for measuring the set of quality of experience information, and a bearer type indicator indicating a target bearer for measuring the set of quality of experience information.

[0205] In some embodiments, the method includes sending, 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 a bearer over a master cell group (MCG) radio interface is established; and / or 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 a bearer over a secondary cell group (SCG) radio interface is established.

[0206] In some embodiments, the method includes receiving, by the network node from the terminal, a quality of experience information indication indicating that the terminal has measured a set of quality of experience information; and sending, by the network node to the terminal, a quality of experience information response, wherein the second message is sent 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 1-bit quality of experience information result 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 result available indication is received by the network node via any of: a radio resource control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC setup complete message, and an RRC resume complete message.

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

[0210] In some embodiments, the method includes sending, by the network node to the terminal, a suspend indication including an indication for the terminal to suspend transmission of the second message and / or to stop 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 from the terminal, a power saving request message to initiate a power saving operation in response to the terminal determining that a power consumption level of the terminal exceeds a threshold power level, wherein the suspension indication is received by the terminal in response to transmission of the power saving request message.

[0213] Example wireless system

[0214] Figure 8 An example of a wireless communication system is shown in which techniques according to one or more embodiments of the technology can be applied. The wireless communication system 800 can 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 can provide wireless service 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 producing two or more directional beams to provide wireless coverage in different sectors.

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

[0216] In some implementations, the wireless communication system can include multiple networks using different wireless technologies. Dual-mode or multi-mode wireless devices include two or more wireless technologies that can be used to connect to different wireless networks.

[0217] Figure 9is 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 a processor electronic 910, such as a microprocessor, that implements one or more of the techniques presented in this document. The hardware platform 905 can include transceiver electronic 915 for sending and / or receiving wired or wireless signals through 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 sending 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 electronic 910 can include at least a portion of the transceiver electronic 915. In some embodiments, at least some of the disclosed techniques, modules, or functional operations are implemented using the hardware platform 905.

[0218] Conclusion

[0219] From the foregoing, it will be appreciated that specific embodiments of the presently disclosed technology have been described herein for purposes of illustration, but that various modifications can be made without deviating from the scope of the present application. Accordingly, the presently disclosed technology is not limited except as by the appended claims.

[0220] The disclosures and other embodiments, modules, and functions described in this document can be implemented using digital electronic circuitry, or computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other 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, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a combination of devices including one or more of them, or a combination of one or more of them and a propagated signal. 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. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. The propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

[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 it 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 in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and are interconnected by a communication network.

[0222] The processes and logic flows described in this document can be performed 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 can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0223] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, 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 performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. 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, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., 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] While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention, but rather as descriptions of features that can be specific to particular embodiments thereof. Certain features described 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 separately or in any suitable subcombination. Moreover, although features can be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination and the claimed combination can be directed to a subcombination or variation of a subcombination.

[0225] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring such an order, or that all illustrated operations be performed, to implement and / or make use of the present technology. Moreover, 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 a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document.

Claims

1. A method for wireless communication, comprising: receiving, by a terminal from a network node, a first message comprising a configuration for collecting quality of experience information; and sending, by the terminal to the network node, a second message comprising a set of quality of experience information collected by the terminal and sent according to the configuration for collecting quality of experience information received in the first message, wherein the set of quality of experience information comprises quality of service, QoS, information; the QoS information comprising one or more of a QoS flow identifier, QFI, or a protocol data unit, PDU, session identification.

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

3. The method of claim 1, wherein the QoS information further comprises one or more of an evolved universal terrestrial access network, E-UTRAN, radio access bearer identifier, E-RAB ID, and QoS configuration information.

4. The method of claim 1 or 3, wherein the QoS information is further included in the configuration for collecting quality of experience information in the first message.

5. The method of claim 1, wherein any of the configuration for collecting quality of experience information included in the first message or the set of collected quality of experience information included in the second message comprises a network slice identifier.

6. The method of claim 1, wherein any of the configuration for collecting quality of experience information included in the first message or the set of collected quality of experience information included in the second message comprises information identifying a target radio access technology, RAT, for collecting the set of quality of experience information.

7. The method of claim 6, wherein the information identifying the target RAT comprises any of a list of cell identities of at least one RAT or a list of tracking area codes of at least one RAT or RAT type.

8. The method of claim 1, wherein any of the configuration for collecting quality of experience information included in the first message or the set of collected quality of experience information included in the second message comprises node information indicating a target node for collecting the set of quality of experience information.

9. The method of claim 1, wherein any of the configuration for collecting quality of experience information included in the first message or the set of collected quality of experience information included in the second message comprises a bearer type indicator indicating a target bearer type for collecting the set of quality of experience information.

10. The method of claim 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, an MN terminated SCG bearer, an MN terminated split bearer, a secondary node (SN) terminated MCG bearer, an SN terminated SCG bearer, or an SN terminated split bearer.

11. The method of claim 1, wherein the configuration for collecting quality of experience information comprises a plurality of application configuration containers, wherein each application configuration container is applied to a particular RAT.

12. The method of claim 2, wherein collecting the set of quality of experience information comprises: recording, according to the configuration for collecting quality of experience information, bearer type and timestamp information of the collected service.

13. The method of claim 1, further comprising: receiving, by the terminal from each of a master node (MN) and a secondary node (SN), a plurality of configurations for measuring quality of experience information; 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 sending, by the terminal to the MN, a first report comprising the first set of quality of experience information and to the SN, a second report comprising the second set of quality of experience information.

14. The method of claim 1, wherein the second message is sent in response to the terminal measuring the set of quality of experience information.

15. The method of claim 1, further comprising: sending, 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; and receiving, by the terminal from the network node, a quality of experience information response, wherein the second message is sent by the terminal in response to receiving the quality of experience information response from the network node.

16. The method of claim 1, further comprising: sending, by the terminal to the network node, a 1-bit quality of experience information result available indication indicating that the terminal has measured the set of quality of experience information.

17. The method of claim 16, wherein the 1-bit quality of experience information result available indication is sent to the network node via any of a radio resource control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC setup complete message, and an RRC resume complete message.

18. The method of any of claims 16 and 17, further comprising: receiving, by the terminal from the network node, an RRC message comprising a request for the set of quality of experience information when network load is below a threshold level, wherein the second message is sent by the terminal to the network node in response to receiving the RRC message from the network node.

19. The method of claim 1, further comprising: ​ ​ receiving, by the terminal from the network node, a suspension indication, the suspension indication comprising an indication for the terminal to suspend transmission of the second message and / or to stop measuring the set of quality of experience information.

20. The method of claim 19, further comprising: receiving, by the terminal from the network node, a resume indication, wherein the second message is transmitted by the terminal in response to receiving the resume indication from the network node.

21. The method of claim 19, further comprising: initiating, by the terminal, a timer after receiving the suspension indication, or after completing collection of the set of quality of experience information, the timer having a duration indicated in the suspension indication; and releasing, by the terminal, the set of quality of experience information collected by the terminal upon expiration of the timer.

22. The method of claim 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 the network node, a power saving message to initiate a power saving operation, wherein the suspension indication is received by the terminal in response to transmission of the power saving message.

23. A method for wireless communication, comprising: transmitting, by a network node to a terminal, a first message, the first message comprising a configuration for collecting quality of experience information; and receiving, by the network node from the terminal, a second message, the second message comprising a set of quality of experience information collected by the terminal transmitted in accordance with the configuration for collecting quality of experience information received in the first message, wherein the set of quality of experience information comprises quality of service, QoS, information; the QoS information comprising one or more of: a QoS flow identifier, QFI, or a protocol data unit, PDU, session identification.

24. The method of claim 23, further comprising: receiving, by the network node, the configuration for collecting quality of experience information from a core network node.

25. The method of any one of claims 23 and 24, further comprising: forwarding, by the network node, the second message to a QoE collection node.

26. The method of claim 24, wherein the core network node comprises any one of: a core access and mobility management function, AMF, node, and a mobility management entity, MME, node.

27. The method of claim 23, further comprising: forwarding, by the network node, the configuration for collecting quality of experience information to a secondary network node, wherein the secondary network node is configured to modify the configuration for collecting quality of experience information, and / or to transmit the configuration for collecting quality of experience information to the terminal.

28. The method of claim 23, wherein the network node comprises a central unit, CU, and wherein the network node sends the configuration for collecting quality of experience information to a distributed unit, CU, wherein the configuration for collecting quality of experience information comprises 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 measuring the set of quality of experience information by the terminal.

29. The method of claim 23, further comprising: receiving, by the network node from a secondary network node, a configuration indication about whether the network node is capable of configuring the terminal with the configuration for collecting quality of experience information.

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 over a radio access technology, RAT, associated with the secondary network node.

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

32. The method of any of claims 23 and 24, wherein any of the configuration for collecting quality of experience information included in the first message, and the configuration for collecting quality of experience information from a core network node comprises 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, 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, the set of quality of experience information further comprises any of: 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.

33. The method of claim 23, further comprising: sending, 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 comprising a first set of quality of experience information measured by the terminal when a bearer is established over a master cell group, MCG, radio interface; and receiving, by the network node from the terminal, a second report comprising a second set of quality of experience information measured by the terminal when a bearer is established over a secondary cell group, SCG, radio interface.

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

35. The method of claim 23, further comprising: receiving, by the network node from the terminal, a 1-bit quality of experience information result available indication indicating that the terminal has measured the set of quality of experience information.

36. The method of claim 35, wherein the 1-bit quality of experience information result available indication is received by the network node via any of: a radio resource control (RRC) reconfiguration complete message, a terminal assistance information message, an RRC setup complete message, and an RRC resume complete message.

37. The method of any one of claims 35 and 36, further comprising: transmitting, by the network node to the terminal, an RRC message including a request for the set of quality of experience information when network load is below a threshold level, wherein the second message is transmitted by the terminal to the network node in response to receiving the RRC message from the network node.

38. The method of claim 23, further comprising: transmitting, by the network node to the terminal, a suspension indication including an indication for the terminal to suspend transmission of the second message and / or to stop measuring the set of quality of experience information.

39. The method of claim 38, further comprising: transmitting, by the network node to the terminal, a resumption indication, wherein the second message is transmitted by the terminal in response to receiving the resumption indication from the network node.

40. The method of claim 38, further comprising: receiving, by the network node from the terminal, a power saving message to initiate a power saving operation in response to the terminal determining that a power consumption level of the terminal exceeds a threshold power level, wherein the suspension indication is received by the terminal in response to transmission of the power saving message.

41. An apparatus for wireless communication, comprising a processor configured to perform the method of any one of claims 1-40.

42. A non-transitory computer-readable medium having code stored thereon, the code, when executed by a processor, causing the processor to implement the method of any one of claims 1-40.

Images