END MARKER FOR SDT

Related Applications

[0001] This application claims the benefit of provisional patent application serial number 63/186,074, filed May 8, 2021, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

[0002] The present disclosure is directed to systems and methods of using a logical channel identification (LCID), for example, for an uplink shared channel (UL-SCH), as an end marker for small data transmissions (SDT).

Background

New Radio (NR) Small Data Transmissions (SDT) in Inactive State [0003] A new Work Item (WI) RP-200954 ‘New Work Item on NR small data transmissions in INACTIVE state’ has been approved in 3rd Generation Partnership Project (3GPP) with the focus of optimizing the transmission for small data payloads by reducing the signaling overhead. The WI contains the following relevant objectives:

***** START OF EXCERPT FROM WI RP-200954 *****

This work item enables small data transmission in RRC_IN ACTIVE state as follows:

For the RRC_IN ACTIVE state: o UL small data transmissions for RACH-based schemes (i.e. 2-step and 4-step RACH):

• General procedure to enable UP data transmission for small data packets from INACTIVE state (e.g. using MSGA or MSG3) [RAN2]

• Enable flexible payload sizes larger than the Rel-16 CCCH message size that is possible currently for INACTIVE state for MSGA and MSG3 to support UP data transmission in UL (actual payload size can be up to network configuration) [RAN2]

• Context fetch and data forwarding (with and without anchor relocation) in INACTIVE state for RACH-based solutions [RAN2, RAN3]

Note 1 : The security aspects of the above solutions should be checked with S A3 o Transmission of UL data on pre-configured PUSCH resources (i.e. reusing the configured grant type 1) - when TA is valid

• General procedure for small data transmission over configured grant type 1 resources from INACTIVE state [RAN2] • Configuration of the configured grant typel resources for small data transmission in UL for INACTIVE state [RAN2]

***** END OF EXCERPT FROM WI RP-200954 *****

[0004] For Narrow Band Internet of Things (NB-IoT) and Long-Term Evolution for Machines (LTE-M) similar signaling optimizations for small data have been introduced through Rel-15 Early Data Transmission (EDT) and Rel-16 Preconfigured Uplink Resources (PUR). Somewhat similar solutions could be expected for NR with the difference that the Rel-17 NR Small Data is only to be supported for Radio Resource Control (RRC) INACTIVE state, includes also 2-step Random Access Channel (RACH) based small data, and that it should also include regular complexity Mobile broadband (MBB) User Equipments (UEs). Both support mobile originated (MO) traffic only.

[0005] Within the context of SDT, the possibility of transmitting subsequent data has been discussed, meaning transmission of further segments of the data that cannot fit in the Msg3 Transport Block. Such segments of data can be transmitted either in RRC_CONNECTED as in legacy after the 4-step RACH procedure has been completed, or they can be transmitted in RRC_INACTIVE before the UE transitions to RRC_CONNECTED. In the former case, the transmission will be more efficient as the NR base station (gNB) and the UE are appropriately configured based on the current UE channel conditions, while in the latter case, several optimization are not in place yet, especially if the UE has moved while not connected, and also the transmission may collide with the transmission from other UEs as the contention has not been resolved yet.

[0006] The WI has already started in 3GPP meeting RAN2#111-e, and the following relevant agreements have already been made:

• Small data transmission with RRC message is supported as baseline for RA-based and CG based schemes.

• The 2-step RACH or 4-step RACH should be applied to RACH based uplink small data transmission in RRC_INACTIVE.

• The uplink small data can be sent in MSGA of 2-step RACH or msg3 of 4-step RACH.

• Small data transmission is configured by the network on a per DRB basis.

• Data volume threshold is used for the UE to decide whether to do SDT or not. For Further Study (FFS) how we calculate data volume.

• FFS if an “additional SDT specific” RSRP threshold is further used to determine whether the UE should do SDT. • UL/DL transmission following UL SDT without transitioning to RRC_CONNECTED is supported.

• When UE is in RRC_INACTIVE, it should be possible to send multiple UL and DL packets as part of the same SDT mechanism and without transitioning to RRC_CONNECTED on dedicated grant. FFS on details and whether any indication to network is needed.

[0007] So, in NR Rel-17 SDT WI, two main solutions will be specified for enabling SDT in RRC_INACTIVE state: (a) RACH-based SDT (i.e., transmitting small data on Message A PUSCH (Physical Uplink Shared Channel) in a 2-step RACH procedure, or transmitting small data on Message 3 PUSCH in a 4-step RACH procedure) and (b) Configured Grant (CG) based SDT (i.e., SDT over configured grant type-1 PUSCH resources for UEs in RRC inactive state). The 4-step, 2-step RACH and configured grant type have already been specified as part of Rel-15 and Rel-16. So, the SDT features to be specified in NR Rel-17 build on these building blocks to enable small data transmission in INACTIVE state for NR.

[0008] Notice that some of the mechanisms discussed in this document are already agreed and serve the purpose of presenting a complete working solution.

[0009] In RAN2#112-e, and the following agreements have been made:

• The configuration of configured grant resource for UE uplink small data transfer is contained in the RRCRelease message. FFS if other dedicated messages can configure CG in INACTIVE CG. Configuration is only type 1 CG with no contention resolution procedure for CG.

• The configuration of configured grant resource can include one type 1 CG configuration. FFS if multiple configured CGs are allowed.

• A new TA timer for TA maintenance specified for configured grant based small data transfer in RRC_INACTIVE should be introduced. FFS on the procedure, the validity of TA, and how to handle expiration of TA timer. The TA timer is configured together with the CG configuration in the RRCRelease message.

• The configuration of configured grant resource for UE small data transmission is valid only in the same serving cell. FFS for other CG validity criteria (e.g., timer, UL/SUL aspect, etc.).

• The UE can use configured grant based small data transfer if at least the following criteria is fulfilled (1) user data is smaller than the data volume threshold; (2) configured grant resource is configured and valid; (3) UE has valid TA. FFS for the candidate beam criteria. • From RAN2 point of view: An association between CG resources and SSBs is required for CG-based SDT. FFS up to RAN 1 how the association is configured or provided to the UE. Send an LS to RANI to start the discussion on how the association can be made. Mention that one option RAN2 considered was explicit configuration with RRC Release message

• A SS-RSRP threshold is configured for SSB selection. UE selects one of the SSB with SS-RSRP above the threshold and selects the associated CG resource for UL data transmission.

[0010] In RAN2#113-e, and the following agreements have been made:

• CG-SDT resource configuration is provided to UEs in RRC_Connected only within the RRCRelease message, i.e., no need to also include it in RRCReconfiguration message.

• CG-PUSCH resources can be separately configured for NUL and SUL. FFS if we allow them at the same time. This depends on the alignments CRs for Rel-16.

• RRCRelease message is used to reconfigure or release the CG-SDT resources while UE is in RRCJNACTIVE.

• For CG-SDT the subsequent data transmission can use the CG resource or DG (i.e., dynamic grant addressed to UE’s C-RNTI). Details on C-RNTI, can be the same as the previous C-RNTI or may be configured explicitly by the network can be discussed in stage 3.

• TAT-SDT is started upon receiving the TAT-SDT configuration from gNB, i.e., RRCrelease message, and can be (re)started upon reception of TA command.

