DEACTIVATION OF CELLS IN MULTI-TRP SCENARIOS

RELATED APPLICATION

[0001] This application claims the benefits of priority of U.S. Provisional Patent Application No. 63/227,050, entitled “handling of timer-based deactivation of cells in multi-TRP scenarios” and filed at the United States Patent and Trademark Office on July 29, 2021, the content of which is incorporated herein by reference.

TECHNICAL FIELD

[0002] This application generally relates to wireless communication systems, and particularly, to methods and nodes for handling of timer-based deactivation of cells in multi-Transmission Reception Point (mTRP) scenarios.

BACKGROUND

[0003] Carrier aggregation

[0004] Carrier aggregation is a concept where the User Equipment (UE) can operate using multiple carriers (sometimes referred to as cells) that the network has available. With a greater number of carriers, more spectrum can be used by the UE and hence higher throughput can be achieved.

[0005] A UE may be configured with a subset of the cells offered by the network and the number of aggregated cells configured for one UE can change dynamically through time based on, for example, terminal traffic demand, type of service used by the terminal/UE, system load, etc. A cell for which a terminal is configured to use is referred to as a "serving cell" for that terminal. A UE has one primary serving cell (called PCell) and zero or more secondary serving cells (SCells). The term “serving cell” includes both the PCell and SCells. Which cell is a terminal’s PCell is UE specific. The PCell is considered more important and for example some control signaling is handled via the PCell.

[0006] In addition to the concept of "configuration" of cells, the concept of "activation" has been introduced for SCells (not for the PCell). Cells may be configured (or deconfigured) using Radio Resource Control (RRC) signaling, which can be slow, and SCells can be activated (or deactivated) using a Medium Access Control (MAC) control element (CE), which is faster. Since the activation process is based on MAC control elements, an activation/de-activation process can quickly adjust the number of activated cells to match the number that is required to fulfill data rate needed at any given time. Activation therefore provides the possibility to keep multiple cells configured for activation on an as-needed basis. [0007] An SCell can be activated/de-activated via:

[0008] - SCell Activation/Deactivation MAC CE;

[0009] - sCellDeactivationTimer timer; and

[0010] - RRC (re-)configuration (sCellState).

[0011] The sCellDeactivaitonTimer is a timer which, upon expiry, triggers the UE to deactivate the SCell. There is one such timer per SCell. The timer is started/restarted when the UE is using the cell, e.g. when the UE is scheduled on the SCell, etc.

[0012] Inter-cell mTRP enhancements in Release 17 (Rel-17)

[0013] In Rel-17, third Generation partnership project (3gpp) is going to standardize a mTRP enhancement scheme in which the UE can receive/transmit data from/to a TRP that belongs to a different Physical Cell Identity (PCI) in the serving frequency than its serving PCI. The UE is expected to be in the coverage of the serving PCI, while being configured to receive and transmit data from and to the TRP belonging to a different PCI. This is explicitly captured in the following objective of the Work item Description (WID) (RP-193133).

[0014] 1. Enhancement on the support for multi -TRP deployment, targeting both Frequency

Range 1 (FR1) and Frequency Range 2 (FR2): a. Identify and specify features to improve reliability and robustness for channels other than Physical Downlink Shared Channel (PDSCH), that is, Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), and Physical Uplink Control Channel (PUCCH), using multi -TRP and/or multi -panel, with Rel-16 reliability features as the baseline.

[0015] Associated to this, the following agreements were made in RAN2#114 meeting. [0016] RAN2 confirms the simplified procedures on the inter-cell multi-TRP-like model as a baseline RAN2 understanding:

[0017] Scenario 1 : Inter-cell multi-TRP-like model

[0018] 1. A UE receives from the serving cell, a configuration of Synchronization

Signal Blocks (SSBs) of the TRP with different PCI for beam measurement, and configurations needed to use radio resources for data transmission/reception including resources for different PCI. [0019] 2. The UE performs beam measurement for the TRP with different PCI and report it to the serving cell.

