Terminal, base station and communication method

Abstract

A terminal includes: a control circuit that determines a field size of control information on the basis of a field size when a first transmission waveform of an uplink signal and a second transmission waveform are set, the data size of the second transmission waveform being larger than the data size of the first transmission waveform, when dynamic switching between the first transmission waveform and the second transmission waveform is set; and a receiving circuit receiving the control information based on the field size.

Description

Technical Field

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

[0002] In recent years, with the expansion and diversification of wireless services, the rapid development of the Internet of Things (IoT) is expected, and the application of mobile communications is expanding not only to information terminals such as smartphones, but also to all fields such as vehicles, homes, home appliances, and industrial equipment. In order to support the diversification of services, in addition to increasing system capacity, the performance and functions of mobile communication systems are required to be greatly improved in response to various requirements such as the increase in the number of connected devices or low latency. The fifth generation mobile communication system (5G) has the characteristics of large capacity and ultra-high speed (eMBB: enhanced Mobile Broadband), multi-device connection (mMTC: massive Machine Type Communication), and ultra-reliable and low latency communication (URLLC: Ultra Reliable and Low Latency Communication), and uses these characteristics to flexibly provide wireless communication according to a variety of needs.

[0003] The 3rd Generation Partnership Project (3GPP), an international standards organization, is developing specifications for New Radio (NR), one of the 5G wireless interfaces.

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS38.104, “NR Base Station (BS) radio transmission and reception (Release 15),” March 2021.

[0007] Non-patent document 2: RP-202928, “New WID on NR coverage enhancements,” China Telecom, December 2020.

[0008] Non-patent document 3: RP-220937, “Revised WID on Further NR coverage enhancements,” China Telecom, March 2022.

[0009] Non-patent document 4: 3GPP TS38.211, “NR Physical channels and modulation (Release 17),” March 2022.

[0010] Non-patent document 5: 3GPP TS38.212, “NR Multiplexing and channel coding (Release 17),” March 2022.

[0011] Non-patent document 6: 3GPP TS38.213, “NR Physical layer procedures for control (Release 17),” March 2022.

[0012] Non-patent document 7: 3GPP TS38.214, “NR Physical layer procedures for data (Release 17),” March 2022. Summary of the invention

[0013] Further study is needed on the transmit signals used by NR.

[0014] The non-limiting embodiments of the present disclosure help to provide a terminal, a base station, and a communication method that can improve the reception performance of signals in an uplink.

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

[0016] Effects of the Invention

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

[0018] More advantages and effects of an embodiment of the present disclosure will be explained through the description and drawings. These advantages and / or effects are provided by several embodiments, and the features described in the description and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 This is a method for determining the transmission waveform of the PUSCH (Physical Uplink Shared Channel) in NR up to Release 17.

[0020] Figure 2 It is a mapping table of the precoding information and number of layers fields in scenario 3-1.

[0021] Figure 3 It is a mapping table of the precoding information and layer number field in case 3-2.

[0022] Figure 4 It is a mapping table of the precoding information and layer number field in case 4-1.

[0023] Figure 5 It is a mapping table of the precoding information and layer number field in case 4-2.

[0024] Figure 6 It is a mapping table of the precoding information and layer number field in case 4-3.

[0025] Figure 7 It is a mapping table of the precoding information and layer number field in scenario 5-1.

[0026] Figure 8 It is a mapping table of the precoding information and layer number field in case 5-2.

[0027] Fig. 9 It is a mapping table of precoding information and layer number field in case 6.

[0028] Fig.10 It is a mapping table of the antenna ports field relative to DFT-s-OFDM (Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing) in scenario A1.

[0029] Fig.11It is a mapping table of antenna port fields for CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) in scenario A1 (transmission layer number 1).

[0030] Fig.12 It is a mapping table of the antenna port field relative to CP-OFDM in case A1 (transmission layer number 2).

[0031] Fig.13 This is a mapping table of the antenna port field relative to CP-OFDM in case A1 (number of transmission layers: 3).

[0032] Fig.14 This is a mapping table of the antenna port field relative to CP-OFDM in case A1 (number of transmission layers 4).

[0033] Fig.15 It is a mapping table of the antenna port field relative to DFT-s-OFDM in case A2.

[0034] Fig.16 It is a mapping table of the antenna port field relative to CP-OFDM in case A2 (transmission layer number 1).

[0035] Fig.17 It is a mapping table of the antenna port field relative to CP-OFDM in case A2 (transmission layer number 2).

[0036] Fig.18 It is a mapping table of the antenna port field relative to CP-OFDM in case A2 (transmission layer number 3).

[0037] Fig.19 This is a mapping table of the antenna port field relative to CP-OFDM in case A2 (number of transmission layers 4).

[0038] Fig. 20 It is a mapping table of the antenna port field relative to CP-OFDM in case B1 (transmission layer number 1).

[0039] Fig.21 It is a mapping table of the antenna port field relative to CP-OFDM in case B1 (transmission layer number 2).

[0040] Fig. 22 This is a mapping table of the antenna port field relative to CP-OFDM in case B1 (number of transmission layers: 3).

[0041] Fig.23 This is a mapping table of the antenna port field relative to CP-OFDM in case B1 (number of transmission layers: 4).

[0042] Fig.24 It is a mapping table of the antenna port field relative to CP-OFDM in case B2 (transmission layer number 1).

[0043] Fig.25 It is a mapping table of the antenna port field relative to CP-OFDM in case B2 (transmission layer number 2).

[0044] Fig.26 This is a mapping table of the antenna port field relative to CP-OFDM in case B2 (number of transmission layers: 3).

[0045] Fig. 27 This is a mapping table of the antenna port field relative to CP-OFDM in case B2 (number of transmission layers: 4).

[0046] Fig.28 It is a flow chart.

[0047] Fig.29 It is the structure of the base station.

[0048] Fig.30 It is the structure of the terminal.

[0049] Fig.31 It is the NG-RAN (Next Generation-Radio Access Network) architecture.

[0050] Fig.32 It is the functional separation between NG-RAN and 5GC (5th Generation Core).

[0051] Fig.33 It is the interaction between UE (user equipment), gNB (gNodeB) and AMF (Access and Mobility Management Function) (5GC entity).

[0052] Fig.34 is a use case for 5G NR.

[0053] Fig.35 It is the non-roaming reference architecture for 5G NR.

[0054] Fig.36 It is a block diagram showing a configuration example of a part of the base station 100 .

[0055] Fig.37 It is a block diagram showing a configuration example of a part of the terminal 200.

[0056] Fig.38 This is an example of an MCS (Modulation and Coding Scheme) table.

[0057] Fig.39 is another example of an MCS table. DETAILED DESCRIPTION

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

[0059] In NR, in addition to the frequency bands below 6 GHz (FR1: Frequency Range 1) such as 700 MHz to 3.5 GHz bands that have been mainly used for cellular, millimeter wave bands (FR2) such as 28 GHz or 39 GHz that can ensure a wideband are also used (Non-Patent Document 1). In addition, in FR1, it is also possible to use higher frequency bands than 3.5 GHz such as Long Term Evolution (LTE) or 3G (3rd Generation mobile communication systems).

[0060] As the frequency band increases, the propagation loss increases and the reception quality deteriorates. Therefore, in NR, it is expected to maintain appropriate communication quality relative to the same communication area (coverage) as previous radio access technologies (RAT: Radio Access Technology) such as LTE and 3G. In 3GPP Release 17 (Rel.17) and Release 18 (Rel.18), research was conducted to improve the coverage of NR (Non-Patent Documents 2, 3).

[0061] In NR, a terminal (e.g., also referred to as "user equipment (UE)") sends and receives data based on resource allocation indicated by a layer 1 control signal (e.g., DCI: Downlink Control Information) on a downlink control channel (e.g., PDCCH: Physical Downlink Control Channel) from a base station (e.g., also referred to as "gNB") or by radio resource control (RRC: Radio Resource Control) as layer 3 (non-patent documents 4 to 7).

[0062] In the uplink (UL), the terminal transmits an uplink data channel (eg, PUSCH: Physical Uplink Shared Channel) according to resource allocation (eg, Grant or UL grant) from the base station.

[0063] In NR, the transmission waveform for PUSCH transmission supports both DFT-s-OFDM and CP-OFDM. DFT-s-OFDM can ensure a wider uplink coverage than CP-OFDM because the peak-to-average power ratio (PAPR) of the transmitted signal is low and the power utilization efficiency is high. On the other hand, CP-OFDM has a high affinity with multiple-input multiple-output (MIMO), so it is an effective transmission waveform for high-efficiency transmission (for example, multi-rank or multi-layer transmission in spatial multiplexing transmission) in a high signal-to-interference and noise power ratio (SINR) environment.

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

[0065] The transmission waveform of message 3 PUSCH is determined based on msg3-transformPrecoder, which is a parameter set in RRC. The transmission waveform of message A PUSCH is determined based on msgA-transformPrecoder, which is a parameter set in RRC. If msgA-transformPrecoder is not set in RRC, the transmission waveform is determined based on msg3-transformPrecoder.

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

[0067] The transmission waveform of the PUSCH dynamically scheduled in DCI format 0-1 or DCI format 0-2 is determined based on transformPrecoder, which is a parameter included in pusch configuration (pusch-Config) configured in RRC. If transformPrecoder is not configured in RRC, the transmission waveform is determined based on msg3-transformPrecoder.

[0068] The transmission waveform of a PUSCH (e.g., a configured grant-PUSCH (CG-PUSCH)) that transmits a PUSCH with resource allocation indicated by RRC as layer 3 or semi-fixed resource allocation using activation DCI is determined based on transformPrecoder, which is a parameter included in configuredGrantConfig (configured grant configuration) set in RRC. When transformPrecoder is not set in RRC, the transmission waveform is determined based on msg3-transformPrecoder.

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

[0070] In a conventional cellular system, it is assumed that DFT-s-OFDM is set to ensure coverage of the cell edge terminals, which is particularly important for improving uplink coverage. However, in the cell edge terminals, there may be a situation where a higher SINR is ensured to transmit PUSCH due to instantaneous fluctuations in the channel or interference environment. In this case, if the transmission waveform is limited to semi-static setting, it is difficult for the cell edge terminal that sets the transmission waveform to DFT-s-OFDM to switch the transmission waveform to CP-OFDM according to the instantaneous fluctuation to perform efficient transmission (for example, multi-layer transmission using MIMO spatial multiplexing, etc.), and the transmission efficiency of the cell edge terminal cannot be improved.

[0071] We are currently studying how to dynamically switch the DCI format for scheduling PUSCH and dynamically change the PUSCH transmission waveform.

[0072] As an example, DFT-s-OFDM can be set for PUSCH scheduled in DCI format 0-0, and CP-OFDM can be set for PUSCH scheduled in DCI format 0-1. However, since DCI format 0-0 only supports the allocation of PUSCH with the minimum required functions, there are greater restrictions on the scheduling of PUSCH using DFT-s-OFDM transmission waveform. Specifically, cross-carrier scheduling in carrier aggregation cannot be performed, or bandwidth part (BWP: Bandwidth Part) cannot be switched, or precoding or antenna port notification cannot be performed, or retransmission control based on codebook group (CBG: Code Block Group) cannot be performed.

[0073] As another example, CP-OFDM can be set for PUSCH scheduled in DCI format 0-0, and DFT-s-OFDM can be set for PUSCH scheduled in DCI format 0-1. However, since DCI format 0-0 only supports one layer of transmission, and PUSCH transmission of the DFT-s-OFDM transmission waveform also only supports one layer of transmission, it is not possible to use multi-layer transmission of more than two layers for efficient transmission.

