Terminal and communication method

Abstract

To flexibly apply frequency hopping in a wireless communication system.SOLUTION: A terminal includes a receiving unit that receives, from a base station, DCI (Downlink Control Information) for scheduling a PUSCH (Physical Uplink Shared Channel) in an unlicensed band and parameters related to frequency hopping, and a transmitting unit that applies frequency hopping to the PUSCH based on the parameters and transmits the PUSCH to the base station in a plurality of RB (Resource Block) sets.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to a terminal and a communication method in a wireless communication system. [Background technology]

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1).

[0003] 3GPP (registered trademark) NR Release 17 is considering the use of a higher frequency band than previous releases (e.g., Non-Patent Document 2). For example, in the frequency band from 52.6 GHz to 71 GHz, applicable numerology including subcarrier spacing and channel bandwidth, physical layer design, and expected interference in actual wireless communications are being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V17.2.0(2022-09) [Non-patent document 2] 3GPP TS 38.306 V17.2.0(2022-09) [Non-patent document 3] 3GPP TS 38.331 V17.2.0(2022-09) Summary of the Invention [Problem to be solved by the invention]

[0005] In the newly operated frequency bands using higher frequencies than conventional bands, frequency hopping is supported when transmitting channels or signals in the uplink (UL). However, the frequency hopping method to be applied when introducing a resource block (RB) set corresponding to a carrier defined in the regulations has not been specified.

[0006] The present invention has been made in view of the above points, and makes it possible to flexibly apply frequency hopping to a wireless communication system. [Means for solving the problem]

[0007] According to the disclosed technique, there is provided a terminal including: a receiver that receives, from a base station, DCI (Downlink Control Information) for scheduling a PUSCH (Physical Uplink Shared Channel) in an unlicensed band and parameters related to frequency hopping; and a transmitter that applies frequency hopping to the PUSCH based on the parameters and transmits the PUSCH to the base station in a plurality of RB (Resource Block) sets. [Effects of the Invention]

[0008] According to the disclosed technology, frequency hopping can be flexibly applied in a wireless communication system. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of the configuration of a wireless communication system according to an embodiment of the present invention. [Figure 2] FIG. 4 is a diagram illustrating an example of a frequency range according to an embodiment of the present invention. [Figure 3] 10 is a flowchart illustrating an example of transmission according to an embodiment of the present invention. [Figure 4] FIG. 1 is a diagram showing an example (1) of frequency hopping in an embodiment of the present invention. [Figure 5] FIG. 10 is a diagram showing an example (2) of frequency hopping in the embodiment of the present invention. [Figure 6] FIG. 10 is a diagram showing an example (3) of frequency hopping in the embodiment of the present invention. [Figure 7] FIG. 10 is a diagram showing an example (4) of frequency hopping in the embodiment of the present invention. [Figure 8] FIG. 10 is a diagram showing an example (5) of frequency hopping in the embodiment of the present invention. [Figure 9] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 10] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to the embodiment of the present invention. [Figure 11] 2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. [Figure 12] FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced, a system subsequent to LTE-Advanced (e.g., NR), or a wireless LAN (Local Area Network), unless otherwise specified.

[0012] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0013] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0014] Fig. 1 is a diagram showing an example of the configuration of a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0015] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is, for example, transmitted via NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 in the downlink (DL) and receives control signals or data from the terminal 20 in the uplink (UL). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to the DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0016] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals.

[0017] Fig. 2 is a diagram showing an example of frequency bands used in a wireless communication system. In the NR specifications of 3GPP Release 15 and Release 16, operation of a frequency band of 52.6 GHz or higher is being considered. As shown in Fig. 2, the frequency range (FR) 1 currently specified for operation is a frequency band from 410 MHz to 7.125 GHz, with a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth of 5 MHz to 100 MHz.

[0018] FR2-1 is the frequency band from 24.25 GHz to 52.6 GHz, and the SCS uses 60, 120, or 240 kHz, with a bandwidth of 50 MHz to 400 MHz. As shown in Figure 12, FR2-2 may be assumed to be from 52.6 GHz to 71 GHz. It may also be assumed to support frequency bands above 71 GHz.

