Quality of experience and radio access network visible quality of experience reporting upon radio link failure in new radio dual connectivity

Abstract

A communication device may be in a communication network that includes a first network node and a second network node that provide dual connectivity to the communication device. The communication device may determine (1410) that a failure has occurred during sending the report to the first network node. The report may be a Quality of Experience (QoE) report and / or a Radio Access Network Visible (QoE) "RVQoE" report. The communication device may suspend (1415) to send the report to the first network node in response to determining that the failure has occurred. The communication device may perform (1420) an action associated with the reporting in response to determining that a failure has occurred.

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems, and more particularly, to handling quality of experience ("QoE") and radio access network seen QoE ("RVQoE") reporting upon radio link failure in New Radio Dual Connectivity ("NR-DC"). Background Art

[0002] Figure 1 An example of a current fifth generation radio access network ("NG-RAN") architecture is shown. The NG-RAN architecture may be further described as follows. The NG-RAN includes a set of fifth generation ("5G") base stations (referred to herein as gNBs) connected to a fifth generation core network ("5GC") via a next generation ("NG") interface. The gNBs may support frequency division duplex ("FDD") mode, time division duplex ("TDD") mode, or dual mode operation. The gNBs may be interconnected via an Xn-C interface. The gNBs may include a gNB central unit ("CU") and a gNB distributed unit ("DU"). The gNB-CU and the gNB-DU are connected via an F1 logical interface. One gNB-DU is connected to only one gNB-CU. For resiliency, the gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. NG, Xn-C, and F1 are logical interfaces. The NG-RAN is layered into a radio network layer ("RNL") and a transport network layer ("TNL"). The NG-RAN architecture (e.g., NG-RAN logical nodes and interfaces therebetween) is defined as a part of the RNL. For each NG-RAN interface (e.g. NG, Xn-C and F1), the relevant TNL protocols and functions are specified. TNL provides services for user plane transport and signaling transport.

[0003] For NG-RAN, the NG and Xn-C interfaces of the gNB consisting of gNB-CU and gNB-DU are terminated in the gNB-CU. For EN-DC, the S1-U and X2-C interfaces of the gNB (including gNB-CU and gNB-DU) are terminated in the gNB-CU. The gNB-CU and the connected gNB-DU are visible as gNBs only to other gNBs and 5GC.

[0004] The gNB may also be connected to a Long Term Evolution ("LTE") base station (referred to herein as an eNB) via an X2 interface. Another architectural option is that an LTE eNB connected to an Evolved Packet Core network is connected via an X2 interface to a so-called nr-gNB. The latter is a gNB that is not directly connected to the Core Network (CN) but is connected to the eNB via X2 for the sole purpose of performing dual connectivity.

[0005] Figure 1The architecture in can be extended by splitting the gNB-CU into two entities: a gNB-CU-User Plane (“UP”), which serves the user plane and hosts the Packet Data Convergence Protocol (“PDCP”); and a gNB-CU-Control Plane (“CP”), which serves the control plane and hosts the PDCP and Radio Resource Control (“RRC”) protocols. The gNB-DU hosts the Radio Link Control (“RLC”) / Medium Access Control (“MAC”) / Physical Layer (“PHY”) protocols.

[0006] Other standardization groups, such as Open Radio Access Network ("ORAN"), have further extended the above architecture and, for example, have split the gNB-DU into two additional nodes connected by a fronthaul interface. The lower node of the split gNB-DU may include the PHY protocol and radio frequency ("RF") parts, and the upper node of the split gNB-DU may host the RLC and MAC. In ORAN, the upper node is referred to as O-DU and the lower node is referred to as O-RU.

[0007] The NG-RAN may also include a set of ng-eNBs, and the ng-eNB may include an ng-eNB-CU and one or more ng-eNB-DUs. The ng-eNB-CU and the ng-eNB-DU may be connected via a W1 interface. Although the present disclosure may generally relate to gNBs, the general principles may apply to other radio access technologies, for example, these principles may apply to ng-eNBs and the W1 interface.

[0008] Figure 2 An example of an architecture in which the gNB-CU-CP is separated from the gNB-CU-UP is shown. The gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs. The gNB-CU-CP is connected to the gNB-DU via the F1-C interface. The gNB-CU-UP is connected to the gNB-DU via the F1-U interface. The gNB-CU-UP is connected to the gNB-CU-CP via the E1 interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP. One gNB-DU may be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP. One gNB-CU-UP may be connected to multiple DUs under the control of the same gNB-CU-CP.

[0009] In dual connectivity, a UE capable of multiple transmit / receive can be connected to more than one RAN node. The RAN nodes can be of the same RAT (both primary and secondary in NR or LTE, respectively) or different RATs (e.g. one primary LTE node and one secondary NR node). Summary of the invention

[0010] According to some embodiments, there is provided a method of operating a communication device in a communication network including a first network node and a second network node, the first network node and the second network node providing dual connectivity to the communication device. The method includes: determining that a failure has occurred during the sending of a report to the first network node. The report includes a quality of experience ("QoE") report and / or a radio access network visible QoE ("RVQoE") report. The method also includes: in response to determining that a failure has occurred, suspending the sending of the report to the first network node. The method also includes, in response to determining that a failure has occurred, performing an action associated with the report.

[0011] According to other embodiments, a method of operating a first network node in a communication network including a second network node is provided. The first network node and the second network node provide dual connectivity to a communication device. The method includes: determining that a failure has occurred during the transmission of a report from the communication device to the second network node. The report includes a quality of experience ("QoE") report and / or a radio access network visible QoE ("RVQoE") report. The method also includes: in response to determining that a failure has occurred, communicating with the communication device.

[0012] According to other embodiments, a communication device, a first network node, a second network node, a computer program, a computer program product, a non-transitory computer-readable medium, a host or a system is provided to perform the above method.

[0013] Certain aspects of the present disclosure and embodiments thereof may provide technical advantages.Some embodiments enable RVQoE and / or QoE reporting to continue in the event of an SCG failure or an MCG failure (eg, where a fast MCG recovery procedure is used). BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings illustrate certain non-limiting embodiments of the inventive concept, and are included to provide a further understanding of the present disclosure, and are incorporated into and constitute a part of this application. In the drawings:

[0015] Figure 1 is a schematic diagram illustrating an example of a Next Generation Radio Access Network ("NG-RAN") overall architecture;

[0016] Figure 2 is a schematic diagram showing an example of an overall architecture in which a gNB-Central Unit-Control Plane (“CU-CP”) is separated from a gNB-Central Unit-User Plane (“CU-UP”);

[0017] Figure 3 is a signal flow diagram illustrating an example of end-to-end signaling for configuring QoE measurements;

[0018] Figure 4 is a signal flow diagram illustrating an example of activation of signaling-based QoE in NR;

[0019] Figure 5 is a signal flow diagram illustrating an example of RRC configuration and reporting of QoE measurements;

[0020] Figure 6 is a diagram showing an example of an ASN.1 code for an AppLayerMeasConfig information element;

[0021] Figure 7 is a table showing an example of AppLayerMeasConfig field description;

[0022] Figure 8 is a table showing an example of RAN-VisibleParameters field description;

[0023] Fig. 9 is a table showing an example of conditional presence associated with AppLayerMeasConfig IE;

[0024] Fig.10 is a diagram showing an example of an ASN.1 code of a MeasurementReportAppLayer message;

[0025] Fig.11 is a table showing an example of MeasReportAppLayer field description;

[0026] Fig.12 is a table showing an example of RAN-VisibleMeasurements field description;

[0027] Fig.13 is a table showing an example of an ASN.1 code for an AppLayerMeasConfig IE according to some embodiments;

[0028] Fig.14 is a flow chart illustrating an example of operations performed by a communication device according to some embodiments;

[0029] Fig.15 is a flow chart illustrating an example of operations performed by a network node according to some embodiments;

[0030] Fig.16 is a block diagram of a communication system according to some embodiments;

[0031] Fig.17 is a block diagram of a user equipment according to some embodiments;

[0032] Fig.18 is a block diagram of a network node according to some embodiments;

[0033] Fig.19 is a block diagram of a host according to some embodiments, which may be Fig.16 An embodiment of a host;

[0034] Fig. 20 is a block diagram of a virtualization environment according to some embodiments; and

[0035] Fig.21 A communication diagram illustrating a host communicating with a user device via a network node over a partially wireless connection according to some embodiments. DETAILED DESCRIPTION

[0036] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of subject matter to those skilled in the art, wherein examples of embodiments of the inventive concept are shown. However, the inventive concept can be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided so that the disclosure will be comprehensive and complete, and the scope of the inventive concept will be fully conveyed to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. A component from one embodiment may be assumed by default to be present in / used in another embodiment.

[0037] A Quality of Experience ("QoE") framework is described below. QoE measurements (sometimes referred to as "application layer measurements") have been specified for Long Term Evolution ("LTE") and Universal Mobile Telecommunications System ("UMTS"), and are being specified for New Radio ("NR") in 3rd Generation Partnership Project ("3GPP") Release 17. The purpose of application layer measurements is to measure the end-user experience when using certain applications. QoE measurements are currently supported for streaming services and mobile telephone service over Internet Protocol Multimedia Subsystem ("MTSI") services. For NR, at least virtual reality ("VR") may be added to the list of services for which QoE measurements are specified and supported.

[0038] The process of conventional QoE is similar in NR, LTE and UMTS, and the general principles are as follows. Quality of Experience Measurement Collection ("QMC") enables the configuration of application layer measurements in the user equipment ("UE") (also known as the communication device) and sends the QoE measurement result file (commonly referred to as QoE report) to the network through radio resource control ("RRC") signaling. The application layer measurement configuration (also known as QoE measurement configuration or QoE configuration) received by the radio access network ("RAN") from the operation, administration and maintenance ("OAM") system or the core network ("CN") is encapsulated in a transparent container, which is forwarded to the UE in a downlink RRC message. The application layer measurement report (also known as QoE report) received by the UE access stratum ("AS") or UE RRC layer from the higher layer (application layer) of the UE is encapsulated in a transparent container and sent to the network in an uplink RRC message. The RAN then forwards the QoE report to the measurement collector entity (MCE).

[0039] Configuration data related to QoE measurements (often referred to as application layer measurements in standard specifications) is received by the gNB from the OAM and consists of an indication of the type of service, an indication of the area in which the measurements are to be performed (denoted as area range), the Internet Protocol ("IP") address of the entity to which the collected measurements (e.g., QoE reports) should be sent (often referred to as the MCE, spelled Measurement Collector Entity or Measurement Collection Entity, but this entity may also sometimes be referred to as a Trace Collection Entity), and a set of instructions on the details of what type of measurements should be performed and how to perform them. These instructions are intended for the application layer in the UE and are placed in a "container" that the network entity that processes it (e.g., forwards it to the UE) and the UE access layer cannot interpret and do not attempt to read.

[0040] This container is forwarded to the UE in RRC signaling along with the indicated service type. For measurements under RRC_CONNECTED, the area is maintained in the gNB and the network ensures that the UE measures in the correct area by configuring when the UE starts and stops measuring. Area scopes are defined in terms of cells or network related areas. In UMTS, area scopes are defined as a list of cells, a list of routing areas, or a list of tracking areas. In LTE and NR, area scopes are defined as a list of cells or a list of tracking areas.

