Implicit Sounding Reference Signal Aperiodic Triggering Offset

By adjusting slot offsets for aperiodic SRS transmission to avoid downlink slots, the method addresses PDCCH congestion and enhances SRS triggering flexibility, improving downlink transmission efficiency in 5G NR systems.

JP7588070B2Active Publication Date: 2024-11-21TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2021521517
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2018-10-26
Filing Date
2019-09-25
Publication Date
2024-11-21
Estimated Expiration
2039-09-25

AI Technical Summary

Technical Problem

The existing 5G NR radio access technology faces limitations in aperiodic SRS triggering due to fixed slot offsets, leading to high PDCCH congestion and reduced SRS triggering capacity, especially in multi-user multiple-input multiple-output (MU-MIMO) scenarios, which affects downlink transmission performance.

Method used

Implementing a method for aperiodic SRS transmission that allows SRS to be transmitted in slots that are not downlink slots by adjusting the slot offset based on semi-static or dynamic slot format indications, ensuring SRS is sent in flexible or uplink slots, thereby reducing PDCCH congestion and increasing SRS triggering flexibility.

Benefits of technology

This approach enhances SRS triggering flexibility, reduces PDCCH congestion, and improves PDCCH efficiency by allowing SRS requests to be integrated with normal UL or DL grants, thus optimizing downlink transmission performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007588070000019
    Figure 0007588070000019
  • Figure 0007588070000020
    Figure 0007588070000020
  • Figure 0007588070000021
    Figure 0007588070000021
Patent Text Reader

Abstract

A method for transmitting a sounding reference signal (SRS) is implemented by a wireless device. The method includes receiving downlink control information that triggers aperiodic SRS transmission and identifying a slot indicated by the downlink control information. If the slot indicated by the downlink control information is a downlink slot, the wireless device transmits the SRS in a slot that is not a downlink slot.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This relates to cellular communication systems, and in particular to the transmission of sounding reference signals by wireless devices. [Background technology]

[0002] In cellular communication systems, it is known that user equipment devices transmit sounding reference signals (SRS), which can be used for uplink channel quality measurements, uplink timing estimation, and uplink power control.

[0003] In the 5G NR (New Radio) radio access technology developed by 3GPP, aperiodic SRS transmission is possible, in which the UE transmits SRS only when SRS is requested by the base station. The request is sent in a downlink control information (DCI) that triggers the aperiodic SRS transmission, and the slot offset for the aperiodic SRS transmission relative to the triggering DCI is fixed by a radio resource control (RRC) configuration from the network to the UE for each SRS resource set. In some situations, only one or two slot offsets are possible.

[0004] This has the disadvantage that if there is a single slot in which aperiodic SRS can be triggered, sometimes many UEs need to be triggered to transmit SRS simultaneously in that slot, in which case there is a large overhead on the downlink channel carrying the associated DCI. This may limit the SRS triggering capacity and may affect performance for downlink transmissions, especially when the channel is needed for multiple UEs at the same time, e.g., in case of multi-user multiple-input multiple-output (MU-MIMO) transmissions. Summary of the Invention

[0005] According to a first aspect of the present invention, there is provided a method implemented by a wireless device for transmitting a Sounding Reference Signal (SRS), the method comprising: receiving downlink control information triggering aperiodic SRS transmission; identifying a slot indicated by the downlink control information; If the slot indicated by the downlink control information is a downlink slot, the SRS is transmitted in a slot other than the downlink slot. Includes.

[0006] According to a second aspect of the present invention, there is provided a base station implemented method for triggering aperiodic Sounding Reference Signal (SRS) transmissions, the method comprising: Transmitting downlink control information to the UE, the downlink control information triggering aperiodic SRS transmission by the UE. Including, The downlink control information identifies slots for aperiodic SRS transmission by the UE; The slots identified for aperiodic SRS transmission by the UE are downlink slots.

[0007] According to a further aspect, a wireless device is provided, the wireless device comprising: a processing circuit configured to perform any of the steps of the method of the first aspect; a power delivery circuit configured to provide power to a wireless device; Equipped with.

[0008] According to a further aspect, a base station is provided, comprising: a processing circuit configured to perform any of the steps of the method of the second aspect; a power supply circuit configured to supply power to the base station; Equipped with.

[0009] According to a further aspect, a user equipment (UE) is provided, the UE comprising: an antenna configured to transmit and receive radio signals; a radio front-end circuit coupled to the antenna and to the processing circuit and configured to condition signals communicated between the antenna and the processing circuit; a processing circuit configured to perform any of the steps of the method of the first aspect; an input interface coupled to the processing circuitry and configured to enable input of information to the UE to be processed by the processing circuitry; an output interface coupled to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; a battery connected to the processing circuit and configured to power the UE; Equipped with.

[0010] According to a further aspect, there is provided a communication system including a host computer, the host computer comprising: processing circuitry configured to provide user data; a communications interface configured to forward user data to a cellular network for transmission to a user equipment (UE); Equipped with The cellular network comprises a base station having a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps of the method of the second aspect.

[0011] The communication system may further include a base station.

[0012] The communication system may further include a UE, the UE being configured to communicate with the base station.

[0013] In a communication system, the processing circuitry of the host computer may be configured to execute a host application and thereby provide user data; The UE may comprise processing circuitry configured to execute a client application associated with the host application.

[0014] According to a further aspect, there is provided a method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at a host computer; initiating, in a host computer, a transmission conveying user data to a UE via a cellular network comprising a base station, the base station performing any of the steps of the method of the second aspect; Includes.

[0015] The method may further include transmitting, at the base station, the user data.

[0016] In the method, the user data may be provided at the host computer by executing a host application, and the method may further include executing, at the UE, a client application associated with the host application.

[0017] According to a further aspect, a user equipment (UE) configured to communicate with a base station is provided, the UE comprising a radio interface and a processing circuit configured to implement the method.

[0018] According to a further aspect, there is provided a communication system including a host computer, the host computer comprising: processing circuitry configured to provide user data; a communications interface configured to forward user data to a cellular network for transmission to a user equipment (UE); Equipped with The UE comprises a radio interface and processing circuitry, the components of the UE being configured to perform any of the steps of the method of the first aspect.

[0019] In the communication system, the cellular network may further include base stations configured to communicate with the UEs.

[0020] In a communication system, the processing circuitry of the host computer may be configured to execute a host application and thereby provide user data; Processing circuitry of the UE may be configured to execute a client application associated with the host application.

[0021] According to a further aspect, there is provided a method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at a host computer; initiating, in a host computer, a transmission conveying user data to a UE via a cellular network comprising a base station, the UE performing any of the steps of the method of the first aspect; Includes.

[0022] The method may further include receiving, at the UE, user data from the base station.

[0023] According to a further aspect, there is provided a communication system including a host computer, the host computer comprising: A communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station Equipped with The UE comprises a radio interface and a processing circuit, the processing circuit of the UE being configured to perform any of the steps of the method of the first aspect.

[0024] The communication system may further include a UE.

[0025] The communication system may further include a base station, the base station comprising a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by transmissions from the UE to the base station to a host computer.

[0026] In a communication system, The processing circuitry of the host computer may be configured to execute a host application; The processing circuitry of the UE may be configured to execute a client application associated with the host application thereby providing user data.

[0027] In a communication system, processing circuitry of the host computer may be configured to execute the host application and thereby provide the requested data; Processing circuitry of the UE may be configured to execute a client application associated with the host application thereby providing user data in response to the requested data.

[0028] According to a further aspect, there is provided a method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: Receiving, at the host computer, user data transmitted from the UE to the base station, the UE performing any of the steps of the method of the first aspect. Includes.

[0029] The method may further include, at the UE, providing user data to the base station.

[0030] The method is: - executing, in the UE, a client application thereby providing user data to be transmitted; - executing, at the host computer, a host application associated with the client application; It may further include.

[0031] The method is: executing, in the UE, a client application; receiving, at the UE, input data for a client application, the input data being provided at a host computer by executing a host application associated with the client application; may further include The user data to be transmitted is provided by the client application in response to the input data.

[0032] According to a further aspect, there is provided a communications system including a host computer, the host computer comprising a communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the base station comprising a wireless interface and processing circuitry, the processing circuitry of the base station being configured to perform any of the steps of the method of the second aspect.

[0033] The communication system may further include a base station.

[0034] The communication system may further include a UE, the UE being configured to communicate with the base station.

[0035] In a communication system, The processing circuitry of the host computer may be configured to execute a host application; The UE may be configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0036] According to a further aspect, there is provided a method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: - receiving, at the host computer, from a base station, user data originating from a transmission received by the base station from a UE, the UE performing any of the steps of the method of the first aspect. Includes.

[0037] The method may further include receiving, at the base station, user data from the UE.

[0038] The method may further include initiating, at the base station, transmission of the received user data to the host computer.

[0039] In particular, various methods, e.g., methods implemented in a UE, for transmitting aperiodic SRS in symbols of a slot are disclosed, the methods including: Obtaining a slot format setting; Obtaining one or more nominal slot offset configurations; receiving a PDCCH including a DCI triggering aperiodic SRS transmission, the DCI indicating a nominal slot offset from one or more configured nominal slot offsets; determining a slot in which the aperiodic SRS is to be transmitted based on a nominal slot offset and a slot format setting; Transmitting a non-periodic SRS in the determined slot symbol; Includes.

[0040] The slot format configuration may be a semi-static TDD configuration provided by higher layers.

[0041] The slot format configuration may be indicated by a DCI, which may be a group common DCI that includes a slot format indication.

[0042] Determining the slot may include determining a slot offset relative to the slot of the PDCCH reception. The determined slot offset may be greater than or equal to a nominal slot offset.

[0043] The determined slot may not be a downlink slot depending on the slot format setting.

[0044] The determined slot may be a flexible slot depending on a slot format configuration, and the symbol of the determined slot may not be a downlink symbol.

