WO2020067967A1

WO2020067967A1 - Frequency hopping for transmission with multiple repetitions

Info

Publication number: WO2020067967A1
Application number: PCT/SE2019/050895
Authority: WO
Inventors: Alexey SHAPIN; Jonas FRÖBERG OLSSON; Kittipong KITTICHOKECHAI; Majid GERAMI; Mattias Andersson; Sorour Falahati; Yufei Blankenship
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2018-09-28
Filing date: 2019-09-20
Publication date: 2020-04-02

Abstract

A method, network node and wireless device for frequency hopping for transmission with multiple repetitions are disclosed. According to one aspect, a method in a wireless device includes generating physical uplink shared channel, PUSCH, messages to be transmitted to the network node. The method includes generating a physical uplink shared channel (PUSCH) message to be transmitted to the network node, the PUSCH message spanning a duration of less than 14 symbols, The method further includes transmitting the PUSCH messages by frequency hopping so that each PUSCH message of a group of PUSCH messages is transmitted on alternating frequencies.

Description

FREQUENCY HOPPING FOR TRANSMISSION WITH MULTIPLE

REPETITIONS

TECHNICAL FIELD

The present disclosure relates to wireless communication and in particular, to frequency hopping for transmissions with multiple repetitions.

BACKGROUND

Ultra-reliable and low latency communication (URLLC) requirements on reliability and latency are very strict. For example, requirements may include at least 99.999% reliability with a 1 milli-second (ms) one-way latency. To achieve low latency, transmissions with short duration are used. To achieve high reliability, transmissions with a low code rate, possibly with longer duration, may be used.

The New Radio (NR) radio communication standard, Technical Standards (TS) Release 15 (Rel. 15), developed by the Third Generation Partnership Project (3GGP), provides that transmission of the physical uplink shared channel, PUSCH, is to be supported in the forms of intra-slot and inter-slot frequency hopping.

When PUSCH is scheduled without repetition, intra-slot frequency hopping applies frequency offset on the starting resource block (RB) of the second hop of the scheduled PUSCH. Each hop is determined by number of orthogonal frequency division multiplexed, OFDM, symbols in the scheduled PUSCH, i.e., the number of symbols in the first hop is

Nsym is the number of OFDM symbols in the scheduled PUSCH.

When the PUSCH is scheduled over multiple slots including the case of PUSCH message repetition, inter-slot frequency hopping can be applied. Here frequency hopping applies on the slot basis where the starting resource block (RB) of every slot with an odd slot number within a radio frame is applied with a frequency offset.

The following text is taken from the 3GPP Technical Standard, TR 38.214 V15.2.0, as a reference: 1. If a WD is configured by higher layer parameter frequencyHopping in PUSCH-Config , one of two frequency hopping modes can be configured:

Intra-slot frequency hopping, applicable to single slot and multi- slot PUSCH transmission.

Inter-slot frequency hopping, applicable to multi-slot PUSCH transmission.

2. When frequency hopping on PUSCH is enabled and for resource allocation type 1, frequency offsets are configured by higher layer parameter f requencyHoppingOffsetLists in PUSCH-Config:

3. - when the size of the active bandwidth part (BWP) is less than 50

physical resource blocks (PRBs), one of two higher layer configured offsets is indicated in the uplink (UL) grant.

4. - when the size of the active BWP is equal to or greater than 50 PRBs, one of four higher layer configured offsets is indicated in the UL grant.

5. The starting RB during in each hop is given by:

RB start Firsthop

