Inter-node signaling for sn-initiated spr

Abstract

According to some embodiments, a method is performed by a wireless device operating in dual connectivity with a master node (MN) and a secondary node (SN). The method comprises: receiving a successful PSCell report (SPR) configuration from the SN; receiving from the MN an indication that a PSCell change is a SN-initiated PSCell change; and applying the SPR configuration for the PSCell change to determining logging of the SPR.

Description

Inter-Node Signaling for SN -initiated SPRTECHNICAL FIELD

[0001] Embodiments of the present disclosure are directed to wireless communications and, more particularly, to inter-node signaling for secondary node (SN)-initiated successful PSCell report (SPR).BACKGROUNDWireless communication systems in Third Generation Partnership Project (3GPP)

[0002] Consider the simplified wireless communication system illustrated in FIGURE 1, with a user equipment (UE) 102, which communicates with one or multiple access nodes 103 and 104, which in turn is connected to a network node 106. Access nodes 103 and 104 are part of radio access network 100.

[0003] For wireless communication systems pursuant to Third Generation Partnership Project(3GPP) Evolved Packet System (EPS) (also referred to as Long Term Evolution (LTE) or fourth generation (4G)) standard specifications, such as specified in 3GPP TS 36.300 and related specifications, access nodes 103 and 104 correspond typically to an Evolved NodeB (eNB) and network node 106 corresponds typically to either a Mobility Management Entity (MME) and / or a Serving Gateway (SGW). The eNB is part of radio access network 100, which in this case is the E-UTRAN (Evolved Universal Terrestrial Radio Access Network), while the MME and SGW are both part of the EPC (Evolved Packet Core network). The eNBs are inter-connected via the X2 interface, and connected to EPC via the SI interface, more specifically via Sl-C to the MME and Sl-U to the SGW.

[0004] For wireless communication systems pursuant to 3GPP fifth generation (5G) system, 5GS (also referred to as New Radio (NR) or 5G) standard specifications, such as specified in 3GPP TS 38.300 and related specifications, on the other hand, access nodes 103 and 104 corresponds typically to a 5G NodeB (gNB) and the network node 106 corresponds typically to either an Access and Mobility Management Function (AMF) and / or a User Plane Function (UPF). The gNB is part of radio access network 100, which in this case is the NG-RAN (Next Generation Radio Access Network), while the AMF and UPF are both part of the 5G Core Network (5GC). The gNBs areinter-connected via the Xn interface, and connected to 5GC via the NG interface, more specifically via NG-C to the AMF and NG-U to the UPF.

[0005] To support fast mobility between NR and LTE and avoid change of core network, LTE eNBs may also be connected to the 5G-CN viaNG-U / NG-C and support the Xn interface. An eNB connected to 5GC is referred to as a next generation eNB (ng-eNB) and is considered part of the NG-RAN. LTE connected to 5GC will not be discussed further herein; however, the solutions / features / embodiments described herein for LTE and NR also apply to LTE connected to 5GC. When the term LTE is used herein without further specification, it refers to LTE-EPC.Self-Organizing Networks in 3GPP

[0006] A Self-Organizing Network (SON) is an automation technology designed to make the planning, configuration, management, optimization, and healing of mobile radio access networks simpler and faster. SON functionality and behavior has been defined and specified in generally accepted mobile industry recommendations produced by organizations such as 3GPP and the NGMN (Next Generation Mobile Networks).

[0007] In 3GPP, the processes within the SON area are classified into self-configuration process and self-optimization process. Self-configuration process is the process where newly deployed nodes are configured by automatic installation procedures to get the necessary basic configuration for system operation.

[0008] This process works in pre-operational state. Pre -operational state is understood as the state from when the eNB is powered up and has backbone connectivity until the radio frequency (RF) transmitter is switched on.

[0009] As illustrated in FIGURE 2, functions handled in the pre-operational state, like basic setup and initial radio configuration, are covered by the self configuration process. Selfoptimization process is defined as the process where a UE and access node measurements and performance measurements are used to auto-tune the network.

[0010] This process works in operational state. Operational state is understood as the state where the RF interface is additionally switched on. As described in FIGURE 2, functions handled in the operational state, like optimization / adaptation, are covered by the self optimization process.