[0045] The determined slot offset that is greater than or equal to the nominal slot offset may be the smallest slot offset such that the determined slot is not a downlink slot.

[0046] Determining the slot offset may include determining an additional slot offset.

[0047] Embodiments disclosed herein may provide one or more of the following technical advantage(s). Increased flexibility for aperiodic SRS triggering, so that SRS can be triggered at any slot without worrying about the SRS transmission being dropped due to collision with semi-statically configured DL slots. Reduced PDCCH congestion, because the PDCCH that triggers SRS for multiple UEs can be spread across multiple DL or flexible ("X") slots. Increased PDCCH efficiency, because the SRS request can always be piggybacked onto the UE's regular UL or DL ​​grant, which avoids the need to send a separate DCI with the SRS request just to meet strict timing criteria. [Brief description of the drawings]

[0048] [Figure 1] FIG. 2 illustrates a physical resource grid. [Diagram 2] A diagram showing the location of SRS signals in physical resource blocks of an SRS subframe. [Diagram 3] FIG. 2 illustrates an example of cell-specific and UE-specific SRS subframes. [Figure 4] FIG. 1 illustrates an example of wideband and narrowband SRS with a 10 MHz system bandwidth. [Diagram 5] A diagram showing an example of a set of locations for SRS transmission with a bandwidth of four physical resource blocks. [Figure 6] FIG. 1 illustrates limited SRS triggering flexibility. [Figure 7] 1 is a flowchart showing a first method. [Figure 8] 11 is a flowchart showing a second method. [Figure 9] FIG. 13 is a diagram of aperiodic SRS triggering with an implicit slot determination procedure. [Figure 10] FIG. 1 illustrates a wireless network according to some embodiments. [Figure 11] FIG. 2 illustrates a user equipment according to some embodiments. [Figure 12] FIG. 1 illustrates a virtualization environment in accordance with some embodiments. [Figure 13] FIG. 1 illustrates a communications network connected to a host computer through an intermediate network, according to some embodiments. [Figure 14] FIG. 2 illustrates a host computer communicating with user equipment via a base station over a partially wireless connection according to some embodiments. [Figure 15] FIG. 1 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 16]FIG. 1 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 17] FIG. 1 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 18] FIG. 1 illustrates a method implemented in a communications system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 19] FIG. 2 illustrates a virtualization device according to some embodiments. [Figure 20] FIG. 2 illustrates a virtualization device according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0049] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which: However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments described herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0050] Generally, all terms used herein should be interpreted according to the ordinary meaning of those terms in the relevant technical field, unless a different meaning is expressly given and / or implied from the context in which the term is used. All references to a / an / the element, apparatus, component, means, step, etc. should be openly interpreted as referring to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is expressly described as following or preceding another step, and / or 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 be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the enclosed embodiments will become apparent from the following description.

[0051] NR Frame Structure Next-generation mobile radio communication systems (5G) or New Radio (NR) will support a diverse set of use cases and deployment scenarios, the latter including deployment at both low frequencies (hundreds of MHz) and very high frequencies (mm wavelengths in the tens of GHz range) similar to today's Long Term Evolution (LTE) systems.

[0052] Like LTE, NR uses OFDM (orthogonal frequency division multiplexing) in the downlink (i.e., from a network node, gNB, eNB, or base station, to a user equipment or UE). Thus, the basic NR physical resources on an antenna port can be viewed as a time-frequency grid 100 as shown in FIG. 1, with resource blocks (RBs) in 14 symbol slots (with slots numbered 0-13 horizontally in FIG. 1). Resource block 102 corresponds to 12 consecutive subcarriers (numbered 0-11 vertically in FIG. 1) in the frequency domain. Resource blocks are numbered in the frequency domain starting with 0 from one end of the system bandwidth. Each resource element, such as resource element 104, corresponds to one OFDM subcarrier in one OFDM symbol interval.

[0053] Different subcarrier spacing values ​​are supported in NR. (Also called different numerologies) The supported subcarrier spacing values ​​are Δf = (15 × 2 α ) kHz, where α∈(0,1,2,3,4). Δf=15 kHz is the basic (or reference) subcarrier spacing, also used in LTE.

[0054] In the time domain, downlink and uplink transmissions in NR are organized into equal-sized subframes of 1 ms each, similar to LTE. Subframes are further divided into multiple slots of equal duration. The subcarrier spacing Δf = (15 × 2 α ) kHz, the slot length is 1 / 2 α ms. There is only one slot per subframe with Δf=15 kHz and a slot consists of 14 OFDM symbols.

[0055] Downlink transmissions are typically dynamically scheduled, i.e., in each slot, the gNB transmits downlink control information (DCI) regarding which UEs data should be transmitted to and on which resource blocks in the current downlink slot the data is transmitted. This control information is typically transmitted in the first one or two OFDM symbols in each slot in NR. The control information is carried on a physical control channel (PDCCH) and the data is carried on a physical downlink shared channel (PDSCH). If the UE first detects and decodes the PDCCH, and if the PDCCH is successfully decoded, the UE then decodes the corresponding PDSCH based on the decoded control information in the PDCCH.

[0056] In addition to the PDCCH and PDSCH, there are also other channels and reference signals transmitted in the downlink.

[0057] Uplink data transmissions carried on the Physical Uplink Shared Channel (PUSCH) are also dynamically scheduled by the gNB by transmitting a DCI. In case of time division duplex (TDD) operation, the DCI (transmitted in the downlink or DL ​​domain) always indicates a scheduling offset such that the PUSCH is transmitted in a slot in the uplink or UL domain.

[0058] SRS in LTE Sounding Reference Symbols (SRS) are used for uplink channel quality measurements for frequency selective scheduling and link adaptation. SRS are also used for uplink timing estimation and uplink power control.

[0059] Up to Release 15 in LTE, in a normal UL subframe configured for SRS transmission, the SRS can only be transmitted by the UE in the last single carrier frequency division multiple access (SC-FDMA) symbol. The location of the SRS 202 in a physical resource block (PRB) in the SRS subframe 206 is shown in Figure 2, where a demodulation reference signal (DMRS) 204 is used for channel estimation in PUSCH demodulation.

[0060] A subframe in which SRS transmission can occur in a cell is called a cell-specific SRS subframe. In the current LTE specification, the cell-specific SRS subframe configuration is determined by the T SFC and the periodicity given by Δ SFC The cell-specific SRS subframe is set with a subframe offset given by TIFF0007588070000001.tif8170, where n is the subframe s indicates the slot number.

[0061] The UE may be configured to transmit SRS on a subset of cell-specific SRS subframes. This subset of cell-specific SRS subframes is also referred to as a UE-specific SRS configuration. As specified in clause 8.2 of 3GPP TS36.213 V15.0.0, the UE-specific SRS configuration is determined by the SRS transmission periodicity T SRS and the subframe offset T offset It should be noted that the UE-specific SRS configuration may be different for periodic and aperiodic SRS.

[0062] An example of cell-specific and UE-specific configured SRS subframes is shown in FIG. 3, where a cell-specific configured SRS subframe 302 is shown in the first line and a UE-specific configured SRS subframe 304 is shown in the second line.

[0063] The UEs may be configured with different SRS bandwidths. In general, two kinds of sounding bandwidths are supported, one is wideband and the other is narrowband. For wideband, channel measurements across the entire system bandwidth may be performed in a single subframe. On the other hand, in narrowband sounding, only a portion of the entire system bandwidth may be measured in a subframe, and thus multiple SRS subframes are needed for full-bandwidth channel measurements. Frequency hopping is supported for narrowband SRS so that different parts of the frequency band may be measured in different subframes.

[0064] Furthermore, two types of sounding are supported: periodic (also called type 0) and aperiodic (also called type 1). For periodic SRS, the UE transmits SRS periodically in some configured SRS subframes. For aperiodic SRS, the UE transmits SRS only when SRS is requested by the eNB. The SRS subframes for periodic SRS and aperiodic SRS are configured separately for the UE and both are included in the cell-specific SRS subframe.

[0065] The SRS bandwidth for a UE is configurable and is a multiple of four PRBs. The minimum SRS bandwidth is four PRBs. An example is shown in FIG. 4 where PRBs numbered 1-48 occupy a 10 MHz system bandwidth, which is a wideband SRS bandwidth, and a consecutive block of four PRBs (PRBs 1-4, 5-8, 9-12, ..., 45-48) indicates the minimum SRS bandwidth.

[0066] For narrowband SRS with frequency hopping (FH), the SRS is transmitted on different parts of the system bandwidth in different SRS subframes. For example, for a 10 MHz system and an SRS bandwidth of 4 PRBs, a possible set of locations in the frequency domain for SRS transmission, i.e., locations A, B, C, ..., L, occurring at the beginning of RB#1, 2, 3, ..., 12, respectively, are shown in Figure 5. In this example, the entire bandwidth may be measured after 12 SRS subframes.

[0067] The SRS signal is a phase-shifted Zadoff-Chu sequence. Different UEs can be multiplexed on the same time-frequency resource by allocating different phase shifts, known as cyclic shifts (CS). There are eight cyclic shifts specified in LTE Rel.8. Furthermore, the SRS signal is transmitted only on half of the subcarriers in the configured SRS bandwidth, either on even-numbered subcarriers or odd-numbered subcarriers, which can be configured through a parameter called comb. Thus, up to 16 UEs can be multiplexed on the same SRS bandwidth. In LTE Rel.8 to Rel.12, 2 combs are supported, which means that SRS can be transmitted on every other subcarrier.

[0068] In the current LTE specification (3GPP TS36.211 V15.0.0), the SRS sequence is generated by the physical cell ID. This is a function of TIFF0007588070000002.tif7170. In particular, the Zadoff-Chu (ZC) basis sequences used to construct the SRS sequences are TIFF0007588070000003.tif8170 is parameterized by a sequence group number u and a number within the group v, and to select the values ​​of u and v TIFF0007588070000004.tif8170 is used. This implies that SRS transmissions for all UEs connected to the same cell must use the same ZC base sequence, which allows user separation only in a fully orthogonal manner by using different combs or cyclic shifts.