• From RAN2 point of view, assume similar to PUR, that we introduce a TA validation mechanism for SDT based on RSRP change, i.e. RSRP-based threshold(s) are configured. Ask RANI to confirm. FFS on how to handle CG configuration when TA expires or when is invalid due to RSRP threshold. Details of the TA validation procedure can be further discussed.

• As a baseline assumption, it’s a network configuration issue whether to support multiple CG-SDT configurations per carrier in RRCJNACTIVE (i.e., we will not restrict network configuration for now).

• FFS discuss further in stage 3 how to specify the agreement that CG-SDT resources are only valid in one cell (i.e., cell in which RRCRelease is received)

• UE releases CG-SDT resources when TAT expires in RRC_ In active state.

• For RA-SDT, up to two preamble groups (corresponding to two different payload sizes for MSGA/MSG3) may be configured by the network. • [CB] UE performs carrier selection as per legacy procedure and then the UE determines whether SDT can be initiated.

• [CB] Upon initiating SDT, after the carrier selection, if valid CG-SDT resource exists, then CG-SDT is chosen, otherwise UE proceeds to RA-SDT procedure.

• If RACH procedure is initiated for SDT (i.e., RA-SDT initiated), the UE first performs RACH type selection as specified in MAC (i.e., Rel-16). FFS whether threshold is SDT specific or not.

• RAN2 continues to progress the work based the separate RACH resources for SDT (i.e., explicit mechanisms to support common resources won’t be pursued unless there is sufficient support for this. However, use of common RACH resources will not be precluded if possible via implementation

• RAN2 design assumes that RRCRelease message is sent at the end to terminate the SDT procedure from RRC point of view. The RRCRelease sent at the end of the SDT may contain the CG resource (as per previous agreement). Write an LS to SA3 to explain SDT procedure and agreement.

• The UE behavior for handling of non-SDT data arrival after sending the first UL data packet is fully specified (i.e., not left to UE implementation)

[0011] In RAN2 113bis-e, the following agreements have been made:

• RSRP threshold is used to select between SDT and non-SDT procedure, if configured (RSRP refers to the same RSRP measured for carrier selection).

• RSRP threshold to select between SDT and non-SDT procedure is used for both CG-SDT and RA-SDT

• RSRP threshold to select between SDT and non-SDT procedure is same for both CG- SDT and RA-SDT

• RSRP threshold for carrier selection is specific to SDT (i.e., separately configured for SDT). This is optional for the network.

• Confirm that cell selection mechanism is not modified

• RSRP threshold for RA type selection is specific to SDT (i.e., separately configured for SDT)

• Data volume threshold is the same for CG-SDT and RA-SDT (can be checked further in stage 3 if we obtain majority support)

• FFS on the order and missing pieces (e.g., failure, fallback) of the high level procedure. The details of the procedures are left for stage 3. FFS on the procedure below, but copied for information. - Upon arrival of data only for DRB/SRB(s) for which SDT is enabled, the high level procedure for selection between SDT and non SDT procedure is as follows:

- If CG-SDT criteria is met: UE selects CG-SDT. UE initiate SDT procedure

- Else if RA-SDT criteria is met: UE selects RA-SDT. UE initiate SDT procedure

- Else: UE initiate non SDT procedure.

- CG-SDT criteria is considered met, if all of the following conditions are met, o available data volume <= data volume threshold o RSRP is greater than or equal to a configured threshold

- FFS 3) CG-SDT resources are configured on the selected UL carrier and are valid

- RA-SDT criteria is considered met, if all of the following conditions are met, o available data volume <= data volume threshold o RSRP is greater than or equal to a configured threshold o 4 step RA-SDT resources are configured on the selected UL carrier and criteria to select 4 step RA SDT is met; or 2 step RA-SDT resources are configured on the selected UL carrier and criteria to select 2 step RA SDT is met

• Switching from SDT to non-SDT is supported.

• FFS Switching from CG-SDT to RA-SDT is not allowed

• UE switches from SDT to non-SDT in following cases:

- Case 1 (27/0): UE receive indication from network to switch to non-SDT procedure. o Network can send RRCResume. FFS whether network can send indication in RAR/fallbackRAR/DCI to switch to non-SDT procedure.

FFS Case 2 (18/9): Initial UL transmission (in msgA/Msg3/CG resources) fails configured number of times

[0012] In RAN2#113bis-e, the following agreements were made:

• gNB can only configure MN terminated MCG bearer type for SDT

• Non-SDT radio bearers are only resumed upon receiving RRCResume (same as today)

• Down-scope to two solutions (CCCH or DCCH) and ask SA3 about security issues (explain that CCCH message will be repeated in same cell and ask if there is a question)

• The UE performs PDCP re-establishment implicitly, i.e., without explicit indication for PDCP re-establishment, when the UE initiates SDT procedure.

• As in legacy, whether to support ROHC continuity is explicitly configured by the network. • PDCP duplication is not supported for SDT.

• Connected mode DRX is not supported for SDT.

• PHR functionality is supported for SDT. FFS on PHR procedure.

• SR resource is not configured for SDT. When the BSR is triggered by SDT data, the UE will trigger RA because SR resource is not available, same as legacy.

• SDT failure detection timer is started upon initiation of SDT procedure.

• T319 legacy is not started if RRCResumeRequest or RRCResumeRequestl is transmitted

• T319 legacy stop conditions also apply to SDT failure detection timer.

• RRC re-establishment procedure is not supported for SDT.

• An LS is sent to SA3 to verify feasibility/impacts of re-using same NCC/I-RNTI value temporarily for RRC Resume procedure in new cell during SDT procedure (include same cell question from 502].

• FFS - RAN2 to select between the following options for cell re-selection during ongoing SDT procedure next meeting: 1) UE transitions to IDLE, possibly performing high-layer retransmission (8/25); or 2) UE remains in INACTIVE and sends RRC Resume to new cell.

• FFS Upon SDT failure detection timer expiry, the same procedure as T319 expiry is used (e.g., transition to IDLE as in the case of expiry of the T319 timer and attempts RRC connection setup). (18/8)

• CG-SDT resources can be configured at the same time on NUL and SUL.

• Implicit release of CG-SDT resource is not supported.

• UE start a window after CG DG transmission for CG-SDT. FFS whether to design a new timer or to reuse an existing timer.

• Support retransmission by dynamic grant for CG-SDT.

• Support multiple HARQ processes for uplink CG-SDT.

• CG resource availability delay is not considered as a criterion for CG validation.

• UL carrier selection is performed before CG-SDT selection.

• FFS CG-SDT resource can be configured on BWPs other than initial BWP.

4-step Random Access (RA) Type

[0013] The 4-step RA type has been used in 4G LTE and is also the baseline for 5G NR. The principle of this procedure in NR is shown in Figure 1 .

[0014] Step 1 : Preamble transmission [0015] The UE randomly selects a RA preamble (PREAMBLE_INDEX) corresponding to a selected Synchronization Signal/Physical Broadcast Channel (SS/PBCH) block, transmit the preamble on the PRACH occasion mapped by the selected SS/PBCH block. When the gNB detects the preamble, it estimates the Timing advance (TA) the UE should use in order to obtain Uplink (UL) synchronization at the gNB.

[0016] Step 2: RA response (RAR)

