RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application Serial Number 63/034,046 filed June 3, 2020, the disclosure of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] The present invention relates generally to wireless communication networks, and in particular to systems and methods of validating spatial domain filters in pre-configured resource grants prior to transmission in an inactive state.

BACKGROUND

[0003] Wireless communication networks, enabling voice and data communications to wireless devices, are ubiquitous in many parts of the world, and continue to advance in technological sophistication, system capacity, data rates, bandwidth, supported services, and the like. A basic model of one type of wireless network, generally known as “cellular,” features a plurality of generally fixed network nodes (known variously as base station, radio base station, base transceiver station, serving node, NodeB, eNobeB, eNB, gNB, and the like), each providing wireless communication service to a large plurality of wireless devices (known variously as mobile terminals, User Equipment or UE, and the like) within a generally fixed geographical area, known as a cell or sector.

[0004] Radio Resource Control (RRC) is an air interface protocol used in the 3rd generation (3G) mobile cellular wireless network protocol Universal Mobile Telecommunications System (UMTS), as well as the 4th generation (4G) protocol, Long Term Evolution (LTE). Modifications to RRC have been made for the 5th generation (5G) protocol, New Radio (NR).

[0005] In LTE, two general RRC states are defined for a UE: RRCJDLE and RRC_CONNECTED.

[0006] In LTE RRCJDLE state, a UE is known to the core network (CN or EPC), and has an Internet Protocol (IP) address, but is not known/tracked by the Radio Access Network (E- UTRAN/eNB). The UE can receive broadcast/multicast data (e.g., System Information, or SI); monitors a paging channel to detect incoming calls; may perform neighbor cell measurements; and can do cell (re)selection.

[0007] In the LTE RRC_CONNECTED state, the UE is known by the RAN (E-UTRAN/eNB), as well as the core network, and the mobility of the UE is managed by the network. The UE monitors control channels for downlink data, sends channel quality feedback, and may request uplink resources. Conventionally (i.e., prior to Rel-16), all user plane communications occurred in RRC_CONNECTED state. Accordingly, a UE was required to transition from RRCJDLE to RRC_CONNECTED for every data transfer between the UE and eNB. This required significant signaling overhead and power consumption, in particular for UEs that need to infrequently transmit small data packets, such as many Machine-Type Communications (MTC) devices. [0008] In LTE Rel-13 a mechanism was introduced for the UE to be suspended by the network in a suspended state, similar to RRCJDLE, but with the difference that the UE stored the Access Stratum (AS) context or RRC context. This made it possible to reduce the signaling when the UE again became active by resuming the RRC connection, instead of having to establish the RRC connection from scratch.

[0009] In Rel-15, 3GPP introduced a new radio-access technology known as New Radio (NR). The technology was further enhanced in Rel-16, and will continue to evolve in future releases. One aspect of NR is support for an RRCJNACTIVE state with similar properties as the suspended state in LTE Rel-13. The RRCJNACTIVE has slightly different properties from the LTE Rel-13 suspended state, in that it is a separate RRC state and not part of RRCJDLE, as in LTE. Additionally, the CN/RAN connection (NG or N2 interface) is kept for RRCJNACTIVE while it was suspended in LTE. Figure 1 depicts the possible RRC state transitions in NR.

[0010] In order to enable efficient transmission of small infrequent data packets, 3GPP has approved a Rel-17 work item on NR small data transmissions in RRCJNACTIVE state. See RP-193252 “New Work Item on NR small data transmissions in INACTIVE state.” Generally, a UE, while in RRC_CONNECTED state, is configured with one or more (periodic) grants on a time-frequency resource, such as a Physical Uplink Shared Channel (PUSHC). The UE then enters RRCJNACTIVE state, and can transmit small quantities of data, at the times of the configured grants, while remaining in RRCJNACTIVE state. This avoids the overhead signaling, and concomitant battery power, required to transition to RRC_CONNECETED state for each of these small, periodic transmissions.

[0011] One of the technical features of NR is operation in extremely high frequency ranges, such as 25-50 GHz. While these frequencies exploit unused spectrum and enable higher bit rates, they present unique challenges. These include a shorter transmission range for a given power, smaller antenna apertures, and atmospheric attenuation. For effective operation in high frequencies, NR includes support for beamforming. Beamforming employs a large number of antenna elements in an array. By individually controlling the phase and other signal characteristics to each antenna element, constructive interference increases signal gain in specific, desired directions, and destructive interference reduces or eliminates the signal in other directions, resulting in a highly directional antenna. Beamforming is employed in both RF signal transmission (Tx) and reception (Rx). Beamforming information (e.g., a spatial domain filter) may be indicated in the configuration provided to a UE in RRC_CONNECETED state, for its uplink data transmissions that occur in RRCJNACTIVE state.

[0012] However, since the mobility of UEs in RRCJNACTIVE state is not managed by the network, as the UE moves through a cell the beamforming information may no longer be valid. First, the UE’s Tx beam may no longer be directionally aimed at a gNB or other receiving antenna. Second, because the network is not tracking the UE location, the gNB cannot properly steer its Rx beam to capture the UE Tx. The combination may result in severely degraded performance.

[0013] The Background section of this document is provided to place embodiments of the present invention in technological and operational context, to assist those of skill in the art in understanding their scope and utility. Approaches described in the Background section could be pursued, but are not necessarily approaches that have been previously conceived or pursued. Unless explicitly identified as such, no statement herein is admitted to be prior art merely by its inclusion in the Background section. SUMMARY

[0014] The following presents a simplified summary of the disclosure in order to provide a basic understanding to those of skill in the art. This summary is not an extensive overview of the disclosure and is not intended to identify key/critical elements of embodiments of the invention or to delineate the scope of the invention. The sole purpose of this summary is to present some concepts disclosed herein in a simplified form as a prelude to the more detailed description that is presented later.

[0015] According to one or more embodiments described and claimed herein, the network configures a UE in RRC_CONNECETED state with one or more grants for periodic uplink transmissions on PUSCH when the UE is in RRCJNACTIVE state. The configuration may include numerous parameters, such as the periodicity of a recurring time-frequency resource identified in a grant and an indication of a Tx beam, also known as a spatial domain filter to use. Due to UE mobility within the cell, and the fact that the network does not manage the UE mobility in RRCJNACTIVE state, the Tx beam may no longer be valid at the time of the uplink Tx. Shortly prior to the time of the grant, the UE evaluates the Tx beam against predetermined validation criteria, such as the Reference Signal Received Power (RSRP) of a Synchronization Signal Block (SSB) that is spatially related (i.e., has a Rx beam corresponding to the configured Tx beam). If the RSRP is less than a configured threshold RSRP value, the UE declines to perform the uplink Tx, at least for that grant.

[0016] One embodiment relates to a method, performed by a wireless device operative in a wireless communication network (such as a User Equipment, or UE), of performing uplink transmissions (Tx). In Radio Resource Control (RRC) connected state, a pre-configured uplink resource (PUR) configuration is received from the network. The PUR configuration includes a first grant for at least a first future uplink Tx, wherein the first grant includes information identifying an uplink time-frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for at least the first future uplink Tx. In RRC inactive state, prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, a validity of the spatial domain filter indicated in the PUR configuration is evaluated against one or more predetermined validation criteria. In response to evaluating the spatial domain filter as valid, the uplink Tx is performed using the indicated spatial domain filter in RRC inactive state in the uplink time-frequency resource for the first future uplink Tx.

[0017] Another embodiment relates to a method, performed by a base station operative in a wireless communication network (such as a gNB), of pre-configuring a time-frequency resource for a wireless device to transmit in an inactive state. When the wireless device is in Radio Resource Control (RRC) connected state, a pre-configured uplink resource (PUR) configuration is transmitted to the wireless device. The PUR configuration includes a first grant for at least a first future uplink Tx, wherein the first grant includes information identifying an uplink time- frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for the uplink Tx. Prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, signals enabling the wireless device to evaluate a validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined validation criteria are transmitted. A signal transmitted by the wireless device in RRC inactive state is received if the wireless device evaluated the spatial domain filter indicated in the PUR configuration as valid.