[0011] LTE specifies support for self-configuration and self-optimization as described in 3GPP TS 36.300 section 22.2, including features such as dynamic configuration, automaticneighbor relation (ANR), mobility load balancing, mobility robustness optimization (MRO), random access channel (RACH) optimization and support for energy saving.

[0012] NR specifies support for self-configuration and self-optimization as well, starting with self-configuration features such as dynamic configuration, automatic neighbor relation (ANR) in Rel-15, as described in 3GPP TS 38.300 section 15. NR Rel-16 specifies more SON features, including self-optimization features such as mobility robustness optimization (MRO).Successful handover report

[0013] Successful handover (HO) report (SHR) has been standardized as part of 3GPP Rel 17 TS e.g., see Radio Resource Control (RRC) specification 38.331 (V17.0.0). The main purpose of the successful HO report is to enable the network nodes to deduce sub-optimal performance of the underlaying procedures executed during the HO procedure.

[0014] The network node upon being interested in SHR, may configure a UE to report the SHR after successful execution of a HO, if at least one of the SHR triggering conditions / thresholds is met. The SHR triggering thresholds are defined as the following:• Whether the T304 timer value was above a certain threshold at the time of successful HO execution (thresholdPercentageT304)• Whether the T310 timer value was above a certain threshold at the time of successful HO execution (thresholdPercentageT310)• Whether the T312 timer value was above a certain threshold at the time of successful HO execution (ihresholdl’e rceniageT312)• Whether the UE experienced radio link failure (RLF) at the source node while performing a dual active protocol stack (DAPS) HO (sourceDAPS-FailureReporting).

[0015] When storing the successful handover report, the UE may include various information to aid the network to optimize the handover, such as measurements of the neighboring cells, the fulfilled condition that triggered the successful handover report (e.g., threshold on T310 exceeded, specific RLF issue in the source node while doing DAPS HO), etc.

[0016] The SHR may be configured by a certain serving cell, and when triggering conditions for SHR logging are fulfilled, the UE stores this information until the network requests it. In particular, the UE may indicate availability of SHR information in certain RRC message, such as RRCReconfigurationComplete, RRCReestablishmentComplete, RRCSetupComplete, RRCResumeComplete, and the network may request such information via theUEInformationRequest message, upon which the UE transmits the stored SHR in the UEInformationResponse message.Multi-Radio Dual Connectivity

[0017] Multi-Radio Dual Connectivity (MR-DC) describes the scenario where a UE capable of connecting to multiple nodes uses the multiple resources to increase throughput as described in TS 37.340. This is a generalization of the intra-E-UTRA dual connectivity described in TS 36.300.

[0018] When a UE is in DC mode, one node acts as the master node (MN) and the other node acts as a secondary node (SN). The MN and SN are connected via a network interface and at least the MN is connected to the core network. Details on MR-DC can be found in TS 38.401. The primary cell in MN is known as PCell and the primary cell in SN is known as PSCell.Successful PSCell Report (SPR)

[0019] The ongoing rel-18 Work Item “New WID on further enhancement of data collection for SON (Self-Organizing Networks) / MDT (Minimization of Drive Tests) in NR standalone and MR-DC (Multi -Radio Dual Connectivity)” has the following objective: support of SON / MDT enhancements for successful PScell change report. The successful PScell (change) report, or SPR, is likely to have the same properties as the SHR described above, but is related to PSCell change / addition events, which means that the UE will generate an SPR, if events configured by the network are triggered during a PSCell Change or PSCell Addition. The UE will advertise the presence of the SPR to the network, which will in return fetch it. Network signaling will then be used to send the SPR to the node that configured the event that triggered the creation of the SPR. The SPR will be used by the network node to optimize PSCell Change / Addition.

[0020] There currently exist certain challenges. For example, for SN-initiated PSCell change, the source SN is responsible for configuring the T310 and T312 SPR triggers. This configuration can happen before or during the PSCell Change preparation. Also, the UE needs to know if the PSCell Change was MN-initiated (i.e., triggered by MN) or SN-initiated (i.e., triggered by SN). This information shall be sent to the UE only if SPR has been configured, by either MN, source SN or target SN. Two SPR configurations can co-exist in the UE (one from MN, the other from source SN), but only one SPR configuration will be applied by the UE to determine whether SPRshould be logged or not, depending on the “MN-initiated” or “SN-initiated” indicator received by the UE in the PSCell Change command.