[0020] 3. Based on the above reports, Transmission Configuration Indicator (TCI) state(s) associated to the TRP with different PCI is activated from the serving cell (e.g. by Layer 1/Layer 2 (L1/L2) signaling). [0021] 4. The UE receives and transmits using UE-dedicated channel on TRP with different PCE

[0022] 5. The UE should be in coverage of a serving cell always, also for multi -TRP case, e.g. the UE should use common channels, Broadcast Control Channel (BCCH), Paging Channel (PCH), etc., from the serving cell (as in legacy).

[0023] In current systems, a UE can be configured with multiple SCells, where each of these SCell is on a different frequency. Each of these SCell is associated to a sCellDeactivationTimer. The UE waits for the duration of this timer and if the UE does not communicate (data transmission in uplink (UL) or downlink (DL)) using this SCell for the duration of this timer, then the UE deactivates this SCell.

SUMMARY

[0024] There currently exist certain challenge(s). In multi-TRP communication, the UE may be configured with a serving cell (i.e. SCell) and an associated non-serving cell on the same serving frequency. The current MAC specification describes sCellDeactivationTimers. These timers will deactivate an SCell if the UE is not communicating on the SCell for a certain time.

[0025] In multi-TRP scenarios, both these cells (SCell and associated non-serving cell) can be used to communicate with the UE. However, the network might use only the non-serving cell on the serving frequency to communicate with the UE, i.e. it does not use the serving cell. With the existing definition of sCellDeactivationTimer, that will trigger the UE to deactivate the serving cell (SCell) on the serving frequency if the serving cell is not used to communicate with the UE during the duration of the timer (sCellDeactivationTimer). Such a scenario will reduce radio resources that the UE can use, which may not be the preferred behavior.

[0026] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0027] In one example, the UE can (re)start the timer (e.g. sCellDeactivationTimer) for a serving cell when communicating on the associated non-serving cell on the same frequency. [0028] In one example, the UE can maintain one timer (e.g. sCellDeactivationTimer) for the serving cell and one timer (e.g. sCellDeactivationTimer, which may, in case this embodiment is adopted into specifications, be given a different name, while having a similar behaviour) for the non-serving cell on the same frequency. These timers can be independently started and trigger deactivation of their respective cells. Alternatively, these timers can be related and/or coordinated in some ways. For example, the timer associated to the non-serving cell can be started and trigger deactivation of the non-serving cell based on the communication on the non-serving cell, whereas the timer associated to the serving cell can be started only after the expiration of the timer associated to the non-serving cell and if there is no communication on the serving cell.

[0029] In one example, the network node communicates with the UE on the serving cell for the purpose of avoiding that the timer, e.g. sCellDeactivationTimer, expires. This example is applicable only when the UE is being communicated using the non-serving cell and the network does some communications using the serving cell so that the timer associated to the serving cell does not expire.

[0030] According to an aspect, there is provided a method in a UE operating in an inter-cell mTRP environment. The method may comprise: determining that a communication between the UE and a network node is related to a non-serving cell configured for the UE; determining a serving cell which is associated with the non-serving cell; and starting or restarting a timer associated with the serving cell.

[0031] In some examples, the serving cell may be one of a Primary cell (PCell), a Primary

Secondary Cell Group (SCG) Cell (PScell) and a Secondary Cell (Scell).

[0032] In some examples, the non-serving cell may be a cell different from the serving cell but using the same frequency as the serving cell.

[0033] In some examples, the timer may be a sCellDeactivationTimer.

[0034] In some examples, determining that a communication between the UE and a network node is related to a non-serving cell may comprise determining that transmissions are performed on a channel associated with the non-serving cell.

[0035] In some examples, determining that a communication between the UE and a network node is related to a non-serving cell may comprise determining transmissions that are performed for the non-serving cell.

[0036] In some examples, the timer may be also associated with the non-serving cell.

[0037] In some examples, the method may further comprise deactivating both the serving cell and the associated non-serving cell after expiry of the timer.

[0038] In some examples, the timer may have a first duration or a second duration.

[0039] In some examples, the first duration may be different from the second duration when the timer is triggered for a communication between the UE and the network node related to the serving cell.

[0040] According to an aspect, there is provided a wireless device or a UE for performing the above method.