[0018] Yet another embodiment relates to a wireless device operative in a wireless communication network (such as a User Equipment, or UE). The wireless device includes communication circuitry and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to, in Radio Resource Control (RRC) connected state, receive from the network a pre-configured uplink resource (PUR) configuration. The PUR configuration includes a first grant for at least a first future uplink Tx, wherein the first grant includes information identifying an uplink time-frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for at least the first future uplink Tx. The processing circuitry is further configured to, in RRC inactive state, prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, evaluate a validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined validation criteria. In response to evaluating the spatial domain filter as valid, the processing circuitry is configured to perform the uplink Tx using the indicated spatial domain filter in RRC inactive state in the uplink time-frequency resource for the first future uplink Tx. [0019] Still another embodiment relates to a base station operative in a wireless communication network (such as a gNB). The base station includes communication circuitry and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to, when a wireless device is in Radio Resource Control (RRC) connected state, transmit to the wireless device a pre-configured uplink resource (PUR) configuration. The PUR configuration includes a first grant for at least a first future uplink Tx, wherein the first grant includes information identifying an uplink time-frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for the uplink Tx. The processing circuitry is further configured to, prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, transmit signals enabling the wireless device to evaluate a validity of the spatial domain filter identified in the PUR configuration against one or more predetermined validation criteria. The processing circuitry is still further configured to receive a signal transmitted by the wireless device in RRC inactive state, if the wireless device evaluated the spatial domain filter identified in the PUR configuration as valid.

[0020] Still another embodiment relates to a computer readable medium having thereon instructions operative to cause processing circuitry of a wireless device operative in a wireless communication network to perform uplink transmissions, Tx, by performing the steps of: in Radio Resource Control (RRC) connected state, receiving from the network a pre-configured uplink resource (PUR) configuration including a first grant for at least a first future uplink Tx, wherein the first grant includes information identifying an uplink time-frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for the uplink Tx for at least the first future uplink Tx; in RRC inactive state, prior to uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, evaluating a validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined validation criteria; and in response to evaluating the spatial domain filter as valid, performing the uplink Tx using the indicated spatial domain filter in RRC inactive state in the uplink time-frequency resource for the first future uplink Tx.

[0021] Still another embodiment relates to a computer program comprising instructions which, when executed by processing circuitry of a wireless device operative in a wireless communication network, causes the wireless device to carry out a method of performing uplink transmissions as described and claimed herein.

[0022] Still another embodiment relates to a computer readable medium having thereon instructions operative to cause processing circuitry of a base station operative in a wireless communication network to pre-configuring a time-frequency resource for a wireless device to transmit in an inactive state, by performing the steps of: when the wireless device is in Radio Resource Control (RRC) connected state, transmitting to the wireless device a pre-configured uplink resource (PUR) configuration including a first grant for at least a first future uplink transmission, Tx, wherein the first grant includes information identifying an uplink time- frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for the uplink Tx; prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, transmitting signals enabling the wireless device to evaluate a validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined validation criteria; and receiving a signal transmitted by the wireless device in RRC inactive state, if the wireless device evaluated the spatial domain filter indicated in the PUR configuration as valid.

[0023] Still another embodiment relates to a computer program comprising instructions which, when executed by processing circuitry of a base station operative in a wireless communication network, causes the base station to carry out a method of pre-configuring a time-frequency resource for a wireless device to transmit in an inactive state as described and claimed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. However, this invention should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. [0025] Figure 1 is an RRC state diagram for NR.

[0026] Figure 2A is a diagram of a wireless device in a cell when being pre-configured for transmissions in an inactive state.

[0027] Figure 2B is a diagram of the wireless device of Figure 2A having moved in the cell so its pre-configured beams are no longer valid.

[0028] Figure 3 is a timeline of a wireless device receiving a pre-configuration in connected state, and transmitting in inactive state.

[0029] Figure 4 is a flow diagram of a method of performing uplink transmissions by a wireless device.

[0030] Figure 5 is a flow diagram of a method of receiving uplink transmissions by a base station.

[0031] Figure 6 is a hardware block diagram of a wireless device, such as a UE.

[0032] Figure 7 is a functional block diagram of a wireless device, such as a UE.

[0033] Figure 8 is a hardware block diagram of a network node, such as a base station.

[0034] Figure 9 is a functional block diagram of a network node, such as a base station.

[0035] Figure 10 is a diagram of a wireless communication network and some nodes.

[0036] Figure 11 is a block diagram of a UE.

[0037] Figure 12 is a schematic block diagram illustrating a virtualization environment.

[0038] Figure 13 illustrates a telecommunication network connected via an intermediate network to a host computer.

[0039] Figure 14 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection.

[0040] Figure 15 is a flowchart illustrating a method implemented in a communication system according to one embodiment.

[0041] Figure 16 is a flowchart illustrating a method implemented in a communication system according to another embodiment.

[0042] Figure 17 is a flowchart illustrating a method implemented in a communication system according to another embodiment. [0043] Figure 18 is a flowchart illustrating a method implemented in a communication system according to another embodiment.

DETAILED DESCRIPTION

[0044] For simplicity and illustrative purposes, the present invention is described by referring mainly to an exemplary embodiment thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be readily apparent to one of ordinary skill in the art that the present invention may be practiced without limitation to these specific details. In this description, well known methods and structures have not been described in detail so as not to unnecessarily obscure the present invention.

[0045] As described above, the 3GPP work item RP-193252, “New Work Item on NR small data transmissions in INACTIVE state,” identifies the following objective:

• Transmission of UL data on pre-configured PUSCH resources (i.e. reusing the configured grant type-1) - when Timing Advance (TA) is valid o General procedure for small data transmission over configured grant type-1 resources from inactive state o Configuration of the configured grant type-1 resources for small data transmission in uplink for inactive state

[0046] Pre-configuration of PUSCH resources in RRCJNACTIVE state is particularly useful for transmission of periodic data traffic, such as periodic positioning information from wearables, periodic reporting from sensors, periodic readings from smart meters, and the like. As stated in RP-193252, this feature will partly be built on the configured grant type-1 that has already been specified in Rel-15. In configured grant type-1 , an uplink grant is provided by RRC configuration. The configuration contains the full set of information needed to make use of a periodically occurring PUSCH resource. However, the configured grant type-1 is applicable only in RRC_CONNECETED state; the pre-configured PUSCH will be valid in RRCJNACTIVE state. Also, the maximum periodicity of configured grant type-1 is only 640 ms. The periodicity of a pre-configured PUSCH is expected to be much larger.

[0047] NR is designed to be deployed in a wide range of frequencies. Due to the differences in how radio frequency (RF) requirements are defined, currently in 3GPP, the frequencies that NR supports are divided into two frequency ranges. Frequency Range 1 (FR1) includes all bands below 7.12 GHz. Frequency Range 2 (FR2) includes all bands in the range 24.25 — 52.6 GHz. Radio communications in FR2 is particularly challenging due to shorter range, higher environmental attenuation, and smaller antenna apertures, which limits the network coverage. As described above, this limitation is partly overcome in NR by having support for beamforming, which employs a large number of small antenna elements to selectively steer RF beams in desired directions. Due to implementation constraints at higher frequencies, it is likely that only analog beamforming is supported at the UE and the gNB, at least initially. Analog beamforming only allows to transmit (Tx) or receive (Rx) in one direction at a given time instant. Accordingly, beam management procedures have been specified in NR to assist the UE to select a suitable Rx/Tx beam for transmission.

[0048] In NR, initial cell search is based on a Synchronization Signal Block (SSB) consisting of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS) and a Physical Broadcast Channel (PBCH). To enable cell wide coverage, SSBs are transmitted by the gNB in sequence in different downlink beams. In RRCJDLE and RRCJNACTIVE states, the UE autonomously adjusts its Rx beam (also known as a spatial domain Rx filter) to receive a certain SSB. The same Rx beam is then used by the UE for the reception of system information, paging, and Msg2 and Msg4 of a Re-Authorization Request (RAR). For the uplink transmission of Msg1 on the Physical Random Access Channel (PRACH), the RAN1 specification does not explicitly mandate the UE to use any specific Tx beam (or spatial domain Tx filter). In practice, however, it is likely that the UE would select its Tx beam based on the Rx beam it used to acquire the SSB. The subsequent transmission of Msg3 (on the PUSCH) would then use the same Tx beam as Msg1.

[0049] While in RRC_CONNECTED state, the network may provide the UE with explicit instruction on how it should select its Tx beam. This instruction is provided to the UE via spatial relation. If the network configures an uplink reference signal A, e.g., sounding reference signal (SRS), with spatial relation to a downlink reference signal B, e.g., SSB or channel state information reference signal (CSI-RS), then the UE should use the same (or similar) beam for transmitting A as it used to receive B. The spatial relation for A can also be configured to be another SRS. If the spatial relation is a downlink reference signal, then the UE should have beam correspondence capability, i.e., the capability of the UE to determine uplink Tx beam based on the downlink Rx beam. Otherwise, the UE may have to rely on SRS beam sweeping to determine a suitable Tx beam.

