Terminal, wireless communication system, and wireless communication method

Abstract

To appropriately operate a frequency hopping (FH) offset that is applied separately from non-SBFD in SBFD (Sub-Band non-overlapping Full Duplex).SOLUTION: A terminal 200 includes a receiving unit that receives downlink control information (DCI) including information that commonly specifies first and second FH offsets when the second FH offset applied in SBFD is applied separately from the first FH offset applied in non-SBFD, and a control unit that performs FH in SBFD using the second FH offset specified by the information included in the DCI. A second FH offset list used in SBFD is set separately from a first FH offset list used in non-SBFD, and the number of FH offsets included in the second FH offset list is smaller than the number of FH offsets included in the first FH offset list.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to a terminal, a wireless communication system, and a wireless communication method in a next-generation mobile communication system. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) has developed specifications for the 5th generation mobile communication system (also known as 5G, New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution or 6G.

[0003] For example, 3GPP Release 18 is considering an extension of the duplex method. Specifically, SBFD (Sub-Band non-overlapping Full Duplex) is proposed as a new duplex method that enables simultaneous use of the downlink (DL) and uplink (UL) within a carrier in a time division duplex (TDD) band. SBFD may also be read as XDD (Cross Division Duplex) (Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] "New WID: Evolution of NR duplex operation: Sub-band full duplex (SBFD)", RP-234035, 3GPP TSG RAN#102, 3GPP, December 2023 Summary of the Invention

[0005] Incidentally, SBFD also assumes repeated transmission of uplink signals via uplink channels such as PUSCH (Physical Uplink Shared Channel). In the repeated transmission of uplink signals, frequency hopping of the uplink signals is assumed.

[0006] Against this background, the inventors, after careful consideration, focused on cases in which frequency hopping offsets are applied separately between SBFD and Non-SBFD, and found it necessary to clarify the details of the frequency hopping offset that is set separately in SBFD from Non-SBFD.

[0007] Therefore, the present disclosure has been made to solve the above-mentioned problems, and aims to provide a terminal, a wireless communication system, and a wireless communication method that can appropriately operate frequency hopping offsets that are applied in SBFD separately from Non-SBFD.

[0008] In one aspect of the disclosure, there is provided a terminal including: a receiving unit that receives downlink control information including information that commonly specifies a first frequency hopping offset and a second frequency hopping offset when a second frequency hopping offset that is applied in a second case in which a duplex scheme capable of performing simultaneous communication of uplink and downlink signals within a time division duplex band is applied and the first frequency hopping offset is not applied; and a control unit that performs frequency hopping in the second case by using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list that is used in the second case is set separately from a first frequency hopping offset list that is used in the first case, and the number of frequency hopping offsets included in the second frequency hopping offset list is smaller than the number of frequency hopping offsets included in the first frequency hopping offset list.

[0009] An aspect of the disclosure is a wireless communication system comprising a terminal and a base station, wherein the terminal comprises: a receiving unit that receives downlink control information including information commonly specifying a first frequency hopping offset and a second frequency hopping offset when a second frequency hopping offset applied in a second case in which a duplexing scheme capable of performing simultaneous communication of uplink signals and downlink signals within a time division duplex band is applied, separately from a first frequency hopping offset applied in a first case in which the duplexing scheme is not applied; and a control unit that performs frequency hopping in the second case by using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list used in the second case is set separately from a first frequency hopping offset list used in the first case, and the number of frequency hopping offsets included in the second frequency hopping offset list is smaller than the number of frequency hopping offsets included in the first frequency hopping offset list.

[0010] An aspect of the disclosure is a wireless communication method comprising: a step of receiving downlink control information including information commonly specifying a first frequency hopping offset and a second frequency hopping offset when a second frequency hopping offset applied in a second case in which a duplex scheme capable of performing simultaneous communication of uplink and downlink signals within a time division duplex band is applied, separately from a first frequency hopping offset applied in a first case in which the duplex scheme is not applied; and a step of performing frequency hopping in the second case by using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list used in the second case is set separately from a first frequency hopping offset list used in the first case, and the number of frequency hopping offsets included in the second frequency hopping offset list is smaller than the number of frequency hopping offsets included in the first frequency hopping offset list. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing frequency ranges used in the wireless communication system 10. As shown in FIG. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Figure 4] FIG. 4 is a functional block diagram of the UE 200. [Figure 5] Figure 5 is a functional block diagram of gNB100. [Figure 6] FIG. 6 is a diagram for explaining the problem. [Figure 7] FIG. 7 is a diagram for explaining the second operation example. [Figure 8] FIG. 8 is a diagram for explaining the third operation example. [Figure 9] FIG. 9 is a diagram for explaining the third operation example. [Figure 10] FIG. 10 is a diagram for explaining the fifth operation example. [Figure 11] FIG. 11 is a diagram for explaining the fifth operation example. [Figure 12] FIG. 12 is a diagram for explaining the fifth operation example. [Figure 13] FIG. 13 is a diagram for explaining the fifth operation example. [Figure 14] FIG. 14 is a diagram for explaining the sixth operation example. [Figure 15] FIG. 15 is a diagram showing an example of the hardware configuration of gNB100 and UE200. [Figure 16] FIG. 16 is a diagram showing an example of the configuration of a vehicle 2001. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0013] (1) Overall configuration of wireless communication system 1 is a schematic diagram of the overall configuration of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE (User Equipment) 200).

[0014] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0015] The NG-RAN 20 includes a base station 100 (hereinafter, gNB 100). Note that the specific configuration of the wireless communication system 10, including the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG.

[0016] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and the 5GC may be simply referred to as a "network."

[0017] The gNB 100 is a radio base station conforming to 5G, and performs 5G radio communication with the UE 200. The gNB 100 and the UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam BM by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates on two or more transport blocks between the UE and each of two NG-RAN nodes.

[0018] The wireless communication system 10 also supports a plurality of frequency ranges (FR).

[0019] First, the wireless communication system 10 may support multiple frequency ranges (FR) as shown in Fig. 2. For example, the wireless communication system 10 supports FR1, FR2-1, and FR2-2. The frequency bands of each FR are as follows:

[0020] FR1: 410 MHz to 7.125 GHz FR2-1: 24.25 GHz to 52.6 GHz ·FR2-2: More than 52.6GHz~71GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz, and may use a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 kHz or 120 kHz (including 240 kHz), and may use a bandwidth (BW) of 50 to 400 MHz.

[0021] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0022] Furthermore, the wireless communication system 10 may also be compatible with frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 may be compatible with frequency bands exceeding 52.6 GHz up to 71 GHz or 114.25 GHz.

[0023] Second, the wireless communication system 10 may support the radio frames, subframes, and slots shown in FIG.

[0024] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). In addition to 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz, the SCS may also use 480 kHz, 960 kHz, etc.

[0025] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols or 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.

[0026] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, or a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.

[0027] (2) Functional block configuration of wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described.

[0028] First, the functional block configuration of the UE 200 will be described.

[0029] Fig. 4 is a functional block diagram of UE 200. As shown in Fig. 4, UE 200 includes radio signal transmitting / receiving unit 210, amplifier unit 220, modem unit 230, control signal / reference signal processing unit 240, encoding / decoding unit 250, data transmitting / receiving unit 260, and control unit 270.

[0030] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting / receiving unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0031] In the embodiment, the radio signal transceiver 210 may communicate with a duplex cell that can simultaneously communicate an uplink signal (hereinafter, referred to as an UL signal) and a downlink signal (hereinafter, referred to as a DL signal) within a time division duplex band. Note that a new duplex cell that can simultaneously communicate an UL signal and a DL signal may be referred to as SBFD (Sub-Band non-overlapping Full Duplex). SBFD may be read as XDD (Cross Division Duplex).

[0032] Simultaneous communication of UL signals and DL signals may be performed using specific time resources. The specific time resources are time resources to which SBFD can be applied. The specific time resources may also be interpreted as SBFD resources (SBFD symbols / slots) that are semi-statically or dynamically configured in the time direction (or the time domain). The specific time resources may also be interpreted as resources in which UL sub-band(s) and DL sub-band(s) are simultaneously configured semi-statically or dynamically in the time direction (or the time domain).

[0033] The duplex mode cell may be referred to as an SBFD operation cell. The additional cell may be referred to as an Additional PCI (Physical Cell Identifier) ​​Cell. The Additional PCI Cell may include a cell that operates in SBFD (SBFD operation cell) or a cell that does not operate in SBFD (Non-SBFD operation cell).

[0034] In the embodiment, the radio signal transmitting / receiving unit 210 may be configured as a receiving unit that receives downlink control information (DCI) including information specifying a second frequency hopping offset when a second frequency hopping offset applied in a second case in which a duplex duplex mode (SBFD) capable of performing simultaneous communication of uplink and downlink signals within a time division duplex band is applied is applied, separate from a first frequency hopping offset applied in a first case in which a duplex duplex mode (SBFD) is not applied. Hereinafter, the term "first case" may simply be read as "Non-SBFD" or "Non-SBFD symbol." The term "second case" may simply be read as "SBFD" or "SBFD symbol." The term "first frequency hopping offset" may be read as an existing frequency hopping offset or a frequency hopping offset for Non-SBFD. The term "second frequency hopping offset" may be read as a new frequency hopping offset or a frequency hopping offset for SBFD.