[0069] In LTE Rel.13, 4-com support is introduced, which means that the SRS signal can be mapped to every fourth subcarrier, thereby increasing the SRS multiplexing capacity, provided that the channel is sufficiently flat such that transmitting SRS on every fourth subcarrier is reasonable.

[0070] UEs with different SRS bandwidths may be multiplexed on SRS subframes with different comb values, and UEs with the same SRS bandwidth may be multiplexed in SRS subframes with different cyclic shifts.

[0071] Up to LTE Release 12, one or two SC-FDMA symbols can be used for SRS transmission in the UpPTS. In LTE Release 13, the number of SC-FDMA symbols that can be used for SRS in the UpPTS has been extended to up to six SC-FDMA symbols. In LTE Release 13 SRS extensions, a new set of RRC parameters was introduced for additional SRS symbols in the UpPTS for both aperiodic and periodic SRS.

[0072] Aperiodic SRS in LTE In LTE, until Release 15, three sets of SRS parameters are configured by higher layers for aperiodic SRS triggering in uplink-related DCI formats 4, 4A, 4B, and 7-0B. A 2-bit SRS request field present in DCI formats 4, 4A, 4B, and 7-0B indicates an SRS parameter set according to Table 1. As shown in the table, given the value of the SRS request field in DCI formats 4, 4A, 4B, and 7-0B, either an aperiodic SRS transmission corresponding to one of the SRS parameter sets is triggered or an aperiodic SRS transmission is not triggered. JPEG0007588070000005.jpg27170

[0073] For uplink-related DCI formats 0, 0A, 0B, 6-0A, and 7-0A, a single set of SRS parameters is configured by higher layers for aperiodic SRS triggering. Similarly, for downlink-related DCI formats 1A, 2B, 2C, 2D, 6-1A, 7-1E, 7-1F, and 7-1G, a single set of SRS parameters is configured by higher layers for aperiodic SRS triggering. For these DCI formats 0, 1A, 2B, 2C, 2D, 6-0A, 6-1A, 7-0A, 7-1E, 7-1F, and 7-1G, there is a one-bit SRS request field. When this bit field is set to "1", an aperiodic SRS transmission corresponding to the SRS parameter set configured for the DCI format carrying the SRS request is triggered.

[0074] The triggered aperiodic SRS is n+k, k ≥ 4, and (10.n f +k SRS -T offset,1 )modT SRS,1 = 0, where n f is the frame index, and k SRS ={0,1,...,9} is frame n f is the subframe index in T SRS and Toffset corresponds to the UE-specific configured SRS subframe set, i.e., the first enabled subframe according to the subframe configuration that occurs at least four subframes after the DCI trigger is the subframe in which the LTE SRS is transmitted.

[0075] SRS in NR In NR, both PUSCH and SRS transmissions are more flexible than in LTE. For example, multiple SRS symbols in a resource may be used, including intra-slot frequency hopping, and the transmission length for the PUSCH may be dynamically indicated in the DCI and is not fixed as in LTE. This implies that NR does not require cell-specific or UE-specific SRS subframe configuration, since the length of the PUSCH may be dynamically reduced if there is an SRS transmission in some symbols at the end of a slot.

[0076] SRS resources in NR are grouped into SRS resource sets that contain one or more SRS resources. An SRS resource set has a specific usage = {beamManagement, codebook, nonCodebook, antennaSwitching} with a specific set of rules that apply. An SRS with usage equal to antennaSwitching is used for DL ​​CSI acquisition purposes (including non-antenna switching). At most two such sets may be defined in NR, with each set containing only one SRS resource in case of non-antenna switching. For aperiodic SRS resource sets, each set is associated with an aperiodic slot offset k according to the RRC parameter slotOffset. The SRS resource sets are configured in RRC as follows: TIFF0007588070000006.tif208170TIFF0007588070000007.tif106170

[0077] In the case of aperiodic SRS triggering, the following rules are applied to derive the slot in which the SRS is transmitted relative to the trigger. - if the UE receives DCI triggering aperiodic SRS in slot n, the UE shall In TIFF0007588070000008.tif13170, transmitting aperiodic SRS in each of the triggered SRS resource set(s), where k is set via an upper layer parameter slotoffset for each triggered SRS resource set and is based on the subcarrier spacing of the triggered SRS transmission, and μ SRS and μ PDCCH are the subcarrier spacing settings for the triggered SRS and the PDCCH carrying the triggering command, respectively.

[0078] Thus, to trigger an SRS at different slot offsets, different SRS resource sets need to be configured with different offsets, and then the particular set is triggered based on the desired slot offset. This can be achieved by mapping different SRS set(s) to different DCI code point(s).

[0079] Uplink-Downlink Configuration in TDD for NR In TDD, some subframes / slots are allocated for uplink transmission and some subframes / slots are allocated for downlink transmission. Switching between downlink and uplink is done in so-called special subframes (LTE) or flexible slots (NR).

[0080] In LTE, seven different uplink-downlink configurations are provided, as shown in Table 2. TIFF0007588070000009.tif45170

[0081] The size of the guard period (and therefore the number of symbols for DwPTS (downlink transmission in a special subframe) and UpPTS (uplink transmission in a special subframe) in a special subframe) may also be set from a set of possible choices.

[0082] NR, on the other hand, offers many different uplink-downlink configurations. Depending on the subcarrier spacing, there are between 10 and 320 slots per radio frame (each radio frame having a duration of 10 ms). The OFDM symbols in a slot are classified as "downlink" (denoted as "D"), "flexible" (denoted as "X"), or "uplink" (denoted as "U"). If the TDD configuration is RRC configured from the network to the UE using the IE TDD-UL-DL-ConfigCommon, a quasi-static TDD UL-DL configuration may be used. TIFF0007588070000010.tif7170--The reference SCS used to determine the time domain boundaries in the UL-DL pattern, which must be common across all subcarrier-specific virtual carriers, i.e., independent of the actual subcarrier spacing used for data transmission. --Only the values ​​15 or 30 kHz (<6 GHz), 60 or 120 kHz (>6 GHz) are applicable. --Corresponds to the L1 parameter "reference-SCS" (see 38.211, section FFS_Section) TIFF0007588070000011.tif20170 -- Periodicity of the DL-UL pattern. Corresponds to the L1 parameter "DL-UL-transmission-periodicity" (see 38.211, section FFS_Section) TIFF0007588070000012.tif14170 -- The number of consecutive complete DL slots at the beginning of each DL-UL pattern. --Corresponds to the L1 parameter "number-of-DL-slots" (see 38.211, Table 4.3.2-1) TIFF0007588070000013.tif15170 -- The number of consecutive DL symbols at the beginning of a slot following the last complete DL slot (derived from nrofDownlinkSlots). --If the field is absent or released, there are no partial downlink slots. --Corresponds to the L1 parameter "number-of-DL-symbols-common" (see 38.211, section FFS_Section). TIFF0007588070000014.tif15170 -- The number of consecutive complete UL slots at the end of each DL-UL pattern. --Corresponds to the L1 parameter "number-of-UL-slots" (see 38.211, Table 4.3.2-1) TIFF0007588070000015.tif14170 -- The number of consecutive UL symbols at the end of the slot preceding the first complete UL slot (derived from nrofUplinkSlots). --If the field is absent or open, there are no partial uplink slots. --Corresponds to the L1 parameter "number-of-UL-symbols-common" (see 38.211, section FFS_Section) TIFF0007588070000016.tif13170

[0083] That is, the TDD periodicity of Pms is defined, and how many DL and UL slots are fitted to this TDD periodicity, as well as the size of the GP, can be arbitrarily specified. 1 +P 2 Two concatenated periodicities P, each with a distinct number of DL / UL slots, yielding a total TDD periodicity of 100 ms. 1 and P 2 It is possible to set

[0084] In NR, the SSB periodicity is fixed to the allowed values ​​5, 10, 20, 40, 80 and 160 ms. With the SSB in the initial access procedure having a default periodicity of 20 ms, all TDD periodicities must divide 20 ms evenly. For unconcatenated TDD periodicity, the value range for P is {0.5, 0.625, 1, 1.25, 2, 2.5, 3, 4, 5, 10} ms, which all divide 20 ms evenly except for the value of 3 ms (which in that case is not allowed to be selected for unconcatenated TDD periodicity, but only as part of the concatenated TDD periodicity). For concatenated TDD periodicity, P 1 +P 2 appears to be flexible, but in fact, this is 1 and P 2 This places constraints on what periodicity can be set to.

[0085] Or alternatively, the slot format can be dynamically indicated in the slot format indicator (SFI) conveyed in DCI format 2_0. In this case, the SFI overrides the slot / symbol semi-statically set as "X". Regardless of whether dynamic or semi-static TDD configuration is used in NR, the number of UL and DL slots and the guard period (the number of UL and DL symbols in the flexible slot(s)) can be set almost arbitrarily within the TDD periodicity. This allows for highly flexible uplink-downlink configuration.

[0086] In NR, the slot offset k for aperiodic SRS transmission for triggering DCI is fixed by RRC configuration from the network to the UE for each SRS resource set. For SRS for DL ​​CSI acquisition, only a maximum of two SRS resource sets may be configured, and in some cases only one, so only one or two slot offsets are possible for triggering.

[0087] This is problematic because it is not flexible and may result in a large PDCCH load in one of the DL slots to trigger aperiodic SRS in a given, sometimes single UL slot. If a single UL slot is in a TDD pattern period, many UEs need to be triggered to transmit simultaneous SRS in that slot, in which case the PDCCH overhead k slots in advance is large. This is problematic because it may limit the SRS triggering capacity and may affect performance for DL ​​transmissions, especially in the case of MU-MIMO where the channel is needed for multiple UEs at the same time.