[0041] There are two types of QoE (and specifically, QoE configuration): management-based QoE configuration and signaling-based QoE configuration. In both cases, the QoE configuration originates from the OAM system or some other management entity (e.g., handling customer satisfaction). These entities are sometimes referred to as the OAM system in this article (where the OAM system also includes other entities). For management-based QoE (sometimes referred to as m-based QoE in this article), the OAM system is typically interested in general QoE statistics from a specific area (which is configured as an area scope). The m-based QoE configuration is sent directly from the OAM system to the RAN nodes that control the cells within the area scope. Each RAN node then selects UEs that are within the area scope (and also meet any other relevant conditions, such as supporting relevant application / service types) and sends m-based QoE configurations to these UEs.

[0042] For signaling-based QoE (sometimes referred to herein as S-based QoE), the OAM system is interested in collecting QoE measurements from a specific UE (e.g., because the UE's user has filed a complaint). The OAM system sends the S-based QoE configuration to the Home Subscriber Server ("HSS") (in Evolved Packet System ("EPS") / LTE) or Unified Data Management ("UDM") (in 5GS / NR), which forwards the QoE configuration to the UE's current core network node (e.g., the Mobility Management Entity ("MME") in EPS / LTE or the Access and Mobility Management Function ("AMF") in 5G / NR). The CN then forwards the S-based QoE configuration to the RAN node serving the relevant UE, and the RAN forwards it to the UE.

[0043] What is forwarded to the UE is a service type indication and a container with measurement instructions. The UE is unaware whether the received QoE configuration is m-based or s-based. In legacy systems, the QoE framework is integrated with the tracing function and a tracing ID is associated with each QoE configuration. In NR, the QoE function is logically separated from the tracing function, but the tracing signaling mechanism will still be partially reused. In NR and LTE, a globally unique QoE reference (consisting of Mobile Country Code ("MCC") + Mobile Network Code ("MNC") + QMC Identifier ("ID"), where the QMC ID is a 24-bit string) will be associated with each QoE configuration. The QoE reference is included in the container with the measurement instructions and is also sent to the RAN (e.g., gNB in ​​NR). For communications between the gNB and the UE, the QoE Reference is replaced by a shorter identifier (denoted as measConfigAppLayerId) that is locally unique within the UE (e.g., there is a one-to-one mapping between measConfigAppLayerId and the QoE Reference for each QoE configuration provided to the UE). The measConfigAppLayerId is stored in the UE access stratum and is also forwarded in AT commands (which are the type of instructions used in communications between the modem part of the UE and the application layer of the UE) together with the service type indication and the container with measurement instructions.

[0044] A report with the collected QoE measurements (QoE Report) is sent from the UE Application Layer to the UE Access Layer, which forwards it to the RAN, which forwards it to the MCE. These QoE measurements are placed in a "container" that is uninterpretable to the UE Access Layer and the RAN. The QoE Report can be configured to be sent periodically or only at the end of an application session. In addition, the RAN can instruct the UE to suspend QoE reporting (for example, in case the cell / gNB is in an overloaded state).

[0045] The RAN is not aware when an application session with an associated QoE measurement session is ongoing, and the UE access layer is not automatically aware of this. To mitigate this, session start / stop indications have been introduced, which are sent from the application layer in the UE to the UE AS, and from the UE AS to the RAN. When the application session and the associated QoE measurement session end, a session end indication is sent.

[0046] The RAN may decide to release the QoE configuration in the UE at any time as an implementation based decision. Typically this is done when the UE has moved out of the area configured for QoE measurements (often referred to as the area scope) and the measurement session has ended.

[0047] An extension of the QoE framework that has been implemented in 3GPP Release 17 is the concept of RAN Visible QoE ("RVQoE"). Conventional QoE reports are intended for the MCE, which is an entity outside the RAN (e.g., part of the OAM system), and the RAN cannot read the QoE reports (at least not according to the specification, although gNB / eNB implementations are not prevented from doing so). In contrast, the reported RVQoE metrics are intended for the RAN and are transmitted to the RAN in a format that the RAN understands. The RVQoE metrics are derived from the conventional QoE metrics, collected and compiled in reports by the UE application layer, and transmitted to the RAN so that the RAN can use the reports for various types of optimizations. As an example, when the RAN receives a RVQoE report during an ongoing application session, the RAN can perform adaptation actions to affect the QoE of the associated application session while the application session is ongoing, such as changing various parameters related to the scheduling of the UE and the data flows associated with the application session.

[0048] Figure 3 End-to-end signaling for configuring QoE measurements is shown in . At operation 310, the NM sends an activateAreaQMCjob message to the DM / EM. In some examples, the activateAreaQMCjob message includes a service type, an area range, a slice range, a QoE CE address, a PLMN target, a QoE target, a QoE reference, and / or a QMC profile. At operation 320, the DM / EM forwards the activateAreaQMCjob message to the gNB. At operation 330, the gNB starts looking for UEs that match the criteria. At operation 340, the gNB sends an RRCReconfiguration message to the UE AS. At operation 350, the UE AS sends a +CAPPLEVMC message to the UE application layer. In some examples, the RRCReconfiguration message and the +CAPPLEVMC message include information from the activateAreaQMCjob message.

[0049] At operation 360, the UE application layer starts the application and QoE measurement collection. At operation 370, the UE application layer sends a +CAPPLEVMR message to the UE AS. At operation 380, the UE AS sends a MeasurementReport to the gNB. In some examples, the +CAPPLEVMR message and the MeasurementReport include MeasConfigAppLayerId. At operation 382, ​​the gNB sends a notification to the NM. In some examples, the notification includes an indication to log the session.

[0050] At operation 384, the UE application layer measurement collection is complete. At operation 386, the UE application layer sends a +CAPPLEVMR message to the UE AS. At operation 388, the UE AS sends a MeasurementReport message to the gNB. In some examples, the +CAPPLEVMR message and the MeasurementReport message include information associated with the measurements collected by the UE application layer. At operation 390, the gNB sends a report to the MCE.

[0051] Figure 4 4 shows the activation of signaling-based QoE in NR. First, the UE may obtain access to the network through a registration procedure. Then, at operation 410, the MnS consumer sends a message to the UDM to create a MOI QMC job. The UDM may send a Nudm_SDM data change notification to the AMF based on the information in the message from the MnS consumer (operation 420). At operation 430, the AMF sends a UE context modification request to the gNB. The gNB verifies whether the UE capabilities match the criteria of the service type indicated in the UE context modification request (operation 440). At operation 450, the gNB sends an RRCReconfiguration message to the UE AS. At operation 460, the UE AS sends a +CAPPLEVMCNR to the UE application layer.

[0052] At operation 470, the UE application layer starts application and QoE measurement collection. At operation 480, the UE application layer sends a +CAPPLEVMRNR message to the UE AS. At operation 482, the UE AS sends a MeasurementReprotAppLayer message to the gNB.

[0053] At operation 484, the UE application layer measurement collection is complete. At operation 486, the UE application layer sends +CAPPLEVMRNR to the UE AS. At operation 488, the UE AS sends a MeausmentReprotAppLayer message to the gNB. At operation 490, the gNB sends a Report-Container to the MCE.

[0054] The following describes the configuration and reporting of QoE and RVQoE measurements in RRC. The configuration of QoE and RVQoE measurements is done by the RRC message RRCReconfiguration and the reporting is done according to Figure 5 The signal flow shown is sent in the RRC message MeasurementReportAppLayer.

[0055] Figure 5An example of RRC configuration and reporting of QoE measurements is shown. As shown, the gNB sends an RRCReconfiguration message to the UE. The RRCReconfiguration message may include an information element AppLayerMeasConfig. In some examples, the RRCReconfiation message and / or the AppLayerMeasConfig IE include a configuration container for configuring conventional QoE or RRC parameters for configuring RVQoE. Figure 6 An example of an ASN.1 code of an AppLayerMeasConfig IE indicating configuration of application layer measurement is shown. Figure 7 An example of description of fields in the AppLayerMeasConfig IE is shown. The AppLayerMeasConfig field may include: measConfigAppLayerContainer; pauseReporting; ran-VisibleParameters; rrc-SegAllowed; serviceType; and transmissionOfSessionStartStop. Figure 8 An example of field description in the RAN-VisibleParameters field of the AppLayerMeasConfig IE is shown. The RAN-VisibleParameters field may include: numberOfBufferLevelEntires (e.g., including the maximum number of buffer level entries that can be reported for RAN-visible application layer measurements); ran-VisiblePeriodicity (e.g., indicating the periodicity of RAN-visible application layer measurement reports); and reportPlayoutDelayForMediaStartup (e.g., indicating whether the UE should report media start play delay for RAN-visible application layer measurements). Fig. 9 An example of conditional presence associated with the AppLayerMeasConfig IE is shown.

[0056] return Figure 5 , the UE may respond by sending an RRCReconfigurationComplete message to the gNB. After a period of time has passed, the UE may further send a MeasurementReportAppLayer message to the gNB. In some examples, the MeasurementReportAppLayer includes the AppLayerMeasConfig IE. Fig.10An example of the ASN.1 code of the MeasurementReportAppLayer IE is shown, which includes a report container for normal QoE and / or RRC parameters for reporting RVQoE. The MeasurementReportAppLayer message is used to send an application layer measurement report. Fig.11 An example of MeasReportAppLayer field description is shown. The MeasReprotAppLayer field includes: appLayerSessionSatus; measReportAppLayerContainer; and ran-VisibleMeasurements. Fig.12 An example of a RAN-VisibleMeasurements field description is shown. The RAN-VisibleMeasurements field may include appLayerBufferLevelList (e.g., indicating a list of application layer buffer levels); playoutDelayForMediaSartup (e.g., indicating an application layer media start play delay); and pdu-SessionIdList (e.g., including identification of PDU sessions).

[0057] In existing specifications, the network may only configure RVQoE if a corresponding configuration of conventional QoE also exists in the UE. Figures 6 to 12 A further description can be found in TS 38.331 v17.2.0.

[0058] AT commands are used for communication between the AS (Radio) layer and the application layer in the UE. AT commands are used in QoE to transfer configurations from the RRC layer to the application and to transfer reports from the application layer to the RRC layer.

[0059] In 3GPP Release 12, the LTE feature Dual Connectivity (“DC”) was introduced to enable a UE to connect in two cell groups, each controlled by an LTE access node eNB, labeled Master eNB (MeNB) and Secondary eNB (SeNB). The UE has only one RRC connection with the network. In 3GPP, the DC solution has evolved since then and is now also specified for NR and between LTE and NR. Multi-Connectivity (“MC”) is the case when more than 2 nodes are involved. With the introduction of 5G, the term MR-DC (Multi-Radio Dual Connectivity) is defined as a generic term for all dual connectivity options that include at least one NR access node. Using the MR-DC generic terminology, the UE is connected in a Primary Cell Group (“MCG”) controlled by a Primary Node (“MN”) and in a Secondary Cell Group (“SCG”) controlled by a Secondary Node (“SN”).

[0060] In addition, in MR-DC, when dual connectivity is configured for the UE, carrier aggregation can also be used in each of the two cell groups MCG and SCG. In this case, within the primary cell group MCG controlled by the MN, the UE can use one PCell and one or more SCells. And within the secondary cell group SCG controlled by the secondary node (SN), the UE can use one primary SCell (PSCell, also called the primary SCG cell in NR) and one or more SCells. In NR, the primary cell of the primary or secondary cell group is sometimes also called a special cell (SpCell). Therefore, the SpCell in the MCG is the PCell, and the SpCell in the SCG is the PSCell.

[0061] UE triggers SCG failure in the following cases: SCG RLF, SCG beam failure when SCG is deactivated, SN addition / change failure, SCG configuration failure of RRC message on SRB3, SCG synchronization reconfiguration failure, SCG integrity check failure, etc. UE indicates SCG failure to the gNB by sending the RRC message SCGFailureInformation (SCG failure information).

[0062] If radio link failure is detected for the MCG link, fast MCG link recovery is configured, and the SCG is not deactivated, the UE triggers fast MCG link recovery. Otherwise, the UE initiates the RRC connection reestablishment procedure. Similarly, if MCG link failure is detected, the UE initiates the RRC connection reestablishment procedure when performing a PSCell addition or PSCell change.

[0063] During fast MCG link recovery, the UE suspends MCG transmission of all radio bearers except SRBs and BH RLC channels (if any), and reports the failure to the MN via the SCG using a MCGFailureInformation (MCG Failure Information) message using the SCG split SRB1 or SRB3. The UE includes in the MCGFailureInformation message the measurement results available according to the current measurement configuration of both the MN and the SN.

[0064] There are certain challenges currently. Currently, 3GPP specifications do not support QoE measurement configuration and reporting in dual connectivity. The current specifications only consider the case where the UE is connected to a single gNB, which both provides the QoE configuration and receives the resulting reports. One of the goals of Release 18 is to enhance support for QoE in dual connectivity scenarios. While work has begun on which node should be allowed to configure the UE for QoE measurements and which bearers should be used for both this configuration and reporting QoE, some fundamental issues arising from the use of NR-DC have not yet been addressed. Namely, radio link failures and changes in SN / SCG when moving or SN switching.

[0065] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. Various embodiments provide processes for handling QoE and RVQoE reporting and reporting continuation in the event of RLF in NR-DC. The solution involves actions to be performed by the UE for QoE / RVQoE measurements and reporting when a radio failure is detected in one of the two cell groups. UE actions may be exchanged a priori, on request / on demand (where the failure cause may also be transmitted as part of the QoE report), or based on interpretation. Special cases such as failures on two legs are also addressed.

[0066] In some embodiments, a process is provided for handling the transmission of QoE / RVQoE reports in an NR-DC scenario when a failure occurs in one of the nodes (primary or secondary node).

[0067] Various embodiments are associated with QoE report transmission processing when a radio link fails.Some embodiments associated with QoE report processing when a SN changes are described below.

[0068] In some embodiments, the SN may be activated as a secondary source to provide additional resources to improve the user experience and therefore also carry the data flows of the application session alone or in addition to the MN. In this case, the SN may also configure the UE for QoE / RVQoE measurements. However, the following applies when the MN is the primary bearer of the application session data flows and if the session is not interrupted (at least from the MN side).

[0069] In some embodiments (where the UE is sending QoE and / or RVQoE reports to the SN and an SCG failure occurs but no MCG failure is detected), the UE may log and indicate the SCG failure in a QoE report and / or RVQoE report (preferably a report covering the time period in which the SCG failure occurred), for example by sending an indication of the SCG failure that occurred in a MeasurementReportAppLayer RRC message along with the QoE report and / or the reported RVQoE metrics. In some examples, if the UE is configured with RAN-located QoE measurements (i.e., QoE measurements performed in the AS layer in the UE), this information may be logged. In additional or alternative examples, if the UE is not configured with RAN-located QoE measurements, an indication of the SCG failure may be added in the AT command. In additional or alternative examples, in addition to the SCG failure indication included in the QoE report and / or RVQoE report, the UE may also include information about the SCG failure, such as the elapsed time (duration) between the SCG failure and successful recovery. This may be indicated, for example, in the form of timestamps of failure and successful recovery, or in the form of an indication of duration (e.g., in milliseconds). In an additional or alternative example, when the UE AS receives the RVQoE report from the UE application layer, the UE AS may add the indication of SCG failure (and optionally associated information) to the RVQoE report before storing or forwarding it to the RAN, or supplement the received RVQoE reporting parameters with the SCG failure indication (and optionally associated information) before storing or forwarding the RVQoE reporting parameters and the SCG failure indication to the RAN.

[0070] In additional or alternative embodiments, if / when the UE attempts to re-establish an SCG connection, the UE may stop reporting QoE / RVQoE measurements entirely and store QoE / RVQoE reports instead. In some examples, the QoE / RVQoE reports may be discarded if the connection re-establishment fails or exceeds a certain time limit. In additional or alternative examples, when / if the UE attempts to initiate a connection re-establishment procedure to the SCG, it may instead start sending QoE and / or RVQoE reports to the MN / MCG. The decision to start sending reports to the MN may be made in one of the following ways: the UE may start sending reports to the MN on its own (i.e., without being instructed), the UE may receive such an indication from the MN, or the UE may ask the MN how to continue reporting. In an additional or alternative example, prior to detection of SCG failure, for example when performing SN addition or SN modification, the UE may have received an explicit indication (from the MN or SN) that in the event of an SCG failure, the reporting branch to be used for QoE / RVQoE reporting (i.e., the DC connection branch over which the reports are to be sent) will have to be switched, or that in the event of an SCG failure, QoE / RVQoE reporting will have to be suspended / stopped. The UE may be configured with an indication to continue QoE measurements but suspend reporting until the SCG has been restored. The UE may be configured with an indication to suspend both measurements and reporting until the SCG has been restored. For QoE and RVQoE, the indications may be separate, such that, for example, QoE measurements continue but reporting is suspended, while RVQoE measurements as well as reporting are suspended.

[0071] The innovations described herein may be applied to UE behavior when SCG fails. In additional or alternative embodiments, this may require the UE to be reconfigured with another SRB to transmit reports to the network.

[0072] In an additional or alternative embodiment, as soon as the SN detects an SCG failure, the SN may query the MN to instruct the UE to send reports to the MN from now on. In another variant, as described above, the UE may query the MN how to continue reporting. In some examples, the indication that the UE sends reports to the MN from now on may apply to QoE or RVQoE reports or both. It may also apply to each QoE / RVQoE configuration or all QoE / RVQoE configurations or only QoE or only RVQoE configurations. In an additional or alternative example, before the failure, the SN was forwarding QoE reports directly to the MCE, and if the MN is to start receiving reports, the MN may need to request from the SN the information required to forward the reports to the correct MCE, such as a mapping between the MCE IP address, URI, measConfigAppLayerId, and QoE reference (if it does not already have this information). In another variant, this information is provided from the SN as soon as an SCG failure is detected.

[0073] Upon successful SCG re-establishment, the SN or MN may send an indication to the UE (after coordination) to resume sending reports to the SN.

[0074] The above options and process extensions also apply to the case where the attempted SN change results in a SN add failure. The UE may be instructed to continue QoE / RVQoE measurements but suspend reporting, or to continue reporting to the MN or SN during the SN change phase. Upon detecting a SN add failure, the UE may ask the MN how to continue reporting, or the UE may have received instructions as described above.

[0075] Some embodiments associated with QoE reporting processing upon failure in the MN are described below. In some embodiments (where the UE is sending QoE and / or RVQoE reports to the MN, and an MCG failure occurs, but no SCG failure is detected), the UE may record and indicate the MCG failure in a QoE report and / or RVQoE report (preferably a report covering the time period in which the MCG failure occurred), for example by sending an indication of the MCG failure that occurred in a MeasurementReportAppLayer RRC message together with the QoE report and / or the reported RVQoE metrics.

[0076] In some examples, if the UE is configured with RAN-located QoE measurements, this information may be logged. In an additional or alternative example, if the UE is not configured with RAN-located QoE measurements, an indication of MCG failure may be added to the AT command. In an additional or alternative example, in addition to the MCG failure indication included in the QoE report and / or RVQoE report, the UE may also include information about the MCG failure (e.g., the elapsed time (duration) between the MCG failure and successful recovery). This may be indicated, for example, in the form of timestamps of the failure and successful recovery or in the form of an indication of the duration (e.g., in milliseconds). In an additional or alternative example, for RVQoE reporting, when the UE AS receives the RVQoE report from the UE application layer, the UE AS may add the indication of MCG failure (and optionally, associated information) to the RVQoE report before storing it or forwarding it to the RAN, or supplement the received RVQoE reporting parameters with the MCG failure indication (and optionally, associated information) before storing the RVQoE reporting parameters and the MCG failure indication or forwarding them to the RAN.

[0077] In additional or alternative embodiments, the UE may stop reporting QoE / RVQoE measurements and store QoE / RVQoE reports if / when the UE attempts to re-establish an MCG connection.

[0078] In additional or alternative embodiments, the report may be discarded if the reconnection establishment fails or if a certain time limit is exceeded (eg, a certain timer expires).

[0079] In additional or alternative embodiments, the UE may be pre-configured with an indication related to behavior in the event of MCG failure. In some examples, the indication may, for example, indicate a QoE and / or RVQoE report.

[0080] In an additional or alternative embodiment, the UE may receive an indication from the SN to start sending reports to the SCG while it (ie, the UE) simultaneously initiates an RRC connection reestablishment procedure to the MCG.

[0081] The innovations described herein may be applied to UE behavior upon MCG failure.In additional or alternative embodiments, upon successful re-establishment procedure, the UE may resume sending QoE and / or RVQoE reports to the MCG if the UE receives any such indication from the MN.

[0082] The above options and process extensions may also apply to situations where an attempted MN change results in a failure scenario that triggers fast MCG link recovery.

[0083] Some embodiments associated with QoE reporting processing upon failure in both the MN and SN are described below. In some embodiments where both the MCG and SCG fail, the UE may store the reports until connectivity with either node is reestablished. The recovery node may notify the UE that it should send the stored reports / resume sending reports to the recovery node. There may be different conditions for storing QoE and RVQoE reports as these reports are used for different purposes. The network may configure what actions the UE takes, or the actions may be determined by the UE (based on UE implementation). The actions may, for example, be to continue measuring and storing reports until one or both nodes are recovered, or, for example, to continue QoE measurements but not RVQoE measurements until one or both nodes are recovered.

[0084] Some embodiments associated with QoE reporting processing in the case of fast MCG link recovery are described below. In some embodiments, fast MCG link recovery is an RRC procedure applicable to UEs in MR-DC, wherein upon detecting a radio link failure on the MCG, the UE sends an MCG Failure Information message to the MN via the SCG.

[0085] In some embodiments (where the UE is sending QoE and / or RVQoE reports to the MN, an MCG failure occurs, the SCG link is not suspended, and fast MCG link recovery is attempted), the UE may record and indicate the MCG failure in a QoE report and / or RVQoE report (preferably a report covering the time period in which the MCG failure occurred), for example by sending an indication of the MCG failure that occurred in a MeasurementReportAppLayer RRC message together with the QoE report and / or the reported RVQoE metrics.

[0086] In some examples, if the UE is configured with RAN-located QoE measurements, this information may be logged.

[0087] In an additional or alternative example, if the UE is not configured with RAN-located QoE measurements, an indication of MCG failure may be added in the AT command.

[0088] In an additional or alternative example, in addition to the MCG failure indication included in the QoE report and / or RVQoE report, the UE may also include information about the MCG failure, such as the elapsed time (duration) between the MCG failure and successful recovery. This may be indicated, for example, in the form of timestamps of the failure and successful recovery or in the form of an indication of the duration (e.g., in milliseconds).

[0089] In an additional or alternative example, for RVQoE reporting, when the UE AS receives the RVQoE report from the UE application layer, the UE AS may add the indication of MCG failure (and optionally associated information) to the RVQoE report before storing or forwarding it to the RAN, or supplement the received RVQoE reporting parameters with the MCG failure indication (and optionally associated information) before storing or forwarding the RVQoE reporting parameters and the MCG failure indication to the RAN.

[0090] In additional or alternative embodiments, while attempting fast MCG link recovery, the UE may stop reporting QoE / RVQoE measurements and store the QoE / RVQoE reports.

[0091] In additional or alternative embodiments, the report may be discarded if the reconnection establishment fails or if a certain time limit is exceeded (eg, a certain timer expires).

[0092] In an additional or alternative embodiment, the UE may receive an indication from the SN to start sending reports to the SCG while it (ie, the UE) simultaneously initiates an RRC connection reestablishment procedure to the MCG.

[0093] In additional or alternative embodiments, upon successful MCG re-establishment procedure, the UE may resume sending QoE and / or RVQoE reports to the MCG if the UE receives any such indication from the MN.

[0094] When the UE triggers the MCG failure message to be sent to the MN via the SN, it starts a timer T316 during which the UE waits for instructions from the MN. In the case of successful recovery from an MCG failure, the value of the time elapsed since the start of T316 can be added to the QoE / RVQoE report. This will let the recipient of the report know that an MCG failure has occurred (potentially affecting the user's QoE) and how long it will take to recover from such a failure.

[0095] Similar to the above case, if the UE is sending QoE and / or RVQoE reports to the SN when an MCG failure occurs, a fast MCG link recovery is attempted and the same steps as above may be performed. In a variation of this case, while attempting to recover the MCG link via fast MCG link recovery, the SN may send an indication to the UE to suspend QoE / RVQoE reporting until / if the MCG link is recovered. During the MCG recovery process, the SN may notify the MN in an XnAP message (e.g., in an XnAP RRC TRANSFER message as part of or in conjunction with fast MCG recovery, from the SN to the MN IE via SRB3 containing an RRC container with the MCGFailureInformation IE provided therein) that the UE's QoE / RVQoE reporting has been suspended / stopped.

[0096] Upon successful completion of MCG failure recovery, the MN may send an indication to the UE via the MN that QoE / RVQoE reporting is resumed / (re)started. This indication may be carried in an XnAP RRC TRANSFER message from the MN to the SNIE (sent from the MN to the SN) via SRB3, for example, together with or as part of fast MCG recovery.

[0097] Some embodiments associated with a reconfiguration failure on a secondary node SRB are described below. In some embodiments, the UE will determine whether it can comply with an RRC message from the SN carrying a QoE measurement related configuration. If the UE cannot comply with such a message, the UE will trigger a failure when attempting to apply the message. The failure may be an SCG failure event.

[0098] In additional or alternative embodiments, the SCG failure event may be indicated in a message sent to another node (eg, a MN) other than the SN itself, for example, in a SCGFailureInformation message.

[0099] In an additional or alternative embodiment, the failure message may carry an indication indicating that the reason for the failure is that the UE has attempted to apply a reconfiguration message carrying a QoE measurement related configuration. Although some embodiments herein describe the presence of a message carrying a QoE measurement related configuration, it should be understood that other indications / configurations may be carried in the same message (e.g., not directly related to the QoE measurement configuration).

[0100] In an additional or alternative embodiment, another approach is for the UE to indicate on which bearer the message was received. For example, considering sending a configuration message on SRB3, the UE can indicate that the UE has been unable to comply with the RRC message received on SRB3. Note: When it is described herein that there is a bearer for carrying messages including QoE measurement related configurations, it should be understood that the bearer can also be used to carry other indications / configurations (i.e., not directly related to the QoE measurement configuration). Therefore, if the failure indication message only indicates that it was an SRB3 message that caused the failure, it may not be known (from the failure message itself) what configuration was carried in the message.

[0101] As mentioned before, the QoE and RVQoE reporting behavior of the UE in case of MCG and / or SCG failure can be standardized or (pre-)configured. If configuration is introduced, there are several degrees of freedom to explore, some of which are detailed below.

[0102] In general, the UE may be configured to perform any of the following non-limiting list of actions upon MCG and / or SCG failure, where these actions may be configured differently depending on the type of failure (e.g., MCG failure or SCG failure). Note that not all actions may be configured for all types of failures, and also note that more than one action may be configured and performed.

[0103] In some examples, the UE may be configured to send a report to a node where a failure has not occurred (eg, to send a report within the node's serving cell group (ie, MCG or SCG)).

[0104] In an additional or alternative example, the UE may be configured to store the reports in the UE until a successful recovery has been performed after a failure, and then send the stored reports. This may advantageously be combined with configuration of where to send the QoE and / or RVQoE reports.

[0105] In an additional or alternative example, the UE may be configured to max-store The timer is started at T and the pending reports and the newly generated reports are stored in the UE. max-storeWhen due, send the stored report. (This can be advantageously combined with configuration of where to send the QoE and / or RVQoE reports.)

[0106] In an additional or alternative example, the UE may be configured to keep reporting to another node even after successful failure recovery if reporting is redirected to that node.

[0107] In an additional or alternative example, the UE may be configured to return to reporting to the original node upon successful failure recovery if reporting was redirected to another node.

[0108] In an additional or alternative example, the UE may be configured to max-store The timer is started at UE 1 and the pending reports and the newly generated reports are stored in the UE. When failure recovery is successful, the stored reports are sent (and T is stopped). max-store timer). At T max-store Upon expiration, the stored reports are discarded. (This can be advantageously combined with configuration of where to send QoE and / or RVQoE reports.)

[0109] In an additional or alternative example, the UE may be configured to discard all but the most recently generated RVQoE report if a pending RVQoE report is stored (eg, according to one of the configuration options in the list) and more than one periodic RVQoE report is stored for the same application session.

[0110] In an additional or alternative example, the UE may be configured to, if pending RVQoE reports are stored (e.g., according to one of the configuration options in the list), then to clear the UE when any stored RVQoE reports have been stored for more than T max-store-individual-RVQoE-report (which is a timer that can be started for each newly generated and stored RVQoE report), any stored RVQoE report is discarded.

[0111] In an additional or alternative example, the UE may be configured to, if a pending RVQoE report is stored (eg, according to one of the configuration options in the list), discard the stored periodic RVQoE report when generating a subsequent periodic RVQoE report for the same application session.

[0112] In an additional or alternative example, the UE may be configured to encapsulate the MeasurementReportAppLayer RRC message in a ULInformationTransferMRDC RRC message if the report is redirected to another node. If this is configured for only one report type, i.e. only one of the QoE report and the RVQoE report, the encapsulated MeasurementReportAppLayer RRC message shall only contain report information relevant to the relevant report type.

[0113] In an additional or alternative example, the UE may be configured to encapsulate the MeasurementReportAppLayer RRC message in a ULInformationTransferMRDC RRC message if the report is redirected from the SN (e.g. in the SCG) to the MN (e.g. in the MCG). If this is configured for only one report type, i.e. only one of the QoE report and the RVQoE report, the encapsulated MeasurementReportAppLayer RRC message shall contain only the report information relevant to the relevant report type.

[0114] Each of the above may be configured separately for QoE reports and RVQoE reports, for example so that different actions are performed for the respective report types or generally for both report types (and note that this includes different timer values ​​(e.g., T may be configured for pending QoE reports and pending RVQoE reports). max-store different values ​​of )).

[0115] Different configurations can be associated with different failure types (e.g., MCG failure (general), SCG failure (general), RLF (in MCG or SCG), beam failure (in MCG or SCG), random access failure (in MCG or SCG), persistent LBT failure (in MCG or SCG), RLF in MCG, RLF in SCG, beam failure in MCG, beam failure in SCG, random access failure in MCG, random access failure in SCG, persistent LBT failure in MCG, and persistent LBT failure in SCG).

[0116] In addition, the configuration of the UE's reporting behavior upon failure when in MR-DC mode can have different scopes, such as applying to all configured QoE measurements and / or RVQoE measurements in the UE, applying to all configured QoE measurements and / or RVQoE measurements in the UE related to a certain service type or certain service types, or applying to only one QoE configuration and / or RVQoE configuration.

[0117] Configuration of the UE's QoE / RVQoE reporting behavior upon failure when in MR-DC mode may advantageously be included in the AppLayerMeasConfig-r17 IE in the RRCReconfigurationRRC message, either inside or outside the MeasConfigAppLayer-r17 IE.

[0118] Fig.13 An example showing how configuration options can be implemented in ASN.1 code in future releases of 3GPP. This example does not cover all of the above configuration options, but selects a few to show how they can be captured in ASN.1 code. It is based on the ASN.1 code of AppLayerMeasConfig-r17 IE in 3GPP. Additions are bolded and underlined.

[0119] Another QoE related feature that needs to be configured for the behavior of the UE in MR-DC mode in conjunction with failures is the sending of session start indications and session stop indications. Like QoE reports and RVQoE reports, session start indications and session stop indications are sent from the UE to the RAN in the MeasurementReportAppLayer RRC message. Therefore, configuration options similar to those described above for QoE reports and / or RVQoE reports may also be used for the UE to send session start indications and session stop indications.

[0120] Fig.14 An example of operations performed by a communication device in a communication network including a first network node and a second network node providing dual connectivity to the communication device is shown.

[0121] At block 1410, operations include determining that a failure has occurred during sending a report to the first network node. In some embodiments, the report includes at least one of: a Quality of Experience (QoE) report; and a Radio Access Network Visible QoE (RVQoE) report.

[0122] In an additional or alternative embodiment, the first network node is a master node MN, the failure is a master cell group MCG failure, and the second network node is a secondary node SN.

[0123] In an additional or alternative embodiment, the first network node is a secondary node SN, the failure is a secondary cell group SCG failure, and the second network node is a master node MN.

[0124] At block 1415, operations include suspending sending the report to the first network node. In some examples, suspending sending the report to the first network node includes stopping, delaying, or deferring sending the report to the first network node.

[0125] At block 1420, operations include performing an action associated with the report. In some embodiments, performing the action includes sending the report to a second network node. In some examples, sending the report to the second network node includes receiving a message from the second network node, the message including a request for the report; and in response to receiving the message, sending the report to the second network node. In additional or alternative examples, the message is a second message. Sending the report to the second network node also includes sending a first message to the second network node, the first message requesting instructions on how to process the report.

[0126] In additional or alternative embodiments, performing the action includes starting a timer after determining that a failure has occurred.

[0127] In additional or alternative embodiments, performing the action includes storing the report and / or the indication of failure in a local memory. In some examples, performing the action also includes deleting the report and / or the indication of failure from the local memory in response to expiration of a timer. In additional or alternative examples,

[0128] Storing the report and / or the indication of the failure in the local memory includes: determining that a communication failure has occurred with the second network node; and storing the report and / or the indication of the failure in the local memory in response to determining that a communication failure has occurred with the second network node.

[0129] In additional or alternative embodiments, performing the action further comprises reconfiguring the communication device with another signaling radio bearer.

[0130] In additional or alternative embodiments, performing the actions further comprises sending a report to the first network node in response to reestablishing contact with the first network node.

[0131] From Fig.14 Various operations of the flow diagrams may be optional for some embodiments of the communication devices and related methods.

[0132] Fig.15 An example of operations performed by a first network node in a communication network including a second network node is shown.The first network node and the second network node may provide dual connectivity to a communication device.

[0133] At block 1510, operations include determining that a failure has occurred during transmission of a report from the communication device to the second network node. In some embodiments, the report includes at least one of: a Quality of Experience (QoE) report; and a Radio Access Network Visible QoE (RVQoE) report.

[0134] In an additional or alternative embodiment, the first network node is a master node MN, the failure is a secondary cell group SCG failure, and the second network node is a secondary node SN.

[0135] In an additional or alternative embodiment, the first network node is a secondary node SN, the failure is a master cell group MCG failure, and the second network node is a master node MN.

[0136] At block 1520, operations include communicating with the communication device. In some embodiments, the first network node communicates with the communication device in response to determining that a failure has occurred.

[0137] In an additional or alternative embodiment, communicating with the communication device comprises sending a message to the communication device requesting the communication device to send a report to the first network node.

[0138] In additional or alternative embodiments, communicating with the communication device includes receiving a message including the report from the communication device.

[0139] From Fig.15 Various operations of the flowcharts may be optional for some embodiments of the RAN node and related methods.

[0140] Fig.16 An example of a communication system 1600 is shown in accordance with some embodiments.

[0141] In the text, the terms "or" and "and / or" are sometimes used interchangeably.

[0142] In this example, the communication system 1600 includes a telecommunications network 1602, which includes an access network 1604 such as a radio access network (RAN) and a core network 1606, which includes one or more core network nodes 1608. The access network 1604 includes one or more access network nodes, such as network nodes 1610a and 1610b (one or more of which may be generally referred to as network nodes 1610), or any other similar third generation partnership project (3GPP) access nodes or non-3GPP access points. The network node 1610 facilitates direct or indirect connection of user equipment (UE), such as connecting UE 1612a, UE 1612b, UE 1612c, and UE 1612d (one or more of which may be generally referred to as UE 1612) to the core network 1606 through one or more wireless connections.

[0143] Example wireless communications via wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without using wiring, cables, or other material conductors. In addition, in different embodiments, the communication system 1600 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (whether via a wired connection or via a wireless connection). The communication system 1600 may include any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system, and / or be connected to any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system interface.

[0144] UE 1612 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to wirelessly communicate with network node 1610 and other communication devices. Similarly, network node 1610 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 1612 and / or with other network nodes or devices in telecommunication network 1602 to enable and / or provide network access (e.g., wireless network access) and / or to perform other functions (e.g., management) in telecommunication network 1602.

[0145] In the depicted example, the core network 1606 connects the network node 1610 to one or more hosts (such as the host 1616). These connections may be direct, or may be indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 1606 includes one or more core network nodes (e.g., core network node 1608) composed of hardware and software components. The features of these components may be substantially similar to those described for the UE, network node, and / or host, so that their description is generally applicable to the corresponding components of the core network node 1608. The example core network node includes one or more functions of: a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network exposure function (NEF), and / or a user plane function (UPF).

[0146] The host 1616 may be owned or under the control of a service provider other than the operator or provider of the access network 1604 and / or the telecommunications network 1602, and may be operated by or on behalf of the service provider. The host 1616 may host a variety of applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data about various environmental conditions detected by multiple UEs), analysis functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0147] As a whole, Fig.16 The communication system 1600 enables connections between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other appropriate wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards (e.g., LoRa and Sigfox).

