Frequency Hopping for Joint Channel Estimation

Abstract

A system and method for a frequency hopping scheme compatible with joint channel estimation is disclosed. In one embodiment, the method implemented in a user equipment (UE) includes determining a value of a hopping index for a first set of N consecutive slots (N is an integer greater than 1) and incrementing the value of the hopping index for a second set of N consecutive slots after the N consecutive slots. The method further includes determining, for uplink slots in the second set of N consecutive slots, a set of physical resource blocks (PRBs) for transmitting a physical channel from a set of frequency offsets according to the value of the hopping index for the second set of slots, and transmitting a physical uplink channel on the selected set of PRBs in the uplink slot.

Description

[Technical Field]

[0001] Related Applications This application claims the benefit of International Patent Application Serial No. PCT / CN2021 / 122497, filed October 2, 2021, the disclosure of which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates to a frequency hopping scheme for joint channel estimation. [Background technology]

[0003] I. Time Division Duplex (TDD) Frame Structure in New Radio (NR) The 3rd Generation Partnership Project (3GPP®) New Radio (NR) supports highly configurable combinations of downlink, uplink, and flexible slots for time division duplexing (TDD). The periodicity of the overall TDD pattern can be 20 milliseconds (ms), or 160 slots long with 120 kilohertz (kHz) subcarrier spacing. An overall TDD pattern can be specified with up to two partial patterns. Each partial TDD pattern can have a periodicity of 0.5, 0.625, 1, 1.25, 2, 2.5, 3, 4, 5, or 10 ms. A partial TDD pattern is defined by the number of downlink slots occupying the first slot of the TDD pattern, the number of downlink symbols in the special slot following the downlink slot, and the number of uplink slots at the end of the pattern, as well as the number of symbols preceding the uplink slot. If a TDD pattern has slots not defined as containing uplink (UL) or downlink (DL) slots or symbols, these symbols are considered flexible and can be dynamically directed to be used for either UL or DL ​​transmission.

[0004] Figure 1 shows an example of a TDD pattern for NR. The radio resource control (RRC) parameters that make up the TDD pattern in 3GPP Technical Specification (TS) 38.331 V16.5.0 TDD-UL-DL-ConfigCommon are shown in Figure 1. The total TDD pattern is 10 slots (5 ms) long and is defined by the TDD-UL-DL-ConfigCommon subpatterns "pattern1" and "pattern2" (5 slots each). The first pattern has three DL ("D") slots and one UL ("U") slot, while the second pattern has two DL slots and two UL slots. Each pattern has a special slot with 10 DL symbols, a two-symbol gap, and two UL symbols.

[0005] II. PUSCH Repetition in NR Release 15 and Release 16 II.A.NR Release 15 Slot aggregation for the Physical Uplink Shared Channel (PUSCH) was supported in Release 15 and renamed to "PUSCH Repetition Type A" in Release 16. The name PUSCH Repetition Type A is used even when there is only one repetition, i.e., no slot aggregation. In Release 15, no PUSCH transmissions overlapping with DL symbols are sent. For example, as disclosed in the Release 15 document (3GPP TSG RAN WG1 #AH_1801 Final Report V1.0.0, 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, February 26-March 2, 2018): Comparison of multi-slot transmission (PDSCH / PUSCH) with DCI and semi-static DL / UL allocation If the semi-static DL / UL allocation configuration of a slot does not conflict in direction with the scheduled PDSCH / PUSCH allocation symbols, the PDSCH / PUSCH of that slot is received / transmitted. If the semi-static DL / UL allocation configuration of a slot collides in direction with the scheduled PDSCH / PUSCH allocated symbols, the PDSCH / PUSCH transmission for that slot will not be received / transmitted, i.e., the effective repetition count will be reduced.

[0006] In Rel-15, the number of repetitions is semi-statically configured by the RRC parameter pusch-AggregationFactor. As shown below from the Rel-15 specification, a maximum of 8 repetitions is supported: pusch-AggregationFactor ENUMERATED { n2, n4, n8}

[0007] Early termination of PUSCH repetitions was discussed in R14 NR SI of RAN1#88, with the following consensus, but ultimately not standardized: ***Initiation of Agreement*** R1-1703868 WF with Grant-Free Iterations Huawei, HiSilicon, Nokia, ABS, ZTE, ZTE Microelectronics, CATT, Convida Wireless, CATR, OPPO, Inter Digital, Fujitsu agreement: · For a UE configured with K repetitions for TB transmission, with or without grant, the UE may continue to repeat (FFS can be different RV versions, FFS can be different MCS) for TB until one of the following conditions is met: If a UL grant is successfully received for the slot / minislot of the same TB FFS: How do you know if the grants are for the same TB? · FFS: Acknowledgement / indication of successful reception of that TB from the gNB. The number of iterations of the TB reaches K. FFS: Whether it is possible to determine whether the grant is for the same TB Note that this does not assume that UL grants are scheduled based on slots, whereas grant-free allocations are based on minislots (and vice versa). Other iteration termination criteria may also apply. ***Termination of Agreement***

[0008] II.B.NR Release 16 Release 16 supports a new repetition format, "PUSCH Repetition Type B." In this new repetition format, PUSCH repetition allows back-to-back repetition of PUSCH transmissions. The biggest difference between "PUSCH Repetition Type A" and "PUSCH Repetition Type B" is that "Repetition Type A" only allows one repetition per slot, and each repetition occupies the same symbol. Using this format when the PUSCH length is shorter than 14 results in gaps between repetitions, increasing overall latency. Another change compared to Release 15 is the way the repetition count is signaled. In Release 15, the repetition count is semi-statically configured, but in Release 16, the repetition count can be dynamically indicated in the downlink control information (DCI). This applies to both dynamic grants and Type 2 configured grants.

[0009] In NR Release 16, the invalid symbols of PUSCH repetition type B include reserved UL resources. The invalid symbol pattern indicator field is set in the scheduling DCI. Segmentation occurs around the symbols indicated as DL by the semi-static TDD pattern and the invalid symbols. The signaling of the number of repetitions is shown below.

[0010] In PUSCH repetition type A, when transmitting a PUSCH scheduled with DCI format 0_1 ​​or 0_2 in a physical downlink control channel (PDCCH) with a cyclic redundancy check (CRC)-scrambled cell radio network temporary identifier (C-RNTI), a modulation and coding scheme C-RNTI (MCS-C-RNTI), or a configured scheduling radio network temporary identifier (CS-RNTI) with new data indicator (NDI) equal to 1, 3GPP TS38.214 V16.2.0 discloses that the number of repetitions K is determined as described in the following excerpt: ***Beginning of excerpt from 3GPP TS38.214*** ·If numberofrepetitions exists in the resource allocation table, the number of repetitions K is equal to numberofrepetitions; ·If the UE is configured with pusch-AggregationFactor, the number of iterations K is equal to pusch-AggregationFactor; · Otherwise, K=1. ***END EXCERPT FROM 3GPP TS38.214***

[0011] In the following excerpt, 3GPP TS38.212 V16.1.0 discloses the format of DCI0_1: ***Beginning of excerpt from 3GPP TS38.212*** Time domain resource allocation - 0, 1, 2, 3, 4, 5, or 6 bits · 0, 1, 2, 3, or 4 bits, as defined in clause 6.1.2.1 of [6,TS38.214], if the upper layer parameter PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 is not set and the upper layer parameter pusch-TimeDomainAllocationList is set. The bit width of this field is determined as ceil(log2(I)) bits, where I is the number of entries in the upper layer parameter pusch-TimeDomainAllocationList or pusch-TimeDomainAllocationList-r16; · 0, 1, 2, 3, 4, 5, or 6 bits, as defined in clause 6.1.2.1 of [6,TS38.214], if the higher layer parameter PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1 is set. The bit width of this field is determined as ceil(log2(I)) bits, where I is the number of entries in the higher layer parameter PUSCH-TimeDomainResourceAllocationList-ForDCIformat0_1; Otherwise, the bit width of this field is determined as ceil(log2(I)) bits, where I is the number of entries in the default table. ***END OF EXCERPT FROM 3GPP TS38.212***

[0012] Also, 3GPP 38.331 V16.1.0 discloses the following information elements: ***Beginning of excerpt from 3GPP TS38.331*** PUSCH-Config information element pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} pusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need S pusch-TimeDomainAllocationListForDCI-Format0-1-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16} pusch-TimeDomainAllocationListForDCI-Format0-2-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16} PUSCH-TimeDomainResourceAllocation information element -- ASN1START -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START PUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocation PUSCH-TimeDomainResourceAllocation ::= SEQUENCE { k2 INTEGER(0..32) OPTIONAL, -- Need S mappingType ENUMERATED {typeA, typeB}, startSymbolAndLength INTEGER (0..127) } PUSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations-r16)) OF PUSCH-TimeDomainResourceAllocation-r16 PUSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE { k2-r16 INTEGER(0..32) OPTIONAL, -- Need S puschAllocationList-r16 SEQUENCE (SIZE(1..maxNrofMultiplePUSCHs-r16)) OF PUSCH-Allocation-r16, ... } PUSCH-Allocation-r16 ::= SEQUENCE { mappingType-r16 ENUMERATED {typeA, typeB} OPTIONAL, -- Cond NotFormat01-02-Or-TypeA startSymbolAndLength-r16 INTEGER (0..127) OPTIONAL, -- Cond NotFormat01-02-Or-TypeA startSymbol-r16 INTEGER (0..13) OPTIONAL, -- Cond RepTypeB length-r16 INTEGER (1..14) OPTIONAL, -- Cond RepTypeB numberOfRepetitions-r16 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} OPTIONAL, -- Cond Format01-02 ... } -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP -- ASN1STOP maxNrofUL-Allocations INTEGER ::= 16 -- Maximum number of PUSCH time domain resource allocations. maxNrofUL-Allocations-r16 INTEGER ::= 64 -- Maximum number of PUSCH time domain resource allocations ***END OF EXCERPT FROM 3GPP TS38.331***

[0013] III. Frequency Hopping Mechanism and Signaling In NR up to Release 16, different frequency hopping types are supported for the multi-slot PUSCH. More specifically, intra-slot and inter-slot frequency hopping is supported with PUSCH repetition type A, while inter-slot and inter-repetition frequency hopping is supported with PUSCH repetition type B. Two types of PUSCH repetitions are applied: PUSCH with dynamic grant and PUSCH with type 1 / 2 configuration grant. An indication of whether frequency hopping is enabled, the type of frequency hopping, and the frequency hopping offset list are configured in the RRC. For PUSCH with dynamic grant and type 2 configuration grant, the frequency hopping flag in the DCI field additionally enables frequency hopping, and the Frequency Domain Resource Allocation (FDRA) indicates one offset list. For type 1 configuration grant PUSCH, frequency hopping enablement and one frequency hopping offset are configured in the RRC.

[0014] The number of configurable frequency hopping offsets depends on the Bandwidth Part (BWP) size, up to a maximum of four. If the size of the active BWP is less than 50 Physical Resource Blocks (PRBs), one of two higher layer configured offsets is indicated in the UL grant. If the size of the active BWP is 50 PRBs or more, one of four higher layer configured offsets is indicated in the UL grant.

[0015] For PUSCH repetition type A, for intra-slot frequency hopping, the starting resource block (RB) at each hop is given by: TIFF0007774718000001.tif14158, where i=0 and i=1 are the first and second hops, respectively, and RB start is the starting RB in the UL BWP calculated from the resource block allocation information for resource allocation type 1 (as described in 3GPP TS32.213, section 6.1.2.2.2) or calculated from the resource allocation for the MsgA PUSCH (as described in 3GPP TS38.213), and RB offset is the frequency offset in RBs between two frequency hops. The number of symbols in the first hop is floor(N symb PUSCH,s / 2), and the number of symbols in the second hop is N symb PUSCH,s -floor(N symb PUSCH,s / 2) N symb PUSCH,s is the length of PUSCH transmission in one slot of OFDM symbols.

