Terminal, wireless communication system, and wireless communication method

Abstract

This terminal comprises: a reception unit which, when a second FH offset that is applied in SBFD is applied separately from a first FH offset that is applied in Non-SBFD, receives DCI including information designating the first FH offset and the second FH offset jointly; and a control unit which executes FH in the SBFD using the second FH offset designated by the information included in the DCI. A second frequency hopping offset list that is used in the SBFD is set separately from a first frequency hopping offset list that is used in the Non-SBFD, and the number of FH offsets included in the second frequency hopping offset list is less than the number of FH offsets included in the first frequency hopping offset list.

Description

Terminal, wireless communication system, and wireless communication method

[0001] This disclosure relates to terminals, wireless communication systems, and wireless communication methods in next-generation mobile communication systems.

[0002] The 3rd Generation Partnership Project (3GPP®) has standardized the 5th generation mobile communication system (also known as 5G, New Radio (NR), or Next Generation (NG)), and is also working on standardizing the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] For example, 3GPP Release 18 considers extensions to duplexing schemes. Specifically, a new duplexing scheme called SBFD (Sub-Band non-overlapping Full Duplex) is proposed, which enables simultaneous use of downlink (DL) and uplink (UL) within a carrier in the time-division duplex (TDD) band. SBFD may also be interpreted as XDD (Cross Division Duplex) (Non-Patent Literature 1).

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

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

[0006] Against this backdrop, the inventors, after diligent study, focused on the case where frequency hopping offsets are applied separately between SBFD and Non-SBFD, and found it necessary to clarify the details of the frequency hopping offset set separately in SBFD from that in Non-SBFD.

[0007] Therefore, this 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 the frequency hopping offset that is applied separately from Non-SBFD in SBFD.

[0008] The disclosed aspect is a terminal comprising: a receiving unit that receives downlink control information including information specifying the first frequency hopping offset and the second frequency hopping offset in common when a second frequency hopping offset is applied in a second case in which the duplexing scheme is applied, in addition to 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 using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list for use in the second case is set separately from the first frequency hopping offset list for use in the first case, and 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.

[0009] The disclosed aspect is a wireless communication system comprising a terminal and a base station, wherein the terminal includes a receiving unit that receives downlink control information including information specifying the first frequency hopping offset and the second frequency hopping offset in common when a second frequency hopping offset is applied in a second case in which the duplexing scheme is applied, in addition to 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 using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list for use in the second case is set separately from the first frequency hopping offset list for use in the first case, and 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.

[0010] The disclosed aspect is a wireless communication method comprising: receiving downlink control information that specifies the first frequency hopping offset and the second frequency hopping offset in common when a second frequency hopping offset is applied in a second case in which the duplexing scheme is applied, in addition to a first frequency hopping offset applied in a first case in which the duplexing scheme is not applied, and the second frequency hopping offset is applied in addition to a first frequency hopping offset applied in a first case in which the duplexing scheme is applied; and performing frequency hopping in the second case using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list for use in the second case is set separately from the first frequency hopping offset list for use in the first case, and 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.

[0011] Figure 1 is an overall schematic diagram of the wireless communication system 10. Figure 2 is a diagram showing the frequency range used in the wireless communication system 10. Figure 3 is a diagram showing an example configuration of wireless frames, subframes, and slots used in the wireless communication system 10. Figure 4 is a functional block configuration diagram of UE200. Figure 5 is a functional block configuration diagram of gNB100. Figure 6 is a diagram for explaining the problem. Figure 7 is a diagram for explaining operation example 2. Figure 8 is a diagram for explaining operation example 3. Figure 9 is a diagram for explaining operation example 3. Figure 10 is a diagram for explaining operation example 5. Figure 11 is a diagram for explaining operation example 5. Figure 12 is a diagram for explaining operation example 5. Figure 13 is a diagram for explaining operation example 5. Figure 14 is a diagram for explaining operation example 6. Figure 15 is a diagram showing an example of the hardware configuration of gNB100 and UE200. Figure 16 is a diagram showing an example configuration of vehicle 2001.

[0012] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

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

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

[0015] NG-RAN20 includes base station 100 (hereinafter referred to as gNB100). The specific configuration of the wireless communication system 10, including the number of gNB100 and UE200, is not limited to the example shown in Figure 1.

[0016] 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). Note that NG-RAN 20 and 5GC may simply be referred to as the "network".

[0017] gNB 100 is a 5G-compliant radio base station that performs wireless communication with UE 200 according to 5G. gNB 100 and UE 200 can support Massive MIMO (Multiple-Input Multiple-Output) that generates a more directional beam BM by controlling radio signals transmitted from a plurality of antenna elements, carrier aggregation (CA) that bundles and uses a plurality of component carriers (CCs), and dual connectivity (DC) that communicates with two or more transport blocks simultaneously between the UE and each of the two NG-RAN nodes.

[0018] In addition, the wireless communication system 10 supports a plurality of frequency ranges (FRs). FIG. 2 shows the frequency ranges used in the wireless communication system 10.

[0019] First, the wireless communication system 10 may support the plurality of frequency ranges (FRs) 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: Above 52.6 GHz to 71 GHz In FR1, a sub-carrier spacing (SCS) of 15, 30, or 60 kHz may be used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 has a higher frequency than FR1, and an SCS of 60 kHz or 120 kHz (240 kHz may be included) may be used, and a bandwidth (BW) of 50 to 400 MHz may be used.

[0021] Note that SCS may also be interpreted as numerology. Numerology 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 support a frequency band higher than the FR2 frequency band. Specifically, the wireless communication system 10 may support a frequency band exceeding 52.6 GHz and 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. 3.

[0024] As shown in FIG. 3, one slot is composed of 14 symbols, and as the SCS increases (broadens), the symbol period (and slot period) becomes shorter. In addition to 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc., 480 kHz, 960 kHz, etc. may also be used for the SCS.

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

[0026] Note that the time direction (t) shown in FIG. 3 may also be referred to as the time domain, symbol period, or symbol time. Also, the frequency direction may be referred to as the frequency domain, resource block, subcarrier, 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 UE200 will be described.

