Managing the experience quality report after recovery from a failure

Abstract

A Radio Access Network (RAN), Core Network (CN), or Operation and Maintenance (OAM) node and a User Equipment (UE) may implement a method for managing Quality of Experience (QoE) reporting from a UE, the method including receiving, by processing hardware, a request from the UE to re-establish a radio connection, obtaining, by the processing hardware, a configuration for QoE reporting, and at least one of (i) facilitating, by the processing hardware thereafter, reporting of QoE measurements for the UE to a QoE node, or (ii) releasing the configuration.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a wireless communication system that manages experience quality measurement collection and experience quality reporting during mobility transitions and / or state transitions.

Background Art

[0002] Mobile networks are enhanced to improve the user experience. For this reason, the evaluation of the user experience on the UE side is useful to network operators. Specifically, such an evaluation is useful even when the operator provides real-time services that require, for example, high data rates and low latency, where intermittent quality degradation can interrupt the user experience. Such real-time services include streaming services (typically video services), multimedia telephony services for Internet Multimedia Subsystem (MTSI), multicast services and / or broadcast services (MBS), and / or extended reality (XR) services. The success of implementing real-time services increases mobile traffic, and thus the focus is aligned with the end-user experience.

[0003] Generally speaking, Quality of Experience (QoE) measurement collection (QMC) provides detailed information about the User Equipment (UE) at the call (also called "application session") level. These measurements can provide information that cannot be derived by network operators based on Radio Access Network (RAN) measurements or Core Network (CN) measurements. The UE can collect QoE information and provide that information to a management system for analysis and / or Key Performance Indicator (KPI) calculation. The collected QoE information can be used by the management system, the CN, or the RAN for machine learning to optimize the operation of the CN or the RAN.

[0004] In a wireless communication system, a base station supporting a certain Radio Access Technology (RAT) communicates with a User Equipment (UE) using, among other protocols, a protocol for controlling radio resources corresponding to that RAT in particular. The protocol for controlling radio resources may be, for example, the Radio Resource Control (RRC) protocol utilized by 4G, 5G, 6G, or later-generation wireless communication systems. Once a wireless connection is established via the base station, the UE operates in a connected state of the protocol for controlling radio resources, which may be specific to the RAT (e.g., EUTRA-RRC CONNECTED, NR-RRC CONNECTED).

[0005] In the LTE system, the QMC function enables the collection of application layer measurements from the UE. The supported service types can include streaming services and MTSI services. The trace function from the Minimization of Drive Test (MDT) framework activates the QMC. LTE supports signaling-based start cases and management-based start cases. For signaling-based cases, the collection of application layer measurements is initiated from the CN node to a specific UE using the MDT mechanism. For management-based cases, the collection of application layer measurements is initiated from an operations, administration, and management (OAM) node targeting a certain area (without targeting a specific UE).

[0006] As described in 3GPP (registered trademark, the same hereinafter) specifications 28.405 v16.0.0, 36.300 v16.6.0, and 36.331 v16.5.0, a transparent container encapsulates the application layer measurement configuration received from the OAM node or the CN and transfers it to the UE by the radio access network (RAN) in a downlink RRC message. After receiving the application layer measurement collection configuration, the UE encapsulates the application layer measurements and transmits the measurements to the network in an uplink RRC message. The application layer measurement configuration and the application layer measurement report are supported only in the RRC_CONNECTED state. The E-UTRAN can release the application layer measurement configuration to the UE at any time.

Prior Art Documents

Non-Patent Documents

[0007]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Summary of the Invention

Means for Solving the Problems

[0008] The network node implements QMC and supports configurations and reports for multiple simultaneous QoE measurements for the UE, for the same or different service types. When a communication failure occurs between the UE and the source node of the RAN, the UE initiates a re-establishment procedure with the target base station of the RAN, and the target base station obtains QoE operation information such as the configuration for QoE reporting from the source node.

[0009] After obtaining the QoE operation information, the target node may facilitate further QoE reporting, or may release the configuration, for example, if the target node does not support QoE operations. Further, the target node may determine whether QoE communication should be suspended or resumed during the re-establishment procedure, and decide to suspend or resume those operations.

[0010] One exemplary embodiment of these techniques is a method for managing QoE reporting for a user equipment (UE) initially configured to report QoE measurements to a QoE node via a source node of a radio access network (RAN), the method being implemented at a target node of the RAN. The method includes receiving, by processing hardware, a request from the UE to re-establish a radio connection, obtaining, by processing hardware, a configuration for QoE reporting, and performing at least one of (i) facilitating, by processing hardware, reporting QoE measurements to a QoE node regarding the UE after obtaining, or (ii) releasing the configuration.

[0011] Another exemplary embodiment of these techniques is a method for managing QoE reports for a user equipment (UE) with respect to a Quality of Experience (QoE) node, the method being implemented at a source node in a radio access network (RAN). The method includes receiving, by processing hardware, a configuration for QoE, receiving, by processing hardware, a request for context regarding the UE from a target base station of the RAN, and in response to the reception, transmitting, by processing hardware, a configuration for QoE reporting regarding the UE to the target node.

[0012] Yet another exemplary embodiment of these techniques is a method for managing Quality of Experience (QoE) reports, the method being implemented at a user equipment (UE). The method includes reporting, by processing hardware, QoE measurements to a QoE node via a radio access network (RAN), detecting, by processing hardware, a communication failure between the UE and a source node of the RAN, in response to the detection, performing, by processing hardware, a radio connection re-establishment procedure with a target node of the RAN, and determining, by processing hardware, to perform a QoE operation in response to receiving an indication from the target node. BRIEF DESCRIPTION OF THE DRAWINGS

[0013]

Fig. 1A

Fig. 1B

Fig. 2A

Fig. 2B

Fig. 3A

Fig. 3B

Fig. 3C

Fig. 3D

Fig. 3E

Fig. 3F

Fig. 3G

Fig. 4A

Fig. 4B

Fig. 4C

Fig. 5

Fig. 6

Fig. 7

Fig. 8

Fig. 9

Fig. 10

Fig. 11

Fig. 12

Fig. 13

Fig. 14

Fig. 15

Mode for Carrying Out the Invention

[0014] A UE, a source node of a RAN, a target node of a RAN, a core network, and / or an operation and maintenance management node implement the technology of the present disclosure for managing QoE measurement and QoE reporting after a communication failure. The target node may receive a command to suspend QoE reporting and / or a command to resume QoE reporting during a re-establishment process. Alternatively, the target node may determine to release and / or change a QoE configuration for QoE reporting during a re-establishment process.

[0015] Specifically, referring first to FIG. 1A, an exemplary wireless communication system 100 includes a UE 102, a source base station (S-BS) 104, a target base station (T-BS) 106, and a core network (CN) 110. Also, the wireless communication system 100 includes an operation and maintenance management node (OAM) 180, as well as a Trace Collection Entity (TCE) and / or a Multicast Coordination Entity (MCE) 190. The base stations 104 and 106 can operate in a radio access network (RAN) 105 connected to the core network (CN) 110. The CN 110 can be implemented, for example, as an evolved packet core (EPC) 111 or as a fifth generation (5G) core (5GC) 160. Also, the CN 110 can be implemented as a sixth generation (6G) core in another embodiment.

[0016] S-BS104 includes cell 124 within its scope, and T-BS106 includes cell 126 within its scope. If S-BS104 is a gNB, cell 124 is an NR cell. If base station 124 is an ng-eNB or an eNB, cell 124 is an evolved universal terrestrial radio access (E-UTRA) cell. Similarly, if T-BS106 is a gNB, cell 126 is an NR cell, and if base station 126 is an ng-eNB or an eNB, cell 126 is an E-UTRA cell. Cell 124 and cell 126 may be within the same radio access network (RAN) notification area (RNA) or in different RNAs. Generally, RAN105 can include any number of base stations, and each of the base stations can include one, two, three, or any other appropriate number of cells within its scope. UE102 can support at least 5G NR (or simply "NR") or E-UTRA radio interfaces to communicate with base stations 104 and 106. Each of base stations 104 and 106 can be connected to CN110 via an interface (e.g., S1 interface or NG interface). Also, base station 104 and base station 106 can be connected to each other via an interface (e.g., X2 interface or Xn interface) for connecting NG RAN nodes to each other.

[0017] Among other components, and in particular, EPC 111 can include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network Gateway (PGW) 116. The SGW 112 is generally configured to transfer user plane packets related to, among other things, audio calls, video calls, Internet traffic, etc. The MME 114 is configured to manage authentication functions, registration functions, paging functions, and other related functions. The PGW 116 provides a connection from the UE 102 to one or more external packet data networks (e.g., the Internet network and / or the Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a User Plane Function (UPF) 162, an Access and Mobility Management Function (AMF) 164, and / or a Session Management Function (SMF) 166. Generally speaking, the UPF 162 is configured to transfer user plane packets related to, among other things, audio calls, video calls, Internet traffic, etc. The AMF 164 is configured to manage authentication functions, registration functions, paging functions, and other related functions. The SMF 166 is configured to manage PDU sessions.

[0018] As shown in FIG. 1A, the S-BS 104 supports cell 124 and the T-BS 106 supports cell 126. Cells 124 and 126 can partially overlap, and thus, the UE 102 can select, reselect, or hand over from one of cells 124 and 126 to the other. To directly exchange messages or information, the S-BS 104 and the T-BS 106 can support an X2 interface or an Xn interface. Generally, the CN 110 can be connected to any suitable number of base stations that support NR cells and / or EUTRA cells.

[0019] The S-BS104 and the UE102 establish a connection (e.g., wirelessly) through which the UE102 and the S-BS104 send data payloads. When establishing a connection via the S-BS104, the UE102 enters a connected state of the RAT protocol for controlling radio resources (e.g., EUTRA-RRC_CONNECTED, NR-RRC CONNECTED). The S-BS104 maintains the context of the UE102, where the context of the UE102 includes configuration information and other information related to the connection between the UE102 and the S-BS104. The context of the UE102 may include the configuration of SRB1, the configuration of SRB2, the configuration of SRB4, the configuration of DRB, and / or other configurations related to the connection between the UE102 and the S-BS104 (e.g., security configuration).

[0020] At some point, the UE102 establishes, resumes, or re-establishes a wireless connection with the T-BS106 for the maintenance inspection service. This can occur in various scenarios. In one scenario (the "handover scenario"), the S-BS104 determines that the UE102 should hand over to the T-BS106. In another scenario (the "re-establishment scenario"), the UE102 detects a radio link failure (RLF) on an established connection with the S-BS104, or detects an integrity check failure on SRB1, SRB2, or SRB4, and then selects the T-BS106 for the maintenance inspection service. In yet another scenario (the "re-selection scenario"), the S-BS104 detects that there has been no activity or data activity below a threshold for the UE102 over some time interval on the established connection. After this detection, the S-BS104 instructs the UE102 to enter an inactive state of the RAT protocol (e.g., EUTRA-RRC INACTIVE, NR-RRC INACTIVE). At some subsequent point, such as when the UE102 (which is in the inactive state) moves into a different coverage area and has payload data to send to the system, the UE102 selects or re-selects the T-BS106 for the maintenance inspection service.

[0021] S-BS104 includes processing hardware 130 that can include one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable memory that stores instructions executed by the one or more general-purpose processors. Additionally, or alternatively, the processing hardware 130 can include dedicated processing units. The processing hardware 130 in an exemplary implementation includes an RRC controller 132 that implements procedures and messaging in the RRC sublayer of the protocol communication stack. Also, the processing hardware 130 can include a QMC controller 134 configured to manage (one or more) QoE configurations and QoE reports for one or more UEs. T-BS106 can generally include similar components. Specifically, component 142 can be similar to component 132, and component 144 can be similar to component 134, respectively.

[0022] UE102 includes processing hardware 150 that can include one or more general-purpose processors such as a CPU and a non-transitory computer-readable memory that stores machine-readable instructions executable on the one or more general-purpose processors and / or on dedicated processing units. The processing hardware 150 in an exemplary implementation includes an RRC controller 152 that implements procedures and messaging in the RRC sublayer of the protocol communication stack. Also, the processing hardware 150 can include a QMC controller 154 configured to manage (one or more) QoE configurations, QMC, and reports.

[0023] FIG. 1B shows an exemplary distributed or disaggregated implementation of any one or more of base stations 104, 106. In this implementation, base stations 104A, 104B, 106A, or 106B include a central unit (CU) 172 and one or more DUs 174. CU 172 includes processing hardware such as one or more general-purpose processors (e.g., CPUs), and a computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors and / or on dedicated processing units. For example, CU 172 can include PDCP controllers 134, 144, RRC controllers 136, 146, and / or paging controllers 138, 148, such as PDCP controllers, RRC controllers, and / or paging controllers. In some implementations, CU 172 includes a radio link control (RLC) controller configured to manage or control one or more RLC operations or RLC procedures. In other implementations, CU 172 does not include an RLC controller.

[0024] Each of DUs 174 also includes processing hardware that can include one or more general-purpose processors (e.g., CPUs), and a computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors and / or on dedicated processing units. In some implementations, the processing hardware includes a MAC controller (e.g., MAC controllers 132, 142) configured to manage or control one or more MAC operations or MAC procedures (e.g., random access procedures), and / or an RLC controller configured to manage or control one or more RLC operations or RLC procedures. Also, the processing hardware can include a physical layer controller configured to manage or control one or more physical layer operations or physical layer procedures.

[0025] In some implementation forms, CU172 includes a logical node CU-CP172A that hosts the control plane part of the PDCP protocol of CU172. Further, CU172 may also include one or more logical nodes CU-UP172B that host the user plane part of the PDCP protocol and / or the Service Data Adaptation Protocol (SDAP) protocol of CU172. CU-CP172A can send control information (e.g., RRC messages, F1 application protocol messages), and CU-UP172B can send data packets (e.g., SDAP PDUs or Internet protocol packets).

[0026] CU-CP172A can be connected to a number of CU-UP172B via an E1 interface. CU-CP172A selects an appropriate CU-UP172B for the service required for UE102. In some implementation forms, a single CU-UP172B is connected to a number of CU-CP172A via an E1 interface. When CU-CP and one or more DUs belong to gNB, CU-CP172A can be connected to one or more DUs174 via an F1-C interface and / or an F1-U interface. When CU-CP and one or more DUs belong to ng-eNB, CU-CP172A can be connected to one or more DUs174 via a W1-C interface and / or a W1-U interface. In some implementation forms, one DU174 is connected to a number of CU-UP172B under the control of the same CU-CP172A. In such an implementation form, CU-CP172A uses a bearer context management function to establish a connection between CU-UP172B and DU174.

[0027] FIG. 2A shows, in a simplified manner, an exemplary protocol stack 200 by which UE 102 can communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106).

