Communication device, communication method and integrated circuit

Abstract

Properly transmit uplink signals. In a terminal (200), a control unit (211) determines a processing mode for the uplink data and the uplink control information in accordance with requirements for at least one of the uplink data and the uplink control information when transmission of an uplink data channel including uplink data and transmission of an uplink control channel including uplink control information overlap in time. A transmission unit (218) transmits at least one of the uplink data and the uplink control information based on the determined processing mode.

Description

[Technical Field]

[0001] The present disclosure relates to a terminal and a communication method. [Background technology]

[0002] The 3GPP (3rd Generation Partnership Project) has completed the Release 15 NR (New Radio access technology) specification for the realization of 5G (5th Generation mobile communication systems). NR supports Ultra Reliable and Low Latency Communication (URLLC) in addition to high speed and large capacity, which are the basic requirements for enhanced Mobile Broadband (eMBB) (see, for example, Non-Patent Documents 1-4).

[0003] The requirements for URLLC in Release 15 defined by 3GPP include a user plane delay of 0.5 ms or less one way, a certain level of reliability, and a delay of 1 ms or less.

[0004] In Release 15 NR, low latency is achieved by shortening the Transmit Time Interval (TTI) by flexibly controlling the subcarrier spacing or the number of transmitted symbols. Highly reliable data transmission is also achieved by configuring or reporting a Modulation and Coding Scheme (MCS) or a Channel Quality Indicator (CQI) to achieve a low target Block Error Rate (BLER). For example, the target error rate (or target BLER) can be set to a value less than the normal mode (e.g., BLER = 10 -1 ) and high reliability mode (e.g., BLER=10 -5 ) can be set.

Prior Art Documents

Non-Patent Documents

[0005]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Non-Patent Document 5

Summary of the Invention

[0006] In NR, the method of transmitting uplink signals has not been fully considered.

[0007] Non-limiting examples of the present disclosure contribute to providing a terminal and a communication method that can appropriately transmit uplink signals.

[0008] A terminal according to an embodiment of the present disclosure includes: a circuit that, when transmission of an uplink data channel including uplink data and transmission of an uplink control channel including uplink control information overlap in time, determines a processing mode for the uplink data and the uplink control information in accordance with requirements for at least one of the uplink data and the uplink control information; and a transmitter that transmits at least one of the uplink data and the uplink control information based on the determined processing mode.

[0009] A communication method according to one embodiment of the present disclosure, when transmission of an uplink data channel including uplink data and transmission of an uplink control channel including uplink control information overlap in time, determines a processing mode for the uplink data and the uplink control information in accordance with requirements for at least one of the uplink data and the uplink control information, and transmits at least one of the uplink data and the uplink control information based on the determined processing mode.

[0010] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0011] According to an embodiment of the present disclosure, uplink signals can be transmitted appropriately.

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

[0013] [Figure 1] FIG. 1 is a block diagram showing a partial configuration of a terminal according to a first embodiment; [Figure 2] Block diagram showing a configuration of a base station according to a first embodiment. [Figure 3] Block diagram showing the configuration of a terminal according to the first embodiment. [Figure 4] FIG. 1 is a sequence diagram showing processing by a base station and a terminal according to the first embodiment; [Figure 5] FIG. 1 is a diagram showing an example of a transmission process of an uplink signal according to the first embodiment; [Figure 6] FIG. 1 is a diagram showing an example of a transmission process of an uplink signal according to the first embodiment; [Figure 7] FIG. 1 is a diagram showing an example of a transmission process of an uplink signal according to the first embodiment; [Figure 8] FIG. 10 is a diagram showing an example of a transmission process of an uplink signal according to a third embodiment. [Figure 9] FIG. 10 is a diagram showing an example of a transmission process of an uplink signal according to a third embodiment. [Figure 10] FIG. 10 is a diagram showing an example of a transmission process of an uplink signal according to a third embodiment. [Figure 11] FIG. 13 is a diagram showing an example of a transmission process of an uplink signal according to a fifth embodiment. [Figure 12] FIG. 13 is a diagram showing an example of a transmission process of an uplink signal according to a fifth embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a transmission process of an uplink signal according to a fifth embodiment. [Figure 14] FIG. 13 is a diagram showing an example of a transmission process of an uplink signal according to a fifth embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0015] In the use case of eMBB in LTE (Long-Term Evolution) or NR, it is required to maximize cell throughput or spectral efficiency. In such cases, the target data error rate is set to a relatively high value (e.g., BLER = 10 -1 ) is generally used for operation. This is because Hybrid Automatic Repeat Request (HARQ) is applied. In eMBB, for example, after taking into consideration the combined gain from several retransmissions by HARQ, highly reliable packet transmission (e.g., BLER = 10 -5 ) is allowed to be realized.