[0148] In some examples, the telecommunication network 1602 is a cellular network implementing 3GPP standardized features. Therefore, the telecommunication network 1602 can support network slicing to provide different logical networks to different devices connected to the telecommunication network 1602. For example, the telecommunication network 1602 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, while providing enhanced mobile broadband (eMBB) services to other UEs, and / or providing massive machine type communication (mMTC) / massive IoT services to additional UEs.

[0149] In some examples, UE 1612 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network 1604 according to a predetermined schedule, when triggered by an internal or external event, or in response to a request from access network 1604. In addition, the UE may be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE may operate with any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0150] In an example, the hub 1614 communicates with the access network 1604 to facilitate indirect communication between one or more UEs (e.g., UE 1612c and / or UE 1612d) and a network node (e.g., network node 1610b). In some examples, the hub 1614 may be a controller, a router, a content source and an analyzer, or any other communication device described herein with respect to the UE. For example, the hub 1614 may be a broadband router that enables the UE to access the core network 1606. As another example, the hub 1614 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 1610, or received through executable code, scripts, processes, or other instructions in the hub 1614. As another example, the hub 1614 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, analysis or other processing of the data may be performed. As another example, the hub 1614 may be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 1614 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and then the hub 1614 provides it to the UE directly, after performing local processing, and / or after adding additional local content. In another example, the hub 1614 acts as a proxy server or coordinator for the UE, especially when one or more of the UEs are low-energy IoT devices.