[0035] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0036] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100 or another gNB). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0037] The control signal / reference signal processor 240 performs processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0038] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

[0039] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0040] DMRS is a reference signal (pilot signal) known between the base station and the terminal for estimating the fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.

[0041] In addition to the DMRS and PTRS, the reference signals may include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0042] The channels include control channels and data channels, such as a PDCCH (Physical Downlink Control Channel), a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel), Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), and a Physical Broadcast Channel (PBCH).

[0043] Furthermore, the data channel includes a PDSCH (Physical Downlink Shared Channel) and a PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via the data channel. The data channel may be interpreted as a shared channel.

[0044] Here, the control signal and reference signal processor 240 may receive downlink control information (DCI). The DCI includes existing fields for storing DCI Formats, Carrier indicator (CI), BWP indicator, Frequency Domain Resource Assignment (FDRA), Time Domain Resource Assignment (TDRA), Modulation and Coding Scheme (MCS), HARQ Process Number (HPN), New Data Indicator (NDI), Redundancy Version (RV), etc.

[0045] The value stored in the DCI Format field is an information element that specifies the format of the DCI. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. The time domain resource may be identified by the value stored in the TDRA field and a default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is identified by the value stored in the MCS and an MCS table. The MCS table may be specified by an RRC message or may be determined by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ process to which the DCI is applied. The value stored in the NDI field is an information element for specifying whether the data to which the DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which the DCI is applied.

[0046] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or another gNB).

[0047] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0048] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on HARQ (Hybrid Automatic Repeat Request).

[0049] The control unit 270 controls each functional block constituting the UE 200. In the embodiment, the control unit 270 configures a control unit that performs frequency hopping in the second case using a second frequency hopping offset specified by information included in the downlink control information (DCI).

[0050] Secondly, we will explain the functional block configuration of gNB100.

[0051] Fig. 5 is a functional block diagram of the gNB 100. As shown in Fig. 5, the gNB 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0052] The receiving unit 110 receives various signals from the UE 200. The receiving unit 110 may receive an UL signal via a PUCCH or a PUSCH.

[0053] The transmitter 120 transmits various signals to the UE 200. The transmitter 120 may transmit the DL signal via the PDCCH or the PDSCH.

[0054] The receiver 110 and the transmitter 120 may communicate with the UE 200 via a SBFD operation cell that can simultaneously communicate UL signals and DL signals within the TDD band.

[0055] In an embodiment, when a second frequency hopping offset applied in an SBFD symbol is applied separately from the first frequency hopping offset applied in a non-SBFD symbol, the transmitter 120 may transmit downlink control information (DCI) including information specifying the second frequency hopping offset.

[0056] The control unit 130 controls the gNB 100. In an embodiment, the control unit 130 may assume that the terminal performs frequency hopping of the SBFD symbol based on information specifying a second frequency hopping offset included in downlink control information (DCI).

[0057] (3) Issues First, we will explain resource allocation for gNB100.

[0058] In 3GPP Releases 15, 16, and 17, the gNB 100 sets or designates "DL," "F (Flexible)," or "UL" for each symbol, as shown in the upper part of Figure 6. Simultaneous communication of DL signals and UL signals is not permitted in a certain time resource.

[0059] On the other hand, in 3GPP Release 18, as shown in the lower part of Figure 6, the gNB 100 sets or designates "DL" for symbols of certain frequency resources (e.g., sub-band(s)) and sets or designates "UL" for symbols of other frequency resources (e.g., sub-band(s)). Simultaneous communication of DL signals and UL signals is permitted in certain time resources. This method may be referred to as SBFD (Sub-Band non-overlapping Full Duplex).

[0060] Secondly, we will explain the issues related to frequency hopping of UL signals in repeated transmission of UL signals in the case of SBFD.

[0061] As shown in Figure 6, the UL sub-band for SBFD is narrower than the uplink band (UL BWP) to which SBFD is not applied because the DL sub-band is excluded from the BWP. Therefore, when the resource for repeated transmission of the uplink signal includes an SBFD symbol, if frequency hopping similar to that in the case where SBFD is not applied is applied, hopping to the DL sub-band of SBFD, etc. may be performed.

[0062] As a result of careful consideration, the inventors have noted that the UL Sub-band to which SBFD is applied is narrower than the UL BWP; Bandwidth Part to which SBFD is not applied, and have found the need to introduce a mechanism for appropriately performing frequency hopping of the uplink signal when the resource for repeated transmission of the uplink signal includes the SBFD symbol.

[0063] (4) Definitions The following explains the definitions of terms related to SBFD.

[0064] The SBFD operation cell is a cell in which the position of the SBFD sub-band in the time or frequency direction is set in the serving cell.

[0065] A non-SBFD operation cell is a cell in which no SBFD sub-bands are configured in the serving cell.

[0066] A semi-static DL slot / symbol is a slot / symbol that is configured as DL by higher layer parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

[0067] A semi-static UL slot / symbol is a slot / symbol configured as a UL by higher layer parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

[0068] A semi-static flexible slot / symbol is a slot / symbol that is configured as Flexible by the upper layer parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

[0069] A Dynamic DL slot / symbol is a slot / symbol that is set as Flexible by higher layer parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and is specified as DL by DCI Format 2_0.

[0070] A Dynamic UL slot / symbol is a slot / symbol that is set as Flexible by higher layer parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and is specified as UL by DCI Format 2_0.

