Capability Signaling in a Wireless Communication Network

A wireless device (12) transmits signaling (26) which indicates that the wireless device (12) supports cross-slot scheduling. Support for cross-slot scheduling indicates a range of values that the wireless device (12) supports for a triggering offset (20). A triggering offset (20) is an offset between: (i) a slot containing downlink control information (14) that triggers a set (16) of aperiodic channel state information reference signal, CSI-RS, resources; and (ii) a slot in which the set (16) of aperiodic CSI-RS resources is transmitted. The signaling (26) may enable a network node (15) that receives the signaling (26) to correspondingly transmit, to the wireless device (12), a control message which configures the wireless device (12) with a triggering offset (20) that has a value within the indicated range of values.

TECHNICAL FIELD

The present application relates generally to a wireless communication network, and relates more particularly to capability signaling in such a network.

BACKGROUND

Cross-slot scheduling is one of the mechanisms introduced in New Radio (NR) Rel-16 to allow user equipment (UE) power saving. The UE is configured with a minimum scheduling offset restriction that allows the UE opportunity to micro-sleep by ensuring a minimum gap between a control channel and the corresponding downlink signal/channel that a UE is expected to receive based on the Downlink Control Information (DCI) in the control channel, e.g., a Physical Downlink Control Channel (PDCCH). A similar gap may be ensured between a control channel and an uplink transmission for uplink. The same minimum gap that applies to Physical Downlink Shared Channel (PDSCH) scheduling is also applied for aperiodic Channel State Information Reference Signal (A-CSI RS) reception. Thus, the two parameters (KO or PDCCH-to-PDSCH scheduling offset) and A-CSI triggering offset have some inter-dependencies, when a UE is configured with a minimum scheduling offset restriction.

The value ranges for minimum KO value (0 to 16), A-CSI-RS triggering offset (e.g. {0, 1, 2, 3, 4, 16, 24} slots.), UE assistance related to minimum KO values, and possible set of KO values (0 to 32) may have different values and ranges, which can lead to undesirable scheduling restrictions or delays in cases with mismatch. For example, if a minimum KO value of 5 is enforced, the network may be forced to use a large A-CSI-RS triggering offset (e.g. 16 slots). Therefore, the value range of A-CSI-RS triggering offset was extended for cross-slot scheduling. For other reasons, the value range of A-CSI-RS triggering offset was extended for cross-carrier A-CSI triggering with different numerologies between PDCCH and CSI-RS. There currently exist certain challenge(s). Existing signaling proves insufficient for the network to unambiguously know a UE's capability to support the extended value range of A-CSI-RS triggering offset, at least under some conditions for the cross-slot scheduling case. The conditions may include for instance a condition under which the extended range can be configured for a UE indicating support of such capability.

SUMMARY

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. Some embodiments use UE capability signaling to explicitly indicate to the network whether and under what conditions the extended offset value range for A-CSI-RS triggering offset is supported, e.g., for cross-slot scheduling based UE power savings and/or for cross-carrier A-CSI-RS triggering with different numerologies.

In some embodiments, a UE indicating support for “Cross Slot Scheduling” also indicates the capability (e.g. implicitly or explicitly) to support the new Radio Resource Control (RRC) parameter (e.g. aperiodicTriggeringOffsetExt-r16.) and/or the extended offset value range for A-CSI-RS triggering offset. For example, in the implicit case, support of extended offset value range for A-CSI triggering offset via aperiodicTriggeringOffsetExt-r16 can become a component within the capability to “Cross Slot Scheduling”.

In other embodiments, a UE indicates a separate capability to support the new RRC parameter (e.g. aperiodicTriggeringOffsetExt-r16.) and/or the extended offset value range for A-CSI triggering offset. For example, the capability can be separate from the capability indicating support for “Cross slot scheduling”.

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

Some embodiments make the UE capability unambiguous with respect to the support of extended offset value range for A-CSI-RS triggering offset, e.g., for the case with cross-slot scheduling based power savings.

Generally, then, some embodiments herein include a method performed by a wireless device. The method comprises transmitting signaling which indicates that the wireless device supports cross-slot scheduling. Support for cross-slot scheduling indicates a range of values that the wireless device supports for a triggering offset. Here, a triggering offset is an offset between a slot containing downlink control information that triggers a set of aperiodic channel state information reference signal, CSI-RS, resources and a slot in which the set of aperiodic CSI-RS resources is transmitted.

In some embodiments, the method further comprises, after transmitting the signaling, receiving a control message that configures the wireless device with a triggering offset that has a value within the indicated range of values. In one or more of these embodiments, the control message includes a first parameter configurable to indicate a triggering offset within the indicated range of values. The control message may also be configurable with a second parameter for indicating a triggering offset within a different range of values, where the indicated range of values includes at least one value not included in the different range of values.

In some embodiments, the method further comprises receiving, in a first slot, downlink control information that triggers a set of aperiodic CSI-RS resources, and receiving, in a second slot, CSI-RS on the set of aperiodic CSI-RS resources triggered by the received downlink control information. In this case, the offset between the first slot and the second slot has a value within the indicated range of values. In one or more of these embodiments, the method further comprises, based on the triggering offset configured by the received control message, operating in a sleep state between the first slot and the second slot. In one or more of these embodiments. the downlink control information is received from a first cell and the CSI-RS is received from a second cell. In this case, the second cell has a higher subcarrier spacing, SCS, than the first cell.

In some embodiments, the indicated range of values for the triggering offset is extended as compared to a range of values supportable by another type of wireless device for the triggering offset.

In some embodiments, the indicated range of values for the triggering offset includes values above a value threshold and/or includes a number of values above a range size threshold.

Other embodiments herein include a method performed by a network node. The method comprises receiving signaling which indicates that a wireless device supports cross-slot scheduling. Support for cross-slot scheduling indicates a range of values that the wireless device supports for a triggering offset. Here, a triggering offset is an offset between a slot containing downlink control information that triggers a set of aperiodic channel state information reference signal, CSI-RS, resources, and a slot in which the set of aperiodic CSI-RS resources is transmitted.

In some embodiments, the method further comprises transmitting, to the wireless device, a control message which configures the wireless device with a triggering offset that has a value within the indicated range of values. In one or more of these embodiments, the control message includes a first parameter configurable to indicate a triggering offset within the indicated range of values. In this case, the control message is configurable with a second parameter for indicating a triggering offset within a different range of values, and the indicated range of values includes at least one value not included in the different range of values.

In some embodiments, the method further comprises transmitting aperiodic CSI-RS to the wireless device based on the received signaling.

In some embodiments, the method further comprises transmitting aperiodic CSI-RS to the wireless device on a set of aperiodic CSI-RS resources within a slot that is determined based on the received signaling.

In some embodiments, the method further comprises transmitting, in a first slot, to the wireless device, downlink control information that triggers a set of aperiodic CSI-RS resources. Additionally or alternatively, the method further comprises transmitting, in a second slot, to the wireless device, CSI-RS on the set of aperiodic CSI-RS resources triggered by the transmitted downlink control information. In this case, the offset between the first slot and the second slot has a value within the indicated range of values. In one or more of these embodiments, the downlink control information is transmitted from a first cell and the CSI-RS is transmitted from a second cell, and the second cell has a higher subcarrier spacing, SCS, than the first cell.

In some embodiments, the indicated range of values for the triggering offset is extended as compared to a range of values supportable by another type of wireless device for the triggering offset.

In some embodiments, the indicated range of values for the triggering offset includes values above a value threshold. Additionally or alternatively, the indicated range of values for the triggering offset includes a number of values above a range size threshold.

Other embodiments herein include a wireless device configured to transmit signaling which indicates that the wireless device supports cross-slot scheduling. In this case, support for cross-slot scheduling indicates a range of values that the wireless device supports for a triggering offset, a triggering offset being an offset between a slot containing downlink control information that triggers a set of aperiodic channel state information reference signal, CSI-RS, resources, and a slot in which the set of aperiodic CSI-RS resources is transmitted.

In some embodiments, the wireless device is configured to perform the steps described above for a wireless device.

Other embodiments herein include a network node configured to receive signaling which indicates that the wireless device supports cross-slot scheduling. Support for cross-slot scheduling indicates a range of values that the wireless device supports for a triggering offset. Here, a triggering offset is an offset between a slot containing downlink control information that triggers a set of aperiodic channel state information reference signal, CSI-RS, resources, and a slot in which the set of aperiodic CSI-RS resources is transmitted In some embodiments, the network node is configured to perform the steps described above for a network node.

