Communication equipment, base stations, communication methods, and integrated circuits

Abstract

This terminal is provided with: a control circuit which, if a transmission resource allocated to transmission of an uplink shared channel employing a plurality of slots and a transmission resource of an uplink control channel overlap in the time domain, determines a second resource amount to be used to transmit uplink control information, on the basis of the size of data to be transmitted on the uplink shared channel in the plurality of slots, and / or a first resource amount of the uplink shared channel in the plurality of slots; and a transmission circuit for multiplexing and transmitting the uplink control information in a resource having the determined second resource amount, and the data.

Description

[Technical Field]

[0001] This disclosure is, Communication device , relating to base stations, communication methods, and integrated circuits. [Background technology]

[0002] In recent years, driven by the expansion and diversification of wireless services, the Internet of Things (IoT) is expected to develop dramatically. The use of mobile communication is expanding beyond smartphones and other information terminals to encompass a wide range of fields, including cars, homes, home appliances, and industrial equipment. To support this service diversification, significant improvements in the performance and functionality of mobile communication systems are required, including increased system capacity, an increase in the number of connected devices, and low latency. Fifth-generation mobile communication systems (5G) possess features such as large capacity and ultra-high speed (eMBB: enhanced Mobile Broadband), massive machine-type communication (mMTC: massive Machine Type Communication), and ultra-reliable and low-latency communication (URLLC: Ultra Reliable and Low Latency Communication), enabling flexible wireless communication to meet diverse needs.

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

[0004] [Non-Patent Document 1] 3GPP TS38.104, “NR Base Station (BS) radio transmission and reception (Release 15),” December 2020. [Non-Patent Document 2] RP-202928, “New WID on NR coverage enhancements,” China Telecom, December 2020. [Non-Patent Document 3] 3GPP TS38.211, “NR Physical channels and modulation (Release 16),” December 2020. [Non-Patent Document 4] 3GPP TS38.212, “NR Multiplexing and channel coding (Release 16),” December 2020. [Non-Patent Document 5] 3GPP TS38.213, “NR Physical layer procedures for control (Release 16),” December 2020. [Non-Patent Document 6] 3GPP TS38.214, “NR Physical layer procedures for data (Release 16),” December 2020. [Non-Patent Document 7] R1-2102241, “FL summary of TB processing over multi-slot PUSCH (SI 8.8.1.2),” Moderator (Nokia, Nokia Shanghai Bell), January 25th-February 5th, 2021. [Overview of the project]

[0005] In NR, resources on different channels may overlap. However, there is room for consideration regarding how to control (or operate) when resources on different channels overlap.

[0006] Non-limiting embodiments of this disclosure provide appropriate control when resources from different channels overlap. Communication device This contributes to the provision of base stations, communication methods, and integrated circuits.

[0007] A terminal according to one embodiment of the present disclosure includes a control circuit that determines a second resource amount to be used for transmitting uplink control information based on the size of the data transmitted in the uplink shared channel in the multiple slots and / or the first resource amount of the uplink shared channel in the multiple slots, when the transmission resources allocated for transmitting an uplink shared channel using multiple slots and the transmission resources for an uplink control channel overlap in time, and a transmission circuit that multiplexes and transmits the uplink control information and the data in the resources of the determined second resource amount.

[0008] These comprehensive or specific embodiments may be implemented as systems, devices, methods, integrated circuits, computer programs, or recording media, or as any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0009] According to one embodiment of this disclosure, appropriate control can be achieved when resources from different channels overlap.

[0010] Further advantages and effects of one embodiment of this disclosure will be made apparent from the specification and drawings. Such advantages and / or effects are provided by several embodiments and features described in the specification and drawings, but not all of them are necessarily provided in order to obtain one or more identical features. [Brief explanation of the drawing]

[0011] [Figure 1] This diagram illustrates an example where single-slot PUCCH (Physical Uplink Control Channel) transmission and multi-slot PUSCH (Physical Uplink Shared Channel) transmission overlap in time. [Figure 2] This diagram illustrates an example where PUCCH transmissions from multiple single slots and PUSCH transmissions using multiple slots overlap in time. [Figure 3] Block diagram showing a configuration example focusing on a part of the base station. [Figure 4] Block diagram showing a configuration example focusing on a part of the terminal. [Figure 5] Block diagram showing an example of a base station configuration. [Figure 6] Block diagram showing an example of terminal configuration [Figure 7] Flowchart showing an example of operation in Embodiment 1 [Figure 8A] Figure showing an example of modified example 2. [Figure 8B] Figure showing an example of modified example 2. [Figure 9A] Figure showing an example of Embodiment 2 [Figure 9B] Figure showing an example of Embodiment 2 [Figure 10] Flowchart showing an example of operation in Embodiment 2 [Figure 11] Diagram illustrating the constraints of UCI (Uplink Control Information) on PUSCH in NR Rel.15 / 16. [Figure 12] This diagram shows an example of the relationship between Transport block processing over multi-slot PUSCH (TBoMS) transmission and retransmission in downlink transmission. [Figure 13] Flowchart showing an example of operation of Method 1 in Embodiment 3 [Figure 14] A diagram showing an example of the operation of Method 1 in Embodiment 3. [Figure 15] Flowchart showing an example of operation of Method 2 in Embodiment 3 [Figure 16]Figure showing an example of operation of Method 2 in Embodiment 3. [Figure 17] Flowchart showing an example of operation of Method 3 in Embodiment 3 [Figure 18] A diagram showing an example of the operation of Method 3 in Embodiment 3. [Figure 19] Figure showing an example of operation related to Modification 2 [Figure 20] Figure showing an example of operation related to Modification 2 [Figure 21] A diagram showing an example of case classification related to Modification Example 3. [Figure 22] Diagram showing an example of operation related to Supplement 4 [Figure 23] Diagram showing an example of operation related to Supplement 5 [Figure 24] Diagram showing an example of operation related to Supplement 7 [Figure 25] Diagram of a representative architecture of a 3GPP NR system [Figure 26] Schematic diagram showing the functional separation between NG-RAN and 5GC. [Figure 27] Sequence diagram of the setup / reconfiguration procedure for Radio Resource Control (RRC) connection. [Figure 28] This schematic diagram illustrates usage scenarios for high-capacity, high-speed communication (eMBB: enhanced Mobile Broadband), massive machine type communications (mMTC: massive machine type communications), and highly reliable, ultra-low-latency communications (URLLC: Ultra Reliable and Low Latency Communications). [Figure 29] Block diagram illustrating an exemplary 5G system architecture for a non-roaming scenario. [Modes for carrying out the invention]

[0012] Embodiments of this disclosure will be described in detail below with reference to the drawings.

[0013] In NR, for example, in addition to the frequency bands below 6GHz, mainly the 700MHz to 3.5GHz band, which have been used for cellular communications (for example, also called Frequency Range 1 (FR1)), millimeter-wave bands such as 28GHz or 39GHz (for example, also called FR2) that can secure a wide bandwidth may be utilized (see, for example, Non-Patent Document 1). Furthermore, in FR1, for example, higher frequency bands may be used compared to the frequency bands used in Long Term Evolution (LTE) or 3G (3rd Generation mobile communication systems), such as the 3.5GHz band.

[0014] The higher the frequency band, the greater the radio wave propagation loss, and the more likely the reception quality of radio waves is to deteriorate. For this reason, when NR uses a higher frequency band compared to, for example, LTE or 3G, it is expected that it will ensure a communication area (or coverage) comparable to that of radio access technologies (RATs) such as LTE or 3G, or in other words, that it will ensure appropriate communication quality. For example, in Release 17 (represented as "Rel.17"), methods for improving coverage in NR are being considered (see, for example, Non-Patent Document 2).

[0015] In NR, terminals send and receive data according to resource allocations indicated by, for example, Layer 1 control signals (e.g., DCI: Downlink Control Information) on the downlink control channel (PDCCH: Physical Downlink Control Channel) from the base station (see, for example, Non-Patent Documents 3-6).

[0016] For example, the terminal feeds back a response signal (ACK / NACK: Acknowledgement / Negative Acknowledgement) indicating the success or failure of decoding for the downlink data channel (PDSCH: Physical Downlink Shared Channel) using the uplink control channel (PUCCH: Physical Uplink Control Channel) (see, for example, Non-Patent Document 5).

[0017] A terminal can also use PUCCH, for example, to transmit downlink channel state information (CSI), which indicates the state of the downlink channel, to the base station in addition to ACK / NACK. These ACK / NACK and CSI are also called uplink control information (UCI).

[0018] In the following, transmitting at least one of data and control information using PUCCH may be abbreviated as "transmitting PUCCH" or "PUCCH transmission." Similarly, receiving at least one of data and control information using PUCCH may be abbreviated as "receiving PUCCH" or "PUCCH reception." For other channels, similar abbreviations may be used for at least one of the transmission and reception operations.

[0019] When the terminal transmits ACK / NACK for the PDSCH allocated by DCI, the terminal transmits the PUCCH in accordance with, for example, the resource allocation indicated by DCI from the base station. The control information included in the DCI may include information regarding the PUCCH resource. For example, the information regarding the PUCCH resource may include information regarding the timing of how many slots after the slot in which the terminal received the PDSCH to transmit the PUCCH. This information regarding the timing may be referred to as K1 or PDSCH-to-HARQ_feedback timing indication. Note that HARQ is an abbreviation for Hybrid Automatic Repeat reQuest.

[0020] In the uplink, for example, the terminal transmits the uplink data channel (PUSCH: Physical Uplink Shared Channel) in accordance with the resource allocation (e.g., Grant) indicated by DCI on the PDCCH from the base station (see, for example, Non-Patent Documents 3-6). The control information included in the DCI may include, for example, information regarding the time domain resource for transmitting the PUSCH.

[0021] For example, the information regarding the time domain resource may be information regarding the timing of how many slots after the slot in which the terminal received the PDCCH to transmit the PUSCH (e.g., information referred to as K2), or information regarding at least one of the position of the first symbol of the PUSCH in the slot, or the number of symbols for transmitting the PUSCH.

[0022] <Determination of TBS> In NR Rel.15 / 16 (Release 15 and / or 16), the data size or transport block size (TBS) is determined based on the amount of resources per slot and / or based on the amount of resources allocated to the first PUSCH transmission in Repetition. Note that the amount of resources may be represented by, for example, the number of symbols or the number of resource elements. Also, the TBS may be described as the TB size.

[0023] On the other hand, in NR Rel.17, when PUSCH is transmitted using multiple slots, a method of determining the TBS based on the amount of resources of the number of slots used for PUSCH transmission and a method of determining the TBS by multiplying the TBS calculated from the amount of resources per slot or the amount of resources allocated to the first PUSCH transmission in Repetition by a scaling factor greater than 1 are being considered (see, for example, Non-Patent Document 7). Note that the method of calculating the TBS from the amount of resources per slot or the amount of resources allocated to the first PUSCH transmission in Repetition may be, for example, the method defined in NR Rel.15 / 16 as described above.

[0024] <Time overlap between PUCCH and PUSCH> In the uplink transmission of the terminal, the transmission resources for PUCCH and the transmission resources for PUSCH may overlap (collide) in time. Hereinafter, the resources where the transmission resources for PUCCH and the transmission resources for PUSCH overlap in time may be referred to as the resources (or slots) where PUCCH and PUSCH collide.

[0025] FIG. 1 is a diagram showing an example where PUCCH transmission in a single slot and PUSCH transmission using multiple slots overlap in time. FIG. 2 is a diagram showing an example where PUCCH transmissions in multiple single slots and PUSCH transmission using multiple slots overlap in time.

[0026] As illustrated in FIGS. 1 and 2, when PUCCH transmission (PUCCH in FIGS. 1 and 2) and PUSCH transmission using multiple slots (PUSCH repetition in FIGS. 1 and 2) overlap in time, in NR Rel. 15 / 16, the terminal may multiplex and transmit UCI and uplink data on the PUSCH (see, for example, Non-Patent Documents 4 and 5).

[0027] In NR Rel. 15 / 16, for example, as illustrated in FIG. 1, PUCCH transmission in a single slot may sometimes overlap in time with some slots of PUSCH transmission using multiple slots (e.g., Repetition). In this case, the terminal may multiplex and transmit UCI and uplink data on the PUSCH in the slots where the PUCCH transmission and the PUSCH transmission overlap in time (see, for example, Non-Patent Document 5).