[0071] A dynamic flexible slot / symbol is a slot / symbol that is set as Flexible by higher layer parameters (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and is specified as Flexible by DCI Format 2_0.

[0072] (5) Example of operation To solve the above-mentioned problems, the following operation examples may be defined. Specifically, the following mainly describes frequency hopping of UL signals (UL channels) using SBFD UL sub-bands. The UL channels may include PUCCH, PUSCH, Msg.3 PUSCH, Msg.A PUSCH, etc. Frequency hopping may be applied to repeated transmission of UL signals (UL channels).

[0073] In a repeat transmission in which one TB can be transmitted in one slot (e.g., PUSCH repetition type A), inter-slot frequency hopping and intra-slot frequency hopping may be supported. In a repeat transmission in which two or more one TBs can be transmitted in one slot (e.g., PUSCH repetition type B), inter-repetition frequency hopping and inter-slot frequency hopping may be supported.

[0074] The frequency hopping mode may be set by higher layer parameters (RRC).

[0075] For example, in PUSCH repetition type A, the frequency hopping mode for PUSCH transmission scheduled by DCI format 0_2 may be set in UE 200 by frequencyHoppingDCI-0-2. The frequency hopping mode for PUSCH transmission scheduled by DCI other than DCI format 0_2 may be set in UE 200 by frequencyHopping.

[0076] For example, in PUSCH repetition type B, the frequency hopping mode for PUSCH transmission scheduled by DCI format 0_2 may be configured in UE 200 by frequencyHoppingDCI-0-2. The frequency hopping mode for PUSCH transmission scheduled by DCI format 0_1 ​​may be configured in UE 200 by frequencyHoppingDCI-0-1.

[0077] For an UL channel scheduled by a DCI, enabling or disabling frequency hopping may be determined by a Frequency hopping field included in the DCI scheduling the UL channel.

[0078] (5.1) Example 1 In Operation Example 1, it will be explained whether or not to apply frequency hopping of a UL signal (UL channel) using the UL Sub-band of SBFD. As Operation Example 1, the following options are possible.

[0079] Option 1-1 explains the case where frequency hopping of the UL signal (UL channel) using the SBFD UL Sub-band is applied. Option 1-1 can be considered to be based on the premise that the first condition is met. For Option 1-1, the following options are possible:

[0080] In option 1-1-1, UE 200 may apply frequency hopping to the UL signal (UL channel) in the SBFD symbol. In other words, UE 200 may not apply frequency hopping in repeated transmissions spanning the SBFD symbol and the non-SBFD symbol.

[0081] In Example 1-1-1-1, UE 200 may apply intra-slot frequency hopping to PUSCH or PUCCH. In Example 1-1-1-1, the fact that the frequency hopping type is intra-slot frequency hopping may be considered an example of the first condition. The fact that the frequency hopping type is not inter-slot frequency hopping may be considered an example of the first condition.

[0082] In Example 1-1-1-2, UE 200 may apply inter-repetition frequency hopping or intra-slot frequency hopping to PUSCH or PUCCH when all resources for repeated transmission of PUSCH or PUCCH are SBFD symbols in repeated transmission of PUSCH or PUCCH. In Example 1-1-1-2, the fact that all resources for repeated transmission of PUSCH or PUCCH are SBFD symbols may be considered to be an example of the first condition.

[0083] In option 1-1-2, UE 200 may apply frequency hopping to repeated transmissions spanning SBFD symbols and non-SBFD symbols. Option 1-1-2 may be based on the premise that each resource for repeated transmissions is only SBFD symbols or only non-SBFD symbols. The fact that each resource for repeated transmissions is only SBFD symbols or only non-SBFD symbols may be considered to be an example of the first condition.

[0084] In Example 1-1-2-1, UE200 may apply inter-repetition frequency hopping or intra-slot frequency hopping to PUSCH or PUCCH when some of the resources for the repeated transmission of PUSCH or PUCCH are SBFD symbols and some of the resources for the repeated transmission of PUSCH or PUCCH are non-SBFD symbols in repeated transmission of PUSCH or PUCCH.

[0085] Option 1-2 explains the case where frequency hopping of the UL signal (UL channel) using the SBFD UL Sub-band is not applied. Option 1-2 can be considered to be based on the premise that the second condition is met. For Option 1-2, the following options are possible:

[0086] In option 1-2-1, UE 200 may not apply frequency hopping of the UL signal (UL channel) in the SBFD symbol.

[0087] In Example 1-2-1-1, when inter-slot frequency hopping or inter-repetition frequency hopping is configured for PUSCH or PUCCH and the resources of PUSCH or PUCCH are SBFD symbols, UE 200 may not apply frequency hopping. In Example 1-2-1-1, when inter-slot frequency hopping or inter-repetition frequency hopping is configured for PUSCH or PUCCH and the resources of PUSCH or PUCCH are SBFD symbols, this may be considered to be an example of the second condition.

[0088] In Example 1-2-1-2, UE 200 may not apply frequency hopping if all resources for repeated transmission of PUSCH or PUCCH are SBFD symbols, regardless of whether frequency hopping is enabled. In other words, UE 200 may not apply frequency hopping if all resources for repeated transmission of PUSCH or PUCCH are not SBFD symbols.

[0089] In option 1-2-2, UE 200 may not apply frequency hopping to repeated transmissions spanning SBFD symbols and non-SBFD symbols. Option 1-2-2 may be based on the premise that each resource for repeated transmissions is only SBFD symbols or only non-SBFD symbols.

[0090] In option 1-2-2, UE200 may perform the following operations when inter-slot frequency hopping or inter-repetition frequency hopping is configured for PUSCH or PUCCH, some resources for repeated transmission of PUSCH or PUCCH are SBFD symbols, and some resources for repeated transmission of PUSCH or PUCCH are non-SBFD symbols.

[0091] In Example 1-2-2-1, the UE 200 may not apply frequency hopping to all repeated transmissions. In Example 1-2-2-1, repeated transmissions spanning an SBFD symbol and a non-SBFD symbol may be considered to be an example of the second condition.

[0092] In Example 1-2-2-2, UE 200 may not apply frequency hopping to repeated transmission of SBFD symbols, but may apply frequency hopping to repeated transmission of non-SBFD symbols. In Example 1-2-2-2, the fact that the resources for repeated transmission are non-SBFD symbols may be considered to be an example of the first condition, and the fact that the resources for repeated transmission are SBFD symbols may be considered to be an example of the second condition.

[0093] In Example 1-2-2-3, UE 200 applies different frequency hopping between SBFD symbols and non-SBFD symbols. For example, UE 200 may apply frequency hopping using a first method to repeated transmission of SBFD symbols and a second method to repeated transmission of non-SBFD symbols. The first method may be a method described in Operation Example 2 or Operation Example 3 described below. The second method may be a method used for repeated transmission of a UL signal not using the SBFD UL sub-band (i.e., an existing method). The existing method may include a method using offsets (frequencyHoppingOffsetLists or frequencyHoppingOffsetListsDCI-0-2-r16) specified in 3GPP TS38.331. The existing method may include a resource determination method for the nth hop (n is an integer equal to or greater than 2) specified in 3GPP TS38.214.

[0094] (5.2) Example 2 In Operation Example 2, a case where frequency hopping using the UL sub-band of SBFD is applied will be described. In Operation Example 2, the frequency hopping offset will be mainly described.

[0095] In operation example 2, when applying frequency hopping to a UL signal using an SBFD UL sub-band, UE200 may apply a frequency hopping offset that is different from the frequency hopping offset applied in repeated transmission of a UL signal that does not use an SBFD UL sub-band.

[0096] The frequency hopping offset applied in repeated transmission of a UL signal that does not use the UL sub-band of SBFD may be the frequency hopping offset used in the existing method described above.

[0097] As operation example 2, the following options are possible:

[0098] Option 2-1 will be mainly described with respect to PUSCH or PUCCH. In option 2-1, the frequency hopping offset is set separately for SBFD and non-SBFD.

[0099] The frequency hopping offset configured in Non-SBFD may be an offset configured in existing higher layer parameters (e.g., frequencyHoppingOffsetLists or frequencyHoppingOffsetListsDCI-0-2-r16). The frequency hopping offset configured in SBFD may be an offset configured in new higher layer parameters (e.g., frequencyHoppingOffsetLists-sbfd-r19 and / or frequencyHoppingOffsetListsDCI-0-2-sbfd-r19).

[0100] In option 2-1, the frequency hopping offset configured for SBFD is applied to PUSCH / PUSCCH hops of SBFD symbols, and the frequency hopping offset configured for SBFD is applied to PUSCH / PUSCCH hops of non-SBFD symbols.

[0101] Option 2-2 mainly describes Msg.3 PUSCH. In Option 2-2, a new frequency hopping offset for SBFD is introduced.

[0102] For example, a new table may be introduced that defines frequency hopping for Msg.3 PUSCH in SBFD. The new table may be the table shown in Figure 7. In Figure 7, N_UL subband ^size represents the size of the UL sub-band.

[0103] In Option 2-2, when Msg. A PUSCH transmission in SBFD symbols is supported, a new table (see FIG. 7) may be used for frequency hopping of Msg. A PUSCH in SBFD symbols. The table for Mg. A PUSCH in SBFD symbols may be the same as the table for Mg. 3 PUSCH in SBFD, or may be defined separately from the table for Mg. 3 PUSCH in SBFD.

[0104] (5.3) Example 3 In Operation Example 3, a case where frequency hopping using UL sub-band of SBFD is applied will be described. In Operation Example 3, a resource determination method for the nth hop (n is an integer equal to or greater than 2) will be mainly described. The value of n may be a value that satisfies n mod 2 = 0, and may be, for example, 2, 4, 6, 8, etc.

[0105] In operation example 3, when applying frequency hopping of an UL signal using an SBFD UL sub-band, UE200 may apply a resource determination method for the nth hop (n is an integer equal to or greater than 2) that is different from the resource determination method for the nth hop that is applied in repeated transmission of an uplink signal that does not use an SBFD UL sub-band.

[0106] The resource determination method for the n-th hop applied to repeated transmission of a UL signal not using the UL sub-band of SBFD may be the resource determination method for the n-th hop used in the above-mentioned existing method.

[0107] As operation example 3, the following options are possible.

[0108] In Option 3-1, the resource of the nth hop is determined as shown in Option 1 in Figure 8. In Figure 8, nd For example, the starting position of the resource of the n-th hop is determined by the starting position of the resource of the n-1-th hop, the offset between the n-1-th hop and the n-th hop (RB offset For example, the starting position of the resource at the n-th hop is calculated by the following formula (1):

[0109]

number

[0110] Equation (1) may be used in the resource determination method for the n-th hop used in the above-mentioned existing method. However, as shown in Option 1 of FIG. nd In consideration of such a case, in Option 3-1, the gNB100 allocates resources to each hop so that the resources are not allocated to the DL sub-band. st It may be configured to set hop resources and frequency hopping parameters (such as offsets).

[0111] In Option 3-2, the resource of the nth hop is determined as shown in Option 2 of Figure 8. In Figure 8, nd For example, the starting position of the resource of the n-th hop is determined by the starting position of the resource of the n-1-th hop, the offset between the n-1-th hop and the n-th hop (RB offset For example, the starting position of the resource at the n-th hop is calculated by the following formula (2):

[0112]

number

[0113] RB UL, start N_UL represents the offset of the start RB of the UL sub-band relative to the start RB of the UL BWP. subband ^size represents the size of the UL sub-band.

[0114] In option 3-2, the range of values ​​obtained by equation (2) is as follows:

[0115]

number

[0116] In Option 3-3, the resource of the nth hop is determined as shown in Option 3 of Figure 9. In Figure 9, nd For example, the starting position of the resource of the n-th hop is determined by the starting position of the resource of the n-1-th hop, the offset between the n-1-th hop and the n-th hop (RB offset For example, the starting position of the resource at the n-th hop is calculated by the following formula (3):

[0117]

number

[0118] RB UL, start N_UL represents the offset of the start RB of the UL sub-band relative to the start RB of the UL BWP. subband ^size represents the size of the UL sub-band.

[0119] In option 3-3, the range of values ​​obtained by equation (3) is as follows:

[0120]

number

[0121] In Option 3-4, the resource of the nth hop is determined as shown in Option 4 of Figure 9. In Figure 9, nd For example, the starting position of the resource of the n-th hop is determined by the starting position of the resource of the n-1-th hop, the offset between the n-1-th hop and the n-th hop (RB offset For example, the starting position of the resource at the n-th hop is calculated by the following formula (4):

[0122]

number

[0123] RB UL, start N_UL represents the offset of the start RB of the UL sub-band relative to the start RB of the UL BWP. subband ^size represents the size of the UL sub-band.

[0124] In option 3-4, the range of values ​​obtained by equation (4) is as follows:

[0125]

number

[0126] (5.4) Example 4 In Operation Example 4, a second frequency hopping offset applied in SBFD is applied separately from the first frequency hopping offset applied in Non-SBFD, as described in Operation Example 2. In Operation Example 4, separate frequency hopping offsets are set for SBFD and Non-SBFD in a CG (Configured Grant) setting.

[0127] First, a frequency hopping offset parameter for SBFD (e.g., frequencyHoppingOffset-sbfd-r19) may be configured for rrc-ConfiguredUplinkGrant. The frequency hopping offset parameter for SBFD (e.g., frequencyHoppingOffset-sbfd-r19) may be applied to the frequency hopping of the CG PUSCH of the SBFD symbol. The frequency hopping offset parameter for SBFD may be read as a new frequency hopping offset parameter.

[0128] Second, a frequency hopping offset parameter for Non-SBFD (e.g., frequencyHoppingOffset) may be configured for rrc-ConfiguredUplinkGrant. The frequency hopping offset parameter for Non-SBFD (e.g., frequencyHoppingOffset) may be applied to the FH of the CG PUSCH of a Non-SBFD symbol. The frequency hopping offset parameter for Non-SBFD may be interpreted as replacing the existing frequency hopping offset parameter.

[0129] In operation example 4, if a frequency hopping offset parameter for SBFD is not set for the rrc-ConfiguredUplinkGrant and a frequency hopping offset parameter for Non-SBFD is set for the rrc-ConfiguredUplinkGrant, the following operation may be assumed.

[0130] In option 4-1, a frequency hopping offset parameter for Non-SBFD (eg, frequencyHoppingOffset) may be applied to the FH of the CG PUSCH of the SBFD symbol.

[0131] In option 4-2, a default value may be applied for the frequency handoff of the CG PUSCH of the SBFD symbol. The default value may be UL_SB / 2, where UL_SB may be the number of RBs in PRBs available in the UL or the number of RBs in the UL sub-band(s).

[0132] In option 4-3, FH does not need to be applied to the CG PUSCH of the SBFD symbol.

[0133] In the operation example 4, whether to apply Option 4-1 or Option 4-2 may be determined based on a new parameter (e.g., FH enabling parameter for SBFD) included in the CG configuration. For example, if a new parameter is provided, Option 4-1 or Option 4-2 may be applied, and if a new parameter is not provided, Option 4-3 may be applied.

[0134] In the fourth operational example, the frequency hopping offset parameter for SBFD may be configured only when a CG PUSCH occasion or repetition in the type 1 CG configuration is included in an SBFD symbol and a non-SBFD symbol.

[0135] In the fourth operational example, the frequency hopping offset parameter for non-SBFD in the CG configuration may be used to determine frequency hopping.

[0136] In the fourth operational example, a type 1 CG PUSCH may be assumed.

[0137] (5.5) Example 5 In the fifth operation example, as described in the second or fourth operation example, a second frequency hopping offset applied in SBFD is applied in addition to the first frequency hopping offset applied in Non-SBFD.

[0138] In operation example 5, we will focus on a case where frequency hopping offsets are applied separately between SBFD and non-SBFD, and explain the details of the frequency hopping offset that is set in SBFD separately from non-SBFD. Specifically, we will explain a case where the frequency hopping offset applied to SBFD is different from the frequency hopping offset applied to non-SBFD, as shown in Fig. 10.

[0139] In operation example 5, when a second frequency hopping offset applied in SBFD is applied separately from the first frequency hopping offset applied in Non-SBFD, UE 200 performs frequency hopping in the second case using the second frequency hopping offset specified by information included in downlink control information (DCI). As operation example 5, the following operation example is considered.

[0140] (5.5.1) Example 5-1 In operation example 5-1, as shown in Fig. 11, a frequency hopping offset list (FH offset list) common to both the first case (Non-SBFD) and the second case (SBFD) is set. In DCI, information specifying the second frequency hopping offset is separate from information specifying the first frequency hopping offset. The following options are possible for operation example 5-1.

[0141] In option 5-1-1, the information specifying the frequency hopping offset is the 2*N UL_hop For example, the information specifying the second frequency hopping offset may be 2*N UL_hop MSB bits N UL_hop The information specifying the first frequency hopping offset is 2*N UL_hop Remaining N MSB bits UL_hop Alternatively, the information specifying the first frequency hopping offset may be 2*N UL_hop MSB bits NUL_hop The information specifying the second frequency hopping offset is 2*N UL_hop Remaining N MSB bits UL_hop It may be the LSB bits.

[0142] In Option 5-1-1, N UL_hop The value (number of bits) of may be the same as the existing value. For example, if there are two values ​​in the set FH offset list, N UL_hop The value (number of bits) of may be 1. If there are four values ​​in the configured FH offset list, N UL_hop The value (number of bits) may be 2.

[0143] In option 5-1-1, the UE may assume that there are two values ​​in the configured FH offset list when a PUSCH is configured for an SBFD cell. According to this configuration, the number of DCI bits in the FDRA field is 1 / 2 the number of DCI bits in the existing N UL_hop The maximum value (maximum number of bits) of

[0144]

number

[0145] The bits provide resource allocation in the frequency domain.

[0146] In Option 5-1-1, the information specifying the first frequency hopping offset and the information specifying the second frequency hopping offset are 2*N UL_hop MSB bits N UL_hop MSB bits and 2*N UL_hop MSB bits N UL_hop Since they are represented by the LSB bits, it is possible to consider that the information specifying the first frequency hopping offset and the information specifying the second frequency hopping offset are separate.

[0147] In option 5-2-2, the information specifying the first frequency hopping offset and the information specifying the second frequency hopping offset are N included in the FDRA field. UL_hop In other words, the FDRA field is N for Non-SBFD. UL_hop N for MSB bits and SBFD UL_hop Contains the MSB bits separately.

[0148] For example, N UL_hop Let us consider a case where the value (number of bits) of is 2 bits. In other words, let us consider a case where 2 bits are used to specify the FH offset. In such a case, the information specifying the second frequency hopping offset is the 2 MSB bits, and the information specifying the first frequency hopping offset is the remaining N bits of the 2 bits. UL_hop Alternatively, the information specifying the first frequency hopping offset may be N LSB bits. UL_hop The information specifying the second frequency hopping offset is the remaining 2 bits, N UL_hop It may be the LSB bits.

[0149] In option 5-1-2, the UE sets N regardless of the size of the configured FH offset list (the number of values ​​in the FH offset list). UL_hop It may be assumed that the value (number of bits) of is 2 bits.

[0150] In option 5-1-2, when the configured FH offset list has four values, the first two values ​​may be used as FH offset candidates for the PUSCH of an SBFD symbol, and the last two values ​​may be used as FH offset candidates for the PUSCH of a non-SBFD symbol. Alternatively, when the configured FH offset list has four values, the first two values ​​may be used as FH offset candidates for the PUSCH of a non-SBFD symbol, and the last two values ​​may be used as FH offset candidates for the PUSCH of an SBFD symbol. In such a case, the FH offset indication (bit) for the SBFD PUSCH is mapped to the FH offset candidates for the PUSCH of an SBFD symbol. The FH offset indication (bit) for the non-SBFD PUSCH is mapped to the FH offset candidates for the PUSCH of a non-SBFD symbol.

[0151] Option 5-1-3 explains how to interpret the DCI bits for FH offset indication. Possible interpretations of the DCI bits for FH offset indication include separate interpretations for SBFD and Non-SBFD (first interpretation) and the existing interpretation (second interpretation). The first interpretation is the interpretation of option 5-1-1 or option 5-1-2. The first interpretation may be replaced with a new interpretation. In option 5-1-3, the following Alts are possible.

[0152] In Alt5-1-3-1, a new parameter (for example, separate-FH-offset-sbfd-r19) may be set to specify the first interpretation.

[0153] First, if a new parameter is set, the UE determines the FH offset according to the first interpretation (option 5-1-1 or option 5-1-2).

[0154] Second, if a new parameter is not configured, the UE interprets the DCI bits according to the second interpretation (existing interpretation). For example, a specified FH offset is applied to a PUSCH occasion of a non-SBFD symbol. On the other hand, the following Alts are possible for a PUSCH occasion of an SBFD symbol.

[0155] In Alt5-1-3-1-1, a specified FH offset may be applied.

[0156] In Alt5-1-3-1-2, FH may not be applied.

[0157] In Alt5-1-3-1-3, a default value may be applied. The default value may be UL_SB / 2. UL_SB may be the number of RBs in PRBs available in the UL, or the number of RBs in the UL sub-band(s).

[0158] In Alt5-1-3-2, the interpretation of DCI bits for FH offset indication may be determined based on whether the symbol type (Non-SBFD or SBFD) of the scheduled PUSCH is one symbol type or two symbol types (first criterion).The interpretation of DCI bits for FH offset indication may be determined based on whether the symbol type (Non-SBFD or SBFD) of the activated type 2 CG configuration is one symbol type or two symbol types (second criterion).

[0159] First, if the PUSCH occasion scheduled by the DCI is a non-SBFD symbol and an SBFD symbol, the UE determines the FH offset according to the first interpretation (option 5-1-1 or option 5-1-2). If the type 2 CG occasion activated by the DCI format is a non-SBFD symbol and an SBFD symbol, the UE determines the FH offset according to the first interpretation (option 5-1-1 or option 5-1-2).

[0160] Second, if one PUSCH is scheduled by DCI without repetition, the UE interprets the DCI bits according to the second interpretation (legacy interpretation). If the type 2 CG occasion or repetition activated by the DCI format is limited to one symbol type, the UE interprets the DCI bits according to the second interpretation (legacy interpretation). If the PUSCH repetition or TBoMS (Transport Block over Multi-Slots) scheduled by DCI is limited to one symbol type, the UE interprets the DCI bits according to the second interpretation (legacy interpretation). For example, a specified FH offset is applied to a PUSCH occasion of a non-SBFD symbol. On the other hand, the following Alts are possible for a PUSCH occasion of an SBFD symbol.

[0161] In Alt5-1-3-2-1, the FH offset specified by the DCI bits may be applied according to the second interpretation (existing interpretation).

[0162] In Alt5-1-3-2-2, FH may not be applied.

[0163] In Alt5-1-3-2-3, a default value may be applied. The default value may be UL_SB / 2. UL_SB may be the number of RBs in PRBs available in the UL, or the number of RBs in the UL sub-band(s).

[0164] Alt5-1-3-3 may combine Alt5-1-3-1 and Alt5-1-3-2.

[0165] For example, if a new parameter is configured and the PUSCH occasion scheduled by the DCI is a non-SBFD symbol and an SBFD symbol, the UE determines the FH offset according to the first interpretation (option 5-1-1 or option 5-1-2). Similarly, if a new parameter is configured and the type 2 CG occasion activated by the DCI format is a non-SBFD symbol and an SBFD symbol, the UE determines the FH offset according to the first interpretation (option 5-1-1 or option 5-1-2).

[0166] (5.5.2) Example 5-2 In operation example 5-2, a second frequency hopping offset list used in the second case (SBFD) is set separately from the first frequency hopping offset list used in the first case (Non-SBFD) as shown in Fig. 12. In DCI, information specifying the second frequency hopping offset is common to information specifying the first frequency hopping offset.

[0167] In operation example 5-2, the second frequency hopping offset list used in the second case (SBFD) may be configured by new higher layer parameters (e.g., frequencyHoppingOffsetLists-sbfd-r19 and / or frequencyHoppingOffsetListsDCI-0-2-sbfd-r19). The size of the second frequency hopping offset list for SBFD (the number of values ​​included in the list) may be 1, 2, or 4.

[0168] In operation example 5-2, the UE may assume that the size of the second frequency hopping offset list for SBFD is the same as the size of the second frequency hopping offset list for non-SBFD. The UE may assume that the size of the second frequency hopping offset list for SBFD is larger than the size of the second frequency hopping offset list for non-SBFD. The UE may assume that the size of the second frequency hopping offset list for SBFD is smaller than the size of the second frequency hopping offset list for non-SBFD.

[0169] In the operational example 5-2, the number of MSB bits used for the FH offset indication in the FDRA field is determined according to Alt shown below.

[0170] In Alt5-2-1, the number of MSB bits used for the FH offset indication is determined based on the maximum value between the size of the first frequency hopping offset list (the number of FH offset values) and the size of the second frequency hopping offset list (the number of FH offset values).

[0171] For example, for DCI formats 0_0 / 0_1 / 0_3, the number of MSB bits used for the FH offset indication is determined based on the maximum value between the size of frequencyHoppingOffsetLists and the size of frequencyHoppingOffsetLists-sbfd-r19.

[0172] For example, for DCI format 2_0, the number of MSB bits used for the FH offset indication is determined based on the maximum value between the size of frequencyHoppingOffsetListsDCI-0-2 and the size of frequencyHoppingOffsetListsDCI-0-2-sbfd-r19.

[0173] In Alt5-2-2, the number of MSB bits used for the FH offset indication may be the same as the number of existing MSB bits.

[0174] For example, the size of the second frequency hopping offset list may be assumed to be no larger than the size of the first frequency hopping offset list.

[0175] In the operation example 5-2, the FH offset is determined based on the corresponding DCI bits (FH offset indication) and the corresponding frequency hopping offset list.

[0176] For example, for a PUSCH occasion of an SBFD symbol, the FH offset is determined based on the DCI bits (FH offset indication) and the second frequency hopping offset list.

[0177] For example, for a PUSCH occasion of a non-SBFD symbol, the FH offset is determined based on DCI bits (FH offset indication) and the first frequency hopping offset list.

[0178] In operation example 5-2, the UE may assume only one value in the second frequency hopping offset list for SBFD and identify the FH offset for SBFD without using DCI bits (FH offset indication). In other words, the value in the second frequency hopping offset list for SBFD may be used as the FH offset for SBFD as is.

[0179] In the operational example 5-2, if the second frequency hopping offset list for SBFD is not configured, the FH offset used in the PUCCH occasion of the SBFD symbol may be determined according to the options shown below.

[0180] In option 5-2-1, the FH offset used in the PUCCH occasion of the SBFD symbol may be determined based on the first frequency hopping offset list for non-SBFD.

[0181] In option 5-2-2, the FH offset used in the PUCCH occasion of the SBFD symbol may be determined based on a list predefined in the wireless communication system 10. The predefined list may be {UL_SB / 2, UL_SB / 4}. UL_SB may be the number of RBs in PRBs available in the UL, or may be the number of RBs in the UL sub-band(s).

[0182] In option 5-2-3, the FH offset used in the PUCCH occasion of the SBFD symbol may be a default value, which may be UL_SB / 2, where UL_SB may be the number of RBs in PRBs available in the UL or the number of RBs in the UL sub-band(s).

[0183] In option 5-2-4, FH may not be applied.

[0184] In operation example 5-2, the application of FH (options 5-2-1 to 5-2-3) and non-application of FH (option 5-2-4) may be specified by the frequency hopping flag field for SBFD included in the DCI. The frequency hopping flag field for SBFD may be defined separately from the existing frequency hopping flag field. For example, when the frequency hopping flag field for SBFD is 1, FH is applied (options 5-2-1 to 5-2-3). When the frequency hopping flag field for SBFD is 0, FH is not applied (option 5-2-4).

[0185] (5.5.3) Example 5-3 In operation example 5-3, a second frequency hopping offset list used in the second case (SBFD) is set separately from the first frequency hopping offset list used in the first case (Non-SBFD) as shown in Fig. 13. In DCI, information specifying the second frequency hopping offset is separate from information specifying the first frequency hopping offset.

[0186] In operation example 5-3, the second frequency hopping offset list used in the second case (SBFD) may be configured by new higher layer parameters (e.g., frequencyHoppingOffsetLists-sbfd-r19 and / or frequencyHoppingOffsetListsDCI-0-2-sbfd-r19). The size of the second frequency hopping offset list for SBFD (the number of values ​​included in the list) may be 1, 2, or 4.

[0187] In operation example 5-3, the UE may assume that the size of the second frequency hopping offset list for SBFD is the same as the size of the second frequency hopping offset list for non-SBFD. The UE may assume that the size of the second frequency hopping offset list for SBFD is larger than the size of the second frequency hopping offset list for non-SBFD. The UE may assume that the size of the second frequency hopping offset list for SBFD is smaller than the size of the second frequency hopping offset list for non-SBFD.

[0188] In the operational example 5-3, the FH offset indication is identified in the same manner as in the operational example 5-1.

[0189] In the operation example 5-3, the FH offset is determined based on the corresponding DCI bits (FH offset indication) and the corresponding frequency hopping offset list.

[0190] For example, for a PUSCH occasion of an SBFD symbol, the FH offset is determined based on the DCI bits (FH offset indication) and the second frequency hopping offset list.

[0191] For example, for a PUSCH occasion of a non-SBFD symbol, the FH offset is determined based on DCI bits (FH offset indication) and the first frequency hopping offset list.

[0192] In operation example 5-3, the UE may assume only one value in the second frequency hopping offset list for SBFD and identify the FH offset for SBFD without using DCI bits (FH offset indication). In other words, the value in the second frequency hopping offset list for SBFD may be used as the FH offset for SBFD as is.

[0193] In the operational example 5-3, if the second frequency hopping offset list for SBFD is not configured, the FH offset used in the PUCCH occasion of the SBFD symbol may be determined according to the options shown below.

[0194] In option 5-3-1, the FH offset used in the PUCCH occasion of the SBFD symbol may be determined based on the first frequency hopping offset list for non-SBFD.

[0195] In option 5-3-2, the FH offset used in the PUCCH occasion of the SBFD symbol may be determined based on a list predefined in the wireless communication system 10. The predefined list may be {UL_SB / 2, UL_SB / 4}. UL_SB may be the number of RBs in PRBs available in the UL, or may be the number of RBs in the UL sub-band(s).

[0196] In option 5-3-3, the FH offset used in the PUCCH occasion of the SBFD symbol may be a default value, which may be UL_SB / 2, where UL_SB may be the number of RBs in PRBs available in the UL or the number of RBs in the UL sub-band(s).

[0197] In option 5-3-4, FH may not be applied.

[0198] In operation example 5-3, the application of FH (options 5-3-1 to 5-3-3) and non-application of FH (option 5-3-4) may be specified by the frequency hopping flag field for SBFD included in DCI. The frequency hopping flag field for SBFD may be defined separately from the existing frequency hopping flag field. For example, when the frequency hopping flag field for SBFD is 1, FH is applied (options 5-3-1 to 5-3-3). When the frequency hopping flag field for SBFD is 0, FH is not applied (option 5-3-4).

[0199] (5.5.4) Example 5-4 In operation example 5-4, the FH offset applied in SBFD may be determined based on a specified or configured FH offset. Alternatively, the FH offset applied in SBFD may be determined based on a default value. The following options are possible for operation example 5-4.

[0200] In option 5-4-1, the FH offset and RB offset specified or configured by the existing method are used to determine the FH offset of the SBFD symbol.

[0201] For example, the UE determines the FH offset based on the frequency hopping offset list and DCI bits (existing method). Furthermore, the UE determines (FH_offset + RB_offset) or (FH_offset - RB_offset) as the FH offset to be applied in SBFD. Here, the FH offset is the FH offset specified or configured in the existing method. The RB_offset may be configured by the RRC or may be predefined in the wireless communication system 10. The RB_offset may be UL_SB / 2. The UL_SB may be the number of RBs in PRBs available in the UL, or the number of RBs in the UL sub-band(s).

[0202] In option 5-4-1, if RB_offset is not set, the following Alts are possible:

[0203] In Alt5-4-1-1, a default value may be used as RB_offset, which may be 0 or UL_SB / 2.

[0204] In Alt5-4-1-1, FH may not be applied.

[0205] In option 5-4-2, the FH offset of the SBFD symbol may be the default value.

[0206] For example, the default value may be UL_SB / 2, where UL_SB may be the number of RBs in PRBs available in the UL, or may be the number of RBs in the UL sub-band(s).

[0207] In operation example 5-4, option 5-4-1 or option 5-4-2 may be applied to PUSCH occasion(s) in SBFD symbols and non-SBFD symbols.

[0208] For example, if one PUSCH is scheduled by DCI without repetition, the UE determines the FH offset according to an existing method. If the type 2 CG occasion or repetition activated by the DCI format is limited to one symbol type, the UE determines the FH offset according to an existing method. If the PUSCH repetition or TBoMS (Transport Block over Multi-Slots) scheduled by DCI is limited to one symbol type, the UE determines the FH offset according to an existing method.

[0209] For example, if the type 2 CG occasion or repetition activated by the DCI format is SBFD symbol and non-SBFD symbol, the UE applies option 5-4-1 or option 5-4-2. If the PUSCH repetition or TBoMS (Transport Block over Multi-Slots) scheduled by the DCI is SBFD symbol and non-SBFD symbol, the UE applies option 5-4-1 or option 5-4-2.

[0210] (5.6) Example 6 Operation example 6 may be an operation example premised on operation example 5-2 (see FIG. 12). That is, in operation example 6, a second frequency hopping offset list used in the second case (SBFD) may be set separately from the first frequency hopping offset list used in the first case (Non-SBFD). In DCI, information specifying the second frequency hopping offset may be common to information specifying the first frequency hopping offset.

[0211] In the sixth operational example, attention may be focused on a case where frequency hopping is applied to a PUSCH scheduled by DCI format 0_0 / 0_1 / 0_2 / 0_3.

[0212] In Operation Example 6, the second frequency hopping offset list used in the second case (SBFD) may be configured by new higher layer parameters (e.g., frequencyHoppingOffsetLists-sbfd-r19 and / or frequencyHoppingOffsetListsDCI-0-2-sbfd-r19). The size of the second frequency hopping offset list for SBFD (the number of values ​​included in the list) may be 1, 2, or 4.

[0213] In operation example 6, UE 200 may assume that the size of the second frequency hopping offset list for SBFD is smaller than the size of the first frequency hopping offset list for non-SBFD. In other words, UE 200 may assume that the number of second FH offsets included in the second frequency hopping offset list for SBFD is smaller than the number of second FH offsets included in the first frequency hopping offset list for non-SBFD. The bit(s) specifying the FH offset from the frequency hopping offset list may be an FH offset indication included in DCI (FDRA field).

[0214] For frequency hopping of a PUSCH occasion of a non-SBFD symbol / slot, the FH offset is specified by the FH offset indication in accordance with the existing interpretation of the FH offset indication. The existing interpretation may be interpreted as an interpretation for non-SBFD.

[0215] For frequency hopping of a PUSCH occasion of an SBFD symbol / slot, the FH offset is specified by the FH offset indication according to a new interpretation of the FH offset indication. The new interpretation may be replaced with the interpretation for SBFD. The interpretation for SBFD may be an interpretation in which the LSB bits of the FH offset indication are used as the bit(s) specifying the FH offset. The interpretation for SBFD may be an interpretation in which the MSB bits of the FH offset indication are used as the bit(s) specifying the FH offset.

[0216] For example, as shown in FIG. 14, a case will be described in which the number of FH offsets included in the first frequency hopping offset list used in the first case (Non-SBFD) is four (offset1, offset2, offset3, offset4), and the number of FH offsets included in the second frequency hopping offset list used in the second case (SBFD) is two (offset1, offset2).

[0217] In such a case, the FH offset indication included in the DCI may be expressed by 2 bits. For example, if the FH offset indication is 01, the FH offset may be determined as follows:

[0218] For frequency hopping of a PUSCH occasion with a non-SBFD symbol / slot, UE 200 determines the FH offset (=offset2) based on the FH offset indication (=01). For frequency hopping of a PUSCH occasion with an SBFD symbol / slot, UE 200 determines the FH offset (=offset2) based on the LSB (=1) of the FH offset indication.

[0219] (5.7) Example 7 Operation example 7 may be an operation example premised on operation example 2 (see FIG. 7). That is, in operation example 7, when applying frequency hopping to a UL signal using an SBFD UL sub-band, UE 200 may apply a frequency hopping offset that is different from the frequency hopping offset applied in repeated transmission of a UL signal not using an SBFD UL sub-band.

[0220] In the seventh operational example, attention may be paid to a case where frequency hopping can be applied to Msg. 3 PUSCH scheduled by a RAR (Random Access Response) UL grant.

[0221] As operation example 7, the following options are possible.

[0222] In option 7-1, frequency hopping may be disabled for Msg.3 PUSCH in SBFD symbol / slot. The following options are possible for option 7-1.

[0223] In option 7-1-1, when UE 200 detects an RAR UL grant that schedules Msg.3 PUSCH in an SBFD symbol / slot, UE 200 may assume that the frequency hopping flag field is set to 0. In option 7-1-1, the following variations are possible:

[0224] In option 7-1-1, UE 200 may assume that the frequency hopping flag field is set to 0 if it detects a RAR UL grant that schedules a Msg. 3 PUSCH without repetitive transmission in an SBFD symbol / slot.

[0225] In option 7-1-1, the UE 200 may assume that the frequency hopping flag field is set to 0 if it detects a RAR UL grant that schedules a Msg. 3 PUSCH with repeated transmissions in SBFD symbols / slots only.

[0226] In option 7-1-2, when UE 200 detects a RAR UL grant that schedules Msg. 3 PUSCH in an SBFD symbol / slot, frequency hopping may be disabled regardless of the value set in the frequency hopping flag field.

[0227] In option 7-2, one FH offset may be defined in the wireless communication system 10 as the FH offset of the Msg.3 PUSCH in the SBFD symbol / slot. One FH offset may be defined as 0, FLOOR (N_UL subband ^size / 2), FLOOR (N_UL subband ^size / 4), -FLOOR (N_UL subband ^size / 4) etc. subband ^size represents the size of the UL sub-band.

[0228] In option 7-2, the RAR field indication may not be required for the FH offset of Msg.3 PUSCH in SBFD symbol / slot.

[0229] In option 7-2, if the FH offset is 0, frequency hopping may be disabled, similar to option 7-1.

[0230] As option 7-2, the following options are possible for the RAR UL grant that schedules Msg.3 PUSCH in the SBFD symbol / slot.

[0231] In option 7-2-1, for an RAR UL grant that schedules Msg.3 PUSCH at SBFD symbol / slot, the FDRA field may be interpreted as having an FH offset indication (eg, N_UL,hop) of 0.

[0232] In option 7-2-2, for an RAR UL grant that schedules Msg.3 PUSCH in an SBFD symbol / slot, the FH offset indication (eg, N_UL,hop) may be interpreted as before.

[0233] In Option 7-2, whether to apply Option 7-2-1 or Option 7-2-2 may be determined as follows:

[0234] Which option to apply may be determined depending on whether or not the Msg.3 PUSCH in the SBFD symbol / slot involves repeated transmission. For example, if the Msg.3 PUSCH does not involve repeated transmission, option 7-2-1 may be applied. If the Msg.3 PUSCH involves repeated transmission, option 7-2-2 may be applied.

[0235] When Msg.3 PUSCH involves repeat transmission, which option to apply may be determined depending on whether the repeat transmission of Msg.3 PUSCH is included in only the SBFD symbol / slot or spans both the SBFD symbol / slot and non-SBFD symbol / slot. For example, when the repeat transmission of Msg.3 PUSCH is included in only the SBFD symbol / slot, option 7-2-1 may be applied. When the repeat transmission of Msg.3 PUSCH spans both the SBFD symbol / slot and non-SBFD symbol / slot, option 7-2-2 may be applied.

[0236] In option 7-3, multiple FH offsets may be defined separately from the non-SBFD FH offset as the FH offset of Msg.3 PUSCH in the SBFD symbol / slot (hereinafter referred to as the SBFD FH offset). The following options are possible for the number of SBFD FH offsets:

[0237] In option 7-3-1, the number of FH offsets for SBFD may be fixed to two.

[0238] In option 7-3-2, the number of FH offsets for SBFD may be 2 or 4. subband ^size may be read as the size of the UL usable PRB(s) instead of the size of the UL sub-band, and N_UL usable prb It may also be expressed as ^size.

[0239] In option 7-3-3, the number of FH offsets for SBFD may be two or four depending on the size of the UL BWP. The number of FH offsets for SBFD for the Msg.3 PUSCH may be determined based on the size of the UL BWP, similar to the number of FH offsets for non-SBFD for the Msg.3 PUSCH. For example, if the UL BWP is smaller than 50 PRBs, the number of FH offsets for SBFD for the Msg.3 PUSCH may be two. If the UL BWP is 50 PRBs or more, the number of FH offsets for SBFD for the Msg.3 PUSCH may be four.

[0240] In option 7-3, the candidate values ​​for the FH offset for SBFD are 0, FLOOR (N_UL subband ^size / 2), FLOOR (N_UL subband ^size / 4), -FLOOR (N_UL subband ^size / 4) etc. subband^size represents the size of the UL usable PRB(s).

[0241] In option 7-3, the following Alts are possible for the number of FH offset indications (for example, N_UL,hop) included in the RAR UL grant that schedules Msg.3 PUSCH in SBFD symbol / slot.

[0242] In Alt 7-3-1, for an RAR UL grant that schedules Msg.3 PUSCH at an FD symbol / slot, N_UL,hop is interpreted in the existing manner. For example, N_UL,hop is determined based on the size of the UL BWP.

[0243] In Alt 7-3-1, if the number of FH offsets for SBFD is less than the number of FH offsets corresponding to the UL BWP size, the FH offset may be determined as follows: For the Msg.3 PUSCH occasion in the SBFD symbol / slot, the FH offset may be specified by the LSB of N_UL,hop; or, for the Msg.3 PUSCH occasion in the SBFD symbol / slot, the FH offset may be specified by the MSB of N_UL,hop.

[0244] In Alt.7-3-2, for RAR UL grants that schedule Msg.3 PUSCH in FD symbols / slots, N_UL,hop is interpreted in a new way, for example, N_UL,hop is interpreted based on the number of FH offsets for SBFD.

[0245] In option 7-3, whether to use Alt 7-3-1 or Alt 7-3-2 may be determined as follows.

[0246] Which Alt to apply may be determined depending on whether or not the Msg.3 PUSCH in the SBFD symbol / slot involves repeated transmission. For example, if the Msg.3 PUSCH does not involve repeated transmission, Alt 7-3-1 may be applied. If the Msg.3 PUSCH involves repeated transmission, Alt 7-3-2 may be applied.

[0247] When Msg.3 PUSCH involves repeated transmission, which Alt to apply may be determined depending on whether the repeated transmission of Msg.3 PUSCH is included only in the SBFD symbol / slot or spans both the SBFD symbol / slot and non-SBFD symbol / slot. For example, when the repeated transmission of Msg.3 PUSCH is included only in the SBFD symbol / slot, Alt 7-3-1 may be applied. When the repeated transmission of Msg.3 PUSCH spans both the SBFD symbol / slot and non-SBFD symbol / slot, Alt 7-3-2 may be applied.

[0248] In operation example 7, option 7-1 may be applied when the number of UL usable PRB(s) is smaller than or not larger than threshold X. Option 7-2 or option 7-3 may be applied when the number of UL usable PRB(s) is larger than or not smaller than threshold X. Threshold X may be specified by the SIB or may be set by the RRC.

[0249] (5.8) Other examples of operation It is also possible to combine two or more operation examples selected from the above-described operation examples 1 to 6. In such a case, an option of one operation example may be combined with an option of another operation example.

[0250] In the above-described operational example, a new PUCCH format may be introduced for the PUCCH using the UL sub-band of SBFD. The new PUCCH format may be a format defined to include resources of the UL sub-band of SBFD but not resources of the DL sub-band of SBFD.

[0251] (6) Actions and Effects In the embodiment, the UE 200 controls whether to apply frequency hopping of the UL signal using the UL sub-band of SBFD according to a condition (for example, the first condition or the second condition described in the operation example 1) (for example, the operation example 1). With this configuration, in the case where the SBFD is applied, the frequency hopping of the UL signal can be appropriately performed.

[0252] In the embodiment, the UE 200 applies frequency hopping offsets that are set separately for SBFD and non-SBFD (for example, operation example 2). With this configuration, it is possible to appropriately perform frequency hopping of a UL signal using the UL sub-band of SBFD.

[0253] In the embodiment, the UE 200 applies different n-th resource determination methods for SBFD and Non-SBFD (for example, Operation Example 3). With this configuration, it is possible to appropriately perform frequency hopping of the UL signal using the UL sub-band of SBFD.

[0254] In the embodiment, when a second frequency hopping offset applied in SBFD is applied separately from the first frequency hopping offset applied in Non-SBFD, UE 200 performs frequency hopping in the second case by using the second frequency hopping offset specified by information included in downlink control information (DCI). According to such a configuration, when a case is assumed in which the second frequency hopping offset is applied separately from the first frequency hopping offset, the details (such as how to determine) of the frequency hopping offset (FH offset) are clarified, and therefore it is possible to appropriately operate the frequency hopping offset applied in SBFD separately from Non-SBFD.

[0255] (7) Other embodiments The present invention has been described above in accordance with the embodiments, but it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0256] Although not particularly mentioned in the above disclosure, which of Operational Examples 1 to 6 is to be used (hereinafter, referred to as which aspect is to be used) may be set by a higher layer parameter. Which of each option or Alt. of Operational Examples 1 to 6 is to be used (hereinafter, referred to as which aspect is to be used) may be set by a higher layer parameter. Which aspect is to be supported may be reported from UE 200 as UE capability(ies). Which aspect is to be used may be defined in advance in wireless communication system 20. Which aspect is to be used may be set by a higher layer parameter and reported from UE 200 as UE capability(ies).

[0257] Although not specifically mentioned in the above disclosure, the following UE capability(ies) may be defined. The UE capability(ies) may be defined for each UE 200, for each FR, or for each FC. The UE capability(ies) may be included in a signal reported from the UE 200 to the gNB 100, or may be included in a signal (RRC configuration) configured for the UE 200 from the NB 100.

[0258] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports intra-slot PUCCH frequency hopping in the SBFD symbol for the PUCCH.

[0259] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports intra-slot PUSCH frequency hopping in the SBFD symbol for the PUSCH.

[0260] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports inter-slot PUCCH frequency hopping in the SBFD symbol for the PUCCH.

[0261] Although not particularly mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports inter-slot PUSCH frequency hopping in the SBFD symbol for the PUSCH.

[0262] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports inter-repetition PUSCH frequency hopping in SBFD symbols for the PUSCH. In inter-repetition PUSCH frequency hopping, it may be assumed that each resource for repeated transmission is only SBFD symbols or only non-SBFD symbols.

[0263] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports inter-slot PUCCH frequency hopping across SBFD symbols and non-SBFD symbols for the PUCCH. In inter-slot PUCCH frequency hopping, it may be assumed that each resource for repeated transmission is only SBFD symbols or only non-SBFD symbols.

[0264] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports inter-slot PUSCH frequency hopping across SBFD symbols and non-SBFD symbols for the PUSCH. In inter-slot PUSCH frequency hopping, it may be assumed that each resource for repeated transmission is only SBFD symbols or only non-SBFD symbols.

[0265] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports inter-repetition PUSCH frequency hopping across SBFD symbols and non-SBFD symbols for the PUSCH. In inter-repetition PUSCH frequency hopping, it may be assumed that each resource for repeated transmission is only SBFD symbols or only non-SBFD symbols.

[0266] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports frequency hopping offsets that are set separately for SBFD and Non-SBFD.

[0267] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports the frequency hopping offset of Msg. 3, which is set separately for SBFD and Non-SBFD.

[0268] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether the UE 200 supports separate n-th resource determination methods for SBFD and Non-SBFD.

[0269] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether or not the FH offset for the PUSCH of an SBFD symbol is supported, in addition to the FH offset for the PUSCH of a non-SBFD symbol.

[0270] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether or not the FH offset parameter for SBFD in the CG configuration (rrc-ConfiguredUplinkGrant) is supported, in addition to the FH offset parameter for non-SBFD in the CG configuration (rrc-ConfiguredUplinkGrant).

[0271] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether or not the UE supports DCI bits for SBFD (FH offset indicator), in addition to DCI bits for non-SBFD (FH offset indicator).

[0272] Although not specifically mentioned in the above disclosure, the UE capability(ies) may include information indicating whether or not the UE supports a second frequency hopping offset list for SBFD, separate from the first frequency hopping offset list for non-SBFD. The second frequency hopping offset list for SBFD may be included in the PUSCH-Config.

[0273] In the above disclosure, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0274] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0275] The block diagrams (FIGS. 4 and 5) used in the description of the above-described embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0276] 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, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, 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 each is implemented.

[0277] Furthermore, the above-described gNB100 and UE200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 15 is a diagram showing an example of the hardware configuration of the device. As shown in Figure 15, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0278] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus 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.