[0028] In the exemplary stack 200, the physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, and the EUTRA MAC sublayer 204A provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A provides RLC channels to the EUTRA PDCP sublayer 208 and, in some cases, also to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, and the NR MAC sublayer 204B provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B provides data transfer services to the NR PDCP sublayer 210. The NR PDCP sublayer 210 can provide data transfer services to the service data adaptation protocol (SDAP) 212 or the radio resource control (RRC) sublayer (not shown in FIG. 2A). In some implementations, UE 102 supports handover between EUTRA base stations and NR base stations and / or supports DC via the EUTRA interface and the NR interface, and thus supports both the EUTRA stack and the NR stack as shown in FIG. 2A. Further, as shown in FIG. 2A, UE 102 can support stacking the NR PDCP 210 as a layer on top of the EUTRA RLC 206A and stacking the SDAP sublayer 212 as a layer on top of the NR PDCP sublayer 210.

[0029] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets, which may be referred to as service data units (SDUs) (e.g., directly on top of the PDCP layer 208 or 210, or from an Internet Protocol (IP) layer stacked as a layer indirectly), and output packets, which may be referred to as protocol data units (PDUs) (e.g., to the RLC layer 206A or 206B). Except where the difference between the SDU and the PDU is relevant, for simplicity, the present disclosure refers to both the SDU and the PDU as "packets".

[0030] On the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide a signaling radio bearer (SRB) or an RRC sublayer (not shown in FIG. 2A) to exchange, for example, RRC messages or non-access-stratum (NAS) messages. On the user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide a data radio bearer (DRB) to support data exchange. The data exchanged on the NR PDCP sublayer 210 can be an SDAP PDU, an Internet Protocol (IP) packet, or an Ethernet packet.

[0031] Therefore, as shown by the radio protocol stack 250 in FIG. 2B, it is possible to functionally split the radio protocol stack. The CU can hold all control layer functions and upper layer functions (e.g., RRC 214, SDAP 212, and NR PDCP 210), while the operation of the lower layers (e.g., NR RLC 206B, NR MAC 204B, and NR PHY 202B) is delegated to the DU 174. To support the connection to the 5GC, the NR PDCP 210 provides an SRB to the RRC 214, the NR PDCP 210 provides a DRB to the SDAP 212, and provides an SRB to the RRC 214.

[0032] Figures 3A to 3G are message sequences of exemplary scenarios in which the RAN facilitates the collection of quality of experience (QoE) measurements (QMC) and the reporting of quality of experience (QoE) regarding the UE and the CN or the OAM node during mobility. Generally speaking, similar reference signs are labeled for the equal events in Figures 3A to 3G, with differences to be described later as appropriate (e.g., event 384 in Figure 3A is the same as event 384 in Figures 3B to 3G). Except for the differences shown in the figures and described later, any of the alternative implementations described for a particular event (e.g., regarding messaging and processing) may be applied to the events labeled with similar reference signs in other figures, and may also be applied to both integrated base stations and distributed base stations.

[0033] Referring initially to FIG. 3A, in scenario 300A, the UE initially operates in a connected state (e.g., RRC_CONNECTED) with the base station 104 of RAN105 (e.g., S-BS104) (302). While in the connected state, the UE102 communicates with the S-BS104 (e.g., via cell 124) and the CN110 (304). In some implementations, the UE102 can communicate information to the S-BS104 via the control plane (CP). Depending on the implementation, the UE102 communicates information via one or more SRBs and / or one or more DRBs. The one or more SRBs include SRB1 and / or SRB2. The CN110 or the OAM180 sends a QMC activation command to the S-BS104 to activate QMC and reporting for the UE102 (306). The QMC activation command can include one or more QoE configurations. In some implementations, the QMC activation command also includes a specific reference identifier, such as a reference ID, that identifies each of the one or more QoE configurations. In some implementations, the reference ID is a QoE reference ID. In other implementations, the reference ID is a service type. Depending on the implementation, the activation command can further include one or more trace IDs associated with each of the one or more QoE configurations, different sets of the one or more QoE configurations, or all of the one or more QoE configurations. In other implementations, the activation command includes a specific configuration identifier (i.e., configuration ID) for each of the one or more QoE configurations as one or more interface IEs of the activation command. In some implementations, the CN110 generates or assigns a value to the configuration ID (i.e., CN configuration ID). In other implementations, the OAM180 generates or assigns a value to the configuration ID (i.e., OAM configuration ID). Alternatively, the activation command does not include a configuration ID that identifies the QoE configuration.

[0034] In some implementation forms, the activation command includes an indication of the QMC pause status or the QMC resume status. In some implementation forms, the activation command includes, as an interface IE in the activation command, an IE (one or more) that describes the area information (i.e., areaScope), an interface for the trace IE, a trace depth IE, a TCE IP address (e.g., the IP address of TCE190), an MCE IP address (e.g., the IP address of MCE190), and / or a TCE URI. In some implementation forms, CN110 or OAM180 transmits one or more QoE configurations and / or any other information elements described above to S-BS104 while communicating with S-BS104 and UE102 (304).

[0035] In some implementation forms, the QMC activation command is a trace start message. In further implementation forms, the QMC activation command is included in an OAM-BS message or a CN-BS message (e.g., an NGAP message). In such cases, the QoE activation command can be an interface IE of the OAM-BS message or the CN-BS message. CN110 or OAM180 may transmit the CN-BS message or the OAM-BS message each containing the QMC activation command to S-BS104 (306). Depending on the implementation form, the (one or more) reference IDs may have the same value or different values. In some implementation forms, as described above, CN110 or OAM180 generates the (one or more) reference IDs and / or the (one or more) configuration IDs.

[0036] In some implementations, one or more QoE configurations are associated with a first trace ID. In other implementations, CN110 or OAM180 includes in the QMC activation command one or more additional trace IDs for additional QoE configurations beyond the first QoE configuration. Depending on the implementation, there may be an additional trace ID for each additional QoE configuration, or multiple QoE configurations may be associated with a single trace ID. CN110 or OAM180 can generate each trace ID with a different value. Alternatively, CN110 or OAM180 can obtain (one or more) trace IDs from TCE / MCE190.

[0037] In some implementations, S-BS104 can assign (307) each of the (one or more) QoE configuration IDs to a specific value. There are some implementations that assign or determine (one or more) values. In one implementation, S-BS104 derives the (one or more) values of the (one or more) QoE configuration IDs from the (one or more) CN configuration IDs or OAM configuration IDs, as in the case where S-BS104 receives the (one or more) CN configuration IDs or OAM configuration IDs at event 306. In such an implementation, there may be a one-to-one mapping between the (one or more) QoE configuration IDs and the (one or more) CN configuration IDs or OAM configuration IDs. For example, S-BS104 can use a function with the value of the CN configuration ID or OAM configuration ID as input to obtain the QoE configuration ID. In some such implementations, the function is a hash function or has a simple expression. In another example, S-BS104 sets the (one or more) values of the (one or more) QoE configurations to the (one or more) values of the (one or more) CN configuration IDs or OAM configuration IDs associated with the (one or more) QoE configurations that S-BS104 received at event 306.

[0038] In the case where S-BS104 does not receive one or more CN configuration IDs or OAM configuration IDs related to one or more QoE configurations, S-BS104 can generate (e.g., determine or assign) a specific QoE configuration ID and / or a specific value for each of the one or more QoE configurations (307) without referring to the one or more IDs (e.g., one or more reference IDs or one or more trace IDs) received in event 306. For example, S-BS104 can generate a specific QoE configuration ID and / or a specific value for each of the one or more QoE configurations according to the order of the one or more QoE configurations in the QoE activation command. In another embodiment, S-BS104 can generate a specific QoE configuration ID and / or a specific value for each of the QoE configurations by referring to the one or more IDs (e.g., one or more reference IDs or one or more trace IDs) received in event 306, similar to referring to the aforementioned one or more CN configuration IDs or OAM configuration IDs.

[0039] Next, S-BS104 transmits (308) a message (e.g., an RRC reconfiguration message) including one or more QoE configurations to UE102. In some implementations, S-BS104 generates a QoE configuration identifier such as a QoE configuration ID (e.g., measConfigAppLayerId) associated with a specific QoE configuration among the one or more QoE configurations. S-BS104 can include the one or more QoE configuration IDs associated with the one or more QoE configurations in message 308. UE102 can transmit a "completion" message such as an RRC reconfiguration complete message to S-BS104 (not shown) in response to message 308.

[0040] In some implementation forms, S-BS104 can further include in message 308 association information about the relationship between (one or more) QoE configuration IDs and (one or more) QoE configurations. In one implementation form, the association information is represented by a data structure of an IE that includes a list of (one or more) QoE configuration IDs and (one or more) QoE configurations in message 308. In some implementation forms, the list is structured as {QoE configuration ID, QoE configuration}. For example, (one or more) QoE configurations include (one or more) first QoE configurations, second QoE configurations, …, Mth QoE configurations each having QoE configuration ID X, …, QoE configuration ID (X + M - 1), where M is an integer greater than 0 and X can be 0 or 1. In the case where X is 0, X can be omitted. In the case where X is 1, (one or more) QoE configurations include (one or more) first QoE configurations, second QoE configurations, …, Mth QoE configurations each having QoE configuration ID 1, …, QoE configuration ID M. S-BS104 can include in message 308 {QoE configuration ID X, first QoE configuration}, {QoE configuration ID X + 1, second QoE configuration}, …, {QoE configuration ID (X + M - 1), Mth QoE configuration}. According to the association information, UE102 can associate (one or more) QoE configuration IDs with (one or more) QoE configurations.