[0016] For PUSCH repetition type A, in the case of inter-slot frequency hopping, slot n s μ The starting RB between is given by: TIFF0007774718000002.tif14158 where n s μ is the current slot number in the radio frame in which the multi-slot PUSCH transmission takes place, and RBstart is the starting RB in the UL BWP calculated from the resource block allocation information of resource allocation type 1 (described in section 6.1.2.2 of 3GPP TS32.213), and RB offset is the frequency offset in RBs between two frequency hops.

[0017] PUSCH repetition type B supports inter-repetition frequency hopping and inter-slot frequency hopping. Inter-repetition frequency hopping is performed for every nominal repetition. For inter-repetition frequency hopping, the starting resource block (RB) of the actual repetition within the nth nominal repetition (defined in 3GPP TS32.213 clause 6.1.2.1) is given by: TIFF0007774718000003.tif14158

[0018] Here, RB start is the starting RB in the UL BWP calculated from the resource block allocation information of resource allocation type 1 (described in section 6.1.2.2 of 3GPP TS32.213), and RB offset is the frequency offset in RBs between two frequency hops.

[0019] 3GPP TS38.331 V16.1.0 discloses: ***Beginning of excerpt from 3GPP TS38.331*** PUSCH-Config information element PUSCH-Config ::= SEQUENCE { frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need M frequencyHoppingForDCI-Format0-2-r16 CHOICE { pusch-RepTypeA ENUMERATED {intraSlot, interSlot}, pusch-RepTypeB ENUMERATED {interRepetition, interSlot} } OPTIONAL, -- Need S frequencyHoppingOffsetListsForDCI-Format0-2-r16 SetupRelease { FrequencyHoppingOffsetListsForDCI-Format0-2-r16} OPTIONAL, -- Need M frequencyHoppingForDCI-Format0-1-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB } FrequencyHoppingOffsetListsForDCI-Format0-2-r16 ::= SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1) frequency hopping The intraSlot value enables "intra-slot frequency hopping", the interSlot value enables "inter-slot frequency hopping". If this field is absent, no frequency hopping is configured for "pusch-RepTypeA" (see TS 38.214

[19] , clause 6.3). The field frequencyHopping applies to DCI formats 0_0 and 0_1 for "pusch-RepTypeA". frequencyHoppingForDCI-Format0-1 If pusch-RepTypeIndicatorForDCI-Format0-1 is set to "pusch-RepTypeB", it indicates the frequency hopping method for DCI format 0_1. The value interRepetition enables "inter-repetition frequency hopping" and the value interSlot enables "inter-slot frequency hopping". If this field is absent, frequency hopping is not configured in DCI format 0_1 ​​(see TS38.214

[19] , section 6.1). frequencyHoppingForDCI-Format0-2 Indicates the frequency hopping method for DCI format 0_2. The value intraSlot enables "intra-slot frequency hopping", the value interRepetition enables "inter-slot frequency hopping", and the value interSlot enables "inter-slot frequency hopping". If pusch-RepTypeIndicatorForDCI-format 0-2 is set to "pusch-RepTypeA", the frequency hopping method can be selected between "intra-slot frequency hopping" and "inter-slot frequency hopping", if enabled. If pusch-RepTypeIndicatorForDCI-format 0-2 is set to "pusch-RepTypeB", the frequency hopping method can be selected between "repetition inter-slot frequency hopping" and "inter-slot frequency hopping", if enabled. If this field is absent, no frequency hopping is configured for DCI format 0_2 with "pusch-RepTypeB" (see TS38.214

[19] , clause 6.3). frequencyHoppingOffsetLists, frequencyHoppingOffsetListsForDCI-Format0-2 The set of frequency hopping offsets to be used if frequency hopping is enabled for allowed transmissions (not msg3) and configured grant activation of type 2 (see TS38.214

[19] , clause 6.3). The field frequencyHoppingOffsetLists applies to DCI format 0_0 and DCI format 0_1, and the field frequencyHoppingOffsetListsForDCI-Format 0-2 applies to DCI format 0_2 (see TS38.214

[19] , clause 6.3). ConfiguredGrantConfig information element -- ASN1START -- TAG-CONFIGUREDGRANTCONFIG-START ConfiguredGrantConfig ::= SEQUENCE { frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S rrc-ConfiguredUplinkGrant SEQUENCE { timeDomainOffset INTEGER (0..5119), timeDomainAllocation INTEGER (0..15), frequencyDomainAllocation BIT STRING (SIZE(18)), antennaPort INTEGER (0..31), dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need R precodingAndNumberOfLayers INTEGER (0..63), srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need R mcsAndTBS INTEGER (0..31), frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need R pathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1), ..., [[ pusch-RepTypeIndicator-r16 ENUMERATED {pusch-RepTypeA,pusch-RepTypeB} OPTIONAL, -- Need M frequencyHoppingPUSCH-RepTypeB-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB timeReferenceSFN-r16 ENUMERATED {sfn512} OPTIONAL -- Need S ]] frequency hopping The intraSlot value enables "intra-slot frequency hopping", and the interSlot value enables "inter-slot frequency hopping". If this field is absent, no frequency hopping is configured. The field frequencyHopping applies to grants configured for "pusch-RepTypeA" (see TS38.214

[19] , section 6.3.1). frequencyHoppingOffset The frequency hopping offset used when frequency hopping is enabled (see TS38.214

[19] , clauses 6.1.2 and 6.3). frequencyHoppingPUSCH-RepTypeB Indicates the frequency hopping method for Type 1 CG when pusch-RepTypeIndicator is set to "pusch-RepTypeB" (see TS38.214

[19] , section 6.1). The value interRepetition enables "inter-repetition frequency hopping", and the value interSlot enables "inter-slot frequency hopping". If this field is absent, frequency hopping is not enabled for Type 1 CG. PUCCH-Config information element PUCCH-FormatConfig ::= SEQUENCE { interslotFrequencyHopping ENUMERATED {enabled} OPTIONAL, -- Need R additionalDMRS ENUMERATED {true} OPTIONAL, -- Need R maxCodeRate PUCCH-MaxCodeRate OPTIONAL, -- Need R nrofSlots ENUMERATED {n2,n4,n8} OPTIONAL, -- Need S pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need R simultaneousHARQ-ACK-CSI ENUMERATED {true} OPTIONAL -- Need R } PUCCH-Resource ::= SEQUENCE { pucch-ResourceId PUCCH-ResourceId, startingPRB PRB-Id, intraSlotFrequencyHopping ENUMERATED { enabled} OPTIONAL, -- Need R secondHopPRB PRB-Id OPTIONAL, -- Need R format CHOICE { format0 PUCCH-format0, format1 PUCCH-format1, format2 PUCCH-format2, format3 PUCCH-format3, format4 PUCCH-format4 } } Description of PUCCH-Format Config field interslotFrequencyHopping If this field is present, the UE enables inter-slot frequency hopping when PUCCH format 1, 3, or 4 is repeated across multiple slots. For long PUCCHs spanning multiple slots, the UE cannot simultaneously enable intra-slot and inter-slot frequency hopping. See clause 9.2.6 of TS38.213

[13] . PUCCH-Resource and PUCCH-ResourceExt field descriptions intraSlotFrequencyHopping Enabling intra-slot frequency hopping applies to all types of PUCCH formats. For long PUCCHs spanning multiple slots, intra-slot and inter-slot frequency hopping cannot be enabled at the same time in a UE. See clause 9.2.1 of TS38.213

[13] . ***END OF EXCERPT FROM 3GPP TS38.331***

[0020] Also, 3GPP 38.212 V16.1.0 discloses the following in format 0_0: ***Beginning of excerpt from 3GPP TS38.212*** Frequency domain resource allocation - if neither the higher layer parameters useInterlacePUSCH-Common nor userInterlacePUSCH-Dedicated are configured, TIFF0007774718000004.tif1167 bits, where N RB UL,BWP is defined in section 7.3.1.0. For PUSCH hopping with resource allocation type 1: N UL_hop The MSB bits are used to indicate the frequency offset according to clause 6.3 of [6,TS38.214], where N is the number of MSB bits if the higher layer parameter frequencyHoppingOffsetLists contains two offset values. UL_hop= 1, if the upper layer parameter frequencyHoppingOffsetLists contains four offset values, then N UL_hop =2. · TIFF0007774718000005.tif1184 bits provide frequency domain resource allocation according to clause 6.1.2.2.2 of [6,TS38.214]. Frequency Hopping Flag - 1 bit according to Table 7.3.1.1.1-3 defined in clause 6.3 of [6, TS38.214]. ***END OF EXCERPT FROM 3GPP TS38.212***

[0021] Additionally, 3GPP 38.212 V16.1.0 discloses Format 0_1 ​​and Format 0_2: ***Beginning of excerpt from 3GPP TS38.212*** Frequency domain resource allocation - number of bits determined by N RB UL,BWP The size of the active UL bandwidth portion: ·When the upper layer parameter useInterlacePUSCH-Dedicated·r16 is not set For resource allocation type 1, TIFF0007774718000006.tifThe 1167 LSBs provide resource allocation as follows: For PUSCH hopping with resource allocation type 1: N UL_hop The MSB bits are used to indicate the frequency offset according to clause 6.3 of [6,TS38.214], where N is the number of MSB bits if the higher layer parameter frequencyHoppingOffsetLists contains two offset values. UL_hop = 1, if the upper layer parameter frequencyHoppingOffsetLists contains four offset values, then N UL_hop =2. · The TIFF0007774718000007.tif1184 bits provide frequency domain resource allocation according to clause 6.1.2.2.2 of [6,TS38.214]. For non-PUSCH hopping with resource allocation type 1: · The TIFF0007774718000008.tif1167 bits provide frequency domain resource allocation according to clause 6.1.2.2.2 of [6,TS38.214]. Frequency Hopping Flag - 0 or 1 bit: -0 bit if only resource allocation type 0 is set, or if the upper layer parameter frequencyHopping is not set and the upper layer parameter pusch-RepTypeIndicatorForDCI-format0-1-r16 is not set to pusch-RepTypeB, or if the upper layer parameter frequencyHoppingForDCI-format0-1-r16 is not set and pusch-RepTypeIndicatorForDCI-format0-1-r16 is set to pusch-RepTypeB, or if only resource allocation type 2 is set; -1 bit according to Table 7.3.1.1.1-3, otherwise applies only to resource allocation type 1 as defined in clause 6.3 of [6,TS38.214]. TIFF0007774718000009.tif33158***END EXCERPT FROM 3GPP TS38.212***

[0022] IV. Time-Domain Windows for Joint Channel Estimation 3GPP has agreed to specify a "time-domain window" for joint channel estimation. This window is used to determine the amount of time a user equipment unit (UE) needs to maintain power consistency and phase continuity across multiple transmissions on a physical channel. The window is characterized by a maximum duration, and whether the maximum duration is reported by the UE as a UE capability is under discussion at the time of writing. As will be further discussed below, if transmissions occupy different PRBs, as can occur in frequency-hopping channels, the UE may not need to maintain phase continuity and power consistency of transmissions across slots. Therefore, the implications for frequency hopping when a network employs joint channel estimation and the UE is configured to bundle demodulation reference signals (DMRS) across slots are currently under discussion. Some agreements regarding joint channel estimation include: ***Initiation of Agreement*** agreement: For joint channel estimation, a time domain window is defined in which the UE is expected to maintain power consistency and phase continuity between PUSCH transmissions that comply with the power consistency and phase continuity requirements. Specify . How the FFS time domain window is determined (e.g., explicitly configured and / or implicitly derived) and whether the time domain window can be enabled / disabled. FFS Time domain window units (e.g., repetitions, slots, and / or symbols). FFS: Potential use cases and their relevance to time window units FFS: Single or multiple time domain windows FFS: Relationship with UE capabilities · FFS: Whether the term "time domain window" is used in the specification or replaced by other technical terms. ·Whether to further explore the impact on FFS timing advance. agreement: · Maximum duration definition: The maximum duration for which the UE can maintain power consistency and phase continuity according to the power consistency and phase continuity requirements. ·FFS Whether such a definition is necessary in the RAN1 specification. Note: It is up to RAN4 to specify such a definition in the RAN4 specification. · FFS maximum duration may be reported by the UE. NOTE: For the UE, the maximum duration is understood to be equal to or greater than the duration of the time domain window. agreement: Inter-slot frequency hopping with inter-slot bundling has two options: Option 1: The bundle size (time domain hopping interval) is equal to the time domain window size. Option 2: The bundle size (time domain hopping interval) can be different from the time domain window size. FFS: Whether the bundle size (hopping interval in the time domain) is explicitly set or implicitly determined. FFS: Whether the bundle size (hopping interval in the time domain) is defined separately for FDD and TDD. FFS: Relationship between bundle size (hopping interval in the time domain) and window size in the time domain agreement: Joint channel estimation for PUSCH transmission is enabled or disabled by the UE's RRC configuration · FFS: Whether additional dynamic signaling is required to enable / disable joint channel estimation for PUSCH transmissions. Note: Enabling such functionality requires certain prerequisites. FFS RRC parameter details (including explicit and implicit configuration) · In joint channel estimation for FFS PUSCH, time domain windowing is not explicitly enabled or disabled separately from joint channel estimation. Note: Enabling / disabling joint channel estimation for PUSCH transmission means enabling / disabling DMRS bundling for PUSCH transmission under the conditions of power consistency and phase continuity. ***Termination of Agreement***

[0023] V. PUSCH Repetition and Transport Block over Multiple Slots (TBoMS) PUSCH Repetition in VANR Release 15 Slot aggregation for PUSCH was supported in Release 15 and was renamed to PUSCH repetition type A in Release 16. The name PUSCH repetition type A is also used for a single repetition, i.e., no slot aggregation. In Release 15, no PUSCH transmissions overlapping with DL symbols are sent.

[0024] For example, the Release 15 document (3GPP TSG RAN WG1 #AH_1801 Final Report V1.0.0, 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, February 26-March 2, 2018) discloses the following: Comparison of multi-slot transmission (PDSCH / PUSCH) with DCI and semi-static DL / UL allocation If the semi-static DL / UL allocation configuration of a slot does not conflict in direction with the scheduled PDSCH / PUSCH allocation symbols, the PDSCH / PUSCH of that slot is received / transmitted. If the semi-static DL / UL allocation configuration of a slot collides in direction with the scheduled PDSCH / PUSCH allocated symbols, the PDSCH / PUSCH transmission in that slot will not be received / transmitted, i.e., the effective repetition count will be reduced.

[0025] In other words, in Release 15, the number of repetitions is semi-statically configured by the RRC parameter pusch-AggregationFactor. A maximum of 8 repetitions is supported, as shown below: pusch-AggregationFactor ENUMERATED { n2, n4, n8}

[0026] PUSCH repetition in VBNR Release 16 Release 16 supports a new repetition format, PUSCH repetition type B, which allows back-to-back repetition of PUSCH transmissions. The biggest difference between type B and type A is that type A only allows one repetition per slot, and each repetition occupies the same symbol. Using this format when the PUSCH length is shorter than 14 will result in gaps between repetitions, increasing overall latency. Another change from Release 15 is the way the number of repetitions is signaled. In Release 15, the number of repetitions is configured semi-statically, but in Release 16, the number of repetitions can be dynamically indicated in the DCI. This applies to both dynamic grants and type 2 configured grants.

[0027] PUSCH repetition based on available slots in VC Release 17 In the 3GPP Release 17 NR Coverage Enhancement Work Item, two options for enhancing PUSCH repetition type A were agreed upon. The first option increases the maximum number of repetitions to a number to be determined during the work. The second option counts the number of repetitions based on the available uplink slots, or equivalently, the available PUSCH slots. While 3GPP is still debating how to identify available slots for PUSCH repetition type A, it is agreed that a slot will be determined unavailable if at least one of the symbols indicated by TDRA for PUSCH within the slot overlaps with a symbol not intended for UL transmission.

[0028] VDTBoMS transmission In NR Release 15 / 16, one UL TB is limited to UL symbols within a slot. To support higher data rates, multiple PRBs within a slot can be used to transmit large TBs, and the multiple PRBs share the UE's transmit power. Multi-slot transport block (TB) processing (TBoMS) has been proposed as a candidate solution for PUSCH coverage extension and is specified in NR Release 17. TBoMS extends the time-domain resources for transmitting TBs across slot boundaries, increasing the total power of TB transmissions compared to TB transmissions in a single slot. TBoMS also reduces CRC overhead by reducing the number of CRCs in a given number of slots compared to PUSCH transmissions at the same data rate using separate TBs. TBoMS is partially based on PUSCH repetition type A in that the same number of OFDM symbols are occupied per slot, and the slot in which the UE transmits TBoMS is identified as an available slot. Summary of the Invention

[0029] Disclosed herein are systems and methods for improving frequency hopping schemes compatible with joint channel estimation. In one embodiment, a method implemented in a user equipment (UE) transmitting a physical channel on different frequency domain resources over time includes determining a value of a hopping index for a first set of N consecutive slots, where N is an integer greater than 1. The method further includes incrementing the value of the hopping index for a second set of N consecutive slots after the N consecutive slots. The method further includes resetting the value of the hopping index to zero if the hopping index exceeds a maximum value. The method further includes, for an uplink slot within the second set of N consecutive slots in which a physical uplink channel is transmitted, determining a set of physical resource blocks (PRBs) for transmitting a physical channel from a set of frequency offsets according to the value of the hopping index for the second set of N consecutive slots, and transmitting the physical uplink channel on the selected set of PRBs in the uplink slot.

[0030] In one embodiment, the first set of N consecutive slots includes both downlink and uplink slots.

[0031] In one embodiment, the value of the hopping index is a function of the physical slot number. In another embodiment, the value of the hopping index is a function of: TIFF0007774718000010.tif9158, where n hop is the hopping index, and n s,f μis the physical slot number of the slot to which the hopping index applies, N is the number of consecutive slots to which the hopping index applies, and L-1 is the maximum value of the hopping index, the hopping index being a value in the range from 0 to L-1 inclusive. In one embodiment, the value of the hopping index is further a function of a defined or configured offset.

[0032] In one embodiment, the value of the hopping index is: TIFF0007774718000011.tif9158, where n hop is the hopping index, and n s,f μ is the physical slot number of the slot to which the hopping index is applied, and n off is a defined or configured offset, N is the number of consecutive slots to which the hopping index applies, L-1 is the maximum value of the hopping index, and the hopping index is a value in the range from 0 to L-1 inclusive.

[0033] In one embodiment, the hopping index changes once every N consecutive time slots, the N consecutive time slots including both downlink and uplink slots, and the offset reaches one of L values ​​corresponding to L possible offsets.

[0034] In one embodiment, the offset is configured for each slot of a set of N slots, where N is an integer sub-multiple of a predetermined number of slots. In one embodiment, the predetermined number of slots is a number of slots within a radio frame or a number of slots within a predetermined number of radio frames.

[0035] In one embodiment, the offset is a function of the value of the hopping index.

[0036] In one embodiment, the offset is a predetermined number of PRBs times the value of the hopping index.

[0037] In one embodiment, N has a value that is a fractional multiple of the number of slots in a configured time division duplex (TDD) uplink-downlink pattern.

[0038] In one embodiment, the UE indicates its capability for a frequency hopping pattern configured for each slot of a plurality of slots indicated to the UE, regardless of whether the UE indicates its ability to maintain phase continuity between uplink transmissions in different slots.

[0039] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE for transmitting a physical channel on different frequency domain resources over time is adapted to determine a value of a hopping index for a first set of N consecutive slots, where N is an integer greater than 1. The UE is further adapted to increment the value of the hopping index for a second set of N consecutive slots after the N consecutive slots. The UE is further adapted to reset the value of the hopping index to zero if the hopping index exceeds a maximum value. The UE is further adapted, for an uplink slot in the second set of N consecutive slots in which a physical uplink channel is transmitted, to: determine a set of physical resource blocks (PRBs) for transmitting a physical channel from a set of frequency offsets according to the value of the hopping index for the second set of N consecutive slots; and transmit the physical uplink channel on the selected set of PRBs in the uplink slot.

[0040] In one embodiment, a UE for transmitting a physical channel on different frequency domain resources over time comprises one or more transmitters, one or more receivers, and a processing circuit associated with the one or more transmitters and the one or more receivers. The processing circuit is configured to cause the UE to determine a value of a hopping index for a first set of N consecutive slots, where N is an integer greater than 1. The processing circuit is further configured to cause the UE to increment the value of the hopping index for a second set of N consecutive slots after the N consecutive slots. The processing circuit is further configured to cause the UE to reset the value of the hopping index to zero if the hopping index exceeds a maximum value. The processing circuit is further configured to, for an uplink slot within the second set of N consecutive slots in which a physical uplink channel is transmitted, determine a set of physical resource blocks (PRBs) for transmitting a physical channel from a set of frequency offsets according to the value of the hopping index for the second set of N consecutive slots, and transmit the physical uplink channel on the selected set of PRBs in the uplink slot.

[0041] In another embodiment, a method in a UE transmitting physical channels on different frequency domain resources over time includes receiving signaling to configure the UE with multiple time domain windows used for demodulation reference signal (DMRS) bundling, and restarting a frequency hopping pattern at the start of each of the multiple time domain windows used for DMRS bundling.

[0042] In one embodiment, resuming a frequency hopping pattern at the start of each of the plurality of time domain windows used for DMRS bundling includes transmitting, in a first configured time domain window of the plurality of time domain windows used for DMRS bundling, an uplink physical channel having a frequency hopping offset defined by the frequency hopping pattern, and transmitting, in a second configured time domain window of the plurality of time domain windows used for DMRS bundling, an uplink physical channel having a frequency hopping offset defined by the frequency hopping pattern that is resumed at the start of the second configured time domain window.

[0043] In one embodiment, a method in a UE for identifying a capability for DMRS bundling includes reporting the UE capability for DMRS bundling according to a combination of parameters, the combination of parameters including two or more of a maximum amount of maximum window length in time, a measurement of phase error, and a maximum number of repetitions of a physical uplink shared channel (PUSCH). [Brief explanation of the drawings]

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

[0045] [Figure 1] An example of a New Radio (NR) time division duplex (TDD) pattern is shown below.

[0046] [Figure 2A] 1 illustrates an example of a cellular communication system according to some embodiments of the present disclosure.

[0047] [Figure 2B] 1 is a flowchart illustrating the operation of a user equipment (UE) in accordance with some embodiments of the present disclosure.

[0048] [Figure 3] An example of an extended hopping pattern derived from a slot number is shown below.

[0049] [Figure 4] 10 shows an example of an extended hopping pattern derived from a slot number offset.

[0050] [Figure 5A] FIG. 2 illustrates a first method performed by a UE in accordance with some embodiments of the present disclosure.

[0051] [Figure 5B] FIG. 10 illustrates a method performed by a UE according to another embodiment of the present disclosure.

[0052] [Figure 6] A comparison of configurable hopping patterns and their alternatives is presented.

[0053] [Figure 7A] 10 illustrates a second method performed by a UE in accordance with some embodiments of the present disclosure. [Figure 7B] 10 illustrates a second method performed by a UE in accordance with some embodiments of the present disclosure.

[0054] [Figure 8] 1 is a schematic block diagram of a radio access node according to some embodiments of the present disclosure.

[0055] [Figure 9] 9 is a schematic block diagram illustrating a virtualized embodiment of the radio access node of FIG. 8 in accordance with some embodiments of the present disclosure.

[0056] [Figure 10] 9 is a schematic block diagram of the radio access node of FIG. 8 according to some other embodiments of the present disclosure.

[0057] [Figure 11] 1 is a schematic block diagram of a UE according to some embodiments of the present disclosure.

[0058] [Figure 12] FIG. 12 is a schematic block diagram of the UE of FIG. 11 in accordance with some other embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0059] The embodiments described below represent information to enable those skilled in the art to practice the embodiments and illustrate the best modes for practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the present disclosure and will recognize applications of these concepts not specifically addressed herein. It is understood that these concepts and applications are within the scope of the present disclosure.

[0060] Wireless Node: As used herein, a "wireless node" is either a wireless access node or a wireless communication device.

[0061] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to transmit and / or receive signals wirelessly. Examples of radio access nodes include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a 3rd Generation Partnership Project (3GPP) fifth-generation (5G) NR network, or an enhanced or evolved Node B (eNB) in a 3GPP long-term evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a Home eNB, etc.), a relay node, a network node implementing some of the functionality of a base station, or a network node implementing a gNB distributed unit (gNB-DU), or a network node implementing some of the functionality of another type of radio access node, etc.

