Frequency Hopping Method and Apparatus

Abstract

An embodiment of the present disclosure discloses a frequency hopping method and apparatus, which is performed by a terminal device, and includes: determining a hop number and / or a time domain length per hop in response to a frequency hopping scheme of a physical uplink shared channel (PUSCH) being enabled, where the transmission scheme of the PUSCH is processing a transmission block in multiple slots; and performing frequency hopping based on the frequency hopping scheme and the hop number and / or the time domain length per hop, thereby supporting frequency hopping when the time domain resource allocation pattern of the PUSCH is processing a transmission block in multiple slots.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a frequency hopping method and apparatus.

Background Art

[0002] Currently, for time domain resource allocation in the Physical Uplink Shared Channel (PUSCH), a time domain resource assignment (TDRA) table such as PUSCH repetition type B can be used. Type B-based PUSCH repeated transmission supports two frequency hopping methods: nominal frequency hopping between PUSCH copies and frequency hopping between slots, and a specific frequency hopping method is configured by radio resource control (RRC) upper layer signaling.

[0003] When the time domain resource allocation pattern of PUSCH is a transmission block processing over multi-slots (TBoMS) pattern, if a single transmission block crosses a slot boundary, it may be distributed at different positions in multiple slots. However, the existing patterns of in-slot frequency hopping or inter-slot frequency hopping configured by upper layer signaling are no longer applicable.

[0004] Therefore, a frequency hopping pattern that meets the multi-TBoMS pattern is urgently needed.

Summary of the Invention

Problems to be Solved by the Invention

[0005] Embodiments of the present disclosure propose a frequency hopping method and apparatus, which are applicable to the time domain resource allocation pattern of the Physical Uplink Shared Channel (PUSCH) that is a Transmission Block Processing Over Multi-slots (TBoMS) pattern, and can support frequency hopping in a multi-TBoMS pattern. **Means for Solving the Problem**

[0006] According to a first aspect, embodiments of the present disclosure propose a frequency hopping method, which is executed by a terminal device. The method includes: in response to the frequency hopping mode of the Physical Uplink Shared Channel (PUSCH) being enabled, determining the number of hops and / or the length of the time domain for each hop, where the transmission mode of the PUSCH is the processing of transmission blocks in multiple slots; and performing frequency hopping based on the frequency hopping mode of the PUSCH, the number of hops, and / or the length of the time domain for each hop.

[0007] In the frequency hopping method proposed by embodiments of the present disclosure, when the frequency hopping of the Physical Uplink Shared Channel (PUSCH) is enabled, the terminal device determines the number of hops and the length of the time domain for each hop. Here, the time domain resource allocation pattern of the PUSCH is the processing of transmission blocks in multiple slots, and the terminal device performs frequency hopping based on the number of hops, the length of the time domain for each hop, and the frequency hopping, so as to support frequency hopping when the time domain resource allocation pattern of the PUSCH is the processing of transmission blocks in multiple slots, obtain a frequency diversity gain, and improve the coverage ability.

[0008] In some embodiments, determining the number of hops includes determining the number of hops based on protocol specifications.

[0009] In one implementation form, determining the number of hops based on the protocol regulations includes obtaining a first preset value defined by the protocol, where the first preset value is 2 or more, and determining the first preset value as the number of hops.

[0010] In an alternative implementation form, determining the number of hops based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and determining the number of hops based on the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the number of hops, and the length of the time domain occupied by the transmission block.

[0011] In an alternative implementation form, determining the number of hops based on the protocol regulations includes obtaining the number of settings of the demodulation reference signal (DMRS) in PUSCH, and determining the number of hops based on the correspondence between the number of settings of DMRS defined by the protocol and the number of hops, and the number of settings of DMRS in PUSCH.

[0012] In an alternative implementation form, determining the number of hops based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and determining the number of hops based on the length of the time domain per hop defined by the protocol, the correspondence between the length of the time domain per hop defined by the protocol, the length of the time domain occupied by the transmission block, and the number of hops, and the length of the time domain occupied by the transmission block.

[0013] Optionally, the correspondence between the length of the time domain per hop defined by the protocol, the length of the time domain occupied by the transmission block, and the number of hops is that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain per hop.

[0014] In an alternative implementation, determining the number of hops based on the protocol regulations includes obtaining the positions of the unusable symbols in the PUSCH, determining that the unusable symbols cannot be used for data transmission, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence between the positions of the unusable symbols defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and the positions of the unusable symbols in the PUSCH.

[0015] Optionally, the correspondence between the positions of the unusable symbols defined by the protocol, the frequency hopping start position, and the frequency hopping end position is such that the adjacent symbol position before the position of the unusable symbol is the frequency hopping end position, and the adjacent symbol position after the position of the unusable symbol is the frequency hopping start position.

[0016] In an alternative implementation, determining the number of hops based on the protocol regulations includes obtaining the slot boundary position in the PUSCH, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence between the slot boundary position defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and the slot boundary position in the PUSCH.

[0017] Optionally, the correspondence between the slot boundary position defined by the protocol and the frequency hopping start position is such that the adjacent symbol position before the slot boundary position is the frequency hopping end position, and the adjacent symbol position after the slot boundary position is the frequency hopping start position.

[0018] In an alternative implementation, determining the number of hops based on the protocol specification includes obtaining the slot boundary position in PUSCH and the number of symbol bits of a first preset, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence between the slot boundary position defined by the protocol, the number of symbol bits of the first preset, the frequency hopping start position, and the frequency hopping end position, and based on the slot boundary position and the number of symbol bits of the first preset.

[0019] Optionally, the correspondence between the slot boundary position defined by the protocol, the number of symbol bits of the first preset, and the frequency hopping start position is such that the adjacent symbol position before the slot boundary position is the frequency hopping end position, the adjacent symbol position after the slot boundary position is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by the number of symbol bits of the first preset is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by the number of symbol bits of the first preset is the frequency hopping end position.

[0020] In some embodiments, determining the number of hops includes determining the number of hops based on the configuration of the base station.

[0021] In one implementation, determining the number of hops based on the configuration of the base station includes receiving a third preset value transmitted from the base station, where the third preset value is 2 or more, and determining the third preset value as the number of hops.

[0022] In one implementation form, obtaining the third preset value set by the base station includes receiving the third preset value transmitted via the remaining system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling scheduled by the base station.

[0023] Optionally, receiving the third preset value transmitted via downlink control information (DCI) signaling by the base station includes receiving the third preset value transmitted by multiplexing some or all bits of the modulation and coding scheme (MCS) field or transmission power control (TPC) field of the downlink control information (DCI) via downlink control information (DCI) signaling by the base station, or receiving the third preset value transmitted by adding a new field.

[0024] In one implementation form, determining the number of hops based on the setting of the base station includes receiving one first parameter value within the first parameter set indicated by the base station and determining the first parameter value as the number of hops.

[0025] Optionally, obtaining one first parameter value within the first parameter set indicated by the base station includes receiving the first parameter set set via the remaining system information (RMSI) or radio resource control (RRC) signaling by the base station, and receiving one of the first parameter values within the first parameter set indicated via downlink control information (DCI) or media access control layer control element (MAC CE) signaling by the base station.

[0026] Selectively, receiving the first parameter value within the first parameter set indicated by the base station includes receiving the first parameter set carried in one field added to a modulation and coding scheme (MCS) table or a time domain resource allocation (TDRA) table by the base station, and receiving, via downlink control information (DCI) signaling by the base station, one of the first parameter values within the first parameter set indicated by multiplexing a modulation and coding scheme (MCS) field of the downlink control information (DCI).

[0027] In one implementation, determining the number of hops based on the settings of the base station includes obtaining the length of the time domain resources occupied by the transport block, and determining the number of hops based on the length of the time domain for each hop set by the base station, a specific calculation rule corresponding to the length of the time domain for each hop set by the base station, the length of the time domain occupied by the transport block, and the length of the time domain occupied by the transport block.

[0028] In some embodiments, determining the length of the time domain for each hop includes determining the length of the time domain for each hop based on protocol specifications.

[0029] In one implementation, determining the length of the time domain for each hop based on the protocol specifications includes obtaining a second preset value defined by the protocol, where the second preset value is an integer greater than zero, and determining the second preset value as the length of the time domain for each hop.

[0030] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain for each hop based on the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the length of the time domain for each hop, and the length of the time domain occupied by the transmission block.

[0031] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the number of settings of the demodulation reference signal (DMRS) in PUSCH, and determining the length of the time domain for each hop based on the correspondence between the number of settings of DMRS defined by the protocol and the length of the time domain for each hop, and the number of settings of DMRS in the PUSCH.

[0032] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain for each hop based on the number of hops defined by the protocol, the correspondence between the number of hops defined by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop, and the length of the time domain occupied by the transmission block.

[0033] Optionally, the correspondence between the number of hops, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain for each hop.

[0034] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the positions of the unusable symbols in the PUSCH, determining that the unusable symbols cannot be used for data transmission, and based on the correspondence between the positions of the unusable symbols defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and the positions of the unusable symbols in the PUSCH, determining the frequency hopping start position and the frequency hopping end position.

[0035] Optionally, the correspondence between the positions of the unusable symbols defined by the protocol, the frequency hopping start position, and the frequency hopping end position is such that the adjacent symbol position before the position of the unusable symbol is the frequency hopping end position, and the adjacent symbol position after the position of the unusable symbol is the frequency hopping start position.

[0036] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the slot boundary position in the PUSCH, and based on the correspondence between the slot boundary position defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and the slot boundary position in the PUSCH, determining the frequency hopping start position and the frequency hopping end position.

[0037] Optionally, the correspondence between the slot boundary position defined by the protocol and the frequency hopping start position is such that the adjacent symbol position before the slot boundary position is the frequency hopping end position, and the adjacent symbol position after the slot boundary position is the frequency hopping start position.

[0038] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the slot boundary position in PUSCH and the number of symbol bits of a second preset symbol, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence relationship between the slot boundary position defined by the protocol, the number of symbol bits of the second preset symbol, the frequency hopping start position and the frequency hopping end position, and the slot boundary position and the number of symbol bits of the second preset symbol.

[0039] Optionally, the correspondence relationship between the slot boundary position defined by the protocol, the number of symbol bits of the second preset symbol, the frequency hopping start position and the frequency hopping end position is such that the adjacent symbol position before the slot boundary position is the frequency hopping end position, the adjacent symbol position after the slot boundary position is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by the number of symbol bits of the second preset symbol is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by the number of symbol bits of the second preset symbol is the frequency hopping end position.

[0040] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain for each hop based on the preset number of hops by the protocol, the specific calculation rule corresponding to the preset number of hops by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop, and the length of the time domain occupied by the transmission block.

[0041] Optionally, the specific calculation rule corresponding to the number of hops preset by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is to determine the length of the time domain for each hop at the i (i = 1, 2, …, N - 1) -th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop at the N -th hop as L - floor(L / N)*(N - 1).

[0042] Optionally, the specific calculation rule corresponding to the number of hops preset by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is to determine the length of the time domain for each hop at the i (i = 1, 2, …, N - L + floor(L / N)*N) -th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop at the i (i = 1 + N - L + floor(L / N)*N, …, N) -th hop as ceil(L / N).

[0043] In one embodiment, determining the length of the time domain for each hop includes determining the length of the time domain for each hop based on the setting of the base station.

[0044] In one implementation form, determining the length of the time domain for each hop based on the setting of the base station includes obtaining a fourth preset value set by the base station, where the fourth preset value is 2 or more, and determining the fourth preset value as the length of the time domain for each hop.

[0045] Optionally, obtaining the fourth preset value set by the base station includes receiving the fourth preset value transmitted via remaining system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling by the base station.

[0046] Optionally, instructing the fourth preset value via downlink control information (DCI) signaling by the base station includes receiving the fourth preset value transmitted by multiplexing some or all bits of the modulation and coding scheme (MCS) field or transmission power control (TPC) field of the downlink control information (DCI), or the fourth preset value transmitted by adding a new field, via downlink control information (DCI) signaling by the base station.

[0047] In one implementation, determining the length of the time domain for each hop based on the settings of the base station includes receiving one second parameter value within a second parameter set indicated by the base station, and determining the second parameter value as the number of hops.

[0048] Optionally, obtaining one second parameter value within the second parameter set indicated by the base station includes receiving the second parameter set set via remaining system information (RMSI) or radio resource control (RRC) signaling by the base station, and receiving one second parameter value within the second parameter set indicated via downlink control information (DCI) or media access control layer control element (MAC CE) signaling by the base station.

[0049] Optionally, receiving the first parameter value within the first parameter set indicated by the base station includes receiving the second parameter set carried in one field added to a modulation and coding scheme (MCS) table or a time domain resource allocation (TDRA) table by the base station, and receiving one of the second parameter values within the second parameter set indicated by multiplexing a modulation and coding scheme (MCS) field of downlink control information (DCI) via downlink control information (DCI) signaling by the base station.

[0050] In one implementation, determining the length of the time domain for each hop based on the settings of the base station includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain for each hop based on the number of hops set by the base station, a specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transmission block, and the time domain for each hop, and the length of the time domain occupied by the transmission block.