[0041] In response to receiving the reconfiguration message (308), UE 102 starts QMC and reporting (310). In some implementations, after starting QMC and reporting (310), UE 102 transmits one or more uplink (UL) messages to S-BS 104 (312), and the one or more messages include one or more QoE reports. In some implementations, the one or more uplink messages are one or more UL RRC messages, and UE 102 transmits the one or more UL RRC messages to S-BS 104 via SRB. In some implementations, the SRB is SRB4. In such implementations, S-BS 104 can include the configuration parameter(s) that configure SRB4 in the RRC reconfiguration 308. Alternatively, S-BS 104 can transmit a DL RRC message (e.g., an RRC reconfiguration message) including the configuration parameter(s) that configure SRB4 to UE 102 during event 304 or before event 312. Depending on the implementation, S-BS 104 then transmits one or more QoE reports to TCE / MCE 190 (314). In some implementations, the one or more QoE reports are encapsulated in one or more transparent containers that S-BS 104 receives from UE 102 (312) and forwards to CN 110 or OAM 180.

[0042] In some implementations, UE102 periodically transmits (312) one or more QoE reports. In other implementations, UE102 transmits (312) one or more QoE reports in response to a specific trigger event and / or a predefined trigger event. In some such implementations, S-BS104 immediately transmits (314) any received (312) one or more QoE reports to CN110 or OAM180. In other implementations, S-BS104 aggregates the QoE reports before transmitting a message containing the multiple QoE reports to CN110 or OAM180. In yet other implementations, S-BS104 aggregates the QoE reports together with QoE reports from other one or more UEs before transmitting a message containing the multiple QoE reports to CN110 or OAM180.

[0043] Events 302, 304, 306, 308, 310, 312, and 314 are collectively referred to in FIG. 3A as the QMC activation procedure 384.

[0044] After S-BS104 receives a "completed" message (not shown) or after UE102 starts QMC and reporting, UE102 detects a failure (316) in communication with S-BS104. In some implementations, the failure can be a radio link failure, a reconfiguration failure, a consistency check failure, or a reconfiguration with a synchronization failure as described in section 5.3.10.3 of 3GPP technical specification 38.331 (e.g., v16.5.0). In response to the detection of the failure, UE102 can suspend transmissions, one or more SRBs, and / or one or more DRBs.

[0045] In response to the detection of a failure, UE 102 starts an RRC reestablishment procedure. In response to its start, UE 102 transmits an RRC reestablishment request message (e.g., an RRCReestablishmentRequest message) to base station 106 (e.g., T-BS 106 via cell 126) (318). In response to the reception of the RRC reestablishment request message, or after its reception, T-BS 106 transmits a UE context acquisition request message to S-BS 104 (320). In response thereto, S-BS 104 transmits a UE context acquisition response message to T-BS 106 (322). Depending on the implementation, S-BS 104 includes in the UE context acquisition response message, as interface IEs, one or more QoE configurations, one or more QoE configuration IDs, one or more trace IDs, an interface for the trace IE, a trace depth IE, a TCE IP address (e.g., the IP address of TCE 190), an MCE IP address (e.g., the IP address of MCE 190), one or more reference IDs, indications of QMC activation status and / or QMC suspension status, and / or a TCE URI. In some implementations, the UE context acquisition response message may include one or more IEs that describe area information (i.e., areaScope) regarding one or more QoE configurations. In further implementations, S-BS 104 includes a QMC activation command in the UE context acquisition response message.

[0046] In some implementation forms, S-BS104 can further include in the UE context acquisition response message association information about the relationship between (one or more) QoE configuration IDs and (one or more) QoE configurations, (one or more) reference IDs, or (one or more) trace IDs. In one implementation form, the association information can be represented by a data structure of an IE including a list of (one or more) QoE configuration IDs and (one or more) QoE configurations in the UE context acquisition response message. In some implementation forms, the list is structured as {QoE configuration ID, QoE configuration}. For example, (one or more) QoE configurations include (one or more) first QoE configurations, second QoE configurations, …, Mth QoE configurations each having QoE configuration ID X, …, QoE configuration ID (X + M - 1), where M is an integer greater than 0 and X can be 0 or 1. S-BS104 can include {QoE configuration ID X, first QoE configuration}, {QoE configuration ID X + 1, second QoE configuration}, …, {QoE configuration ID (X + M - 1), Mth QoE configuration} in the UE context acquisition response message.

[0047] Alternatively, S-BS104 does not include the association information, and the association information can be pre-defined in the 3GPP specification. In such a case, T-BS106 can associate the (one or more) QoE configuration IDs with the QoE configuration according to the pre-defined rules in the 3GPP specification. In some implementations, S-BS104 can include the (one or more) QoE configuration IDs and the (one or more) QoE configurations in the first list and the second list in the UE context acquisition response message. For example, the (one or more) QoE configurations include the (one or more) first QoE configurations, the second QoE configurations, …, the Mth QoE configurations, each having the (one or more) QoE configuration IDs X, …, QoE configuration ID (X + M - 1), where M is an integer greater than 0, and X can be 0 or 1. The first list can be {QoE configuration ID X, QoE configuration ID X + 1, …, QoE configuration ID (X + M - 1)}, and the second list can be {the first QoE configuration, the second QoE configuration, …, the Mth QoE configuration}, where the first position, the second position, …, the Mth position in the first list respectively correspond to the first position, the second position, …, the Mth position in the second list. The correspondence can be pre-defined in the 3GPP specification.

[0048] In some implementation forms, in addition to the aforementioned interface IE, S-BS104 includes an RRC inter-node message IE in the UE context acquisition response message. In a further implementation form, S-BS104 includes one or more QoE configuration IDs and one or more QoE configurations in the RRC inter-node message IE. In an even further implementation form, S-BS104 can further include association information about the relationship between one or more QoE configuration IDs and one or more QoE configurations in the RRC inter-node message IE. In one implementation form, the association information can be represented by a data structure of an IE including a list of one or more QoE configuration IDs and one or more QoE configurations in the RRC inter-node message. For example, one or more QoE configurations include one or more first QoE configurations, second QoE configurations, …, Mth QoE configurations each having QoE configuration ID X, …, QoE configuration ID (X + M - 1), where M is an integer greater than 0, and X can be 0 or 1. S-BS104 can include {QoE configuration ID X, first QoE configuration}, {QoE configuration ID X + 1, second QoE configuration}, …, {QoE configuration ID (X + M - 1), Mth QoE configuration} in the RRC inter-node message.

[0049] Alternatively, S-BS104 does not include the association information, which can be pre-defined in the 3GPP specifications. In such cases, T-BS106 can associate the (one or more) QoE configuration IDs with the QoE configuration according to the pre-defined rules in the 3GPP specifications. In some implementations, S-BS104 can include the (one or more) QoE configuration IDs and the (one or more) QoE configurations in the first list and the second list in the RRC inter-node message. For example, the (one or more) QoE configurations include the (one or more) first QoE configurations, second QoE configurations, …, Mth QoE configurations, each having QoE configuration ID X, …, QoE configuration ID (X + M - 1), where M is an integer greater than 0 and X can be 0 or 1. The first list can be {QoE configuration ID X, QoE configuration ID X + 1, …, QoE configuration ID (X + M - 1)}, and the second list can be {first QoE configuration, second QoE configuration, …, Mth QoE configuration}, where the first position, second position, …, Mth position in the first list respectively correspond to the first position, second position, …, Mth position in the second list. The correspondence can be pre-defined in the 3GPP specifications.

[0050] In other implementations, S-BS104 does not include the (one or more) QoE configuration IDs and the (one or more) QoE configurations in the RRC inter-node message.

[0051] In some implementations, unlike a base station that manages only a single QoE configuration for a UE, S-BS104 can transmit multiple QoE configurations, QoE configuration IDs, and reference IDs or trace IDs, and as described above, can further transmit the association information or other information associated with the multiple QoE configurations. Then, T-BS106 can store the (one or more) QoE configurations and / or the (one or more) QoE configuration IDs as described in relation to FIGS. 6 and 7.

[0052] After receiving the UE context acquisition response message (322), the T-BS 106 then transmits (324) an RRC reestablishment message (e.g., an RRC Reestablishment message) to the UE 102, for example, via cell 126. In response thereto, the UE 102 transmits (326) an RRC reestablishment completion message to the T-BS 106. In some implementations, the UE 102 resumes SRB1 after transmitting the RRC reestablishment request message or after receiving the RRC reestablishment message. After transmitting the RRC reestablishment message or after receiving the RRC reestablishment completion message, the T-BS 106 transmits (328) an RRC reconfiguration message to the UE 102. In response thereto, the UE 102 may transmit (330) an RRC reconfiguration completion message to the T-BS 106. In some implementations, the S-BS 104 indicates to the UE 102 in the RRC reconfiguration message to resume (one or more) SRBs (e.g., SRB2 and / or SRB4) and (one or more) DRBs. For example, the S-BS 104 may indicate to the UE 102 to resume (one or more) SRBs and (one or more) DRBs by excluding (one or more) release indicators for (one or more) SRBs in the RRC reconfiguration message 328. In response to receiving (328) or after receiving the RRC reconfiguration message, the UE 102 resumes (one or more) SRBs (e.g., SRB2 and / or SRB4) and (one or more) DRBs.

[0053] Then, the T-BS 106 may transmit (332) a BS-CN message (e.g., a path switch request message) or a BS-OAM message indicating that the UE 102 is connected to the T-BS 106 to the CN 110 or the OAM 180, respectively. Events 318, 320, 322, 324, 326, 328, 330, 332 are collectively referred to as the reestablishment procedure 386 in FIG. 3A.

[0054] After executing the re-establishment procedure 386, or after resuming the (one or more) SRBs and the (one or more) DRBs, the UE 102 communicates information to the T-BS 106 and the CN 110. In some implementations, after executing the re-establishment procedure 386, similar to the previous event 312, the UE 102 continues or resumes QoE reporting and transmits (334) one or more UL messages including one or more QoE reports to the T-BS 106. Then, the T-BS 106 transmits (336) one or more QoE reports to the TCE / MCE 190 as described in the previous event 314. In other implementations, the UE 102 may suspend QMC and / or QoE reporting after executing the re-establishment procedure 386, or after resuming the (one or more) SRBs and the (one or more) DRBs. In some such implementations, the UE 102 suspends QMC and / or QoE reporting because the T-BS 106 may not belong to the area configured in the area configuration. In such cases, the S-BS 104 may include the area configuration in the RRC reconfiguration message 308.

[0055] In some implementation forms, in order to remove the influence of a fault from the QMC, the UE102 suspends the QMC in response to the detection of the fault (316). For this reason, when the management system analyzes or processes the (one or more) QoE reports, the management system does not need to exclude or identify some of the (one or more) QoE reports affected by the fault. In such a case, after the UE102 executes the re-establishment procedure 386 or after resuming the (one or more) SRBs and the (one or more) DRBs, the UE102 resumes the QMC. In other implementation forms, when the UE102 detects a fault (316), the UE102 continues the QMC and can further record the fault in the fault report. Next, the UE102 can send the fault information to the T-BS106, and the T-BS106 sends the fault information to the TCE / MCE190. When the management system analyzes or processes the (one or more) QoE reports, the management system can identify or process some of the (one or more) QoE reports affected by the fault. In some implementation forms, the management system is part of the TCE / MCE190. In other implementation forms, the management system is a network node other than the TCE / MCE190. In such a case, the TCE / MCE190 transfers the (one or more) QoE reports and / or the fault report to the network node.

[0056] CN110 or OAM180 ultimately determines to deactivate QMC and reporting. For this, CN110 or OAM180 sends a QMC deactivation message including a command to release one or more QoE configurations configured in procedure 384 to T-BS106 (338). In some implementations, T-BS106 may determine (347) whether a QoE configuration ID exists for the stored reference ID as described in FIGS. 6 and 7. When receiving the message, T-BS106 sends an RRC reconfiguration message to UE102 (340), which message includes a command to release the indicated QoE configuration. Then, UE102 releases the indicated QoE configuration (342) and stops the QMC process and the reporting process. Events 338, 347, 340, and 342 are collectively called the QMC deactivation procedure 388 in FIG. 3A.

[0057] In some implementations, the QMC deactivation message is a trace deactivation message. In other implementations, the QMC deactivation message (e.g., a trace deactivation IE, a QoE deactivation IE, or a QoE deactivation IE) is included in an OAM-BS message or a CN-BS message (e.g., an NGAP message). In such implementations, CN110 or OAM180 sends a message including the QMC deactivation message (i.e., an OAM-BS message or a CN-BS message) to T-BS106 (338). In this way, the (one or more) QoE configurations related to the UE are transferred from the first base station to the second base station, and CN or OAM can deactivate QMC at the second base station.