[0062] Core Network Node: As used herein, "core network node" refers to any type of node in a core network or any node that implements a core network function. Some examples of core network nodes include, for example, a Mobile Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), etc. Other examples of core network nodes include nodes that implement an Access Mobility Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc.

[0063] Communications Device: As used herein, a "communications device" refers to any type of device that can access an access network. Examples of communications devices include, but are not limited to, a mobile phone, a smartphone, a sensor device, a meter, a vehicle, a home appliance, a medical appliance, a media player, a camera, or any type of consumer electronic device, such as a television, a radio, a lighting fixture, a tablet computer, a laptop, a personal computer (PC), etc. A communications device may be a portable, handheld, computer-based, or vehicle-mounted mobile device capable of communicating voice and / or data via wireless or wired connections.

[0064] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that accesses (i.e., receives service from) a wireless network (e.g., a cellular network). Examples of wireless communication devices include, but are not limited to, user equipment devices (UEs) in 3GPP networks, machine-type communication (MTC) devices, Internet of Things (IoT) devices, etc. Such wireless communication devices may be, or may be integrated into, mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting fixtures, tablet computers, laptops, PCs, etc. Wireless communication devices may be portable, handheld, computer-embedded, or vehicle-mounted mobile devices capable of communicating voice and / or data over a wireless connection.