[0051] Optionally, the specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transmission block, and the time domain for each hop is to determine the length of the time domain for each hop at the i (i = 1, 2,..., N - 1) -th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop at the N -th hop as L - floor(L / N) * (N - 1).

[0052] Optionally, the specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is to determine the length of the time domain for each hop in the i (i = 1, 2, …, N - L + floor(L / N)*N)th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop in the i (i = 1 + N - L + floor(L / N)*N, …, N)th hop as ceil(L / N).

[0053] In some embodiments, the frequency hopping method is intra-slot frequency hopping, or inter-slot frequency hopping, or intra-transmission-block frequency hopping, or intra-retransmission frequency hopping, or inter-retransmission frequency hopping.

[0054] Optionally, performing frequency hopping based on the frequency hopping method of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing frequency hopping based on the intra-slot frequency hopping, the number of hops determined by the method described in some of the above embodiments within the slot, and the length of the time domain for each hop determined by the method described in some of the above embodiments within the slot.

[0055] Optionally, performing frequency hopping based on the frequency hopping method of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing frequency hopping based on the inter-slot frequency hopping, the number of hops determined by the method described in some of the above embodiments, and the length of the time domain for each hop determined by the method described in some of the above embodiments.

[0056] Optionally, performing frequency hopping based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing in-band frequency hopping and performing frequency hopping based on the number of hops determined by the method described in some of the above embodiments within the transmission block or the length of the time domain for each hop determined by the method described in some of the above embodiments within the transmission block.

[0057] Optionally, performing frequency hopping based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing in-band frequency hopping for retransmission copies and performing frequency hopping based on the number of hops determined by the method described in some of the above embodiments within the retransmission copy or the length of the time domain for each hop determined by the method described in some of the above embodiments within the retransmission copy.

[0058] Optionally, performing frequency hopping based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing inter-retransmission-copy frequency hopping and performing frequency hopping based on the number of hops determined by the method described in some of the above embodiments and the length of the time domain for each hop determined by the method described in some of the above embodiments.

[0059] In one implementation, each hop in the frequency hopping includes a demodulation reference signal (DMRS) symbol.

[0060] In one implementation form, responding to the activation of the frequency hopping mode of the physical uplink shared channel (PUSCH) includes enabling the frequency hopping mode of the physical uplink shared channel (PUSCH) in response to a frequency hopping indication carried via radio resource control (RRC), or remaining minimum system information (RMSI), or media access control layer control element (MAC CE), or downlink control information (DCI) signaling by a base station.

[0061] According to a second aspect, an embodiment of the present disclosure provides a frequency hopping method, which is executed by a base station. The method includes determining the number of hops and / or the length of the time domain for each hop of a user equipment (UE) in response to the activation of the frequency hopping mode of a physical uplink shared channel (PUSCH), where the transmission mode of the PUSCH is processing of a transmission block in multiple slots, and performing frequency hopping on the UE based on the frequency hopping mode of the PUSCH and the number of hops and / or the length of the time domain for each hop.

[0062] In one implementation form, determining the number of hops includes determining the number of hops based on protocol specifications.

[0063] In one implementation form, determining the number of hops based on the protocol specifications includes obtaining a fifth preset value defined by the protocol, where the fifth preset value is greater than or equal to 2, and determining the fifth preset value as the number of hops.

[0064] In an alternative implementation form, determining the number of hops based on the protocol specifications includes obtaining the length of the time domain occupied by the transmission block, and determining the number of hops based on the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the number of hops, and the length of the time domain occupied by the transmission block.

[0065] In an alternative implementation, determining the number of hops based on the protocol regulations includes obtaining the number of configured demodulation reference signals (DMRS) in PUSCH, and determining the number of hops based on the correspondence between the number of configured DMRS stipulated by the protocol and the number of hops, and the number of configured DMRS in the PUSCH.

[0066] In an alternative implementation, determining the number of hops based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and determining the number of hops based on the length of the time domain per hop stipulated by the protocol, the correspondence between the length of the time domain per hop stipulated by the protocol, the length of the time domain occupied by the transmission block, and the number of hops, and the length of the time domain occupied by the transmission block.

[0067] Optionally, the correspondence between the length of the time domain per hop stipulated by the protocol, the length of the time domain occupied by the transmission block, and the number of hops is that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain per hop.

[0068] In an alternative implementation, determining the number of hops based on the protocol regulations includes obtaining the positions of the unavailable symbols in PUSCH, the fact that the unavailable symbols cannot be used for data transmission, the correspondence between the positions of the unavailable symbols stipulated by the protocol and the start position and end position of frequency hopping, and determining the start position and end position of frequency hopping based on the positions of the unavailable symbols in the PUSCH.

[0069] Optionally, the correspondence between the positions of the unusable symbols defined by the protocol, the frequency hopping start position, and the frequency hopping end position is such that the adjacent symbol position before the position of the unusable symbol is the frequency hopping end position, and the adjacent symbol position after the position of the unusable symbol is the frequency hopping start position.

[0070] In an optional implementation form, determining the number of hops based on the protocol regulations includes obtaining the slot boundary position in PUSCH, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence between the slot boundary position defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and the slot boundary position in the PUSCH.

[0071] Optionally, the correspondence between the slot boundary position defined by the protocol and the frequency hopping start position is such that the adjacent symbol position before the slot boundary position is the frequency hopping end position, and the adjacent symbol position after the slot boundary position is the frequency hopping start position.

[0072] In an optional implementation form, determining the number of hops based on the protocol regulations includes obtaining the slot boundary position in PUSCH and the number of symbol bits of a third preset, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence between the slot boundary position defined by the protocol, the number of symbol bits of the third preset, the frequency hopping start position, and the frequency hopping end position, and the slot boundary position and the number of symbol bits of the third preset.

[0073] Optionally, the correspondence relationship between the slot boundary position defined by the protocol, the third preset symbol bit number, and the frequency hopping start position is such that the adjacent symbol position before the slot boundary position is the frequency hopping end position, the adjacent symbol position after the slot boundary position is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by the third preset symbol bit number is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by the third preset symbol bit number is the frequency hopping end position.

[0074] In some embodiments, determining the number of hops includes determining the number of hops based on the settings of the base station.

[0075] In one implementation, determining the number of hops based on the settings of the base station includes setting a sixth preset value for the UE, where the sixth preset value is 2 or more, and determining the sixth preset value as the number of hops.

[0076] In one implementation, obtaining the sixth preset value set by the base station includes instructing the sixth preset value by setting scheduling remaining system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling for the UE.

[0077] Optionally, instructing the sixth preset value by setting downlink control information (DCI) signaling to the UE includes setting downlink control information (DCI) signaling to the UE, multiplexing some or all bits of the modulation and coding scheme (MCS) field or transmission power control (TPC) field of the downlink control information (DCI) to instruct the sixth preset value, or instructing the sixth preset value by adding a new field.

[0078] In one implementation, determining the number of hops based on the settings of the base station includes setting one third parameter value within the indicated third parameter set to the UE and determining the third parameter value as the number of hops.

[0079] Optionally, setting one third parameter value within the indicated third parameter set to the UE includes transmitting the third parameter set set by the remaining scheduling system information (RMSI) or radio resource control (RRC) signaling to the UE, and transmitting one third parameter value within the third parameter set indicated by the downlink control information (DCI) or media access control layer control element (MAC CE) signaling to the UE.

[0080] Optionally, setting the third parameter value within the indicated third parameter set to the UE includes transmitting a modulation and coding scheme (MCS) table or time domain resource allocation (TDRA) table with a field added for carrying the third parameter set to the UE, and transmitting downlink control information (DCI) signaling to the base station to instruct one third parameter value within the third parameter set by multiplexing the modulation and coding scheme (MCS) field of the downlink control information (DCI).

[0081] In one implementation form, determining the number of hops based on the setting of the base station includes obtaining the length of the time-domain resource occupied by the transmission block, the length of the time domain for each hop set by the base station, a specific calculation rule corresponding to the length of the time domain for each hop, the length of the time domain occupied by the transmission block, and the number of hops, and determining the number of hops based on the length of the time domain occupied by the transmission block.

[0082] In some embodiments, determining the length of the time domain for each hop includes determining the length of the time domain for each hop based on protocol regulations.

[0083] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining a seventh preset value defined by the protocol, where the seventh preset value is an integer greater than zero, and determining the seventh preset value as the length of the time domain for each hop.

[0084] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the length of the time domain for each hop, and determining the length of the time domain for each hop based on the length of the time domain occupied by the transmission block.

[0085] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the number of settings of the demodulation reference signal (DMRS) in PUSCH, the correspondence between the number of settings of DMRS defined by the protocol and the length of the time domain for each hop, and determining the length of the time domain for each hop based on the number of settings of DMRS in PUSCH.

[0086] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain for each hop based on the number of hops defined by the protocol, the correspondence between the number of hops defined by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop, and the length of the time domain occupied by the transmission block.

[0087] Optionally, the correspondence between the number of hops, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain for each hop.

[0088] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the position of the unusable symbol in PUSCH, the fact that the unusable symbol cannot be used for data transmission, the correspondence between the position of the unusable symbol defined by the protocol and the start position and end position of frequency hopping, and determining the start position of the frequency hopping and the technical position of the frequency hopping based on the position of the unusable symbol in PUSCH.

[0089] Optionally, the correspondence between the position of the unusable symbol defined by the protocol and the start position and end position of frequency hopping is that the adjacent symbol position before the position of the unusable symbol is the end position of the frequency hopping, and the adjacent symbol position after the position of the unusable symbol is the start position of the frequency hopping.

[0090] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the slot boundary position in PUSCH, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence relationship between the slot boundary position defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and the slot boundary position in PUSCH.

[0091] Optionally, the correspondence relationship between the slot boundary position defined by the protocol and the frequency hopping start position is that the adjacent symbol position before the slot boundary position is the frequency hopping end position, and the adjacent symbol position after the slot boundary position is the frequency hopping start position.

[0092] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the slot boundary position in PUSCH and the number of bits of the fourth preset symbol, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence relationship between the slot boundary position defined by the protocol, the number of bits of the fourth preset symbol, the frequency hopping start position, and the frequency hopping end position, and the slot boundary position and the number of bits of the fourth preset symbol.

[0093] Optionally, the correspondence relationship between the slot boundary position defined by the protocol, the fourth preset symbol bit number, the frequency hopping start position, and the frequency hopping end position is such that the symbol position adjacent to the slot boundary position before is the frequency hopping end position, the symbol position adjacent to the slot boundary position after is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by the fourth preset symbol bit number is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by the fourth preset symbol bit number is the frequency hopping end position.

[0094] In one implementation form, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and based on the preset number of hops by the protocol, the specific calculation rule corresponding to the preset number of hops by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop, and determining the length of the time domain for each hop.

[0095] Optionally, the specific calculation rule corresponding to the preset number of hops by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is to determine the length of the time domain for each hop in the i (i = 1, 2,..., N - 1) -th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop in the N -th hop as L - floor(L / N) * (N - 1).

[0096] Optionally, the specific calculation rule corresponding to the number of hops preset by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain per hop is to determine the length of the time domain per hop at the i-th (i = 1, 2, …, N - L + floor(L / N)*N) hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain per hop at the i-th (i = 1 + N - L + floor(L / N)*N, …, N) hop as ceil(L / N).

[0097] In one embodiment, determining the length of the time domain per hop includes determining the length of the time domain per hop based on the settings of the base station.

[0098] In one implementation form, determining the length of the time domain per hop based on the settings of the base station includes setting a fourth preset value for the UE, where the eighth preset value is 2 or more, and determining the eighth preset value as the length of the time domain per hop.

[0099] Optionally, setting the eighth preset value for the UE includes indicating the eighth preset value by setting scheduling remaining system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling to the UE.

[0100] Optionally, indicating the eighth preset value by configuring downlink control information (DCI) signaling for the UE includes configuring downlink control information (DCI) signaling for the UE and indicating the eighth preset value by multiplexing some or all bits of a modulation and coding scheme (MCS) field or a transmission power control (TPC) field of the downlink control information (DCI), or indicating the eighth preset value by adding a new field.

[0101] In one implementation, determining the length of the time domain for each hop based on the configuration of the base station includes configuring one fourth parameter value within the indicated fourth parameter set for the UE and determining the fourth parameter value as the number of hops.

[0102] Optionally, configuring one fourth parameter value within the indicated fourth parameter set for the UE includes transmitting the fourth parameter set configured by the remaining minimum system information (RMSI) or radio resource control (RRC) signaling to the UE, and transmitting one fourth parameter value within the fourth parameter set indicated by the downlink control information (DCI) or media access control layer control element (MAC CE) signaling to the UE.

[0103] Optionally, configuring the fourth parameter value within the indicated fourth parameter set for the UE includes transmitting a modulation and coding scheme (MCS) table or a time domain resource allocation (TDRA) table with a field for carrying the fourth parameter set to the UE, transmitting downlink control information (DCI) signaling to the UE, and indicating one fourth parameter value within the fourth parameter set by multiplexing the modulation and coding scheme (MCS) field of the downlink control information (DCI).