[0041] According to an aspect, there is provided a method in a network node. The method may comprise: determining to communicate with a UE using a serving cell, even though data transmissions are related to a non-serving cell configured for the UE; and sending communications to the UE on the serving cell, within a duration provided by a timer associated with the serving cell.

[0042] In some examples, sending communications to the UE may comprise sending dummy data to the UE.

[0043] In some examples, the timer may be a sCelltheDeactivationTimer.

[0044] According to an aspect, a network node is provided for performing the above method (in the network node).

[0045] Certain embodiments may provide one or more of the following technical advantage(s).

[0046] The sCellDeactivationTimer (or similar timers) will be kept running (i.e. it will not expire) even if the UE is communicating with the network node only using the associated non serving cell.

[0047] Alternatively, the UE would not trigger deactivation of the non-serving cell in response to the expiry of the timer (e.g. sCellDeactivationTimer) of the serving cell.

[0048] Alternatively, the network node ensures that the timer (e.g. sCellDeactivationTimer) for the serving cell does not expire by scheduling the UE often enough to avoid expiry of the timer. BRIEF DESCRIPPTION OF THE DRAWINGS

[0049] Exemplary embodiments will be described in more detail with reference to the following figures, in which:

[0050] Fig. 1 illustrates a signal diagram between a UE and a network node, according to an embodiment.

[0051] Fig. 2 illustrates a signal diagram between a UE and a network node, according to an embodiment.

[0052] Fig. 3 illustrates a signal diagram between a UE and a network node, according to an embodiment.

[0053] Fig. 4 illustrates a signal diagram between a UE and a network node, according to an embodiment.

[0054] Fig. 5 shows an example of a communication system, according to an embodiment.

[0055] Fig. 6 shows a schematic diagram of a UE, according to an embodiment.

[0056] Fig. 7 shows a schematic diagram of a network node, according to an embodiment.

[0057] Fig. 8 illustrates a block diagram of a host.

[0058] Fig. 9 illustrates a block diagram illustrating a virtualization environment.

[0059] Fig. 10 shows a communication diagram of a host. DETAILED DESCRIPTION

[0060] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0061] Before going into detail, it should be noted that, in the context of inter-cell mTRP, a SCell is considered to be a serving cell on a serving frequency, whereas an associated non-serving cell is a different cell on the same serving frequency.

[0062] In this disclosure, it will be described how the UE can handle a timer, such as the sCellDeactivationTimer, in multi -TRP scenarios. However, the embodiments herein describing handling of this timer can be applied to other similar timers as well.

[0063] Example 1: Starting of a timer (e.g. sCellDeactivationTimer) for a serving cell upon communicating on a non-serving cell

[0064] This example is shown in Fig. 1, as a method 10, for handling communications in a mTRP scenario between a UE and a network node. In this method, the UE will:

[0065] In step 12: determine that a communication between the UE and the network node is related to a non-serving cell (or is performed on or for a non-serving cell).

[0066] In step 14: determine a serving cell which is associated with the non-serving cell.

[0067] In step 16: start or restart a timer associated with the serving cell. [0068] It should be noted that, in step 12, it says that the communications are performed "on or for" a non-serving cell. The communication "on" means that transmissions are performed on a channel associated with the non-serving cell. When a communication is done "for" a non-serving cell can, for example, mean that the non-serving cell is cross-carrier scheduled. Cross-carrier scheduling means that a cell (or "carrier") is scheduled by another cell. So, uplink grants and downlink assignments are not sent on the cell itself (i.e. the "scheduled" cell), but rather they are sent on another cell (i.e. a "scheduling" cell).

[0069] The serving cell may be a PCell, a Primary SCG Cell (PSCell) or a Scell, for example. [0070] The timer may for example be a timer used to deactivate the serving cell, such as the sCellDeactivationTimer. Also, the timer may be seen as being associated to both the serving cell and the non-serving cell.

[0071] The communications performed between the UE and the network node may comprise one or more of:

[0072] - PDCCH indicating an uplink grant or downlink assignment; a. Note: PDCCH may be sent on the same or different cell. As explained above, for cross-carrier scheduling, the PDCCH is sent on a different cell than the cell which uplink grant or downlink assignment is valid for.