[0074] As a method of dynamically switching the transmission waveform in a single DCI format (e.g., only DCI format 0-1 or DCI format 0-2), it is possible to consider adding a field for notifying the transmission waveform in the DCI format. However, the introduction of the transmission waveform notification field will increase the number of DCI bits. In particular, DCI format 0-2 is a DCI designed for URLLC. Since it is expected to improve the reliability of DCI reception by reducing the number of DCI bits as much as possible, it is not desirable to increase the number of DCI bits.

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

[0076] Specifically, when the base station sets a dynamic switching of the transmission waveform for the terminal, the field size of each existing DCI is determined based on the field size when CP-OFDM is set as the transmission waveform, and the existing DCI field is used to notify the transmission waveform of the PUSCH. As a result, the dynamic transmission waveform can be notified without increasing the number of DCI bits.

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

[0078] After the dynamic transmission waveform switching is enabled, in order to actually perform the enabled dynamic transmission waveform switching, it is necessary to receive DCI, and in order to receive DCI, it is necessary to first determine the DCI field size.

[0079] That is, if dynamic transmission waveform switching is to be enabled, the DCI field size must be determined first, and the DCI field size is determined based on the size of CP-OFDM, which is larger than the size of DFT-s-OFDM. It should be noted that when the DCI field size of DFT-s-OFDM is larger than the field size of CP-OFDM, it can also be determined based on the size of DFT-OFDM. The transmission waveform is not limited to DFT-s-OFDM and CP-OFDM, and can also be applied to cases with more than three transmission waveforms. When there are more than three transmission waveforms, the determination is based on the largest size, but a transmission waveform that is not the largest size can also be used.

[0080] In one example, the DCI field contains the following.

[0081] Frequency domain resource assignment

[0082] Precoding information and number of layers

[0083] Antenna port

[0084] PTRS-DMRS association (Phase Tracking Reference Signal-Demodulation Reference Signal associsation)

[0085] DMRS sequence initialization

[0086] By changing (repurposing) an existing field in DCI format 0-1 or DCI format 0-2, it is notified whether the transmission waveform is CP-OFDM or DFT-s-OFDM, and whether transform precoding is enabled or disabled.

[0087] This makes it possible to dynamically switch the transmission waveform without increasing the number of DCI bits.

[0088] Hereinafter, non-limiting embodiments of the present disclosure will be described.

[0089] Reference Fig.28 ,In step 1, the terminal determines whether the dynamic transmission waveform switching is valid.

[0090] When the dynamic transmission waveform switching in step 1 is valid, the terminal determines the DCI field size based on CP-OFDM in step 2. In addition, the terminal receives DCI according to the determined DCI field size and determines the number of transmission layers.

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

[0092] When the dynamic transmission waveform switching in step 1 is invalid, the terminal determines the transmission waveform based on the RRC parameters, and determines the DCI field size based on the transmission waveform set semi-statically.

[0093] (Implementation Method 1)

[0094] In this embodiment, the terminal determines the transmission waveform of the PUSCH based on the precoding information included in the DCI and the number of transmission layers notified to the terminal by the layer number field or the SRI (Scheduling Request Indicator) field.

[0095] [Step 1]

[0096] The RRC setting is used to enable (enabled) or disable (disabled) dynamic transmission waveform switching for DG-PUSCH dynamically scheduled in DCI format 0-1 or DCI format 0-2. For example, the dynamic transmission waveform switching can be enabled by the following method. When the setting is disabled, the terminal performs semi-static transmission waveform switching.

[0097] <How to enable dynamic transmission waveform switching 1>

[0098] Dynamic transmit waveform switching is enabled using a new parameter value (dynamicSwitch) of the parameter (transformPrecoder) of the PUSCH-Config IE. Dynamic transmit waveform switching is enabled based on the new parameter value dynamicSwitch included in the pusch-Config for the PUSCH dynamically scheduled in DCI format 0-1 or DCI format 0-2 for the transformPrecoder.

[0099] Specifically, when the value of transformPrecoder is set to dynamicSwitch, the terminal dynamically determines the transmission waveform of PUSCH based on the information notified by DCI as described below. In other words, the terminal determines whether to apply DFT-s-OFDM or CP-OFDM to PUSCH. In addition, "dynamicSwitch" set as the value of transformPrecoder is an example and is not limited to this.

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

[0101] In addition, when the value of transformPrecoder is set to disabled, the terminal may disable the semi-static switching of the transmission waveform of the PUSCH. The terminal may also semi-statically set the transmission waveform of the PUSCH to CP-OFDM instead of disabling the semi-static switching of the transmission waveform.

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

[0103] <How to enable dynamic transmission waveform switching 2>

[0104] The new RRC parameter transformPrecoderDynamic is imported into the pusch-ConfigIE for PUSCH dynamically scheduled in DCI format 0-1 or DCI format 0-2 to enable dynamic transmission waveform switching based on transformPrecoderDynamic.

[0105] Specifically, when the pusch-ConfigIE is set to transformPrecoderDynamic, the terminal determines that the value of transformPrecoder as the existing RRC parameter is invalid (that is, the value of transformPrecoder is discarded), and enables dynamic transmission waveform switching to perform Fig.28 Steps 2 and 3 are shown.

[0106] When transformPrecoderDynamic is not set, when the value of transformPrecoder is set to enabled, the terminal can enable semi-static transmission waveform switching of the PUSCH transmission waveform. The terminal can also semi-statically set the PUSCH transmission waveform to DFT-s-OFDM instead of enabling semi-static transmission waveform switching.

[0107] When transformPrecoderDynamic is not set, when the value of transformPrecoder is set to disabled, the terminal may disable the semi-static transmission waveform switching of the PUSCH. The terminal may also semi-statically set the transmission waveform of the PUSCH to CP-OFDM instead of disabling the semi-static transmission waveform switching.

[0108] In the case where transformPrecoderDynamic is not set, when transformPrecoder is not set, the terminal determines the sending waveform based on msg3-transformPrecoder.

[0109] [Step 2]

[0110] In Embodiment 1, the terminal uses the precoding information and the number of layers field to determine the number of layers among the parameters included in the DCI. Hereinafter, a method for determining the size (number of bits) of the precoding information and the number of layers field required for receiving the precoding information and the number of layers field will be described.

[0111] When the terminal enables dynamic transmission waveform switching, the size (number of bits) of the precoding information and layer number field of the DCI is set to the same number of bits as when the CP-OFDM transmission waveform is semi-statically set. The details are as follows.

[0112] Furthermore, when the DCI field size when a transmission waveform other than CP-ODFM is set in step 1 is used, the size (number of bits) of the precoding information and the layer number field can be determined based on the DCI field size of the transmission waveform used.

[0113] (Case 1) When the RRC parameter txConfig included in the pusch-ConfigIE is set to nonCodeBook, the number of bits of the precoding information and layer number fields is 0 bits.