[0019] In order to reduce the load required for monitoring PDCCHs (Physical Downlink Control Channels) in newly operated frequency bands that use higher frequencies than conventional ones, studies are being conducted to increase the monitoring period. On the other hand, in order to ensure flexibility in scheduling even when the PDCCH monitoring period is increased, studies are being conducted to support the scheduling of multiple PDSCHs (Physical Downlink Shared Channels) or multiple PUSCHs (Physical Uplink Shared Channels) using a single DCI (Downlink Control Information).

[0020] As types of PUSCH repetition, PUSCH repetition type A and PUSCH repetition type B are supported. As shown in FIG. 4, for PUSCH repetition type A, a mapping type, SLIV, and K may be specified, and for PUSCH repetition type B, S, L, and K may be specified. Note that SLIV (Start and Length Indicator) indicates the start symbol and length, and K indicates the number of repetitions. Note that PUSCH repetition type A can be set to PUSCH mapping type A or PUSCH mapping type B. PUSCH repetition type B can be set to only PUSCH mapping type B.

[0021] Here, when a single PUSCH is scheduled by DCI format 0_1 ​​or DCI format 0_2, frequency hopping is supported in resource allocation type 1.

[0022] For PUSCH repetition type A, inter-slot frequency hopping and intra-slot frequency hopping may be supported, and for PUSCH repetition type B, inter-repetition frequency hopping and inter-slot frequency hopping may be supported.

[0023] The frequency hopping mode may be set by RRC. In the case of PUSCH repetition type A, frequency hopping may be set by the higher layer parameter frequencyHoppingDCI-0-2 for PUSCH transmission scheduled by DCI format 0_2, and frequency hopping may be set by the higher layer parameter frequencyHopping for PUSCH transmission scheduled by a DCI format other than DCI format 0_2.

[0024] In the case of PUSCH repetition type B, frequency hopping may be configured by the upper layer parameter frequencyHoppingDCI-0-2 for PUSCH transmissions scheduled by DCI format 0_2, and frequency hopping may be configured by the upper layer parameter frequencyHoppingDCI-0-1 for PUSCH transmissions scheduled by DCI format 0_1.

[0025] For a PUSCH scheduled by a DCI, whether frequency hopping is enabled or disabled is determined based on the frequency hopping field of the DCI.

[0026] In Release 16, the intra-slot hopping may divide the PUSCH into two equal parts, i.e., the first hop and the second hop. If the number of symbols in the PUSCH is odd, the second hop may be one symbol more. The inter-slot hopping may alternate between the first hop and the second hop for each slot. The inter-repetition hopping may alternate between the first hop and the second hop for each repeat transmission.

[0027] Here, since frequency hopping is not supported in resource allocation type 2 of Release 16NR-U (unlicensed), frequency hopping is not assumed when multiple PUSCH transmissions are scheduled. On the other hand, since resource allocation type 2 is not applied to PUSCH transmissions in Release 17NR 52.6-71 GHz, it is necessary to consider whether and how frequency hopping should be applied to the scheduling of multiple PUSCHs. Therefore, the following options may be applied to frequency hopping for multiple PUSCH transmissions.

[0028] Option 1) For multiple PUSCH scheduling, PUSCH frequency hopping may not be supported.

[0029] Option 2) PUSCH frequency hopping may be supported for scheduling multiple PUSCHs. Whether to apply frequency hopping may be determined based on the frequency hopping indication field of the scheduling DCI or based on a new RRC parameter, such as EnablingFrequencyHoppingMulti-Pusch.

[0030] Option 2-1) For multiple PUSCH scheduling, no additional frequency hopping parameters may be configured, i.e., existing frequency hopping parameters, such as FrequencyHopping, frequencyHoppingDCI-0-1, and frequencyHoppingDCI-0-2, may be used to indicate frequency hopping for multiple PUSCH scheduling and single PUSCH scheduling.