[0088] In FIG. 6, the periodicity of the TDD pattern 600 is shown, and one typical example is that the pattern consists of six complete DL slots, one flexible slot ("X"), and one complete UL slot. Thus, the SRS needs to be transmitted in the flexible and / or UL slots, which leads to PDCCH congestion in up to two DL slots where the SRS may be triggered, which limits the SRS utilization. For example, if two SRS sets are configured with slot offsets K=1 and K=2, respectively, only the last two of the DL slots in the TDD periodicity, i.e., slots 602, 604, can be used for SRS triggering. If the SRS is triggered in the first four slots, e.g., slot 606, the SRS occurs in a DL slot (e.g., slot 604), is dropped, and is not transmitted by the UE.

[0089] Disclosed herein is an implicit slot determination for aperiodic SRS triggering, where the slot for SRS transmission is determined based on a nominal slot offset (e.g., k) and a quasi-static or dynamic slot format indication (such as a quasi-static TDD configuration) such that the SRS is transmitted on the first slot equal to or greater than the nominal slot offset that is not a downlink slot according to the slot format indication.

[0090] FIG. 7 is a flow chart illustrating a method according to a particular embodiment implemented by a wireless device for transmitting a sounding reference signal (SRS).

[0091] In the method, the wireless device has information that defines a slot format configuration. In some embodiments, the slot format configuration is a semi-static TDD configuration that is configured in the UE via RRC, such as via a TDD-UL-DL-ConfigCommon IE. The semi-static TDD configuration defines which slots are downlink, flexible and uplink slots, and further whether symbols of the flexible slot(s) are classified as downlink or uplink symbols.

[0092] 9 illustrates an example of a slot format configuration 900. In this example, slots 901, 902, 903, 904, 905, and 906 are designated as downlink slots, slot 907 is designated as a flexible slot, and slot 908 is designated as an uplink slot.

[0093] The method of FIG. 7 begins in step 702 with a wireless device receiving downlink control information triggering aperiodic SRS transmission and includes step 704, identifying a slot indicated by the downlink control information.

[0094] The slot may be identified by a nominal slot offset, which indicates the number of slots from the slot in which the DCI was received until the identified slot follows.

[0095] 9, for example, if DCI is received in slot 901 and the nominal slot offset k=1, then the slot indicated by the DCI is slot 902. Similarly, if DCI is received in slot 904 and the nominal slot offset k=2, then the slot indicated by the DCI is slot 906.

[0096] The nominal slot offset may be indicated by the SRS request field of the triggering DCI in a similar manner as the slot offset for SRS is indicated in existing standards, i.e., each code point in the SRS request field triggers one or more SRS resource sets, and each SRS resource set is associated with a nominal slot offset that may be configured using an RRC field.

[0097] For a PDCCH carrying a DCI that triggers aperiodic SRS transmission (by setting a non-zero value in the SRS request field) received in slot n, the indicated nominal slot offset k is implicitly given by the SRS request field of the DCI, and the slot indicated by the DCI is slot n+k.

[0098] The method of FIG. 7 then continues with step 706, where if the slot indicated by the downlink control information is a downlink slot, the wireless device transmits the SRS in a slot that is not a downlink slot.

[0099] That is, if the indicated nominal slot n+k is a downlink slot, it drops the SRS transmission in the existing solution because an uplink signal cannot be transmitted in the downlink slot. However, with the proposed method, the actual slot offset for the SRS transmission is instead determined as slot n+k+Δ, where Δ is an additional slot offset that is implicitly determined based on the slot format configuration.

[0100] In some embodiments, the additional slot offset Δ is determined such that slot n+k+Δ is not a downlink slot. For example, Δ may be the smallest integer greater than or equal to 0 such that slot n+k+Δ is not a downlink slot (i.e., slot n+k+Δ is a flexible or uplink slot). This means that the wireless device transmits the SRS in the first slot after the indicated nominal slot that is not a downlink slot.

[0101] 9, if the DCI is received in slot 901 and the nominal slot offset k=1, then the slot indicated by the DCI is slot 902. An additional slot offset Δ=5 is added and the wireless device transmits the SRS in slot 907.

[0102] Similarly, if the DCI is received in slot 904 and the nominal slot offset k=2, then the slot indicated by the DCI is slot 906. An additional slot offset Δ=1 is added and the wireless device transmits the SRS in slot 907.

[0103] More generally, the additional slot offset Δ is determined based on the slot format configuration such that the SRS transmission occurs in a flexible or uplink slot.

[0104] It should be noted that in some embodiments, the additional slot offset may not be explicitly determined, but rather may be implicitly determined via a calculation of available slots for SRS transmission according to predefined rules, as described herein.

[0105] For a PDCCH carrying DCI that triggers aperiodic SRS transmission, the additional slot offset Δ is determined such that slot n+k+Δ is not a downlink slot. For example, as described above, Δ may be the smallest integer greater than or equal to 0 such that slot n+k+Δ is not a downlink slot (i.e., slot n+k+Δ is a flexible or uplink slot). In other cases, Δ may be the second smallest integer greater than or equal to 0 such that slot n+k+Δ is not a downlink slot (i.e., slot n+k+Δ is a flexible or uplink slot). More generally, Δ may be the q-th smallest integer greater than or equal to 0 such that slot n+k+Δ is not a downlink slot.

[0106] In particular, in one embodiment, one trigger code point selects the smallest such integer for that value of Δ, and another code point selects the second smallest such integer for that value of Δ.

[0107] The method of FIG. 7 implies that aperiodic SRS may be triggered by the base station in early downlink slots, since if the nominal slot offset indicates a downlink slot, the SRS transmission simply "skips forward" to an available flexible or uplink slot.

[0108] 8 illustrates a method implemented by a base station according to a particular embodiment for triggering aperiodic sounding reference signal (SRS) transmission. The method includes step 802 of transmitting downlink control information to a UE, the downlink control information triggering the aperiodic SRS transmission by the UE. As shown in step 804, the downlink control information identifies slots for aperiodic SRS transmission by the UE. As shown in step 806, the slots identified for aperiodic SRS transmission by the UE are downlink slots.

[0109] This means that DCI may be sent by the base station in an earlier slot than would normally be acceptable, since a wireless device implementing the method of FIG. 7 takes action to ensure that the SRS is still transmitted in a slot that is not a downlink slot.

[0110] In particular, aperiodic SRS may be triggered in an early downlink slot, and if the nominal slot offset indicates a downlink slot, the SRS transmission simply "skips ahead" to the first or second available flexible or uplink slot.

[0111] In this way, for a quasi-static TDD configuration pattern that is like DDDUU, where D indicates the downlink slot, U indicates the uplink slot, and S is the slot used for switching, then one trigger in the "D" slot can trigger SRS in the first U slot, while another trigger in the "D" slot can trigger SRS in the second U slot. Note that the use of "UU" in the pattern is common, especially when LTE and NR coexist and NR uses 30 kHz subcarrier spacing (and LTE uses 15 kHz), where one LTE subframe matches two NR slots, hence "UU".

[0112] Thus, in general, each trigger point may be set (e.g., by higher layers) with Δ, where Δ is the q-th smallest integer greater than or equal to 0 such that slot n+k+Δ is not a downlink slot.

[0113] In other embodiments, the determination of the additional slot offset operates at the symbol level rather than the slot level, as in some cases where the slot format defines symbols as either downlink, flexible, or uplink within a slot, in which case the additional slot offset is determined such that symbols of the SRS resource do not occur at symbols determined as downlink symbols according to the obtained slot format configuration.

[0114] An SRS resource may include between one and four symbols in NR Rel-15, i.e., generally, one or more symbols. In some cases, only a subset of the symbols of an SRS resource may be classified as downlink symbols. In that case, in one embodiment, no additional slot offset is allowed to be determined such that at least one symbol of the SRS resource is a downlink symbol (and a larger value for the additional slot offset is chosen according to a predefined rule). In another embodiment, a symbol-by-symbol dropping of SRS symbols in an SRS resource is supported, and an additional slot offset is allowed to be determined such that one or more SRS symbols in an SRS resource are downlink symbols, as long as at least one symbol is a flexible or uplink symbol.

[0115] In some embodiments, the slot format configuration is alternatively or additionally obtained from dynamic L1 signaling, such as via a slot format indication (SFI) conveyed in a DCI on the PDCCH, where the dynamic SFI indication overrides and / or replaces the semi-static slot format configuration obtained via RRC. In some embodiments, an additional slot offset is determined such that SRS symbols occur only in uplink symbols (and not in uplink or flexible symbols).

[0116] Thus, the embodiment can be expressed as follows: If the UE receives a DCI that triggers aperiodic SRS in slot n, the UE In TIFF0007588070000017.tif12170, transmitting aperiodic SRS in each of the triggered SRS resource set(s), where k is set via an upper layer parameter slotoffset for each triggered SRS resource set and is based on the subcarrier spacing of the triggered SRS transmission, and μ SRS and μ PDCCH are the subcarrier spacing settings for the triggered SRS and the PDCCH carrying the triggering command, respectively, and Δ is the smallest integer greater than 0 such that one or more of the symbols of the configured SRS resource are allowed to be transmitted in accordance with 3GPP TS38.213 clause 11.1, where TS38.213 clause 11.1 describes the allowed UL channels and signal transmission with dynamically indicated or semi-statically configured slot formats.

[0117] Alternatively, some embodiments may be expressed as follows: If the UE receives a DCI that triggers aperiodic SRS in slot n, the UE In TIFF0007588070000018.tif12170, transmit aperiodic SRS in each of the triggered SRS resource set(s), where k is set via an upper layer parameter slotoffset for each triggered SRS resource set and is based on the subcarrier spacing of the triggered SRS transmission, and μ SRS and μ PDCCHare the subcarrier spacing settings for the triggered SRS and the PDCCH carrying the triggering command, respectively, and Δ is the smallest integer greater than 0 such that one or more of the symbols of the configured SRS resource set do not occupy a downlink symbol semi-statically configured by the UL-DL-configuration-common.