[0114] (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 of the precoding information and layer number fields is 0 bits.

[0115] (Case 3) When the RRC parameter txConfig included in the pusch-ConfigIE 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,

[0116] (Case 3-1) When the RRC parameter maxRank (maximum rank) is set to 2, 3, or 4, the number of bits of the precoding information and layer number fields can be 4, 5, or 6 bits.

[0117] (Case 3-2) When the RRC parameter maxRank is set to 1, the number of bits of the precoding information and layer number fields is 2, 4, or 5 bits.

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

[0119] (Case 4-1) When the RRC parameter maxRank is set to 2, the number of bits of the precoding information and layer number fields is 4 or 5 bits.

[0120] (Case 4-2) When the RRC parameter maxRank is set to 3 or 4, the number of bits of the precoding information and layer number fields is 4 or 6 bits.

[0121] (Case 4-3) When the RRC parameter maxRank is set to 1, the number of bits of the precoding information and layer number fields is 3 or 4 bits.

[0122] (Case 5) When the RRC parameter txConfig included in the pusch-ConfigIE 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,

[0123] (Case 5-1) When the RRC parameter maxRank is set to 2, the number of bits of the precoding information and layer number fields is 2 or 4 bits.

[0124] (Case 5-2) When the RRC parameter maxRank is set to 1, the number of bits of the precoding information and layer number fields is 1 or 3 bits.

[0125] (Case 6) When the RRC parameter txConfig included in the pusch-ConfigIE 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 of the precoding information and layer number field is 2 bits.

[0126] [Step 3]

[0127] The terminal is capable of receiving the precoding information and the number of layers field after determining the number of bits of the precoding information and the number of layers field. The terminal determines the number of transmission layers for PUSCH transmission based on the precoding information and the number of layers field of the DCI or the information of the SRI field, for example. In addition, the terminal determines the transmission waveform of the PUSCH based on the determined number of transmission layers.

[0128] Specifically, when 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, 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 in each case of step 2 above is as follows.

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

[0130] (Case 2) The terminal determines that the number of transmission layers is 1, and determines that the transmission waveform is DFT-s-OFDM.

[0131] (Scenario 3-1) The terminal is based on Figure 2 The mapping table and precoding information and layer number field information (for example, Figure 2 The terminal determines the number of transmission layers and TPMI (Transmit Precoding Matrix Index) by using the value of the bit field mapped to index. When the number of transmission layers determined is 1, the terminal determines the transmission waveform of PUSCH to be DFT-s-OFDM. When the number of transmission layers determined is 2 or more, the transmission waveform of PUSCH is determined to be CP-OFDM.

[0132] (Case 3-2) The terminal determines that the number of transmission layers is 1 and the transmission waveform is DFT-s-OFDM. In addition, the terminal determines that the transmission layer is 1 and the transmission waveform is DFT-s-OFDM. Figure 3 The mapping table and precoding information and layer number field information (for example, Figure 3 The value of the bit field mapped to the index) determines the TPMI.

[0133] (Case 4-1) The terminal is based on Figure 4 The mapping table and precoding information and layer number field information (for example, Figure 4 The terminal determines the number of transmission layers and TPMI based on the value of the bit field mapped to the index. When the number of transmission layers determined is 1, the terminal determines the transmission waveform of the PUSCH to be DFT-s-OFDM. When the number of transmission layers determined is 2 or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM.

[0134] (Case 4-2) The terminal is based on Figure 5 The mapping table and precoding information and layer number field information (for example, Figure 5 The terminal determines the number of transmission layers and TPMI based on the value of the bit field mapped to the index. When the number of transmission layers determined is 1, the terminal determines the transmission waveform of the PUSCH to be DFT-s-OFDM. When the number of transmission layers determined is 2 or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM.

[0135] (Case 4-3) The terminal determines the number of transmission layers to be 1 and determines the transmission waveform to be DFT-s-OFDM. In addition, the terminal determines the number of transmission layers to be 1 and determines the transmission waveform to be DFT-s-OFDM. Figure 6 The mapping table and precoding information and layer number field information (for example, Figure 6 The value of the bit field mapped to the index) determines the TPMI.

[0136] (Case 5-1) The terminal is based on Figure 7 The mapping table and precoding information and layer number field information (for example, Figure 7 The terminal determines the number of transmission layers and TPMI based on the value of the bit field mapped to the index. When the number of transmission layers determined is 1, the terminal determines the transmission waveform of the PUSCH to be DFT-s-OFDM. When the number of transmission layers determined is 2 or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM.

[0137] (Case 5-2) The terminal determines that the number of transmission layers is 1, and determines that the transmission waveform is DFT-s-OFDM. In addition, based on Figure 8 The mapping table and precoding information and layer number field information (for example, Figure 8 The value of the bit field mapped to the index) determines the TPMI.

[0138] (Case 6) The terminal is based on Fig. 9 The mapping table and precoding information and layer number field information (for example, Fig. 9 The terminal determines the number of transmission layers and TPMI based on the value of the bit field mapped to the index. When the number of transmission layers determined is 1, the terminal determines the transmission waveform of the PUSCH to be DFT-s-OFDM. When the number of transmission layers determined is 2 or more, the terminal determines the transmission waveform of the PUSCH to be CP-OFDM.

[0139] According to this embodiment, the transmission waveform of the PUSCH can be notified using the precoding information and the number of layers or the SRI field which are the existing DCI fields, so that the transmission waveform can be dynamically notified without increasing the number of DCI bits for switching the transmission waveform. By dynamically switching the transmission waveform using the number of transmission layers, it is possible to ensure the coverage of DFT-s-OFDM and one-layer transmission, as well as the high-efficiency transmission by flexibly switching CP-OFDM and multi-layer transmission.

[0140] In addition, according to the present embodiment, when the terminal dynamically switches the transmission waveform between CP-OFDM and DFT-s-OFDM, the field size of DCI is determined based on the field size of DCI when CP-OFDM is set. Thus, even when the transmission waveform is dynamically switched with a single DCI format (e.g., DCI format 0-1 or DCI format 0-2), the terminal can grasp the field size of DCI and appropriately receive DCI without depending on the switched transmission waveform.

[0141] (Implementation Method 2)

[0142] In this embodiment, the terminal determines the transmission waveform of the PUSCH based on the number of transmission layers and TPMI notified to the terminal by the precoding information and layer number field or the SRI field included in the DCI.

[0143] In implementation mode 2, precoding information and layer number fields are used to determine the number of layers in the parameters contained in the DCI, and the method for determining the size (number of bits) of the precoding information and layer number fields required to receive the precoding information and layer number fields (i.e., steps 1 and 2) is the same as in implementation mode 1.

[0144] In step 3, when the number of transmission layers is 1, the transmission waveform of the PUSCH is determined based on the value of the TPMI, which is different from implementation mode 1. The mapping of the TPMI and the transmission waveform can be predetermined or notified by the RRC. Furthermore, it is also possible to set a threshold for the TPMI, and when the notified TPMI is greater than the threshold, the transmission waveform is set to DFT-s-OFDM, and when the TPMI is below the threshold, the transmission waveform is set to CP-OFDM. In addition, it is also possible that when the notified TPMI is greater than the threshold, the transmission waveform is set to CP-OFDM, and when the TPMI is below the threshold, the transmission waveform is set to DFT-s-OFDM.

[0145] [Step 3]

[0146] The terminal determines a transmission waveform of the PUSCH based on the determined number of transmission layers and TPMI.

[0147] Specifically, when the number of transmission layers is 1, the terminal determines the transmission waveform of the PUSCH based on the value of the 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 in each case of step 2 above is as follows.

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

[0149] (Case 2) The terminal determines that the number of transmission layers is 1, and determines that the transmission waveform is DFT-s-OFDM.

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

[0151] (Case 3-2) The terminal is based on Figure 3 The mapping table given determines the PUSCH transmission waveform based on the TPMI value.

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

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

[0154] (Case 4-3) The terminal is based on Figure 6 The mapping table given determines the PUSCH transmission waveform based on the TPMI value.

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

[0156] (Case 5-2) The terminal is based on Figure 8 The mapping table given determines the PUSCH transmission waveform based on the TPMI value.

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

[0158] The correspondence relationship between the TPMI value and the transmission waveform of the PUSCH (for example, the transmission waveform when TPMI=n is notified) may be predetermined, or the correspondence relationship may be set by RRC.

[0159] In the correspondence relationship using RRC, the correspondence relationship between each TPMI number and the transmission waveform may be notified, and a threshold value of the TPMI number for switching the transmission waveform may be notified.

[0160] In the case where a threshold value has been set, for example, a TPMI number below the threshold value may be associated with DFT-s-OFDM, and a TPMI number greater than the threshold value may be associated with CP-OFDM. Alternatively, for example, a TPMI number below the threshold value may be associated with CP-OFDM, and a TPMI number greater than the threshold value may be associated with DFT-s-OFDM.

[0161] In addition, multiple thresholds can be set according to the number of transmitted waveforms. Alternatively, a TPMI number below a first threshold is associated with a first transmitted waveform, a TPMI number greater than the first threshold and below a second threshold is associated with a second transmitted waveform, and a TPMI number greater than the second threshold is associated with a third transmitted waveform.

[0162] In addition, the number N of TPMI numbers corresponding to DFT-s-OFDM may also be notified. TPMI In this case, for example, TPMI=0~N TPMI -1 establishes a correspondence with DFT-s-OFDM, and the other TPMI numbers establish a correspondence with CP-OFDM. In addition, the correspondence between the TPMI value and the transmission waveform of the PUSCH may be different according to each of the above situations, or the same correspondence may be used. In addition, the number of TPMI numbers corresponding to DFT-s-OFDM and the number of TPMI numbers corresponding to CP-OFDM may also be different.

[0163] According to this embodiment, the transmission waveform of the PUSCH can be notified using the precoding information and the number of layers or the SRI field which are the existing DCI fields, so that the transmission waveform can be dynamically notified without increasing the number of DCI bits for switching the transmission waveform. By dynamically switching the transmission waveform using the number of transmission layers, it is possible to ensure the coverage of DFT-s-OFDM and one-layer transmission, and to flexibly switch the high-efficiency transmission of CP-OFDM and multi-layer transmission. In addition, in one-layer transmission, since the transmission waveform is also determined based on the TPMI, the transmission waveform can be switched more flexibly.

[0164] (Implementation 3)

[0165] Step 1 of the operational example of the third embodiment may be the same as that of the first embodiment.

[0166] 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 for receiving the TDRA is described.

[0167] [Step 2]

[0168] The number of bits of TDRA is the same for both CP-OFDM and DFT-s-OFDM. The terminal sets the size (number of bits) of the TDRA field of the DCI to

[0169] [Mathematical formula 1]

[0170]

[0171] Here, I is the number of registrations of the RRC parameter pusch-TimeDomainAllocationList (pusch time domain allocation list).

[0172] The sizes (number of bits) of other fields such as the DCI precoding information and layer number field or antenna port are determined based on CP-OFDM. As described in Embodiment 1, they can also be determined based on DFT-s-OFDM.

[0173] TDRA may include the time slot offset K2 applied in PUSCH, the start and length indicator SLIV (Start and Length Indicator Value) or the start codeword S and the number of codewords (PUSCH length) L, the PUSCH mapping type, the number of repeated transmissions and the transmission waveform.

[0174] In addition, the terminal may determine the size (number of bits) of the precoding information and the number of layers field of the DCI. The method of determining the size (number of bits) of the precoding information and the number of layers field is the same as that of the first and second embodiments.

[0175] [Step 3]

[0176] The terminal determines the time domain resource allocation and transmission waveform of PUSCH transmission based on the information of the TDRA field of DCI. Specifically, based on the index notified by the TDRA field, the terminal determines the time domain resource allocation candidate (that is, the combination of K2, S, L, PUSCH mapping type, number of repetitions, and transmission waveform) corresponding to the index.

[0177] The information of the time domain resource candidates corresponding to the index of TDRA can be notified by RRC.

[0178] The correspondence between the TDRA index value and the PUSCH transmission waveform (for example, the transmission waveform when index n is notified) can be set by RRC. In addition, the number of indices corresponding to DFT-s-OFDM and the number of indices corresponding to CP-OFDM can also be different.

[0179] In addition, when the terminal determines that the transmission waveform of the PUSCH is DTF-s-OFDM based on the information in the TDRA field, it is not assumed that the number of transmission layers is notified by 2 or more using the precoding information and the number of layers field.

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

[0181] (Implementation 4)

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

[0183] Step 1 of Implementation 4 may be the same as that of Implementation 1.

[0184] [Step 2]

[0185] The size (number of bits) of the MCS field of DCI is 5 bits regardless of CP-OFDM or DFT-s-OFDM, so the terminal sets the size (number of bits) of the MCS field to 5 bits.

[0186] The sizes (number of bits) of other fields such as the DCI precoding information and layer number field or antenna port are determined based on CP-OFDM. As described in Embodiment 1, they can also be determined based on DFT-s-OFDM.

[0187] [Step 3]

[0188] The terminal uses DCI I MCS , determine the modulation order Q according to the MCS table m , target coding rate R. Specifically, the terminal is based on the index I notified by the MCS field MCS , decide to send the waveform.

[0189] I MCS The corresponding relationship between the value of and the transmission waveform of PUSCH (for example, notification I MCS = n The transmission waveform when the transmission is performed can be determined in advance according to the standard, or the corresponding relationship can be set by RRC. In addition, in the corresponding relationship using RRC, I MCS The correspondence relationship between each and the transmission waveform may be notified as well as a threshold value (waveform - MCS) of the MCS number for switching the transmission waveform.

[0190] When a threshold is set, for example, an MCS number below the threshold may be associated with DFT-s-OFDM, and an MCS number greater than the threshold may be associated with CP-OFDM. When a wide range of DFT-s-OFDM is used as the target, the coding rate is often reduced to improve reliability. Since CP-OFDM aims at high efficiency, it is effective to allocate a high coding rate (high MCS number) to CP-OFDM.

[0191] However, it is also possible to establish a correspondence between MCS numbers below a threshold and CP-OFDM, and establish a correspondence between MCS numbers above the threshold and DFT-s-OFDM, thereby using coding to improve reliability when the transmission waveform aims at high efficiency.

[0192] In addition, the number N of MCS numbers corresponding to DFT-s-OFDM may also be notified. MCS In this case, for example, it may be that I MCS =0~N MCS -1 establishes a corresponding relationship with DFT-s-OFDM. MCS Establish a corresponding relationship with CP-OFDM. MCS =0~N MCS -1 can establish a corresponding relationship with CP-OFDM. MCS A corresponding relationship can be established with DFT-s-OFDM.

[0193] In addition, the number of MCS numbers corresponding to DFT-s-OFDM and the number of MCS numbers corresponding to CP-OFDM may be different.

[0194] According to the present embodiment, since the transmission waveform of the PUSCH can be notified using the MCS field which is an existing DCI field, it is possible to perform dynamic transmission waveform notification without increasing the number of DCI bits for switching the transmission waveform.

[0195] (Variation of Implementation Example 4)

[0196] According to non-patent document 7, the MCS table of NR has the following I MCS The value of, that is, determines the modulation order Q m and the target coding rate R MCS The value of m I MCS For example, in the MCS table containing 256QAM (Quadrature Amplitude Modulation) for CP-OFDM or the MCS table for DFT-s-OFDM, 0<=IMCS <=27 determines the modulation order Q m and the target coding rate R MCS The value of Fig.38 ), 28<=I MCS <=31 means only the modulation order Q is determined m I MCS In addition, in the MCS table for CP-OFDM including up to 64QAM (that is, excluding 256QAM), 0<=I MCS <=28 determines the modulation order Q m and the target coding rate R MCS The value of 29 <= I MCS <=31 means only the modulation order Q is determined m I MCS The value of Fig.39 ). Generally speaking, the modulation order Q is determined when the signal is first transmitted. m and the target coding rate R MCS The value of the modulation order Q is determined during retransmission. m I MCS The value of .

[0197] Only determines the modulation order Q m I MCS The value is not determined by the modulation order Q m and the target coding rate R MCS The value of the spectrum efficiency increases continuously with the increase of the MCS number. Fig.38 Middle I MCS =28 Fig.39 Middle I MCS =29, that is, the modulation order Q m Even if the MCS number is increased, the target coding rate R is not determined, so the spectrum efficiency is not determined. Therefore, the fourth embodiment cannot be directly applied in retransmission. In this regard, in this variation, the retransmission (that is, when the notification only determines the modulation order Q) is described. m I MCS The method for determining the transmission waveform when the value of is set.

[0198] The following modified examples 1 to 3 describe the determination of the transmission waveform during retransmission, and the determination of the transmission waveform during initial transmission can use the transmission waveform determination method in embodiment 4. The threshold value (waveform-MCS) for switching the MCS number of the transmission waveform during initial transmission or the number N of MCS numbers corresponding to DFT-s-OFDM MCS The range of possible values ​​can be set to determine the modulation order Q m and the target coding rate R MCS The value of .

[0199] In the case where a threshold is set, for example, the MCS number below the threshold may be associated with the DFT-s-OFDM, and the modulation order Q may be determined. m and the target coding rate R MCS An MCS number greater than a threshold within a range of values ​​is established in correspondence with CP-OFDM.

[0200] In addition, when notifying the number N of MCS numbers corresponding to DFT-s-OFDM MCS In the case of, for example, it can also be, I MCS =0~N MCS -1 establishes a corresponding relationship with DFT-s-OFDM, and determines the modulation order Q m and the target coding rate R MCS The values ​​other than those in the range of I MCS Establish a corresponding relationship with CP-OFDM.

[0201] (Variation 1 of Implementation Example 4)

[0202] 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 the previous time. According to this modification, the processing for determining the transmission waveform can be omitted at the time of retransmission, so there is an advantage that the transmission waveform determination processing can be performed simply.

[0203] (Variation 2 of Implementation Example 4)

[0204] In this variant, the transmission waveform during retransmission is determined based on the number of transmission layers notified to the terminal. For example, when the number of transmission layers is 1, the terminal determines the transmission waveform of PUSCH to be DFT-s-OFDM. On the other hand, when the number of transmission layers is 2 or more, the terminal determines the transmission waveform of PUSCH to be CP-OFDM. According to this variant, dynamic notification of the transmission waveform can also be performed during retransmission. By dynamically switching the transmission waveform using the number of transmission layers, it is possible to ensure the coverage of DFT-s-OFDM and one-layer transmission, as well as high-efficiency transmission by flexibly switching CP-OFDM and multi-layer transmission.

[0205] (Variation 3 of Implementation Example 4)

[0206] In this variation, the transmission waveform at the time of retransmission is determined based on the modulation order notified to the terminal. The correspondence between the modulation order and the transmission waveform can apply any of the following options.

[0207] <Option 1>

[0208] The corresponding relationship between the modulation order and the transmission waveform is determined in advance. For example, the following corresponding relationship can be determined: m =2) or 16QAM (Q m =4) is set to DFT-s-OFDM, when 64QAM (Q m =6) or 256QAM (Q m =8) is set to a corresponding relationship such as CP-OFDM. The corresponding relationship between the modulation order and the transmission waveform can be predetermined according to the standard, or can be set by the higher layer (RRC signaling). In addition, as in the fourth embodiment, m I MCS The value of the MCS number is notified, and the threshold value (waveform-MCS) of the MCS number or the number N of the MCS number corresponding to DFT-s-OFDM is notified. MCS .

[0209] <Option 2>

[0210] Compared with only determining the modulation order Q m I MCS The value of determines the modulation order Q m and the target coding rate R MCS The corresponding relationship of the value of is predetermined, and the retransmission is based on the modulation order Q m I MCS The value of the corresponding modulation order Q m and the target coding rate R MCS The value of is used to determine the transmission waveform in the same way as the initial transmission. m and the target coding rate R MCS The value of ", can be set to have the same modulation order Q m Multiple I MCS The smallest value of I MCS For example, in Fig.38 In the MCS table for CP-OFDM including 256QAM, the modulation order Q m and the target coding rate R MCS The minimum index value of each modulation order, if QPSK (Q m =2) then I MCS =0, if 16QAM (Q m =4) then I MCS =5, if 64QAM (Q m =6) then I MCS =11, if 256QAM (Q m =8) then I MCS= 20. That is, the decision on the transmission waveform is different from the I MCS =28(Q m =2) is I MCS =0, relative to I MCS =29(Q m =4) is I MCS =5, relative to I MCS =30(Q m =6) is I MCS =11, relative to I MCS =31(Q m =8) is I MCS =20, the transmission waveform can be determined in the same manner as the initial transmission.

[0211] It should be noted that the modulation order Q determined by establishing a corresponding relationship with the modulation order at the time of retransmission m and the target coding rate R MCS The index of each modulation order is not limited to the minimum index value. A corresponding relationship can also be established with the maximum index value. In addition, it can also be set to a value that is offset from the minimum index value (or maximum index value). In addition, the value of the index can be predetermined according to the standard or set by the upper layer (RRC signaling). In addition, the value offset from the minimum index value (or maximum index value) can be predetermined according to the standard or set by the upper layer (RRC signaling).

[0212] (MCS table determination method)

[0213] According to non-patent document 7, in NR, for a terminal, an MCS table (mcs-Table) used when the transmission waveform is CP-OFDM and an MCS table (mcs-TableTransformPrecoder) used when the transmission waveform is DFT-s-OFDM can be set. That is, the terminal first determines the transmission waveform, and then determines that the MCS table used for transmission is the MCS table corresponding to the transmission waveform.

[0214] On the other hand, in the third variation of the fourth embodiment, since the MCS table is required for determining the transmission waveform at the time of retransmission, the MCS table needs to be determined before determining the transmission waveform. The following options are applicable to the MCS table determination method.

[0215] <When sending for the first time, option 1>

[0216] [Step 1] The terminal determines the transmission waveform based on the MCS index according to the method of implementation mode 4.

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

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

[0219] In addition, this option is not limited to variant example 3 of implementation example 4, and can also be applied to implementation example 4 and all variant examples of implementation example 4.

[0220] <When sending for the first time, option 2>

[0221] [Step 1] The terminal predetermines the MCS table to be used before deciding on the transmission waveform. For example, it may decide to use the MCS table based on the RRC parameters corresponding to CP-OFDM (e.g., mcs-Table). Alternatively, it may decide to use the MCS table based on the RRC parameters corresponding to DFT-s-OFDM (e.g., mcs-TableTransformPrecoder).

[0222] [Step 2] The terminal determines the transmission waveform based on the MCS index according to the method of Embodiment 4. In addition, the modulation order Q is determined based on the determined MCS table and MCS index. m and the target coding rate R.

[0223] In addition, this option is not limited to the third variant of the fourth embodiment, and can also be applied to the fourth embodiment and all the variants of the fourth embodiment.

[0224] <When resending, option 1>

[0225] [Step 1] The terminal determines that the MCS table is the same as the MCS table used for the previous transmission of the PUSCH of the same transport block.

[0226] [Step 2] The terminal determines the modulation method and the transmission waveform based on the MCS index according to the method of variant example 3 of implementation mode 4.

[0227] <When resending, option 2>

[0228] [Step 1] The terminal predetermines the MCS table to be used before deciding on the transmission waveform. For example, it may decide to use the MCS table based on the RRC parameters corresponding to CP-OFDM (e.g., mcs-Table). Alternatively, it may decide to use the MCS table based on the RRC parameters corresponding to DFT-s-OFDM (e.g., mcs-TableTransformPrecoder).

[0229] [Step 2] The terminal determines the modulation method and the transmission waveform based on the MCS index according to the method of variant example 3 of implementation example 4.

[0230] (Implementation method 5)

[0231] 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 Allocation (FDRA) field included in the DCI.

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

[0233] Step 2 of the action example of Implementation 5 may be the same as the case of dynamic resource allocation type switching in which the frequency domain resource allocation field determination method is enabled in other Implementation 2 described below.

[0234] [Step 3]

[0235] The terminal determines the frequency resource allocation and transmission waveform of PUSCH transmission based on the information of the FDRA field of DCI. Specifically, the terminal determines the transmission waveform based on the resource allocation type notified by the FDRA field. Specifically, when the resource allocation type 0 is notified in the frequency domain resource allocation method, the transmission waveform is determined to be CP-OFDM. On the other hand, when the resource allocation type 1 is notified in the frequency domain resource allocation method, the transmission waveform is determined to be DFT-s-OFDM.

[0236] According to the present embodiment, the transmission waveform of the PUSCH can be notified using the FDRA field which is an existing DCI field. Therefore, it is possible to perform dynamic transmission waveform notification without increasing the number of DCI bits for switching the transmission waveform.

[0237] (Other Embodiments 1)

[0238] Dynamic transmission waveform switching can also be applied to Message 3 or Message A transmitted as the first uplink data at the time of initial access.

[0239] In this case, the terminal can transmit on a physical random access channel (PRACH), and the terminal can switch the preamble of the PRACH between supporting dynamic transmission waveform switching and not supporting dynamic transmission waveform switching, and transmit.

[0240] Furthermore, the threshold of RSRP (Reference Signal Received Power) or RSRQ (Reference Signal Received Quality) for switching the transmission waveform may be notified to the terminal. For example, when the RSRP or RSRQ of the reference signal at the time of initial access is below the threshold, the terminal does not select dynamic transmission waveform switching in the PUSCH transmission of message 3 or message A, but selects dynamic transmission waveform switching when it is greater than the threshold. Alternatively, when the RSRP or RSRQ at the time of initial access is below the threshold, the terminal selects dynamic transmission waveform switching in the PUSCH transmission of message 3 or message A, but does not select dynamic transmission waveform switching when it is greater than the threshold.

[0241] Alternatively, a new parameter msg3-transformPrecoderDynamic may be introduced into 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 msg3-transformPrecoder, which is an existing RRC parameter, is invalid (that is, the value of msg3-transformPrecoder is discarded), and dynamic transmission waveform switching may be enabled. Alternatively, a new parameter value (msg3-transformPrecodeDynamic) may be introduced into the msg3-transformPrecode of the SIB.

[0242] The terminal can decide whether dynamic transmission waveform switching is valid or invalid based on the information contained in the DCI format 0-1 scrambled by the temporary cell radio network temporary identifier (TC-RNTI: Temporary Cell-RadioNetwork Temporary identifier) ​​or the random access response (RAR: Random Access Response) UL authorization.

[0243] In the notification of the transmission waveform (waveform indication), as method 1, DCI format 0-1 or RNR UL grant scrambled by TC-RNTI can be used, and if the reserved bit field is further used, the number of bits does not increase.

[0244] As method 2, it may be based on the number of transmission layers or number of repetitions.

[0245] As method 3, it can be based on the index of the TDRA table.

[0246] As method 4, it can be based on the MCS index.

[0247] (Other Implementation 2)

[0248] In the above-mentioned embodiment, regarding the method for determining other parameters included in the DCI, such as the method for determining the frequency domain resource allocation, antenna port, PTRS-DMRS association, and the number of bits for DMRS sequence initialization, the following method may be used.

[0249] [Frequency domain resource allocation field]

[0250] <Method 1>

[0251] When dynamic switching of transmission waveforms is enabled, the terminal determines the size (number of bits) of the frequency domain resource allocation field of the DCI using the following method.

[0252] When the terminal determines to use DFT-s-OFDM for PUSCH transmission according to the above embodiment, the resource allocation type 1 is applied in the frequency domain resource allocation method.

[0253] [Mathematical formula 2]

[0254]

[0255] Notify resource allocation.

[0256] On the other hand, when the terminal decides to use CP-OFDM for PUSCH transmission according to the above embodiment, resource allocation type 0 is applied in frequency domain resource allocation. RBG LSB notifies resource allocation.

[0257] (When resource allocation type 0 is set)

[0258] The number of bits in the frequency domain resource allocation field is

[0259] [Mathematical formula 3]

[0260]

[0261] bits. Here, N RB UL,BWP N is the number of resource blocks contained in the uplink BWP (Bandwidth Part) set for the terminal, RBG is the number of resource block groups (RBGs).

[0262] (When resource allocation type 1 is set)

[0263] The number of bits in the frequency domain resource allocation field is

[0264] [Formula 4]

[0265]

[0266] Bit.

[0267] (When dynamic resource allocation type switching is enabled)

[0268] The number of bits in the frequency domain resource allocation field is determined based on the larger bit of type 0 and type 1, so it is

[0269] [Mathematical formula 5]

[0270]

[0271] Bit.

[0272] When the terminal determines to use DFT-s-OFDM for PUSCH transmission according to the above embodiment, the resource allocation type 1 is applied in the frequency domain resource allocation method.

[0273] [Mathematical formula 6]

[0274]

[0275] Notify resource allocation.

[0276] On the other hand, when the terminal decides to use CP-OFDM for PUSCH transmission according to the above embodiment, it decides whether to apply resource allocation type 0 or resource allocation type 1 through the MSB of the frequency domain resource allocation field.

[0277] In the case of applying resource allocation type 0, the N RBG LSB notifies resource allocation. In case of applying resource allocation type 1, the frequency domain resource allocation field

[0278] [Formula 7]

[0279]

[0280] Notify resource allocation.

[0281] <Method 2>

[0282] When the dynamic switching of the transmission waveform is enabled, the terminal does not assume that the resource allocation type 0 is set. In other words, when the dynamic switching of the transmission waveform is enabled, the resource allocation method may always be determined to be the resource allocation type 1.

[0283] Thus, the number of bits in the frequency domain resource allocation field is

[0284] [Mathematical formula 8]

[0285]

[0286] Bit.

[0287] [Antenna Port field]

[0288] (Scenario A1)

[0289] When the RRC parameters are set to dmrs-Type=1 and maxLength (maximum length)=1, the number of bits of the antenna port field is 3 bits.

[0290] When it is decided to use DFT-s-OFDM for PUSCH transmission according to the above embodiment, the antenna port is notified by the 2LSB (or 2MSB) of the antenna port field. Fig.10 The given mapping table and the information of the antenna port field determine the antenna port.

[0291] On the other hand, when it is determined to use CP-OFDM for PUSCH transmission according to the above embodiment, the terminal performs the following operations based on the number of transmission layers: Fig.11 , 12 The mapping table given in 13 or 14 and the information in the antenna port field determine the antenna port.

[0292] It should be explained that Fig.10 The mapping of the values ​​0, 1, 2, and 3 to the antenna ports, and Fig.11 The values ​​2, 3, 4, and 5 of are the same as the mapping of antenna ports. Therefore, when the terminal decides to use DFT-s-OFDM for PUSCH transmission, it can use it in the same way as CP-OFDM. Fig.11 Instead of using a mapping table Fig.10 The mapping table.

[0293] (Case A2) When the RRC parameter is set to dmrs-Type=1 and maxLength=2, the number of bits of the antenna port field is 4 bits.

[0294] When the terminal determines to use DFT-s-OFDM for PUSCH transmission according to the above embodiment, based on Fig.15 The given mapping table and the information of the antenna port field determine the antenna port.

[0295] On the other hand, when the terminal determines to use CP-OFDM for PUSCH transmission according to the above embodiment, for each case where the number of transmission layers is 1, 2, 3 or 4, based on Fig.16 , 17 The antenna port is determined by the mapping table given in 18 or 19 and the information in the antenna port field.

[0296] It should be explained that Fig.15 The mapping of the value 0-11 to the antenna port, and Fig.16 The values ​​2-13 of are the same as the mapping of antenna ports. Therefore, when the terminal decides to send PUSCH as DFT-s-OFDM (or enable conversion precoding), it can use it in the same way as CP-OFDM. Fig.16 Instead of using a mapping table Fig.15 The mapping table.

[0297] In NR up to Rel.17, PUSCH using DFT-s-OFDM as the transmission waveform does not support RRC parameter setting to dmrs-Type = 2. Therefore, it is also possible that the terminal does not assume the setting of dmrs-Type = 2 when dynamic switching of the transmission waveform is enabled. In other words, when dynamic switching of the transmission waveform is enabled, the DMRS type can always be determined to be dmrs-Type = 1.

[0298] On the other hand, when the terminal enables dynamic switching of the transmission waveform, it is assumed that dmrs-Type = 2 is set. In this case, the DMRS type may be dynamically switched based on the transmission waveform. The details are as follows.

[0299] (Case B1) When the RRC parameter is set to dmrs-Type=2 and maxLength=1, the number of bits of the antenna port field is 4 bits.

[0300] When it is decided to use DFT-s-OFDM for PUSCH transmission according to the above embodiment, the antenna port is notified by the 2LSB (or 2MSB) of the antenna port field. Fig.10 The given mapping table and the information of the antenna port field determine the antenna port.

[0301] When the terminal determines to use CP-OFDM for PUSCH transmission according to the above embodiment, for each case where the number of transmission layers is 1, 2, 3 or 4, based on Fig. 20 , 21 The antenna port is determined by the mapping table given in 22 or 23 and the information in the antenna port field.

[0302] also, Fig.10 The mapping of the values ​​0, 1, 2, and 3 of to the antenna ports, and Fig. 20 The values ​​2, 3, 4, and 5 of are the same as the mapping of antenna ports. Therefore, when the terminal decides to use DFT-s-OFDM for PUSCH transmission, it can use it in the same way as CP-OFDM. Fig. 20 Instead of using a mapping table Fig.10 The mapping table.

[0303] (Case B2) When the RRC parameter is set to dmrs-Type=2 and maxLength=2, the number of bits of the antenna port field is 5 bits.

[0304] When DFT-s-OFDM is used for PUSCH transmission according to the above embodiment, the DMRS type is determined to be dmrs-Type=1, and the antenna port is notified by the 4LSB (or 4MSB) of the antenna port field. Fig.15 The given mapping table and the information of the antenna port field determine the antenna port.

[0305] On the other hand, when the terminal determines to use CP-OFDM for PUSCH transmission according to the above embodiment, for each case where the number of transmission layers is 1, 2, 3 or 4, based on Fig.24 , 25 The antenna port is determined by the mapping table given in 26 or 27 and the information in the antenna port field.

[0306] [PTRS-DMRS association field]

[0307] Similar to step 2 of the above embodiment, when dynamic switching of the transmission waveform is enabled, the terminal can 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 semi-statically set.

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

[0309] Here, the value of the PTRS-DMRS association field is valid only when the terminal decides to use CP-OFDM for PUSCH transmission according to the above implementation. That is, when the terminal decides to use DFT-s-OFDM for PUSCH transmission according to the above implementation, the terminal may not consider the value of the PTRS-DMRS association field.

[0310] [DMRS sequence initialization field]

[0311] Similar to step 2 of the above embodiment, when dynamic switching of the transmission waveform is enabled, the terminal can 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 semi-statically set.

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

[0313] (Other Implementation 3)

[0314] In the above embodiment, if the dynamic switching of the transmission waveform is enabled, the DCI field size is determined based on the field size of CP-OFDM, and the total DCI size (that is, 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 transmission waveform determined in the dynamic switching of the transmission waveform. In addition, when the total number of bits of all DCI fields is less than the DCI size, zero insertion (zero padding) may be applied.

[0315] In addition, the DCI field whose field size is determined based on CP-OFDM when dynamic switching of the transmission waveform is enabled may be part of the following DCI field (eg, frequency domain resource allocation).

[0316] Frequency domain resource allocation

[0317] Precoding information and number of layers

[0318] Antenna port

[0319] PTRS-DMRS association

[0320] DMRS sequence initialization

[0321] In addition to the DCI field whose field size is determined based on CP-OFDM, the size of each DCI field may be determined based on a transmission waveform determined by dynamic switching of the transmission waveform.

[0322] (Variation Example)

[0323] The DCI format of the above-mentioned embodiment is not limited to DCI format 0-1 or DCI format 0-2, and can also be applied to other DCI formats.

[0324] For example, the above-mentioned embodiment can be applied to the DCI format used after the dedicated RRC parameter is set, in addition to the DCI format used for initial access. In addition, the present embodiment can be applied to the DCI format capable of notifying a transmission rank greater than Rank 1. In addition, it can also be applied to the DCI format set in the RRC inherent to the terminal.

[0325] The above embodiment is not limited to DG-PUSCH, but can also be applied to PUSCH (Type-2 CG-PUSCH) that transmits PUSCH in semi-fixed resource allocation using activation DCI. In this case, the above transmission waveform can be notified based on the field included in the activation DCI.

[0326] In the above implementation, the DFT-s-OFDM transmission waveform only supports transmission of layer number 1, and the CP-OFDM transmission waveform supports transmission of layers number 2 or more, 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 can support more than 2 layers. In this case, the number of layers of the switching transmission waveform can be replaced from 1 to N, and the DFT-s-OFDM transmission waveform supports transmission of layers number N or less, and the CP-OFDM transmission waveform supports transmission of layers number N+1 or more.

[0327] (flow chart)

[0328] Fig.28 It is a flow chart of the present invention.

[0329] According to the first embodiment, in step 3, the terminal determines the transmission waveform based only on the transmission layer.

[0330] According to the second embodiment, in step 3, the terminal determines the transmission waveform based on the transmission layer and TPMI.

[0331] According to Embodiment 3, in step 3, the terminal determines a transmission waveform based on TDRA.

[0332] According to Embodiment 4, in step 3, the terminal determines a transmission waveform based on the MCS index.

[0333] 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. Fig.37 2 is a block diagram showing a configuration example of a part of the terminal 200 according to an embodiment of the present disclosure.

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

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

[0336] (Structure of base station)

[0337] Fig.29 It is a block diagram showing the structure of the base station 100 according to the embodiment of the present invention.

[0338] also, Fig.29 At least one of the control unit 101, the high-layer control signal generating unit 102, the downlink control information generating unit 103, the encoding unit 104, the modulation unit 105, the signal distribution unit 106, the extraction unit 109, the demodulation unit 110 and the decoding unit 111 shown in the figure may also be included in Fig.36 In addition, Fig.29 The sending unit 107 shown may also be included in Fig.36 The sending part is shown.

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

[0340] The control unit 101 determines the coding / modulation scheme and radio resource allocation for downlink signals for transmitting the higher layer control signal and downlink control information, and outputs the determined information to the coding unit 104, the modulation unit 105, and the signal allocation unit 106. In addition, the control unit 101 outputs the coding / modulation scheme and radio resource allocation information for the data signal or the higher layer control signal to the downlink control information generation unit 103.

[0341] The higher layer control signal generation unit 102 generates a higher layer control signal bit sequence using the control information input from the control unit 101 , and outputs the bit sequence to the coding unit 104 .

[0342] The downlink control information generating section 103 generates a DCI bit sequence using the control information input from the control section 101, and outputs the generated DCI bit sequence to the coding section 104. In addition, the control information may be transmitted to a plurality of terminals.

[0343] The coding unit 104 codes the bit sequence obtained from the higher layer control signal generating unit 102 or the DCI bit sequence input from the downlink control information generating unit 103 , and outputs the coded bit sequence to the modulation unit 105 .

[0344] The modulation unit 105 modulates the coded bit sequence received from the coding unit 104 , and outputs the modulated bit sequence to the signal distribution unit 106 .

[0345] 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 resource instructed by the control unit 101. In addition, the signal allocation unit 106 inputs the mapped signal to the transmission unit 107.

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

[0347] The transmission unit 107 performs radio frequency (RF) processing such as digital to analog (D / A) conversion and up-conversion, and transmits a wireless signal to the terminal 200 via the antenna.

[0348] The receiving unit 108 performs RF processing such as down-conversion or analog-to-digital (A / D) conversion on the uplink transmission sent from the terminal 200 and received via the antenna. In addition, in the case of OFDM transmission, the receiving unit 108 applies FFT (Fast Fourier Transform) to the received signal, obtains a frequency domain signal, and outputs it to the extraction unit 109.

[0349] The extraction unit 109 extracts the radio resource portion in which the PUSCH is transmitted from the received signal based on the information acquired from the control unit 101 , and outputs the extracted radio resource portion to the demodulation unit 110 .

[0350] The demodulation unit 110 demodulates the PUSCH based on the information acquired from the control unit 101 , and outputs the demodulation result to the decoding unit 111 .

[0351] The decoding unit 111 performs error correction decoding of the PUSCH using the information obtained from the control unit 101 and the demodulation result obtained from the demodulation unit, and obtains a decoded received bit sequence.

[0352] (Terminal structure)

[0353] Fig.30 It is a block diagram showing the structure of the terminal 200 according to the embodiment of the present invention.

[0354] also, Fig.30 At least one of the extraction unit 202, the demodulation unit 203, the decoding unit 204, the control unit 205, the encoding unit 206, the modulation unit 207, and the signal distribution unit 208 shown in the figure may also be included in Fig.37 In addition, Fig.30 The receiving unit 201 shown may also be included in Fig.37 The receiving part shown.

[0355] The receiving unit 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 wireless received signal to obtain a baseband signal. In addition, when receiving an OFDM signal, the receiving unit 201 performs FFT processing on the received signal to convert the received signal into the frequency domain.

[0356] The extraction unit 202 extracts the radio resource portion including the downlink control signal from the reception signal acquired from the reception unit 201 using the information on the radio resource of the control signal input from the control unit 205, and outputs it to the demodulation unit 203. In addition, the extraction unit 202 extracts the radio resource portion including the data signal using the information on the radio resource of the data signal input from the control unit 205, and outputs it to the demodulation unit 203.

[0357] The demodulation unit 203 demodulates the PDCCH or PDSCH (Physical Downlink Shared Channel) based on the information acquired from the control unit 205 , and outputs the demodulation result to the decoding unit 204 .

[0358] 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 high-layer control information or downlink control information. The decoding unit 204 outputs the obtained high-layer control information and downlink control information to the control unit 205. In addition, the decoding unit 204 can generate an ACK (acknowledgement) / NACK (negative ACK) signal based on the decoding result of the PDSCH.

[0359] The control unit 205 determines the transmission waveform and the like for PUSCH transmission according to the above-mentioned method from the information related to PUSCH transmission obtained from the upper layer control signal and the downlink control information, and controls the coding unit 206, the modulation unit 207, and the signal allocation unit 208. In addition, the control unit 205 outputs the determined information to the extraction unit 202, the demodulation unit 203, and the decoding unit 204.

[0360] The coding unit 206 codes the uplink data signal or the uplink control signal based on the information input from the control unit 205 , and outputs the coded bit sequence to the modulation unit 207 .

[0361] The modulation unit 207 modulates the encoded bit sequence received from the encoding unit 206 based on the information input from the control unit 205 , generates a modulation symbol sequence, and outputs it to the signal distribution unit 208 .

[0362] The signal allocation unit 208 maps the signal input from the modulation unit 207 to the radio resource instructed by the control unit 205. In addition, the signal allocation unit 208 outputs the mapped signal to the transmission unit 209.

[0363] The transmission unit 209 generates a transmission waveform such as OFDM for the signal input from the signal distribution unit 208. In the case of OFDM transmission or DFT-s-OFDM transmission using CP, CP is added after IFFT. In addition, when generating a DFT-s-OFDM transmission waveform, a DFT unit may be added in the latter stage of the modulation unit or in the former stage of the signal distribution unit. In addition, the transmission unit 209 performs RF processing such as D / A conversion and up-conversion on the transmission signal. In addition, the transmission unit 209 transmits a wireless signal to the base station 100 via an antenna.

[0364] In addition, although PUSCH transmission is described as uplink transmission in each of the above embodiments, the channel used for uplink transmission is not limited to PUSCH, and may be other channels. In addition, the type of information transmitted is not limited to data, and may be other types of information (e.g., uplink control signal). In addition, an embodiment of the present disclosure is not limited to uplink transmission, and may also be applied to downlink transmission or sidelink transmission.

[0365] In addition, in each of the above-mentioned embodiments, the transmission waveform is not limited to CP-OFDM and DFT-s-OFDM, and may be a waveform of multi-carrier transmission or other transmission waveform of single-carrier transmission.

[0366] In addition, the parameters such as the number of transmission layers, the transmission precoding matrix (TPMI), the number of time slots, the number of symbols, the symbol position, the value of K2, the number of repetitions, etc. illustrated in the present disclosure are examples and may also be other values. Figure 2 to Figure 27 The table shown is an example, and the values ​​associated with the table may be other values. In addition, the types of parameters associated with the table are not limited to these.

[0367] The present disclosure can also be applied to, for example, inter-terminal communication such as sidelink communication.

[0368] In addition, 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 (Physical Uplink Contorl Channel) and PUSCH, respectively, and may also be control channels and data channels with other names.

[0369] In addition, although RRC signaling is assumed as high-layer signaling in the present disclosure, it may be replaced by MAC (Medium Access Control) signaling and notification by physical layer signaling, namely, DCI.

[0370] (Replenish)

[0371] The information indicating whether the terminal 200 supports the functions, actions or processes shown in the above-mentioned embodiments, modifications and supplements may be sent (or notified) by the terminal 200 to the base station 100 as capability information or capability parameters of the terminal 200, for example.

[0372] The capability information may also include the following information element (IE: Information Element), which alone indicates whether the terminal 200 supports at least one of the functions, actions, and processes shown in the above-mentioned embodiments, variations, and supplements. Alternatively, the capability information may also include the following information element, which indicates whether the terminal 200 supports a combination of two or more of the functions, actions, and processes shown in the above-mentioned embodiments, variations, and supplements.

[0373] The base station 100 may, for example, determine (or determine or assume) a function, action or process supported (or not supported) by the terminal 200 that sends the capability information based on the capability information received from the terminal 200. The base station 100 may implement an action, process or control corresponding to the result of the determination 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.

[0374] It should be noted that the terminal 200 does not support a part of the functions, actions or processes shown in the above-mentioned embodiments, modifications and supplements, which may also be replaced by limiting such a part of the functions, actions or processes in the terminal 200. For example, information or requests related to such limitations may also be notified to the base station 100.

[0375] The information related to the capability or limitation of the terminal 200 may be defined in the standard, for example, or may be implicitly notified to the base station 100 by being associated with information known to the base station 100 or information transmitted to the base station 100 .

[0376] In the above, various embodiments, various modifications, and supplements of a non-limiting example of the present disclosure have been described.

[0377] (Control signal)

[0378] In the present disclosure, the downlink control signal (information) associated with the present disclosure may be a signal (information) sent in the PDCCH of the physical layer, or a signal (information) sent in the MAC (Medium Access Control) CE (Control Element) or RRC of the higher layer. In addition, a predetermined signal (information) may be used as a downlink control signal.

[0379] The uplink control signal (information) associated with the present disclosure may be a signal (information) sent in the PUCCH of the physical layer, or a signal (information) sent in the MAC CE or RRC of the higher layer. In addition, the uplink control signal may also be a predetermined signal (information). In addition, the uplink control signal may also be changed to UCI (uplink control information), 1st stage SCI (sidelink control information), and 2nd stage SCI.

[0380] (Base Station)

[0381] In the present disclosure, a base station may also 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 mother machine, a gateway, etc. In addition, in sidelink communication, a base station may also be changed to a terminal. A base station may also be a relay device that relays communication between a high-level node and a terminal. In addition, a base station may also be a roadside device.

[0382] (Uplink / Downlink / Sidelink)

[0383] The present disclosure may also be applied to any link in the uplink, downlink, and sidelink. For example, the present disclosure may also be applied to PUSCH, PUCCH, PRACH (Physical Random Access Channel) of the uplink, PDSCH, PDCCH, PBCH (Physical Broadcast Channel) of the downlink, PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), and PSBCH (Physical Sidelink Broadcast Channel) of the sidelink.

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

[0385] (Data Channel / Control Channel)

[0386] The present disclosure may also be applied to any channel in the data channel and the control channel. For example, the channel of the present disclosure may also be replaced by PDSCH, PUSCH, PSSCH of the data channel, PDCCH, PUCCH, PBCH, PSCCH, PSBCH of the control channel.

[0387] (Reference signal)

[0388] In the present disclosure, a reference signal is a signal known to both the base station and the terminal, and is sometimes referred to as an "RS (Reference Signal)" or a "pilot signal". A reference signal may also be one of the following reference signals: DMRS (Demodulation Reference Signal), 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).

[0389] (Time interval)

[0390] In the present disclosure, the unit of time resources is not limited to one of a time slot and a symbol or a combination thereof, and may be, for example, a frame, a superframe, a subframe, a time slot, a sub-time slot, a micro-time slot, or a symbol, an OFDM (orthogonal frequency division multiplexing) symbol, an SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbol, or other time resource units. In addition, the number of symbols contained in one time slot is not limited to the number of symbols exemplified in the above-mentioned embodiment, and may be other numbers of symbols.

[0391] (frequency band)

[0392] The present disclosure may also be applied to any of the licensed and unlicensed bands.

[0393] (communication)

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

[0395] In addition, the present disclosure can also be applied to any network in a terrestrial network, a network other than the terrestrial network (NTN: Non-Terrestrial Network) using satellites or high altitude pseudo satellites (HAPS: High Altitude Pseudo Satellite). In addition, the present disclosure can also be applied to a terrestrial network such as a network with a large cell size and an ultra-wideband transmission network where the transmission delay is greater than the symbol length or the time slot length.

[0396] (Antenna port)

[0397] An antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. That is, an antenna port does not necessarily refer to a physical antenna, but sometimes refers to an array antenna composed of multiple antennas. For example, it is not specified that an antenna port is composed of several physical antennas, but is specified as the minimum unit that a terminal can send a reference signal. In addition, an antenna port is sometimes also specified as the minimum unit multiplied by the weight of a precoding vector.

[0398] <5G NR system architecture and protocol stack>

[0399] 3GPP is continuing work to implement the next version of fifth generation mobile technology (also referred to simply as "5G"), including 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 in late 2017, which enabled the transition to trial production of terminals (e.g., smartphones) compliant with the 5G NR standard and commercial deployment.

[0400] For example, the system architecture as a whole envisions a NG-RAN (Next Generation Radio Access Network) including gNBs. The gNB provides the UE-side termination of the protocols of the user plane (SDAP (Service Data Adaptation Protocol) / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY (Physical Layer)) and control plane (RRC) of the NG radio access. The gNBs are connected to each other through an Xn interface. In addition, the gNB is connected to the NGC (Next Generation Core) through a Next Generation (NG) interface, more specifically, to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that executes the AMF) through an NG-C interface, and in addition, to the UPF (User Plane Function) (e.g., a specific core entity that executes the UPF) through an NG-U interface. Fig.31 Represents the NG-RAN architecture (for example, refer to 3GPP TS 38.300v15.6.0, section 4).

[0401] The protocol stack of the user plane of NR (e.g., refer to 3GPP TS 38.300, Section 4.4.1) includes the PDCP (Packet Data Convergence Protocol (see Section 6.4 of TS 38.300)) sublayer, the RLC (Radio Link Control (see Section 6.3 of TS 38.300)) sublayer and the MAC (Media Access Control (see Section 6.2 of TS 38.300)) sublayer terminated on the network side in the gNB. In addition, a sublayer (SDAP: Service Data Adaptation Protocol) of the new access stratum (AS: Access Stratum) has been introduced on PDCP (e.g., refer to Section 6.5 of 3GPP TS 38.300). In addition, a protocol stack of the control plane is defined for NR (e.g., refer to TS 38.300, Section 4.4.2). An overview of the functions of Layer 2 is described in Section 6 of TS 38.300. The functions of the PDCP sublayer, RLC sublayer and MAC sublayer are listed in Sections 6.4, 6.3 and 6.2 of TS 38.300 respectively. The functions of the RRC layer are listed in Section 7 of TS 38.300.

[0402] For example, the media access control layer handles multiplexing of logical channels, and scheduling including processing of various parameter sets and various functions associated with the scheduling.

[0403] For example, the physical layer (PHY) is responsible for coding, PHY HARQ (Physical Layer Hybrid Automatic Repeat Request) processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. In addition, the physical layer handles the 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 to send a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, in the physical channel, the uplink physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), PUCCH (Physical Uplink Control Channel), and the downlink physical channels include PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel).