[0016] On the other hand, URLLC provides highly reliable packet transmission (e.g., BLER=10 -5 ) with a delay of 1 ms or less. For example, in the above-mentioned HARQ, if an error occurs in data transmission, a retransmission request occurs and the data is retransmitted, so the delay time increases as the number of retransmissions increases, and the low delay requirement cannot be met. Therefore, in URLLC, in order to enable highly reliable packet transmission without retransmission by HARQ, the above-mentioned high reliability mode (target error rate of data is set to a relatively low value (for example, BLER=10 -5 ) to ensure reliable data transmission in the first transmission.

[0017] Although setting a low target error rate leads to highly reliable data transmission, it requires more radio resources than setting a high target error rate. In Release 15 NR, the URLLC data size is limited to a relatively small 32 bytes, so setting a low target error rate does not have a significant impact on resource utilization efficiency.

[0018] On the other hand, Release 16 and future URLLC are expected to handle larger data sizes than Release 15 NR, expanding the use cases of URLLC. In this case, if a low target error rate is set, a huge amount of radio resources may be required to achieve highly reliable packet transmission in a single transmission, which is inefficient from the viewpoint of resource utilization.

[0019] Therefore, in a use case of URLLC that handles a relatively large data size, for example, the application of high-speed HARQ retransmission control is expected. In high-speed HARQ retransmission control, for example, a high target error rate (e.g., BLER=10 -1 or BLER=10 -2 In this way, high-speed HARQ retransmission control is effective for achieving low-latency, highly reliable packet transmission while improving resource utilization efficiency.

[0020] Here, focusing on HARQ transmission in the downlink, a terminal (UE: User Equipment) transmits a response signal (ACK / NACK: Acknowledgement / Negative Acknowledgement, or referred to as HARQ-ACK) indicating an error detection result for downlink data to a base station (e.g., eNB or gNB) using an uplink control channel (e.g., PUCCH: Physical Uplink Control Channel).

[0021] At this time, the reliability or delay requirement required for transmitting the response signal differs depending on the reliability or delay requirement of downlink data transmission, or the type (or usage scenario) of use case (or service).

[0022] For example, in URLLC, assume an operation in which data can be transmitted reliably in the next transmission (retransmission) even if an error occurs in the first transmission. In this case, the higher the target error rate of the first data transmission, the more reliable the transmission of a response signal (in other words, the lower the target error rate of the response signal). For example, if the target error rate of the first data transmission is BLER=10 -1 If the response signal has a BLER of 10, -4 The following error rate is obtained, and the target error rate for the first data transmission is BLER=10 -3 If the response signal has a BLER of 10, -2 The following error rate is obtained (see, for example, Non-Patent Document 5).

[0023] Furthermore, in the case of eMBB and URLLC, a response signal to a URLLC data transmission is required to have a lower delay than a response signal to an eMBB data transmission.

[0024] An NR terminal is expected to support multiple use cases or service types (e.g., eMBB and URLLC). It is also expected that an NR terminal will support multiple URLLC data transmissions with different target error rates in URLLC. In this case, in the uplink, transmission of response signals corresponding to downlink data transmissions with different reliability, delay requirements, or use case (service) types and transmission of uplink data may occur simultaneously within the same slot.

[0025] In NR, when PUCCH transmission including uplink control information (e.g., UCI: Uplink Control Information) such as a response signal and PUSCH (Physical Uplink Shared Channel) transmission including uplink data (e.g., UL-SCH: Uplink-Shared Channel) overlap in time, the terminal supports "UCI on PUSCH," which multiplexes UCI onto PUSCH and transmits it (see, for example, Non-Patent Documents 2 and 3).

[0026] For example, when a response signal, which is one of the UCIs, is multiplexed into a PUSCH, the amount of resources (number of resource elements (RE)) Q' allocated to the response signal in the PUSCH is ACK is calculated using the following formula (1):

number

[0027] Generally, in formula (1), β offset HARQ-ACK The larger the value of α, the more resources are allocated to the response signal. Also, in equation (1), the larger the value of α, the higher the upper limit of the amount of resources allocated to the response signal.

[0028] However, in Release 15 NR, in the case of UCI on PUSCH, the operation regarding the response signal and uplink data (UL-SCH) according to the reliability, delay requirement, or type of use case (or service) has not been sufficiently considered.

[0029] For example, if the reliability required for a response signal multiplexed onto a PUSCH is higher than the reliability required for uplink data, more resources may be allocated to the response signal in order to satisfy the requirement for the response signal that requires high reliability. offset HARQ-ACK It is conceivable to set at least one of the values ​​of .gamma. and .alpha. to a large value.

[0030] However, β offset HARQ-ACK and β if the setting of α cannot be dynamically controlled (e.g., in the case of a quasi-static setting). offset HARQ-ACK In a state where the values ​​of and are set to be large, even when a response signal that does not require high reliability is multiplexed onto a PUSCH, the same radio resources (more radio resources) as those for a response signal that requires high reliability may be assigned, which is inefficient in terms of resource utilization efficiency. Furthermore, when high reliability is required for uplink data, if extra radio resources are assigned to the response signal that does not require high reliability, radio resources may not be assigned sufficiently to the uplink data, and the requirement on the reliability of the uplink data may not be satisfied.

[0031] On the other hand, when the reliability required for uplink data is higher than the reliability required for the response signal multiplexed onto the PUSCH, it is possible to reduce the amount of resources allocated to the response signal in order to satisfy the requirements of the uplink data that require high reliability. For example, in equation (1), β offset HARQ-ACK It is conceivable to set at least one of the value of .gamma. and the value of .alpha. to a small value.

[0032] However, βoffset HARQ-ACK and β if the setting of α cannot be dynamically controlled (e.g., in the case of a quasi-static setting). offset HARQ-ACK When the values ​​of and α are set to be large, if a response signal that requires high reliability is multiplexed onto the PUSCH, radio resources may not be allocated sufficiently to the response signal, and the required condition for the reliability of the response signal may not be met.

[0033] Furthermore, for example, if the delay requirements differ between the response signal and the uplink data (for example, in the case of uplink data corresponding to eMBB and a response signal corresponding to URLLC), when a terminal multiplexes and transmits a response signal corresponding to URLLC onto a PUSCH of eMBB, the transmission of a PUSCH that does not require low delay (for example, a PUSCH corresponding to eMBB) may become a delay bottleneck.

[0034] Therefore, in one embodiment of the present disclosure, a method for transmitting a response signal and uplink data with different reliability levels, delay requirements, or types of use cases (or services) will be described. In other words, a method for transmitting a response signal and uplink data according to "requirement conditions" such as reliability levels, delay requirements, or types of use cases (or services) will be described.

[0035] Each embodiment will be described in detail below.

[0036] (Embodiment 1) [Communication System Overview] A communication system according to each embodiment of the present disclosure includes a base station 100 and a terminal 200.

[0037] Fig. 1 is a block diagram showing a partial configuration of terminal 200 according to each embodiment of the present disclosure. In terminal 200 shown in Fig. 1, when transmission of an uplink data channel (e.g., PUSCH) including uplink data (e.g., UL-SCH) and transmission of an uplink control channel (e.g., PUCCH) including uplink control information (e.g., UCI) overlap in time, control unit 211 determines a processing mode for the uplink data and the uplink control information according to requirements for at least one of the uplink data and the uplink control information (e.g., reliability, delay requirement, or type of use case (or service)). Transmitter 218 transmits at least one of the uplink data and the uplink control information based on the determined processing mode.

[0038] [Base station configuration] Fig. 2 is a block diagram showing a configuration of base station 100 according to embodiment 1 of the present disclosure. In Fig. 2, base station 100 includes a control unit 101, a data generation unit 102, an encoding unit 103, a retransmission control unit 104, a modulation unit 105, an upper control signal generation unit 106, an encoding unit 107, a modulation unit 108, a downlink control signal generation unit 109, an encoding unit 110, a modulation unit 111, a signal allocation unit 112, an IFFT (Inverse Fast Fourier Transform) unit 113, a transmission unit 114, an antenna 115, a reception unit 116, an FFT (Fast Fourier Transform) unit 117, an extraction unit 118, a demodulation unit 119, a decoding unit 120, a determination unit 121, a demodulation unit 122, a decoding unit 123, and a determination unit 124.

[0039] The control unit 101 determines information related to downlink data transmission of the terminal 200, and outputs the determined information to the coding unit 103, the modulation unit 105, and the signal allocation unit 112. The information related to downlink data transmission includes, for example, a modulation and coding method (e.g., MCS) for downlink data transmitted in the PDSCH, or radio resources of the PDSCH (hereinafter referred to as "PDSCH resources"). The control unit 101 also outputs the determined information to the downlink control signal generation unit 109.

[0040] Furthermore, the control unit 101 determines information relating to the reliability of downlink data of the terminal 200, a delay request, or the type of use case (or service) (in other words, information relating to the request conditions of the response signal), and outputs the determined information to the upper control signal generation unit 106 or the downlink control signal generation unit 109. This information is notified to the terminal 200 (for example, the control unit 211).

[0041] Furthermore, the control unit 101 determines information on the reliability of the uplink data of the terminal 200, delay requirement, or type of use case (or service) (in other words, information on the requirements for the uplink data), and outputs the determined information to the upper control signal generation unit 106 or the downlink control signal generation unit 109. This information is notified to the terminal 200 (for example, the control unit 211).

[0042] Furthermore, control section 101 determines information related to transmission of uplink control information (UCI) of terminal 200, and outputs the determined information to extraction section 118 and decoding section 120. The information related to transmission of UCI includes, for example, a parameter for calculating the amount of resources when multiplexing UCI into PUSCH (for example, β offset HARQ-ACK and α, etc.

[0043] In addition, the control unit 101 determines radio resource allocation for a downlink control signal for transmitting a control signal of an upper layer (upper control signal) or downlink control information, and radio resource allocation for downlink data, and outputs the determined information to the signal allocation unit 112.

[0044] Furthermore, the control unit 101 determines information related to the uplink data of the terminal 200, and outputs the determined information to the extraction unit 118 and the downlink control signal generation unit 109. The information related to the uplink data transmission of the terminal 200 includes, for example, a modulation and coding scheme (e.g., MCS) of the data signal transmitted using the PUSCH, radio resources of the PUSCH (hereinafter referred to as "PUSCH resources"), and the like.

[0045] The data generator 102 generates downlink data for the terminal 200 and outputs the data to the encoder 103 .

[0046] The encoding unit 103 performs error correction encoding on the downlink data input from the data generation unit 102 based on information input from the control unit 101 (e.g., information regarding the coding rate), and outputs the encoded data signal to the retransmission control unit 104.

[0047] At the time of the first transmission, retransmission control section 104 holds the coded data signal input from coding section 103 and outputs it to modulation section 105. Furthermore, when a NACK for the transmitted data signal is input from determination section 121, which will be described later, retransmission control section 104 outputs the corresponding held data to modulation section 105. On the other hand, when an ACK for the transmitted data signal is input from determination section 121, retransmission control section 104 deletes the corresponding held data.

[0048] Modulation section 105 modulates the data signal input from retransmission control section 104 based on information input from control section 101 (for example, information on the modulation method), and outputs the modulated data signal to signal allocation section 112.

[0049] Higher-order control signal generating section 106 generates a control information bit string (higher-order control signal) using the control information input from control section 101 , and outputs the generated control information bit string to encoding section 107 .

[0050] Encoding section 107 performs error correction coding on the control information bit string inputted from higher-order control signal generating section 106 and outputs the coded control signal to modulation section 108 .

[0051] Modulation section 108 modulates the control signal inputted from encoding section 107 and outputs the modulated control signal to signal allocation section 112 .

[0052] The downlink control signal generating unit 109 generates a control information bit string (downlink control signal, for example, DCI) using the control information input from the control unit 101, and outputs the generated control information bit string to the encoding unit 110. Note that since control information may be transmitted to multiple terminals, the downlink control signal generating unit 109 may generate a bit string by including the terminal ID of each terminal in the control information for each terminal. Note that a scrambling sequence, which will be described later, may be used for the terminal ID.

[0053] The coding section 110 performs error correction coding on the control information bit string inputted from the downlink control signal generating section 109 and outputs the coded control signal to the modulating section 111 .

[0054] Modulation section 111 modulates the control signal input from encoding section 110 and outputs the modulated control signal to signal allocation section 112 .

[0055] The signal allocation unit 112 maps the data signal input from the modulation unit 105, the higher control signal input from the modulation unit 108, or the downlink control signal input from the modulation unit 111 to the radio resources based on the information indicating the radio resources input from the control unit 101. The signal allocation unit 112 outputs the downlink signal onto which the signal has been mapped to the IFFT unit 113.

[0056] The IFFT unit 113 performs transmission waveform generation processing such as OFDM on the signal input from the signal allocation unit 112. In the case of OFDM transmission that adds a CP (Cyclic Prefix), the IFFT unit 113 adds a CP (not shown). The IFFT unit 113 outputs the generated transmission waveform to the transmission unit 114.

[0057] Transmitting section 114 performs RF (Radio Frequency) processing such as D / A (Digital-to-Analog) conversion and up-conversion on the signal input from IFFT section 113 , and transmits the radio signal to terminal 200 via antenna 115 .

[0058] The receiving unit 116 performs RF processing such as down-conversion or A / D (Analog-to-Digital) conversion on the uplink signal waveform from the terminal 200 received via the antenna 115, and outputs the uplink signal waveform after the receiving processing to the FFT unit 117.

[0059] The FFT unit 117 performs FFT processing on the uplink signal waveform input from the receiving unit 116 to convert a time domain signal into a frequency domain signal. The FFT unit 117 outputs the frequency domain signal obtained by the FFT processing to the extracting unit 118.

[0060] The extraction unit 118 extracts radio resource components on which UCI is transmitted and radio resource components on which uplink data is transmitted from the signal input from the FFT unit 117, based on information input from the control unit 101 (for example, information on transmission of UCI and information on uplink data). The extraction unit 118 outputs the extracted radio resource components on which UCI is transmitted to the demodulation unit 119, and outputs the extracted radio resource components on which uplink data is transmitted to the demodulation unit 122.

[0061] Demodulation section 119 performs equalization and demodulation on the radio resource components corresponding to UCI received as input from extraction section 118, and outputs the demodulation result (demodulated sequence) to decoding section 120.

[0062] The decoding unit 120 performs error correction decoding on the demodulation result input from the demodulation unit 119 based on information related to the transmission of UCI input from the control unit 101 (for example, information related to the encoding of UCI), and outputs the decoded bit sequence to the determination unit 121.

[0063] Based on the bit sequence input from decoding section 120, determination section 121 determines whether the response signal transmitted from terminal 200 indicates ACK (error) or NACK (no error) for the transmitted data signal. Determination section 121 outputs the determination result to retransmission control section 104.

[0064] The demodulation unit 122 performs equalization and demodulation on the radio resource components corresponding to the uplink data input from the extraction unit 118, and outputs the demodulation result (demodulated sequence) to the decoding unit 123.

[0065] The decoding unit 123 performs error correction decoding on the demodulation result input from the demodulation unit 122, and outputs the decoded bit sequence to the determination unit .

[0066] Determining section 124 performs error detection on the bit sequence input from decoding section 123, and obtains received data (received UL-SCH) if no error is detected. Note that determining section 124 may use the error detection result to generate a response signal (ACK / NACK or HARQ-ACK) for a retransmission request to terminal 200, and output the response signal to retransmission control section 104 (not shown).

[0067] [Device configuration] Fig. 3 is a block diagram showing a configuration of terminal 200 according to Embodiment 1 of the present disclosure. In Fig. 3, terminal 200 includes antenna 201, receiving section 202, FFT section 203, extraction section 204, downlink control signal demodulation section 205, decoding section 206, higher control signal demodulation section 207, decoding section 208, data demodulation section 209, decoding section 210, control section 211, coding sections 212 and 214, modulation sections 213 and 215, signal allocation section 216, IFFT section 217, and transmission section 218.

[0068] The receiving unit 202 performs RF processing such as down-conversion or A / D (Analog-to-Digital) conversion on the signal waveform of the downlink signal (data signal or control signal) from the base station 100 received via the antenna 201, and outputs the resulting received signal (baseband signal) to the FFT unit 203.

[0069] FFT section 203 performs FFT processing on the signal (time domain signal) input from receiving section 202 to convert the time domain signal into a frequency domain signal. FFT section 203 outputs the frequency domain signal obtained by the FFT processing to extraction section 204.

[0070] Extraction section 204 extracts a downlink control signal (for example, DCI), an upper control signal, or downlink data from the signal input from FFT section 203, based on control information (for example, information related to the radio resource of the downlink data or the control signal) input from control section 211. Extraction section 204 outputs the downlink control signal to downlink control signal demodulation section 205, outputs the upper control signal to upper control signal demodulation section 207, and outputs the downlink data to data demodulation section 209.

[0071] The downlink control signal demodulation section 205 equalizes and demodulates the downlink control signal inputted from the extraction section 204 and outputs the demodulation result to the decoding section 206 .

[0072] The decoding unit 206 obtains control information by performing error correction decoding using the demodulation result inputted from the downlink control signal demodulation unit 205. The decoding unit 206 outputs the obtained control information to the control unit 211.

[0073] The higher-order control signal demodulation unit 207 equalizes and demodulates the higher-order control signal inputted from the extraction unit 204 and outputs the demodulation result to the decoding unit 208 .

[0074] Decoding section 208 performs error correction decoding to obtain control information using the demodulation result inputted from higher order control signal demodulation section 207. Decoding section 208 outputs the obtained control information to control section 211.

[0075] The data demodulation unit 209 equalizes and demodulates the downlink data input from the extraction unit 204 and outputs the decoded result to the decoding unit 210 .

[0076] The decoding unit 210 performs error correction decoding using the demodulation result input from the data demodulation unit 209. The decoding unit 210 also performs error detection on the downlink data and outputs the error detection result to the control unit 211. The decoding unit 210 also outputs the downlink data that is determined to be error-free as a result of the error detection as received data.

[0077] Control unit 211 determines a transmission method or parameters (e.g., MCS or radio resources, etc.) for uplink transmission (e.g., UCI or uplink data) based on information related to PUCCH transmission and information related to PUSCH transmission of terminal 200, which are included in control information input from decoding unit 206 or decoding unit 208. Control unit 211 outputs the determined information to coding units 212 and 214, modulation units 213 and 215, and signal allocation unit 216.

[0078] Furthermore, control section 211 generates a response signal (ACK / NACK or HARQ-ACK) using the error detection result inputted from decoding section 210 , and outputs the response signal to encoding section 212 .

[0079] Furthermore, the control unit 211 outputs, to the extraction unit 204, information about the radio resource of the downlink data or control signal, which information is included in the control information input from the decoding unit 206 or the decoding unit 208.

[0080] Based on the information input from control section 211 , coding section 212 performs error correction coding on the response signal (bit sequence), and outputs the coded response signal (bit sequence) to modulation section 213 .

[0081] Modulation section 213 modulates the response signal input from encoding section 212 based on information input from control section 211 and outputs the modulated response signal (modulation symbol sequence) to signal allocation section 216.

[0082] The encoding unit 214 performs error correction encoding on the uplink data (transmission bit sequence) based on the information input from the control unit 211, and outputs the encoded uplink data (bit sequence) to the modulation unit 215.

[0083] The modulation unit 215 modulates the uplink data input from the encoding unit 214 based on the information input from the control unit 211, and outputs the modulated uplink data (modulation symbol sequence) to the signal allocation unit 216.

[0084] The signal allocation unit 216 maps the response signal (modulation symbol sequence) input from the modulation unit 213 to radio resources (for example, PUCCH resources or PUSCH resources) instructed by the control unit 211. Furthermore, the signal allocation unit 216 maps the uplink data (modulation symbol sequence) input from the modulation unit 215 to PUSCH resources instructed by the control unit 211. For example, as will be described later, the signal allocation unit 216 may allocate resources to both the response signal and uplink data having different types of reliability, delay requirement, or use case (or service), or may drop all of the resources or puncture some of the resources. The signal allocation unit 216 outputs the signal onto which the response signal or the uplink data is mapped to the IFFT unit 217.

[0085] IFFT unit 217 performs transmission waveform generation processing such as OFDM on the signal input from signal allocation unit 216. In the case of OFDM transmission that adds a CP (Cyclic Prefix), IFFT unit 217 adds a CP (not shown). Alternatively, if IFFT unit 217 generates a single-carrier waveform, a DFT (Discrete Fourier Transform) unit may be added (not shown) before signal allocation unit 216. IFFT unit 217 outputs the generated transmission waveform to transmission unit 218.

[0086] Transmitting section 218 performs RF (Radio Frequency) processing such as D / A (Digital-to-Analog) conversion and up-conversion on the signal input from IFFT section 217 and transmits the radio signal to base station 100 via antenna 201.

[0087] [Operations of Base Station 100 and Terminal 200] The operations of base station 100 and terminal 200 having the above configuration will now be described in detail.

[0088] FIG. 4 shows a processing flow of base station 100 and terminal 200 according to this embodiment.

[0089] Base station 100 transmits information relating to the amount of resources of UCI to be multiplexed onto a PUSCH to terminal 200 (ST101). Terminal 200 acquires information relating to the amount of resources of UCI to be multiplexed onto a PUSCH notified from base station 100 (ST102). The information relating to the amount of resources of UCI to be multiplexed onto a PUSCH includes, for example, a parameter (for example, a parameter shown in equation (1)) that controls the amount of resources of UCI to be multiplexed onto a PUSCH.

[0090] Base station 100 transmits DCI including information about downlink data to terminal 200 (ST103). Terminal 200 acquires scheduling information for downlink data or information about the PUCCH, for example, based on the DCI notified from base station 100 (ST104).

[0091] Base station 100 transmits downlink data to terminal 200 (ST105). Terminal 200 receives downlink data (PDSCH), for example, based on DCI notified from base station 100 (ST106).

[0092] Base station 100 transmits DCI including information about uplink data to terminal 200 (ST107). Terminal 200 acquires information about the PUSCH, for example, based on the DCI reported from base station 100 (ST108).

[0093] Terminal 200 controls operations related to uplink signals (for example, UCI and uplink data) according to requirements for response signals or uplink data (in other words, reliability, delay requirement, or type of use case (service)) (ST109).

[0094] Based on the determined operation, terminal 200 transmits an uplink signal (including, for example, UCI or uplink data) to base station 100 using PUCCH or PUSCH (ST110). Base station 100 receives the uplink signal transmitted from terminal 200 (ST111).

[0095] In FIG. 4, the order of the processes of ST103 to ST106 and ST107 to ST108 may be reversed.

[0096] Next, a method for controlling operations related to UCI transmission in terminal 200 (for example, the processing in ST109 in FIG. 4) will be described in detail.

[0097] In this embodiment, the operation of terminal 200 when PUCCH transmission including a response signal corresponding to URLLC and PUSCH transmission including uplink data (for example, UL-SCH) corresponding to eMBB overlap in time will be described.

[0098] In this embodiment, it is not limited to the case where the PUCCH includes a response signal corresponding to URLLC and the PUSCH includes uplink data corresponding to eMBB, but it is also acceptable, for example, if the signal included in the PUCCH is a signal with stricter requirements such as high reliability or low delay, like URLLC, compared to the signal included in the PUSCH.

[0099] Terminal 200 determines a processing manner (e.g., a transmission method or parameters) of the response signal or uplink data according to the reliability of the response signal (e.g., a target error rate or a target BLER of the response signal). In other words, terminal 200 varies the transmission method or parameters of the response signal or uplink data according to the reliability of the response signal corresponding to URLLC.

[0100] As an example of generating a difference in the transmission of a response signal or uplink data, a case where the reliability of the response signal differs will be described. For example, in URLLC, if the target error rate of the first data transmission is high (for example, BLER=10 -1 ) Response signal for downlink data and the target error rate for the first data transmission is low (e.g., BLER=10 -5 ) The transmission method or parameters may be different between the response signal to the downlink data and the response signal to the downlink data.

[0101] If the target error rate for the first data transmission is high, the response signal must have high reliability to ensure that the data is retransmitted. On the other hand, if the target error rate for the first data transmission is low, data errors are less likely to occur, so the response signal does not require such high reliability.

[0102] Therefore, when a PUCCH transmission including a response signal that does not require high reliability (for example, a response signal for downlink data with a low target error rate for the first data transmission) overlaps in time with a PUSCH transmission including uplink data corresponding to eMBB, terminal 200 multiplexes the response signal onto the PUSCH using, for example, a method or parameters similar to the methods or parameters described in Non-Patent Documents 2 and 3 mentioned above.

[0103] On the other hand, when a PUCCH transmission including a response signal requiring high reliability (for example, a response signal for downlink data with a high target error rate for the first data transmission) overlaps in time with a PUSCH transmission including uplink data corresponding to eMBB, terminal 200 transmits the response signal on the PUCCH or multiplexes the response signal onto the PUSCH using, for example, a method or parameters different from the methods or parameters described in Non-Patent Documents 2 and 3.

[0104] The following three methods (Options 1, 2, and 3) are described as examples of methods for multiplexing a response signal onto a PUSCH when PUCCH transmission including a response signal requiring high reliability (for example, a response signal with a target error rate equal to or lower than a predetermined value) and PUSCH transmission including uplink data corresponding to eMBB overlap in time.

[0105] [Option 1] In Option 1, terminal 200 drops (in other words, cancels transmission of) the PUSCH (that is, uplink data) of eMBB and transmits a response signal using the PUCCH.

[0106] FIG. 5 shows an example of the operation of the terminal 200 in Option 1.

[0107] As shown in FIG. 5, when a PUCCH (URLLC PUCCH) including a response signal corresponding to URLLC and a PUSCH (eMBB PUSCH) including uplink data corresponding to eMBB are transmitted in the same slot, terminal 200 drops the eMBB PUSCH (uplink data) and transmits the URLLC PUCCH (response signal).

[0108] According to Option 1, the PUSCH transmission of eMBB does not affect the transmission of response signals for URLLC, which require high reliability, and therefore the quality of the response signals, which require high reliability, can be guaranteed.

[0109] Furthermore, according to Option 1, terminal 200 simply needs to drop eMBB PUSCH (uplink data), and no complex processing is required in terminal 200, which has the advantage that implementation in terminal 200 is easy.

[0110] In Option 1, terminal 200 may drop uplink data (UL-SCH) in the eMBB PUSCH and transmit a response signal using the PUSCH.

[0111] [Option 2] In Option 2, terminal 200 does not transmit (punctures) the eMBB PUSCH (uplink data) in a section that overlaps in time with the transmission section of the PUCCH for URLLC within the same slot, among the transmission sections of the eMBB PUSCH. In other words, terminal 200 transmits uplink data using the PUSCH in a section that does not overlap in time with the transmission section of the PUCCH for URLLC within the same slot, among the transmission sections of the eMBB PUSCH.

[0112] FIG. 6 shows an example of the operation of the terminal 200 in Option 2.

[0113] As shown in Fig. 6, when transmission of a PUCCH (URLLC PUCCH) including a response signal corresponding to URLLC and transmission of a PUSCH (eMBB PUSCH) including uplink data corresponding to eMBB occur in the same slot, terminal 200 transmits the URLLC PUCCH (e.g., the response signal). Also, as shown in Fig. 6, terminal 200 punctures the eMBB PUSCH (uplink data) in a section that temporally overlaps with the URLLC PUCCH transmission section within the same slot, and transmits the eMBB PUSCH (e.g., uplink data) in a section other than the section that temporally overlaps with the URLLC PUCCH transmission section.

[0114] In transmissions compatible with eMBB, the amount of data to be transmitted is relatively large. For this reason, transmissions compatible with eMBB are slot-based transmissions (e.g., transmissions using all or most of one slot). On the other hand, in transmissions compatible with URLLC, the amount of data to be transmitted is relatively small. Furthermore, in transmissions compatible with URLLC, it is expected that the main use case will be non-slot-based transmissions (e.g., transmissions using several symbols) in order to achieve low latency.

[0115] Therefore, it is assumed that the interval in which transmission corresponding to URLLC overlaps in time with transmission corresponding to eMBB is several symbols within a slot, that is, part of the transmission interval corresponding to eMBB, as shown in Fig. 6. For this reason, terminal 200 does not drop all transmission corresponding to eMBB after transmission corresponding to URLLC, but rather does not transmit (punctures) the interval in the transmission interval corresponding to eMBB that overlaps in time with the transmission interval corresponding to URLLC, as shown in Fig. 6, thereby making it possible to suppress deterioration of the transmission quality and frequency efficiency of eMBB.

[0116] In Option 2, terminal 200 may puncture uplink data in the eMBB PUSCH and transmit a response signal in the section where the uplink data is punctured.

[0117] [Option 3] In Option 3, terminal 200 multiplexes a response signal for URLLC onto the PUSCH for eMBB and transmits the result.

[0118] FIG. 7 shows an example of the operation of the terminal 200 in Option 3.

[0119] 7, when transmission of a PUCCH (URLLC PUCCH) including a response signal corresponding to URLLC and transmission of a PUSCH (eMBB PUSCH) including uplink data corresponding to eMBB occur in the same slot, terminal 200 multiplexes the response signal (in other words, URLLC UCI) included in the URLLC PUCCH onto the PUSCH. Terminal 200 then transmits the eMBB PUSCH signal onto which the response signal (URLLC UCI) is multiplexed.

[0120] For example, base station 100 may set β in equation (1) for terminal 200 depending on the required condition (for example, reliability) of the response signal. offset HARQ-ACK and a different value is set for at least one of the values.

[0121] For example, β depending on the reliability of the response signal offset HARQ-ACK The values ​​of and α may be explicitly set in terminal 200 by a terminal-specific upper layer signal, or a coefficient according to the reliability of the response signal may be introduced. For example, when a highly reliable response signal is multiplexed, terminal 200 may set β offset HARQ-ACK and the value of α is multiplied by a coefficient, and the multiplied value of β offset HARQ-ACK The values ​​of and α may be used to calculate the amount of resources shown in equation (1). For example, the coefficient according to the reliability of the response signal is offset HARQ-ACK and α may have a common value or different values.

[0122] This allows terminal 200 to allocate appropriate resources to response signals in the PUSCH according to the reliability of the response signals.

[0123] In Option 3, the following methods (Options 3-1 to 3-3) may also be applied.

[0124] <option 3-1> In equation (1), the value calculated by the following equation (2) indicates the amount of resources required for a response signal in the PUSCH, and the value calculated by the following equation (3) indicates the upper limit of the amount of resources to be allocated to the response signal.

number

number

[0125] In Option 3-1, terminal 200 multiplexes a response signal onto a PUSCH when the amount of resources required for the response signal calculated by equation 2 does not exceed the upper limit value calculated by equation 3. Thus, terminal 200 transmits uplink data and the response signal on the PUSCH.

[0126] On the other hand, when the amount of resources required for a response signal calculated by equation (2) exceeds the upper limit calculated by equation (3), terminal 200, for example, drops uplink data and multiplexes the response signal onto the PUSCH. Thus, terminal 200 transmits the response signal on the PUSCH without transmitting uplink data.

[0127] Alternatively, if the amount of resources required for the response signal calculated by equation (2) exceeds the upper limit value calculated by equation (3), terminal 200 may, for example, drop the PUSCH (uplink data) and transmit the response signal using the PUCCH.

[0128] In Option 3-1, as long as the amount of resources required for the response signal does not exceed an upper limit, terminal 200 can allocate sufficient resources to the transmission of a response signal for URLLC, which requires high reliability, and can multiplex and transmit uplink data corresponding to eMBB and the response signal. Therefore, Option 3-1 can suppress deterioration in uplink resource utilization efficiency while ensuring the transmission of a highly reliable response signal.

[0129] Furthermore, in Option 3-1, if the amount of resources required for a response signal exceeds an upper limit, that is, if there are insufficient resources for the response signal, terminal 200 drops the uplink data. As a result, Option 3-1 can guarantee the quality of a response signal that requires high reliability with priority over other signals.

[0130] < / option> <option 3-2> In Option 3-2, terminal 200 multiplexes a response signal onto a PUSCH when the amount of resources required for the response signal calculated by equation 2 does not exceed the upper limit value calculated by equation 3. Thus, terminal 200 transmits uplink data and the response signal on the PUSCH.

[0131] On the other hand, when the amount of resources required for the response signal calculated by equation (2) exceeds the upper limit value calculated by equation (3), terminal 200 multiplexes the response signal onto the PUSCH and increases the transmission power of the PUSCH within a range that does not exceed the maximum transmission power of terminal 200.

[0132] Here, the parameter for increasing the transmission power of the PUSCH may be notified in advance from base station 100 to terminal 200 by a terminal-specific higher layer signal or a UL grant (DCI) for scheduling uplink data, or a fixed value may be specified in advance.

[0133] Furthermore, when the transmission power of the PUSCH exceeds the maximum transmission power of terminal 200, terminal 200 drops uplink data in the PUSCH, multiplexes a response signal into the PUSCH, and transmits the PUSCH (in other words, the response signal) at the maximum transmission power of terminal 200. Alternatively, terminal 200 may drop the PUSCH and transmit the response signal using the PUCCH.

[0134] In Option 3-2, as long as the amount of resources required for the response signal does not exceed an upper limit, terminal 200 can allocate sufficient resources to the transmission of a response signal for URLLC, which requires high reliability, and can multiplex and transmit uplink data corresponding to eMBB and the response signal, as in Option 3-1. Therefore, Option 3-2 can suppress deterioration in uplink resource utilization efficiency while ensuring the transmission of a highly reliable response signal.

[0135] Furthermore, with Option 3-2, even if the amount of resources required for a response signal exceeds an upper limit, that is, even if the resources required for the response signal are insufficient, terminal 200 can improve the quality of uplink transmission by increasing the transmission power of the uplink signal within a range that does not exceed the maximum transmission power of terminal 200. Therefore, with Option 3-2, it is possible to suppress deterioration in uplink resource utilization efficiency while ensuring transmission of a highly reliable response signal.

[0136] In addition, in Option 3-2, if the amount of resources required for the response signal is insufficient and the set transmission power exceeds the maximum transmission power, terminal 200 can guarantee the quality of the response signal, which requires high reliability, by dropping the uplink data, with priority over other signals.

[0137] < / option> <option 3-3> In Option 3-3, when terminal 200 is notified of specific parameters from base station 100, terminal 200 drops uplink data in the PUSCH and multiplexes a response signal onto the PUSCH to transmit the response signal. Alternatively, when terminal 200 is notified of specific parameters from base station 100, terminal 200 may drop the PUSCH (uplink data) and transmit the response signal using the PUCCH.

[0138] The specific parameter notified from the base station 100 may be, for example, a parameter for calculating the amount of resources required for a response signal. For example, β in Equation (1) offset HARQ-ACK If the value of is a specific value (for example, 0), terminal 200 determines to drop uplink data or PUSCH. Note that the specific parameter notified from base station 100 is β in equation (1). offset HARQ-ACK The present invention is not limited to the specific value of , and other parameters may be used.

[0139] In this way, in Option 3-3, terminal 200 determines the transmission method of a response signal or uplink data based on parameters notified from base station 100. Therefore, terminal 200 can determine whether to drop uplink data or PUSCH without calculating the amount of resources required for a response signal and comparing it with an upper limit, as in Option 3-1 or Option 3-2, which has the advantage of simplifying the processing in terminal 200.

[0140] The above describes an example of a method (Options 1, 2, and 3) for multiplexing a response signal onto a PUSCH.

[0141] As described above, in the present embodiment, when PUSCH transmission including uplink data corresponding to eMBB and PUCCH transmission including UCI (for example, a response signal) corresponding to URLLC overlap in time, terminal 200 determines a processing mode (transmission method or parameters) for the uplink data and UCI according to requirements for UCI. Terminal 200 then transmits UCI, or UCI and uplink data, based on the determined processing mode.

[0142] As a result, terminal 200 can perform appropriate terminal operation or resource allocation according to the reliability of the UCI (for example, response signal), and perform uplink transmission that satisfies the requirements of the response signal corresponding to URLLC.

[0143] As described above, according to the present embodiment, terminal 200 can appropriately transmit uplink signals.

[0144] The method for calculating the amount of resources required for a response signal is not limited to the calculation formula shown in formula (1). For example, the calculation formula for calculating the amount of resources required for a response signal is the β offset HARQ-ACK It is sufficient if the parameter includes a parameter for controlling the coding rate of the response signal (in other words, the amount of resources) corresponding to α in equation (1) and a parameter for controlling the upper limit of the amount of resources corresponding to α in equation (1).

[0145] In addition, NR supports two types of PUSCH transmissions including uplink data: "grant-based PUSCH transmission," in which the radio resources for transmitting the PUSCH are dynamically instructed by a UL grant from the base station; and "grant-free PUSCH transmission" (also called "configured grant PUSCH transmission"), in which the terminal transmits the PUSCH using radio resources that are quasi-statically allocated in advance when data is generated, without a UL grant from the base station.

[0146] When terminal 200 multiplexes UCI onto a PUSCH and transmits the PUSCH, in grant-based PUSCH transmission, base station 100 knows that UCI will be multiplexed onto a PUSCH, and can therefore allocate radio resources that take UCI multiplexing into consideration when instructing radio resources by grant (UL grant). On the other hand, in grant-free PUSCH transmission, base station 100 cannot allocate radio resources to terminal 200 in advance that take UCI multiplexing into consideration.

[0147] Therefore, Option 1 (see, for example, FIG. 5), Option 2 (see, for example, FIG. 6), or Option 3 (see, for example, FIG. 7) may be switched and applied between grant-based PUSCH transmission and grant-free PUSCH transmission. For example, terminal 200 applies Option 3 to grant-based PUSCH transmission and multiplexes UCI onto the PUSCH for transmission. On the other hand, terminal 200 applies Option 1 or Option 2 to grant-free PUSCH transmission, drops the PUSCH, and transmits a response signal using a PUCCH. This allows terminal 200 to appropriately transmit response signals in accordance with grant-based PUSCH transmission and grant-free PUSCH transmission.

[0148] In addition, in this embodiment, in the case where PUCCH transmission including a response signal corresponding to URLLC and PUSCH transmission including uplink data corresponding to eMBB overlap in time, a method of transmitting a response signal or uplink data, or a method of causing differences in parameters, depending on the reliability of the response signal corresponding to URLLC, has been described.

[0149] However, the method of transmitting an uplink signal (e.g., a response signal or uplink data) or a method of differentiating parameters are not limited to the above examples. For example, when the delay requirements of the response signal are different or when the types of use cases (or services) are different, a difference may be made between the URLLC response signal and the eMBB response signal.

[0150] For example, when PUCCH transmission including a response signal to downlink data corresponding to eMBB and PUSCH transmission including uplink data corresponding to eMBB overlap in time, terminal 200 multiplexes the response signal onto the PUSCH using the same method or parameters as those described in Non-Patent Documents 2 and 3. On the other hand, when PUCCH transmission including a response signal to downlink data corresponding to URLLC overlaps in time with PUSCH transmission including uplink data corresponding to eMBB, terminal 200 may transmit the response signal using the above-mentioned Option 1, Option 2, or Option 3 method.

[0151] (Embodiment 2) A base station and a terminal according to this embodiment have the same basic configuration as base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0152] In this embodiment, as in embodiment 1, the operation of terminal 200 when PUCCH transmission including a response signal corresponding to URLLC and PUSCH transmission including uplink data (e.g., UL-SCH) corresponding to eMBB overlap in time is described.

[0153] Also, in this embodiment, the operation of terminal 200 when a PUCCH includes a plurality of response signals with different reliability, delay requests, or types of use cases (services) (in other words, request conditions) will be described.

[0154] For example, in URLLC, the target error rate for the first data transmission is high (e.g., BLER=10 -1 ) Response signal for downlink data and the target error rate for the first data transmission is low (e.g., BLER=10 -5 ) A response signal to downlink data may be included in the PUCCH. A response signal to downlink data with a high target error rate requires high reliability, whereas a response signal to downlink data with a low target error rate does not require high reliability.

[0155] In this case, since the PUCCH includes a response signal that requires high reliability, terminal 200 determines that transmission of the response signal has high priority. Therefore, terminal 200 may apply, for example, the method of Option 1, Option 2, or Option 3 described in embodiment 1.

[0156] Furthermore, in this embodiment, when a response signal is multiplexed onto a PUSCH and transmitted (for example, in the case of the above-mentioned Option 3), the transmission method or parameters of the response signal on the PUSCH are differentiated depending on the reliability of the response signal, the delay requirement, or the type of use case (service) (in other words, the requirement conditions).

[0157] As an example of generating differences in the transmission method or parameters of a response signal in PUSCH, a case where the reliability of the response signal is different will be described. For example, in URLLC, if the target error rate of the first data transmission is high (for example, BLER=10 -1 ) Response signal for downlink data and the target error rate for the first data transmission is low (e.g., BLER=10 -5 ) The transmission method or parameters may be different between the response signal to the downlink data and the response signal to the downlink data.

[0158] For example, when a response signal, which is one of the UCIs, is multiplexed into a PUSCH, the amount of resources (number of REs) Q' allocated to the response signal in the PUSCH is ACK is calculated using the following formula (4).

number

[0159] In addition, in formula (4), O ACK_total indicates the total number of bits of multiple response signals with different reliability, delay requirements, or types of use cases (services).

[0160] Furthermore, the amount of resources allocated to a response signal may be calculated for each response signal having a different reliability, delay requirement, or type of use case (service) using the following formula: Note that, as an example, two response signals (ACK1 and ACK2) will be described, but the number of multiple response signals may be three or more.

number

number

[0161] In equations (5) and (6), ACK1 represents a response signal that requires high reliability, and ACK2 represents a response signal that does not require high reliability. In this case, β in equations (5) and (6) offset HARQ-ACK A different value may be set in terminal 200 for at least one of α and β depending on the reliability of the response signal. offset HARQ-ACK The values ​​of α and β may be explicitly set by a terminal-specific higher layer signal, or a coefficient according to the reliability of the response signal may be introduced. For example, when multiplexing a highly reliable response signal, terminal 200 may use β applied to UCI on PUSCH in equations (4) and (5). offset HARQ-ACK and the value of α is multiplied by a coefficient, and the multiplied value of β offset HARQ-ACK The values ​​of and α may be applied to the calculation of the amount of resources shown in Equation (5) and Equation (6). For example, the coefficient according to the reliability of the response signal is offset HARQ-ACK and α may have a common value or different values.

[0162] This allows terminal 200 to allocate appropriate resources to response signals in the PUSCH according to the reliability of the response signals.

[0163] Furthermore, similar to the first embodiment, in Option 3, the following methods (Options 3-1 to 3-3) may be further applied.

[0164] < / option> <option 3-1> In equation (4), the value calculated by the following equation (7) indicates the amount of resources required for multiple response signals in the PUSCH, and the value calculated by the following equation (8) indicates the upper limit of the amount of resources to be allocated to multiple response signals.

number

number

[0165] In Option 3-1, terminal 200 multiplexes response signals onto a PUSCH when the amount of resources required for multiple response signals calculated by equation 7 does not exceed the upper limit value calculated by equation 8. Thus, terminal 200 transmits uplink data and response signals on the PUSCH.

[0166] On the other hand, when the amount of resources required for multiple response signals calculated by equation (7) exceeds the upper limit value calculated by equation (8), terminal 200, for example, drops uplink data and multiplexes multiple response signals onto a PUSCH. Thus, terminal 200 transmits response signals on the PUSCH without transmitting uplink data.

[0167] Alternatively, if the amount of resources required for multiple response signals calculated by equation (7) exceeds the upper limit value calculated by equation (8), terminal 200 may, for example, drop PUSCH (uplink data) and transmit multiple response signals using PUCCH.

[0168] Similarly, for a response signal (ACK1) that requires high reliability, the value calculated by the following equation (9) in equation (5) indicates the amount of resources required for the response signal (ACK1) that requires high reliability in the PUSCH, and the value calculated by the following equation (10) indicates the upper limit of the amount of resources to be allocated to the response signal that requires high reliability.

number

number

[0169] In Option 3-1, terminal 200 multiplexes a response signal (ACK1) onto a PUSCH when the amount of resources required for the response signal calculated by equation 9 does not exceed the upper limit value calculated by equation 10. Thus, terminal 200 transmits uplink data and a response signal (at least ACK1) on the PUSCH.

[0170] On the other hand, when the amount of resources required for a response signal calculated using equation (9) exceeds the upper limit value calculated using equation (10), terminal 200, for example, drops the uplink data and multiplexes the response signal onto the PUSCH. Thus, terminal 200 transmits a response signal (at least ACK1) without transmitting uplink data on the PUSCH. Alternatively, when the amount of resources required for a response signal calculated using equation (9) exceeds the upper limit value calculated using equation (10), terminal 200 may, for example, drop the PUSCH and transmit a response signal (at least ACK1) using the PUCCH.

[0171] Furthermore, for example, for an answer signal (ACK1) that does not require high reliability, the value calculated by the following equation (11) in equation (6) indicates the amount of resources required for an answer signal (ACK2) that does not require high reliability in the PUSCH, and the value calculated by the following equation (12) indicates the upper limit of the amount of resources to be allocated to an answer signal that does not require high reliability.

number

number

[0172] As shown in equation (12), the upper limit of the resource amount for the response signal (ACK2) is calculated by subtracting the upper limit of the number of response signals (RE count) from the resource amount Q' for the response signal (ACK1). ACK1 In other words, the amount of resources for the response signal (ACK2) is determined after the resources for the response signal (ACK1) are secured.

[0173] In Option 3-1, terminal 200 multiplexes a response signal (ACK2) onto a PUSCH when the amount of resources required for the response signal calculated by equation 11 does not exceed the upper limit value calculated by equation 12. Thus, terminal 200 transmits uplink data and multiple response signals (ACK1 and ACK2) on the PUSCH.

[0174] Furthermore, when the amount of resources required for response signals calculated by equation (11) exceeds the upper limit value calculated by equation (12), terminal 200, for example, multiplexes each response signal onto a PUSCH without dropping uplink data. Thus, terminal 200 transmits uplink data and multiple response signals (ACK1 and ACK2) on the PUSCH. In this case, although sufficient PUSCH resources are not allocated to the response signal (ACK2), the reliability required for the response signal (ACK2) is not high, so there is a possibility that the required condition for the reliability of ACK2 can be met.

[0175] In this way, with Option 3-1, as long as the amount of resources required for response signals does not exceed an upper limit, terminal 200 can allocate sufficient resources to the transmission of response signals for URLLC, which requires high reliability, and can multiplex and transmit uplink data corresponding to eMBB and multiple response signals. Therefore, with Option 3-1, it is possible to suppress deterioration in uplink resource utilization efficiency while ensuring the transmission of highly reliable response signals.

[0176] Furthermore, in Option 3-1, if the resources required for a response signal requiring high reliability exceed an upper limit, that is, if there are insufficient resources for a response signal requiring high reliability, terminal 200 drops the uplink data. As a result, Option 3-1 can guarantee the quality of a response signal requiring high reliability with priority over other signals.

[0177] < / option> <option 3-2> In Option 3-2, terminal 200 multiplexes multiple response signals into a PUSCH when the amount of resources required for multiple response signals calculated by equation 7 does not exceed the upper limit value calculated by equation 8. Thus, terminal 200 transmits uplink data and multiple response signals on the PUSCH.

[0178] On the other hand, when the amount of resources required for multiple response signals calculated by equation (7) exceeds the upper limit value calculated by equation (8), terminal 200 multiplexes the multiple response signals onto a PUSCH and increases the transmission power of the PUSCH within a range that does not exceed the maximum transmission power of terminal 200.

[0179] Here, the parameter for increasing the transmission power of the PUSCH may be notified in advance from base station 100 to terminal 200 by a terminal-specific higher layer signal or a UL grant (DCI) for scheduling uplink data, or a fixed value may be specified in advance.

[0180] Furthermore, when the transmission power of the PUSCH exceeds the maximum transmission power of terminal 200, terminal 200 drops uplink data in the PUSCH, multiplexes a response signal into the PUSCH, and transmits the PUSCH (in other words, the response signal) at the maximum transmission power of terminal 200. Alternatively, terminal 200 may drop the PUSCH and transmit the response signal using the PUCCH.

[0181] Next, a case will be described where the amount of resources to be allocated to each of response signals having different reliability, delay requirements, or types of use cases (services) is calculated as shown in (5) and (6).

[0182] Terminal 200 multiplexes the response signal (ACK1) onto the PUSCH when the amount of resources required for the response signal (ACK1) that requires high reliability calculated by equation 9 does not exceed the upper limit value calculated by equation 10. Thus, terminal 200 transmits uplink data and the response signal (at least ACK1) on the PUSCH.

[0183] On the other hand, when the amount of resources required for a response signal (ACK1) that requires high reliability calculated by equation (9) exceeds the upper limit value calculated by equation (10), terminal 200 multiplexes the response signal (ACK1) onto the PUSCH and increases the transmission power of the PUSCH within a range that does not exceed the maximum transmission power of terminal 200.

[0184] Here, the parameter for increasing the transmission power of the PUSCH may be notified in advance from base station 100 to terminal 200 by a terminal-specific higher layer signal or a UL grant (DCI) for scheduling uplink data, or a fixed value may be specified in advance.

[0185] Furthermore, when the transmission power of the PUSCH exceeds the maximum transmission power of terminal 200, terminal 200 drops uplink data in the PUSCH, multiplexes a response signal (ACK1) onto the PUSCH, and transmits the PUSCH at the maximum transmission power of terminal 200. Alternatively, terminal 200 may drop the PUSCH and transmit the response signal (ACK1) using the PUCCH.

[0186] Furthermore, terminal 200 multiplexes the response signal (ACK2) onto the PUSCH when the amount of resources required for the response signal (ACK2) that does not require high reliability calculated by equation 11 does not exceed the upper limit value calculated by equation 12. Thus, terminal 200 transmits uplink data and multiple response signals (for example, ACK1 and ACK2) on the PUSCH.

[0187] On the other hand, when the amount of resources required for a response signal (ACK2) that does not require high reliability calculated by equation (11) exceeds the upper limit value calculated by equation (12), terminal 200 multiplexes each response signal (ACK1 and ACK2) onto the PUSCH without increasing the transmission power of the PUSCH. In this case, although sufficient PUSCH resources are not allocated to the response signal (ACK2), the reliability required for the response signal (ACK2) is not high, so there is a possibility that the requirement regarding the reliability of ACK2 can be met.

[0188] In Option 3-2, as long as the amount of resources required for a response signal requiring high reliability does not exceed an upper limit, terminal 200 can allocate sufficient resources to the transmission of a response signal for URLLC requiring high reliability, and can multiplex and transmit uplink data corresponding to eMBB and the response signal, as in Option 3-1. Therefore, Option 3-2 can suppress deterioration in uplink resource utilization efficiency while ensuring the transmission of a response signal with high reliability.

[0189] Furthermore, with Option 3-2, even if the amount of resources required for a response signal requiring high reliability exceeds an upper limit, that is, even if the resources required for the response signal are insufficient, terminal 200 can improve the quality of uplink transmission by increasing the transmission power of the uplink signal within a range that does not exceed the maximum transmission power of terminal 200. Therefore, with Option 3-2, it is possible to suppress deterioration in uplink resource utilization efficiency while ensuring transmission of a highly reliable response signal.

[0190] In addition, in Option 3-2, if the amount of resources required for a response signal requiring high reliability is insufficient and the set transmission power exceeds the maximum transmission power, terminal 200 can guarantee the quality of the response signal requiring high reliability by dropping the uplink data, giving priority to other signals.

[0191] < / option> <option 3-3> In Option 3-3, terminal 200 drops uplink data in the PUSCH and multiplexes multiple response signals onto the PUSCH when specific parameters are notified from base station 100 to terminal 200. Alternatively, when specific parameters are notified from base station 100, terminal 200 may drop the PUSCH (uplink data) and transmit multiple response signals using the PUCCH.

[0192] The specific parameter notified from the base station 100 may be, for example, a parameter for calculating the amount of resources required for a response signal. For example, β offset HARQ-ACK If the value of is a specific value (for example, 0), terminal 200 determines to drop uplink data or PUSCH. Note that the specific parameter notified from base station 100 is β in equation (4), equation (5), or equation (6). offset HARQ-ACK The present invention is not limited to the specific value of , and other parameters may be used.

[0193] In this way, in Option 3-3, terminal 200 determines a method for transmitting multiple response signals or uplink data based on parameters notified from base station 100. Therefore, terminal 200 can determine whether to drop uplink data or PUSCH without calculating the amount of resources required for multiple response signals and comparing it with an upper limit value, which has the advantage of simplifying the processing of terminal 200.

[0194] So far, examples of methods (Options 3-1, 3-2, and 3-3) for multiplexing response signals onto PUSCH in this embodiment have been described.

[0195] As described above, in the present embodiment, when PUSCH transmission including uplink data corresponding to eMBB and PUCCH transmission including multiple UCIs (e.g., multiple response signals) corresponding to URLLC overlap in time, terminal 200 determines processing modes (transmission methods or parameters) for the uplink data and multiple UCIs according to requirements for the multiple UCIs. Then, terminal 200 transmits the multiple UCIs, or the multiple UCIs and uplink data, based on the determined processing mode.

[0196] As a result, even if multiple response signals with different reliabilities are included in the PUCCH, terminal 200 can perform appropriate terminal operation or resource allocation according to the reliabilities of the multiple response signals, and perform uplink transmission that meets the requirements of the response signals corresponding to URLLC.

[0197] As described above, according to the present embodiment, terminal 200 can appropriately transmit uplink signals.

[0198] The method for calculating the amount of resources required for a response signal is not limited to the calculation formula shown in formula (4), formula (5), or formula (6). For example, the calculation formula for calculating the amount of resources required for a response signal includes the β offset HARQ-ACK and a parameter that controls the upper limit of the resource amount corresponding to α in equation (4), equation (5), or equation (6).

[0199] Furthermore, in this embodiment, for response signals with different reliability, delay requirements, or types of use cases (services), terminal 200 may apply different coding to generate HARQ-ACK bits, or may apply one coding to generate HARQ-ACK bits.

[0200] For example, performing different encoding processes on multiple response signals increases the amount of processing in terminal 200, which may complicate implementation. On the other hand, if terminal 200 performs one encoding process, the implementation of terminal 200 can be simplified, but it is necessary to consider the capability (UE capability, hereinafter referred to as "N1") related to the processing time required from receiving downlink data to decoding the downlink data, generating a response signal, and transmitting the response signal.

[0201] In NR, terminal 200 reports “N1” to base station 100.

[0202] Base station 100 sets the slot position of the PUCCH for terminal 200 to transmit a response signal to the downlink data (or the time from the slot in which downlink data is received to the slot in which PUCCH (e.g., a response signal) is transmitted: "PDSCH-to-HARQ-ACK timing") and notifies terminal 200. At this time, base station 100 cannot set and notify a value for the PDSCH-to-HARQ-ACK timing that exceeds the processing capability (N1) of terminal 200 reported by terminal 200 (in other words, a value smaller than N1).

[0203] In the present embodiment, terminal 200 defines capabilities (N1) for transmitting response signals with different reliability, delay requirements, or types of use cases (or services), and reports these to base station 100. Terminal 200 may also determine coding methods for response signals with different reliability, delay requirements, or types of use cases (or services), based on the value of PDSCH-to-HARQ-ACK timing configured and reported by base station 100 and the defined value of N1.

[0204] For example, terminal 200 has two or more capabilities (N1) related to the processing time required from receiving downlink data to decoding the data, generating a response signal, and transmitting a PUCCH, depending on the reliability, delay requirement, or type of use case (or service). Terminal 200 reports two or more capabilities (N1) to base station 100. As an example, terminal 200 may have two UE capabilities: N1 for eMBB (hereinafter referred to as "N1_X" or "N1_eMBB") and N1 for URLLC (hereinafter referred to as "N1_Y" or "N1_URLLC"). For example, since URLLC is likely to require lower delay than eMBB, N1 for URLLC may be set to a smaller value than N1 for eMBB.

[0205] Regarding the identification of the slot position of the PUCCH (PDSCH-to-HARQ-ACK timing) for transmitting a response signal for downlink data, the base station 100 notifies a set of quasi-static slot positions by a terminal-specific upper layer signal (e.g., RRC signaling), and notifies which PDSCH-to-HARQ-ACK timing from the set will actually be used by a DCI that allocates downlink data.

[0206] When response signals corresponding to data transmissions with different reliability, delay requirements, or types of use cases (or services) occur simultaneously within the same slot, terminal 200 determines how to process the response signals based on the PDSCH-to-HARQ-ACK timing values ​​for each response signal and the capability (N1) of terminal 200.

[0207] For example, if the minimum value of the PDSCH-to-HARQ-ACK timing value for each response signal is equal to or greater than N1_X or N1_eMBB, terminal 200 performs common coding processing on each response signal to generate an HARQ-ACK bit.

[0208] On the other hand, if the value of the PDSCH-to-HARQ-ACK timing for a response signal requiring high reliability or low delay or a response signal corresponding to URLLC is less than N1_X or N1_eMBB, terminal 200 cannot perform a common coding process for each response signal. In this case, terminal 200 applies different coding methods to each response signal to generate HARQ-ACK bits.

[0209] This allows the encoding process to be standardized as much as possible depending on the processing capacity of the terminal 200, thereby reducing an increase in the amount of processing by the terminal 200 or reducing the complexity of implementation.

[0210] (Embodiment 3) A base station and a terminal according to this embodiment have the same basic configuration as base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0211] In the first and second embodiments, a case has been described in which PUCCH transmission including a response signal corresponding to URLLC and PUSCH transmission including uplink data corresponding to eMBB overlap in time. In contrast, in the present embodiment, an operation in terminal 200 will be described in which PUCCH transmission including a response signal corresponding to eMBB and PUSCH transmission including uplink data (for example, UL-SCH) corresponding to URLLC overlap in time.

[0212] In this embodiment, it is not limited to the case where the PUCCH includes a response signal corresponding to eMBB and the PUSCH includes uplink data corresponding to URLLC, but it is also acceptable, for example, if the signal included in the PUSCH is a signal with stricter requirements such as high reliability or low delay, like URLLC, compared to the signal included in the PUCCH.

[0213] Terminal 200 determines a processing manner (e.g., a transmission method or parameters) of a response signal or uplink data according to the reliability of the uplink data (e.g., a target error rate or a target BLER of the uplink data). In other words, terminal 200 varies the transmission method or parameters of the response signal or uplink data according to the reliability of the uplink data corresponding to URLLC.

[0214] As an example of causing a difference in the transmission of a response signal or uplink data, a case where the reliability of uplink data is different will be described. For example, in URLLC, when the target error rate is high (for example, BLER=10 -1 ) uplink data and a low target error rate (e.g., BLER=10 -5 ) The transmission method or parameters may be different between the uplink data and the HS-1 data.

[0215] High reliability is not required for uplink data with a high target error rate, whereas high reliability is required for uplink data with a low target error rate.

[0216] Therefore, when a PUSCH transmission including uplink data that does not require high reliability (e.g., a data signal with a high target error rate) overlaps in time with a PUCCH transmission including a response signal to downlink data corresponding to eMBB, terminal 200 multiplexes the response signal onto the PUSCH using, for example, a method or parameters similar to the methods or parameters described in Non-Patent Documents 2 and 3 mentioned above.

[0217] On the other hand, when a PUSCH transmission including uplink data requiring high reliability (e.g., a data signal with a low target error rate) overlaps in time with a PUCCH transmission including a response signal to downlink data corresponding to eMBB, the terminal 200 transmits the response signal on the PUCCH or multiplexes the response signal onto the PUSCH using, for example, a method or parameters different from the methods or parameters described in Non-Patent Documents 2 and 3.

[0218] The following three methods (Options 1, 2, and 3) are described as examples of methods for multiplexing a response signal onto a PUSCH when a PUSCH transmission including uplink data requiring high reliability (for example, uplink data with a target error rate equal to or lower than a predetermined value) and a PUCCH transmission including a response signal to downlink data corresponding to eMBB overlap in time.

[0219] [Option 1] In Option 1, terminal 200 drops (in other words, cancels transmission of) the PUCCH (for example, a response signal) of eMBB and transmits uplink data using the PUSCH.

[0220] FIG. 8 shows an example of the operation of the terminal 200 in Option 1.

[0221] As shown in FIG. 8, when transmission of a PUSCH (URLLC PUSCH) including uplink data corresponding to URLLC and transmission of a PUCCH (eMBB PUCCH) including a response signal to downlink data corresponding to eMBB occur in the same slot, terminal 200 drops the eMBB PUCCH (response signal) and transmits the URLLC PUSCH (uplink data).

[0222] According to Option 1, PUSCH transmission for eMBB does not affect PUSCH transmission for URLLC, which requires high reliability, and therefore the quality of uplink data, which requires high reliability, can be guaranteed.

[0223] Furthermore, according to Option 1, terminal 200 simply needs to drop the eMBB PUCCH (response signal), and no complex processing is required in terminal 200, which has the advantage that implementation in terminal 200 is easy.

[0224] [Option 2] In Option 2, terminal 200 does not transmit (punctures) the eMBB PUCCH (e.g., a response signal) in a section that overlaps in time with the transmission section of the PUSCH for URLLC within the same slot of the eMBB PUCCH transmission section. In other words, terminal 200 transmits a response signal using the PUCCH in a section that does not overlap in time with the transmission section of the PUSCH for URLLC within the same slot of the eMBB PUCCH transmission section.

[0225] FIG. 9 shows an example of the operation of the terminal 200 in Option 2.

[0226] As shown in Fig. 9, when transmission of a PUSCH (URLLC PUSCH) including uplink data corresponding to URLLC and transmission of a PUCCH (eMBB PUCCH) including a response signal to downlink data corresponding to eMBB occur in the same slot, terminal 200 transmits the URLLC PUSCH (uplink data). Also, as shown in Fig. 9, terminal 200 punctures the eMBB PUCCH (e.g., response signal) in an interval that temporally overlaps with the URLLC PUSCH transmission interval within the eMBB PUCCH transmission interval in the same slot, and transmits the eMBB PUCCH (e.g., response signal) in an interval other than the interval that temporally overlaps with the URLLC PUSCH transmission interval.

[0227] In transmissions compatible with eMBB, the amount of data to be transmitted is relatively large. For this reason, transmissions compatible with eMBB are slot-based transmissions (e.g., transmissions using all or most of one slot). On the other hand, in transmissions compatible with URLLC, the amount of data to be transmitted is relatively small. Furthermore, in transmissions compatible with URLLC, it is expected that the main use case will be non-slot-based transmissions (e.g., transmissions using several symbols) in order to achieve low latency.

[0228] Therefore, it is assumed that the interval in which transmission corresponding to URLLC overlaps in time with transmission corresponding to eMBB is several symbols within a slot, that is, part of the transmission interval corresponding to eMBB, as shown in Fig. 9. For this reason, terminal 200 does not drop all transmission corresponding to eMBB after transmission corresponding to URLLC, but rather does not transmit (punctures) the interval in the transmission interval corresponding to eMBB that overlaps in time with the transmission interval corresponding to URLLC, as shown in Fig. 9, thereby making it possible to suppress deterioration of the transmission quality and frequency efficiency of eMBB.

[0229] [Option 3] In Option 3, terminal 200 multiplexes a response signal for eMBB onto the PUSCH of URLLC and transmits the result.

[0230] FIG. 10 shows an example of the operation of the terminal 200 in Option 3.

[0231] 10, when transmission of a PUCCH (eMBB PUCCH) including a response signal corresponding to eMBB and transmission of a PUSCH (URLLC PUSCH) including uplink data corresponding to URLLC occur in the same slot, terminal 200 multiplexes the response signal (in other words, eMBB UCI) included in the eMBB PUCCH onto the PUSCH. Terminal 200 then transmits a URLLC PUSCH signal onto which the response signal (eMBB UCI) is multiplexed.

[0232] For example, base station 100 may adjust β in equation (1) for terminal 200 depending on the requirements (for example, reliability) of uplink data (or PUSCH). offset HARQ-ACK and a different value is set for at least one of the values.

[0233] For example, β depending on the reliability of PUSCH offset HARQ-ACK The values ​​of and may be explicitly set in terminal 200 by a terminal-specific higher layer signal, or a coefficient according to the reliability of uplink data may be introduced. For example, when a response signal is multiplexed onto a PUSCH including highly reliable uplink data, terminal 200 may use β shown in Equation (1) offset HARQ-ACK and the value of α is multiplied by a coefficient, and the multiplied value of β offset HARQ-ACK The values ​​of and α may be applied to the calculation of the amount of resources shown in Equation (1). For example, the coefficient according to the reliability of the uplink data (or PUSCH) is offset HARQ-ACK and α may have a common value or different values.

[0234] This allows terminal 200 to allocate appropriate resources to response signals in the PUSCH according to the reliability of the uplink data (or the PUSCH).

[0235] The above describes an example of a method (Options 1, 2, and 3) for multiplexing a response signal onto a PUSCH.

[0236] As described above, in the present embodiment, when PUSCH transmission including uplink data corresponding to URLLC and PUCCH transmission including UCI (for example, a response signal) corresponding to eMBB overlap in time, terminal 200 determines a processing mode (transmission method or parameters) for the uplink data and UCI according to requirements for the uplink data. Then, terminal 200 transmits the uplink data or the UCI and uplink data based on the determined processing mode.

[0237] As a result, terminal 200 can perform appropriate terminal operation or resource allocation according to the reliability of the uplink data, and perform uplink transmission that satisfies the requirements of the uplink data corresponding to URLLC.

[0238] As described above, according to the present embodiment, terminal 200 can appropriately transmit uplink signals.

[0239] In Option 3, similarly to Option 3 (Option 3-3) in the first embodiment, when a specific parameter is notified to terminal 200 from base station 100, terminal 200 may drop the PUCCH (for example, a response signal) and transmit uplink data using the PUSCH. The specific parameter notified from base station 100 may be, for example, a parameter for calculating the amount of resources required for the response signal. For example, β in equation (1) offset HARQ-ACK If the value of is a specific value (for example, 0), terminal 200 determines to drop the PUCCH. Note that the specific parameter notified from base station 100 is β in equation (1). offset HARQ-ACK The present invention is not limited to the specific value of , and other parameters may be used.

[0240] As described above, NR supports two types of PUSCH transmissions including uplink data: "grant-based PUSCH transmission," in which the radio resources for transmitting the PUSCH are dynamically instructed by a UL grant from the base station; and "grant-free PUSCH transmission" (also called "configured grant PUSCH transmission"), in which the terminal transmits the PUSCH using radio resources that are quasi-statically allocated in advance when data is generated, without a UL grant from the base station.

[0241] When terminal 200 multiplexes UCI onto a PUSCH and transmits the PUSCH, in grant-based PUSCH transmission, base station 100 knows that UCI will be multiplexed onto a PUSCH, and can therefore allocate radio resources that take UCI multiplexing into consideration when instructing radio resources by grant (UL grant). On the other hand, in grant-free PUSCH transmission, base station 100 cannot allocate radio resources to terminal 200 in advance that take UCI multiplexing into consideration.

[0242] Therefore, Option 1 (see, for example, FIG. 8), Option 2 (see, for example, FIG. 9), or Option 3 (see, for example, FIG. 10) may be switched and applied between grant-based PUSCH transmission and grant-free PUSCH transmission. For example, terminal 200 applies Option 3 to grant-based PUSCH transmission and multiplexes UCI onto the PUSCH for transmission. On the other hand, terminal 200 applies Option 1 or Option 2 to grant-free PUSCH transmission, drops the PUCCH, and transmits uplink data using the PUSCH. This allows terminal 200 to appropriately transmit response signals in response to grant-based PUSCH transmission and grant-free PUSCH transmission.

[0243] In addition, in this embodiment, in the case where PUSCH transmission including uplink data corresponding to URLLC and PUCCH transmission including a response signal to downlink data corresponding to eMBB overlap in time, a method of transmitting a response signal or uplink data, or a method of causing differences in parameters, depending on the reliability of the uplink data corresponding to URLLC, has been described.

[0244] However, the method of transmitting an uplink signal (e.g., a response signal or uplink data) or a method of differentiating parameters are not limited to the above examples. For example, when the delay requirements of the uplink data are different or when the types of use cases (or services) are different, differences may be made between the uplink data of URLLC and the uplink data of eMBB.

[0245] For example, when a PUSCH transmission including uplink data corresponding to eMBB (or uplink data not requiring low latency) and a PUSCH transmission including downlink data corresponding to eMBB overlap in time, terminal 200 multiplexes a response signal onto the PUSCH using a method or parameters similar to those described in Non-Patent Documents 2 and 3. On the other hand, when a PUSCH transmission including uplink data corresponding to URLLC (or uplink data requiring low latency) and a PUCCH transmission including a response signal to the downlink data corresponding to eMBB overlap in time, terminal 200 may transmit the uplink data (and the response signal) using the method of Option 1, Option 2, or Option 3 described above.

[0246] (Fourth embodiment) A base station and a terminal according to this embodiment have the same basic configuration as base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0247] In the present embodiment, the operation of terminal 200 when PUCCH transmission including a response signal corresponding to URLLC and PUSCH transmission including uplink data corresponding to URLLC overlap in time will be described.