[0104] In one implementation form, determining the length of the time domain for each hop based on the setting of the base station includes obtaining the length of the time domain occupied by the transmission block, and based on the number of hops set by the base station, the specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transmission block, and the time domain for each hop, and the length of the time domain occupied by the transmission block, determining the length of the time domain for each hop.

[0105] Optionally, the specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transmission block, and the time domain for each hop is to determine the length of the time domain for each hop in the i (i = 1, 2,..., N - 1) - th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop in the N - th hop as L - floor(L / N) * (N - 1).

[0106] Optionally, the specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transmission block, and the time domain for each hop is to determine the length of the time domain for each hop in the i (i = 1, 2,..., N - L + floor(L / N) * N) - th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop in the i (i = 1 + N - L + floor(L / N) * N,..., N) - th hop as ceil(L / N).

[0107] In some embodiments, determining the length of the time domain for each hop includes determining the length of the time domain for each hop based on the setting of the base station.

[0108] In one implementation form, determining the length of the time domain for each hop based on the setting of the base station includes setting a fourth preset value in the UE, where the eighth preset value is 2 or more, and determining the eighth preset value as the length of the time domain for each hop.

[0109] Optionally, setting the eighth preset value in the UE includes instructing the eighth preset value by setting scheduling remaining system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling in the UE.

[0110] Optionally, instructing the eighth preset value by setting downlink control information (DCI) signaling in the UE includes setting downlink control information (DCI) signaling in the UE and instructing the eighth preset value by multiplexing some or all bits of the modulation and coding scheme (MCS) field or transmission power control (TPC) field of the downlink control information (DCI), or instructing the eighth preset value by adding a new field.

[0111] In one implementation form, determining the length of the time domain for each hop based on the setting of the base station includes setting one fourth parameter value within the indicated fourth parameter set in the UE and determining the fourth parameter value as the number of hops.

[0112] Optionally, setting one of the fourth parameter values within the indicated fourth parameter set to the UE includes transmitting the fourth parameter set set by scheduling remaining system information (RMSI) or radio resource control (RRC) signaling to the UE, and transmitting one of the fourth parameter values within the fourth parameter set indicated by downlink control information (DCI) or media access control layer control element (MAC CE) signaling to the UE.

[0113] Optionally, setting the fourth parameter value within the indicated fourth parameter set to the UE includes transmitting a modulation and coding scheme (MCS) table or time domain resource allocation (TDRA) table with a field for carrying the fourth parameter set to the UE, and transmitting downlink control information (DCI) signaling to the UE to indicate one of the fourth parameter values within the fourth parameter set by multiplexing the modulation and coding scheme (MCS) field of the downlink control information (DCI).

[0114] In one implementation, determining the length of the time domain per hop based on the settings of the base station includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain per hop based on the number of hops set by the base station, a specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transmission block, and the time domain per hop, and the length of the time domain occupied by the transmission block.

[0115] Optionally, the specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transport block, and the time domain for each hop is to determine the length of the time domain for each hop in the i (i = 1, 2, …, N - 1) -th hop as floor(L / N), where L is the length of the time domain occupied by the transport block, N is an integer, and to determine the length of the time domain for each hop in the N -th hop as L - floor(L / N)*(N - 1).

[0116] Optionally, the specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transport block, and the length of the time domain for each hop is to determine the length of the time domain for each hop in the i (i = 1, 2, …, N - L + floor(L / N)*N) -th hop as floor(L / N), where L is the length of the time domain occupied by the transport block, N is an integer, and to determine the length of the time domain for each hop in the i (i = 1 + N - L + floor(L / N)*N, …, N) -th hop as ceil(L / N).

[0117] In some embodiments, the frequency hopping pattern is intra - slot frequency hopping, or inter - slot frequency hopping, or intra - transport - block frequency hopping, or intra - retransmission frequency hopping, or inter - retransmission frequency hopping.

[0118] Optionally, performing frequency hopping on the UE based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing frequency hopping on the UE based on the intra - slot frequency hopping, the number of hops determined by the method described in some of the above embodiments within the slot, and the length of the time domain for each hop determined by the method described in some of the above embodiments within the slot.

[0119] Optionally, performing frequency hopping on the UE based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing inter-slot frequency hopping on the UE based on the number of hops determined by the method described in some of the above embodiments and the length of the time domain for each hop determined by the method described in some of the above embodiments.

[0120] Optionally, performing frequency hopping on the UE based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing intra-transport-block frequency hopping on the UE based on the number of hops determined by the method described in some of the above embodiments within the transport block or the length of the time domain for each hop determined by the method described in some of the above embodiments within the transport block.

[0121] Optionally, performing frequency hopping based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing intra-retransmission-copy frequency hopping on the UE based on the number of hops determined by the method described in some of the above embodiments within the retransmission copy or the length of the time domain for each hop determined by the method described in some of the above embodiments within the retransmission copy.

[0122] Optionally, performing frequency hopping on the UE based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing inter-retransmission-copy frequency hopping on the UE based on the number of hops determined by the method described in some of the above embodiments and the length of the time domain for each hop determined by the method described in some of the above embodiments.

[0123] In one implementation, each hop in the frequency hopping includes a demodulation reference signal (DMRS) symbol.

[0124] In one implementation, responding to the activation of the frequency hopping mode for the UE on the physical uplink shared channel (PUSCH) includes sending a frequency hopping indication carried by radio resource control (RRC), or remaining system information (RMSI) of scheduling, or media access control layer control element (MAC CE), or downlink control information (DCI) signaling to the UE, in response to which the frequency hopping mode for the UE on the physical uplink shared channel (PUSCH) is activated.

[0125] According to a third aspect, an embodiment of the present disclosure provides a communication device, which has a function of realizing part or all of the terminal device in the method described in the first aspect above. For example, the function of the communication device may have the functions in some or all of the embodiments of the present disclosure, or may have the function of implementing any one embodiment of the present disclosure alone. The function can be realized by hardware, or can also be realized by executing corresponding software via the hardware. The hardware or software includes one or more units or modules corresponding to the above functions.

[0126] In one implementation, the structure of the communication device can include a transceiver module and a processing module. Here, the transceiver module is configured to determine the number of hops and / or the length of the time domain for each hop in response to the activation of the frequency hopping mode for the physical uplink shared channel (PUSCH). Here, the transmission mode of the PUSCH is the processing of transmission blocks in multiple slots, and the processing module is configured to perform frequency hopping based on the frequency hopping mode of the PUSCH, the number of hops, and / or the length of the time domain for each hop.

[0127] As an example, the processing module may be a processor, the transmitting and receiving module may be a transceiver or a communication interface, and the storage module may be a memory.

[0128] According to a fourth aspect, an embodiment of the present disclosure provides another communication device, which has a function of implementing part or all of the base station in the method example described in the second aspect above. For example, the function of the communication device may have the functions in some or all of the embodiments of the present disclosure, or may have the function of implementing any one embodiment of the present disclosure alone. The function can be realized by hardware, or can also be realized by executing corresponding software via the hardware. The hardware or software includes one or more units or modules corresponding to the above functions.

[0129] In one implementation form, the structure of the communication device can include a transmitting and receiving module and a processing module. Here, the transmitting and receiving module is configured to determine the number of hops of the UE and / or the length of the time domain for each hop in response to the activation of the frequency hopping method of the physical uplink shared channel (PUSCH). Here, the transmission method of the PUSCH is the processing of transmission blocks in multiple slots, and the processing module is configured to perform frequency hopping on the UE based on the frequency hopping method of the PUSCH, the number of hops, and / or the length of the time domain for each hop.

[0130] As an example, the processing module may be a processor, the transmitting and receiving module may be a transceiver or a communication interface, and the storage module may be a memory.

[0131] According to a fifth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory. A computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the device to execute the method described in the first aspect above.

[0132] According to a sixth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, a computer program is stored in the memory, and the processor executes the computer program stored in the memory to cause the device to execute the method described in the second aspect above.

[0133] According to a seventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to execute the code instructions so as to execute the method described in the first aspect above.

[0134] According to an eighth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to execute the code instructions so as to execute the method described in the second aspect above.

[0135] According to a ninth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing instructions. When the instructions are executed, the method described in the first aspect above is realized.

[0136] According to a tenth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing instructions. When the instructions are executed, the method described in the second aspect above is realized.

[0137] According to an eleventh aspect, an embodiment of the present disclosure provides a computer program product including a computer program. When it is executed by a computer, the computer is caused to execute the method described in the first aspect above.

[0138] According to the 12th aspect, an embodiment of the present disclosure provides a computer program product including a computer program, which, when executed by a computer, causes the computer to execute the method described in the above 2nd aspect.

[0139] According to the 13th aspect, the present disclosure provides a chip system, which includes at least one processor and an interface, and is used to support a terminal device to realize the function according to the 1st aspect, for example, to determine or process at least one of the data and information related to the above method. In one possible design, the chip system further includes a memory, and the memory is used to store computer programs and data required for the terminal device. The chip system may be composed of chips or may include chips and other individual elements.

[0140] According to the 14th aspect, the present disclosure provides a chip system, which includes at least one processor and an interface, and is used to support a terminal device to realize the function according to the 2nd aspect, for example, to determine or process at least one of the data and information related to the above method. In one possible design, the chip system further includes a memory, and the memory is used to store computer programs and data required for the terminal device. The chip system may be composed of chips or may include chips and other individual elements.

[0141] According to the 15th aspect, an embodiment of the present disclosure provides a computer program, which, when executed by a computer, causes the computer to execute the method described in the above 1st aspect.

[0142] According to the 16th aspect, an embodiment of the present disclosure provides a computer program, which, when executed by a computer, causes the computer to execute the method described in the above 2nd aspect.

Brief Description of the Drawings

[0143] To more clearly explain the technical solutions in the embodiments or background art of the present disclosure, the drawings necessary for use in the embodiments or background art of the present disclosure will be described below.

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Modes for Carrying Out the Invention

[0144] To facilitate understanding, first, the terms related to the present disclosure will be explained.

[0145] 1. Downlink Control Information (DCI) DCI is carried by the Physical Downlink Control Channel (PDCCH), and DCI can include uplink-downlink resource allocation, Hybrid Automatic Repeat Request (HARQ) information, power control, etc.

[0146] 2. Physical Uplink Share Channel (PUSCH) PUSCH is used to carry uplink services and upper layer signaling data related to Long Term Evolution (LTE) users. As the main uplink data carrier channel in the physical layer, it can schedule and transmit uplink data and can also carry control information.

[0147] 3. Demodulation Reference Signal (DMRS) In communication technology, it is used for coherent demodulation of the PUSCH and PUCCH channels.

[0148] 4. Frequency Hopping (FH). Frequency hopping is a communication method in which both the receiving end and the transmitting end convert the frequency domain resources used for information transmission according to a predetermined rule to obtain frequency diversity gain.

[0149] To better understand the frequency hopping method proposed by the embodiments of the present disclosure, the following first describes the communication system used in the embodiments of the present disclosure.

[0150] As shown in FIG. 1, FIG. 1 is a schematic diagram of the architecture of a communication system 10 provided by an embodiment of the present disclosure. The communication system 10 can include one network device 11 and one terminal device 12. However, the number and form of the devices shown in FIG. 1 are exemplary and do not limit the embodiments of the present disclosure. In actual applications, it can include two or more network devices 11 and two or more terminal devices 12. For example, the communication system 10 shown in FIG. 1 includes one network device 11 and one terminal device 12 is taken as an example.

[0151] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems. For example, a long term evolution (LTE) system, a 5th generation (5G) mobile communication system, a 5G new radio (NR) system, or other future new type mobile communication systems, etc.

[0152] The network device 11 in the embodiments of the present disclosure is an entity on the network side for transmitting and receiving signals. For example, the network device 11 may be an evolved NodeB (eNB), a transmission reception point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system, etc. The embodiments of the present disclosure do not limit the specific technologies and specific device forms used by the network device. The network device 11 provided by the embodiments of the present disclosure can be composed of a central unit (CU) and a distributed unit (DU). Here, the CU can also be called a control unit. Using the CU-DU structure, the protocol layer of a network device, such as a base station, can be separated. The functions of some protocol layers are centrally controlled in the CU, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0153] The terminal device 12 in the embodiments of the present disclosure is an entity on the user side for transmitting and receiving signals, such as a mobile phone. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be an automobile equipped with a communication function, a smart car, a mobile phone, a wearable device, a tablet (Pad), a computer equipped with a wireless transmission and reception function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. The embodiments of the present disclosure do not limit the specific technologies and specific device forms used by the terminal device 12.