[0029] Figure 4 is a functional block diagram of the UE200. As shown in Figure 4, the UE200 comprises a wireless signal transmission / reception unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmission / reception unit 260, and a control unit 270.

[0030] The wireless signal transceiver unit 210 transmits and receives wireless signals in accordance with NR. The wireless signal transceiver unit 210 supports Massive MIMO, CA which uses multiple CCs bundled together, and DC which communicates simultaneously between the UE and each of the two NG-RAN Nodes.

[0031] In this embodiment, the wireless signal transceiver 210 may communicate with a duplexing cell capable of simultaneously communicating uplink signals (hereinafter referred to as UL signals) and downlink signals (hereinafter referred to as DL signals) within the time-division duplex band. The new duplexing method capable of simultaneously communicating UL signals and DL signals may be called SBFD (Sub-Band non-overlapping Full Duplex). SBFD may also be interpreted as XDD (Cross Division Duplex).

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

[0033] A duplexing cell may be referred to as an SBFD operation cell. Additional cells may be referred to as Additional PCI (Physical Cell Identifier) ​​cells. Additional PCI cells may include SBFD operation cells and non-SBFD operation cells.

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

[0035] The amplifier section 220 consists of components such as a PA (Power Amplifier) ​​and an LNA (Low Noise Amplifier). The amplifier section 220 amplifies the signal output from the modulation / demodulation section 230 to a predetermined power level. The amplifier section 220 also amplifies the RF signal output from the wireless signal transmission / reception section 210.

[0036] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (gNB100 or other gNB). The modulation / demodulation 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 processing unit 240 performs processing related to various control signals transmitted and received by the UE200, and processing related to various reference signals transmitted and received by the UE200.

[0038] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB100 via a predetermined control channel, such as control signals for the radio resource control layer (RRC). The control signal / reference signal processing unit 240 also transmits various control signals to the gNB100 via a predetermined control channel.

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

[0040] DMRS is a terminal-specific, known reference signal (pilot signal) between the base station and the terminal used to estimate the fading channel used for data demodulation. PTRS is a terminal-specific reference signal intended to estimate phase noise, which is a problem in the high-frequency band.

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

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

[0043] Furthermore, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), among others. "Data" refers to data transmitted through a data channel. A data channel may also be interpreted as a shared channel.

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

[0045] The value stored in the DCI Format field is an information element that specifies the DCI format. 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 an information element (pdsch-TimeDomainAllocationList, push-TimeDomainAllocationList) included in the RRC message. The time domain resource may also be identified by the value stored in the TDRA field and the 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 MCS and the MCS table. The MCS table may be specified by the RRC message or identified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ Process to which DCI is applied. The value stored in NDI is an information element that determines whether the data to which 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 DCI is applied.

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

[0047] Specifically, the encoding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into predetermined sizes and performs channel coding on the divided data. The encoding / decoding unit 250 also decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.

[0048] The data transmission / reception unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / decomposition of PDUs / SDUs at multiple layers (such as the Media Access Control Layer (MAC), Radio Link Control Layer (RLC), and Packet Data Convergence Protocol Layer (PDCP)). In addition, the data transmission / reception unit 260 performs error correction and retransmission control of data based on HARQ (Hybrid Automatic Repeat Request).

[0049] The control unit 270 controls each functional block that constitutes the UE200. In this embodiment, the control unit 270 is configured to perform frequency hopping in the second case using a second frequency hopping offset specified by the information included in the downlink control information (DCI).

[0050] Secondly, the functional block configuration of the gNB100 will be described.

[0051] Figure 5 is a functional block diagram of the gNB100. As shown in Figure 5, the gNB100 has a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0052] The receiver 110 receives various signals from the UE200. The receiver 110 may also receive the UL signal via PUCCH or PUSCH.

[0053] The transmitter 120 transmits various signals to the UE200. The transmitter 120 may also transmit DL signals via PDCCH or PDSCH.

[0054] The receiving unit 110 and the transmitting unit 120 may communicate with the UE200 via a duplexing cell (SBFD operation cell) capable of simultaneous communication of UL signals and DL signals within the TDD band.

[0055] In this embodiment, the transmitter 120 may transmit downlink control information (DCI) that includes information specifying a second frequency hopping offset when a second frequency hopping offset applied with an SBFD symbol is applied, in addition to a first frequency hopping offset applied with a non-SBFD symbol.

[0056] The control unit 130 controls the gNB100. In this 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 the downlink control information (DCI).

[0057] (3) The first task will be explained in terms of resource allocation for gNB100.

[0058] In 3GPP Release 15 / 16 / 17, as shown in the upper part of Figure 6, the gNB100 sets or specifies "DL," "F (Flexible)," or "UL" for each symbol. Simultaneous communication of DL and UL signals is not permitted within a given time resource.

[0059] On the other hand, in 3GPP Release 18, as shown in the lower part of Figure 6, the gNB100 sets or designates "DL" as the symbol for one frequency resource (e.g., Sub-band(s)) and "UL" as the symbol for another frequency resource (e.g., Sub-band(s)). Simultaneous communication of DL and UL signals is permitted within a given time resource. Such a scheme may be called SBFD (Sub-Band non-overlapping Full Duplex).

[0060] Secondly, we will explain the challenges related to frequency hopping of the UL signal during repeated transmission of the UL signal in a case assuming SBFD.

[0061] As shown in Figure 6, the UL sub-band of SBFD is narrower than the uplink band (UL BWP) to which SBFD does not apply, because the DL sub-band is excluded from the BWP. Therefore, if the resources for repeated transmission of uplink signals include SBFD symbols, applying the same frequency hopping as in the case where SBFD does not apply may result in hopping to the DL sub-band of SBFD, etc.

[0062] Thus, after diligent study, the inventors focused on the fact that the UL Subband to which SBFD applies is narrower than the UL BWP (Bandwidth Part) to which SBFD does not apply, and found the need to introduce a mechanism to appropriately perform frequency hopping of the uplink signal when the resources for repeated transmission of the uplink signal include SBFD symbols.

[0063] (4) Definitions of Terms The following sections will explain the definitions of terms related to SBFD.

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

[0065] A non-SBFD operation cell is a serving cell in which an SBFD subband is not configured.

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

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