[0058] In some implementations having a single trace ID, CN110 or OAM180 includes the trace ID in a QMC deactivation message to instruct T - BS106 to release all of the QoE configuration regarding UE102. Then, T - BS106 can send a reconfiguration message to UE102 (340) to instruct UE102 to release all of the QoE configuration using the single trace ID. In further implementations, CN110 or OAM180 includes a specific reference ID in the QMC deactivation message to indicate that T - BS106 should release the QoE configuration associated with the reference ID regarding UE102. In some such implementations, T - BS106 obtains a specific QoE configuration ID based on the specific reference ID and associated information. In still other implementations, CN110 or OAM180 includes a specific trace ID in the QMC deactivation message to indicate that T - BS106 should release the QoE configuration associated with the trace ID regarding UE102. In some such implementations, T - BS106 obtains a specific QoE configuration ID based on the specific trace ID and associated information.

[0059] In this way, both (i) re - establishing QMC and / or QoE reporting after the UE detects a communication failure, and (ii) then stopping QMC and / or QoE reporting for the UE via the RAN's T - BS are realized.

[0060] Next, referring to Figure 3B, scenario 300B is similar to 300A and also includes S - BS104 and UE102 activating QMC and reporting regarding UE102 before detecting a communication error and performing a re - establishment procedure with T - BS106 as the counterpart. However, different from scenario 300A, after the re - establishment procedure, RAN105 sends a command to UE102 to change the QoE configuration instead of releasing the QoE configuration.

[0061] After executing the re - establishment procedure 386, depending on the implementation form, while continuing QMC and reports 334 / 336 with respect to UE102 and T - BS106, CN110 or OAM180 sends a QMC activation command to T - BS106 (339). CN110 or OAM180 includes a command to change one or more QoE configurations in the QMC activation command. Then, T - BS106 sends a radio resource re - configuration message (e.g., an RRC re - configuration message) to UE102 (341), and this message includes a command to change one or more QoE configurations. Upon receiving the radio resource re - configuration message (341), UE102 changes one or more QoE configurations (343) and starts to send an uplink RRC message including a QoE report to T - BS106 according to the changed QoE configuration (344). Then, T - BS106 may send the report to the TCE / MCE node 190 (346). Events 339, 347, 341, 343, 344, and 346 are collectively called the QMC change procedure 390 in Figure 3B. Depending on the implementation form, UE102, T - BS106, and CN110 or OAM180 may later execute the QMC de - activation procedure 388 detailed in Figure 3A above.

[0062] Referring next to Figure 3C, scenario 300C is similar to 300A and similarly includes S - BS104 and UE102 activating QMC and reports with respect to UE102 before detecting a communication error and executing a re - establishment procedure with respect to T - BS106. However, different from scenario 300A, in response to the execution of the re - establishment procedure, T - BS106 releases (one or more) QoE configurations.

[0063] After executing the re-establishment procedure 386, both the UE 102 and the T-BS 106 release their respective (one or more) QoE configurations (350 / 351). The UE 102 is capable of releasing its (one or more) QoE configurations (350) in response to the re-establishment procedure 386. In some implementations, the T-BS 106 releases its (one or more) QoE configurations (351) in response to determining that the T-BS 106 does not support QoE reporting or specific QoE commands. In further implementations, the T-BS 106 releases its (one or more) QoE configurations (351) in response to determining that the (one or more) QoE configurations are invalid. For example, the T-BS 106 may not belong to the area configured in the area configuration. In such cases, similar to event 340, the T-BS 106 can include an indication to release the (one or more) QoE configurations in the RRC reconfiguration 328 during the re-establishment procedure 386. In even further implementations, the T-BS 106 releases its (one or more) QoE configurations (351) in response to receiving a command from the CN 110 or the OAM 180 during the re-establishment procedure 386. In some implementations, after releasing the (one or more) QoE configurations, the T-BS 106 sends a message to the CN 110 or the OAM 180 notifying the CN 110 or the OAM 180 that the (one or more) QoE configurations have been released (352). In response to message 352, the CN 110 or the OAM 180 is capable of releasing the (one or more) QoE configurations. In other implementations, upon receiving a BS-CN message or a BS-OAM message during the re-establishment procedure 386 (332), the CN 110 or the OAM 180 determines that the T-BS 106 may not belong to the area configured in the area configuration. In response to that determination, the CN 110 or the OAM 180 is capable of releasing the (one or more) QoE configurations.

[0064] Next, referring to FIG. 3D, scenario 300D is similar to 300C and similarly includes S-BS104 and UE102 activating QMC and reporting for UE102 before detecting a communication error and performing a re-establishment procedure with respect to T-BS106. However, unlike scenario 300C, S-BS104 releases the QoE configuration in response to performing the re-establishment procedure.

[0065] After performing re-establishment procedure 386, both UE102 and S-BS104 release their respective (one or more) QoE configurations (350 / 349). During re-establishment procedure 386, S-BS104 does not need to transfer the QoE configuration to T-BS106. For this reason, S-BS104 releases the QoE configuration after the re-establishment procedure is completed (349). In some implementations, S-BS104 does not transfer the QoE configuration because T-BS106 does not support QoE reporting or is not configured for QoE reporting. In further implementations, S-BS104 releases the QoE configuration in response to determining that the QoE configuration is invalid (349). In yet further implementations, S-BS104 releases the QoE configuration in response to receiving a command from CN110 or OAM180 during or immediately prior to re-establishment procedure 386 (349). Depending on the implementation, S-BS104 may send a message to CN110 or OAM180 notifying CN110 or OAM180 that the QoE configuration has been released in response to the release of the QoE configuration (353).

[0066] Next, referring to FIG. 3E, scenario 300E is similar to 300A and similarly includes S-BS104 and UE102 activating QMC and reporting for UE102 before detecting a communication error and performing a re-establishment procedure with respect to T-BS106. However, unlike scenario 300A, S-BS104 suspends QoE reporting prior to detecting the communication error, and T-BS106 resumes QoE reporting after the re-establishment procedure.

[0067] After executing the QMC activation procedure 384, CN110 or OAM180 decides (354) to suspend the QoE measurement report (hereinafter referred to as the QoE report). In some implementations (not shown), CN110 or OAM180 makes the decision 354 in response to a request from UE102 via S - BS104 or in response to a request from S - BS104. UE102 may send its request to CN110 or OAM180 via S - BS104 in response to deciding to conserve power or in response to suspending the application associated with the QoE report. In further implementations, S - BS104 may send its request to CN110 or OAM180 in response to receiving more than a predetermined amount of information from one or more UEs (i.e., RAN overload). After making the decision 354, CN110 or OAM180 sends a command to suspend the QoE report (e.g., QoE suspension command) to S - BS104 (356). After receiving the command (356), S - BS104 sends a command to suspend the QoE report to UE102 (358). Then, UE102 suspends the QoE report (360).

[0068] In some implementations, UE102 continues the QMC associated with the QoE report but stops transmitting the QoE report in response to receiving the command (358) or after receiving the command (358). In other implementations, UE102 suspends the QMC and / or the QoE report in response to a command that acts as a toggle and resumes the QMC and the report in response to receiving the command a second time. In some implementations, CN110 or OAM180 can indicate in the command whether the QMC is to be suspended in the network.

[0069] In some implementation forms, S-BS104 can send an RRC reconfiguration including a QoE suspension command to UE102 (358). In response to this, UE102 can send an RRC reconfiguration completion message to S-BS104 (not shown). In some implementation forms, the QoE suspension command is a CN-BS message (for example, an NGAP message or a QoE suspension message). In other implementation forms, the QoE suspension command is included in an OAM-BS message or a CN-BS message (such as an NGAP message). In such cases, the QoE suspension command can be an interface IE of an OAM-BS message or a CN-BS message.

[0070] In some implementations, in response to command 358, UE 102 pauses QoE reporting for one or more (up to all) of the (one or more) QoE configurations configured in procedure 384. In such cases, in one implementation, CN 110 or OAM 180 can include in command 358 one or more indicators that instruct UE 102 to pause QoE reporting for the (one or more) QoE configurations individually indicated, or alternatively, can include a single indicator that pauses QoE reporting for all QoE configurations in the UE. The (one or more) indicators can be the (one or more) IDs associated with the aforementioned (one or more) QoE configurations. In other implementations, CN 110 or QAM 180 includes the (one or more) indicators in an OAM-BS message or a CN-BS message 356. In such cases, S-BS 104 can identify, as described above, the (one or more) QoE configuration IDs associated with one or more of the (one or more) QoE configurations by the (one or more) indicators (e.g., the (one or more) IDs). In another implementation, CN 110 or OAM 180 does not include in command 358 an indicator that indicates to UE 102 to pause QoE reporting for the selected (one or more) QoE configurations. In this case, command 358 without the indicator implicitly indicates that UE 102 should pause QoE reporting for all of the (one or more) QoE configurations.

[0071] After pausing the QoE report (360), UE 102 detects a communication failure (316) and performs a re-establishment procedure 386 with respect to S-BS 104, T-BS 106, and CN 110 or OAM 180 as described in FIG. 3A. After performing the re-establishment procedure 386, CN 110 or OAM 180 transmits a QoE resume command to resume the QoE report to T-BS 106 (362). In some implementations, CN 110 or OAM 180 transmits the QoE resume command (362) after receiving a notification from T-BS 106 that the re-establishment procedure 386 has been performed (332). In other implementations, CN 110 or OAM 180 may receive an indication from S-BS 104 instead of or in addition to receiving the indication from T-BS 106 (332).

[0072] In response to receiving a command (362), T-BS106 transmits a QoE resume command to UE102 (364). In the case where UE102 suspends QMC, UE102 resumes QMC. In some implementations, T-BS106 transmits an RRC reconfiguration including the QoE resume command to UE102 (364). In response, UE102 may transmit an RRC reconfiguration complete message to T-BS106 (not shown). In some implementations, UE102 then begins to resume QoE reporting (366) and transmits an uplink message including a QoE report to T-BS106 (368), and T-BS106 transmits the QoE report to TCE / MCE190 (370). Events 366, 368, and 370 are collectively known as the QoE report resume procedure 392 in FIG. 3E. Depending on the implementation, UE102, T-BS106, and CN110 or OAM180 may then execute a QMC change procedure 390 or a QMC inactivation procedure 388 as described in FIGS. 3A and 3B. If the reason or condition for suspending the QoE report as described above is still invalid, CN110 or OAM180 may refrain from transmitting a command (362). Otherwise, CN110 or OAM180 may transmit a command (362). For example, CN110 or OAM180 makes a determination in response to a request by UE102 via S-BS104 or in response to a request by S-BS104. In response to determining not to conserve power or in response to resuming an application associated with QoE reporting, UE102 may transmit its request to CN110 or OAM180 via S-BS104.

[0073] In some scenarios and some implementations, CN110 or OAM180 receives an indication from T-BS106 that T-BS106 is overloaded before the re-establishment procedure 386 is completed. In such cases, CN110 or OAM180 refrains from sending a command to T-BS106 (362). After CN110 or OAM180 receives an indication from T-BS106 that T-BS106 is no longer overloaded, CN110 or OAM180 can then decide to send a command to T-BS106 (362).

[0074] In some implementations, the QoE resume command is a CN-BS message (e.g., an NGAP message or a QoE resume message). In other implementations, the QoE resume command is included in an OAM-BS message or a CN-BS message (e.g., an NGAP message). In such cases, the QoE resume command can be an interface IE of the OAM-BS message or the CN-BS message.

[0075] In some implementations, in response to command 362, UE102 resumes QoE reporting for all of the QoE configurations configured in procedure 384. In such cases, in some implementations, CN110 or OAM180 can include an indication in command 362 to indicate to UE102 to resume QoE reporting for all of the QoE configurations. The indication can be, as described above, one or more IDs associated with the one or more QoE configurations. In another implementation, CN110 or OAM180 does not include an indication in command 358 to indicate to UE102 to resume QoE reporting for all of the QoE configurations. In this case, command 362 without that indication indicates to UE102 to resume QoE reporting for all of the QoE configurations.

