Terminal, communication method and integrated circuit

Abstract

This terminal is provided with: a control circuit which, when dynamic switching is set between a first transmission waveform for an uplink signal and a second transmission waveform having a greater data size than the first transmission waveform, determines a field size of control information on the basis of a field size in the case where the second transmission waveform is set; and a reception circuit which receives the control information on the basis of the field size.

Description

Terminal, base station and communication method

[0001] The present disclosure relates to a terminal, a base station, and a communication method.

[0002] In recent years, the expansion and diversification of wireless services has led to expectations for the dramatic development of the Internet of Things (IoT). Mobile communications are expanding beyond smartphones and other information terminals to include automobiles, homes, home appliances, industrial equipment, and a wide range of other applications. To support this diversification, significant improvements in the performance and functionality of mobile communication systems are essential, addressing various requirements, including not only increased system capacity but also an increased number of connected devices and low latency. Fifth-generation mobile communication systems (5G) boast high-capacity, ultra-high-speed data transfer (eMBB: enhanced Mobile BroadBand), massive machine-type communication (mMTC: massive machine-type communication), and ultra-reliable and low-latency communication (URLLC: ultra-reliable and low-latency communication). By leveraging these features, 5G will provide flexible wireless communications to meet a wide variety of needs.

[0003] The 3rd Generation Partnership Project (3GPP), an international standardization organization, is working on the specification of New Radio (NR) as one of the 5G wireless interfaces.

[0004] 3GPP TS38.104,“NR Base Station (BS) radio transmission and reception (Release 15),”March 2021.RP-202928,“New WID on NR coverage enhancements,”China Telecom, December 2020.RP-220937,“Revised WID on Further NR coverage enhancements,”China Telecom, March 2022.3GPP TS38.211, “NR Physical channels and modulation (Release 17),” March 2022.3GPP TS38.212, “NR Multiplexing and channel coding (Release 17),” March 2022.3GPP TS38.213, “NR Physical layer procedures for control (Release 17),” March 2022.3GPP TS38.214, “NR Physical layer procedures for data (Release 17),” March 2022.

[0005] Further study is needed on the transmission signals used in NR.

[0006] Non-limiting examples of the present disclosure contribute to providing a terminal, a base station, and a communication method that can improve the reception performance of signals in the uplink.

[0007] A terminal according to one embodiment of the present disclosure includes a control circuit that, when dynamic switching between a first transmission waveform of an uplink signal and a second transmission waveform having a data size larger than that of the first transmission waveform is configured, determines a field size of control information based on a field size when the second transmission waveform is configured, and a receiving circuit that receives the control information based on the field size.

[0008] According to an embodiment of the present disclosure, a transmission signal can be transmitted appropriately.

[0009] Further advantages and benefits of one embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features.

[0010] Method for determining the PUSCH transmit waveform in NR up to Release 17 Mapping table of the Precoding information and number of layers field in Case 3-1 Mapping table of the Precoding information and number of layers field in Case 3-2 Mapping table of the Precoding information and number of layers field in Case 4-1 Mapping table of the Precoding information and number of layers field in Case 4-2 Mapping table of the Precoding information and number of layers field in Case 4-3 Mapping table of the Precoding information and number of layers field in Case 5-1 Mapping table of the Precoding information and number of layers field in Case 5-2 Mapping table of the Precoding information and number of layers field in Case 6 Mapping table of the Antenna ports field for DFT-s-OFDM in Case A1 Mapping table of the Antenna ports field for CP-OFDM in Case A1 (number of transmission layers: 1) Mapping table of the Antenna ports field for CP-OFDM in Case A1 (number of transmission layers: 2) Antenna for CP-OFDM in Case A1 Mapping table of the antenna ports field (number of transmission layers: 3) Mapping table of the antenna ports field for CP-OFDM in case A1 (number of transmission layers: 4) Mapping table of the antenna ports field for DFT-s-OFDM in case A2 Mapping table of the antenna ports field for CP-OFDM in case A2 (number of transmission layers: 1) Mapping table of the antenna ports field for CP-OFDM in case A2Mapping table of the antenna ports field (number of transmission layers: 2)Mapping table of the antenna ports field for CP-OFDM in case A2 (number of transmission layers: 3)Mapping table of the antenna ports field for CP-OFDM in case A2 (number of transmission layers: 4)Mapping table of the antenna ports field for CP-OFDM in case B1 (number of transmission layers: 1)Mapping table of the antenna ports field for CP-OFDM in case B1 (number of transmission layers: 2)Mapping table of the antenna ports field for CP-OFDM in case B1 (number of transmission layers: 3)Mapping table of the antenna ports field for CP-OFDM in case B1 (number of transmission layers: 4)Mapping table of the antenna ports field for CP-OFDM in case B2 (number of transmission layers: 1)Mapping table of the antenna ports field for CP-OFDM in case B2 (number of transmission layers: 2)Mapping table of the antenna ports field for CP-OFDM in case B2 (number of transmission layers: 3)Mapping table of the antenna ports field for CP-OFDM in case B2 Mapping table of ports field (number of transmission layers: 4) Flowchart Base station configuration Terminal configuration NG-RAN architecture Separation of functions between NG-RAN and 5GC Interaction between UE, gNB, and AMF (5GC entity) Use case for 5G NR Non-roaming reference architecture of 5G NR Block diagram showing an example configuration of a part of a base station 100 Block diagram showing an example configuration of a part of a terminal 200 Example of MCS table Another example of MCS table

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0012] NR will utilize frequency bands below 6 GHz (FR1: Frequency Range 1), such as the 700 MHz to 3.5 GHz band, which have traditionally been used for cellular communications, as well as millimeter wave bands (FR2) such as 28 GHz and 39 GHz, which can secure wide bandwidth (Non-Patent Document 1). Even within FR1, there is a possibility that higher frequency bands, such as 3.5 GHz, will be used compared to Long Term Evolution (LTE) and 3G.

[0013] As the frequency band becomes higher, propagation loss increases and reception quality deteriorates, so NR is expected to maintain appropriate communication quality for a communication area (coverage) similar to that of conventional radio access technologies (RATs) such as LTE and 3G. 3GPP Release 17 (Rel. 17) and Release 18 (Rel. 18) are considering improving NR coverage (Non-Patent Documents 2 and 3).

[0014] In NR, a terminal (e.g., user equipment (UE)) transmits and receives data in accordance with resource allocation indicated by layer 1 control signals (e.g., Downlink Control Information (DCI)) on a downlink control channel (e.g., Physical Downlink Control Channel (PDCCH)) from a base station (e.g., gNB) or layer 3 Radio Resource Control (RRC) (see Non-Patent Documents 4 to 7).

[0015] In the uplink (UL), a terminal transmits an uplink data channel (for example, a Physical Uplink Shared Channel (PUSCH)) in accordance with resource allocation (for example, a Grant or UL grant) from a base station.

[0016] NR supports both Discrete Frourier Transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) and Cyclic prefix-OFDM (CP-OFDM) as PUSCH transmission waveforms. DFT-s-OFDM has a lower peak-to-average power ratio (PAPR) and higher power utilization efficiency, ensuring wider uplink coverage than CP-OFDM. On the other hand, CP-OFDM is highly compatible with Multiple-Input Multiple-Output (MIMO), making it an effective transmission waveform for high-efficiency transmission in high Signal-to-Interference and Noise power Ratio (SINR) environments (e.g., multi-rank or multi-layer transmission in spatial multiplexing transmission).

[0017] In NR up to Rel. 17, the PUSCH transmission waveform is set semi-statically by RRC. Figure 1 shows a method for determining the PUSCH transmission waveform in NR up to Rel. 17.

[0018] The transmission waveform of Message 3 PUSCH is determined based on msg3-transformPrecoder, a parameter set by RRC. The transmission waveform of Message A PUSCH is determined based on msgA-transformPrecoder, a parameter set by RRC. If msgA-transformPrecoder is not set by RRC, the transmission waveform is determined based on msg3-transformPrecoder.

[0019] The transmission waveform of a PUSCH (for example, DG-PUSCH: Dynamic Grant-PUSCH) that is dynamically scheduled in DCI format 0-0 is determined based on msg3-transformPrecoder, which is a parameter set by RRC.

[0020] The transmit waveform of PUSCH dynamically scheduled in DCI format 0-1 or DCI format 0-2 is determined based on the transformPrecoder parameter included in pusch-Config configured by RRC. If transformPrecoder is not configured by RRC, the transmit waveform is determined based on msg3-transformPrecoder.

[0021] The transmission waveform of a PUSCH (for example, CG-PUSCH: Configured grant-PUSCH) that transmits a PUSCH using resource allocation instructed by RRC, which is layer 3, or semi-static resource allocation by Activation DCI, is determined based on transformPrecoder, which is a parameter included in configuredGrantConfig, which is set by RRC. If transformPrecoder is not set by RRC, the transmission waveform is determined based on msg3-transformPrecoder.

[0022] In addition, in NR up to Rel. 17, the number of transmission layers for PUSCH transmission using DFT-s-OFDM is limited to one.

[0023] In a typical cellular system, DFT-s-OFDM is typically configured to ensure coverage for cell-edge terminals, where improving uplink coverage is crucial. However, even cell-edge terminals may experience situations where they transmit PUSCHs with a high SINR due to instantaneous fluctuations in the channel or interference environment. In such cases, the constraint that the transmit waveform can only be configured quasi-statically makes it difficult for cell-edge terminals configured with DFT-s-OFDM to switch their transmit waveform to CP-OFDM to adapt to the instantaneous fluctuations and perform highly efficient transmission (e.g., multi-layer transmission using MIMO spatial multiplexing), making it impossible to improve the transmission efficiency of cell-edge terminals.

[0024] Dynamically switching the DCI format for scheduling the PUSCH and dynamically changing the transmission waveform of the PUSCH are being considered.

[0025] As an example, DFT-s-OFDM can be configured for PUSCH scheduled with DCI format 0-0, and CP-OFDM can be configured for PUSCH scheduled with DCI format 0-1. However, DCI format 0-0 only supports PUSCH allocation with the minimum necessary functionality, which imposes significant restrictions on PUSCH scheduling using DFT-s-OFDM transmission waveforms. Specifically, cross-carrier scheduling in carrier aggregation, Bandwidth Part (BWP) switching, precoding and antenna port notification, and Code Block Group (CBG)-based retransmission control are not possible.

[0026] As another example, CP-OFDM can be configured for the PUSCH scheduled by DCI format 0-0, and DFT-s-OFDM can be configured for the PUSCH scheduled by DCI format 0-1. However, DCI format 0-0 only supports single-layer transmission, and PUSCH transmission of a DFT-s-OFDM transmission waveform also only supports single-layer transmission, so highly efficient transmission using multiple layer transmission of two or more layers is not possible.

[0027] One possible method for dynamically switching the transmit waveform in a single DCI format (for example, only DCI format 0-1 or DCI format 0-2) is to add a field to the DCI format to indicate the transmit waveform. However, introducing a transmit waveform indication field would increase the number of DCI bits. In particular, DCI formats 0-2 are DCIs designed for URLLC, and it is desirable to increase the reliability of DCI reception by reducing the number of DCI bits as much as possible, so increasing the number of DCI bits is undesirable.

[0028] It is expected to provide a terminal device, a base station device, a communication method, and a control system that can dynamically notify the transmission waveform of a PUSCH using a single DCI without adding a field for notifying the transmission waveform to the DCI.

[0029] Specifically, when dynamic transmission waveform switching is configured for a terminal, the base station determines the field size of each existing DCI based on the field size when CP-OFDM is configured as the transmission waveform, and notifies the PUSCH transmission waveform using the existing DCI field. This makes it possible to notify dynamic transmission waveforms without increasing the number of DCI bits.

[0030] Dynamic transmit waveform switching for DG-PUSCH with DCI format 0-1 or DCI format 0-2 is enabled via RRC.