[0031] Option 2-1-1) Existing frequency hopping methods, i.e., inter-slot frequency hopping and intra-slot frequency hopping, may be applied to scheduling of multiple PUSCHs using a single DCI. Note that frequency hopping for repeated transmissions does not need to be considered.

[0032] When a DCI format for scheduling multiple PUSCHs schedules repeated transmission of a single PUSCH and PUSCH repetition type A is configured for the PUSCH in this DCI format, either inter-slot frequency hopping or intra-slot frequency hopping may be configured by the frequency hopping parameter. When inter-slot frequency hopping is configured, inter-slot frequency hopping is configured when multiple PUSCHs are scheduled in multiple slots, and frequency hopping may not be applied when a PUSCH is scheduled in a single slot. When intra-slot frequency hopping is configured, intra-slot frequency hopping is applied to one or more PUSCHs in one slot, and when multiple PUSCHs are scheduled in one slot, each hop may include one or more PUSCHs.

[0033] When a DCI format for scheduling multiple PUSCHs schedules repeated transmission of a single PUSCH and PUSCH repetition type B is configured for the PUSCH in this DCI format, either inter-repetition frequency hopping or inter-slot frequency hopping may be configured by the frequency hopping parameter. When inter-slot frequency hopping is configured, inter-slot frequency hopping is configured when multiple PUSCHs are scheduled in multiple slots, and RB allocation for each hop may be the same as conventional inter-slot frequency hopping. When a PUSCH is scheduled in a single slot, frequency hopping may not be applied. When inter-repetition frequency hopping is configured, frequency hopping may not be applied to the scheduling of multiple PUSCHs.

[0034] When a DCI format that schedules multiple PUSCHs does not schedule repeated transmission of a single PUSCH, either inter-slot frequency hopping or intra-slot frequency hopping may be configured by the DCI format that schedules multiple PUSCHs.

[0035] Note that the above option 2-1-1) does not affect the RRC setting specifications.

[0036] Option 2-1-2) An enhanced frequency hopping scheme, i.e., inter-PUSCH frequency hopping and / or intra-PUSCH frequency hopping, may be applied to the scheduling of multiple PUSCHs. Details will be described later. Neither inter-slot frequency hopping nor intra-slot frequency hopping may be supported, or either one or both may be supported for the scheduling of multiple PUSCHs.

[0037] When a DCI format for scheduling multiple PUSCHs schedules repeated transmission of a single PUSCH, many candidate values ​​may be set for the frequency hopping parameter. If the frequency hopping mode is not supported for scheduling multiple PUSCHs, frequency hopping may not be applied to scheduling of multiple PUSCHs. If the frequency hopping mode is not supported for scheduling of a single PUSCH, frequency hopping may not be applied to scheduling of a single PUSCH.

[0038] When PUSCH repetition type A is configured for a PUSCH scheduled by a DCI format, inter-PUSCH frequency hopping, and / or intra-PUSCH frequency hopping, and / or inter-slot frequency hopping, and / or intra-slot frequency hopping may be configurable as candidate values ​​for frequency hopping parameter configuration. When inter-PUSCH frequency hopping is configured and there is a single PUSCH, frequency hopping may not be applied.

[0039] When PUSCH repetition type B is configured for a PUSCH scheduled by a DCI format, inter-PUSCH frequency hopping, and / or intra-PUSCH frequency hopping, and / or inter-slot frequency hopping, and / or inter-repetition frequency hopping may be configurable as candidate values ​​for frequency hopping parameter configuration. When inter-PUSCH frequency hopping is configured and there is a single PUSCH, frequency hopping may not be applied. When inter-repetition frequency hopping is configured and multiple PUSCHs without repetition configured are scheduled, frequency hopping may not be applied.

[0040] If a DCI format for scheduling multiple PUSCHs does not schedule repeated transmission of a single PUSCH, candidate values ​​for frequency hopping parameter settings indicating inter-PUSCH frequency hopping, and / or intra-PUSCH frequency hopping, and / or inter-slot frequency hopping, and / or intra-slot frequency hopping may be configured by the DCI format for scheduling multiple PUSCHs.