[0073] - a MAC Protocol Data Unit (PDU) being transmitted; [0074] - a MAC PDU being received.

[0075] If the timer expires, the UE may deactivate both the serving cell and the associated non-serving cell. It should be noted that the term “expire” means when the whole duration of the timer has passed.

[0076] When the UE starts the sCellDeactivationTimer for legacy purposes, the time duration provided by the timer is configurable using the RRC field with the same name. However, the time duration applied by the UE is common/the same for all SCells of a UE's MAC entity, meaning that all SCells use the same timer duration.

[0077] In another example, the timer can have different timer durations. More specifically, the timer can be provided with different timer values and the UE can apply a specific timer value depending on whether the communication happens via the serving cell or the associated non serving cell.

[0078] A method 20 for handling communications in a mTRP scenario between a UE and a network node, using different durations for a timer is shown in Fig. 2. In this method, the UE can: [0079] In step 22: determine whether a communication between the UE and a network node is related to a serving cell or a non-serving cell configured for the UE;

[0080] In step 24, in response to determining that the communication is related to the non serving cell, apply a first duration to the timer, when starting the timer;

[0081] In step 26, in response to determining that the communication is related to the serving cell, apply a second duration to the timer, when starting the timer. [0082] The first and the second timer durations may be configurable. The first timer duration may be different than the second timer duration. Optionally, the first timer duration and the second timer duration may be the same. The timer can be the sCellDeactivationTimer or a similar timer. [0083] It should be noted that communications between the UE and a network node that are related to a serving cell comprise communications performed on or for the serving cell. Similarly, communications related to a non-serving comprise communications performed on or for an associated non-serving cell.

[0084] Example 2: A separate timer (e.g. sCellDeactivationTimer) for a non-serving cell [0085] As described above, the UE may have a serving cell, and a non-serving cell associated to the serving cell. There is a relation between these two cells. In the example above (example 1) the UE has only a timer which is applied to both cells, as such, the UE needs to restart the timer for the serving cell, when communicating over the non-serving cell.

[0086] In this example, the UE can have a first timer for (or associated with) the serving cell and a second timer for (or associated with) the non-serving cell. [0087] The first and the second timers may be started independently: the first timer may trigger deactivation of the serving cell, but not the non-serving cell. The second timer may trigger deactivation of the non-serving cell, but not the serving cell. In another example, the first timer can trigger deactivation of both the serving cell and the non-serving cell. In another example, the first and second timers can be related and/or coordinated in some ways (i.e. they can be started conditionally, depending on the first timer or second timer). For example, the second timer associated to the non-serving cell can be started and trigger deactivation of the non-serving cell based on the communication on the non-serving cell, whereas the first timer associated to the serving cell can be started only after the expiration of the second timer associated to the non serving cell and if there is no communication on the serving cell. [0088] Fig. 3 illustrates a method 30 for handling communications between a UE and a network node. In this method, the UE will:

[0089] In step 32: determine whether the UE is scheduled on a serving cell or on an associated non-serving cell (e.g. anon-serving cell configured for the UE);

[0090] In step 34, in response to determining that the UE is scheduled on the serving cell, the UE can start a timer associated with the serving cell;

[0091] In step 36: in response to determining that the UE is scheduled on the non-serving cell, the UE can start a timer associated with the non-serving cell.

[0092] For the case when the serving cell is activated, the UE may start both the timers, for example. [0093] Example implementations in the standard specifications

[0094] Below are example implementations of some embodiments of this disclosure. An implementation of example 1 is shown below. For example, an excerpt from the 3GPP 38.321 v.16.4.0 specification is shown with changes, where the changes compared to the legacy specification are shown with underlined words. 5.9 Activation/Deactivation of SCells

If the MAC entity is configured with one or more SCells, the network may activate and deactivate the configured SCells. Upon configuration of an SCell, the SCell is deactivated unless the parameter sCellState is set to activated for the SCell by upper layers.

The configured SCell(s) is activated and deactivated hv: - receiving the SCell Activation/Deactivation MAC CE described in clause 6.1.3.10;