[0154] In the time-domain resource allocation of PUSCH, a time-domain resource allocation (TDRA) table such as PUSCH repetition type B like may be adopted. The Type B PUSCH repetition, that is, the PUSCH repeated transmission scheme based on sub-slot aggregation, can improve the reliability of PUSCH transmission and further reduce the transmission delay. In the case of Type B PUSCH repetition, the uplink grant signaling or the first type of grant-free configuration information indicates the resource of the first nominal PUSCH, and the time-domain resources of the remaining PUSCH repetitions depend on the available symbols of the first PUSCH repetition. The number of repeated transmissions indicated by the base station represents the nominal number of repetitions, and the actual number of repetitions may be greater than the nominal number of repetitions. If the time-domain resource of the nominal PUSCH crosses the slot boundary, it is divided into two actual PUSCH transmissions. The Type B-based PUSCH repeated transmission supports two frequency hopping methods, namely, frequency hopping between nominal PUSCH repetitions and frequency hopping between slots, and the specific frequency hopping method is set by the RRC upper layer signaling of the base station.

[0155] However, these two existing frequency hopping methods are no longer applicable when the time-domain resource allocation of the physical uplink shared channel (PUSCH) is in the multi-TBoMS pattern. The present disclosure proposes a frequency hopping method that can support frequency hopping in the multi-TBoMS pattern for the multi-TBoMS pattern.

[0156] Note that the communication system described in the embodiments of the present disclosure is for more clearly explaining the technical solutions of the embodiments of the present disclosure, and does not limit the technical solutions provided by the embodiments of the present disclosure. Those skilled in the art will understand that with the evolution of system architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present disclosure are similarly applicable to similar technical problems.

[0157] Hereinafter, the frequency hopping method and apparatus provided by the present disclosure will be introduced in detail in combination with the drawings.

[0158] Referring to FIG. 2, FIG. 2 is a schematic flowchart of a frequency hopping method provided by an embodiment of the present disclosure. This method is executed by a terminal device. As shown in FIG. 2, this method can include, but is not limited to, the following steps S1 to S2.

[0159] In S1, in response to the frequency hopping mode of the Physical Uplink Shared Channel (PUSCH) becoming effective, the number of hops and / or the length of the time domain for each hop are determined. Here, the transmission mode of the PUSCH is the processing of transmission blocks in multiple slots.

[0160] In the embodiments of the present disclosure, the time domain resource allocation pattern of the PUSCH is the processing of transmission blocks in multiple slots. In the Fifth-Generation mobile Communications (5G) New Radio (NR) system being studied by the 3rd Generation Partnership Project (3GPP), the length of the time domain of one radio frame is 10 milliseconds (ms), one radio frame is equal to 10 subframes, one subframe can include multiple slots, and each slot contains a certain number of time domain symbols.

[0161] Examples of the present disclosure will be described by taking as an example that each slot includes 14 time domain symbols. Specifically, as shown in FIG. 3, each transmission block occupies 42 time domain symbols, and the position of the start symbol of the transmission block is 3. In this case, one transmission block needs to be transmitted in 4 slots, that is, the time domain resource allocation of PUSCH is that one transmission block needs to be transmitted in 4 slots.

[0162] Also, the start position of the transmission block can be set to any of 0 to 13 as needed.

[0163] Note that one transmission block needs to be transmitted in a plurality of slots, and it may be transmitted in two or more slots. FIG. 3 is only used as an example for explanation, and can be determined based on the number of time domain symbols occupied by each transmission block, the start position of the transmission block, and the number of time domain symbol bits included in the slot.

[0164] The frequency hopping method of the examples of the present disclosure is a method of performing frequency hopping when the time domain resource allocation pattern of PUSCH is such that the number of time domain symbols occupied by each transmission block is greater than the number of time domain symbols included in one slot.

[0165] In S2, frequency hopping is performed based on the frequency hopping mode of PUSCH, the number of hops, and / or the length of the time domain for each hop.

[0166] Specifically, frequency hopping is performed based on the frequency hopping mode and the number of hops, or frequency hopping is performed based on the frequency hopping mode and the length of the time domain for each hop, or frequency hopping is performed based on the frequency hopping mode, the number of hops, and the length of the time domain for each hop.

[0167] According to an embodiment of the present disclosure, the frequency hopping method provided by the embodiment includes that when the frequency hopping mode of PUSCH becomes effective, the terminal device determines the number of hops and / or the length of the time domain for each hop, where the time domain resource allocation pattern of PUSCH is the processing of a transmission block in multiple slots, and the terminal device performs frequency hopping based on the frequency hopping mode, the number of hops and / or the length of the time domain for each hop, so as to be able to perform frequency hopping when the time domain resource allocation pattern of PUSCH is the processing of a transmission block in multiple slots, obtain a frequency diversity gain, and improve the coverage ability.

[0168] In some embodiments, determining the number of hops includes determining the number of hops based on protocol regulations.

[0169] In an embodiment of the present disclosure, the number of hops can be determined according to protocol regulations.

[0170] In some embodiments, determining the number of hops based on protocol regulations includes obtaining a first preset value defined by the protocol, where the first preset value is greater than or equal to 2, and determining the first preset value as the number of hops.

[0171] Exemplarily, when the protocol stipulates that the first preset value is 2, the number of hops is 2. Of course, the protocol may stipulate that the first preset value is another integer greater than 2, and the present disclosure is not limited thereto.

[0172] In some embodiments, determining the number of hops based on protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and determining the number of hops based on the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the number of hops, and the length of the time domain occupied by the transmission block.

[0173] Note that the correspondence between the length of the time domain occupied by the transport block defined by the protocol and the number of hops may be a one-to-one correspondence, that is, the number of hops can correspond to different values according to the length of the time domain occupied by the transport block. Alternatively, the correspondence between the length of the time domain occupied by the transport block and the number of hops may be a proportional relationship. Alternatively, it may be another relationship in which one value is obtained from the other value, that is, the number of hops may be directly determined based on the length of the time domain occupied by the transport block.

[0174] Exemplarily, when the protocol stipulates that the length of the time domain occupied by the transport block is 16 symbols, and when the corresponding number of hops is 2, upon obtaining that the length of the time domain occupied by the transport block is 16 symbols, the number of hops is determined to be 2.

[0175] In some embodiments, determining the number of hops based on the protocol specification includes obtaining the number of settings of the demodulation reference signal (DMRS) in the PUSCH, and determining the number of hops based on the correspondence between the number of DMRS stipulated by the protocol and the number of hops, and the number of settings of the DMRS in the PUSCH.

[0176] Note that the correspondence between the number of DMRS stipulated by the protocol and the number of hops may be a one-to-one correspondence, that is, the number of hops can correspond to different values according to the number of DMRS settings. Alternatively, the correspondence between the number of DMRS and the number of hops may be a proportional relationship. Alternatively, it may be another relationship in which one value is obtained from the other value, that is, the number of hops may be directly determined based on the number of DMRS.

[0177] Exemplarily, the correspondence between the number of DMRS and the number of hops may be a proportional relationship, the number of DMRS is k times the number of hops, and k is 1 or more. When k is equal to 1, upon obtaining that the number of DMRS is 3, the number of hops is determined to be 3.

[0178] In some embodiments, determining the number of hops based on protocol regulations includes obtaining the length of the time domain occupied by the transmission block, the length of the time domain for each hop defined by the protocol, the correspondence between the length of the time domain for each hop preset by the protocol, the length of the time domain occupied by the transmission block, and the number of hops, and determining the number of hops based on the length of the time domain occupied by the transmission block.

[0179] Here, in the embodiments of the present disclosure, the number of hops can be determined based on the length of the time domain for each hop defined by the protocol, the correspondence between the length of the time domain for each hop defined by the protocol, the length of the time domain occupied by the transmission block, and the number of hops, and the length of the time domain occupied by the obtained transmission block.

[0180] In some embodiments, the correspondence between the length of the time domain for each hop preset by the protocol, the length of the time domain occupied by the transmission block, and the number of hops is that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain for each hop.

[0181] Exemplarily, when the protocol stipulates that the length of the time domain for each hop is 7, based on the correspondence that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain for each hop, after obtaining that the length of the time domain occupied by the transmission block is 42, the number of hops can be determined to be 6.

[0182] In some embodiments, determining the number of hops based on protocol regulations includes obtaining the position of the unusable symbol in the PUSCH, the fact that the unusable symbol cannot be used for data transmission, the correspondence between the position of the unusable symbol defined by the protocol and the frequency hopping start position and the frequency hopping end position, and determining the frequency hopping start position and the frequency hopping end position based on the position of the unusable symbol in the PUSCH.

[0183] Exemplarily, in the PUSCH, the unusable symbol is, in the unpaired spectrum, a protection symbol for the downlink to uplink switching set by upper layer signaling is the unusable symbol, or the symbol pattern indication information field with 1 bit set in the DCI provided by the base station is the unusable symbol, etc. Note that the unusable symbol in the PUSCH is not only the examples of the above two types, and the unusable symbols of the above two types are only used for the purpose of explanation.

[0184] In some embodiments, the correspondence relationship between the position of the unusable symbol defined by the protocol and the frequency hopping start position and the frequency hopping end position is that the adjacent symbol position before the position of the unusable symbol is the frequency hopping end position, and the adjacent symbol position after the position of the unusable symbol is the frequency hopping start position.

[0185] Specifically, in the embodiments of the present disclosure, the position of the unusable symbol in the PUSCH is obtained, and based on the unusable symbol position, the frequency hopping start position and the frequency hopping end position are determined.

[0186] Exemplarily, as shown in FIG. 4, the adjacent symbol position before the position of the unusable symbol is the frequency hopping end position, and the adjacent symbol position after the position of the unusable symbol is the frequency hopping start position.

[0187] In some embodiments, determining the number of hops based on the protocol provisions includes obtaining the slot boundary position in the PUSCH, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence relationship between the slot boundary position defined by the protocol and the frequency hopping start position and the frequency hopping end position, and the slot boundary position in the PUSCH.

[0188] Note that one radio frame is equal to ten sub - frames, one sub - frame can include a plurality of slots, each slot can include a certain number of time - domain symbols, the slot boundary may be the boundary of the time - domain symbols included in the slot, each slot includes two slot boundaries, and two adjacent slots have a common one slot boundary.

[0189] In some embodiments, the correspondence between the slot boundary position defined by the protocol and the frequency - hopping start position is that the adjacent symbol position before the slot boundary position is the frequency - hopping end position, and the adjacent symbol position after the slot boundary position is the frequency - hopping start position.

[0190] Exemplarily, as shown in FIG. 5, the adjacent symbol position before the slot boundary position is the frequency - hopping end position, and the adjacent symbol position after the slot boundary position is the frequency - hopping start position.

[0191] In some embodiments, determining the number of hops based on the protocol regulations includes obtaining the slot boundary position in the PUSCH and the number of bits of the first preset symbol, and determining the frequency - hopping start position and the frequency - hopping end position based on the correspondence between the slot boundary position defined by the protocol, the number of bits of the first preset symbol, the frequency - hopping start position, and the frequency - hopping end position, and the slot boundary position and the number of bits of the first preset symbol.

[0192] In the embodiments of the present disclosure, the number of bits of the first preset symbol may be any value greater than 0 and less than the number of time - domain symbols included in the slot, and this is not specifically limited.

[0193] In some embodiments, the correspondence relationship between the slot boundary position defined by the protocol, the first preset number of symbol bits, and the frequency hopping start position is such that the adjacent symbol position before the slot boundary position is the frequency hopping end position, the adjacent symbol position after the slot boundary position is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by the first preset number of symbol bits is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by the first preset number of symbol bits is the frequency hopping end position.

[0194] Exemplarily, as shown in FIG. 6, when the number of time domain symbols included in the slot is 14 and the first preset symbol is 7, the adjacent symbol position before the slot boundary position is the frequency hopping end position, the adjacent symbol position after the slot boundary position is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by 7 is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by 7 is the frequency hopping end position.

[0195] In some embodiments, determining the number of hops includes determining the number of hops based on the settings of the base station.

[0196] In the embodiments of the present disclosure, the number of hops can be determined based on the settings of the base station.

[0197] In some embodiments, determining the number of hops based on the settings of the base station includes receiving a third preset value transmitted from the base station, where the third preset value is 2 or more, and determining the third preset value as the number of hops.

[0198] Exemplarily, when the protocol stipulates that the third preset value is 2, the number of hops is 2. Naturally, the protocol may stipulate that the third preset value is another integer greater than 2, and the present disclosure is not limited thereto.

[0199] In some embodiments, receiving the third preset value set by the base station includes receiving the third preset value transmitted via scheduling remaining system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling by the base station.

[0200] In an embodiment of the present disclosure, first, the third preset value transmitted via scheduling remaining system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling by the base station is received.

[0201] In some embodiments, receiving the third preset value indicated via downlink control information (DCI) signaling by the base station includes obtaining the third preset value transmitted by multiplexing some or all bits of the modulation and coding scheme (MCS) field or transmit power control (TPC) field of the downlink control information (DCI) or the third preset value transmitted by adding a new field via downlink control information (DCI) signaling by the base station via downlink control information (DCI) signaling by the base station.

[0202] In some embodiments, determining the number of hops based on the base station configuration includes receiving one first parameter value within a first parameter set indicated by the base station and determining the first parameter value as the number of hops.