¾tart^{— '}

(RB_star_t+RB_offSe_t)^modA¾^ Secondiop

6

7. where ^RBstiirt be the starting resource within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1

(described in sub-clause 6.1.2.2.2) and RB offset is the frequency offset in RBs between the two frequency hops.

8. In case of intra-slot frequency hopping is configured for PUSCH without repetitions, the number of symbols in the first hop is given

N ^uUS

the number of symbols in the second hop is given by stymb

where N^_y^^H'^s is the length of the PUSCH transmission in OFDM symbols in one slot. 9. In case of inter-slot frequency hopping, the starting RB during slot n ^{5 f} is given by:

11. where " _' is the current slot number within a radio frame, where a multi-slot

PUSCH transmission can take place, RB_C is the starting resource within the

UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (described in sub-clause 6.1.2.2.2 of 3GPP. Rel.

15) and RB offset is the frequency offset in RBs between the two frequency hops.

In NR Rel. 15, PUSCH frequency hopping is specified for intra- and inter-slot frequency hopping. The intra-slot frequency hopping is defined based on symbol number in a slot, while the inter-slot frequency hopping is defined only on a slot basis based on slot numbers. SUMMARY

Some embodiments advantageously provide methods, network nodes and wireless devices for frequency hopping of transmissions with multiple repetitions.

To achieve both high reliability and low latency, repetition of a short-duration transmission can be desirable, especially in a scenario where the wireless device (WD) might have to wait for the start of the next slot for the transmission. Due to short total time duration, each repetition is likely to experience similar channel conditions. Therefore, frequency hopping across repetitions is relevant to provide additional frequency diversity gain.

Some embodiments provide methods for frequency hopping for PUSCH message repetition where each repetition may span less than 14 symbols (slot duration). These methods are useful for latency critical services where repetition of short transmission duration is scheduled or configured. Frequency hopping for PUSCH message repetition where each repetition spans less than 14 symbols is based on applying a frequency offset on the starting resource block (RB) of certain repetitions or a group of repetitions within the PUSCH transmission.

The frequency hopping pattern can be defined based on repetition number or repetition group number within the PUSCH transmission.

The repetition number or repetition group number within the PUSCH transmission can be derived from radio resource control (RRC) configured parameters related to repetition factor or number or an explicit indicator in the downlink control information (DCI) of the uplink (UL) grant or activation grant.

According to one aspect, a network node is configured to communicate with a WD. The network node includes a radio interface and processing circuitry configured to transmit an indication of a number of repetitions of a physical uplink shared channel, PUSCH, message to be transmitted by the WD, each PUSCH message repetition spanning a duration of less than 14 symbols. The radio interface and processing circuitry are further configured to receive repetitions of the PUSCH message from the WD according to a frequency hopping pattern.

According to this aspect, in some embodiments, a plurality of the repetitions are within the same 14-symbol slot. In some embodiments, a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot. In some embodiments, the radio interface and the processing circuitry are configured to transmit an indication of a duration of a first repetition of the PUSCH message. In some embodiments, at least two of the repetitions of the PUSCH message are in consecutive symbol allocations. In some embodiments, the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message. In some embodiments, a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message. In some embodiments, frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of repetition

given by:

mod 2 = 0

mod 2 = 1 and where is the number of a specific repetition of the PUSCH message, ^RBslarl is the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^ ^offset is a frequency offset in RBs between two frequency hops. In some embodiments, frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition. In some embodiments, a frequency hopping pattern includes alternation between two frequencies at most within a slot. In some embodiments, a number of hops in the frequency hopping pattern is limited to two per slot. In some embodiments, when a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition. In some embodiments, a hopping position corresponds to a position of a demodulation reference signal,

DMRS, symbol in the PUSCH message repetition. In some embodiments, the network node further transmits a resource block offset value in downlink control information, DCI.

According to another aspect, a method implemented in a network node includes transmitting an indication of a number of repetitions of a PUSCH message to be transmitted by the WD, each repetition spanning a duration of less than 14 symbols. The method further includes receiving repetitions of the PUSCH message from the WD according to a frequency hopping pattern.

According to this aspect, in some embodiments, a plurality of the repetitions are within the same 14-symbol slot. In some embodiments, a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot. In some embodiments, the radio interface and/or the processing circuitry is configured to transmit an indication of a duration of a first repetition of the PUSCH message. In some embodiments, at least two of the repetitions of the PUSCH message are in consecutive symbol allocations. In some embodiments, the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message. In some embodiments, a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message. In some embodiments, frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of

rf

repetition is given by:

mod 2 = 0

mod 2 = 1 and where is the number of a specific repetition of the PUSCH message,

the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^ ^offset is a frequency offset in RBs between two frequency hops. In some embodiments, frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition. In some embodiments, a frequency hopping pattern includes alternation between two frequencies at most within a slot. In some embodiments, a number of hops in the frequency hopping pattern is limited to two per slot. In some embodiments, when a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition. In some embodiments, a hopping position corresponds to a position of a demodulation reference signal,

DMRS, symbol in the PUSCH message repetition. In some embodiments, the method further includes transmitting a resource block offset value in downlink control information, DCI.

According to yet another aspect, a WD is configured to communicate with a network node. The WD includes a radio interface and processing circuitry configured to generate a physical uplink shared channel, PUSCH, message to be transmitted to the network node, the PUSCH message spanning a duration of less than 14 symbols; and to transmit multiple repetitions of the PUSCH message by frequency hopping according to a frequency hopping pattern, repetitions of the PUSCH message being transmitted on alternating frequencies.

According to this aspect, in some embodiments, the radio interface and processing circuitry is configured to receive the span of the PUSCH message by signaling from the network node. In some embodiments, a plurality of the repetitions are within the same 14-symbol slot. In some embodiments, a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot. In some embodiments, the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message. In some embodiments, a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message. In some embodiments, frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of repetition is given by:

and where

is the number of a specific repetition of the PUSCH message,

^RBstart i_s the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^RB °^ffset is a frequency offset in RBs between two frequency hops. In some embodiments, frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition. In some embodiments, a frequency hopping pattern includes alternation between two frequencies at most within a slot. In some embodiments, a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition. In some embodiments, a hopping position corresponds to a position of a demodulation reference signal, DMRS, symbol in the PUSCH message repetition. In some embodiments, the radio interface and processing circuitry are further configured to receive a resource block offset value in downlink control information, DCI.

According to another aspect, in some embodiments, a method implemented in a WD 22 includes generating a physical uplink shared channel, PUSCH, message to be transmitted to the network node, the PUSCH message spanning a duration of less than 14 symbols. The method further includes transmitting multiple repetitions of the PUSCH message by frequency hopping according to an intra-slot frequency hopping pattern, repetitions of the PUSCH message being transmitted on alternating frequencies.

According to another aspect, in some embodiments, a plurality of the repetitions are within the same 14-symbol slot. In some embodiments, a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot. In some embodiments, the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message. In some embodiments, a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message. In some embodiments, frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of repetition ^s is given by:

mod 2 = 0

mod 2 = 1 and where

is the number of a specific repetition of the PUSCH message, ^RBstart i_s the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^{RB offset} is a frequency offset in RBs between two frequency hops. In some embodiments, frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition. In some embodiments, a frequency hopping pattern includes alternation between two frequencies at most within a slot. In some embodiments, when a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition. In some embodiments, a hopping position corresponds to a position of a demodulation reference signal,

DMRS, symbol in the PUSCH message repetition. In some embodiments, the method further includes a resource block offset value in downlink control information, DCI.

BRIEF DESCRIPTION OF THE DRAWINGS A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

FIG. 1 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

FIG. 2 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

FIG. 3 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

FIG. 4 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

FIG. 6 is a flowchart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

FIG. 7 is a flowchart of an exemplary process in a network node for frequency hopping for transmission with multiple repetitions; FIG. 8 is a flowchart of an exemplary process in a wireless device for frequency hopping for transmission with multiple repetitions;

FIG. 9 is an illustration of frequency offset applied to a transmission with two repetitions;

FIG. 10 is an illustration of a repetition pattern;

FIG. 11 is an illustration of a group repetition pattern;

FIG. 12 is an illustration of another group repetition pattern;

FIG. 13 is an illustration of scheduling across a slot boundary;

FIG. 14 is an illustration of PUSCH transmission with two repetitions across a slot border;

FIG. 15 is an illustration of using a larger duration to determine hopping position; and

FIG. 16 is an illustration of a first repetition having a larger duration than a second repetition.

DETAILED DESCRIPTION

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to frequency hopping for transmission with multiple repetitions. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

As used herein, relational terms, such as“first” and“second,”“top” and

“bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms“a”,“an” and“the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms“comprises,”“comprising,”“includes” and/or“including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term,“in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may inter-operate and modifications and variations are possible for achieving the electrical and data communication.

In some embodiments described herein, the term“coupled,”“connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term“network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term“radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals. The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), ETSB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc.

Also, in some embodiments the generic term“radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio ETnit (RRET) Remote Radio Head (RRH).