[0017] The gNB sends a RAR including the TA, the Temporary Cell Radio Network Temporary Identifier (TC-RNTI) (temporary identifier) to be used by the UE, a Random Access Preamble identifier that matches the transmitted PREAMBLE_INDEX and a grant for Msg3.

The UE expects the RAR and thus, monitors Physical Downlink Control Channel (PDCCH) addressed to Random Access Radio Network Temporary Identifier (RA-RNTI) to receive the RAR message from the gNB until the configured RAR window (ra-ResponseWindow) has expired or until the RAR has been successfully received. From 3GPP TS 38.321: “The MAC entity may stop ra-ResponseWindow (and hence monitoring for Random Access Response(s)) after successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the transmitted PREAMBLE_INDEX.“

[0018] Step 3: “Msg3” (UE ID or UE-specific C-RNTI)

[0019] In Msg3, the UE transmits its identifier (UE ID, or more exactly the initial part of the 5G-Temporary Mobile Subscriber Identity (TMSI)) for initial access or if it is already in RRC_CONNECTED or RRC_INACTIVE mode and needs to e.g. re-synchronize, its UE- specific RNTI. If the gNB cannot decode Msg3 at the granted UL resources, it may send a Downlink Control Information (DCI) addressed to TC-RNTI for retransmission of Msg3. Hybrid Automatic Repeat Request (HARQ) retransmission is requested until the UEs restart the random access procedure from step 1 after reaching the maximum number of HARQ retransmissions or until Msg3 can be successfully received by the gNB.

[0020] Step 4: “Msg4” (contention resolution)

[0021] In Msg4, the gNB responds by acknowledging the UE ID or C-RNTI. The Msg4 gives contention resolution, i.e., only one UE ID or C-RNTI will be sent even if several UEs have used the same preamble (and the same grant for Msg3 transmission) simultaneously. For Msg4 reception, the UE monitors TC-RNTI (if it transmitted its UE ID in Msg3) or C-RNTI (if it transmitted its C-RNTI in Msg3). 2-step RA Type

[0022] The 2-step RA type gives much shorter latency than the ordinary 4-step RA. In the 2- step RA, the preamble and a message corresponding to Msg3 (msgA PUSCH) in the 4-step RA can, depending on configuration, be transmitted in two subsequent slots. The msgA PUSCH is sent on a resource dedicated to the specific preamble. The 2-step RA procedure is depicted in Figure 2.

[0023] Upon successful reception msgA, the gNB will respond with a msgB. The msgB may be either a “successRAR”, “fallbackRAR”, or “Back off’. The content of msgB has been agreed as seen below. It is noted in particular that fallbackRAR provides a grant for a Msg3 PUSCH that identifies resources in which the UE should transmit the PUSCH, as well as other information.

[0024] Note: The notations “msgA” and “MsgA” are used interchangeably herein to denote message A. Similarly, the notations “msgB” and “MsgB” are used interchangeably herein to denote message B.

[0025] The possibility to replace the 4-step message exchange by a 2-step message exchange would lead to reduced RA latency. On the other hand, the 2-step RA will consume more resources since it uses contention-based transmission of the data. This means that the resources that are configured for the data transmission may often be unused. Another difference is that 2- step RA operated without a timing advance (TA) since there is no feedback from gNB on how to adjust the uplink synchronization before the data payload is transmitted in MsgA PUSCH. Effectively TA is zero for 2-step RA and therefore the solution is restricted to use in cell of smaller size, whereas 4-step RA can operate in any cell size.

[0026] When the 4-step RA is applied for SDT, the Msg3 will contain the RRCResumeRequest message and UP data. The gNB will as in the legacy case respond with the contention resolution ID (CR-ID) to resolve contention and at this point the TC-RNTI will be used by the UE as C-RNTI, i.e., the UE will monitor PDCCH for DCI scrambled by C-RNTI to obtain new UL grants, in case subsequent transmissions are needed. The SDT procedure ends when the gNB sends a RRCRelease with suspend config message and thereby keeping the UE in Inactive state. Alternatively, the gNB may instead send a RRCResume and move the UE to connected state.

[0027] When the 2-step RA is applied for SDT, the MsgA will contain the RRCResumeRequest message and UP data. The gNB will as in the legacy case respond with the contention resolution ID (CR-ID) to resolve contention. It will also send a C-RNTI and the UE will monitor PDCCH for DCI scrambled by C-RNTI to obtain new UL grants, in case subsequent transmissions are needed. As for the 4-step procedure, the SDT procedure ends when the gNB sends a RRCRelease with suspend config message and thereby keeping the UE in Inactive state. Alternatively, the gNB may instead send a RRCResume and move the UE to connected state.

Release Assistance Information (RAI)

[0028] In LTE, the early data transmission concept (e.g., in 3GPP TS 36.300) is similar to NR RACH based SDT, but is for SDT from Idle mode instead of inactive mode. In this procedure, it is possible to send a RAI in msg3 of the RA procedure to indicate that no further UL/DL higher layer Protocol Data Unit (PDU) is available. This indication is used by the network to determine whether the UE should remain in Idle or if the gNB should move the UE to connected mode.

[0029] For the Preconfigured PUSCH (PUR) in the LTE procedure (corresponding to CG based SDT in NR), there is no RAI specified. One reason for this is that there is no possibility to move the UE to connected mode. Instead, the UE remains in idle. In PUR, the first (UL) message is a RRCConnectionResumeRequest and the DL response is a RRCConnectionRelease message which keeps the UE in Idle mode.

NR CG based PUSCH Transmission

[0030] CG PUSCH resources are the PUSCH resources configured in advance for the UE. When there is uplink data available at UE’s buffer, it can immediately start uplink transmission using the pre-configured PUSCH resources without waiting for an UL grant from the gNB, thus reducing the latency. NR supports CG type 1 PUSCH transmission and CG type 2 PUSCH transmission. For both two types, the PUSCH resources (time and frequency allocation, periodicity, etc.) are preconfigured via dedicated RRC signaling. The CG type 1 PUSCH transmission is activated/deactivated by RRC signaling, while the CG type 2 PUSCH transmission is activated/deactivated by an UL grant using DCI signaling.

[0031] For SDT, it has been agreed that the CG type 1 should be the baseline. The SDT using CG (CG-SDT) is configured by the network in a RRCRelease with suspendconfig.

[0032] The UE will check that the TA is valid before each UL transmission on the CG-SDT resources. The exact definition of what a valid TA is has not yet been agreed in 3gpp for SDT.

It will mean that the time alignment timer is running but there will also be requirements of minimum Reference Signal Received Power (RSRP) level and possibly that the RSRP level has not changed more than a threshold since the last CG transmission occasion. If the TA is not valid, the UE will not be allowed to transmit on the CG-SDT resource. [0033] The first UL transmission will contain a RRCResume message and UP data, the following transmissions will only contain UP data and possibly Medium Access Control (MAC) Control Elements (CEs). The network will end the CG-SDT procedure by either sending a RRCRelease with which keeps the UE in Inactive mode, and RRCRelease without suspendconfig, which moves the UE to Idle mode or by sending a RRCResume which moves the UE to connected mode.