[0028] Also, for example, as illustrated in FIG. 2, PUCCH transmissions in multiple single slots may sometimes overlap in time with some slots (slots #0 and #2 in the example of FIG. 2) of PUSCH transmission using multiple slots (e.g., Repetition). In this case, the terminal may multiplex and transmit UCI and uplink data on the PUSCH in each of the slots where the PUCCH transmission and the PUSCH transmission overlap in time.

[0029] <Example of calculating the amount of UCI resources> When UCI (e.g., ACK / NACK) is multiplexed and transmitted on the PUSCH, the amount of resources (number of resource elements) allocated to the UCI within the PUSCH may be calculated by Equation (1) (see, for example, Non-Patent Document 4).

Number

[0030] In NR Rel. 15 / 16, K representing the code block size (or TBS) rThis value is determined by the amount of resources per slot, or the amount of resources allocated to the initial PUSCH transmission in a Repetition.

[0031] Furthermore, N represents the number of OFDM symbols in PUSCH. symb, all PUSCH The number of OFDM symbols for PUSCH in each slot (individual slot) is used.

[0032] Furthermore, y = min(α, β) is a function in which y takes the smaller value of α and β (hereinafter sometimes referred to as the "min function"). In the following, α may be referred to as the first element and β as the second element in min(α,β).

[0033] For example, using equation (1), the amount of UCI resources in a slot where PUCCH and PUSCH collide is determined, and the UCI and uplink data are multiplexed and transmitted to PUSCH.

[0034] In NR Rel.17, when a PUSCH is transmitted using multiple slots as described above, two methods are considered for determining the TBS: one based on the resource amount of the number of slots used for the PUSCH transmission, and the other by multiplying the TBS calculated from the resource amount allocated per slot or to the first PUSCH transmission in a Repetition by a scaling factor greater than 1. In the following, these two methods for determining the TBS may be referred to as "Rel.17 TBS determination methods."

[0035] Furthermore, a PUSCH transmission method is being considered in which the TB of the TBS calculated using the TBS determination method of Rel.17 described above is transmitted across multiple slots. This PUSCH transmission, which transmits TB across multiple slots, may be described as TBoMS (TB processing over multi-slot) PUSCH, or TBoMS transmission. There may be cases where the transmission resources for TBoMS transmission (transmission resources for PUSCH) and the transmission resources for PUCCH overlap in time. However, there is room for consideration regarding the UCI transmission method in this case.

[0036] For example, when UCI and uplink data are multiplexed and transmitted to PUSCH, the amount of resources allocated to UCI can be calculated using the UCI resource amount calculation method of NR Rel. 15 / 16. For example, in the UCI resource amount calculation method of NR Rel. 15 / 16 (e.g., equation (1)), the number of OFDM symbols N in PUSCH symb, all PUSCH Replace with the number of symbols used for TBoMS transmission, i.e., the number of symbols included in multiple slots, and the code block size (or TBS)K r One possible approach is to replace the TBS calculated using the TBS determination method of Rel.17 and then calculate the amount of resources that can be allocated to the UCI. However, if the amount of UCI resources calculated using these replacements is used, it may not be possible to properly map the UCI to the slot where PUCCH and PUSCH are in conflict.

[0037] For example, a UCI may be mapped to multiple slots. For instance, if a UCI before multiplexing with uplink data could be transmitted using a single slot PUCCH, but a UCI after multiplexing with uplink data is mapped to multiple slots, at least one of the UCI decoding delay and decoding processing load may increase. For example, if the multiple slots used for TBoMS transmission are non-contiguous slots, the tendency for at least one of the UCI decoding delay and decoding processing load to increase will be more pronounced. Also, if the slot where PUCCH and PUSCH collide is the last slot in TBoMS transmission, and the UCI after multiplexing with uplink data is mapped to multiple slots, there may be a shortage of PUSCH resources to multiplex the UCI.

[0038] In non-limiting embodiments of this disclosure, the objective is to provide a terminal, base station, and communication method that can appropriately determine the amount of UCI resources to be multiplexed to PUSCH when the transmission resources for PUCCH transmission and PUSCH transmission using multiple slots (TBoMS transmission) overlap in time, and the TBS transmitted by TBoMS is greater than the TBS calculated from the amount of resources allocated per slot or to the first PUSCH transmission in a repeat.

[0039] For example, the amount of UCI resources to be multiplexed on PUSCH may be determined on a slot basis, or based on the amount of resources allocated to the initial PUSCH transmission in a Repetition. In this determination, for example, the number of OFDM symbols, which is a parameter used to determine the amount of UCI resources, may be a different value from the number of symbols allocated to the TBoMS transmission. Also, in this determination, for example, the code block size (or TBS), which is a parameter used to determine the amount of UCI resources, may be a different value from the code block size (or TBS) transmitted in TBoMS.

[0040] Several embodiments will be described below.

[0041] [Overview of the communication system] Each embodiment of the present disclosure comprises, for example, at least one base station and at least one terminal.

[0042] Figure 3 is a block diagram showing a partial configuration example of a base station 100 according to one embodiment of the present disclosure, and Figure 4 is a block diagram showing a partial configuration example of a terminal 200 according to one embodiment of the present disclosure.

[0043] In the base station 100 shown in Figure 3, the control unit 101 determines, for example, when the transmission resources allocated to the transmission of an uplink sharing channel (PUSCH) using multiple slots and the transmission resources for the uplink control channel (PUCCH) overlap in time, the amount of second resources to be used for transmitting uplink control information (UCI) based on the size of the data transmitted in the PUSCH in multiple slots (e.g., code block size or TBS), and / or the amount of first resources for the PUSCH in multiple slots. The receiving unit 108 receives the UCI in the determined second amount of resources and the multiplexed data.

[0044] In the terminal 200 shown in Figure 4, the control unit 205 determines, for example, when the transmission resources allocated to the transmission of the uplink shared channel (PUSCH) using multiple slots and the transmission resources for the uplink control channel (PUCCH) overlap in time, the amount of second resources to be used for transmitting uplink control information (UCI) based on the size of the data transmitted in the PUSCH in multiple slots (e.g., code block size or TBS), and / or the amount of first resources for the PUSCH in multiple slots. The transmission unit 209 then multiplexes the UCI and data in the determined second resource amount and transmits them, for example.

[0045] (Embodiment 1) [Base station configuration] Figure 5 is a block diagram showing an example configuration of base station 100. The example configuration of base station 100 shown in Figure 5 may be common throughout this disclosure, including other embodiments and modifications described later.

[0046] As shown in Figure 5, the base station 100 may include, for example, a control unit 101, a higher-level control signal generation unit 102, a downlink control information generation unit 103, an encoding unit 104, a modulation unit 105, a signal allocation unit 106, and a transmission unit 107. The base station 100 may also include, for example, a receiving unit 108, an extraction unit 109, a demodulation unit 110, and a decoding unit 111.

[0047] The control unit 101 determines, for example, at least one of the following: information regarding PDSCH reception to terminal 200, information regarding PUSCH transmission, and information regarding PUCCH transmission, and outputs the determined information to the higher-level control signal generation unit 102. The information regarding PDSCH reception and PUSCH transmission may include, for example, at least one of the following: information regarding the TDRA (Time Domain Resource Allocation) table and information regarding the number of transmission slots (e.g., whether or not TBoMS transmission is performed). The information regarding PUCCH transmission may include, for example, at least one of the following: information regarding the PUCCH resource set and information regarding K1.

[0048] Furthermore, the control unit 101 determines, for example, the encoding and modulation scheme and radio resource allocation for the downlink signal used to transmit downlink data signals or higher-level control signals, and downlink control information. The determined information may be output to, for example, the encoding unit 104, the modulation unit 105, and the signal allocation unit 106. The encoding and modulation scheme and radio resource allocation information for the data signals or higher-level control signals may also be output to, for example, the downlink control information generation unit 103.

[0049] Furthermore, the control unit 101 may, for example, determine the PUCCH resources for the terminal 200 to transmit PUCCH and output the determined information to the higher-level control signal generation unit 102 or the downlink control information generation unit 103. The control unit 101 may also, for example, output the determined information to the extraction unit 109, the demodulation unit 110, and the decoding unit 111.

[0050] Furthermore, the control unit 101 determines, for example, the encoding and modulation scheme and wireless resource allocation for the uplink data signal transmitted by the terminal 200, and outputs the determined information to the downlink control information generation unit 103, extraction unit 109, demodulation unit 110, and decoding unit 111. In addition, the control unit 101 determines, for example, the TBS, and outputs information related to the determined TBS to the decoding unit 111.

[0051] Furthermore, the control unit 101 may determine, for example, whether or not to apply TBoMS transmission in PUSCH transmission, and whether or not the PUCCH resource for transmitting PUCCH (e.g., UCI) and the radio resource for transmitting uplink data overlap in time. If the resources overlap in time, the control unit 101 may, for example, specify the amount of UCI resource in PUSCH. The specified information may be output to, for example, the extraction unit 109, the demodulation unit 110, and the decoding unit 111. Note that "specify" may be replaced with other terms such as "determine," "calculate," or "calculate."

[0052] The higher-level control signal generation unit 102 generates a higher-level control signal (e.g., a bit sequence) using control information input from the control unit 101, for example. The generated signal may be output to the encoding unit 104, for example.

[0053] The downlink control information generation unit 103 may, for example, generate a DCI (e.g., a bit string) using the control information input from the control unit 101, and output the generated DCI to the encoding unit 104. Note that the control information may also be transmitted to multiple terminals 200.

[0054] The encoding unit 104 encodes, for example, downlink data, a bit sequence obtained from the higher-level control signal generation unit 102, or DCI input from the downlink control information generation unit 103, and outputs the encoded bit sequence to the modulation unit 105.

[0055] The modulation unit 105 modulates the encoded bit sequence received from the encoding unit 104, for example, and outputs it to the signal assignment unit 106.

[0056] The signal assignment unit 106 maps, for example, the downlink data signal or control signal input as a symbol sequence from the modulation unit 105 to a radio resource instructed by the control unit 101. The signal assignment unit 106 also inputs, for example, the signal mapped to the radio resource to the transmission unit 107.

[0057] The transmitting unit 107 performs a transmission waveform generation process, such as OFDM (Orthogonal Frequency Division Multiplexing), on the signal output from the signal assignment unit 106. In the case of OFDM transmission using CP (Cyclic Prefix), the transmitting unit 107 may add CP to the signal after applying IFFT (Inverse Fast Fourier Transform).

[0058] Furthermore, the transmitting unit 107 performs wireless (e.g., RF: Radio Frequency) processing, such as digital-to-analog (D / A) conversion and upconversion, on the signal output from the signal assignment unit 106, and transmits the wireless signal to the terminal 200 via the antenna.

[0059] The receiving unit 108 performs RF processing, such as down-conversion and analog-to-digital (A / D) conversion, on the uplink signal transmitted from the terminal 200 and received via the antenna.

[0060] Furthermore, in the case of OFDM transmission, for example, the receiving unit 108 generates a frequency domain signal by applying an FFT to the received signal and outputs it to the extraction unit 109.

[0061] The extraction unit 109 extracts the portion of the radio resource from the received signal that has been transmitted as PUSCH or PUCCH, based on the information received from the control unit 101, and outputs the extracted PUSCH or PUCCH signal to the demodulation unit 110.

[0062] The demodulation unit 110, for example, demodulates PUSCH or PUCCH based on the information received from the control unit 101, and outputs the demodulation result to the decoding unit 111.

[0063] The decoding unit 111 uses, for example, the information received from the control unit 101 and the demodulation result obtained from the demodulation unit 110 to perform error-corrected decoding of PUSCH or PUCCH to obtain the decoded received bit sequence (e.g., UL data signal or UCI).

[0064] [Device Configuration] Next, an example configuration of the terminal 200 will be described with reference to Figure 6. As shown in Figure 6, the terminal 200 may include, for example, a receiving unit 201, an extraction unit 202, a demodulation unit 203, a decoding unit 204, and a control unit 205. Alternatively, the terminal 200 may include, for example, an encoding unit 206, a modulation unit 207, a signal allocation unit 208, and a transmission unit 209.

[0065] The receiving unit 201 receives, for example, a data signal or downlink control signal transmitted from the base station 100 via an antenna, and performs RF processing such as downconversion or A / D conversion on the wirelessly received signal to generate a baseband signal.

[0066] Furthermore, when the receiving unit 201 receives an OFDM signal, for example, it may perform FFT processing on the received signal to convert the received signal into the frequency domain.

[0067] The extraction unit 202, for example, uses information about the radio resource of the control signal input from the control unit 205 to extract the radio resource portion containing the downlink control signal from the received signal received from the receiving unit 201, and outputs the extracted signal to the demodulation unit 203. The extraction unit 202 also uses information about the radio resource of the data signal input from the control unit 205 to extract the radio resource portion containing the data signal, and outputs the extracted signal to the demodulation unit 203.

[0068] The demodulation unit 203, for example, demodulates the PDCCH or PDSCH based on the information received from the control unit 205, and outputs the demodulation result to the decoding unit 204.

[0069] Furthermore, the decoding unit 204 uses, for example, the information received from the control unit 205 and the demodulation results obtained in the demodulation unit 203 to perform error-corrected decoding of the PDCCH or PDSCH to obtain downlink received data, upper layer control information, or downlink control information. The obtained upper layer control information and downlink control information may be output to, for example, the control unit 205. The decoding unit 204 may also generate an ACK / NACK signal from, for example, the decoding result of the downlink received data.

[0070] The control unit 205 identifies (or determines) the radio resources for PDSCH reception, PUSCH transmission, and PUCCH transmission based on, for example, radio resource allocation information obtained from higher-layer control signals and downlink control information. The control unit 205 also outputs the determined information to, for example, the signal allocation unit 208, the extraction unit 202, and the demodulation unit 203.

[0071] Furthermore, the control unit 205 may determine, for example, whether or not to apply TBoMS transmission in PUSCH transmission, and / or whether the PUCCH resources for transmitting PUCCH and the radio resources for transmitting uplink data overlap in time. If the resources overlap in time, the control unit 205 may specify the amount of UCI resources in PUSCH. The specified information may be output, for example, to the encoding unit 206, the modulation unit 207, and the signal allocation unit 208.

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

[0073] The modulation unit 207 modulates the encoded bit sequence received from the encoding unit 206 to generate a modulation symbol sequence, and outputs the modulation symbol sequence to the signal assignment unit 208.

[0074] The signal assignment unit 208 maps the signal input from the modulation unit 207 to a radio resource instructed by the control unit 205. The signal assignment unit 208 also inputs the signal, after it has been mapped to the radio resource, to the transmission unit 209.

[0075] The transmitting unit 209 performs, for example, OFDM (Optical Frequency Modulation) waveform generation on the signal input from the signal assignment unit 208. In the case of OFDM transmission using CP (Critical Packet), the transmitting unit 209 may, for example, add CP to the signal after IFFT (Intermediate Frequency Transform). When generating a single-carrier waveform, a DFT (Dynamic Fracture Transform) unit may be provided after the modulation unit 207 or before the signal assignment unit 208.

[0076] Furthermore, the transmitting unit 209 performs RF processing on the transmission signal, such as D / A conversion and upconversion, and transmits the wireless signal via the antenna.

[0077] In Embodiment 1, the number of OFDM symbols and the code block size (or TBS), which are parameters used to determine the UCI resource amount, are determined based on, for example, the resource amount per slot or the resource amount allocated to the first PUSCH transmission in Repetition. Note that the resource amount may be defined by, for example, the number of symbols or the number of resource elements.

[0078] [TBS Calculation Method for PUSCH Transmission (TBoMS Transmission) Using Multiple Slots] A method for calculating the TBS for TBoMS transmission will be described. The TBS transmitted in TBoMS may be calculated by any of the following methods. Note that "calculation" may be mutually read as other terms such as "derivation" and "determination".

[0079] <TBS-Approach 1> In TBS-Approach 1, the TBS is determined based on the resource amount of the number of slots used for PUSCH transmission. Note that in the case of TBoMS, the number of slots used for PUSCH transmission is an integer of 2 or more. For example, the resource amount N of the number of slots used for PUSCH transmission RE may be calculated by the following formula (2). Note that N RE is the resource amount represented by the number of resource elements. [Number] [[ID=2)4]]

[0080] In formula (2), the upper limit of the number of REs in a slot is set to 156. Note that the upper limit value is not limited to 156. Also, in formula (2), N' RE indicates the number of REs allocated in a plurality of slots used for PUSCH transmission. For example, N' RE is the number of PUSCH transmissions used slot Each of the N slots may indicate the total value of the number of REs in one resource block. For example, N' RE may be calculated by the following formula (3).

number

[0081] TB size N info This is the resource amount N of the number of slots used for PUSCH transmission, calculated by equation (2). RE It may also be calculated using the following formula (4).

number

[0082] <TBS-Approach 2> In TBS-Approach 2, the TBS is determined by multiplying the TBS calculated from the amount of resources allocated per slot or to the first PUSCH transmission in a Repeat by a scaling factor greater than 1. For example, the amount of resources N allocated per slot or to the first PUSCH transmission in a Repeat RE N may also be calculated by the following formula (5). RE This represents the amount of resources expressed by the number of resource elements.

number

[0083] In equation (5), as in equation (2), the upper limit of the number of REs in a slot may be set to, for example, 156. However, the upper limit is not limited to 156.

[0084] N' RE This may be calculated, for example, by the following formula (6).

number

[0085] For example, the number of OFDM symbols allocated per slot, or to the first PUSCH transmission in a Repetition, may be notified to terminal 200 by information regarding the symbol length of the Time Domain Resource Allocation (TDRA).

[0086] TB size N info This is the amount of resources N allocated to the first PUSCH transmission in a slot unit or Repetition, calculated by equation (5). RE For example, it may be calculated using the following formula (7).

number

[0087] Furthermore, the method for calculating TBS is not limited to the method described above. For example, it is sufficient if the TBS transmitted via TBoMS is greater than the TBS calculated per slot or from the amount of resources allocated to the first PUSCH transmission in Repetition.

[0088] [Rate matching method for PUSCH transmission (TBoMS) using multiple slots] A TB having the TB size determined by the method described above may be transmitted using multiple slots in the following manner.

[0089] <RM-Approach 1> In NR, for example, a Circular Buffer is used in retransmission control. The Circular Buffer is memory that stores the encoder output. The Circular Buffer reads the encoder output with a number of bits corresponding to the allocated resource amount from a predetermined read start position (RV: Redundancy Version) in the Circular Buffer. In RM-Approach 1, for example, the encoder output with a number of bits corresponding to the resource amount of the number of slots used for PUSCH transmission may be read from a predetermined RV position and mapped to PUSCH resources spanning multiple slots.

[0090] <RM-Approach 2> In RM-Approach 2, for example, the encoder output of a number of bits corresponding to the amount of resources allocated to each slot or the first PUSCH transmission in a Repeat may be read from a predetermined RV position and mapped to the PUSCH resources of each slot or Repeat. Furthermore, the RV may be changed between slots or between Repeats.

[0091] [Method for determining UCI resource quantities] In slots where the transmission resources of two PUCCH signals overlap in time, the amount of UCI resources to be allocated to a PUSCH signal may be determined, for example, on a per-slot basis or based on the amount of resources allocated to the first PUSCH transmission in a Repeat. For example, the amount of UCI resources may be represented by the number of resource elements, and the amount of resources allocated on a per-slot basis or to the first PUSCH transmission in a Repeat may be represented by the number of symbols or the number of resource elements.

[0092] For example, the amount of UCI resources may be calculated using the following formula (8).

number

[0093] In this embodiment 1, equation (8) for determining the amount of UCI resources is N in equation (1). symb, all PUSCH is N symb, nominal PUSCH It has been replaced with N in equation (1). symb, all PUSCH While represents the number of OFDM symbols for PUSCH in each slot, N in equation (8) symb, nominal PUSCH This represents the number of OFDM symbols assigned to a slot or the first PUSCH transmission in a repeat. For example, the number of OFDM symbols assigned to a slot or the first PUSCH transmission in a repeat is N. symb, nominal PUSCH This information may be communicated to terminal 200 by means of the symbol length of the TDRA.

[0094] Furthermore, in this embodiment 1, equation (8) for determining the amount of UCI resources is K in equation (1). r However, K r,nominal It has been replaced with K. r,nominal This represents the code block size (or TBS) of the r-th code block, calculated based on the number of slots or the amount of resources allocated to the initial PUSCH transmission in a Repetition.

[0095] For example, if the number of code blocks is 1, K 0,nominal This is N obtained using equations (5) and (6). RE Based on this, it may also be calculated by the following formula (9).

number

[0096] Furthermore, if the number of code blocks is greater than 1, the sum of the code block sizes may be expressed by the following formula (10).

number

[0097] Next, an example of the operation of terminal 200 in this embodiment 1 will be described. Figure 7 is a flowchart showing an example of the operation of terminal 200 in this embodiment 1.

[0098] Terminal 200 determines whether the transmission resources for PUCCH transmission and PUSCH transmission overlap in time (S11).

[0099] If the PUCCH transmission and the transmission resources for the PUSCH transmission do not overlap in time (No in S11), terminal 200 sends the UCI using the PUCCH of the non-overlapping transmission resource (S12). Then the flow in Figure 7 ends.

[0100] If the transmission resources for PUCCH transmission and PUSCH transmission overlap in time (Yes in S11), terminal 200 determines whether or not to apply PUSCH transmission using multiple slots (TBoMS transmission) (S13).

[0101] If PUSCH transmission (TBoMS transmission) using multiple slots is applied (Yes in S13), terminal 200 will be as described above.<TBS-Approach 1> or<TBS-Approach 2> TBS was chosen based on this (S14).

[0102] Terminal 200 determines the amount of UCI resources to be multiplexed to PUSCH and maps the determined amount of UCI resources to the PUSCH resources (S15).

[0103] Terminal 200 is as described above.<RM-Approach 1> or<RM-Approach 2> The rate-adjusted uplink data is then mapped to the PUSCH resource (S16).

[0104] Terminal 200 multiplexes the UCI and uplink data to PUSCH and transmits it (S17). Then the flow shown in Figure 7 ends.

[0105] If PUSCH transmission (TBoMS transmission) using multiple slots is not applicable (No in S13), terminal 200 determines the TBS on a slot-by-slot basis (S18).