[0076] In other implementations, UE 102 resumes QoE reporting for one or more of the (one or more) QoE configurations in response to command 362. In such cases, CN 110 or OAM 180 may include in command 362 an indication to UE 102 to resume QoE reporting for one or more of the (one or more) QoE configurations. The indication may be, as described above, one or more (one or more) IDs associated with the (one or more) QoE configurations. Alternatively, CN 110 or QAM 180 may include the indication in an OAM-BS message or a CN-BS message 362. In this case, T-BS 106 can identify, as described above, one or more (one or more) QoE configuration IDs associated with the (one or more) QoE configurations by the indication (e.g., the (one or more) IDs). Next, T-BS 106 includes the (one or more) QoE configuration IDs in the RRC reconfiguration message 364. Thus, UE 102 can determine to resume QoE reporting for one or more of the (one or more) QoE configurations based on the (one or more) QoE configuration IDs.

[0077] Referring next to Figure 3F, scenario 300F is similar to 300E and also includes S-BS 104 and UE 102 activating QMC and reporting with respect to UE 102 before detecting a communication error and performing a re-establishment procedure with T-BS 106. However, unlike scenario 300E, base stations 104 and 106 make a decision to suspend or resume QoE reporting independently of CN 110 or OAM 180.

[0078] After executing the QMC activation procedure 384, S-BS104 decides to suspend the QoE report (355). In some implementations, S-BS104 may make the decision 355 after receiving a request from UE102. UE102 may send the request to S-BS104 in response to deciding to conserve power. In further implementations, S-BS104 may make the decision 355 in response to receiving more than a predetermined amount of information from one or more UEs (i.e., RAN overload). In response to the decision 355 to suspend the QoE report, S-BS104 sends a QoE suspension command to UE102 to suspend the QoE report (358). In some implementations, the command includes a measConfigAppLayer information element that includes a QoE suspension command to temporarily suspend the QoE report. In such implementations, UE102 may continue to execute the QMC and only stop reporting. Alternatively, UE102 may also suspend the QMC in response to the QoE suspension command. After receiving the command, UE102 suspends the QoE report (360). In some implementations, S-BS104 may send a message to CN110 or OAM180 notifying CN110 or OAM180 that the QoE report has been suspended (359). Events 355, 358, 359, and 360 are collectively known as the QMC suspension procedure 394 in FIG. 3F.

[0079] After pausing the QoE report (360), UE 102 detects a communication failure (316) and executes a re-establishment procedure 386 with respect to S-BS 104, T-BS 106, and CN 110 or OAM 180 as described in FIG. 3A. Similar to event 323 in FIG. 3G later, S-BS 104 can include an indication of the paused status regarding the QoE configuration associated with the QoE report in the UE context acquisition response message during the re-establishment procedure 386. After executing the re-establishment procedure 386, or in response to the execution of the re-establishment procedure 386, T-BS 106 determines to resume the QoE report (363) and transmits a QoE resume command to UE 102 to resume the QoE report (364). In some implementations, T-BS 106 then transmits a message to CN 110 or OAM 180 notifying CN 110 or OAM 180 that the QoE report is to be resumed. UE 102, T-BS 106, and TCE / MCE 190 then execute a QoE report resumption procedure 392 as described in FIG. 3E. Similarly, UE 102, T-BS 106, and CN 110 or OAM 180 may then execute a QMC change procedure 390 and / or a QMC deactivation procedure 388 as described in FIGS. 3A and 3B.

[0080] Referring next to FIG. 3G, scenario 300G is similar to 300E and also includes S-BS 104 and UE 102 activating QMC and reporting with respect to UE 102 before detecting a communication error and executing a re-establishment procedure with respect to T-BS 106. However, unlike scenario 300E, T-BS 106 obtains an indication of the paused status regarding the QoE configuration during the re-establishment procedure.

[0081] After detecting a communication failure (316), UE 102 sends a re-establishment request to T-BS 106 (318). Then, T-BS 106 sends a request to obtain the context regarding UE 102 from S-BS 104 (320). Then, S-BS 104 responds with the QoE configuration configured in the QMC activation procedure 384 and an indication that the QoE configuration has been suspended (323). After obtaining the context regarding UE 102 (320 / 322), T-BS 106 sends a re-establishment message to UE 102 (324), and UE 102 responds with a confirmation response indicating that the re-establishment is complete (326). In some implementations, T-BS 106 then sends a radio resource (e.g., RRC) reconfiguration message to UE 102 (328), and this message includes an indication to resume the QoE reporting regarding the QoE configuration. In response to this, UE 102 sends a message to T-BS 106 indicating that the radio resource reconfiguration is complete (330), and T-BS 106 notifies CN 110 or OAM 180 by sending the message to CN 110 or OAM 180 (332). Depending on the implementation, UE 102, T-BS 106, and / or CN 110 or OAM 180 may perform any or all of the QoE reporting resumption procedure 392, the QMC change procedure 390, and / or the QMC deactivation procedure 388 as described above.

[0082] Figures 4A to 4C are message sequences of exemplary scenarios in which the RAN facilitates Quality of Experience (QoE) Measurement Collection (QMC) and Quality of Experience (QoE) reporting for the UE, and the CN or OAM node during and / or after a communication failure. Generally speaking, the equivalent events in Figures 4A to 4C are labeled with similar reference signs with differences explained later as appropriate (e.g., event 386 in Figures 3A to 3G is similar to event 486 in Figures 4A to 4C). Except for the differences shown in the figures and explained later, any alternative implementations described for a particular event (e.g., regarding messaging and processing) may be applied to events labeled with similar reference signs in other figures, and may also be applied to both integrated base stations and distributed base stations.

[0083] Referring next to Figure 4A, scenario 400A is similar to 300A and similarly includes S-BS104 and UE102 communicating before detecting a communication error and performing a re-establishment procedure with T-BS106. However, unlike scenario 300A, S-BS104 cannot send an initial QoE configuration to activate QMC and QoE reporting.

[0084] After (404) or while (404) communicating with S-BS104 and UE102, CN110 or OAM180 sends a command to S-BS104 to activate QMC and QoE reporting, and the command includes a QoE configuration. In response, S-BS104 attempts to send the QoE configuration to UE102 in a reconfiguration message (e.g., an RRC reconfiguration message) (408). However, UE102 does not receive the configuration and then detects a communication failure (416). In some implementations, UE102 detects a communication failure (416) because UE102 does not receive the configuration. Depending on the implementation, S-BS104 sends a message to CN110 or OAM180 indicating that the communication with UE102 has failed (409).

[0085] After detecting the failure (416), UE 102, S-BS 104, T-BS 106, and CN 110 or OAM 180 execute a re-establishment procedure 486. In some implementations, S-BS 104 retains the QoE configuration, and T-BS 106 obtains the QoE configuration directly from S-BS 104 during the re-establishment procedure 486.

[0086] In yet other implementations, T-BS 106, similar to event 332, transmits a message to notify CN 110 or OAM 180 as part of the re-establishment procedure 486 to CN 110 or OAM 180. In response, CN 110 or OAM 180 transmits the QoE configuration in a QMC activation command (466) to enable T-BS 106 to obtain the QoE configuration from CN 110 or OAM 180. Depending on the implementation, T-BS 106 may obtain the QoE configuration from both S-BS 104 and CN 110 or OAM 180, or T-BS 106 may obtain the QoE configuration from S-BS 104 and then obtain or receive a second QoE configuration from CN 110 or OAM 180.

[0087] After receiving the QoE configuration from CN110 or OAM180 (466), similar to event 308, T-BS106 transmits the QoE configuration to UE102 in an RRC reconfiguration message (468). In response, UE102 starts a new session for QoE measurement collection and QoE reporting (410). UE102 can transmit an RRC reconfiguration complete message to T-BS106 (not shown) in response to the RRC reconfiguration message. UE102 then transmits an uplink message containing the QoE report to T-BS106 (434), and T-BS106 transmits the QoE report to TCE / MCE190. Depending on the implementation form, UE102, T-BS106, and CN110 or OAM180 execute a QMC change procedure 490 and / or a QMC inactivation procedure 488, similar to the QMC change procedure 390 and / or the QMC inactivation procedure 388 described in FIGS. 3A and 3B.

[0088] Referring now to FIG. 4B, scenario 400B is similar to 400A and similarly includes S-BS104 and UE102 communicating before detecting a communication error and performing a reestablishment procedure with T-BS106 as the counterpart. However, unlike scenario 400A, S-BS104 attempts to send a command to UE102 to release the QoE configuration.

[0089] UE102, S-BS104, and CN110 or OAM180 succeed in executing QMC activation procedure 484 in the same way as QMC activation procedure 384 described in FIG. 3A in the previous section. After activation procedure 484, CN110 or OAM180 decides to deactivate QMC and QoE reporting and sends a command to S-BS104 to release the QoE configuration (438). S-BS104 attempts to send an RRC reconfiguration message to UE102 to release the QoE configuration (442) in the same way as event 340. However, UE102 does not receive the message and then detects a communication failure (416). In some implementations, UE102 detects a communication failure (416) because UE102 does not receive the message. Depending on the implementation, S-BS104 sends a message indicating that communication with UE102 has failed to CN110 or OAM180 (409). In other implementations, T-BS106 may send a message to CN110 or OAM180 as part of re-establishment procedure 486 in the same way as event 332.

[0090] In response to the detection of a failure (416), UE 102 performs a re-establishment procedure 486 against T-BS 106, S-BS 104, and CN 110 or OAM 180 as described previously in connection with FIG. 4A. In some implementations, T-BS 106 obtains a command to release the QoE configuration along with the QoE configuration in a UE context acquisition response message from S-BS 104 during the re-establishment procedure 486. In further implementations, in response to receipt of that message during or after the re-establishment procedure 486 (e.g., similar to event 332), CN 110 or OAM 180 performs a QMC deactivation procedure 488 similar to the QMC deactivation procedure 388 described in FIG. 3A. After performing the re-establishment procedure 486 and before receiving a command to release the QoE configuration, UE 102 can continue or resume QoE reporting by transmitting one or more UL messages (434) containing one or more QoE reports to T-BS 106. Then, T-BS 106 transmits the one or more QoE reports to TCE / MCE 190 (436).

[0091] Referring now to FIG. 4C, scenario 400C is similar to 400B and likewise includes S-BS 104 and UE 102 communicating before detecting a communication error and performing a re-establishment procedure against T-BS 106. However, unlike scenario 400B, S-BS 104 attempts to send a command to UE 102 to change the QoE configuration.

[0092] After executing the QMC activation procedure 484 with respect to UE102 and S-BS104, CN110 or OAM180 sends a message containing an indication to change the QoE configuration to S-BS104. In response thereto, S-BS104 attempts to send an RRC reconfiguration message to UE102 (443) to instruct UE102 to change the QoE configuration, similar to event 341. However, UE102 does not receive the message and then detects a communication failure (416). In some implementations, UE102 detects a communication failure (416) because UE102 does not receive the message. Depending on the implementation, S-BS104 sends a message indicating that the communication with respect to UE102 has failed to CN110 or OAM180 (409). In other implementations, T-BS106 sends a message to CN110 or OAM180 as part of the re-establishment procedure 486, similar to event 332.

[0093] In response to the detection of a failure (416), UE102 executes the re-establishment procedure 486 with respect to T-BS106, S-BS104, and CN110 or OAM180 as described above in connection with FIG. 4A. In some implementations, T-BS106 obtains a command to change the QoE configuration in the UE context acquisition response message from S-BS104 during the re-establishment procedure 486. In further implementations, in response to receiving the message (e.g., similar to event 332) during the re-establishment procedure 486, or after receiving the message, CN110 or OAM180 executes the QMC change procedure 490 similar to the QMC change procedure 390 described in FIG. 3B. After executing the re-establishment procedure 486 and before receiving a command to change the QoE configuration, UE102 can send one or more UL messages containing one or more QoE reports to T-BS106 (434) to continue or resume QoE reporting. Then, T-BS106 sends the one or more QoE reports to TCE / MCE190 (436).

[0094] Next, several exemplary methods that may be implemented at the UE, RAN, CN, or OAM node will be described with reference to FIGS. 5 to 15. Each of these methods may be implemented using processing hardware, such as one or more processors, that execute instructions stored on a non-transitory computer-readable medium, such as a computer memory.