[0031] After dynamic transmit waveform switching is enabled, DCI must be received to actually perform the enabled dynamic transmit waveform switching, and the DCI field size must be determined in order to receive DCI.

[0032] That is, when dynamic transmit waveform switching is enabled, the DCI field size must be determined in advance, and the DCI field size is determined based on the CP-OFDM size, which is larger than the DFT-s-OFDM size. Note that if the DFT-s-OFDM DCI field size is larger than the CP-OFDM field size, the DCI field size may be determined based on the DFT-OFDM size. The transmit waveforms are not limited to DFT-s-OFDM and CP-OFDM, and three or more transmit waveforms can also be used. When there are three or more transmit waveforms, the DCI field size is determined based on the largest size, but it is also possible to use a transmit waveform that is not the largest.

[0033] In one example, the DCI fields include: Frequency domain resource assignment, Precoding information and number of layers, Antenna ports, PTRS-DMRS association, and DMRS sequence initialization.

[0034] Whether the transmission waveform is CP-OFDM or DFT-s-OFDM, and whether transform precoding is enabled or disabled, are signaled by repurposing existing fields in DCI format 0-1 or DCI format 0-2.

[0035] This enables dynamic transmission waveform switching without increasing the number of DCI bits.

[0036] Non-limiting embodiments of the present disclosure will be described below.

[0037] Referring to FIG. 28, in step 1, the terminal determines whether dynamic transmission waveform switching is enabled.

[0038] If dynamic transmit waveform switching is enabled in step 1, the terminal determines a DCI field size based on CP-OFDM in step 2. The terminal also receives DCI and determines the number of transmission layers according to the determined DCI field size.

[0039] In step 3, the terminal determines the transmission waveform based on the number of transmission layers. For example, if one-layer transmission is indicated, the terminal determines the transmission waveform to be DFT-s-OFDM, and if two or more layer transmissions are indicated, the terminal determines the transmission waveform to be CP-OFDM.

[0040] If dynamic transmit waveform switching is not enabled in step 1, the terminal determines the transmit waveform based on RRC parameters and determines the DCI field size based on the semi-statically configured transmit waveform.

[0041] (Embodiment 1) In this embodiment, the terminal determines the transmission waveform of the PUSCH based on the number of transmission layers notified to the terminal by the Precoding information and number of layers field or the SRI field included in the DCI.

[0042] [Step 1] Whether dynamic transmission waveform switching is enabled or disabled for DG-PUSCH dynamically scheduled in DCI format 0-1 or DCI format 0-2 is configured by RRC. For example, dynamic transmission waveform switching may be enabled by the following method. If set to Disabled, the terminal performs semi-static transmission waveform switching.

[0043] <Method 1 for enabling dynamic transmit waveform switching> Dynamic transmit waveform switching is enabled using a new parameter value (dynamicSwitch) of the parameter (transformPrecoder) in PUSCH-ConfigIE. Dynamic transmit waveform switching is enabled based on dynamicSwitch, which is the new parameter value of transformPrecoder included in pusch-Config for a PUSCH that is dynamically scheduled in DCI format 0-1 or DCI format 0-2.

[0044] Specifically, when the value of transformPrecoder is set to dynamicSwitch, the terminal dynamically determines the transmission waveform of the PUSCH based on information notified by DCI, which will be described later. That is, the terminal determines whether to apply DFT-s-OFDM or CP-OFDM to the PUSCH. Note that the value "dynamicSwitch" set in transformPrecoder is an example and is not limited to this.

[0045] On the other hand, when the value of transformPrecoder is set to enabled, the terminal may enable semi-static transmission waveform switching of the PUSCH. Instead of enabling semi-static transmission waveform switching, the terminal may set the transmission waveform of the PUSCH to DFT-s-OFDM semi-statically.

[0046] Furthermore, when the value of transformPrecoder is set to disabled, the terminal may disable semi-static transmission waveform switching of the PUSCH. Instead of disabling semi-static transmission waveform switching, the terminal may set the transmission waveform of the PUSCH to CP-OFDM semi-statically.

[0047] Furthermore, if transformPrecoder is not set, the terminal determines the transmission waveform based on msg3-transformPrecoder.

[0048] <Method 2 for enabling dynamic transmission waveform switching> A new RRC parameter, transformPrecoderDynamic, is introduced into pusch-ConfigIE for PUSCH that is dynamically scheduled in DCI format 0-1 or DCI format 0-2, and dynamic transmission waveform switching is enabled based on transformPrecoderDynamic.

[0049] Specifically, when transformPrecoderDynamic is set in pusch-ConfigIE, the terminal determines that the value of the existing RRC parameter transformPrecoder is invalid (i.e., discards the value of transformPrecoder), enables dynamic transmission waveform switching, and performs steps 2 and 3 shown in FIG. 28 .

[0050] When transformPrecoderDynamic is not set and the value of transformPrecoder is set to enabled, the terminal may enable semi-static transmission waveform switching for the PUSCH transmission waveform. Instead of enabling semi-static transmission waveform switching, the terminal may set the PUSCH transmission waveform to DFT-s-OFDM semi-statically.

[0051] When transformPrecoderDynamic is not set and the value of transformPrecoder is set to disabled, the terminal may disable semi-static transmission waveform switching of the PUSCH. Instead of disabling semi-static transmission waveform switching, the terminal may set the transmission waveform of the PUSCH to CP-OFDM semi-statically.

[0052] If transformPrecoderDynamic is not set and transformPrecoder is not set, the terminal determines the transmission waveform based on msg3-transformPrecoder.

[0053] [Step 2] In the first embodiment, the terminal uses the Precoding information and number of layers field, among the parameters included in the DCI, to determine the number of layers. The following describes a method for determining the size (number of bits) of the Precoding information and number of layers field required to receive the Precoding information and number of layers field.

[0054] When dynamic transmit waveform switching is enabled, the size (number of bits) of the Precoding information and number of layers field of the DCI is set to the same number of bits as when the CP-OFDM transmit waveform is set quasi-statically. Specifically, this is as follows:

[0055] In addition, if the DCI field size is used when a transmission waveform other than CP-ODFM is set in step 1, the size (number of bits) of the Precoding information and number of layers field can be determined based on the DCI field size of the transmission waveform used.

[0056] (Case 1) When the RRC parameter txConfig included in the pusch-Config IE is set to nonCodeBook, the number of bits in the Precoding information and number of layers field is 0.

[0057] (Case 2) When the RRC parameter txConfig included in the pusch-Config IE is set to codebook and the number of antenna ports is set to 1, the number of bits in the Precoding information and number of layers field is 0.

[0058] (Case 3) If the RRC parameter txConfig included in the pusch-Config IE is set to codebook, the number of antenna ports is set to 4, and ul-FullPowerTransmission is not set or the value of ul-FullPowerTransmission is set to fullpowerMode2 or fullpower,

[0059] (Case 3-1) When the RRC parameter maxRank is set to 2, 3, or 4, the number of bits in the Precoding information and number of layers field is either 4, 5, or 6 bits.

[0060] (Case 3-2) When the RRC parameter maxRank is set to 1, the number of bits in the Precoding information and number of layers field is either 2, 4, or 5 bits.

[0061] (Case 4) When the RRC parameter txConfig included in the pusch-Config IE is set to codebook, the number of antenna ports is set to 4, and the value of ul-FullPowerTransmission is set to fullpowerMode1,

[0062] (Case 4-1) When the RRC parameter maxRank is set to 2, the number of bits in the Precoding information and number of layers field is either 4 or 5 bits.

[0063] (Case 4-2) When the RRC parameter maxRank is set to 3 or 4, the number of bits in the Precoding information and number of layers field is either 4 or 6 bits.

[0064] (Case 4-3) When the RRC parameter maxRank is set to 1, the number of bits in the Precoding information and number of layers field is either 3 or 4 bits.

[0065] (Case 5) If the RRC parameter txConfig included in the pusch-Config IE is set to codebook, the number of antenna ports is set to 2, and ul-FullPowerTransmission is not set or the value of ul-FullPowerTransmission is set to fullpowerMode2 or fullpower,

[0066] (Case 5-1) When the RRC parameter maxRank is set to 2, the number of bits in the Precoding information and number of layers field is either 2 or 4 bits.

[0067] (Case 5-2) When the RRC parameter maxRank is set to 1, the number of bits in the Precoding information and number of layers field is either 1 or 3 bits.

[0068] (Case 6) When the RRC parameter txConfig included in the pusch-Config IE is set to codebook, the number of antenna ports is set to 2, and the value of ul-FullPowerTransmission is set to fullpowerMode1, the number of bits in the Precoding information and number of layers field is 2 bits.

[0069] [Step 3] When the number of bits of the Precoding information and number of layers field is determined, the terminal can receive the Precoding information and number of layers field. The terminal determines the number of transmission layers for PUSCH transmission based on, for example, information in the Precoding information and number of layers field or the SRI field of the DCI. The terminal also determines the transmission waveform of the PUSCH based on the determined number of transmission layers.

[0070] Specifically, when the number of transmission layers is 1, the terminal determines the PUSCH transmission waveform to be DFT-s-OFDM. On the other hand, when the number of transmission layers is 2 or more, the terminal determines the PUSCH transmission waveform to be CP-OFDM. The method of determining the transmission waveform in step 3 for each case of step 2 described above is as follows.

[0071] (Case 1) The number of bits in the Precoding information and number of layers is 0, so the terminal determines the number of transmission layers based on the information in the SRI field. For example, if the determined number of transmission layers is 1, the terminal determines the PUSCH transmission waveform to be DFT-s-OFDM, and if the determined number of transmission layers is 2 or more, the terminal determines the PUSCH transmission waveform to be CP-OFDM.

[0072] (Case 2) The terminal determines the number of transmission layers to be 1 and the transmission waveform to be DFT-s-OFDM.

[0073] (Case 3-1) The terminal determines the number of transmission layers and a Transmit Precoding Matrix Index (TPMI) based on the mapping table given in Figure 2 and information in the Precoding information and number of layers field (for example, the value of the Bit field mapped to index in Figure 2). If the determined number of transmission layers is 1, the terminal determines the PUSCH transmission waveform to be DFT-s-OFDM, and if the determined number of transmission layers is 2 or more, the terminal determines the PUSCH transmission waveform to be CP-OFDM.

[0074] (Case 3-2) The terminal determines the number of transmission layers to be 1 and the transmission waveform to be DFT-s-OFDM. The terminal also determines the TPMI based on the mapping table given in Figure 3 and the information in the Precoding information and number of layers fields (e.g., the value of the Bit field mapped to index in Figure 3).

[0075] (Case 4-1) The terminal determines the number of transmission layers and the TPMI based on the mapping table given in Fig. 4 and the information in the Precoding information and number of layers field (for example, the value of the Bit field mapped to index in Fig. 4). If the determined number of transmission layers is 1, the terminal determines the PUSCH transmission waveform to be DFT-s-OFDM, and if the determined number of transmission layers is 2 or more, the terminal determines the PUSCH transmission waveform to be CP-OFDM.

[0076] (Case 4-2) The terminal determines the number of transmission layers and the TPMI based on the mapping table given in Fig. 5 and the information in the Precoding information and number of layers field (for example, the value of the Bit field mapped to index in Fig. 5). If the determined number of transmission layers is 1, the terminal determines the PUSCH transmission waveform to be DFT-s-OFDM, and if the determined number of transmission layers is 2 or more, the terminal determines the PUSCH transmission waveform to be CP-OFDM.

[0077] (Case 4-3) The terminal determines the number of transmission layers to be 1 and the transmission waveform to be DFT-s-OFDM. The terminal also determines the TPMI based on the mapping table given in FIG. 6 and the information in the Precoding information and number of layers fields (e.g., the value of the Bit field mapped to index in FIG. 6).

[0078] (Case 5-1) The terminal determines the number of transmission layers and the TPMI based on the mapping table given in Fig. 7 and the information in the Precoding information and number of layers field (for example, the value of the Bit field mapped to index in Fig. 7). If the determined number of transmission layers is 1, the terminal determines the PUSCH transmission waveform to be DFT-s-OFDM, and if the determined number of transmission layers is 2 or more, the terminal determines the PUSCH transmission waveform to be CP-OFDM.