Other embodiments herein include a computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to perform the steps described above for a wireless device. Other embodiments herein include a computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to perform the steps described above for a network node. In one or more of these embodiments, a carrier containing the computer program described above is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Other embodiments herein include a wireless device comprising communication circuitry and processing circuitry. The processing circuitry is configured to transmit, via the communication circuitry, signaling which indicates that the wireless device supports cross-slot scheduling. Support for cross-slot scheduling indicates a range of values that the wireless device supports for a triggering offset. Here, a triggering offset is an offset between a slot containing downlink control information that triggers a set of aperiodic channel state information reference signal, CSI-RS, resources, and a slot in which the set of aperiodic CSI-RS resources is transmitted.

In some embodiments, the processing circuitry is configured to perform the steps described above for a wireless device.

Other embodiments herein include a network node comprising communication circuitry and processing circuitry. The processing circuitry is configured to receive, via the communication circuitry, signaling which indicates that the wireless device supports cross-slot scheduling. Support for cross-slot scheduling indicates a range of values that the wireless device supports for a triggering offset. Here, a triggering offset is an offset between a slot containing downlink control information that triggers a set of aperiodic channel state information reference signal, CSI-RS, resources, and a slot in which the set of aperiodic CSI-RS resources is transmitted. In some embodiments, the processing circuitry is configured to perform the steps described above for a network node.

DETAILED DESCRIPTION

FIG.1shows a wireless communication network10configured to provide wireless communication service to a wireless device12according to some embodiments. Towards this end, the wireless device12is configured to receive downlink control information (DCI)14in a slot18-0, e.g., via a Physical Downlink Control Channel, PDCCH. This DCI14triggers transmission of a set16of aperiodic channel state information (CSI) reference signal (RS) (CSI-RS) (A-CSI-RS) resources, e.g., a set of resources on which A-CSI-RS may be transmitted. In some embodiments, this set of A-CSI-RS resources is a set of non-zero-power (NZP) A-CSI-RS resources. The wireless device12in some embodiments receives the DCI14from the same network node, carrier, and/or cell as that from which the set16of A-CSI-RS resources is received, whereas in other embodiments the wireless device12receives the DCI14from a different network node, carrier, and/or cell as that from which the set16of A-CSI-RS resources is received. Regardless, the DCI14may trigger the set16of A-CSI-RS resources to be transmitted in a slot18-X, such that there is an offset of X slots between the slot18-0in which the DCI14is received and the slot18-X in which the set of A-CSI-RS resources is received. This offset of X slots is referred to and shown as a triggering offset20.

In some embodiments, a network node15transmits to the wireless device12a control message22that configures the wireless device12with a value to be used for the triggering offset20. The control message22may for example include one or more triggering offset parameters24, each of which can be set to any of multiple possible values in order to signal which of those values is to be used for the triggering offset20. Where the wireless communication network10conforms to 3GPP specifications, for instance, the triggering offset parameter(s)24may include an aperiodicTriggeringOffset parameter and/or an aperiodicTriggeringOffsetExt-r16 parameter. In this case, then, the aperiodicTriggeringOffset parameter can be set to any of the values 0 . . . 6, with the value 0 corresponding a triggering offset20of 0 slots, the value 1 corresponding a triggering offset20of 1 slot, the value 2 corresponding a triggering offset20of 2 slots, the value 3 corresponding a triggering offset20of 3 slots, the value 4 corresponding a triggering offset20of 4 slots, the value 5 corresponding a triggering offset20of 16 slots, and the value 6 corresponding a triggering offset20of 24 slots.

According to some embodiments, the wireless device12transmits (e.g., to the network node15) signaling26which indicates a range of values that the wireless device12supports for the triggering offset20. By indicating the range of values that the wireless device12supports for the triggering offset20, the network node15may more suitably configure the triggering offset20(e.g., via the control message22). The network node15may for example advantageously configure the triggering offset20without any restrictions on configurability.

More particularly, in some embodiments, the signaling26indicates a range of values that the wireless device12supports for the triggering offset20by indicating that the wireless device supports a range of values for the triggering offset that is extended as compared to a range of values supportable by another type of wireless device for the triggering offset. The signaling26may for instance indicate that the wireless device12supports a certain triggering offset parameter in the control message22, e.g., by indicating that the wireless device12supports the aperiodicTriggeringOffsetExt-r16 parameter, which is extended in range as compared to the aperiodicTriggeringOffset parameter. Alternatively or additionally, the signaling26may indicate a range of values that the wireless device12supports for the triggering offset20by indicating that the wireless device supports a range of values for the triggering offset according to a certain 3GPP Release, e.g., Release 16. Alternatively or additionally, the signaling26may indicate a range of values that the wireless device12supports for the triggering offset20by indicating that the wireless device12supports a range of values for the triggering offset20that includes values above a value threshold (e.g., above X=24) and/or that includes a number of values above a range size threshold (e.g., more than the 7 possible values of the aperiodicTriggeringOffset parameter). Alternatively or additionally, the signaling26may indicate a range of values that the wireless device12supports for the triggering offset20by indicating that the wireless device12supports a range of values for the triggering offset20that comprises values between 0 and 31. Alternatively or additionally, the signaling26may indicate a range of values that the wireless device12supports for the triggering offset20by indicating which values the wireless device12supports for the triggering offset20.

Note that the signaling26may indicate any of the above explicitly or implicitly. The signaling26may indicate any of the above explicitly, for instance, if the signaling26includes one or more parameters whose value(s) directly represent or convey the above information, e.g., a parameter whose value directly indicates that the wireless device12supports the aperiodicTriggeringOffsetExt-r16 parameter or whose value directly indicates the range of values supported for the triggering offset20. In these and other embodiments, the signaling26may indicate the range of values that the wireless device12supports for the triggering offset20independent of any support by the wireless device12for cross-slot scheduling and/or for cross-carrier aperiodic CSI-RS triggering with different subcarrier spacing.

By contrast, the signaling26may indicate any of the above implicitly, for instance, if the signaling26includes one or more parameters whose value(s) explicitly represent or convey something else, with the above information merely being implied or deduced therefrom. For example, in some embodiments, the signaling26explicitly indicates that the wireless device12supports cross-slot scheduling, and the wireless device's support for cross-slot scheduling implies that the wireless device12supports a certain range of values for the triggering offset20, e.g., a range of 0 . . . 31 in accordance with the aperiodicTriggeringOffsetExt-r16 parameter. Alternatively or additionally, in other implicit signaling embodiments, the signaling26explicitly indicates that the wireless device12supports cross-carrier aperiodic CSI-RS triggering with different subcarrier spacing, and the wireless device's support for cross-carrier aperiodic CSI-RS triggering with different subcarrier spacing implies that the wireless device12supports a certain range of values for the triggering offset20, e.g., a range of 0 . . . 31 in accordance with the aperiodicTriggeringOffsetExt-r16 parameter.

In view of the above modifications and variations,FIG.2depicts a method performed by a wireless device12in accordance with particular embodiments. The method includes transmitting signaling26which indicates a range of values that the wireless device12supports for a triggering offset20(Block200). In some embodiments, a triggering offset20is an offset between: a slot18-0containing downlink control information14that triggers a set16of aperiodic channel state information reference signal (CSI-RS) resources; and a slot18-X in which the set16of aperiodic CSI-RS resources is transmitted.

Note that, in some embodiments where the signaling26indicates the range of values implicitly, the signaling26may actually indicate that the wireless device12supports cross-slot scheduling, where such support for cross-slot scheduling indicates that the wireless device12supports a certain range of values for the triggering offset20, e.g., a range of 0 . . . 31 in accordance with the aperiodicTriggeringOffsetExt-r16 parameter.

In some embodiments, the method also comprises, after transmitting the signaling26, receiving a control message22that configures the wireless device12with a triggering offset20that has a value within the range of values indicated by the transmitted signaling26(Block210).

In some embodiments, the method also comprises receiving, in a first slot18-0, downlink control information14that triggers a set16of aperiodic CSI-RS resources (Block220). The method may further comprise receiving, in a second slot18-X, CSI-RS on the set16of aperiodic CSI-RS resources triggered by the received downlink control information14(Block230). In one or more embodiments, the offset between the first slot18-0and the second slot18-X has a value within the range of values indicated by the transmitted signaling26.