[0095] Referring first to FIG. 5, method 500 can be implemented at an appropriate RAN source node and includes receiving at least one QoE configuration and reference identifier, assigning a configuration identifier to the configuration, and transmitting the configuration and identifier to a target node. For clarity, method 500 is described with particular reference to RAN 105, S-BS 104 as the source node, T-BS 106 as the target node, CN 110 or OAM 180 as the QoE node (e.g., network node), and UE 102.

[0096] At block 502, S-BS104 communicates with the connected and operating UE102 (e.g., events 304, 384, 404, and 484 in FIGS. 3A-4C). At block 504, S-BS104 receives at least one QoE configuration and at least one reference identifier (e.g., reference ID) from CN110 or OAM180 (e.g., events 306, 384, 406, and 484 regarding FIGS. 3A-4C). In some implementations, each reference identifier is associated with a specific QoE configuration. In further implementations, a reference identifier can refer to a group of multiple configurations. At block 506, S-BS104 assigns a different configuration identifier (e.g., configuration ID) to each of the QoE configurations (e.g., event 384 in FIGS. 3A-3G and event 484 in FIGS. 4B-4C). Next, at block 508, S-BS104 transmits the QoE configuration and the configuration identifier to UE102 (e.g., events 308, 384 in FIGS. 3A-3G and event 484 in FIGS. 4B-4C). In some implementations, the flow continues at block 510 where S-BS104 receives at least one QoE report from UE102 in response to transmitting the QoE configuration (e.g., events 312, 384 in FIGS. 3A-3G and event 484 in FIGS. 4B-4C). In some implementations, S-BS104 receives a QoE report from UE102 for each of the QoE configurations. In other implementations, S-BS104 receives a QoE report from UE102 only for some of the QoE configurations. In still other implementations, S-BS104 receives a smaller number of QoE reports from UE102 than the number of QoE configurations, but at least some of the QoE reports correspond to multiple QoE configurations.

[0097] In block 512, S-BS 104 then receives, from T-BS 106, a first interface message (e.g., a UE context acquisition request message) requesting a context regarding UE 102 (e.g., events 320, 386, and 486 of FIGS. 3A - 4C). In response, in block 514, S-BS 104 then transmits, to T-BS 106, a second interface message (e.g., a UE context acquisition response message) including a QoE configuration, a reference identifier, and a configuration identifier (e.g., events 322, 323, 386, and 486 of FIGS. 3A - 4C). In some implementations, the second interface message further includes information about the association between the reference identifier and the configuration identifier.

[0098] In this way, the RAN's S-BS receives and assigns an identifier for the QoE configuration used for QMC and / or QoE reporting before transmitting an identifier and / or identification information regarding the QoE configuration to the T-BS in response to a request from the RAN's T-BS.

[0099] Referring now to FIG. 6, method 600 can be implemented at an appropriate RAN target node and includes receiving at least one QoE configuration, a reference identifier, and a configuration identifier, and then receiving an indication to release or modify the QoE configuration using the reference identifier. For clarity, method 600 is described with specific reference to RAN 105, S-BS 104 as the source node, T-BS 106 as the target node, CN 110 or OAM 180 as the QoE node (e.g., network node), and UE 102.

[0100] In block 602, T-BS 106 receives a re-establishment request message from UE 102 operating in a connected state (e.g., events 318, 386, and 486 of FIGS. 3A-4C). In response, in block 604, T-BS 106 sends a first interface message (e.g., a UE context acquisition request message) to S-BS 104 (e.g., events 320, 386, and 486 of FIGS. 3A-4C). In block 606, T-BS 106 then receives from S-BS 104 a second interface message (e.g., a UE context acquisition response message) that includes at least one QoE configuration for UE 102, at least one reference identifier (e.g., a reference ID), and at least one configuration identifier (e.g., a configuration ID) (e.g., events 322, 323, 386, and 486 of FIGS. 3A-4C). In some implementations, the second interface message includes information about the association between the reference identifier and the configuration identifier.

[0101] Next, in block 608, before T-BS 106 sends a radio resource reconfiguration message (e.g., an RRC reconfiguration message) in block 610 (e.g., events 328, 386, and 486 of FIGS. 3A-4C), T-BS 106 sends a re-establishment message to UE 102 (e.g., events 324, 386, and 486 of FIGS. 3A-4C). In some implementations, the flow then proceeds to any or all of blocks 612, 614, and 616. In block 612, T-BS 106 receives a QoE message including a reference identifier from CN 110 or OAM 180 (e.g., events 338, 339, 388, 390, 488, or 490 of FIGS. 3A-4C). Depending on the implementation, the message further includes a command to release or modify the QoE configuration based on the reference identifier. In block 614, T-BS 106 identifies the configuration identifier corresponding to the received reference identifier (e.g., events 347, 388, 390, 488, or 490 with respect to FIGS. 3A-4C). In some implementations, the configuration identifier and the reference identifier are mapped one-to-one.

[0102] In block 616, T-BS106 transmits a downlink radio resource message (e.g., a DL RRC message) that includes a configuration identifier identified to release or change the corresponding QoE configuration (e.g., events 340, 341, 388, 390, 488, or 490 with respect to FIGS. 3A-4C). In some implementations, T-BS106 determines that the QoE configuration is invalid. For example, T-BS106 may not belong to the area configured in the area configuration or may otherwise not support QoE operation. In response, the flow may jump directly from block 610 to block 616, and T-BS106 transmits a downlink radio resource message to UE102 that releases or changes QoE in response to the determination that the QoE configuration is invalid.

[0103] Referring now to FIG. 7, method 700 can be implemented at an appropriate RAN source node and includes determining whether to include an indication to suspend or resume a QoE configuration based on whether S-BS104 has suspended QoE reporting. For clarity, method 700 is described with particular reference to RAN105, S-BS104 as the source node, T-BS106 as the target node, CN110 or OAM180 as the QoE node (e.g., a network node), and UE102.

[0104] In block 702, S-BS 104 communicates with a UE operating in a connected state (e.g., events 304, 384, 404, and 484 of FIGS. 3A-4C). In block 704, S-BS 104 transmits a QoE configuration to UE 102 to activate QMC and / or QoE reporting (e.g., events 306, 384 of FIGS. 3A-3G and event 484 of FIGS. 4B-4C). In some implementations, the flow continues to block 706 where S-BS 104 receives a QoE report from UE 102 in response to transmitting the QoE configuration (e.g., events 312, 384 of FIGS. 3A-3G and event 484 of FIGS. 4B-4C). In block 708, S-BS 104 receives a first interface message (e.g., a UE context acquisition request message) from T-BS 106 requesting a context regarding UE 102 operating in a connected state (e.g., events 320, 386, and 486 of FIGS. 3A-4C). In response, in block 710, S-BS 104 includes the QoE configuration in a second interface message (e.g., a UE context acquisition response message) (e.g., events 322, 323, 386, and 486 of FIGS. 3A-4C).

[0105] Next, at block 712, S-BS104 determines what to include in the second interface message based on whether S-BS104 had previously suspended the QoE report regarding the QoE configuration from UE102. If it had previously suspended, the flow continues to blocks 714 and 718. At block 714, S-BS104 includes an indication that the QoE report is suspended in the second interface message (e.g., event 323 in FIG. 3G). If S-BS104 has not suspended the QoE report from UE102, depending on the implementation form, the flow may continue to blocks 716 and 718, or may directly continue to block 718. At block 716, S-BS104 includes an indication that the QoE report is resumed in the second interface message (e.g., events 386 and 323 in FIGS. 3F - 3G). At block 718, S-BS104 transmits the second interface message to T-BS106 (e.g., events 386 and 323 in FIGS. 3F and 3G).

[0106] Referring now to FIG. 8, method 800 can be implemented at an appropriate RAN target node and includes receiving a suspension status indication during a reestablishment process and then resuming a QoE report regarding the configuration at the UE. For clarity, method 800 is described with specific reference to RAN 105, S-BS104 as the source node, T-BS106 as the target node, CN 110 or OAM 180 as the QoE node (e.g., network node), and UE 102.

[0107] At block 802, the T-BS 106 receives a re-establishment request message from the UE 102 (e.g., events 318, 386, and 486 of FIGS. 3A - 4C). At block 804, the T-BS 106 transmits a first interface message (e.g., a UE context acquisition request message) requesting a context regarding the UE 102 to the S-BS 104 and / or the CN 110 or the OAM 180 (e.g., events 320, 386, and 486 of FIGS. 3A - 4C). In some implementations, the T-BS 106 transmits the first interface message directly to the CN 110 or the OAM 180. In further implementations, the T-BS 106 transmits the first interface message to the CN 110 or the OAM 180 via the S-BS 104.

[0108] In response, at block 806, the T-BS 106 receives a second interface message (e.g., a UE context acquisition response message) from the S-BS 104 and / or the CN 110 or the OAM 180 (e.g., events 322, 323, 386, and 486 of FIGS. 3A - 4C). Depending on the implementation, the second interface message includes a QoE configuration and / or an indication that the QoE configuration has been at least temporarily suspended or paused. At block 808, the T-BS 106 then transmits a re-establishment message to the UE 102 (e.g., events 324, 386, and 486 of FIGS. 3A - 4C). In implementations where the second interface message includes an indication of the QoE configuration suspension status, the flow continues to block 810. At block 810, the T-BS 106 determines that the UE 102 has been temporarily suspended or paused from transmitting a QoE report due to the indication.

[0109] At block 812, T-BS 106 determines to resume QoE reporting regarding the QoE configuration at UE 102 (e.g., events 362 / 363 in FIGS. 3E-3F). In some implementations, the determination is in response to an indication to resume QoE reporting from CN 110 or OAM 180. In other implementations, the determination is automatic and / or in response to an indication that QoE reporting has been paused. At block 814, T-BS 106 transmits a command to resume QoE reporting to UE 102 (e.g., event 364 in FIGS. 3E-3F). At block 816, T-BS 106 receives one or more QoE reports from UE 102 (e.g., events 368 and 392 in FIGS. 3E-3F), and then, at block 820, transmits the QoE reports to a network node such as TCE / MCE 190 (e.g., events 370 and 392 in FIGS. 3E-3F).

[0110] Referring now to FIG. 9, method 900 can be implemented in a suitable RAN and includes receiving at least one QoE configuration and a reference identifier, assigning a configuration identifier, and transmitting the configuration and the configuration identifier to a UE. For clarity, method 900 is described with specific reference to RAN 105, S-BS 104 as a source node, T-BS 106 as a target node, CN 110 or OAM 180 as a QoE node (e.g., a network node), and UE 102.

[0111] In block 902, RAN 105 communicates with the connected UE 102 (e.g., events 304, 384, 404, and 484 of FIGS. 3A - 4C). In block 904, RAN 105 receives at least one QoE configuration and at least one reference identifier from a QoE node such as CN 110 or OAM 180 (e.g., events 306, 384, 406, and 484 of FIGS. 3A - 4C). In some implementations, each reference identifier is associated with a specific QoE configuration. In other implementations, each reference identifier is associated with multiple QoE configurations and / or a group of QoE configurations. In block 906, RAN 105 assigns a different configuration identifier to each of the QoE configurations (e.g., events 307, 394 of FIGS. 3A - 3G and event 484 of FIGS. 4B - 4C), and in block 908, RAN 105 transmits each configuration and each configuration identifier to UE 102 (e.g., events 308, 384 of FIGS. 3A - 3G and event 484 of FIGS. 4B - 4C).

[0112] In some implementations, the flow continues at block 910 where RAN 105 receives at least one QoE report from UE 102 in response to the transmission of the QoE configuration (e.g., events 312, 384 in FIGS. 3A - 3G and event 484 in FIGS. 4B - 4C). At block 912, RAN 105 then performs a re - establishment procedure with UE 102. At block 914, in response to the execution of the re - establishment procedure, RAN 105 determines to release the QoE configuration, or a group of QoE configurations (e.g., events 338, 388, 351, 349, and 488 in FIGS. 3A - 4B). Depending on the implementation, RAN 105 may make that determination in response to determining that the base station of RAN 105 does not support QoE reporting, or RAN 105 may make that determination in response to receiving a command from CN 110 or OAM 180. In some implementations, the flow continues at block 916 where RAN 105 transmits a downlink message (e.g., a DL RRC message) including at least one configuration identifier to release the QoE configuration or a group of QoE configurations to UE 102 in response to the determination to release the QoE configuration (e.g., events 340, 388, and 488 in FIGS. 3A - 3B and FIGS. 3E - 4B).