[0068] A semi-static flexible slot / symbol is a slot / symbol that is set as Flexible by a higher-level parameter (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 a higher-level parameter (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 a higher-level parameter (tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and specified as UL by DCI Format 2_0.

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

[0072] (5) Examples of Operation In order to solve the above-mentioned problems, the following examples of operation may be provided. Specifically, frequency hopping of UL signals (UL channels) using the UL sub-band of SBFD will be mainly described. 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 repetition transmissions where 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 repetition transmissions where two or more 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 also be set by the higher layer parameter (RRC).

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

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

[0077] For UL channels scheduled by DCI, enabling or disabling frequency hopping may be determined by the frequency hopping field included in the DCI that schedules the UL channel.

[0078] (5.1) Operation Example 1 Operation Example 1 explains whether or not to apply frequency hopping of the UL signal (UL channel) using the UL sub-band of SBFD. The following options are possible for Operation Example 1.

[0079] Option 1-1 describes the case where frequency hopping of a UL signal (UL channel) using the UL subband of SBFD is applied. Option 1-1 can be considered to assume that the first condition is met. The following options are possible for Option 1-1.

[0080] In option 1-1-1, the UE200 may apply frequency hopping of the UL signal (UL channel) in the SBFD symbol. In other words, the UE200 does not have to apply frequency hopping in repeated transmissions that span both the SBFD symbol and the non-SBFD symbol.

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

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

[0083] In Option 1-1-2, the UE200 may apply frequency hopping in repetitive transmissions that span SBFD symbols and non-SBFD symbols. Option 1-1-2 may also assume that each resource in a repetitive transmission consists only of SBFD symbols or only of non-SBFD symbols. The fact that each resource in a repetitive transmission consists only of SBFD symbols or only of non-SBFD symbols can be considered 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 for PUSCH or PUCCH when some resources of the PUSCH or PUCCH repetition are SBFD symbols and some resources of the PUSCH or PUCCH repetition are non-SBFD symbols.

[0085] Option 1-2 describes 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 assume that the second condition is met. The following options are possible for Option 1-2.

[0086] In option 1-2-1, the UE200 does not need to apply frequency hopping of the UL signal (UL channel) in the SBFD symbol.

[0087] In Example 1-2-1-1, UE200 does not need to apply frequency hopping if inter-slot frequency hopping or inter-repetition frequency hopping is set for PUSCH or PUCCH and the resource for PUSCH or PUCCH is an SBFD symbol. In Example 1-2-1-1, the setting of inter-slot frequency hopping or inter-repetition frequency hopping for PUSCH or PUCCH and the fact that the resource for PUSCH or PUCCH is an SBFD symbol can be considered an example of the second condition.

[0088] In Example 1-2-1-2, UE200 does not need to apply frequency hopping if all resources for repeated PUSCH or PUCCH transmissions are SBFD symbols, regardless of whether frequency hopping is enabled or not. In other words, UE200 does not need to apply frequency hopping if all resources for repeated PUSCH or PUCCH transmissions are not SBFD symbols.

[0089] In Option 1-2-2, the UE200 does not need to apply frequency hopping in repetitive transmissions that span SBFD symbols and non-SBFD symbols. Option 1-2-2 may also assume that each resource in a repetitive transmission consists only of SBFD symbols or only of non-SBFD symbols.

[0090] In Option 1-2-2, the UE200 may perform the following actions when Inter-slot frequency hopping or Inter-repetition frequency hopping is set for PUSCH or PUCCH, and some resources for the repeated transmission of PUSCH or PUCCH are SBFD symbols, and some resources for the repeated transmission of PUSCH or PUCCH are Non-SBFD symbols.

[0091] In Example 1-2-2-1, the UE200 does not need to apply frequency hopping to all repeated transmissions. In Example 1-2-2-1, the fact that repeated transmissions span both SBFD symbols and non-SBFD symbols can be considered an example of the second condition.

[0092] In Example 1-2-2-2, the UE200 may apply frequency hopping to the repeated transmission of non-SBFD symbols, but not to the repeated transmission of SBFD symbols. In Example 1-2-2-2, the fact that the resource for repeated transmission is a non-SBFD symbol can be considered an example of the first condition, and the fact that the resource for repeated transmission is an SBFD symbol can be considered an example of the second condition.

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

[0094] (5.2) Operation Example 2 Operation Example 2 describes a case in which frequency hopping using the UL sub-band of SBFD is applied. Operation Example 2 mainly describes the frequency hopping offset.

[0095] In Operation Example 2, when applying frequency hopping of a UL signal using the SBFD's UL Sub-band, the UE200 may apply a different frequency hopping offset than the one applied when repeatedly transmitting a UL signal without using the SBFD's UL Sub-band.

[0096] The frequency hopping offset applied to repeated transmission of UL signals without using the UL sub-band of SBFD may be the same frequency hopping offset used in the existing methods described above.

[0097] The following options are possible as an example of operation 2.

[0098] Option 2-1 primarily describes PUSCH or PUCCH. In Option 2-1, the frequency hopping offset is set separately for SBFD and Non-SBFD.

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

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

[0101] Option 2-2 primarily 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 to define the frequency hopping of Msg.3 PUSCH in SBFD. The new table may be the one shown in Figure 7. In Figure 7, N_ULsubband^size represents the size of the UL sub-band.

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

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

[0105] In Operation Example 3, when UE200 applies frequency hopping of UL signals using the UL Sub-band of SBFD, it may apply a resource determination method for the nth hop (where n is an integer greater than or equal to 2) that is different from the resource determination method for the nth hop applied in repeated transmission of uplink signals that do not use the UL Sub-band of SBFD.

[0106] The resource determination method for the nth hop applied in the repeated transmission of UL signals without using the UL Sub-band of SBFD may be the resource determination method for the nth hop used in the existing method described above.

[0107] The following options are possible as example 3 of operation.

[0108] In Option 3-1, the resource for the nth hop is determined in the way shown in Option 1 in Figure 8. In Figure 8, 2 nd An example of how to determine a hop's resources is given. For example, the starting position of the resource for the nth hop is the starting position of the resource for the (n-1)th hop, and the offset (RB) between the (n-1)th hop and the nth hop. offset ) may be calculated based on the following. For example, the starting position of the resource at the nth hop is calculated by formula (1) shown below.

[0109]

[0110] Equation (1) may be the same as the one used in the resource determination method for the nth hop in the existing method described above. However, as shown in Option 1 in Figure 8, 2 ndThe resources of a hop may become a DL Sub-band. Assuming such a case, in Option 3-1, gNB100 configures the resources of each hop and the parameters of frequency hopping (such as offset) so that the resources of each hop do not become a DL Sub-band. st It may be configured to set the resources of a hop and the parameters of frequency hopping (such as offset).

[0111] In Option 3-2, the resources of the nth hop are determined by the method shown in Option 2 of FIG. 8. FIG. 8 illustrates the method for determining the resources of a hop. For example, the start position of the resources of the nth hop may be calculated based on the start position of the resources of the (n - 1)th hop and the offset (RB nd ) between the (n - 1)th hop and the nth hop. For example, the start position of the resources of the nth hop is calculated by the following formula (2). offset ).

[0112]

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

[0114] In Option 3-2, the range of the value obtained by formula (2) is as follows.

[0115]

[0116] In Option 3-3, the resources of the nth hop are determined by the method shown in Option 3 of FIG. 9. FIG. 9 illustrates the method for determining the resources of a hop. For example, the start position of the resources of the nth hop may be calculated based on the start position of the resources of the (n - 1)th hop and the offset (RB nd ) between the (n - 1)th hop and the nth hop. For example, the start position of the resources of the nth hop is calculated by the following formula (3). offset ).

[0117]

[0118] RB UL, start This represents the offset of the UL Sub-band's starting RB relative to the UL BWP's starting RB. N_UL 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]