Note that although terminology from one particular wireless system, such as, for example, 3GPP Long Term Evolution (LTE) and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), ETltra Mobile Broadband (LIMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices. The term“signaling” used herein may comprise any of: high-layer signaling (e.g., via Radio Resource Control (RRC) or a like), lower-layer signaling (e.g., via a physical control channel or a broadcast channel), or a combination thereof. The signaling may be implicit or explicit. The signaling may further be unicast, multicast or broadcast. The signaling may also be directly to another node or via a third node.

In some embodiments, control information on one or more resources may be transmitted in a message having a specific format. A message may comprise or represent bits representing payload information and coding bits, e.g., for error coding.

Receiving (or obtaining) control information may comprise receiving one or more control information messages (e.g., an RRC monitoring parameter). It may be considered that receiving control signaling comprises demodulating and/or decoding and/or detecting, e.g. blind detection of, one or more messages, a message carried by the control signaling, e.g. based on an assumed set of resources, which may be searched and/or listened for the control information. It may be assumed that both sides of the communication (e.g., network and WD side) are aware of the configurations, and may determine the set of resources, e.g. based on for example the reference size.

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. 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 corresponding to a table, and/or one or more bit patterns representing the information.

Configuring a radio node, in particular a terminal or WD, may refer to the radio node being adapted or caused or set and/or instructed to operate according to the configuration (e.g., to monitor PDCCH according to an adaptable CORESET and search space configuration scheme). Configuring may be done by another device, e.g., a network node (e.g., network node 16) (for example, a base station or gNB) or network, in which case it may comprise transmitting configuration data to the radio node to be configured. Such configuration data may represent the configuration to be configured and/or comprise one or more instruction pertaining to a configuration, e.g. a configuration for transmitting and/or receiving on allocated resources, in particular frequency resources. A radio node may configure itself, e.g., based on configuration data received from a network or network node. A network node may utilize, and/or be adapted to utilize, its circuitry for configuring. Allocation information may be considered a form of configuration data. Configuration data may comprise and/or be represented by configuration information, and/or one or more corresponding indications and/or message/s.

A channel may generally be a logical or physical channel. A channel may comprise and/or be arranged on one or more carriers, including a plurality of subcarriers. A wireless communication network may comprise at least one network node, in particular a network node as described herein. A terminal connected or communicating with a network may be considered to be connected or communicating with at least one network node, in particular any one of the network nodes described herein.

A channel may generally be a logical, transport or physical channel. A channel may comprise and/or be arranged on one or more carriers, in particular a plurality of subcarriers. A channel carrying and/or for carrying control signaling/control information may be considered a control channel, in particular if it is a physical layer channel and/or if it carries control plane information. Analogously, a channel carrying and/or for carrying data signaling/user information may be considered a data channel, in particular if it is a physical layer channel and/or if it carries user plane information. A channel may be defined for a specific communication direction, or for two complementary communication directions (e.g., UL and DL, or sidelink in two directions), in which case it may be considered to have two component channels, one for each direction.

Configuring a terminal or wireless device (WD) or node may involve instructing and/or causing the wireless device or node to change its configuration, e.g., at least one setting and/or register entry and/or operational mode. A terminal or wireless device or node may be adapted to configure itself, e.g., according to information or data in a memory of the terminal or wireless device (e.g., a

predetermined rule as discussed above). Configuring a node or terminal or wireless device by another device or node or a network may refer to and/or comprise transmitting information and/or data and/or instructions to the wireless device or node by the other device or node or the network, e.g., control information (which may also be and/or comprise configuration data) and/or scheduling data and/or scheduling grants. Configuring a terminal may include sending configuration data to the terminal indicating which search space configuration to use. A terminal may be configured with and/or for scheduling data and/or to use, e.g., for transmission, scheduled and/or allocated uplink resources, and/or, e.g., for reception, scheduled and/or allocated downlink resources. Uplink resources and/or downlink resources may be scheduled and/or provided with allocation or configuration data.

Configuring a Radio Node

Configuring a radio node, in particular, a terminal or user equipment or WD, may refer to the radio node being adapted or caused or set and/or instructed to operate according to the configuration. Configuring may be done by another device, e.g., a network node 16 (for example, a radio node of the network like a base station or eNodeB) or network, in which case it may comprise transmitting configuration data to the radio node to be configured. Such configuration data may represent the configuration to be configured and/or comprise one or more instruction pertaining to a configuration, e.g. a configuration for searching for information on a control channel in DRX mode. A radio node may configure itself, e.g., based on configuration data received from a network or network node 16. A network node 16 may use, and/or be adapted to use, its circuitry for configuring. Allocation information may be considered a form of configuration data. Configuration data may comprise and/or be represented by configuration information, and/or one or more corresponding indications and/or message/s.

Configuring in general

Generally, configuring may include determining configuration data representing the configuration and providing, e.g. transmitting, it to one or more other nodes (parallel and/or sequentially), which may transmit it further to the radio node (or another node, which may be repeated until it reaches the wireless device 22). Alternatively, or additionally, configuring a radio node, e.g., by a network node 16 or other device, may include receiving configuration data and/or data pertaining to configuration data, e.g., from another node like a network node 16, which may be a higher-level node of the network, and/or transmitting received configuration data to the radio node. Accordingly, determining a configuration and transmitting the configuration data to the radio node may be performed by different network nodes or entities, which may be able to communicate via a suitable interface, e.g., an X2 interface in the case of LTE or a corresponding interface for NR. Configuring a terminal (e.g. WD 22) may comprise configuring search space parameters or scheduling downlink and/or uplink transmissions for the terminal, e.g. downlink data and/or downlink control signaling and/or DCI and/or uplink control or data or communication signaling, in particular acknowledgement signaling, and/or configuring resources and/or a resource pool therefore.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

When repetition of short transmission is scheduled or configured, it is likely that all repetition will experience the same or at least similar channel conditions. Frequency hopping for PUSCH repetition can provide additional frequency diversity gain for the transmission. This is especially useful for high reliability services such as URLLC.

Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of a

communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes l6a, l6b, l6c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area l8a, 18b, l8c (referred to collectively as coverage areas 18). Each network node l6a, l6b, l6c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area l8a is configured to wirelessly connect to, or be paged by, the corresponding network node l6c. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node l6a. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer 24, 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. The host computer 24 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

The communication system of FIG. 1 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

A network node 16 is configured to include a PUSCH parameter unit 32 which is configured to transmit an indication of a number of repetitions of a PUSCH message to be transmitted by the WD 22, where each PUSCH message repetition spans a duration of less than 14 symbols. A wireless device 22 is configured to include a PUSCH generator unit 34 which is configured to generate a PUSCH message to be transmitted to the network node 16, where the PUSCH message spans a duration of less than 14 symbols.

Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 2. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The“user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.

The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the

communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include the PUSCH parameter unit 32 configured to transmit an indication of a number of repetitions of a PUSCH message to be transmitted by the WD 22, where each PUSCH message repetition spans a duration of less than 14 symbols .

The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a PETSCE1 generator unit 34 configured to generate a PETSCE1 message to be transmitted to the network node 16, where the PETSCE1 message spans a duration of less than 14 symbols.

In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1. In FIG. 2, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, 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 the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or

reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors etc.

Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for

preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for

preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

Although FIGS. 1 and 2 show various“units” such as PUSCH parameter unit 32, and PUSCH generator unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry. FIG. 3 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 1 and 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 2. In a first step of the method, the host computer 24 provides user data (block S100). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S104). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (block S106). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 114, associated with the host application 50 executed by the host computer 24 (block S108).

FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2. In a first step of the method, the host computer 24 provides user data (block Sl 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block Sl 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (block Sl 14).

FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (block Sl 16). In an optional substep of the first step, the WD 22 executes the client application 114, which provides the user data in reaction to the received input data provided by the host computer 24 (block Sl 18). Additionally, or alternatively, in an optional second step, the WD 22 provides user data (block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 114 (block S122). In providing the user data, the executed client application 114 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (block S126).

FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (block S 130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

FIG. 7 is a flowchart of an exemplary process in a network node 16 for frequency hopping for transmission with multiple repetitions. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the PUSCH parameter unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 such as via processing circuitry 68 and/or processor 70 and/or radio interface 62 and/or communication interface 60 is configured to transmit an indication of a number of repetitions of a physical uplink shared channel, PUSCH, message to be transmitted by the WD, each PUSCH message repetition spanning a duration of less than 14 symbols (Block S134). The process further includes receiving repetitions of the PUSCH message from the WD according to a frequency hopping pattern.

According to some aspects, in some embodiments, the process also includes transmitting, via the radio interface 62, an indication of a number of repetitions of a PUSCH message to be transmitted by the WD. In some embodiments, the process also includes transmitting, via the radio interface 62, an indication of a frequency hopping pattern. In some embodiments, the process includes transmitting, via the radio interface 62, an indication of a span of the PUSCH message, the span being less than a slot duration. According to some aspects, in some embodiments, inter-slot frequency hopping is achieved by replacing, via the processor 70, a slot number in the hopping pattern with a repetition number of each repetition of the PUSCH

transmission. In some embodiments, frequency hopping for PUSCH repetition is applied, via the processor 70, per a group of transmission occasions within a repetition. In some embodiments, different frequency hopping patterns result from different durations of each repetition. In some embodiments, a hopping position corresponds to a position of a demodulation reference signal symbol in the PUSCH repetition. In some embodiments, the network node 16 transmits, via the radio interface 62, to the WD 22 a repetition number within downlink control information (DCI). In some embodiments, the network node 16 transmits, via the radio interface 62, to the WD 22 radio resource control, RRC, parameters from which a repetition number can be derived. In some embodiments, transmissions can be coherently combined, via the processor 70.

FIG. 8 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the PUSCH generator unit 34), processor 86, radio interface 82 and/or communication interface 60.

Wireless device 22 such as via processing circuitry 84 and/or processor 86 and/or radio interface 82 is configured to generate a physical uplink shared channel, PUSCH, message to be transmitted to the network node, the PUSCH message spanning a duration of less than 14 symbols (Block S138). The process also includes transmitting multiple repetitions of the PUSCH message by frequency hopping according to a frequency hopping patern, repetitions of the PUSCH message being transmited on alternating frequencies (Block S140).

According to this aspect, in some embodiments, the slot duration is 14 symbols. In some embodiments, the frequency hopping is based on applying, via the processor 86, a frequency offset on a starting resource block, RB, for a group of repetitions of a PUSCH message. In some embodiments, at least some of the repetitions of the PUSCH message start at a symbol. In some embodiments, inter-slot frequency hopping is achieved by replacing a slot number in the hopping pattern with a repetition number of each repetition of the PUSCH transmission. In some embodiment, frequency hopping for PUSCH repetition is applied per a group of transmission occasions within a repetition. In some embodiments, different frequency hopping patterns result from different durations of each repetition. In some embodiments, a hopping position corresponds to a position of a demodulation reference signal symbol in the PUSCH repetition.

In some embodiments, the process further includes receiving, via the radio interface 82, an indication of the repetition number within downlink control information (DCI). In some embodiments, the process further includes receiving, via the radio interface 82, radio resource control, RRC, parameters from which the repetition number can be derived.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for frequency hopping for transmission with multiple repetitions.

In New Radio (NR) Rel. 15, inter-slot and intra-slot frequency hopping are supported for the PUSCH. For URLLC, due to strict latency constraint, scheduling across multiple slots is less relevant. However, with non-slot or“mini-slot” based transmission (e.g., type B allocation in time), frequency hopping across mini-slots becomes relevant especially for the case of PUSCH repetition. In this case, frequency hopping can provide additional frequency diversity gain in addition to the repetition gain in general. As used herein, a mini-slot may be any slot having a duration less than a full slot duration. For example, a full slot duration may be 14 OFDM symbols, and a mini-slot may be any number of symbols fewer than 14 symbols.

It is not clear whether frequency hopping within each mini-slot can provide reasonable performance gain as it depends on several factors including mini-slot duration, bandwidth used, DMRS overhead etc. On one hand, with the WD 22 being power limited, a relatively long mini-slot duration, e.g., 7 OFDM symbols or more may be used and frequency hopping within a mini-slot can be beneficial. On the other hand, when performing frequency hopping, multiple demodulation reference signal (DMRS) symbols may be required for different frequency hops leading to high DMRS overhead which might offset the frequency diversity gain.

Note that intra-slot frequency hopping for PUSCH without repetition in 3 GPP Rel. l5 is already specified in a way that also supports non-slot scheduling, i.e., PUSCH duration of less than 14 symbols. First and second hops may be determined by the number of OFDM symbols of the scheduled PUSCH. The hopping position is in the middle of PUSCH duration, i.e., number of symbols in the first hop is ^ ^sym j That is, intra slot frequency hopping for PUSCH without repetition can directly be used for intra mini-slot hopping of URLLC PUSCH.

For PUSCH with repetition, inter slot frequency hopping can be relied upon where frequency hopping applies at a slot level for each repetition. In 3GPP Rel. 15, an inter slot frequency hopping pattern was defined based on slot numbers.

For URLLC operating with mini-slots of duration less than 14 symbols, there may be multiple mini slot transmissions for the same transport block (TB) repeated within a slot or over multiple slots. In this case, a slot number does not necessarily correspond to each repetition. In the following embodiments, the frequency hopping pattern (also referred to a PUSCH message repetition pattern) may be generated via processing circuitry 68 of the network node 16 and indicated to the WD 22, or vice versa. Thus, in some embodiments, the network node 16 transmits an indication of a number of repetitions of the PUSCH message to be transmitted by the WD 22, and the WD 22 responds by transmitting the number of repetitions of the PUSCH message to the network node 16.

Embodiment 1 : Frequency hopping for PUSCH message repetition, where each repetition spans a duration of less than 14 symbols, is applied by adding a frequency offset to the starting resource block number of each repetition or a group of repetitions. See, e.g., FIG. 9 for an example of frequency offset applied to a transmission with two repetitions.

The frequency offset can be configured to the WD 22 via RRC. It is also possible that the frequency offset can be indicated by DCI in the UL grant indicating the offset values in a table containing a set of frequency offset values.

Embodiment 2:

Frequency hopping for PUSCH message repetition, where each repetition spans a duration of less than 14 symbols, is applied per repetition. It is possible to apply the same principle as in 3GPP Rel. 15 inter-slot frequency hopping by replacing the slot number in the hopping pattern formula with the repetition number or order number of each repetition of the PUSCH transmission (see, e.g., FIG. 10).

For example, to include at least some embodiments disclosed herein, the text for 3GPP Rel. 15 inter slot frequency hopping can be modified to:

• For frequency hopping for PUSCH repetition where each repetition has duration of less than 14 OFDM symbols, the starting RB of repetition is given by:

mod 2 = 0

RB. B start

start )- l(R_¾ size

+ ^{R B}oiTset ) ^mod '^V BWP

mod 2 = 1 where

is the repetition order within PUSCH repetition, ^RBslarl is the starting resource within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (for example as described in sub-clause 6.1.2.2.2) and ^RB °^ffset is the frequency offset in RBs between the two frequency hops.

The repetition number/order can be obtained either implicitly or explicitly. For example, the WD 22 and network node 16 may determine the repetition order from the order of transmission occasions in a PUSCH message repetition based on a repetition factor (configured in an RRC parameter or contained in an UL grant). If there is an UL grant associated with each repetition, a repetition number can be part of DCI in the UL grant. In some embodiments, the frequency offset, denoted as “RB offset” may also be part of the DCI in the UL grant.

Embodiment 3 :

Frequency hopping for PUSCH message repetition, where each repetition spans a duration of less than 14 symbols, may be applied per a group of transmission occasions within the repetition. For example, FIG.l 1 shows an example of 4 repetitions of a 2-symbol PUSCH message where frequency hopping is applied per a group of 2 repetitions. That is, the first hop is formed by the first two repetitions, while the second hop is formed by the last two repetitions.

In some embodiments, the number of repetitions per group can be RRC configured.

Embodiment 4:

A frequency hopping pattern for PUSCH message repetition, where each repetition spans a duration of less than 14 symbols, may be applied to a group of transmission occasions within the repetition so that there are only two hops per slot (one hopping per slot). In some embodiments, the frequency hopping pattern includes alternation between two frequencies at most within a slot. If there are K repetitions within a slot, frequency hopping may be applied at the middle repetition, i.e., the number of repetitions contained in the first hop is [K/2J or [K/2] This condition can provide a good balance between frequency diversity gain and complexity of PUSCH scheduling when, for example, the total transmission duration is relatively short, e.g., within a slot. See FIG. 12, for example.

Note that the above-described embodiments also apply to the case where the PUSCH message transmission with repetitions is scheduled across the slot boundary. See, for example, FIG. 13.

For Embodiment 4, special rules for DMRS mapping can be applied if consecutive repetitions use the same frequency allocation, e.g., the repetition following the first one can reuse DMRS.

Embodiment 5:

In case of PUSCH message repetition across the slot boundary where the duration of repetition in different slots are different, different frequency hopping patterns are possible depending on the duration of each repetition. For example, if there are two repetitions across two slots with different time durations and if the difference in duration is less than a certain threshold, the frequency hopping pattern can be based on the existing inter-slot frequency hopping pattern in 3GPP Rel. 15 (see, e.g., FIG. 14). Or, if the difference in duration is larger than or equal to a certain threshold, the frequency hopping pattern may be applied only on the repetition with a larger duration and may be based on existing intra-slot frequency hopping in 3GPP Rel. 15 using the larger duration to determine the hopping position (see, e.g., FIG. 15). Or, if the difference in duration is larger than or equal to a certain threshold, the frequency hopping pattern can be applied to the overall PUSCH transmission. The hopping position may be at the symbol in the middle of the overall PUSCH transmission, i.e., the number of symbols contained in the first hop is [L/2J or [L/2] where L is the overall PUSCH duration (see, e.g., FIG. 16). If the first repetition has larger duration than the second repetition, the hopping position is in the first repetition. Otherwise, the hopping position is in the second repetition.

FIG. 14 is an example of PUSCH transmission with two repetitions across the slot border where the first repetition has duration of 3 OFDM symbols, while the second repetition has 4 symbols. When the difference in duration between repetitions is less than a certain threshold (in this case, the difference is 1 symbol), frequency hopping is based on 3GPP Rel.15 inter-slot frequency hopping, that is, the frequency offset is applied per slot.

FIG. 15 is an example of PUSCH transmission with two repetitions across the slot border where the first repetition has duration of 5 symbols while the second repetition has 2 symbols. When the difference in duration between repetitions is larger than a certain threshold (in this case, the difference is 3 symbols), frequency hopping is applied to the first repetition with a larger duration and is based on 3GPP Rel.15 intra-slot frequency hopping using the larger duration to determine the hopping position.

FIG. 16 is an example of PUSCH transmission with two repetitions across the slot border where the first repetition has duration of 5 symbols while the second repetition has 2 symbols. When the difference in duration between repetitions is larger than a certain threshold (in this case, the difference is 3 symbols), frequency hopping is applied to the overall PUSCH transmission. The hopping position is at the middle of overall PUSCH transmission, i.e., the number of symbols contained in the first hop is |7/2J=3.

With the frequency hopping patterns for PUSCH message repetition in the above embodiments, the DMRS pattern may also follow the hopping pattern where it is possible to have only one DMRS symbol within each hop. Thus, in some embodiments, an indicated (configured) number of repetitions may be referred to as a nominal number of repetitions, which can be the same or different from the actual number of repetitions. It can be different when one or more of the nominal repetitions cross the slot boundary. In that case, that repetition may be split at the slot boundary into two repetitions, one in one slot and another immediately in the next slot. That is, in some embodiments, the frequency is applied to only nominal repetitions. In such embodiments, the split of a nominal repetition into two repetitions at the slot boundary is treated as one repetition when frequency hopping is applied).

Embodiment 6:

A frequency hopping pattern for PUSCH message repetition where each repetition spans a duration of less than 14 symbols may be applied to the overall PUSCH transmission and may be based on the DMRS pattern of the PUSCH message repetition. For example, the hopping position may correspond to a position of an additional DMRS symbol in the PUSCH message repetition.

Embodiment 7:

When frequency hopping occurs within a slot, there may be other intra-cell transmissions scheduled, e.g., slot-based transmissions (transmissions from other WDs 22), that the frequency-hopping should avoid. Otherwise some of the repetitions may collide with slot-based transmissions. With an RRC configured RB offset, the scheduling alternatives for slot-based transmissions may be severely limited causing reduced system performance. Thus, in one example of this embodiment, the RB offset is part of the UL grant so that a suitable RB offset can be indicated such that the repetitions do not collide with other (slot-based) transmissions. In another example of this embodiment, the UL grant indicates no frequency hopping if the RRC configured RB offset leads to one or more collisions with other (slot-based) transmissions.

Embodiment 8: A plurality of hopping patterns can be configured to the WD 22, e.g., in the form of offsets for every repetition. The active hopping pattern can be signaled to the WD 22 explicitly by the DCI field or implicitly by associated connection identity such as a radio network temporary identifier (RNTI) or hybrid automatic repeat request (HARQ) ID. As another variant of this embodiment, the WD 22 may choose from a plurality of configured hopping patterns according to a list of rules. The hopping pattern can also be associated with an UL configured grant profile.

In some embodiments, different frequency offsets can be applied to different repetitions or group of repetitions. This is a variant of some embodiments where only one offset is used.

Methods of embodiments 1-8 can be extended to interleaved frequency allocation or allocation by a group of RBs, when a WD 22 has been allocated by a non-contiguous set of RBs or groups of RBs, e.g., frequency allocation type 0 or type 1 as well as with a virtual resource block (VRB) to physical resource block (PRB) mapping. In this case, frequency hopping offsets can be defined in resource block groups (RBGs) or considering RB/RBG interleaving rules.

One or a plurality of parameters may be signaled to the WD 22 including an indication of a number of repetitions . In some embodiments, the signaling may include an indication of which of the above-described methods is to be implemented by the WD 22. This indication can be explicitly signaled by high level signaling (RRC) or by physical layer signaling (field in DCI), or can be implicitly signaled by another parameter value, WD 22 capability, DCI type or RNTI type.

Embodiment 9:

Methods to support coherent combinations across repetitions are provided in this embodiment. Since URLLC transmission tends to be short in time to reduce latency, the transmissions can be coherently combined in time to improve reception quality. One consideration is that the redundancy version and/or precoder can vary according to the hopping pattern of the repetition group.

In some embodiments, for a subset of, or all of, the adjacent repetitions that are also at the same frequency location (for example, same set of PRBs at one hop), the redundancy versions (RV) may be kept the same. When the WD 22 hops to a different frequency location, then the redundancy version may change (although it is not precluded that the RV does not change). This can be realized by cycling the RV when frequency hopping occurs. For illustration, in Figure 11, Repetition #1 and Repetition #2 in Repetition Group #1 have the same RV (e.g., RV FH groupl = 0), while Repetition #3 and Repetition #4 in Repetition Group #2 have the same RV (e.g., RV_FH_group2 = 2), which may be different from RV FH groupl.

In some embodiments, for a subset or all of the adjacent repetitions that are also at the same frequency location (for example, same set of PRB at one hop), the precoders are kept the same. When the WD 22 hops to a different frequency location, then the precoder may change (although it is not precluded that the precoder does not change). For illustration, in Figure 11 Repetition #1 and Repetition #2 in Repetition Group #1, the WD 22 uses the same precoder (called precoder FH groupl) for PUSCH transmissions, while Repetition #3 and Repetition #4 in Repetition Group #2 have the same precoder (called precoder_FH_group2) for PUSCH transmissions, which may be different than precoder FH groupl.

Note that if and how the precoder is allowed to vary may also be related to how the DMRS pattern is applied. For example, if repetition #r does not contain DMRS (for example, repetition #r relies on DMRS of its adjacent repetition #(r-l) and/or #(r+l)), then pre-coder of repetition #r may not change compared that of the repetition it relies on for DMRS (i.e., adjacent repetition #(r-l) and/or #(r+ 1 )) This is because the DMRS and the associated data transmission are applied with the same precoder data.

Some embodiments provide solutions for frequency hopping for PUSCH transmissions with repetitions where each repetition spans a duration of less than 14 OFDM symbols. The solutions consist of a number of options where a frequency hopping pattern can be defined by:

• Frequency hopping offset or set of offsets;

• Reusing existing 3GPP Release 15 formulas by applying repetition number instead of slot number;

• Duration of repetition or by presence of slot boundary during repetition process;

• Grouping of a plurality of repetitions into groups and applying hopping patterns to groups, including grouping based on slot boundary presence; and Position of DMRS symbols in transmission.

According to one aspect, a network node 16 is configured to communicate with a WD 22. The network node 16 includes a radio interface 62 and processing circuitry 68 configured to transmit an indication of a number of repetitions of a physical uplink shared channel, PUSCH, message to be transmitted by the WD 22, each PUSCH message repetition spanning a duration of less than 14 symbols. The radio interface 62 and processing circuitry 68 are further configured to receive repetitions of the PUSCH message from the WD 22 according to a frequency hopping pattern.

According to this aspect, in some embodiments, a plurality of the repetitions are within the same 14-symbol slot. In some embodiments, a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot. In some embodiments, the radio interface 62 and the processing circuitry 68 are configured to transmit an indication of a duration of a first repetition of the PUSCH message. In some embodiments, at least two of the repetitions of the PUSCH message are in consecutive symbol allocations. In some embodiments, the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message. In some embodiments, a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message. In some embodiments, frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of repetition

given by:

mod 2 = 0

mod 2 = 1 and where

is the number of a specific repetition of the PUSCH message,

RBstart i_s the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^RB °^ffset is a frequency offset in RBs between two frequency hops. In some embodiments, a number of hops in the frequency hopping pattern is limited to two per slot. In some embodiments, frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition. In some embodiments, a frequency hopping pattern includes alternation between two frequencies at most within a slot. In some embodiments, when a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition. In some embodiments, a hopping position corresponds to a position of a demodulation reference signal,

DMRS, symbol in the PUSCH message repetition. In some embodiments, the network node 16 further transmits a resource block offset value in downlink control information, DCI.

According to another aspect, a method implemented in a network node 16 includes transmitting an indication of a number of repetitions of a PUSCH message to be transmitted by the WD 22, each repetition spanning a duration of less than 14 symbols. The method further includes receiving repetitions of the PUSCH message from the WD 22 according to a frequency hopping pattern.

According to this aspect, in some embodiments, a plurality of the repetitions are within the same 14-symbol slot. In some embodiments, a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot. In some embodiments, the radio interface and/or the processing circuitry is configured to transmit an indication of a duration of a first repetition of the PUSCH message. In some embodiments, at least two of the repetitions of the PUSCH message are in consecutive symbol allocations. In some embodiments, the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message. In some embodiments, a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message. In some embodiments, frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of repetition

given by:

mod 2 = 0

According to yet another aspect, a WD 22 is configured to communicate with a network node 16. The WD 22 includes a radio interface 82 and processing circuitry 84 configured to generate a physical uplink shared channel, PUSCH, message to be transmitted to the network node 16, the PUSCH message spanning a duration of less than 14 symbols; and to transmit multiple repetitions of the PUSCH message by frequency hopping according to a frequency hopping pattern, repetitions of the PUSCH message being transmitted on alternating frequencies.

According to this aspect, in some embodiments, the radio interface 82 and processing circuitry 84 is configured to receive the span of the PUSCH message by signaling from the network node 16. In some embodiments, a plurality of the repetitions are within the same 14-symbol slot. In some embodiments, a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot. In some embodiments, the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a

PUSCH message. In some embodiments, a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message. In some embodiments, frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of repetition

is given by

mod 2 = 0

mod 2 = 1 and where

is the number of a specific repetition of the PUSCH message,

RBstart i_s the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^RB °^ffset is a frequency offset in RBs between two frequency hops. In some embodiments, frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition. In some embodiments, a frequency hopping pattern includes alternation between two frequencies at most within a slot. In some embodiments, a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition. In some embodiments, a hopping position corresponds to a position of a demodulation reference signal,

DMRS, symbol in the PUSCH message repetition. In some embodiments, the radio interface 82 and processing circuitry 84 are further configured to receive a resource block offset value in downlink control information, DCI.

According to another aspect, in some embodiments, a method implemented in a WD 22 includes generating a physical uplink shared channel, PUSCH, message to be transmitted to the network node 16, the PUSCH message spanning a duration of less than 14 symbols. The method further includes transmitting multiple repetitions of the PUSCH message by frequency hopping according to an intra-slot frequency hopping pattern, repetitions of the PUSCH message being transmitted on alternating frequencies.

According to another aspect, in some embodiments, a plurality of the repetitions are within the same 14-symbol slot. In some embodiments, a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot. In some embodiments, the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message. In some embodiments, a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message. In some embodiments, frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of repetition is given by:

and where

is the number of a specific repetition of the PUSCH message, ^RBstart i_s the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^RB °^ffset is a frequency offset in RBs between two frequency hops. In some embodiments, frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition. In some embodiments, a frequency hopping pattern includes alternation between two frequencies at most within a slot. In some embodiments, when a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition. In some embodiments, a hopping position corresponds to a position of a demodulation reference signal, DMRS, symbol in the PUSCH message repetition. In some embodiments, the method further includes a resource block offset value in downlink control information, DCI.

Some embodiments include the following:

Embodiment Al . A network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to:

transmit an indication of a number of repetitions of a physical uplink shared channel, PUSCH, message to be transmitted by the WD;

transmit an indication of a frequency hopping pattern; and transmit an indication of a span of the PUSCH message, the span being less than a slot duration, the number of repetitions of the PUSCH, the frequency pattern and the span of the PUSCH message being usable to provide frequency diversity gain.

Embodiment A2. The network node of Embodiment Al, wherein the slot duration is 14 symbols.

Embodiment A3. The network node of Embodiment Al , wherein the frequency hopping pattern is based on applying a frequency offset on a starting resource block, RB, for a group of repetitions of a PUSCH message.

Embodiment A4. The network node of Embodiment Al, wherein inter slot frequency hopping is achieved by replacing a slot number in the hopping pattern with a repetition number of each repetition of the PUSCH transmission.

Embodiment A5. The network node of Embodiment Al, wherein frequency hopping for PUSCH repetition is applied per a group of transmission occasions within a repetition.

Embodiment A6. The network node of Embodiment Al, wherein different frequency hopping patterns result from different durations of each repetition.

Embodiment A7. The network node of Embodiment Al, wherein a hopping position corresponds to a position of a demodulation reference signal symbol in the PUSCH repetition.

Embodiment A8. The network node of Embodiment A3, further comprising transmitting to the WD a repetition number within downlink control information, DCI.

Embodiment A9. The network node of Embodiment Al, further comprising transmitting to the WD radio resource control, RRC, parameters from which a repetition number can be derived.

Embodiment A10. The network node of Embodiment Al, wherein transmissions can be coherently combined.

Embodiment B 1. A method implemented in a network node, the method comprising:

transmitting an indication of a number of repetitions of a physical uplink shared channel, PUSCH, message to be transmitted by the WD; and

transmitting an indication of a frequency hopping pattern; and transmitting an indication of a span of the PUSCH message, the span being less than a slot duration, the number of repetitions of the PUSCH, the frequency pattern and the span of the PUSCH message being usable to provide frequency diversity gain.

Embodiment B2. The method of Embodiment B 1, wherein the slot duration is 14 symbols.

Embodiment B3. The method of Embodiment B 1 , wherein the frequency hopping pattern is based on applying a frequency offset on a starting resource block, RB, for a group of repetitions of a PUSCH message.

Embodiment B4. The method of Embodiment Bl, wherein inter-slot frequency hopping is achieved by replacing a slot number in the hopping pattern with a repetition number of each repetition of the PUSCH transmission.

Embodiment B5. The method of Embodiment B 1 , wherein frequency hopping for PUSCH repetition is applied per a group of transmission occasions within a repetition.

Embodiment B6. The method of Embodiment Bl, wherein different frequency hopping patterns result from different durations of each repetition.

Embodiment B7. The method of Embodiment Bl, wherein a hopping position corresponds to a position of a demodulation reference signal symbol in the PUSCH repetition.

Embodiment B8. The method of Embodiment B3, further comprising transmitting to the WD a repetition number within downlink control information,

DCI.

Embodiment B9. The method of Embodiment Bl, further comprising transmitting to the WD radio resource control, RRC, parameters from which a repetition number can be derived.

Embodiment B 10. The method of Embodiment Bl, wherein transmissions can be coherently combined.

Embodiment Cl . A wireless device, WD, configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to: generate physical uplink shared channel, PUSCH, messages to be transmitted to the network node;

receive a repetition pattern of the PUSCH to span over less than a slot duration; and

transmit the PUSCH messages by frequency hopping so that each PUSCH message of a group of PUSCH messages is transmitted at a different frequency.

Embodiment C2. The wireless device of Embodiment Cl, wherein the slot duration is 14 symbols.

Embodiment C3. The wireless device of Embodiment Cl, wherein the frequency hopping is based on applying a frequency offset on a starting resource block, RB, for a group of repetitions of a PUSCH message.

Embodiment C4. The wireless device of Embodiment Cl, wherein inter slot frequency hopping is achieved by replacing a slot number in the hopping pattern with a repetition number of each repetition of the PUSCH transmission.

Embodiment C5. The wireless device of Embodiment Cl, wherein frequency hopping for PUSCH repetition is applied per a group of transmission occasions within a repetition.

Embodiment C6. The wireless device of Embodiment Cl, wherein different frequency hopping patterns result from different durations of each repetition.

Embodiment C7. The wireless device of Embodiment Cl, wherein a hopping position corresponds to a position of a demodulation reference signal symbol in the PUSCH repetition.

Embodiment C8. The wireless device of Embodiment Cl, further comprising receiving an indication of the repetition number within downlink control information, DCI.

Embodiment C9. The wireless device of Embodiment Cl, further comprising receiving radio resource control, RRC, parameters from which the repetition number can be derived.

Embodiment C10. The wireless device of Embodiment Cl, wherein transmissions can be coherently combined.

Embodiment Dl . A method implemented in a wireless device, WD, the method comprising: generating physical uplink shared channel, PUSCH, messages to be transmitted to the network node;

receiving a repetition pattern of the PUSCH to span over less than a slot duration; and

transmitting the PUSCH messages by frequency hopping so that each PUSCH message of a group of PUSCH messages is transmitted at a different frequency.

Embodiment D2. The method of Embodiment Dl, wherein the slot duration is 14 symbols.

Embodiment D3. The method of Embodiment D 1 , wherein the frequency hopping is based on applying a frequency offset on a starting resource block, RB, for a group of repetitions of a PUSCH message.

Embodiment D4. The method of Embodiment Dl, wherein inter-slot frequency hopping is achieved by replacing a slot number in the hopping pattern with a repetition number of each repetition of the PUSCH transmission.

Embodiment D5. The method of Embodiment Dl, wherein frequency hopping for PUSCH repetition is applied per a group of transmission occasions within a repetition.

Embodiment D6. The method of Embodiment Dl, wherein different frequency hopping patterns result from different durations of each repetition.

Embodiment D7. The method of Embodiment Dl, wherein a hopping position corresponds to a position of a demodulation reference signal symbol in the PUSCH repetition.

Embodiment D8. The method of Embodiment Dl, further comprising receiving an indication of the repetition number within downlink control information, DCI.

Embodiment D9. The method of Embodiment Dl, further comprising receiving radio resource control, RRC, parameters from which the repetition number can be derived.

Embodiment D10. The method of Embodiment Dl, wherein transmissions can be coherently combined.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, and/or computer program product. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or“module.” Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other

programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that

communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is claimed is:

1. A network node (16) configured to communicate with a wireless device (WD) 22, the network node (16) comprising a radio interface and processing circuitry configured to:

transmit an indication of a number of repetitions of a physical uplink shared channel, PUSCH, message to be transmitted by the WD (22), each PUSCH message repetition spanning a duration of less than 14 symbols; and

receive repetitions of the PUSCH message from the WD (22) according to a frequency hopping pattern.

2. The network node (16) of Claim 1, wherein a plurality of the repetitions are within the same 14-symbol slot.

3. The network node (16) of any of Claims 1 and 2, wherein a plurality of the repetitions start at a symbol other than the first symbol of a l4-symbol duration time slot.

4. The network node (16) of any of Claims 1-3, wherein the radio interface and the processing circuitry are configured to transmit an indication of a duration of a first repetition of the PUSCH message.

5. The network node (16) of any of Claims 1-4, wherein at least two of the repetitions of the PUSCH message are in consecutive symbol allocations.

6. The network node (16) of any of Claims 1-5, wherein the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message.

7. The network node (16) of Claim 6, wherein a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message.

8. The network node (16) of any of Claims 1-7, wherein frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of repetition r is given by:

mod 2 = 0

mod 2 = 1 f

and where is the number of a specific repetition of the PUSCH message,

is the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^ ^offset is a frequency offset in RBs between two frequency hops.

9. The network node (16) of any of Claims 1-8, wherein frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition.

10. The network node (16) of any of Claims 1-9, wherein a frequency hopping pattern includes alternation between two frequencies at most within a slot.

11 The network node (16) of any of Claims 1-10, wherein a number of hops in the frequency hopping pattern is limited to two per slot.

12. The network node (16) of any of Claims 1-11, wherein, when a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition.

13. The network node (16) of any of Claims 1-12, wherein a hopping position corresponds to a position of a demodulation reference signal, DMRS, symbol in the PUSCH message repetition.

14. The network node (16) of any of Claims 1-13, wherein the network node (16) further transmits a resource block offset value in downlink control information, DCI.

15. A method implemented in a network node (16), the method comprising:

transmitting (S134) an indication of a number of repetitions of a physical uplink shared channel, PUSCH, message to be transmitted by the WD (22), each repetition spanning a duration of less than 14 symbols; and

receiving (S136) repetitions of the PUSCH message from the WD (22) according to a frequency hopping pattern.

16. The method of Claim 15, wherein a plurality of the repetitions are within the same l4-symbol slot.

17. The method of any of Claims 15 and 16, wherein a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot.

18. The method of any of Claims 15-17, wherein the radio interface and/or the processing circuitry is configured to transmit an indication of a duration of a first repetition of the PUSCH message.

19. The method of any of Claims 15-18, wherein at least two of the repetitions of the PUSCH message are in consecutive symbol allocations.

20. The method of any of Claims 15-19, wherein the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message.

21. The method of Claim 20, wherein a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message.

22. The method of any of Claims 15-21, wherein frequency hopping is achieved according to the following hopping pattern formula, where the starting resource block, RB, of repetition

is given by

mod 2 = 0

mod 2 = 1 and where

is the number of a specific repetition of the PUSCH message,

the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^ ^offset is a frequency offset in RBs between two frequency hops.

23. The method of any of Claims 15-22, wherein frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition.

24. The method of Claim 23, wherein a frequency hopping pattern includes alternation between two frequencies at most within a slot.

25. The method of any of Claims 15-24, wherein a number of hops in the frequency hopping pattern is limited to two per slot.

26. The method of any of Claims 15-25, wherein, when a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition.

27. The method of any of Claims 15-26, wherein a hopping position corresponds to a position of a demodulation reference signal, DMRS, symbol in the PUSCH message repetition.

28. The method of any of Claims 15-27, further comprising transmitting a resource block offset value in downlink control information, DCI.

29. A wireless device, WD (22), configured to communicate with a network node (16), the WD (22) comprising a radio interface and processing circuitry configured to:

generate a physical uplink shared channel, PUSCH, message to be transmitted to the network node (16), the PUSCH message spanning a duration of less than 14 symbols; and

transmit multiple repetitions of the PUSCH message by frequency hopping according to a frequency hopping pattern, repetitions of the PUSCH message being transmitted on alternating frequencies.

30. The WD (22) of Claim 29, wherein the radio interface and processing circuitry is configured to receive the span of the PUSCH message by signaling from the network node (16).

31. The WD (22) of Claim 29, wherein a plurality of the repetitions are within the same l4-symbol slot.

32. The WD (22) of any of Claims 29-31 wherein a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot.

33. The WD (22) of any of Claims 29-32, wherein the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message.

34. The WD (22) of Claim 33, wherein a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message.

35. The WD (22) of any of Claims 29-34, wherein frequency hopping is achieved according to the following hopping pattern formula , where the starting resource block, RB, of repetition

is given by

mod 2 = 0

mod 2 = 1 and where

is the number of a specific repetition of the PUSCH message,

RBstart i_s the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^RB °^ffset is a frequency offset in RBs between two frequency hops.

36. The WD (22) of any of Claims 29-35, wherein frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a PUSCH message repetition.

37. The WD (22) of Claim 36, wherein a frequency hopping pattern includes alternation between two frequencies at most within a slot.

38. The WD (22) of any of Claims 29-37, wherein, when a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition.

39. The WD (22) of any of Claims 29-38, wherein a hopping position corresponds to a position of a demodulation reference signal, DMRS, symbol in the PUSCH message repetition.

40. The WD (22) of any of Claims 29-39, wherein the radio interface and processing circuitry are further configured to receive a resource block offset value in downlink control information, DCI.

41. A method implemented in a wireless device, WD (22), the method comprising:

generating (S138) a physical uplink shared channel, PUSCH, message to be transmitted to the network node (16), the PUSCH message spanning a duration of less than 14 symbols; and

transmitting (S140) multiple repetitions of the PUSCH message by frequency hopping according to an intra-slot frequency hopping pattern, repetitions of the PUSCH message being transmitted on alternating frequencies.

42. The method of Claim 41, wherein a plurality of the repetitions are within the same l4-symbol slot.

43. The method of any of Claims 41 and 42, wherein a plurality of the repetitions start at a symbol other that the first symbol of a 14-symbol duration time slot.

44. The method of any of Claims 41-43, wherein the frequency hopping pattern is based on applying a frequency offset to a starting resource block, RB, for a group of repetitions of a PUSCH message.

45. The method of Claim 44, wherein a different frequency offset is applied for each one of a plurality of repetitions of the PUSCH message.

46. The method of any of Claims 41-45, wherein frequency hopping is achieved according to the following hopping pattern formula , where the starting resource block, RB, of repetition

is given by

mod 2 = 0

mod 2 = 1 and where

is the number of a specific repetition of the PUSCH message, ^RBstart i_s the starting resource within an uplink, UL, bandwidth part, BWP, as calculated from resource block assignment information of resource allocation type 1 and ^RB °^ffset is a frequency offset in RBs between two frequency hops.

47. The method of any of Claims 41-46, wherein frequency hopping for a PUSCH message repetition is applied per group of transmission occasions within a

PUSCH message repetition.

48. The method of Claim 47, wherein a frequency hopping pattern includes alternation between two frequencies at most within a slot.

49. The method of any of Claims 41-48, wherein, when a PUSCH message repetition crosses a slot boundary where the duration of PUSCH message repetitions in different slots are different, then different frequency hopping patterns correspond to different durations of each PUSCH message repetition.

50. The method of any of Claims 41-49, wherein a hopping position corresponds to a position of a demodulation reference signal, DMRS, symbol in the PUSCH message repetition.

51. The method of any of Claims 41-50, further comprising receiving a resource block offset value in downlink control information, DCI.