- configuring sCellDeactivationTimer timer per configured SCell (except the SCell configured with PUCCH, if any): the associated SCell is deactivated upon its expiry;

- configuring sCellState per configured SCell: if configured, the associated SCell is activated upon SCell configuration.

The MAC entity shall for each configured SCell:

1> if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or

1> if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or

1> if PDCCH on the non-serving cell associated with the activated SCell indicates an uplink grant or downlink assignment: or

1> if PDCCH on the cell scheduling the activated SCell indicates an unlink grant or a downlink assignment for the activated SCell: or

1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or

1> if a MAC PDU is received in a configured downlink assignment:

2> restart the sCellDeactivationTimer associated with the SCell.

1> if the SCell is deactivated:

2> not transmit SRS on the SCell;

2> not report CSI for the SCell;

2> not transmit on UL-SCH on the SCell;

2> not transmit on RACH on the SCell;

2> not monitor the PDCCH on the SCell;

2> not monitor the PDCCH for the SCell;

2> not transmit PUCCH on the SCell.

HARQ feedback for the MAC PDU containing SCell Activation/Deactivation MAC CE shall not be impacted by PCell, PSCell and PUCCH SCell interruptions due to SCell activation/deactivation in TS 38.133 [11]

When SCell is deactivated, the ongoing Random Access procedure on the SCell, if any, is aborted.

[0095] Below is an example implementation of example 2, where the changes introduced in example 2 are underlined.

5.9 Activation/Deactivation of SCells

[ ...]

The MAC entity shall for each configured SCell and for each activated non-serving cell:

1> if an SCell is configured with sCellState set to activated upon SCell configuration, or an SCell Activation/Deactivation MAC CE is received activating the SCell: 2> if the SCell was deactivated prior to receiving this SCell Activation/Deactivation MAC CE; or

2> if the SCell is configured with sCellState set to activated upon SCell configuration:

3> if firstActiveDownlinkBWP-Id is not set to dormant BWP:

4> activate the SCell according to the timing defined in TS 38.213 [6] for MAC CE activation and according to the timing defined in TS 38.133 [11] for direct SCell activation; i.e. apply normal SCell operation including:

5> SRS transmissions on the SCell;

5> CSI reporting for the SCell;

5> PDCCH monitoring on the SCell;

5> PDCCH monitoring for the SCell;

5> PUCCH transmissions on the SCell, if configured.

3> else (i.e. firstActiveDownlinkBWP-Id is set to dormant BWP):

4> stop the bwp-InactivityTimer of this Serving Cell, if running.

3> activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActive UplinkB WP-Id respectively .

2> start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213 [6] for MAC CE activation and according to the timing defined inTS 38.133 [11] for direct SCell activation;

2> if the active DL BWP is not the dormant BWP:

3> (re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this SCell according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2.2;

3> trigger PHR according to clause 5.4.6. > else if an SCell Activation/Deactivation MAC CE is received deactivating the SCell; or > if the sCellDeactivationTimer associated with the activated SCell expires:

2> deactivate the SCell according to the timing defined in TS 38.213 [6];

2> stop the sCellDeactivationTimer associated with the SCell;

2> stop the bwp-InactivityTimer associated with the SCell;

2> deactivate any active BWP associated with the SCell;

2> clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell respectively;

2> clear any PUSCH resource for semi-persistent CSI reporting associated with the SCell;

2> suspend any configured uplink grant Type 1 associated with the SCell;

2> flush all HARQ buffers associated with the SCell;

2> cancel, if any, triggered consistent LBT failure for the SCell. > if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or > if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or 1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or

1> if a MAC PDU is received in a configured downlink assignment:

2> restart the sCellDeactivationTimer associated with the SCell. 1> if the SCell is deactivated:

2> not transmit SRS on the SCell;

2> not report CSI for the SCell;

2> not transmit on UL-SCH on the SCell;

2> not transmit on RACH on the SCell; 2> not monitor the PDCCH on the SCell;

2> not monitor the PDCCH for the SCell;

2> not transmit PUCCH on the SCell.

HARQ feedback for the MAC PDU containing SCell Activation/Deactivation MAC CE shall not be impacted by PCell, PSCell and PUCCH SCell interruptions due to SCell activation/deactivation in TS 38.133 [11] When SCell is deactivated, the ongoing Random Access procedure on the SCell, if any, is aborted.

[0096] It should be noted that, in the added text above, the UE considers "each activated non serving cell". However, in one example, the UE can consider each "configured" non-serving cell.

[0097] Network implementation [0098] In one embodiment, a network node which can communicate with the UE on a serving cell and an associated non-serving cell, will communicate with the UE on the serving cell for the sake of keeping/preventing a timer, e.g. sCellDeactivationTimer, to expire for the serving cell. Even if the network node would not for other reasons need to communicate with the UE on the serving cell, the network node would anyway communicate with the UE. For example, the network node could be scheduling the UE on the serving cell with some dummy data or temporarily scheduling the UE with data on the serving cell that otherwise would have been scheduled via non serving cell.

[0099] Fig. 4 illustrates a method 40 for handling communications between a UE and a network node. In this method, the network node will: [0100] In step 42: determine to communicate with the UE using the serving cell, even though data transmissions are related to the non-serving cell; and

[0101] In step 44: send the communications to the UE on the serving cell, within the duration provided by the timer associated with the serving cell.

[0102] The timer can be sCelltheDeactivationTimer or any similar timers. [0103] Fig. 5 shows an example of a communication system 500 in accordance with some embodiments.

[0104] In the example, the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes, such as network nodes 510a and 510b (one or more of which may be generally referred to as network nodes 510), or any other similar 3GPP access node or non- 3GPP access point. The network nodes 510 facilitate direct or indirect connection of UE, such as by connecting UEs 512a, 512b, 512c, and 512d (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.

[0105] 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 500 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 500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

[0106] The UEs 512 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 510 and other communication devices. Similarly, the network nodes 510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 512 and/or with other network nodes or equipment in the telecommunication network 502 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 502.

[0107] In the depicted example, the core network 506 connects the network nodes 510 to one or more hosts, such as host 516. 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 506 includes one more core network nodes (e.g., core network node 508) 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 508. 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).

[0108] The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and/or the telecommunication network 502, and may be operated by the service provider or on behalf of the service provider. The host 516 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. [0109] As a whole, the communication system 500 of Fig. 5 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); Fong Term Evolution (FTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WEAN) 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.

[0110] In some examples, the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunications network 502 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)/Massive IoT services to yet further UEs.

[0111] In some examples, the UEs 512 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 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. 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 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).

[0112] In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512c and/or 512d) and network nodes (e.g., network node 510b). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 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 510, or by executable code, script, process, or other instructions in the hub 514. As another example, the hub 514 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 514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.

[0113] The hub 514 may have a constant/persistent or intermittent connection to the network node 510b. The hub 514 may also allow for a different communication scheme and/or schedule between the hub 514 and UEs (e.g., UE 512c and/or 512d), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and/or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to an M2M service provider over the access network 504 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 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 510b. In other embodiments, the hub 514 may be a non- dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 510b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0114] Fig. 6 shows a UE 600, which is the same as the UE 512, 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, including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

[0115] 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). Alternatively, a UE may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0116] The UE 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a power source 608, a memory 610, a communication interface 612, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 6. The level of integration between the components may 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. [0117] The processing circuitry 602 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 610. The processing circuitry 602 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 602 may include multiple central processing units (CPUs). The processing circuitry 602 is configured to perform any of the methods 10, 20 and 30 of Figs. 1, 2 and 3 respectively.

[0118] In the example, the input/output interface 606 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 600. 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, atrackpad, 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.

[0119] In some embodiments, the power source 608 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 608 may further include power circuitry for delivering power from the power source 608 itself, and/or an external power source, to the various parts of the UE 600 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 608. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 608 to make the power suitable for the respective components of the UE 600 to which power is supplied.

[0120] The memory 610 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 610 includes one or more application programs 614, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 616. The memory 610 may store, for use by the UE 600, any of a variety of various operating systems or combinations of operating systems. [0121] The memory 610 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 610 may allow the UE 600 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 610, which may be or comprise a device-readable storage medium.

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