[0106] Terminal 200 determines the amount of UCI resources to be multiplexed to PUSCH on a slot-by-slot basis, and maps the determined amount of UCI resources to the PUSCH resources (S19).

[0107] Terminal 200 maps the uplink data to the PUSCH resource on a slot-by-slot basis (S20).

[0108] Terminal 200 multiplexes the UCI and uplink data to PUSCH and transmits it (S21). Then the flow shown in Figure 7 ends.

[0109] According to Embodiment 1 described above, the amount of UCI resources for the UCI multiplexed on PUSCH in each slot can be calculated using slot-specific parameters, thus preventing the UCI from being mapped to multiple slots.

[0110] (Variation 1) In slots where the transmission resources of PUCCH and PUSCH overlap in time, the method for determining the amount of UCI resources to allocate to PUSCH is not limited to the example above. In the following modified example 1, the amount of UCI resources is determined using the number of OFDM symbols allocated per slot or to the first PUSCH transmission in a Repetition, the TBS determined based on the resource amount of the number of slots used for TBoMS transmission (i.e., multiple slots), and the number of OFDM symbols across multiple slots used for TBoMS transmission.

[0111] For example, in this modified example 1, the amount of UCI resources may be calculated by the following formula (11).

number

[0112] Furthermore, the number of OFDM symbols N in PUSCH in equation (11) symb, all PUSCH This may be replaced with the number of symbols used for TBoMS transmission (i.e., the number of symbols included in multiple slots). Code block size (or TBS) K r The above<TBS-Approach 1> or<TBS-Approach 2> This can be replaced with TBS calculated by [the specified method].

[0113] Furthermore, the second element of the min function on the right-hand side of equation (11) is a term that represents the upper limit of the amount of resources that can be allocated to UCI within PUSCH.

[0114] In this modified example 1, the parameter N is the second element of the min function in equation (11). symb, nominal PUSCH This is expressed in units of slots, or by the number of OFDM symbols assigned to the first PUSCH transmission in a Repetition.

[0115] In equation (11), for example, the min function selects the smaller of the first and second elements. Therefore, if the second element of the min function is set as the upper limit, the first element of the min function represents the amount of resources needed to reach that upper limit.