[0248] In this embodiment, it is not limited to the case where the PUCCH includes a response signal corresponding to URLLC and the PUSCH includes uplink data corresponding to URLLC, but it is also acceptable if the signals included in both the PUSCH and the PUCCH are signals with strict requirements such as high reliability or low delay, like URLLC.

[0249] Terminal 200 determines a processing manner (e.g., a transmission method or parameters) of the response signal or uplink data according to the reliability of the response signal (e.g., a target error rate or target BLER of the response signal) and the reliability of the uplink data (e.g., a target error rate or target BLER of the uplink data). In other words, terminal 200 varies the transmission method or parameters of the response signal or uplink data according to the reliability of the response signal and the reliability of the uplink data.

[0250] Regarding the response signal, for example, in URLLC, the target error rate for the first data transmission is high (e.g., BLER=10 -1 ) The response signal for the downlink data and the target error rate for the first data transmission are low (e.g., BLER=10 -5 ) A response signal to the downlink data can be transmitted. The former response signal requires high reliability, while the latter response signal does not require high reliability.

[0251] For uplink data, for example, in URLLC, the target error rate is high (for example, BLER=10 -1 ) uplink data, and the target error rate is low (e.g., BLER=10 -5 ) uplink data can be transmitted. The former uplink data does not require high reliability, while the latter uplink data does require high reliability.