[0404] The use cases / extended scenarios of NR may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communications (mMTC), which have various 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 that are about three times the data rates provided by IMT-Advanced (International Mobile Telecommunications-Advanced). On the other hand, in the case of URLLC, more stringent requirements are proposed for ultra-low latency (the latency of the user plane is 0.5 ms in UL and DL respectively) and high reliability (within 1 ms, 1-10-5). Finally, in mMTC, preferably high connection density (1,000,000 devices / km2 in urban environments), large coverage in harsh environments, and extremely long battery life (15 years) for cheap devices are required.

[0405] Therefore, sometimes the parameter set of OFDM that is suitable for one use case (for example, subcarrier spacing (SCS: SubCarrier Spacing), OFDM codeword length, cyclic prefix (CP: Cyclic Prefix) length, number of codewords per scheduling interval) is invalid for other use cases. For example, in low-latency services, it is preferred that the codeword length is shorter than that of mMTC services (therefore, the subcarrier spacing is larger) and / or the number of codewords per scheduling interval (also called "TTI (Transmission Time Interval)") is small. Moreover, in extended scenarios where the delay spread of the channel is large, it is preferred that the CP length is longer than that of scenarios where the delay spread is short. The subcarrier spacing can also be optimized according to the situation to maintain the same CP overhead. The value of the subcarrier spacing supported by NR can be more than one. Correspondingly, subcarrier spacings of 15kHz, 30kHz, 60kHz... are currently considered. The codeword length Tu and the subcarrier spacing Δf are directly related according to the formula Δf=1 / Tu. Similar to the LTE system, the term “resource element” can be used to represent the minimum resource unit composed of one subcarrier with a length of one OFDM / SC-FDMA (Single-Carrier Frequency Division Multiple Access) symbol.