[0041] 3 is a flowchart illustrating an example of transmission according to an embodiment of the present invention. In step S1, multiple PUSCHs are scheduled for terminal 20 by base station 10 using DCI. In the following step S2, terminal 20 applies frequency hopping to the multiple PUSCHs and transmits them to base station 10.

[0042] Fig. 4 is a diagram showing an example (1) of frequency hopping in an embodiment of the present invention. Fig. 4 shows an example of inter-slot frequency hopping. As shown in Fig. 4, hops are set alternately in slot units in the frequency range.

[0043] Fig. 5 is a diagram showing an example (2) of frequency hopping in an embodiment of the present invention. Fig. 5 shows an example of intra-slot frequency hopping. As shown in Fig. 5, hops are set alternately in half-slot units in the frequency range.

[0044] Fig. 6 is a diagram showing an example (3) of frequency hopping in an embodiment of the present invention. Fig. 6 shows an example of inter-PUSCH frequency hopping. As shown in Fig. 6, hops are set alternately in frequency ranges on a PUSCH-by-PUSCH basis.

[0045] Fig. 7 is a diagram showing an example (4) of frequency hopping in an embodiment of the present invention. Fig. 7 shows an example of frequency hopping within a PUSCH. As shown in Fig. 7, hops are set alternately in the frequency range in units of half the PUSCH.

[0046] Option 2-2) A new RRC parameter, for example, Multi-Pusch-FrequencyHopping, may be additionally configured to indicate the frequency hopping scheme to be applied to scheduling of multiple PUSCHs. Note that the existing frequency hopping parameters (for example, FrequencyHopping, frequencyHoppingDCI-01, frequencyHoppingDCI-0-2) may be configured to indicate the frequency hopping scheme to be applied to scheduling of a single PUSCH.

[0047] Option 2-2-1) An existing frequency hopping scheme may be applied to scheduling of multiple PUSCHs. Multi-Pusch-Frequency Hopping may enable inter-slot frequency hopping and intra-slot frequency hopping.

[0048] Option 2-2-2) An enhanced frequency hopping scheme may be applied to the scheduling of multiple PUSCHs. Inter-PUSCH frequency hopping and / or intra-PUSCH frequency hopping may be applied to the scheduling of multiple PUSCHs. Neither inter-slot frequency hopping nor intra-slot frequency hopping may be supported for the scheduling of multiple PUSCHs, or either one may be supported, or both may be supported. Multi-PUSCH-Frequency Hopping may configure inter-PUSCH frequency hopping, intra-PUSCH frequency hopping, inter-slot frequency hopping, and / or intra-slot frequency hopping.

[0049] In the above Option 2, if frequency hopping is supported for scheduling of multiple PUSCHs, the RB arrangement of the frequency hopping scheme that may be supported may be as follows:

[0050] When inter-slot frequency hopping is applied to multiple PUSCHs in multiple slots, the RB allocation for each hop may be the same as that of Rel-16 inter-slot frequency hopping.

[0051] When intra-slot frequency hopping is applied to multiple PUSCHs in multiple slots, the RB allocation for each hop may be the same as that for intra-slot frequency hopping in Release 16. However, this does not include the case where multiple PUSCHs are scheduled by DCI and where the multiple PUSCHs are allocated discontinuously within one slot. When multiple PUSCHs are allocated discontinuously within one slot, the interval subject to frequency hopping is from the start symbol of the first PUSCH to the end symbol of the last PUSCH.

[0052] When inter-PUSCH frequency hopping is applied to scheduling of multiple PUSCHs, the starting RB of the n-th PUSCH is given by Equation 1 below.

[0053]

number

[0054] As shown in Equation 1, even-numbered PUSCHs are hops without an offset, and odd-numbered PUSCHs are hops with an offset.

[0055] When intra-PUSCH frequency hopping is applied to multiple PUSCHs in multiple slots, the starting RBs of the first hop and the second hop are given by the following Equation 2.