[0252] Therefore, the transmission method may be differentiated depending on the combination of the reliability of the response signal and the reliability of the uplink data.

[0253] First, when PUCCH transmission including a response signal that does not require high reliability and PUSCH transmission including uplink data that requires high reliability overlap in time, the reliability of the uplink data is higher than that of the response signal. Therefore, terminal 200 transmits uplink data, or transmits a response signal and uplink data, using a method or parameters different from the methods or parameters described in Non-Patent Documents 2 and 3, for example, based on the method described in Embodiment 3 (see, for example, FIG. 8, FIG. 9, or FIG. 10).

[0254] Next, when a PUCCH transmission including a response signal requiring high reliability overlaps in time with a PUSCH transmission including uplink data requiring high reliability, the reliability of the response signal and the reliability of the uplink data are equivalent. Therefore, terminal 200 multiplexes the response signal onto the PUSCH using, for example, a method or parameters similar to the methods or parameters described in Non-Patent Documents 2 and 3 above.

[0255] Next, when a PUCCH transmission including a response signal that does not require high reliability overlaps in time with a PUSCH transmission including uplink data that does not require high reliability, the reliability of the response signal and the reliability of the uplink data are equivalent. Therefore, terminal 200 multiplexes the response signal onto the PUSCH using, for example, a method or parameters similar to the methods or parameters described in Non-Patent Documents 2 and 3 above.