[0203] In some embodiments, obtaining one first parameter value within a first parameter set indicated by the base station includes receiving a first parameter set configured by the base station via scheduling remaining system information (RMSI) or radio resource control (RRC) signaling, and obtaining one first parameter value within the first parameter set indicated by the base station via downlink control information (DCI) or media access control layer control element (MAC CE) signaling by the base station.

[0204] In some embodiments, receiving a first parameter value within a first parameter set indicated by the base station includes receiving a first parameter set carried in one field added to a modulation and coding scheme (MCS) table or a time domain resource allocation (TDRA) table by the base station, and receiving one first parameter value within the first parameter set indicated by multiplexing the modulation and coding scheme (MCS) field of the downlink control information (DCI) via downlink control information (DCI) signaling by the base station.

[0205] In some embodiments, determining the number of hops based on the base station configuration includes obtaining the length of the time domain resources occupied by the transport block, and determining the number of hops based on the length of the time domain per hop set by the base station, the corresponding specific calculation rule of the length of the time domain per hop set by the base station, the length of the time domain occupied by the transport block, and the number of hops, and the length of the time domain occupied by the transport block.

[0206] In some embodiments, determining the length of the time domain for each hop includes determining the length of the time domain for each hop based on protocol specifications.

[0207] In some embodiments, determining the length of the time domain for each hop based on protocol specifications includes obtaining a second preset value defined by the protocol, where the second preset value is an integer greater than zero, and determining the second preset value as the length of the time domain for each hop.

[0208] Exemplarily, if the protocol specifies that the second preset value is 5, the length of the time domain for each hop is 5. Of course, the protocol may specify that the second preset value is another integer, and the present disclosure is not limited thereto.

[0209] In some embodiments, determining the length of the time domain for each hop based on protocol specifications includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain for each hop based on the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the length of the time domain for each hop, and the length of the time domain occupied by the transmission block.

[0210] Note that the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the length of the time domain for each hop may be a one-to-one correspondence, that is, the length of the time domain for each hop can correspond to different values according to the length of the time domain occupied by the transmission block. Alternatively, the correspondence between the length of the time domain occupied by the transmission block and the length of the time domain for each hop may be a proportional relationship. Alternatively, it may be another relationship in which one value is obtained from the other value, that is, the length of the time domain for each hop may be directly determined based on the length of the time domain occupied by the transmission block.

[0211] Exemplarily, when the protocol stipulates that the length of the time domain occupied by the transport block is 16 symbols, if the length of the time domain for each hop is 6, when it is obtained that the length of the time domain occupied by the transport block is 16 symbols, the length of the time domain for each hop is determined to be 6.

[0212] In some embodiments, determining the length of the time domain for each hop based on the protocol specification includes obtaining the number of settings of the demodulation reference signal (DMRS) in the PUSCH, and determining the length of the time domain for each hop based on the correspondence between the number of settings of the DMRS stipulated by the protocol and the length of the time domain for each hop, and the number of settings of the DMRS in the PUSCH.

[0213] Note that the correspondence between the number of DMRS stipulated by the protocol and the length of the time domain for each hop may be a one-to-one correspondence, that is, the length of the time domain for each hop can correspond to different values according to the number of DMRS. Alternatively, the correspondence between the number of DMRS and the length of the time domain for each hop may be a proportional relationship. Alternatively, it may be another relationship in which one value is obtained from the other value, that is, the length of the time domain for each hop may be directly determined based on the number of DMRS.

[0214] Exemplarily, the correspondence between the number of DMRS and the number of hops may be a proportional relationship, the number of DMRS is k times the number of hops, and k is 1 or more. When k is equal to 3, when it is obtained that the number of DMRS is 3, the length of the time domain for each hop is determined to be 9.

[0215] In some embodiments, determining the length of the time domain for each hop based on protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain for each hop based on the number of hops defined by the protocol, the correspondence between the number of hops defined by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop, and the length of the time domain occupied by the transmission block.

[0216] Here, in the embodiments of the present disclosure, the length of the time domain for each hop can be determined based on the number of hops defined by the protocol, the correspondence between the number of hops defined by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop, and the length of the time domain occupied by the obtained transmission block.

[0217] In some embodiments, the correspondence between the number of hops, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain for each hop.

[0218] Exemplarily, when the protocol specifies that the number of hops is 6, after obtaining that the length of the time domain occupied by the transmission block is 42 based on the correspondence that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain for each hop, the length of the time domain for each hop can be determined to be 7.

[0219] In some embodiments, determining the length of the time domain for each hop based on protocol regulations includes obtaining the positions of the unusable symbols in the PUSCH, the fact that the unusable symbols cannot be used for data transmission, the correspondence between the positions of the unusable symbols defined by the protocol and the frequency hopping start position and the frequency hopping end position, and determining the frequency hopping start position and the technical position of the frequency hopping based on the positions of the unusable symbols in the PUSCH.

[0220] Exemplarily, in the PUSCH, the unusable symbol is, in the unpaired spectrum, a protection symbol for the downlink-to-uplink switching set by the upper layer signaling and is an unusable symbol, or is a symbol pattern indication information field with 1 bit set in the DCI provided by the base station and is an unusable symbol, and so on. Note that the unusable symbol in the PUSCH is not limited to only the above two types, and the above two types of unusable symbols are used only for explanation purposes.

[0221] In some embodiments, the correspondence relationship between the position of the unusable symbol defined by the protocol and the frequency hopping start position and the frequency hopping end position is that the adjacent symbol position before the position of the unusable symbol is the frequency hopping end position, and the adjacent symbol position after the position of the unusable symbol is the frequency hopping start position.

[0222] Specifically, in the embodiments of the present disclosure, the position of the unusable symbol in the PUSCH is obtained, and based on the unusable symbol position, the frequency hopping start position and the frequency hopping end position are determined.

[0223] Exemplarily, continuing to refer to FIG. 4, the adjacent symbol position before the position of the unusable symbol is the frequency hopping end position, and the adjacent symbol position after the position of the unusable symbol is the frequency hopping start position.

[0224] In some embodiments, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the slot boundary position in the PUSCH, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence relationship between the slot boundary position defined by the protocol and the frequency hopping start position and the frequency hopping end position, and the slot boundary position in the PUSCH.

[0225] Note that one radio frame is equal to ten sub - frames. One sub - frame can include a plurality of slots. Each slot can include a certain number of time - domain symbols. The slot boundary may be the boundary of the time - domain symbols included in the slot. Each slot includes two slot boundaries, and two adjacent slots have one common slot boundary.

[0226] In some embodiments, the correspondence between the slot boundary position defined by the protocol and the frequency - hopping start position is that the adjacent symbol position before the slot boundary position is the frequency - hopping end position, and the adjacent symbol position after the slot boundary position is the frequency - hopping start position.

[0227] Exemplarily, continuing to refer to FIG. 5, the adjacent symbol position before the slot boundary position is the frequency - hopping end position, and the adjacent symbol position after the slot boundary position is the frequency - hopping start position.

[0228] In some embodiments, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the slot boundary position in PUSCH and the number of bits of the second preset symbol, and determining the start and end positions of frequency - hopping based on the correspondence between the slot boundary position defined by the protocol, the number of bits of the second preset symbol, the frequency - hopping start position, and the frequency - hopping end position, and the slot boundary position and the number of bits of the second preset symbol.

[0229] In the embodiments of the present disclosure, the number of bits of the second preset symbol may be any value greater than 0 and less than the number of time - domain symbols included in the slot, and this is not specifically limited.

[0230] In some embodiments, the correspondence relationship between the slot boundary position defined by the protocol, the first preset symbol bit number, and the frequency hopping start position is such that the adjacent symbol position before the slot boundary position is the frequency hopping end position, the adjacent symbol position after the slot boundary position is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by the first preset symbol bit number is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by the first preset symbol bit number is the frequency hopping end position.

[0231] Exemplarily, referring to the attached FIG. 6, when the number of time domain symbols included in the slot is 14 and the first preset symbol is 7, the adjacent symbol position before the slot boundary position is the frequency hopping end position, the adjacent symbol position after the slot boundary position is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by 7 is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by 7 is the frequency hopping end position.

[0232] In some embodiments, determining the length of the time domain for each hop based on the protocol regulations includes obtaining the length of the time domain occupied by the transmission block, and based on the preset number of hops by the protocol, the specific calculation rule corresponding to the preset number of hops by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop, and determining the length of the time domain for each hop.

[0233] In some embodiments, the specific calculation rule corresponding to the number of hops preset by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is to determine the length of the time domain for each hop at the i-th (i = 1, 2, …, N - 1) hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop at the N-th hop as L - floor(L / N)*(N - 1).

[0234] In some embodiments, the specific calculation rule corresponding to the number of hops preset by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is to determine the length of the time domain for each hop at the i-th (i = 1, 2, …, N - L + floor(L / N)*N) hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop at the i-th (i = 1 + N - L + floor(L / N)*N, …, N) hop as ceil(L / N).

[0235] In some embodiments, determining the length of the time domain for each hop includes determining the length of the time domain for each hop based on the settings of the base station.

[0236] In the embodiments of the present disclosure, the length of the time domain for each hop can be determined according to the settings of the base station.

[0237] In some embodiments, determining the length of the time domain for each hop based on the settings of the base station includes obtaining a fourth preset value set by the base station, where the fourth preset value is greater than or equal to 2, and determining the fourth preset value as the length of the time domain for each hop.

[0238] Exemplarily, when the protocol stipulates that the fourth preset value is 2, the length of the time domain per hop is 2. Naturally, the protocol may stipulate that the fourth preset value is another integer greater than 2, and the present disclosure is not limited thereto.

[0239] In some embodiments, obtaining the fourth preset value set by the base station includes receiving the fourth preset value transmitted via the remaining minimum system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling by the base station.

[0240] In an embodiment of the present disclosure, first, the fourth preset value transmitted via the remaining minimum system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling by the base station is received.

[0241] In some embodiments, receiving the fourth preset value indicated via downlink control information (DCI) signaling by the base station includes obtaining the fourth preset value transmitted by multiplexing some or all of the bits of the modulation and coding scheme (MCS) field or transmission power control (TPC) field of the downlink control information (DCI) via downlink control information (DCI) signaling by the base station, or the fourth preset value transmitted by adding a new field via downlink control information (DCI) signaling by the base station.

[0242] In some embodiments, determining the length of the time domain per hop based on the settings of the base station includes receiving one second parameter value within the second parameter set indicated by the base station and determining the second parameter value as the number of hops.

[0243] In some embodiments, obtaining one second parameter value within a second parameter set instructed by a base station includes receiving the second parameter set configured by the base station via remaining master system information (RMSI) or radio resource control (RRC) signaling, and receiving one second parameter value within the second parameter set instructed by the base station via downlink control information (DCI) or media access control layer control element (MAC CE) signaling.

[0244] In some embodiments, receiving a first parameter value within a first parameter set transmitted from a base station includes receiving a second parameter set carried in one field added to a modulation and coding scheme (MCS) table or a time domain resource allocation (TDRA) table by the base station, and receiving one second parameter value within the second parameter set transmitted by multiplexing a modulation and coding scheme (MCS) field of downlink control information (DCI) via downlink control information (DCI) signaling by the base station.

[0245] In some embodiments, determining the length of a time domain for each hop based on the configuration of a base station includes obtaining the length of the time domain occupied by a transport block, and determining the length of the time domain for each hop based on the number of hops configured by the base station, a specific calculation rule corresponding to the number of length hops configured by the base station, the length of the time domain occupied by the transport block, and the time domain for each hop, and the length of the time domain occupied by the transport block.

[0246] In some embodiments, the specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transmission block, and the time domain per hop is to determine the length of the time domain per hop in the i (i = 1, 2, …, N - 1) - th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain per hop in the N - th hop as L - floor(L / N) * (N - 1).

[0247] In some embodiments, the specific calculation rule corresponding to the number of length hops set by the base station, the length of the time domain occupied by the transmission block, and the time domain per hop is to determine the length of the time domain per hop in the i (i = 1, 2, …, N - L + floor(L / N) * N) - th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain per hop in the i (i = 1 + N - L + floor(L / N) * N, …, N) - th hop as ceil(L / N).

[0248] In some embodiments, the frequency hopping mode of PUSCH is intra - slot frequency hopping, or inter - slot frequency hopping, or intra - transmission - block frequency hopping, or inter - retransmission frequency hopping, or inter - retransmission - interval frequency hopping.

[0249] Here, the frequency hopping mode of PUSCH may be intra - slot frequency hopping or inter - slot frequency hopping or intra - transmission - block frequency hopping (Frequency Hopping, intra - TB FH), or inter - retransmission - interval frequency hopping (Inter - repettion FH for TBoMS with repetition), or intra - retransmission frequency hopping (Intra - repetition FH( for TBoMS with repetition)).