[0050] For the transmission of a Physical Uplink Control Channel (PUCCH), the network may RRC configure the UE with up to 64 spatial relations. One of these 64 spatial relations is then activated using a Control Element in the Media Access Control (MAC-CE). For instance, if SSB beams are configured as the PUCCH spatial relation, as a UE moves to the coverage area of a new SSB beam within the cell, a MAC-CE activates a spatial relation corresponding to the new SSB beam. For PUSCH, on the other hand, the spatial relation is based on the spatial relation configured for the transmission of an SRS resource in an SRS resource set. That is, the UE would transmit on PUSCH using the same beam as the spatially related SRS resource. To specify which SRS resource to use for PUSCH spatial relation, the UE is either dynamically indicated (if scheduled using Downlink Control Information, DCI, format 0_1) or configured (for configured grant type-1) with an SRS resource indicator (SRI). Each SRI may correspond to a different UE Tx beam, and is needed only when more than one SRS resource is in the SRS resource set.

[0051] For configured grant type-1 , the UE is configured with all the parameters necessary to transmit on a periodically occurring PUSCH resource. These parameters include the time- frequency resource and periodicity of the grant, link quality parameters (MCS, TBS and repetition of the TBS), power control parameters (pathloss reference signal index), and beam related parameters (SRI, precoder and layer indication). As the UE moves within the cell, the parameters provided in the configured grant may need to be reconfigured. In order to track the movement of the UE, the gNB may perform uplink measurements, e.g., based on SRS, or may configure the UE to send Reference Signal Received Power (RSRP) reports based on downlink measurements, e.g., based on SSB or CSI-RS. These measurements will also help the gNB to determine a suitable Rx beam for the reception of PUSCH.

[0052] In the case of single-port transmission of PUSCH, or PUSCH scheduled using DCI format 0_0 where there is no SRI field, the UE will transmit PUSCH using the same spatial relation as the PUCCH resource with the lowest ID. See 3GPP TS 38.214, “Physical layer procedures for data” v16.1.0, March 2020.

[0053] Another feature related to the NR Rel-17 pre-configured PUSCH feature is the Rel-16 pre-configured uplink resources (PUR), which has been introduced for LTE-Machine (LTE-M) and NarrowBand Internet of Things (NB-loT). In PUR, the UE is pre-configured with PUSCH resources in the RRC_CONNECTED state via RRC signaling. Then later in RRCJDLE state, the UE can transmit over PUSCH if the PUR validation methods determine the TA is still valid. The TA validation methods can be based on, for example, RSRP, TA timer, or the like. It is likely that the Rel-17 NR feature will inherit some of the characteristics of PUR. However, unlike NR, which provides support for analog beamforming via the beam management framework, LTE-M and NB-loT do not provide any such support, as they are not designed for millimeter wave spectrum.

[0054] The PUSCH transmission on configured grant type-1 takes place in RRC_CONNECTED state. This provides the gNB the ability to handle UE movement within the cell. For this purpose, the gNB may rely on periodic SRS transmissions or periodic reports based on SSB/CSI-RS from the UE. For beam management purposes, the report quantity is (layer-1) RSRP. The UE can be configured to report RSRP of up to four previously transmitted SSB or CSI-RS. Based on these measurements/reports, the network may decide to reconfigure, among other parameters, the Tx beam of the UE by providing a new value of the SRI. These measurements will also help the gNB to update its Rx beam for the reception of PUSCH as the UE moves. Since the maximum periodicity of configured grant type-1 is only 640 ms, it is likely that there may not be large changes in the suitable beams between any two consecutive PUSCH occasions.

[0055] In the Rel-17 preconfigured PUSCH feature, it is expected that the UE is configured with an uplink grant in RRC_CONNECTED state. The UE then moves to RRCJNACTIVE state, from which it can transmit periodically on the PUSCH resource, if TA is valid. The periodicity of grant can be much larger than that of configured grant type-1 - typically in the order of several minutes or hours. It may, however, be problematic if the UE is allowed to transmit after validating only the TA. The reason is that in RRCJNACTIVE state, it is not possible for the gNB to track the movement of the UE, as there are no SRS transmissions or measurement reports available from the UE. The mobility is handled by the UE on its own, based on RSRP measurements performed on SSB transmissions.

[0056] Therefore, if the UE moves, there is no information at the gNB on where in the cell, or to which SSB beam, the UE has moved. As a consequence, the gNB would not be able to update its Rx beam for the reception of an uplink Tx using pre-configured PUSCH. Furthermore, the configured uplink Tx beam of the UE may not be suitable to use from the UE’s new position (or new SSB beam). This is because, in practice, it is the Rx beam direction and a corresponding Tx beam direction jointly - that is, a beam pair, rather than individual Rx/Tx beams - that determines a good transmission direction.

[0057] Figure 2A depicts a UE configured with an SRS resource set containing three SRS resources, having indices SRI = 1 , SRI = 2 and SRI = 3. The index of an SSB transmission is referred using SSB resource indicator (SSBRI). The spatial relations for SRI = 1 , SRI = 2 and SRI = 3 are SSBRI = 1 , SSBRI = 2, SSBRI = 3, respectively. When UE is at the position depicted, the beam pair corresponding to SRI=1 and SSBRI=1 is the best in terms of RSRP measured at the UE. Therefore, when the gNB configures the UE with preconfigured PUSCH in RRC_CONNECTED state, it selects SRI=1. So long as the UE remains at this position, it would use SRI=1 for uplink transmission in RRCJNACTIVE state.

[0058] Figure 2B depicts the same UE, with the same configuration, but the UE has moved within the cell. As a consequence, its spatial relationship with the gNB has changed. If TA is valid, the UE transmits on pre-configured PUSCH using the Tx beam corresponding to SRI=1 , and gNB uses the Rx beam corresponding to SSBRI=1. At this position, however, the beam pair corresponding to SRI=1 and SSBRI=1 is no longer suitable for transmission.

[0059] Accordingly, if the existing beam management procedure for configured grant type-1 is applied to the Rel-17 preconfigured PUSCH feature in RRCJNACTIVE state, there may be a significant degradation in the performance if the UE moves. In some cases, the UE may not be able to satisfy the PUSCH initial block error rate requirement of 10%.

[0060] According to embodiments of the present invention, a beam validation procedure is employed in RRCJNACTIVE state to handle the situation where the Tx beam at the UE and the Rx beam at the gNB have become outdated, such as due to the movement of the UE (or other reason, such as blockage moving between the UE and gNB). The procedure is primarily directed to the Rel-17 preconfigured PUSCH feature. Additionally, a procedure is described for validating the uplink Tx and Rx beams, at the UE, based on RSRP. If the UE evaluates the beams (or beam pair) as invalid, it may not transmit on the preconfigured resource. Instead, it may perform other actions, e.g., fallback to legacy random access procedures, skip the upcoming preconfigured PUSCH occasion, request a new pre-configured PUR configuration, or the like.

[0061] Figure 3 depicts a timeline showing the beam validation procedure. Initially (at the left), the UE is in RRC_CONNECTED state. In this state, at time To the network provides a configuration to the UE, via RRC signaling. The configuration identifies the time-frequency resource (e.g. , PUSCH) and includes at least one future uplink Tx grant, scheduled for time T i . The grant may be recurring, with a periodicity T _period . The configuration may additionally include a TA value, and an SRI. The value of SRI, for example SRI = u, identifies the PUSCH Tx beam. The spatial relation of the SRS resource corresponding to SRI = u is configured as an SSB beam with SSBRI = d.

[0062] At some time after receiving the configuration, the UE transitions to RRCJNACTIVE state. While in RRCJNACTIVE state, but prior to the time-frequency resource (e.g., PUSCH) associated with the pre-configured grant at time Ti, the UE prepares for the PUSCH transmission at time Ti. As part of this preparation, the UE verifies the validity of the beams using one or more beam validation criteria. If the UE evaluates the beam as valid, it will proceed with the PUSCH transmission (provided TA is also valid). Otherwise, it will not perform the transmission, and may instead perform other actions, e.g., fallback to legacy random access procedure to get a new configuration, skip only the upcoming pre-configured PUSCH grant, or the like.