[0121] In options 3-4, the resource for the nth hop is determined in the way shown in Option 4 of Figure 9. nd An example of how to determine a hop's resources is given. For example, the starting position of the resource for the nth hop is the starting position of the resource for the (n-1)th hop, and the offset (RB) between the (n-1)th hop and the nth hop. offset ) may be calculated based on the following. For example, the starting position of the resource at the nth hop is calculated by equation (4) shown below.

[0122]

[0123] RB UL, start This represents the offset of the UL Sub-band's starting RB relative to the UL BWP's starting RB. N_UL 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]

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

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

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

[0129] In Operation Example 4, if the frequency hopping offset parameter for SBFD is not set for rrc-ConfiguredUplinkGrant, and the frequency hopping offset parameter for non-SBFD is set for rrc-ConfiguredUplinkGrant, the following behavior may be expected.

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

[0131] In option 4-2, the default value may apply to the FH of the CG PUSCH of the SBFD symbol. The default value may also be UL_SB / 2, where UL_SB may be the number of RBs in the PRBs available in 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 Operation Example 4, whether to apply Option 4-1 or Option 4-2 may be determined based on a new parameter included in the CG setting (e.g., the FH enabling parameter for SBFD). For example, if a new parameter is provided, Option 4-1 or Option 4-2 may be applied; if no new parameter is provided, Option 4-3 may be applied.

[0134] In Operation Example 4, the frequency hopping offset parameter for SBFD may be set only if the CG PUSCH occasion or repetition of the type 1 CG setting includes both an SBFD symbol and a non-SBFD symbol.

[0135] In Operation Example 4, the frequency hopping offset parameter for Non-SBFD in the CG settings may be used to determine the frequency hopping.

[0136] In example 4, a type 1 CG pusher may be assumed.

[0137] (5.5) Operation Example 5 In Operation Example 5, as explained in Operation Example 2 or Operation Example 4, 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 focus on the case where frequency hopping offsets are applied separately between SBFD and Non-SBFD, and explain the details of the frequency hopping offset set separately in SBFD from that in Non-SBFD. Specifically, as shown in Figure 10, we explain the case where the frequency hopping offset applied to SBFD is different from the frequency hopping offset applied to Non-SBFD.

[0139] In Operation Example 5, the UE200 performs frequency hopping in the second case using the second frequency hopping offset specified by the information included in the downlink control information (DCI) when the second frequency hopping offset applied in SBFD is applied in addition to the first frequency hopping offset applied in Non-SBFD. The following operation example is possible for Operation Example 5.

[0140] (5.5.1) Operation Example 5-1 In Operation Example 5-1, as shown in Figure 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, the information specifying the second frequency hopping offset is separate from the 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 included in the FDRA field (2*N). UL_hop It may also be MSB bits. For example, information specifying the second frequency hopping offset could be 2*N. UL_hop N of MSB bits UL_hop The information specifying the first frequency hopping offset, which is the MSB bit, is 2*N. UL_hop The remaining N of the MSB bits UL_hop It may also be LSB bits. Alternatively, the information specifying the first frequency hopping offset is 2*N. UL_hop N of MSB bits UL_hopThe information specifying the second frequency hopping offset, which is the MSB bit, is 2*N. UL_hop The remaining N of the MSB bits UL_hop LSB bits are also acceptable.

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

[0143] In option 5-1-1, the UE may assume that there are two values ​​in the configured FH offset list if PUSCH is configured for the SBFD cell. With this configuration, the number of DCI bits in the FDRA field is the same as the existing N UL_hop It will never exceed the maximum value (maximum number of bits).

[0144]