In some embodiments, the method also comprises based on the triggering offset20configured by the received control message22, operating in a sleep state between the first slot18-0and the second slot18-X (Block240).

FIG.3depicts a method performed by a network node15(e.g., a radio network node) in accordance with other particular embodiments. The method includes receiving signaling26which indicates a range of values that a wireless device12supports for a triggering offset20(Block300). In some embodiments, a triggering offset20is an offset between: a slot18-0containing downlink control information14that triggers a set16of aperiodic channel state information reference signal (CSI-RS) resources; and a slot18-X in which the set16of aperiodic CSI-RS resources is transmitted.

Note that, in some embodiments where the signaling26indicates the range of values implicitly, the signaling26may actually indicate that the wireless device12supports cross-slot scheduling, where such support for cross-slot scheduling indicates that the wireless device12supports a certain range of values for the triggering offset20, e.g., a range of 0 . . . 31 in accordance with the aperiodicTriggeringOffsetExt-r16 parameter.

In some embodiments, the method also comprises, based on the received signaling26, configuring the wireless device12with a triggering offset20(Block310). In one or more embodiments, this comprises transmitting, to the wireless device12, a control message22which configures the wireless device12with a triggering offset20that has a value within the range of values indicated by the receiving signaling26.

In some embodiments, the method also comprises selecting the value of the triggering offset20with which to configure the wireless device12from among any of the values within the range indicated by the receiving signaling26(Block305).

In some embodiments, the method also comprises determining a set16of aperiodic CSI-RS resources on which to transmit aperiodic CSI-RS to the wireless device12, based on the received signaling26(Block320).

In some embodiments, the method also comprises transmitting, in a first slot18-0, to the wireless device12, downlink control information14that triggers a set16of aperiodic CSI-RS resources (Block330).

In some embodiments, the method also comprises transmitting, in a second slot18-X, to the wireless device12, CSI-RS on the set16of aperiodic CSI-RS resources triggered by the transmitted downlink control information14(Block340). In some embodiments, the offset between the first slot18-0and the second slot18-X has a value within the range of values indicated by the received signaling26.

Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a wireless device configured to perform any of the steps of any of the embodiments described above for the wireless device.

Embodiments also include a wireless device12comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the wireless device12. The power supply circuitry is configured to supply power to the wireless device12. Embodiments further include a wireless device12comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the wireless device12. In some embodiments, the wireless device12further comprises communication circuitry.

Embodiments further include a wireless device12comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the wireless device12is configured to perform any of the steps of any of the embodiments described above for the wireless device12.

Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the wireless device12. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

Embodiments herein also include a network node15configured to perform any of the steps of any of the embodiments described above for the network node15.

Embodiments also include a network node15comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node15. The power supply circuitry is configured to supply power to the network node15.

Embodiments further include a network node15comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node15. In some embodiments, the network node15further comprises communication circuitry.

Embodiments further include a network node15comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the network node15is configured to perform any of the steps of any of the embodiments described above for the network node15.

FIG.4for example illustrates a wireless device400(e.g., wireless device12) as implemented in accordance with one or more embodiments. As shown, the wireless device400includes processing circuitry410and communication circuitry420. The communication circuitry420(e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the wireless device400. The processing circuitry410is configured to perform processing described above, e.g., inFIG.2, such as by executing instructions stored in memory430. The processing circuitry410in this regard may implement certain functional means, units, or modules.

FIG.5illustrates a network node500(e.g., network node15) as implemented in accordance with one or more embodiments. As shown, the network node500includes processing circuitry510and communication circuitry520. The communication circuitry520is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The processing circuitry510is configured to perform processing described above, e.g., inFIG.3, such as by executing instructions stored in memory530. The processing circuitry510in this regard may implement certain functional means, units, or modules.

Note that, as used herein, a transmission timing structure may comprise a plurality of symbols, and/or define an interval comprising several symbols (respectively their associated time intervals). In the context of this disclosure, it should be noted that a reference to a symbol for ease of reference may be interpreted to refer to the time domain projection or time interval or time component or duration or length in time of the symbol, unless it is clear from the context that the frequency domain component also has to be considered. Examples of transmission timing structures include slot, subframe, mini-slot (which also may be considered a substructure of a slot), slot aggregation (which may comprise a plurality of slots and may be considered a superstructure of a slot), respectively their time domain component. A transmission timing structure may generally comprise a plurality of symbols defining the time domain extension (e.g., interval or length or duration) of the transmission timing structure, and arranged neighboring to each other in a numbered sequence. A timing structure (which may also be considered or implemented as synchronisation structure) may be defined by a succession of such transmission timing structures, which may for example define a timing grid with symbols representing the smallest grid structures. A transmission timing structure, and/or a border symbol or a scheduled transmission may be determined or scheduled in relation to such a timing grid. A transmission timing structure of reception may be the transmission timing structure in which the scheduling control signaling is received, e.g. in relation to the timing grid. A transmission timing structure may in particular be a slot or subframe or in some cases, a mini-slot.

References to specific resource structures like transmission timing structure and/or symbol and/or slot and/or mini-slot and/or subcarrier and/or carrier may pertain to a specific numerology, which may be predefined and/or configured or configurable. A transmission timing structure may represent a time interval, which may cover one or more symbols. Some examples of a transmission timing structure are transmission time interval (TTI), subframe, slot and mini-slot. A slot may comprise a predetermined, e.g. predefined and/or configured or configurable, number of symbols, e.g. 6 or 7, or 12 or 14. A mini-slot may comprise a number of symbols (which may in particular be configurable or configured) smaller than the number of symbols of a slot, in particular 1, 2, 3 or 4 symbols. A transmission timing structure may cover a time interval of a specific length, which may be dependent on symbol time length and/or cyclic prefix used. A transmission timing structure may pertain to, and/or cover, a specific time interval in a time stream, e.g. synchronized for communication. Timing structures used and/or scheduled for transmission, e.g. slot and/or mini-slots, may be scheduled in relation to, and/or synchronized to, a timing structure provided and/or defined by other transmission timing structures. Such transmission timing structures may define a timing grid, e.g., with symbol time intervals within individual structures representing the smallest timing units. Such a timing grid may for example be defined by slots or subframes (wherein in some cases, subframes may be considered specific variants of slots). A transmission timing structure may have a duration (length in time) determined based on the durations of its symbols, possibly in addition to cyclic prefix/es used. The symbols of a transmission timing structure may have the same duration, or may in some variants have different duration. The number of symbols in a transmission timing structure may be predefined and/or configured or configurable, and/or be dependent on numerology. The timing of a mini-slot may generally be configured or configurable, in particular by the network and/or a network node. The timing may be configurable to start and/or end at any symbol of the transmission timing structure, in particular one or more slots.

In general, a numerology and/or subcarrier spacing may indicate the bandwidth (in frequency domain) of a subcarrier of a carrier, and/or the number of subcarriers in a carrier and/or the numbering of the subcarriers in a carrier. Different numerologies may in particular be different in the bandwidth of a subcarrier. In some variants, all the subcarriers in a carrier have the same bandwidth associated to them. The numerology and/or subcarrier spacing may be different between carriers in particular regarding the subcarrier bandwidth. A symbol time length, and/or a time length of a timing structure pertaining to a carrier may be dependent on the carrier frequency, and/or the subcarrier spacing and/or the numerology. In particular, different numerologies may have different symbol time lengths.

Signaling may generally comprise one or more symbols and/or signals and/or messages. A signal may comprise or represent one or more bits. An indication may represent signaling, and/or be implemented as a signal, or as a plurality of signals. One or more signals may be included in and/or represented by a message. Signaling, in particular control signaling, may comprise a plurality of signals and/or messages, which may be transmitted on different carriers and/or be associated to different signaling processes, e.g. representing and/or pertaining to one or more such processes and/or corresponding information. An indication may comprise signaling, and/or a plurality of signals and/or messages and/or may be comprised therein, which may be transmitted on different carriers and/or be associated to different acknowledgement signaling processes, e.g. representing and/or pertaining to one or more such processes. Signaling associated to a channel may be transmitted such that represents signaling and/or information for that channel, and/or that the signaling is interpreted by the transmitter and/or receiver to belong to that channel. Such signaling may generally comply with transmission parameters and/or format/s for the channel.

Signaling may generally be considered to represent an electromagnetic wave structure (e.g., over a time interval and frequency interval), which is intended to convey information to at least one specific or generic (e.g., anyone who might pick up the signaling) target. A process of signaling may comprise transmitting the signaling. Transmitting signaling, in particular control signaling or communication signaling may comprise encoding and/or modulating. Encoding and/or modulating may comprise error detection coding and/or forward error correction encoding and/or scrambling. Receiving control signaling may comprise corresponding decoding and/or demodulation. Error detection coding may comprise, and/or be based on, parity or checksum approaches, e.g. CRC (Cyclic Redundancy Check). Forward error correction coding may comprise and/or be based on for example turbo coding and/or Reed-Muller coding, and/or polar coding and/or LDPC coding (Low Density Parity Check). The type of coding used may be based on the channel (e.g., physical channel) the coded signal is associated to.

Example types of signaling comprise signaling of a specific communication direction, in particular, uplink signaling, downlink signaling, sidelink signaling, as well as reference signaling (e.g., SRS or CRS or CSI-RS), communication signaling, control signaling, and/or signaling associated to a specific channel like PUSCH, PDSCH, PUCCH, PDCCH, PSCCH, PSSCH, etc.).