[0118] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a wireless network, such as the exemplary wireless network shown in FIG. 10. For simplicity, the wireless network of FIG. 10 illustrates only the network 1006, the network nodes 1060 and 1060b, and the WDs 1010, 1010b, and 1010c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices, or between a wireless device and another communication device, such as a landline, a service provider, or any other network node or end device. Of the components shown, the network node 1060 and the wireless device (WD) 1010 are illustrated with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless device's access to the wireless network and / or use of services provided by or via the wireless network.

[0119] A 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, a wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network may implement a communications standard, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards, a wireless local area network (WLAN) standard, such as the IEEE 802.11 standard, and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0120] The network 1006 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), 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 for enabling communication between devices. The network nodes 1060 and WDs 1010 comprise various components that are described in more detail below. These components cooperate to provide network node and / or wireless device functions, such as providing wireless connectivity 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.

[0121] A network node, as used herein, refers to a device capable of, set up, configured, and / or operable to communicate directly or indirectly with wireless devices and / or other network nodes or devices in a wireless network to enable and / or provide wireless access to wireless devices 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., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR Node Bs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, in other words, their transmit power levels), and may then be referred to as femto, pico, micro, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A part of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Still further examples of a network node include MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node, as described in more detail below.More generally, however, a network node may represent any suitable device (or group of devices) capable of, configured to, and / or operable to enable and / or provide wireless devices with access to a wireless network or to provide some service to wireless devices that have accessed the wireless network.

[0122] In FIG. 10, the network node 1060 includes a processing circuit 1070, a device readable medium 1080, an interface 1090, ancillary equipment 1084, a power source 1086, a power circuit 1087, and an antenna 1062. Although the network node 1060 shown in the example wireless network of FIG. 10 may represent a device including the shown combination of hardware components, other embodiments may comprise a network node with a different combination of components. It should be understood that a network node comprises any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. Moreover, although the components of the network node 1060 are illustrated as a single box located within a larger box or nested within multiple boxes, in reality the network node may comprise multiple different physical components that make up a single shown component (e.g., the device readable medium 1080 may comprise multiple separate hard drives as well as multiple RAM modules). Similarly, the network node 1060 may be assembled from multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have their own respective components. In some scenarios in which the network node 1060 comprises multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control several Node Bs. In such scenarios, each unique Node B and RNC pair may be considered as a single separate network node in some instances. In some embodiments, the network node 1060 may be configured to support several radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 1080 for different RATs) and some components may be reused (e.g., the same antenna 1062 may be shared by the RATs).The network node 1060 may also include multiple sets of the various shown components for different wireless technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies, integrated into the network node 1060. These wireless technologies may be integrated in the same or different chips or sets of chips and other components within the network node 1060.

[0123] The processing circuit 1070 is configured to perform any decision, computation, or similar operations (e.g., some acquisition operations) described herein as being provided by a network node. These operations performed by the processing circuit 1070 may include processing information acquired by the processing circuit 1070, for example, by transforming the acquired information into other information, comparing the acquired or transformed information with information stored in the network node, and / or performing one or more operations based on the acquired or transformed information and as a result of said processing making a decision.

[0124] The processing circuit 1070 may comprise one or more combinations 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 coded logic operable to provide network node 1060 functionality, either alone or in conjunction with other network node 1060 components, such as device readable medium 1080. For example, the processing circuit 1070 may execute instructions stored on the device readable medium 1080 or in memory within the processing circuit 1070. Such functionality may include providing any of the various wireless features, functions, or benefits described herein. In some embodiments, the processing circuit 1070 may include a system on a chip (SOC). In some embodiments, the processing circuit 1070 may include one or more of a radio frequency (RF) transceiver circuit 1072 and a baseband processing circuit 1074. In some embodiments, the radio frequency (RF) transceiver circuitry 1072 and the baseband processing circuitry 1074 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit, In alternative embodiments, some or all of the RF transceiver circuitry 1072 and the baseband processing circuitry 1074 may be on the same chip or set of chips, board, or unit.

[0125] In some 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 the processing circuitry 1070 executing instructions stored in the device-readable medium 1080, or in memory within the processing circuitry 1070. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 1070 without executing instructions stored in a separate or distinct device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuitry 1070 may be configured to perform the described functionality, whether or not it executes instructions stored in a device-readable storage medium. Benefits provided by such functionality are enjoyed by the processing circuitry 1070 alone, or by other components of the network node 1060, but by the network node 1060 as a whole, and / or by end users and wireless networks generally.

[0126] The device readable medium 1080 may comprise any form of volatile or non-volatile computer readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 1070. The device readable medium 1080 may store any suitable instructions, data or information, including applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 1070 and utilized by the network node 1060. The device-readable medium 1080 may be used to store calculations performed by the processing circuit 1070 and / or data received via the interface 1090. In some embodiments, the processing circuit 1070 and the device-readable medium 1080 may be considered to be integrated.

[0127] The interface 1090 is used in wired or wireless communication of signaling and / or data between the network node 1060, the network 1006, and / or the WD 1010. As shown, the interface 1090 comprises a port(s) / terminal(s) 1094 for sending and receiving data to and from the network 1006, for example, over a wired connection. The interface 1090 also includes a radio front-end circuit 1092, which is coupled to the antenna 1062 or, in some embodiments, may be part of the antenna 1062. The radio front-end circuit 1092 comprises a filter 1098 and an amplifier 1096. The radio front-end circuit 1092 may be connected to the antenna 1062 and the processing circuit 1070. The radio front-end circuit may be configured to condition signals communicated between the antenna 1062 and the processing circuit 1070. The radio front-end circuit 1092 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 1092 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1098 and / or amplifiers 1096. The radio signal may then be transmitted via the antenna 1062. Similarly, when receiving data, the antenna 1062 may collect the radio signal, which is then converted into digital data by the radio front-end circuit 1092. The digital data may be passed to the processing circuit 1070. In other embodiments, the interface may comprise different components and / or different combinations of components. In some alternative embodiments, the network node 1060 may not include a separate radio front-end circuit 1092, and instead, the processing circuit 1070 may comprise a radio front-end circuit and be connected to the antenna 1062 without a separate radio front-end circuit 1092. Similarly, in some embodiments, all or a portion of the RF transceiver circuit 1072 may be considered part of the interface 1090.In yet other embodiments, the interface 1090 may include one or more ports or terminals 1094, a radio front-end circuit 1092, and an RF transceiver circuit 1072 as part of a radio unit (not shown), and the interface 1090 may communicate with a baseband processing circuit 1074 that is part of a digital unit (not shown).

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

[0129] The antenna 1062, the interface 1090, and / or the processing circuit 1070 may be configured to perform any receiving operation and / or some obtaining operation described herein as being performed by a network node. Any information, data, and / or signal may be received from a wireless device, another network node, and / or any other network equipment. Similarly, the antenna 1062, the interface 1090, and / or the processing circuit 1070 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signal may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0130] The power circuit 1087 may comprise or be coupled to a power management circuit and is configured to supply power to the components of the network node 1060 for performing the functions described herein. The power circuit 1087 may receive power from a power source 1086. The power source 1086 and / or the power circuit 1087 may be configured to provide power to the various components of the network node 1060 in a form suitable for the respective components (e.g., at voltage and current levels required for each respective component). The power source 1086 may either be included in the power circuit 1087 and / or the network node 1060 or may be external to the power circuit 1087 and / or the network node 1060. For example, the network node 1060 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source supplies power to the power circuit 1087. As a further example, the power source 1086 may comprise a power source in the form of a battery or battery pack connected to or integrated in the power circuit 1087. The battery may provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used. Alternative embodiments of the network node 1060 may include additional components other than those shown in FIG. 10 that may be responsible for providing some aspects of the functionality of the network node, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, the network node 1060 may include user interface devices to enable input of information into the network node 1060 and output of information from the network node 1060. This may enable a user to perform diagnostics, maintenance, repair, and other administrative functions for the network node 1060.

[0131] A wireless device (WD) as used herein refers to a device capable of, configured to, 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, radio, infrared, and / or other types of signals suitable for conveying information over the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predefined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cell phones, voice-over-IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premise equipment (CPE), in-vehicle wireless terminal devices, etc. A WD may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), in which case it may be referred to as a D2D communications device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another WD and / or network node.The WD may be a machine-to-machine (M2M) device in this case, which may be referred to as an MTC device in the 3GPP context. As one particular example, the WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other equipment capable of monitoring and / or reporting on its operational status, or other functions related to its operation. The WD described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, the WD described above may be mobile, in which case the device may be referred to as a mobile device or mobile terminal.

[0132] As shown, wireless device 1010 includes antenna 1011, interface 1014, processing circuitry 1020, device-readable medium 1030, user interface equipment 1032, auxiliary equipment 1034, power source 1036, and power circuitry 1037. WD 1010 may include multiple sets of one or more of the shown components for different wireless technologies supported by WD 1010, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to name a few. These wireless technologies may be integrated on the same or different chip or set of chips as other components within WD 1010.

[0133] The antenna 1011 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to the interface 1014. In some alternative embodiments, the antenna 1011 may be separate from the WD 1010 and connectable to the WD 1010 through an interface or port. The antenna 1011, the interface 1014, and / or the processing circuitry 1020 may be configured to perform any receiving or transmitting operation described herein as being performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the wireless front-end circuitry and / or the antenna 1011 may be considered an interface.