[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 N of MSB bits UL_hop MSB bits and 2*N UL_hop N of MSB bits UL_hop Since it is represented by LSB bits, it is possible to consider the information specifying the first frequency hopping offset and the information specifying the second frequency hopping offset as 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 included in the FDRA field, N UL_hopThe MSB bits are provided separately. In other words, the FDRA field is for Non-SBFD. UL_hop MSB bits and N for SBFD UL_hop Includes MSB bits separately.

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

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

[0150] In option 5-1-2, if the set FH offset list contains four values, the first two values ​​may be used as candidates for the FH offset of the SBFD symbol PUSCH, and the last two values ​​may be used as candidates for the FH offset of the Non-SBFD symbol PUSCH. Alternatively, if the set FH offset list contains four values, the first two values ​​may be used as candidates for the FH offset of the Non-SBFD symbol PUSCH, and the last two values ​​may be used as candidates for the FH offset of the SBFD symbol PUSCH. In such cases, the FH offset indication (bit) for the SBFD PUSCH is mapped to the candidates for the FH offset of the SBFD symbol PUSCH. The FH offset indication (bit) for the Non-SBFD PUSCH is mapped to the candidates for the FH offset of the Non-SBFD symbol PUSCH.

[0151] Option 5-1-3 describes the method of interpreting DCI bits for FH offset indication. There are two possible interpretations of DCI bits for FH offset indication: separate interpretations for SBFD and Non-SBFD (first interpretation) and the existing interpretation (second interpretation). The first interpretation is the interpretation described in Option 5-1-1 or Option 5-1-2. The first interpretation may be reinterpreted as a new interpretation. Option 5-1-3 offers the following alternatives.

[0152] Alt5-1-3-1 may also include a new parameter specifying the first interpretation (for example, separate-FH-offset-sbfd-r19).

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

[0154] Secondly, if no new parameters are set, the UE interprets the DCI bits according to the second interpretation (existing interpretation). For example, for push occasions of non-SBFD symbols, the specified FH offset is applied. On the other hand, for push occasions of SBFD symbols, the following Alt values ​​are possible.

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

[0156] In Alt5-1-3-1-2, FH does not need to be applied.

[0157] Alt5-1-3-1-3 may apply a default value. The default value may be UL_SB / 2. UL_SB may be the number of RBs in the PRBs available in 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 scheduled PUSCH symbol type (Non-SBFD or SBFD) is one symbol type or two symbol types (first criterion). The interpretation of DCI bits for FH offset indication may also be determined based on whether the activated type 2 CG setting symbol type (Non-SBFD or SBFD) is one symbol type or two symbol types (second criterion).

[0159] Firstly, if the PUSCH occasion scheduled by DCI is a Non-SBFD symbol and an SBFD symbol, the UE shall determine 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 DCI format is a Non-SBFD symbol and an SBFD symbol, the UE shall determine the FH offset according to the first interpretation (option 5-1-1 or option 5-1-2).

[0160] Secondly, if a single PUSCH is scheduled by DCI without repetition, the UE interprets the DCI bits according to the second interpretation (existing 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 (existing 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 (existing interpretation). For example, for a PUSCH occasion of a non-SBFD symbol, the specified FH offset applies. On the other hand, for a PUSCH occasion of an SBFD symbol, the following Alts are possible.

[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 does not need to be applied.

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

[0164] In Alt5-1-3-3, Alt5-1-3-1 and Alt5-1-3-2 may be combined.

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

[0166] (5.5.2) Operation Example 5-2 In Operation Example 5-2, as shown in Figure 12, 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). In DCI, the information for specifying the second frequency hopping offset is the same as the information for specifying the first frequency hopping offset.

[0167] In example 5-2, the second frequency hopping offset list used in the second case (SBFD) may be set by a new higher-level parameter (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 ​​in the list) may be 1, 2, or 4.

[0168] In 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 Operation Example 5-2, the number of MSB bits used for FH offset indication in the FDRA field is determined according to the Alt shown below.

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

[0171] For example, for DCI format 0_0 / 0_1 / 0_3, the number of MSB bits used for 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 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 FH offset indication may be the same as the existing number of 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 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 push occasion of an SBFD symbol, the FH offset is determined based on DCI bits (FH offset indication) and a second frequency hopping offset list.

[0177] For example, for a push 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 example 5-2, the UE may assume only one value in the second frequency-hopping offset list for SBFD and determine 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 directly as the FH offset for SBFD.

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

[0180] In option 5-2-1, the FH offset used for 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 predefined list in the radio communication system 10. The predefined list may be {UL_SB / 2, UL_SB / 4}. UL_SB may be the number of RBs in the PRBs available in UL, or 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 the default value. The default value may be UL_SB / 2. UL_SB may be the number of RBs in the PRBs available in UL, or the number of RBs in the UL Sub-band(s).

[0183] In option 5-2-4, FH does not need to be applied.

[0184] In 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 SBFD frequency hopping flag field included in DCI. The SBFD frequency hopping flag field may be defined separately from the existing frequency hopping flag field. For example, if the SBFD frequency hopping flag field is 1, FH is applied (options 5-2-1 to 5-2-3). If the SBFD frequency hopping flag field is 0, FH is not applied (option 5-2-4).

[0185] (5.5.3) Operation Example 5-3 In Operation Example 5-3, as shown in Figure 13, 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). In DCI, the information specifying the second frequency hopping offset is separate from the information specifying the first frequency hopping offset.

[0186] In example 5-3, the second frequency hopping offset list used in the second case (SBFD) may be set by a new higher-level parameter (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 ​​in the list) may be 1, 2, or 4.

[0187] In 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 operation example 5-3, the FH offset indication is identified in the same manner as in operation example 5-1.

[0189] In 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 push occasion of an SBFD symbol, the FH offset is determined based on DCI bits (FH offset indication) and a second frequency hopping offset list.

[0191] For example, for a push 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 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 directly as the FH offset for SBFD.

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

[0194] In option 5-3-1, the FH offset used for 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 predefined list in the radio communication system 10. The predefined list may be {UL_SB / 2, UL_SB / 4}. UL_SB may be the number of RBs in the PRBs available in UL, or 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 the default value. The default value may be UL_SB / 2. UL_SB may be the number of RBs in the PRBs available in UL, or the number of RBs in the UL Sub-band(s).

[0197] In option 5-3-4, FH does not need to 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 SBFD frequency hopping flag field included in DCI. The SBFD frequency hopping flag field may be defined separately from the existing frequency hopping flag field. For example, if the SBFD frequency hopping flag field is 1, FH is applied (options 5-3-1 to 5-3-3). If the SBFD frequency hopping flag field is 0, FH is not applied (option 5-3-4).

[0199] (5.5.4) Operation Example 5-4 In Operation Example 5-4, the FH offset applied by SBFD may be determined based on the specified or set FH offset. Alternatively, the FH offset applied by SBFD may be determined based on the 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 set by existing methods 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 apply in SBFD, where FH offset is the FH offset specified or set by the existing method. RB_offset may be set by the RRC or may be predefined in the radio communication system 10. RB_offset may also be UL_SB / 2. UL_SB may be the number of RBs in the PRBs available in 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 Alt statements are possible.

[0203] In Alt5-4-1-1, the default value may be used for RB_offset. The default value may be 0 or UL_SB / 2.

[0204] In Alt5-4-1-1, FH does not need to 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. UL_SB may be the number of RBs in the PRBs available in UL, or the number of RBs in the UL Sub-band(s).

[0207] In 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 a single PUSCH is scheduled by DCI without repetition, the UE determines the FH offset according to the 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 the 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 the existing method.

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

[0210] (5.6) Operation Example 6 Operation Example 6 may be an operation example that assumes Operation Example 5-2 (see Figure 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, the information specifying the second frequency hopping offset may be the same as the information specifying the first frequency hopping offset.

[0211] In Operation Example 6, we may also consider the case where frequency hopping is applied to a PUSCH scheduled by DCI format 0_0 / 0_1 / 0_2 / 0_3.

[0212] In example 6, the second frequency hopping offset list used in the second case (SBFD) may be set by a new higher-level parameter (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 ​​in the list) may be 1, 2, or 4.

[0213] In example 6, UE200 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, UE200 may assume that the number of second FH offsets included in the second frequency-hopping offset list for SBFD is less 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 the FH offset indication included in the DCI (FDRA field).

[0214] For frequency hopping of push occasions in non-SBFD symbols / slots, the FH offset is specified by the FH offset indication, according to the existing interpretation of the FH offset indication. The existing interpretation may be reinterpreted as the interpretation for non-SBFD.

[0215] For frequency hopping of push occasions in SBFD symbols / slots, 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 reinterpreted as the interpretation for SBFD. The interpretation for SBFD may be one in which the LSB bits of the FH offset indication are used as the bits(s) that specify the FH offset. The interpretation for SBFD may be one in which the MSB bits of the FH offset indication are used as the bits(s) that specify the FH offset.

[0216] For example, as shown in Figure 14, we will describe a case where 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 cases, the FH offset indication included in the DCI may be represented 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 Non-SBFD symbol / slot push occasions, the UE200 determines the FH offset (=offset2) by the FH offset indication (=01). For frequency hopping of SBFD symbol / slot push occasions, the UE200 determines the FH offset (=offset2) by the LSB (=1) of the FH offset indication.

[0219] (5.7) Operation Example 7 Operation Example 7 may be an operation example that is based on Operation Example 2 (see Figure 7). That is, in Operation Example 7, when UE200 applies frequency hopping of UL signals using the UL Sub-band of SBFD, it may apply a different frequency hopping offset than the one applied when repeatedly transmitting UL signals that do not use the UL Sub-band of SBFD.

[0220] In Operation Example 7, we may also consider the case where frequency hopping can be applied to Msg.3 PUSCH scheduled by RAR (Random Access Response) UL grant.

[0221] The following options are possible as example 7 of operation.

[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, the UE200 may assume that the frequency hopping flag field is set to 0 when it detects a RAR UL grant that schedules Msg.3 PUSCH in an SBFD symbol / slot. The following variations are possible in Option 7-1-1.

[0224] In Option 7-1-1, the UE200 may assume that the frequency hopping flag field is set to 0 when it detects a RAR UL grant that schedules a Msg.3 PUSCH without repeated transmissions in the SBFD symbol / slot.

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

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

[0227] In Option 7-2, one FH offset may be defined in the radio communication system 10 as the FH offset for Msg.3 PUSCH in the SBFD symbol / slot. One FH offset is 0, FLOOR (N_UL subband ^size / 2), FLOOR (N_UL subband ^size / 4), -FLOOR (N_UL subband It may be any of the following: ^size / 4). N_UL subband ^size represents the size of the UL Sub-band.

[0228] In Option 7-2, the FH offset of Msg.3 PUSCH in SBFD symbol / slot may not require a RAR field indication.

[0229] In Option 7-2, if the FH offset is 0, frequency hopping may be disabled, as in Option 7-1.

[0230] Option 7-2 could include the following options for the RAR UL grant that schedules Msg.3 PUSCH in SBFD symbol / slot.

[0231] In option 7-2-1, for a RAR UL grant scheduling Msg.3 PUSCH in an SBFD symbol / slot, the FDRA field may be interpreted as having 0 FH offset indications (e.g., N_UL,hop).

[0232] In Option 7-2-2, for RAR UL grants that schedule Msg.3 PUSCH in SBFD symbol / slots, the FH offset indication (e.g., N_UL,hop) may be interpreted in the same way as before.

[0233] In Option 7-2, the decision of whether to apply Option 7-2-1 or Option 7-2-2 may be made as follows:

[0234] The choice of which option to apply may depend on whether the Msg.3 PUSCH in the SBFD symbol / slot involves repeated transmissions. For example, option 7-2-1 may be applied if the Msg.3 PUSCH does not involve repeated transmissions. Option 7-2-2 may be applied if the Msg.3 PUSCH involves repeated transmissions.

[0235] The choice of which option to apply may depend on whether the repeated transmission of Msg.3 PUSCH includes only SBFD symbol / slots or spans both SBFD symbol / slots and non-SBFD symbol / slots. For example, option 7-2-1 may be applied if the repeated transmission of Msg.3 PUSCH includes only SBFD symbol / slots. Option 7-2-2 may be applied if the repeated transmission of Msg.3 PUSCH spans both SBFD symbol / slots and non-SBFD symbol / slots.

[0236] In Option 7-3, multiple FH offsets may be defined separately from the Non-SBFD FH offset as the FH offset for Msg.3 PUSCH in SBFD symbols / slots (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 at two.

[0238] In Option 7-3-2, the number of FH offsets for SBFD may be two or four. (See Operation Example 2 for N_UL) subband ^size can be interpreted not as the size of the UL Sub-band, but as the size of the UL usable PRB(s), and N_UL usable prb It can also be represented 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 in Msg.3 PUSCH may be determined based on the size of the UL BWP, similar to the number of FH offsets for Non-SBFD in Msg.3 PUSCH. For example, if the detail of the UL BWP is less than 50 PRBs, the number of FH offsets for SBFD in Msg.3 PUSCH may be two. If the detail of the UL BWP is 50 PRBs or more, the number of FH offsets for SBFD in Msg.3 PUSCH may be four.

[0240] In Option 7-3, 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) is also acceptable. N_UL subband ^size represents the size of the UL usable PRB(s).

[0241] In Option 7-3, the following Alt values ​​are possible for the number of FH offset indications (e.g., 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 RAR UL grants that schedule Msg.3 PUSCH in FD symbol / slots, N_UL,hop is interpreted in the existing way. 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 size of the UL BWP, 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. Alternatively, 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 symbol / 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, the choice between using Alt 7-3-1 or Alt 7-3-2 may be determined as follows:

[0246] The choice of which Alt to apply may depend on whether the Msg.3 PUSCH in the SBFD symbol / slot involves repeated transmissions. For example, if the Msg.3 PUSCH does not involve repeated transmissions, Alt 7-3-1 may be applied. If the Msg.3 PUSCH involves repeated transmissions, Alt 7-3-2 may be applied.

[0247] The choice of which Alt to apply may depend on whether the repeated transmission of Msg.3 PUSCH is contained only in SBFD symbol / slots or spans both SBFD symbol / slots and non-SBFD symbol / slots. For example, if the repeated transmission of Msg.3 PUSCH is contained only in SBFD symbol / slots, Alt 7-3-1 may be applied. If the repeated transmission of Msg.3 PUSCH spans both SBFD symbol / slots and non-SBFD symbol / slots, Alt 7-3-2 may be applied.

[0248] In example 7, option 7-1 may be applied if the number of UL usable PRB(s) is less than or equal to threshold X. Option 7-2 or 7-3 may be applied if the number of UL usable PRB(s) is greater than or equal to threshold X. Threshold X may be specified by SIB or set by RRC.

[0249] (5.8) Other Operation Examples Two or more operation examples selected from operation examples 1 to 6 described above may be combined. In such cases, the options of one operation example may be combined with the options of another operation example.

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

[0251] (6) Operation and Effects In the embodiment, the UE200 controls whether or not to apply frequency hopping of the UL signal using the UL sub-band of the SBFD according to a condition (for example, the first or second condition described in Operation Example 1) (for example, Operation Example 1). With such a configuration, frequency hopping of the UL signal can be appropriately performed when the SBFD is applied.

[0252] In this embodiment, the UE200 applies separately configured frequency hopping offsets for SBFD and Non-SBFD (e.g., Operation Example 2). With this configuration, frequency hopping of the UL signal using the UL sub-band of the SBFD can be properly performed.

[0253] In this embodiment, the UE200 applies separate nth resource determination methods for SBFD and Non-SBFD (e.g., Operation Example 3). With this configuration, frequency hopping of the UL signal using the UL sub-band of the SBFD can be properly performed.

[0254] In this embodiment, when a second frequency hopping offset applied in SBFD is applied in addition to the first frequency hopping offset applied in Non-SBFD, the UE200 performs frequency hopping in the second case using the second frequency hopping offset specified by the information included in the downlink control information (DCI). With this configuration, when considering the case in which a second frequency hopping offset is applied in addition to the first frequency hopping offset, the details of the frequency hopping offset (FH offset), such as how it is determined, are clarified, so that the frequency hopping offset applied separately in SBFD from Non-SBFD can be appropriately operated.

[0255] (7) Other Embodiments Although the contents of the present invention have been described above in accordance with the embodiments, 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 specifically mentioned in the disclosure above, which of Operation Examples 1 to 6 to be used (hereinafter, which mode to use) may be set by a higher-layer parameter. Which of each option or Alt. in Operation Examples 1 to 6 to be used (hereinafter, which mode to use) may be set by a higher-layer parameter. Which mode to support may be reported by UE200 as UE capability(ies). Which mode to use may be predefined in the wireless communication system 20. Which mode to use may be set by a higher-layer parameter and reported by UE200 as UE capability(ies).

[0257] Although not specifically mentioned in the disclosure above, the following UE capability(ies) may be defined. UE capability(ies) may be defined for each UE200, for each FR, or for each FC. UE capability(ies) may be included in the signals reported from the UE200 to the gNB100, or in the signals (RRC configuration) set from the NB100 to the UE200.

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

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

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

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

[0262] Although not specifically mentioned in the disclosure above, UE capability(ies) may include information indicating whether the UE200 supports inter-repetition PUSCH frequency hopping in SBFD symbols for PUSCH. Inter-repetition PUSCH frequency hopping may assume that each resource in the repeated transmission consists only of SBFD symbols or only of non-SBFD symbols.

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

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

[0265] Although not specifically mentioned in the disclosure above, UE capability(ies) may include information indicating whether the UE200 supports inter-repetition PUSCH frequency hopping that spans SBFD symbols and non-SBFD symbols for PUSCH. Inter-repetition PUSCH frequency hopping may assume that each resource in the repeated transmission consists only of SBFD symbols or only of non-SBFD symbols.

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

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

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

[0269] Although not specifically mentioned in the disclosure above, UE capability(ies) may include information indicating whether or not it supports an FH offset for pushing SBFD symbols, in addition to the FH offset for pushing non-SBFD symbols.

[0270] Although not specifically mentioned in the disclosure above, UE capability(ies) may include information indicating whether or not it supports the FH offset parameter for SBFD in the CG setting (rrc-ConfiguredUplinkGrant), separate from the FH offset parameter for Non-SBFD in the CG setting (rrc-ConfiguredUplinkGrant).

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

[0272] Although not specifically mentioned in the disclosure above, UE capability(ies) may include information indicating whether or not it 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 PUSCH-Config.

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

[0274] Furthermore, "specific," "dedicated," "UE specific," and "UE individual" may be interpreted interchangeably. Similarly, "common," "shared," "group-common," "UE common," and "UE shared" may be interpreted interchangeably.

[0275] The block diagrams (Figures 4 and 5) used in the description of the embodiments above show functional units. 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 one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the above one device or the above multiple devices with software.

[0276] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In any case, as mentioned above, the method of implementation is not particularly limited.

[0277] Furthermore, the gNB100 and UE200 (the device) described above may function as a computer that processes the wireless communication method of this disclosure. Figure 15 shows 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, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0278] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

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

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

[0281] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0282] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0283] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software module, etc., that can execute a method according to one embodiment of this disclosure.

[0284] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., Compact Disc, Digital Multipurpose Disc, Blu-ray® Disc), a smart card, flash memory (e.g., a card, stick, key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0285] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.

[0286] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0287] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0289] Furthermore, the device may include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), and some or all of the functional blocks may be implemented by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.