Communication signaling may comprise, and/or represent, and/or be implemented as, data signaling, and/or user plane signaling. Communication signaling may be associated to a data channel, e.g. a physical downlink channel or physical uplink channel or physical sidelink channel, in particular a PDSCH (Physical Downlink Shared Channel) or PSSCH (Physical Sidelink Shared Channel). Generally, a data channel may be a shared channel or a dedicated channel. Data signaling may be signaling associated to and/or on a data channel.

An indication generally may explicitly and/or implicitly indicate the information it represents and/or indicates. Implicit indication may for example be based on position and/or resource used for transmission. Explicit indication may for example be based on a parametrization with one or more parameters, and/or one or more index or indices, and/or one or more bit patterns representing the information. It may in particular be considered that control signaling as described herein, based on the utilized resource sequence, implicitly indicates the control signaling type.

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

In some embodiments, Channel State Information Reference Signals (CSI-RSs) are used for channel state feedback related to the use of transmission modes that enable UE-specific antenna precoding. These transmission modes use the UE-specific Demodulation Reference Symbols (DM-RSs) at the time of transmission with the precoding performed based on the feedback received from and measured by the UE on the CSI-RSs. The CSI-RS can be configured for a UE as Non-Zero-Power (NZP) and Zero-Power (ZP) instances. The NZP CSI-RS configuration indicates the resource elements (REs) where the cell being measured transmits CSI-RS and the ZP CSI-RS configuration indicates the REs where no information is transmitted by the cell being measured. The ZP CSI-RS REs are typically configured so that they overlap with transmissions from other cells which allows the UE to make interference measurements or Reference Signal Received Power (RSRP) measurements on the CSI-RS of other cells. Knowledge of the ZP CSI-RS configurations also allows the UE to not use these REs, i.e., rate-match around these REs when receiving the Physical Downlink Shared Channel (PDSCH).

In Rel-15, the A-CSI triggering offset value that can be configured is restricted to the set of values in {0, 1, 2, 3, 4, 16, 24} slots. For example, this RRC parameter can be aperiodicTriggeringOffset.

In Rel-16, a new RRC parameter is introduced for indicating a flexible A-CSI triggering offset value between 0 to 31 (in slots) i.e. with extended offset value range. For example, this RRC parameter can be aperiodicTriggeringOffsetExt-r16.

The Information Element (IE) NZP-CSI-RS-Resource is used to configure Non-Zero-Power (NZP) CSI-RS transmitted in the cell where the IE is included, which the UE may be configured to measure on.

NZP-CSI-RS-Resource field descriptionsperiodicityAndOffsetPeriodicity and slot offset sl1 corresponds to a periodicity of 1 slot, sl2 to a periodicity oftwo slots, and so on. The corresponding offset is also given in number of slots. Networkalways configures the UE with a value for this field for periodic and semi-persistent NZP-CSI-RS-Resource (as indicated in CSI-ResourceConfig).powerControlOffsetPower offset of PDSCH RE to NZP CSI-RS RE. Value in dBpowerControlOffsetSSPower offset of NZP CSI-RS RE to SSS RE. Value in dBqcl-InfoPeriodicCSI-RSFor a target periodic CSI-RS, contains a reference to one TCI-State in TCI-States forproviding the QCL source and QCL type. For periodic CSI-RS, the source can be SSB oranother periodic-CSI-RS. Refers to the TCI-State which has this value for tci-StateId and isdefined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlinkcorresponding to the serving cell and to the DL BWP to which the resource belongs toresourceMappingOFDM symbol location(s) in a slot and subcarrier occupancy in a PRB of the CSI-RSresource.scramblingIDScrambling IDConditional PresenceExplanationPeriodicThe field is optionally present, Need M, for periodic NZP-CSI-RS-Resources (as indicated in CSI-ResourceConfig).The field is absent otherwise.PeriodicOrSemiPersistentThe field is optionally present, Need M, for periodic andsemi-persistent NZP-CSI-RS-Resources (as indicated inCSI-ResourceConfig). The field is absent otherwise.

The IE NZP-CSI-RS-Resourceld is used to identify one NZP-CSI-RS-Resource.

The IE NZP-CSI-RS-ResourceSet is a set of Non-Zero-Power (NZP) CSI-RS resources (their IDs) and set-specific parameters.

NZP-CSI-RS-ResourceSet field descriptionsaperiodicTriggeringOffset, aperiodicTriggeringOffsetExtOffset X between the slot containing the DCI that triggers a set ofaperiodic NZP CSI-RS resources and the slot in which the CSI-RSresource set is transmitted. For aperiodicTriggeringOffset, thevalue 0 corresponds to 0 slots, value 1 corresponds to 1 slot, value 2corresponds to 2 slots, value 3 corresponds to 3 slots, value 4corresponds to 4 slots, value 5 corresponds to 16 slots, value 6corresponds to 24 slots. For aperiodicTriggeringOffsetExt, the valueindicates the number of slots. The network configures only one ofthe fields. When neither field is included, the UE applies the value 0.nzp-CSI-RS-ResourcesNZP-CSI-RS-Resources associated with this NZP-CSI-RS resourceset. For CSI, there are at most 8 NZP CSI RS resources per resource set.repetitionIndicates whether repetition is on/off. If the field is set to off or if thefield is absent, the UE may not assume that the NZP-CSI-RS resourceswithin the resource set are transmitted with the same downlink spatialdomain transmission filter. Can only be configured for CSI-RSresource sets which are associated with CSI-ReportConfig withreport of L1 RSRP or “no report”.trs-InfoIndicates that the antenna port for all NZP-CSI-RS resources in theCSI-RS resource set is same. If the field is absent or released the UEapplies the value false.

The IE NZP-CSI-RS-ResourceSetld is used to identify one NZP-CSI-RS-ResourceSet.

For a given NZP-CSI-RS resource set, a UE can be configured with a triggering offset value using one of the Rel-15 and Rel-16 parameters. An example TP update based on the above two parameters is as follows:

An example TP for RRC parameter name alignment is below (with bold underlined changes).

1.5.2.1.5.1 Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the CSI-RS have the same numerology

Omitted Text

When aperiodic CSI-RS is used with aperiodic reporting, the CSI-RS offset is configured per resource set by the higher layer parameter aperiodicTriggeringOffset or aperiodicTriggeringOffsetExt-r16. The CSI-RS triggering offset has the values of {0, 1, 2, 3, 4, 16, 24} slots. If the UE is not configured with [minimumSchedulingOffset] for any DL or UL bandwidth part (BWP) and if all the associated trigger states do not have the higher layer parameter qcl-Type set to ‘QCL-TypeD’ in the corresponding Transmission Configuration Indicator (TCI) states, the CSI-RS triggering offset is fixed to zero. The aperiodic triggering offset of the CSI Interference Measurement (CSI-IM) follows offset of the associated NZP CSI-RS for channel measurement.

Omitted Text

2.5.2.1.5.1a Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the CSI-RS have different numerologies

Omitted Text

When the aperiodic CSI-RS is used with aperiodic CSI reporting, the CSI-RS triggering offset X is configured per resource set by the higher layer parameter aperiodicTriggeringOffset or aperiodicTriggeringOffsetExt-r16, including the case that the UE is not configured with [minimumSchedulingOffset] for any DL or UL BWP and all the associated trigger states do not have the higher layer parameter qcl-Type set to ‘QCL-TypeD’ in the corresponding TCI states. The CSI-RS triggering offset has the values of {0, 1, . . . , 31} slots when the PDCCH<μCSIRS and {0, 1, 2, 3, 4, 16, 24} when the μPDCCH>μCIRS. The aperiodic CSI-RS is transmitted in a slot