[0079] (Case 5-2) The terminal determines the number of transmission layers to be 1, and the transmission waveform to be DFT-s-OFDM. It also determines the TPMI based on the mapping table given in FIG. 8 and the information in the Precoding information and number of layers fields (for example, the value of the Bit field mapped to index in FIG. 8).

[0080] (Case 6) The terminal determines the number of transmission layers and the TPMI based on the mapping table given in Fig. 9 and the information in the Precoding information and number of layers field (for example, the value of the Bit field mapped to index in Fig. 9). If the determined number of transmission layers is 1, the terminal determines the PUSCH transmission waveform to be DFT-s-OFDM, and if the determined number of transmission layers is 2 or more, the terminal determines the PUSCH transmission waveform to be CP-OFDM.

[0081] According to the present embodiment, the transmission waveform of the PUSCH can be notified using the existing DCI field, Precoding information and number of layers or SRI field, so that dynamic transmission waveform notification becomes possible without increasing the number of DCI bits for switching the transmission waveform. Dynamic switching of the transmission waveform depending on the number of transmission layers enables flexibly switching between ensuring coverage using DFT-s-OFDM and single-layer transmission and highly efficient transmission using CP-OFDM and multi-layer transmission.

[0082] Furthermore, according to the present embodiment, when dynamically switching the transmission waveform between CP-OFDM and DFT-s-OFDM, the terminal determines the field size of the DCI based on the field size of the DCI when CP-OFDM is configured. As a result, even when dynamically switching the transmission waveform for a single DCI format (for example, DCI format 0-1 or DCI format 0-2), the terminal can grasp the field size of the DCI and properly receive the DCI regardless of the switched transmission waveform.

[0083] (Embodiment 2) In this embodiment, the terminal determines the transmission waveform of the PUSCH based on the number of transmission layers and the TPMI notified to the terminal by the Precoding information and number of layers field or the SRI field included in the DCI.

[0084] In the second embodiment, among the parameters included in the DCI, the Precoding information and number of layers field is used to determine the number of layers, but the method of determining the size (number of bits) of the Precoding information and number of layers field required to receive the Precoding information and number of layers field (i.e., steps 1 and 2) is the same as in the first embodiment.

[0085] Step 3 differs from embodiment 1 in that the PUSCH transmission waveform is determined based on the TPMI value when the number of transmission layers is 1. The mapping between the TPMI and the transmission waveform may be determined in advance or may be notified by RRC. Furthermore, a threshold may be set for the TPMI, and the transmission waveform may be set to DFT-s-OFDM when the notified TPMI is greater than the threshold, and the transmission waveform may be set to CP-OFDM when the notified TPMI is less than or equal to the threshold. Note that the transmission waveform may be set to CP-OFDM when the notified TPMI is greater than the threshold, and the transmission waveform may be set to DFT-s-OFDM when the TPMI is less than or equal to the threshold.

[0086] [Step 3] The terminal determines the PUSCH transmission waveform based on the determined number of transmission layers and TPMI.

[0087] Specifically, when the number of transmission layers is 1, the terminal determines the transmission waveform of the PUSCH based on the value of TPMI. On the other hand, when the number of transmission layers is 2 or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM. The method of determining the transmission waveform in step 3 for each case of step 2 described above is as follows.

[0088] (Case 1) The terminal determines the number of transmission layers based on information in the SRI field. If the determined number of transmission layers is 1, the terminal determines the PUSCH transmission waveform based on the SRI. If the determined number of transmission layers is 2 or more, the terminal determines the PUSCH transmission waveform to be CP-OFDM.

[0089] (Case 2) The terminal determines the number of transmission layers to be 1 and the transmission waveform to be DFT-s-OFDM.

[0090] (Case 3-1) Based on the mapping table given in Figure 2, if the number of determined transmission layers is 1, the terminal determines the transmission waveform of the PUSCH based on the value of TPMI, and if the number of determined transmission layers is 2 or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM.

[0091] (Case 3-2) The terminal determines the transmission waveform of the PUSCH based on the value of TPMI, based on the mapping table given in FIG.

[0092] (Case 4-1) Based on the mapping table given in Figure 4, if the number of determined transmission layers is 1, the terminal determines the transmission waveform of the PUSCH based on the value of TPMI, and if the number of determined transmission layers is 2 or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM.

[0093] (Case 4-2) Based on the mapping table given in Figure 5, if the number of determined transmission layers is 1, the terminal determines the transmission waveform of the PUSCH based on the value of TPMI, and if the number of determined transmission layers is 2 or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM.

[0094] (Case 4-3) The terminal determines the transmission waveform of the PUSCH based on the value of TPMI, based on the mapping table given in FIG.

[0095] (Case 5-1) Based on the mapping table given in Figure 7, if the number of determined transmission layers is 1, the terminal determines the transmission waveform of the PUSCH based on the value of TPMI, and if the number of determined transmission layers is 2 or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM.

[0096] (Case 5-2) The terminal determines the transmission waveform of the PUSCH based on the value of TPMI, based on the mapping table given in FIG.

[0097] (Case 6) Based on the mapping table given in FIG. 9, if the determined number of transmission layers is 1, the terminal determines the PUSCH transmission waveform based on the TPMI value, and if the determined number of transmission layers is 2 or more, the terminal determines the PUSCH transmission waveform to be CP-OFDM.

[0098] The association between the TPMI value and the transmission waveform of the PUSCH (for example, the transmission waveform when TPMI=n is notified) may be determined in advance, or the association may be set by RRC.

[0099] In the association by RRC, association between each TPMI number and a transmission waveform may be notified, or a threshold value of the TPMI number at which the transmission waveform is switched may be notified.

[0100] When a threshold is set, for example, TPMI numbers equal to or less than the threshold may be associated with DFT-s-OFDM, and TPMI numbers greater than the threshold may be associated with CP-OFDM, or, for example, TPMI numbers equal to or less than the threshold may be associated with CP-OFDM, and TPMI numbers greater than the threshold may be associated with DFT-s-OFDM.

[0101] Alternatively, multiple thresholds may be set according to the number of transmit waveforms, such that a TPMI number equal to or less than a first threshold is associated with a first transmit waveform, a TPMI number greater than the first threshold and equal to or less than a second threshold is associated with a second transmit waveform, and a TPMI number greater than the second threshold is associated with a third transmit waveform.

[0102] In addition, the number of TPMI numbers associated with DFT-s-OFDM, N TPMI In this case, for example, TPMI=0 to N TPMI TPMI numbers up to -1 may be associated with DFT-s-OFDM, and the other TPMI numbers may be associated with CP-OFDM. Furthermore, the association between the TPMI value and the PUSCH transmission waveform may be different for each of the above-mentioned cases, or the same association may be used. Furthermore, the number of TPMI numbers associated with DFT-s-OFDM may be different from the number of TPMI numbers associated with CP-OFDM.

[0103] According to the present embodiment, the transmission waveform of the PUSCH can be notified using the existing DCI field, Precoding information and number of layers or SRI field, thereby enabling dynamic transmission waveform notification without increasing the number of DCI bits for switching the transmission waveform. Dynamic switching of the transmission waveform depending on the number of transmission layers enables flexible switching between ensuring coverage using DFT-s-OFDM and single-layer transmission and highly efficient transmission using CP-OFDM and multi-layer transmission. Furthermore, in single-layer transmission, the transmission waveform is determined based on the TPMI as well, allowing for more flexible switching of the transmission waveform.

[0104] Third Embodiment Step 1 of the operation example of the third embodiment may be the same as that of the first embodiment.

[0105] In embodiment 3, the terminal determines the transmission waveform of the PUSCH based on the index notified to the terminal by the Time Domain Resource Assignment (TDRA) field included in the DCI, so in step 2, a method for determining the number of TDRA bits required to receive the TDRA will be described.

[0106] [Step 2] The number of TDRA bits is the same for both CP-OFDM and DFT-s-OFDM. The terminal sets the size (number of bits) of the TDRA field in the DCI. bits, where I is the number of registrations in the RRC parameter pusch-TimeDomainAllocationList.

[0107] The sizes (number of bits) of other fields, such as the Precoding information and number of layers field of DCI and the Antenna ports field, are determined based on CP-OFDM. As described in the first embodiment, they can also be determined based on DFT-s-OFDM.

[0108] The TDRA may include a slot offset K2, a start / length indicator SLIV or a start symbol S and the number of symbols (PUSCH length) L, a PUSCH mapping type, the number of repeated transmissions, and a transmission waveform applied to the PUSCH.

[0109] Furthermore, the terminal may determine the size (number of bits) of the Precoding Information and Number of Layers field of the DCI. The method of determining the size (number of bits) of the Precoding Information and Number of Layers field is the same as in the first and second embodiments.

[0110] [Step 3] The terminal determines the time domain resource allocation and transmission waveform for PUSCH transmission based on the information in the TDRA field of the DCI. Specifically, based on the index notified in the TDRA field, the terminal determines the time domain allocation resource candidates (i.e., the combination of K2, S, L, PUSCH mapping type, repetition count, and transmission waveform) associated with that index.

[0111] Information on time domain resource candidates associated with TDRA indices can be notified by RRC.

[0112] The correspondence between the TDRA index value and the PUSCH transmission waveform (for example, the transmission waveform when index n is notified) may be configured by RRC. Furthermore, the number of indexes associated with DFT-s-OFDM may be different from the number of indexes associated with CP-OFDM.

[0113] Furthermore, when the terminal determines that the transmission waveform of the PUSCH is DTF-s-OFDM based on the information in the TDRA field, it does not assume that the number of transmission layers, two or more, will be notified by the Precoding information and number of layers field.

[0114] According to the present embodiment, the transmission waveform of the PUSCH can be notified using the TDRA field, which is an existing DCI field, and therefore, dynamic transmission waveform notification becomes possible without increasing the number of DCI bits for switching the transmission waveform.

[0115] (Embodiment 4) In Embodiment 4, a terminal determines a PUSCH transmission waveform based on an index notified to the terminal by a modulation and coding scheme (MCS) field included in DCI. The following describes a method for determining the size of the MCS field required to receive the MCS field.

[0116] Step 1 of the fourth embodiment may be the same as that of the first embodiment.

[0117] [Step 2] Because the size (number of bits) of the MCS field of DCI is 5 bits for both CP-OFDM and DFT-s-OFDM, the terminal sets the size (number of bits) of the MCS field to 5 bits. The sizes (number of bits) of other fields, such as the DCI Precoding Information and Number of Layers field and Antenna Ports, are determined based on CP-OFDM. As described in the first embodiment, they can also be determined based on DFT-s-OFDM.

[0118] [Step 3] The terminal receives the DCI MCS Using this, the modulation multi-level number Q is calculated from the MCS table. m , and determine the target coding rate R. Specifically, the terminal uses the index I MCS The transmit waveform is determined based on the above.