[0151] The hub 1614 may have a continuous / persistent or intermittent connection to the network node 1610b. The hub 1614 may also allow different communication schemes and / or scheduling between the hub 1614 and the UE (e.g., UE 1612c and / or UE 1612d) and between the hub 1614 and the core network 1606. In other examples, the hub 1614 is connected to the core network 1606 and / or one or more UEs via a wired connection. In addition, the hub 1614 may be configured to be connected to an M2M service provider via an access network 1604, and / or to another UE via a direct connection. In some scenarios, the UE may establish a wireless connection with the network node 1610 while still being connected via a wired or wireless connection through the hub 1614. In some embodiments, the hub 1614 may be a dedicated hub, that is, a hub whose main function is to route communications from the network node 1610b to the UE / route communications from the UE to the network node 1610b. In other embodiments, hub 1614 may be a non-dedicated hub - ie, a device operable to route communications between UEs and network node 1610b, but which is additionally capable of operating as a communications origin and / or endpoint for certain data channels.

[0152] Fig.17 A UE 1700 according to some embodiments is shown. As used herein, a UE refers to a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client equipment (CPEs), vehicle mounted or vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine type communication (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0153] The UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a "user" in the sense of a human user who owns and / or operates the associated device. Alternatively, a UE may represent a device that is intended to be sold to or operated by a human user but may not or may not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart meter).