if UE is configured with ca-SlotOffset for at least one of the triggered and triggering cell, and

otherwise, and where

n is the slot containing the triggering DCI, Xis the CSI-RS triggering offset in the numerology of CSI-RS according to the higher layer parameter aperiodicTriggeringOffset or aperiodicTriggeringOffsetExt-r16,

Omitted Text

The use case for the extended offset value range may enable more efficient/flexible A-CSI triggering offset configuration for the case when a Physical Downlink Control Channel (PDCCH) on a first cell with a lower subcarrier spacing (SCS) schedules an A-CSI-RS transmission on a second cell with higher SCS.

Another use case for the extended offset value range is to enable more efficient/flexible A-CSI triggering offset configuration for the case when a UE supports cross-slot scheduling based power savings, wherein a minimum scheduling offset restriction is applied for PDSCH scheduling, and the same restriction is also applied for A-CSI-RS triggering offset. For example, if a minimum scheduling offset restriction is applicable (e.g. min K0=5), then UE will not expect to be scheduled using a DCI that indicates a Physical Downlink Shared Channel (PDSCH) scheduling offset of K0<5 and the UE will not expect to be scheduled using a DCI that indicates a A-CSI triggering offset smaller than 5. This can be applied for all cases including same-SCS scheduling (including same-carrier scheduling), high-SCS-PDCCH scheduling lower-SCS PDSCH/A-CSI-RS, and lower-SCS PDCCH scheduling higher-SCS PDSCH/A-CSI-RS.

The case where a UE indicates capability for support for configuration of the extended offset value range for A-CSI triggering offset will now be described, e.g., so as to illustrate various examples of signaling26inFIG.1.

In an embodiment, a UE indicating support for “Cross Slot Scheduling” also indicates the capability (e.g. implicitly or explicitly) to support the new RRC parameter (e.g. aperiodicTriggeringOffsetExt-r16.) and/or the extended offset value range for A-CSI triggering offset. For example, in the implicit case, support of extended offset value range for A-CSI triggering offset via aperiodicTriggeringOffsetExt-r16 can become a component within the capability to “Cross Slot Scheduling”.

In an embodiment, a UE indicates a separate capability to support the new RRC parameter (e.g. aperiodicTriggeringOffsetExt-r16.) and/or the extended offset value range for A-CSI triggering offset. For example, the capability can be separate from the capability indicating support for “Cross-carrier A-CSI RS triggering with different SCS” and/or “Cross slot scheduling”. For example, a new feature group may be introduced for this option.

In an embodiment, a UE indicating capability to “Cross-carrier A-CSI RS triggering with different SCS” also indicates the capability (e.g. implicitly or explicitly) to support the new RRC parameter (e.g. aperiodicTriggeringOffsetExt-r16.) and/or the extended offset value range for A-CSI triggering offset. For example, in the implicit case, support of extended offset value range for A-CSI triggering offset via aperiodicTriggeringOffsetExt-r16 can become a component within the capability to “Cross-carrier A-CSI RS triggering with different SCS”.

Cross-slot scheduling capability (e.g. 19-2) may have a component as follows:Dynamic indication of applicable minimum scheduling restriction by DCI format 0_1 and 1_1minimumSchedulingOffset K0 configuration for PDSCH and aperiodic CSI-RS triggering offset

Cross-carrier A-CSI RS triggering with different SCS capability (e.g. 18-6) may have a component as follows: Cross-carrier A-CSI RS triggering with different SCS.

As described in some of previous embodiments, an additional component as follows can be added to one or both of the above capabilities: support of extended offset value range for A-CSI triggering offset via aperiodicTriggeringOffsetExt-r16.

As described in one of previous embodiments, an additional new capability can be introduced “support of extended offset value range for A-CSI triggering offset” with the following component: support of extended offset value range for A-CSI triggering offset via aperiodicTriggeringOffsetExt-r16.

Note: the new capability can be independent of other capabilities e.g. 19-2 or 18-6.

A gNB upon receiving the UE capability signaling according to one of the above embodiments (e.g., as examples of signaling26), can suitably configure the A-CSI triggering offset for the UE.

Since a UE indicates capability support of extended offset value range for A-CSI triggering offset, in one embodiment, the extended value range can be used regardless of whether the corresponding feature (Cross-carrier A-CSI-RS triggering with different SCS or Cross-slot scheduling) is enabled or not. The cases where it is configurable may be clear from 3GPP specifications already in some cases such as “The CSI-RS triggering offset has the values of {0, 1, . . . , 31} slots when the μPDCCH<μCSIRS”, where μ denotes the numerology corresponding to the SCS for control channel (PDCCH) and SCS for CSI-RS. μ=0,1,2,3, for 15 kHz, 30 kHz, 60 kHz, and 120 kHz, respectively.

However, in some cases such as UEs supporting cross-slot scheduling, it may not be so clear from the 3GPP specification. For the Cross-slot scheduling case, there may be some additional conditions added under which a UE may support the extended offset value range for A-CSI triggering offset via aperiodicTriggeringOffsetExt-r16.The CSI-RS triggering offset has the extended value range (e.g. of {0, 1, 2, 3, 4, 5, 6 . . . 15, 16, 24} slots) for any DL bandwidth part (BWP) when the UE is configured with minimum scheduling offset value (e.g. for DL or UL) for at least one BWP.The CSI-RS triggering offset has the extended value range (e.g. of {0, 1, 2, 3, 4, 5, 6 . . . 15, 16, 24} slots) for a DL BWP when the UE is configured with minimum scheduling offset (e.g. for DL) for the DL BWP.

The CSI-RS triggering offset with extended value range (e.g. of {0, 1, 2, 3, 4, 5, 6 . . . 15, 16, 24} slots) can be configured only for a DL BWP when the UE is configured with minimum scheduling offset (e.g. for DL) for the DL BWP.The CSI-RS triggering offset with extended value range (e.g. of {0, 1, 2, 3, 4, 5, 6 . . . 15, 16, 24} slots) can be configured for any DL BWP only when the UE is configured with minimum scheduling offset (e.g. for DL or UL) for at least one BWP.

InFIG.6, network node660includes processing circuitry670, device readable medium680, interface690, auxiliary equipment684, power source686, power circuitry687, and antenna662. Although network node660illustrated in the example wireless network ofFIG.6may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node660are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium680may comprise multiple separate hard drives as well as multiple RAM modules).

Processing circuitry670is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry670may include processing information obtained by processing circuitry670by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry670may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node660components, such as device readable medium680, network node660functionality. For example, processing circuitry670may execute instructions stored in device readable medium680or in memory within processing circuitry670. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry670may include a system on a chip (SOC).

In some embodiments, processing circuitry670may include one or more of radio frequency (RF) transceiver circuitry672and baseband processing circuitry674. In some embodiments, radio frequency (RF) transceiver circuitry672and baseband processing circuitry674may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry672and baseband processing circuitry674may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry670executing instructions stored on device readable medium680or memory within processing circuitry670. In alternative embodiments, some or all of the functionality may be provided by processing circuitry670without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry670can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry670alone or to other components of network node660, but are enjoyed by network node660as a whole, and/or by end users and the wireless network generally.

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

Interface690is used in the wired or wireless communication of signalling and/or data between network node660, network606, and/or WDs610. As illustrated, interface690comprises port(s)/terminal(s)694to send and receive data, for example to and from network606over a wired connection. Interface690also includes radio front end circuitry692that may be coupled to, or in certain embodiments a part of, antenna662. Radio front end circuitry692comprises filters698and amplifiers696. Radio front end circuitry692may be connected to antenna662and processing circuitry670. Radio front end circuitry may be configured to condition signals communicated between antenna662and processing circuitry670. Radio front end circuitry692may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry692may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters698and/or amplifiers696. The radio signal may then be transmitted via antenna662.