[0290] Furthermore, notification of information is not limited to the embodiments / models described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

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

[0292] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0293] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. 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 can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates a case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0294] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

[0295] The input and output information may be stored in a specific location (e.g., memory) or managed using a management table. The input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0296] The determination may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0297] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0298] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0299] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

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

[0301] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0302] The terms “system” and “network” as used in this disclosure are interchangeable.

[0303] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0304] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not restrictive in any way.

[0305] In this disclosure, terms such as "Base Station (BS)," "wireless 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 house one or more (e.g., three) cells (also called sectors). If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0307] The terms "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base stations and base station subsystems that provide communication services in this coverage.

[0308] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0309] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" 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 several other appropriate terms.

[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 be a device that does not necessarily move during communication operation. 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, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, each aspect / embodiment of this 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), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel.

[0313] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.

[0314] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe.

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

[0316] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

[0318] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (or PUSCH) mapping type B.

[0319] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[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. In other words, at least one of a subframe and a 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 unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0322] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Note that when a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0323] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0324] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0325] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0327] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0328] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0329] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0330] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a given BWP.

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

[0332] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0333] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0334] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be read as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0336] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

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

[0338] Any reference to elements using designations such as “First,” “Second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed therein, or that the First element must precede the Second element in any way.

[0339] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0340] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

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