[0034] Compared to LTE PUR, there can be several transmissions on CG resources before the UE receives a RRCRelease/RRCResume. In PUSCH resource unit (PRU), an RRCConnectionRelease is sent after each PUR transmission. An example of a CG-SDT procedure is shown in Figure 3.

Summary

[0035] There are various proposed embodiments which address one or more of the issues disclosed herein. In one embodiment, a method performed by a user equipment (UE) for small data transmissions (SDT) with a network node comprises detecting a condition that indicates that transmission of an end marker is to occur. The end marker is an indication that the UE (a) has no data for uplink transmission using a Configured Grant (CG) SDT configuration, (b) expects no data for uplink transmission using the CG-SDT configuration for a time period, or both (a) and (b). In response to the detection, the method further comprises a step of transmitting the end marker to the network node. In this way, the end marker allows the UE to indicate that it has no more data and does not need the CG-SDT configuration with the allocated resources. This allows the gNB to know that skipped transmissions are temporary with respect to data.

[0036] In one embodiment, the end marker further indicates that resources configured for CG-SDT should be released.

[0037] In one embodiment, the end marker comprises information indicating that the UE does not need the CG-SDT configuration.

[0038] In one embodiment, the step of detecting the condition comprises detecting that an uplink buffer in the UE is empty.

[0039] In one embodiment, the step of detecting the condition comprises detecting that an uplink buffer in the UE becomes empty in next N transmissions, wherein N is an integer that is one or greater.

[0040] In one embodiment, the step of detecting the condition comprises detecting that an uplink buffer in the UE is empty and that no more uplink data is expected for a time period. [0041] In one embodiment, the time period is based on a timing advance (TA) timer value. [0042] In one embodiment, the time period is based on a configured SDT failure detection timer value associated with the UE.

[0043] In one embodiment, the time period applies only to a next uplink occasion.

[0044] In one embodiment, the time period is received from the network node.

[0045] In one embodiment, the step of detecting the condition comprises receiving an indication from an upper layer of the UE.

[0046] In one embodiment, the step of receiving an indication from an upper layer of the UE comprises receiving an indication from an application generating data.

[0047] In one embodiment, the indication is an indication that a sensor has been turned on or off.

[0048] In one embodiment, the indication is an indication that an application has been turned on or off.

[0049] In one embodiment, the upper layer is a higher layer protocol entity.

[0050] In one embodiment, the indication from the upper layer comprises receiving signaling radio bearers (SRBs).

[0051] In one embodiment, the end marker comprises additional information.

[0052] In one embodiment, the additional information indicates (a) a logical channel (LCH) that is configured for CG-SDT that has no more data and (b) data available on other LCHs configured or not configured for SDT.

[0053] In one embodiment, the additional information indicates a periodicity or a size of the data that has changed and a new Configured Grant (CG) configuration.

[0054] In one embodiment, the additional information indicates estimated traffic characteristics or Quality-of-Service (QoS) bearer information.

[0055] In one embodiment, the additional information indicates radio link information or other cell information or carrier information.

[0056] In one embodiment, the end marker is encoded with an otherwise unused logical channel identification (LCID) or enhanced LCID (eLCID) in a fixed sized reserved LCID, R/LCID, Medium Access Control (MAC) Subheader.

[0057] In one embodiment, the end marker is encoded with index value 36, 36, 37, 38, 39,

40, 41, 42, 43 or 44 as LCID in a R/LCID MAC Subheader.

[0058] In one embodiment, the end marker is encoded with an otherwise unused eLCID in a R/LCID or R/L/LCID MAC Subheader.

[0059] In one embodiment, the end marker is encoded with a Buffer Status Reporting (BSR). [0060] In one embodiment, a method performed by a network node for SDT with a UE comprises receiving an end marker from the UE. The end marker indicates that the UE (a) has no data for uplink transmission using a CG-SDT configuration, (b) expects no data for uplink transmission using the CG-SDT configuration for a time period, or both (a) and (b).

[0061] Corresponding embodiments of the UE and the network node are also disclosed. [0062] A UE is adapted to detect a condition that indicates that transmission of an end marker is to occur. The end marker is an indication that the UE (a) has no data for uplink transmission using a Configured Grant (CG) SDT configuration, (b) expects no data for uplink transmission using the CG-SDT configuration for a time period, or both (a) and (b). In response to the detection, the UE is further adapted to transmit the end marker to the network node.

[0063] A UE comprises one or more transmitters, one or more receivers, and processing circuitry associated with the one or more transmitters and the one or more receivers. The processing circuitry is configured to cause the UE to detect a condition that indicates that transmission of an end marker is to occur. The end marker is an indication that the UE (a) has no data for uplink transmission using a Configured Grant (CG) SDT configuration, (b) expects no data for uplink transmission using the CG-SDT configuration for a time period, or both (a) and (b). In response to the detection, the processing circuitry is further configured to cause the UE to transmit the end marker to the network node.

[0064] A network node is adapted to receive an end marker from the UE. The end marker indicates that the UE (a) has no data for uplink transmission using a CG-SDT configuration, (b) expects no data for uplink transmission using the CG-SDT configuration for a time period, or both (a) and (b).

[0065] A network node comprises processing circuitry configured to cause the network node to receive an end marker from the UE. The end marker indicates that the UE (a) has no data for uplink transmission using a CG-SDT configuration, (b) expects no data for uplink transmission using the CG-SDT configuration for a time period, or both (a) and (b).

Brief Description of the Drawings

[0066] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0067] Figure 1 illustrates a 4-step Random Channel (RACH) procedure.

[0068] Figure 2 illustrates a 2-step RACH procedure. [0069] Figure 3 illustrates a procedure of Small Data Transmissions using Configured Grant (CG-SDT).

[0070] Figure 4 shows an example of a communication system in accordance with some embodiments.

[0071] Figure 5 reproduces Table 6.2.1-2a in 3rd Generation Partnership Project (3GPP) TS 38.321.

[0072] Figure 6 shows a reserved logical channel identification (R/LCID) Medium Access Control (MAC) subheader.

[0073] Figure 7 shows an R/LCID/eLCID MAC subheader in Figure 6.1.2-3 of 3GPP TS 38.321.

[0074] Figure 8 shows an R/F/LCID/eLCID/L MAC subheader in Figure 6.1.2-1 and 6.1.2-2 of 3GPP TS 38.321.

[0075] Figure 9 shows a legacy short Small Data Buffer Status Reporting (BSR) MAC Control Element (CE).

[0076] Figure 10 illustrates a flow chart in accordance with some embodiments.

[0077] Figure 11 shows a User Equipment (UE) in accordance with some embodiments.

[0078] Figure 12 shows a network node in accordance with some embodiments

[0079] Figure 13 is a block diagram of a host, which may be an embodiment of the host of

Figure 4, in accordance with various aspects described herein.

[0080] Figure 14 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0081] Figure 15 shows a communication diagram of a host communicating via a network node with the UE over a partially wireless connection in accordance with some embodiments.

Detailed Description

[0082] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments.

Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0083] There currently exist certain challenges.

[0084] In New Radio (NR), Uplink (UL) skipping can be configured which means that when a User Equipment (UE) receives a grant and has no data to transmit, it does not need to transmit anything. If UL skipping is not allowed, the UE would need to send padding in every Configured Grant (CG) transmission occasion. In legacy NR Rel 15, UL skipping can be configured in setting e.g., skipUplinkTxDynamic. If set to true, the UE skips UL transmissions as described in 3GPP TS 38.321.