[0406] In the new wireless system 5G-NR, for each parameter set and each carrier, a resource grid of subcarriers and OFDM symbols is defined in the uplink and downlink. Each element of the resource grid is called a "resource element", which is determined based on the frequency index in the frequency domain and the symbol position in the time domain (refer to 3GPP TS 38.211v15.6.0).

[0407] <Functional separation between NG-RAN and 5GC in 5G NR>

[0408] Fig.32 Indicates 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 (Session Management Function).

[0409] For example, gNB and ng-eNB host the following main functions:

[0410] - Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and Radio Resource Management functions such as dynamically allocating (scheduling) resources to UEs in both uplink and downlink;

[0411] -IP (Internet Protocol) header compression, encryption and integrity protection of data;

[0412] - Selection of the AMF when attaching the UE in case the routing towards the AMF cannot be decided based on the information provided by the UE;

[0413] - Routing of user plane data towards UPF;

[0414] - Routing of control plane information towards the AMF;

[0415] -Set up and disconnect connections;

[0416] - Scheduling and sending of paging messages;

[0417] - Scheduling and sending of system broadcast information (AMF or operation, admission, maintenance function (OAM) as the originator);

[0418] - Settings for measurements and measurement reports for mobility and scheduling;

[0419] - Packet marking of the transmission class in uplink;

