Quality of experience handling in dual connectivity
Patent Information
- Application Number
- PCT/CN2023/093700
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-14
Smart Images

Figure CN2023093700_14112024_PF_FP_ABST
Abstract
Description
QUALITY OF EXPERIENCE HANDLING IN DUAL CONNECTIVITYFIELD
[0001] Various example embodiments relate to the field of telecommunication, and in particular, to devices, methods, apparatuses and a computer readable storage medium for quality of experience (QoE) in dual connectivity.BACKGROUND
[0002] With the development of communication technologies, several solutions have been proposed to provide efficient and reliable solutions for communication. It is important to measure communication quality in order to evaluate communication performances. Hence, Quality of Experience (QoE) has been proposed as a measure to quantify subscriber satisfaction. QoE is a term used to describe communication performances and how usable the subscribers think the services are. As such, QoE may take into account the overall application or service layer performance of traffic between the application or service at a user equipment to a network device.SUMMARY
[0003] In general, example embodiments of the present disclosure provide a solution for QoE handing in dual connectivity.
[0004] In a first aspect, there is provided a terminal device. The terminal device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: receive, in dual connectivity operation, a first quality of experience (QoE) configuration configured by a first node; determine unavailability of a reporting leg for transmission of a QoE measurement report according to the received configuration; transmit information on the unavailability of the reporting leg to a second node, wherein the second node is different from the first node; and receive, from the second node, a second configuration, wherein the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0005] In a second aspect, there is provided a network device. The network device is configured to provide a dual connectivity to a terminal device with another network device, the network device includes at least one processor and at least one memory storing an instruction that, when executed by the at least one processor, cause the network device at least to: receive, from a terminal device, information on unavailability of a reporting leg for transmission of a quality of experience (QoE) measurement report according to a first QoE configuration; and transmit, to the terminal device, a second configuration indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0006] In a third aspect, there is provided a network device. The network device is configured to provide a dual connectivity to a terminal device with another network device, the network device includes at least one processor and at least one memory storing an instruction that, when executed by the at least one processor, cause the network device at least to: transmit a first quality of experience (QoE) configuration to a terminal device; receive at least one QoE measurement report according to the first QoE configuration; and transmit information associated with the received at least one QoE measurement report to another network device.
[0007] In a fourth aspect, there is provided a method. The method includes: receiving, in dual connectivity operation, a first quality of experience (QoE) configuration configured by a first node; transmitting information on the unavailability of the reporting leg to a second node, wherein the second node is different from the first node; and receiving, from the second node, a second configuration, wherein the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0008] In a fifth aspect, there is provided a method. The method includes: receiving, from a terminal device, information on unavailability of a reporting leg for transmission of a quality of experience (QoE) measurement report according to a first QoE configuration; and transmitting, to the terminal device, a second configuration indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0009] In a sixth aspect, there is provided a method. The method includes: transmitting a first quality of experience (QoE) configuration to a terminal device; receiving at least one QoE measurement report according to the first QoE configuration; and transmitting information associated with the received at least one QoE measurement report to another network device.
[0010] In a seventh aspect, there is provided an apparatus. The apparatus includes: means for receiving, in dual connectivity operation, a first quality of experience (QoE) configuration configured by a first node; means for transmitting information on the unavailability of the reporting leg to a second node, wherein the second node is different from the first node; and means for receiving, from the second node, a second configuration, wherein the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0011] In an eighth aspect, there is provided an apparatus. The apparatus includes: means for receiving, from a terminal device, information on unavailability of a reporting leg for transmission of a quality of experience (QoE) measurement report according to a first QoE configuration; and means for transmitting, to the terminal device, a second configuration indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0012] In a ninth aspect, there is provided an apparatus. The apparatus includes: means for transmitting a first quality of experience (QoE) configuration to a terminal device; means for receiving at least one QoE measurement report according to the first QoE configuration; and means for transmitting information associated with the received at least one QoE measurement report to another network device.
[0013] In an tenth aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method in the fourth, fifth, or sixth aspect.
[0014] In an eleventh aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to perform at least the method in the fourth, fifth, or sixth aspect.
[0015] In a twelfth aspect, there is provided a device. The device is configured to provide a dual connectivity to a terminal device with another device, the device includes: a first receiving circuitry, configured to receive, in dual connectivity operation, a first quality of experience (QoE) configuration configured by a first node; a determination circuity, configured to determine unavailability of a reporting leg for transmission of a QoE measurement report according to the received configuration; transmit information on the unavailability of the reporting leg to a second node, wherein the second node is different from the first node; and a second receiving circuitry, configured to receive, from the second node, a second configuration, wherein the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0016] In an thirteenth aspect, there is provided a device. The device is configured to provide a dual connectivity to a terminal device with another device, the device includes: a receiving circuitry, configured to receive, from a terminal device, information on unavailability of a reporting leg for transmission of a quality of experience (QoE) measurement report according to a first QoE configuration; and a transmission circuitry, configured to transmit, to the terminal device, a second configuration indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0017] In a fourteenth aspect, there is provided a device. The device is configured to provide a dual connectivity to a terminal device with another network device, the device includes: a first transmission circuitry, configured to transmit a first quality of experience (QoE) configuration to a terminal device; a receiving circuitry, configured to receive at least one QoE measurement report according to the first QoE configuration; and a second transmission circuitry, configured to transmit information associated with the received at least one QoE measurement report to another network device.
[0018] It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Some example embodiments will now be described with reference to the accompanying drawings, in which:
[0020] Fig. 1 illustrates an example of an environment in which some example embodiments of the present disclosure may be implemented;
[0021] Fig. 2 illustrates an example signaling process of management-based QoE configuration and reporting;
[0022] Fig. 3 illustrates an example signaling process for performing QoE handling in a dual connectivity according to some embodiments of the present disclosure;
[0023] Fig. 4 illustrates an example signaling process for performing QoE configuration in a first scenario;
[0024] Fig. 5A illustrates an example signaling process for performing a second configuration for the terminal device according to some embodiments of the present disclosure;
[0025] Fig. 5B illustrates another example signaling process for performing a second configuration for the terminal device according to some embodiments of the present disclosure;
[0026] Fig. 6 illustrates an example signaling process for performing QoE configuration in a second scenario;
[0027] Fig. 7 illustrates an example signaling process for performing establishment of a connection when a master cell group (MCG) reporting leg is unavailable according to some embodiments of the present disclosure;
[0028] Fig. 8 illustrates a flowchart of a method implemented at a terminal device in accordance with some example embodiments of the present disclosure;
[0029] FIG. 9 illustrates a flowchart of a method implemented at a network device in accordance with some example embodiments of the present disclosure;
[0030] FIG. 10 illustrates a flowchart of a method implemented at a network device in accordance with some example embodiments of the present disclosure;
[0031] Fig. 11 illustrates a simplified block diagram of a device that is suitable for implementing some example embodiments of the present disclosure; and
[0032] Fig. 12 illustrates a block diagram of an example of a computer readable medium in accordance with some example embodiments of the present disclosure.
[0033] Throughout the drawings, the same or similar reference numerals represent the same or similar elements.DETAILED DESCRIPTION
[0034] Principles of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.
[0035] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one skilled in the art to which this disclosure belongs.
[0036] References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0037] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0038] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0039] As used in this application, the term “circuitry” may refer to one or more or all of the following:
[0040] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and
[0041] (b) combinations of hardware circuits and software, such as (as applicable) :
[0042] (i) a combination of analog and / or digital hardware circuit (s) with software / firmware and
[0043] (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and
[0044] (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (for example, firmware) for operation, but the software may not be present when it is not needed for operation.
[0045] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0046] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, the future sixth generation (6G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
[0047] As used herein, the term “network device” or “network node” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a system simulator, a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.
[0048] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (for example, remote surgery) , an industrial device and applications (for example, a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
[0049] The term “reporting leg” is used in 3rd generation partnership project (3GPP) technical specification, and refers to a communication link between a terminal device and a network device. Information such as measurement reports may be transmitted over the reporting leg, e.g., from the terminal device to the network device. The term “reporting leg for transmission of a QoE measurement report” , may refer to a communication link between a terminal device and a network device over which a QoE measurement report is transmitted from the terminal device to the network device.
[0050] As stated above, QoE has been proposed to evaluate communication performances in a communication system. Generally, QoE may be defined for multiple characteristics of a service, such as service integrity, which is defined by, for example, throughput, delay, jitter and data loss, and service security, which may include authentication, integrity and confidentiality, etc. Some objectives have been agreed by 3GPP community on “NR QoE management and optimizations for diverse services” , such as specification of QoE measurements, definition of procedures to support QoE data collection in intra-system intra-RAT mobility scenarios, radio access network (RAN) visible QoE (RVQoE) as well as QoE measurement collection per single network slice selection assistance information (S-NSSAI) .
[0051] QoE configuration may comprise RVQoE configuration or container-based QoE configuration. QoE measurements may comprise RVQoE measurements or container-based QoE measurements. QoE measurement report may comprise RVQoE measurement report or container-based QoE measurement report.
[0052] New radio (NR) QoE solutions and procedures include a signaling-based procedure and a management-based procedure as LTE. In the signaling-based procedure, the core network initiates an activation of QoE measurements as configured by an operation administration and maintenance (OAM) , while in the management-based procedure, the OAM sends the QoE management configuration directly to a RAN node.
[0053] For both of the signaling-based procedure and the management-based procedure, once a RAN node identifies a terminal device that matches a certain criterion, for example, area scope, service type, slice scope, then the RAN node may forward the QoE measurement configuration to an access stratum (AS) layer of the terminal device, which in turn sends the measurement configuration to an application layer of the terminal device. The RAN node may encapsulate the configuration in a transparent container, which is then sent to the terminal device as an application (APP) layer configuration in the RRCReconfiguration message. The measurement reports generated from the APP layer of the terminal device are encapsulated in a transparent container and sent to the network, for example, in the MeasurementReportAppLayer message using SRB4.
[0054] RAN visible quality of experience (RVQoE) has been introduced as a further enhancement to container-based QoE. RVQoE is reported by a terminal device to a RAN node (e.g., a network device or a network node) for a subset of the configured container-based QoE metrics as an explicit information element readable by the RAN node. RAN node can utilize these RVQoE reports to further optimize its behavior, for instance to optimize scheduling decisions.
[0055] Current RVQoE metrics may include metrics of application layer buffer level (appLayerBufferLevelList) and playout delay for media start-up (playoutDelayForMediaStartup) . Multiple RVQoE measurement configurations may be supported for a RVQoE measurement. The RVQoE measurement configuration and the RVQoE measurement report are identified by the same measurement configuration identifier, e.g. radio resource control (RRC) identifier, as the QoE measurement configuration and measurement report (measConfigAppLayerId) . After receiving the RVQoE measurement configuration, the AS layer of the terminal device may forward the configuration to APP layer of the terminal device. RVQoE configuration can be configured, e.g. only be configured, if there is a corresponding QoE measurement configuration for the same service type configured at the terminal device.
[0056] The APP layer of the terminal device may send the RVQoE measurement report associated with the RRC identifier (e.g., measConfigAppLayerId) to the AS layer of the terminal device. If there is no reporting periodicity defined in the RVQoE configuration, the terminal device may send both RVQoE measurement reports and the QoE measurement reports to the network node in the same message, e.g., MeasurementReportAppLayer message, except in case of RAN overload. In case of RAN overload, if there is no reporting periodicity defined in the RVQoE configuration, the encapsulated QoE reports are stored at the AS layer of the terminal device, while the RVQoE reports continue to be reported to the network node with the reporting periodicity configured for legacy QoE reporting, even if the corresponding reporting of encapsulated QoE measurement is paused. The RVQoE measurements can be reported with a reporting periodicity different from the one of the corresponding encapsulated QoE measurements, when a dedicated RVQoE reporting periodicity is configured by the network node. The APP layer of the terminal device may measure the RVQoE metrics based on this reporting periodicity. The network node may release one or multiple RVQoE measurement configurations from the terminal device in one RRCReconfiguration message at any time.
[0057] The following objectives have been agreed by 3GPP community with respect to enhancements of QoE in NR-dual connectivity (DC) setup:
[0058] Specify the support for QoE in NR-DC, e.g., enable QoE reporting via SN [RAN3, RAN2] :
[0059] -specify the QoE configuration and measurement reporting over a master node (MN) / asecondary node (SN) for NR-DC architecture, and specify the QoE measurement reporting over the other DC leg in order to maintain the reporting continuity (the QoE measurements might not be performed separately for each leg) ;
[0060] -support RAN-visible QoE and radio related measurement configuration and reporting in NR-DC scenarios;
[0061] -specify the QoE measurement continuity in mobility scenarios in NR-DC; and
[0062] -specify an alignment of QoE measurements (including legacy QoE and RAN visible QoE measurements) and radio related measurement in NR-DC.
[0063] In light of supporting RVQoE in NR-DC the following agreements have been made:
[0064] -both MN and SN can generate RVQoE configurations;
[0065] -MN and SN may coordinate about configuring a dual-connected UE with RVQoE measurements;
[0066] -SN can receive RVQoE directly from the UE;
[0067] -to ensure that the RVQoE report is sent to a node that provides the bearer (s) associated with the corresponding RVQoE measurement result in the report;
[0068] -SN may send RVQoE configuration to UE. FFS if sent to UE via SRB3 or via split SRB1 over an Xn interface (if MN can modify RVQoE) ;
[0069] -the first RVQoE configuration may be blindly configured and after the node determines which node provides the bearer (s) , the RVQoE configuration may be modified; and
[0070] -if a node receives an RVQoE report from a UE in NR-DC, and determines that the bearers for the application session are, also or e.g. only, provided by the peer node, this node may send the received RVQoE report to the peer node.
[0071] Currently, some ideas have been provided with respect to QoE report continuity in NR-DC setup. Moreover, these ideas use existing messages, such as SN addition request message, to transfer the QoE configuration to the target SN via MN during a period of primary service cell (PSCell) change. Furthermore, the SN release message is enhanced to transfer the QoE configuration from SN to MN when UE goes from a dual connectivity to a single connectivity.
[0072] Moreover, there has been a discussion about a scenario for container-based QoE when a secondary cell group (SCG) or master cell group (MCG) leg fails.
[0073] It may be desirable to clarify MN’s behavior in such scenarios to enable continuity for QoE. It may be desirable to provide a solution for QoE report continuity when a reporting leg becomes unavailable, for example, due to a SCG failure, SN release, or an MCG failure.
[0074] In view of the above, example embodiments of the present disclosure provide a solution for QoE or RVQoE handling in dual connectivity during a time period that a reporting leg is unavailable for transmission of the QoE measurement report or RVQoE measurement report.
[0075] FIG. 1 illustrates an example of an environment 100 in which some example embodiments of the present disclosure may be implemented. In the description of the example embodiments of the present disclosure, the environment 100 may be implemented as a dual connectivity. As shown in Fig. 1, a terminal device 140 communicates with a node (e.g., a network device) 110 and a node (e.g., a network device) 120 in the environment 100. The node 110 may be implemented as a master node (MN) of the dual connectivity, and the node 120 may be implemented as a secondary node (SN) of the dual connectivity. For example, MN 110 is a node to which the terminal device 140 first connects, and subsequently, the terminal device 140 may use a radio resource control (RRC) signaling message via the MN 110 to connect to the SN 120.
[0076] As illustrated in Fig. 1, the terminal device 140 may communicate with the MN 110 and the SN 120 in the environment or the system 100 supporting wired / wireless communication. In the environment 100, a link from the MN 110 or the SN 120 to the terminal device 140 may be referred to as a downlink (DL) , a link from the terminal device 140 to any of the MN 110 or the SN 120 may be referred to as an uplink (UL) , and a link between the terminal device 140 and a peer terminal device may be referred to as sidelink.
[0077] In downlink, the MN 110 or the SN 120 is a transmitting (TX) device (or a transmitter) while any of the terminal device 140 is a receiving (RX) device (or a receiver) . In uplink, the terminal device 140 is a transmitting TX device (or a transmitter) , while the MN 110 or the SN 120 is a RX device (or a receiver) . In some embodiments, the MN 110, the SN 120 and the terminal device 140 may communicate with direct links / channels.
[0078] The terminal device 140 may be configured with QoE configuration. On the basis of the configuration, the terminal device 140 may perform QoE measurements and report the QoE measurement results to a consumer node, e.g. the MN 110 or the SN 120. In some embodiments, a QoE configuration may include a RAN visible QoE (RVQoE) configuration. The node that receives and utilizes the RVQoE measurement reports may be referred to as a consumer node. The consumer node may configure the terminal device 140 with the RVQoE configuration. In other words, the consumer node may provide data radio bearers (DRBs) for the service at the terminal device 140. The terminal device 140 may receive the configuration from a configuring node, or via another node. For example, SN 120, if acts as a consumer node, may provide the configuration of RVQoE measurements via MN 110 to the terminal device 140, e.g. if there is no suitable bearer, e.g. SCG bearer or SRB3, to send the configuration. If SN 120 is the consumer node, it is the node that receives the RVQoE measurement reports from the terminal device 140.
[0079] During implementations of the communication, a secondary cell group (SCG) failure may occur, SN may be released, or a master cell group (MCG) failure may occur. In any of these situations, a reporting leg for transmission of a QoE measurement report based on the QoE configuration may be or become unavailable. In order to implement QoE report continuity, in some embodiments, the terminal device 140 may transmit information on the unavailability of the reporting leg to a second node different from the previous consumer node, and receive, from the second node, a second configuration that is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration. In some embodiments, the MN 110 may have been the consumer node and the second node may be the SN 120or another network device 130. In some embodiments, the second node may become a master node in the connection.
[0080] In some embodiments, the consumer node may have been the SN 120 and the second node may be the MN 110.
[0081] It is to be understood that communications among devices in the environment 100 may be implemented according to any appropriate communication protocol (s) , including, but not limited to, cellular communication protocols of the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) , the sixth generation (6G) , and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any appropriate wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0082] It should be noted that, although RVQoE configuration is described with reference to QoE configuration, the QoE configuration is not limited. The QoE configuration may also include other types of QoE configuration, e.g., container-based QoE configuration.
[0083] Fig. 2 illustrates an example signaling process 200 of management-based QoE configuration and reporting which may be implemented in the environment 100 as shown in Fig. 1. As shown in Fig. 2, in the management-based QoE configuration and reporting, the OAM 270 sends a QoE Measurement Configuration to a network node 230 (e.g., the node 110 in Fig. 1) at 201. The network node 230 may detect that a terminal device 240 (e.g., a terminal device 140 in Fig. 1) fulfills criteria for performing measurements at 202, and send a RRCReconfiguration message including AppLayerConfig-r17 IE with container-based QoE measurement and RVQoE configuration at 203. The terminal device 240 may forward the QoE measurement configuration from the AS layer 242 to the APP layer 244 in an AT command at 204. The APP layer 244 may perform measurement collection at 205, and send the measurement results to the AS layer 242 at 206 via an AT command with an ApplicationLayer Measurement Report. Accordingly, the terminal device 240 may transmit the measurement results provided by the APP layer 244 to the network node 230 at 207. For example, the terminal device 240 may transmit the measurement results to the network node 230 via a SRB4. At 208, the network node 230 may forward the measurement result, e.g. in a form of MeasurementReportApplicationLayer message, to a management collection entity (MCE) or trace collection entity (TCE) 260.
[0084] Fig. 3 illustrates an example signaling process 300 for performing QoE handling in dual connectivity according to some embodiments of the present disclosure. For the purpose of discussion, the process 300 will be described with reference to Fig. 1. The process 300 may involve a first node 310 and a second node 320. The first node 310 may include a network device and the second node 320 may include a network device. In some embodiments, the first node 310 is a node that configures the terminal device 340 with a QoE configuration, e.g., RVQoE configuration, and receives a QoE measurement report, e.g. RVQoE measurement report, as a consumer node via a reporting leg. When the reporting leg is unavailable for transmission of the (RV) QoE measurement report, the consumer node of the (RV) QoE measurement report may be changed to be the second node 320. When the first node 310 is the MN 110 in Fig. 1, the second node 320 may be either the SN 120 or a new MN 130. When the first node 310 is the SN 120 in Fig. 1, the second node 320 may be the MN 110 in Fig. 1. An operation administration and maintenance (OAM) 370 is also shown in Fig. 3, and the OAM 370 may transmit configuration information to the first node 310 and the second node 320 to instruct how the nodes behave in the process 300. It may be understood that, in the process 300, it is possible to add, omit, modify one or more operations, or the operations may also be performed in any suitable order without departing from the scope of the present disclosure.
[0085] In the process 300, the OAM 370 may transmit (301) first configuration information to the first node 310 indicative of QoE handling at least during a time period that the reporting leg is unavailable for transmission of the QoE measurement report (s) according to a first QoE configuration configured by the first node 310. The OAM 370 may further transmit (302) second configuration information to the second node 320 indicative of QoE handling at least during a time period that the reporting leg is unavailable for transmission of the QoE measurement report (s) according to a first QoE configuration configured by the first node 310. The first configuration information and the second configuration information configure the first node 310 and the second node 320, respectively, to perform an operation related to QoE configuration. For example, based on the first configuration information from the OAM 370, the first node 310 may provide assistance information to the second node 320 with respect to the QoE configuration. For another example, the second node 320 may determine whether to reconfigure QoE for the terminal device 340, maintain the QoE configuration configured by the first node 310, or release the QoE configuration configured by the first node 310, when a reporting leg associated with the first node is unavailable for a transmission of a QoE measurement report. It should be understood that, the first configuration information and the second configuration information may also be self-configured by the first node 310 and the second node 320, respectively. The present disclosure does not limit the entity that configures the first node 310 and second node 320 with the first and second configuration information.
[0086] As shown in Fig. 3, the first node 310 may transmit (303) a first QoE configuration to the terminal device 340. The first QoE configuration is used to configure the terminal device 340 with QoE measurements and QoE reporting. In some embodiments, the QoE configuration may include a RVQoE configuration. In some other embodiments, the QoE configuration may also include other types of QoE configuration, e.g., a container-based QoE configuration. In some embodiments, if the first node 310 is the SN in the dual connectivity, the first QoE configuration is transmitted to the terminal device 340 via SRB3 or to the MN (the second node 320 in Fig. 3) of the dual connectivity which embeds or encapsulates the configuration and sends the embedded or encapsulated QoE configuration to the terminal device 340 via SRB1. In some embodiments, if the first node 310 is the MN in the dual connectivity, the first node may transmit the QoE configuration to the terminal device 340 via SRB1.
[0087] The terminal device 340, upon receiving the first QoE configuration, may perform (304) QoE measurements and transmit (305) a QoE measurement report to the first node 310, which is a consumer node of the QoE reports at this stage. In some embodiments, the terminal device 340 may include an access stratum (AS) layer and an application (APP) layer. The AS layer of the terminal device 340 may receive the first QoE configuration and forward the first QoE configuration to the APP layer. The APP layer of the terminal device 340 may perform the QoE measurements according to the first QoE configuration and provide the QoE measurement results to the first node 310 via a QoE measurement report. In some embodiments, the QoE measurement may be transmitted to a MCE / TCE by the first node 310.
[0088] The terminal device 340 may determine (306) unavailability of a reporting leg for transmission of a QoE measurement report according to the received first QoE configuration. For example, the reporting leg may be associated with the first node 310 for transmission of a QoE measurement report. The unavailability of the reporting leg for transmission of a QoE measurement report may be caused by different factors depending on the first node 310 being MN or SN in the dual connectivity. For example, when the first node 310 is the SN of the dual connectivity, the terminal device 340 determines the unavailability of the reporting leg based on an occurrence of a secondary cell group (SCG) failure or based on an occurrence of the SN being released; and when the first node 310 is the MN of the dual connectivity, the terminal device 340 determines the unavailability of the reporting leg based on an occurrence of a master cell group (MCG) failure.
[0089] Upon determining that the report leg is unavailable for transmitting a QoE measurement report according to the received first QoE configuration, the terminal device 340 may transmit (307) information on the unavailability of the reporting leg to the second node 320. The second node 320, in response to the information received from the terminal device 340, may reconfigure the QoE for the terminal device 340, maintain the first QoE configuration as configured by the first node 310, or release the first QoE configuration configured by the first node 310. For example, the second node 320 may transmit (309) second configuration to the terminal device 340. The second configuration may indicate a QoE reconfiguration, maintain the first QoE configuration, or release of the first QoE configuration.
[0090] In some embodiments, the QoE reconfiguration may be used to reconfigure the terminal device 340. The QoE reconfiguration may include updated configuration of the first QoE configuration, and the updated configuration may include one or more of: at least one updated QoE configuration parameter; or a measurement configuration identifier associated with the second configuration. In some embodiments, the measurement configuration identifier may include, but not limited to, RRC identifier, or measConfigAppLayerId. Accordingly, the terminal device 340 may be configured based on the QoE reconfiguration.
[0091] Alternatively, the second node 320 may instruct the terminal device 340 to release the previously configured first QoE configuration. The second configuration may include release information to indicate release of the first QoE configuration, and the release information may include a measurement configuration identifier associated with the first QoE configuration. In some embodiments, the measurement configuration identifier may include, but not limited to, RRC identifier, or measConfigAppLayerId. Accordingly, the terminal device 340 may be configured based on the QoE reconfiguration. Based on the measurement configuration identifier associated with the first QoE configuration, the terminal device 340 may decide to release the first QoE configuration.
[0092] Alternatively, the second configuration may also instruct the terminal device 340 to maintain the previously configured first QoE configuration. For example, the second configuration transmitted by second node 320 may include an indication or a flag with a preset value to indicate the terminal device 340 to maintain the previously configured first QoE configuration. It should be understood that, other formats of the second configuration may be employed by the second node 320 to inform the terminal device 340 to maintain the previously QoE configuration.
[0093] In some embodiments, the terminal device 340, upon determining the unavailability of the reporting leg, may start counting, for example, start a timer. The terminal device 340, based on a determination that a predetermined time period has been elapsed without receiving the second configuration from the second node, may release the first QoE configuration or may continue performing QoE measurements according to the first QoE configuration. The predetermined time period is preset and may be configured to any time period.
[0094] Continuing with reference to Fig. 3, the second node 320, in order to reconfigure the terminal device 340 in a situation that the reporting leg is unavailable to transmit a QoE measurement report, may receive assistance information, e.g., information on the first QoE configuration and / or information associated with the QoE measurement report, from the first node 310. The information associated with the QoE measurement report may include the QoE measurement report, statistics of the QoE measurement report, or a combination of the QoE measurement report and statistics of the QoE measurement report. Statistics of QoE measurement result may be in a form of an average measurement result, in a form of a full measurement, or in some other forms depending on actual application and requirements.
[0095] Accordingly, the first node 310 may transmit (308) information on the first QoE configuration and / or information associated with the QoE measurement report to the second node 320. The information received by the second node 320 may include information on the first QoE configuration and / or information associated with the QoE measurement report. For example, information associated with the QoE measurement report may include at least one of the following: statistics (average or full measurements, or other appropriate forms) of the QoE measurement report, or the QoE measurement report. The assistance information may facilitate the second node 320 to adequately perform the second configuration for the terminal device 340. In some embodiments, the information associated with the QoE measurement report (e.g., statistics of the QoE measurement reports or the QoE measurement reports) may be transmitted by the first node 310 periodically to the second node 320.
[0096] Although the transmission of information is shown at 308 after the determination of unavailability of the reporting leg for transmission of a QoE measurement report according to the first QoE configuration, this is not limited. For example, the first node 310 may transmit (308) information on the first QoE configuration and / or the information associated with QoE measurement results to the second node 320 before determining (306) the unavailability of the reporting leg, e.g., based on the first configuration from the OAM 370. In addition, the first node 310 may transmit the information on the first QoE configuration and the QoE measurement results in separate procedures with a certain time delay. In some other embodiments, the first node 310 may transmit the QoE measurement results together with information on the first QoE configuration.
[0097] The terminal device 340, based on the second configuration from the second node 320, may perform the configured QoE measurements or release the first QoE configuration. When the terminal device 340 performs the QoE measurements based on the QoE reconfiguration or the first QoE configuration as indicated by the second configuration, the terminal device 340 may transmit the QoE measurement results to the second node 320, which becomes the consumer node of the QoE reports during the time period that the reporting leg for transmission of the QoE measurement report according to the first QoE configuration is unavailable.
[0098] As explained above in combination with Fig. 3, the first node 310 in Fig. 3 may be either a master node (MN) or a secondary node (SN) in a dual connectivity. Accordingly, different detailed procedures may be implemented in these scenarios. A detailed explanation about the QoE handling in these two different scenarios may be provided below in combination with Figs. 4-7.
[0099] Fig. 4 illustrates an example signaling process 400 for performing QoE configuration in a first scenario. In the first scenario, the SN 410 of the dual connectivity configures the terminal device 440 with a first QoE configuration and provides the bearers to the terminal device 440 for the service. Accordingly, the SN 410 is the consumer of the QoE measurement report during a time period when a SCG reporting leg is available for transmission of a QoE measurement report according to the first QoE configuration. When a SCG failure or SN release occurs, the SCG reporting leg is unavailable for transmission of a QoE measurement report, and the terminal device 440 may determine this unavailability and inform the MN 420 in the dual connectivity. The MN 420 may reconfigure the terminal device 440 with a second configuration, which is indicative of a QoE reconfiguration, maintenance of the first QoE configuration, or release of the first QoE configuration. Accordingly, the consumer node is changed from the SN 410 to the MN 420, which receives the QoE measurement results measured and reported based on the second configuration.
[0100] Now referring to the process 400 of Fig. 4, the OAM 470 may transmit first configuration information (e.g., QoE measurement configuration) at 401 to the SN 410 indicative of QoE handling at least during a time period that the SCG reporting leg is unavailable for transmission of the QoE measurement report. The OAM 470 may further transmit second configuration information (e.g., QoE measurement configuration) at 402 to the MN 420 indicative of QoE handling at least during a time period that the SCG reporting leg is unavailable for transmission of the QoE measurement report. It should be understood that, the first configuration information and the second configuration information may also be self-configured by the SN 410 and the MN 420, respectively. The present disclosure does not limit the entity that configures the SN 410 and the MN 420 with the first and second configuration information.
[0101] In some embodiments, the second configuration information (e.g., QoE measurement configuration) includes information that instructs MN 420 whether to reconfigure the QoE configuration for the terminal device 440 or release the QoE configuration when the SCG reporting leg becomes unavailable. In this first scenario, SCG reporting leg unavailability is associated with a SCG failure or SN release. Accordingly, the MN 420 may determine to reconfigure the QoE configuration for the terminal device 440 or release the QoE configuration. In some embodiments, the MN 420 may also maintain the first QoE configuration for the terminal device 440 through the second configuration.
[0102] The first configuration is provided from OAM 470 to the SN 410, and the first configuration may include information instructing how the SN 410 performs in a situation that the SN 410 configures the terminal device 440 with the first QoE configuration and the SCG reporting leg is unavailable. In some embodiments, the first configuration information may include information indicative of remapping the SN-terminated bearers to MN-terminated bearers and reconfigure the QoE for the terminal device. Additionally or alternatively, the first configuration information may include information indicative of releasing QoE configured by SN to the terminal device. Additionally or alternatively, the first configuration information may include information indicative of providing a policy to SN to indicate SN’s behaviour with respect to QoE handling in case of SN release. Additionally or alternatively, the first configuration information may include information indicative of whether SN shall provide assistance information to MN with respect to QoE configuration in case SN has configured QoE to the terminal device and now being released.
[0103] Continuing with reference to Fig. 4, the SN 410 and the MN 420 may communicate with each other information about the QoE configuration at 411. For example, the MN 420 and SN 410 may negotiate with each other to identify which node configures the terminal device 440 with management-based QoE and which node configures the terminal device 440 with the first QoE configuration. At 411, the MN 420 and SN 410 may also communicate with each other information on the first QoE configuration. The information on the first QoE configuration may include the measurement configuration identifier, e.g., RRC identifier or measConfigAppLayerId, and / or the whole first QoE configuration sent to the terminal device 440. The measurement configuration identifier is associated with the first QoE configuration. The SN 410 may provide the MN 420 information on the first QoE configuration. Moreover, the MN 420 may further indicate a flag or indication to SN 410 indicating that MN 420 will receive an update about QoE reports (e.g., QoE measurement results) from the SN 410 during a period that SCG reporting leg is available for transmission of a QoE measurement report.
[0104] As shown in Fig. 4, the SN 410 may transmit a first QoE configuration to the terminal device 440 and configures the terminal device 440 with the first QoE configuration at 403. The first QoE configuration is used to configure the terminal device 440 with QoE measurements and QoE reporting. In some embodiments, the SN 410 configures the terminal device 440 with the first QoE configuration via SRB3. In some other embodiments, the SN 410 may transmit the first QoE configuration to the MN 420 via an Xn interface, and the MN 420 may embed or encapsulate the first QoE configuration and forward the embedded or encapsulated first QoE configuration to the terminal device 440 using SRB1.
[0105] The terminal device 440 includes an AS layer 442 and an APP layer 444. The QoE configuration is received by the AS layer 442 and provided to the APP layer 444 at 413. Upon receiving the first QoE configuration, the APP layer 444, may perform QoE measurements and may determine the App measurement is available at 404. The APP layer may transmit a QoE measurement report including QoE measurement results to AS layer 442. For example, the APP layer 444 may transmit AppLayerMeasurement including QoE reports at 405 to the AS layer 442 of the terminal device 440. In some embodiments, the QoE reports may be transmitted to the SN 410, which is a consumer node of the QoE reports at this stage, and accordingly, the SN 410 receives the QoE reports at 406.
[0106] In some embodiments, the SN 410 may receive the QoE measurements from the terminal device 440. SN 410 may receive the QoE measurement results directly from the AS layer 442 of the terminal device 440 via SRB3 or via the MN 410. In some embodiments, based on the first configuration from the OAM 470 or based on the flag or indication received at 411, the SN 410 may forward the QoE measurement results to the MN 420 during a period when the SCG reporting leg is available for transmission of the QoE measurement results according to the first QoE configuration. For example, the SN 410 may forward the MN 420 statistics about the QoE measurement reports either in average measurements or in full measurements, which facilitates a more adequate second configuration to be performed by the MN 420. In some embodiments, the SN 410 may transmit the MN 420 the QoE measurement reports.
[0107] At 425, the QoE measurements may also be transmitted to the MCE / TCE 460 from the SN 410. SCG leg may fail or the SN may be released, as shown at 426 in Fig. 4. In some embodiments, the terminal device 440 may determine unavailability of a reporting leg, e.g. SCG reporting leg, for transmission of a QoE measurement report. The terminal device 440 may determine the unavailability of the SCG reporting leg based on an occurrence of a SCG failure or based on an occurrence of the SN being released. Upon determining that the SCG reporting leg is unavailable for transmitting a QoE measurement report, the terminal device 440 may transmit information on the unavailability of the SCG reporting leg to the second node, which is the MN 420 in the first scenario.
[0108] In some embodiments, based on the first configuration from the OAM 470 or based on the flag or indication received at 411, SN 410 may forward to MN 420 statistics about QoE measurement reports and / or suggestion associated with a data radio bearer (DRB) to be configured based on previous QoE measurement reports, before SN 410 is released, as shown at 427 in Fig. 4. In some embodiments, the QoE measurement statistics may be in a form of average or full measurements. SN 410 may indicate MN 420 bearers to configure for the terminal device 440 based on previously collected QoE measurement results. The SN 410 may provide the suggestion about DRB to the MN 420. In some embodiments, SN 410 may determine at least one bearer configuration suggestion based on the at least one QoE measurement report and at least one bearer distributed to the first QoE configuration, and transmit the at least one bearer configuration suggestion to the MN 420. The exchange of information may be applied using SN release message for instance. Additionally, an Xn interface between MN 420 and SN 410 is enhanced such that MN 420 and SN 410 may exchange information with respect to measured QoE metrics to help MN 420 reconfigure the terminal device 440 with the adequate QoE configuration in case of SCG failure or SN release.
[0109] It should be noted that, although the statistics about QoE measurement reports and / or suggestion associated with a data radio bearer (DRB) to be configured are transmitted to the MN 420 at 407 before SN 410 is released, the statistics about QoE measurement reports and / or suggestion associated with a data radio bearer (DRB) to be configured may be transmitted to the MN 410 periodically.
[0110] Now referring back to Fig. 4, the MN 420, in response to the information received from the terminal device 440, may perform second configuration for the terminal device 440 at 409. For example, the MN 420 may reconfigure the QoE configuration for the terminal device 440, maintain the first QoE configuration as configured by the SN 410, or release QoE configuration from the terminal device 440. The procedure 409 will be described in detail in combination with Figs. 5A-5B.
[0111] Fig. 5A illustrates an example signaling process 500 for performing second configuration for the terminal device according to some embodiments of the present disclosure. The MN 420 as shown in Fig. 5A may reconfigure QoE configuration for the terminal device 440. Specifically, the MN 420 may determine to reconfigure the terminal device 440 with QoE reconfiguration at 501. In some embodiments, MN 420 may determine to reconfigure the terminal device 440 with QoE reconfiguration based on the second configuration information provided by the OAM 470.
[0112] Continuing with reference to Fig. 5A, the MN 420 may transmit second configuration with QoE reconfiguration to the terminal device 440 at 502. The MN 420 may transmit RRCReconfiguration message including the QoE reconfiguration to the terminal device 440, and the QoE reconfiguration may include updated configuration of the first QoE configuration. The updated configuration may include one or more of at least one updated QoE configuration parameter or a measurement configuration identifier associated with the second configuration, e.g., measConfigAppLayerId. In some embodiments, MN 420 may transmit an RRCReconfiguration to the terminal device 440, such as an AS layer 442 of the terminal device 440, indicating the update in the previous QoE configuration with a measurement configuration identifier associated with the previous QoE configuration.
[0113] In some alternative embodiments, MN 420 may transmit an RRCReconfiguration to the terminal device 440, such as an AS layer 442 of the terminal device 440, indicating the update in the previous QoE configuration with a measurement configuration identifier associated with the QoE reconfiguration. In some embodiments, MN 420 may transmit an RRCReconfiguration to the terminal device 440, such as an AS layer 442 of the terminal device 440, including previous QoE configuration with a measurement configuration identifier associated with the QoE reconfiguration, which indicates configure the terminal device 440 with the first QoE configuration as configured by the first node 410. The AS layer 442 of the terminal device 440 may forward the updated QoE configuration to the AP layer 444 for further processing, as shown at 503 in Fig. 5A.
[0114] Fig. 5B illustrates another example signaling process 500’ for performing second configuration for the terminal device according to some embodiments of the present disclosure. The MN 420 as shown in Fig. 5B may release the first QoE configuration. Specifically, the MN 420 may determine to release the first QoE configuration at 511. In some embodiments, MN 420 may determine to release the first QoE configuration based on the second configuration information provided by the OAM 470. In some embodiments, the release information indicates release of the first QoE configuration, and may include a measurement configuration identifier associated with the first QoE configuration. In some embodiments, the measurement configuration identifier may include, but not limited to, RRC identifier, or measConfigAppLayerId. Accordingly, the terminal device 440 may be configured based on the QoE reconfiguration.
[0115] In some embodiments, the AS layer 442 of the terminal device 440 may receive the release information at 512 and forward the release information to the APP layer 444 of the terminal device 440 at 513. Based on the received release information, the APP layer 444 terminates the QoE measurements. For example, based on the measurement configuration identifier associated with the first QoE configuration, the terminal device 440 may decide to release the first QoE configuration, and terminate the QoE measurements.
[0116] In some embodiments, the second configuration may also instruct the terminal device 440 to maintain the previously configured first QoE configuration. For example, the second configuration transmitted by MN 420 may include an indication or a flag with a preset value to indicate the terminal device 440 to maintain the previously configured first QoE configuration. It should be understood that, other formats of the second configuration may be employed by the MN 420 to inform the terminal device 440 to maintain the previously QoE configuration.
[0117] In some embodiments, the terminal device 440, upon determining the unavailability of the reporting leg, may start counting, for example, start a timer. The terminal device 440, based on a determination that a predetermined time period has been elapsed without receiving the second configuration from the second node, may release the first QoE configuration or may continue performing QoE measurements according to the first QoE configuration. The predetermined time period is preset and may be configured to any time period.
[0118] Fig. 6 illustrates an example signaling process 600 for performing QoE configuration in a second scenario. In the second scenario, the source MN 610 of the dual connectivity configures the terminal device 640 with a first QoE configuration and provides the bearers to the terminal device 640 for the service. The dual connectivity also includes SN 630, which is connected to the terminal device 640. Accordingly, the source MN 610 is the consumer of the QoE measurement report during a time period when a MCG reporting leg is available for transmission of a QoE measurement report according to the first QoE configuration.
[0119] When a MCG failure occurs, the MCG reporting leg is unavailable for transmission of a QoE measurement report, the terminal device 640 may determine this unavailability, and a second MN (may either be a target MN 620 or the SN 630) may reconfigure the terminal device 640 with a second configuration, which is indicative of a QoE reconfiguration, maintenance of the first QoE configuration, or release of the first QoE configuration. Accordingly, the consumer node is changed from the source MN 610 to the second MN, which may include the target MN 620 or the SN 630. The second MN may receive the QoE measurement results measured and reported based on the second configuration. In some embodiments, the source MN 610 and the SN 630 are in the same dual connectivity.
[0120] Now referring to the process 600 of Fig. 6, the OAM 670 may transmit first configuration information (e.g., QoE measurement configuration) to the source MN 610 indicative of QoE handling at least during a time period that the MCG reporting leg is unavailable for transmission of the QoE measurement report at 601. The OAM 670 may further transmit second configuration information (e.g., QoE measurement configuration) to the target MN 620 indicative of QoE handling at least during a time period that the MCG reporting leg is unavailable for transmission of the QoE measurement report.
[0121] In some embodiments, the configuration information provided to the source MN 610 and the target MN 620 may indicate MN’s behaviour with respect to QoE handling at least during a time period that the MCG reporting leg is unavailable for transmission of the QoE measurement report. The second configuration information may indicate in case the source MN 610 has configured the terminal device with the first QoE configuration and the MCG reporting leg is unavailable, the target MN 620 may either reconfigure the terminal device with a QoE reconfiguration, maintenance of the first QoE configuration, or release the first QoE configuration configured by the source MN 610. The first configuration information may instruct the source MN 610 to provide assistance information to the second node (including the target MN 620 or SN 630) with respect to the QoE configuration to facilitate QoE reconfiguration.
[0122] Continuing with reference to Fig. 6, the source MN 610 and the SN 630 may communicate with each other information about the QoE configuration at 611. For example, the source MN 610 and SN 630 may negotiate with each other to identify which node configures the terminal device 640 with QoE configuration and which node configures the terminal device 640 with the first QoE configuration. At 611, the source MN 610 and SN 630 may also communicate with each other information on the first QoE configuration. The information on the first QoE configuration may include the measurement configuration identifier, e.g., RRC identifier or measConfigAppLayerId, and / or the whole first QoE configuration sent to the terminal device 640. The measurement configuration identifier is associated with the first QoE configuration. The source MN 610 may inform the SN 630 information on the first QoE configuration.
[0123] As shown in Fig. 6, the source MN 610 may transmit the first QoE configuration to the terminal device 640 and configure the terminal device 640 with the first QoE configuration, as shown at 603 in Fig. 6. The first QoE configuration is used to configure the terminal device 640 with QoE measurement configuration and QoE measurement reporting.
[0124] In some embodiments, the terminal device 640 may include an access stratum (AS) layer 642 and an application (AP) layer 644. The AS layer 642 of the terminal device 640 may receive the first QoE configuration and forward the first QoE configuration to the APP layer 644 at 613. The APP layer 644 of the terminal device 640 may perform QoE measurements and may determine that the App measurements are available at 604. The App layer 644 may further transmit QoE measurement results to AS layer 642 at 605 via the AppLayerMeasurement message including the QoE measurement results, which are then forwarded to the source MN 610, at 606. In some embodiments, the source MN 610 may further transmit the QoE measurement results to the MCE / TCE 660 via an AppLayerMeasurement message, at 625.
[0125] An MCG failure may occur at 607, which cause an MCG reporting leg unavailability to transmit a QoE report. The terminal device 640 may determine unavailability of the MCG reporting leg for transmission of a QoE measurement report. The terminal device 640 may determine the unavailability of the MCG reporting leg based on an occurrence of an MCG failure. Upon determining that the MCG reporting leg is unavailable for transmitting a QoE measurement report, the terminal device 640 may establish a connection with a cell that is controlled by the second MN at 608. The detailed explanation of establishing the connection will be described in detail with reference to Fig. 7.
[0126] Based on the connection establishment made at 608, the cell of the second MN may be selected. The second MN may include a target MN 620. The second MN may include SN 630, alternatively. If the cell of the target MN 620 is selected as the second MN, the target MN 620 may retrieve UE context information from the source MN 610 containing the first QoE configuration.
[0127] In some embodiments, the terminal device 640 may re-select the cell of the target MN 620, and the target MN 620 may be as the second MN, for example, in a situation when the terminal device 640 is not configured with a fast MCG recovery. If the target MN 620 includes an Xn interface with the MN 610 in a previous dual connectivity, the target MN 620 may retrieve the first QoE configuration configured for the terminal device 640.
[0128] In some other embodiments, the terminal device 640 configured with the fast MCG recovery, may handover to a new cell which is controlled by the second MN including the target MN 620 or the SN 630. The Xn interface of the second MN may be used to transfer the QoE measurement configuration (QMC) information within the handover request command. The NG interface may be used where the QMC configuration information is contained in the Node Transparent Container included in the handover command.
[0129] In some embodiments, the second MN may include the target MN 620, and in other embodiments, the second MN may be the previous SN 630. In some embodiments, as explained above, the source MN 610 may also transmit context information of the terminal device to the target MN 620. The target MN 620 may perform second configuration at 609 to reconfigure QoE configuration for the terminal device 640 or release the first QoE configuration. The operations performed at 609 are similar to those as described in combination with Fig. 5A and Fig. 5B, and will not repetitively described for the purposes of clarity and brevity. In some embodiments, the second configuration may configure the terminal device 640 to maintain the first QoE configuration. The implementation of maintaining the first QoE configuration is similar to those as described in combination with Fig. 3, and the repetitive description is omitted herein for the purposes of clarity and brevity.
[0130] Now the detailed description about establishment of a connection at 608 will be described with reference to Fig. 7. Fig. 7 illustrates an example signaling process 700 for performing an establishment of a connection with a cell controlled by the second MN when an MCG reporting leg is unavailable according to some embodiments of the present disclosure. The terminal device 640 as shown in Fig. 7 is configured with a fast MCG recovery. In some embodiments, at 702, the terminal device 640 may report the MCG failure to the source MN 610 through the SN 630 when an MCG failure occurs. The source MN 610 may transmit an instruction to the terminal device at 704. In some embodiments, the instruction may instruct the terminal device 640 to handover to a cell that is controlled by the second master node or to release a connection of the terminal device 640. If the instruction from the source MN 610 instructs the terminal device 640 to handover to a new cell, then the terminal device 640 may handover to a cell which is controlled by a second MN including the target MN 620 or the previous SN 630, and the second MN is a consumer node of the QoE measurement report during a time period that the MCG reporting leg is unavailable of transmission of the QoE measurement report according to the first QoE configuration. In some embodiments, the second MN may include the target MN 620, and in other embodiments, the second MN may be the previous SN 630.
[0131] Alternatively, if the terminal device 640 is not configured with the fast MCG recovery, the terminal device 640 may reselect and camp to a new cell which may be controlled by the second MN including target MN 620 or the previous SN 630.
[0132] Fig. 8 illustrates a flowchart of a method implemented at a terminal device in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the terminal device 140 with reference to Fig. 1.
[0133] At 820, the terminal device 140 receives, in dual connectivity operation, a first quality of experience (QoE) configuration configured by a first node. At 840, the terminal device 140 determines unavailability of a reporting leg for transmission of a QoE measurement report according to the received configuration. At 860, the terminal device 140 transmits information on the unavailability of the reporting leg to a second node. In some embodiments, the second node is different from the first node. At 880, the terminal device 140 receives, from the second node, a second configuration. In some embodiments, the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration, or release of the first QoE configuration.
[0134] In some embodiments, the terminal device 140 may provide, from a first layer of the terminal device, information on the second configuration to a second layer of the terminal device.
[0135] In some embodiments, the terminal device 140 may transmit, in the dual connectivity, the QoE measurement report to the first node during a time period that the reporting leg is available for transmission of the QoE measurement report.
[0136] In some embodiments, a consumer node of the QoE measurement report is changed from the first node to the second node during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.
[0137] In some embodiments, the QoE reconfiguration may include updated configuration of the first QoE configuration, and the updated configuration may include one or more of the following: at least one updated QoE configuration parameter; or a measurement configuration identifier associated with the second configuration.
[0138] In some embodiments, the second configuration may include release information to indicate release of the first QoE configuration, and wherein the release information may include a measurement configuration identifier associated with the first QoE configuration.
[0139] In some embodiments, the terminal device 140 may start counting based on a determination of the unavailability of the reporting leg, and based on a determination that a predetermined time period has been elapsed without receiving the second configuration from the second node, release the first QoE configuration or continue performing QoE measurements according to the first configuration.
[0140] In some embodiments, the first node is a secondary node (SN) in the dual connectivity, and a determination of the unavailability of the reporting leg is made based on an occurrence of a secondary cell group, SCG, failure or based on an occurrence of the SN being released.
[0141] In some embodiments, the first node is a master node (MN) in the dual connectivity, and wherein a determination of the unavailability of the reporting leg is made based on an occurrence of master cell group (MCG) failure.
[0142] In some embodiments, the terminal device may report the MCG failure to the first node through a secondary node based on the occurrence of the MCG failure, and the terminal device is configured with a fast MCG recovery. And the terminal device may receive an instruction from the first node, wherein the instruction instructs the terminal device to handover to a cell that is controlled by a second node or to release a connection of the terminal device.
[0143] In some embodiments, the terminal device may handover to a cell which is controlled by the second node, and the second node is a consumer node of the QoE measurement report at least during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.
[0144] In some embodiments, QoE configuration comprises radio access network visible quality of experience (RVQoE) or container-based QoE; QoE measurement report comprises RVQoE measurement report or container-based QoE measurement report; and QoE reconfiguration comprises RVQoE reconfiguration or container-based QoE reconfiguration.
[0145] FIG. 9 illustrates a flowchart 900 of a method implemented at a network device in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described from the perspective of the network device. The network device may include the node 110 or the node 120 or the node 130 in Fig. 1.
[0146] At block 920, the network device receives, from a terminal device, information on unavailability of a reporting leg for transmission of a quality of experience (QoE) measurement report according to a first QoE configuration. At 940, the network device transmits, to the terminal device, a second configuration indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0147] In some embodiments, the first QoE configuration is used by a first network device to configure the terminal device.
[0148] In some embodiments, a consumer node of the QoE measurement report is changed from the first network device to the network device during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration, and wherein the network device is a master node (MN) of the dual connectivity.
[0149] In some embodiments, the QoE reconfiguration may include updated configuration of the first QoE configuration, and the updated configuration may include at least one of: at least one updated QoE configuration parameter; or a measurement configuration identifier associated with the second configuration.
[0150] In some embodiments, the second configuration may include release information to indicate release of the first QoE configuration, and the release information may include a measurement configuration identifier associated with the first QoE configuration.
[0151] In some embodiments, the network device may receive configuration information from an operation administration and maintenance (OAM) , and the configuration information is indicative of QoE handling at least during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.
[0152] In some embodiments, QoE configuration comprises radio access network visible quality of experience (RVQoE) or container-based QoE; QoE measurement report comprises RVQoE measurement report or container-based QoE measurement report; and QoE reconfiguration comprises RVQoE reconfiguration or container-based QoE reconfiguration.
[0153] FIG. 10 illustrates a flowchart 1000 of a method implemented at a network device in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described from the perspective of the network device. The network device may include the node 110 or the node 120 in Fig. 1.
[0154] In some embodiments, at 1020, the network device may transmit a first quality of experience (QoE) configuration to a terminal device. At 1040, the network device may receive at least one QoE measurement report according to the first QoE configuration. At 1060, the network device may transmit information associated with the received at least one QoE measurement report to another network device.
[0155] In some embodiments, the information associated with the received at least one QoE measurement report is used to configure a second configuration, and the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0156] In some embodiments, the QoE reconfiguration may include updated configuration of the first QoE configuration, and wherein the updated configuration may include at least one of: at least one updated QoE configuration parameter; or a measurement configuration identifier associated with the second configuration.
[0157] In some embodiments, the second configuration may include release information to indicate release of the first QoE configuration, and wherein the release information may include a measurement configuration identifier associated with the first QoE configuration.
[0158] In some embodiments, the network device is a secondary node (SN) in the dual connectivity, and the another network device is a master node (MN) in the dual connectivity.
[0159] In some embodiments, the network device may determine at least one bearer configuration suggestion based on the at least one QoE measurement report and at least one bearer distributed to the first QoE configuration, and transmit at least one bearer configuration suggestion to another network device.
[0160] In some embodiments, QoE configuration comprises radio access network visible quality of experience (RVQoE) or container-based QoE; QoE measurement report comprises RVQoE measurement report or container-based QoE measurement report; and QoE reconfiguration comprises RVQoE reconfiguration or container-based QoE reconfiguration.
[0161] In some example embodiments, an apparatus capable of performing the method 800 (for example, the terminal device) may include means for performing the respective steps of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0162] In some embodiments, the apparatus comprises means for receiving, in dual connectivity operation, a first quality of experience (QoE) configuration configured by a first node. The apparatus may include means for determining unavailability of a reporting leg for transmission of a QoE measurement report according to the received configuration. The apparatus may include means for transmitting information on the unavailability of the reporting leg to a second node. In some embodiments, the second node is different from the first node. The apparatus may include means for receiving, from the second node, a second configuration. In some embodiments, the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0163] In some embodiments, the apparatus may include means for providing, from a first layer of the terminal device, information on the second configuration to a second layer of the terminal device.
[0164] In some embodiments, the apparatus may include means for transmitting, in the dual connectivity, the QoE measurement report to the first node during a time period that the reporting leg is available for transmission of the QoE measurement report.
[0165] In some embodiments, a consumer node of the QoE measurement report is changed from the first node to the second node during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.
[0166] In some embodiments, the QoE reconfiguration may include updated configuration of the first QoE configuration, and the updated configuration may include one or more of the following: at least one updated QoE configuration parameter; or a measurement configuration identifier associated with the second configuration.
[0167] In some embodiments, the second configuration may include release information to indicate release of the first QoE configuration, and wherein the release information may include a measurement configuration identifier associated with the first QoE configuration.
[0168] In some embodiments, the apparatus may include means for starting counting based on a determination of the unavailability of the reporting leg, and means for releasing the first QoE configuration or continue performing QoE measurements according to the first configuration based on a determination that a predetermined time period has been elapsed without receiving the second configuration from the second node.
[0169] In some embodiments, the first node is a secondary node (SN) in the dual connectivity, and a determination of the unavailability of the reporting leg is made based on an occurrence of a secondary cell group, SCG, failure or based on an occurrence of the SN being released.
[0170] In some embodiments, the first node is a master node (MN) in the dual connectivity, and wherein a determination of the unavailability of the reporting leg is made based on an occurrence of master cell group (MCG) failure.
[0171] In some embodiments, the apparatus may include means for reporting the MCG failure to the first node through a secondary node based on the occurrence of the MCG failure, and the terminal device is configured with a fast MCG recovery. And the apparatus may include means for receiving an instruction from the first node, and the instruction instructs the terminal device to handover to a cell that is controlled by a second node or to release a connection of the terminal device.
[0172] In some embodiments, the apparatus may include means for handovering to a cell which is controlled by the second node, and the second node is a consumer node of the QoE measurement report at least during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.
[0173] In some embodiments, QoE configuration comprises radio access network visible quality of experience (RVQoE) or container-based QoE; QoE measurement report comprises RVQoE measurement report or container-based QoE measurement report; and QoE reconfiguration comprises RVQoE reconfiguration or container-based QoE reconfiguration.
[0174] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 800. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
[0175] In some example embodiments, an apparatus capable of performing the method 900 (for example, the network device) may include means for performing the respective steps of the method 900. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0176] In some embodiments, the apparatus comprises means for receiving, from a terminal device, information on unavailability of a reporting leg for transmission of a quality of experience (QoE) measurement report according to a first QoE configuration. The apparatus may include means for transmitting, to the terminal device, a second configuration indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0177] In some embodiments, the apparatus may include means for receiving, from a first network device, information on the first QoE configuration, and the first QoE configuration is used by the first network device to configure the terminal device.
[0178] In some embodiments, a consumer node of the QoE measurement report is changed from the first network device to the network device during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration, and wherein the network device is a master node (MN) of the dual connectivity.
[0179] In some embodiments, the QoE reconfiguration may include updated configuration of the first QoE configuration, and the updated configuration may include at least one of: at least one updated QoE configuration parameter; or a measurement configuration identifier associated with the second configuration.
[0180] In some embodiments, the second configuration may include release information to indicate release of the first QoE configuration, and the release information may include a measurement configuration identifier associated with the first QoE configuration.
[0181] In some embodiments, the apparatus may include means for receiving configuration information from an operation administration and maintenance (OAM) , and the configuration information is indicative of QoE handling at least during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.
[0182] In some embodiments, QoE configuration comprises radio access network visible quality of experience (RVQoE) or container-based QoE; QoE measurement report comprises RVQoE measurement report or container-based QoE measurement report; and QoE reconfiguration comprises RVQoE reconfiguration or container-based QoE reconfiguration.
[0183] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 900. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
[0184] In some example embodiments, an apparatus capable of performing the method 1000 (for example, the network device) may include means for performing the respective steps of the method 1000. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0185] In some example embodiments, the apparatus may include means for transmitting a first quality of experience (QoE) configuration to a terminal device. The apparatus may include means for receive at least one QoE measurement report according to the first QoE configuration. The apparatus may further include means for transmitting information associated with the received at least one QoE measurement report to another network device..
[0186] In some embodiments, the information associated with the received at least one QoE measurement report is used to configure a second configuration, and the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.
[0187] In some embodiments, a consumer node of the QoE measurement report is changed from the network device to another network device during a time period that a reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.
[0188] In some embodiments, the QoE reconfiguration may include updated configuration of the first QoE configuration, and wherein the updated configuration includes at least one of: at least one updated QoE configuration parameter; or a measurement configuration identifier associated with the second configuration.
[0189] In some embodiments, the second configuration may include release information to indicate release of the first QoE configuration, and wherein the release information may include a measurement configuration identifier associated with the first QoE configuration.
[0190] In some embodiments, the network device is a secondary node (SN) in the dual connectivity, and the another network device is a master node (MN) in the dual connectivity.
[0191] In some embodiments, the apparatus may include means for determining at least one bearer configuration suggestion based on the at least one QoE measurement report and at least one bearer distributed to the first QoE configuration, and means for transmitting at least one bearer configuration suggestion to the another network device.
[0192] In some embodiments, QoE configuration comprises radio access network visible quality of experience (RVQoE) or container-based QoE; QoE measurement report comprises RVQoE measurement report or container-based QoE measurement report; and QoE reconfiguration comprises RVQoE reconfiguration or container-based QoE reconfiguration.
[0193] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1000. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
[0194] FIG. 11 illustrates a simplified block diagram of a device 1100 that is suitable for implementing some example embodiments of the present disclosure. The device 1100 may be provided to implement a device, for example, the terminal device, the source MN, the SN, or the target MN as shown in Figs. 1-7. As shown, the device 1100 includes one or more processors 1110, one or more memories 1120 coupled to the processor 1110, and one or more communication modules 1140 coupled to the processor 1110.
[0195] The communication module 1140 is for bidirectional communications. The communication module 1140 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network elements.
[0196] The processor 1110 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1100 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0197] The memory 1120 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1124, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 1122 and other volatile memories that will not last in the power-down duration.
[0198] A computer program 1130 includes computer executable instructions that are executed by the associated processor 1110. The program 1130 may be stored in the ROM 1124. The processor 1110 may perform any suitable actions and processing by loading the program 1130 into the RAM 1122.
[0199] The embodiments of the present disclosure may be implemented by means of the program 1130 so that the device 1100 may perform any process of the disclosure as discussed with reference to Figs. 3 to 10. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0200] In some example embodiments, the program 1130 may be tangibly contained in a computer readable medium which may be included in the device 1100 (such as in the memory 1120) or other storage devices that are accessible by the device 1100. The device 1100 may load the program 1130 from the computer readable medium to the RAM 1122 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
[0201] FIG. 12 illustrates a block diagram of an example of a computer readable medium 1200 in accordance with some example embodiments of the present disclosure. The computer readable medium 1200 has the program 1130 stored thereon. It is noted that although the computer readable medium 1200 is depicted in form of CD or DVD in FIG. 12, the computer readable medium 1200 may be in any other form suitable for carry or hold the program 1130.
[0202] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0203] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method 800, 900, or 1000 as described above with reference to Figs. 8-10. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0204] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0205] In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0206] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
[0207] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.
[0208] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.A terminal device comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to:receive, in dual connectivity operation, a first quality of experience, QoE, configuration configured by a first node;determine unavailability of a reporting leg for transmission of a QoE measurement report according to the received configuration;transmit information on the unavailability of the reporting leg to a second node, wherein the second node is different from the first node; andreceive, from the second node, a second configuration, wherein the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.2.The terminal device of claim 1, wherein the terminal device is further caused to:provide, from a first layer of the terminal device, information on the second configuration to a second layer of the terminal device.3.The terminal device of claim 1 or 2, wherein the terminal device is further caused to:transmit, in the dual connectivity, the QoE measurement report to the first node during a time period that the reporting leg is available for transmission of the QoE measurement report.4.The terminal device of any of claims 1 to 3, wherein a consumer node of the QoE measurement report is changed from the first node to the second node during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.5.The terminal device of any of claims 1 to 4, wherein the QoE reconfiguration comprises updated configuration of the first QoE configuration, and wherein the updated configuration comprises at least one of:at least one updated QoE configuration parameter; ora measurement configuration identifier associated with the second configuration.6.The terminal device of any of claims 1 to 4, wherein the second configuration comprises release information to indicate release of the first QoE configuration, and wherein the release information comprises a measurement configuration identifier associated with the first QoE configuration.7.The terminal device of any of claims 1 to 6, wherein the terminal device is further caused to:start counting based on a determination of the unavailability of the reporting leg; andbased on a determination that a predetermined time period has been elapsed without receiving the second configuration from the second node, release the first QoE configuration or continue performing QoE measurements according to the first configuration.8.The terminal device of any of claims 1 to 7, wherein the first node is a secondary node, SN, in the dual connectivity, and wherein a determination of the unavailability of the reporting leg is made based on an occurrence of a secondary cell group, SCG, failure or based on an occurrence of the SN being released.9.The terminal device of any of claims 1 to 7, wherein the first node is a master node, MN, in the dual connectivity, and wherein a determination of the unavailability of the reporting leg is made based on an occurrence of master cell group, MCG, failure.10.The terminal device of claim 9, wherein the terminal device is further caused to:report the MCG failure to the first node through a secondary node, SN based on the occurrence of the MCG failure, wherein the terminal device is configured with a fast MCG recovery; andreceive an instruction from the first node, wherein the instruction instructs the terminal device to handover to a cell that is controlled by the second node or to release a connection of the terminal device.11.The terminal device of claim 10, wherein the terminal device is further caused to:handover to a cell which is controlled by the second node,wherein the second node is a consumer node of the QoE measurement report at least during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.12.The terminal device of any of claims 1 to 11, wherein QoE configuration comprises radio access network visible quality of experience, RVQoE configuration; or container-based QoE configuration;QoE measurement report comprises RVQoE measurement report or container-based QoE measurement report; andQoE reconfiguration comprises RVQoE reconfiguration or container-based QoE reconfiguration.13.A network device configured to provide a dual connectivity to a terminal device with another network device, the network device comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to:receive, from a terminal device, information on unavailability of a reporting leg for transmission of a quality of experience, QoE, measurement report according to a first QoE configuration; andtransmit, to the terminal device, a second configuration indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.14.The network device of claim 13, wherein the first QoE configuration is used by a first network device to configure the terminal device.15.The network device of claim 14, wherein a consumer node of the QoE measurement report is changed from the first network device to the network device during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration, and wherein the network device is a master node, MN, of the dual connectivity.16.The network device of any of claims 13 to 15, wherein the QoE reconfiguration comprises updated configuration of the first QoE configuration, and wherein the updated configuration comprises at least one of:at least one updated QoE configuration parameter; ora measurement configuration identifier associated with the second configuration.17.The network device of any of claims 12 to 16, wherein the second configuration comprises release information to indicate release of the first QoE configuration, and wherein the release information comprises a measurement configuration identifier associated with the first QoE configuration.18.The network device of any of claims 13 to 17, wherein the network device is further caused to:receive configuration information from an operation administration and maintenance, OAM,wherein the configuration information is indicative of QoE handling at least during a time period that the reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.19.The network device of any of claims 13 to 18, wherein QoE configuration comprises radio access network visible quality of experience, RVQoE configuration; or container-based QoE configuration;QoE measurement report comprises RVQoE measurement report or container-based QoE measurement report; andQoE reconfiguration comprises RVQoE reconfiguration or container-based QoE reconfiguration.20.A network device, configured to provide a dual connectivity to a terminal device with another network device, the network device comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to:transmit a first quality of experience, QoE, configuration to a terminal device;receive at least one QoE measurement report according to the first QoE configuration; andtransmit information associated with the received at least one QoE measurement report to another network device.21.The network device of claim 20, wherein the information associated with the received at least one QoE measurement report is used to configure a second configuration, and the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.22.The network device of claim 20 or 21, wherein a consumer node of the QoE measurement report is changed from the network device to the another network device during a time period that a reporting leg is unavailable for transmission of the QoE measurement report according to the first QoE configuration.23.The network device of any of claims 20 to 22, wherein the QoE reconfiguration comprises updated configuration of the first QoE configuration, and wherein the updated configuration comprises at least one of:at least one updated QoE configuration parameter; ora measurement configuration identifier associated with the second configuration.24.The network device of any of claims 20 to 22, wherein the second configuration comprises release information to indicate release of the first QoE configuration, and wherein the release information comprises a measurement configuration identifier associated with the first QoE configuration.25.The network device of any of claims 20 to 24, wherein the network device is a secondary node, SN, in the dual connectivity, and the another network device is a master node, MN, in the dual connectivity.26.The network device of claim 25, wherein the network device is further caused to:determine at least one bearer configuration suggestion based on the at least one QoE measurement report and at least one bearer distributed to the first QoE configuration; andtransmit the at least one bearer configuration suggestion to the another network device.27.The network device of any of claims 20 to 26, wherein QoE configuration comprises radio access network visible quality of experience, RVQoE, or container-based QoE;QoE measurement report comprises RVQoE measurement report or container-based QoE measurement report; andQoE reconfiguration comprises RVQoE reconfiguration or container-based QoE reconfiguration.28.A method comprising:receiving, in dual connectivity operation, a first quality of experience, QoE, configuration configured by a first node;determining unavailability of a reporting leg for transmission of a QoE measurement report according to the received configuration;transmitting information on the unavailability of the reporting leg to a second node, wherein the second node is different from the first node; andreceiving, from the second node, a second configuration, wherein the second configuration is indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.29.A method, comprising:receiving, from a terminal device, information on unavailability of a reporting leg for transmission of a quality of experience, QoE, measurement report according to a first QoE configuration; andtransmitting, to the terminal device, a second configuration indicative of a QoE reconfiguration, maintenance of the first QoE configuration or release of the first QoE configuration.30.A method, comprising:transmitting a first quality of experience, QoE, configuration to a terminal device;receiving at least one QoE measurement report according to the first QoE configuration; andtransmitting information associated with the received at least one QoE measurement report to another network device.31.An apparatus comprising:means for receiving, in dual connectivity operation, a first quality of experience, QoE, configuration configured by a first node;means for determining unavailability of a reporting leg for transmission of a QoE measurement report according to the received configuration;means for transmitting information on the unavailability of the reporting leg to a second node, wherein the second node is different from the first node; andmeans for receiving, from the second node, a second configuration, wherein the second configuration is indicative of a QoE reconfiguration, or release of the first QoE configuration.32.An apparatus comprising:means for receiving, from a terminal device, information on unavailability of a reporting leg for transmission of a quality of experience, QoE, measurement report according to a first QoE configuration; andmeans for transmitting, to the terminal device, a second configuration indicative of a QoE reconfiguration or release of the first QoE configuration.33.An apparatus comprising:means for transmitting a first quality of experience, QoE, configuration to a terminal device;means for receiving at least one QoE measurement report according to the first QoE configuration; andmeans for transmitting information associated with the received at least one QoE measurement report to another network device.34.A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of claim 28, 29, or 30.
Citation Information
Patent Citations
Communication Method and Apparatus for Sending Quality of Experience Measurement Result
US20230115085A1
Handling of quality-of-experience (QOE) measurement status
WO2022164380A1
Multi-connectivity with quality of experience measurement
WO2023283113A1
Cited By
Priority setting for quality of experience
US12628025B2
Priority setting for quality of experience
US20240236745A1