[0154] UE 1700 includes a processing circuit 1702, which is operably coupled to an input / output interface 1706, a power supply 1708, a memory 1710, a communication interface 1712, and / or any other components or any combination thereof via a bus 1704. Some UEs may utilize Fig.17 All or a subset of the components shown. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0155] The processing circuit 1702 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 1710 as a machine-readable computer program. The processing circuit 1702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic and suitable firmware; one or more stored computer programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination of the above. For example, the processing circuit 1702 may include multiple central processing units (CPUs).

[0156] In an example, the input / output interface 1706 may be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1700. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, scroll wheels, smart cards, etc. A presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use an interface port of the same type as an input device. For example, a universal serial bus (USB) port may be used to provide input devices and output devices.

[0157] In some embodiments, the power supply 1708 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery unit. The power supply 1708 may also include a power supply circuit for delivering power from the power supply 1708 itself and / or an external power supply to various parts of the UE 1700 via an input circuit or an interface such as a power cable. The delivered power may be used, for example, for charging the power supply 1708. The power supply circuit may perform any formatting, conversion, or other modification on the power from the power supply 1708 to make the power suitable for various components of the UE 1700 being powered.

[0158] The memory 1710 may be or be configured to include a memory, such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable tape, a flash drive, etc. In one example, the memory 1710 includes one or more application programs 1714 (e.g., an operating system, a web browser application, a widget, a gadget engine, or other application) and corresponding data 1716. The memory 1710 may store any one or a combination of various operating systems for use by the UE 1700.

[0159] The memory 1710 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, a built-in hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identity modules (SIMs), such as USIM and / or ISIM), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". The memory 1710 may allow the UE 1700 to access instructions, applications, etc. stored on a temporary or non-temporary memory medium to offload data or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in memory 1710, which may be or include a device-readable storage medium.

[0160] The processing circuit 1702 may be configured to communicate with an access network or other network using a communication interface 1712. The communication interface 1712 may include one or more communication subsystems and may include an antenna 1722 or be communicatively coupled to the antenna 1722. The communication interface 1712 may include one or more transceivers for communication (such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network)). Each transceiver may include a transmitter 1718 and / or a receiver 1720 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 1718 and the receiver 1720 may be coupled to one or more antennas (e.g., antenna 1722) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0161] In the illustrated embodiment, the communication functionality of the communication interface 1712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near field communication, location-based communication (such as use of a global positioning system (GPS) for determining location), another similar communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, code division multiple access (CDMA), wideband code division multiple access (WCDMA), GSM, LTE, new radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / Internet protocol (TCP / IP), synchronous optical network (SONET), asynchronous transfer mode (ATM), QUIC, hypertext transfer protocol (HTTP), etc.

[0162] Regardless of the type of sensor, the UE may provide an output of data captured by its sensor through its communication interface 1712 via a wireless connection to a network node. The data captured by the UE's sensor may be transmitted via another UE via a wireless connection to a network node. The output may be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the load of reports from several sensors), in response to a trigger event (e.g., sending an alarm when humidity is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0163] As another example, the UE includes an actuator, motor, or switch associated with a communication interface that is configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0164] When the UE is in the form of an Internet of Things (IoT) device, the UE may be a device used in one or more application areas including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are embedded in: a connected refrigerator or freezer, a TV, connected lighting, an electric meter, a robotic vacuum cleaner, a voice-activated smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electronic door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality (AR) or virtual reality (VR), a wearable device for tactile enhancement or sensory enhancement, a sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any kind of medical device (such as a heart rate monitor or a teleoperated surgical robot). In addition to the above, Fig.17 In addition to the other components depicted in the illustrated UE 1700 , a UE in the form of an IoT device may include circuitry and / or software depending on the intended application of the IoT device.

[0165] As another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle (e.g., a car, bus, truck, ship, and airplane) or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation.

[0166] In fact, for a single use case, any number of UEs may be used together. For example, a first UE may be a drone or integrated in a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller operating the drone. When the user makes changes via the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first UE and / or the second UE may also include more than one of the above functions. For example, a UE may include a sensor and an actuator and handle data communications for both the speed sensor and the actuator.

[0167] Fig.18 A network node 1800 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, NodeBs, evolved NodeBs (eNBs), and NR NodeBs (gNBs)).