[0116] According to this modified example 1, the upper limit of the amount of UCI resources (UCI resource amount) to be duplicated on PUSCH in each slot (for example, the second element of the min function in equation (11)) is set to a slot-specific parameter (for example, N symb, nominal PUSCH Since it can be calculated using ( ), it is possible to prevent UCI from being mapped to multiple slots. Also, until the amount of UCI resources reaches the upper limit, the number of PUSCH resource elements across multiple slots (for example, N in equation (11)) symb, all PUSCH ), and TBS of TBoMS (for example, K in equation (11) rSince the amount of UCI resources can be set using a value calculated with (for example, the first element of the min function in equation (11)), it is possible to set the amount of UCI resources based on the exact number of resource elements in multiple slots. For example, this modified example 1 is effective when the number of resource elements in each slot is different, and / or when the number of resource elements allocated to the first PUSCH transmission in Repetition is different from the number of resource elements allocated to subsequent PUSCH transmissions.

[0117] (Modification 2) In this modified example 2, the method for calculating the amount of UCI resources may be varied depending on which of the multiple slots used to transmit PUSCH conflicts with PUCCH.

[0118] Figures 8A and 8B show an example of modification 2.

[0119] For example, the method for calculating the amount of UCI resources may differ depending on whether the first slot for TBoMS transmission (slot #0 in Figure 8A) collides with PUCCH, as shown in Figure 8A, or whether the slot other than the first slot for TBoMS transmission (slot #1 in Figure 8B) collides with PUCCH, as shown in Figure 8B.

[0120] For example, as shown in Figure 8A, if the initial slot for TBoMS transmission conflicts with PUCCH, UCI resource determination method 1 (Scheme 1 in Figure 8A), described later, may be applied. If PUCCH conflicts with a slot other than the initial slot, UCI resource determination method 2 (Scheme 2 in Figure 8B), described later, may be applied.

[0121] Here, in UCI resource determination method 1, in equation (1), the number of OFDM symbols of PUSCH is N. symb, all PUSCH Replace with the number of symbols used for TBoMS transmission (i.e., the number of symbols included in multiple slots). Also, in UCI resource determination method 1, in equation (1), code block size (or TBS) K rThe above<TBS-Approach 1> or<TBS-Approach 2> Replace it with the value calculated by [the method described].

[0122] The UCI resource determination method 2 may be the method of Embodiment 1 or Modification 1 described above.

[0123] According to this modified example 2, in slots other than the initial slot, the UCI after being multiplexed on PUSCH is mapped to multiple slots, thus preventing a shortage of PUSCH resources for UCI multiplexing. On the other hand, in the initial slot, even if the UCI after being multiplexed on PUSCH is mapped to multiple slots, there is no shortage of PUSCH resources for UCI multiplexing.

[0124] (Variation 3) In this modified example 3, the method for calculating the amount of UCI resources may be varied depending on which of the multiple slots used for TBoMS transmission PUCCH conflicts with.

[0125] For example, the amount of UCI resources may be calculated using the following formula (12).

number

[0126] Furthermore, the number of OFDM symbols N in PUSCH in equation (12) symb, all PUSCH This may be replaced with the number of symbols used for TBoMS transmission (i.e., the number of symbols included in multiple slots). Code block size (or TBS) K r The above<TBS-Approach 1> or<TBS-Approach 2> It can be replaced with this.

[0127] Furthermore, the second element of the min function on the right-hand side of equation (12) is a term that represents the upper limit of the amount of resources that can be allocated to UCI within PUSCH.

[0128] In this modified example 3, the parameter N is the second element of the min function on the right-hand side of equation (12). symb, remaining PUSCH This uses the number of OFDM symbols in the slot where PUCCH collided and in subsequent slots among the multiple slots used for TBoMS transmission.

[0129] According to this modified version 3, even if the UCI after multiplexing is mapped to multiple slots, it is possible to prevent a shortage of PUSCH resources for UCI multiplexing.

[0130] (Supplement to Embodiment 1) Note that the method for setting (calculating) TBS is not limited to the example described above. The following provides further details on how to set TBS.

[0131] <Setup Method 1> In configuration method 1, for example, the TB size may be set based on the number of resources for the TBoMS transmission (e.g., the number of slots). In other words, the TB size may be set based on the number of slots (e.g., time intervals) used in one of the multiple slots for the TBoMS transmission.

[0132] For example, in NR Rel.15 / 16, the TB size (e.g., the number of information bits) is a value calculated according to the following equation (13) (also called the intermediate variable) "N info It is set based on (for example, as described in TS38.214 V16.1.0 sections 5.1.3 and 6.1.4). The TB size is, for example, N info It may be determined by further adjustments depending on the value of N. info The larger the value, the larger the TB size can be set.

number

[0133] In setting method 1, for example, the number of resources for TBoMS transmission (e.g., the number of slots) is set to "N MSIf this is the case, the TB size is calculated according to the following formula (14): info It may be set based on the following.

number

[0134] From equation (14), for example, N MS The more there are, the larger the TB size will be set. Therefore, for example, N MS The more slots there are, the more information bits are transmitted in each slot used for TBoMS transmission, thus improving user throughput.

[0135] Furthermore, for example, the same HARQ process is used for multiple slots used in TBoMS transmission. Therefore, TBoMS transmission allows for the use of more slots within the RTT (Round Trip Time) without increasing the number of HARQ processes. For example, in environments where the RTT is extremely long compared to the slot length, such as NTN (Non-Terrestrial Network) environments, user throughput can be improved by expanding the TB size based on the number of TBoMS transmission slots, without increasing the number of HARQ processes.

[0136] Furthermore, for example, with TBoMS transmission, the TB size increases based on the increase in the number of slots used for data transmission, so the effective coding rate (e.g., MCS) can be set in the same way as the coding rate (e.g., MCS) set when TBoMS transmission is not performed. Therefore, even when using TBoMS transmission, the decrease in frequency utilization efficiency (spectral efficiency) can be suppressed, and transmission with a necessary and sufficient error rate (e.g., BLER: Block Error Rate) is possible.

[0137] Note that when setting the TB size, N MSWhether or not to apply (for example, which of equations (13) and (14) to apply) may be separately notified to terminal 200, for example, by an RRC (Radio Resource Control) message (also called RRC signaling or upper-layer parameter), MAC CE (Control Element), or DCI. This notification allows, for example, terminal 200 or traffic type where an increase in data rate is expected to be improved by setting a larger TB size by applying equation (14) to improve throughput. On the other hand, for terminals or traffic types different from those mentioned above, a smaller TB size can be set by applying equation (13) to improve reliability (in other words, transmission with a lower error rate).

[0138] Furthermore, NTN is considering disabling HARQ retransmission (for example, by setting "HARQ-feedback disable") for traffic where low latency is required. If HARQ retransmission is disabled, HARQ retransmission will not be performed, and therefore, more reliable transmission (for example, a lower error rate) can be expected.

[0139] Therefore, in setting method 1, for example, when retransmission by HARQ is enabled (for example, when HARQ-feedback enable is set), or for HARQ processes where retransmission by HARQ is enabled, the TB size setting is N as shown in equation (14). MS The following may be applied: For example, when retransmission control by HARQ is applied to base station 100 and terminal 200 (for example, when "HARQ-feedback enable" is set), or when retransmission control by HARQ is applied to data (or HARQ process), N according to equation (14) MS The TB size may be determined based on the following: For example, if retransmission by HARQ is disabled (for example, if HARQ-feedback disable is set), or for a HARQ process where retransmission by HARQ is disabled, the TB size setting can be set to N as shown in equation (13). MSSince this rule does not apply, reliability can be improved (for example, transmission with a low error rate).

[0140] Note N MS (Or, parameters for deriving the number of resources for TBoMS transmission) may be notified to terminal 200, for example, by an RRC message and at least one of DCIs.

[0141] For example, RRC messages may include "pdsch-AggregationFactor" (message for downlinks), "pusch-AggregationFactor" (message for uplinks) as defined in TS38.331 V16.1.0, or "repK" (parameter for uplink configured grant) within "ConfigureGrantConfig", or other messages may be used.

[0142] Also, N MS For example, multiple candidates may be notified (or set) to terminal 200 by an RRC message, and one of the multiple candidates may be notified to terminal 200 by DCI for each PDSCH or PUSCH assignment (e.g., scheduling information). In this case, the RRC message used to set multiple candidates may be, for example, "repetitionNumber-r16" in "PDSCH-TimeDomainResourceAllocationList-r16" (message for downlink) or "PUSCH-TimeDomainResourceAllocationList-r16" (message for uplink), or other messages may be used.

[0143] This type of notification allows for the reuse of notification mechanisms in existing standards, thereby reducing the complexity of processing on terminal 200.

[0144] Furthermore, since these notifications are explicitly sent to terminal 200, for example, scheduling information may be notified to terminal 200 by DCI during the initial transmission, and the same TB (e.g., data of the same TB size) based on that scheduling information may be transmitted in consecutive slots. In other words, scheduling information does not need to be notified by DCI in each slot after the slot corresponding to the initial transmission of TBoMS.

[0145] <Setup Method 2> In configuration method 2, for example, the TB size may be set based on a scaling factor. In other words, the TB size may be set based on a scaling factor of the TB size in multiple slots (e.g., time intervals) used for TBoMS transmission.

[0146] In setting method 2, for example, the scaling factor is set to "N scaling In this case, the TB size is calculated according to the following formula (15): info It may be set based on the following.

number

[0147] From equation (15), for example, the scaling coefficient N scaling The larger the scaling factor N, the larger the TB size will be set. scaling The larger the value, the more information bits are transmitted in each slot used for TBoMS transmission, thus improving user throughput.

[0148] Methods for setting the scaling factor include, for example, setting (or notifying) terminal 200 semi-statically via RRC messages, and setting (or notifying) terminal 200 dynamically via DCI.

[0149] Furthermore, the scaling factor may be set to a value of 1 or greater. Also, the scaling factor may be an integer value or a decimal value. If the scaling factor is set to a decimal value, a ceiling (carry-up) or floor (borrow-down) operation may be performed in equation (3).

[0150] In the method of setting the scaling factor semi-statically, for example, the scaling factor may be notified to terminal 200 semi-statically by an RRC message. For example, the RRC message used to set the scaling factor may be "PDSCH-TimeDomainResourceAllocationList" or "PUSCH-TimeDomainResourceAllocationList", or it may be "PDSCH-Config" or "PUSCH-Config", or other messages may be used.

[0151] Furthermore, for example, a scaling factor may be applied in setting the TB size when TBoMS transmission is performed (e.g., application of equation (15)). In other words, if TBoMS transmission is not performed, a scaling factor may not be applied in setting the TB size (e.g., application of equation (13)). In other words, the base station 100 and terminal 200 may, for example, base their TB size determination on a scaling factor when TBoMS transmission is applied, but not on a scaling factor when TBoMS transmission is not applied. Alternatively, information indicating whether or not to apply a scaling factor in setting the TB size may be notified to terminal 200. This information may be notified to terminal 200 by DCI for each data scheduling, for example.

[0152] Furthermore, the scaling factor may be set individually for each HARQ process, for example. If the number of TBoMS transmission slots is set individually for each HARQ process, then, for example, the scaling factor may be applied to HARQ processes that perform TBoMS transmissions, while it may not be applied to HARQ processes that do not perform TBoMS transmissions.

[0153] Thus, throughput can be improved by applying scaling factors to HARQ processes when retransmission by HARQ is enabled or when HARQ processes are disabled. Conversely, transmission reliability can be improved by not applying scaling factors to HARQ processes when retransmission by HARQ is disabled (e.g., HARQ-feedback disable is set) or when HARQ processes are disabled.

[0154] The above explains how to set the scaling factor to semi-static.

[0155] In addition, when setting the scaling factor to Dynamic, for example, the scaling factor may be notified to terminal 200 by DCI, which notifies data scheduling information.

[0156] Alternatively, for example, multiple candidate scaling factors may be set on terminal 200 via an RRC message, and one of the multiple candidate scaling factors may be notified to terminal 200 via DCI for each data scheduling.

[0157] For example, the scaling factor may be included in information regarding time domain resource allocation (e.g., Time Domain Resource Allocation (TDRA)) (e.g., time domain resource allocation patterns). TDRA information may be represented, for example, in a table format (e.g., a TDRA table). In other words, the scaling factor may be defined in the TDRA table. In this case, for example, multiple candidates for TDRA information may be set on terminal 200 by an RRC message (e.g., PDSCH-TimeDomainResourceAllocationList-r16 or PUSCH-TimeDomainResourceAllocationList-r16), and DCI may notify terminal 200 of one of the multiple candidates' allocation patterns (including the scaling factor).

[0158] Alternatively, the scaling factor may be included in information that includes scaling factors (e.g., values ​​less than or equal to 1) for paging or random access processing (e.g., Random Access Channel (RACH) response). Information that includes scaling for paging or random access processing may be represented, for example, by a table. In other words, the scaling factor may be defined in a table that includes scaling factors for paging or random access processing.

[0159] In this case, for example, a table may be defined that includes scaling factors (e.g., values ​​less than or equal to 1) for paging (e.g., P-RNTI (Paging-Radio Network Temporary ID)) or random access processing (e.g., RA-RNTI (Random Access-RNTI)) as defined in Table 5.1.3.2-2 of TS38.214 V16.1.0, as well as scaling factors (e.g., values ​​greater than or equal to 1) for TBoMS transmission. Alternatively, for example, multiple candidate scaling factors may be set on terminal 200 by an RRC message, and one of the multiple candidate scaling factors may be notified to terminal 200 by DCI (e.g., TB scaling field).

[0160] The above explains how to set the scaling factor to Dynamic.

[0161] By notifying the scaling factor in the manner described above, the scaling factor can be notified using the notification mechanism in existing standards, thereby reducing the complexity of processing on terminal 200.

[0162] According to configuration method 2, for example, by expanding the TB size based on a scaling factor in multiple slots used for TBoMS transmission, more slots within the RTT can be used without increasing the number of HARQ processes. For example, in environments where the RTT is extremely long compared to the slot length, such as NTN environments, user throughput can be improved by expanding the TB size based on a scaling factor without increasing the number of HARQ processes.

[0163] Furthermore, since the TB size increases based on an increase in the number of slots used for data transmission, the actual coding rate (e.g., MCS) can be controlled based on a scaling factor, for example. Therefore, even when performing TBoMS transmission, controlling the scaling factor (or coding rate or MCS) can suppress a decrease in spectral efficiency and enable transmission with a necessary and sufficient error rate (e.g., BLER).

[0164] Furthermore, according to setting method 2, for example, a scaling factor can be set for terminal 200 independently of the number of TBoMS transmission slots. Therefore, even if the number of TBoMS transmission slots is not explicitly notified to terminal 200, for example, base station 100 and terminal 200 can set the TB size based on the number of transmissions or slots of the same TB using the scaling factor.

[0165] Furthermore, for example, the larger the value set for the scaling factor, the greater the amount of data transmitted, and the lower the transmission reliability. In other words, the smaller the value set for the scaling factor, the less data is transmitted, and the higher the transmission reliability. In this way, by adjusting the scaling factor, the trade-off between throughput and transmission reliability can be adjusted, making it possible to efficiently accommodate various types of traffic with different delay or reliability requirements.

[0166] The above explains an example of how to set the TB size.

[0167] Note that setting methods 1 and 2 may be combined. Alternatively, for example, the TB size is N MS and scaling coefficient N scaling It may be set based on both of the following. For example, for equation (13), N MS and scaling coefficient N scaling and may be multiplied together.

[0168] Thus, the base station 100 and the terminal 200 are N MS or scaling factor N scalingThe TB size is determined based on this.

[0169] This allows for improved user throughput, for example, in satellite communications, where round-trip propagation delay (e.g., RTT) is greater compared to terrestrial networks. Even when using the number of HARQ processes specified in Rel.15 / 16 (e.g., up to 16), the number of information bits that can be transmitted within RTT can be increased by expanding the TB size in each HARQ process based on the number of slots used for TBoMS transmission.

[0170] Furthermore, the increase in user throughput due to the expansion of the TB size can suppress the increase in the number of HARQ processes. Therefore, for example, it is possible to suppress the increase in the required HARQ buffer amount at the base station 100 or terminal 200, and to suppress the occurrence of new specifications such as the method of notifying the number of processes, thereby suppressing the increase in complexity of terminal 200, base station 100, and wireless communication system.

[0171] Furthermore, after increasing the number of HARQ processes to a certain extent (for example, up to 32), the number of slots N MS or scaling factor N scaling The TB size may be determined based on this. In this case, N is needed to transmit a sufficient number of information bits within the RTT. MS or scaling factor N scaling Because this can be kept under control to some extent, the TB size will not become too large.

[0172] The upper limit of the scaling factor for setting the TB size may be set, for example, to RTT(slot) / HARQ process count, or to the number of configurable TBoMS transmission slots.

[0173] Also, for example, in the case of disabling HARQ retransmission (HARQ-feedback disable), N for the TB size setting MS or N scaling In cases where it does not apply, N MS = 1 or N scaling The figure = 1 may also be shown.

[0174] Also, for example, whether N is applicable to the TB size setting MS or N scaling may be notified to the terminal 200 by the System Information Block (SIB) for each cell. Or, whether N MS or N scaling is applicable may be set and notified for each terminal 200 according to, for example, the capability of the terminal 200 (e.g., UE capability). Also, whether N MS or N scaling is applicable or the applicable N MS or N scaling upper limit value may be notified by the terminal 200 to the base station 100, and the base station 100 may set N MS or N scaling based on the notification of the terminal 200.

[0175] Also, for example, the TB size calculated by the application of N MS or N scaling may be set within a range not exceeding the upper limit of the TB size supported by the terminal 200. ?

[0176] [Another method for setting the TB size] An example of another method for the TB size will be described.

[0177] As described above, the TB size may be set based on, for example, the formula (13) described in TS38.214 V16.1.0 section 5.1.3 (PDSCH) and 6.1.4 (PUSCH) for "N info ". For example, the value of N info is determined based on the number of slots used for PDSCH or PUSCH transmission.

[0178] For example, N info in the calculation formula of N (e.g., formula (13)) included REThe number of REs used for data transmission may be calculated based on the number of slots used for PUSCH transmission (in other words, the transmitted signal or received signal). For example, N RE This can be expressed by the following equation (16).

number

[0179] In equation (16), N′ RE n indicates the number of REs in one resource block (Resource Blok (RB) or Physical Resource Block (PRB)) within the slot used for data transmission. PRB This indicates the number of resource blocks allocated to the data. Also, in equation (16), for example, the upper limit of the number of REs in the slot used to calculate the TB size is set to 156 so that the TB size does not exceed the supported data rate of terminal 200. Note that the upper limit is not limited to 156.

[0180] Below, the number of REs (N RE Two methods (for example, calculation method A and calculation method B) are described as examples of how to calculate ).

[0181] <Calculation method A> In calculation method A, N RE This can be calculated according to the following formula (17).

number

[0182] In equation (17), N′ RE This indicates the number of REs allocated in the multiple slots used for data transmission (e.g., PDSCH or PUSCH). For example, N′ RE N is used for data transmission. slot The sum of REs within one resource block in each of the individual slots may be shown. Also, in equation (17), N slotThis indicates the number of slots used for data transmission (e.g., PDSCH or PUSCH).

[0183] For example, N′ RE This can be calculated according to the following formula (18).

number

[0184] For example, N SC RB is, N SC RB =12 is also acceptable, and other values ​​are also acceptable. Also, N oh PRB For example, notifications to terminal 200 may be sent via "PDSCH-ServingCellConfig" for PDSCH and "PUSCH-ServingCellConfig" for PUSCH. Also, the overhead coefficient N oh PRB This can be a coefficient used to account for the overhead of signals different from DMRS, and is specified as {0, 6, 12, or 18} in Rel.15 / 16 NR.

[0185] Also, the overhead coefficient N oh PRB For this purpose, values ​​for multiple-slot transmission may be added, or the values ​​may be extended by multiplying coefficients. For example, the coefficient could be the number of slots N used for data transmission. slot You may apply N′ RE This can be calculated according to the following formula (19).

number

[0186] Equation (19) allows the use of the conventional overhead coefficient specified in Rel. 15 / 16, thus eliminating the need for new notifications and simplifying processing and reducing notification overhead.

[0187] Also, N'RE As a modification of the calculation of N′ RE it may be calculated according to the following formula (20).

Equation

[0188] In formula (20), N DMRS PRB represents the number of resource elements of DMRS in a resource block per slot allocated for PDSCH or PUSCH transmission. According to formula (20), for example, even when transmitting over multiple slots, the N DMRS PRB and N oh PRB defined in Rel.15 / 16 NR can be applied, thus simplifying the processing in the terminal 200.

[0189] In formula (18) or formula (19), N DMRS PRB represents the number of resource elements of DMRS per resource block in the slot interval (the interval of N slot ) allocated for PDSCH or PUSCH transmission. Therefore, for example, even when the number of DMRS is set individually for each slot (for example, when it is different for each slot), the exact number of resource elements of DMRS can be represented, and the number of resource elements used for data transmission (that is, N′ RE ) can be calculated more accurately.

[0190] According to formula (17), since the value N′ RE obtained by summing up the number of REs used for data transmission in each of the multiple slots is used for calculating the TB size, the TB size can be set according to the number of slots used for data transmission.

[0191] Also, for example, even when the number of REs is different for each slot, since the total value N′ RE of the number of REs in multiple slots is used for calculating the TB size, the accurate N REIt is possible to set the TB size based on a value.

[0192] Additionally, the upper limit of the number of REs in a slot is 156, and the number of slots is N. slot The value obtained by multiplying by is N RE By setting it to the upper limit, N′ RE The value taken can prevent the TB size from being set to an extremely large value.

[0193] <Calculation method B> In calculation method B, N RE This can be calculated according to the following equation (21).

number

[0194] In equation (21), N′ RE This indicates the number of REs in one resource block per slot of the multiple slots used for data transmission (e.g., PDSCH or PUSCH). Also, N slot This indicates the number of slots used for data transmission (e.g., PDSCH or PUSCH).

[0195] Calculation method B may assume, for example, that the number of REs per resource block is the same for each of the multiple slots used for data transmission. On the other hand, if the number of REs per resource block is different for each of the multiple slots used for data transmission, then N′ RE For example, the RE number of the slot with the fewest REs (e.g., the fewest) may be applied, or the RE number of a specific slot, such as the first slot (e.g., also called the first slot) or the last slot, may be applied. Or, N' RE A value based on the average number of REs in each of the multiple slots may be applied to this value.

[0196] Calculation method B uses the number of REs in one slot to calculate the TB size, making it possible to calculate the TB size more simply compared to calculation method A, for example.

[0197] Note that instead of equation (21), N is calculated according to equation (22) below. RE The following may be calculated.

number

[0198] The above explains calculation methods A and B.

[0199] Note that while calculation methods A and B describe an example where the min calculation is performed with an upper limit of 156 REs for one slot, N RE The calculation method is not limited to these. For example, the upper limit for the number of REs in a single slot may be a value other than 156. For example, in a single slot interval, the number of resource elements in a single resource block is 168 (=12 subcarriers × 14 symbols). Of the 168 resource elements, 1 symbol's worth of resource elements (=12) correspond to overhead such as DMRS, and the remaining 156 are defined as the upper limit for the number of resource elements allocated to data. For example, when transmitting with multiple slots, the upper limit for the number of resource elements may be set to 156 in a specific slot (e.g., the first slot), and to 168 in other slots (e.g., the second slot and beyond). In this case, N RE The min operation in the calculation formula is min(156 + 12·14·(N slot - 1), N′ RE ) may be replaced with this. This allows for an appropriate setting of the upper limit on the number of resource elements, for example, when overhead such as DMRS is mapped to the first symbol in multiple slots used for data transmission and not to the other symbols.

[0200] Furthermore, for example, there is no need to set an upper limit on the number of resource elements. In this case, for example, in calculation method A, "N RE = N′ RE ·n PRB" or, in calculation method B, "N RE = N′ RE ·N slot ·n PRB N RE The following may be calculated.

[0201] According to the TB size setting method described above, the base station 100 and terminal 200 set the TB size according to, for example, the number of slots used for data transmission (e.g., PDSCH or PUSCH). In other words, the base station 100 and terminal 200 determine the TB size based on information related to the amount of resources (e.g., number of slots) used for data (e.g., transmission signals). For example, the more slots used for data transmission, the greater the number of information bits transmitted in each slot used for data transmission. This TB size setting increases the amount of data that can be transmitted in a single HARQ process, thus improving throughput even with a specified (e.g., limited) number of HARQ processes.

[0202] Furthermore, the TB size is set according to the number of slots used for data transmission (e.g., PDSCH or PUSCH). Therefore, for example, as the number of information bits transmitted (e.g., data volume) increases with the number of slots, throughput can be improved while suppressing the increase in the number of resource blocks, that is, while suppressing the decrease in transmit power spectrum density (PSD). This makes it possible to transmit data with suppressed PSD degradation, for example, by expanding the coverage area where a certain data rate can be achieved.

[0203] Furthermore, for example, data allocation can be notified to terminal 200 via a single DCI for multiple slots, thus reducing control overhead. Additionally, it suppresses the consumption of HARQ processes (in other words, the increase in the number of HARQ processes used), allowing for terminal simplification by reducing the number of HARQ processes.

[0204] Furthermore, in TBoMS transmission, data transmission and reception processing such as encoding or modulation is performed individually for each slot. However, in the case of transmitting data spanning multiple slots (e.g., PDSCH or PUSCH), the base station 100 and terminal 200 can improve channel estimation accuracy and reduce the error rate by performing channel estimation for multiple slots collectively, demodulating and decoding, and then performing the decryption.

[0205] Furthermore, for example, DMRS may be mapped to a specific slot (e.g., the first slot) among multiple slots used for data transmission, while DMRS does not need to be mapped to the remaining slots. This DMRS mapping allows the base station 100 and terminal 200 to transmit more data. Therefore, even if DMRS mapping is set individually for each slot (e.g., different for each slot), the TB size can be set appropriately.

[0206] The number of slots used for data transmission (e.g., PDSCH or PUSCH) can also be rephrased as, for example, "the number of slots that constitute a unit of TB processing."

[0207] Furthermore, the multiple slots used for data transmission (e.g., PDSCH or PUSCH) may be temporally consecutive or non-contiguous. Also, the frequency resources (e.g., resource blocks) to which data is allocated in each of the multiple slots may be set individually (e.g., to different resources).

[0208] Also, the number of slots N slot The number of TBoMS transmission slots may be set here. In other words, the number of slots N slot This may correspond to the number of slots for TBoMS transmission.

[0209] Furthermore, the above setting methods may be combined. For example, the TB size may be determined based on information regarding the number of slots for TBoMS transmission of data, the scaling factor, and at least one of the number of slots used for data transmission (e.g., the number of time intervals). As an example, in the method for calculating the TB size, the calculated N info Furthermore, a scaling factor may be multiplied to it. For example, N info When a scaling factor less than 1 is multiplied to this, it becomes possible to transmit data at a lower MCS (or Spectral Efficiency), thereby expanding the coverage area.

[0210] Also, the number of slots N slot This can be an integer or a decimal. For example, N slot If = 2.5, then two slots and a half-slot (half of a slot) may be used for data transmission (e.g., PDSCH or PUSCH). Also, the number of slots N slot This can be expressed as the number of symbols used for data transmission. For example, N slot If =2, then 28 symbols, N slot If the value is 2.5, it may be expressed as 42 symbols.

[0211] Furthermore, the shorter the slot length, the more the decoding frequency (or number of attempts) of control information (e.g., PDCCH) can be reduced to once per slot (or fewer than the number of slots) for multiple slots, in order to reduce the processing load or power consumption of the terminal. In this case as well, as in the embodiment described above, determining the TB size based on the number of slots to which the data transmitted by multiple slots is allocated enables the transmission of data in amounts corresponding to the number of slots, thereby improving throughput. In addition to improving throughput, data transmission using multiple slots can also expand the coverage area where a certain data rate can be achieved.

[0212] Furthermore, while an example has been described in which data allocation (e.g., scheduling) is notified to terminal 200 by DCI, the invention is not limited to this. One embodiment of this disclosure can also be applied, for example, to transmissions using semi-persistent scheduling or configured grants that are scheduled periodically in advance. For example, the scaling factor may be notified (or set) to terminal 200 by the RRC message "SPS-Config" for semi-persistent scheduling. Alternatively, the scaling factor may be notified (or set) to terminal 200 by the RRC message "configuredGrantConfig" for configured uplink grants.

[0213] Furthermore, ACK / NACK is sometimes referred to as HARQ-ACK or HARQ-Feedback information.

[0214] Repetition is also sometimes called slot aggregation, slot bundling, TTI aggregation, or TTI bundling.

[0215] Furthermore, the number of repetitions mentioned above is the number of slots N used for data transmission (PDSCH or PUSCH). slot This can also be substituted. In other words, the number of repetitions is equal to the number of slots N. slot It may also be possible to accommodate this.

[0216] Furthermore, while the above-described embodiments described the transmission of uplink data (e.g., PUSCH), one embodiment of this disclosure may be applied to both downlink data (e.g., PDSCH) and uplink data, or it may be applied to one or the other without being applied to the other.

[0217] (Embodiment 2) In NR, as shown in Figure 2, if a PUCCH collision occurs in one or more of the multiple slots used to transmit PUSCH repetitions, the UCI and uplink data can be multiplexed and transmitted to the PUSCH in the one or more slots where the PUCCH and PUSCH collision occurs.

[0218] On the other hand, in TBoMS transmission, if the number of slots for multiplexing UCI increases, the transmission quality of PUSCH, for example, may deteriorate.

[0219] Therefore, in this second embodiment, a method is provided for controlling the amount of UCI resources to be multiplexed on PUSCH by varying whether or not UCI is multiplexed in TBoMS transmission, and / or the amount of UCI resources to be multiplexed on PUSCH on a slot-by-slot or repetition-by-repetition basis.

[0220] For example, the amount of UCI resources may be controlled by the following method. In the following, multiple slots in TBoMS transmission are referred to sequentially as the 0th to the nth slot (where n is an integer greater than or equal to 2) in the time direction. Also, a slot in TBoMS transmission may be abbreviated as a TBoMS transmission slot. In this case, TBoMS transmission slots prior to the nth slot may be, for example, the 0th to the (n-1)th slot.

[0221] <option 1> For example, if a PUCCH collision occurs in the nth slot of a TBoMS transmission, and it has already been decided that UCI will be multiplexed in at least one of the TBoMS transmission slots prior to the nth slot, then the nth slot will be dropped without multiplexing the UCI.

[0222] < / option> <option 2> If a PUCCH collision occurs in the nth slot of a TBoMS transmission, and it has already been decided that UCIs will be multiplexed in a TBoMS transmission slot prior to the nth slot, then some UCIs will not be multiplexed in the nth slot and will be dropped.

[0223] For example, some UCIs may be low-priority UCIs. For example, low-priority UCIs may be CSIs. Also, if a CSI has CSI part 1 and CSI part 2, a UCI may include CSI part 2, or it may include CSI part 1 and CSI part 2.

[0224] < / option> <option 3> In equations (1), (8), (11), and (12), either or both of the parameter β that controls the coding rate of UCI and the parameter α that controls the upper limit of the amount of UCI resources may be extended to TBoMS transmission.

[0225] For example, if a PUCCH collision occurs in the nth slot of a TBoMS transmission, the value of parameter β or parameter α will differ depending on whether it has already been determined that UCIs will be multiplexed in the TBoMS transmission slots prior to the nth slot, or whether it has not been determined that UCIs will be multiplexed.

[0226] For example, for each of the parameters β and α, there are two candidate elements {β,β ext } and {α,α ext } may be set. And if a PUCCH collision occurs in the nth slot of TBoMS transmission and it is determined that UCI will not be multiplexed in the TBoMS transmission slots prior to the nth slot, the amount of UCI resources may be calculated using β and α. On the other hand, if a PUCCH collision occurs in the nth slot of TBoMS transmission and it is determined that UCI will be multiplexed in the TBoMS transmission slots prior to the nth slot, β ext and α ext The amount of UCI resources may be calculated using the following method. Here, β and α may be parameters used in the calculation of UCI resources as used in NR Rel.15 / 16.

[0227] In the example above, both parameter β and parameter α are set depending on whether or not UCI is duplicated. However, either parameter β or parameter α may be set depending on whether or not UCI is duplicated, while the other may be set regardless of whether or not UCI is duplicated.

[0228] In Option 3, the candidate elements for parameters β and α are not limited to two; three or more candidate elements may be set. In this case, the elements used may differ depending on the number of slots in which UCI is multiplexed in the TBoMS transmission slots prior to the nth slot. For example, there may be three candidate elements for each of β and α {β, β ext1 ,β ext2 } and {α,α ext1 ,α ext2 } may be set. And if a PUCCH collision occurs in the nth slot of TBoMS transmission, and if the number of slots in which UCI is multiplexed in the TBoMS transmission slots prior to the nth slot is 1, then β ext1 and α ext1 The amount of UCI resources may be calculated using β, on the other hand, if the number of slots in which UCI is multiplexed in TBoMS transmission slots prior to the nth slot is two or more, ext2 and α ext2 The amount of UCI resources may be calculated using this method.

[0229] Figures 9A and 9B show an example of this second embodiment. Figures 9A and 9B show the TBoMS transmission slot (labeled "TBoMS PUSCH" in Figures 9A and 9B) and the PUCCH slot. The horizontal axis in Figures 9A and 9B represents the time axis. The TBoMS transmission slots are assigned identification numbers from #0 (n=0) to #3 (n=3).

[0230] In Figure 9A, we focus on the second slot (n=2) of the TBoMS transmission. In Figure 9A, the UCI is multiplexed in the 0th slot preceding the second slot. Therefore, in the second slot, we can either drop the UCI without multiplexing it (for example, option 1), or in the second slot, β ext and α ext The UCI calculated using this method may be duplicated (for example, option 3).

[0231] In Figure 9B, we focus on the second TBoMS transmission slot (n=2). In Figure 9B, the UCI is not multiplexed in the 0th and 1st TBoMS transmission slots preceding the second slot. Therefore, in the second slot, we must use a method that multiplexes the UCI without dropping it (e.g., option 1). Alternatively, in the second slot, β ext and α ext The UCI calculated using this method may be duplicated (for example, option 3).

[0232] Next, an example of operation in this second embodiment will be described. Figure 10 is a flowchart showing an example of operation of terminal 200 in this second embodiment. The flow shown in Figure 10 is a flow that shows the operation of determining whether or not to duplicate the UCI in the nth slot (nth slot), or calculating the amount of resources for the UCI to be duplicated.

[0233] Terminal 200 determines whether the transmission resources for PUCCH transmission and PUSCH transmission overlap in time in the nth slot (S61).

[0234] In the nth slot, if the transmission resources for PUCCH transmission and PUSCH transmission do not overlap in time (No in S61), terminal 200 uses the PUCCH transmission resource that does not overlap to send the UCI (S62). Then the flow in Figure 10 ends.

[0235] If the transmission resources for PUCCH transmission and PUCCH transmission overlap in time (Yes in S61), terminal 200 determines whether UCI is multiplexed in a slot prior to the nth slot (whether it has been decided that it will be multiplexed) (S63).

[0236] If UCI is duplicated in a slot prior to the nth slot (Yes in S63), terminal 200 will drop some or all of the UCI (apply Option 1 or Option 2), or β ext and α ext The amount of UCI resources is calculated using (Option 3 is applied) (S64). Then, the flow in Figure 10 is completed.

[0237] If UCI is not multiplexed in a slot prior to the nth slot (No in S63), terminal 200 either multiplexes UCI (applies Option 1 or Option 2) or calculates the amount of UCI resources using β and α (applies Option 3) (S65). Then the flow in Figure 10 ends.

[0238] As described above, according to Embodiment 2, the amount of UCI resources and whether or not UCI multiplexing is possible in a certain TBoMS transmission slot (for example, the second slot in Figures 9A and 9B) can be determined by considering the UCI multiplexing status in the TBoMS transmission slots preceding that TBoMS transmission slot (for example, the 0th and 1st slots in Figures 9A and 9B). Therefore, in TBoMS transmission, the degradation of PUSCH transmission quality can be suppressed by increasing the number of slots that multiplex UCI.

[0239] (modified version) Furthermore, among the above-mentioned Options 1 to 3, the applicable option may differ depending on the number of slots used for TBoMS transmission. For example, if the number of slots used for TBoMS transmission is relatively small (e.g., 2 slots), Option 3 may be applied, and if the number of slots used for TBoMS transmission is relatively large (e.g., 4 to 8 slots), Option 1 may be applied. By applying Option 1 when the coverage expansion degree is high and the number of slots used for TBoMS transmission is large, and not increasing the number of slots to which UCI is multiplexed, it is possible to prevent deterioration of the transmission quality of PUSCH.

[0240] Furthermore, the elements of parameter β and / or parameter α applied in Option 3 may differ depending on the number of slots used for TBoMS transmission. For example, parameter β or parameter α may have two elements {β, β ext} and {α, α ext This explains the case where} is set. In this case, even if the number of slots used for TBoMS transmission is relatively small (e.g., 2 slots), and it has been determined that UCI will be multiplexed in TBoMS transmission slots prior to the nth slot, the amount of UCI resources can be calculated using β and / or α. On the other hand, if the number of slots used for TBoMS transmission is relatively large (e.g., 4 or 8 slots), and it has been determined that UCI will be multiplexed in TBoMS transmission slots prior to the nth slot, β ext and / or α ext The amount of UCI resources can be calculated using this method. When the coverage scalability is high and a large number of slots are required for TBoMS transmission, using parameters that minimize UCI multiplexing can prevent degradation of PUSCH transmission quality.

[0241] Depending on the type of UCI, such as ACK / NACK, CSI part 1, and CSI part 2, the elements of parameter β and / or parameter α applied in Option 3 may differ. For example, for ACK / NACK, β and / or α (e.g., the parameters used to calculate the existing UCI resource amount used in NR Rel. 15 / 16) may be used regardless of whether UCI is multiplexed in TBoMS transmission slots prior to the nth slot. On the other hand, for CSI, if it has been determined that UCI is multiplexed in TBoMS transmission slots prior to the nth slot, β ext and / or α ext The amount of UCI resources can be calculated using [this method]. By avoiding multiplexing of UCIs with relatively low priority as much as possible, it is possible to prevent degradation of PUSCH transmission quality while suppressing degradation of downlink transmission efficiency.

[0242] Furthermore, in TBoMS transmission, the number of slots on which UCI can be multiplexed may be defined by specifications (standards), etc., or set by RRC, etc. If the number of slots on which UCI can be multiplexed is N (where N is an integer greater than or equal to 1), and it has been determined that UCI will be multiplexed in N slots within the TBoMS transmission slots prior to the nth slot, then the UCI may not be multiplexed in the nth slot and may be dropped. The value of N may be defined by specifications (standards), etc., such as N=2 and N=4, or set by RRC, etc. Alternatively, it may be implicitly determined according to the number of slots used for TBoMS transmission.

[0243] (Embodiment 3) In embodiments 1 and 2 described above, the case in which UCI and uplink data are multiplexed to PUSCH when the transmission resources for PUCCH and PUSCH overlap in time during uplink transmission from terminal 200 was explained. NR Rel.15 has a constraint that the PUCCH resource, which transmits an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns PUSCH, cannot be assigned to a resource that overlaps in time with the transmission of PUSCH assigned by the first DCI.

[0244] Figure 11 illustrates the constraints of UCI (Uplink Control Information) on PUSCH in NR Rel.15 / 16. For example, as shown in the upper part of Figure 11, if a first DCI assigning PUSCH to slot #3 is received in slot #0, and then a second DCI assigning PDSCH to slot #1 is received, the resources for sending ACK / NACK to PDSCH will not be allocated to resources that overlap temporally with the transmission of PUSCH (slot #3).

[0245] Therefore, NR Rel.15 / 16 does not support the UE multiplexing an ACK / NACK for a PDSCH assigned by a second DCI after receiving a first DCI that assigns a PUSCH, and then transmitting that ACK / NACK to the PUSCH assigned by the first DCI.

[0246] Therefore, the PUCCH resource for sending an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns the PUSCH is allocated to a resource (e.g., slot #4) that does not temporally overlap with the transmission of the PUSCH assigned by the first DCI (e.g., slot #3), as shown in the lower part of Figure 11.

[0247] On the other hand, in PUSCH transmission using multiple slots (for example, TBoMS transmission), the PUSCH transmission slot may occupy an uplink slot.

[0248] In this case, given the constraint described above that "it is not permitted to allocate a PUCCH resource that sends an ACK / NACK to a PDSCH assigned by a second DCI after receiving a first DCI that assigns a PUSCH to a resource that overlaps in time with the transmission of a PUSCH assigned by the first DCI," for example, as shown in Figure 12, terminal 200 will not send an ACK / NACK to the PDSCH until the TBoMS transmission is complete. As a result, the delay of the downlink, where data transmission is controlled based on the ACK / NACK from terminal 200, may increase.

[0249] Furthermore, the control information included in the DCI that assigns the PDSCH may include timing information (K1 or PDSCH-to-HARQ_feedback timing indication) such as how many slots after receiving the PDSCH the PUCCH should be transmitted, but the range of K1 values ​​that can be notified is limited. Therefore, with the constraints mentioned above, blocking of PDSCH assignment may occur due to the inability to assign PUCCH, which can reduce the frequency utilization efficiency of the downlink.

[0250] To improve frequency utilization efficiency and reduce latency in downlink transmission, it is desirable to remove the constraint mentioned above, which states that "a PUCCH resource that sends an ACK / NACK to a PDSCH assigned by a second DCI after receiving a first DCI that assigns a PUSCH cannot be allocated to a resource that temporally overlaps with the transmission of a PUSCH assigned by the first DCI."

[0251] For example, it is permissible to allocate a PUCCH resource that sends an ACK / NACK to a PDSCH assigned by a second DCI after receiving a first DCI that assigns a PUSCH to a resource that overlaps in time with the transmission of the PUSCH assigned by the first DCI.

[0252] However, the coverage performance of PUSCH may degrade because some of the PUSCH resources are overloaded with sending ACK / NACKs to the PDSCH allocated by the second DCI.

[0253] This third embodiment describes a method for improving the frequency utilization efficiency and reducing delay of downlink transmission, and for mitigating the degradation of PUSCH's coverage performance, when terminal 200 performs TBoMS transmission of PUSCH.

[0254] For example, a PUCCH resource that sends an ACK / NACK to a PDSCH assigned by a second DCI after receiving a first DCI that assigns a PUSCH may be assigned to a resource that overlaps in time with the transmission of the PUSCH assigned by the first DCI. Then, depending on whether the PUCCH resource that sends an ACK / NACK to a PDSCH assigned by a second DCI after receiving a first DCI overlaps in time with the transmission of the PUSCH assigned by the first DCI, at least one of the ACK / NACK transmission method, the number of bits of the ACK / NACK transmitted, or the PUSCH repetition transmission resource is controlled.

[0255] As an example, this third embodiment will describe the following three methods.

[0256] <Method 1> Method 1 in this third embodiment will be described.

[0257] If TBoMS transmission is applied to terminal 200, method 1 allows the PUCCH resource, which sends an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns the PUSCH, to be assigned to a resource that overlaps in time with the transmission of the PUSCH assigned by the first DCI.

[0258] For example, in a slot where the transmission resources for PUCCH and PUSCH overlap in time, the ACK / NACK for the PDSCH allocated by the second DCI is transmitted by puncturing a portion of the PUSCH resource allocated by the first DCI. However, the number of bits of the ACK / NACK for the PDSCH allocated by the second DCI that can be transmitted by puncturing a portion of the PUSCH resource allocated by the first DCI is limited to X bits. If the number of bits of the ACK / NACK for the PDSCH allocated by the second DCI exceeds X bits, ACK / NACK bundling (compression of ACK / NACK bits) is applied to reduce the number of ACK / NACK bits actually transmitted to X bits or less, and then the ACK / NACK is transmitted by puncturing a portion of the PUSCH resource allocated by the first DCI.

[0259] Here, the value of X may be a value predetermined in the standard (e.g., X=2 bits), a value statically set by RRC signaling, a value set by notification in MAC-CE (Medium Access Control - Control Element), a value dynamically notified by DCI, or a value implicitly determined, or any combination thereof. If the value of X is implicitly determined, for example, it may be determined based on the number of slots used for PUSCH transmission, or it may be determined from other parameters set in the terminal.

[0260] Next, we will describe an example of the operation of terminal 200 to which Method 1 is applied.

[0261] Figure 13 is a flowchart showing an example of the operation of Method 1 in this embodiment 3. As shown in Figure 13, terminal 200, for example, after receiving a first DCI for assigning PUSCH from base station 100 (after S101), determines whether or not TBoMS transmission is applied (S102).

[0262] If TBoMS transmission is not applied (S102; No), terminal 200 does not allow the PUCCH resource, which transmits an ACK / NACK to a PDSCH assigned by a second DCI after receiving a first DCI that assigns a PUSCH, to be allocated to a resource that overlaps in time with the transmission of the PUSCH assigned by the first DCI (S108). For example, terminal 200 may transmit a PUCCH using a resource that does not overlap in time with the transmission of the PUSCH, in an operation equivalent to the operation supported in NR Rel. 15 / 16.

[0263] If TBoMS transmission is applied (S102; Yes), terminal 200 allows, for example, the allocation of a PUCCH resource that sends an ACK / NACK to a PDSCH assigned by a second DCI after receiving a first DCI that allocates a PUSCH to a resource that overlaps in time with the transmission of the PUSCH assigned by the first DCI (S103).

[0264] When terminal 200 receives a second DCI that assigns a PDSCH (S104), it determines, for example, whether the PUCCH assigned by the second DCI and the PUSCH transmission resource assigned by the first DCI overlap in time (S105).

[0265] If the resources for PUCCH and PUSCH overlap in time (S105; Yes), terminal 200 may, for example, puncture a portion of the PUSCH resources allocated by the first DCI and send an ACK / NACK to the PDSCH allocated by the second DCI using the punctured resources (S106). In other words, terminal 200 may use (or reallocate) a portion of the resources allocated for PUSCH by the first DCI as resources for PUCCH and send an ACK / NACK to the PDSCH allocated by the second DCI. Note that the puncture may be performed, for example, by avoiding resources to which a reference signal (e.g., demodulation reference signal (DMRS)) is mapped in PUSCH.

[0266] Here, the number of ACK / NACK bits that can be punctured and sent (to the PDSCH allocated by the second DCI) by a portion of the PUSCH resources allocated by the first DCI may be limited to, for example, a threshold (e.g., X bits).

[0267] If the number of ACK / NACK bits to be sent to the PDSCH allocated by the second DCI exceeds X bits, terminal 200 may apply ACK / NACK bundling (e.g., compression of ACK / NACK bits) to reduce the actual number of ACK / NACK bits sent to X (bits) or less. For example, terminal 200 may puncture a portion of the PUSCH resources allocated by the first DCI according to the number of ACK / NACK bits reduced to X bits or less and send the ACK / NACK. Here, X is a positive integer value greater than 0.

[0268] The value of X may be determined, for example, based on the required coverage performance of PUSCH. Alternatively, the value of X may be determined by a predetermined value in the standard (e.g., X=2 bits), a value statically set by RRC signaling, a value set by notification in MAC-CE (Medium Access Control - Control Element), a value dynamically notified by DCI, or an implicitly determined value, or any combination thereof. A non-exclusive example of how the value of X may be implicitly determined is that it may be determined based on the number of PUSCH repetitions, or based on other information or parameters set in terminal 200.

[0269] If the transmission resources for the PUCCH assigned by the second DCI and the PUSCH assigned by the first DCI do not overlap in time (S105; No), terminal 200 may, for example, send an ACK / NACK to the PDSCH assigned by the second DCI using the PUCCH assigned by the second DCI (S107).

[0270] Figure 14 shows an example of the operation of Method 1. As illustrated in Figure 14, the first DCI in slot #0 assigns slot #3 as the timing for transmitting PUSCH. Terminal 200 transmits TBoMS in slots #3, #4, #7, and #8. In this disclosure, "slot" is an example of a time resource unit, and other units may be used.

[0271] Furthermore, a PDSCH is allocated in slot #1 by the second DCI, and a PUCCH resource to send ACK / NACK to the PDSCH is allocated in slot #3. In this case, in slot #3, where the transmission resources for PUCCH and PUSCH overlap in time, the ACK / NACK to the PDSCH allocated by the second DCI is transmitted by puncturing a portion of the PUSCH resource. Here, the number of ACK / NACK bits transmitted is less than or equal to X bits.

[0272] As described above, according to Method 1, when terminal 200 performs a TBoMS transmission, it is permitted to allocate the PUCCH resource for sending an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns the PUSCH to a resource that temporally overlaps with the transmission of the PUSCH assigned by the first DCI. Therefore, it is possible to improve the frequency utilization efficiency and reduce the delay of downlink transmission.

[0273] Furthermore, by appropriately setting the value of X to limit the number of ACK / NACK bits for the PDSCH allocated by the second DCI, which transmits a portion of the PUSCH resources allocated by the first DCI by puncturing them, to X bits or less, the degradation of PUSCH coverage performance can be mitigated.

[0274] <Method 2> Method 2 in this third embodiment will now be described.

[0275] Figure 15 is a flowchart showing an example of the operation of terminal 200 to which Method 2 is applied. In Figure 15, the processes S101 to S105, S107 and S108, excluding S106a, may be the same as the processes exemplified in Figure 13.

[0276] In Method 2, similar to Method 1, if TBoMS transmission is applied to terminal 200, the PUCCH resource that sends an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns the PUSCH is allowed to be assigned to a resource that overlaps in time with the transmission of the PUSCH assigned by the first DCI.

[0277] In Method 2, in slots where the transmission resources for PUCCH and PUSCH overlap in time, ACK / NACKs for PDSCH assigned by the second DCI are treated as higher priority transmissions than PUSCH assigned by the first DCI. For example, slots where the transmission resources for PUCCH and PUSCH overlap in time may be set as unavailable slots for PUSCH transmission.

[0278] In this case, terminal 200 may send an ACK / NACK using the PUCCH resource allocated by the second DCI, and postpone the TBoMS transmission of the PUSCH allocated by the first DCI, for example, to a later time (S106a).

[0279] Figure 16 shows an example of the operation of Method 2. The first DCI in slot #0 assigns slot #3 as the timing for sending PUSCH. Also, the second DCI in slot #1 assigns PDSCH, and the PUCCH resource for sending ACK / NACK to PDSCH is assigned to slot #3.

[0280] In this case, in slot #3, where the transmission resources for PUCCH and PUSCH overlap in time, ACK / NACK is treated as a higher priority transmission than PUSCH, and slot #3 is set as an unavailable slot for PUSCH transmission. Therefore, in slot #3, terminal 200 transmits ACK / NACK, which has a higher priority than PUSCH, using the PUCCH resource.

[0281] On the other hand, in TBoMS transmission, the number of slots is counted based on the uplink slots available for PUSCH transmission. Therefore, terminal 200 transmits PUSCH using slots #4, #7, #8, and #9, which are uplink slots available for TBoMS transmission.

[0282] As described above, according to Method 2, when terminal 200 performs a TBoMS transmission, it is permitted to allocate the PUCCH resource for sending an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns the PUSCH to a resource that temporally overlaps with the transmission of the PUSCH assigned by the first DCI. Therefore, it is possible to improve the frequency utilization efficiency and reduce the delay of downlink transmission.

[0283] Furthermore, in Method 2, slots where the transmission resources for PUCCH and PUSCH overlap in time are set as unavailable slots for PUSCH transmission, so terminal 200 can perform TBoMS transmission in a later slot (postpone). Therefore, terminal 200 can perform PUSCH transmission (TBoMS transmission) without being affected by PUSCH resource congestion due to ACK / NACK, thus avoiding or suppressing degradation of PUSCH coverage performance.

[0284] <Method 3> Method 3 in this third embodiment will now be described.

[0285] Figure 17 is a flowchart showing an example of the operation of terminal 200 to which Method 3 is applied. In Figure 17, the processes S101 to S105, S107 and S108, excluding S106b, may be the same as the processes exemplified in Figure 13.

[0286] In Method 3, as in Methods 1 and 2, if TBoMS transmission is applied to terminal 200, the PUCCH resource that sends an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns the PUSCH is allowed to be assigned to a resource that overlaps in time with the transmission of the PUSCH assigned by the first DCI.

[0287] Furthermore, in Method 3, if the PUCCH resource that sends an ACK / NACK to the PDSCH assigned by the second DCI overlaps in time with the transmission of a PUSCH assigned by the first DCI, the HARQ process of the PDSCH assigned by the second DCI may be disabled (S106b).

[0288] In other words, if a PUCCH resource that sends an ACK / NACK to a PDSCH assigned by the second DCI overlaps in time with the transmission of a PUSCH assigned by the first DCI, terminal 200 will not send an ACK / NACK to the PDSCH assigned by the second DCI.

[0289] Figure 18 shows an example of the operation of Method 3. The first DCI in slot #0 assigns slot #3 as the timing for sending PUSCH. Terminal 200 performs TBoMS transmissions in slots #3, #4, #7, and #8.

[0290] Additionally, a PDSCH is allocated in slot #1 by the second DCI, and a PUCCH resource to send ACK / NACK to the PDSCH is allocated to slot #3. In this case, the HARQ process for the PDSCH allocated in slot #1 by the second DCI is disabled, and terminal 200 does not send ACK / NACK in slot #3.

[0291] As described above, Method 3, similar to Methods 1 and 2, allows terminal 200 to allocate the PUCCH resource for sending an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns the PUSCH, to a resource that temporally overlaps with the transmission of the PUSCH assigned by the first DCI when terminal 200 performs a TBoMS transmission. Therefore, it is possible to improve the frequency utilization efficiency and reduce the delay of downlink transmission.

[0292] Furthermore, according to Method 3, if the PUCCH resource sending ACK / NACK to the PDSCH allocated by the second DCI overlaps in time with the PUSCH transmission allocated by the first DCI, the HARQ process of the PDSCH allocated by the second DCI is disabled. Therefore, terminal 200 can send PUSCH (TBoMS transmission) without being affected by the PUSCH resource being punctured by ACK / NACK. As a result, degradation of PUSCH coverage performance can be avoided or suppressed.

[0293] Furthermore, from the perspective of the base station 100, for example, it is possible to assign (or schedule) a PDSCH without waiting for the reception of HARQ-ACK feedback from the terminal 200, thus improving the flexibility of scheduling.

[0294] Disabling the HARQ process can lead to a degradation in the retransmission efficiency of downlink transmissions. However, this degradation in retransmission efficiency can be mitigated by applying a process that appropriately sets the reliability of the PDSCH, such as increasing the confidence of the initial transmission (for example, by adjusting the Modulation and Coding Scheme, MCS, or allocated resource amount) when the HARQ process is disabled.

[0295] Furthermore, in TBoMS transmission, in Embodiment 1<RM-Approach 1> When using this method, the number of bits corresponding to the resource amount of the number of slots (an integer of 2 or more) used for PUSCH transmission is read from a predetermined RV position and mapped to a PUSCH resource spanning multiple slots. This unit of TBoMS transmission consisting of multiple slots is treated as one TBoMS transmission unit, and by repeatedly transmitting (repetitioning) one TBoMS transmission unit, PUSCH coverage can be improved. For example, in Embodiment 3, one resource (slot) of TBoMS transmission may be considered as one TBoMS transmission unit. For example, in Figure 10, each of the four TBoMS transmission slots may be considered as one TBoMS transmission unit. Alternatively, when treating a unit of TBoMS transmission consisting of multiple slots as one TBoMS transmission unit and repeatedly transmitting (repetitioning) one TBoMS transmission unit, Embodiment 3 may be applied by replacing the slot unit with 1 TBoMS transmission unit.

[0296] Furthermore, the applicable embodiment may differ depending on which slot in the TBoMS transmission the PUCCH resource that sends the ACK / NACK to the PDSCH allocated in the first DCI conflicts with. For example, if it conflicts with the first slot of the TBoMS, Embodiment 1 may be applied, and if it conflicts with a slot other than the first slot of the TBoMS, Embodiment 2 may be applied. Alternatively, if it conflicts with the first slot of the TBoMS, Embodiment 3 may be applied, and if it conflicts with a slot other than the first slot of the TBoMS, Embodiment 2 may be applied.

[0297] If a PUCCH collision occurs in the nth slot of a TBoMS transmission, the method applied may differ depending on whether or not UCI multiplexing has already been determined in the TBoMS transmission slots prior to the nth slot. For example, if a PUCCH collision occurs in the nth slot of a TBoMS transmission, and UCI multiplexing has already been determined in the TBoMS transmission slots prior to the nth slot, then method 2 or method 3 may be applied to the nth slot. If UCI multiplexing has not been determined in the TBoMS transmission slots prior to the nth slot, then method 1 may be applied. Since the amount of UCI multiplexing resources or the feasibility of UCI multiplexing in a TBoMS transmission can be determined by considering the UCI multiplexing status in the preceding slots, the degradation of PUSCH transmission quality due to an increase in the number of slots that multiplex UCI in a TBoMS transmission can be suppressed.

[0298] (Variation 1) In this modified example 1 of Embodiment 3, when TBoMS transmission is applied to terminal 200, the PUCCH resource that transmits an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns the PUSCH is allowed to be assigned to a resource that overlaps in time with the transmission of the PUSCH assigned by the first DCI.

[0299] Furthermore, in this modified example, if the PUCCH resource that sends an ACK / NACK to the PDSCH assigned by the second DCI overlaps in time with the transmission of a PUSCH assigned by the first DCI, ACK skipping may be applied to the HARQ process of the PDSCH assigned by the second DCI.

[0300] When ACK skipping is applied to the HARQ process, terminal 200 does not send an ACK / NACK to the PDSCH if the decryption result to the PDSCH is an ACK. Since the probability of the decryption result to the PDSCH being an ACK tends to be higher than the probability of it being a NACK, skipping the ACK transmission can reduce overhead, for example, that of the PUCCH, and also reduce the processing load on terminal 200.

[0301] This modified example can be understood as being equivalent to applying Method 3 when the decoding result for the PDSCH assigned by the second DCI is ACK. On the other hand, when the decoding result for the PDSCH assigned by the second DCI is NACK, either Method 1 or Method 2 may be applied.

[0302] According to this modified version, if the decoding result of the PDSCH assigned by the second DCI is NACK, a PUSCH resource puncture or a PUSCH transmission postpone is applied, thereby mitigating the impact on TBoMS transmission.

[0303] (Modification 2) In methods 1, 2, and 3 described above, when TBoMS transmission of PUSCH is applied to terminal 200, the PUCCH resource that sends an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns PUSCH is allowed to be assigned to a resource that overlaps in time with the transmission of PUSCH assigned by the first DCI.

[0304] Here, the slot in which the transmission resources for PUCCH and PUSCH overlap in time can be any slot among the TBoMS transmissions allocated by the first DCI. For example, the slot in which the transmission resources for PUCCH and PUSCH overlap in time can be the first slot of the TBoMS transmission, as illustrated in Figures 14, 16, and 18, or it can be a different slot from the first slot.

[0305] Furthermore, depending on which slot in the TBoMS transmission the PUCCH resource that sends an ACK / NACK to the PDSCH assigned by the first DCI overlaps with (or clashes with) may be used, the method applied from methods 1, 2, and 3 may be different.

[0306] As a non-restrictive example, if a PUCCH resource sending an ACK / NACK collides with the first slot (MS#0) of a TBoMS transmission, as shown in Figure 19, Method 1 may be applied. If it collides with a slot different from the first slot of a TBoMS transmission (for example, MS#1), as shown in Figure 20, Method 2 may be applied.

[0307] As an additional, non-restrictive example, if a PUCCH resource sending an ACK / NACK conflicts with the first slot of a TBoMS transmission, Method 3 may be applied, and if a PUCCH resource sending an ACK / NACK conflicts with a slot different from the first slot of a TBoMS transmission, Method 2 may be applied.

[0308] According to this modified version, for example, based on the time required for terminal operations (or processes) such as puncture, postpone, or HARQ disable, an appropriate operation or process according to the terminal's capabilities can be applied to terminal 200.

[0309] (Variation 3) NR Rel.16 allows prioritization of uplink transmissions such as PUSCH or ACK / NACK. For example, NR Rel.16 has two priority levels; uplink transmissions with priority index 0 are low priority, and uplink transmissions with priority index 1 are high priority.

[0310] In this modified version, the method applied from methods 1, 2, and 3 may differ depending on the priority of ACK / NACK, the priority of PUSCH, or both.

[0311] Figure 21 shows an example of how to differentiate between cases based on the priority of ACK / NACK and the priority of PUSCH. For example, method 1 may be applied in Case 1 or Case 4 (ACK / NACK and PUSCH have the same priority), method 3 in Case 2 (PUSCH has a higher priority than ACK / NACK), and method 2 in Case 3 (ACK / NACK has a higher priority than PUSCH).

[0312] Note that the combinations of methods applicable to each case are not limited to those listed above. For example, method 2 or 3 may be applied to Case 1 or Case 4.

[0313] According to this modified version, if ACK / NACK has high priority, Method 2 can be applied to prioritize the transmission of ACK / NACK while postponing PUSCH to compensate for PUSCH coverage. Furthermore, if PUSCH has high priority, Method 3 can be applied to transmit PUSCH using resources allocated by DCI, compensating for both coverage and delay. In this way, appropriate uplink transmission can be achieved based on the priority of ACK / NACK or PUSCH.

[0314] (Modification 4) If a PUCCH collision occurs in the nth TBoMS transmission slot, the method applied may differ depending on whether or not UCI has already been multiplexed in the TBoMS transmission slots prior to the nth slot. For example, if a PUCCH collision occurs in the nth TBoMS transmission slot and it has been determined that UCI has already been multiplexed in the TBoMS transmission slots prior to the nth slot, then method 2 or method 3 may be applied to the nth slot. For example, if a PUCCH collision occurs in the nth TBoMS transmission slot and it has been determined that UCI will not be multiplexed in the TBoMS transmission slots prior to the nth slot, then method 1 may be applied.

[0315] In TBoMS transmission, the amount of UCI multiplexing resources or whether UCI multiplexing is possible can be determined by considering the UCI multiplexing status in slots prior to the slot where PUCCH and PUSCH conflict. Therefore, in TBoMS transmission, the degradation of PUSCH transmission quality due to an increase in the number of slots that multiplex UCI can be suppressed.

[0316] (Other variation 1) In this third embodiment, when TBoMS transmission of PUSCH is applied to terminal 200, the PUCCH resource that transmits an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns PUSCH is allowed to be assigned to a resource that overlaps in time with the transmission of PUSCH assigned by the first DCI, thereby applying either the method or a modified version described above.

[0317] Here, for example, the above method or its variations may be applied when the number of resources (slots) for TBoMS transmission is greater than the threshold. Furthermore, the method applied may differ depending on the number of PUSCH iterations.

[0318] Furthermore, the method of application or modifications may differ depending on the number of ACK / NACK bits. Also, for example, the method of application or modifications may differ depending on whether the number of ACK / NACK bits is less than or equal to a threshold (e.g., X bits as described above), or whether the number of ACK / NACK bits can be compressed to less than or equal to the threshold.

[0319] The number of bits in the ACK / NACK may be, for example, the number of bits in the ACK / NACK for the PDSCH assigned by the second DCI, or it may be the sum of the bits in the ACK / NACK for the PDSCH assigned by the second DCI and the ACK / NACK for the PDSCH assigned by the DCI before receiving the first DCI.

[0320] In the former example, since we don't need to consider the number of ACK / NACK bits assigned to the PDSCH by the DCI received before the second DCI, we can mitigate potential constraints on the allocation of ACK / NACK to the PUCCH resource. In other words, we can improve the degree of freedom in allocating ACK / NACK to the PUCCH resource.

[0321] The latter example is useful in cases where ACK / NACKs for PDSCHs allocated by multiple DCIs are multiplexed into the UCI and transmitted in PUCCH. For example, it can reduce PUSCH resource puncture, thus avoiding or mitigating a decrease in PUSCH coverage performance.

[0322] Furthermore, in Method 1, the number of ACK / NACK bits may be the number of bits before ACK / NACK bundling, or the number of bits after ACK / NACK bundling.

[0323] (Other variations 2) In embodiments 1, 2, and 3 described above, when TBoMS transmission of PUSCH is applied to terminal 200, it is permitted to allocate the PUCCH resource that sends an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns PUSCH to a resource that overlaps in time with the transmission of PUSCH assigned by the first DCI.

[0324] Here, the slot in which the transmission resources for PUCCH and PUSCH overlap in time can be any slot among the TBoMS transmissions allocated by the first DCI. For example, the slot in which the transmission resources for PUCCH and PUSCH overlap in time can be the first slot of the TBoMS transmission, or it can be a different slot from the first slot.

[0325] Furthermore, depending on which slot in the TBoMS transmission the PUCCH resource that sends ACK / NACK to the PDSCH assigned by the first DCI overlaps with (or clashes with) may be used, the applicable embodiment from Embodiments 1, 2, and 3 may be different.

[0326] As a non-limiting example, if a PUCCH resource sending an ACK / NACK conflicts with the first slot, Embodiment 1 may be applied, and if it conflicts with a slot different from the first slot for TBoMS transmission, Embodiment 2 may be applied.

[0327] Furthermore, as a non-limiting example, if a PUCCH resource sending an ACK / NACK conflicts with the first slot of a TBoMS transmission, Embodiment 3 may be applied, and if a PUCCH resource sending an ACK / NACK conflicts with a slot different from the first slot of a TBoMS transmission, Embodiment 2 may be applied.

[0328] According to this modified version, for example, based on the time required for terminal operations (or processes) such as puncture, postpone, or HARQ disable, an appropriate operation or process according to the terminal's capabilities can be applied to terminal 200.

[0329] The following provides supplementary information to this disclosure, including each of the embodiments and variations described above.

[0330] (Supplement 1) In TBoMS transmission, the number of slots is counted based on the uplink slots available for PUSCH transmission, but any of the following determination methods may be applied to determine which uplink slots are available for PUSCH transmission.

[0331] <Decision method 1> The determination of the uplink slot available for PUSCH transmission may depend on RRC signaling. For example, RRC signaling may include TDD uplink / downlink slot format notifications (e.g., semi-static slot format indicator (SFI)).

[0332] <Decision method 2> The determination of which uplink slots are available for PUSCH transmissions may depend, for example, on notifications from the DCI that allocate resources for RRC signaling and TBoMS transmissions. For example, RRC signaling may include notifications of the uplink / downlink slot format of the TDD (e.g., semi-static SFI). The DCI that allocates resources for TBoMS transmissions may directly (or explicitly) notify of slots unavailable for PUSCH transmissions, or it may instruct whether to invalidate or enable invalid uplink slots / symbols notified by RRC signaling.

[0333] <Decision method 3> The determination of uplink slots available for PUSCH transmissions may depend, for example, on notifications via RRC signaling, DCI for allocating TBoMS transmission resources, and dynamic SFIs. For example, RRC signaling may include TDD uplink / downlink slot format notifications (e.g., semi-static SFIs). DCI for allocating TBoMS transmission resources may directly (or explicitly) notify of unavailable slots for PUSCH transmissions, or instruct whether to invalidate or enable invalid uplink slots / symbols notified by RRC signaling. Dynamic SFIs may include, for example, TDD uplink / downlink slot format notifications (dynamic SFIs) notified by Group-common PDCCHs.

[0334] The relationship between the method for determining the uplink slot available for PUSCH transmission and each method in Embodiment 3 is as follows, for example.

[0335] Method 1 may be applied to any of Determination Methods 1, 2, and 3. Method 2 is preferably applied in conjunction with Determination Method 3, for example, because a second DCI after receiving a first DCI assigning a PUSCH can be processed as a notification similar to the Dynamic SFI of Determination Method 3. However, Method 2 may be applied to other determination methods. Method 3 may be applied to any of Determination Methods 1, 2, and 3.

[0336] (Supplement 2) The embodiments and modifications described above illustrate the application of PUSCH to TBoMS transmission as an example, but the disclosure is not limited thereto. For example, the disclosure may be applied to PUSCH repetition. For example, the PUSCH repetition method may be PUSCH repetition Type A enhancement or PUSCH repetition Type B.

[0337] Furthermore, the above-described embodiments or modifications may be applied only to specific TBoMS transmissions. Also, the applicable embodiments or modifications may differ depending on the TBoMS transmission method.

[0338] (Supplement 3) In the embodiments and modifications described above, examples of application to slot-unit PUCCH transmission were explained, but the transmission unit of PUCCH is not limited to slots. For example, the transmission unit of PUCCH may be a sub-slot unit, as introduced in NR Rel. 16. In sub-slot-unit PUCCH transmission, the number of symbols included in a sub-slot is less than that of a slot. For example, if the number of symbols included in a slot is 14 (or 12), the number of symbols included in a sub-slot may be 2 or 7 (or 6).

[0339] Furthermore, the application of the embodiment or modification may be controlled (e.g., enabled or disabled) depending on whether the unit of PUCCH transmission is a slot or a sub-slot. Also, the embodiment or modification applied may differ depending on whether the unit of PUCCH transmission is a slot or a sub-slot.

[0340] (Supplement 4) In the above-described embodiment 3 or modification, an example was given in which there is only one second DCI after receiving the first DCI that assigns PUSCH. Here, as shown in Figure 22 for example, terminal 200 may receive multiple DCIs that assign PUSCH to resources that overlap in time with the transmission of PUSCH assigned by the first DCI. In this case, for example, the above-described embodiment or modification may be applied by replacing (or reinterpreting) the last DCI received by terminal 200 among the multiple DCIs with the second DCI.

[0341] (Supplement 5) In the embodiments or modifications described above, the transmission of PUCCH, which sends ACK / NACK, was explained using a single slot as an example, but PUCCH may be transmitted using multiple slots. For example, Repetition may also be applied to PUCCH.

[0342] In this case, for example, in Method 1, some of the TBoMS transmission slots may conflict with PUSCH. In a slot where two PUCCH resources conflict (for example, slot #8 shown in Figure 23), the terminal 200 may, as in Embodiment 1, puncture a portion of the PUSCH resource and send an ACK / NACK. On the other hand, in a slot where two PUCCH resources do not conflict (for example, slot #9 shown in Figure 19), the terminal 200 may use PUCCH to send an ACK / NACK.

[0343] The number of ACK / NACK bits transmitted may be the same across TBoMS transmission slots, or it may be different across TBoMS transmission slots. An unrestricted example of the former is to apply the X-bit restriction of Method 1 in Embodiment 3 (or apply ACK / NACK bundling) regardless of whether a PUCCH resource and a PUSCH resource collide. An unrestricted example of the latter is to apply the X-bit restriction (or apply ACK / NACK bundling) in the same way as Method 1 in Embodiment 3 when a PUCCH resource and a PUSCH resource collide, and not apply the X-bit restriction (or do not apply ACK / NACK bundling) in slots where a PUCCH resource and a PUSCH resource do not collide.

[0344] (Supplement 6) In the embodiments or modifications described above, the transmission of ACK / NACK was used as an example, but this disclosure is not limited to ACK / NACK and may be applied to other UCIs. For example, NR Rel.17 considers triggering the transmission of an Aperiodic CSI PUCCH by a DCI that assigns a downlink PDSCH. The UCI transmitted using the PUCCH assigned by the second DCI may be replaced from ACK / NACK to an Aperiodic CSI.

[0345] (Supplement 7) In this third embodiment, when TBoMS transmission of PUSCH is applied to terminal 200, the PUCCH resource that sends an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns PUSCH is allowed to be assigned to a resource that overlaps in time with the transmission of PUSCH assigned by the first DCI.

[0346] On the other hand, if TBoMS transmission of PUSCH is applied to terminal 200, as in NR Rel.15 / 16, it may not be permitted to allocate the PUCCH resource that sends an ACK / NACK to the PDSCH assigned by the second DCI after receiving the first DCI that assigns PUSCH to a resource that temporally overlaps with the transmission of PUSCH assigned by the first DCI. Also, as previously stated, depending on the conditions, the embodiments or modifications described above may not be applied.

[0347] In this case, terminal 200, for example, sends an ACK / NACK to the PDSCH in the uplink slot after the TBoMS transmission is complete. The control information included in the DCI that assigns the PDSCH may include timing information (K1 or PDSCH-to-HARQ_feedback timing indication) indicating how many slots after the slot that received the PDSCH the PUCCH should be sent.

[0348] Here, since the information regarding timing that can be notified (or instructed) to terminal 200 by the control information (e.g., the range of timing) is limited, if TBoMS transmission is applied to terminal 200, it is considered to expand the range of timing that can be notified.

[0349] For example, if a TBoMS transmission of PUSCH is applied to terminal 200, and it is not permitted to assign a PUCCH resource that sends an ACK / NACK to a PDSCH assigned in a second DCI after receiving a first DCI that assigns PUSCH to a resource that temporally overlaps with the transmission of PUSCH assigned in the first DCI, then the TBoMS transmission slot does not need to be included in the determination (e.g., calculation) of K1.

[0350] For example, as shown in Figure 24, if the first DCI in slot #0 assigns slot #3 and a TBoMS transmission with 4 slots as the timing for sending a PUSCH, terminal 200 will send PUSCHs in slots #3, #4, #7, and #8. Also, Figure 20 shows an example where the second DCI assigns a PDSCH in slot #1, and a PUCCH resource that sends an ACK / NACK to the PDSCH is assigned to slot #9.

[0351] In this case, with a slot-based K1 determination method, the timing of slot #9, where terminal 200 transmits PUCCH, can be specified by K1=8. However, if the TBoMS transmission slot is not used to determine K1, the timing of slot #9 can be specified by K1=4. Therefore, the range of PUCCU transmission timings that can be specified by K1 can be expanded, for example, reducing the occurrence of PDSCH allocation blocking and avoiding or suppressing a decrease in downlink frequency utilization efficiency.

[0352] Furthermore, the method for determining K1 described above may be applied depending on the TBoMS transmission method, whether the unit of PUCCH transmission is a slot or a sub-slot, or depending on the priority of ACK / NACK. In addition, the method for determining K1 described above may be applied in combination with the embodiments or modifications described above.

[0353] (Supplement 8) Information indicating whether the terminal 200 supports the functions, operations, or processes described in each of the embodiments, modifications, and supplements described above may be transmitted (or notified) from the terminal 200 to the base station 100 as, for example, capability information or capability parameters of the terminal 200.

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

[0355] The base station 100 may, for example, determine (or decide or assume) which functions, operations, or processes the source terminal 200 supports (or does not support) based on capability information received from the terminal 200. The base station 100 may perform operations, processes, or controls in accordance with the determination result based on the capability information. For example, the base station 100 may control the allocation (in other words, scheduling) of at least one downlink resource such as PDCCH or PDSCH, and an uplink resource such as PUCCH or PUSCH, based on capability information received from the terminal 200.

[0356] Furthermore, the fact that terminal 200 does not support some of the functions, operations, or processes described in each embodiment, each modification, and each supplement described above may be interpreted as the terminal 200 having restrictions on such some functions, operations, or processes. For example, information or requests regarding such restrictions may be notified to base station 100.

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

[0358] The embodiments, modifications, and supplementary information relating to one non-limiting embodiment of this disclosure have been described above.

[0359] In this disclosure, ACK / NACK may be referred to as, for example, HARQ-ACK or HARQ-Feedback information. Repetition may also be referred to as, for example, slot aggregation, slot bundling, TTI aggregation, or TTI bundling.

[0360] This disclosure may be applied, for example, to terminal-to-terminal communications such as Sidelink communications.

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

[0362] Furthermore, while this disclosure assumes RRC signaling for the upper layer signaling, it may be replaced with Medium Access Control (MAC) signaling and DCI notifications, which are physical layer signaling.

[0363] (Control signal) In this disclosure, the downlink control signal (information) related to this disclosure may be a signal (information) transmitted by the PDCCH of the physical layer, or a signal (information) transmitted by the MAC CE (Control Element) or RRC of the upper layer. Furthermore, the downlink control signal may be a predefined signal (information).

[0364] The uplink control signal (information) related to this disclosure may be a signal (information) transmitted by PUCCH at the physical layer, or a signal (information) transmitted by MAC CE or RRC at the upper layer. The uplink control signal may also be a predefined signal (information). Furthermore, the uplink control signal may be replaced with UCI (uplink control information), 1st stage SCI (sidelink control information), or 2nd stage SCI.

[0365] (base station) In this disclosure, a base station may be a TRP (Transmission Reception Point), cluster head, access point, RRH (Remote Radio Head), eNodeB (eNB), gNodeB (gNB), BS (Base Station), BTS (Base Transceiver Station), master unit, gateway, etc. In side-link communication, one terminal may perform the operation equivalent to a base station. A base station may also be a relay device that relays communication between a higher-level node and a terminal. Furthermore, a base station may also be a roadside unit.

[0366] (Uphill rink / Downhill rink / Side rink) This disclosure may be applied to uplink, downlink, or sidelink. For example, this disclosure may be applied to uplink PUSCH, PUCCH, PRACH, downlink PDSCH, PDCCH, PBCH, and sidelink PSSCH (Physical Sidelink Shared Channel), PSCCH (Physical Sidelink Control Channel), and PSBCH (Physical Sidelink Broadcast Channel).

[0367] Note that 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.

[0368] (Data channel / Control channel) This disclosure may be applied to either data channels or control channels. For example, the channels in this disclosure may be replaced with PDSCH, PUSCH, PSSCH for data channels and PDCCH, PUCCH, PBCH, PSCCH, PSBCH for control channels.

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

[0370] (Time interval) In this disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may also be other time resource units such as frames, superframes, subframes, slots, time slots, subslots, minislots, symbols, OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier - Frequency Division Multiple Access) symbols, etc. Furthermore, the number of symbols contained in one slot is not limited to the number of symbols exemplified in the embodiments described above, but may be other numbers of symbols.

[0371] (Frequency band) This disclosure may apply to either the licensed band or the unlicensed band.

[0372] (communication) This disclosure may be applied to any of the following: communication between a base station and a terminal (Uu-link communication), communication between terminals (Sidelink communication), or V2X (Vehicle to Everything) communication. For example, the channels in this disclosure may be replaced with PSCCH, PSSCH, PSFCH (Physical Sidelink Feedback Channel), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, or PBCH.

[0373] Furthermore, this disclosure may be applied to either terrestrial networks or non-terrestrial networks (NTN) using satellites or high-altitude pseudo-satellites (HAPS). It may also be applied to terrestrial networks with large cell sizes, ultra-wideband transmission networks, and other networks where transmission delay is large relative to symbol length or slot length.

[0374] (Antenna port) 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 single physical antenna; it can refer to an array antenna or other structure composed of multiple antennas. For example, the number of physical antennas an antenna port consists of is not specified; it is defined as the smallest unit from which a terminal can transmit a reference signal. Furthermore, an antenna port may also be defined as the smallest unit from which the weighting of a precoding vector is multiplied.

[0375] <5G NR System Architecture and Protocol Stack> 3GPP is continuing work on the next release of fifth-generation mobile phone technology (also simply called "5G"), which includes the development of new radio access technologies (NR) operating in the frequency range up to 100 GHz. The initial version of the 5G standard was completed at the end of 2017, which will enable the prototyping and commercial deployment of devices (e.g., smartphones) that comply with the 5G NR standard.

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

[0377] The NR user plane protocol stack (see, for example, 3GPP TS 38.300, section 4.4.1) includes the PDCP (Packet Data Convergence Protocol (see section 6.4 of TS 38.300)) sublayer, RLC (Radio Link Control (see section 6.3 of TS 38.300)) sublayer, and MAC (Medium Access Control (see section 6.2 of TS 38.300)) sublayer, which are terminated on the network side in gNB. Additionally, a new Access Stratum (AS) sublayer (SDAP: Service Data Adaptation Protocol) is introduced on top of PDCP (see, for example, 3GPP TS 38.300, section 6.5). Furthermore, a control plane protocol stack is defined for NR (see, for example, TS 38.300, section 4.4.2). An overview of Layer 2 functionality 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.

[0378] For example, the Medium-Access-Control layer handles scheduling and scheduling-related functions, including the multiplexing of logical channels and the handling of various neural networks.

[0379] For example, the Physical Layer (PHY) is responsible for coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. The Physical Layer also 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 for transmitting a particular transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels include uplink physical channels such as PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel), and downlink physical channels such as PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel).

[0380] Use cases / deployment scenarios for NR may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communications (mMTC), each with diverse requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20 Gbps on the downlink and 10 Gbps on the uplink) and effective (user-experienced) data rates approximately three times that of IMT-Advanced. URLLC, on the other hand, imposes more stringent requirements for ultra-low latency (0.5 ms for UL and DL respectively for user plane latency) and high reliability (1-10⁻⁵ within 1 ms). Finally, mMTC may preferably require high connectivity density (1,000,000 devices / km² in urban environments), wide coverage in harsh environments, and extremely long-lasting batteries (15 years) for low-cost devices.

[0381] Therefore, an OFDM neurology suitable for one use case (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) may not be effective for other use cases. For example, low-latency services may preferably require a shorter symbol length (and thus a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also known as TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with short delay spreads. The subcarrier spacing may be optimized on a case-by-case basis to maintain similar CP overhead. There may be one or more subcarrier spacing values ​​supported by NR. Accordingly, subcarrier spacings of 15kHz, 30kHz, 60kHz, etc. are currently being considered. The symbol length Tu and subcarrier spacing Δf are directly related by the equation Δf = 1 / Tu. Similar to LTE systems, the term “resource element” can be used to mean the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

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

[0383] <Functional separation between NG-RAN and 5GC in 5G NR> Figure 26 shows the functional separation between NG-RAN and 5GC. The logical nodes of NG-RAN are gNB or ng-eNB. 5GC has logical nodes AMF, UPF, and SMF.

[0384] For example, gNB and ng-eNB host the following main functions: - Radio resource management functions such as radio bearer control, radio admission control, connection mobility control, and dynamic allocation (scheduling) of resources to UEs on both uplink and downlink; - Compression, encryption, and integrity protection of the IP header of the data; - Selection of the AMF when the UE attaches if routing to the AMF cannot be determined from the information provided by the UE; - Routing of user plane data toward UPF; - Routing of control plane information to AMF; - Setting up and disconnecting connections; - Scheduling and sending paging messages; - Scheduling and transmission of system notification information (originating from AMF or Operation, Admission, Maintenance functions (OAM)); - Setting up measurements and measurement reporting for mobility and scheduling; - Transport-level packet marking on the uplink; - Session management; - Support for network slicing; - Management of QoS flows and mapping to data radio bearers; - Support for UEs in the RRC_INACTIVE state; - NAS message delivery function; - Sharing of wireless access network; Dual connectivity; - Close cooperation between NR and E-UTRA.

[0385] The Access and Mobility Management Function (AMF) hosts the following main functions: - A function to terminate Non-Access Stratum (NAS) signaling; - Security of NAS signaling; - Security control of Access Stratum (AS); - Core Network (CN) node-to-node signaling for mobility between 3GPP access networks; - Reachability of the UE in idle mode (including control and execution of paging retransmissions); - Management of registration areas; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization including roaming permission checks; - Mobility management and control (enrollment and policies); - Support for network slicing; - Selection of Session Management Function (SMF).

[0386] Furthermore, the User Plane Function (UPF) hosts the following main functions: - Anchor points for intra-RAT mobility / inter-RAT mobility (where applicable); - External PDU (Protocol Data Unit) session points for interconnection with data networks; - Routing and forwarding of packets; - Packet inspection and enforcement of policy rules in the user plane. - Reporting traffic usage; - Uplink classifier to support routing of traffic flow to data networks; - A Branching Point for supporting multi-homed PDU sessions; - QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement); - Verification of uplink traffic (mapping to QoS flows of SDFs); - Downlink packet buffering and triggering function for downlink data notification.

[0387] Finally, the Session Management Function (SMF) hosts the following main functions: - Session management; - Allocation and management of IP addresses for UEs; - Selection and control of UPFs; - Traffic steering setting function in the User Plane Function (UPF) for routing traffic to appropriate destinations; - Enforcement of control plane policies and QoS; - Notification of downlink data.

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

[0389] RRC is a higher-layer signaling protocol used for configuring UEs and gNBs. During this transition, the AMF prepares UE context data (including, for example, PDU session context, security key, UE Radio Capability, UE Security Capabilities, etc.) and sends it to the gNB along with an Initial Context Setup Request. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, to which the UE responds with a SecurityModeComplete message. Subsequently, the gNB sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB reconfigures itself to set up the Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the RRCReconfiguration step is omitted because SRB2 and DRB are not set up. Finally, gNB notifies AMF that the setup procedure is complete with an Initial Context Setup Response.

[0390] Accordingly, this disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) comprising a control circuit that establishes a Next Generation (NG) connection with a gNodeB during operation, and a transmission unit that sends an initial context setup message to the gNodeB via the NG connection during operation so that a signaling radio bearer between the gNodeB and the user equipment (UE) is set up. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, including an Information Element (IE), to the UE via the signaling radio bearer. The UE then transmits on the uplink or receives on the downlink based on the resource allocation setting.