[0250] Here, Intra-slot Frequency Hopping (Intra-slot FH) means that the frequency domain resources for information transmission can change according to a predetermined rule within a slot, and one slot of Intra-slot Frequency Hopping permits two or more different frequency hopping center frequency points. Exemplarily, in the embodiments of the present disclosure, it is described by taking an example that each slot includes 14 time domain symbols and one slot includes two frequency hops. As shown in FIG. 7, one slot is included in the time domain, two frequency domain resources f1 and f2 are included in the frequency domain, the information transmitted from the transmitting end includes two parts, i.e., the first partial information and the second partial information. The transmitting end transmits the first partial information using the second frequency domain resource f2 from symbol 6 to symbol 9, and transmits the second partial information using the frequency domain resource f1 from symbol 10 to symbol 13.

[0251] Inter-slot Frequency Hopping (Inter-slot FH) means that the frequency domain resources for information transmission are constant within a slot, but the frequency domain resources for information transmission change according to a predetermined rule between different slots. Exemplarily, in the embodiments of the present disclosure, it is described by taking an example that each slot includes 14 time domain symbols. As shown in FIG. 8, two slots are included in the time domain, each slot includes 14 symbols, and two frequency domain resources fl and f2 are included in the frequency domain. The transmitting end transmits data using the frequency domain resource fl in the first slot, and transmits data using the frequency domain resource f2 in the second slot.

[0252] It should be noted that the frequency hopping within the transmission block, the frequency hopping within retransmission, and the frequency hopping between retransmissions are similar to the methods of inter-slot frequency hopping and intra-slot frequency hopping, and the description thereof is omitted here.

[0253] In some embodiments, performing frequency hopping based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing intra-slot frequency hopping and performing frequency hopping based on the number of hops determined by the method described in some of the above embodiments within the slot or the length of the time domain for each hop determined by the method described in some of the above embodiments within the slot.

[0254] In addition, in the embodiments of the present disclosure, after obtaining that the frequency hopping pattern is intra-slot frequency hopping, the number of hops of the intra-slot frequency hopping is determined by the method for determining the number of hops in some of the above embodiments within the slot, and the number of time domain symbols included in the slot is divided by the number of hops of the frequency hopping to obtain the length of the time domain for each hop. In this way, the terminal device can perform frequency hopping based on the number of hops of the intra-slot frequency hopping and the length of the time domain for each hop. Alternatively, after obtaining that the frequency hopping pattern is intra-slot frequency hopping, the length of the time domain for each hop within the slot is determined by the method for determining the length of the time domain for each hop in some of the above embodiments within the slot, and the number of time domain symbols included in the slot is divided by the length of the time domain for each hop to obtain the number of hops. In this way, the terminal device can perform frequency hopping based on the number of hops or the length of the time domain for each hop by the intra-slot frequency hopping pattern.

[0255] In the embodiments of the present disclosure, the scheme for determining the number of hops or the scheme for determining the length of the time domain for each hop can refer to the descriptions of some of the above embodiments, and the descriptions are omitted here.

[0256] In some embodiments, performing frequency hopping based on the frequency hopping pattern of PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing inter-slot frequency hopping and performing frequency hopping based on the number of hops determined by the method described in some of the above embodiments within a slot and the length of the time domain for each hop determined by the method described in some of the above embodiments within a slot.

[0257] In addition, in the embodiments of the present disclosure, after obtaining that the frequency hopping pattern is inter-slot frequency hopping, the number of hops of the inter-slot frequency hopping can be determined by the method for determining the number of hops in some of the above embodiments between slots, and after obtaining that the frequency hopping pattern is inter-slot frequency hopping, the length of the time domain for each hop between slots can be determined by the method for determining the length of the time domain for each hop in some of the above embodiments between slots. After obtaining the number of hops and the length of the time domain for each hop of the inter-slot frequency hopping, the terminal device can perform frequency hopping based on the number of hops and the length of the time domain for each hop of the frequency hopping in accordance with the inter-slot frequency hopping pattern.

[0258] In the embodiments of the present disclosure, the scheme for determining the number of hops and the scheme for determining the length of the time domain for each hop can refer to the descriptions of some of the above embodiments, and the descriptions are omitted here.

[0259] In some embodiments, performing frequency hopping based on the frequency hopping pattern of PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing intra-transmission-block frequency hopping and performing frequency hopping based on the number of hops determined by the method described in some of the above embodiments within the transmission block or the length of the time domain for each hop determined by the method described in some of the above embodiments within the transmission block.

[0260] In the embodiments of the present disclosure, after obtaining that the frequency hopping method is intra-transmission block frequency hopping, the number of hops of the intra-transmission block frequency hopping is determined by the method for determining the number of hops in some of the above embodiments within the transmission block, and the number of time domain symbols included in the transmission block is divided by the number of hops of the frequency hopping to obtain the length of the time domain per hop. In this way, the terminal device can perform frequency hopping based on the number of hops of the frequency hopping or the length of the time domain per hop in the manner of transmission block frequency hopping. Alternatively, after obtaining that the frequency hopping method is intra-transmission block frequency hopping, the length of the time domain per hop within the transmission block is determined by the method for determining the length of the time domain per hop in some of the above embodiments within the transmission block, and the number of time domain symbols included in the transmission block is divided by the length of the time domain per hop to obtain the number of hops of the frequency hopping. In this way, the terminal device can perform frequency hopping based on the number of hops or the length of the time domain per hop in the manner of intra-transmission block frequency hopping.

[0261] In the embodiments of the present disclosure, the scheme for determining the number of hops or the scheme for determining the length of the time domain per hop can refer to the descriptions of some of the above embodiments, and the descriptions are omitted here.

[0262] In some embodiments, performing frequency hopping based on the frequency hopping method of PUSCH and the number of hops and / or the length of the time domain per hop includes performing frequency hopping based on the intra-redundancy copy frequency hopping and the number of hops determined by the method described in some of the above embodiments within the redundancy copy or the length of the time domain per hop determined by the method described in some of the above embodiments within the redundancy copy.

[0263] In the embodiments of the present disclosure, after obtaining that the frequency hopping method is intra - retransmission - copy frequency hopping, the number of hops of the intra - retransmission - copy frequency hopping is determined by the method for determining the number of hops in some of the above - mentioned embodiments within the retransmission copy, and the number of time - domain symbols included in the retransmission copy is divided by the number of hops of the frequency hopping to obtain the length of the time domain per hop. Thus, the terminal device can perform frequency hopping according to the intra - retransmission - copy frequency hopping method based on the number of hops of the frequency hopping or the length of the time domain per hop. Alternatively, after obtaining that the frequency hopping method is intra - retransmission - copy frequency hopping, the length of the time domain per hop within the retransmission copy is determined by the method for determining the length of the time domain per hop in some of the above - mentioned embodiments within the retransmission copy, and the number of time - domain symbols included in the retransmission copy is divided by the length of the time domain per hop to obtain the number of hops of the frequency hopping. Thus, the terminal device can perform frequency hopping according to the intra - retransmission - copy frequency hopping method based on the number of hops or the length of the time domain per hop.

[0264] In the embodiments of the present disclosure, the scheme for determining the number of hops or the scheme for determining the length of the time domain per hop can refer to the descriptions of some of the above - mentioned embodiments, and the descriptions are omitted here.

[0265] In some embodiments, performing frequency hopping based on the frequency hopping method of PUSCH, the number of hops, and / or the length of the time domain per hop includes performing frequency hopping based on inter - retransmission - copy frequency hopping, the number of hops determined by the method described in some of the above - mentioned embodiments, and the length of the time domain per hop determined by the method described in some of the above - mentioned embodiments.

[0266] In addition, in the embodiments of the present disclosure, after it is obtained that the frequency hopping method is the frequency hopping between retransmission copies, the number of hops in some of the above embodiments between retransmission copies can be determined by the method for determining the number of hops, and after it is obtained that the frequency hopping method is the frequency hopping between retransmission copies, the length of the time domain for each hop in some of the above embodiments between retransmission copies can be determined by the method for determining the length of the time domain for each hop, and after the number of hops and the length of the time domain for each hop of the frequency hopping between retransmission copies are obtained, the terminal device can perform frequency hopping according to the frequency hopping method between retransmission copies based on the number of hops of the frequency hopping and the length of the time domain for each hop.

[0267] In the embodiments of the present disclosure, the scheme for determining the number of hops and the scheme for determining the length of the time domain for each hop can refer to the descriptions of some of the above embodiments, and the descriptions are omitted here.

[0268] In some embodiments, each hop in frequency hopping includes a demodulation reference signal (DMRS) symbol.

[0269] Here, each hop in frequency hopping includes a demodulation reference signal (DMRS) symbol for the terminal device to determine the channel quality.

[0270] In some embodiments, responding to the fact that the frequency hopping of the physical uplink shared channel (PUSCH) becomes effective includes that the frequency hopping method of the physical uplink shared channel (PUSCH) becomes effective in response to a frequency hopping instruction carried through radio resource control (RRC), or remaining system information (RMSI) of scheduling, or media access control layer control element (MAC CE), or downlink control information (DCI) signaling by the base station.

[0271] FIG. 9 is a schematic flowchart of another frequency hopping method provided by an embodiment of the present disclosure. This method is executed by a base station. As shown in FIG. 9, this method can include, but is not limited to, the following steps.

[0272] In S10, in response to the frequency hopping mode of the Physical Uplink Shared Channel (PUSCH) becoming effective, determine the number of hops of the UE and / or the length of the time domain for each hop. Here, the transmission mode of the PUSCH is the processing of transmission blocks in multiple slots. In S20, perform frequency hopping on the UE based on the frequency hopping mode of the PUSCH and the number of hops and / or the length of the time domain for each hop.

[0273] In some embodiments, determining the number of hops includes determining the number of hops based on protocol specifications.

[0274] In some embodiments, determining the number of hops based on protocol specifications includes obtaining a fifth preset value defined by the protocol, where the fifth preset value is 2 or more, and determining the fifth preset value as the number of hops.

[0275] In some embodiments, determining the number of hops based on protocol specifications includes obtaining the length of the time domain occupied by the transmission block, and determining the number of hops based on the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the number of hops, and the length of the time domain occupied by the transmission block.

[0276] In some embodiments, determining the number of hops based on protocol specifications includes obtaining the number of settings of the Demodulation Reference Signal (DMRS) in the PUSCH, and determining the number of hops based on the correspondence between the number of settings of the DMRS defined by the protocol and the number of hops, and the number of settings of the DMRS in the PUSCH.

[0277] In some embodiments, determining the number of hops based on protocol regulations includes obtaining the length of the time domain occupied by the transmission block, the length of the time domain for each hop defined by the protocol, the correspondence between the length of the time domain for each hop defined by the protocol, the length of the time domain occupied by the transmission block, and the number of hops, and determining the number of hops based on the length of the time domain occupied by the transmission block.

[0278] In some embodiments, the correspondence between the length of the time domain for each hop defined by the protocol, the length of the time domain occupied by the transmission block, and the number of hops is that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain for each hop.

[0279] In some embodiments, determining the number of hops based on protocol regulations includes obtaining the positions of the unusable symbols in the PUSCH, the fact that the unusable symbols cannot be used for data transmission, the correspondence between the positions of the unusable symbols defined by the protocol and the frequency hopping start position and the frequency hopping end position, and determining the frequency hopping start position and the frequency hopping end position based on the positions of the unusable symbols in the PUSCH.

[0280] In some embodiments, the correspondence between the positions of the unusable symbols defined by the protocol and the frequency hopping start position and the frequency hopping end position is that the adjacent symbol position before the position of the unusable symbol is the frequency hopping end position, and the adjacent symbol position after the position of the unusable symbol is the frequency hopping start position.

[0281] In some embodiments, determining the number of hops based on protocol regulations includes obtaining the slot boundary position in PUSCH, the correspondence between the slot boundary position defined by the protocol and the frequency hopping start position and the frequency hopping end position, and determining the frequency hopping start position and the frequency hopping end position based on the slot boundary position in PUSCH.

[0282] In some embodiments, the correspondence between the slot boundary position defined by the protocol and the frequency hopping start position is that the adjacent symbol position before the slot boundary position is the frequency hopping end position, and the adjacent symbol position after the slot boundary position is the frequency hopping start position.

[0283] In some embodiments, determining the number of hops based on protocol regulations includes obtaining the slot boundary position in PUSCH and the third preset symbol bit number, the correspondence between the slot boundary position defined by the protocol, the third preset symbol bit number, the frequency hopping start position and the frequency hopping end position, and determining the frequency hopping start position and the frequency hopping end position based on the slot boundary position and the third preset symbol bit number.

[0284] In some embodiments, the correspondence between the slot boundary position defined by the protocol, the first preset symbol bit number, and the frequency hopping start position is that the adjacent symbol position before the slot boundary position is the frequency hopping end position, the adjacent symbol position after the slot boundary position is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by the first preset symbol bit number is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by the first preset symbol bit number is the frequency hopping end position.

[0285] In some embodiments, determining the number of hops includes determining the number of hops based on the base station configuration.

[0286] In some embodiments, determining the number of hops based on the base station configuration includes setting a sixth pre-set value to the UE, where the sixth pre-set value is 2 or more, and determining the sixth pre-set value as the number of hops.