[0134] As shown, the interface 1014 comprises a radio front-end circuit 1012 and an antenna 1011. The radio front-end circuit 1012 comprises one or more filters 1018 and an amplifier 1016. The radio front-end circuit 1014 is connected to the antenna 1011 and the processing circuit 1020 and is configured to condition signals communicated between the antenna 1011 and the processing circuit 1020. The radio front-end circuit 1012 may be coupled to the antenna 1011 or may be part of the antenna 1011. In some embodiments, the WD 1010 may not include a separate radio front-end circuit 1012, rather the processing circuit 1020 may comprise a radio front-end circuit and be connected to the antenna 1011. Similarly, in some embodiments, some or all of the RF transceiver circuit 1022 may be considered part of the interface 1014. The radio front-end circuit 1012 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuitry 1012 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1018 and / or amplifiers 1016. The radio signal may then be transmitted via the antenna 1011. Similarly, when receiving data, the antenna 1011 may collect the radio signal, which is then converted into digital data by the radio front-end circuitry 1012. The digital data may be passed to the processing circuitry 1020. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0135] The processing circuit 1020 may comprise one or more combinations 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 coded logic operable to provide WD1010 functionality, either alone or in conjunction with other WD1010 components, such as the device readable medium 1030. Such functionality may include providing any of the various wireless features or benefits described herein. For example, the processing circuit 1020 may execute instructions stored on the device readable medium 1030 or in a memory within the processing circuit 1020 to provide functionality disclosed herein. As shown, the processing circuit 1020 includes one or more of an RF transceiver circuit 1022, a baseband processing circuit 1024, and an application processing circuit 1026. In other embodiments, the processing circuit may comprise different components and / or different combinations of components. In some embodiments, the processing circuitry 1020 of the WD 1010 may comprise a SOC. In some embodiments, the RF transceiver circuitry 1022, the baseband processing circuitry 1024, and the application processing circuitry 1026 may be on separate chips or sets of chips. In alternative embodiments, some or all of the baseband processing circuitry 1024 and the application processing circuitry 1026 may be combined into one chip or set of chips, and the RF transceiver circuitry 1022 may be on a separate chip or set of chips. In yet further alternative embodiments, some or all of the RF transceiver circuitry 1022 and the baseband processing circuitry 1024 may be on the same chip or set of chips, and the application processing circuitry 1026 may be on a separate chip or set of chips. In yet other alternative embodiments, some or all of the RF transceiver circuitry 1022, the baseband processing circuitry 1024, and the application processing circuitry 1026 may be combined in the same chip or set of chips.In some embodiments, the RF transceiver circuitry 1022 may be part of the interface 1014. The RF transceiver circuitry 1022 may condition RF signals for the processing circuitry 1020.

[0136] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by the processing circuitry 1020 executing instructions stored on a device-readable medium 1030, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 1020 without executing instructions stored on a separate or distinct device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, the processing circuitry 1020 may be configured to perform the described functionality, regardless of whether it executes instructions stored on a device-readable storage medium. Benefits provided by such functionality are enjoyed by the WD 1010 as a whole, and / or by end users and wireless networks in general, but not limited to the processing circuitry 1020 alone or other components of the WD 1010.

[0137] The processing circuit 1020 may be configured to perform any of the decision, calculation, or similar operations (e.g., some of the acquisition operations) described herein as being performed by the WD. These operations as performed by the processing circuit 1020 may include processing information acquired by the processing circuit 1020, for example, by transforming the acquired information into other information, comparing the acquired or transformed information with information stored by the WD 1010, and / or performing one or more operations based on the acquired or transformed information and as a result of the processing making a decision.

[0138] The device-readable medium 1030 may be operable to store applications including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that may be executed by the processing circuit 1020. The device-readable medium 1030 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 1020. In some embodiments, the processing circuit 1020 and the device-readable medium 1030 may be considered to be integrated.

[0139] The user interface device 1032 may provide components that allow a human user to interact with the WD 1010. Such interaction may be of many forms, such as visual, auditory, tactile, etc. The user interface device 1032 may be operable to produce output to the user and to allow the user to provide input to the WD 1010. The type of interaction may vary depending on the type of user interface device 1032 installed on the WD 1010. For example, if the WD 1010 is a smartphone, the interaction may be via a touch screen, and if the WD 1010 is a smart meter, the interaction may be through a screen that provides usage (e.g., number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 1032 may include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface device 1032 is configured to allow input of information to the WD 1010 and is connected to the processing circuit 1020 to allow the processing circuit 1020 to process the input information. The user interface device 1032 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device 1032 is also configured to enable output of information from the WD 1010 and to enable the processing circuitry 1020 to output information from the WD 1010. The user interface device 1032 may include, for example, a speaker, a display, vibration circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface device 1032, the WD 1010 may communicate with an end user and / or a wireless network, enabling the end user and / or the wireless network to benefit from the functionality described herein.

[0140] The auxiliary device 1034 is operable to provide more specific functionality that may not generally be implemented by a WD. It may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communication, such as wired communication, etc. The inclusion of components of the auxiliary device 1034 and the types of components of the auxiliary device 1034 may vary depending on the embodiment and / or scenario.

[0141] The power source 1036 may be in the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The WD 1010 may further comprise a power circuit 1037 for delivering power from the power source 1036 to various parts of the WD 1010 that require power from the power source 1036 to perform any of the functions described or indicated herein. The power circuit 1037 may comprise a power management circuit in some embodiments. The power circuit 1037 may additionally or alternatively be operable to receive power from an external power source, in which case the WD 1010 may be connectable to an external power source (such as an electrical outlet) via an input circuit or interface, such as a power cable. The power circuit 1037 may also be operable in some embodiments to deliver power from the external power source to the power source 1036. This may be for charging the power source 1036, for example. Power circuitry 1037 may perform any formatting, conversion, or other modification on the power from power source 1036 to make the power suitable for the respective components of WD 1010 that are being powered.

[0142] FIG. 11 illustrates an embodiment of a UE according to various aspects described herein. User equipment or UE as used herein does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or may not be initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. The UE 11200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including an NB-IoT UE, a machine-type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. The UE 1100 shown in FIG. 11 is an example of a WD configured for communication according to one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as the 3GPP GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, while FIG. 11 is a UE, the components described herein are equally applicable to a WD and vice versa. In FIG. 11, the UE 1100 includes a processing circuit 1101 operably coupled to an input / output interface 1105, a radio frequency (RF) interface 1109, a network connection interface 1111, a memory 1115 including a random access memory (RAM) 1117, a read only memory (ROM) 1119, a storage medium 1121, etc., a communication subsystem 1131, a power source 1133, and / or other components, or any combination thereof. The storage medium 1121 includes an operating system 1123, an application program 1125, and data 1127. In other embodiments, storage medium 1121 may contain other similar types of information.Some UEs may utilize all of the components shown in FIG. 11 or only a subset of those components. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc. In FIG. 11, processing circuitry 1101 may be configured to process computer instructions and data. Processing circuitry 1101 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic with appropriate firmware, one or more pre-programmed, general-purpose processors, such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, processing circuitry 1101 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0143] In the illustrated embodiment, the input / output interface 1105 may be configured to provide an input device, an output device, or a communication interface to an input / output device. The UE 1100 may be configured to use an output device via the input / output interface 1105. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 1100. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE 1100 may be configured to use an input device via the input / output interface 1105 to allow a user to capture information on the UE 1100. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light 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 a light sensor.

[0144] In FIG. 11, the RF interface 1109 may be configured to provide a communication interface to RF components, such as a transmitter, a receiver, and an antenna. The network connection interface 1111 may be configured to provide a communication interface to a network 1143a. The network 1143a may encompass a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another similar network, or any combination thereof. For example, the network 1143a may comprise a Wi-Fi network. The network connection interface 1111 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, etc. The network connection interface 1111 may implement receiver and transmitter functions appropriate for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software or firmware, or may alternatively be implemented separately.

[0145] The RAM 1117 may be configured to interface to the processing circuit 1101 via the bus 1102 to provide storage or caching of data or computer instructions during execution of software programs, such as an operating system, application programs, and device drivers. The ROM 1119 may be configured to provide computer instructions or data to the processing circuit 1101. For example, the ROM 1119 may be configured to store unchanging low-level system code or data for basic system functions, such as basic input / output (I / O), booting, or receiving keystrokes from a keyboard, stored in non-volatile memory. The storage medium 1121 may be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, the storage medium 1121 may be configured to include an operating system 1123, an application program 1125, such as a web browser application, a widget or gadget engine, or another application, and data files 1127. The storage medium 1121 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 1100.

[0146] The storage medium 1121 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-Ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory such as a subscriber identity module or a removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 1121 may enable the UE 1100 to access computer executable instructions, application programs, etc. stored in a temporary or non-transitory memory medium, offload data, or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied in the storage medium 1121, and the storage medium 1121 may comprise a device-readable medium.

[0147] In FIG. 11, the processing circuit 1101 may be configured to communicate with the network 1143b using the communication subsystem 1131. The network 1143a and the network 1143b may be the same network or networks or different networks or networks. The communication subsystem 1131 may be configured to include one or more transceivers used to communicate with the network 1143b. For example, the communication subsystem 1131 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, etc. Each transceiver may include a transmitter 1133 and / or a receiver 1135 for implementing a transmitter function or a receiver function, respectively, appropriate for a RAN link (e.g., frequency allocation, etc.). Furthermore, the transmitter 1133 and receiver 1135 of each transceiver may share circuit components, software or firmware, or may alternatively be implemented separately.

[0148] In the illustrated embodiment, the communication capabilities of the communication subsystem 1131 may include data communications, voice communications, multimedia communications, short-range communications such as Bluetooth, near-field communications, location-based communications such as using a global positioning system (GPS) to determine location, another similar communication capability, or any combination thereof. For example, the communication subsystem 1131 may include cellular communications, Wi-Fi communications, Bluetooth communications, and GPS communications. The network 1143b 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 communications network, another similar network, or any combination thereof. For example, the network 1143b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power source 1113 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1100.