[0056]

number

[0057] As shown in Equation 2, the first hop has no offset, and the second hop has an offset. The number of symbols in the first hop is shown in Equation 3 below, and the number of symbols in the second hop is shown in Equation 4.

[0058]

number

[0059]

number

[0060] In addition, N in Equation 3 and Equation 4 PUSCH,S symb is the length of the PUSCH.

[0061] Here, in NR Release 16, frequency hopping with resource allocation type 1 is supported for a single PUSCH scheduled by DCI format 0_1 ​​or 0_2. Frequency hopping may be supported as shown in 1) or 2) below.

[0062] 1) For PUSCH repetition type A, inter-slot frequency hopping and intro-slot frequency hopping are supported.

[0063] 2) For PUSCH repetition type A, inter-repetition frequency hopping and inter-slot frequency hopping are supported.

[0064] The frequency hopping mode may be set by RRC signaling. In the case of PUSCH repetition type A, frequency hopping according to the higher layer parameter frequencyHoppingDCI-0-2 (see Non-Patent Document 3) is set for PUSCH transmission scheduled by DCI format 0_2, and frequency hopping according to the higher layer parameter frequencyHopping (see Non-Patent Document 3) is set for PUSCH transmission scheduled by a DCI format other than DCI format 0_2.

[0065] In the case of PUSCH repetition type B, frequency hopping is configured by the upper layer parameter frequencyHoppingDCI-0-2 (see non-patent document 3) for PUSCH transmissions scheduled by DCI format 0_2, and frequency hopping is configured by the upper layer parameter frequencyHoppingDCI-0-1 (see non-patent document 3) for PUSCH transmissions scheduled by DCI format 0_1.

[0066] FIG. 8 is a diagram showing an example (5) of frequency hopping in an embodiment of the present invention. As shown in FIG. 8, NR Release 16 supports frequency hopping applied to SRS (Sounding Reference Signal) transmission. Note that hopping may mean transmission using different frequency domain resources as shown in FIG. 8. Note that terminal 20 may receive from base station 10 an upper layer parameter instructing frequency hopping to be applied to SRS transmission, and apply frequency hopping to SRS transmission based on the upper layer parameter. The upper layer parameter may be, for example, freqHopping (see Non-Patent Document 3).

[0067] The concept of RB (Resource Block) sets was introduced in Release 16NR-U. In the 5 GHz unlicensed band, available carriers (center frequency and bandwidth) are defined by regulations. One RB set generally corresponds to one carrier defined by regulations. Wideband operation, which operates multiple carriers defined by regulations, may also be considered. The number of RBs in an RB set may be configurable, for example.

[0068] In shared spectrum channel access operation in unlicensed bands, UL transmissions may be restricted to one RB set, e.g., in frequency hopping applied to PUSCH and SRS, each hop may be restricted to one RB set.

[0069] Unlicensed bands are also set in the 52.6 GHz-71 GHz band. However, there is no clear definition of frequency domain resources. For example, flexibility may be allowed in whether transmission is within one band, whether transmission is within one carrier, bandwidth operation, LBT operation, etc. Furthermore, new definitions may be introduced for the RB sets defined in Release 16NR-U when operating in the 52.6 GHz-71 GHz band.

[0070] In the 52.6 GHz-71 GHz band where an RB set is not defined or configured, the frequency domain resources of the PUSCH or SRS are limited to be included in one RB set. Even when frequency hopping is configured, the frequency domain resources of the PUSCH or SRS are limited to be included in one RB set. This reduces the advantages of frequency hopping, such as the effect of improving frequency domain diversity.

[0071] Therefore, when frequency hopping is configured for UL-PUSCH transmission in the 52.6 GHz-71 GHz unlicensed band, the hops of the PUSCH may be transmitted without being restricted by the RB set.

[0072] The 52.6 GHz-71 GHz band may be written as FR2-2 or simply as FR2.

[0073] An unlicensed band may be referred to as a band that operates using shared spectrum channel access, or as a shared spectrum.