Similarly, when receiving data, antenna662may collect radio signals which are then converted into digital data by radio front end circuitry692. The digital data may be passed to processing circuitry670. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node660may not include separate radio front end circuitry692, instead, processing circuitry670may comprise radio front end circuitry and may be connected to antenna662without separate radio front end circuitry692. Similarly, in some embodiments, all or some of RF transceiver circuitry672may be considered a part of interface690. In still other embodiments, interface690may include one or more ports or terminals694, radio front end circuitry692, and RF transceiver circuitry672, as part of a radio unit (not shown), and interface690may communicate with baseband processing circuitry674, which is part of a digital unit (not shown).

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

Antenna662, interface690, and/or processing circuitry670may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna662, interface690, and/or processing circuitry670may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

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

Alternative embodiments of network node660may include additional components beyond those shown inFIG.6that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node660may include user interface equipment to allow input of information into network node660and to allow output of information from network node660. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node660.

As illustrated, wireless device610includes antenna611, interface614, processing circuitry620, device readable medium630, user interface equipment632, auxiliary equipment634, power source636and power circuitry637. WD610may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD610, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-IoT, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD610.

Antenna611may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface614. In certain alternative embodiments, antenna611may be separate from WD610and be connectable to WD610through an interface or port. Antenna611, interface614, and/or processing circuitry620may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna611may be considered an interface.

As illustrated, interface614comprises radio front end circuitry612and antenna611. Radio front end circuitry612comprise one or more filters618and amplifiers616. Radio front end circuitry614is connected to antenna611and processing circuitry620, and is configured to condition signals communicated between antenna611and processing circuitry620. Radio front end circuitry612may be coupled to or a part of antenna611. In some embodiments, WD610may not include separate radio front end circuitry612; rather, processing circuitry620may comprise radio front end circuitry and may be connected to antenna611. Similarly, in some embodiments, some or all of RF transceiver circuitry622may be considered a part of interface614. Radio front end circuitry612may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry612may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters618and/or amplifiers616. The radio signal may then be transmitted via antenna611. Similarly, when receiving data, antenna611may collect radio signals which are then converted into digital data by radio front end circuitry612. The digital data may be passed to processing circuitry620. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry620may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD610components, such as device readable medium630, WD610functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry620may execute instructions stored in device readable medium630or in memory within processing circuitry620to provide the functionality disclosed herein.

As illustrated, processing circuitry620includes one or more of RF transceiver circuitry622, baseband processing circuitry624, and application processing circuitry626. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry620of WD610may comprise a SOC. In some embodiments, RF transceiver circuitry622, baseband processing circuitry624, and application processing circuitry626may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry624and application processing circuitry626may be combined into one chip or set of chips, and RF transceiver circuitry622may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry622and baseband processing circuitry624may be on the same chip or set of chips, and application processing circuitry626may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry622, baseband processing circuitry624, and application processing circuitry626may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry622may be a part of interface614. RF transceiver circuitry622may condition RF signals for processing circuitry620.

Device readable medium630may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry620. Device readable medium630may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry620. In some embodiments, processing circuitry620and device readable medium630may be considered to be integrated.

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

Power source636may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD610may further comprise power circuitry637for delivering power from power source636to the various parts of WD610which need power from power source636to carry out any functionality described or indicated herein. Power circuitry637may in certain embodiments comprise power management circuitry. Power circuitry637may additionally or alternatively be operable to receive power from an external power source; in which case WD610may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry637may also in certain embodiments be operable to deliver power from an external power source to power source636. This may be, for example, for the charging of power source636. Power circuitry637may perform any formatting, converting, or other modification to the power from power source636to make the power suitable for the respective components of WD610to which power is supplied.

InFIG.7, UE700includes processing circuitry701that is operatively coupled to input/output interface705, radio frequency (RF) interface709, network connection interface711, memory715including random access memory (RAM)717, read-only memory (ROM)719, and storage medium721or the like, communication subsystem731, power source733, and/or any other component, or any combination thereof. Storage medium721includes operating system723, application program725, and data727. In other embodiments, storage medium721may include other similar types of information. Certain UEs may utilize all of the components shown inFIG.7, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

InFIG.7, RF interface709may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface711may be configured to provide a communication interface to network743a.Network743amay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network743amay comprise a Wi-Fi network. Network connection interface711may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface711may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM717may be configured to interface via bus702to processing circuitry701to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM719may be configured to provide computer instructions or data to processing circuitry701. For example, ROM719may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium721may 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 disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium721may be configured to include operating system723, application program725such as a web browser application, a widget or gadget engine or another application, and data file727. Storage medium721may store, for use by UE700, any of a variety of various operating systems or combinations of operating systems.

InFIG.7, processing circuitry701may be configured to communicate with network743busing communication subsystem731. Network743aand network743bmay be the same network or networks or different network or networks. Communication subsystem731may be configured to include one or more transceivers used to communicate with network743b.For example, communication subsystem731may 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.7, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter733and/or receiver735to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter733and receiver735of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem731may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem731may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network743bmay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network743bmay be a cellular network, a Wi-Fi network, and/or a near-field network. Power source713may be configured to provide alternating current (AC) or direct current (DC) power to components of UE700.

The features, benefits and/or functions described herein may be implemented in one of the components of UE700or partitioned across multiple components of UE700. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem731may be configured to include any of the components described herein. Further, processing circuitry701may be configured to communicate with any of such components over bus702. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry701perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry701and communication subsystem731. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

The functions may be implemented by one or more applications820(which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications820are run in virtualization environment800which provides hardware830comprising processing circuitry860and memory890. Memory890contains instructions895executable by processing circuitry860whereby application820is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment800, comprises general-purpose or special-purpose network hardware devices830comprising a set of one or more processors or processing circuitry860, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory890-1which may be non-persistent memory for temporarily storing instructions895or software executed by processing circuitry860. Each hardware device may comprise one or more network interface controllers (NICs)870, also known as network interface cards, which include physical network interface880. Each hardware device may also include non-transitory, persistent, machine-readable storage media890-2having stored therein software895and/or instructions executable by processing circuitry860. Software895may include any type of software including software for instantiating one or more virtualization layers850(also referred to as hypervisors), software to execute virtual machines840as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines840, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer850or hypervisor. Different embodiments of the instance of virtual appliance820may be implemented on one or more of virtual machines840, and the implementations may be made in different ways.

During operation, processing circuitry860executes software895to instantiate the hypervisor or virtualization layer850, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer850may present a virtual operating platform that appears like networking hardware to virtual machine840.

As shown inFIG.8, hardware830may be a standalone network node with generic or specific components. Hardware830may comprise antenna8225and may implement some functions via virtualization. Alternatively, hardware830may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO)8100, which, among others, oversees lifecycle management of applications820.

In the context of NFV, virtual machine840may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines840, and that part of hardware830that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines840, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines840on top of hardware networking infrastructure830and corresponds to application820inFIG.8.

In some embodiments, one or more radio units8200that each include one or more transmitters8220and one or more receivers8210may be coupled to one or more antennas8225. Radio units8200may communicate directly with hardware nodes830via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system8230which may alternatively be used for communication between the hardware nodes830and radio units8200.

FIG.9illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference to

FIG.9, in accordance with an embodiment, a communication system includes telecommunication network910, such as a 3GPP-type cellular network, which comprises access network911, such as a radio access network, and core network914. Access network911comprises a plurality of base stations912a,912b,912c,such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area913a,913b,913c.

Each base station912a,912b,912cis connectable to core network914over a wired or wireless connection915. A first UE991located in coverage area913c is configured to wirelessly connect to, or be paged by, the corresponding base station912c.A second UE992in coverage area913ais wirelessly connectable to the corresponding base station912a.While a plurality of UEs991,992are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station912.

Telecommunication network910is itself connected to host computer930, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer930may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections921and922between telecommunication network910and host computer930may extend directly from core network914to host computer930or may go via an optional intermediate network920. Intermediate network920may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network920, if any, may be a backbone network or the Internet; in particular, intermediate network920may comprise two or more sub-networks (not shown).