[0420] -Session management;

[0421] - Network slicing support;

[0422] - Management of QoS (Quality of Service) flows and mapping to data radio bearers;

[0423] - Support of UE in RRC_INACTIVE state;

[0424] -NAS (Non Access Stratum) message distribution function;

[0425] -Sharing of wireless access networks;

[0426] -Dual connection;

[0427] -Close collaboration between NR and E-UTRA (Evolved Universal Terrestrial Radio Access).

[0428] The access and mobility management function (AMF) hosts the following main functions:

[0429] - Functionality to terminate non-access stratum (NAS) signaling;

[0430] -Security of NAS signaling;

[0431] - Security control of the access layer (AS);

[0432] -Core Network (CN) inter-node signaling for mobility between 3GPP access networks;

[0433] - the possibility of reaching the UE in idle mode (including the control and execution of paging retransmission);

[0434] - Management of the registration area;

[0435] -Support for intra-system and inter-system mobility;

[0436] -Access authentication;

[0437] - Access permission including roaming permission check;

[0438] -Mobility management control (subscription and policy);

[0439] - Network slicing support;

[0440] - Selection of Session Management Function (SMF).

[0441] In addition, the User Plane Function (UPF) hosts the following main functions:

[0442] - Anchor point for intra-RAT (Radio Access Technology) mobility / inter-RAT (Inter-RAT) mobility (where applicable);