[0119] I MCS The correspondence between the value of and the PUSCH transmission waveform (for example, I MCS=n The transmission waveform when the I is notified may be determined in advance by a standard, or the correspondence may be set by RRC. MCS The correspondence with each transmission waveform may be notified, or the threshold value of the MCS number (waveform-MCS) for switching the transmission waveform may be notified.

[0120] When a threshold is set, for example, MCS numbers equal to or less than the threshold may be associated with DFT-s-OFDM, and MCS numbers greater than the threshold may be associated with CP-OFDM. When targeting a wide area using DFT-s-OFDM, the coding rate is often lowered to increase reliability, while CP-OFDM aims for high efficiency, so it is effective to assign a high coding rate (high MCS number) to CP-OFDM.

[0121] However, MCS numbers below the threshold may be associated with CP-OFDM, and MCS numbers above the threshold may be associated with DFT-s-OFDM, thereby increasing the reliability of coding when aiming for high efficiency in the transmission waveform.

[0122] Also, the number of MCS numbers associated with DFT-s-OFDM, N MCS In this case, for example, I MCS =0 to N MCS -1 corresponds to DFT-s-OFDM, and the other I MCS may be mapped to CP-OFDM. MCS =0 to N MCS -1 corresponds to CP-OFDM, and the other I MCS may be mapped to DFT-s-OFDM.

[0123] Furthermore, the number of MCS numbers associated with DFT-s-OFDM may be different from the number of MCS numbers associated with CP-OFDM.

[0124] According to the present embodiment, the transmission waveform of the PUSCH can be notified using the MCS field, which is an existing DCI field, and therefore it is possible to notify dynamic transmission waveforms without increasing the number of DCI bits for switching the transmission waveform.

[0125] (Modification of the Fourth Embodiment) According to Non-Patent Document 7, the NR MCS table includes the modulation multi-level number Q m and determine the target coding rate R MCS and the modulation multi-value number Q m Only I decide MCS For example, in an MCS table containing 256QAM for CP-OFDM or an MCS table for DFT-s-OFDM, 0<=I MCS <=27 is the modulation multi-value Q m and determine the target coding rate R MCS The value of 28 is (Figure 38), and 28<=I MCS <=31 is the modulation multi-value Q m Only I decide MCS In addition, for MCS tables that include up to 64QAM for CP-OFDM (i.e., excluding 256QAM), 0<=I MCS <=28 is the modulation multi-value Q m and determine the target coding rate R MCS The value of 29<=IMCS <=31 is the modulation multi-value Q m Only I decide MCS Generally, at the time of the first transmission, the modulation multi-level number Q m and determine the target coding rate R MCS The value of Q is notified, and at the time of retransmission, m Only I decide MCS The value of is reported.

[0126] Modulation multi-value number Q m Only I decide MCS The value of is the modulation multi-level number Q m and determine the target coding rate R MCS In Figure 38, the spectral efficiency does not increase as the MCS number increases from the value of I MCS =28, and in Figure 39, I MCS = 29, modulation multi-value Q m becomes smaller once, and even if the MCS number becomes larger, the target coding rate R is not determined, so the spectral efficiency is also undetermined. Therefore, the fourth embodiment cannot be applied as it is to the retransmission. Therefore, in this modification, m Only I decide MCS This section describes how to determine the transmit waveform when the value of

[0127] The following modifications 1 to 3 describe the determination of the transmission waveform at the time of retransmission, and the transmission waveform determination method in embodiment 4 may be used for determining the transmission waveform at the time of initial transmission. The threshold value of the MCS number (waveform-MCS) for switching the transmission waveform at the time of initial transmission or the number N of MCS numbers associated with DFT-s-OFDM is MCS The range of values ​​that can be taken by is determined by the modulation multi-level number Q m and determine the target coding rate R MCS The value may be:

[0128] When a threshold is set, for example, MCS numbers below the threshold are associated with DFT-s-OFDM, and the modulation multi-level number Q m and determine the target coding rate R MCSMCS numbers greater than a threshold in the range of values ​​may be associated with CP-OFDM.

[0129] Also, the number of MCS numbers associated with DFT-s-OFDM, N MCS If you are notified, for example, MCS =0 to N MCS -1 corresponds to DFT-s-OFDM, and the modulation level Q m and determine the target coding rate R MCS Other I values ​​in the range MCS may be mapped to CP-OFDM.

[0130] (First Modification of Fourth Embodiment) In this modification, the transmission waveform at the time of retransmission is determined to be the same as the transmission waveform of the PUSCH that transmitted the same transport block immediately before. This modification has the advantage that the process for determining the transmission waveform at the time of retransmission can be omitted, thereby simplifying the process for determining the transmission waveform.

[0131] (Second Variation of Fourth Embodiment) In this variation, the transmission waveform at the time of retransmission is determined based on the number of transmission layers notified to the terminal. For example, if the number of transmission layers is 1, the terminal determines the transmission waveform of the PUSCH to be DFT-s-OFDM. On the other hand, if the number of transmission layers is two or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM. This variation makes it possible to dynamically notify the transmission waveform even at the time of retransmission. Dynamically switching the transmission waveform depending on the number of transmission layers makes it possible to ensure coverage using DFT-s-OFDM and single-layer transmission, and flexibly switch between highly efficient transmission using CP-OFDM and multi-layer transmission.

[0132] (Third Modification of Fourth Embodiment) In this modification, the transmission waveform at the time of retransmission is determined based on the modulation level notified to the terminal. Any of the following options may be applied to the correspondence between the modulation level and the transmission waveform.

[0133] <Option 1> The correspondence between the modulation level and the transmission waveform is determined in advance. For example, QPSK (Q m =2) or 16QAM(Q m=4), DFT-s-OFDM is used, and 64QAM (Q m =6)256QAM(Q m The correspondence between the modulation level Q and the transmission waveform may be predetermined in the standard, or may be set by the upper layer (RRC signaling). Also, as in the fourth embodiment, the modulation level Q m Only I decide MCS For the value of MCS may be notified.

[0134] <Option 2> Modulation multi-value number Q m Only I decide MCS For the value of m and determine the target coding rate R MCS The correspondence between the values ​​of and is determined in advance, and at the time of retransmission, the modulation multi-level number Q m Only I decide MCS The modulation multi-value Q corresponding to the value of m and determine the target coding rate R MCS The transmission waveform is determined from the value of the corresponding "modulation multi-value number Q m and determine the target coding rate R MCS The same modulation multi-value Q m Multiple I with MCS The smallest I value MCS For example, in the MCS table including 256QAM for CP-OFDM shown in FIG. m and determine the target coding rate R MCS The minimum index value for each modulation level is QPSK(Q m =2) I MCS =0, 16QAM(Q m =4) in I MCS =5, 64QAM(Q m =6) in I MCS =11, 256QAM(Q m =8) in I MCS= 20. In other words, the transmit waveform is determined by the I MCS =28(Q m =2) is I MCS =0, I MCS =29(Q m =4) is I MCS =5, I MCS =30(Q m =6) is I MCS =11, I MCS =31(Q m =8) for I MCS = 20, and the transmission waveform may be determined in the same way as in the first transmission.

[0135] In addition, the modulation multi-level number Q corresponding to the modulation multi-level number at the time of retransmission is m and determine the target coding rate R MCS The index for each modulation level is not limited to the minimum index value. The maximum index value may be associated with the index. Also, a value offset from the minimum index value (or maximum index value) may be used. Also, the index value may be predetermined according to the standard, or may be set by a higher layer (RRC signaling). Also, the offset value from the minimum index value (or maximum index value) may be predetermined according to the standard, or may be set by a higher layer (RRC signaling).

[0136] (MCS Table Determination Method) According to Non-Patent Document 7, in NR, an MCS table (mcs-Table) to be used when the transmission waveform is CP-OFDM and an MCS table (mcs-TableTransformPrecoder) to be used when the transmission waveform is DFT-s-OFDM can be configured for a terminal. In other words, the terminal first determines the transmission waveform, and then determines the MCS table to be used for transmission to be the MCS table corresponding to the transmission waveform.

[0137] On the other hand, in the third modification of the fourth embodiment, an MCS table is required to determine the transmission waveform at the time of retransmission, so the MCS table must be determined before determining the transmission waveform. The following options may be applied to the method of determining the MCS table.

[0138] <First Transmission, Option 1> [Step 1] The terminal determines the transmission waveform based on the MCS index using the method of embodiment 4.

[0139] [Step 2] The terminal determines an MCS table based on the determined transmission waveform and the RRC parameters corresponding to that transmission waveform. The RRC parameters are, for example, mcs-Table if the transmission waveform is CP-OFDM, and mcs-TableTransformPrecoder if the transmission waveform is DFT-s-OFDM.

[0140] [Step 3] The terminal determines the modulation level Q based on the determined MCS table and MCS index. m and the target coding rate R.

[0141] This option may be applied not only to the third modification of the fourth embodiment but also to all of the fourth embodiment and the modifications of the fourth embodiment. <First transmission, Option 2>

[0142] [Step 1] Before determining the transmission waveform, the terminal determines the MCS table to use. For example, the terminal may determine the MCS table to use based on RRC parameters corresponding to CP-OFDM (e.g., mcs-Table). Alternatively, the terminal may determine the MCS table to use based on RRC parameters corresponding to DFT-s-OFDM (e.g., mcs-TableTransformPrecoder).

[0143] [Step 2] The terminal determines the transmission waveform based on the MCS index using the method of embodiment 4. It also determines the modulation level Q based on the determined MCS table and MCS index. m and the target coding rate R.

[0144] This option may be applied not only to the third modification of the fourth embodiment but also to all of the fourth embodiment and its modifications.

[0145] <Option 1 at retransmission> [Step 1] The terminal determines the MCS table to be the same as the MCS table used for the PUSCH that transmitted the same transport block immediately before.

[0146] [Step 2] The terminal determines the modulation scheme and transmission waveform based on the MCS index using the method of Variation 3 of Embodiment 4.

[0147] <When retransmitting, Option 2> [Step 1] The terminal determines the MCS table to use before determining the transmission waveform. For example, the terminal may determine the MCS table to use based on RRC parameters corresponding to CP-OFDM (e.g., mcs-Table). Alternatively, the terminal may determine the MCS table to use based on RRC parameters corresponding to DFT-s-OFDM (e.g., mcs-TableTransformPrecoder).

[0148] [Step 2] The terminal determines the modulation scheme and transmission waveform based on the MCS index using the method of Variation 3 of Embodiment 4.

[0149] (Embodiment 5) In embodiment 5, the terminal determines the transmission waveform of the PUSCH based on the resource allocation type notified to the terminal by the frequency domain resource assignment (FDRA) field included in the DCI.

[0150] Step 1 of the operation example of the fifth embodiment may be the same as that of the first embodiment.

[0151] Step 2 of the operation example of the fifth embodiment may be the same as that in the case where dynamic resource allocation type switching of the frequency domain resource assignment field determination method in another second embodiment described below is enabled.

[0152] [Step 3] The terminal determines the frequency resource allocation and transmit waveform for PUSCH transmission based on the information in the FDRA field of the DCI. Specifically, the terminal determines the transmit waveform based on the resource allocation type indicated in the FDRA field. Specifically, if resource allocation type 0 is indicated as the frequency domain resource allocation method, the terminal determines the transmit waveform to be CP-OFDM. On the other hand, if resource allocation type 1 is indicated as the frequency domain resource allocation method, the terminal determines the transmit waveform to be DFT-s-OFDM.

[0153] According to this embodiment, the transmission waveform of the PUSCH can be notified using the FDRA field, which is an existing DCI field, and therefore it is possible to notify the transmission waveform dynamically without increasing the number of DCI bits for switching the transmission waveform.

[0154] (Another embodiment 1) Dynamic transmission waveform switching may be applied to Message 3 or Message A, which is the first uplink data transmission at the time of initial access.

[0155] In this case, the terminal may transmit on a random access channel (PRACH: Physical Random Access Channel), and may transmit by switching the preamble of the PRACH depending on whether dynamic transmission waveform switching is supported or not.

[0156] Furthermore, the terminal may be notified of an RSRP or RSRQ threshold for switching the transmission waveform. For example, if the RSRP or RSRQ of the reference signal at the time of initial access is equal to or less than the threshold, the terminal may not select dynamic transmission waveform switching for PUSCH transmission of Message 3 or Message A, but may select dynamic transmission waveform switching if it is greater than the threshold. Alternatively, the terminal may select dynamic transmission waveform switching for PUSCH transmission of Message 3 or Message A if the RSRP or RSRQ at the time of initial access is equal to or less than the threshold, but may not select dynamic transmission waveform switching if it is greater than the threshold.

[0157] Alternatively, a new parameter msg3-transformPrecoderDynamic may be introduced in the System Information Block (SIB), and dynamic transmission waveform switching may be enabled based on msg3-transformPrecoderDynamic. Specifically, when msg3-transformPrecoderDynamic is set in the SIB, the terminal determines that the value of the existing RRC parameter msg3-transformPrecoder is invalid (i.e., discards the value of msg3-transformPrecoder), and enables dynamic transmission waveform switching. Alternatively, a new parameter value (msg3-transformPrecodeDynamic) may be introduced into msg3-transformPrecode of the SIB.

[0158] The terminal may determine whether dynamic transmit waveform switching is enabled or disabled based on information contained in DCI format 0-1 scrambled with a Temporary Cell-Radio Network Temporary identifier (TC-RNTI) or a Random Access Response (RAR) UL grant.

[0159] For waveform indication, DCI format 0-1 or RNR UL grant scrambled with TC-RNTI may be used as method 1, and further, the number of bits is not increased by using a reserved bit field.

[0160] Method 2 may be based on the number of transmission layers or the number of repetitions.

[0161] Method 3 may be based on the index of the TDRA table.

[0162] Method 4 may be based on the MCS index.

[0163] (Another embodiment 2) In the above-described embodiment, the following method may be used to determine the number of bits of other parameters included in DCI, such as Frequency domain resource assignment, Antenna ports, PTRS-DMRS association, and DMRS sequence initialization.

[0164] [Frequency domain resource assignment field]

[0165] <Method 1> When dynamic transmission waveform switching is enabled, the terminal determines the size (number of bits) of the DCI frequency domain resource assignment field using the following method.

[0166] When the terminal determines to use DFT-s-OFDM for PUSCH transmission according to the above-described embodiment, it applies resource allocation type 1 to the frequency domain resource allocation method. The resource allocation is announced by

[0167] On the other hand, when the terminal determines to use CP-OFDM for PUSCH transmission according to the above-described embodiment, it applies resource allocation type 0 to frequency domain resource allocation. RBG Resource allocation is signaled by the LSB.

[0168] (When resource allocation type 0 is set) The number of bits in the Frequency domain resource assignment field is bits, where N RB UL,BWP is the number of resource blocks included in the uplink BWP (Bandwidth Part) configured in the terminal, NRBG is the number of resource block groups (RBGs).

[0169] (When resource allocation type 1 is set) The number of bits in the Frequency domain resource assignment field is It is a bit.

[0170] (When dynamic resource allocation type switching is enabled) The number of bits in the Frequency domain resource assignment field is determined based on the larger bit of type 0 or type 1, so It is a bit.

[0171] When the terminal determines to use DFT-s-OFDM for PUSCH transmission according to the above-described embodiment, it applies resource allocation type 1 to the frequency domain resource allocation method. The resource allocation is announced by

[0172] On the other hand, when the terminal determines to use CP-OFDM for PUSCH transmission according to the above-described embodiment, the terminal determines whether to apply resource allocation type 0 or resource allocation type 1 based on the MSB of the Frequency domain resource assignment field.

[0173] If resource allocation type 0 is applied, N in the Frequency domain resource assignment field RBG The resource allocation is notified by the LSB. When resource allocation type 1 is applied, the Frequency domain resource assignment field The resource allocation is announced by

[0174] <Method 2> When dynamic transmit waveform switching is enabled, the terminal does not assume that resource allocation type 0 will be set. In other words, when dynamic transmit waveform switching is enabled, the terminal may always determine the resource allocation method to be resource allocation type 1.

[0175] Then, the number of bits in the Frequency domain resource assignment field is It is a bit.

[0176] [Antenna ports field]

[0177] (Case A1) When the RRC parameters are set to dmrs-Type=1 and maxLength=1, the number of bits in the Antenna ports field is 3 bits.

[0178] When it is determined to use DFT-s-OFDM for PUSCH transmission according to the above-described embodiment, the antenna port is notified by the 2 LSBs (or 2 MSBs) of the Antenna ports field. Furthermore, the terminal determines the antenna port based on the mapping table given in FIG. 10 and the information in the Antenna ports field.

[0179] On the other hand, when it is determined to use CP-OFDM for PUSCH transmission according to the above-described embodiments, the terminal determines antenna ports based on the mapping table given in FIG. 11, 12, 13, or 14 and the information in the Antenna ports field for each of the transmission layers being 1, 2, 3, or 4.

[0180] Note that the mapping of Values ​​0, 1, 2, and 3 to antenna ports in Fig. 10 is the same as the mapping of Values ​​2, 3, 4, and 5 to antenna ports in Fig. 11. Therefore, when a terminal determines that DFT-s-OFDM is to be used for PUSCH transmission, it may use the mapping table in Fig. 11 in the same way as for CP-OFDM, instead of using the mapping table in Fig. 10.

[0181] (Case A2) When the RRC parameters are set to dmrs-Type=1 and maxLength=2, the number of bits in the Antenna ports field is 4 bits.

[0182] When the terminal determines to use DFT-s-OFDM for PUSCH transmission according to the above-described embodiment, the terminal determines the antenna ports based on the mapping table given in FIG. 15 and the information in the Antenna ports field.

[0183] On the other hand, when the terminal determines to use CP-OFDM for PUSCH transmission according to the above-described embodiment, the terminal determines antenna ports based on the mapping table given in FIG. 16, 17, 18 or 19 and the information in the Antenna ports field for each of the cases where the number of transmission layers is 1, 2, 3 or 4.

[0184] Note that the mapping between Values ​​0 to 11 and antenna ports in Fig. 15 is the same as the mapping between Values ​​2 to 13 and antenna ports in Fig. 16. Therefore, when the terminal determines to use DFT-s-OFDM (or enables transform precoding) for PUSCH transmission, it may use the mapping table in Fig. 16 in the same way as CP-OFDM, instead of using the mapping table in Fig. 15.

[0185] In NR up to Rel. 17, PUSCH using DFT-s-OFDM as the transmit waveform does not support the RRC parameter being set to dmrs-Type=2. Therefore, when dynamic transmit waveform switching is enabled, the terminal may not assume that dmrs-Type=2 will be set. In other words, when dynamic transmit waveform switching is enabled, the DMRS type may always be determined to be dmrs-Type=1.

[0186] On the other hand, if dynamic transmit waveform switching is enabled, the terminal may assume that dmrs-Type=2 is set. In this case, the DMRS type may be dynamically switched based on the transmit waveform. Specifically, as follows:

[0187] (Case B1) When the RRC parameters are set to dmrs-Type=2 and maxLength=1, the number of bits in the Antenna ports field is 4 bits.

[0188] When it is determined to use DFT-s-OFDM for PUSCH transmission according to the above-described embodiment, the antenna port is notified by the 2 LSBs (or 2 MSBs) of the Antenna ports field. Furthermore, the terminal determines the antenna port based on the mapping table given in FIG. 10 and the information in the Antenna ports field.

[0189] When the terminal determines to use CP-OFDM for PUSCH transmission according to the above-described embodiment, the terminal determines antenna ports based on the mapping table given in Figure 20, 21, 22 or 23 and the information in the Antenna ports field for each of the cases where the number of transmission layers is 1, 2, 3 or 4.

[0190] Note that the mapping of Values ​​0, 1, 2, and 3 to antenna ports in Fig. 10 is the same as the mapping of Values ​​2, 3, 4, and 5 to antenna ports in Fig. 20. Therefore, when a terminal determines that DFT-s-OFDM is to be used for PUSCH transmission, the terminal may use the mapping table in Fig. 20 in the same manner as for CP-OFDM, instead of using the mapping table in Fig. 10.

[0191] (Case B2) When the RRC parameters are set to dmrs-Type=2 and maxLength=2, the number of bits in the Antenna ports field is 5 bits.

[0192] When it is determined to use DFT-s-OFDM for PUSCH transmission according to the above-described embodiment, the DMRS type is determined to be dmrs-Type=1, and the antenna port is notified by the 4 LSBs (or 4 MSBs) of the Antenna ports field. Furthermore, the terminal determines the antenna port based on the mapping table given in FIG. 15 and the information in the Antenna ports field.

[0193] On the other hand, when the terminal determines to use CP-OFDM for PUSCH transmission according to the above-described embodiment, the terminal determines antenna ports based on the mapping table given in Figure 24, 25, 26 or 27 and the information in the Antenna ports field for each of the cases where the number of transmission layers is 1, 2, 3 or 4.

[0194] [PTRS-DMRS association field] As in step 2 of the above-described embodiment, when dynamic transmission waveform switching is enabled, the terminal may set the size (number of bits) of the PTRS-DMRS association field of the DCI to the same number of bits as when the CP-OFDM transmission waveform is set quasi-statically.

[0195] Specifically, if the RRC parameter PTRS-UplinkConfig is not set or if maxRank=1 is set, the number of bits in the PTRS-DMRS association field is 0. In other cases, the number of bits in the PTRS-DMRS association field is 2.

[0196] Here, the value of the PTRS-DMRS association field is valid only when the terminal determines to use CP-OFDM for PUSCH transmission according to the above-described embodiment. That is, when the terminal determines to use DFT-s-OFDM for PUSCH transmission according to the above-described embodiment, the terminal does not need to consider the value of the PTRS-DMRS association field.

[0197] [DMRS sequence initialization field] As in step 2 of the above-described embodiment, when dynamic transmission waveform switching is enabled, the terminal may set the size (number of bits) of the DMRS sequence initialization field of the DCI to the same number of bits as when the CP-OFDM transmission waveform is set quasi-statically.

[0198] Specifically, when dynamic transmission waveform switching is enabled, the number of bits in the PTRS-DMRS association field is 1 bit.

[0199] (Other Embodiment 3) In the above-described embodiment, when dynamic transmit waveform switching is enabled, the DCI field size is determined based on the CP-OFDM field size. However, the total DCI size (i.e., the number of DCI bits) may be determined based on CP-OFDM. In this case, the size of each DCI field may be determined based on the transmit waveform determined by dynamic transmit waveform switching. Furthermore, if the total number of bits of all DCI fields is smaller than the DCI size, zero insertion (zero padding) may be applied.

[0200] Furthermore, the DCI field whose field size is determined based on CP-OFDM when dynamic transmit waveform switching is enabled may be part of the following DCI fields (e.g., Frequency domain resource assignment): Frequency domain resource assignment Precoding information and number of layers Antenna ports PTRS-DMRS association DMRS sequence initialization

[0201] Except for DCI fields whose field sizes are determined based on CP-OFDM, the size of each DCI field may be determined based on the transmission waveform determined by dynamic transmission waveform switching.

[0202] (Modification) In the above-described embodiment, the DCI format is not limited to DCI format 0-1 or DCI format 0-2, and may be applied to other DCI formats.

[0203] For example, the above-described embodiment may be applied to a DCI format other than that used for initial access, that is, a DCI format used after dedicated RRC parameters are set. Also, the present embodiment may be applied to a DCI format that can notify a transmission rank higher than Rank 1. Also, the present embodiment may be applied to a DCI format set in a terminal-specific RRC.

[0204] The above-described embodiment is not limited to DG-PUSCH, and may be applied to PUSCH (Type-2 CG-PUSCH) that transmits PUSCH with semi-static resource allocation by Activation DCI. In this case, the above-described transmission waveform may be notified based on a field included in Activation DCI.

[0205] In the above-described embodiment, the DFT-s-OFDM transmission waveform supports only transmission with one layer, and the CP-OFDM transmission waveform supports transmission with two or more layers, but the relationship between the transmission waveform and the number of layers is not limited to the above. For example, the DFT-s-OFDM transmission waveform may support two or more layers. In that case, the number of layers for switching the transmission waveform may be changed from 1 to N, so that the DFT-s-OFDM transmission waveform supports transmission with N or fewer layers, and the CP-OFDM transmission waveform supports transmission with N+1 or more layers.

[0206] (Flowchart) FIG. 28 is a flowchart of the present invention.

[0207] In the first embodiment, in step 3, the terminal determines the transmission waveform based only on the transmission layer.

[0208] In the second embodiment, in step 3, the terminal determines the transmission waveform based on the transmission layer and the TPMI.

[0209] In the third embodiment, in step 3, the terminal determines the transmission waveform based on the TDRA.

[0210] In the fourth embodiment, in step 3, the terminal determines the transmission waveform based on the MCS index.

[0211] FIG. 36 is a block diagram showing a configuration example of a portion of a base station 100 according to an embodiment of the present disclosure, and FIG. 37 is a block diagram showing a configuration example of a portion of a terminal 200 according to an embodiment of the present disclosure.

[0212] In the base station 100 shown in Fig. 36, when dynamic switching between a first transmission waveform (e.g., DFT-s-OFDM) of an uplink signal (e.g., PUSCH) and a second transmission waveform (e.g., CP-OFDM) having a data size larger than that of the first transmission waveform is configured, a control unit (e.g., corresponding to a control circuit) determines a field size of control information (e.g., DCI) based on the field size when the second transmission waveform is configured. A transmission unit (e.g., corresponding to a transmission circuit) transmits the control information based on the determined field size.

[0213] In terminal 200 shown in Fig. 37, when dynamic switching between a first transmission waveform (e.g., DFT-s-OFDM) of an uplink signal (e.g., PUSCH) and a second transmission waveform (e.g., CP-OFDM) having a data size larger than that of the first transmission waveform is configured, a control unit (e.g., corresponding to a control circuit) determines a field size of control information (e.g., DCI) based on the field size when the second transmission waveform is configured. A receiving unit (e.g., corresponding to a receiving circuit) receives the control information based on the determined field size.

[0214] (Configuration of Base Station) FIG. 29 is a block diagram showing the configuration of a base station 100 according to an embodiment of the present invention.

[0215] At least one of the control unit 101, higher control signal generation unit 102, downlink control information generation unit 103, coding unit 104, modulation unit 105, signal allocation unit 106, extraction unit 109, demodulation unit 110, and decoding unit 111 shown in Fig. 29 may be included in the control unit shown in Fig. 36. Furthermore, the transmission unit 107 shown in Fig. 29 may be included in the transmission unit shown in Fig. 36.

[0216] The control unit 101 determines information related to PUSCH transmission for the terminal 200, and outputs the determined information to the higher control signal generation unit or the downlink control information generation unit 103. The information related to PUSCH transmission may include, for example, the above-described information related to the transmission waveform, information related to precoding information and the number of layers, information related to time domain resource allocation (TDRA), and information related to the MCS. The control unit 101 also outputs the determined information to the extraction unit 109, the demodulation unit 110, and the decoding unit 111.

[0217] The control unit 101 determines the coding and modulation scheme and radio resource allocation for the downlink signal for transmitting the higher control signal and the downlink control information, and outputs the determined information to the coding unit 104, the modulation unit 105, and the signal allocation unit 106. The control unit 101 also outputs the coding and modulation scheme for the data signal and the higher control signal and the radio resource allocation information to the downlink control information generation unit 103.

[0218] The upper control signal generating section 102 uses the control information input from the control section 101 to generate an upper layer control signal bit string and outputs it to the encoding section 104 .

[0219] The downlink control information generating section 103 generates a DCI bit string using the control information input from the control section 101, and outputs the generated DCI bit string to the encoding section 104. Note that the control information may be transmitted to multiple terminals.

[0220] The encoding unit 104 encodes the bit string obtained from the higher control signal generating unit 102 or the DCI bit string input from the downlink control information generating unit 103, and outputs the encoded bit string to the modulation unit 105.

[0221] The modulation unit 105 modulates the coded bit string received from the coding unit 104 and outputs the modulated bit string to the signal allocation unit 106 .

[0222] The signal allocation unit 106 maps the downlink data signal or control signal input as a symbol sequence from the modulation unit to the radio resources instructed by the control unit 101. The signal allocation unit 106 also inputs the mapped signal to the transmission unit 107.

[0223] The transmitter 107 generates a transmission waveform such as OFDM for the signal output from the signal allocation unit 106. In the case of OFDM transmission using a CP, a CP is added after applying an Inverse Fast Fourier Transform (IFFT).

[0224] The transmitting section 107 performs radio frequency (RF) processing such as digital to analog (D / A) conversion and up-conversion, and transmits the radio signal to the terminal 200 via an antenna.

[0225] The receiving unit 108 performs RF processing such as down-conversion or analog-to-digital (A / D) conversion on uplink transmission signals transmitted from the terminal 200 and received via an antenna. In addition, in the case of OFDM transmission, the receiving unit 108 applies FFT to the received signals to obtain frequency domain signals and outputs the frequency domain signals to the extracting unit 109.

[0226] Based on the information received from the control unit 101 , the extraction unit 109 extracts the radio resource portion on which the PUSCH was transmitted from the received signal and outputs it to the demodulation unit 110 .

[0227] Demodulation section 110 demodulates the PUSCH based on the information received from control section 101 and outputs the demodulation result to decoding section 111 .

[0228] The decoding section 111 performs error correction decoding on the PUSCH using the information received from the control section 101 and the demodulation result obtained from the demodulation section, and obtains a decoded received bit string.

[0229] (Configuration of Terminal) FIG. 30 is a block diagram showing the configuration of terminal 200 according to an embodiment of the present invention.

[0230] At least one of extraction section 202, demodulation section 203, decoding section 204, control section 205, coding section 206, modulation section 207, and signal allocation section 208 shown in Fig. 30 may be included in the control section shown in Fig. 37. Also, reception section 201 shown in Fig. 30 may be included in the reception section shown in Fig. 37.

[0231] The receiver 201 receives a data signal or a downlink control signal transmitted from the base station 100 via an antenna, and performs RF processing such as down-conversion or A / D conversion on the radio received signal to obtain a baseband signal. When receiving an OFDM signal, the receiver 201 also performs FFT processing on the received signal to convert it into the frequency domain.

[0232] The extraction unit 202 extracts a radio resource portion including a downlink control signal from the received signal received from the receiving unit 201, using information related to the radio resource of the control signal input from the control unit 205, and outputs the extracted radio resource portion to the demodulation unit 203. Furthermore, the extraction unit 202 extracts a radio resource portion including a data signal, using information related to the radio resource of the data signal input from the control unit 205, and outputs the extracted radio resource portion to the demodulation unit 203.

[0233] The demodulation section 203 demodulates the PDCCH or PDSCH based on the information received from the control section 205 and outputs the demodulation result to the decoding section 204 .

[0234] The decoding unit 204 performs error correction decoding of the PDCCH or PDSCH using the information received from the control unit 205 and the demodulation result obtained from the demodulation unit 203, and obtains upper layer control information or downlink control information. The decoding unit 204 outputs the obtained upper layer control information and downlink control information to the control unit 205. The decoding unit 204 may also generate an acknowledgement (ACK) / negative ACK (NACK) signal from the PDSCH decoding result.

[0235] The control unit 205 specifies the transmission waveform for PUSCH transmission and the like from information related to PUSCH transmission obtained from the higher layer control signal and downlink control information by the above-described method, and controls the coding unit 206, the modulation unit 207, and the signal allocation unit 208. Furthermore, the control unit 205 outputs the determined information to the extraction unit 202, the demodulation unit 203, and the decoding unit 204.

[0236] The encoding unit 206 encodes the uplink data signal or the uplink control signal based on the information input from the control unit 205 and outputs the encoded bit string to the modulation unit 207 .

[0237] The modulation unit 207 modulates the coded bit sequence received from the coding unit 206 based on the information input from the control unit 205 to generate a modulated symbol sequence, and outputs it to the signal allocation unit 208 .

[0238] Signal allocation section 208 maps the signal input from modulation section 207 to the radio resource instructed by control section 205. Furthermore, signal allocation section 208 outputs the mapped signal to transmission section 209.

[0239] The transmitter 209 generates a transmission waveform such as OFDM for the signal input from the signal allocation unit 208. In the case of OFDM transmission using a CP or DFT-s-OFDM transmission, a CP is added after IFFT. When generating a DFT-s-OFDM transmission waveform, a DFT unit may be added after the modulation unit or before the signal allocation unit. The transmitter 209 also performs RF processing such as D / A conversion and up-conversion on the transmission signal. The transmitter 209 also transmits a radio signal to the base station 100 via an antenna.

[0240] In the above-described embodiments, PUSCH transmission has been described as uplink transmission, but the channel used for uplink transmission is not limited to PUSCH and may be another channel. Furthermore, the type of information to be transmitted is not limited to data and may be another type of information (e.g., an uplink control signal). Furthermore, an embodiment of the present disclosure is not limited to uplink transmission and may be applied to downlink transmission or sidelink transmission.

[0241] Furthermore, in each of the above-described embodiments, the transmission waveform is not limited to CP-OFDM and DFT-s-OFDM, and may be a waveform for multicarrier transmission or another transmission waveform for single carrier transmission.

[0242] Furthermore, the parameters exemplified in the present disclosure, such as the number of transmission layers, the transmission precoding matrix (TPMI), the number of slots, the number of symbols, the symbol position, the value of K2, and the number of repetitions, are merely examples, and other values ​​may be used. Furthermore, the tables exemplified in the present disclosure and shown in Figures 2 to 27 are merely examples, and the values ​​associated in the tables may be other values, and the types of parameters associated in the tables are not limited to these.

[0243] The present disclosure may be applied to communication between terminals, such as sidelink communication, for example.

[0244] Furthermore, in the present disclosure, the downlink control channel, downlink data channel, uplink control channel, and uplink data channel are not limited to PDCCH, PDSCH, PUCCH, and PUSCH, respectively, and may be control channels and data channels with other names.

[0245] Furthermore, in the present disclosure, RRC signaling is assumed as higher layer signaling, but it may be replaced with Medium Access Control (MAC) signaling and notification by DCI, which is physical layer signaling.

[0246] (Supplementary Note) Information indicating whether the terminal 200 supports the functions, operations, or processes described in each of the above-described embodiments and each supplementary note may be transmitted (or notified) from the terminal 200 to the base station 100, for example, as capability information or capability parameters of the terminal 200.

[0247] The capability information may include an information element (IE) that individually indicates whether or not the terminal 200 supports at least one of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements. Alternatively, the capability information may include an information element that indicates whether or not the terminal 200 supports a combination of any two or more of the functions, operations, or processes described in the above-described embodiments, modifications, and supplements.

[0248] For example, the base station 100 may determine (or decide or assume) the functions, operations, or processes that the terminal 200 that transmitted the capability information supports (or does not support) based on the capability information received from the terminal 200. The base station 100 may perform operations, processes, or controls according to the determination result based on the capability information. For example, the base station 100 may control uplink-related processing based on the capability information received from the terminal 200.

[0249] Note that the fact that terminal 200 does not support some of the functions, operations, or processes described in the above-described embodiments, modifications, and supplementary notes may be interpreted as meaning that such some of the functions, operations, or processes are restricted in terminal 200. For example, information or a request regarding such restrictions may be notified to base station 100.

[0250] Information regarding the capabilities or limitations of terminal 200 may, for example, be defined in a standard, or may be implicitly notified to base station 100 in association with information known at base station 100 or information transmitted to base station 100.

[0251] The above has described the embodiments, modifications, and supplementary notes according to a non-limiting example of the present disclosure.

[0252] (Control Signal) In the present disclosure, a downlink control signal (information) related to the present disclosure may be a signal (information) transmitted by a PDCCH of a physical layer, or may be a signal (information) transmitted by a MAC CE (Control Element) or RRC of a higher layer. Also, the downlink control signal may be a signal (information) that is specified in advance.

[0253] The uplink control signal (information) related to the present disclosure may be a signal (information) transmitted on a PUCCH in the physical layer, or a signal (information) transmitted on a MAC CE or RRC in a higher layer. The uplink control signal may also be a predefined signal (information). The uplink control signal may also be replaced with uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.

[0254] (Base Station) In the present disclosure, a base station may be a TRP (Transmission Reception Point), a cluster head, an access point, an RRH (Remote Radio Head), an eNodeB (eNB), a gNodeB (gNB), a BS (Base Station), a BTS (Base Transceiver Station), a parent device, a gateway, or the like. In sidelink communication, the base station may be replaced with a terminal. The base station may be a relay device that relays communication between an upper node and a terminal. The base station may be a roadside unit.

[0255] (Uplink / Downlink / Sidelink) The present disclosure may be applied to any of the uplink, downlink, and sidelink. For example, the present disclosure may be applied to the uplink PUSCH, PUCCH, and PRACH, the downlink PDSCH, PDCCH, and PBCH, and the sidelink PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), and PSBCH (Physical Sidelink Broadcast Channel).

[0256] The PDCCH, PDSCH, PUSCH, and PUCCH are examples of a downlink control channel, a downlink data channel, an uplink data channel, and an uplink control channel. The PSCCH and PSSCH are examples of a sidelink control channel and a sidelink data channel. The PBCH and PSBCH are examples of broadcast channels, and the PRACH is an example of a random access channel.

[0257] (Data Channel / Control Channel) The present disclosure may be applied to either a data channel or a control channel. For example, the channels of the present disclosure may be replaced with data channels such as PDSCH, PUSCH, and PSSCH, and control channels such as PDCCH, PUCCH, PBCH, PSCCH, and PSBCH.

[0258] (Reference Signal) In the present disclosure, a reference signal is a signal known by both a base station and a terminal, and may also be referred to as an RS (Reference Signal) or a pilot signal. The reference signal may be any of DMRS, CSI-RS (Channel State Information - Reference Signal), TRS (Tracking Reference Signal), PTRS (Phase Tracking Reference Signal), CRS (Cell-specific Reference Signal), and SRS (Sounding Reference Signal).

[0259] (Time Interval) In the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may be, for example, a time resource unit such as a frame, a superframe, a subframe, a slot, a time slot, a subslot, a minislot, a symbol, an OFDM (Orthogonal Frequency Division Multiplexing) symbol, or an SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbol, or another time resource unit. Furthermore, the number of symbols included in one slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be another number of symbols.

[0260] (Frequency Band) The present disclosure may be applied to either a licensed band or an unlicensed band.

[0261] (Communication) The present disclosure may be applied to communication between a base station and a terminal (Uu link communication), communication between terminals (Sidelink communication), and V2X (Vehicle to Everything) communication. For example, the channels of the present disclosure may be replaced with PSCCH, PSSCH, PSFCH (Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, or PBCH.

[0262] The present disclosure may be applied to a terrestrial network, a non-terrestrial network (NTN) using satellites or highly advanced pseudo satellites (HAPS), or a terrestrial network in which the transmission delay is large compared to the symbol length or slot length, such as a network with a large cell size or an ultra-wideband transmission network.

[0263] (Antenna Port) An antenna port refers to a logical antenna (antenna group) consisting of one or more physical antennas. In other words, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna consisting of multiple antennas. For example, the number of physical antennas an antenna port consists of is not specified, but it is specified as the smallest unit by which a terminal can transmit a reference signal. An antenna port may also be specified as the smallest unit by which a weighting of a precoding vector is multiplied.

[0264] 5G NR System Architecture and Protocol Stack 3GPP continues work on the next release of fifth-generation cellular technology (also referred to simply as "5G"), which includes the development of new radio access technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, allowing for the prototyping and commercial deployment of 5G NR-compliant devices (e.g., smartphones).

[0265] For example, the system architecture generally assumes a Next Generation - Radio Access Network (NG-RAN) comprising gNBs. The gNBs provide UE-side termination of NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols. The gNBs are connected to each other via an Xn interface. The gNBs are also connected to a Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to an Access and Mobility Management Function (AMF) (e.g., a specific core entity performing AMF) via an NG-C interface, and to a User Plane Function (UPF) (e.g., a specific core entity performing UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 31 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0266] The NR user plane protocol stack (see, for example, 3GPP TS 38.300, section 4.4.1) includes a Packet Data Convergence Protocol (PDCP) sublayer (see Section 6.4 of TS 38.300), a Radio Link Control (RLC) sublayer (see Section 6.3 of TS 38.300), and a Medium Access Control (MAC) sublayer (see Section 6.2 of TS 38.300), which are terminated on the network side in the gNB. A new Access Stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) has also been introduced above PDCP (see, for example, Section 6.5 of 3GPP TS 38.300). A control plane protocol stack has also been defined for the NR (see, for example, Section 4.4.2 of TS 38.300). An overview of Layer 2 functions is provided in Section 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are listed in clauses 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in clause 7 of TS 38.300.

[0267] For example, the Medium-Access-Control layer handles logical channel multiplexing and scheduling and scheduling-related functions, including handling various numerologies.

[0268] For example, the physical layer (PHY) is responsible for coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. The physical layer also handles mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmitting a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels include the Physical Random Access Channel (PRACH), the Physical Uplink Shared Channel (PUSCH), and the Physical Uplink Control Channel (PUCCH) as uplink physical channels, and the Physical Downlink Shared Channel (PDSCH), the Physical Downlink Control Channel (PDCCH), and the Physical Broadcast Channel (PBCH) as downlink physical channels.

[0269] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communication (mMTC), which have diverse requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps in the downlink and 10 Gbps in the uplink) and effective (user-experienced) data rates approximately three times those offered by IMT-Advanced. On the other hand, URLLC imposes stricter requirements for ultra-low latency (0.5 ms for user plane latency in both UL and DL) and high reliability (1-10-5 within 1 ms). Finally, mMTC may require preferably high connection density (1,000,000 devices / km2 in urban environments), wide coverage in adverse environments, and extremely long battery life (15 years) for low-cost devices.