[0342] In this 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 "combine" may be interpreted similarly to "different."

[0343] Figure 16 shows an example of the configuration of vehicle 2001. As shown in Figure 16, 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, which is operated by the user.

[0346] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2027 installed in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

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

[0348] The Information Services Unit 2012 consists of various devices for providing various types of information, such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of Vehicle 1.

[0349] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0350] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028 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 external devices. For example, it can send and receive various types of information to and from external devices 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 or a mobile station.

[0352] The communication module 2013 transmits current signals from current sensors input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits, via wireless communication, other signals input to the electronic control unit 2010, including front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0353] The communication module 2013 receives various information (traffic information, signal information, distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 installed in the vehicle. The communication module 2013 also stores the various information received from external devices in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021 to 2028, etc., installed in the vehicle 2001.

[0354] Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0355] (Note) The disclosure described above may also be expressed as follows:

[0356] The first feature is a terminal comprising: a receiving unit that receives downlink control information including information specifying the first frequency hopping offset and the second frequency hopping offset in common when a second frequency hopping offset is applied in a second case in which the duplexing method is applied, in addition to a first frequency hopping offset applied in a first case in which the duplexing method is not applied, and a control unit that performs frequency hopping in the second case using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list for use in the second case is set separately from the first frequency hopping offset list for use in the first case, and 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.