[0279] Each functional block of the device (see FIGS. 4 and 5) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0280] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0281] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0282] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may 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.

[0283] The memory 1002 is a computer-readable recording medium and may be configured by, for example, 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 memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., that can execute a method according to an embodiment of the present disclosure.

[0284] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-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. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0285] 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 called, for example, a network device, a network controller, a network card, or a communication module.

[0286] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0287] 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 performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0288] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to 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.

[0289] Furthermore, the device 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, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0290] 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., 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.

[0291] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. In addition, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may be applied.

[0292] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure 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.

[0293] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, 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, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0294] Information and signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and may be input and output via multiple network nodes.

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

[0296] 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).

[0297] 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).

[0298] 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.

[0299] 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.

[0300] 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.

[0301] 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.

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

[0303] 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.

[0304] 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.

[0305] In this disclosure, terms such as "base station (BS)," "radio 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.

[0306] A base station can accommodate one or more (e.g., three) cells (also called sectors). 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 (Remote Radio Head: RRH)).

[0307] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0308] 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.

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

[0310] 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.

[0311] At least one of the base station and the mobile station may be called 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 body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (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 also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

[0313] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0314] A radio frame may be composed of one or more frames in the time domain, each of which may be called a subframe.

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

[0316] Numerology may be a communication parameter applied 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 a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.

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