[0021] However, there are some cases where the MN does not know if the source SN has configured (e.g., via SRB3) a UE with SPR. Another example is the source SN configuring the SPR configuration over SRB1 in advance, i.e., the SN configures the UE with SPR configuration via SRB1 prior to initiating the PSCell change procedure. In such cases, when the SN-initiated PSCell change is executed by the UE, the MN does not know whether the UE was configured with the SPR configuration by the source SN. Thus, the MN will not be able to know when to signal to the UE the indication of whether the PSCell Change was SN-initiated or MN-initiated. The UE in this case would need to select the SPR configuration provided by the source SN, because the PSCell change is SN-initiated, but because the UE would not know that the PSCell change was SN-initiated, the UE will not be able to determine which SPR configuration to execute. As a consequence, the UE will also not be able to indicate the information of whether the PSCell change was SN- or MN-initiated into the SPR itself. This will make the SPR useless for the network (because the network does not know which node, MN or SN, should optimize mobility parameters).SUMMARY

[0022] As described above, certain challenges currently exist with inter-node signaling for secondary node (SN)-initiated successful PSCell report (SPR). Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, in some embodiments, a source SN configures a user equipment (UE) with an SPR configuration including one or more parameters for the UE to determine whether to log the SPR.

[0023] According to some embodiments, a method is performed by a wireless device operating in dual connectivity with a master node (MN) and a SN. The method comprises: receiving a SPR configuration from the SN; receiving from the MN an indication that a PSCell change is a SN-initiated PSCell change; and applying the SPR configuration for the PSCell change to determining logging of the SPR.

[0024] In particular embodiments, the method further comprises transmitting the SPR to a network node. The SPR comprises an indication that the PSCell change was SN-initiated.

[0025] In particular embodiments, the SPR configuration comprises one or more thresholds for triggering SPR generation.

[0026] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.

[0027] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

[0028] According to some embodiments, a method is performed by a network node operating as a SN for a wireless device operating in dual connectivity with a MN and the SN. The method comprises configuring the wireless device with a SPR configuration and transmitting to the MN an indication that the wireless device is configured with the SPR configuration.

[0029] In particular embodiments, the indication transmitted to the MN comprises an indication that a PSCell change is needed. The indication may comprise an information element in a S-Node Change Required indicating that a PSCell change is needed.

[0030] In particular embodiments, the indication transmitted to the MN comprises a CG- Config message contained in a S-Node Change Required message or S-Node Modification.

[0031] In particular embodiments, the indication transmitted to the MN comprises an indication that the PSCell change is SN-initiated.

[0032] In particular embodiments, the SPR configuration comprises one or more thresholds for triggering SPR generation.

[0033] According to some embodiments, a method is performed by a network node operating as a MN for a wireless device operating in dual connectivity with a SN and the MN. The method comprises receiving an indication from the SN that the wireless device is configured with a SPR configuration and transmitting an indication to the wireless device that a PSCell change is a SN- initiated PSCell change.

[0034] In particular embodiments, the indication received from the SN comprises an indication that a PSCell change is needed. The indication may comprise an information element in a S-Node Change Required indicating that a PSCell change is needed.

[0035] In particular embodiments, the indication received from the SN comprises a CG- Config message contained in a S-Node Change Required message or S-Node Modification.

[0036] In particular embodiments, the indication received from the SN comprises an indication that the PSCell change is SN-initiated.

[0037] In particular embodiments, the SPR configuration comprises one or more thresholds for triggering SPR generation.

[0038] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0039] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network nodes described above.

[0040] Certain embodiments may provide one or more of the following technical advantages.For example, if a source SN has configured a UE with T310 / T312 SPR triggers, the MN and the UE will be able to understand that SPR has been configured and that the SN-initiated SPR configuration shall be applied. In return, the UE will be able to indicate to the network, in the SPR, that the PSCell Change was MN-initiated. By including such information to MN, SN informs MN that the UE is configured with a SN configured SPR and thus needs to know the PSCell change initiator information.BRIEF DESCRIPTION OF THE DRAWINGS