[0287] In some embodiments, setting the sixth pre-set value to the UE includes instructing the sixth pre-set value by setting scheduling remaining system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling to the UE.

[0288] In some embodiments, instructing the sixth pre-set value by setting downlink control information (DCI) signaling to the UE includes setting downlink control information (DCI) signaling to the UE and instructing the sixth pre-set value by multiplexing some or all bits of the modulation and coding scheme (MCS) field or the transmission power control (TPC) field of the downlink control information (DCI), or instructing the sixth pre-set value by adding a new field.

[0289] In some embodiments, determining the number of hops based on the base station configuration includes setting one third parameter value within the indicated third parameter set to the UE and determining the first parameter value as the number of hops.

[0290] In some embodiments, setting, for a UE, one third parameter value within an indicated third parameter set includes transmitting to the UE a third parameter set set by remaining master information block (RMSI) scheduling or radio resource control (RRC) signaling, and transmitting to the UE one third parameter value within the third parameter set indicated by downlink control information (DCI) or media access control layer control element (MAC CE) signaling.

[0291] In some embodiments, setting, for a UE, a third parameter value within an indicated third parameter set includes transmitting to the UE a modulation and coding scheme (MCS) table or a time domain resource allocation (TDRA) table with three additional fields for carrying the third parameter set, and transmitting downlink control information (DCI) signaling to a base station to indicate, by multiplexing a modulation and coding scheme (MCS) field of the downlink control information (DCI), one third parameter value within the third parameter set.

[0292] In some embodiments, determining the number of hops based on a base station setting includes obtaining a length of a time domain resource occupied by a transport block, and determining the number of hops based on a length of a time domain per hop set by the base station, a specific calculation rule corresponding to the length of the time domain per hop set by the base station, the length of the time domain occupied by the transport block, and the length of the time domain occupied by the transport block.

[0293] In some embodiments, determining the length of a time domain per hop includes determining the length of a time domain per hop based on protocol specifications.

[0294] In some embodiments, determining the length of the time domain for each hop based on protocol specifications includes obtaining a seventh preset value defined by the protocol, where the seventh preset value is an integer greater than zero, and determining the seventh preset value as the length of the time domain for each hop.

[0295] In some embodiments, determining the length of the time domain for each hop based on protocol specifications includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain for each hop based on the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the length of the time domain for each hop, and the length of the time domain occupied by the transmission block.

[0296] In some embodiments, determining the length of the time domain for each hop based on protocol specifications includes obtaining the number of settings of the demodulation reference signal (DMRS) in PUSCH, and determining the length of the time domain for each hop based on the correspondence between the number of settings of DMRS defined by the protocol and the length of the time domain for each hop, and the number of settings of DMRS in PUSCH.

[0297] In some embodiments, determining the length of the time domain for each hop based on protocol specifications includes obtaining the length of the time domain occupied by the transmission block, and determining the length of the time domain for each hop based on the number of hops defined by the protocol, the correspondence between the number of hops defined by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop, and the length of the time domain occupied by the transmission block.

[0298] In some embodiments, the correspondence between the number of hops, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is that the length of the time domain occupied by the transmission block is the product of the number of hops and the length of the time domain for each hop.

[0299] In some embodiments, determining the length of the time domain for each hop based on protocol specifications includes obtaining the positions of the unusable symbols in the PUSCH, determining that the unusable symbols cannot be used for data transmission, determining the correspondence between the positions of the unusable symbols defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and determining the frequency hopping start position and the technical position of the frequency hopping based on the positions of the unusable symbols in the PUSCH.

[0300] In some embodiments, the correspondence between the positions of the unusable symbols defined by the protocol, the frequency hopping start position, and the frequency hopping end position is such that the adjacent symbol position before the position of the unusable symbol is the frequency hopping end position, and the adjacent symbol position after the position of the unusable symbol is the frequency hopping start position.

[0301] In some embodiments, determining the length of the time domain for each hop based on protocol specifications includes obtaining the slot boundary position in the PUSCH, determining the correspondence between the slot boundary position defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and determining the frequency hopping start position and the frequency hopping end position based on the slot boundary position in the PUSCH.

[0302] In some embodiments, the correspondence between the slot boundary position defined by the protocol and the frequency hopping start position is such that the adjacent symbol position before the slot boundary position is the frequency hopping end position, and the adjacent symbol position after the slot boundary position is the frequency hopping start position.

[0303] In some embodiments, determining the length of the time domain for each hop based on protocol regulations includes obtaining the slot boundary position in PUSCH and the number of bits of the fourth preset symbol, and determining the frequency hopping start position and the frequency hopping end position based on the correspondence between the slot boundary position and the number of bits of the fourth preset symbol defined by the protocol, and the frequency hopping start position and the frequency hopping end position.

[0304] In some embodiments, the correspondence between the slot boundary position and the number of bits of the fourth preset symbol defined by the protocol, and the frequency hopping start position and the frequency hopping end position is that the adjacent symbol position before the slot boundary position is the frequency hopping end position, the adjacent symbol position after the slot boundary position is the frequency hopping start position, the symbol position before the slot boundary position and separated from the slot boundary position by the number of bits of the fourth preset symbol is the frequency hopping start position, and the symbol position after the slot boundary position and separated from the slot boundary position by the number of bits of the fourth preset symbol is the frequency hopping end position.

[0305] In some embodiments, determining the length of the time domain for each hop based on protocol regulations includes obtaining the length of the time domain occupied by the transport block, and determining the length of the time domain for each hop based on the preset number of hops defined by the protocol, the specific calculation rule corresponding to the preset number of hops defined by the protocol, the length of the time domain occupied by the transport block, and the length of the time domain for each hop.

[0306] In some embodiments, the specific calculation rule corresponding to the number of hops preset by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is to determine the length of the time domain for each hop at the i (i = 1, 2, …, N - 1) -th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop at the N -th hop as L - floor(L / N) * (N - 1).

[0307] In some embodiments, the specific calculation rule corresponding to the number of hops preset by the protocol, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is to determine the length of the time domain for each hop at the i (i = 1, 2, …, N - L + floor(L / N) * N) -th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop at the i (i = 1 + N - L + floor(L / N) * N, …, N) -th hop as ceil(L / N).

[0308] In some embodiments, determining the length of the time domain for each hop includes determining the length of the time domain for each hop based on the setting of the base station.

[0309] In some embodiments, determining the length of the time domain for each hop based on the setting of the base station includes setting a fourth preset value to the UE, where the eighth preset value is 2 or more, and determining the eighth preset value as the length of the time domain for each hop.

[0310] In some embodiments, setting the eighth preset value for the UE includes indicating the eighth preset value by setting scheduling remaining system information (RMSI) or radio resource control (RRC) or downlink control information (DCI) or media access control layer control element (MAC CE) signaling for the UE.

[0311] In some embodiments, indicating the eighth preset value by setting downlink control information (DCI) signaling for the UE includes setting downlink control information (DCI) signaling for the UE and indicating the eighth preset value by multiplexing some or all bits of the modulation and coding scheme (MCS) field or transmission power control (TPC) field of the downlink control information (DCI), or indicating the eighth preset value by adding a new field.

[0312] In some embodiments, determining the length of the time domain for each hop based on the base station settings includes setting one fourth parameter value within the indicated fourth parameter set for the UE and determining the fourth parameter value as the number of hops.

[0313] In some embodiments, setting one fourth parameter value within the indicated fourth parameter set for the UE includes transmitting the fourth parameter set set by scheduling remaining system information (RMSI) or radio resource control (RRC) signaling to the UE and transmitting one fourth parameter value within the fourth parameter set indicated by downlink control information (DCI) or media access control layer control element (MAC CE) signaling to the UE.

[0314] In some embodiments, setting the fourth parameter value in the indicated fourth parameter set for the UE involves transmitting to the UE a fourth parameter set carried in one field added to a modulation and coding scheme (MCS) table or a time domain resource allocation (TDRA) table, and transmitting downlink control information (DCI) signaling to the UE to indicate one fourth parameter value within the fourth parameter set by multiplexing the modulation and coding scheme (MCS) field of the downlink control information (DCI).

[0315] In some embodiments, determining the time domain length per hop based on the base station settings involves obtaining the time domain length occupied by the transport block, and determining the time domain length per hop based on the number of hops set by the base station, a specific calculation rule corresponding to the number of length hops set by the base station, the time domain length occupied by the transport block, and the time domain per hop, and the time domain length occupied by the transport block.

[0316] In some embodiments, the specific calculation rule corresponding to the number of length hops set by the base station, the time domain length occupied by the transport block, and the time domain per hop is to determine the time domain length per hop at the i (i = 1, 2, …, N - 1) -th hop as floor(L / N), where L is the time domain length occupied by the transport block, N is an integer, and to determine the time domain length per hop at the N -th hop as L - floor(L / N)*(N - 1).

[0317] In some embodiments, the specific calculation rule corresponding to the number of hops of the length set by the base station, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is to determine the length of the time domain for each hop in the i (i = 1, 2, …, N - L + floor(L / N)*N) -th hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and to determine the length of the time domain for each hop in the i (i = 1 + N - L + floor(L / N)*N, …, N) -th hop as ceil(L / N).

[0318] In some embodiments, the frequency hopping pattern of the PUSCH is intra - slot frequency hopping, or inter - slot frequency hopping, or intra - transmission - block frequency hopping, or intra - retransmission frequency hopping, or inter - retransmission frequency hopping.

[0319] In some embodiments, performing frequency hopping on the UE based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing intra - slot frequency hopping on the UE based on the number of hops determined by the method described in some of the above embodiments within the slot and the length of the time domain for each hop determined by the method described in some of the above embodiments within the slot.

[0320] In some embodiments, performing frequency hopping on the UE based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing inter - slot frequency hopping on the UE based on the number of hops determined by the method described in some of the above embodiments and the length of the time domain for each hop determined by the method described in some of the above embodiments.

[0321] In some embodiments, performing frequency hopping on the UE based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing frequency hopping within a transport block and performing frequency hopping on the UE based on the number of hops determined by the method described in some of the above embodiments within the transport block or the length of the time domain for each hop determined by the method described in some of the above embodiments within the transport block.

[0322] In some embodiments, performing frequency hopping based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing frequency hopping within a retransmission copy and performing frequency hopping on the UE based on the number of hops determined by the method described in some of the above embodiments within the retransmission copy or the length of the time domain for each hop determined by the method described in some of the above embodiments within the retransmission copy.

[0323] In some embodiments, performing frequency hopping on the UE based on the frequency hopping pattern of the PUSCH, the number of hops, and / or the length of the time domain for each hop includes performing frequency hopping between retransmission copies and performing frequency hopping on the UE based on the number of hops determined by the method described in some of the above embodiments and the length of the time domain for each hop determined by the method described in some of the above embodiments.

[0324] In some embodiments, each hop in the frequency hopping includes a demodulation reference signal (DMRS) symbol.

[0325] In some embodiments, in response to the frequency-hopping scheme for the physical uplink shared channel (PUSCH) UE becoming effective, it includes that the frequency-hopping scheme for the physical uplink shared channel (PUSCH) UE becomes effective in response to sending a frequency-hopping indication carried in radio resource control (RRC), or remaining system information (RMSI) of scheduling, or media access control layer control element (MAC CE), or downlink control information (DCI) signaling to the UE.

[0326] In some embodiments, a transceiver module configured to determine the number of hops and / or the length of the time domain for each hop in response to the frequency-hopping scheme for the physical uplink shared channel (PUSCH) becoming effective, where the transmission scheme of the PUSCH is processing of a transmission block in multiple slots, a frequency-hopping scheme for the PUSCH, and a processing module configured to perform frequency hopping based on the number of hops and / or the length of the time domain for each hop.

[0327] The frequency-hopping method provided in the above embodiments of the present disclosure, the specific process of the corresponding steps is similar to the frequency-hopping method provided in the above several embodiments and has the same beneficial effects, so detailed description is omitted here.

[0328] FIG. 10 is a schematic configuration diagram of a communication device 100 according to another embodiment of the present disclosure. As shown in FIG. 10, the communication device 100 includes a transceiver module 101 and a processing module 102.

[0329] Here, the transceiver module is configured to determine the number of hops and / or the length of the time domain for each hop in response to the frequency-hopping scheme for the physical uplink shared channel (PUSCH) becoming effective, where the time domain resource allocation pattern of the PUSCH is processing of a transmission block in multiple slots.

[0330] The processing module is configured to perform frequency hopping based on the frequency hopping pattern of PUSCH, the number of hops, and / or the length of the time domain for each hop.

[0331] Referring to FIG. 11, FIG. 11 is a schematic configuration diagram of another communication device 1000 provided according to an embodiment of the present disclosure. The communication device 1000 may be a terminal device, or may be a chip, a chip system, or a processor that supports a network device to implement the above method, or a chip, a chip system, or a processor that supports a terminal device to implement the above method. The apparatus can be used to implement the method described in the above method embodiments. Specifically, refer to the description in the above method embodiments.

[0332] The communication device 1000 may include one or more processors 1001. The processor 1001 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor can process communication protocols and communication data, and the central processing unit can control a communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU, or a CU, etc.), execute a computer program, and process the data of the computer program.