[0318] 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.

[0319] 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.

[0320] 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 (e.g., 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.

[0321] 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 radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

[0322] 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.

[0323] 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.

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

[0325] 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.

[0326] 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.

[0327] 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.

[0328] 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.

[0329] 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.

[0330] 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.

[0331] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

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

[0333] 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.

[0334] 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.

[0335] The reference signal may also be abbreviated as Reference Signal (RS), and may also be called a pilot depending on the applicable standard.

[0336] 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."

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

[0338] 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 therein or that the first element must precede the second element in some way.

[0339] 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.

[0340] 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.

[0341] 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.

[0342] 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."

[0343] Fig. 16 shows an example of the configuration of a vehicle 2001. As shown in Fig. 16, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right 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.

[0344] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0345] 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.

[0346] 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 2027 provided in the vehicle. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0347] The signals from the various sensors 2021 to 2028 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.

[0348] 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 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 obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0349] 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 millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, 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 driving assistance functions or autonomous driving functions.

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

[0351] 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.

[0352] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0353] 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. The communication module 2013 also stores the various information received from the 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 a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0354] 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.

[0355] (Addendum) The above disclosure may be expressed as follows:

[0356] a receiving unit that receives downlink control information including information that commonly specifies a first frequency hopping offset and a second frequency hopping offset when a second frequency hopping offset that is applied in a second case in which a duplex scheme capable of performing simultaneous communication of uplink and downlink signals within a time division duplex band is applied is applied separately from a first frequency hopping offset that is applied in a first case in which the duplex scheme is not applied; and a control unit that performs frequency hopping in the second case by using the second frequency hopping offset specified by information included in the downlink control information, wherein a second frequency hopping offset list that is used in the second case is set separately from a first frequency hopping offset list that is used in the first case, and the number of frequency hopping offsets included in the second frequency hopping offset list is smaller than the number of frequency hopping offsets included in the first frequency hopping offset list.