[0256] Finally, when a PUCCH transmission including a response signal requiring high reliability overlaps in time with a PUSCH transmission including uplink data not requiring high reliability, the reliability of the response signal is higher than the reliability of the uplink data. Therefore, terminal 200 transmits a response signal, or transmits a response signal and uplink data, using a method or parameters different from the methods or parameters described in Non-Patent Documents 2 and 3, for example, based on the method described in Embodiment 1 (see, for example, FIG. 5, FIG. 6, or FIG. 7).

[0257] As described above, in the present embodiment, when PUSCH transmission including uplink data corresponding to URLLC and PUCCH transmission including UCI (for example, a response signal) corresponding to URLLC overlap in time, terminal 200 determines a processing mode (transmission method or parameters) for the uplink data and UCI in accordance with requirements for both the uplink data and UCI. Then, terminal 200 transmits at least one of the uplink data and UCI based on the determined processing mode.

[0258] As a result, terminal 200 can perform appropriate terminal operation or resource allocation according to the reliability of both the uplink data and UCI, and can perform uplink transmission that satisfies the requirements of an uplink signal corresponding to URLLC.

[0259] As described above, according to the present embodiment, terminal 200 can appropriately transmit uplink signals.

[0260] (Embodiment 5) A base station and a terminal according to this embodiment have the same basic configuration as base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0261] In the present embodiment, the operation of terminal 200 when PUCCH transmission using repetition and PUSCH transmission including uplink data overlap in time will be described.