[0063] For certain small cells TA can be configured as valid in the entire cell, as the cyclic prefix in NR will be able to provide protection against timing misalignment at the gNB. Even for these cells, however, beam-sweeping may be required to provide coverage to the entire cell, which implies that the same beam is not valid in the entire cell. Therefore, it is important that the UE transmits on pre-configured PUSCH only if both the TA and the uplink Tx beam are valid. [0064] In one embodiment, one of the beam validation criteria is based on measured Reference Signal Received Power (RSRP) at the UE. In particular, at T ₀ the UE is configured with a RSRP threshold, RSRP _Th . At another time instance Ti’ in inactive state, where TT< Ti, the UE performs an RSRP measurement, RSRP(d, Ti’), on the SSB beam with SSBRI = d. The UE evaluates the beam as valid if the RSRP value at Ti’ is equal to or greater than RSRP _Th ., i.e, RSRP(d, Ti’) > RSRP _Th . Otherwise, i.e., if RSRP(d, Ti’) < RSRP _Th , the beam is evaluated as invalid. Note that the SSB with indicator d is used for beam validation because of its spatial relation to the SRS resource with indicator u. Therefore, this beam validation criterion is, in fact, validating the uplink beam pair to be used for the PUSCH transmission.

[0065] An SRI is needed only when more than one SRS resource is in the SRS resource set configured by the network. If the UE is not configured with any SRI at the time of configuring the PUSCH resource, the spatial relation of the single SRS resource in the SRS resource set determines the Tx beam for PUSCH. The beam validation procedure described above applies to this case as well.

[0066] In one embodiment, if SRI = u does not have a spatial relation configured, or if the spatial relation of this SRI is another SRS resource, the network explicitly configures the SSBRI that the UE should use to validate the beam. In another embodiment, if SSBRI is not explicitly configured, the UE defaults to use, for beam validation, the SSBRI corresponding to the path- loss reference signal configured at T ₀ for PUSCH power control.

[0067] In one embodiment, if the UE evaluates the uplink Tx beam as invalid based on the configured beam validation criteria, the preconfigured PUSCH resource is considered as released.

[0068] In one embodiment, the UE is configured to validate the uplink Tx beam based on a set of downlink SSB beams. In this embodiment, the UE evaluates the beam as invalid only if the RSRP of all of the configured SSB beams fall below the threshold RSRP _Th . Otherwise, the UE transmits on the preconfigured PUSCH resource using the SRI with a spatial relation to the strongest SSB beam. [0069] Those of skill in the art will readily recognize that, although the beam validation procedures are described herein based on SSB transmissions and SSB beams, they can alternatively be based on other types of downlink reference signal transmissions and beams (e.g., Channel State Information Reference Signal, or CSI-RS).

[0070] If no beam validation criteria are configured at T ₀ , the uplink Tx beam is considered implicitly valid in the entire cell. In this case, the UE can skip the beam validation check prior to performing the uplink Tx on a preconfigured PUSCH resource.

[0071] In one embodiment the UE is configured with multiple grants for RRCJNACTIVE state PUSCH transmission, with each grant containing a unique SRI that corresponds to a unique SRS resource, which is spatially related to a unique downlink RS. The UE determines which of the multiple grants to use based on downlink RSRP measurements on the set of downlink RS associated with the configured multiple grants. The PUSCH uplink Tx is based on the grant which contains the SRI that is associated with the strongest downlink RSRP.

[0072] In one embodiment, if the UE detects a new RS that is stronger than any one of the RSs on which the UE is to perform RSRP measurements, the UE refrains from using a configured grant for RRCJNACTIVE state PUSCH uplink Tx.

[0073] In one embodiment, the time-frequency resource and the periodicity of the grant T _pe rio _d configured for the UE are dependent on the periodicity of the Physical Random Access Channel (PRACH) resource, which is associated with the same SSB for which the UE is configured for beam validation purposes. That is, the periodicity of the pre-configured PUSCH transmission for a UE is configured as a multiple of the PRACH periodicity, and the PRACH and the PUSCH resources are multiplexed in frequency. This ensures that the PRACH and the pre-configured PUSCH uplink Tx can be received by the gNB using the same Rx beam. In this embodiment, the start occasion of the pre-configured PUSCH and PRACH are configured in such a way that they can be received using the same Rx beam.

Methods

[0074] Figure 4 depicts the steps in a method 100 of performing uplink transmissions (Tx) by a wireless device, such as a UE, operative in a wireless communication network. Initially, at block 102, the UE is in RRC_CONNECTED state. A pre-configured uplink resource (PUR) configuration is received from the network (block 102). The PUR configuration includes a first grant for at least a first future uplink Tx, wherein the first grant includes information identifying an uplink time-frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for at least the first future uplink Tx.

[0075] As indicated by the dashed line, the wireless device then moves into RRCJNACTIVE state. Prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, a validity of the spatial domain filter indicated in the PUR configuration is evaluated against one or more predetermined validation criteria (block 104). In response to evaluating the spatial domain filter as valid (block 106), the uplink Tx is performed using the indicated spatial domain filter in RRCJNACTIVE state in the uplink time-frequency resource for the first future uplink Tx (block 108). In one embodiment (as indicated by the dashed-line block 110), in response to evaluating the spatial domain filter as invalid (block 106), the UE performs an action other than the uplink Tx in the uplink time-frequency resource for the first future uplink Tx (block 110).

[0076] Figure 5 depicts the steps in a corresponding method 200 of pre-configuring a time- frequency resource for a wireless device to transmit in an inactive state, performed by a base station, such as a gNB, operative in a wireless communication network. Initially, at block 202, the wireless device is in RRC_CONNECTED state. A pre-configured uplink resource (PUR) configuration including a first grant for at least a first future uplink transmission, Tx, is transmitted to the wireless device (block 202). The first grant includes information identifying an uplink time-frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for the uplink Tx.

[0077] As indicated by the dashed line, the wireless device then moves into RRCJNACTIVE state. Prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, signals enabling the wireless device to evaluate a validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined criteria are transmitted to the wireless device (block 204). In dependence on whether the wireless device evaluates the spatial domain filter as valid (block 206), the uplink signal transmitted by the wireless device in RRCJNACTIVE state in the uplink time-frequency resource for the first future uplink Tx is received (block 208), or not (block 210).

Apparatuses

[0078] Apparatuses described herein may perform the methods 100, 200 herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

[0079] Figure 6 for example illustrates a hardware block diagram wireless device 10 (e.g., a UE) as implemented in accordance with one or more embodiments. As shown, the wireless device 10 includes processing circuitry 12 and communication circuitry 16. The communication circuitry 16 (e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas 18 that are either internal or external to the wireless device 10. The processing circuitry 12 is configured to perform processing described above, such as by executing instructions stored in memory 14. The processing circuitry 12 in this regard may implement certain functional means, units, or modules. [0080] Figure 7 illustrates a functional block diagram of a wireless device 20 in a wireless network according to still other embodiments (for example, the wireless network shown in Figure 10). As shown, the wireless device 20 implements various functional means, units, or modules, e.g., via the processing circuitry 12 in Figure 6 and/or via software code. These functional means, units, or modules, e.g., for implementing method 100 herein, include for instance a PUR configuration receiving unit 22, a spatial domain filter evaluating unit 24, and an uplink signal transmitting unit 26.

[0081] The PUR configuration receiving unit 22 is configured to, in RRC_CONNECTED state, receive from the network a pre-configured uplink resource (PUR) configuration including a first grant for at least a first future uplink Tx, wherein the first grant includes information identifying an uplink time-frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for at least the first future uplink Tx. The spatial domain filter evaluating unit 24 is configured to, in RRCJNACTIVE state, prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, evaluate a validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined validation criteria. The uplink signal transmitting unit 26 is configured to, in response to evaluating the spatial domain filter as valid, perform the uplink Tx using the indicated spatial domain filter in RRCJNACTIVE state in the uplink time-frequency resource for the first future uplink Tx; and in response to evaluating the spatial domain filter as invalid, perform an action other than the uplink Tx in the uplink time-frequency resource for the first future uplink Tx.

[0082] Figure 8 illustrates a hardware block diagram of a network node 40 as implemented in accordance with one or more embodiments. The network node 40 implements base station functionality, e.g., a gNB in NR. As shown, the network node 40 includes processing circuitry 42 and communication circuitry 46. The communication circuitry 46 is configured to transmit and/or receive information to and/or from one or more wireless devices and/or other network nodes, e.g., via any communication technology. The communication circuitry 46 communicates with wireless devices wirelessly via one or more antennas 48. As indicated by the broken line, the antennas 48 may be located remotely from the network node 40, such as on a tower or building. The processing circuitry 42 is configured to perform processing described above, such as by executing instructions stored in memory 44. The processing circuitry 42 in this regard may implement certain functional means, units, or modules.

[0083] Figure 9 illustrates a functional block diagram of a network node 50 in a wireless network according to still other embodiments (for example, the wireless network shown in Figure 10). As shown, the network node 50 implements various functional means, units, or modules, e.g., via the processing circuitry 42 in Figure 8 and/or via software code. These functional means, units, or modules, e.g., for implementing the method 200 herein, include for instance: PUR configuration transmitting unit 52, evaluation signal transmitting unit 54, and uplink signal receiving unit 56.

[0084] The PUR configuration transmitting unit 52 is configured to, when the wireless device is in RRC_CONNECTED state, transmit to the wireless device a pre-configured uplink resource (PUR) configuration including a first grant for at least a first future uplink Tx, wherein the first grant includes information identifying an uplink time-frequency resource for a first future uplink Tx, and an indication of a spatial domain filter for the uplink Tx. The evaluation signal transmitting unit 54 is configured to, prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, transmit signals enabling the wireless device to evaluate a validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined validation criteria. The uplink signal receiving unit 56 is configured to receive a signal transmitted by the wireless device in RRCJNACTIVE state in the uplink time- frequency resource for the first future uplink Tx if the wireless device evaluated the spatial domain filter identified in the PUR configuration as valid, and not to receive an uplink signal in the uplink time-frequency resource for the first future uplink Tx if the wireless device evaluated the spatial domain filter identified in the PUR configuration as invalid.

[0085] Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

[0086] A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above. [0087] Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0088] In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