[0357] A second feature is a wireless communication system including a terminal and a base station, wherein the terminal, when a second frequency hopping offset applied in a second case in which a duplexing scheme capable of performing simultaneous communication of uplink signals and downlink signals within a time division duplex band is applied and separate from a first frequency hopping offset applied in a first case in which the duplexing scheme is not applied, comprises: a receiving unit that receives downlink control information including information that commonly specifies the first frequency hopping offset and the second frequency hopping offset; and a control unit that performs frequency hopping in the second case by using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list used in the second case is set separate from a first frequency hopping offset list used in the first case, and the number of frequency hopping offsets included in the second frequency hopping offset list is smaller than the number of frequency hopping offsets included in the first frequency hopping offset list.

[0358] A third feature is a wireless communication method including: receiving downlink control information including information commonly specifying a first frequency hopping offset and the second frequency hopping offset, when a second frequency hopping offset applied in a second case in which a duplex scheme capable of performing simultaneous communication of uplink and downlink signals within a time division duplex band is applied, separately from a first frequency hopping offset applied in a first case in which the duplex scheme is not applied; and performing frequency hopping in the second case by using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list used in the second case is set separately from a first frequency hopping offset list used in the first case, and the number of frequency hopping offsets included in the second frequency hopping offset list is smaller than the number of frequency hopping offsets included in the first frequency hopping offset list. [Explanation of symbols]