[0113] Referring now to FIG. 10, method 1000 can be implemented in a suitable RAN and includes determining to suspend or resume QoE reporting regarding a QoE configuration during or after a re - establishment procedure. For clarity, method 1000 is described with specific reference to RAN 105, S - BS 104 as a source node, T - BS 106 as a target node, CN 110 or OAM 180 as a QoE node (e.g., a network node), and UE 102.

[0114] In block 1002, RAN 105 communicates with UE 102 operating in a state connected via S-BS 104 of RAN 105 (e.g., events 304, 384, 404, and 484 in FIGS. 3A to 4C). In block 1004, RAN 105 sends a QoE configuration to UE 102 to cause UE 102 to start QMC and / or QoE reporting to RAN 105 (e.g., events 308, 384 in FIGS. 3A to 3G and event 484 in FIGS. 4B to 4C). In some implementations, the flow continues with either or both of block 1006 and block 1008. In block 1006, RAN 105 receives a QoE report from UE 102 in response to the transmission of the QoE configuration (e.g., events 312, 384 in FIGS. 3A to 3G and event 484 in FIGS. 4B to 4C). In block 1008, RAN 105 sends a command to UE 102 to temporarily suspend QoE reporting in UE 102 (e.g., events 358 and 394 in FIGS. 3E to 3G). In block 1010, RAN 105 performs a re-establishment procedure with UE 102 to re-establish a connection between T-BS 106 of RAN 105 and UE 102 (e.g., events 386, 387, and 486 in FIGS. 3A to 4C). In block 1012, RAN 105 then determines to perform a QoE reporting operation regarding the QoE configuration during or after the re-establishment procedure (e.g., events 338, 339, 386, 388, 390, 362, 363, 466, 486, 488, or 490 in FIGS. 3A to 4C). Depending on the implementation, the QoE reporting operation can be a pause operation or a resume operation. In some implementations, the determination is in response to receiving a command to perform the operation from CN 110 or OAM 180. In further implementations, the determination is in response to T-BS 106 of RAN 105 receiving an indication of the status of QoE reporting from S-BS 104.

[0115] Next, referring to FIG. 11, method 1100 can be implemented in a suitable UE, and the UE determines whether to resume or continue to suspend QoE reporting based on whether it receives a resumption indication regarding the QoE configuration or a new QoE configuration. For clarity, method 1100 is described with particular reference to RAN 105, S-BS 104 as the source node, T-BS 106 as the target node, CN 110 or OAM 180 as the QoE node (e.g., network node), and UE 102.

[0116] In block 1102, UE 102 communicates with RAN 105 while operating in a connected state (e.g., events 304, 384, 404, and 484 in FIGS. 3A - 4C). In block 1104, UE 102 receives a QoE configuration from RAN 105 (e.g., events 308, 384 in FIGS. 3A - 3G and event 484 in FIGS. 4B - 4C). Receiving the QoE configuration activates QMC and / or QoE reporting in UE 102, and in block 1106, UE 102 executes QMC and / or QoE reporting according to the QoE configuration (e.g., events 310, 384 in FIGS. 3A - 3G and event 484 in FIGS. 4B - 4C). In some implementations, the flow continues to block 1108 where UE 102 transmits a QoE report to RAN 105 according to the QoE configuration (e.g., events 312, 384 in FIGS. 3A - 3G, event 484 in FIGS. 4B - 4C).

[0117] In block 1110, UE 102 receives a QoE suspension command from RAN 105 regarding the QoE configuration (e.g., events 358 and 394 in FIGS. 3E - 3G), and in response, in block 1112, UE 102 temporarily suspends the QoE report regarding the QoE configuration (e.g., events 360 and 394 in FIGS. 3E - 3G). In block 1114, UE 102 detects a communication failure in the communication between UE 102 and RAN 105 (e.g., events 316 and 416 in FIGS. 3A - 4C). In response, in block 1116, UE 102 executes a re - establishment procedure with RAN 105 to re - establish the connection between UE 102 and the base station of RAN 105 (e.g., events 386, 387, and 486 in FIGS. 3A - 4C).

[0118] In block 1118, during the re - establishment procedure, UE 102 determines whether it receives either (i) a QoE resume indication regarding the QoE configuration or (ii) a new QoE configuration that updates the QoE configuration from RAN 105. If UE 102 receives either the QoE resume indication or the new QoE configuration, the flow continues to block 1120, where UE 102 resumes transmitting the QoE report regarding the QoE configuration (e.g., event 366 or 392 in FIGS. 3E - 3G). If UE 102 determines that it receives neither, the flow instead proceeds to block 1122, where UE 102 continues to suspend the QoE report and refrains from transmitting the QoE report regarding the QoE configuration.

[0119] Next, referring to FIG. 12, method 1200 can be implemented in a suitable UE and includes determining whether to suspend or continue QoE reporting based on whether the UE receives a suspension indication during the re-establishment procedure. For clarity, method 1200 is described with particular reference to RAN 105, S-BS 104 as the source node, T-BS 106 as the target node, CN 110 or OAM 180 as the QoE node (e.g., network node), and UE 102.

[0120] In block 1202, UE 102 communicates with RAN 105 while operating in a connected state (e.g., events 304, 384, 404, and 484 of FIGS. 3A - 4C). In block 1204, UE 102 receives a QoE configuration from the RAN (e.g., events 308, 384 of FIGS. 3A - 3G and event 484 of FIGS. 4B - 4C). In response, UE 102 activates QMC and / or QoE reporting and, in block 1206, executes QMC and / or QoE reporting according to the QoE configuration (e.g., events 310, 384 of FIGS. 3A - 3G and event 484 of FIGS. 4B - 4C). In some implementations, the flow continues to block 1208 where UE 102 sends a QoE report to the RAN according to the QoE configuration (e.g., events 312, 384 of FIGS. 3A - 3G and event 484 of FIGS. 4B - 4C). In block 1210, UE 102 detects a communication failure in the communication between UE 102 and RAN 105 (e.g., events 316 and 416 of FIGS. 3A - 4C). In response, in block 1212, UE 102 executes a re-establishment procedure with RAN 105 to re-establish the connection between UE 102 and the base station of RAN 105 (e.g., events 386, 387, and 486 of FIGS. 3A - 4C).

[0121] In block 1214, UE 102 determines whether UE 102 receives a suspension indication regarding the QoE configuration during the re-establishment procedure (e.g., events 358 and 394 in FIGS. 3E to 3G). If a suspension indication is received, the flow continues to block 1216, where the UE suspends transmitting a QoE report regarding the QoE configuration (e.g., events 360 and 394 in FIGS. 3E to 3G). If UE 102 does not receive a suspension indication during the re-establishment procedure, the flow continues to block 1218, where UE 102 continues to transmit a QoE report to the RAN according to the QoE configuration (e.g., events 334, 368, 392 in FIGS. 3A to 3B and 3E to 3G).

[0122] Referring next to FIG. 13, method 1300 can be implemented at an appropriate RAN target node and includes managing QoE measurement collection and QoE reporting. For clarity, method 1300 is described with particular reference to RAN 105, S-BS 104 as a source node, T-BS 106 as a target node, CN 110 or OAM 180 as a QoE node (e.g., a network node), and UE 102.

[0123] In block 1302, a target node such as T-BS106 receives a request from UE102 to re-establish a radio connection (e.g., events 318, 386, and 486 in FIGS. 3A-4C, event 602 in FIG. 6, and events 802, 912, 1010, 1116, and 1212 in FIGS. 8-12). In block 1304, T-BS106 obtains a configuration for QoE reporting (e.g., events 320 / 322 / 323, 386, 486, 512 / 514, 604 / 606, 708 / 718, 804 / 806, 912, and 1010 in FIGS. 3A-10). In block 1306, T-BS106 performs at least one of (i) facilitating reporting QoE measurements regarding UE102 to a QoE node after its acquisition (e.g., events 334 / 336 regarding FIGS. 3A-3B, events 368 / 370, 392, and 434 / 436 regarding FIGS. 3E-4C, events 816 / 818 regarding FIG. 8, and events 1012, 1120, and 1218 regarding FIGS. 10-12), or (ii) releasing the configuration (e.g., events 388, 351, 349, and 488 in FIGS. 3A-4B, event 616 in FIG. 6, and events 914 / 916 in FIG. 9).

[0124] Referring now to FIG. 14, method 1400 can be implemented at an appropriate RAN source node and includes managing QoE measurement collection and QoE reporting. For clarity, method 1400 is described with particular reference to RAN105, S-BS104 as the source node, T-BS106 as the target node, CN110 or OAM180 as the QoE node (e.g., network node), and UE102.

[0125] In block 1402, a source node such as S-BS104 receives a configuration regarding QoE (e.g., events 306, 384, 406, 484, 504 in FIGS. 3A - 5, and event 904 in FIG. 9). In block 1404, S-BS104 receives a request for a context regarding UE102 from a target node of RAN105 such as T-BS106 (e.g., events 320, 386, 486, 512, 604, 708, 804, 912, and 1010 in FIGS. 3A - 10). In block 1406, in response to the reception, S-BS104 transmits a configuration for a QoE report regarding UE102 to the target node (e.g., events 322, 323, 386, 486, 514, 606, 710 / 718, 806, 912, and 1010 in FIGS. 3A - 10).

[0126] Referring now to FIG. 15, method 1500 can be implemented in a suitable UE and includes managing QoE measurement collection and QoE reporting. For clarity, method 1500 is described with particular reference to RAN105, S-BS104 as a source node, T-BS106 as a target node, CN110 or OAM180 as a QoE node (e.g., a network node), and UE102.

[0127] In block 1502, UE 102 reports QoE measurements to a QoE node such as CN 110 or OAM 180 via a source node of RAN 105 such as S-BS 104 (e.g., events 312, 384, 484, 510, 706, 816 / 818, 910, 1006, 1108, and 1208 in FIGS. 3A-5 and FIGS. 7-12). In block 1504, UE 102 detects a communication failure between UE 102 and the source node (e.g., events 316, 416, 1114, and 1210 in FIGS. 3A-4C and FIGS. 11-12). In block 1506, in response to the detection, UE 102 performs a radio connection re-establishment procedure with a target node of RAN 105 such as T-BS 106 (e.g., events 386, 387, 486, 1116, and 1212 in FIGS. 3A-4C and FIGS. 11-12). In block 1508, in response to receiving an indication from the target node, UE 102 determines to perform a QoE operation (e.g., events 1118 and 1214 in FIGS. 11-12).

[0128] The following list of examples reflects various embodiments explicitly contemplated by the present disclosure.

[0129] Example 1 A method for managing QoE reporting for a user equipment (UE) initially configured to report quality of experience (QoE) measurements to a QoE node via a source node of a radio access network (RAN), the method implemented at a target node of the RAN and including receiving, by processing hardware, a request from the UE to re-establish a radio connection, obtaining, by the processing hardware, a configuration for QoE reporting, and performing at least one of (i) facilitating, by the processing hardware, reporting of QoE measurements from the UE to the QoE node after the obtaining, or (ii) releasing the configuration.

[0130] Example 2 The method of Example 1 including receiving a first command to change the configuration and transmitting a second command to change the configuration to the UE.

[0131] Example 3: The method of Example 1, including receiving a first command to release a configuration and transmitting a second command to release that specific configuration to the UE.

[0132] Example 4: The method of Example 2 or 3, including receiving a reference identifier corresponding to a configuration and identifying that configuration from among a plurality of configurations related to the UE based on that reference identifier.

[0133] Example 5: The method of Examples 2 to 4, including transmitting a second command in response to determining that the configuration is invalid with respect to the target node.

[0134] Example 6: The method of Example 1, including releasing the configuration at the target node after obtaining the configuration.

[0135] Example 7: The method of Example 6, including transmitting a notification to the QoE node that the target node has released the configuration in response to the release of the configuration.

[0136] Example 8: The method of Example 6, where the release is in response to determining that the target node does not support QoE reporting.

[0137] Example 9: The method of any of Examples 1 to 8, further including determining that the QoE report has been suspended, after obtaining the configuration, deciding to resume the QoE report, and transmitting a command to resume the QoE report to the UE.

[0138] Example 10: The method of Example 9, where deciding to resume is in response to receiving an indication to resume the QoE report from the QoE node.