[0041] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:FIGURE 1 is a network diagram illustrating a simplified wireless communication system.FIGURE 2 is a flowchart illustrating self-configuration / self-optimization functionality (from 3GPP TS 36.300 figure 22.1-1);FIGURE 3 illustrates an example communication system, according to certain embodiments;FIGURE 4 illustrates an example UE, according to certain embodiments;FIGURE 5 illustrates an example network node, according to certain embodiments;FIGURE 6 illustrates a block diagram of a host, according to certain embodiments;FIGURE 7 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;FIGURE 8 illustrates a host communicating via a network node with a UE over a partially wireless connection, according to certain embodiments;FIGURE 9 is a flowchart illustrating an example method in a wireless device, according to particular embodiments;FIGURE 10 is a flowchart illustrating an example method in a network node operating as a secondary node (SN) in dual connectivity, according to particular embodiments; andFIGURE 11 is a flowchart illustrating an example method in a network node operating as a master node (MN) in dual connectivity, according to particular embodiments.DETAILED DESCRIPTION

[0042] As described above, certain challenges currently exist with inter-node signaling for secondary node (SN)-initiated successful PSCell report (SPR). Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, in some embodiments, a source SN configures a user equipment (UE) with an SPR configuration including one or more parameters for the UE to determine whether to log the SPR. A master node (MN) determines that the source SN has configured the SPR configuration to the UE based on one or more of the following information:• The SN signals information to the MN that the UE is configured with a SPR configuration, wherein the information may be provided, e.g., as part of the SN-initiated PSCell change preparation (e.g., in the S-Node change required), or in response to the source SN configuring the UE with SPR configuration (e.g., as part of S-Node modification procedure)• The MN determining that the RRCReconfiguration transmitted by the source SN to the UE contains the SPR configuration for the UE

[0043] In some embodiments, the SN sends the above listed information to the MN only if the SPR configuration is configured at the UE by the source SN.

[0044] In response of the above actions, the MN indicates to the UE one or more of the following information: (a) that the PSCell change is an SN-initiated PSCell Change, and (b) that the SPR configuration provided by the SN should be applied by the UE for the concerned PSCell change, wherein the above information may be provided by the MN after receiving indication from the SN to initiate the PSCell change (e.g., upon receiving the S-Node change required).

[0045] In some embodiments, the UE applies and / or monitors the SPR configuration provided by the source SN serving the PSCell for the concerned SN-initiated PSCell change to determine the logging of the SPR.

[0046] Some embodiments include a method for a network node, acting as secondary node (source SN) in dual connectivity. The method comprises configuring the UE with an SPR configuration, including one or more parameters for the UE to determine whether to log the SPR. The SPR configuration including, e.g., the threshold on T310 / T312 as triggering conditions for the SPR generation.

[0047] The method comprises transmitting an indication to the MN indicating that the UE is configured with a SPR configuration, wherein the indication may be transmitted in one of the following messages:• In a new information element (IE) in the S-Node Change Required indicating that a PSCell Change is needed;• In a CG-Config message, which is contained in the S-Node Change Required message, or S-Node Modification.• In one embodiment, the indication also indicates that the PSCell Change is “SN-initiated.” In that case the MN implicitly deduces that the UE is configured with a SPR configuration (e.g., a new “SN-initiated” IE is added to above messages).In one embodiment, in response of reconfiguring the SPR configuration of the UE, the SN transmits an indication to the MN that the SPR configuration is reconfigured, wherein such indication may comprise an indication that the SPR configuration is not configured any longer to the UE, or the indication of the new SPR configuration comprising one or more parameters for the logging of the SPR. Such reconfiguration information may be sent as part of the S-Node modification.

[0048] Some embodiments include extension of the method to the intra-SN PSCell change scenario. In an embodiment, for the intra-SN PSCell change procedure, the source SN sends the SN initiated PSCell change indication directly to the UE in the PSCell change command (send over SRB3 or SRB 1), In this scenario the indication of SN initiated PSCell change is not explicitly sent to the MN, but to the UE, if the SPR configuration is configured either prior to or as part of the intra-SN PSCell change RRC Reconfiguration.