[0270] Therefore, OFDM numerology (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) suitable for one use case may not be valid for another use case. For example, low-latency services may preferably require a shorter symbol length (and therefore a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also referred to as TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with short delay spreads. The subcarrier spacing may be optimized accordingly to maintain similar CP overhead. NR may support one or more subcarrier spacing values. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, etc. are currently considered. The symbol length Tu and subcarrier spacing Δf are directly related by the formula Δf = 1 / Tu. Similar to LTE systems, the term "resource element" can be used to mean the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

[0271] In the new radio system 5G-NR, for each numerology and each carrier, a resource grid of subcarriers and OFDM symbols is defined for each uplink and downlink. Each element of the resource grid is called a resource element and is specified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).

[0272] <Functional Separation Between NG-RAN and 5GC in 5G NR> Figure 32 shows the functional separation between NG-RAN and 5GC. The logical node of NG-RAN is gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF.

[0273] For example, gNB and ng-eNB host the following main functions: - Radio Resource Management functions such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink; - IP header compression, ciphering and integrity protection of data; - AMF selection at UE attach time if routing to the AMF cannot be determined from the information provided by the UE; - Routing of user plane data towards the UPF; - Routing of control plane information towards the AMF; - Connection setup and release; - Scheduling and transmission of paging messages; - Scheduling and transmission of system broadcast information (sourced from the AMF or Operation, Admission, Maintenance (OAM)); - Configuration of measurements and measurement reports for mobility and scheduling; - Transport level packet marking in the uplink; - Session management; Support for network slicing; - QoS flow management and mapping to data radio bearers; - Support for UEs in RRC_INACTIVE state; - NAS message delivery function; - Radio access network sharing; - Dual connectivity; - Close coordination between NR and E-UTRA.