[0443] - External PDU (Protocol Data Unit) session point for interconnection with data networks;

[0444] -Packet routing and forwarding;

[0445] -Policy rule enforcement for packet inspection and user plane;

[0446] - Business usage reporting;

[0447] - Uplink classifier for supporting routing of traffic towards data networks;

[0448] -BranchingPoint used to support multi-homed PDU session;

[0449] - QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement);

[0450] - Verification of uplink services (mapping of SDF (Service Data Flow) to QoS flows);

[0451] - Downlink packet buffering and downlink data notification triggering function.

[0452] Finally, the Session Management Function (SMF) hosts the following main functions:

[0453] -Session management;

[0454] -Allocation and management of UE IP addresses;

[0455] - UPF selection and control;

[0456] - Traffic steering configuration function in the user plane function (UPF) for directing traffic to the appropriate destination;

[0457] - Enforcement of policies and QoS in the control part;

[0458] -Notification of downlink data.

[0459] <RRC connection setup and re-setup process>

[0460] Fig.33 Represents several interactions between the UE, gNB and AMF (5GC entity) when the NAS part of the UE transitions from RRC_IDLE (RRC Idle) to RRC_CONNECTED (RRC Connected) (refer to TS 38.300v15.6.0).

[0461] RRC is a high-layer signaling (protocol) used for the configuration of UE and gNB. Through this transition, AMF prepares UE context data (which includes, for example, PDU session context, security keys, UE radio capabilities (UE Radio Capability), UE security capabilities (UE Security Capabilities), etc.), and sends it to gNB together with the initial context setup request (INITIAL CONTEXTSETUP REQUEST). Next, the gNB activates AS security together with the UE. The gNB sends a Security Mode Command (SecurityModeCommand) message to the UE, and the UE responds to the gNB with a Security Mode Complete (SecurityModeComplete) message to activate AS security. Then, the gNB sends an RRC Reconfiguration (RRCReconfiguration) message to the UE, and the gNB receives an RRC Reconfiguration Complete (RRCReconfigurationComplete) from the UE for the RRC Reconfiguration message, thereby reconfiguring the Signaling Radio Bearer 2 (SRB2) and the Data Radio Bearer (DRB). For signaling-only connections, since SRB2 and DRB are not configured, the steps related to RRC reconfiguration can be omitted. Finally, the gNB notifies the AMF of the completion of the setup process using the INITIAL CONTEXT SETUP RESPONSE.

[0462] Therefore, the present disclosure provides the following fifth generation core network (5GC) entity (e.g., AMF, SMF, etc.), which includes: a control circuit, which, when in action, establishes a next generation (Next Generation, NG) connection with a gNodeB (gNodeB); and a sending unit, which, when in action, sends an initial context setting message to the gNodeB via the NG connection to set a signaling radio bearer between the gNodeB and the user equipment (UE: User Equipment). Specifically, the gNodeB sends a radio resource control (RRC) signaling containing a resource allocation setting information element (IE: Information Element) to the UE via the signaling radio bearer. Then, the UE sends in the uplink or receives in the downlink based on the resource allocation setting.

[0463] <Application scenarios of IMT after 2020>

[0464] Fig.34Indicates several use cases for 5G NR. In the 3rd generation partnership project new radio (3GPP NR), three use cases supporting a wide range of services and applications conceived through IMT-2020 have been studied. The planning and development of the first phase of specifications for large-capacity high-speed communications (eMBB: enhanced mobile broadband) has been completed. In current and future work, in addition to gradually expanding support for eMBB, it also includes standardization for ultra-reliable and low-latency communications (URLLC: ultra-reliable and low-latency communications) and multiple simultaneous machine-type communications (mMTC: massive machine-type communications). Fig.34 Several examples of the conceptual use scenarios of IMT after 2020 are shown (for example, see ITU-R M.2083 Figure 2 ).

[0465] The use cases of URLLC have strict requirements related to performance such as throughput, latency (delay) and availability. The use cases of URLLC are conceived as an element technology for realizing future applications such as wireless control of industrial production processes or manufacturing processes, remote medical surgery, automation of power transmission and distribution in smart grids, and traffic safety. The ultra-high reliability of URLLC is supported by determining technologies that meet the requirements set by TR38.913. In version 15 of NR URLLC, as an important requirement, the target user plane latency is 0.5ms in UL (uplink) and 0.5ms in DL (downlink). The overall URLLC requirement for a packet transmission is that the block error rate (BLER) is 1E-5 for a packet size of 32 bytes when the user plane latency is 1ms.

[0466] Considering the physical layer, a number of possible approaches can be used to improve reliability. Current scope for improving reliability includes defining additional CQI (Channel Quality Indicator) tables for URLLC, more compact DCI formats, repetition of PDCCH, etc. However, as NR (an important prerequisite for NR URLLC) becomes more stable and further developed, the scope can be expanded to achieve ultra-high reliability. Specific use cases for NR URLLC in Release 15 include Augmented Reality / Virtual Reality (AR / VR), e-Health, e-Safety and critical applications.

[0467] In addition, the technical enhancements of the NR URLLC target are aimed at improving latency and increasing reliability. Technical enhancements for improving latency include configurable parameter sets, non-slot-based scheduling with flexible mapping, unauthorized (configured authorized) uplink, slot-level repetition in the data channel, and preemption in the downlink. Preemption means stopping the transmission of allocated resources and using the allocated resources for other transmissions that are requested later and meet the necessary conditions of lower latency / higher priority. Therefore, the allowed transmission will be replaced by the subsequent transmission. Preemption can be applied regardless of the specific service type. For example, the transmission of service type A (URLLC) can also be replaced by the transmission of service type B (eMBB, etc.). Technical enhancements related to reliability improvement include dedicated CQI / MCS tables for target BLER of 1E-5.

[0468] The use case of mMTC (Massive Machine Type Communications) is characterized by the fact that typically there are a very large number of connected devices that send relatively small amounts of data that are not susceptible to latency. The devices are required to be low-priced and have very long battery life. From the NR point of view, utilizing very narrow bandwidth portions is one solution that can save power in the UE and extend its battery life.

[0469] As mentioned above, it is predicted that the room for reliability improvement in NR will be further expanded. It is one of the important requirements for all situations. For example, the important requirement related to URLLC and mMTC is high reliability or ultra-high reliability. From the wireless point of view and the network point of view, reliability can be improved in several mechanisms. In general, there are two to three important areas that may help improve reliability. These areas include compact control channel information, repetition of data channels / control channels, and diversity related to frequency domain, time domain and / or space domain. These areas can be used universally to improve reliability regardless of the specific communication scenario.