[0168] Base stations may be classified based on the amount of coverage they provide (or in other words, based on their transmit power level), and therefore, depending on the amount of coverage provided, they may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay host node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0169] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio (MSR) device (e.g., an MSR BS), a network controller (e.g., a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC)), and / or a minimization of drive tests (MDT).

[0170] The network node 1800 includes a processing circuit 1802, a memory 1804, a communication interface 1806, and a power supply 1808. The network node 1800 may be composed of a plurality of physically separated components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding component. In certain scenarios where the network node 1800 includes a plurality of separated components (e.g., a BTS and a BSC component), one or more of these separated components may be shared between several network nodes. For example, a single RNC may control a plurality of NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered as a single separate network node in some cases. In some embodiments, the network node 1800 may be configured to support a plurality of radio access technologies (RATs). In such an embodiment, some components may be duplicated (e.g., separate memories 1804 for different RATs), and some components may be reused (e.g., the same antenna 1810 may be shared by different RATs). The network node 1800 may also include multiple sets of the various components shown for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies) integrated into the network node 1800. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1800.

[0171] The processing circuit 1802 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic, which is operable to provide network node 1800 functionality alone or in combination with other network node 1800 components (e.g., memory 1804).

[0172] In some embodiments, processing circuit 1802 includes a system on chip (SOC). In some embodiments, processing circuit 1802 may include one or more of radio frequency (RF) transceiver circuit 1812 and baseband processing circuit 1814. In some embodiments, radio frequency (RF) transceiver circuit 1812 and baseband processing circuit 1814 may be located on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, part or all of RF transceiver circuit 1812 and baseband processing circuit 1814 may be on the same chip or chipset, board, or unit.

[0173] The memory 1804 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data and / or instructions that can be used by the processing circuit 1802. The memory 1804 may store any suitable instructions, data or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, and / or other instructions that can be executed by the processing circuit 1802 and used by the network node 1800. The memory 1804 may be used to store any calculations made by the processing circuit 1802 and / or any data received via the communication interface 1806. In some embodiments, the processing circuit 1802 and the memory 1804 are integrated.

[0174] The communication interface 1806 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 1806 includes a port / terminal 1816 for sending data to and receiving data from the network, for example, via a wired connection. The communication interface 1806 also includes a radio front-end circuit 1818, which can be coupled to an antenna 1810, or in some embodiments is a part of the antenna 1810. The radio front-end circuit 1818 includes a filter 1820 and an amplifier 1822. The radio front-end circuit 1818 can be connected to the antenna 1810 and the processing circuit 1802. The radio front-end circuit can be configured to adjust the signal communicated between the antenna 1810 and the processing circuit 1802. The radio front-end circuit 1818 can receive digital data, which will be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1818 can use a combination of a filter 1820 and / or an amplifier 1822 to convert the digital data into a radio signal having suitable channel and bandwidth parameters. The radio signal can then be sent via the antenna 1810. Similarly, when receiving data, antenna 1810 may collect radio signals, which may then be converted to digital data by radio front end circuitry 1818. The digital data may be passed to processing circuitry 1802. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0175] In some alternative embodiments, the network node 1800 does not include a separate radio front end circuit 1818, instead the processing circuit 1802 includes the radio front end circuit and is connected to the antenna 1810. Similarly, in some embodiments, all or some of the RF transceiver circuit 1812 is part of the communication interface 1806. In other embodiments, the communication interface 1806 may include one or more ports or terminals 1816, the radio front end circuit 1818 and the RF transceiver circuit 1812 as part of a radio unit (not shown), and the communication interface 1806 communicates with the baseband processing circuit 1814 as part of a digital unit (not shown).

[0176] Antenna 1810 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1810 may be coupled to radio front end circuit 1818 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1810 is separate from network node 1800 and may be connected to network node 1800 via an interface or port.

[0177] Antenna 1810, communication interface 1806 and / or processing circuit 1802 may be configured to perform any receiving operation and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, antenna 1810, communication interface 1806 and / or processing circuit 1802 may be configured to perform any sending operation performed by a network node described herein. Any information, data and / or signal may be sent to a UE, another network node and / or any other network device.

[0178] The power supply 1808 provides power to the various components of the network node 1800 in a form suitable for each component (e.g., at the voltage and current levels required by each corresponding component). The power supply 1808 may also include power management circuitry or be coupled to a power management circuitry to provide power to the components of the network node 1800 to perform the functions described herein. For example, the network node 1800 may be connected to an external power source (e.g., a power grid, a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source supplies power to the power circuit of the power supply 1808. As another example, the power supply 1808 may include a power source in the form of a battery or a battery pack, which is connected to or integrated in the power circuit. If the external power source fails, the battery may provide backup power.

[0179] Embodiments of network node 1800 may include beyond Fig.18, which are used to provide certain aspects of the functionality of the network node (including any of the functions described herein and / or any functions required to support the subject matter described herein). For example, the network node 1800 may include a user interface device to allow information to be input into the network node 1800 and to allow information to be output from the network node 1800. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node 1800.

[0180] Fig.19 is a block diagram of a host 1900 according to various aspects described herein, which host 1900 may be Fig.16 1616 of the embodiment of the host. As used herein, the host 1900 can be or include various combinations of hardware and / or software, including processing resources in a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a server farm. The host 1900 can provide one or more services to one or more UEs.

[0181] Host 1900 includes processing circuitry 1902, which is operably coupled to input / output interface 1906, network interface 1908, power supply 1910, and memory 1912 via bus 1904. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to the previous figures (e.g., Fig.17 and Fig.18 ) so that its description is generally applicable to corresponding components of host 1900.

[0182] The memory 1912 may include one or more computer programs including data 1916 and one or more host applications 1914, which may include user data, such as data generated by a UE for the host 1900, or data generated by the host 1900 for the UE. An embodiment of the host 1900 may utilize only a subset or all of the components shown. The host application 1914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., generic video coding (VVC), high efficiency video coding (HEVC), advanced video coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, advanced audio coding (AAC), MPEG, G.711), including code conversion for multiple different categories, types or implementations of UE (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application 1914 may also provide user authentication and permission checks, and may periodically report health status, routing, and content availability to a central node (e.g., a device in a core network or a device on the edge of a core network). Thus, the host 1900 can select and / or indicate to the UE a different host for an over-the-top (OTT) service. The host application 1914 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0183] Fig. 20 2000 is a block diagram showing a virtualized environment 2000 in which functions implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which can include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization can be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of a function is implemented as one or more virtual components. Some or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 2000, and one or more virtual environments 2000 are hosted by one or more hardware nodes (such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). In addition, in embodiments where a virtual node does not require a radio connection (e.g., a core network node or host), the node can be fully virtualized at this time.

[0184] Application 2002 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment Q400 to implement some features, functions and / or benefits of some embodiments disclosed herein.

[0185] Hardware 2004 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein (e.g., network interfaces, input / output interfaces, etc.). Software may be executed by the processing circuitry to instantiate one or more virtualization layers 2006 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2008a and VMs 2008b (one or more of which may be generally referred to as VMs 2008), and / or perform any functions, features, and / or benefits described in connection with some embodiments described herein. Virtualization layer 2006 may present a virtual operating platform that appears to be networked hardware to WM 2008.

[0186] The VM 2008 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 2006. Different embodiments of instances of virtual devices 2002 can be implemented on one or more of the VMs 2008, and the implementation can be made in different ways. In some contexts, the virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to unify numerous network device types onto industry standard high-capacity server hardware, physical switches, and physical storage that can be located in data centers and customer premises equipment.

[0187] In the context of NFV, VM 2008 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each VM 2008 and the portion of hardware 2004 that executes the VM (which can be hardware dedicated to the VM and / or hardware shared by the VM and other VMs in the VM) form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 2008 on hardware 2004 and correspond to applications 2002.

[0188] Hardware 2004 may be implemented in a standalone network node with general or specific components. Hardware 2004 may implement some functions via virtualization. Alternatively, hardware 2004 may be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed by management and coordination 2010, which oversees the lifecycle management of application 2002, etc. In some embodiments, hardware 2004 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio unit may communicate directly with other hardware nodes via one or more suitable network interfaces, and may be used in conjunction with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station. In some embodiments, a control system 2012 may be used to provide some signaling, which may be used alternatively for communication between hardware nodes and radio units.

[0189] Fig.21 A communication diagram is shown in which a host 2102 communicates with a UE 2106 via a network node 2104 over a partially wireless connection according to some embodiments. Fig.21 Describe the UE discussed in the previous paragraphs (e.g., Fig.16 UE 1612a and / or Fig.17 UE 1700), network node (e.g., Fig.16 The network node 1610a and / or Fig.18 network nodes 1800) and hosts (e.g., Fig.16 Host 1616 and / or Fig.19 An example implementation of a host 1900 according to various embodiments.

[0190] Similar to the host 1900, an embodiment of the host 2102 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 2102 also includes software that is stored in the host 2102 or can be accessed by the host 3002 and can be executed by the processing circuit. The software includes a host application that is operable to provide services to a remote user (e.g., UE 2106), which is connected via an over-the-top (OTT) connection 2150 extending between the UE 2106 and the host 2102. When providing services to the remote user, the host application can provide user data sent using the OTT connection 2150.

[0191] The network node 2104 includes hardware that enables it to communicate with the host 2102 and the UE 2106. The connection 2160 can be direct or can go through a core network (such as Fig.16The core network 1606 of the present invention) and / or one or more other intermediate networks (eg, one or more public, private, or managed networks). For example, the intermediate network may be a backbone network or the Internet.

[0192] UE 2106 includes hardware and software, which is stored in or accessible by UE 2106 and can be executed by the processing circuit of UE. The software includes a client application (e.g., a web browser or an operator-specific "application"), which is operable to provide services to human or non-human users via UE 2106 with the support of host 2102. In the host 2102, the executed host application can communicate with the executed client application via the OTT connection 2150 terminated at UE 2106 and host 2102. When providing services to the user, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. The OTT connection 2150 can transmit both request data and user data. The client application of the UE can interact with the user to generate user data provided to the host application via the OTT connection 2150.

[0193] The OTT connection 2150 may extend via a connection 2160 between the host 2102 and the network node 2104 and via a wireless connection 2170 between the network node 2104 and the UE 2106 to provide connectivity between the host 2102 and the UE 2106. The connection 2160 and the wireless connection 2170 through which the OTT connection 2150 may be provided have been abstractly drawn to illustrate communications between the host 2102 and the UE 2106 via the network node 2104, without explicitly mentioning any intermediate devices and the precise routing of messages via these devices.

[0194] As an example of sending data via the OTT connection 2150, in step 2108, the host 2102 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user who interacts with the UE 2106. In other embodiments, the user data is associated with the UE 2106, which shares data with the host 2102 without explicit human interaction. In step 2110, the host 2102 initiates a transmission carrying the user data to the UE 2106. The host 2102 may initiate the transmission in response to a request sent by the UE 2106. The request may be caused by human interaction with the UE 2106 or by the operation of a client application executed on the UE 2106. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be via the network node 2104. Therefore, in step 2112, according to the teachings of the embodiments described throughout the present disclosure, the network node 2104 sends the user data carried in the transmission initiated by the host 2102 to the UE 2106. In step 2114 , UE 2106 receives user data carried in the transmission, which may be performed by a client application executing on UE 2106 that is associated with a host application executed by host 2102 .

[0195] In some examples, UE 2106 executes a client application that provides user data to host 2102. User data may be provided as a reaction or response to data received from host 2102. Therefore, in step 2116, UE 2106 may provide user data, which may be performed by executing the client application. When providing user data, the client application may also take into account user input received from a user via an input / output interface of UE 2106. Regardless of the specific manner in which user data is provided, in step 2118, UE 2106 initiates transmission of user data to host 2102 via network node 2104. In step 2120, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 2104 receives user data from UE 2106 and initiates transmission of the received user data to host 2102. In step 2122, host 2102 receives user data carried in the transmission initiated by UE 2106.

[0196] One or more of the various embodiments improve the performance of OTT services provided to UE 2106 using OTT connection 2150, where wireless connection 2170 forms the last leg in OTT connection 2150. More specifically, the teachings of these embodiments can improve data rate and / or latency, thereby providing benefits such as reduced user waiting, better responsiveness, and improved user experience.

[0197] In an example scenario, the host 2102 may collect and analyze plant status information. As another example, the host 2102 may process audio and video data that may have been retrieved from the UE for creating a map. As another example, the host 2102 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic lights). As another example, the host 2102 may store surveillance videos uploaded by the UE. As another example, the host 2102 may store or control access to media content such as video, audio, VR, or AR, which the host 2102 may broadcast, multicast, or unicast the media content to the UE. As other examples, the host 2102 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, positioning services, demonstration services (such as compiling charts based on data collected from remote devices, etc.), or any other function of collecting, retrieving, storing, analyzing, and / or sending data.