[0149] The features, benefits and / or functions described herein may be implemented in one of the components of the UE 1100 or distributed across multiple components of the UE 1100. Furthermore, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 1131 may be configured to include any of the components described herein. Furthermore, the processing circuit 1101 may be configured to communicate with any of such components over the bus 1102. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processing circuit 1101, perform the corresponding functions described herein. In another example, the functions of any of such components may be distributed between the processing circuit 1101 and the communication subsystem 1131. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0150] FIG. 12 is a schematic block diagram illustrating a virtualization environment 1200 in which functions implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. Virtualization as used herein may apply 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 a component of that device, and relates to implementations 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). In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1200 hosted by one or more of the hardware nodes 1230. Furthermore, 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), the network node may be fully virtualized.

[0151] The functionality may be implemented by one or more applications 1220 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 1220 are run in a virtualization environment 1200, which provides hardware 1230 comprising a processing circuit 1260 and a memory 1290. The memory 1290 includes instructions 1295 executable by the processing circuit 1260 such that the applications 1220 are operable to provide one or more of the features, functions, and / or benefits of the embodiments disclosed herein.

[0152] The virtualization environment 1200 includes a general-purpose or dedicated network hardware device 1230 that includes a set of one or more processors or processing circuitry 1260, which may be a commercial off-the-shelf (COTS) processor, a dedicated application-specific integrated circuit (ASIC), or any other type of processing circuitry including digital or analog hardware components or dedicated processors. Each hardware device may include a memory 1290-1, which may be a non-persistent memory for temporarily storing instructions 1295 or software executed by the processing circuitry 1260. Each hardware device may include one or more network interface controllers (NICs) 1270, also known as network interface cards, which include a physical network interface 1280. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 1290-2 that stores software 1295 and / or instructions executable by the processing circuitry 1260. Software 1295 may include any type of software, including software for instantiating one or more virtualization layers 1250 (also called hypervisors), software for running virtual machines 1240, and software that enables it to perform the functions, features and / or benefits described in connection with some embodiments described herein.

[0153] The virtual machines 1240 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of the virtual appliance 1220 instances may be implemented on one or more of the virtual machines 1240, and the implementations may be done in different ways.

[0154] During operation, the processing circuitry 1260 executes the software 1295 to instantiate a hypervisor or virtualization layer 1250, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 1250 may present a virtual operating platform to the virtual machine 1240 that appears as networking hardware. As shown in FIG. 12, the hardware 1230 may be a standalone network node with general or specific components. The hardware 1230 may include an antenna 12225 and may implement some functions via virtualization. Alternatively, the hardware 1230 may be part of a larger cluster of hardware (e.g., as in the case of a data center or customer premises equipment (CPE)) that is managed via a management and orchestration (MANO) 12100 where many hardware nodes work together and, among other things, oversee the lifecycle management of the application 1220.

[0155] Hardware virtualization is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0156] In the context of NFV, virtual machine 1240 may be a software implementation of a physical machine that runs programs as if those programs were running on a physical, non-virtualized machine. Each virtual machine 1240 and the portion of hardware 1230 on which it runs, whether hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other ones of virtual machines 1240, form a separate Virtual Network Element (VNE).

[0157] Further in the context of NFV, a Virtual Network Function (VNF) is responsible for handling a specific network function running on one or more virtual machines 1240 on top of the hardware networking infrastructure 1230 and corresponds to application 1220 in FIG. 12.

[0158] In some embodiments, one or more radio units 12200, each including one or more transmitters 12220 and one or more receivers 12210, may be coupled to one or more antennas 12225. The radio units 12200 may communicate directly with a hardware node 1230 via one or more suitable network interfaces and may be used in combination with a virtualization component to provide a virtual node with wireless capabilities, such as a wireless access node or base station.

[0159] In some embodiments, some signaling may be accomplished using a control system 12230, which may alternatively be used for communication between the hardware nodes 1230 and the wireless unit 12200.

[0160] Referring to Fig. 13, according to one embodiment, a communication system includes a communication network 1310, such as a 3GPP type cellular network, comprising an access network 1311, such as a wireless access network, and a core network 1314. The access network 1311 comprises a number of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c can be connected to the core network 1314 over a wired or wireless connection 1315. A first UE 1391 located in the coverage area 1313c is configured to wirelessly connect to or be paged by the corresponding base station 1312c. A second UE 1392 in the coverage area 1313a can be wirelessly connected to the corresponding base station 1312a. Although multiple UEs 1391, 1392 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or where only one UE is connected to the corresponding base station 1312.

[0161] The communication network 1310 is itself connected to a host computer 1330, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 1330 may be owned or under the control of a service provider, or may be operated by or on behalf of the service provider. The connections 1321 and 1322 between the communication network 1310 and the host computer 1330 may extend directly from the core network 1314 to the host computer 1330, or may proceed through an optional intermediate network 1320. The intermediate network 1320 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 1320 may be a backbone network or the Internet, if any, and in particular the intermediate network 1320 may comprise two or more sub-networks (not shown).

[0162] The communication system of FIG. 13 as a whole enables connectivity between connected UEs 1391, 1392 and a host computer 1330. The connectivity may be described as an over-the-top (OTT) connection 1350. The host computer 1330 and connected UEs 1391, 1392 are configured to communicate data and / or signaling via the OTT connection 1350 using the access network 1311, the core network 1314, any intermediate networks 1320, and possible further infrastructure (not shown) as intermediaries. The OTT connection 1350 may be transparent in the sense that the participating communication devices through which the OTT connection 1350 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 1312 may not be or need not be informed of the past routing of incoming downlink communications involving data originating from the host computer 1330 to be forwarded (e.g., handed over) to the connected UE 1391. Similarly, the base station 1312 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 1391 and destined for the host computer 1330 .

[0163] Next, an exemplary implementation of the UE, base station and host computer described in the previous paragraph according to an embodiment will be described with reference to FIG. 14. In the communication system 1400, the host computer 1410 comprises hardware 1415 including a communication interface 1416 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 1400. The host computer 1410 further comprises a processing circuit 1418, which may have storage and / or processing capabilities. In particular, the processing circuit 1418 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 1410 further comprises software 1411, which is stored in or accessible by the host computer 1410 and is executable by the processing circuit 1418. The software 1411 includes a host application 1412. The host application 1412 may be operable to provide services to a remote user, such as the UE 1430 connecting via an OTT connection 1450 that terminates at the UE 1430 and the host computer 1410. In providing services to the remote user, the host application 1412 may provide user data that is transmitted using the OTT connection 1450.

[0164] The communication system 1400 further includes a base station 1420 provided in the communication system, the base station 1420 comprising hardware 1425 enabling the base station 1420 to communicate with the host computer 1410 and the UE 1430. The hardware 1425 may include a communication interface 1426 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 1400, as well as a wireless interface 1427 for setting up and maintaining at least a wireless connection 1470 with a UE 1430 located in a coverage area (not shown in FIG. 14) served by the base station 1420. The communication interface 1426 may be configured to facilitate a connection 1460 to the host computer 1410. The connection 1460 may be direct or alternatively the connection 1460 may pass through a core network (not shown in FIG. 14) of the communication system and / or one or more intermediate networks outside the communication system. In the illustrated embodiment, the hardware 1425 of the base station 1420 further includes processing circuitry 1428, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 1420 further has software 1421 stored internally or accessible via an external connection.

[0165] The communication system 1400 further includes the UE 1430 already mentioned. The hardware 1435 of the UE 1430 may include a wireless interface 1437 configured to set up and maintain a wireless connection 1470 with a base station serving a coverage area in which the UE 1430 is currently located. The hardware 1435 of the UE 1430 further includes a processing circuit 1438, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof adapted to execute instructions (not shown). The UE 1430 further includes software 1431 stored in or accessible by the UE 1430 and executable by the processing circuit 1438. The software 1431 includes a client application 1432. The client application 1432 may be operable to provide services to a human or non-human user via the UE 1430 with the support of the host computer 1410. At the host computer 1410, a running host application 1412 may communicate with a running client application 1432 via an OTT connection 1450 that terminates at the UE 1430 and the host computer 1410. In providing services to a user, the client application 1432 may receive request data from the host application 1412 and provide user data in response to the request data. The OTT connection 1450 may transfer both the request data and the user data. The client application 1432 may interact with the user to generate the user data that the client application 1432 provides.

[0166] It should be noted that the host computer 1410, base station 1420, and UE 1430 shown in FIG. 14 may be similar or equivalent to the host computer 1330, one of the base stations 1312a, 1312b, 1312c, and one of the UEs 1391, 1392, respectively, of FIG. 13. That is, the inner workings of these entities may be as shown in FIG. 14, and separately, the surrounding network topology may be that of FIG. 13. In FIG. 14, the OTT connection 1450 is depicted abstractly to show the communication between the host computer 1410 and the UE 1430 via the base station 1420, without explicit reference to intermediate devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 1430 or from the service provider operating the host computer 1410, or both. While the OTT connection 1450 is active, the network infrastructure may further determine that the network infrastructure dynamically changes the routing (eg, based on load balancing considerations or reconfiguration of the network).

[0167] The wireless connection 1470 between the UE 1430 and the base station 1420 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 1430 using the OTT connection 1450 of which the wireless connection 1470 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate and latency that may be achieved on the downlink channel, thereby providing benefits such as reduced user latency and improved responsiveness.

[0168] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 1450 between the host computer 1410 and the UE 1430 in response to fluctuations in the measurement results. The measurement procedures and / or the network function for reconfiguring the OTT connection 1450 may be implemented in the software 1411 and hardware 1415 of the host computer 1410 or in the software 1431 and hardware 1435 of the UE 1430, or both. In an embodiment, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 1450 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 1411, 1431 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1450 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 1420, and the reconfiguration may be unknown or imperceptible to the base station 1420. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 1410 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in the software 1411 and 1431 causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 1450 while the software 1411 and 1431 monitors propagation times, errors, etc.