The communication system ofFIG.9as a whole enables connectivity between the connected UEs991,992and host computer930. The connectivity may be described as an over-the-top (OTT) connection950. Host computer930and the connected UEs991,992are configured to communicate data and/or signaling via OTT connection950, using access network911, core network914, any intermediate network920and possible further infrastructure (not shown) as intermediaries. OTT connection950may be transparent in the sense that the participating communication devices through which OTT connection950passes are unaware of routing of uplink and downlink communications. For example, base station912may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer930to be forwarded (e.g., handed over) to a connected UE991. Similarly, base station912need not be aware of the future routing of an outgoing uplink communication originating from the UE991towards the host computer930.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference toFIG.10.FIG.10illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system1000, host computer1010comprises hardware1015including communication interface1016configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system1000. Host computer1010further comprises processing circuitry1018, which may have storage and/or processing capabilities. In particular, processing circuitry1018may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer1010further comprises software1011, which is stored in or accessible by host computer1010and executable by processing circuitry1018. Software1011includes host application1012. Host application1012may be operable to provide a service to a remote user, such as UE1030connecting via OTT connection1050terminating at UE1030and host computer1010. In providing the service to the remote user, host application1012may provide user data which is transmitted using OTT connection1050.

Communication system1000further includes base station1020provided in a telecommunication system and comprising hardware1025enabling it to communicate with host computer1010and with UE1030. Hardware1025may include communication interface1026for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system1000, as well as radio interface1027for setting up and maintaining at least wireless connection1070with UE1030located in a coverage area (not shown inFIG.10) served by base station1020. Communication interface1026may be configured to facilitate connection1060to host computer1010. Connection1060may be direct or it may pass through a core network (not shown inFIG.10) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware1025of base station1020further includes processing circuitry1028, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station1020further has software1021stored internally or accessible via an external connection.

Communication system1000further includes UE1030already referred to. Its hardware1035may include radio interface1037configured to set up and maintain wireless connection1070with a base station serving a coverage area in which UE1030is currently located. Hardware1035of UE1030further includes processing circuitry1038, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE1030further comprises software1031, which is stored in or accessible by UE1030and executable by processing circuitry1038. Software1031includes client application1032. Client application1032may be operable to provide a service to a human or non-human user via UE1030, with the support of host computer1010. In host computer1010, an executing host application1012may communicate with the executing client application1032via OTT connection1050terminating at UE1030and host computer1010. In providing the service to the user, client application1032may receive request data from host application1012and provide user data in response to the request data. OTT connection1050may transfer both the request data and the user data. Client application1032may interact with the user to generate the user data that it provides.

It is noted that host computer1010, base station1020and UE1030illustrated inFIG.10may be similar or identical to host computer930, one of base stations912a,912b,912cand one of UEs991,992ofFIG.9, respectively. This is to say, the inner workings of these entities may be as shown inFIG.10and independently, the surrounding network topology may be that ofFIG.9.

InFIG.10, OTT connection1050has been drawn abstractly to illustrate the communication between host computer1010and UE1030via base station1020, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE1030or from the service provider operating host computer1010, or both. While OTT connection1050is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection1070between UE1030and base station1020is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE1030using OTT connection1050, in which wireless connection1070forms the last segment.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection1050between host computer1010and UE1030, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection1050may be implemented in software1011and hardware1015of host computer1010or in software1031and hardware1035of UE1030, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection1050passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software1011,1031may compute or estimate the monitored quantities. The reconfiguring of OTT connection1050may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station1020, and it may be unknown or imperceptible to base station1020. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer1010′s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software1011and1031causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection1050while it monitors propagation times, errors etc.

FIG.11is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS.9and10. For simplicity of the present disclosure, only drawing references toFIG.11will be included in this section. In step1110, the host computer provides user data. In substep1111(which may be optional) of step1110, the host computer provides the user data by executing a host application.