[0359] 10. Wireless communication systems 20 NG-RAN 100 gNB 110 Receiving unit 120 Transmitter 130 Control Unit 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 Left and right front wheels 2008 Left and right rear wheels 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

Claims

1. a receiver for receiving downlink control information including information commonly specifying a first frequency hopping offset and a second frequency hopping offset when a second frequency hopping offset is applied in a second case in which a duplex scheme capable of performing simultaneous communication of an uplink signal and a downlink signal within a time division duplex band is applied, separate from a first frequency hopping offset applied in a first case in which the duplex scheme is not applied; a control unit that performs frequency hopping in the second case by using the second frequency hopping offset specified by information included in the downlink control information; a second frequency hopping offset list to be used in the second case is set separately from a first frequency hopping offset list to be used in the first case; The number of frequency hopping offsets included in the second frequency hopping offset list is less than the number of frequency hopping offsets included in the first frequency hopping offset list.

2. A terminal and a base station are provided, The terminal a receiver for receiving downlink control information including information commonly specifying a first frequency hopping offset and a second frequency hopping offset when a second frequency hopping offset is applied in a second case in which a duplex scheme capable of performing simultaneous communication of an uplink signal and a downlink signal within a time division duplex band is applied, separate from a first frequency hopping offset applied in a first case in which the duplex scheme is not applied; a control unit that performs frequency hopping in the second case by using the second frequency hopping offset specified by information included in the downlink control information; a second frequency hopping offset list to be used in the second case is set separately from a first frequency hopping offset list to be used in the first case; A wireless communication system, wherein the number of frequency hopping offsets included in the second frequency hopping offset list is less than the number of frequency hopping offsets included in the first frequency hopping offset list.

3. receiving downlink control information including information commonly specifying a first frequency hopping offset and a second frequency hopping offset when a first frequency hopping offset applied in a first case in which a duplex scheme capable of performing simultaneous communication of an uplink signal and a downlink signal within a time division duplex band is not applied and a second frequency hopping offset applied in a second case in which the duplex scheme is applied; performing frequency hopping in the second case using the second frequency hopping offset specified by information included in the downlink control information; a second frequency hopping offset list to be used in the second case is set separately from a first frequency hopping offset list to be used in the first case; A wireless communication method, wherein the number of frequency hopping offsets included in the second frequency hopping offset list is less than the number of frequency hopping offsets included in the first frequency hopping offset list.

Images