[0065] Network Node: As used herein, a "network node" refers to a node that is part of the RAN or core network of a cellular communications network / system.

[0066] It should be noted that this specification will focus on 3GPP cellular communication systems and therefore 3GPP terminology or terminology similar to 3GPP terminology will often be used, however the concepts disclosed herein are not limited to 3GPP systems.

[0067] In the description herein, reference may be made to the term "cell", however, it is important to note that, particularly with regard to 5G NR concepts, beams may be used instead of cells, and therefore the concepts described herein are equally applicable to both cells and beams.

[0068] Disclosed herein are systems and methods for improving frequency hopping schemes compatible with joint channel estimation in both time division duplex (TDD) and frequency division duplex (FDD) operations. In one embodiment, a method implemented in a user equipment (UE) transmitting physical channels on different frequency domain resources over time includes determining values ​​of a hopping index for N consecutive slots, where N is an integer greater than 1, and the N consecutive slots include both downlink and uplink slots. The method also includes determining a hopping index value for each of the N consecutive slots. ,before and resetting the value of the hopping index to zero if the hopping index exceeds a maximum value. The method also includes determining a set of PRBs for transmitting a physical channel from a set of frequency offsets according to the value of the hopping index, and transmitting the physical uplink channel on the selected set of PRBs in a slot. In this way, PRBs can be efficiently used for frequency hopping operations, enabling spatially efficient operation of the network node and UE while avoiding increasing interference received by the network node.

[0069] In one embodiment, the method further includes receiving an indication of a hopping index offset O and shifting the hopping index by O slots such that the value of the hopping sequence at slot n occurs O slots earlier or later than when O=0.

[0070] In one embodiment, the method further includes at least one of (a) resetting the hopping index to an initial value in response to receiving an instruction to reset the frequency hopping pattern, and (b) selecting one of the first frequency hopping pattern or the second frequency hopping pattern configured for the UE in response to receiving an instruction to select a pattern.

[0071] In one embodiment, the method further includes receiving signaling identifying a pattern of uplink and downlink slots, the pattern repeating every M slots, and receiving signaling identifying N, where N is constrained such that M / N is an integer.

[0072] In one embodiment, the method further includes receiving an allocation of PRBs, and performing at least one of: (a) receiving signaling identifying a set of frequency offsets, selecting an offset from the set according to a hopping index, and determining the set of PRBs by shifting the allocation of PRBs in the frequency domain by the offset; (b) calculating an offset of the set of offsets in the frequency domain by multiplying the hopping index by a predetermined PRB number; and (c) determining the set of PRBs by shifting the allocation of PRBs in the frequency domain by the calculated offset.

[0073] In one embodiment, a method implemented in a UE transmitting a physical channel on different frequency domain resources over time includes receiving a list of frequency hopping offsets. Each offset in the list corresponds to a slot indicated to the UE as a slot in which the UE can transmit the physical channel. The method further includes selecting a frequency offset according to a number of repeated transmissions of the physical channel, where a first frequency offset is selected for the first transmission of the physical channel and a second offset is selected for the second transmission. For repeated transmissions starting with transmission T at T=P+1 (where P is the number of frequency hopping offsets in the list), the method further includes selecting a first frequency offset for transmission T, selecting a second frequency offset for transmission T+1, and so on. For at least one of the repeated transmissions, the method further includes determining a set of PRBs for transmitting the physical channel from the set of frequency offsets according to the hopping. The method further includes transmitting at least one of the repeated transmissions of the physical channel on the set of PRBs.

[0074] In one embodiment, the method further includes receiving an indication of a hopping index offset O, selecting a frequency hopping offset in the list having index O as a first frequency offset, and selecting a frequency hopping offset in the list having index O+1 as a second frequency offset. For repeated transmissions starting with transmission T+O where T+O=P+1, the method further includes selecting a frequency hopping offset in the list having index O as a first frequency offset for transmission T, selecting a frequency hopping offset in the list having index O+1 as a second frequency offset for transmission T+1, etc.

[0075] In one embodiment, the method further includes at least one of (a) selecting a first frequency offset as a first frequency offset for transmission T′, selecting a second frequency offset as a second frequency offset for transmission T′+1 in response to receiving an instruction to reset the frequency hopping pattern, and (b) selecting one of the first frequency hopping pattern or a second frequency hopping pattern configured in the UE in response to receiving an instruction to select a pattern.

[0076] In one embodiment, the method further includes receiving signaling identifying a pattern of uplink and downlink slots, the pattern repeating every M slots, and the list of frequency hopping offsets being constrained such that M / P is an integer.

[0077] In one embodiment, the method further includes transmitting a physical channel according to a first element of the frequency hopping pattern in a first slot of each of one or more time domain windows used for demodulation reference signal (DMRS) bundling.

[0078] In one embodiment, a UE indicates its transmit capability regardless of whether the UE indicates its ability to maintain phase continuity between uplink transmissions in different slots.

[0079] In one embodiment, in the UE for identifying a capability for DMRS bundling, the method further includes reporting the UE capability for DMRS bundling according to a combination of parameters including two or more of a maximum amount of a maximum window length in units of time (e.g., slots, symbols, or seconds), a measure of phase error, or a maximum number of repetitions of a physical uplink shared channel (PUSCH).

[0080] Corresponding embodiments of a UE are also disclosed. In one embodiment, the UE is adapted to (a) determine a value of a hopping index for N consecutive slots, where N is an integer greater than 1, and the N consecutive slots include both downlink and uplink slots, (b) increment the hopping index after the N consecutive slots, (c) reset the hopping index to zero if the hopping index exceeds a maximum value, (d) determine a set of PRBs for transmitting a physical channel from a set of frequency offsets according to the hopping index, and (e) transmit the physical channel on the selected set of PRBs in the slot.

[0081] In one embodiment, a UE comprises one or more transmitters, one or more receivers, and processing circuitry associated with the one or more transmitters and the one or more receivers, wherein the processing circuitry is configured to: (a) determine values ​​of a hopping index for N consecutive slots, where N is an integer greater than 1, and the N consecutive slots include both downlink and uplink slots; (b) increment the hopping index after the N consecutive slots; (c) reset the hopping index to zero if the hopping index exceeds a maximum value; (d) determine a set of PRBs for transmitting a physical channel from a set of frequency offsets according to the hopping index; and (e) transmit the physical channel in the slot on the selected set of PRBs.

[0082] In one embodiment, the UE is adapted to (a) receive a list of frequency hopping offsets, each offset in the list corresponding to a slot indicated to the UE as one in which the UE can transmit a physical channel; (b) select a frequency offset according to the number of repeated transmissions of the physical channel, wherein a first frequency offset is selected for the first transmission of the physical channel and a second offset is selected for the second transmission; (c) for repeated transmissions starting from transmission T, T=P+1, where P is the number of frequency hopping offsets in the list, selecting the first frequency offset for transmission T, the second frequency offset for transmission T+1, etc.; (d) for at least one of the repeated transmissions, determine a set of PRBs for transmitting the physical channel from the set of frequency offsets according to the hopping index; and (e) transmit at least one of the repeated transmissions of the physical channel in the set of PRBs.

[0083] In one embodiment, a UE comprises one or more transmitters, one or more receivers, and processing circuitry associated with the one or more transmitters and one or more receivers. The processing circuitry is configured to: (a) cause the UE to receive a list of frequency hopping offsets, each offset in the list corresponding to a slot indicated to the UE as one in which the UE can transmit a physical channel; (b) cause the UE to select a frequency offset according to a number of repeated transmissions of the physical channel, a first frequency offset being selected for the first transmission of the physical channel and a second offset being selected for the second transmission; (c) for repeated transmissions starting with transmission T, T=P+1, where P is the number of frequency hopping offsets in the list, selecting the first frequency offset for transmission T, the second frequency offset for transmission T+1, etc.; (d) for at least one of the repeated transmissions, determine a set of PRBs for transmitting the physical channel from the set of frequency offsets according to a hopping index; and (e) cause the UE to transmit at least one of the repeated transmissions of the physical channel on the set of PRBs.

[0084] 2A illustrates an example of a cellular communication system 200 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communication system 200 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes base stations 202-1 and 202-2, which in 5GS include NR base stations (gNBs) and optionally Next Generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to 5GC) that control corresponding (macro) cells 204-1 and 204-2. Base stations 202-1 and 202-2 are generally referred to herein collectively as base stations 202 and individually as base stations 202. Similarly, (macro) cells 204-1 and 204-2 are generally referred to herein collectively as (macro) cells 204 and individually as (macro) cells 204. The RAN may also include a number of low-power nodes 206-1 through 206-4 that control corresponding small cells 208-1 through 208-4. The low-power nodes 206-1 through 206-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs), etc. Notably, although not shown, one or more of the small cells 208-1 through 208-4 may alternatively be provided by the base station 202. The low-power nodes 206-1 through 206-4 are generally referred to herein collectively as low-power nodes 206 and individually as low-power nodes 206. Similarly, the small cells 208-1 through 208-4 are generally referred to herein collectively as small cells 208 and individually as small cells 208. The cellular communication system 200 also includes a core network 210, which is referred to as 5GC in a 5G system (5GS). The base station 202 (and optionally the low power node 206 ) is connected to a core network 210 .

[0085] Base station 202 and low power node 206 serve wireless communication devices 212-1 through 212-5 within corresponding cells 204 and 208. Wireless communication devices 212-1 through 212-5 are generally referred to herein collectively as wireless communication devices 212 and individually as wireless communication devices 212. In the following description, wireless communication devices 212 are often UEs, although the disclosure is not limited thereto.

[0086] Before describing embodiments of the present disclosure, it is useful to briefly discuss the problems with existing frequency hopping solutions. The frequency hopping patterns currently defined in 3GPP NR Release 15 and Release 16 are incompatible with maintaining phase continuity and power consistency required for joint channel estimation. The current frequency hopping patterns change the resource blocks (RBs) occupied by the Physical Uplink Shared Channel (PUSCH) depending on the slot number. It is assumed that this interferes with the phase continuity and power consistency between adjacent slots. Therefore, frequency hopping extensions to maintain phase continuity and power consistency will be specified in the NR Coverage Extension Work Item in Release 17.