[0357] The second feature is a wireless communication system comprising a terminal and a base station, wherein the terminal includes a receiving unit that receives downlink control information including information specifying the first frequency hopping offset and the second frequency hopping offset in common when a second frequency hopping offset is applied in a second case in which the duplexing scheme is applied, in addition to 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 using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list for use in the second case is set separately from the first frequency hopping offset list for use in the first case, and 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.

[0358] The third feature is a wireless communication method comprising: receiving downlink control information that includes information specifying the first frequency hopping offset and the second frequency hopping offset in common when a second frequency hopping offset is applied in a second case in which the duplexing scheme is applied, in addition to a first frequency hopping offset applied in a first case in which the duplexing scheme is not applied, and a second frequency hopping offset applied in a second case in which the duplexing scheme is applied; and performing frequency hopping in the second case using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list for use in the second case is set separately from the first frequency hopping offset list for use in the first case, and 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.

[0359] This patent application claims priority based on Japanese Patent Application No. 2024-179945, filed on 15 October 2024, and the entire contents of Japanese Patent Application No. 2024-179945 are incorporated herein by reference.

[0360] 10 Wireless communication system 20 NG-RAN 100 gNB 110 Receiver 120 Transmitter 130 Control unit 200 UE 210 Wireless signal transmission / reception unit 220 Amplifier unit 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transmission / reception unit 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 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 service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed 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 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A terminal comprising: a receiving unit that receives downlink control information including information specifying the first frequency hopping offset and the second frequency hopping offset in common when a second frequency hopping offset is applied in a second case in which the duplexing method is applied, in addition to a first frequency hopping offset applied in a first case in which the duplexing method is not applied, and the first frequency hopping offset applied in a second case in which the duplexing method is applied; and a control unit that performs frequency hopping in the second case using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list for use in the second case is set separately from the first frequency hopping offset list for use in the first case, and 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 wireless communication system comprising a terminal and a base station, wherein the terminal includes a receiving unit that receives downlink control information including information specifying the first frequency hopping offset and the second frequency hopping offset in common when a second frequency hopping offset is applied in a second case in which the duplexing scheme is applied, in addition to a first frequency hopping offset applied in a first case in which the duplexing scheme is not applied, and the first frequency hopping offset applied in a second case in which the duplexing scheme is applied, and a control unit that performs frequency hopping in the second case using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list for use in the second case is set separately from the first frequency hopping offset list for use in the first case, and 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. A wireless communication method comprising: receiving downlink control information that includes information specifying the first frequency hopping offset and the second frequency hopping offset in common when a second frequency hopping offset is applied in a second case in which the duplexing scheme is applied, in addition to a first frequency hopping offset applied in a first case in which the duplexing scheme is not applied, and the second frequency hopping offset is applied in addition to a first frequency hopping offset applied in a first case in which the duplexing scheme is applied; and performing frequency hopping in the second case using the second frequency hopping offset specified by the information included in the downlink control information, wherein a second frequency hopping offset list for use in the second case is set separately from the first frequency hopping offset list for use in the first case, and 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