[0049] Some embodiments include MN embodiments. Particular embodiments include a method for a network node, acting as Master Node (MN) in Dual-Connectivity. The method comprises receiving a message from the SN comprising an indication that that the UE is configured with a SPR configuration, wherein the message may be one of the following:A new information element (IE) in the S-Node Change Required message• A new IE in the CG-Config message, which is contained in the S-Node Change Required message, or in the S-Node Modification• The RRCReconfiguration transmitted by the source SN to the UE containing the SPR configuration for the UE. This action implies that the UE read the RRCReconfiguration transmitted by the source SN and checks if it contains the SPR configuration for the UE• In one embodiment the MN implicitly deduces that the UE is configured with a SPR configuration by receiving the indication (via same messages as above) that the PSCell Change is SN-initiated.

[0050] In response to determining that the UE is configured with an SPR configuration configured by the SN, the method further comprises transmitting an indication to the UE, e.g., as part of the RRC Reconfiguration with synchronization for the PSCell change, one or more of the following information:• That the PSCell Change is SN-initiated• That the SPR configuration provided by the SN should be applied by the UE for the concerned PSCell change

[0051] In some embodiments, the MN receives an indication that the SN has configured the UE with SPR. In some embodiments, the indication is a new IE contained in S-Node Modification Request. In some embodiments, the indication is contained in a new XnAP message.

[0052] In some of the above embodiments, the MN stores the indication of whether the UE is configured or not configured with SPR configuration provided by the source SN. For example, at the moment of receiving S-Node modification (e.g., transmitted by the source SN in advance, before the S-Node change required transmission), the MN stores the status of the SPR configuration for the concerned UE. At the moment of receiving configuration for the UE to initiate the SN-initiated PSCell change, the MN checks whether it has stored for the concerned UE an indication indicating that the UE is configured with SPR configuration provided by the source SN. If this is the case, the MN indicates to the UE an indication that the PSCell change is SN- initiated (from which the UE deduces that the SPR-configuration provided by the source SN should be applied for the PSCell change), or that SPR configuration provided by the SN should be applied by the UE for the concerned PSCell change.

[0053] Certain embodiments may provide one or more of the following technical advantages. For example, if a source SN has configured a UE with T310 / T312 SPR triggers, the MN and the UE will be able to understand that SPR has been configured and that the SN-initiated SPR configuration shall be applied. In return, the UE will be able to indicate to the network, in the SPR, that the PSCell Change was MN-initiated. By including such information to MN, SN informs MNthat the UE is configured with a SN configured SPR and thus needs to know the PSCell change initiator information.

[0054] FIGURE 3 illustrates an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0055] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0056] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0057] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108)that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0058] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0059] As a whole, the communication system 100 of 1FIGURE 3 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are 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 standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the 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 such as LoRa and Sigfox.

[0060] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

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

[0062] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0063] The hub 114 may have a constant / persi stent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to anM2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0064] FIGURE 4 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0065] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (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 relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which 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 for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0066] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 4. The level of integration between the componentsmay vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0067] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine -readable computer programs in the memory 210. The processing circuitry 202 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 together with appropriate firmware; one or more stored computer programs, general -purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0068] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, 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 the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0069] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from thepower source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0070] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0071] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0072] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, 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 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations,and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0073] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0074] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0075] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0076] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smartspeaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical 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 for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in FIGURE 4.

[0077] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0078] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from 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 and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0079] FIGURE 5 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, accesspoints (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).

[0080] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, 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 donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units 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).

[0081] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0082] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave,LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0083] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0084] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0085] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0086] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, forexample to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises fdters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0087] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0088] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0089] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may beconfigured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0090] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0091] Embodiments of the network node 300 may include additional components beyond those shown in FIGURE 5 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0092] FIGURE 6 is a block diagram of a host 400, which may be an embodiment of the host 116 of FIGURE 3, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs.

[0093] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such asFigures 3 and 4, such that the descriptions thereof are generally applicable to the corresponding components of host 400.

[0094] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile 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 transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0095] FIGURE 7 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0096] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in thevirtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0097] Hardware 504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.

[0098] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0099] In the context of NFV, a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.

[0100] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one ormore transmiters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.

[0101] FIGURE 8 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of FIGURE 3 and / or UE 200 of FIGURE 4), network node (such as network node 110a of FIGURE 3 and / or network node 300 of FIGURE 5), and host (such as host 116 of FIGURE 3 and / or host 400 of FIGURE 6) discussed in the preceding paragraphs will now be described with reference to FIGURE 8.

[0102] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmited using the OTT connection 650.