[0087] For example, 3GPP document R1-2107604 proposes a simple approach, such as increasing the number of adjacent PUSCH transmissions occupying a given physical resource block (PRB). However, such approaches do not address issues such as how to allow more flexible frequency hopping patterns that provide better diversity and better joint channel estimation performance when the number of adjacent PUSCH slots varies in a time division duplex (TDD) pattern, or a general frequency hopping pattern that can be used with or without joint channel estimation. Because frequency hopping operation is typically configured for a large number of UEs in a cell, it is important to control signaling overhead, especially downlink control information (DCI) signaling, to enable efficient spectrum sharing. Efficient methods for signaling frequency hopping patterns for radio resource control (RRC) that are compatible with joint channel estimation have also not yet been fully addressed in 3GPP discussions, as fundamental aspects of joint channel estimation have yet to be defined.

[0088] The implementation of joint channel estimation in a UE is still under study in 3GPP, and the combination of parameters that define the UE's capability for joint channel estimation is not yet understood. In embodiments herein, implementation may be more challenging or require more effort depending on the amount of maximum phase error the UE is required to have across slots and how the maximum phase error requirement can be combined with other parameters, such as the maximum period for which the UE maintains phase continuity and power consistency. do There are cases where this happens.

[0089] Systems and methods are disclosed herein that address the aforementioned and / or other challenges. The present disclosure describes methods for configuring frequency hopping such that it functions efficiently, taking into account aspects such as UE capabilities for TDD patterns and demodulation reference signal (DMRS) bundling (maintaining coherence across multiple slots for joint channel estimation).

[0090] Some embodiments of the present disclosure include (a) creating, signaling, and applying an appropriate frequency hopping pattern that (i) assigns the same hop frequency index across multiple consecutive slots and (ii) varies the hopping frequency based on radio frame timing; (b) handling UEs that do not support DMRS bundling; and (c) defining UE capabilities according to different amounts of phase error tolerance depending on the duration of the time domain window used for DMRS bundling and / or the maximum number of PUSCH repetitions.

[0091] The present disclosure provides enhanced frequency hopping patterns that are compatible with joint channel estimation in both TDD and frequency division duplex (FDD) operation, may be signaled with low DCI and low RRC overhead, may be used when all UEs in a cell are not configured for joint channel estimation, and may improve performance even when joint channel estimation is not configured.

[0092] This disclosure allows for defining the capabilities of joint channel estimation according to different amounts of maximum phase error tolerated during operation, which can better suit UE implementation, improve cost / performance tradeoffs in UE design, and better define UE operating limitations.

[0093] Time-Domain Windows for Joint Channel Estimation At the 3GPP RAN1 #106-e meeting, the following working assumptions were presented in the document (RAN1 Chair's Note, 3GPP TSG RAN WG1 #106-e, August 16-27, 2021) regarding the definition of time windows to support joint channel estimation. ***Begin excerpt from RAN1 Chair's Notes*** Work assumptions: For joint channel estimation with PUSCH repetition type A for PUSCH repetitions of the same TB, Every iteration is covered by one or more contiguous / non-contiguous configuration TDWs. · Each configured TDW consists of one or more consecutive physical slots. The window length L of a configured TDW can be explicitly set with a single value (deleted from here), where L is no longer than the maximum duration (deleted to here). · The maximum value of FFS:L is the duration of all iterations (deleted from here). (deleted to here) · We will consider solutions to the problem of error propagation when FFS:L is longer than the maximum duration. · FFS: The window length L is set for each BWP of the UL. The start of the initially configured TDW is the first PUSCH transmission FFS: First available slot / symbol or first physical slot / symbol for first PUSCH transmission. The start of other configured TDWs can be implicitly determined before the first iteration. · FFS: The set TDW is the pair spectrum / SUL band are consecutive. · FFS: The start of the configured TDW for unpaired spectrum is implicitly determined based on a semi-static DL / UL configuration. The end of the last configured TDW is the end of the last PUSCH transmission. FFS: The end of the configured TDW is the last available slot / symbol or the last physical slot / symbol for the last PUSCH transmission. Within one configured TDW, one or more actual TDWs can be implicitly determined: The start of the first actual TDW is the first PUSCH transmission within the configured TDW. FFS: First available slot / symbol or first physical slot / symbol for first PUSCH transmission. Once the actual TDW is started, the UE is expected to maintain power consistency and phase continuity until one of the following conditions is met, after which the actual TDW is terminated: The actual TDW is reached at the end of the last PUSCH transmission within the configured TDW. FFS: The end of the actual TDW is the last available slot / symbol or the last physical slot / symbol for the last PUSCH transmission. -Events that violate the integrity and phase continuity of the power supply occur. FFS: Events include, for example, DL / UL configurations in unpaired spectrum. Based on DL slot , The actual TDW reaches its maximum duration. These include DL reception / monitoring opportunities in unpaired spectrum, high priority transmissions, frequency hopping, and precoder cycling. FFS: The end of the actual TDW is the last available slot / symbol of PUSCH transmission immediately before the event that breaks power coherence and phase continuity. · If an event violates power coherence and phase continuity, whether a new actual TDW is created depends on the UE's ability to support DMRS bundling resumption. If the UE can restart DM-RS bundling, one new actual TDW is created after the event; FFS: The start of the new actual TDW is the first slot / symbol available for PUSCH transmission after the event. If the UE cannot resume DM-RS bundling, a new actual TDW will not be created until the configured TDW expires. FFS: Resume DMRS bundling Whether the UE functionality applies only to dynamic events NOTE 1: A "configured TDW" is a time domain window whose length can be set to "L" and whose start and end are determined as above. Note 2: "Actual TDW" refers to the time domain window during the entire period during which DM-RS bundling is actually applied. The "Actual TDW" period is always less than or equal to the "Configured TDW" period. NOTE 3: Whether the terms "configured TDW" and "actual TDW" will be revised to other terms and whether such terms will be used in the specification will be further discussed. ***END EXCERPT FROM RAN1 CHAIRMAN'S NOTE***

[0094] In this disclosure, the terms "PUSCH transmission," "PUCCH transmission," or "PUSCH or PUCCH transmission" are merely examples of uplink (UL) transmissions received in a window with joint channel estimation. This disclosure does not exclude other types of UL transmissions within the joint channel estimation time window that may be received on the joint estimation channel. Much of this disclosure may also apply to the downlink (DL) (e.g., Physical Downlink Shared Channel (PDSCH) with the gNB as the transmitter and UE receiver) or sidelink (UE to UE), although these cases are not currently standardized by 3GPP.

[0095] The UE is configured to support joint channel estimation in Release 17, where the gNB (or receiving network node) performs joint channel estimation. Supporting joint channel estimation consists of maintaining phase continuity and / or power consistency between multiple transmissions of a physical channel from the UE, particularly between DMRS transmissions of the physical channel. Thus, in this disclosure, configuring a UE to support joint channel estimation is referred to as configuring the UE to use “DMRS bundling.” Such configuration can be done for a given physical channel independently from other physical channels; for example, a UE can be configured for DMRS bundling for only one of the PUCCH or PUSCH. Similarly, the ability of a UE to support joint channel estimation in a network can be referred to as the ability to support DMRS bundling.

[0096] As seen in the working assumptions above, the time-domain window starts at the first transmission, and the duration of the window covers all repetitions of the physical channel. Generalizing the working assumptions to cover both PUCCH and PUSCH, the start of the first window is where the first PUSCH or PUCCH transmission occurs, and the end of the last window is where the last PUSCH or PUCCH transmission ends. Each window consists of one or more consecutive slots and can be configured with a length L. The UE maintains phase continuity and power consistency until the window ends or the constraints are no longer met. For brevity, in the following, rather than identifying a transmission as PUCCH or PUSCH, "transmission" may refer to "PUCCH transmission" or "PUSCH transmission" unless otherwise noted.

[0097] The window defines a specific region within which phase continuity or power consistency can be maintained (within a certain error tolerance), but other constraints also apply. The UE is not required to maintain phase continuity across various conditions, such as when the transmit power, modulation state, or subcarriers (occupied by the transmission) are changed. The UE must also use the same beam, precoder, or both the same beam and the same precoder throughout the PUSCH transmission, if a beam or precoder is used. Furthermore, the UE is not required to maintain phase continuity and power consistency within a certain range if it turns off its transmit chain, such as during downlink reception. The UE's ability to maintain phase continuity and power consistency on one carrier may also be limited if the UE is scheduled on different carriers. Furthermore, the UE should not adjust its timing advance (TA) during the time-domain window. For brevity, the phase continuity and power consistency constraints are referred to as "continuity constraints," and phase continuity and power consistency within a certain range are generally referred to as "continuity."

[0098] If fewer PUSCH repetitions are transmitted, a larger amount of phase continuity error accumulated over the PUSCH repetitions may be tolerated. Phase continuity error measurements may include the root-mean-square (RMS) phase error over a measurement interval (e.g., one or more slots) or the error vector magnitude (EVM). In such cases, the length of the time-domain window may be related to the UE's capability for phase continuity and power consistency within a certain range. Such capabilities may also be associated with specific constraints, such as a condition that only a certain number of repetitions are allowed or another condition that no frequency / time adjustments are made for a certain number of time slots. The UE may report these capabilities in association with different phase continuity ranges. The network may schedule the corresponding number of repetitions within such a window according to the constraints specified by the UE capability report.

[0099] Thus, in some embodiments, a UE's capability for DMRS bundling is defined according to a combination of parameters including two or more of: (a) a maximum amount of maximum window length in time units (e.g., slots, symbols, or seconds); (b) a measure of phase error (which may be characterized by a distortion measure such as RMS phase error or EVM); or (c) a maximum number of repetitions of a PUSCH. In this regard, FIG. 2B is a flowchart illustrating UE operation in accordance with some embodiments of the present disclosure. As shown, the UE reports its capability for DMRS bundling (step 220) according to a combination of parameters including two or more of: (a) a maximum amount of maximum window length in time units (e.g., slots, symbols, or seconds); (b) a measure of phase error (which may be characterized by a distortion measure such as RMS phase error or EVM); or (c) a maximum number of repetitions of a PUSCH.