[0074] The hopping of the PUSCH is transmitted without being restricted by the RB set, which may mean 1) or 2) below.

[0075] 1) The hops of the PUSCH are transmitted across multiple RB sets. For example, the RB set of hop #1 and the RB set of hop #2 may be different RB sets.

[0076] 2) The PUSCH hops are transmitted over X RB sets, where X may be defined by the specification, configured by RRC signaling, or signaled by MAC-CE or DCI.

[0077] In addition, in shared spectrum channel access only in FR1, transmission may be restricted to within one RB set even when the restriction, i.e., frequency hopping, is set.

[0078] Also, if frequency hopping is configured for UL-SRS transmission in the 52.6 GHz-71 GHz unlicensed band, the hops of the SRS may be transmitted without being restricted by the RB set.

[0079] The 52.6 GHz-71 GHz band may be written as FR2-2 or simply as FR2.

[0080] An unlicensed band may be referred to as a band that operates using shared spectrum channel access, or as a shared spectrum.

[0081] The hop of the SRS is transmitted without being restricted by the RB set, which may mean 1) or 2) shown below.

[0082] 1) The hops of the SRS are transmitted across multiple RB sets. For example, the RB set of hop #1 and the RB set of hop #2 may be different RB sets.

[0083] 2) The hops of the SRS are transmitted across X RB sets, where X may be defined by a specification, configured by RRC signaling, or signaled by MAC-CE or DCI.

[0084] In addition, in shared spectrum channel access only in FR1, transmission may be restricted to within one RB set even when the restriction, i.e., frequency hopping, is set.

[0085] Regarding frequency hopping in PUSCH repetition type A and TB transmission for multiple slots, in shared spectrum channel access operation in FR1, the UE does not need to assume that two hops of PUSCH transmission are transmitted using different RB sets.

[0086] Regarding frequency hopping in PUSCH repetition type B, in shared spectrum channel access operation in FR1, the UE does not need to assume that two hops of PUSCH transmission are transmitted using different RB sets.

[0087] Regarding frequency hopping in PUSCH repetition type A and TB transmission for multiple slots, in shared spectrum channel access operation in FR1, the UE does not need to assume that two hops of PUSCH transmission are transmitted using different RB sets. Also, regarding frequency hopping in PUSCH repetition type A and TB transmission for multiple slots, in shared spectrum channel access operation in FR2-2, if the higher layer parameter IntraCellGuardBandsPerSCS (see Non-Patent Document 3) is configured for the UL carrier and DL carrier whose SCS setting is μ, the UE does not need to assume that two hops of PUSCH transmission are transmitted using different RB sets. Note that IntraCellGuardBandsPerSCS may be a parameter that sets guard bands between RB sets when multiple RB sets are used.

[0088] Regarding frequency hopping in PUSCH repetition type A and TB transmission for multiple slots, in shared spectrum channel access operation in FR1, the UE does not need to assume that two hops of PUSCH transmission are transmitted using different RB sets. Also, regarding frequency hopping in PUSCH repetition type A and TB transmission for multiple slots, in shared spectrum channel access operation in FR2-2, if the higher layer parameter IntraCellGuardBandsPerSCS is configured for a UL carrier with an SCS setting of μ, the UE does not need to assume that two hops of PUSCH transmission are transmitted using different RB sets.

[0089] Regarding frequency hopping in SRS transmission, in shared spectrum channel access operation in FR1, the UE does not need to assume that two hops of PUSCH transmission are transmitted using different RB sets.

[0090] Regarding frequency hopping in SRS transmission, in shared spectrum channel access operation in FR2-2, if the upper layer parameter IntraCellGuardBandsPerSCS (see Non-Patent Document 3) is set for the UL carrier and DL carrier with SCS setting μ, the UE does not need to assume that two hops of SRS transmission are transmitted using different RB sets.

[0091] Regarding frequency hopping in SRS transmission, in shared spectrum channel access operation in FR2-2, if the higher layer parameter IntraCellGuardBandsPerSCS is set for a UL carrier with an SCS setting of μ, the UE does not need to assume that two hops of PUSCH transmission are transmitted using different RB sets.