[0333] Optionally, the communication device 1000 may further include one or more memories 1002, in which a computer program 1004 may be stored, and the processor 1001 executes the computer program 1004 so that the communication device 1000 executes the method described in the above method embodiments. Optionally, the memory 1002 may store data. The communication device 1000 and the memory 1002 may be set separately or integrated together.

[0334] Optionally, the communication device 1000 may further include a transceiver 1005 and an antenna 1006. The transceiver 1005 can be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to realize the transceiver function. The transceiver 1005 can include a receiver and a transmitter. The receiver can be referred to as a receiver or a receiving circuit, etc., and is used to realize the receiving function. The transmitter can be referred to as a transmitter or a transmitting circuit, etc., and is used to realize the transmitting function.

[0335] Optionally, the communication device 1000 may further include one or more interface circuits 1007. The interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001. The processor 1001 executes the code instructions so that the communication device 1000 executes the method described in the above method embodiments.

[0336] When the communication device 1000 is a terminal device, the transceiver 1005 executes S1 in FIG. 2, and the processor 1001 executes S2 in FIG. 2.

[0337] When the communication device 1000 is a network device, the transceiver 1005 executes S10 in FIG. 9, and the processor 1001 executes S20 in FIG. 9.

[0338] In one implementation, the processor 1001 can include a transceiver for realizing the receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, or an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for realizing the receiving and transmitting functions may be separate or integrated together. The above transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or the above transceiver circuit, interface, or interface circuit can be used for signal transmission or communication.

[0339] In one implementation, the processor 1001 can store the computer program 1003, and the computer program 1003 is executed in the processor 1001, whereby the communication device 1000 can execute the method described in the above method embodiments. The computer program 1003 can be fixed in the processor 1001. In this case, the processor 1001 can be realized by hardware.

[0340] In one implementation, the communication device 1000 can include a circuit, and the circuit can realize the functions of transmitting, receiving, or communicating in the foregoing method embodiments. The processor and transceiver described in the present disclosure can be realized in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed-signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0341] The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device in the description of the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 11. The communication device may be an independent device or a part of a large device. For example, the communication device may be any of the following (1) to (6). (1) An independent integrated circuit IC, or chip, or chip system or subsystem. (2) A set having one or more ICs, optionally, the IC set may include storage elements for storing data and computer programs. (3) ASIC, such as a Modem. (4) A module that can be embedded within other devices. (5) Receiver, terminal device, intelligent terminal device, cellular phone, wireless device, handheld, mobile unit, in-vehicle device, network device, cloud device, artificial intelligence device, etc. (6) Others.

[0342] For the case where the communication device may be a chip or a chip system, refer to the schematic diagram of the chip structure shown in FIG. 12. The chip shown in FIG. 11 includes a processor 1101 and an interface 1102. Here, the number of processors 1101 may be one or more, and the number of interfaces 1102 may be more than one.

[0343] For the case where the chip is used to realize the functions of the terminal device in the embodiments of the present disclosure, The interface 1102 executes S1 in FIG. 2, and the processor 1101 executes S2 in FIG. 2.

[0344] For the case where the chip is used to realize the functions of the network device in the embodiments of the present disclosure, The interface 1102 executes S10 in FIG. 9, and the processor 1101 executes S20 in FIG. 9.

[0345] Optionally, the chip further includes a memory 1103, and the memory 1103 is used to store necessary computer programs and data.

[0346] As will be understood by those skilled in the art, the various illustrative logical blocks and steps described in the embodiments of the present disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the particular application and the overall design requirements of the system. Those skilled in the art can implement the above-described functionality in various ways for each particular type of application, but such implementation should not be construed as exceeding the protection scope of the embodiments of the present disclosure.

[0347] The embodiments of the present disclosure further provide a communication system, which includes a communication device that is a terminal device (for example, the terminal device in the above method embodiment) and a communication device that is a network device in the embodiment of FIG. 10 described above, or the system includes a communication device that is a terminal device (for example, the terminal device in the above method embodiment) and a communication device that is a network device in the embodiment of FIG. 11 described above.

[0348] The present disclosure further provides a computer-readable storage medium storing a storage instruction, and when the instruction is executed, the functions of any one of the above method embodiments are realized.

[0349] The present disclosure further provides a computer program product, and when the computer program product is executed by a computer, the functions of any one of the above method embodiments are realized.

[0350] The beneficial effects of the above computer-readable storage medium, computer program product, and computer program are the same as the beneficial effects of the frequency hopping method described in some of the above embodiments, and the description thereof is omitted here.

[0351] In the above embodiments, all or part of them can be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of them can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of it generates the flow or functions described in the embodiments of the present disclosure. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. The computer program can be stored in a computer-readable storage medium, or can be transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device such as a server, data center, etc. that includes one or more available medium integrations. The available medium may be a magnetic medium (such as a floppy disk), an optical medium (such as a high-definition digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0352] Unless the context requires otherwise, throughout the specification and claims, the term "comprise" and other forms thereof, such as the third-person singular form "comprises" and the present participle form "comprising", shall be construed in an open, inclusive sense, i.e., "including but not limited to". In the description of the specification, terms such as "one embodiment", "some embodiments", "exemplary embodiments", "example", "specific example", or "some examples" are intended to represent that the specific features, structures, materials, or characteristics related to this embodiment or example are included in at least one embodiment or example of the present disclosure. The exemplary expressions of the above terms do not necessarily mean the same embodiment or example. It should be noted that the above specific features, structures, materials, or features may be included in any one or more embodiments or examples in any suitable manner.

[0353] As can be understood by those skilled in the art, various numerical numbers such as the first, second, etc. related to the present disclosure are for the convenience of explanation and do not limit the scope of the embodiments of the present disclosure, nor do they represent priority.

[0354] At least one of the present disclosure may be described as one or more, and the plurality may be two, three, four, or more, and is not limited in the present disclosure. In the disclosed embodiments of the present disclosure, for one technical feature, the technical features in the technical feature are distinguished by "the first", "the second", "the third", "A", "B", "C", and "D", etc., and there is no priority or size order among the technical features described by the "first", "the second", "the third", "A", "B", "C", and "D".

[0355] The correspondence relationships shown in each table in this disclosure may be set or pre - defined. The possible values of the information in each table are merely examples and may be set to other values, and this disclosure is not limited thereto. When setting the correspondence relationship between information and each parameter, it is not necessary to set all the correspondence relationships shown in each table. For example, in the tables in this disclosure, it is not necessary to set the correspondence relationship indicated by a specific row. Also, appropriate deformations and adjustments may be made based on the above - mentioned tables, such as splitting, combining, etc. The names of the parameters indicated by the titles of the above - mentioned tables may also use other names understandable to the communication device, and the possible values or display methods of those parameters may also be other possible values or display methods understandable to the communication device. When implementing the above - mentioned tables, other data structures may be used, for example, arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash maps, etc.

[0356] The pre - definition in this disclosure can be understood as definition, pre - definition, memory, pre - memory, pre - agreement, pre - setting, fixation, or pre - firing.

[0357] As those skilled in the art will understand, each unit and algorithm step described in the embodiments disclosed in this specification can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware manner or a software manner is determined by the specific application of the technical solution and design constraints. Those skilled in the art can use different methods to implement the described functions according to each specific application, but such implementation should not be understood as exceeding the scope of this disclosure.

[0358] As will be clearly understood by those skilled in the art, for the sake of convenience of description, the specific operation processes of the above - described systems, devices, and units refer to the corresponding processes of the method embodiments described above, and detailed descriptions are omitted here.

[0359] What is described above is only a specific embodiment of the present disclosure, and the protection scope of the present disclosure is not limited thereto. For those skilled in the art, any changes or replacements that can be easily conceived within the technical scope disclosed in the present disclosure should be included within the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should also be based on the protection scope of the claims.

Claims

1. A frequency hopping method, wherein the frequency hopping method is executed by a terminal device, and the frequency hopping method includes: determining a frequency hopping pattern of a Physical Uplink Shared Channel (PUSCH); determining the number of hops and the length of the time domain for each hop, wherein the transmission mode of the PUSCH is processing of a transmission block in multiple slots; performing frequency hopping based on the frequency hopping pattern of the PUSCH, the number of hops, and the length of the time domain for each hop; determining the number of hops includes determining the number of hops based on protocol specifications; determining the length of the time domain for each hop includes determining the length of the time domain for each hop based on protocol specifications; determining the length of the time domain for each hop based on the protocol specifications includes: obtaining the length of the time domain occupied by the transmission block; determining the length of the time domain for each hop based on the number of hops, a specific calculation rule corresponding to the number of hops, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop; the specific calculation rule corresponding to the number of hops, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is: determining the length of the time domain for each hop in the i-th (i = 1, 2,..., N - 1) hop as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and floor(L / N) calculates the largest integer less than or equal to L / N; determining the length of the time domain for each hop in the N-th hop as L - floor(L / N) * (N - 1); A frequency hopping method, characterized by the above.

2. Determining the number of hops based on the protocol specifications includes: obtaining the length of the time domain occupied by the transmission block; determining the number of hops based on the correspondence between the length of the time domain occupied by the transmission block specified by the protocol and the number of hops, and the length of the time domain occupied by the transmission block; The frequency hopping method according to claim 1, characterized by the above.

3. The frequency hopping method is intra-slot frequency hopping or inter-slot frequency hopping. The frequency hopping method according to claim 1, characterized in that.

4. The frequency hopping method includes: obtaining the slot boundary position in PUSCH; determining the frequency hopping start position and the frequency hopping end position based on the correspondence between the slot boundary position defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and the slot boundary position in the PUSCH. The frequency hopping method according to claim 1, characterized in that.

5. The correspondence between the slot boundary position defined by the protocol and the frequency hopping start position is that: the adjacent symbol position before the slot boundary position is the frequency hopping end position; the adjacent symbol position after the slot boundary position is the frequency hopping start position. The frequency hopping method according to claim 4, characterized in that.

6. Each hop in the frequency hopping includes a demodulation reference signal (DMRS) symbol. The frequency hopping method according to claim 1, characterized in that.

7. A frequency hopping method, wherein the frequency hopping method is executed by a base station, and the frequency hopping method includes: determining a frequency hopping method for a physical uplink shared channel (PUSCH); determining the number of hops of the UE and the length of the time domain for each hop, wherein the transmission method of the PUSCH is processing of a transmission block in multiple slots; performing frequency hopping on the UE based on the frequency hopping method of the PUSCH, the number of hops, and the length of the time domain for each hop. Determining the number of hops includes determining the number of hops based on protocol regulations. Determining the length of the time domain for each hop includes determining the length of the time domain for each hop based on protocol regulations. Determining the length of the time domain for each hop based on the protocol regulations includes: obtaining the length of the time domain occupied by the transmission block. Determining the length of the time domain for each hop based on the number of hops, a specific calculation rule corresponding to the number of hops, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop; The specific calculation rule corresponding to the number of hops, the length of the time domain occupied by the transmission block, and the length of the time domain for each hop is as follows: For the i-th (i = 1, 2,..., N - 1) hop, the length of the time domain for each hop is determined as floor(L / N), where L is the length of the time domain occupied by the transmission block, N is an integer, and floor(L / N) calculates the largest integer less than or equal to L / N; For the N-th hop, the length of the time domain for each hop is determined as L - floor(L / N) * (N - 1). A frequency hopping method characterized by the above. **Claim 8** Determining the number of hops based on the protocol specification includes: Obtaining the length of the time domain occupied by the transmission block; Determining the number of hops based on the correspondence between the length of the time domain occupied by the transmission block defined by the protocol and the number of hops, and the length of the time domain occupied by the transmission block. The frequency hopping method according to claim 7, characterized by the above. **Claim 9** The frequency hopping method is intra-slot frequency hopping or inter-slot frequency hopping. The frequency hopping method according to claim 7, characterized by the above. **Claim 10** The frequency hopping method further includes: Obtaining the slot boundary position in PUSCH; Determining the frequency hopping start position and the frequency hopping end position based on the correspondence between the slot boundary position defined by the protocol, the frequency hopping start position, and the frequency hopping end position, and the slot boundary position in PUSCH. The frequency hopping method according to claim 7, characterized by the above. **Claim 11** The correspondence between the slot boundary position defined by the protocol and the frequency hopping start position is as follows: The adjacent symbol position before the slot boundary position is the frequency hopping end position; The adjacent symbol position after the slot boundary position is the frequency hopping start position. The frequency hopping method according to claim 10, characterized in that...

12. Each hop in the frequency hopping includes a demodulation reference signal (DMRS) symbol. The frequency hopping method according to claim 7, characterized in that...

13. A communication device, comprising a processor and a memory, wherein a computer program is stored in the memory, and when the processor executes the computer program stored in the memory, the communication device is caused to execute the method according to any one of claims 1 to 12. A communication device, characterized in that...

14. A computer program, characterized in that when the computer program is executed, the method according to any one of claims 1 to 12 is realized. A computer program, characterized in that...

Images