[0391] <IMT Usage Scenarios from 2020 Onward> Figure 28 shows some use cases for 5G NR. The 3rd generation partnership project for new radio (3GPP NR) is considering three use cases envisioned by IMT-2020 to support a wide variety of services and applications. The first phase of specification development for enhanced mobile-broadband (eMBB) has been completed. Current and future work will include expanding eMBB support, as well as standardization for ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC). Figure 28 shows some examples of conceptual use scenarios for IMT beyond 2020 (see, e.g., ITU-R M.2083 Figure 2).

[0392] URLLC use cases have stringent performance requirements, such as throughput, latency, and availability. URLLC use cases are envisioned as one of the key technologies to enable future applications such as wireless control of industrial production or manufacturing processes, telemedicine surgery, automation of power transmission and distribution in smart grids, and traffic safety. The ultra-high reliability of URLLC is supported by identifying technologies that meet the requirements set by TR 38.913. In NR URLLC in Release 15, a key requirement is that the target user plane latency is 0.5 ms for UL (uplink) and 0.5 ms for DL ​​(downlink). The general URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a 32-byte packet size when the user plane latency is 1 ms.

[0393] From a physical layer perspective, reliability can be improved in many ways. Current room for reliability improvement includes defining a separate CQI table for URLLC, a more compact DCI format, and PDCCH iterations. However, this room for improvement may expand towards achieving ultra-high reliability as NR becomes more stable and developed (in terms of critical requirements for NR URLLC). Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0394] Furthermore, the technical enhancements targeted by NR URLLC aim to improve latency and reliability. Technical enhancements for latency improvement include configurable neurology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level iteration on data channels, and preemption on downlink. Preemption means that a transmission for which a resource has already been allocated is stopped, and that allocated resource is used for other transmissions with lower latency / higher priority requirements that are requested later. Thus, transmissions that were already permitted are replaced by later transmissions. Preemption is applicable regardless of the specific service type. For example, a transmission of service type A (URLLC) may be replaced by a transmission of service type B (eMBB, etc.). Technical enhancements for reliability improvement include a dedicated CQI / MCS table for the 1E-5 target BLER.