[0092] Which option is used in the above embodiments may be set by higher layer parameters, may be reported as UE capabilities from terminal 20, may be defined in a specification, or may be determined based on higher layer parameters and UE capabilities.

[0093] In addition, a UE capability indicating whether or not frequency hopping for scheduling of multiple PUSCHs is supported may be defined. In addition, a UE capability indicating whether or not an enhanced frequency hopping scheme for scheduling of multiple PUSCHs is supported may be defined. A UE capability indicating whether or not a new RRC parameter indicating a frequency hopping mode for scheduling of multiple PUSCHs is supported may be defined.

[0094] A UE capability may be defined that indicates whether or not frequency hopping unrestricted by an RB set is supported. A UE capability may be defined that indicates whether or not a new RRC parameter indicating a frequency hopping mode unrestricted by an RB set is supported.

[0095] According to the above-described embodiment, when an RB set is introduced, the terminal 20 can apply frequency hopping in a highly flexible manner when transmitting a PUSCH or an SRS.

[0096] That is, frequency hopping can be flexibly applied to a wireless communication system.

[0097] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0098] <Base station 10> Fig. 9 is a diagram showing an example of the functional configuration of base station 10. As shown in Fig. 9, base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 9 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiments of the present invention.

[0099] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal wirelessly. The transmitter 110 also transmits inter-network node messages to other network nodes. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

[0100] The setting unit 130 stores in a storage device setting information that is set in advance and various setting information to be transmitted to the terminal 20, and reads out the setting information from the storage device as needed. The content of the setting information is, for example, information related to the setting of frequency hopping.

[0101] As described in the embodiments, the control unit 140 controls the setting of frequency hopping. The control unit 140 also executes scheduling. The signal transmission-related functional unit of the control unit 140 may be included in the transmitting unit 110, and the signal reception-related functional unit of the control unit 140 may be included in the receiving unit 120.

[0102] <Terminal 20> Fig. 10 is a diagram showing an example of the functional configuration of terminal 20. As shown in Fig. 10, terminal 20 has transmitting unit 210, receiving unit 220, setting unit 230, and control unit 240. The functional configuration shown in Fig. 10 is merely an example. The names of the functional divisions and functional units may be any names as long as they can execute the operations related to the embodiment of the present invention.

[0103] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. For example, the transmitter 210 transmits a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 220 receives the PSCCH, PSSCH, PSDCH, or PSBCH, and the like, from the other terminal 20.

[0104] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The setting information includes, for example, information related to the setting of frequency hopping.

[0105] As described in the embodiments, the control unit 240 controls the setting of frequency hopping. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0106] (Hardware configuration) The block diagrams (FIGS. 9 and 10) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and connected directly or indirectly (for example, by wire, wirelessly, etc.). The functional block may be realized by combining software with the one device or the multiple devices.

[0107] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0108] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 11 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0109] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0110] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0111] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0112] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 10 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0113] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0114] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0115] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0116] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0117] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0118] Furthermore, base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

[0119] Fig. 12 shows an example configuration of a vehicle 2001. As shown in Fig. 12, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0120] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0121] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0122] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0123] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0124] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0125] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0126] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0127] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0128] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0129] (Summary of the embodiment) As described above, according to the embodiments of the present invention, there is provided a terminal including: a receiver that receives, from a base station, DCI (Downlink Control Information) for scheduling a PUSCH (Physical Uplink Shared Channel) in an unlicensed band and parameters related to frequency hopping; and a transmitter that applies frequency hopping to the PUSCH based on the parameters and transmits the PUSCH to the base station in a plurality of RB (Resource Block) sets.

[0130] With the above configuration, when an RB set is introduced, terminal 20 can flexibly apply frequency hopping when transmitting a PUSCH or an SRS, i.e., frequency hopping can be flexibly applied in a wireless communication system.