[0089] Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

[0090] Additional embodiments will now be described. At least some of these embodiments may be described as applicable in certain contexts and/or wireless network types for illustrative purposes, but the embodiments are similarly applicable in other contexts and/or wireless network types not explicitly described.

Network Description and Over the Top Implementations

[0091] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 10. For simplicity, the wireless network of Figure 10 only depicts network 1106, network nodes 1160 and 1160b, and wireless devices (WD) 1110, 1110b, and 1110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 1160 and WD 1110 are depicted with additional detail.

The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network. [0092] The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-loT), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

[0093] Network 1106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0094] Network node 1160 and WD 1110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, 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.

[0095] As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless 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) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also 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). Yet further examples of network nodes include 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), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

[0096] In Figure 10, network node 1160 includes processing circuitry 1170, device readable medium 1180, interface 1190, auxiliary equipment 1184, power source 1186, power circuitry 1187, and antenna 1162. Although network node 1160 illustrated in the example wireless network of Figure 10 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 1160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component ( e.g ., device readable medium 1180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0097] Similarly, network node 1160 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 network node 1160 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 NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 1160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 1180 for the different RATs) and some components may be reused (e.g., the same antenna 1162 may be shared by the RATs). Network node 1160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1160, such as, for example, GSM, WCDMA, LTE,

NR, WiFi, 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 1160. [0098] Processing circuitry 1170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 1170 may include processing information obtained by processing circuitry 1170 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.

[0099] Processing circuitry 1170 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 1160 components, such as device readable medium 1180, network node 1160 functionality. For example, processing circuitry 1170 may execute instructions stored in device readable medium 1180 or in memory within processing circuitry 1170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1170 may include a system on a chip (SOC).

[00100] In some embodiments, processing circuitry 1170 may include one or more of radio frequency (RF) transceiver circuitry 1172 and baseband processing circuitry 1174. In some embodiments, radio frequency (RF) transceiver circuitry 1172 and baseband processing circuitry 1174 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 1172 and baseband processing circuitry 1174 may be on the same chip or set of chips, boards, or units [00101] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 1170 executing instructions stored on device readable medium 1180 or memory within processing circuitry 1170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 1170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1170 alone or to other components of network node 1160, but are enjoyed by network node 1160 as a whole, and/or by end users and the wireless network generally.

[00102] Device readable medium 1180 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 processing circuitry 1170. Device readable medium 1180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1170 and, utilized by network node 1160. Device readable medium 1180 may be used to store any calculations made by processing circuitry 1170 and/or any data received via interface 1190. In some embodiments, processing circuitry 1170 and device readable medium 1180 may be considered to be integrated.

[00103] Interface 1190 is used in the wired or wireless communication of signalling and/or data between network node 1160, network 1106, and/or WDs 1110. As illustrated, interface 1190 comprises port(s)/terminal(s) 1194 to send and receive data, for example to and from network 1106 over a wired connection. Interface 1190 also includes radio front end circuitry 1192 that may be coupled to, or in certain embodiments a part of, antenna 1162. Radio front end circuitry 1192 comprises filters 1198 and amplifiers 1196. Radio front end circuitry 1192 may be connected to antenna 1162 and processing circuitry 1170. Radio front end circuitry may be configured to condition signals communicated between antenna 1162 and processing circuitry 1170. Radio front end circuitry 1192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1198 and/or amplifiers 1196. The radio signal may then be transmitted via antenna 1162. Similarly, when receiving data, antenna 1162 may collect radio signals which are then converted into digital data by radio front end circuitry 1192. The digital data may be passed to processing circuitry 1170. In other embodiments, the interface may comprise different components and/or different combinations of components.

[00104] In certain alternative embodiments, network node 1160 may not include separate radio front end circuitry 1192, instead, processing circuitry 1170 may comprise radio front end circuitry and may be connected to antenna 1162 without separate radio front end circuitry 1192. Similarly, in some embodiments, all or some of RF transceiver circuitry 1172 may be considered a part of interface 1190. In still other embodiments, interface 1190 may include one or more ports or terminals 1194, radio front end circuitry 1192, and RF transceiver circuitry 1172, as part of a radio unit (not shown), and interface 1190 may communicate with baseband processing circuitry 1174, which is part of a digital unit (not shown).

[00105] Antenna 1162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1162 may be coupled to radio front end circuitry 1190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 1162 may be separate from network node 1160 and may be connectable to network node 1160 through an interface or port.

[00106] Antenna 1162, interface 1190, and/or processing circuitry 1170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1162, interface 1190, and/or processing circuitry 1170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