[0262] In Release 15 NR, if a PUCCH transmission with repetition applied and a PUSCH transmission containing uplink data overlap in time, the PUSCH (uplink data) is dropped. Release 15 NR does not take into account the behavior of response signals and uplink data with different reliability, delay requirements, and use cases (services).

[0263] Therefore, in the present embodiment, terminal 200 determines a processing manner (e.g., a transmission method or parameters) of the repeatedly transmitted response signal or uplink data according to the reliability of the response signal (e.g., a target error rate or target BLER of the response signal) and the reliability of the uplink data (e.g., a target error rate or target BLER of the uplink data). In other words, terminal 200 varies the transmission method or parameters of the response signal or uplink data according to the reliability of the response signal and the reliability of the uplink data.

[0264] Below, operation examples (Cases 1, 2 and 3) according to this embodiment will be described.

[0265] [Case 1] Case 1 is a case where, similarly to the first or second embodiment, PUCCH transmission to which Repetition is applied and which includes a response signal corresponding to URLLC overlaps in time with PUSCH transmission which includes uplink data corresponding to eMBB.

[0266] For example, in URLLC, the target error rate for the first data transmission is high (e.g., BLER=10 -1 ) Response signal for downlink data and the target error rate for the first data transmission is low (e.g., BLER=10 -5 ) A response signal to downlink data with a high target error rate may be transmitted. A response signal to downlink data with a high target error rate requires high reliability. On the other hand, a response signal to downlink data with a low target error rate does not require high reliability.

[0267] Therefore, when a PUCCH transmission using Repetition, which includes a response signal that does not require high reliability, and a PUSCH transmission including uplink data corresponding to eMBB overlap in time, terminal 200 drops the PUSCH (uplink data) in the same way as in Release 15 NR, as shown in FIG. 11.

[0268] Furthermore, when, for example, a PUCCH transmission using Repetition, which includes a response signal that requires high reliability, and a PUSCH transmission including uplink data corresponding to eMBB overlap in time, terminal 200 drops the PUSCH (uplink data) in the same way as in Release 15 NR, as shown in FIG. 11 .

[0269] In this way, in Case 1, when Repetition is applied to a PUCCH (URLLC PUCCH) including a response signal corresponding to URLLC, terminal 200 drops the eMBB PUSCH (uplink data) that overlaps in time, regardless of the reliability of the response signal.

[0270] [Case 2] Case 2 is a case where, similarly to the third embodiment, PUCCH transmission to which Repetition is applied and which includes a response signal corresponding to eMBB and PUSCH transmission which includes uplink data corresponding to URLLC overlap in time.

[0271] For example, in URLLC, the target error rate is high (e.g., BLER=10 -1 ) uplink data and a low target error rate (e.g., BLER=10 -5 ) uplink data can be transmitted. High reliability is not required for uplink data with a high target error rate, while high reliability is required for uplink data with a low target error rate.

[0272] Therefore, when a PUSCH transmission including uplink data that does not require high reliability and a PUCCH transmission using Repetition that includes a response signal to downlink data corresponding to eMBB overlap in time, terminal 200 drops the PUSCH (uplink data), as in Release 15 NR.

[0273] On the other hand, when a PUSCH transmission including uplink data that requires high reliability and a PUCCH transmission to which Repetition is applied including a response signal to downlink data corresponding to eMBB overlap in time, terminal 200 transmits the uplink data using a method different from Release 15 NR, or multiplexes the response signal onto the PUSCH using parameters different from Release 15 NR.

[0274] As examples of methods for multiplexing a response signal onto a PUSCH when a PUSCH transmission including uplink data requiring high reliability (for example, uplink data with a target error rate equal to or lower than a predetermined value) and a PUCCH transmission including downlink data corresponding to eMBB overlap in time, the following three methods (Options 1, 2, and 3) will be described.

[0275] [Option 1] In Option 1, terminal 200 drops (in other words, cancels transmission of) the eMBB PUCCH (e.g., response signal) and transmits uplink data using the PUSCH. At this time, terminal 200 may drop all PUCCHs (e.g., response signals) to which Repetition is applied, or may drop PUCCHs (e.g., response signals) in slots that overlap in time with PUSCHs corresponding to URLLC and transmit PUCCHs (e.g., response signals) in slots that do not overlap in time with PUSCHs corresponding to URLLC.

[0276] FIG. 12 shows an example of the operation of the terminal 200 in Option 1.

[0277] As shown in FIG. 12, when transmission of a PUSCH (URLLC PUSCH) including uplink data corresponding to URLLC and transmission of a PUCCH (eMBB PUCCH) including a response signal to downlink data corresponding to eMBB occur in the same slot, terminal 200 drops the eMBB PUCCH (response signal) in that slot and transmits the URLLC PUSCH (uplink data).

[0278] 12, terminal 200 transmits eMBB PUCCH (response signal) in slots other than the slot where PUSCH transmission and PUCCH transmission overlap. However, terminal 200 may also drop eMBB PUCCH (response signal) in slots other than the slot where PUSCH transmission and PUCCH transmission overlap. Alternatively, terminal 200 may transmit (postpone) the eMBB PUCCH (response signal) dropped in the slot where PUSCH transmission and PUCCH transmission overlap in a later slot.

[0279] According to Option 1, PUSCH transmission for eMBB does not affect PUSCH transmission for URLLC, which requires high reliability, and therefore the quality of uplink data, which requires high reliability, can be guaranteed.

[0280] Furthermore, according to Option 1, terminal 200 simply needs to drop the eMBB PUCCH (response signal), and no complex processing is required in terminal 200, which has the advantage that implementation in terminal 200 is easy.

[0281] [Option 2] In Option 2, terminal 200 does not transmit (punctures) the eMBB PUCCH (e.g., a response signal) in a section that overlaps in time with the transmission section of the PUSCH for URLLC within the same slot of the eMBB PUCCH transmission section. In other words, terminal 200 transmits a response signal using the PUCCH in a section that does not overlap in time with the transmission section of the PUSCH for URLLC within the same slot of the eMBB PUCCH transmission section.

[0282] FIG. 13 shows an example of the operation of the terminal 200 in Option 2.

[0283] As shown in Fig. 13, when transmission of a PUSCH (URLLC PUSCH) including uplink data corresponding to URLLC and transmission of a PUCCH (eMBB PUCCH) including a response signal to downlink data corresponding to eMBB occur in the same slot, terminal 200 transmits the URLLC PUSCH (uplink data). Also, as shown in Fig. 13, terminal 200 punctures the eMBB PUCCH (e.g., response signal) in an interval that temporally overlaps with the URLLC PUSCH transmission interval within the same slot, and transmits the eMBB PUCCH (e.g., response signal) in an interval other than the interval that temporally overlaps with the URLLC PUSCH transmission interval.

[0284] Also, as shown in FIG. 13, terminal 200 transmits eMBB PUCCH (for example, a response signal) in slots where PUSCH transmission and PUCCH transmission do not overlap.

[0285] In transmissions compatible with eMBB, the amount of data to be transmitted is relatively large. For this reason, transmissions compatible with eMBB are slot-based transmissions (e.g., transmissions using all or most of one slot). On the other hand, in transmissions compatible with URLLC, the amount of data to be transmitted is relatively small. Furthermore, in transmissions compatible with URLLC, it is expected that the main use case will be non-slot-based transmissions (e.g., transmissions using several symbols) in order to achieve low latency.

[0286] Therefore, it is assumed that the interval in which transmission corresponding to URLLC overlaps in time with transmission corresponding to eMBB is several symbols within a slot, that is, part of the transmission interval corresponding to eMBB, as shown in Fig. 13. For this reason, terminal 200 does not drop all transmission corresponding to eMBB after transmission corresponding to URLLC, but rather does not transmit (punctures) the interval in the transmission interval corresponding to eMBB that overlaps in time with the transmission interval corresponding to URLLC, as shown in Fig. 13, thereby making it possible to suppress deterioration of the transmission quality and frequency efficiency of eMBB.