[0169] FIG. 15 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 13 and FIG. 14. For simplicity of the disclosure, only drawing references to FIG. 15 are included in this section. In step 1510, the host computer provides user data. In sub-step 1511 of step 1510 (which may be optional), the host computer provides the user data by executing a host application. In step 1520, the host computer initiates a transmission carrying the user data to the UE. In step 1530 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE, according to the teachings of the embodiments described throughout this disclosure. In step 1540 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0170] FIG. 16 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 13 and FIG. 14. For simplicity of the disclosure, only drawing references to FIG. 16 are included in this section. In step 1610 of the method, the host computer provides user data. In an optional sub-step (not shown), 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. The transmission may proceed via the base station according to the teachings of the embodiments described throughout this disclosure. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.

[0171] FIG. 17 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 13 and FIG. 14. For simplicity of the disclosure, only drawing references to FIG. 17 are included in this section. In step 1710 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1720, the UE provides user data. In sub-step 1721 (which may be optional) of step 1720, the UE provides the user data by executing a client application. In sub-step 1711 (which may be optional) of step 1710, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step 1730 (which may be optional). In method step 1740, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0172] FIG. 18 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 13 and FIG. 14. For simplicity of the disclosure, only drawing references to FIG. 18 are included in this section. In step 1810 (which may be optional), the base station receives user data from the UE, according to the teachings of the embodiments described throughout this disclosure. In step 1820 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1830 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0173] Any suitable steps, methods, features, functions, or benefits disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated 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, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.

[0174] FIG. 19 illustrates a schematic block diagram of an apparatus 190 in a wireless network (e.g., the wireless network shown in FIG. 10). The apparatus may be implemented in a wireless device or a network node (e.g., the wireless device 1010 or the network node 1060 shown in FIG. 10). The apparatus 1900 is operable to perform the example method described with respect to FIG. 7 and, possibly, any other process or method disclosed herein. It should also be understood that the method of FIG. 7 is not necessarily performed solely by the apparatus 1900. At least some operations of the method may be performed by one or more other entities. The virtual apparatus 1900 may comprise processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated 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, and the like. The program code stored in the memory, in some embodiments, includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the receiving unit 1902, the identifying unit 1904, the transmitting unit 1906, and any other suitable units of the device 1900 to perform corresponding functions according to one or more embodiments of the present disclosure.

[0175] As shown in FIG. 19, the apparatus 1900 includes a receiving unit 1902 for receiving downlink control information triggering aperiodic SRS transmission, an identification unit 1904 for identifying a slot indicated by the downlink control information, and a transmitting unit 1906 for transmitting an SRS in a slot that is not a downlink slot when the slot indicated by the downlink control information is a downlink slot.

[0176] FIG. 20 shows a schematic block diagram of an apparatus 2000 in a wireless network (e.g., the wireless network shown in FIG. 10). The apparatus may be implemented in a wireless device or a network node (e.g., the wireless device 1010 or the network node 1060 shown in FIG. 10). The apparatus 2000 is operable to perform the example method described with respect to FIG. 8 and, possibly, any other process or method disclosed herein. It should also be understood that the method of FIG. 8 is not necessarily performed solely by the apparatus 2000. At least some operations of the method may be performed by one or more other entities. The virtual apparatus 2000 may comprise processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated 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, and the like. The program code stored in the memory, in some embodiments, includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the transmitting unit 2002, and any other suitable units of the device 2000, to perform corresponding functions according to one or more embodiments of the present disclosure.

[0177] As shown in FIG. 20 , the apparatus 2000 includes a transmitting unit 2002 for transmitting downlink control information to a UE, where the downlink control information triggers aperiodic SRS transmission by the UE, where the downlink control information identifies a slot for the aperiodic SRS transmission by the UE, where the slot identified for the aperiodic SRS transmission by the UE is a downlink slot.

[0178] The term unit may have its conventional meaning in the field of electronics, electrical devices, and / or electronic devices and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logical solid and / or discrete devices, computer programs or instructions, etc., for performing a respective task, procedure, computation, output, and / or display function, such as those described herein.

[0179] Abbreviation At least some of the following abbreviations may be used in this disclosure. In case of inconsistencies between abbreviations, how the abbreviation is used above should be preferred. If listed multiple times below, the first listing should be preferred over subsequent listing(s). 3GPP 3rd Generation Partnership Project 5G 5th Generation CA Carrier Aggregation CC Carrier Components CDMA Code Division Multiple Access CIR Channel Impulse Response CSI Channel State Information DCCH Dedicated Control Channel DL Downlink DM Demodulation DMRS demodulation reference signal eNB E-UTRAN Node B E-SMLC Evolved Serving Mobile Location Center E-UTRA Evolved UTRA E-UTRAN Evolved UTRAN gNB NR base station GSM Global System for Mobile Communications HO Handover LTE Long-Term Evolution MDT Drive Test Minimization MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NR new radio OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operation Support System O&M operation and maintenance PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PUSCH Physical Uplink Shared Channel RAN Radio Access Network RAT Radio Access Technology RNC Radio Network Controller RRC Radio Resource Control RS reference signal SCH Synchronization Channel SDU Service Data Unit SI System Information SON Self-optimizing Network SS Sync Signal TDD Time Division Duplex UE User Equipment UL Uplink UMTS Universal Mobile Telecommunication System UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA Wide CDMA WLAN Wide Local Area Network

Claims

1. 1. A method implemented by a wireless device for transmitting a sounding reference signal (SRS), the method comprising: Receiving downlink control information (702) that triggers aperiodic SRS transmission; Identifying (704) a slot indicated by the downlink control information; If the slot indicated by the downlink control information is a downlink slot, transmitting the aperiodic SRS in a slot that is not a downlink slot (706); A method comprising:

2. 2. The method of claim 1, comprising transmitting the aperiodic SRS in a first slot that is after the slot indicated by the downlink control information and that is not a downlink slot.

3. 2. The method of claim 1, comprising transmitting the aperiodic SRS in a second slot that is after the slot indicated by the downlink control information and is not a downlink slot.

4. 2. The method of claim 1, comprising transmitting the aperiodic SRS in a qth slot that is after the slot indicated by the downlink control information and is not a downlink slot, where a value of q is indicated by a codepoint of an SRS request field in the downlink control information.

5. The method of claim 1 , further comprising transmitting the aperiodic SRS in an uplink slot.

6. The method of claim 1 , comprising transmitting the aperiodic SRS in designated symbols of a flexible slot, the designated symbols being not downlink symbols.

7. 7. The method of claim 1, comprising receiving the downlink control information on a Physical Downlink Control Channel (PDCCH).

8. Identifying the slot indicated by the downlink control information comprises: receiving the downlink control information in a third slot; identifying the slot indicated by the downlink control information based on a nominal slot offset from the third slot, the nominal slot offset being the slot indicated by the downlink control information; The method of any one of claims 1 to 7, comprising:

9. The method of claim 8 , wherein the nominal slot offset is implicitly indicated by an SRS request field of the downlink control information.

10. 10. The method of claim 9, wherein the nominal slot offset is selected from a plurality of predetermined possible nominal slot offsets and is implicitly indicated by the SRS request field of the downlink control information.

11. 11. The method of claim 10, wherein each of the possible nominal slot offsets is configured using an RRC field, and each code point of the SRS request field triggers one or more SRS resource sets, each SRS resource set being associated with a nominal slot offset.

12. 12. The method of claim 1, further comprising, as a preliminary step, obtaining a slot format configuration.

13. 13. The method of claim 12, wherein the slot format configuration is a quasi-static time division duplex (TDD) configuration provided by a higher protocol layer.

14. 14. The method of claim 13, wherein the semi-static time division duplex (TDD) configuration is provided by a radio resource control protocol layer.

15. The method of claim 12 , wherein the slot format configuration is indicated by different downlink control information.

16. The method of claim 1 , comprising transmitting the aperiodic SRS in symbols of the slot.

17. Providing user data; forwarding said user data to a host computer via said transmission to a base station; 16. The method of claim 1, further comprising:

18. A method implemented by a communication system including a UE and a base station that triggers aperiodic Sounding Reference Signal (SRS) transmission to the UE, the method comprising: the base station transmitting downlink control information to the UE, the downlink control information triggering the UE to transmit the aperiodic SRS; the UE identifying a slot indicated by the downlink control information; If the slot identified by the UE is a downlink slot, the UE transmits the aperiodic SRS in a first slot that is after the slot indicated by the downlink control information and is not a downlink slot; A method comprising:

19. The method of claim 18, wherein the downlink control information is transmitted in a third slot, and the downlink control information indicates an offset relative to the third slot for the UE to identify the slot for the aperiodic SRS transmission.

20. 20. The method of claim 19, comprising indicating the offset implicitly by an SRS request field of the downlink control information.

21. 21. The method of claim 20, wherein the offset is selected from a plurality of predetermined possible nominal slot offsets.

22. 22. A method according to any one of claims 18 to 21, comprising indicating slot format configuration in the downlink control information.

23. 23. The method of any one of claims 18 to 22, comprising transmitting the downlink control information on a Physical Downlink Control Channel (PDCCH).

24. 24. The method of claim 18, further comprising transmitting, in the downlink control information, information identifying which slot after the identified slot should be used for the aperiodic SRS transmission.

25. Obtaining user data; forwarding said user data to a host computer or a wireless device; 25. The method of any one of claims 18 to 24, further comprising:

26. A wireless device configured to perform the method of any one of claims 1 to 17.

27. A communication system including a UE and a base station configured to implement a method according to any one of claims 18 to 25.

Citation Information

Patent Citations

  • Terminal device, base station device, communications method, and integrated circuit

    WO2014156617A1

  • Terminal device, base station, method, and recording medium

    WO2019097929A1