[00107] Power circuitry 1187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 1160 with power for performing the functionality described herein. Power circuitry 1187 may receive power from power source 1186. Power source 1186 and/or power circuitry 1187 may be configured to provide power to the various components of network node 1160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1186 may either be included in, or external to, power circuitry 1187 and/or network node 1160. For example, network node 1160 may be connectable to an external power source ( e.g ., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 1187. As a further example, power source 1186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

[00108] Alternative embodiments of network node 1160 may include additional components beyond those shown in Figure 10 that may be responsible 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, network node 1160 may include user interface equipment to allow input of information into network node 1160 and to allow output of information from network node 1160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1160.

[00109] As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD 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 WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[00110] As illustrated, wireless device 1110 includes antenna 1111 , interface 1114, processing circuitry 1120, device readable medium 1130, user interface equipment 1132, auxiliary equipment 1134, power source 1136 and power circuitry 1137. WD 1110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-loT, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 1110. [00111] Antenna 1111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1114. In certain alternative embodiments, antenna 1111 may be separate from WD 1110 and be connectable to WD 1110 through an interface or port. Antenna 1111 , interface 1114, and/or processing circuitry 1120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 1111 may be considered an interface.

[00112] As illustrated, interface 1114 comprises radio front end circuitry 1112 and antenna

1111. Radio front end circuitry 1112 comprise one or more filters 1118 and amplifiers 1116. Radio front end circuitry 1114 is connected to antenna 1111 and processing circuitry 1120, and is configured to condition signals communicated between antenna 1111 and processing circuitry 1120. Radio front end circuitry 1112 may be coupled to or a part of antenna 1111. In some embodiments, WD 1110 may not include separate radio front end circuitry 1112; rather, processing circuitry 1120 may comprise radio front end circuitry and may be connected to antenna 1111. Similarly, in some embodiments, some or all of RF transceiver circuitry 1122 may be considered a part of interface 1114. Radio front end circuitry 1112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1118 and/or amplifiers 1116. The radio signal may then be transmitted via antenna 1111. Similarly, when receiving data, antenna 1111 may collect radio signals which are then converted into digital data by radio front end circuitry

1112. The digital data may be passed to processing circuitry 1120. In other embodiments, the interface may comprise different components and/or different combinations of components.

[00113] Processing circuitry 1120 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 WD 1110 components, such as device readable medium 1130, WD 1110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1120 may execute instructions stored in device readable medium 1130 or in memory within processing circuitry 1120 to provide the functionality disclosed herein.

[00114] As illustrated, processing circuitry 1120 includes one or more of RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1120 of WD 1110 may comprise a SOC. In some embodiments, RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1124 and application processing circuitry 1126 may be combined into one chip or set of chips, and RF transceiver circuitry 1122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1122 and baseband processing circuitry 1124 may be on the same chip or set of chips, and application processing circuitry 1126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 1122 may be a part of interface 1114. RF transceiver circuitry 1122 may condition RF signals for processing circuitry 1120.

[00115] In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 1120 executing instructions stored on device readable medium 1130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1120 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 device readable storage medium or not, processing circuitry 1120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1120 alone or to other components of WD 1110, but are enjoyed by WD 1110 as a whole, and/or by end users and the wireless network generally. [00116] Processing circuitry 1120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 1120, may include processing information obtained by processing circuitry 1120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1110, 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.

[00117] Device readable medium 1130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 1120. Device readable medium 1130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., 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 processing circuitry 1120. In some embodiments, processing circuitry 1120 and device readable medium 1130 may be considered to be integrated.

[00118] User interface equipment 1132 may provide components that allow for a human user to interact with WD 1110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 1132 may be operable to produce output to the user and to allow the user to provide input to WD 1110. The type of interaction may vary depending on the type of user interface equipment 1132 installed in WD 1110. For example, if WD 1110 is a smart phone, the interaction may be via a touch screen; if WD 1110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 1132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1132 is configured to allow input of information into WD 1110, and is connected to processing circuitry 1120 to allow processing circuitry 1120 to process the input information. User interface equipment 1132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 1132 is also configured to allow output of information from WD 1110, and to allow processing circuitry 1120 to output information from WD 1110. User interface equipment 1132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 1132, WD 1110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

[00119] Auxiliary equipment 1134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 1134 may vary depending on the embodiment and/or scenario.

[00120] Power source 1136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 1110 may further comprise power circuitry 1137 for delivering power from power source 1136 to the various parts of WD 1110 which need power from power source 1136 to carry out any functionality described or indicated herein. Power circuitry 1137 may in certain embodiments comprise power management circuitry. Power circuitry 1137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 1137 may also in certain embodiments be operable to deliver power from an external power source to power source 1136. This may be, for example, for the charging of power source 1136. Power circuitry 1137 may perform any formatting, converting, or other modification to the power from power source 1136 to make the power suitable for the respective components of WD 1110 to which power is supplied. [00121] Figure 11 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or 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). UE 1200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 1200, as illustrated in Figure 11, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 11 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[00122] In Figure 11 , UE 1200 includes processing circuitry 1201 that is operatively coupled to input/output interface 1205, radio frequency (RF) interface 1209, network connection interface 1211 , memory 1215 including random access memory (RAM) 1217, read-only memory (ROM) 1219, and storage medium 1221 or the like, communication subsystem 1231 , power source 1233, and/or any other component, or any combination thereof. Storage medium 1221 includes operating system 1223, application program 1225, and data 1227. In other embodiments, storage medium 1221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 11 , or only a subset of the components. 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.

[00123] In Figure 11 , processing circuitry 1201 may be configured to process computer instructions and data. Processing circuitry 1201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, 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 1201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[00124] In the depicted embodiment, input/output interface 1205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 1200 may be configured to use an output device via input/output interface 1205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 1200. The output device may be 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. UE 1200 may be configured to use an input device via input/output interface 1205 to allow a user to capture information into UE 1200. The input device may 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, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[00125] In Figure 11 , RF interface 1209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1211 may be configured to provide a communication interface to network 1243a. Network 1243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1243a may comprise a Wi-Fi network. Network connection interface 1211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 1211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately. [00126] RAM 1217 may be configured to interface via bus 1202 to processing circuitry 1201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 1219 may be configured to provide computer instructions or data to processing circuitry 1201. For example, ROM 1219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 1221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 1221 may be configured to include operating system 1223, application program 1225 such as a web browser application, a widget or gadget engine or another application, and data file 1227. Storage medium 1221 may store, for use by UE 1200, any of a variety of various operating systems or combinations of operating systems.

[00127] Storage medium 1221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, 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 a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 1221 may allow UE 1200 to access computer-executable instructions, application programs or 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 in storage medium 1221 , which may comprise a device readable medium.

[00128] In Figure 11 , processing circuitry 1201 may be configured to communicate with network 1243b using communication subsystem 1231. Network 1243a and network 1243b may be the same network or networks or different network or networks. Communication subsystem 1231 may be configured to include one or more transceivers used to communicate with network 1243b. For example, communication subsystem 1231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11 , CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 1233 and/or receiver 1235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1233 and receiver 1235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[00129] In the illustrated embodiment, the communication functions of communication subsystem 1231 may include 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. For example, communication subsystem 1231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 1243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 1213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1200. [00130] The features, benefits and/or functions described herein may be implemented in one of the components of UE 1200 or partitioned across multiple components of UE 1200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 1231 may be configured to include any of the components described herein. Further, processing circuitry 1201 may be configured to communicate with any of such components over bus 1202.

In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 1201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 1201 and communication subsystem 1231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