[0274] The Access and Mobility Management Function (AMF) hosts the following main functions: - Termination of Non-Access Stratum (NAS) signaling; - Security of NAS signaling; - Security control of Access Stratum (AS); - Signaling between Core Network (CN) nodes for mobility between 3GPP access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Registration area management; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization including checking of roaming rights; - Mobility management control (subscription and policy); - Support for network slicing; - Selection of Session Management Function (SMF).

[0275] Furthermore, the User Plane Function (UPF) hosts the following main functions: - anchor point for intra-RAT / inter-RAT mobility (if applicable); - external PDU (Protocol Data Unit) session point for interconnection with data networks; - packet routing and forwarding; - packet inspection and policy rule enforcement for the user plane part; - traffic usage reporting; - uplink classifier to support routing of traffic flows to the data network; - branching point to support multi-homed PDU sessions; - QoS processing for the user plane (e.g. packet filtering, gating, UL / DL rate enforcement); - uplink traffic validation (mapping of SDF to QoS flows); - downlink packet buffering and triggering of downlink data notifications.

[0276] Finally, the Session Management Function (SMF) hosts the following main functions: session management; allocation and management of IP addresses for UEs; selection and control of UPF; configuration of traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination; policy enforcement and QoS of the control part; downlink data notification.