[0103] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of FIGURE 3) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0104] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide userdata in response to the request data. The OTT connection 650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650.

[0105] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawn abstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0106] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.

[0107] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, thenetwork node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606.

[0108] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 forms the last segment. More precisely, the teachings of these embodiments may improve the delay to directly activate an SCell by RRC and power consumption of user equipment and thereby provide benefits such as reduced user waiting time and extended battery lifetime.

[0109] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0110] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and / or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art. In certainembodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.[oni] FIGURE 9 is a flowchart illustrating an example method 900 in a wireless device, according to particular embodiments. In particular embodiments, one or more steps of FIGURE 9 may be performed by wireless device 200 described with respect to FIGURE 4.

[0112] The method begins at step 912, where the wireless device (e.g., UE 200) receives a successful PSCell report (SPR) configuration from the SN. The wireless device may receive the SPR configuration according to any of the embodiments and examples described herein.

[0113] At step 914, the wireless device receives from the MN an indication that a PSCell change is a SN-initiated PSCell change. The wireless device may receive the indication according to any of the embodiments and examples described herein.

[0114] At step 916, the wireless device applies the SPR configuration for the PSCell change to determining logging of the SPR. For example, the SPR configuration may comprise one or more thresholds for triggering SPR generation. The wireless device may log the SPR if one of thresholds in the SPR configuration is triggered.

[0115] At step 918, the wireless device may transmit the SPR to a network node. The SPR comprises an indication that the PSCell change was SN-initiated.

[0116] Modifications, additions, or omissions may be made to method 900 of FIGURE 9. Additionally, one or more steps in the method of FIGURE 9 may be performed in parallel or in any suitable order.

[0117] FIGURE 10 is a flowchart illustrating an example method 1000 in a network node operating as a secondary node (SN) in dual connectivity, according to particular embodiments. In particular embodiments, one or more steps of FIGURE 10 may be performed by network node 300 described with respect to FIGURE 5.

[0118] The method begins at step 1012, where the network node (e.g., network node 300) configures the wireless device with a SPR configuration. The network node may configure the wireless device according to any of the embodiments and examples described herein.

[0119] At step 1014, the network node transmits to the MN an indication that the wireless device is configured with the SPR configuration. In particular embodiments, the indication transmitted to the MN comprises a CG-Config message contained in a S-Node Change Requiredmessage or S-Node Modification. In particular embodiments, the indication transmitted to the MN comprises an indication that the PSCell change is SN-initiated. In particular embodiments, the SPR configuration comprises one or more thresholds for triggering SPR generation.

[0120] In particular embodiments, the indication comprises any of the indications described with respect to any of the embodiments and examples described herein.

[0121] Modifications, additions, or omissions may be made to method 1000 of FIGURE 10. Additionally, one or more steps in the method of FIGURE 10 may be performed in parallel or in any suitable order.

[0122] FIGURE 11 is a flowchart illustrating an example method 1100 in a network node operating as a master node (MN) in dual connectivity, according to particular embodiments. In particular embodiments, one or more steps of FIGURE 11 may be performed by network node 300 described with respect to FIGURE 5.

[0123] The method begins at step 1112, where the network node (e.g., network node 300) receives an indication from the SN that the wireless device is configured with a SPR configuration. In particular embodiments, the indication received from the SN comprises an indication that a PSCell change is needed. The indication may comprise an information element in a S-Node Change Required indicating that a PSCell change is needed. In particular embodiments, the indication received from the SN comprises a CG-Config message contained in a S-Node Change Required message or S-Node Modification. In particular embodiments, the indication received from the SN comprises an indication that the PSCell change is SN-initiated. In particular embodiments, the SPR configuration comprises one or more thresholds for triggering SPR generation.

[0124] In particular embodiments, the indication comprises any of the indications described with respect to any of the embodiments and examples described herein.

[0125] At step 1114, the network node transmits an indication to the wireless device that a PSCell change is a SN-initiated PSCell change. The network node may transmit the indication according to any of the embodiments and examples described herein.

[0126] Modifications, additions, or omissions may be made to method 1100 of FIGURE 11. Additionally, one or more steps in the method of FIGURE 11 may be performed in parallel or in any suitable order.

[0127] Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