In step1120, the host computer initiates a transmission carrying the user data to the UE. In step1130(which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step1140(which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

In view of the above, then, embodiments herein generally include a communication system including a host computer. The host computer may comprise processing circuitry configured to provide user data. The host computer may also comprise a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The cellular network may comprise a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the embodiments described above for a base station.

In some embodiments, the communication system further includes the base station.

In some embodiments, the communication system further includes the UE, wherein the UE is configured to communicate with the base station.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data. In this case, the UE comprises processing circuitry configured to execute a client application associated with the host application.

Embodiments herein also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, providing user data. The method may also comprise, at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The base station performs any of the steps of any of the embodiments described above for a base station.

In some embodiments, the method further comprising, at the base station, transmitting the user data.

In some embodiments, the user data is provided at the host computer by executing a host application. In this case, the method further comprises, at the UE, executing a client application associated with the host application.

Embodiments herein also include a user equipment (UE) configured to communicate with a base station. The UE comprises a radio interface and processing circuitry configured to perform any of the embodiments above described for a UE.

Embodiments herein further include a communication system including a host computer. The host computer comprises processing circuitry configured to provide user data, and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE). The UE comprises a radio interface and processing circuitry. The UE's components are configured to perform any of the steps of any of the embodiments described above for a UE.

In some embodiments, the cellular network further includes a base station configured to communicate with the UE.

In some embodiments, the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data. The UE's processing circuitry is configured to execute a client application associated with the host application.

Embodiments also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, providing user data and initiating a transmission carrying the user data to the UE via a cellular network comprising the base station. The UE performs any of the steps of any of the embodiments described above for a UE.

In some embodiments, the method further comprises, at the UE, receiving the user data from the base station.

Embodiments herein further include a communication system including a host computer. The host computer comprises a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The UE comprises a radio interface and processing circuitry. The UE's processing circuitry is configured to perform any of the steps of any of the embodiments described above for a UE.

In some embodiments the communication system further includes the UE.

In some embodiments, the communication system further including the base station. In this case, the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

Embodiments herein also include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, receiving user data transmitted to the base station from the UE. The UE performs any of the steps of any of the embodiments described above for the UE.

In some embodiments, the method further comprises, at the UE, providing the user data to the base station.

In some embodiments, the method also comprises, at the UE, executing a client application, thereby providing the user data to be transmitted. The method may further comprise, at the host computer, executing a host application associated with the client application.

In some embodiments, the method further comprises, at the UE, executing a client application, and, at the UE, receiving input data to the client application. The input data is provided at the host computer by executing a host application associated with the client application. The user data to be transmitted is provided by the client application in response to the input data.

Embodiments also include a communication system including a host computer. The host computer comprises a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station. The base station comprises a radio interface and processing circuitry. The base station's processing circuitry is configured to perform any of the steps of any of the embodiments described above for a base station.

In some embodiments, the communication system further includes the base station.

In some embodiments, the communication system further includes the UE. The UE is configured to communicate with the base station.

Embodiments moreover include a method implemented in a communication system including a host computer, a base station and a user equipment (UE). The method comprises, at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE. The UE performs any of the steps of any of the embodiments described above for a UE.

In some embodiments, the method further comprises, at the base station, receiving the user data from the UE.

In some embodiments, the method further comprises, at the base station, initiating a transmission of the received user data to the host computer.

The term “A and/or B” as used herein covers embodiments having A alone, B alone, or both A and B together. The term “A and/or B” may therefore equivalently mean “at least one of any one or more of A and B”.

Some of the embodiments contemplated herein are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.Notably, modifications and other embodiments of the disclosed invention(s) will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention(s) is/are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of this disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Example embodiments of the techniques and apparatus described herein include, but are not limited to, the following enumerated examples:

Group A Embodiments

A1. A method performed by a wireless device, the method comprising: transmitting signaling which indicates a range of values that the wireless device supports for a triggering offset, wherein a triggering offset is an offset between:a slot containing downlink control information that triggers a set of aperiodic channel state information reference signal, CSI-RS, resources; anda slot in which the set of aperiodic CSI-RS resources is transmitted.A2. The method of embodiment A1, further comprising, after transmitting the signaling, receiving a control message that configures the wireless device with a triggering offset that has a value within the range of values indicated by the transmitted signaling.A3. The method of embodiment A2, further comprising:receiving, in a first slot, downlink control information that triggers a set of aperiodic CSI-RS resources; andreceiving, in a second slot, CSI-RS on the set of aperiodic CSI-RS resources triggered by the received downlink control information, wherein the offset between the first slot and the second slot has a value within the range of values indicated by the transmitted signaling.A4. The method of embodiment A3, further comprising, based on the triggering offset configured by the received control message, operating in a sleep state between the first slot and the second slot.A5. The method of embodiment A3, wherein the downlink control information is received from a first cell and the CSI-RS is received from a second cell, wherein the second cell has a higher subcarrier spacing, SCS, than the first cell.A6. The method of any of embodiments A1-A5, wherein the signaling indicates that the wireless device supports a range of values for the triggering offset that is extended as compared to a range of values supportable by another type of wireless device for the triggering offset.A7. The method of any of embodiments A1-A6, wherein the signaling indicates that the wireless device supports a range of values for the triggering offset that includes values above a value threshold and/or that includes a number of values above a range size threshold.A8. The method of any of embodiments A1-A7, wherein the signaling indicates that the wireless device supports a range of values for the triggering offset that comprises values between 0 and 31.A9. The method of any of embodiments A1-A8, wherein the signaling indicates that the wireless device supports a range of values for the triggering offset according to a certain 3GPP Release.A10. The method of any of embodiments A1-A9, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset by indicating that the wireless device supports a certain parameter in a control message that configures the triggering offset.A11. The method of embodiment A10, wherein the certain parameter is an aperiodicTriggeringOffsetExt-r16 parameter, and wherein the control message is a Radio Resource Control, RRC, message.

A12. The method of any of embodiments A1-A9, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset by indicating which values the wireless device supports for the triggering offset.

A13. The method of any of embodiments A1-A9, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset by indicating that the wireless device supports cross-slot scheduling.

A14. The method of any of embodiments A1-A9, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset by indicating that the wireless device supports cross-carrier aperiodic CSI-RS triggering with different subcarrier spacing.

A15. The method of any of embodiments A1-A9, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset independent of any support by the wireless device for cross-slot scheduling and/or for cross-carrier aperiodic CSI-RS triggering with different subcarrier spacing.AA. The method of any of the previous embodiments, further comprising:providing user data; andforwarding the user data to a host computer via the transmission to a base station.

Group B Embodiments

B1. A method performed by a network node, the method comprising:receiving signaling which indicates a range of values that a wireless device supports fora triggering offset, wherein the triggering offset is an offset between:a slot containing downlink control information that triggers a set of aperiodic channel state information reference signal, CSI-RS, resources; anda slot in which the set of aperiodic CSI-RS resources is transmitted.B2. The method of embodiment B1, further comprising, based on the received signaling, configuring the wireless device with a triggering offset.B3. The method of any of embodiments B1-B2, further comprising transmitting, to the wireless device, a control message which configures the wireless device with a triggering offset that has a value within the range of values indicated by the receiving signaling.B4. The method of any of embodiments B1-B3, further comprising selecting the value of the triggering offset with which to configure the wireless device from among any of the values within the range indicated by the receiving signaling.

B5. The method of any of embodiments B1-B4, further comprising transmitting aperiodic CSI-RS to the wireless device based on the received signaling.B6. The method of any of embodiments B1-B5, further comprising determining a set of aperiodic CSI-RS resources on which to transmit aperiodic CSI-RS to the wireless device, based on the received signaling.B7. The method of any of embodiments B1-B6, further comprising determining a slot in which a set of aperiodic CSI-RS resources is to be transmitted to the wireless device, based on the received signaling.B8. The method of any of embodiments B1-B7, further comprising transmitting aperiodic CSI-RS to the wireless device on a set of aperiodic CSI-RS resources within a slot that is determined based on the received signaling.B9. The method of any of embodiments B1-B8, further comprising:transmitting, in a first slot, to the wireless device, downlink control information that triggers a set of aperiodic CSI-RS resources; and/ortransmitting, in a second slot, to the wireless device, CSI-RS on the set of aperiodic CSI-RS resources triggered by the transmitted downlink control information, wherein the offset between the first slot and the second slot has a value within the range of values indicated by the received signaling.B10. The method of embodiment B9, wherein the downlink control information is transmitted from a first cell and the CSI-RS is transmitted from a second cell, wherein the second cell has a higher subcarrier spacing, SCS, than the first cell.B11. The method of any of embodiments B1-B5, wherein the signaling indicates that the wireless device supports a range of values for the triggering offset that is extended as compared to a range of values supportable by another type of wireless device for the triggering offset.B12. The method of any of embodiments B1-B11, wherein the signaling indicates that the wireless device supports a range of values for the triggering offset that includes values above a value threshold and/or that includes a number of values above a range size threshold.B13. The method of any of embodiments B1-B12, wherein the signaling indicates that the wireless device supports a range of values for the triggering offset that comprises values between 0 and 31.B14. The method of any of embodiments B1-B13, wherein the signaling indicates that the wireless device supports a range of values for the triggering offset according to a certain 3GPP Release.B15. The method of any of embodiments B1-B14, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset by indicating that the wireless device supports a certain parameter in a control message that configures the triggering offset.B16. The method of embodiment B15, wherein the certain parameter is an aperiodicTriggeringOffsetExt-r16 parameter, and wherein the control message is a Radio Resource Control, RRC, message.B17. The method of any of embodiments B1-B14, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset by indicating which values the wireless device supports for the triggering offset.B18. The method of any of embodiments B1-B14, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset by indicating that the wireless device supports cross-slot scheduling.B19. The method of any of embodiments B1-B14, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset by indicating that the wireless device supports cross-carrier aperiodic CSI-RS triggering with different subcarrier spacing.B20. The method of any of embodiments B1-B14, wherein the signaling indicates the range of values that the wireless device supports for a triggering offset independent of any support by the wireless device for cross-slot scheduling and/or for cross-carrier aperiodic CSI-RS triggering with different subcarrier spacing.B21. The method of any of embodiments B1-B20, wherein the network node is a radio network node.BB. The method of any of the previous embodiments, further comprising:obtaining user data; andforwarding the user data to a host computer or a wireless device.

Group C Embodiments

C1. A wireless device configured to perform any of the steps of any of the Group A embodiments.C2. A wireless device comprising processing circuitry configured to perform any of the steps of any of the Group A embodiments.C3. A wireless device comprising:communication circuitry; andprocessing circuitry configured to perform any of the steps of any of the Group A embodiments.C4. A wireless device comprising:processing circuitry configured to perform any of the steps of any of the Group A embodiments; andpower supply circuitry configured to supply power to the wireless device.C5. A wireless device comprising:processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the wireless device is configured to perform any of the steps of any of the Group A embodiments.C6. A user equipment (UE) comprising:an antenna configured to send and receive wireless signals;radio front-end circuitry connected to the antenna and to processing circuitry, andconfigured to condition signals communicated between the antenna and the processing circuitry;the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; anda battery connected to the processing circuitry and configured to supply power to the UE.C7. A computer program comprising instructions which, when executed by at least one processor of a wireless device, causes the wireless device to carry out the steps of any of the Group A embodiments.C8. A carrier containing the computer program of embodiment C7, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.C9. A network node configured to perform any of the steps of any of the Group B embodiments.C10. A network node comprising processing circuitry configured to perform any of the steps of any of the Group B embodiments.C11. A network node comprising:communication circuitry; andprocessing circuitry configured to perform any of the steps of any of the Group B embodiments.C12. A network node comprising:processing circuitry configured to perform any of the steps of any of the Group B embodiments;power supply circuitry configured to supply power to the network node.C13. A network node comprising:processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the network node is configured to perform any of the steps of any of the Group B embodiments.C14. The network node of any of embodiments C9-C13, wherein the network node is a base station.C15. A computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to carry out the steps of any of the Group B embodiments.C16. The computer program of embodiment C14, wherein the network node is a base station.C17. A carrier containing the computer program of any of embodiments C15-C16, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Group D Embodiments

D1. A communication system including a host computer comprising:processing circuitry configured to provide user data; anda communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.D2. The communication system of the previous embodiment further including the base station.D3. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.D4. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE comprises processing circuitry configured to execute a client application associated with the host application.D5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, providing user data; andat the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.D6. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.D7. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the previous 3 embodiments.D9. A communication system including a host computer comprising:processing circuitry configured to provide user data; anda communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments.D10. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.D11. The communication system of the previous 2 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE's processing circuitry is configured to execute a client application associated with the host application.D12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, providing user data; andat the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.D13. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.D14. A communication system including a host computer comprising:communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.D15. The communication system of the previous embodiment, further including the UE.D16. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.D17. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application; andthe UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.D18. The communication system of the previous 4 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; andthe UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.D19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.D20. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.D21. The method of the previous 2 embodiments, further comprising:at the UE, executing a client application, thereby providing the user data to be transmitted; andat the host computer, executing a host application associated with the client application.D22. The method of the previous 3 embodiments, further comprising:at the UE, executing a client application; andat the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,wherein the user data to be transmitted is provided by the client application in response to the input data.D23. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.D24. The communication system of the previous embodiment further including the base station.D25. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.D26. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application;the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.D27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.D28. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.D29. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.