[0085] A problem with skipping is that the network does not know why it does not receive any transmission on a CG transmission occasion. It could be because the UE temporarily has no data to transmit and therefore skips this transmission, but it could also be because the channel quality is so bad that the NR base station (gNB) does not detect the transmission. It could also be because the UE has an invalid timing alignment and is not allowed to transmit. Thus, Discontinuous Transmission (DTX) detection to detect actual transmissions can be performed at the gNB but comes with a significant error probability.

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

[0087] In this disclosure, an end marker is defined for Configured Grant for Small Data Transmissions (CG-SDT). The purpose of the end marker is to let the gNB know that the UE has no more data and expects no more data for the nearest time and has no need for the CG-SDT configuration. This can be used by the gNB to release the CG-SDT resources since they are not needed. This allows for reducing the time to detect unused UL resources allocated to the UE. [0088] This can be implemented in various ways. Triggers for when the end marker is sent are given and the formats of the end marker are specified. In one example, an end marker is triggered by an empty buffer or by indication from upper layers. In another example, a new Medium Access Control (MAC) Control Element (CE) is defined. In another example, a Buffer Status Reporting (BSR) indicating buffer size zero can be taken as an end marker. In another example, a specific coding of the MAC subheader or Logical Channel Identification/ enhanced Logical Channel Identification (LCID/eLCID) can be used as an end marker.

[0089] Certain embodiments may provide one or more of the following technical advantages. The end marker allows the UE to indicate that it has no more data and does not need the CG-SDT configuration with the allocated resources. This allows the gNB to know that skipped transmissions are temporary with respect to data. Without the teachings of the disclosure, the gNB may either keep the CG-SDT configuration although the UE does not use it or release the CG-SDT configuration when there is only a temporary short lack of data at the UE.

Alternatively, the UE transmits padding only, for where retransmissions would apply unnecessary. It would thereby be uncertain to what extent it would still be optimal to keep the CG-SDT configuration. Additionally, an appropriate decision on release of the UE to, for example, Inactive with or without an CG configuration can be performed.

[0090] Figure 4 shows an example of a communication system 400 in accordance with some embodiments.

[0091] In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410a and 410b (one or more of which may be generally referred to as network nodes 410), or any other similar 3 ^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 412a, 412b, 412c, and 412d (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections.

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

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

[0094] In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. 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 406 includes one more core network nodes (e.g., core network node 408) 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 408. 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).

[0095] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and/or the telecommunication network 402, and may be operated by the service provider or on behalf of the service provider. The host 416 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.

[0096] As a whole, the communication system 400 of Figure 4 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.

[0097] In some examples, the telecommunication network 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunications network 402 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.

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

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

[0100] The hub 414 may have a constant/persistent or intermittent connection to the network node 410b. The hub 414 may also allow for a different communication scheme and/or schedule between the hub 414 and UEs (e.g., UE 412c and/or 412d), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and/or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to an M2M service provider over the access network 404 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 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 410b. In other embodiments, the hub 414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

[0101] This disclosure describes several embodiments for when an end marker transmission should be triggered, its content and different formats of the end marker.

1 Triggering of an End Marker Transmission [0102] The end marker transmission can be triggered when:

• The UEs UL buffer (e.g., the UL buffer of the UE 412) is empty, or alternatively becomes empty in the next transmission, or next n transmissions. In the following, the embodiments are not limited to empty buffer only.

• The UEs UL buffer (e.g., the UL buffer of the UE 412) is empty and no more UL data is expected for a configurable time period.

• The time period can be configured to be: a) related to the configured CG periodicity, e.g., a number of configured CG periodicities, b) related to the configured SDT failure detection timer value, e.g., a number of configured SDT failure detection timer values, c) related to the configured TA timer value, e.g., a number of configured TA timer values, d) applied only to the next UL transmission occasion, or e) any value configured by the network.

• Indication from upper layers. a) Indication from the upper layers may be from an application generating the data, for example, (i) a sensor on/off, (ii) an application is turned off/on, (iii) a higher layer protocol entity such as for measurements for positioning, b) The indication are hereby not limited to data but also includes signaling, such as signaling radio bearers (SRBs). 2 End Marker information

[0103] In addition to indicating that the UE (e.g., UE 412) has no more data and indirectly or directly indicating that the CG-SDT configuration can be released. The end marker can be combined to convey other information such as:

• The current logical channel (LCH) that are configured for CG-SDT that have no more data with additional indication for data available on other LCHs configured or not configured for SDT. For example, on SRB or other Data Radio Bearer (DRB) configured for SDT. In one example, this data can be non-SDT data.

• The periodicity or size of the data has changed, and a new CG configuration would be beneficial.

• Estimated traffic characteristics or Quality of Service (QoS) bearer information/indication.

• Radio Link information or other cell/carrier information. For example, cell reselection trigger estimation.

3 End Marker Formats

[0104] There are several options of how to code the end marker, as explained below.

3.1 Option 1 - Use an unused LCID or eLCID in the fixed size Reserved LCID (R/LCID) MAC Subheader

[0105] In one embodiment, the end marker is coded by a new LCID in the R/LCID header.

As seen from Table 6.2.1-2a in 3GPP TS 38.321 (reproduced in Figure 5), the index 35-44 are reserved and thereby unused.

[0106] In one example, using index 35 (or any one of the reserved values 35-44) as LCID in the R/LCID MAC Subheader (as seen in Figure 6) could be used for this indication. In this embodiment, no MAC CE is used, instead the indication is done by the R/LCID MAC Subheader alone. The gNB 410 would, from receiving this R/LCID MAC Subheader and the indicated LCID value, understand that this is an end marker.

3.2 Option 2 - Use an Unused eLCID in the R/LCID or R/F/LCID MAC Subheader

[0107] In another embodiment, using LCID of 33 or 34 in the R/LCID MAC Subheader and a new eLCID is used to indicate the end marker.

[0108] In one example, LCID=34 is used in the R/LCID/eLCID MAC subheader to indicate a one octet eLCID and fixed size payload size, as shown in Figure 6.1.2-3 from 3GPP TS 38.321 (reproduced in Figure 7). In this case, the fixed size of the payload could be 0 and only the end marker is signalled. Other fixed values could be specified (in e.g., 3GPP TS 38.321) and used. [0109] In another example, R/F/LCID/eLCID/L MAC subheader is used. This is based on the existing R/F/LCID/eLCID/L MAC subheader in Figure 6.1.2-1 and 6.1.2-2 in 3GPP TS 38.321 (reproduced in Figure 8). The subheader is then used to indicate the end marker.

[0110] In one example, LCID=34 (one octet eLCID field) and an 8-bit L field is used. In this case, a new eLCID is used to indicate the end marker and the L field can be coded to indicate additional information.

3.3 Option 3 - Using BSR

[0111] In another embodiment, the legacy BSR is used but triggered differently. Figure 9 illustrates the legacy short Small Data BSR MAC CE. The BSR indicates that the LCG has zero data. In this case, the BSR should be triggered according to the above-described triggering rules for end marker (“Section 1: Triggering of an end marker transmission”) since the legacy trigger conditions for BSR will not be sufficient.