[0123] In the illustrated embodiment, communication functions of the communication interface 612 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.

[0124] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 612, 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). [0125] 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.

[0126] A UE, when in the form of an IoT 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 IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, 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 IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 600 shown in Fig. 6.

[0127] As yet another specific example, in an IoT 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.

[0128] 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.

[0129] Fig. 7 shows a network node 700, which is the same as the network node 510, 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, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs (NBs), evolved NBs (eNBs) and NRNBs (gNBs)).

[0130] 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).

[0131] Other examples of network nodes include mTRP 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).

[0132] The network node 700 includes a processing circuitry 702, a memory 704, a communication interface 706, and a power source 708. The network node 700 may be composed of multiple physically separate components (e.g., a NB 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 700 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 NBs. In such a scenario, each unique NB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 700 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 704 for different RATs) and some components may be reused (e.g., a same antenna 710 may be shared by different RATs). The network node 700 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 700, 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 700.

[0133] The processing circuitry 702 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 700 components, such as the memory 704, to provide network node 700 functionality. The processing circuitry 702 may be configured to perform method 40 of Fig. 4, for example.

[0134] In some embodiments, the processing circuitry 702 includes a system on a chip (SOC). In some embodiments, the processing circuitry 702 includes one or more of radio frequency (RF) transceiver circuitry 712 and baseband processing circuitry 714. In some embodiments, the radio frequency (RF) transceiver circuitry 712 and the baseband processing circuitry 714 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 712 and baseband processing circuitry 714 may be on the same chip or set of chips, boards, or units.

[0135] The memory 704 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, RAM, 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 702. The memory 704 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 702 and utilized by the network node 700. The memory 704 may be used to store any calculations made by the processing circuitry 702 and/or any data received via the communication interface 706. In some embodiments, the processing circuitry 702 and memory 704 is integrated.

[0136] The communication interface 706 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 706 comprises port(s)/terminal(s) 716 to send and receive data, for example to and from a network over a wired connection. The communication interface 706 also includes radio front-end circuitry 718 that may be coupled to, or in certain embodiments a part of, the antenna 710. Radio front-end circuitry 718 comprises filters 720 and amplifiers 722. The radio front-end circuitry 718 may be connected to an antenna 710 and processing circuitry 702. The radio front-end circuitry may be configured to condition signals communicated between antenna 710 and processing circuitry 702. The radio front-end circuitry 718 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 718 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 720 and/or amplifiers 722. The radio signal may then be transmitted via the antenna 710. Similarly, when receiving data, the antenna 710 may collect radio signals which are then converted into digital data by the radio front-end circuitry 718. The digital data may be passed to the processing circuitry 702. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

[0137] In certain alternative embodiments, the network node 700 does not include separate radio front-end circuitry 718, instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712, as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).

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

[0139] The antenna 710, communication interface 706, and/or the processing circuitry 702 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 710, the communication interface 706, and/or the processing circuitry 702 may be configured 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. [0140] The power source 708 provides power to the various components of network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein. For example, the network node 700 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 708. As one example, the power source 708 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. [0141] Embodiments of the network node 700 may include additional components beyond those shown in Fig. 7 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 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700.

[0142] Fig. 8 is a block diagram of a host 800, which may be an embodiment of the host 516 of Fig. 5, in accordance with various aspects described herein. As used herein, the host 800 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 800 may provide one or more services to one or more UEs.

[0143] The host 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and a memory 812. 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 as Figs. 6 and 7, such that the descriptions thereof are generally applicable to the corresponding components of host 800.

[0144] The memory 812 may include one or more computer programs including one or more host application programs 814 and data 816, which may include user data, e.g., data generated by a UE for the host 800 or data generated by the host 800 for a UE. Embodiments of the host 800 may utilize only a subset or all of the components shown. The host application programs 814 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 814 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 800 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 814 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.

[0145] Fig. 9 is a block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments (in the UE and network node) 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 900 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.

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

[0147] Hardware 904 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 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 908a and 908b (one or more of which may be generally referred to as VMs 908), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.

[0148] The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, 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.