[0139] Example 11: The method of Example 9 or 10, where determining that the QoE report has been suspended includes receiving a suspension status indication from the QoE node.

[0140] Example 12 The configuration is the first configuration, and the method is any of the methods of Examples 1 to 11, including receiving, from a QoE node, a second configuration for QoE reporting, and sending, to a UE, a command to start a new QoE reporting session using the second configuration.

[0141] Example 13 Any of the methods of Examples 1 to 8, including receiving, from a source node, an indication that QoE reporting has been suspended, and after receiving the indication that QoE reporting has been suspended, sending, to a UE, an indication to resume QoE reporting.

[0142] Example 14 The method of Example 13, including receiving a single message including an indication that QoE reporting has been suspended and its configuration.

[0143] Example 15 The method of Example 13 or 14, wherein obtaining the configuration includes receiving the configuration during a re-establishment procedure, and the indication to resume QoE reporting is included in a radio reconfiguration message.

[0144] Example 16 Any of the methods of Examples 1 to 8, wherein obtaining the configuration includes receiving the configuration during a re-establishment procedure, and the method further includes determining to suspend QoE reporting and sending, to a UE, an indication to suspend QoE reporting during the re-establishment procedure.

[0145] Example 17 The method of Example 16, wherein determining to suspend QoE reporting is in response to receiving, from a source node, a message including an indication to suspend QoE reporting and its configuration.

[0146] Example 18 A target base station of a radio access network (RAN) equipped with processing hardware and configured to implement the method according to any of Examples 1 to 17.

[0147] Example 19 A method for managing a quality of experience (QoE) report for a user equipment (UE) with respect to a QoE node, the method being implemented at a source node in a radio access network (RAN), and including receiving, by processing hardware, a configuration regarding QoE, receiving, by processing hardware, a request for a context regarding the UE from a target node of the RAN, and in response to the receiving, transmitting, by processing hardware, a configuration for a QoE report regarding the UE to the target node.

[0148] Example 20 The method of Example 19 including determining to release the configuration after transmitting the configuration to the target node, and releasing the configuration at the source node.

[0149] Example 21 The method of Example 20 including transmitting, in response to the release of the configuration, an indication that the source node has released the configuration to the QoE node.

[0150] Example 22 The method according to any one of Examples 19 to 21 including determining to suspend the QoE report, and transmitting a command to suspend the QoE report to the UE.

[0151] Example 23 The method of Example 22, wherein determining to suspend is in response to receiving an indication to pause the QoE report from the QoE node.

[0152] Example 24 The method of Example 22 including transmitting an indication that the QoE report has been suspended to the QoE node.

[0153] Example 25 The method according to any one of Examples 22 to 24, wherein transmitting the configuration further includes transmitting, in response to receiving the request for the context, an indication that the QoE report has been suspended to the target node.

[0154] Example 26. A method according to any one of Examples 19 to 25, including receiving an indication to perform a QoE operation from a QoE node, attempting to send a radio reconfiguration command to a UE in response to receiving the indication to perform the QoE operation, and determining that the attempt has failed.

[0155] Example 27. A method according to Example 26, including sending an indication to a QoE node that sending a radio reconfiguration command has failed.

[0156] Example 28. A method according to Example 26 or 27, wherein the indication to perform a QoE operation is one of (i) a command to activate a QoE report using the configuration, (ii) a command to release the configuration, or (iii) a command to change the configuration.

[0157] Example 29. The configuration for QoE reporting is at least one configuration, and the method includes receiving at least one configuration and at least one reference identifier from a QoE node, assigning a configuration identifier to each of the at least one configuration, and in response to receiving a request for context, sending the at least one configuration, the at least one reference identifier, and the configuration identifier for each of the at least one configuration to a target node, according to any one of Examples 19 to 28.

[0158] Example 30. A method according to any one of Examples 19 to 29, including determining whether to send a suspension status indication or a resume indication to a UE depending on whether a QoE report for the configuration is suspended in response to receiving a request for context.

[0159] Example 31. A source base station of a radio access network (RAN) equipped with processing hardware and configured to implement a method according to any one of Examples 19 to 30.

[0160] Example 32 A method for managing an experience quality (QoE) report, the method being implemented in a user equipment (UE), the method including: reporting, by processing hardware, QoE measurements to a QoE node via a radio access network (RAN); detecting, by processing hardware, a communication failure between the UE and a source node of the RAN; in response to the detection, performing, by processing hardware, a radio connection re-establishment procedure with a target node of the RAN; and determining, by processing hardware, to perform a QoE operation in response to receiving an indication from the target node.

[0161] Example 33 Determining to perform a QoE operation includes suspending, in response to receiving a message from the RAN, a QoE report regarding a first configuration for QoE reporting, and determining, by the UE, whether to resume the QoE report based on whether the UE receives (i) an indication to resume the QoE report regarding the first configuration or (ii) at least one of a second configuration for QoE reporting during the re-establishment procedure, in the method of Example 32.

[0162] Example 34 The method of Example 32 further includes determining, by the UE, whether to suspend the QoE report based on whether the UE receives an indication to temporarily stop the QoE report regarding a configuration for QoE reporting during the re-establishment procedure.

[0163] Example 35 A user equipment including processing hardware and configured to implement the method according to any one of Examples 32 to 34.

[0164] The following further considerations apply to the above description.

[0165] In some implementation forms, the reference ID can be a QoE reference ID. In other implementation forms, the reference ID can be a service type. In still other implementation forms, the reference ID can be the aforementioned CN configuration ID or OAM configuration ID. In still other implementation forms, the reference ID can be the aforementioned trace ID.

[0166] In some implementation forms, "message" is used and can be replaced by "information element (IE)". In some implementation forms, "IE" is used and can be replaced by "field". In some implementation forms, "configuration" can be replaced by "multiple configurations" or configuration parameters.

[0167] The user device (e.g., UE102) on which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smartphone, tablet computer, laptop computer, mobile gaming console, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or another personal media device, wearable device such as a smartwatch, wireless hotspot, femtocell, or broadband router. Further, in some cases, the user device may be embedded in an in-vehicle head unit or an electronic system such as an advanced driver assistance system (ADAS). Additionally, the user device can operate as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, computer-readable memory, user interface, one or more network interfaces, one or more sensors, and others.

[0168] Some embodiments are described in this disclosure as including logic or some components or modules. A module may be a software module (e.g., code or machine-readable instructions stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing some operations and can be configured or arranged in a certain manner. A hardware module can include dedicated circuitry or logic (e.g., as a dedicated processor such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) permanently configured to perform some operations. Also, a hardware module may include programmable logic or a programmable circuit (e.g., included within a dedicated processor or within another programmable processor) temporarily configured by software to perform some operations. The decision of whether to implement a hardware module in dedicated permanently configured circuitry or in temporarily configured circuitry (e.g., configured by software) may be motivated by cost and time considerations.

[0169] When implemented in software, the technology can be provided as part of an operating system, a library used by multiple applications, a particular software application, or the like. The software can be executed by one or more general-purpose processors or by one or more dedicated processors.

[0170] Upon reading this disclosure, additional structural and functional designs for managing radio bearers through the principles disclosed herein, as well as alternative structural and functional designs, will be recognized by those skilled in the art. For this reason, while specific embodiments and application examples have been illustrated and described, it should be understood that the disclosed embodiments are not limited to the configurations and components themselves disclosed herein. Various modifications, changes, and alterations that will be apparent to those skilled in the art may be made to the configurations, operations, and details of the methods and apparatuses disclosed herein without departing from the spirit and scope defined in the appended claims.

Explanation of Reference Numerals

[0171] 100 Wireless communication system 102 User equipment 104, 104A, 104B, 106, 106A, 106B Base station 105 Radio access network 106 Target base station 110 Core network 111 Evolved Packet Core 112, 116 Gateway 114 Mobility Management Entity 124, 126 Cell 130, 140, 150 Processing hardware 132, 142, 152 RRC Controller 134, 144, 154 QoE Measurement Controller 160 5G Core 162 User Plane Function 164 Access and Mobility Management Function 166 Session Management Function 172 Central Unit 172A, 172B Logical Node 174 Distributed Unit 180 Operation and Maintenance Management Node 190 Trace Collection Entity and / or Multi-cell / Multicast Coordination Entity 200 protocol stack Layers 202A, 202B, 204A, 204B, 206A, 206B, 208, 210, 212

Claims

1. A method for managing a QoE report for a user equipment (UE) that reports QoE measurements to a QoE node via a source node of a radio access network (RAN), the method being implemented at a target node of the RAN, receiving, from the UE, a request to re - establish a RAN connection after a RAN connection failure; obtaining a configuration for the QoE measurement from the source node; including at least one of: (i) receiving, from the UE, a QoE report for reporting post - failure QoE measurements to the QoE node according to the configuration, or (ii) releasing the configuration.

2. determining that the QoE report is suspended; after obtaining the configuration, determining to resume the QoE report; sending a command to resume the QoE report to the UE The method according to claim 1, further comprising.

3. The obtaining step receiving, from the source node, a reference identifier corresponding to the configuration; identifying the configuration from among a plurality of configurations related to the UE based on the reference identifier The method according to claim 1, including.

4. receiving, from the source node, an indication that the QoE report is suspended; after receiving the indication that the QoE report is suspended, sending an indication to resume the QoE report to the UE The method according to claim 1, including.

5. The method according to claim 4, including receiving a single message including both the indication that the QoE report is suspended and the configuration.

6. The step of obtaining the configuration includes receiving the configuration during a re - establishment procedure, and the indication to resume the QoE report is included in a radio re - configuration message. The method according to claim 4.

7. The step of obtaining the configuration includes receiving the configuration during a re - establishment procedure, and the method includes determining to suspend the QoE report; sending an indication to suspend the QoE report to the UE during the re - establishment procedure The method according to claim 1, further comprising. A method for managing a QoE report for a user equipment (UE) with respect to a Quality of Experience (QoE) node, the method being implemented at a source node in a radio access network (RAN), receiving, from the QoE node, a configuration for QoE measurement; receiving, from a target node of the RAN, a request for a context regarding the UE after a RAN connection failure occurs; in response to receiving the request after the RAN connection failure occurs, sending the configuration for QoE report to the target node; and the method includes these steps.

9. determining to release the configuration after sending the configuration to the target node; releasing the configuration at the source node; and the method according to claim 8 includes these steps.

10. determining to suspend the QoE report; sending a command to suspend the QoE report to the UE; and the method according to claim 8 includes these steps.

11. receiving, from the QoE node, an indication to perform a QoE operation; attempting to send a radio reconfiguration command to the UE in response to receiving the indication to perform the QoE operation; determining that the attempt has failed; and the method according to claim 8 includes these steps.

12. The indication to perform the QoE operation is (i) a command to activate a QoE report using the configuration, (ii) a command to release the configuration, or (iii) a command to change the configuration and is one of these, and the method according to claim 11.

13. The configuration for QoE report is at least one configuration, and the method includes receiving, from the QoE node, the at least one configuration and at least one reference identifier; assigning a configuration identifier to each of the at least one configuration; in response to receiving the request for the context, sending the at least one configuration, the at least one reference identifier, and the configuration identifier for each of the at least one configuration to the target node; and the method according to claim 8 includes these steps.

14. In response to receiving the request for the context, determining whether to send a suspension status indication or a resume indication to the UE depending on whether the QoE report for the configuration is suspended, the method according to claim 8.

15. A method for managing a quality of experience (QoE) report, the method being implemented in a user equipment (UE), reporting QoE measurements to a QoE node via a radio access network (RAN); detecting a communication failure between the UE and a source node of the RAN; in response to the detection, sending a request to re-establish a RAN connection to a target node of the RAN and performing a radio connection re-establishment procedure with the target node as a counterpart; determining to perform a QoE operation in response to receiving an indication from the target node; and a method comprising:

16. The step of determining to perform the QoE operation comprises suspending a QoE report for a first configuration for QoE reporting in response to receiving a message from the RAN; while the UE is in the re-establishment procedure, (i) an indication to resume the QoE report for the first configuration, or (ii) a second configuration for QoE reporting determining whether to resume the QoE report based on whether at least any one of the above is received, the method according to claim 15.

17. An apparatus comprising processing hardware and configured to implement the method according to any one of claims 1 to 16.

Images