[0395] A key characteristic of mMTC (massive machine type communication) use cases is the extremely large number of connected devices that typically transmit relatively small amounts of data that are less susceptible to latency. These devices require low cost and very long battery life. From a noise reduction (NR) perspective, utilizing a very narrow bandwidth is one solution that saves power from the user interface (UE) and extends battery life.

[0396] As mentioned above, the scope of reliability improvements in NR is expected to broaden. High reliability or very high reliability is a critical requirement in all cases, for example, for URLLC and mMTC. Several mechanisms can improve reliability from both a radio and network perspective. Generally, there are two to three key areas that can help improve reliability. These areas include compact control channel information, data channel / control channel repetition, and diversity in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability improvements regardless of the specific communication scenario.

[0397] Regarding NR URLLC, further use cases with more stringent requirements are envisioned, such as factory automation, transportation, and power distribution. These stringent requirements include high reliability (up to 10⁻⁶ levels), high availability, packet size up to 256 bytes, and time synchronization down to a few microseconds (depending on the use case, the value can be 1 microsecond or a few microseconds depending on the frequency range and short latency of approximately 0.5 ms to 1 ms (e.g., 0.5 ms latency in the target user plane)).

[0398] Furthermore, for NR URLLC, several technical enhancements may be available from the perspective of the physical layer. These technical enhancements include enhancements to the Physical Downlink Control Channel (PDCCH) related to compact DCI, repetition of the PDCCH, and increased monitoring of the PDCCH. Also, the enhancement of UCI (Uplink Control Information) is related to the enhancement of enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. Additionally, there may be enhancements to the PUSCH related to mini-slot level hopping, and enhancements to 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).

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

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

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

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

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