[0149] In the context of NFV, a VM 908 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 908, and that part of hardware 904 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 908 on top of the hardware 904 and corresponds to the application 902.

[0150] Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 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 910, which, among others, oversees lifecycle management of applications 902. In some embodiments, hardware 904 is coupled to one or more radio units that each include one or more transmitters 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 912 which may alternatively be used for communication between hardware nodes and radio units.

[0151] Fig. 10 shows a communication diagram of a host 1002, such as the host 800 or 516, communicating via a network node 1004 with a UE 1006 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 512a of Fig. 5 and/or UE 600 of Fig. 6), network node (such as network node 510a of Fig. 5 and/or network node 700 of Fig. 7), and host (such as host 516 of Fig. 5 and/or host 800 of Fig. 8) discussed in the preceding paragraphs will now be described with reference to Fig. 10.

[0152] Like host 800, embodiments of host 1002 include hardware, such as a communication interface, processing circuitry, and memory. The host 1002 also includes software, which is stored in or accessible by the host 1002 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 1006 connecting via an over-the-top (OTT) connection 1050 extending between the UE 1006 and host 1002. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1050.

[0153] The network node 1004 includes hardware enabling it to communicate with the host 1002 and UE 1006. The connection 1060 may be direct or pass through a core network (like core network 506 of Fig. 5) 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.

[0154] The UE 1006 includes hardware and software, which is stored in or accessible by UE 1006 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 1006 with the support of the host 1002. In the host 1002, an executing host application may communicate with the executing client application via the OTT connection 1050 terminating at the UE 1006 and host 1002. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1050 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 1050.

[0155] The OTT connection 1050 may extend via a connection 1060 between the host 1002 and the network node 1004 and via a wireless connection 1070 between the network node 1004 and the UE 1006 to provide the connection between the host 1002 and the UE 1006. The connection 1060 and wireless connection 1070, over which the OTT connection 1050 may be provided, have been drawn abstractly to illustrate the communication between the host 1002 and the UE 1006 via the network node 1004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0156] As an example of transmitting data via the OTT connection 1050, in step 1008, the host 1002 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 1006. In other embodiments, the user data is associated with a UE 1006 that shares data with the host 1002 without explicit human interaction. In step 1010, the host 1002 initiates a transmission carrying the user data towards the UE 1006. The host 1002 may initiate the transmission responsive to a request transmitted by the UE 1006. The request may be caused by human interaction with the UE 1006 or by operation of the client application executing on the UE 1006. The transmission may pass via the network node 1004, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1012, the network node 1004 transmits to the UE 1006 the user data that was carried in the transmission that the host 1002 initiated, according to the teachings of this disclosure. In step 1014, the UE 1006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1006 associated with the host application executed by the host 1002.

[0157] In some examples, the UE 1006 executes a client application which provides user data to the host 1002. The user data may be provided in reaction or response to the data received from the host 1002. Accordingly, in step 1016, the UE 1006 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 1006. Regardless of the specific manner in which the user data was provided, the UE 1006 initiates, in step 1018, transmission of the user data towards the host 1002 via the network node 1004. In step 1020, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1004 receives user data from the UE 1006 and initiates transmission of the received user data towards the host 1002. In step 1022, the host 1002 receives the user data carried in the transmission initiated by the UE 1006.

[0158] One or more of the various embodiments improve the performance of OTT services provided to the UE 1006 using the OTT connection 1050, in which the wireless connection 1070 forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, and thereby provide benefits such as e.g., reduced user waiting time, better responsiveness.

[0159] In an example scenario, factory status information may be collected and analyzed by the host 1002. As another example, the host 1002 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1002 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1002 may store surveillance video uploaded by a UE. As another example, the host 1002 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 1002 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.

[0160] 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 1050 between the host 1002 and UE 1006, 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 1002 and/or UE 1006. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1050 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 1050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1004. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1002. The measurements may be implemented in that software causes messages to be transmitted, e.g. empty or ‘dummy’ messages, using the OTT connection 1050 while monitoring propagation times, errors, etc.

[0161] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0162] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

[0163] The above-described embodiments are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the description, which is defined solely by the appended claims.