[0100] Joint channel estimation and compatible frequency hopping In the 3GPP TSG RAN meeting document (R1-2104151, "3GPP TSG RAN WG1 #104bis-e Final Report" V1.0.0, 3GPP TSG RAN WG1 Meeting #105-e, e-Meeting, May 10-27, 2021), the following was agreed upon: ***BEGIN EXCERPT FROM R1-2104151*** agreement: Inter-slot frequency hopping with inter-slot bundling has two options: Option 1: The bundle size (time domain hopping interval) is equal to the time domain window size. Option 2: The bundle size (time domain hopping interval) can be different from the time domain window size. FFS: Whether the bundle size (hopping interval in the time domain) is explicitly set or implicitly determined. FFS: Whether the bundle size (hopping interval in the time domain) is defined separately for FDD and TDD. FFS: Relationship between bundle size (hopping interval in the time domain) and window size in the time domain ***END EXCERPT FROM R1-2104151***

[0101] Also, 3GPP RAN4 document R4-2103393 states: ***BEGIN EXCERPT FROM R4-2103393*** Ran4 discussed phase continuity and concluded that there are cases where continuity is lost during repetition. Questions from RAN1 and answers from RAN4 Question 1: Under what conditions can a UE maintain phase continuity across PUCCH or PUSCH repetitions? ·Answer to question 1 of RAN4: If the following conditions are met: The modulation order remains the same. (The following is in bold) The RB allocation of length and frequency location should not be changed, and frequency hopping within and between slots is not enabled within the repetition bundle. ·(underlined below) There is no change in the transmission power level of the own CC, i.e., there is no change in the power control parameters specified in TS38.213, and the own CC is not affected by other simultaneous CCs configured for inter-band CA or DC of the same UE with dynamic power sharing, and there are no changes in configured CCs that are part of the configured intra-band uplink CA or DC. (Strikethrough from here) No change in the transmit power level of its own CC, i.e., no change in the power control parameters specified in TS38.213, and no influence of other simultaneous CCs for CA and DC with dynamic power sharing. (Strikethrough to here) UL beam switching for FR2 UE does not occur ***END EXCERPT FROM R4-2103393***

[0102] That is, according to the above description, the requirement for maintaining phase continuity is that "RB allocation in length and frequency location should not be changed, and frequency hopping within and between slots should not be enabled within the repeated bundle." This requirement must be compatible with other requirements for continuity, such as the UE not receiving downlink slots in TDD.

[0103] The hopping pattern in Release 15 changes the occupied RB depending on the slot number as described above. This prevents continuity between adjacent slots, so frequency hopping extensions will be specified in the NR Coverage Extension Work Item in Release 17.

[0104] Considering hopping patterns that meet the continuity requirement for joint channel estimation, it is desirable for all UEs in a cell to follow the same hopping pattern. This allows for efficient use of frequency domain resources, such that when a first UE hops to a given PRB set, the first UE hops to the next PRB set, and then the second UE hops to the PRB occupied by the first UE. This is possible if the hopping pattern has a common timing for all UEs in the cell; for example, the hopping pattern counter is based on a common timing reference, such as radio frame timing. If the hop counter is not based on frame timing, it must be determined based on something else. One possibility is to indicate the hop timing or hop counter in the DCI, but this increases DCI overhead and generally may not be beneficial because all UEs in the cell must use the same timing for the hopping pattern.

[0105] One way to increase the number of adjacent slots that occupy the same PRB is to use a hopping counter that changes once every N slots, regardless of whether it is an uplink or downlink slot. If the number of consecutive uplink slots is less than N, and N divides the TDD pattern evenly, then consecutive UL slots will occupy the same PRB. This is shown in Figure 4.

[0106] In Figure 3, the uplink, downlink, and special slots of the TDD pattern are indicated by U, D, and S, respectively, in the "Direction" row. The uplink slots are highlighted because that is where PUSCH repetitions are transmitted. For "Slot Number," this disclosure considers a typical TDD pattern with one isolated UL slot every five slots and two adjacent uplink slots every five slots. Setting N=5 means that the "hopping counter" changes once every five slots, and since 5 evenly divides the 10 ms TDD pattern periodicity, the hopping counter is constant across consecutive uplink slots.

[0107] The hopping counter can take one of L values ​​in the range {0...L-1}, allowing for L different locations in frequency. This allows for better performance than Release 15 when diversity is not sufficient. The overall hopping counter calculation can be expressed as: TIFF0007774718000012.tif9158where n s,f μ is the slot number, and n hop is the hopping counter in Figure 3.

[0108] In one embodiment, an offset is added to the above formula. In this way, the appropriate offset value ensures that the hopping pattern change begins in the expected slot. In one approach to this embodiment, a slot-level offset is added to determine the Hop ID: TIFF0007774718000013.tif9158

[0109] For example, if N=5, L=3, and n off The case where .DELTA..times ...

[0110] In another embodiment, the slot level offset L offis added and the hop ID is determined. Here, 0 ≦ L off <L. With this offset, multiple UEs having different L off values can share the same set of PRBs. TIFF0007774718000014.tif9158

[0111] To obtain the best joint channel estimation gain, each frequency hopping position (indexed by the frequency hopping counter in the above embodiment) may be used in adjacent uplink slots during the slots containing the repetitions of the transport block. In the case of the above-mentioned TDD pattern where isolated UL slots are used alternately with two adjacent UL slots, this can be facilitated by selecting an odd value of L. In the above embodiment, L = 3. When PUSCH starts at slot n s,f μ = 8 and repeats 8 times, the hopping sequence is n hop = {11, 2, 00, 1, 22}, so all three hopping positions occupy adjacent UL slots once. For example, if the starting slot is n s,f μ = 4, the sequence is n hop = {0, 11, 2, 00, 1, 2}, so the frequency hopping position n hop = 2 does not occupy adjacent slots. Therefore, if the network desires the best performance, it may be necessary to select a specific starting slot in the frequency hopping pattern or use more repetitions to increase the chance of adjacent UL slots with the same frequency offset.

[0112] The frequency hopping offset can be easily calculated by the formula floor(N prb / L)·n hop Here, N prbis the number of PRBs in the UL bandwidth portion that the UE uses to transmit the PUSCH. However, this makes it difficult to schedule UEs that do not perform frequency hopping with other UEs that do. One way to avoid this difficulty is to configure the UE with a frequency hopping offset value for each of the L possible hops. The frequency hopping offset value is the number of PRBs in the UL bandwidth portion that the UE uses to transmit the PUSCH. offset It is also possible to determine the frequency hopping pattern without directly using the slot number.

[0113] In one embodiment, the hopping counter is not directly based on the following system frame timing and its variants. Instead, there is an additional counter that increments for each slot, up to a limit m lim When n is reached hop is updated (e.g., incremented by 1 modulo L) and m is reset to zero. TIFF0007774718000016.tif9158The value of m is therefore updated once per slot according to: Counter m must be initially initialized to some value (e.g., 0, or some signal value) at a well-defined point in time (e.g., the start of a radio frame). In another embodiment, the counter is initialized differently for different UEs. In another embodiment, counter m Reset is associated with the configured TDD UL / DL pattern.

[0114] In one embodiment, the number of consecutive slots, n, hop is not constant but varies. For example, n hop There is a set of three consecutive slots with one value, followed by n hopThere are sets of two consecutive slots with different values, then sets of three consecutive slots, then sets of two consecutive slots, etc. This is the case with DUDDU and DDDUDD D It is convenient to hop between each UL slot of a UL / DL pattern such as U. Such a pattern may be unlikely in a network where the UL / DL pattern is configured semi-statically, but may occur temporarily in a network where the TDD pattern is configured more dynamically. hop To achieve a hopping pattern that varies the number of consecutive slots in m, one option is to use two m lim Another option is to have a value based on a mapping function from, for example, the slot number modulo n hop For example, TIFF0007774718000018.tif9158

[0115] For example, for the TDD pattern DUDDU, a suitable function f can be defined as follows: TIFF0007774718000019.tif11158 (Such a function can also be used if the number of consecutive slots on each frequency is always the same.) Yet another option is to tie the reset of m (or the reset of the definition of function f) to the concatenation boundaries of the (semi-statically configured) concatenated TDD patterns (3GPP TS38.213 V16.5.0 Section 11.1, "pattern1" and "pattern2").

[0116] In one embodiment, the network may signal to the UE, for example via a DCI, that counter m should be reset to 0 or set to a specific value. This is useful if the network does not use semi-statically configured UL / DL patterns.

[0117] Thus, in some embodiments, the UE transmits according to a frequency hopping pattern, where the frequency hopping offset (i.e., frequency hopping index) changes once every N consecutive time instants, where the N consecutive time instants include both downlink and uplink slots, and the frequency hopping offset reaches one of L values. In some embodiments, the value of L may be odd. In some embodiments, the value of N is always a fractional multiple of the number of slots in the configured TDD UL-DL pattern as defined by "pattern1" (possibly summed with that of "pattern2") of TDD-UL-DL-ConfigCommon in 3GPP TS38.331 V16.5.0.

[0118] In a similar embodiment, a UE transmits a physical channel on different frequency domain resources over time. As shown in FIG. 5A, the UE determines a hopping index value for N consecutive slots, where N is an integer greater than 1, and the N consecutive slots include both downlink and uplink slots (step 500). The UE increments the hopping index after each of the N consecutive slots and resets the hopping index to zero if it exceeds a maximum value (steps 502 and 504). The UE then determines a set of PRBs from a set of frequency offsets to transmit the physical channel according to the hopping index (step 506), and transmits the physical channel on the selected set of PRBs within the slot (step 508).

[0119] In other words, the UE determines a first value of a hopping index for a first set of N consecutive slots in step 500. After the first value of the hopping index is applied to the first set of N consecutive slots, the UE increments the hopping index in step 502 to provide a second value of the hopping index to be applied to a next set of N consecutive slots. This next set of N consecutive slots is referred to herein as a second set of N consecutive slots. If the second value of the hopping index for the second set of N consecutive slots exceeds the maximum value, the UE resets the hopping index for the second set of N consecutive slots to zero in step 504 (i.e., sets the second value of the hopping index applicable to the second set of N consecutive slots to zero). Next, for an uplink slot within the second set of N consecutive slots in which a physical channel is to be transmitted, the UE determines a set of PRBs to transmit the physical channel from the set of frequency offsets according to the second value of the hopping index for the second set of N consecutive slots, and transmits the physical uplink channel on the selected set of PRBs in the uplink slot.

[0120] It may be desirable to configure different frequency hopping offsets for different UEs, since UEs can share the same set of PRBs but occupy them at different times, allowing for efficient use of the PRBs for frequency hopping operations. In such cases, the UE can determine the frequency offset of its transmission by shifting its hopping index by an integer number O, thereby advancing or retarding the frequency hopping sequence. Having different UEs use different values ​​of O to share the same set of PRBs without simultaneously transmitting on a given PRB can enable spectrally efficient operation without increasing interference received by the network. Thus, in some embodiments in which the UE determines hopping index values ​​for N consecutive slots, as shown in FIG. 5A, the UE optionally receives an indication of the hopping index offset O (step 510) and shifts the hopping index by O slots so that the value of the hopping sequence in slot n occurs one O slots earlier or later than when O=0 (zero) (step 512).

[0121] There are other solutions to determine the frequency hopping pattern without using the slot number directly. One other solution is to hop according to a group of adjacent uplink slots. and in some cases may coincide with the time domain window This solution has the advantage that the pattern to be specified is simple. Furthermore, since the hopping pattern follows the TDD pattern, it can be common to all UEs in a cell, avoiding conflicting hopping between UEs in a cell.

[0122] Here, a group of adjacent uplink slots is the actual time-domain window (also called a subwindow) within which the UE can maintain phase continuity. As mentioned above, RAN1#106e agreed on the working premise that the gNB can configure a time-domain window for joint channel estimation. However, if the requirements of maintaining phase continuity and power consistency are violated, the time-domain window may be divided into multiple subwindows. While the UE's determination of the start and end of each configured time-domain window is based on semi-static factors such as the TDD UL / DL configuration, the division into subwindows may be more dynamic, depending on open-loop power control, timing advance adjustments, and even temperature changes. Therefore, it may be beneficial to reset the frequency hopping offset at the start of each configured time-domain window.

[0123] Thus, in one embodiment with two frequency hopping offsets, the first UL transmission in each configured window uses the same frequency hopping offset. In other words, as shown in FIG. 5B, the UE receives signaling to configure the UE with one or more time domain windows used for DMRS bundling (step 520), and the UE restarts the frequency hopping pattern at the start of each configured time domain window (step 522). For example, in one configured time domain window, the UE transmits using frequency hopping offsets 0, 1, 0, sequentially (step 522A). In subsequent configured time domain windows, instead of using offset 1, it starts with offset 0 (e.g., step 522B). In other words, in the first configured time domain window used for DMRS bundling, the UE transmits with the frequency hopping offset defined by the frequency hopping pattern (e.g., a frequency hopping pattern defined sequentially by offsets 0, 1, 0) (step 522A). Next, in a second configured time domain window used for DMRS bundling, the UE transmits at a frequency hopping offset defined by the frequency hopping pattern (e.g., a frequency hopping pattern defined sequentially by offsets 0, 1, 0), where the frequency hopping pattern restarts at the beginning of the second configured time domain window (step 522B).

[0124] If a TDD pattern has adjacent uplink slots between downlink slots and downlink slots with non-adjacent uplink slots, a frequency hopping pattern that hops through all groups may not have an equal number of slots occupying the same PRB.

[0125] Figure 6 shows an example with a typical 10-slot long TDD pattern with one isolated uplink slot and two adjacent uplink slots in different 5-slot periods. As explained in the above embodiment, it may be desirable to occupy the same PRB across two adjacent UL slots for continuity. Figure 6 also shows various hopping patterns. The Release 15 hopping pattern is shown in the "Hop #" row, where the frequency hopping offset alternates between two offset values ​​every other slot. In this case, adjacent slots always have different hopping offsets, so there is no possibility to perform joint channel estimation across adjacent slots. If instead a simple approach labeled "hop by window" is used, where hops are by group (or "window"), considering an 8-slot repetition starting from slot 4 and ending at slot 28, three hops are in PRBs indexed with "0" and five are in PRBs indexed with "1." This imbalance reduces the diversity gain of the frequency hopping pattern.

[0126] If an alternative pattern is used, such as one of those identified in FIG. 6 as "Configured Hopping Patterns 1 and 2" and identified by the patterns {01100011} and {01101100}, respectively, the eight repetitions or available slots from slots 4 through 28 have four slots each of PRB indexes 0 and 1, allowing for a balanced pattern of eight repetition offsets. Note that other lengths or starting points may be unbalanced. However, the pattern generally achieves a more even distribution of slots for the hopped PRBs. For example, {11000111} and {11011000} may be suitable for eight repetitions from slots 8 through 29. Furthermore, scheduling can be used to ensure that UEs requiring the best performance are scheduled with the best hopping pattern.

[0127] The illustrated pattern consists of one frequency hopping offset per slot in which the UE can transmit, which corresponds to an uplink slot or an available PUSCH slot. This has the advantage of reducing signaling overhead, which would be greater if the pattern also indicated, for example, a downlink slot or special slot.

[0128] A short frequency hopping pattern is desirable because a longer frequency hopping pattern results in a larger number of possible frequency locations and a larger time variation in the occupied PRBs. Therefore, a longer frequency hopping pattern can complicate gNB scheduling. A short frequency hopping pattern can result in a larger number of repetitions than the length of the frequency hopping pattern. In such cases, it is necessary to determine the frequency hopping offsets for transmissions that exceed the pattern length. One approach to doing this is to repeat the sequence when the index of a transmission exceeds the pattern length. In other words, the UE selects a first frequency offset for the first transmission, a second offset for the second transmission, and so on. For a repeated transmission #T that exceeds the frequency hopping pattern length P, i.e., T=P+1, the UE selects the first frequency offset for transmission T and the second frequency offset for transmission T+1.

[0129] Thus, in one embodiment, a UE transmits a physical channel on different frequency domain resources over time. As shown in FIG. 7A, the UE receives a list of frequency hopping offsets, each offset in the list corresponding to a slot indicated to the UE as one in which the UE can transmit the physical channel (step 700). The UE selects a frequency offset according to the number of repeated transmissions of the physical channel, where a first frequency offset is selected for the first transmission of the physical channel, a second offset is selected for the second transmission, and so on (step 702). For repeated transmissions starting with transmission T at T=P+1 (where P is the number of frequency hopping offsets in the list), the UE selects the first frequency offset for transmission T, the second frequency offset for transmission T+1, and so on (step 704). For at least one of the repeated transmissions, the UE determines a set of PRBs for transmitting the physical channel from the set of frequency offsets according to a hopping index (step 706), and transmits at least one of the repeated transmissions of the physical channel on the set of PRBs (step 708).

[0130] As mentioned above, it may be desirable to configure different frequency hopping offsets for different UEs to allow the UEs to share the same set of PRBs but occupy them at different times, thereby enabling efficient use of the PRBs for frequency hopping operations. In such a case, the UE may select a frequency offset for transmission according to an index in the list of frequency hopping offsets, where the selected offset is shifted by an integer O that identifies a shift in the frequency hopping sequence.

[0131] 7B, in some embodiments in which a list of frequency-domain hopping offsets is configured in the UE, the UE optionally receives an indication of a hopping index offset O (step 710). The UE selects the frequency hopping offset with index O in the list as the first frequency offset, the frequency hopping offset with index O+1 in the list as the second frequency offset, and so on (step 712). For repeated transmissions starting with transmission T+O at T+O=P+1, the UE selects the frequency hopping offset with index O in the list as the first frequency offset for transmission T, the frequency hopping offset with index O+1 in the list as the second frequency offset for transmission T+1, and so on (step 714).

[0132] 7A and 7B can be described as follows: The UE receives (at step 700) a list of frequency hopping offsets, each of which corresponds to a slot indicated to the UE as one in which the UE can transmit a physical channel. In steps 702 and 704 (or equivalently, steps 712 and 714 if there is an offset O), the UE selects a frequency hopping offset for each repeated transmission of the physical channel as follows: The repeated transmissions are indexed here using index "i", where i=1,...N repetitions and N repetitions Note that σ is the number of repetitions of the physical channel, which in this example is greater than P, where P is the number of frequency hopping offsets in the list. i=1...each iteration of PO sends: The UE selects the (i+O)th frequency hopping offset from the list as the frequency hopping offset for the i-th repeated transmission. · i>Each iteration of PO sends: The UE selects the (i+OP)th frequency hopping offset from the list as the frequency hopping offset for the i-th repeated transmission. Note that, depending on the particular embodiment, there may or may not be an offset (see, e.g., steps 702 and 704 when there is no offset, and steps 712 and 714 when there is an offset). The case without an offset (i.e., steps 702 and 704) is equivalent to O=0. Next, in step 706, for at least one of the repeated transmissions of the physical channel, the UE determines a set of PRBs from the set of frequency offsets on which to transmit the repeated transmission according to a frequency hopping index, where the frequency hopping index is a function of the frequency hopping offset selected for that repeated transmission in step 702 or 704. In step 708, the UE transmits the at least one repeated transmission of the physical channel on the determined set of PRBs.

[0133] As with the other embodiments above, resetting the frequency hopping pattern may be beneficial, for example, to accommodate dynamic TDD operation.

[0134] Thus, in some embodiments in which a list of frequency domain hopping offsets is configured in the UE, the UE, in response to receiving an instruction to reset the frequency hopping pattern, selects a first frequency offset as the first frequency offset for transmission T′ and a second frequency offset as the second frequency offset for transmission T′+1.

[0135] In one embodiment, the frequency hopping pattern can be represented by a binary bit string or its corresponding decimal value, where a 0 or 1 starting from the most significant bit (MSB) of the bit string indicates a different frequency hopping offset to be used for transmission of the first, second, etc. physical or available slot.

[0136] In the above embodiment, for PUSCH repetition with a repetition factor of 8, the bit sequences that the gNB can configure are {01100011, 01101100, 11000111, 11011000} or {99, 108, 199, 216}.

[0137] In Rel-17 PUSCH repetition based on available slots, each bit of the bit string can represent the frequency hopping offset in the corresponding available slot. In Rel-15 and Rel-16 PUSCH repetition with repetition factor K, there is no such concept of available slots, so the bit string indicates the frequency hopping offset in K consecutive slots.

[0138] In another embodiment, if a frequency hopping pattern is configured for the UE by higher layers, the DCI indicates whether frequency hopping based on this pattern is enabled or disabled. If multiple frequency hopping patterns are configured for the UE by higher layers, the DCI can indicate which pattern is enabled.

[0139] It may be desirable for the frequency hopping pattern to be different from the semi-statically configured TDD UL / DL pattern. The reason why only one frequency hopping pattern is sufficient for the UE is that if dynamic slot format indicators (SFIs) are not taken into account, one frequency hopping pattern may achieve a balanced distribution across hops according to the specific TDD pattern and PUSCH starting slot (which may be identified by the parameter K2). If the time domain resource allocation table contains different K2 values, multiple patterns may be considered, or one pattern may be considered that starts the first bit of the bit string at a different offset.

[0140] In another embodiment, the length of the bit sequence of the frequency hopping pattern may be the same as or different from the number of PUSCH repetitions. If the length of the bit sequence is greater than the number of repetitions K, the UE determines the frequency hopping offset according to the first K bits from the MSB. Otherwise, the bit sequence is repeated. In some cases, if the frequency hopping pattern is configured by a higher layer and the number of repetitions is indicated by DCI, the length of the bit sequence of the hopping pattern may be different from the number of repetitions indicated by DCI.

[0141] In another embodiment, if a decimal value is used to indicate the frequency hopping pattern, its maximum value is set or predetermined. For example, if a hopping pattern of 3 is indicated, the UE knows that the maximum number is {0011} for 15 / {1111} and {00000011} for 255 / {11111111}. As an example of pre-determination, the maximum decimal value is based on an all-ones bit string whose length is equal to the number of repetitions.

[0142] In another embodiment, the offset of one frequency hopping pattern may be configured to indicate which bits the UE should start using from the MSB of the bit string, e.g., offset 0, 1... indicates that the UE should start using the MSB, 2nd... bits of the bit string.

[0143] Specifying a hopping pattern to match a TDD pattern as described above can be done based on the structure of the TDD pattern. As disclosed above, the TDD patterns in Release 15 / 16 occur at periods of 20 ms or less. The example TDD pattern above corresponds to 20 ms with a subcarrier spacing of 30 kHz.

[0144] The frequency hopping counter is incremented for each UL slot of the frequency hopping pattern and reset after a period containing the complete number of instances of the TDD pattern. The 3GPP TS38.331 V16.5.0 Release 15 / 16 parameter dl-UL-TransmissionPeriodicity, used to set the periodicity of the TDD pattern, can be used to set the periodicity of the frequency hopping pattern, for example, by setting the length of the frequency hopping pattern equal to "pattern1" if "pattern2" is not configured, or equal to the sum of the dl-UL-TransmissionPeriodicity values ​​for "pattern1" and "pattern2" if "pattern2" is configured. The frequency hopping counter will have a value for each slot of the frequency hopping pattern, but frequency hopping values ​​may only be defined for slots available for UL transmission.

[0145] A frequency hopping offset can be set for each value of the frequency hopping counter. Such offsets can be quantized to, for example, two or four values, requiring one or two bits to identify them in the signaling. These values ​​are identified by a modified version of the Release 15 / 16 frequency hopping offset parameter frequencyHoppingOffsetLists, which allows the offset range to include zero PRBs: frequencyHoppingOffsetLists-r17 SEQUENCE (SIZE (1..4)) OF INTEGER ( 0 ..maxNrofPhysicalResourceBlocks-1)

[0146] Thus, a zero value can be selected so that the UE does not hop from the starting PRB, and each hop can be set to one of the allowed values ​​in frequencyHoppingOffsetLists-r17.

[0147] The configured hopping pattern can be indicated, for example, by a list of hopping offsets containing an entry for each hopping counter value (one hopping counter value per UL slot): frequencyHoppingPattern-r17 SEQUENCE (SIZE (1..maxHoppingPatternLength)) OF INTEGER (0..3)

[0148] To generate the example 9 slot long hopping pattern {011000111} above, three repetitions of the TDD pattern must be used since there are three UL slots per TDD pattern. frequencyHoppingPattern-r17 can be a 9-element sequence: requencyHoppingPattern-r17:=[011000111].

[0149] Thus, in one embodiment, the UE is configured with a hopping pattern, where a hopping offset is configured for each slot of the set of slots available for UL transmission, the length of the hopping pattern is a multiple of the number of slots available for UL transmission, and the set of slots occurs with a periodicity that is a multiple of the TDD UL-DL pattern.

[0150] Because UEs that do not support joint channel estimation must also hop in the same pattern, the frequency hopping pattern must be available regardless of whether cross-slot DMRS bundling (or, in other words, joint channel estimation) is configured and regardless of whether the UE supports DMRS bundling. Such UEs must specify their frequency hopping pattern capabilities without needing to specify their DMRS bundling capabilities (or equivalently, their ability to maintain joint channel estimation or phase continuity).

[0151] Thus, in some embodiments, a UE indicates capability of a hopping pattern configured for each slot of a set of slots available for said UE transmission, regardless of whether the UE indicates capability of maintaining phase continuity between uplink transmissions in different slots.

[0152] For FDD operation, a UE may be configured such that it is required to maintain continuity over a subset of UL transmissions (e.g., a subset of the number of PUSCH repetitions for Type A). In such cases, if frequency hopping is used, it may be desirable to maintain continuity over multiple consecutive slots, which requires occupying the same frequency hopping offset. This again conflicts with Release 15 / 16 frequency hopping, which changes the frequency hopping offset on a slot-by-slot basis. Therefore, new frequency hopping patterns are needed for both FDD and TDD to support joint channel estimation.

[0153] The above embodiment, which defines a hopping pattern that applies to all UEs in a cell and uses frame timing, also applies to FDD, since common hopping timing is beneficial for UEs in a cell. The periodicity of the hopping pattern does not depend on the DL-UL pattern in TDD, but if used by the UE, it must be a multiple of the configured window duration. Even if the duration is not used, the network can adjust the hopping pattern according to the trade-off between joint channel estimation and frequency hopping gain. In scenarios where joint channel estimation gain is limited, it may be better to hop more frequently to benefit from the diversity provided by frequency hopping. In cases where diversity is low, it may be better to configure the pattern to maximize joint channel estimation gain and keep the UE on the same subcarrier for a longer period.

[0154] The same basic approach as for TDD can be used for FDD. A frequency hopping pattern can be defined with a set hopping offset for each hop and each UL transmission. As with network scheduling, the pattern should have a limited length to simplify timing of the hopping pattern. It is also desirable for the pattern to support a maximum number of repetitions. A periodicity of 40 ms allows for a pattern length of 40 for a 15 kHz subcarrier spacing, which is longer than the length required for the 32 repetitions agreed to be supported in Release 17.

[0155] Thus, in some embodiments, a UE is configured with a hopping pattern in which a hopping offset is configured for each slot of a set of slots, and the length of the hopping pattern is an integer submultiple of a predetermined number of slots, such as the number of slots in a radio frame, or a predetermined number of radio frames, such as 2, 3, or 4 radio frames. In other words, in some embodiments, a UE is configured with multiple hopping offsets, each hopping offset is configured for each slot of the set of slots, and the length of the set of slots for which the hopping offsets are configured is an integer submultiple of a predetermined number of slots, such as the number of slots in a radio frame, or a predetermined number of radio frames, such as 2, 3, 4 radio frames.

[0156] Other explanations FIG. 8 is a schematic block diagram of a radio access node 800 according to some embodiments of the present disclosure. Optional functionality is represented by dashed boxes. The radio access node 800 may be, for example, a base station 202 or 206, or a network node that implements all or a portion of the functionality of a base station 202 or gNB described herein. As shown, the radio access node 800 includes a control system 802 that includes one or more processors 804 (e.g., a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or the like), a memory 806, and a network interface 808. The one or more processors 804 are also referred to herein as processing circuits. Additionally, the radio access node 800 may include one or more radio units 810 that each include one or more transmitters 812 and one or more receivers 814 coupled to one or more antennas 816. The radio unit 810 may refer to or be part of air interface circuitry. In some embodiments, the wireless unit(s) 810 are external to the control system 802 and are connected to the control system 802, for example, via a wired connection (e.g., an optical cable). The one or more processors 804 operate to provide one or more functions of the wireless access node 800 described herein. In some embodiments, the functions are implemented in software that is stored, for example, in memory 806 and executed by the one or more processors 804.

[0157] 9 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 800 in accordance with some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have similar virtualization architectures. Again, optional functionality is represented by dashed boxes.

[0158] As used herein, a “virtualized” radio access node is an implementation of a radio access node 800 in which at least a portion of the functionality of the radio access node 800 is implemented as virtual component(s) (e.g., via virtual machine(s) running on physical processing node(s) in network(s)). As shown, in this example, the radio access node 800 may include a control system 802 and / or one or more radio units 810, as described above. The control system 802 may be connected to the radio unit(s) 810 via, for example, an optical cable or the like. The radio access node 800 includes one or more processing nodes 900 coupled to or included as part of a network(s) 902. If present, the control system 802 or radio units are connected to the processing nodes 900 via the network 902. Each processing node 900 includes one or more processors 904 (e.g., CPUs, ASICs, FPGAs, etc.), memory 906, and a network interface 908.

[0159] In this example, the functionality 910 of the radio access node 800 described herein is implemented in one or more processing nodes 900, or distributed in any desired manner between one or more processing nodes 900 and the control system 802 and / or radio unit 810. In some particular embodiments, some or all of the functionality 910 of the radio access node 800 described herein are implemented as virtual components executed by one or more virtual machines implemented in virtual environment(s) hosted by the processing node 900. As will be appreciated by those skilled in the art, additional signaling or communication between the processing node 900 and the control system 802 is used to perform at least some of the desired functionality 910. Notably, in some embodiments, the control system 802 may not be included, in which case the radio unit 810 communicates directly with the processing node 900 via an appropriate network interface.

[0160] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functionality of a radio access node 800 or a node (e.g., processing node 900) that implements one or more of the functionality 910 of the radio access node 800 in a virtual environment in accordance with any of the embodiments described herein. In some embodiments, a carrier is provided that includes the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0161] 10 is a schematic block diagram of a radio access node 800 in accordance with some other embodiments of the present disclosure. The radio access node 800 includes one or more modules 1000, each implemented in software. The modules 1000 provide the functionality of the radio access node 800 described herein. This discussion is equally applicable to the processing node 900 of FIG. 9, where the modules 1000 may be implemented on one of the processing nodes 900 or may be distributed across multiple processing nodes 900 and / or may be distributed across the processing nodes 900 and the control system 802.