[0131] The transmitter may transmit the first hop of the PUSCH and the second hop of the PUSCH in different RB sets. With this configuration, when an RB set is introduced, terminal 20 can apply frequency hopping in a highly flexible manner when transmitting a PUSCH or an SRS.

[0132] The parameter may indicate inter-slot frequency hopping, intra-slot frequency hopping, or inter-repetition frequency hopping. This configuration allows the terminal 20 to apply frequency hopping in a flexible manner when transmitting a PUSCH or SRS when an RB set is introduced.

[0133] The transmitter may not assume that the PUSCH is transmitted to the base station in multiple RB sets by applying frequency hopping to the PUSCH in a specific frequency band. This configuration allows the terminal 20 to apply frequency hopping in a highly flexible manner when transmitting a PUSCH or an SRS when an RB set is introduced.

[0134] When the parameters include a parameter for setting a guard band between RB sets, the transmitter does not need to assume that the PUSCH is transmitted to the base station in multiple RB sets by applying frequency hopping to the PUSCH. With this configuration, when an RB set is introduced, terminal 20 can apply frequency hopping in a highly flexible manner when transmitting a PUSCH or an SRS.

[0135] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a terminal performs the following procedures: receiving, from a base station, DCI (Downlink Control Information) for scheduling a PUSCH (Physical Uplink Shared Channel) in an unlicensed band and parameters related to frequency hopping; and applying frequency hopping to the PUSCH based on the parameters and transmitting the PUSCH to the base station in a plurality of RB (Resource Block) sets.

[0136] With the above configuration, when an RB set is introduced, terminal 20 can flexibly apply frequency hopping when transmitting a PUSCH or an SRS, i.e., frequency hopping can be flexibly applied in a wireless communication system.

[0137] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0138] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0139] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0140] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0141] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0142] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0143] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0144] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0145] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0146] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0147] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0148] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0149] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0150] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

[0151] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0152] In this disclosure, terms such as "base station (BS)," "radio base station," "base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0153] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0154] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0155] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0156] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0157] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be an autonomous mobile object operating based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0158] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0159] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0160] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0161] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0162] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0163] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0164] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0165] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0166] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0167] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0168] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0169] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0170] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0171] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0172] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0173] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0174] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0175] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0176] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0177] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0178] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0179] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0180] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0181] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0182] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0183] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set for the terminal 20 within one carrier.

[0184] At least one of the configured BWPs may be active, and the terminal 20 may not expect to transmit or receive a predetermined signal / channel outside the active BWP. Note that the terms "cell," "carrier," and the like in this disclosure may be read as "BWP."

[0185] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0186] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0187] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0188] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0189] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0190] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A receiving unit that receives, from a base station, DCI (Downlink Control Information) that schedules a PUSCH (Physical Uplink Shared Channel) in an unlicensed band and parameters related to frequency hopping; A terminal having a transmitter that applies frequency hopping to the PUSCH based on the parameter and transmits the PUSCH to the base station in a plurality of RB (Resource Block) sets.

2. The terminal according to claim 1 , wherein the transmitting unit transmits the first hop of the PUSCH and the second hop of the PUSCH in different RB sets.

3. 2. The terminal of claim 1, wherein the parameter indicates inter-slot frequency hopping, intra-slot frequency hopping, or inter-repetition frequency hopping.

4. The terminal according to claim 1 , wherein the transmitting unit does not assume that frequency hopping is applied to the PUSCH in a specific frequency band and that the PUSCH is transmitted to the base station in a plurality of RB sets.

5. The terminal according to claim 1, wherein the transmission unit does not assume that frequency hopping is applied to the PUSCH to transmit to the base station in multiple RB sets when the parameters include parameters for setting guard bands between RB sets.

6. A procedure for receiving, from a base station, Downlink Control Information (DCI) for scheduling a Physical Uplink Shared Channel (PUSCH) in an unlicensed band and parameters related to frequency hopping; and a procedure of applying frequency hopping to the PUSCH based on the parameter and transmitting the PUSCH to the base station in a plurality of RB (Resource Block) sets.

Images