[0277] <RRC connection setup and reconfiguration procedure> Figure 33 shows some of the interactions between the UE, gNB, and AMF (5GC entities) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS part (see TS 38.300 v15.6.0).

[0278] RRC is a higher layer signaling (protocol) used to configure the UE and gNB. With this transition, the AMF prepares UE context data (including, for example, PDU session context, security keys, UE radio capabilities, UE security capabilities, etc.) and sends it to the gNB along with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding with a SecurityModeComplete message to the gNB. The gNB then sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the steps related to RRCReconfiguration are omitted because SRB2 and DRB are not set up. Finally, the gNB notifies the AMF that the setup procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0279] Accordingly, the present disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) that includes: a control circuit that, upon operation, establishes a Next Generation (NG) connection with a gNodeB; and a transmitter that, upon operation, transmits an initial context setup message to the gNodeB via the NG connection so that a signaling radio bearer between the gNodeB and a user equipment (UE) is set up. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, including a resource allocation configuration information element (IE), to the UE via the signaling radio bearer. The UE then transmits in uplink or receives in downlink based on the resource allocation configuration.

[0280] <IMT Usage Scenarios Beyond 2020> Figure 34 shows some use cases for 5G NR. The 3rd Generation Partnership Project New Radio (3GPP NR) is considering three use cases envisioned by IMT-2020 to support a wide variety of services and applications. The first phase of specifications for enhanced mobile broadband (eMBB) has been completed. Current and future work includes standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC), in addition to expanding support for eMBB. Figure 34 shows some examples of envisioned usage scenarios for IMT beyond 2020 (see, for example, ITU-R M.2083 Figure 2).

[0281] The URLLC use case has stringent performance requirements for throughput, latency, and availability. It is envisioned as one of the enabling technologies for future applications such as wireless control of industrial production or manufacturing processes, remote medical surgery, automated power transmission and distribution in smart grids, and road safety. URLLC's ultra-high reliability is supported by identifying technologies that meet the requirements set by TR 38.913. Key requirements for NR URLLC in Release 15 include a target user plane latency of 0.5 ms on the uplink (UL) and 0.5 ms on the downlink (DL). The overall URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane latency of 1 ms.

[0282] From a physical layer perspective, reliability can be improved in many possible ways. Current room for reliability improvement includes defining a separate CQI table for URLLC, more compact DCI formats, PDCCH repetition, etc. However, this room can be expanded to achieve ultra-high reliability as NR (with respect to the key requirements of NR URLLC) becomes more stable and developed. Specific use cases for NR URLLC in Release 15 include Augmented Reality / Virtual Reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0283] Additionally, the technology enhancements targeted by NR URLLC aim to improve latency and reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition in the data channel, and preemption in the downlink. Preemption means that a transmission with already allocated resources is stopped and the already allocated resources are used for another transmission with a later requested lower latency / higher priority. Therefore, a previously allowed transmission is preempted by a later transmission. Preemption is applicable regardless of the specific service type. For example, a transmission of service type A (URLLC) may be preempted by a transmission of service type B (eMBB, etc.). Technology enhancements for reliability improvement include a dedicated CQI / MCS table for a target BLER of 1E-5.

[0284] The use case of mMTC (massive machine type communication) is characterized by a very large number of connected devices that typically transmit relatively small amounts of data that are not sensitive to delays. These devices are required to be low-cost and have very long battery life. From the NR perspective, utilizing very narrow bandwidth portions is one solution that saves power and extends battery life from the UE's perspective.