[0162] 11 is a schematic block diagram of a wireless communication device 1100 according to some embodiments of the present disclosure. As shown, the wireless communication device 1100 includes one or more processors 1102 (e.g., CPUs, ASICs, FPGAs, etc.), a memory 1104, and one or more transceivers 1106, each including one or more transmitters 1108 and one or more receivers 1110 coupled to one or more antennas 1112. The transceiver(s) 1106 include radio front-end circuitry connected to the antenna(s) 1112 configured to condition signals communicated between the antenna(s) 1112 and the processor(s) 1102, as will be understood by those skilled in the art. The processor 1102 is also referred to herein as a processing circuit. The transceiver 1106 is also referred to herein as a radio circuit. In some embodiments, the functionality of the wireless communication device 1100 described above may be implemented completely or partially in software, for example, stored in the memory 1104 and executed by the processor(s) 1102. It should be noted that the wireless communication device 1100 may include additional components not shown in FIG. 11 , such as, for example, one or more user interface components (e.g., an input / output interface including a display, buttons, a touchscreen, a microphone, a speaker(s), and / or any other components for enabling the input of information into the wireless communication device 1100 and / or the output of information from the wireless communication device 1100), a power source (e.g., a battery and associated power circuitry), etc.

[0163] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform the functions of the wireless communication device 1100 according to any of the embodiments described herein. In some embodiments, a carrier is provided that includes the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0164] 12 is a schematic block diagram of a wireless communication device 1100 according to some other embodiments of the present disclosure. The wireless communication device 1100 includes one or more modules 1200, each implemented in software. The modules 1200 provide the functionality of the wireless communication device 1100 described herein.