[0470] For NR URLLC, further use cases with stricter requirements are envisioned, such as factory automation, transportation, and power transmission. The strict requirements are high reliability (up to 10-6 reliability), high availability, packet size up to 256 bytes, time synchronization up to a few microseconds (μs) (the value can be set to 1μs or a few microseconds depending on the frequency range and short latency of around 0.5ms to 1ms (for example, 0.5ms latency in the user plane is set as the target) for the use case.

[0471] Moreover, regarding NR URLLC, from the perspective of the physical layer, there may be several technical enhancements. These technical enhancements include the enhancement of PDCCH (Physical Downlink Control Channel) related to compact DCI, repetition of PDCCH, and increased monitoring of PDCCH. In addition, the enhancement of UCI (Uplink Control Information) is related to the enhancement of enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. In addition, there may be enhancement of PUSCH related to frequency hopping at the mini-slot level and enhancement of retransmission / repetition. The term "mini-slot" refers to a transmission time interval (TTI) that contains fewer symbols than a slot (a slot has 14 symbols).

[0472] <QoS Control>

[0473] The 5G QoS (Quality of Service) model is based on QoS flows, supporting both QoS flows that require guaranteed bit rate (GBR: Guaranteed Bit Rate QoS flows) and QoS flows that do not require guaranteed bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows are the most fine-grained QoS divisions in a PDU session. QoS flows are determined within a PDU session based on the QoS flow ID (QFI: QoS Flow ID) transmitted by the encapsulation header via the NG-U interface.

[0474] For each UE, 5GC establishes one or more PDU sessions. For each UE, in conjunction with the PDU session, NG-RAN, for example, as described in the previous reference Fig.33 As described above, at least one data radio bearer (DRB) is established. In addition, the DRB added to the QoS flow of the PDU session can also be set later (when to set it depends on NG-RAN). NG-RAN maps packets belonging to various PDU sessions to various DRBs. NAS-level packet filters in UE and 5GC are used to associate UL packets and DL packets with QoS flows, and AS-level mapping rules in UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0475] Fig.35 Represents the non-roaming reference architecture of 5G NR (see TS23.501v16.1.0, section 4.23). Application Function (AF) (e.g., host Fig.34The 3GPP core network (an external application server for the 5G service illustrated) interacts with the 3GPP core network to provide services. For example, accessing the Network Exposure Function (NEF) to support applications that affect the routing of services, or interacting with the policy framework (refer to the Policy Control Function (PCF)) for policy control (for example, QoS control). Based on the operator's deployment, the operator considers that trusted application functions can interact directly with the associated network function (Network Function). Application functions that are not allowed by the operator to directly access network functions interact with associated network functions via NEF using an open framework to the outside.

[0476] Fig.35 It also represents 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: Data Network, such as services provided by operators, Internet access or services provided by third parties). All or part of the core network functions and application services can also be deployed and operated in a cloud computing environment.

[0477] Therefore, the present disclosure provides the following application server (for example, AF of 5G architecture), which includes: a sending unit, which, in action, sends a request for QoS requirements for at least one of URLLC service, eMMB service and mMTC service to at least one of the functions of 5GC (for example, NEF, AMF, SMF, PCF, UPF, etc.) in order to establish a PDU session of a wireless bearer between a g-node B and a UE corresponding to the QoS requirements; and a control circuit, which, in action, uses the established PDU session to provide service.

[0478] The expression "...part" used in the present disclosure may also be replaced with other expressions such as "...circuitry", "...device", "...unit" or "...module".

[0479] The present disclosure can be implemented by software, hardware or software in cooperation with hardware. Each functional block used in the description of the above-mentioned embodiments is partially or entirely implemented as an LSI (Large Scale Integration) as an integrated circuit, and each process described in the above-mentioned embodiments may also be partially or entirely controlled by an LSI or a combination of LSIs. LSI may be composed of individual chips, or may be composed of one chip in a manner that includes part or all of the functional blocks. LSI may also include input and output of data. LSI may also be referred to as "IC (Integrated Circuit)", "System LSI", "Super LSI", "Ultra LSI" depending on the degree of integration.

[0480] The method of integrated circuitization is not limited to LSI, and can also be implemented by a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connection or setting of the circuit block inside the LSI can also be used. The present disclosure can also be implemented as digital processing or analog processing.

[0481] Furthermore, if integrated circuit technology that replaces LSI emerges as semiconductor technology advances or other technologies are derived, it is of course possible to use this technology to achieve integration of functional blocks. There is also the possibility of applying biotechnology, etc.

[0482] The present disclosure can be implemented in all kinds of devices, equipment, and systems (collectively referred to as "communication devices") with communication functions. The communication device may also include a wireless transceiver and a processing / control circuit. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these parts. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or a device similar to these. Non-limiting examples of communication devices include: phones (mobile phones, smart phones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebook computers, etc.), cameras (digital cameras, digital video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smart watches, tracking devices, etc.), game consoles, e-book readers, telehealth / telemedicine (telehealth / medical prescription) equipment, vehicles or transportation vehicles with communication functions (cars, airplanes, ships, etc.), and combinations of the above-mentioned various devices.

[0483] Communication devices are not limited to portable or mobile devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed. For example, they include: smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.

[0484] The communication includes data communication performed by a cellular system, a wireless LAN (Local Area Network) system, a communication satellite system, etc., and also includes data communication performed by a combination of these systems.

[0485] In addition, the communication device also includes devices such as controllers or sensors connected or linked to the communication device that performs the communication function described in the present invention. For example, it includes a controller or sensor that generates a control signal or data signal used by the communication device that performs the communication function of the communication device.

[0486] In addition, the communication device includes infrastructure equipment that communicates with the above-mentioned non-limiting various devices or controls the above-mentioned various devices, such as base stations, access points, and all other devices, equipment, and systems.

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

[0488] (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.

[0489] (3) In one embodiment of the present disclosure, the terminal of (2) determines the transmission waveform of the uplink signal based on the precoding information contained in the control information and the number of transmission layers notified by the layer number field or the SRI field.

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

[0491] (5) In one embodiment of the present disclosure, the terminal of (2) determines the transmission waveform of the uplink signal based on the index notified by the time domain resource allocation (TDRA) field or the frequency domain resource allocation (FDRA) field contained in the control information.

[0492] (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.

[0493] (7) In one embodiment of the present disclosure, when the index in (6) is the index that determines the modulation order and the target coding rate, 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 the index that only determines the modulation order, the transmission waveform of the uplink signal is determined based on the correspondence between the index and the transmission waveform of the uplink signal other than the index.

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

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

[0496] (10) In one embodiment of the present disclosure, the correspondence between the value representing the transmit precoding matrix of the terminal of (9) and the transmit waveform of the uplink signal is set by higher layer signaling.

[0497] (11) In one embodiment of the present disclosure, the terminal of (5) determines, based on the index, a time domain allocation resource candidate corresponding to the index.

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

[0499] (13) In one embodiment of the present disclosure, the correspondence between the value of the index of the terminal in (6) and the transmission waveform of the uplink signal is set by high-layer signaling.

[0500] (14) In one embodiment of the present disclosure, the terminal of (13) receives information related to a threshold value of the index used to switch the transmission waveform of the uplink signal.

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

[0502] (16) In a communication method of an embodiment of the present disclosure, a terminal performs the following processing: when a dynamic switching between a first transmission waveform and a second transmission waveform of an uplink signal is set, a field size of control information is determined based on a field size when the second transmission waveform is set, and the data size of the second transmission waveform is larger than the data size of the first transmission waveform; and the control information is received based on the field size.

[0503] (17) In a communication method of an embodiment of the present disclosure, a base station performs the following processing: when a dynamic switching between a first transmission waveform and a second transmission waveform of an uplink signal is set, a field size of control information is determined based on a field size when the second transmission waveform is set, and the data size of the second transmission waveform is larger than the data size of the first transmission waveform; and the control information is transmitted based on the field size.

[0504] The disclosure contents 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.

[0505] Industrial Applicability

[0506] One embodiment of the present disclosure is useful for a wireless communication system.

[0507] Description of Reference Numerals

[0508] 100 Base Stations

[0509] 101, 205 Control Department

[0510] 102 High-level control signal generation unit

[0511] 103 Downlink control information generation unit

[0512] 104, 206 Coding Department

[0513] 105, 207 Modulation Department

[0514] 106, 208 Signal Distribution Department

[0515] 107, 209 Sending Department

[0516] 108, 201 Receiving Department

[0517] 109, 202 Extraction Department

[0518] 110, 203 Demodulation Unit

[0519] 111, 204 Decoding Department

[0520] 200 Terminal

Claims

1. A terminal, characterized in that: include: a control circuit that, in a case where dynamic switching between a first transmission waveform and a second transmission waveform of an uplink signal is set, determines a field size of the control information based on a field size when the second transmission waveform is set, the data size of the second transmission waveform being larger than the data size of the first transmission waveform; as well as The receiving circuit receives the control information based on the field size.

2. The terminal according to claim 1, wherein: The control circuit determines a transmission waveform of the uplink signal based on a value notified by a field included in the control information.

3. The terminal according to claim 2, wherein: The control circuit determines a transmission waveform of the uplink signal based on the precoding information included in the control information and the number of transmission layers notified by a layer number field or a scheduling request indicator field (SRI) field.

4. The terminal according to claim 2, wherein: The control circuit determines a transmission waveform of the uplink signal based on the precoding information included in the control information and the number of transmission layers and the transmission precoding matrix notified by the layer number field or the SRI field.

5. The terminal according to claim 2, wherein: The control circuit determines a transmission waveform of the uplink signal based on an index notified by a TDRA field, which is a time domain resource allocation field, or a FDRA field, which is a frequency domain resource allocation field, included in the control information.

6. The terminal according to claim 2, wherein: The control circuit determines a transmission waveform of the uplink signal based on an index notified by an MCS field, which is a modulation and coding scheme field included in the control information.

7. The terminal according to claim 6, wherein: The control circuit determines the transmission waveform of the uplink signal based on the correspondence between the index and the transmission waveform of the uplink signal when the index is the index that determines the modulation order and the target coding rate, and based on the correspondence between the transmission waveform of the uplink signal other than the index when the index is the index that only determines the modulation order.

8. The terminal according to claim 3, wherein: The control circuit determines the transmission waveform of the uplink signal to be a waveform of single-carrier transmission when the number of transmission layers is 1, and determines the transmission waveform of the uplink signal to be a waveform of multi-carrier transmission when the number of transmission layers is 2 or more.

9. The terminal according to claim 4, wherein: The control circuit determines the transmission waveform of the uplink signal based on the 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 waveform of multi-carrier transmission when the number of transmission layers is 2 or more.

10. The terminal according to claim 9, wherein: The correspondence between the value representing the transmit precoding matrix and the transmit waveform of the uplink signal is set by higher layer signaling.

11. The terminal according to claim 5, wherein: The control circuit determines, based on the index, a time domain allocation resource candidate associated with the index.

12. The terminal according to claim 11, wherein: The correspondence between the index value and the transmission waveform of the uplink signal is set by higher layer signaling.

13. The terminal according to claim 6, wherein: The correspondence between the index value and the transmission waveform of the uplink signal is set by higher layer signaling.

14. The terminal according to claim 13, wherein: The receiving circuit receives information related to a threshold value of the index used to switch a transmission waveform of the uplink signal.

15. A base station, characterized in that: include: a control circuit that, in a case where dynamic switching between a first transmission waveform and a second transmission waveform of an uplink signal is set, determines a field size of the control information based on a field size when the second transmission waveform is set, the data size of the second transmission waveform being larger than the data size of the first transmission waveform; as well as The sending circuit sends the control information based on the field size.

16. A communication method, characterized in that: The terminal performs the following processing: In a case where dynamic switching of a first transmission waveform and a second transmission waveform of an uplink signal is set, determining a field size of control information based on a field size when the second transmission waveform is set, the data size of the second transmission waveform being larger than the data size of the first transmission waveform; and The control information is received based on the field size.

17. A communication method, characterized in that: The base station performs the following processing: In a case where dynamic switching of a first transmission waveform and a second transmission waveform of an uplink signal is set, determining a field size of the control information based on a field size when the second transmission waveform is set, the data size of the second transmission waveform being larger than the data size of the first transmission waveform; as well as The control information is sent based on the field size.

Images