[0112] In an alternative, a buffer size of zero is indicated for the transmitting LCH or LCG, for where another field is appended for another LCH indicating data or buffer status information for where this LCH cannot use the current CG configuration (grant).

3.4 Radio Resource Control (RRC) Indication

[0113] The indication end marker could also be carried over RRC. This could be achieved by defining a new RRC message, and a new field could be used to indicate the end marker. In the shorted format, this could be a 1-bit flag, as outlined above, or multiple bits could be used to indicate additional information. In here the included information and trigger for such information in RRC may include the above elements listed.

4 Additional Description

[0114] Figure 10 is a flow chart that illustrates the operation of a UE 412 equipped for SDT with a network node 410 in accordance with at least some of the embodiments described above. As illustrated, the UE 412 operates as follows.

[0115] Step 1000: The UE 412 detects a condition indication that transmission of an end marker should occur. In one embodiment, the end marker is an end marker indicating the network node 410 should release CG-SDT resources. In another embodiment, the end marker is an end marker indicating to the network node 410 that the UE 412 does not need the associated CG-SDT configuration. In another embodiment, the end marker is an end marker indicating that the UE 412 has no more data or that the UE has no more data and expects no more data for a time period. In another embodiment, the end marker is an end marker associated with CG-SDT configuration.

[0116] Step 1002: In response to the detection of step 1000, the UE transmits the end marker to the network node 410.

[0117] In one embodiment, the step of detecting a condition comprises detecting that an uplink buffer in the user equipment is empty.

[0118] In one embodiment, the step of detecting a condition comprises detecting that an uplink buffer in the user equipment becomes empty in the next N transmissions, wherein N is an integer that is one or greater.

[0119] In one embodiment, the step of detecting a condition comprises detecting that an uplink buffer in the user equipment is empty and that no more uplink data is expected for a time period.

[0120] In one embodiment, the time period is based on a TA timer value.

[0121] In one embodiment, the time period is based on a configured SDT failure detection timer value associated with the user equipment.

[0122] In one embodiment, the time period applies only to a next uplink occasion.

[0123] In one embodiment, the time period is received from a network associated with the user equipment.

[0124] In one embodiment, the step of detecting a condition comprises receiving an indication from an upper layer.

[0125] In one embodiment, the step of receiving an indication from an upper layer comprises receiving an indication from an application generating data.

[0126] In one embodiment, the generated data is that a sensor has been turned on or off.

[0127] In one embodiment, the generated data is that an application has been turned on or off.

[0128] In one embodiment, the upper layer is a higher layer protocol entity.

[0129] In one embodiment, the indication from an upper layer comprises receiving signaling comprising signaling radio bearers (SRBs).

[0130] In one embodiment, the end markers includes additional information, which is information in addition to information indicating the user equipment has no data for transmission. [0131] In one embodiment, the additional information indicates current LCH that are configured for CG-SDT that have no more data with additional indication for data available on other LCHs configured or not configured for SDT.

[0132] In one embodiment, the additional information indicates the periodicity or size of the data has changed, and a new CG configuration would be beneficial.

[0133] In one embodiment, the additional information indicates estimated traffic characteristics or QoS bearer information.

[0134] In one embodiment, the additional information indicates Radio Link information or other cell information or carrier information.

[0135] In one embodiment, the end marker is encoded with an otherwise unused LCID or eLCID in a fixed size R/LCID Mac Subheader.

[0136] In one embodiment, the end marker is encoded with index value 36, 36, 37, 38, 39,

40, 41, 42, 43 or 44 as LCID in the R/LCID MAC Subheader.

[0137] In one embodiment, the end marker is encoded with an otherwise unused eLCID in the R/LCID or R/F/LCID MAC Subheader.

[0138] In one embodiment, the end marker is encoded with a BSR.

[0139] In one embodiment, the step of transmitting the end marker comprises transmitting the end marker in an RRC message.

[0140] Figure 11 shows a UE 1100 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. Also, an example of the UE 1100 is the UEs 412A to 412D in Figure 4.

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

[0142] The UE 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/output interface 1106, a power source 1108, a memory 1110, a communication interface 1112, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 11. 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.

[0143] The processing circuitry 1102 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 1110. The processing circuitry 1102 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 1102 may include multiple central processing units (CPUs).

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

[0146] The memory 1110 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 1110 includes one or more application programs 1114, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1116. The memory 1110 may store, for use by the UE 1100, any of a variety of various operating systems or combinations of operating systems. [0147] The memory 1110 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 1110 may allow the UE 1100 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 1110, which may be or comprise a device-readable storage medium. [0148] The processing circuitry 1102 may be configured to communicate with an access network or other network using the communication interface 1112. The communication interface 1112 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1122. The communication interface 1112 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 1118 and/or a receiver 1120 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1118 and receiver 1120 may be coupled to one or more antennas (e.g., antenna 1122) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0149] In the illustrated embodiment, communication functions of the communication interface 1112 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/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [0150] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1112, 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).

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

[0152] A UE, when in the form of an Internet of Things (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, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, 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 item-tracking 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 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 1100 shown in Figure 11.

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

[0154] 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. [0155] Figure 12 shows a network node 1200 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, evolved Node Bs (eNBs), NR NodeBs (gNBs)), and the network nodes 410A, 410B in Figure 4. [0156] 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).

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

[0158] The network node 1200 includes a processing circuitry 1202, a memory 1204, a communication interface 1206, and a power source 1208. The network node 1200 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 1200 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 1200 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1204 for different RATs) and some components may be reused (e.g., a same antenna 1210 may be shared by different RATs). The network node 1200 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1200, 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 1200.

[0159] The processing circuitry 1202 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 1200 components, such as the memory 1204, to provide network node 1200 functionality.

[0160] In some embodiments, the processing circuitry 1202 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1202 includes one or more of radio frequency (RF) transceiver circuitry 1212 and baseband processing circuitry 1214. In some embodiments, the radio frequency (RF) transceiver circuitry 1212 and the baseband processing circuitry 1214 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 1212 and baseband processing circuitry 1214 may be on the same chip or set of chips, boards, or units. [0161] The memory 1204 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 1202. The memory 1204 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 1202 and utilized by the network node 1200. The memory 1204 may be used to store any calculations made by the processing circuitry 1202 and/or any data received via the communication interface 1206. In some embodiments, the processing circuitry 1202 and memory 1204 is integrated. [0162] The communication interface 1206 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 1206 comprises port(s)/terminal(s) 1216 to send and receive data, for example to and from a network over a wired connection. The communication interface 1206 also includes radio front-end circuitry 1218 that may be coupled to, or in certain embodiments a part of, the antenna 1210. Radio front-end circuitry 1218 comprises filters 1220 and amplifiers 1222. The radio front-end circuitry 1218 may be connected to an antenna 1210 and processing circuitry 1202. The radio front-end circuitry may be configured to condition signals communicated between antenna 1210 and processing circuitry 1202. The radio front-end circuitry 1218 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 1218 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1220 and/or amplifiers 1222. The radio signal may then be transmitted via the antenna 1210. Similarly, when receiving data, the antenna 1210 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1218. The digital data may be passed to the processing circuitry 1202. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