[0165] Appropriate steps, methods, features, functions, or advantages disclosed herein may be performed through one or more functional units or modules of one or more virtual devices. Each virtual device may be composed of a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware including digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as ROM (read-only memory), RAM (random access memory), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more telecommunications and / or data communication protocols, as well as instructions for executing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a function corresponding to the respective functional unit in accordance with one or more embodiments of the present disclosure.

[0166] While the steps in the figures may indicate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, or overlap certain operations).

[0167] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. 1. A method implemented in a user equipment (UE) (212, 1100) that transmits physical channels on different frequency domain resources over time, comprising: determining (500) a value of a hopping index for a first set of N consecutive slots, where N is an integer greater than 1; incrementing the value of the hopping index for a second set of N consecutive slots after the N consecutive slots (502); resetting the value of the hopping index to zero if the hopping index exceeds a maximum value (504); For uplink slots in the second set of N consecutive slots in which a physical uplink channel is transmitted: determining (506) a set of physical resource blocks (PRBs) for transmitting physical channels from a set of frequency offsets according to values ​​of the hopping index of the second set of N consecutive slots, wherein the values ​​of the hopping index are: where n hop is the hopping index, and n s，f μ is a physical slot number of a slot to which the hopping index is applied, N is the number of consecutive slots to which the hopping index is applied, and L-1 is the maximum value of the hopping index, and the hopping index is a value in the range of 0 to L-1 inclusive; transmitting (508) the physical uplink channel on a selected set of PRBs in the uplink slot; A method comprising:

2. The first set of N consecutive slots and / or the second set of N consecutive slots include both downlink slots and uplink slots. The method of claim 1.

3. The value of the hopping index is a function of the physical slot number. The method of claim 1.

4. The value of the hopping index is further a function of a defined or configured offset. The method of claim 3.

5. The hopping index changes once every N consecutive time slots, the N consecutive time slots including both downlink and uplink slots, and the set of frequency offsets includes L values ​​corresponding to L possible frequency offsets. The method of claim 4.

6. Each frequency offset is configured for each slot of a set of N slots, where N is an integer submultiple of the predetermined number of slots. The method of claim 4.

7. The predetermined number of slots is the number of slots in a radio frame or the number of slots in a predetermined number of radio frames. The method of claim 6.

8. N has a value that is a fractional multiple of the number of slots in the configured time division duplex (TDD) uplink-downlink pattern. The method of claim 1.

9. The UE indicates its capability for a frequency hopping pattern configured for each slot of a plurality of slots indicated to the UE, regardless of whether the UE indicates an ability to maintain phase continuity between uplink transmissions in different slots. The method of claim 1.

10. A user equipment (UE) (212, 1100) for transmitting physical channels on different frequency domain resources over time, the UE (212, 1100) comprising: determining 500 a value of a hopping index for a first set of N consecutive slots, where N is an integer greater than 1; after the N consecutive slots, incrementing (502) the value of the hopping index for a second set of N consecutive slots; If the hopping index exceeds a maximum value, resetting the value of the hopping index to zero (504); For uplink slots in the second set of N consecutive slots in which a physical uplink channel is transmitted: determining (506) a set of physical resource blocks (PRBs) for transmitting physical channels from a set of frequency offsets according to values ​​of the hopping index of the second set of N consecutive slots, the values ​​of the hopping index being: where n hop is the hopping index, and n s，f μ is a physical slot number of a slot to which the hopping index is applied, N is the number of consecutive slots to which the hopping index is applied, L-1 is the maximum value of the hopping index, and the hopping index is a value in the range of 0 to L-1 inclusive; transmitting the physical uplink channel on the selected set of PRBs in the uplink slot (508); UE that is compatible with.

11. The UE (212; 1100) is further adapted to perform the method according to any one of claims 2 to 9. The UE of claim 10.

12. A user equipment (UE) (212, 1100) for transmitting physical channels on different frequency domain resources over time, the UE (212, 1100) comprising: one or more transmitters; one or more receivers; a processing circuit associated with the one or more transmitters and the one or more receivers, the processing circuit being configured to: determining (500) a value of a hopping index for a first set of N consecutive slots, where N is an integer greater than 1; after the N consecutive slots, incrementing (502) the value of the hopping index for a second set of N consecutive slots; If the hopping index exceeds a maximum value, reset the value of the hopping index to zero (504); For uplink slots in the second set of N consecutive slots in which a physical uplink channel is transmitted: determining (506) a set of physical resource blocks (PRBs) for transmitting physical channels from a set of frequency offsets according to values ​​of the hopping index of the second set of N consecutive slots, the values ​​of the hopping index being: where n hop is the hopping index, and n s，f μ is a physical slot number of a slot to which the hopping index is applied, N is the number of consecutive slots to which the hopping index is applied, L-1 is the maximum value of the hopping index, and the hopping index is a value in the range of 0 to L-1 inclusive; transmitting the physical uplink channel on the set of PRBs selected in the uplink slot (508); The processing circuit configured as above; A UE comprising:

13. The processing circuitry is further configured to cause the UE to perform a method according to any one of claims 2 to 9.

13. The UE of claim 12.

Images