[0198] In some examples, a measurement process may be provided for the purpose of monitoring the data rate, latency, and other factors improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 2150 between the host 2102 and the UE 2106 in response to changes in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection may be implemented in the software and hardware of the host 2102 and / or the UE 2106. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 2150 passes; the sensors may participate in the measurement process by providing the values ​​of the monitored quantities exemplified above, or providing the values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 2150 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 2104. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling that facilitates the host 2102 to measure throughput, propagation time, latency, etc. This measurement may be accomplished by software enabling the use of the OTT connection 2150 to send a message (specifically, an empty or "fake" message) while monitoring propagation times, errors, etc.

[0199] Although the computing devices (e.g., UE, network node, host) described herein may include a combination of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by a processing circuit that may process information in the following manner: for example, converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination based on the result of the processing. In addition, although the components are depicted as a single box located within a larger box or nested within multiple boxes, in fact, the computing device may include multiple different physical components that constitute a single illustrated component, and the functions may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of the components may be divided between the processing circuit and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0200] In some embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these specific embodiments, the processing circuit may be configured to perform the described functions regardless of whether instructions stored on a non-transitory device-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuits or other components of a computing device, but are enjoyed by the computing device as a whole and / or by end users and wireless networks in general.

[0201] Example embodiments are described below.

[0202] Embodiment 1. A method for operating a communication device in a communication network comprising a first network node and a second network node, wherein the first network node and the second network node provide dual connectivity to the communication device, the method comprising:

[0203] determining (1410) that a failure has occurred during sending of the report to the first network node; and

[0204] In response to determining that a failure has occurred, an action associated with the report is performed ( 1420 ).

[0205] Embodiment 2. The method according to embodiment 1, wherein the performing action comprises:

[0206] The report is sent to the second network node.

[0207] Embodiment 3. The method according to embodiment 2, wherein sending the report to the second network node comprises:

[0208] receiving a message from a second network node, the message comprising a request for the report; and

[0209] In response to receiving the message, the report is sent to the second network node.

[0210] Embodiment 4. The method according to embodiment 3, wherein the message is a second message,

[0211] The sending the report to the second network node further includes:

[0212] A first message is sent to the second network node, the first message requesting instructions on how to process the report.

[0213] Embodiment 5. The method according to any one of embodiments 1 to 4, wherein the performing action comprises:

[0214] After determining that a failure has occurred, a timer is started.

[0215] Embodiment 6. The method according to any one of embodiments 1 to 5, wherein the execution action includes: storing the report and / or the indication of the failure in a local memory.

[0216] Embodiment 7. The method according to embodiment 6, wherein the performing action further comprises:

[0217] In response to expiration of the timer, the report and / or the indication of the failure is deleted from the local memory.

[0218] Embodiment 8. The method according to any one of embodiments 6 to 7, wherein storing the report and / or the indication of the failure in a local memory comprises:

[0219] determining that a communication failure has occurred with the second network node; and

[0220] Responsive to determining that a communication failure has occurred with the second network node, the report and / or an indication of the failure is stored in local memory.

[0221] Embodiment 9. The method according to any one of embodiments 1 to 8, wherein the performing action further comprises:

[0222] The communication device is reconfigured with another signalling radio bearer.

[0223] Embodiment 10. The method according to any one of embodiments 1 to 9, wherein the performing action further comprises:

[0224] In response to reestablishing contact with the first network node, sending the report to the first network node.

[0225] Embodiment 11. The method according to any one of embodiments 1 to 10, wherein the report includes at least one of the following items:

[0226] Quality of Experience (QoE) reporting; and

[0227] Radio Access Network Visible QoE "RVQoE" reports.

[0228] Embodiment 12. The method according to any one of embodiments 1 to 11, wherein the first network node is a master node MN,

[0229] The failure is a master cell group MCG failure, and

[0230] The second network node is a secondary node SN.

[0231] Embodiment 13. The method according to any one of embodiments 1 to 11, wherein the first network node is a secondary node SN,

[0232] The failure is a secondary cell group SCG failure, and

[0233] The second network node is a master node MN.

[0234] Embodiment 14. A method of operating a first network node in a communication network including a second network node, the first network node and the second network node providing dual connectivity to a communication device, the method comprising:

[0235] determining (1510) that a failure has occurred during sending of the report from the communication device to the second network node; and

[0236] In response to determining that a failure has occurred, communicating with a communication device (1520).

[0237] Embodiment 15. The method according to embodiment 14, wherein communicating with the communication device includes: sending a message to the communication device, the message requesting the communication device to send the report to the first network node.

[0238] Embodiment 16. The method according to any one of embodiments 14 to 15, wherein communicating with the communication device comprises: receiving a message including the report from the communication device.

[0239] Embodiment 17. The method according to any one of embodiments 14 to 16, wherein the report includes at least one of the following items:

[0240] Quality of Experience (QoE) reporting; and

[0241] Radio Access Network Visible QoE "RVQoE" reports.

[0242] Embodiment 18. The method according to any one of embodiments 1 to 17, wherein the first network node is a master node MN,

[0243] The failure is a secondary cell group SCG failure, and

[0244] The second network node is a secondary node SN.

[0245] Embodiment 19. The method according to any one of embodiments 1 to 17, wherein the first network node is a secondary node SN,

[0246] The failure is a master cell group MCG failure, and

[0247] The second network node is a master node MN.

[0248] Embodiment 20. A communication device (1700), the communication device comprising:

[0249] Processing circuit (1702); and

[0250] A memory (1710), coupled to the processing circuit and having instructions stored therein, the instructions being executable by the communication device to cause the network node to perform operations including any of the operations described in embodiments 1 to 13.

[0251] Embodiment 21. A computer program comprising program code to be executed by a processing circuit (1702) of a communication device (1700), whereby execution of the program code causes the communication device to perform operations including any of the operations according to embodiments 1 to 13.

[0252] Embodiment 22. A computer program product comprising a non-transitory storage medium (1710) comprising program code to be executed by a processing circuit (1702) of a communication device (1700), whereby execution of the program code causes the communication device to perform operations including any of the operations described in embodiments 1 to 13.

[0253] Embodiment 23. A non-transitory computer-readable medium having instructions stored therein, the instructions executable by a processing circuit (1702) of a communication device (1700), the communication device (1700) being configured to perform operations including any of the operations described in Embodiments 1 to 13.

[0254] Embodiment 24. A network node (1800), the network node comprising:

[0255] processing circuit (1802); and

[0256] A memory (1804), coupled to the processing circuit and having instructions stored therein, the instructions being executable by the processing circuit to cause the network node to perform operations including any of the operations described in embodiments 14 to 19.

[0257] Embodiment 25. A computer program comprising program code to be executed by a processing circuit (1802) of a network node (1800), whereby execution of the program code causes the network node to perform operations including any of the operations according to embodiments 14 to 19.

[0258] Embodiment 26. A computer program product comprising a non-transitory storage medium (1804) comprising program code to be executed by a processing circuit (1802) of a network node (1800), whereby execution of the program code causes the network node to perform operations including any of the operations described in embodiments 14 to 19.

[0259] Embodiment 27. A non-transitory computer-readable medium having instructions stored therein, the instructions executable by a processing circuit (1802) of a network node (1800), the network node being configured to perform operations including any of the operations described in embodiments 14 to 19.

[0260] Embodiment 28. A host configured to operate in a communication system providing an over-the-top (OTT) service, the host comprising:

[0261] processing circuitry configured to provide user data; and

[0262] A network interface configured to initiate transmission of user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform operations to send the user data from a host to the UE: determining (1510) that a failure has occurred during transmission of a report from the communication device to a second network node; and

[0263] In response to determining that a failure has occurred, communicating with a communication device (1520).

[0264] Embodiment 29. A host according to any preceding embodiment, wherein:

[0265] The processing circuitry of the host is configured to execute a host application, the host application providing user data; and

[0266] The UE includes processing circuitry configured to execute a client application associated with a host application to receive a transmission of user data from the host.

[0267] Embodiment 30. A method implemented in a host configured to operate in a communication system, the communication system also including a network node and a user equipment (UE), the method comprising:

[0268] Providing user data to the UE; and

[0269] Initiating a transmission carrying user data to a UE via a cellular network including a network node, wherein the network node performs the following operations to send the user data from a host to the UE:

[0270] determining (1510) that a failure has occurred during sending of the report from the communication device to the second network node; and

[0271] In response to determining that a failure has occurred, communicating with a communication device (1520).

[0272] Embodiment 31. The method according to the previous embodiment further includes: at the network node, sending user data provided by the host for the UE.

[0273] Embodiment 32. A method according to any of the previous two embodiments, wherein user data is provided at the host by executing a host application, which interacts with a client application executed on the UE, and the client application is associated with the host application.

[0274] Embodiment 33. A communication system configured to provide an over-the-top service, the communication system comprising:

[0275] Host, including:

[0276] a processing circuit configured to provide user data for a user equipment (UE), the user data being associated with an over-the-top service; and

[0277] A network interface configured to initiate transmission of user data to a cellular network node for transmission to a UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform the following operations to send the user data from the host to the UE:

[0278] determining (1510) that a failure has occurred during sending of the report from the communication device to the second network node; and

[0279] In response to determining that a failure has occurred, communicating with a communication device (1520).

[0280] Embodiment 34. The communication system according to the previous embodiment further includes:

[0281] Network nodes; and / or

[0282] User equipment.

[0283] Embodiment 35. The communication system according to the previous two embodiments, wherein:

[0284] The processing circuitry of the host is configured to execute a host application to provide user data; and

[0285] The host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0286] Embodiment 36. A host configured to operate in a communication system providing an over-the-top (OTT) service, the host comprising:

[0287] a processing circuit configured to initiate reception of user data; and

[0288] a network interface configured to receive user data from a network node in a cellular network, the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform operations to receive user data from the UE for the host,

[0289] determining (1510) that a failure has occurred during sending of the report from the communication device to the second network node; and

[0290] In response to determining that a failure has occurred, communicating with a communication device (1520).

[0291] Embodiment 37. A host according to the preceding two embodiments, wherein:

[0292] The processing circuitry of the host is configured to execute a host application to provide user data; and

[0293] The host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0294] Embodiment 38. A host according to any of the previous two embodiments, wherein initiating reception of user data comprises requesting user data.

[0295] Embodiment 39. A method implemented by a host configured to operate in a communication system, the communication system also including a network node and a user equipment (UE), the method comprising:

[0296] At the host, reception of user data from the UE is initiated, the user data originating from a transmission that the network node has received from the UE, wherein the network node performs the following operations to receive the user data from the UE for the host:

[0297] determining (1510) that a failure has occurred during sending of the report from the communication device to the second network node; and

[0298] In response to determining that a failure has occurred, communicating with a communication device (1520).

[0299] Embodiment 40. The method according to the previous embodiment further includes: at the network node, sending the received user data to the host.

[0300] Embodiment 41. A host configured to operate in a communication system providing an over-the-top (OTT) service, the host comprising:

[0301] processing circuitry configured to provide user data; and

[0302] A network interface configured to initiate transmission of user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a communication interface and a processing circuit, wherein the communication interface and the processing circuit of the UE are configured to perform the following operations to receive the user data from the host:

[0303] determining (1410) that a failure has occurred during sending of the report to the first network node; and

[0304] In response to determining that a failure has occurred, an action associated with the report is performed ( 1420 ).

[0305] Embodiment 42. The host of the previous embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE to send user data from the host to the UE.

[0306] Embodiment 43. A host according to the preceding two embodiments, wherein:

[0307] The processing circuitry of the host is configured to execute a host application to provide user data; and

[0308] The host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0309] Embodiment 44. A method implemented by a host operating in a communication system, the communication system also including a network node and a user equipment (UE), the method comprising:

[0310] Providing user data to the UE; and

[0311] Initiating a transmission carrying user data to a UE via a cellular network including a network node, wherein the UE performs the following operations to receive the user data from the host:

[0312] determining (1410) that a failure has occurred during sending of the report to the first network node; and

[0313] In response to determining that a failure has occurred, an action associated with the report is performed ( 1420 ).

[0314] Embodiment 45. The method according to the previous embodiment further comprises:

[0315] At the host, a host application associated with the client application executing on the UE is executed to receive user data from the UE.

[0316] Embodiment 46. The method according to the previous embodiment further comprises:

[0317] sending, at the host, input data to a client application executing on the UE, the input data being provided by execution of the host application,

[0318] The user data is provided by the client application in response to input data from the host application.

[0319] Embodiment 47. A host configured to operate in a communication system providing an over-the-top (OTT) service, the host comprising:

[0320] processing circuitry configured to utilize user data; and

[0321] a network interface configured to receive transmission of user data to a cellular network for transmission to a user equipment (UE),

[0322] The UE includes a communication interface and a processing circuit, and the communication interface and the processing circuit of the UE are configured to perform the following operations to send user data to the host:

[0323] determining (1410) that a failure has occurred during sending of the report to the first network node; and

[0324] In response to determining that a failure has occurred, an action associated with the report is performed ( 1420 ).

[0325] Embodiment 48. The host of the previous embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE to send user data from the UE to the host.

[0326] Embodiment 49. A host according to the preceding two embodiments, wherein:

[0327] The processing circuitry of the host is configured to execute a host application to provide user data; and

[0328] The host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0329] Embodiment 50. A method implemented by a host configured to operate in a communication system, the communication system also including a network node and a user equipment (UE), the method comprising:

[0330] At a host, user data sent by a UE to the host via a network node is received, wherein the UE performs the following operations to send the user data to the host:

[0331] determining (1410) that a failure has occurred during sending of the report to the first network node; and

[0332] In response to determining that a failure has occurred, an action associated with the report is performed ( 1420 ).

[0333] Embodiment 51. The method according to the previous embodiment further comprises:

[0334] At the host, a host application associated with the client application executing on the UE is executed to receive user data from the UE.

[0335] Embodiment 52. The method according to the previous embodiment further comprises:

[0336] sending, at the host, input data to a client application executing on the UE, the input data being provided by execution of the host application,

[0337] The user data is provided by the client application in response to input data from the host application.

Claims

1. A method of operating a communication device in a communication network comprising a first network node and a second network node, wherein the first network node and the second network node provide dual connectivity to the communication device, the method comprising: determining (1410) that a failure has occurred during sending a report to the first network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; In response to determining that the failure has occurred, suspending (1415) sending the report to the first network node; as well as In response to determining that the failure has occurred, an action associated with the report is performed ( 1420 ).

2. The method according to claim 1, wherein: Executing the actions includes: The report is sent to the second network node.

3. The method according to claim 2, wherein: Sending the report to the second network node includes: receiving a message from the second network node, the message comprising a request for the report; and In response to receiving the message, sending the report to the second network node.

4. The method according to claim 3, wherein: The message is a second message, The sending the report to the second network node further includes: A first message is sent to the second network node, the first message requesting instructions on how to process the report.

5. The method according to any one of claims 1 to 4, wherein: Executing the actions includes: After determining that the failure has occurred, a timer is started.

6. The method according to any one of claims 1 to 5, wherein: Performing the actions includes storing the report and / or the indication of the failure in a local memory.

7. The method according to claim 6, wherein: Executing the actions also includes: In response to expiration of the timer, deleting the report and / or the indication of the failure from the local memory.

8. The method according to any one of claims 6 to 7, wherein: Storing the report and / or the indication of the failure in the local memory comprises: determining that a communication failure has occurred with the second network node; and Responsive to determining that the communication failure has occurred with the second network node, storing the report and / or an indication of the failure in the local memory.

9. The method according to any one of claims 1 to 8, wherein: Executing the actions also includes: The communication device is reconfigured with another signaling radio bearer.

10. The method according to any one of claims 1 to 9, wherein: Executing the actions also includes: In response to reestablishing contact with the first network node, sending the report to the first network node.

11. The method according to any one of claims 1 to 10, wherein: The first network node is a secondary node SN, The failure is a secondary cell group SCG failure, and The second network node is a master node MN.

12. The method according to any one of claims 1 to 10, wherein: The first network node is a master node MN, The failure is a master cell group MCG failure, and The second network node is a secondary node SN.

13. A method of operating a first network node in a communication network comprising a second network node, the first network node and the second network node providing dual connectivity to a communication device, the method comprising: determining (1510) that a failure has occurred during sending of a report from the communication device to the second network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; and In response to determining that the failure has occurred, communicating with the communication device (1520).

14. The method according to claim 13, wherein: Communicating with the communication device comprises sending a message to the communication device, the message requesting the communication device to send the report to the first network node.

15. The method according to any one of claims 13 to 14, wherein: Communicating with the communication device includes receiving a message including the report from the communication device.

16. The method according to any one of claims 13 to 15, wherein: The first network node is a master node MN, The failure is a secondary cell group SCG failure, and The second network node is a secondary node SN.

17. The method according to any one of claims 13 to 15, wherein: The first network node is a secondary node SN, The failure is a master cell group MCG failure, and The second network node is a master node MN.

18. A communication device (1700), configured to perform operations, the operations comprising: determining (1410) that a failure has occurred during sending a report to the first network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; In response to determining that the failure has occurred, suspending (1415) sending the report to the first network node; as well as In response to determining that the failure has occurred, an action associated with the report is performed ( 1420 ).

19. The communication device of claim 18, the operations further comprising any of the operations of claims 2 to 12.

20. A computer program comprising program code to be executed by processing circuitry (1702) of a communication device (1700), whereby execution of the program code causes the communication device to perform operations comprising: determining (1410) that a failure has occurred during sending a report to the first network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; In response to determining that the failure has occurred, suspending (1415) sending the report to the first network node; as well as In response to determining that the failure has occurred, an action associated with the report is performed ( 1420 ).

21. The computer program of claim 20, the operations further comprising any of the operations of claims 2 to 12.

22. A computer program product comprising a non-transitory storage medium (1710), the non-transitory storage medium (1710) comprising program code to be executed by processing circuitry (1702) of a communication device (1700), whereby execution of the program code causes the communication device to perform operations comprising: determining (1410) that a failure has occurred during sending a report to the first network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; In response to determining that the failure has occurred, suspending (1415) sending the report to the first network node; as well as In response to determining that the failure has occurred, an action associated with the report is performed ( 1420 ).

23. The computer program product of claim 22, the operations further comprising any of the operations of claims 2 to 12.

24. A communication device (1700), the communication device comprising: Processing circuit (1702); as well as a memory (1710), coupled to the processing circuit and having instructions stored therein, the instructions being executable by the communication device to cause a network node to perform operations comprising: determining (1410) that a failure has occurred during sending a report to the first network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; In response to determining that the failure has occurred, suspending (1415) sending the report to the first network node; and In response to determining that the failure has occurred, an action associated with the report is performed ( 1420 ).

25. The communication device of claim 24, the operations further comprising any of the operations of claims 2 to 12.

26. A network node (1800), configured to perform operations, the operations comprising: determining (1510) that a failure has occurred during sending of a report from the communication device to the second network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; and In response to determining that the failure has occurred, communicating with the communication device (1520).

27. The network node of claim 26, the operations further comprising any of the operations of claims 14 to 17.

28. A computer program comprising program code to be executed by a processing circuit (1802) of a network node (1800), whereby execution of the program code causes the network node to perform operations comprising: determining (1510) that a failure has occurred during sending of a report from the communication device to the second network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; and In response to determining that the failure has occurred, communicating with the communication device (1520).

29. The computer program of claim 28, the operations further comprising any of the operations of claims 14 to 17.

30. A computer program product comprising a non-transitory storage medium (1804), the non-transitory storage medium (1804) comprising program code to be executed by a processing circuit (1802) of a network node (1800), whereby execution of the program code causes the network node to perform operations comprising: determining (1510) that a failure has occurred during sending of a report from the communication device to the second network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; and In response to determining that the failure has occurred, communicating with the communication device (1520).

31. The computer program product of claim 30, the operations further comprising any of the operations of claims 14 to 17.

32. A network node (1800), the network node comprising: Processing circuit (1802); as well as a memory (1804), coupled to the processing circuit and having instructions stored therein, the instructions being executable by the processing circuit to cause the network node to perform operations comprising: determining (1510) that a failure has occurred during sending of a report from the communication device to the second network node, the report comprising a Quality of Experience (QoE) report and / or a Radio Access Network Visible QoE (RVQoE) report; and In response to determining that the failure has occurred, communicating with the communication device (1520).

33. The network node of claim 32, the operations further comprising any of the operations of claims 14 to 17.

Images