[0287] [Option 3] In Option 3, terminal 200 multiplexes a response signal for eMBB onto a PUSCH for URLLC and transmits the multiplexed response signal. At this time, after multiplexing the response signal onto the PUSCH, terminal 200 may drop all PUCCHs (response signals) to which repetition is applied, or may drop PUCCHs (response signals) in slots that overlap in time with PUSCHs corresponding to URLLC.

[0288] FIG. 14 shows an example of the operation of the terminal 200 in Option 3.

[0289] 14, when transmission of a PUCCH (eMBB PUCCH) including a response signal corresponding to eMBB and transmission of a PUSCH (URLLC PUSCH) including uplink data corresponding to URLLC occur in the same slot, terminal 200 multiplexes the response signal (in other words, eMBB UCI) included in the eMBB PUCCH onto the PUSCH. Terminal 200 then transmits a URLLC PUSCH signal onto which the response signal (eMBB UCI) is multiplexed.

[0290] Furthermore, as shown in FIG. 14, terminal 200 transmits eMBB PUCCH (response signal) in a slot where PUSCH transmission and PUCCH transmission do not overlap.

[0291] Furthermore, in this embodiment, when a response signal is multiplexed onto a PUSCH and transmitted, the amount of resources in the PUSCH to be allocated to the response signal may be determined in accordance with a method similar to that in the third embodiment.

[0292] This allows terminal 200 to allocate appropriate resources to response signals in the PUSCH according to the reliability of the uplink data (or the PUSCH).

[0293] An example of a method of multiplexing a response signal onto a PUSCH in Case 2 (Options 1, 2, and 3) has been described above.

[0294] [Case 3] Case 3 is a case where, similarly to the fourth embodiment, PUCCH transmission including a response signal corresponding to URLLC and PUSCH transmission including uplink data corresponding to URLLC overlap in time.

[0295] Regarding the response signal, for example, in URLLC, the target error rate for the first data transmission is high (e.g., BLER=10 -1 ) The response signal for the downlink data and the target error rate for the first data transmission are low (e.g., BLER=10 -5 ) A response signal to the downlink data can be transmitted. The former response signal requires high reliability, while the latter response signal does not require high reliability.

[0296] For uplink data, for example, in URLLC, the target error rate is high (for example, BLER=10 -1 ) uplink data, and the target error rate is low (e.g., BLER=10 -5 ) uplink data can be transmitted. The former uplink data does not require high reliability, while the latter uplink data does require high reliability.

[0297] Therefore, the transmission method may be differentiated depending on the combination of the reliability of the response signal and the reliability of the uplink data.

[0298] First, when PUCCH transmission using Repetition, which includes a response signal that does not require high reliability, and PUSCH transmission, which includes uplink data that requires high reliability, overlap in time, the reliability of the uplink data is higher than the reliability of the response signal. Therefore, terminal 200 transmits uplink data using a method different from Release 15 NR, or multiplexes the response signal onto the PUSCH using parameters different from Release 15 NR, for example, based on the method described in Case 2.

[0299] Next, when a PUCCH transmission using Repetition, which includes a response signal requiring high reliability, and a PUSCH transmission, which includes uplink data requiring high reliability, overlap in time, the reliability of the response signal and the reliability of the uplink data are equivalent. Therefore, terminal 200 drops the PUSCH, for example, in the same way as in Release 15 NR.

[0300] Next, when PUCCH transmission using Repetition, which includes a response signal that does not require high reliability, and PUSCH transmission, which includes uplink data that does not require high reliability, overlap in time, the reliability of the response signal and the reliability of the uplink data are equivalent. Therefore, terminal 200 drops the PUSCH, for example, in the same way as in Release 15 NR.

[0301] Finally, when a PUCCH transmission using Repetition, which includes a response signal that requires high reliability, and a PUSCH transmission that includes uplink data that does not require high reliability, overlap in time, the reliability of the response signal is higher than the reliability of the uplink data, and the reliability of the response signal should be prioritized. Therefore, terminal 200 drops the PUSCH, for example, by the method described in Case 1.

[0302] The operation examples (Cases 1, 2 and 3) according to this embodiment have been described above.

[0303] As described above, in the present embodiment, when PUSCH transmission including uplink data and PUCCH transmission including repeatedly transmitted UCI (for example, a response signal) overlap in time, terminal 200 determines a processing mode (transmission method or parameters) for the uplink data and UCI according to requirements for both the uplink data and UCI. Then, terminal 200 transmits at least one of the uplink data and UCI based on the determined processing mode.

[0304] As a result, terminal 200 can perform appropriate terminal operation or resource allocation according to the reliability of both the uplink data and UCI, and can perform uplink transmission that satisfies the requirements of an uplink signal corresponding to URLLC.

[0305] As described above, according to the present embodiment, terminal 200 can appropriately transmit uplink signals.

[0306] In addition, NR supports two types of PUSCH transmissions including uplink data: "grant-based PUSCH transmission," in which the radio resources for transmitting the PUSCH are dynamically instructed by a UL grant from the base station; and "grant-free PUSCH transmission" (also called "configured grant PUSCH transmission"), in which the terminal transmits the PUSCH using radio resources that are quasi-statically allocated in advance when data is generated, without a UL grant from the base station.

[0307] When terminal 200 multiplexes UCI onto a PUSCH and transmits the PUSCH, in grant-based PUSCH transmission, base station 100 knows that UCI will be multiplexed onto a PUSCH, and can therefore allocate radio resources that take UCI multiplexing into consideration when instructing radio resources by grant (UL grant). On the other hand, in grant-free PUSCH transmission, base station 100 cannot allocate radio resources to terminal 200 in advance that take UCI multiplexing into consideration.

[0308] Therefore, Option 1, Option 2, or Option 3 may be applied by switching between grant-based PUSCH transmission and grant-free PUSCH transmission. For example, terminal 200 applies Option 3 to grant-based PUSCH transmission and multiplexes UCI onto the PUSCH for transmission. On the other hand, terminal 200 applies Option 1 or Option 2 to grant-free PUSCH transmission and drops the PUSCH or PUCCH. This allows terminal 200 to appropriately transmit response signals in accordance with grant-based PUSCH transmission and grant-free PUSCH transmission.

[0309] The embodiments of the present disclosure have been described above.

[0310] (1) In the above embodiment, the uplink transmission method and parameters are varied depending on the reliability of the response signal, the delay requirement, or the type of use case (or service).

[0311] Here, an example of a case where differences occur in the uplink transmission method and parameters is when the reliability of the response signal differs. For example, in URLLC, the target error rate for the first data transmission is high (for example, BLER=10 -1 ) Response signal for downlink data and the target error rate for the first data transmission is low (e.g., BLER=10 -5 ) It is possible to differentiate between the uplink transmission method and parameters for the response signal to the downlink data and the response signal to the downlink data. The former response signal requires high reliability, while the latter response signal does not require such high reliability.

[0312] Further, examples of differences in uplink transmission methods and parameters include cases where the delay requirement for the response signal is different or where the use case (or service) is different. For example, differences can be made in the uplink transmission method and parameters between a response signal corresponding to URLLC and a response signal corresponding to eMBB. The former response signal requires high reliability or low delay, while the latter response signal does not require such high reliability or low delay. Furthermore, as described above, URLLC has a high target error rate for the first data transmission (for example, BLER=10 -1 ) Response signal for downlink data and the target error rate for the first data transmission is low (e.g., BLER=10 -5 ) a response signal to the downlink data may be included.

[0313] Furthermore, examples of differences in uplink transmission methods are not limited to reliability, delay requirement, or type of use case (service), but may also include, for example, differences in physical layer parameters. For example, eMBB may be replaced with "slot-based transmission," and URLLC may be replaced with "non-slot-based transmission." Furthermore, eMBB may be replaced with "PDSCH mapping type A" or "PUSCH mapping type A," and URLLC may be replaced with "PDSCH mapping type B" or "PUSCH mapping type B." Furthermore, the present invention is not limited to transmissions corresponding to eMBB and URLLC; for example, eMBB may be replaced with a transmission having a longer transmission duration (e.g., slot length or symbol length), and URLLC may be replaced with a transmission having a shorter transmission duration than the aforementioned transmission duration.

[0314] In the present disclosure, the target error rate may be the target error rate for the first data transmission as described above, or may be the target error rate for the retransmission if a retransmission occurs. The target error rate may also be called an "instantaneous target error rate" to mean the target error rate for both the first transmission and the retransmission.

[0315] (2) As described in the above embodiments, the methods for determining the “reliability, delay requirement, or type of use case (or service)” of the response signal (in other words, the required conditions) include, for example, the following methods, Examples 1 to 5.

[0316] [Example 1: Scrambled sequence] In example 1, terminal 200 determines the reliability, delay requirement, or type of use case (service) of each response signal based on a terminal-specific scrambling sequence used in DCI that schedules downlink data transmission corresponding to each response signal.

[0317] For example, in DCI for PDSCH assuming eMBB, a C-RNTI (Cell-Radio Network Temporary Identifier) ​​or a CS-RNTI (Configured Scheduling-RNTI) or the like is used as a terminal-specific scrambling sequence. Therefore, if the detected scrambling sequence is different from the C-RNTI or CS-RNTI, terminal 200 determines that the reliability of the response signal is high, the delay requirement is strict, or the transmission is URLLC. Furthermore, if the detected scrambling sequence is the C-RNTI or CS-RNTI, terminal 200 determines that the reliability of the response signal is not high, the delay requirement is not strict, or the transmission is eMBB.

[0318] For example, the control unit 101 of the base station 100 (see, for example, FIG. 2) determines information relating to the reliability of downlink data, delay request, or type of use case (service) of the terminal 200. The determined information is output to the downlink control signal generation unit 109 of the base station 100. As described above, the downlink control signal generation unit 109 generates a DCI bit string using a scrambling sequence according to the reliability of downlink data, delay request, or type of use case (or service) of the terminal 200.

[0319] Meanwhile, decoding unit 206 (see, for example, FIG. 3) of terminal 200 outputs the detected scrambling sequence to control unit 211. Based on the obtained scrambling sequence, control unit 211 determines information related to the reliability of downlink data, delay requirement, or type of use case (service).

[0320] [Example 2: MCS table] In Example 2, terminal 200 determines the reliability, delay requirement, or type of use case (service) of each response signal based on the MCS table used for scheduling downlink data transmission corresponding to each response signal.

[0321] For example, in Release 15 NR, the target BLER is 10 -1 MCS table to achieve this, and target BLER=10 -5 You can set which MCS table to use to achieve this.

[0322] For example, the terminal 200 may set the MCS table set in the URLLC to target BLER=10. -1 On the other hand, if the MCS table set in URLLC is an MCS table for achieving target BLER=10, terminal 200 determines that the reliability required for the response signal is high. -5 If the MCS table is for achieving this, it is determined that the reliability required for the response signal is not high.

[0323] For example, the control unit 101 of the base station 100 determines information related to the reliability, delay requirement, or type of use case (service) of downlink data of the terminal 200. The determined information is output to the downlink control signal generation unit 109, the encoding unit 103, and the modulation unit 105 of the base station 100. The downlink control signal generation unit 109 includes information related to the MCS table used for downlink data transmission in a DCI bit string. Furthermore, the encoding unit 103 and the modulation unit 105 use the information related to the MCS table input from the control unit 101 to encode and modulate the downlink data.

[0324] Meanwhile, decoding section 206 of terminal 200 decodes the DCI and outputs the decoding result to control section 211. Control section 211 determines information relating to the reliability of downlink data, delay requirement, or type of use case (service), based on information relating to the MCS table obtained from the DCI.

[0325] [Example 3: PDSCH-to-HARQ-ACK timing or number of PDSCH transmission symbols] In Example 3, terminal 200 determines the reliability, delay requirement, or type of use case (service) of each response signal based on the "PDSCH-to-HARQ-ACK timing" or the number of PDSCH transmission symbols notified by DCI that schedules downlink data transmission corresponding to each response signal.

[0326] For example, if the PDSCH-to-HARQ-ACK timing is equal to or less than a predetermined value or the number of PDSCH transmission symbols is equal to or less than a predetermined number of symbols, terminal 200 determines that the delay requirement of the response signal is strict or that the response signal is for URLLC.On the other hand, if the PDSCH-to-HARQ-ACK timing is greater than a predetermined value or the number of PDSCH transmission symbols is greater than a predetermined number of symbols, terminal 200 determines that the delay requirement of the response signal is not strict or that the response signal is for eMBB.

[0327] The above-mentioned predetermined value or predetermined number of symbols may be a value determined in advance by a standard, or may be a value that can be set by base station 100 to terminal 200 by means of an upper layer signal.

[0328] For example, the control unit 101 of the base station 100 determines the PDSCH-to-HARQ-ACK timing or the number of PDSCH transmission symbols, which indicate the slot position for transmitting a response signal to downlink data from the terminal 200. The determined information is output to the downlink control signal generation unit 109, the signal allocation unit 112, and the extraction unit 118 of the base station 100. The downlink control signal generation unit 109 includes information regarding the PDSCH-to-HARQ-ACK timing or the number of PDSCH transmission symbols in the bit string of the DCI.

[0329] Meanwhile, decoding section 206 of terminal 200 decodes the DCI and outputs the decoded result to control section 211. Control section 211 determines information related to the reliability of downlink data, delay requirement, or type of use case (service), based on information related to the PDSCH-to-HARQ-ACK timing or the number of PDSCH transmission symbols obtained from the DCI.

[0330] [Example 4: CQI table] In Example 4, terminal 200 determines the reliability, delay requirement, or type of use case (service) of each response signal based on a CQI table set for downlink data transmission corresponding to each response signal.

[0331] For example, in Release 15 NR, the target BLER is 10 -1 CQI table to achieve this, and target BLER=10 -5 It is possible to set which CQI table to use to achieve this.

[0332] For example, the terminal 200 may set the CQI table set in the URLLC to a target BLER of 10. -1 On the other hand, if the CQI table set in URLLC is for achieving the target BLER=10, it is determined that the reliability required for the response signal is high. -5 If the CQI table is for achieving this, it is determined that the reliability required for the response signal is not high.

[0333] For example, control unit 101 of base station 100 determines information related to a CQI table to be set for downlink data transmission of terminal 200. The determined information is output to upper control signal generation unit 106. Upper control signal generation unit 106 includes the information related to the CQI table in the upper control signal.