[0163] In certain alternative embodiments, the network node 1200 does not include separate radio front-end circuitry 1218, instead, the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1212 is part of the communication interface 1206. In still other embodiments, the communication interface 1206 includes one or more ports or terminals 1216, the radio front-end circuitry 1218, and the RF transceiver circuitry 1212, as part of a radio unit (not shown), and the communication interface 1206 communicates with the baseband processing circuitry 1214, which is part of a digital unit (not shown).

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

[0165] The antenna 1210, communication interface 1206, and/or the processing circuitry 1202 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 1210, the communication interface 1206, and/or the processing circuitry 1202 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.

[0166] The power source 1208 provides power to the various components of network node 1200 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1208 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1200 with power for performing the functionality described herein. For example, the network node 1200 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 1208. As a further example, the power source 1208 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.

[0167] Embodiments of the network node 1200 may include additional components beyond those shown in Figure 12 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 1200 may include user interface equipment to allow input of information into the network node 1200 and to allow output of information from the network node 1200. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1200.

[0168] Figure 13 is a block diagram of a host 1300, which may be an embodiment of the host 416 of Figure 4, in accordance with various aspects described herein. As used herein, the host 1300 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 1300 may provide one or more services to one or more UEs.

[0169] The host 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a network interface 1308, a power source 1310, and a memory 1312. 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 Figures 11 and 12, such that the descriptions thereof are generally applicable to the corresponding components of host 1300.

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

[0171] Figure 14 is a block diagram illustrating a virtualization environment 1400 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 1400 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.

[0172] Applications 1402 (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.

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

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

[0175] In the context of NFV, a VM 1408 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 1408, and that part of hardware 1404 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 1408 on top of the hardware 1404 and corresponds to the application 1402.

[0176] Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 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 1410, which, among others, oversees lifecycle management of applications 1402.

In some embodiments, hardware 1404 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 1412 which may alternatively be used for communication between hardware nodes and radio units.

[0177] Figure 15 shows a communication diagram of a host 1502 communicating via a network node 1504 with a UE 1506 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 412a of Figure 4 and/or UE 1100 of Figure 11), network node (such as network node 410a of Figure 4 and/or network node 1200 of Figure 12), and host (such as host 416 of Figure 4 and/or host 1300 of Figure 13) discussed in the preceding paragraphs will now be described with reference to Figure 15.

[0178] Fike host 1300, embodiments of host 1502 include hardware, such as a communication interface, processing circuitry, and memory. The host 1502 also includes software, which is stored in or accessible by the host 1502 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 1506 connecting via an over-the-top (OTT) connection 1550 extending between the UE 1506 and host 1502. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1550. [0179] The network node 1504 includes hardware enabling it to communicate with the host 1502 and UE 1506. The connection 1560 may be direct or pass through a core network (like core network 406 of Figure 4) 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.

[0180] The UE 1506 includes hardware and software, which is stored in or accessible by UE 1506 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 1506 with the support of the host 1502. In the host 1502, an executing host application may communicate with the executing client application via the OTT connection 1550 terminating at the UE 1506 and host 1502. 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 1550 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 1550.

[0181] The OTT connection 1550 may extend via a connection 1560 between the host 1502 and the network node 1504 and via a wireless connection 1570 between the network node 1504 and the UE 1506 to provide the connection between the host 1502 and the UE 1506. The connection 1560 and wireless connection 1570, over which the OTT connection 1550 may be provided, have been drawn abstractly to illustrate the communication between the host 1502 and the UE 1506 via the network node 1504, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0182] As an example of transmitting data via the OTT connection 1550, in step 1508, the host 1502 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 1506. In other embodiments, the user data is associated with a UE 1506 that shares data with the host 1502 without explicit human interaction. In step 1510, the host 1502 initiates a transmission carrying the user data towards the UE 1506. The host 1502 may initiate the transmission responsive to a request transmitted by the UE 1506. The request may be caused by human interaction with the UE 1506 or by operation of the client application executing on the UE 1506. The transmission may pass via the network node 1504, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1512, the network node 1504 transmits to the UE 1506 the user data that was carried in the transmission that the host 1502 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1514, the UE 1506 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1506 associated with the host application executed by the host 1502.

[0183] In some examples, the UE 1506 executes a client application which provides user data to the host 1502. The user data may be provided in reaction or response to the data received from the host 1502. Accordingly, in step 1516, the UE 1506 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 1506. Regardless of the specific manner in which the user data was provided, the UE 1506 initiates, in step 1518, transmission of the user data towards the host 1502 via the network node 1504. In step 1520, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1504 receives user data from the UE 1506 and initiates transmission of the received user data towards the host 1502. In step 1522, the host 1502 receives the user data carried in the transmission initiated by the UE 1506.

[0184] One or more of the various embodiments improve the performance of OTT services provided to the UE 1506 using the OTT connection 1550, in which the wireless connection 1570 forms the last segment. More precisely, the teachings of these embodiments may improve data rate and latency and thereby provide benefits such as reduced user waiting time, improved content resolution, and better responsiveness.

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

[0186] 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 1550 between the host 1502 and UE 1506, 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 1502 and/or UE 1506. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1550 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 1550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1504. 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 1502. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1550 while monitoring propagation times, errors, etc.

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

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

[0189] Some example embodiments of the present disclosure are as follows:

Group A Embodiments

[0190] Embodiment 1. A method performed by a UE for SDT with a network node, comprises (a) detecting a condition indicating that transmission of an end marker should occur, the end marker indicating to the network node should release CG-SDT resources; and (b) in response to the detection, transmitting the end marker to the network node.

[0191] Embodiment 2. A method performed by a UE for SDT with a network node, comprises (a) detecting a condition indicating that transmission of an end marker should occur, the end marker indicating to the network node that the user equipment does not need the associated CG-SDT configuration; and (b) in response to the detection, transmitting the end marker to the network node. [0192] Embodiment 3. A method performed by a UE for SDT comprises detecting a condition indicating that transmission of an end marker should occur, the end marker indicating: the user equipment has no more data; or the user equipment has no more data and expects no more data for a time period; in response to the detection, transmitting the end marker. [0193] Embodiment 4. A method performed by a UE for SDT comprises detecting a condition indicating that transmission of an end marker associated with CG-SDT configuration should occur; and in response to the detection, transmitting the end marker.

[0194] Embodiment 5. In the method of any of the embodiments 1-4, detecting a condition comprises detecting that an uplink buffer in the user equipment is empty. [0195] Embodiment 6. In the method of any of the embodiments 1-4, detecting a condition comprises detecting that an uplink buffer in the user equipment becomes empty in the next N transmissions, wherein N is an integer that is one or greater.

[0196] Embodiment 7. In the method of any of the embodiments 1-4, detecting a condition comprises detecting that an uplink buffer in the user equipment is empty and that no more uplink data is expected for a time period.

[0197] Embodiment 8. The time period is based on a TA timer value.

[0198] Embodiment 9. In the method of embodiment 7, the time period is based on a configured SDT failure detection timer value associated with the user equipment.

[0199] Embodiment 10. In the method of embodiment 7, the time period applies only to a next uplink occasion.

[0200] Embodiment 11. In the method of embodiment 7, the time period is received from a network associated with the user equipment.