[0404] The term "...part" used in this disclosure may be replaced with other terms such as "...circuitry," "...device," "...unit," or "...module."

[0405] This disclosure can be implemented in software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiments may be implemented in part or in whole as an integrated circuit (LSI), and each process described in the above embodiments may be controlled in part or in whole by a single LSI or a combination of LSIs. An LSI may consist of individual chips, or it may consist of a single chip that includes some or all of the functional blocks. An LSI may have data inputs and outputs. Depending on the degree of integration, LSIs may be referred to as ICs, system LSIs, super LSIs, or ultra LSIs.

[0406] The method of integration is not limited to LSIs; it may also be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, FPGAs (Field Programmable Gate Arrays) that can be programmed after LSI manufacturing, or reconfigurable processors that allow for the reconfiguration of the connections and settings of circuit cells within the LSI, may also be used. This disclosure may be implemented as digital or analog processing.

[0407] Furthermore, if advancements in semiconductor technology or other derived technologies lead to the emergence of integrated circuit technologies that replace LSIs, then naturally, it would be possible to use those technologies to integrate functional blocks. The application of biotechnology, for example, is a possibility.

[0408] This disclosure is applicable to all types of devices, systems, and equipment having communication capabilities (collectively referred to as communication equipment). Communication equipment may include a radio transceiver and a processing / control circuit. A radio transceiver may include a receiver and a transmitter, or both as functions. A radio transceiver (transmitter, receiver) may include an RF (Radio Frequency) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or similar. Non-exclusive examples of communication devices include telephones (mobile phones, smartphones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still / video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth / telemedicine devices, vehicles or mobile transport with communication capabilities (cars, airplanes, ships, etc.), and combinations of the above-mentioned devices.

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

[0410] Communication includes data communication via cellular systems, wireless LAN systems, and communication satellite systems, as well as data communication using combinations of these.

[0411] Furthermore, the communication device also includes devices such as controllers and sensors that are connected to or linked to a communication device that performs the communication functions described in this disclosure. For example, this includes controllers and sensors that generate control signals and data signals used by the communication device that performs the communication functions of the communication device.

[0412] Furthermore, communication equipment includes infrastructure facilities such as base stations, access points, and any other devices, devices, and systems that communicate with or control the aforementioned non-limited types of equipment.

[0413] A terminal according to one embodiment of the present disclosure includes a control circuit that determines a second resource amount to be used for transmitting uplink control information based on the size of the data transmitted in the uplink shared channel in the multiple slots and / or the first resource amount of the uplink shared channel in the multiple slots, when the transmission resources allocated for transmitting an uplink shared channel using multiple slots and the transmission resources for an uplink control channel overlap in time, and a transmission circuit that multiplexes and transmits the uplink control information and the data in the resources of the determined second resource amount.

[0414] In one embodiment of the present disclosure, the size is greater than the amount of resources per slot, or the amount of resources allocated to the initial transmission when performing repeated transmissions on the uplink shared channel.

[0415] In one embodiment of the present disclosure, the first resource amount is a value different from the number of symbols included in the plurality of slots.

[0416] In one embodiment of the present disclosure, the size is greater than the amount of resources per slot, or the amount of resources allocated to the first transmission when repeatedly transmitting on the uplink shared channel, and the first amount of resources is different from the number of symbols included in the plurality of slots.

[0417] In one embodiment of the present disclosure, the control circuit determines the second resource amount based on the size of the data, the first resource amount, and the third resource amount of the uplink sharing channel in the plurality of slots.

[0418] In one embodiment of the present disclosure, the size of the data is the code block size or transport block size of the data.

[0419] In one embodiment of the present disclosure, the control circuit determines the amount of the second resource based on which of the plurality of slots the slot in which the transmission resources of the uplink shared channel and the transmission resources of the uplink control channel overlap in time.

[0420] A terminal according to one embodiment of the present disclosure includes a control circuit that determines, on a per-slot basis, the amount of resources to be used for transmitting uplink control information based on whether or not uplink control information is multiplexed in a slot that is temporally earlier than the overlapping slot, when the transmission resources of the uplink sharing channel and the transmission resources of the uplink control channel in a plurality of slots overlap in time, and a transmission circuit that multiplexes the uplink control information and data using the determined amount of resources and transmits them.

[0421] In one embodiment of the present disclosure, the control circuit determines whether or not to set the amount of resources used for transmitting the uplink control information to zero.

[0422] In one embodiment of the present disclosure, the control circuit determines whether or not to set the amount of resources used for transmitting the uplink control information to zero.

[0423] In one embodiment of the present disclosure, the control circuit makes the amount of resources used for transmitting the uplink control information different depending on whether the first slot in the plurality of slots is the overlapping slot or whether a slot other than the first slot in the plurality of slots is the overlapping slot.

[0424] A terminal according to one embodiment of the present disclosure includes a receiving circuit that receives a second downlink control information for allocating resources for a downlink shared channel after receiving a first downlink control information for allocating resources for an uplink shared channel, and a control circuit that controls the transmission of the uplink shared channel based on whether or not the resources of the uplink control channel transmitted in response to the reception of the downlink shared channel overlap in time with the resources of the uplink shared channel, wherein the resources of the uplink shared channel span multiple slots, and controlling the transmission of the uplink shared channel includes at least one of controlling the number of bits of the signal transmitted in the resources of the uplink shared channel, setting the resources of the uplink shared channel to be unavailable, and controlling the HARQ process for the downlink shared channel.

[0425] In one embodiment of the present disclosure, the control circuit, when the resources of the uplink control channel and the uplink sharing channel overlap in time, punctures a portion of the resources of the uplink sharing channel to limit the number of bits to a threshold or less.

[0426] In one embodiment of the present disclosure, the signal is an ACK / NACK signal for reception of the downlink shared channel, and the control circuit compresses the number of bits of the ACK / NACK signal to less than or equal to the threshold by ACK / NACK bundling if the number of bits of the ACK / NACK signal exceeds the threshold.

[0427] In one embodiment of the present disclosure, the control circuit prioritizes the transmission of the signal using the uplink control channel over the transmission of the uplink sharing channel, and sets resources in which the uplink control channel and the uplink sharing channel overlap in time as resources that cannot be used for transmission on the uplink sharing channel.

[0428] In one embodiment of the present disclosure, the control circuit disables the HARQ process for the downlink sharing channel if the resources of the uplink control channel and the resources of the uplink sharing channel overlap in time.

[0429] A base station according to one embodiment of the present disclosure includes a control circuit that determines a second resource amount to be used for transmitting uplink control information based on the size of the data transmitted in the uplink shared channel in the multiple slots and / or the first resource amount of the uplink shared channel in the multiple slots, when the transmission resources allocated for transmitting an uplink shared channel using a plurality of slots and the transmission resources for an uplink control channel overlap in time, and a receiving circuit that receives the uplink control information and the multiplexed data in the resources of the determined second resource amount.

[0430] In one embodiment of the present disclosure, when the transmission resources allocated for transmitting an uplink shared channel using multiple slots and the transmission resources for an uplink control channel overlap in time, the terminal determines a second resource amount to be used for transmitting uplink control information based on the size of the data transmitted in the uplink shared channel in the multiple slots and / or the first resource amount of the uplink shared channel in the multiple slots, and transmits the uplink control information and the data multiplexed on the resources of the determined second resource amount.

[0431] All disclosures in the specification, drawings, and abstract contained in the Japanese application 2021-064901, filed on April 6, 2021, are incorporated herein by reference. [Industrial applicability]

[0432] One embodiment of this disclosure is useful for wireless communication systems. [Explanation of Symbols]

[0433] 100 base stations 101,205 Control Unit 102 Higher-level control signal generation unit 103 Downlink control information generation unit 104,206 Encoding section 105,207 Modulation section 106,208 Signal allocation section 107,209 Transmitter 108,201 Receiving Unit 109,202 Extraction part 110,203 Demodulation section 111,204 Decoding section 200 terminals< / option>

Claims

1. A control circuit determines, when the transmission resources of an uplink control channel overlap in time with the transmission resources of an uplink sharing channel using multiple slots, and a single transport block (TB) is transmitted through the multiple slots, the code block size applied to each slot among the multiple slots through which the uplink sharing channel is transmitted, and the amount of second resources used for transmitting the uplink control information, based on the amount of first resources of the uplink sharing channel in each of the multiple slots through which the uplink control information is transmitted. A transmission circuit that multiplexes and transmits the uplink control information for the resources of the second resource amount onto the uplink shared channel, A communication device equipped with the following features.

2. The aforementioned size is greater than the amount of resources per slot, or the amount of resources allocated to the initial transmission when performing repeated transmissions on the uplink shared channel. The communication device according to claim 1.

3. The first resource amount is a value different from the number of symbols included in the plurality of slots. The communication device according to claim 1.

4. The aforementioned size is greater than the resource amount per slot, or the resource amount allocated to the initial transmission when performing repeated transmissions on the uplink shared channel. The first resource amount is a value different from the number of symbols included in the plurality of slots. The communication device according to claim 1.

5. The control circuit determines the second resource amount based on the code block size, the first resource amount, and the third resource amount of the uplink sharing channel in the plurality of slots. The communication device according to claim 4.

6. The control circuit determines the amount of the second resource based on which of the plurality of slots the slot in which the transmission resources of the uplink shared channel and the transmission resources of the uplink control channel overlap in time. The communication device according to claim 1.

7. The aforementioned size is calculated based on the amount of resources per slot. The communication device according to claim 1.

8. A control circuit determines, when the transmission resources of an uplink control channel overlap in time with the transmission resources of an uplink sharing channel using multiple slots, and a single transport block (TB) is transmitted through the multiple slots, the code block size applied to each slot among the multiple slots through which the uplink sharing channel is transmitted, and the amount of second resources used for transmitting the uplink control information, based on the amount of first resources of the uplink sharing channel in each of the multiple slots through which the uplink control information is transmitted. A receiving circuit that receives the uplink control information for the resources of the second resource amount, which is multiplexed onto the uplink shared channel, A base station equipped with the necessary equipment.

9. Communication equipment, When the transmission resources of the uplink control channel overlap temporally with the transmission resources of the uplink sharing channel using multiple slots, and a single transport block (TB) is transmitted through the multiple slots, the amount of second resources used for transmitting uplink control information is determined based on the code block size applied to each slot among the multiple slots through which the uplink sharing channel is transmitted, and the amount of first resources of the uplink sharing channel in the multiple slots. The uplink control information for the resources of the second resource amount is multiplexed and transmitted on the uplink shared channel. Communication method.

10. The base station is, When the transmission resources of the uplink control channel overlap temporally with the transmission resources of the uplink sharing channel using multiple slots, and a single transport block (TB) is transmitted through the multiple slots, the amount of second resources used for transmitting uplink control information is determined based on the code block size applied to each slot among the multiple slots through which the uplink sharing channel is transmitted, and the amount of first resources of the uplink sharing channel in the multiple slots. The uplink control information for the resources of the second resource amount is multiplexed and received on the uplink shared channel. Communication method.

11. An integrated circuit that controls the processing of a communication device, wherein the processing is When the transmission resources of an uplink control channel overlap temporally with the transmission resources of an uplink sharing channel using multiple slots, and a single transport block (TB) is transmitted through the multiple slots, a process is performed to determine the amount of second resources used for transmitting uplink control information, based on the code block size applied to each slot among the multiple slots through which the uplink sharing channel is transmitted, and the amount of first resources of the uplink sharing channel in the multiple slots. The process of multiplexing and transmitting the uplink control information for the resources of the second resource amount onto the uplink shared channel, An integrated circuit, including

12. An integrated circuit that controls the processing of a base station, wherein the processing is When the transmission resources of an uplink control channel overlap temporally with the transmission resources of an uplink sharing channel using multiple slots, and a single transport block (TB) is transmitted through the multiple slots, a process is performed to determine the amount of second resources used for transmitting uplink control information, based on the code block size applied to each slot among the multiple slots through which the uplink sharing channel is transmitted, and the amount of first resources of the uplink sharing channel in the multiple slots. The process of receiving the uplink control information for the resources of the second resource amount, which is multiplexed onto the uplink shared channel, An integrated circuit, including

Images