[0334] Meanwhile, decoding section 208 of terminal 200 decodes the higher-level control signal and outputs the decoding result to control section 211. Control section 211 determines information on the reliability of downlink data, delay requirement, or type of use case (service), based on information on the CQI table obtained from the higher-level control signal.

[0335] [Example 5: Explicit notification by DCI] In Example 5, terminal 200 determines the reliability, delay requirement, or type of use case (service) of a response signal by explicit notification using several bits in DCI that schedules downlink data transmission corresponding to each response signal.

[0336] The explicit notification may be information regarding the reliability of the response signal itself, a delay request, or the type of use case (service), or may be information regarding the reliability of the PDSCH (e.g., a target BLER), a delay request, or the type of use case (service).

[0337] For example, the control unit 101 of the base station 100 determines information relating to the reliability of a response signal in response to downlink data from the terminal 200, a delay request, or the type of use case (service). The determined information is output to the downlink control signal generation unit 109. The downlink control signal generation unit 109 includes the information relating to the reliability of an ACK / NACK, a delay request, or the type of use case (service) in a bit string of DCI.

[0338] Meanwhile, decoding section 206 of terminal 200 decodes the DCI and outputs the decoded result to control section 211. Control section 211 obtains information on the reliability of the response signal, the delay request, or the type of use case (service) from the DCI.

[0339] The above has described the methods for determining "the reliability of the response signal, the delay request, or the type of use case (or service)." Note that the methods for determining "the reliability of the response signal, the delay request, or the type of use case (or service)" are not limited to the above-mentioned Examples 1 to 5, and may be determination methods based on other information related to the required conditions.

[0340] (3) Furthermore, in the above-described embodiments, a case where a response signal for downlink data transmission is transmitted using a PUCCH or a PUSCH has been described as an example. However, in the present disclosure, the UCI transmitted using a PUCCH or a PUSCH is not limited to a response signal. For example, in the above-described embodiments, the "response signal (ACK / NACK or HARQ-ACK)" may be replaced with channel state information (CSI), or may be replaced with UCI including the response signal and CSI.

[0341] (4) The present disclosure can be realized by software, hardware, or software integrated with hardware. Each functional block described in the above embodiments can be partially or entirely realized as an LSI, which is an integrated circuit. Each process described in the above embodiments can be partially or entirely controlled by a single LSI or a combination of LSIs. An LSI can be composed of individual chips, or a single chip that includes some or all of the functional blocks. An LSI can have data inputs and outputs. Depending on the level of integration, an LSI can also be referred to as an IC, system LSI, super LSI, or ultra LSI. The integration method is not limited to LSIs; it can also be realized by dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, a field programmable gate array (FPGA), which can be programmed after LSI fabrication, or a reconfigurable processor, which allows the connections and settings of circuit cells within an LSI to be reconfigured, can also be used. The present disclosure can be realized as digital or analog processing. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology can be used to integrate functional blocks. The application of biotechnology is also a possibility.

[0342] The present disclosure may be implemented in any type of apparatus, device, or system with communications capabilities (collectively referred to as communications apparatus), including, but not limited to, telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communications-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above.

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

[0344] Communications include data communications via cellular systems, wireless LAN systems, communications satellite systems, etc., as well as data communications via combinations of these.

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

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

[0347] In one embodiment of the present disclosure, a terminal includes: a circuit that, when transmission of an uplink data channel including uplink data and transmission of an uplink control channel including uplink control information overlap in time, determines a processing mode for the uplink data and the uplink control information in accordance with requirements for at least one of the uplink data and the uplink control information; and a transmitter that transmits at least one of the uplink data and the uplink control information based on the determined processing mode.

[0348] In a terminal according to one embodiment of the present disclosure, the requirements include a target error rate, and the circuit determines the processing manner of the uplink data and the uplink control information according to the target error rate of the uplink control information.

[0349] In a terminal according to an embodiment of the present disclosure, when the target error rate of the uplink control information is equal to or less than a predetermined value, the transmitter drops the uplink data and transmits the uplink control information using the uplink control channel.

[0350] In a terminal according to an embodiment of the present disclosure, when the target error rate of the uplink control information is equal to or less than a predetermined value, the transmitter punctures the uplink data in a transmission interval of the uplink data channel that overlaps with the transmission interval of the uplink control channel, transmits the uplink data in an interval other than the interval that overlaps with the transmission interval of the uplink control channel, and transmits the uplink control information using the uplink control channel.

[0351] In a terminal according to an embodiment of the present disclosure, when the target error rate of the uplink control information is equal to or less than a predetermined value, the transmitter multiplexes the uplink control information onto the uplink data channel and transmits the uplink control information.

[0352] In a terminal according to one embodiment of the present disclosure, the uplink control information is a response signal to downlink data, and at least one of a parameter for controlling the amount of resources required for the response signal in the uplink data channel and a parameter for controlling an upper limit value of the amount of resources is set according to the requirement of the response signal.

[0353] In a terminal according to one embodiment of the present disclosure, the uplink control information is a response signal to downlink data, and when the amount of resources required for the response signal in the uplink data channel exceeds an upper limit value of the amount of resources, the transmitter drops the uplink data in the uplink data channel and transmits the response signal.

[0354] In a terminal according to one embodiment of the present disclosure, the uplink control information is a response signal to downlink data, and when the amount of resources required for the response signal in the uplink data channel exceeds an upper limit value of the amount of resources, the circuit increases the transmission power of the uplink data channel.

[0355] In a terminal according to one embodiment of the present disclosure, when the transmission power of the uplink data channel exceeds the maximum transmission power of the terminal, the transmitter drops the uplink data in the uplink data channel and transmits the response signal at the maximum transmission power.

[0356] In a terminal in one embodiment of the present disclosure, when a specific parameter is notified from a base station to the terminal, the transmitter drops the uplink data in the uplink data channel and transmits the uplink control information.

[0357] In a terminal according to an embodiment of the present disclosure, the circuit determines the processing manner of the uplink control information in the uplink data channel according to the requirement of the uplink control information.

[0358] In a terminal in one embodiment of the present disclosure, transmission of the uplink data channel includes transmission using resources dynamically instructed from a base station to the terminal and transmission using resources quasi-statically assigned to the terminal.

[0359] In a terminal according to one embodiment of the present disclosure, the requirements include a target error rate, and the circuit determines the processing manner of the uplink data and the uplink control information according to the target error rate of the uplink data.

[0360] In a terminal according to one embodiment of the present disclosure, when the target error rate of the uplink data is equal to or less than a predetermined value, the transmitter drops the uplink control information in the uplink control channel and transmits the uplink data using the uplink data channel.

[0361] In a terminal according to an embodiment of the present disclosure, when the target error rate of the uplink data is equal to or less than a predetermined value, the transmitter punctures the uplink control information in a section of the transmission section of the uplink control channel that overlaps with the transmission section of the uplink data channel, and transmits the uplink control information in a section other than the section that overlaps with the transmission section of the uplink data channel.

[0362] In a terminal according to an embodiment of the present disclosure, when the target error rate of the uplink data is equal to or less than a predetermined value, the transmitter multiplexes the uplink control information onto the uplink data channel and transmits the uplink control information.

[0363] In a terminal in one embodiment of the present disclosure, the uplink control information is a response signal to downlink data, and at least one of a parameter for controlling the amount of resources required for the response signal in the uplink data channel and a parameter for controlling an upper limit value of the amount of resources is set according to the requirement of the uplink data.

[0364] In a terminal according to one embodiment of the present disclosure, when a specific parameter is notified from a base station to the terminal, the transmitter drops the uplink control information in the uplink control channel and transmits the uplink data signal using the uplink data channel.

[0365] In a terminal in one embodiment of the present disclosure, transmission of the uplink data channel includes transmission using resources dynamically instructed from a base station to the terminal and transmission using resources quasi-statically assigned to the terminal.

[0366] In a terminal according to one embodiment of the present disclosure, the required conditions include a target error rate, and the circuit determines the processing manner of the uplink data and the uplink control information according to the target error rate of the uplink data and the target error rate of the uplink control information.

[0367] In a terminal according to one embodiment of the present disclosure, the required conditions include a target error rate, and the circuit determines the processing manner of the uplink data signal and the uplink control information according to the target error rate of the uplink data and the target error rate of the uplink control information that is repeatedly transmitted.

[0368] In a terminal in one embodiment of the present disclosure, transmission of the uplink data channel includes transmission using resources dynamically instructed from a base station to the terminal and transmission using resources quasi-statically assigned to the terminal.

[0369] A communication method in one embodiment of the present disclosure, when transmission of an uplink data channel including uplink data and transmission of an uplink control channel including uplink control information overlap in time, determines a processing mode for the uplink data and the uplink control information in accordance with requirements for at least one of the uplink data and the uplink control information, and transmits at least one of the uplink data and the uplink control information based on the determined processing mode.

[0370] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2018-144984, filed on August 1, 2018, are incorporated herein by reference in their entirety. [Industrial Applicability]

[0371] An embodiment of the present disclosure is useful in a mobile communication system. [Explanation of symbols]

[0372] 100 base stations 101,211 Control unit 102 Data Generation Unit 103,107,110,212,214 Encoding section 104 Retransmission control section 105, 108, 111, 213, 215 Modulation section 106 Upper control signal generation unit 109 Downstream control signal generator 112,216 Signal Allocation Section 113,217 IFFT section 114,218 Transmitter 115,201 antennas 116,202 Receiver 117,203 FFT section 118,204 Extraction part 119,122 Demodulation section 120,123,206,208,210 Decoding section 121,124 Judgment part 200 devices 205 Downstream control signal demodulation unit 207 Upper control signal demodulation unit 209 Data demodulation section< / option>

Claims

1. A communication device, a circuit for determining whether to multiplex Hybrid Automatic Repeat Request-Acknowledge (HARQ-ACK) information onto a Physical Uplink Shared Channel (PUSCH) based on a comparison between the first reliability and the second reliability when transmission of HARQ-ACK information having a first reliability for an uplink signal overlaps in time with transmission of a Physical Uplink Shared Channel (PUSCH) having a second reliability comparable to the first reliability; A transmitter that transmits at least one of the HARQ-ACK information and the PUSCH, The circuit determines to multiplex the HARQ-ACK information onto the PUSCH when the first reliability is higher than the second reliability; The circuit selects a beta offset value used to calculate an amount of resources allocated to the HARQ-ACK information multiplexed onto the PUSCH from a plurality of different beta offset values, and the beta offset value varies depending on the value of the first reliability. Communication equipment.

2. a first beta offset value is set for first HARQ-ACK information having a first reliability value, and a second beta offset value is set for second HARQ-ACK information having a second reliability value lower than the first value, and the first beta offset value and the second beta offset value are different from each other; When the first beta offset value is used, the circuit calculates Q′, which indicates the amount of resource, according to equation (1). ACK1 When the second beta offset value is used, Q' indicating the amount of resources is calculated according to equation (2). ACK2 Calculate The communication device according to claim 1 . [Equation 1] [Equation 2] where: O ACK1 indicates the number of bits of the first HARQ-ACK information, and O ACK2 indicates the number of bits of the second HARQ-ACK information, L ACK1 indicates the number of CRC (Cyclic Redundancy Check) bits for the first HARQ-ACK information, and L ACK2 indicates the number of CRC bits for the second HARQ-ACK information, β offset HARQ-ACK indicates the first beta offset value or the second beta offset value, C UL-SCH indicates the number of code blocks of uplink data transmitted in the PUSCH, K r denotes the code block size of the rth code block, M sc UCI (l) denotes the number of resource elements (REs) available for uplink control information (UCI) transmission in the lth orthogonal frequency division multiplexing (OFDM) symbol; N symbol,all PUSCH indicates the number of OFDM symbols of the PUSCH, α indicates a parameter that controls the upper limit of the amount of resources allocated to the first HARQ-ACK information or the second HARQ-ACK information in the PUSCH.

3. the first beta offset value and the second beta offset value are set by a higher layer signal; The communication device according to claim 2 .

4. The circuit determines to multiplex the HARQ-ACK information onto the PUSCH when the first reliability is lower than the second reliability. The communication device according to claim 1 .

5. When the first reliability is higher than the second reliability, the circuit does not determine to multiplex the HARQ-ACK information onto the PUSCH, and determines to transmit the HARQ-ACK information and cancel transmission of the PUSCH. The communication device according to claim 1 .

6. When the first reliability is lower than the second reliability, the circuit does not determine to multiplex the HARQ-ACK information onto the PUSCH, and determines to cancel transmission of the HARQ-ACK information and to transmit the PUSCH. The communication device according to claim 1 .

7. the first reliability and the second reliability are set by downlink control information (DCI). The communication device according to claim 1 .

8. A communication method, comprising: determining whether to multiplex Hybrid Automatic Repeat Request-Acknowledge (HARQ-ACK) information onto a Physical Uplink Shared Channel (PUSCH) based on a comparison between the first reliability and the second reliability when transmission of HARQ-ACK information having a first reliability for an uplink signal overlaps in time with transmission of a Physical Uplink Shared Channel (PUSCH) having a second reliability comparable to the first reliability; transmitting at least one of the HARQ-ACK information and the PUSCH; If the first reliability is higher than the second reliability, determining to multiplex the HARQ-ACK information onto the PUSCH; a beta offset value used to calculate an amount of resources allocated to the HARQ-ACK information multiplexed onto the PUSCH is selected from a plurality of different beta offset values, and the beta offset value varies depending on the value of the first reliability; Communication method.

9. 1. An integrated circuit comprising: a determination process for determining whether to multiplex Hybrid Automatic Repeat Request-Acknowledge (HARQ-ACK) information onto a Physical Uplink Shared Channel (PUSCH) based on a comparison between the first reliability and the second reliability when transmission of HARQ-ACK information for an uplink signal having a first reliability and transmission of a Physical Uplink Shared Channel (PUSCH) having a second reliability comparable to the first reliability overlap in time; a transmission process for transmitting at least one of the HARQ-ACK information and the PUSCH; The determination process includes: If the first reliability is higher than the second reliability, determining to multiplex the HARQ-ACK information onto the PUSCH; a beta offset value used to calculate an amount of resources allocated to the HARQ-ACK information multiplexed onto the PUSCH is selected from a plurality of different beta offset values, and the beta offset value varies depending on the value of the first reliability; Integrated circuit.

Images