[00131] Figure 12 is a schematic block diagram illustrating a virtualization environment 1300 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 a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) 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 (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[00132] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1300 hosted by one or more of hardware nodes 1330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized. [00133] The functions may be implemented by one or more applications 1320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 1320 are run in virtualization environment 1300 which provides hardware 1330 comprising processing circuitry 1360 and memory 1390. Memory 1390 contains instructions 1395 executable by processing circuitry 1360 whereby application 1320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

[00134] Virtualization environment 1300, comprises general-purpose or special-purpose network hardware devices 1330 comprising a set of one or more processors or processing circuitry 1360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 1390-1 which may be non-persistent memory for temporarily storing instructions 1395 or software executed by processing circuitry 1360. Each hardware device may comprise one or more network interface controllers (NICs) 1370, also known as network interface cards, which include physical network interface 1380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 1390-2 having stored therein software 1395 and/or instructions executable by processing circuitry 1360. Software 1395 may include any type of software including software for instantiating one or more virtualization layers 1350 (also referred to as hypervisors), software to execute virtual machines 1340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

[00135] Virtual machines 1340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1350 or hypervisor. Different embodiments of the instance of virtual appliance 1320 may be implemented on one or more of virtual machines 1340, and the implementations may be made in different ways. [00136] During operation, processing circuitry 1360 executes software 1395 to instantiate the hypervisor or virtualization layer 1350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1350 may present a virtual operating platform that appears like networking hardware to virtual machine 1340.

[00137] As shown in Figure 12, hardware 1330 may be a standalone network node with generic or specific components. Hardware 1330 may comprise antenna 13225 and may implement some functions via virtualization. Alternatively, hardware 1330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 13100, which, among others, oversees lifecycle management of applications 1320.

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

[00139] In the context of NFV, virtual machine 1340 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 virtual machines 1340, and that part of hardware 1330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 1340, forms a separate virtual network elements (VNE).

[00140] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1340 on top of hardware networking infrastructure 1330 and corresponds to application 1320 in Figure 12.

[00141] In some embodiments, one or more radio units 13200 that each include one or more transmitters 13220 and one or more receivers 13210 may be coupled to one or more antennas 13225. Radio units 13200 may communicate directly with hardware nodes 1330 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. [00142] In some embodiments, some signaling can be effected with the use of control system 13230 which may alternatively be used for communication between the hardware nodes 1330 and radio units 13200.

[00143] Figure 13 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference to FIGURE 13, in accordance with an embodiment, a communication system includes telecommunication network 1410, such as a 3GPP-type cellular network, which comprises access network 1411 , such as a radio access network, and core network 1414. Access network 1411 comprises a plurality of base stations 1412a, 1412b, 1412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1413a, 1413b, 1413c. Each base station 1412a, 1412b, 1412c is connectable to core network 1414 over a wired or wireless connection 1415. A first UE 1491 located in coverage area 1413c is configured to wirelessly connect to, or be paged by, the corresponding base station 1412c. A second UE 1492 in coverage area 1413a is wirelessly connectable to the corresponding base station 1412a. While a plurality of UEs 1491 , 1492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1412.

[00144] Telecommunication network 1410 is itself connected to host computer 1430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 1430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1421 and 1422 between telecommunication network 1410 and host computer 1430 may extend directly from core network 1414 to host computer 1430 or may go via an optional intermediate network 1420. Intermediate network 1420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1420, if any, may be a backbone network or the Internet; in particular, intermediate network 1420 may comprise two or more sub-networks (not shown). [00145] The communication system of Figure 13 as a whole enables connectivity between the connected UEs 1491 , 1492 and host computer 1430. The connectivity may be described as an over-the-top (OTT) connection 1450. Host computer 1430 and the connected UEs 1491 , 1492 are configured to communicate data and/or signaling via OTT connection 1450, using access network 1411 , core network 1414, any intermediate network 1420 and possible further infrastructure (not shown) as intermediaries. OTT connection 1450 may be transparent in the sense that the participating communication devices through which OTT connection 1450 passes are unaware of routing of uplink and downlink communications. For example, base station 1412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1430 to be forwarded (e.g., handed over) to a connected UE 1491. Similarly, base station 1412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1491 towards the host computer 1430. [00146] Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 14. Figure 14 illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system 1500, host computer 1510 comprises hardware 1515 including communication interface 1516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1500. Host computer 1510 further comprises processing circuitry 1518, which may have storage and/or processing capabilities. In particular, processing circuitry 1518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 1510 further comprises software 1511 , which is stored in or accessible by host computer 1510 and executable by processing circuitry 1518. Software 1511 includes host application 1512. Host application 1512 may be operable to provide a service to a remote user, such as UE 1530 connecting via OTT connection 1550 terminating at UE 1530 and host computer 1510. In providing the service to the remote user, host application 1512 may provide user data which is transmitted using OTT connection 1550. [00147] Communication system 1500 further includes base station 1520 provided in a telecommunication system and comprising hardware 1525 enabling it to communicate with host computer 1510 and with UE 1530. Hardware 1525 may include communication interface 1526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1500, as well as radio interface 1527 for setting up and maintaining at least wireless connection 1570 with UE 1530 located in a coverage area (not shown in Figure 14) served by base station 1520. Communication interface 1526 may be configured to facilitate connection 1560 to host computer 1510. Connection 1560 may be direct or it may pass through a core network (not shown in Figure 14) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1525 of base station 1520 further includes processing circuitry 1528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 1520 further has software 1521 stored internally or accessible via an external connection.

[00148] Communication system 1500 further includes UE 1530 already referred to. Its hardware 1535 may include radio interface 1537 configured to set up and maintain wireless connection 1570 with a base station serving a coverage area in which UE 1530 is currently located. Hardware 1535 of UE 1530 further includes processing circuitry 1538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 1530 further comprises software 1531 , which is stored in or accessible by UE 1530 and executable by processing circuitry 1538. Software 1531 includes client application 1532. Client application 1532 may be operable to provide a service to a human or non-human user via UE 1530, with the support of host computer 1510. In host computer 1510, an executing host application 1512 may communicate with the executing client application 1532 via OTT connection 1550 terminating at UE 1530 and host computer 1510. In providing the service to the user, client application 1532 may receive request data from host application 1512 and provide user data in response to the request data. OTT connection 1550 may transfer both the request data and the user data. Client application 1532 may interact with the user to generate the user data that it provides.

[00149] It is noted that host computer 1510, base station 1520 and UE 1530 illustrated in Figure 14 may be similar or identical to host computer 1430, one of base stations 1412a, 1412b, 1412c and one of UEs 1491 , 1492 of Figure 13, respectively. This is to say, the inner workings of these entities may be as shown in Figure 14 and independently, the surrounding network topology may be that of Figure 13.

[00150] In Figure 14, OTT connection 1550 has been drawn abstractly to illustrate the communication between host computer 1510 and UE 1530 via base station 1520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 1530 or from the service provider operating host computer 1510, or both. While OTT connection 1550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[00151] Wireless connection 1570 between UE 1530 and base station 1520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 1530 using OTT connection 1550, in which wireless connection 1570 forms the last segment. More precisely, the teachings of these embodiments may improve the power consumption and reduce interference and thereby provide benefits such as extended battery lifetime and improved system performance.

[00152] 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 OTT connection 1550 between host computer 1510 and UE 1530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1550 may be implemented in software 1511 and hardware 1515 of host computer 1510 or in software 1531 and hardware 1535 of UE 1530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which 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 1511 , 1531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1520, and it may be unknown or imperceptible to base station 1520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1511 and 1531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1550 while it monitors propagation times, errors etc.

[00153] Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figure 13 and Figure 14. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step 1610, the host computer provides user data. In substep 1611 (which may be optional) of step 1610, the host computer provides the user data by executing a host application. In step 1620, the host computer initiates a transmission carrying the user data to the UE. In step 1630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[00154] Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figure 13 and Figure 14. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In step 1710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 1720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1730 (which may be optional), the UE receives the user data carried in the transmission.

[00155] Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figure 13 and Figure 14. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section. In step 1810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1820, the UE provides user data. In substep 1821 (which may be optional) of step 1820, the UE provides the user data by executing a client application. In substep 1811 (which may be optional) of step 1810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1830 (which may be optional), transmission of the user data to the host computer. In step 1840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[00156] Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figure 13 and Figure 14. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section. In step 1910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[00157] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[00158] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the description. [00159] The term “unit” may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. [00160] As used herein, the terms “Tx beam” and “spatial domain Tx filter” are used synonymously. Similarly, the terms “Rx beam” and “spatial domain Rx filter” are synonymous. As used herein, a “periodic grant” refers to a grant that identifies a recurring time-frequency resource for associated uplink transmissions. Similarly, reference to the “periodicity” of a grant refers to the periodicity of the identified recurring time-frequency resource for associated uplink transmissions. As used herein, the term “configured to” means set up, organized, adapted, or arranged to operate in a particular way; the term is synonymous with “designed to.”

[00161] Embodiments of the present invention present numerous advantages over the prior art. By evaluating the ongoing validity of a Tx beam associated with a pre-configured PUSCH resource prior to performing the uplink Tx in RCJNACTIVE state, the UE can suppress the uplink Tx when the Tx beam is no longer valid, such as due to the UE moving within the cell. This avoids the consumption of battery power and interference that would otherwise be caused by a transmission that is unlikely to be accurately received.

[00162] Some of the embodiments contemplated herein are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. The present invention may, of course, be carried out in other ways than those specifically set forth herein without departing from essential characteristics of the invention. The present embodiments are to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning and equivalency range of the appended embodiments are intended to be embraced therein. Representative Embodiments

Group A Embodiments

1. A method (100), performed by a wireless device (10) operative in a wireless communication network, of performing uplink transmissions, Tx, comprising: in Radio Resource Control, RRC, connected state, receiving (102) from the network a pre-configured uplink resource, PUR, configuration including a first grant for at least a first future uplink Tx, wherein the first grant includes information identifying an uplink time-frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for at least the first future uplink Tx; in RRC inactive state, prior to the uplink time-frequency resource for the first future uplink Tx identified in the PUR configuration, evaluating (104) the a validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined validation criteria; and in response to evaluating the spatial domain filter as valid (106), performing (108) the uplink Tx using the indicated spatial domain filter in the RRC inactive state in the uplink time-frequency resource for the first future uplink Tx.

2. The method (100) of claim 1 further comprising: in response to evaluating the spatial domain filter as invalid (106), performing an action other than transmitting the uplink Tx for in the uplink time-frequency resource for the first future uplink Tx.

3. The method (100) of claim 2 wherein the action other than transmitting the uplink Tx comprises one of performing a random access procedure, and skipping at least the time- frequency resource for the first future uplink Tx, and requesting a new PUR configuration.

4. The method (100) of any preceding claim wherein performing (108) the uplink Tx comprises verifying that a current Timing Advance value is also evaluated as valid at the time of the uplink time-frequency resource for the first future uplink Tx.

5. The method (100) of claim 4 wherein the current Timing Advance value was specified in the PUR configuration.

6. The method (100) of any preceding claim wherein the PUR configuration includes one or more of: a periodicity of a recurring uplink time-frequency resource and a Timing Advance value, and wherein the indication of a spatial domain filter is a Sounding Reference Signal Resource Indicator, SRI, identifying a Sounding Reference Signal, SRS, resource of an SRS resource set, wherein a spatial relation associated with the SRS resource determines the spatial domain filter.

7. The method (100) of any preceding claim wherein evaluating (104) the validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined validation criteria comprises: receiving, from the network, a reference signal received power threshold value; measuring the reference signal received power of a downlink signal transmitted by the network using a Tx spatial domain filter that corresponds to an Rx spatial domain filter used to receive the first future uplink Tx indicated in the PUR configuration; and evaluating the validity of the uplink Tx spatial domain filter at the wireless device (10) and/or Rx spatial domain filter at the network, by comparing the measured reference signal received power to the reference signal received power threshold value.

8. The method (100) of claim 7 wherein measuring the reference signal received power of a signal transmitted by the network comprises: in response to the network having configured a reference signal for the wireless device (10) to use for spatial domain filter validation, measuring a reference signal received power of the reference signal configured by the network ; and in response to the network not having configured a reference signal for the wireless device (10) to use for spatial domain filter validation, measuring a reference signal received power of a default reference signal configured by the network.

9. The method (100) of claim 7 wherein the wireless device (10) is configured to evaluate the validity of the spatial domain filter for at least the first future uplink Tx indicated in the PUR configuration based on a set of downlink signals, each transmitted by the network using a different spatial domain filter, and wherein evaluating the validity of the spatial domain filter for at least the first future uplink Tx comprises comparing the reference signal received powers of all signals in the set to the reference signal received power threshold value.

10. The method (100) of claim 9 further comprising: in response to the reference signal received power of all of the downlink signals in the set being less than the reference signal received power threshold value, determining the spatial domain filter for at least the first future uplink Tx indicated in the PUR configuration as invalid; and in response to the reference signal received power of one or more of the downlink signals in the set being equal to or greater than the reference signal received power threshold value, performing the uplink Tx at in the uplink time-frequency resource for the first future uplink Tx using a spatial domain filter corresponding to a network spatial domain filter of the downlink signal having the greatest reference signal received power.

11. The method (100) of claim 7 wherein the signal transmitted by the network, for which a reference signal received power is measured, is a synchronization signal block comprising synchronization and broadcast signals.

12. The method (100) of claim 11 , wherein: the first grant for the future uplink Tx is periodicincludes a periodicity of a recurring uplink time-frequency resource; the PUR configuration includes a periodicity of the first grant; and the periodicity of the first grant is dependent on a periodicity of a physical random access channel resource which is associated with the same synchronization signal block.

13. The method (100) of claim 7 wherein the signal transmitted by the network, for which a reference signal received power is measured, is a downlink reference signal. 14. The method (100) of claim 7 wherein the PUR configuration includes a second grant including an indication of a spatial domain filter for a future uplink Tx, wherein each of the first and second grants contains a unique index identifying a unique sounding reference signal, SRS, resource which is spatially related to a unique downlink reference signal, RS, and further comprising: measuring a reference signal received power of each RS associated with each grant; identifying an RS having the greatest reference signal received power; and performing an uplink Tx based on the grant associated with the RS having the greatest reference signal received power.

15. The method (100) of claim 14 further comprising: detecting a downlink RS having a greater reference signal received power than the RSs associated with SRS resources for which the wireless device (10) has configured grants; and in response to detecting the downlink RS with greater reference signal received power, performing an action other than transmitting the uplink Tx.

16. The method (100) of any preceding claim further comprising, in response to evaluating the spatial domain filter as invalid, considering the PUR configuration as released.

17. The method (100) of any preceding claim wherein when no predetermined validation criteria are configured in the wireless device (10), evaluating the validity of the spatial domain filter identified in the PUR configuration comprises determining the spatial domain filter is valid throughout a cell of the wireless communication network.

AA. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

Group B Embodiments

18. A method (200), performed by a base station (40) operative in a wireless communication network, of pre-configuring a time-frequency resource for a wireless device (10) to transmit in an inactive state, comprising: when the wireless device (10) is in Radio Resource Control, RRC, connected state, transmitting (202) to the wireless device (10) a pre-configured uplink resource, PUR, configuration including a first grant for at least a first future uplink transmission, Tx, wherein the first grant includes information identifying an uplink time-frequency resource for the first future uplink Tx, and an indication of a spatial domain filter for the uplink Tx; prior to the uplink time-frequency resource for the first future uplink Tx identified in the

PUR configuration, transmitting (204) signals enabling the wireless device (10) to evaluate the a validity of the spatial domain filter indicated in the PUR configuration against one or more predetermined validation criteria; and receiving (208) a signal transmitted by the wireless device (10) in RRC inactive state, if the wireless device (10) evaluated the spatial domain filter indicated in the PUR configuration as valid (206). 19. The method (200) of claim 18 wherein the base station (40) receives (208) the signal transmitted by the wireless device (10) in RRC inactive state if the wireless device (10) also evaluates a current Timing Advance value specified in the PUR configuration as valid at the time of the first configured uplink time-frequency resource.

20. The method (200) of claim 19 wherein the base station (40) specified the current Timing Advance value in the PUR configuration.

21. The method (200) of any of claims 18-20 wherein the PUR configuration includes one or more of: a periodicity of a recurring uplink time-frequency resource and a Timing Advance value, and wherein the indication of a spatial domain filter is a Sounding Reference Signal Resource Indicator, SRI, identifying a Sounding Reference Signal, SRS, resource of an SRS resource set, wherein a spatial relation associated with the SRS resource determines the spatial domain filter.

22. The method (200) of any of claims 18-21 further comprising: transmitting to the wireless device (10) a reference signal received power threshold value; and wherein transmitting (204) signals enabling the wireless device (10) to evaluate the validity of the spatial domain filter indicated in the PUR configuration comprises transmitting a downlink signal using a Tx spatial domain filter that corresponds to an Rx spatial domain filter used to receive the first future uplink Tx for which a the first grant was transmitted in the PUR configuration.

23. The method (200) of claim 22 further comprising: transmitting, to the wireless device (10), an indication of which downlink signal to measure using the reference signal received power threshold value.

24. The method (200) of claim 22 wherein transmitting (204) signals enabling the wireless device (10) to evaluate the validity of the spatial domain filter indicated in the PUR configuration comprises transmitting a set of downlink signals, each using a different spatial domain filter.

25. The method (200) of claim 22 wherein transmitting (204) signals enabling the wireless device (10) to evaluate the validity of the spatial domain filter indicated in the PUR configuration comprises transmitting a synchronization signal block comprising synchronization and broadcast signals.

26. The method (200) of claim 25 wherein the first grant for the future uplink Tx is periodic includes a periodicity of a recurring uplink time-frequency resource; the PUR configuration includes a periodicity of the first grant; and the periodicity of the first grant is dependent on a periodicity of a physical random access channel resource which is associated with the same synchronization signal block.

27. The method (200) of claim 22 wherein transmitting (204) signals enabling the wireless device (10) to evaluate the validity of the spatial domain filter identified in the PUR configuration comprises transmitting a downlink reference signal. 28. The method (200) of claim 22 wherein the PUR configuration includes a second grant including an indication of a spatial domain filter for a future uplink Tx, wherein each of the first and second grants contains a unique index identifying a unique sounding reference signal, SRS, resource which is spatially related to a unique downlink reference signal, RS.

29. The method (200) of any of claims 18-28 wherein the PUR configuration does not include validation criteria.

BB. The method of any of the preceding Group B embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.

Group C Embodiments

C1. A wireless device configured to perform any of the steps of any of the Group A embodiments.

C2. A wireless device comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless device.

C3. A wireless device comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the wireless device is configured to perform any of the steps of any of the Group A embodiments.

C4. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

C5. A computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to carry out the steps of any of the Group A embodiments.

C6. A carrier containing the computer program of embodiment C5, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. C7. A base station configured to perform any of the steps of any of the Group B embodiments.

C8. A base station comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the wireless device.

C9. A base station comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the base station is configured to perform any of the steps of any of the Group B embodiments.

C10. A computer program comprising instructions which, when executed by at least one processor of a base station, causes the base station to carry out the steps of any of the Group B embodiments.

C11. A carrier containing the computer program of embodiment C10, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Group D Embodiments

D1. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

D2. The communication system of the pervious embodiment further including the base station.

D3. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

D4. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application. D5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

D6. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

D7. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the previous 3 embodiments.

D9. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.

D10. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

D11. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

D12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

D13. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. D14. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.

D15. The communication system of the previous embodiment, further including the UE.

D16. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

D17. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

D18. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

D19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

D20. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

D21. The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

D22. The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data. D23. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

D24. The communication system of the previous embodiment further including the base station.

D25. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

D26. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

D27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

D28. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

D29. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.