[0285] As mentioned above, the scope of reliability improvement in NR is expected to be broader. One of the key requirements for all cases, for example, URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can improve reliability from a radio perspective and a network perspective. Generally, there are two to three key areas that can help improve reliability. These areas include compact control channel information, repetition of data channels / control channels, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability improvement regardless of the specific communication scenario.

[0286] For NR URLLC, further use cases with more stringent requirements are envisaged, such as factory automation, transportation, and power distribution, such as high reliability (up to 10-6 level), high availability, packet size up to 256 bytes, time synchronization down to a few μs (depending on the use case, the value can be 1 μs or a few μs depending on the frequency range and low latency in the order of 0.5 ms to 1 ms (e.g., 0.5 ms latency on the targeted user plane)).

[0287] Furthermore, for NR URLLC, there may be several technical enhancements from the physical layer perspective. These technical enhancements include PDCCH (Physical Downlink Control Channel) enhancements for compact DCI, PDCCH repetition, and increased PDCCH monitoring. Also, UCI (Uplink Control Information) enhancements relate to enhanced Hybrid Automatic Repeat Request (HARQ) and CSI feedback enhancements. There may also be PUSCH enhancements related to minislot-level hopping and retransmission / repetition enhancements. The term "minislot" refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot comprises 14 symbols).

[0288] <QoS Control> The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (Guaranteed Bit Rate QoS flows (GBR)) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Thus, at the NAS level, a QoS flow is the finest granularity of QoS classification in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over the NG-U interface.

[0289] For each UE, 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) for each PDU session, e.g., as shown above with reference to Figure 33. Additional DRBs for the QoS flows of that PDU session can be configured later (when this is up to the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0290] Figure 35 shows the non-roaming reference architecture for 5G NR (see TS 23.501 v16.1.0, section 4.23). An Application Function (AF) (e.g., an external application server hosting 5G services, as illustrated in Figure 34) interacts with the 3GPP core network to provide services. For example, it may access a Network Exposure Function (NEF) to support applications that affect traffic routing, or interact with a policy framework for policy control (e.g., QoS control) (see Policy Control Function (PCF)). Based on operator deployment, Application Functions considered trusted by the operator can interact directly with associated Network Functions. Application Functions not permitted by the operator to directly access Network Functions interact with associated Network Functions using an external exposure framework via the NEF.

[0291] Figure 35 further illustrates further functional units of the 5G architecture, namely, Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN, e.g., operator-provided services, Internet access, or third-party services). All or part of the core network functions and application services may be deployed and run in a cloud computing environment.

[0292] Therefore, the present disclosure provides an application server (e.g., an AF in a 5G architecture) comprising: a transmitter that, in operation, sends a request including QoS requirements for at least one of a URLLC service, an eMMB service, and an mMTC service to at least one of 5GC functions (e.g., an NEF, an AMF, an SMF, a PCF, an UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements; and a control circuit that, in operation, performs a service using the established PDU session.

[0293] The term "portion" used in this disclosure may be interchangeably used with other terms such as "circuitry," "device," "unit," or "module."

[0294] The present disclosure can be realized by software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may also be called an IC, system LSI, super LSI, or ultra LSI.

[0295] The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.

[0296] Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology may be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0297] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both functions. The radio transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0298] The communication devices are not limited to portable or mobile devices, but also include any kind of non-portable or fixed equipment, devices, and systems, such as smart home devices (such as home appliances, lighting equipment, smart meters or measuring devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0299] Communications include data communications via cellular systems, wireless LAN systems, communication satellite systems, and the like, as well as data communications via combinations of these.

[0300] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0301] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0302] (1) In one embodiment of the present disclosure, when dynamic switching between a first transmission waveform of an uplink signal and a second transmission waveform having a larger data size than the first transmission waveform is configured, the terminal determines the field size of the control information based on the field size when the second transmission waveform is configured.

[0303] (2) In one embodiment of the present disclosure, the terminal of (1) determines the transmission waveform of the uplink signal based on a value notified by a field included in the control information.

[0304] (3) In one embodiment of the present disclosure, the terminal of (2) determines the transmission waveform of the uplink signal based on the number of transmission layers indicated by the Precoding information and number of layers field or the SRI field included in the control information.

[0305] (4) In one embodiment of the present disclosure, the terminal of (2) determines the transmission waveform of the uplink signal based on the number of transmission layers and the transmission precoding matrix notified by the Precoding information and number of layers field or the SRI field included in the control information.

[0306] (5) In one embodiment of the present disclosure, the terminal of (2) determines the transmission waveform of the uplink signal based on an index notified by a Time Domain Resource Assignment (TDRA) field or a Frequency Domain Resource Assignment (FDRA) field included in the control information.

[0307] (6) In one embodiment of the present disclosure, the terminal of (2) determines the transmission waveform of the uplink signal based on an index notified by a Modulation and coding scheme (MCS) field included in the control information.

[0308] (7) In one embodiment of the present disclosure, when the index in (6) is an index for which the modulation level and the target coding rate are determined, the transmission waveform of the uplink signal is determined based on the correspondence between the index and the transmission waveform of the uplink signal. When the index is an index for which only the modulation level is determined, the transmission waveform of the uplink signal is determined based on the correspondence between the index and the transmission waveform of the uplink signal.

[0309] (8) In one embodiment of the present disclosure, the terminal of (3) determines the transmission waveform of the uplink signal to be a waveform for single-carrier transmission when the number of transmission layers is 1, and determines the transmission waveform of the uplink signal to be a waveform for multi-carrier transmission when the number of transmission layers is 2 or more.

[0310] (9) In one embodiment of the present disclosure, the terminal of (4) determines the transmission waveform of the uplink signal based on a value indicating the transmission precoding matrix when the number of transmission layers is 1, and determines the transmission waveform of the uplink signal to be a multicarrier transmission waveform when the number of transmission layers is 2 or more.

[0311] (10) In one embodiment of the present disclosure, in the terminal of (9), the association between the value indicating the transmission precoding matrix and the transmission waveform of the uplink signal is set by higher layer signaling.

[0312] (11) In one embodiment of the present disclosure, the terminal of (5) determines, based on the index, time domain allocation resource candidates associated with the index.

[0313] (12) In one embodiment of the present disclosure, in the terminal of (11), the association between the index value and the transmission waveform of the uplink signal is set by higher layer signaling.

[0314] (13) In one embodiment of the present disclosure, the terminal of (6) is configured such that the correspondence between the value of the index and the transmission waveform of the uplink signal is set by higher layer signaling.

[0315] (14) In one embodiment of the present disclosure, the terminal of (13) receives information regarding a threshold value of the index for switching the transmission waveform of the uplink signal.

[0316] (15) In one embodiment of the present disclosure, when dynamic switching between a first transmission waveform of an uplink signal and a second transmission waveform having a larger data size than the first transmission waveform is configured, a base station determines a field size of control information based on the field size when the second transmission waveform is configured.

[0317] (16) In a communication method according to one embodiment of the present disclosure, when a terminal is configured to dynamically switch between a first transmission waveform of an uplink signal and a second transmission waveform having a larger data size than the first transmission waveform, the terminal determines a field size of control information based on the field size when the second transmission waveform is configured, and receives the control information based on the field size.

[0318] (17) In a communication method according to one embodiment of the present disclosure, when a base station is configured to dynamically switch between a first transmission waveform of an uplink signal and a second transmission waveform having a larger data size than the first transmission waveform, the base station determines a field size of control information based on a field size when the second transmission waveform is configured, and transmits the control information based on the field size.

[0319] The disclosures of the specifications, drawings and abstracts contained in Japanese patent applications No. 2022-095920 filed on June 14, 2022 and No. 2022-158782 filed on September 30, 2022 are incorporated herein by reference in their entirety.

[0320] One embodiment of the present disclosure is useful in wireless communication systems.

[0321] 100 Base station 101, 205 Control unit 102 Upper control signal generation unit 103 Downlink control information generation unit 104, 206 Encoding unit 105, 207 Modulation unit 106, 208 Signal allocation unit 107, 209 Transmission unit 108, 201 Reception unit 109, 202 Extraction unit 110, 203 Demodulation unit 111, 204 Decoding unit 200 Terminal

Claims

1. A receiver for receiving downlink control information including a first upper layer signal instructing dynamic transmission waveform switching and a first control signal instructing whether an uplink signal is to be transmitted using a first transmission waveform or a second transmission waveform; a transmitter that transmits the uplink signal in a signal waveform determined based on the first higher layer signal and the first control signal; A terminal comprising:

2. The first transmission waveform is a signal generated using a transformPrecoder, The second transmission waveform is a signal generated without using the transformPrecoder. The terminal according to claim 1.

3. When the first upper layer signal instructs dynamic switching of a transmission waveform, if a size of a field included in the downlink control information differs between the first transmission waveform and the second transmission waveform, the size of the field in the second transmission waveform is set to be the size of the field. The terminal according to claim 2.

4. The one field is a field related to Precoding information and number of layers, Antenna ports, or PTRS-DMRS association. The terminal according to claim 3.

5. When the first upper layer signal does not instruct dynamic transmission waveform switching, the signal waveform is determined based on a second upper layer signal that instructs whether the uplink signal is to be transmitted using the first transmission waveform or the second transmission waveform. The terminal according to claim 1.

6. A size of one field included in the downlink control information when the first upper layer signal instructs dynamic transmission waveform switching is the same as a size of the one field included in the downlink control information when the second upper layer signal instructs the second transmission waveform. The terminal according to claim 5.

7. The one field is Precoding information and number of layers, Antenna ports, PTRS-DMRS association, or DMRS sequence initialization. The terminal according to claim 6.

8. When the downlink control information indicates a resource allocation method according to resource allocation type 0, the uplink signal is the second transmission waveform. The terminal according to claim 1.

9. The downlink control information is generated using DCI format 0-1 or DCI format 0-2. The terminal according to claim 1.

10. The first higher layer signal is included in a pusch-ConfigIE. The terminal according to claim 1.

11. A method for transmitting downlink control information including a first upper layer signal instructing dynamic transmission waveform switching and a first control signal instructing whether an uplink signal is to be transmitted using a first transmission waveform or a second transmission waveform, transmitting the uplink signal in a signal waveform determined based on the first higher layer signal and the first control signal; Communication methods.

12. The first transmission waveform is a signal generated using a transformPrecoder, The second transmission waveform is a signal generated without using the transformPrecoder. The communication method according to claim 11.

13. When the first upper layer signal indicates dynamic switching of a transmission waveform, if a size of a field included in the downlink control information differs between the first transmission waveform and the second transmission waveform, the size of the field in the second transmission waveform is set to be the size of the field. The communication method according to claim 12.

14. The one field is a field related to antenna ports or PTRS-DMRS association. The communication method according to claim 13.

15. When the first upper layer signal does not instruct dynamic transmission waveform switching, the signal waveform is determined based on a second upper layer signal that instructs whether the uplink signal is to be transmitted using the first transmission waveform or the second transmission waveform. The communication method according to claim 11.

16. A size of one field included in the downlink control information when the first upper layer signal instructs dynamic transmission waveform switching is the same as a size of the one field included in the downlink control information when the second upper layer signal instructs the second transmission waveform. The communication method according to claim 15.

17. The one field is DMRS sequence initialization or Precoding information and number of layers.

17. The communication method according to claim 16.

18. The method of claim 17, wherein when the downlink control information indicates a resource allocation method according to resource allocation type 0, the uplink signal is the second transmission waveform. The communication method according to claim 11.

19. The downlink control information is generated using DCI format 0-1 or DCI format 0-2. The communication method according to claim 11.

20. The first upper layer signal is included in a pusch-ConfigIE. The communication method according to claim 11.

21. A process of receiving downlink control information including a first upper layer signal instructing dynamic transmission waveform switching and a first control signal instructing whether an uplink signal is to be transmitted using a first transmission waveform or a second transmission waveform; a process of transmitting the uplink signal in a signal waveform determined based on the first higher layer signal and the first control signal; Integrated circuits.