[0128] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0129] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0130] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.EXAMPLE EMBODIMENTSGroup A Embodiments1. A method performed by a wireless device operating in dual connectivity with a master node (MN) and a secondary node (SN), the method comprising:- receiving a successful PSCell report (SPR) configuration from the SN;- receiving from MN an indication that a PSCell change is a SN-initiated PSCell change; and- applying the SPR configuration for the PSCell change to determining logging of the SPR.2. A method performed by a wireless device, the method comprising:any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.3. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.4. The method of any of the previous embodiments, further comprising:- providing user data; and- forwarding the user data to a host computer via the transmission to the base station.5. A method performed by a base station operating as a secondary node (SN) for a wireless device operating in dual connectivity with a master node (MN) and the SN, the method comprising:- configuring the wireless device with a successful PSCell report (SPR) configuration; and- transmitting to the MN an indication that the wireless device is configured with the SPR configuration.6. The method of the previous embodiment, wherein the indication transmitted to the MN comprises any one of:- an information element in a S-Node Change Required indicating that a PSCell change is needed;- a CG-Config message, which is contained in a S-Node Change Required message, or S-Node Modification.- an indication that the PSCell Change is “SN-initiated”.7. A method performed by a base station operating as a master node (MN) for a wireless device operating in dual connectivity with a secondary node (SN) and the MN, the method comprising:- receiving an indication from the SN that the wireless device is configured with a successful PSCell report (SPR) configuration; andtransmitting an indication to the wireless device that a PSCell change is a SN- initiated PSCell change.8. The method of the previous embodiment, wherein the indication received from the SN comprises any one of:- an information element in a S-Node Change Required indicating that a PSCell change is needed;- a CG-Config message, which is contained in a S-Node Change Required message, or S-Node Modification.- An indication that the PSCell Change is “SN-initiated”.9. A method performed by a base station, the method comprising:- any of the steps, features, or functions described above with respect to base stations, either alone or in combination with other steps, features, or functions described above.10. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.11. The method of any of the previous embodiments, further comprising:- obtaining user data; and- forwarding the user data to a host computer or a wireless device.12. A mobile terminal comprising:- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and- power supply circuitry configured to supply power to the wireless device.13. A base station comprising:- processing circuitry configured to perform any of the steps of any of the Group Bembodiments; power supply circuitry configured to supply power to the wireless device. A user equipment (UE) comprising:- an antenna configured to send and receive wireless signals;- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and- a battery connected to the processing circuitry and configured to supply power to the UE. A communication system including a host computer comprising:- processing circuitry configured to provide user data; and- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. The communication system of the pervious embodiment further including the base station. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a hostapplication, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, providing user data; and- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. 0. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. 1. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application. 2. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments. 3. A communication system including a host computer comprising:- processing circuitry configured to provide user data; and- a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),- wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments. 4. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.25. The communication system of the previous 2 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and- the UE’s processing circuitry is configured to execute a client application associated with the host application.26. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, providing user data; and- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.27. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.28. A communication system including a host computer comprising:- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,- wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.29. The communication system of the previous embodiment, further including the UE.30. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.31. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application; and- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data. The communication system of the previous 4 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station. The method of the previous 2 embodiments, further comprising:- at the UE, executing a client application, thereby providing the user data to be transmitted; and- at the host computer, executing a host application associated with the client application. The method of the previous 3 embodiments, further comprising:- at the UE, executing a client application; and- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,- wherein the user data to be transmitted is provided by the client application inresponse to the input data.37. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.38. The communication system of the previous embodiment further including the base station.39. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.40. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application;- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.41. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.42. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.43. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Claims

CLAIMS:

1. A method performed by a wireless device operating in dual connectivity with a master node (MN) and a secondary node (SN), the method comprising: receiving (912) a successful PSCell report (SPR) configuration from the SN; receiving (914) from the MN an indication that a PSCell change is a SN-initiated PSCell change; and applying (916) the SPR configuration for the PSCell change to determining logging of the SPR.

2. The method of claim 1, the method further comprising: transmitting (918) the SPR to a network node, the SPR comprising an indication that the PSCell change was SN-initiated.

3. The method of any one of claims 1-2, wherein the SPR configuration comprises one or more thresholds for triggering SPR generation.