[0201] Embodiment 12. In the method any of the embodiments 1-4, detecting a condition comprises receiving an indication from an upper layer. [0202] Embodiment 13. In the method of embodiment 12, receiving an indication from an upper layer comprises receiving an indication from an application generating data.

[0203] Embodiment 14. In the method of embodiment 13, the generated data is that a sensor has been turned on or off.

[0204] Embodiment 15. In the method of embodiment 13, the generated data is that an application has been turned on or off.

[0205] Embodiment 16. In the method of embodiment 12, the upper layer is a higher layer protocol entity.

[0206] Embodiment 17. In the method of embodiment 12, the indication from an upper layer comprises receiving signaling. [0207] Embodiment 18. In the method of embodiment 17, the signaling comprises signaling radio bearers (SRBs).

[0208] Embodiment 19. In the method any of the embodiments 1-4, the end markers includes additional information, which is information in addition to information indicating the user equipment has no data for transmission.

[0209] Embodiment 20. In the method of embodiment 19, the additional information indicates current LCH that are configured for CG-SDT that have no more data with additional indication for data available on other LCHs configured or not configured for SDT.

[0210] Embodiment 21. In the method of embodiment 19, the additional information indicates the periodicity or size of the data has changed, and a new CG configuration would be beneficial.

[0211] Embodiment 22. In the method of embodiment 19, the additional information indicates estimated traffic characteristics or QoS bearer information.

[0212] Embodiment 23. In the method of embodiment 19, the additional information indicates Radio Link information or other cell information or carrier information.

[0213] Embodiment 24. In the method of any of the embodiments 1-4, the end marker is encoded with an otherwise unused LCID or eLCID in a fixed size R/LCID Mac Subheader. [0214] Embodiment 25. In the method of embodiment 24, the end marker is encoded with index value 36, 36, 37, 38, 39, 40, 41, 42, 43 or 44 as LCID in the R/LCID MAC Subheader. [0215] Embodiment 26. In the method of embodiment 24, the end marker is encoded with an otherwise unused eLCID in the R/LCID or R/F/LCID MAC Subheader.

[0216] Embodiment 27. In the method of any of the embodiments 1-4, the end marker is encoded with a BSR.

[0217] Embodiment 28. In the method any of the embodiments 1-4, transmitting the end marker comprises transmitting the end marker in an RRC message.

[0218] Embodiment 29. In method of any of the previous embodiments, further comprises providing user data; and forwarding the user data to a host via the transmission to the network node.

Group B Embodiments

[0219] Embodiment 30. A UE comprises (a) processing circuitry configured to perform any of the steps of any of the Group A embodiments; and (b) power supply circuitry configured to supply power to the processing circuitry. [0220] Embodiment 31. A UE comprises 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.

[0221] Embodiment 32. A host configured to operate in a communication system to provide an OTT service comprises processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a UE. The UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.

[0222] Embodiment 33. In the host of the previous embodiment, the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

[0223] Embodiment 34. In the host of the previous 2 embodiments, the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0224] Embodiment 35. A method implemented by a host operating in a communication system that further includes a network node and a UE comprises providing user data for the UE and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

[0225] Embodiment 36. The method of the previous embodiment further comprises, at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0226] Embodiment 37. The method of the previous embodiment further comprises, at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. [0227] Embodiment 38. A host configured to operate in a communication system to provide an OTT service, comprises processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a UE, wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0228] Embodiment 39. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0229] Embodiment 40. In the host of the previous 2 embodiments, the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0230] Embodiment 41. A method implemented by a host configured to operate in a communication system that further includes a network node and a UE, comprises, at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0231] Embodiment 42. The method of the previous embodiment further comprises, at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0232] Embodiment 43. The method of the previous embodiment further comprises, at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0233] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

3GPP 3rd Generation Partnership Project

5G 5th Generation

6G 6 ^th Generation

AMF Access and Mobility Management Function

AUSF Authentication Server Function

BCH Broadcast Channel • BSR Buffer Status Reporting

• CCCH Common Control Channel

• CDMA Code Division Multiplexing Access

• CG Configured Grant

• CG-SDT Small data transmissions using Configured Grant

• CPU Central Processing Unit

• CR-ID Contention Resolution Identification

• C-RNTI Cell Radio Network Temporary Identifier

• DCCH Dedicated Control Channel

• DCI Downlink Control Information

• DL Downlink

• DRB Data Radio Bearer

• DRX Discontinuous Reception

• DTX Discontinuous Transmission

• EDT Early Data Transmission

• eLCID extended Logical Channel Identification

• eNB evolved Node B

• ePDCCH Enhanced Physical Downlink Control Channel

• E-UTRA Evolved Universal Terrestrial Radio Access

• E-UTRAN Evolved Universal Terrestrial Radio Access Network

• FFS For Further Study

• FPGA Field Programmable Gate Arrays

• gNB New Radio Base Station

• GSM Global System for Mobile Communications

• HARQ Hybrid Automatic Repeat Request

• HSS Home Subscriber Server

• LCG Logical Channel Group

• LCH Logical channel

• LCID Logical Channel Identification

• LPWAN Low Power Wide Area Network

• LTE Long-Term Evolution

• LTE-M Long-Term Evolution for Machines

• MAC Medium Access Control • MAC Message Authentication Code

• MBB Mobile broadband

• MDT Minimization of Drive Tests

• MME Mobility Management Entity

• MO Mobile Originated

• MSC Mobile Switching Center

• NB-IoT Narrow Band Internet of Things

• NEF Network Exposure Function

• NF Network Function

• NFV Network Function Virtualization

• NR New Radio

• O&M Operation and Maintenance

• OSS Operations Support System

• OTT Over-the-Top

• PBCH Physical Broadcast Channel

• PDCCH Physical Downlink Control Channel

• PDCP Packet Data Convergence Protocol

• PDU Protocol Data Unit

• PRACH Physical Random Access Channel

• PRU PUSCH Resource Unit

• PUR Preconfigured Uplink Resources

• PUSCH Physical Uplink Shared Channel

• QoS Quality of Service

• R/LCID Reserved Fogical Channel Identifier

• RA Random Access

• RACH Random Access Channel

• RAI Release Assistance Information

• RAM Random Access Memory

• RAN Radio Access Network

• RAR Random Access Response

• RA-RNTI Random Access Radio Network Temporary Identifier

• RAT Radio Access Technology

• RLC Radio Fink Control RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

ROM Read Only Memory

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Symbol/Signal Received Power

SCH Synchronization Channel

SDT Small Data Transmissions

SEPP Security Edge Protection Proxy

SIDF Subscription Identifier De-concealing Function

SMF Session Management Function

SON Self Optimized Network

SRB Signaling Radio Bearer ss Synchronization Signal

SS/PBCH Synchronization Signal/Physical Broadcast Channel

TA Timing Advance

TC-RNTI Temporary Cell Radio Network Temporary Identifier

TMSI Temporary Mobile Subscriber Identity

UDM Unified Data Management

UE User Equipment

UF Uplink

UMTS Universal Mobile Telecommunications System

UPF User Plane Function

URFFC Ultra Reliable Fow Fatency Communication

USIM Universal Subscriber Identity Module

VM Virtual Machine

VR Virtual Reality

WCDMA Wide Code Division Multiplexing Access

WI Work Item

WEAN Wide Focal Area Network

WiMax Worldwide Interoperability for Microwave Access