4. A wireless device (200) capable of operating in dual connectivity with a master node (MN) (300) and a secondary node (SN) (300), the wireless device comprising processing circuitry (202) operable to: receive a successful PSCell report (SPR) configuration from the SN; receive from the MN an indication that a PSCell change is a SN-initiated PSCell change; and apply the SPR configuration for the PSCell change to determining logging of the SPR.

5. The wireless device of claim 4, the processing circuitry further operable to: transmit the SPR to a network node, the SPR comprising an indication that the PSCell change was SN-initiated.

6. The wireless device of any one of claims 4-5, wherein the SPR configuration comprises one or more thresholds for triggering SPR generation.

7. A method performed by a network node operating as a secondary node (SN) for a wireless device operating in dual connectivity with a master node (MN) and the SN, the method comprising: configuring (1012) the wireless device with a successful PSCell report (SPR) configuration; and transmitting (1014) to the MN an indication that the wireless device is configured with the SPR configuration.

8. The method of claim 7, wherein the indication transmitted to the MN comprises an indication that a PSCell change is needed.

9. The method of claim 8, wherein the indication comprises an information element in a S-Node Change Required indicating that a PSCell change is needed.

10. The method of claim 7, wherein the indication transmitted to the MN comprises a CG- Config message contained in a S-Node Change Required message or S-Node Modification.

11. The method of claim 7, wherein the indication transmitted to the MN comprises an indication that the PSCell change is SN-initiated.

12. The method of any one of claims 7-11, wherein the SPR configuration comprises one or more thresholds for triggering SPR generation.

13. A network node (300) capable of operating as a secondary node (SN) for a wireless device (200) operating in dual connectivity with a master node (MN) (300) and the SN, the network node comprising processing circuitry (302) operable to: configure the wireless device with a successful PSCell report (SPR) configuration; and transmit to the MN an indication that the wireless device is configured with the SPR configuration.

14. The network node of claim 13, wherein the indication transmitted to the MN comprises an indication that a PSCell change is needed.

15. The network node of claim 14, wherein the indication comprises an information element in a S-Node Change Required indicating that a PSCell change is needed.

16. The network node of claim 13, wherein the indication transmitted to the MN comprises a CG-Config message contained in a S-Node Change Required message or S-Node Modification.

17. The network node of claim 13, wherein the indication transmitted to the MN comprises an indication that the PSCell change is SN-initiated.

18. The network node of any one of claims 13-17, wherein the SPR configuration comprises one or more thresholds for triggering SPR generation.

19. A method performed by a network node operating as a master node (MN) for a wireless device operating in dual connectivity with a secondary node (SN) and the MN, the method comprising: receiving (1112) an indication from the SN that the wireless device is configured with a successful PSCell report (SPR) configuration; and transmitting (1114) an indication to the wireless device that a PSCell change is a SN- initiated PSCell change.

20. The method of claim 19, wherein the indication received from the SN comprises an indication that a PSCell change is needed.

21. The method of claim 20, wherein the indication comprises an information element in a S-Node Change Required indicating that a PSCell change is needed.

22. The method of claim 19, wherein the indication received from the SN comprises a CG- Config message contained in a S-Node Change Required message or S-Node Modification.

23. The method of claim 19, wherein the indication received from the SN comprises an indication that the PSCell change is SN-initiated.

24. The method of any one of claims 19-23, wherein the SPR configuration comprises one or more thresholds for triggering SPR generation.

25. A network node (300) capable of operating as a master node (MN) for a wireless device (200) operating in dual connectivity with a secondary node (SN) (300) and the MN, the network node comprising processing circuitry (302) operable to: receive an indication from the SN that the wireless device is configured with a successful PSCell report (SPR) configuration; and transmit an indication to the wireless device that a PSCell change is a SN-initiated PSCell change.

26. The network node of claim 25, wherein the indication received from the SN comprises an indication that a PSCell change is needed.

27. The network node of claim 26, wherein the indication comprises an information element in a S-Node Change Required indicating that a PSCell change is needed.

28. The network node of claim 25, wherein the indication received from the SN comprises a CG-Config message contained in a S-Node Change Required message or S-Node Modification.

29. The network node of claim 25, wherein the indication received from the SN comprises an indication that the PSCell change is SN-initiated.

30. The network node of any one of claims 25-29, wherein the SPR configuration comprises one or more thresholds for triggering SPR generation.

Images