Base station, communication method and integrated circuit

The terminal and communication method optimize uplink control information transmission in 5G NR by adapting encoding and resource allocation to meet varying reliability and delay requirements, enhancing efficiency and reducing delays in response signal transmission.

JP2024164191AActive Publication Date: 2024-11-26PANASONIC INTELLECTUAL PROPERTY CORP OF AMERICA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024144234
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2018-08-01
Filing Date
2024-08-26
Publication Date
2024-11-26
Estimated Expiration
2039-03-25

AI Technical Summary

Technical Problem

The existing 5G NR systems do not adequately address the efficient transmission of uplink control information, particularly for ultra-reliable and low-latency communications (URLLC), especially when handling varying reliability and delay requirements for different use cases, leading to inefficient resource utilization and potential bottlenecks in response signal transmission.

Method used

A terminal and communication method that determines a processing mode for uplink control information based on request conditions, applying different encoding methods and resource allocation strategies to ensure appropriate transmission of response signals with varying reliability and delay requirements, allowing for efficient multiplexing and resource utilization.

Benefits of technology

This approach enables efficient transmission of uplink control information by optimizing resource allocation and encoding methods, ensuring high reliability and low latency for response signals, thereby improving resource utilization efficiency and reducing transmission delays.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024164191000001_ABST
    Figure 2024164191000001_ABST
Patent Text Reader

Abstract

To properly transmit uplink control information.SOLUTION: A base station includes a transmitter that transmits information indicating a first uplink control channel (PUCCH) resource set for first uplink control information having a first priority and a second PUCCH resource set for second uplink control information having a second priority, and a receiver that receives at least one of the first uplink control information and the second uplink control information, and the first uplink control information and the second uplink control information are multiplexed into one slot.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] 3GPP (3rd Generation Partnership Project) has completed the Release 15 NR (New Radio access technology) specification formulation for the realization of 5th generation mobile communication systems (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 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 setting or reporting the Modulation and Coding Scheme (MCS) or Channel Quality Indicator (CQI) to achieve a low target Block Error Rate (BLER). For example, the target error rate (or target BLER) is set to 100 Mbps in normal mode (e.g., BLER = 100 Mbps). -1 ) and high reliability mode (e.g., BLER=10 -5 ) can be set.

Prior technical literature

Non-licensed literature

[0005] [Non-licensed document 1] 3GPP TS 38.211 V15.2.0, "NR; Physical channels and modulation (Release 15)," March 2018.

Non-licensed Document 2

Non-licensed Document 4

Non-licensed Document 5

Non-licensed Document 6

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

[0007] Non-limiting examples of the present disclosure contribute to providing a terminal and a communication method capable of appropriately transmitting uplink control information. [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure includes a circuit that determines a processing mode for uplink control information or an uplink control channel used for transmitting the uplink control information in accordance with a requirement for the uplink control information, and a transmitter that transmits the uplink control information using the uplink control channel based on the determined processing mode.

[0009] A communication method according to one embodiment of the present disclosure determines a processing mode for uplink control information or an uplink control channel used for transmitting the uplink control information in accordance with a requirement for the uplink control information, and transmits the uplink control information using the uplink control channel 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. Effect of the Invention

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

[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 description of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing a partial configuration of a terminal according to a first embodiment; [Diagram 2] FIG. 1 is a block diagram showing a configuration of a base station according to a first embodiment. [Diagram 3] FIG. 1 is a block diagram showing a configuration of a terminal according to a first embodiment. [Figure 4] A sequence diagram showing processing of a base station and a terminal according to the first embodiment. [Diagram 5] FIG. 1 is a diagram showing an example of an ACK / NACK transmission process according to the first embodiment; [Figure 6] FIG. 1 shows an example of ACK / NACK mapping according to Option 1 of the first embodiment. [Figure 7] FIG. 1 shows an example of ACK / NACK mapping according to Option 2 of the first embodiment. [Figure 8] FIG. 1 shows an example of ACK / NACK mapping according to Option 3 of the first embodiment. [Figure 9] FIG. 1 shows an example of ACK / NACK mapping according to Option 4 of the first embodiment. [Figure 10A] FIG. 13 is a diagram showing an example of an ACK / NACK transmission process according to Option 1 of the second embodiment; [Figure 10B] FIG. 13 is a diagram showing an example of an ACK / NACK transmission process according to Option 1 of the second embodiment; [Figure 11A] FIG. 13 is a diagram showing an example of an ACK / NACK transmission process according to Option 2 of the second embodiment; [Figure 11B]FIG. 13 is a diagram showing an example of an ACK / NACK transmission process according to Option 2 of the second embodiment; [Figure 12] FIG. 13 is a diagram showing an example of an ACK / NACK transmission process according to the third embodiment; [Figure 13] FIG. 13 is a diagram showing an example of an ACK / NACK transmission process according to the fourth embodiment; [Figure 14] FIG. 13 is a diagram showing another example of the transmission process of ACK / NACK according to the fourth embodiment; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[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 the cell throughput or frequency utilization efficiency. In such a case, 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 account the combined gain from several retransmissions by HARQ, the final setting is 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 retransmissions by HARQ, the above-mentioned high-reliability mode (target data error rate is set to a relatively low value (e.g., BLER=10 -5) to ensure reliable data transmission in the first transmission.

[0017] Setting a low target error rate leads to highly reliable data transmission, but 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 or future URLLC is 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 one transmission, which is inefficient in terms 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 assumed. In the 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 and 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).

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

[0022] For example, in URLLC, assume that even if an error occurs in the first transmission, data can be transmitted reliably in the next transmission (retransmission). In this case, the higher the target error rate of the first data transmission, the more reliable the transmission of a response signal is required (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 required, 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, between 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] However, in Release 15 NR, in the feedback mechanism of a response signal from a terminal, the operation regarding response signals with different reliability, delay requirements, or types of use cases (or services) has not been fully considered.

[0025] In addition, the terminal transmits a response signal to the base station using an uplink control channel (PUCCH: Physical Uplink Control Channel). However, in Release 15 NR, the requirement on the reliability required for transmission of the response signal in URLLC that allows retransmission (for example, BLER = 10 -4 The PUCCH has not been designed to achieve a BER of 0.1 or less.

[0026] In addition, it is assumed that an NR terminal supports multiple use cases or services (e.g., eMBB and URLLC, etc.). In addition, it is assumed that an NR terminal supports multiple data transmissions with different target error rates in URLLC. In this case, there is a possibility that a terminal may simultaneously transmit response signals corresponding to data transmissions with different reliability, delay requirements, or types of use cases (or services) in the same uplink slot.

[0027] In Release 15 NR, the number of PUCCHs that can transmit response signals in one slot is limited to 1. Therefore, if response signals corresponding to data transmissions with different reliability, delay requirements, or types of use cases (or services) are simultaneously transmitted in the same slot as described above, these response signals are multiplexed and transmitted in one PUCCH.

[0028] For example, in the method in Release 15 NR, when response signals with different required reliability are multiplexed, it is considered to set radio resources for PUCCH according to the reliability of the response signal that requires high reliability in order to satisfy the requirement of the response signal that requires high reliability. However, in this case, radio resources for PUCCH are set for response signals that require lower reliability compared to the response signal that requires high reliability (in other words, response signals that do not require high reliability) in the same way as for response signals that require high reliability, which is inefficient in terms of resource utilization efficiency.

[0029] Furthermore, when response signals with different required reliability are multiplexed, in a HARQ-ACK codebook (response signal bit string) for multiplexing the response signals, the response signals are arranged in order starting from the response signal corresponding to the downlink data received earlier, regardless of the reliability, delay request, or type of use case (or service). For example, when response signals with different delay requests (e.g., response signals corresponding to eMBB and URLLC) are multiplexed and transmitted in one PUCCH, the transmission of a response signal that does not require low delay (e.g., a response signal of eMBB) may become a delay bottleneck.

[0030] Therefore, in one embodiment of the present disclosure, a method for transmitting a response signal with different reliability, delay request, or type of use case (or service) will be described. In other words, a method for transmitting a response signal according to a "request condition" such as reliability, delay request, or type of use case (or service) will be described.

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

[0032] (Embodiment 1) [Communication system overview] The communication system according to each embodiment of the present disclosure includes a base station 100 and a terminal 200.

[0033] Fig. 1 is a block diagram showing a configuration of a part of terminal 200 according to each embodiment of the present disclosure. In terminal 200 shown in Fig. 1, control unit 211 determines a processing mode (e.g., a transmission method or a parameter setting) for uplink control information or an uplink control channel (e.g., PUCCH) used for transmitting the uplink control information according to a requirement (e.g., reliability, delay requirement, or type of use case (service)) for uplink control information (UCI, e.g., a response signal to downlink data). Transmitting unit 216 transmits the uplink control information using the uplink control channel based on the determined processing mode.

[0034] [Base station configuration] Fig. 2 is a block diagram showing a configuration of a base station 100 according to the first embodiment of the present disclosure. In Fig. 2, the base station 100 includes a control unit 101, a data generating unit 102, an encoding unit 103, a retransmission control unit 104, a modulation unit 105, a higher-level control signal generating unit 106, an encoding unit 107, a modulation unit 108, a downlink control signal generating 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, and a determination unit 121.

[0035] 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) of downlink data transmitted in the PDSCH, or radio resources of the PDSCH (hereinafter referred to as "PDSCH resources"). In addition, the control unit 101 outputs the determined information to the downlink control signal generation unit 109.

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

[0037] Furthermore, control unit 101 determines information related to transmission of uplink control information (UCI) of terminal 200, and outputs the determined information to extraction unit 118 and decoding unit 120. Control unit 101 also outputs information related to transmission of UCI to higher control signal generation unit 106 or downlink control signal generation unit 109. The information related to transmission of UCI includes, for example, UCI (for example, a response signal or CSI, etc.) or a transmission method or parameters of a PUCCH used to transmit UCI, etc.

[0038] Furthermore, the information output to the higher control signal generating unit 106 includes, for example, information related to a PUCCH resource set, information related to a set of semi-statically set slot positions (for example, PDSCH-to-HARQ-ACK timing), information related to the maximum coding rate of UCI, etc. Furthermore, the information output to the downlink control information generating unit 109 includes, for example, information for indicating a PUCCH radio resource (hereinafter, PUCCH resource) to be actually used within the PUCCH resource set, information for indicating a PDSCH-to-HARQ-ACK timing to be actually used within a set of semi-statically set slot positions, etc.

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

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

[0041] 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 encoding rate), and outputs the encoded data signal to the retransmission control unit 104.

[0042] 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 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.

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

[0044] High-order control signal generating section 106 generates a control information bit string (high-order control signal) using the control information inputted from control section 101 , and outputs the generated control information bit string to encoding section 107 .

[0045] 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 modulating section 108 .

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

[0047] 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. Since the control information may be transmitted to a plurality of 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. A scrambling sequence, which will be described later, may be used for the terminal ID.

[0048] The encoding 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 .

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

[0050] 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.

[0051] 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 in which a CP (Cyclic Prefix) is added, the IFFT unit 113 adds a CP (not shown). The IFFT unit 113 outputs the generated transmission waveform to the transmission unit 114.

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

[0053] 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 reception processing to the FFT unit 117.

[0054] 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.

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

[0056] The demodulation unit 119 performs equalization and demodulation on the radio resource components corresponding to the PUCCH received from the extraction unit 118 , and outputs the demodulation result (demodulated sequence) to the decoding unit 120 .

[0057] Based on information regarding the transmission of UCI input from control unit 101 (e.g., information regarding the encoding of UCI), decoding unit 120 performs error correction decoding on the demodulation result input from demodulation unit 119, and outputs the decoded bit sequence to determination unit 121.

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

[0059] [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, extracting section 204, downlink control signal demodulating section 205, decoding section 206, higher control signal demodulating section 207, decoding section 208, data demodulating section 209, decoding section 210, control section 211, encoding section 212, modulating section 213, signal allocating section 214, IFFT section 215, and transmitting section 216.

[0060] The receiving unit 202 performs RF processing such as down-conversion or A / D (Analog-to-Digital) conversion on the signal waveform of a 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.

[0061] 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.

[0062] Extraction unit 204 extracts a downlink control signal (e.g., DCI), a higher control signal, or downlink data from the signal input from FFT unit 203, based on control information (e.g., information related to the radio resource of the downlink data or the control signal) input from control unit 211. Extraction unit 204 outputs the downlink control signal to downlink control signal demodulation unit 205, outputs the higher control signal to higher control signal demodulation unit 207, and outputs the downlink data to data demodulation unit 209.

[0063] 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 .

[0064] The decoding unit 206 performs error correction decoding using the demodulation result inputted from the downlink control signal demodulation unit 205 to obtain control information. The decoding unit 206 outputs the obtained control information to the control unit 211.

[0065] 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 .

[0066] 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.

[0067] 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 .

[0068] 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 determined to be error-free as a result of the error detection as received data.

[0069] Control unit 211 determines UCI (for example, ACK / NACK or CSI) or a transmission method or parameters (for example, MCS or radio resources, etc.) of the PUCCH used for transmitting UCI, based on information related to transmission of UCI of terminal 200, which is included in the control information input from decoding unit 206 or decoding unit 208. Control unit 211 outputs the determined information to encoding unit 212, modulation unit 213, and signal allocation unit 214.

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

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

[0072] The encoding unit 212 performs error correction encoding on the response signal (ACK / NACK bit sequence) based on information input from the control unit 211, and outputs the encoded response signal (bit sequence) to the modulation unit 213. For example, as will be described later, the encoding unit 212 may generate encoded bit sequences by applying different encoding methods to response signals having different requirements such as reliability, delay requirement, or type of use case (or service).

[0073] The modulation unit 213 modulates the response signal input from the encoding unit 212 based on the information input from the control unit 211, and outputs the modulated response signal (modulation symbol sequence) to the signal allocation unit 214. For example, when encoded bit sequences to which different encoding methods are applied are input from the encoding unit 212, the modulation unit 213 modulates each encoded bit sequence.

[0074] Signal allocation section 214 maps the response signal (modulation symbol sequence) inputted from modulation section 213 to the radio resource of the PUCCH instructed by control section 211. Signal allocation section 214 outputs, to IFFT section 215, the signal onto which the response signal is mapped.

[0075] The IFFT unit 215 performs transmission waveform generation processing such as OFDM on the signal input from the signal allocation unit 214. In the case of OFDM transmission in which a CP (Cyclic Prefix) is added, the IFFT unit 215 adds a CP (not shown). Alternatively, in the case where the IFFT unit 215 generates a single carrier waveform, a DFT (Discrete Fourier Transform) unit may be added (not shown) before the signal allocation unit 214. The IFFT unit 215 outputs the generated transmission waveform to the transmission unit 216.

[0076] The transmitter 216 performs RF (Radio Frequency) processing such as D / A (Digital-to-Analog) conversion and up-conversion on the signal input from the IFFT unit 215 , and transmits the radio signal to the base station 100 via the antenna 201 .

[0077] [Operation 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.

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

[0079] Base station 100 transmits information about the PUCCH to terminal 200 (ST101). Terminal 200 acquires information about the PUCCH notified from base station 100 (ST102). The information about the PUCCH includes, for example, information about a PUCCH resource set or information about a coding rate for the PUCCH.

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

[0081] 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).

[0082] Terminal 200 controls the response signal or an operation related to transmission of the response signal according to the requirement condition for the response signal (in other words, the reliability, delay requirement, or type of use case (service)) (ST107). For example, terminal 200 determines a processing mode for the response signal or PUCCH according to the requirement condition for the response signal. In determining the processing mode for the response signal or PUCCH, for example, a method for encoding the response signal, a method for determining a PUCCH resource, or parameters related to PUCCH transmission may be determined.

[0083] Terminal 200 transmits UCI (including a response signal, for example) to base station 100 using the PUCCH based on the determined operation (ST108). Base station 100 receives the UCI transmitted from terminal 200 (ST109).

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

[0085] [Encoding method] Terminal 200 applies different encoding methods to response signals having different reliability, delay requirements, or types of use cases (or services) (in other words, response signals with different requirements) to generate HARQ-ACK bits.

[0086] Terminal 200 then multiplexes the response signals coded using different coding methods onto the PUCCH and transmits the multiplexed response signals.

[0087] For example, terminal 200 applies encoding processes with different encoding rates to response signals with different reliability, delay requirements, or types of use cases (or services).

[0088] For example, for a response signal that requires high reliability, terminal 200 generates a HARQ-ACK bit by encoding the response signal using a low encoding rate (for example, an encoding rate equal to or lower than a threshold). By applying a low encoding rate, the reliability of the response signal can be improved.

[0089] On the other hand, for a response signal that does not require high reliability, terminal 200 generates HARQ-ACK bits by encoding the response signal using a high encoding rate (for example, an encoding rate higher than a threshold value). By applying a high encoding rate, it is possible to suppress an increase in the number of bits of the response signal and improve resource utilization efficiency.

[0090] As an example of generating a difference in the encoding process for the response signal, a case where the reliability of the response signal is different will be described. For example, in URLLC, when the target error rate of 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 difference may be made in the coding process between the response signal to the downlink data and the response signal to the downlink data.

[0091] Specifically, when the target error rate for the first data transmission is high, a high reliability is required for the response signal in order to retransmit the data reliably, so an encoding method with a low coding rate is applied to the response signal. On the other hand, when the target error rate for the first data transmission is low, data errors are unlikely to occur, so a high reliability is not required for the response signal, so an encoding method with a high coding rate is applied to the response signal.

[0092] Another example of a difference in the encoding process for a response signal is when the delay requirement of the response signal is different, or when the type of use case (or service) of the response signal (e.g., URLLC or eMBB) is different.

[0093] As an example, Fig. 5 shows an example in which different encoding methods (encoding processes) are applied to response signals for URLLC and eMBB. In Fig. 5, terminal 200 applies encoding process 1 to a response signal for eMBB downlink data (eMBB PDSCH) and applies encoding process 2 to a response signal for URLLC downlink data (URLLC PDSCH).

[0094] For example, URLLC requires high reliability, so a coding method with a low coding rate is applied in coding process 2 for the response signal. On the other hand, eMBB does not require high reliability compared to URLLC, so a coding method with a high coding rate is applied in coding process 1 for the response signal.

[0095] In FIG. 5, terminal 200 applies different encoding methods to a URLLC response signal and an eMBB response signal to generate HARQ-ACK bits, respectively, and multiplexes the generated HARQ-ACK bits into one PUCCH to transmit to base station 100.

[0096] As described above, according to this embodiment, the terminal 200 can apply an appropriate encoding method (e.g., coding rate) for each response signal according to the reliability of the response signal, the delay requirement, or the type of use case (or service). Thereby, even when the required conditions of the response signals multiplexed on one PUCCH are different, each response signal is encoded using an encoding method corresponding to the required condition of each response signal, so that efficient PUCCH transmission is possible from the viewpoint of resource utilization efficiency.

[0097] Note that the different encoding processes for each ACK / NACK are not limited to being determined based on the reliability or the type of use case (service) described above. For example, it may be determined based on at least one of the reliability, the delay requirement, or the type of use case (service).

[0098] [Mapping Method] Next, a method for mapping response signals with different reliability, delay requirements, or types of use cases (or services) (in other words, response signals with different required conditions) to PUCCH resources will be described.

[0099] For example, the terminal 200 maps to the PUCCH in the order of response signals that require higher reliability or in the order of response signals that require lower latency in the delay requirement. Specifically, the terminal 200 first maps the response signals that require higher reliability or lower latency to the PUCCH resources. Next, the terminal 200 maps the response signals that do not require high reliability or low latency to the PUCCH resources.

[0100] Hereinafter, as an example, the mapping methods of response signals in Short-PUCCH (e.g., PUCCH Format 2) composed of 1 or 2 symbols and Long-PUCCH (e.g., PUCCH Format 3 or PUCCH Format 4) composed of 4 or more symbols will be described respectively.

[0101] <In the case of Short PUCCH> The following two methods (Option 1 and Option 2) can be applied to map a response signal in Short PUCCH to a PUCCH resource.

[0102] [Option 1] FIG. 6 shows an example of mapping of a response signal in Option 1 to a Resource Element (RE).

[0103] As shown in Fig. 6, in Option 1, terminal 200 maps a modulation symbol sequence obtained by modulating a response signal (HARQ-ACK) to REs excluding resource elements (REs) to which reference signals (RSs, e.g., Demodulation RSs (DMRSs)) are mapped, based on a "Frequency-first-time-second format". In other words, terminal 200 maps a response signal in the PUCCH in the order from the frequency direction to the time direction.

[0104] Specifically, in mapping to REs, as described above, a response signal that requires high reliability or low delay (in FIG. 6, HARQ-ACK for URLLC) is mapped to a PUCCH resource first, followed by a response signal that does not require high reliability or low delay (in FIG. 6, HARQ-ACK for eMBB) being mapped to a PUCCH resource.

[0105] In accordance with the mapping method of Option 1, in FIG. 6, the HARQ-ACK for URLLC is mapped to all REs of the first symbol constituting the PUCCH (excluding the REs to which DMRS is mapped) and some REs of the second symbol, and the HARQ-ACK for eMBB is mapped to the remaining REs of the second symbol.

[0106] According to the mapping method of Option 1, for example, a response signal that requires a lower delay is mapped to the first symbol of the PUCCH, so that a delay reduction effect can be obtained in the case of a two-symbol Short PUCCH.

[0107] [Option 2] FIG. 7 shows an example of mapping of response signals to REs in Option 2.

[0108] As shown in Fig. 7, in Option 2, terminal 200 maps the modulation symbol sequence after modulating the response signal (HARQ-ACK) to REs excluding the RE to which the reference signal is mapped, based on the "Frequency-first-time-second format" as in Option 1. Furthermore, in Option 2, terminal 200 maps the response signals within the allocated band so as to be distributed in the frequency direction.

[0109] Specifically, in mapping to REs, as described above, a response signal requiring high reliability or low delay (HARQ-ACK for URLLC in FIG. 7) is mapped to PUCCH resources first, and then a response signal requiring less high reliability or low delay (HARQ-ACK for eMBB in FIG. 7) is mapped to PUCCH resources. Also, in FIG. 7, ACK / NACK for URLLC and ACK / NACK corresponding to eMBB are mapped in a distributed manner in the frequency direction.

[0110] According to the mapping method of Option 2, in FIG. 7, for URLLC, the HARQ-ACK is mapped to all the REs in the first symbol constituting the PUCCH (excluding the REs to which DMRS is mapped) and some REs in the second symbol, and for eMBB, the HARQ-ACK is mapped to the remaining REs in the second symbol. Also, in FIG. 7, in the second symbol of the PUCCH, the HARQ-ACK for URLLC and the HARQ-ACK for eMBB are mapped separately in a frequency-wise dispersed manner within the allocated band of the PUCCH (e.g., 4 RBs (Resource Block)).

[0111] According to the mapping method of Option 2, similar to the mapping method of Option 1, since the response signal requiring lower latency is mapped to the leading symbol of the PUCCH, in the case of a 2-symbol Short PUCCH, the effect of reducing latency can be obtained.

[0112] Also, according to the mapping method of Option 2, since the frequency diversity effect can be obtained by the frequency-wise dispersed mapping, the transmission of a higher-quality response signal (in other words, a more reliable response signal) can be realized.

[0113] <In the case of Long PUCCH> As for the mapping of the response signal to the PUCCH resource in Long-PUCCH, the following two methods (Option 3 and Option 4) can be applied.

[0114] [Option 3] In Option 3, a method similar to the mapping relationship between the HARQ-ACK bits and CSI (CSI Part 1 and CSI Part 2) in NR's PUCCH Format 3 or PUCCH Format 4 (see, for example, Non-Patent Document 2) is applied to the mapping for response signals with different reliability, latency requirements, or types of use cases (or services).

[0115] FIG. 8 shows an example of mapping of response signals to REs in Option 3.

[0116] As shown in Fig. 8, in Option 3, terminal 200 maps a modulation symbol sequence obtained by modulating a response signal (HARQ-ACK) to REs excluding REs to which RSs (DMRSs in Fig. 8) are mapped, based on the "Frequency-first-time-second format". Also, as shown in Fig. 8, terminal 200 maps a response signal requiring higher reliability to a symbol closer to a symbol to which a reference signal (e.g., DMRS) is mapped in PUCCH.

[0117] Specifically, as shown in Fig. 8, in the mapping to RE, first, HARQ-ACK for URLLC, which requires high reliability, is mapped to symbols (symbols before and after) close to the symbol to which DMRS is mapped, as described above. Then, as shown in Fig. 8, HARQ-ACK bits for eMBB, which does not require high reliability, are mapped to the remaining PUCCH resources.

[0118] According to the mapping method of Option 3, the HARQ-ACK bit, which requires higher reliability, is mapped to a symbol with high channel estimation accuracy (a symbol close to the symbol to which the DMRS is mapped). Therefore, according to Option 3, it is possible to realize the transmission of a response signal with higher quality (in other words, a response signal with higher reliability).

[0119] [Option 4] FIG. 9 shows an example of mapping of response signals to REs in Option 4.

[0120] As shown in Fig. 9, in Option 4, terminal 200 maps the modulation symbol sequence after modulating the response signal (HARQ-ACK) to REs excluding the RE to which the RS is mapped, based on the "Frequency-first-time-second format." Also, as shown in Fig. 9, terminal 200 maps a response signal for which shorter delay is required in the delay request to an earlier symbol of the PUCCH.

[0121] Specifically, as shown in Fig. 9, in the mapping to RE, as described above, the HARQ-ACK for URLLC, which requires low latency, is first mapped in order from the symbol with the earliest timing (for example, the first symbol). Then, as shown in Fig. 9, the HARQ-ACK for eMBB, which does not require low latency, is mapped to the remaining PUCCH resources.

[0122] According to the mapping method of Option 4, a response signal that requires a lower delay is mapped to the first symbol of the PUCCH, which has the effect of reducing delay.

[0123] The method of mapping a response signal to a PUCCH resource has been described above.

[0124] In this way, terminal 200 preferentially maps a response signal that requires high reliability or low delay, that is, a response signal with strict requirements, to a PUCCH resource. As a result, terminal 200 can preferentially map, for example, a response signal that requires higher reliability or lower delay, among response signals multiplexed into a PUCCH, to a PUCCH resource that can achieve high reliability or low delay. Thus, according to this embodiment, terminal 200 can transmit a response signal using a PUCCH resource that is suitable for the requirements for the response signal.

[0125] In addition, in Option 3 and Option 4, the mapping method of a response signal to a Long-PUCCH using four or more symbols has been described. On the other hand, for example, in URLLC, using a Long-PUCCH is not desirable from the viewpoint of delay reduction. Therefore, in this embodiment, multiplexing of response signals with different reliability, delay requirements, or types of use cases (or services) into one PUCCH may be limited to Short-PUCCH. This makes it possible to omit design for multiple PUCCH formats while satisfying the low-delay requirement.

[0126] Furthermore, the method of mapping a response signal to PUCCH resources is not limited to the above-mentioned Options 1 to 4. Also, for example, any of Options 1 to 4 may be combined. For example, in Option 3 (see FIG. 8) or Option 4 (see FIG. 9), the response signal (HARQ-ACK) may be distributed and mapped in the frequency direction, as in Option 2 (see FIG. 7).

[0127] [How to determine PUCCH resources] Next, a method for determining a PUCCH resource in this embodiment will be described.

[0128] In NR, with regard to identifying PUCCH resources for transmitting a response signal to downlink data from a terminal, a method is adopted in which the base station notifies a semi-static set of PUCCH resources (PUCCH resource set) by a terminal-specific higher layer signal (e.g., RRC (Radio Resource Control) signaling) and notifies the PUCCH resources actually to be used from the PUCCH resource set by DCI (Downlink Control Information) that allocates downlink data (e.g., see Non-Patent Document 3).

[0129] Here, the PUCCH resource is composed of at least one parameter, for example, a symbol position within a slot, the number of symbols within a slot, a frequency domain position, the number of resources in the frequency domain (e.g., the number of RBs or the number of PRBs (Physical RBs)), whether or not frequency hopping is applied, or a code resource (e.g., a cyclic shift sequence or an orthogonal code).

[0130] Furthermore, the base station can notify the terminal of multiple PUCCH resource sets. The terminal can determine which PUCCH resource set to use from among the notified multiple PUCCH resource sets based on the number of bits of uplink control information (UCI) transmitted using the PUCCH.

[0131] In this embodiment, terminal 200 determines a PUCCH resource set based on the total number of bits after encoding of response signals (HARQ-ACK) multiplexed onto the PUCCH.

[0132] In addition, in this embodiment, different values ​​may be set for parameters related to the determination of PUCCH resources for response signals having different reliability, delay requirements, or types of use cases (or services) (in other words, response signals with different requirements).

[0133] For example, in NR, a maximum coding rate is set for each PUCCH format. The terminal determines the number of RBs used for transmitting the PUCCH from the number of bits of UCI transmitted using the PUCCH and the maximum coding rate. However, the number of RBs used for transmitting the PUCCH is limited to the number of RBs of the PUCCH resource notified by the above-mentioned PUCCH resource set.

[0134] In this embodiment, the maximum coding rate is set for each PUCCH format, and for each reliability of the response signal, delay request, or type of use case (or service) (in other words, for each request condition of the response signal).

[0135] For example, terminal 200 calculates the amount of resources (e.g., the number of REs) to be used for transmitting a response signal for each response signal having a different reliability, delay request, or type of use case (or service), based on the number of bits after encoding the response signal and the set maximum coding rate. Then, terminal 200 determines the number of RBs to be used for transmitting one PUCCH, based on the number of REs to be used for transmitting each response signal multiplexed into the PUCCH.

[0136] In this way, terminal 200 can determine a PUCCH resource set in a PUCCH in which response signals with different requirements are multiplexed, based on the number of bits after encoding by an encoding method set for each response signal, for example, as described above. For example, terminal 200 can calculate an appropriate resource amount according to the reliability, delay request, or type of use case (or service) of the response signal, thereby enabling efficient PUCCH transmission in terms of resource utilization efficiency.

[0137] As described above, the number of RBs used for transmitting PUCCH is the upper limit of the number of RBs of the PUCCH resource notified by the PUCCH resource set. Therefore, for example, when the number of RBs determined from the number of bits of the response signal and the maximum coding rate exceeds the upper limit notified by the PUCCH resource set, the actual coding rate of the response signal may exceed the set maximum coding rate. In this case, there is a possibility that the quality required for transmitting PUCCH cannot be satisfied.

[0138] Therefore, in this embodiment, terminal 200 may drop a part of the response signal transmitted using PUCCH when the actual coding rate of the response signal exceeds a predetermined threshold. In this way, the PUCCH resource for the part of the response signal that has been dropped is used for the remaining response signal, thereby improving the quality of PUCCH transmission.

[0139] Here, the threshold may be, for example, a maximum coding rate that is set for each PUCCH format and for each reliability of the response signal, delay request, or type of use case (or service). Furthermore, a threshold for dropping some response signals may be newly notified from base station 100 to terminal 200, separate from the maximum coding rate.

[0140] Furthermore, when the number of RBs calculated from the number of bits of a response signal (or UCI) transmitted using the PUCCH and the maximum coding rate exceeds a predetermined threshold (upper limit), terminal 200 may drop at least a part of the response signal transmitted using the PUCCH. This allows the PUCCH resources used for dropping part of the response signal to be used for the remaining response signal, thereby improving the quality of PUCCH transmission.

[0141] Furthermore, the response signal to be dropped may be determined according to the reliability of the response signal, the delay request, or the priority set according to the type of use case (or service) (in other words, the priority set for each request condition). For example, terminal 200 may preferentially transmit a response signal for a request condition with a high priority. In other words, terminal 200 may preferentially drop a response signal for a request condition with a low priority.

[0142] As an example of the priority, when the reliability of the response signal is different, for example, in URLLC, the target error rate of the first data transmission is high (e.g., BLER=10 -1 ) The priority of the response signal to the downlink data is set such that the target error rate of the first data transmission is low (e.g., BLER=10 -5 ) is set higher than the priority of a response signal for downlink data. Alternatively, when the delay requirement of the response signal is different or the type of use case (or service) is different, for example, the priority of URLLC is set higher than the priority of eMBB.

[0143] When the coding rate of at least one of the response signals with different reliability, delay requirement, or type of use case (or service) exceeds a threshold, the terminal 200 may drop the response signals from the low priority. This makes it possible to suppress deterioration of the transmission quality of the response signals with high priority, that is, the response signals that require higher reliability.

[0144] In addition, when there are response signals with different reliability, delay requirements, or types of use cases (or services), base station 100 may notify terminal 200 in advance of information indicating the ratio at which resources (e.g., REs) in the PUCCH are shared or divided for the different response signals (e.g., resource sharing factor or resource splitting factor).

[0145] The method for determining the PUCCH resource has been described above.

[0146] As described above, in this embodiment, terminal 200 determines a processing mode for a response signal or PUCCH according to requirements for a response signal of downlink data (for example, reliability, delay requirement, or type of use case (service)). Specifically, terminal 200 applies different coding methods to response signals with different requirements. Terminal 200 then multiplexes the coded response signal onto the PUCCH and transmits the result.

[0147] As a result, according to the present embodiment, even when response signals with different requirements are multiplexed onto the PUCCH, terminal 200 can perform processing (e.g., encoding processing) or setting of radio resources (e.g., determination of a mapping method or PUCCH resources) according to the requirements of the response signals multiplexed onto the PUCCH. For example, terminal 200 can improve resource usage efficiency in the PUCCH by setting the position or amount of PUCCH resources according to the reliability required for the response signals. Also, for example, terminal 200 can reduce delays of response signals by setting the position of PUCCH resources according to a delay request for the response signals.

[0148] As described above, according to the present embodiment, terminal 200 can appropriately transmit UCI including a response signal.

[0149] (Embodiment 2) A base station and a terminal according to the present embodiment have basic configurations in common with base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0150] In this embodiment, terminal 200 uses different methods of determining PUCCH resources or PUCCH resource sets for response signals with different reliability, delay requirements, or types of use cases (or services) (in other words, response signals with different requirements).

[0151] Furthermore, in this embodiment, the number of PUCCHs in which terminal 200 can transmit response signals in one slot is not limited to 1. In other words, in this embodiment, the number of PUCCHs in which terminal 200 can transmit response signals in one slot is 1 or more.

[0152] For example, terminal 200 transmits each response signal having a different request condition using a different PUCCH in the slot. For example, multiple PUCCHs are multiplexed in the same slot by time division multiplexing (TDM), frequency division multiplexing (FDM), or code division multiplexing (CDM).

[0153] This allows terminal 200 to allocate appropriate PUCCH resources to each response signal according to the reliability of the response signal, the delay requirement, or the type of use case (or service). In other words, terminal 200 can transmit response signals with different requirements using individual PUCCHs, without multiplexing them into one PUCCH. This allows for efficient PUCCH transmission in terms of resource utilization efficiency.

[0154] Furthermore, according to the present embodiment, terminal 200 can transmit response signals with different delay requests, for example, using different PUCCHs. Therefore, for example, a response signal requiring low delay, such as URLLC, can be transmitted using a Short-PUCCH, and a response signal requiring less low delay, such as eMBB, can be transmitted using a Long-PUCCH, thereby eliminating a bottleneck for delay requests.

[0155] For example, with regard to identifying a PUCCH resource for transmitting a response signal to downlink data of terminal 200, base station 100 notifies a semi-static set of PUCCH resources (e.g., PUCCH resource set) by a terminal-specific higher layer signal (e.g., RRC signaling). Terminal 200 determines a PUCCH resource set based on, for example, one of the following two methods (Option 1 and Option 2).

[0156] [Option 1] In Option 1, different groups of PUCCH resource sets are configured for response signals with different reliability, delay requirements, or types of use cases (or services) (in other words, response signals with different requirements). Thus, terminal 200 configures PUCCH resource sets included in different groups for response signals with different requirements.

[0157] FIG. 10A shows an example of a PUCCH resource set configuration in Option 1.

[0158] In Fig. 10A, a group of PUCCH resource sets for eMBB (e.g., group X) and a group of PUCCH resource sets for URLLC (e.g., group Y) are configured. For example, in Fig. 10A, group X includes PUCCH resource sets X0, X1, X2, and X3, and group Y includes PUCCH resource sets Y0, Y1, Y2, and Y3.

[0159] Terminal 200 determines which PUCCH resource set in each group to use, for example, for each response signal having a different reliability, delay requirement, or type of use case (or service), based on the number of UCI bits (e.g., the number of HARQ-ACK bits) to be transmitted using the PUCCH.

[0160] For example, in Fig. 10A, terminal 200 selects PUCCH resource set X1 from among the PUCCH resource sets in group X based on the number of bits of a response signal for eMBB. Also in Fig. 10A, terminal 200 selects PUCCH resource set Y0 from among the PUCCH resource sets in group Y based on the number of bits of a response signal for URLLC.

[0161] Furthermore, terminal 200 is notified of the PUCCH resource to be actually used from the selected PUCCH resource set by DCI (for example, DL assignment for eMBB or DL ​​assignment for URLLC shown in FIG. 10B) that allocates downlink data corresponding to each of response signals with different types of reliability, delay request, or use case (or service). Terminal 200 transmits a response signal using the PUCCH resource notified by the DCI from the selected PUCCH resource set.

[0162] According to Option 1, a PUCCH resource set is set individually for each reliability, delay request, or type of use case (or service), so that PUCCH resources suitable for response signals with different reliability, delay requests, or types of use cases (or services) can be more flexibly allocated.

[0163] The PUCCH resource set configuration example shown in FIG. 10A is an example, and is not limited thereto. For example, the number of PUCCH resource sets included in the group of PUCCH resource sets for eMBB and URLLC is not limited to four, and may be other numbers. Also, the number of PUCCH resource sets included in each group of PUCCH resource sets for eMBB and URLLC may be the same or different. Also, in FIG. 10A, eMBB and URLLC are described as an example of a case where the requirement conditions are different, but this is not limited thereto, and for example, the group of PUCCH resource sets may be configured according to at least one of different reliability or different delay requirements.

[0164] [Option 2] In Option 2, a group of the same PUCCH resource set is configured for response signals with different reliability, delay requirements, or types of use cases (or services) (in other words, response signals with different requirements). Thus, terminal 200 configures PUCCH resource sets included in the same group for response signals with different requirements.

[0165] FIG. 11A shows an example of a PUCCH resource set configuration in Option 2.

[0166] In FIG. 11A, a group including PUCCH resource sets 0, 1, 2, and 3 is set.

[0167] Terminal 200 determines which PUCCH resource set in the same group to use, based on the number of UCI bits (e.g., the number of HARQ-ACK bits) to transmit using the PUCCH, regardless of the reliability, delay requirement, or type of use case (or service), for example.

[0168] For example, in Fig. 11A, terminal 200 selects PUCCH resource set 1 from among PUCCH resource sets 0 to 3 based on the number of bits of a response signal for eMBB. Also, in Fig. 11A, terminal 200 selects PUCCH resource set 0 from among PUCCH resource sets 0 to 3 based on the number of bits of a response signal for URLLC.

[0169] Furthermore, terminal 200 is notified of the PUCCH resource to be actually used from the selected PUCCH resource set by DCI (for example, DL assignment for eMBB or DL ​​assignment for URLLC shown in FIG. 11B) that allocates downlink data corresponding to each of response signals with different reliability, delay request, or type of use case (or service). Terminal 200 transmits a response signal using the PUCCH resource notified by the DCI from the selected PUCCH resource set.

[0170] According to Option 2, the selectable PUCCH resource set is the same regardless of the reliability, delay requirement, or type of use case (or service), which can reduce overhead related to notification of the PUCCH resource set.

[0171] Furthermore, terminal 200 can individually determine the PUCCH resource set to be actually used based on the number of bits of each response signal having different reliability, delay request, or type of use case (or service). Therefore, terminal 200 can use PUCCH resources suitable for each response signal having different reliability, delay request, or type of use case (or service).

[0172] The method for determining a PUCCH resource set has been described above.

[0173] In this manner, in the present embodiment, terminal 200 applies different resource determination methods to response signals with different requirement conditions (for example, reliability, delay requirement, or type of use case (service)). Then, terminal 200 transmits each response signal using the PUCCH resource set for that response signal.

[0174] As a result, according to the present embodiment, terminal 200 can individually set radio resources according to the requirements of the response signals, thereby improving resource utilization efficiency or reducing delays in the response signals. As described above, according to the present embodiment, terminal 200 can appropriately transmit UCI including a response signal.

[0175] In the present embodiment, a method for determining different PUCCH resources or different PUCCH resource sets for response signals having different reliability, delay requirements, or types of use cases (or services) has been described. However, when the PUCCH resources determined for each response signal based on the resource determination method in the present embodiment are the same, terminal 200 may apply the same processing as in the first embodiment.

[0176] Also, in Option 1 according to the present embodiment, a case has been described in which a group of PUCCH resource sets is set for each reliability, delay request, or type of use case (or service). In addition, for parameters related to PUCCH resource sets, a difference may be created in the settable value (or value range) for each reliability, delay request, or type of use case (or service).

[0177] For example, in PUCCH Format 0 of NR, sequence selection is used (for example, see Non-Patent Document 1). In Release 15 NR, the transmission bandwidth that can be allocated to PUCCH transmission is 1RB, and a transmission sequence with a sequence length of 12, which corresponds to 1RB=12 subcarriers, is used. In addition, NR uses frequency allocation with one-cell repetition. In one-cell repetition, inter-cell interference is the main cause of performance degradation. In particular, in Short-PUCCH, the number of symbols used (one or two symbols) is small, so that it is not possible to suppress inter-cell interference by using multiple symbols to average the interference.

[0178] For this reason, when high reliability is required for the response signal, it is necessary to suppress the inter-cell interference. As a method for suppressing the inter-cell interference, it is effective to expand the transmission bandwidth (sequence length) (for example, see Non-Patent Document 6).

[0179] Therefore, for example, for PUCCH Format 0, the number of RBs or sequence length that can be set for PUCCH may be varied according to response signals with different reliability, delay requirements, or types of use cases (or services).

[0180] For example, a variable number of PRBs (e.g., 1, 2, or 4 PRBs) may be set in a PUCCH resource set for a response signal that requires high reliability. On the other hand, a PUCCH resource set for a response signal that does not require high reliability may have a configurable number of PRBs of 1 PRB. Note that the number of PRBs that can be set for each requirement is not limited to the above example, and may be another number.

[0181] As a result, even when high reliability is required for response signals in PUCCH Format 0, inter-cell interference can be suppressed by expanding the transmission bandwidth (sequence length).

[0182] Furthermore, for PUCCH Format 0, repetitive transmission in the time domain (Repetition) is also an effective technique for improving characteristics.

[0183] Therefore, for PUCCH Format 0, the number of repetitions that can be set for PUCCH may be varied according to response signals with different reliability, delay requirements, or types of use cases (or services).

[0184] For example, in a PUCCH resource set for a response signal that requires high reliability, Repetition may be configurable, and a variable number of Repetitions (for example, 1, 2, or 4) may be configurable. On the other hand, in a PUCCH resource set for a response signal that does not require high reliability, Repetition is not configurable. Note that the number of Repetitions that can be set for each requirement is not limited to the above example, and may be other numbers.

[0185] As a result, even when high reliability is required for a response signal in PUCCH Format 0, the effect of improving characteristics can be obtained by using Repetition.

[0186] Note that time domain Repetition includes a method of repeatedly transmitting the same sequence over multiple symbols. With this method, it is expected that the receiving side (for example, base station 100) will perform in-phase synthesis of the Repetition signals, thereby improving the power of the received signal, thereby improving characteristics. Also, time domain Repetition includes a method of expanding the sequence length and transmitting a part of the expanded sequence with a different symbol. For example, the sequence length is expanded from 12 to 24, and the first half of the sequence length of 24 is transmitted with the first symbol, and the second half is transmitted with the next symbol. With this method, it is expected that the use of a long sequence length will have the effect of suppressing interference.

[0187] As described above, for PUCCH format 0, by making it possible to set parameters different from those in Release 15 NR for the PUCCH resource set for response signals that require high reliability, requirements on the reliability of URLLC response signals that allow retransmissions that are not considered in Release 15 NR (for example, BLER = 10 -4 This enables PUCCH transmission that achieves an error rate of 100 Mbps or less.

[0188] (Variation of the second embodiment) In the second embodiment, a case has been described in which the method of determining the PUCCH resource or the PUCCH resource set is changed for response signals having different reliability, delay requirements, or types of use cases (or services).

[0189] In NR, in order to identify the slot position of the PUCCH for transmitting a response signal to downlink data (or the time from the slot in which downlink data is received to the slot in which PUCCH is transmitted), a method is adopted in which the base station notifies a set of quasi-static slot positions by a terminal-specific higher layer signal (e.g., RRC signaling) and notifies the slot position that will actually be used from the set of slot positions by DCI that allocates downlink data (e.g., see non-patent document 3).

[0190] Therefore, in a variation of embodiment 2, the set of PUCCH slot positions for transmitting response signals can also be set for each response signal having a different reliability, delay requirement, or type of use case (or service) (in other words, response signals with different requirements).

[0191] According to a variation of the second embodiment, terminal 200 can use an appropriate transmission slot for a response signal depending on the reliability of the response signal, the delay request, or the type of use case (or service). For example, if a set of different slot positions is set for different delay requests, terminal 200 can more flexibly allocate slots suitable for the delay requests to each of the response signals for the delay requests, even when the response signals for the delay requests are transmitted using different PUCCHs.

[0192] (Embodiment 3) A base station and a terminal according to the present embodiment have basic configurations in common with base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0193] In this embodiment, when terminal 200 simultaneously transmits response signals for data transmissions with different reliability, delay requirements, or types of use cases (or services) within the same slot, it drops all of the PUCCHs transmitting the response signals or punctures some of them depending on the priority of the PUCCHs.

[0194] The PUCCH to be dropped or partially punctured may be determined based on the reliability of ACK / NACK, delay requirement, or priority given according to the type of use case (or service).

[0195] Specifically, when response signals with different request conditions have the same transmission timing, terminal 200 drops all or punctures part of the PUCCH with a lower priority based on the request condition.

[0196] As an example of the priority of PUCCH, a case where the reliability of a response signal is different will be described. For example, in URLLC, the target error rate of the first data transmission is high (e.g., BLER=10 -1 The priority of the PUCCH, which transmits a response signal to the downlink data, is set such that the target error rate for the first data transmission is low (e.g., BLER=10 -5) is set higher than the priority of the PUCCH that transmits a response signal to the downlink data. In other words, the terminal 200 sets the priority of the PUCCH that transmits the response signal to the downlink data, which is set higher than the priority of the PUCCH that transmits the response signal to the downlink data. -5 ) Drop all or puncture some of the PUCCHs that transmit response signals to the downlink data.

[0197] Also, a case where the delay request of the response signal or the type of use case (or service) is different will be described. For example, Fig. 12 shows a case where there are two services, URLLC and eMBB. The priority of the PUCCH corresponding to URLLC is set higher than the priority of the PUCCH corresponding to eMBB. That is, terminal 200 drops all or punctures a part of the PUCCH corresponding to eMBB. For example, in Fig. 12, terminal 200 transmits a response signal corresponding to URLLC using the PUCCH corresponding to URLLC (URLLC PUCCH) and drops all of the PUCCH corresponding to eMBB (eMBB PUCCH).

[0198] According to this embodiment, PUCCH transmission for a response signal that requires higher reliability or low delay is not affected by PUCCH transmission for another response signal, so that the quality of the response signal that requires higher reliability or low delay can be guaranteed.

[0199] When puncturing a part of the PUCCH, for example, there is a method of puncturing symbols that overlap in time in PUCCH transmissions of different response signals, or a method of puncturing REs that overlap in time and frequency.

[0200] The method of puncturing symbols that overlap in time can be applied, for example, when terminal 200 cannot transmit multiple uplink signals simultaneously, or when terminal 200 has the capability to transmit multiple uplink signals simultaneously but the sum of the transmission power exceeds the maximum transmission power, and therefore it is necessary to transmit only one of the signals.

[0201] In addition, the method of puncturing REs that overlap in time and frequency can be applied, for example, when terminal 200 has the capability of simultaneously transmitting multiple uplink signals and the maximum transmission power of terminal 200 is not exceeded even when multiple uplink signals are simultaneously transmitted.

[0202] (Embodiment 4) For example, in the first embodiment, a case has been described in which different encoding processes are applied to response signals having different reliability, delay requirements, or types of use cases (or services). However, performing different encoding processes increases the amount of processing at the terminal, which may complicate implementation.

[0203] Therefore, in this embodiment, a method of applying one encoding process to response signals having different reliability, delay requirements, or types of use cases (or services) will be described.

[0204] A base station and a terminal according to the present embodiment have basic configurations in common with base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0205] Terminal 200 has 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 a PUCCH. In NR, terminal 200 reports “N1” to base station 100.

[0206] 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, for the PDSCH-to-HARQ-ACK timing, a value that exceeds the processing capability (N1) of terminal 200 reported by terminal 200 (in other words, a value smaller than N1).

[0207] In this embodiment, terminal 200 defines capabilities (N1) for transmitting response signals with different reliability, delay requirements, or types of use cases (or services), and reports them to base station 100. Furthermore, terminal 200 determines a transmission method and parameters of a response signal or a PUCCH used for transmitting the response signal (in other words, a processing mode for the response signal or PUCCH) based on the value of PDSCH-to-HARQ-ACK timing set and notified by base station 100 and the defined value of N1.

[0208] 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.

[0209] 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 more likely to require lower delay than eMBB, N1 for URLLC may be set to a value smaller than N1 for eMBB.

[0210] As described in the variation of the second embodiment, with regard to identifying the slot position of the PUCCH for transmitting a response signal to downlink data (PDSCH-to-HARQ-ACK timing), base station 100 notifies a set of semi-static slot positions by a terminal-specific higher layer signal (e.g., RRC signaling), and notifies which PDSCH-to-HARQ-ACK timing from the set will actually be used by DCI that allocates downlink data.

[0211] 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.

[0212] For example, as shown in FIG. 13, when the minimum value of the PDSCH-to-HARQ-ACK timing for each response signal (in FIG. 13, PDSCH-to-HARQ-ACK timing for URLLC) is equal to or greater than N1 for eMBB (N1_X or N1_eMBB), terminal 200 performs a common encoding process (joint encoding) on ​​the response signal corresponding to eMBB and the response signal corresponding to URLLC to generate an HARQ-ACK bit.

[0213] Specifically, in FIG. 13, terminal 200 can complete processing from generating a response signal corresponding to eMBB to transmitting a PUCCH including the response signal during the time period corresponding to PDSCH-to-HARQ-ACK timing for URLLC after terminal 200 receives a PDSCH for URLLC until the time period corresponding to PDSCH-to-HARQ-ACK timing for URLLC has elapsed (in other words, N1_X / N1_eMBB≦PDSCH-to-HARQ-ACK timing for URLLC). Thus, terminal 200 can perform a common encoding process on the response signal for URLLC and the response signal for eMBB during the time period corresponding to PDSCH-to-HARQ-ACK timing for URLLC after terminal 200 receives a PDSCH for URLLC until the time period corresponding to PDSCH-to-HARQ-ACK timing for URLLC has elapsed.

[0214] On the other hand, as shown in FIG. 14, when 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 (PDSCH-to-HARQ-ACK timing for URLLC in FIG. 14) is less than N1 (N1_X or N1_eMBB) corresponding to eMBB, terminal 200 cannot perform a common encoding process on the response signal corresponding to eMBB and the response signal corresponding to URLLC.

[0215] Specifically, in FIG. 14, terminal 200 cannot complete the process of generating a response signal corresponding to eMBB and transmitting a PUCCH including the response signal between the time when terminal 200 receives a PDSCH for URLLC and the time when a time corresponding to PDSCH-to-HARQ-ACK timing for URLLC has elapsed (in other words, N1_X / N1_eMBB > PDSCH-to-HARQ-ACK timing for URLLC).

[0216] Therefore, terminal 200 cannot collectively code the ACK / NACK of URLLC and the ACK / NACK of eMBB during the time period corresponding to the PDSCH-to-HARQ-ACK timing for URLLC after terminal 200 receives the PDSCH for URLLC. In this case, terminal 200 uses the method of either embodiment 3 or embodiment 1.

[0217] For example, when the method of the third embodiment is used, the number of encoding processes can be limited to one overall for response signals having different reliability, delay requests, or types of use cases (or services), which has the advantage of simplifying the implementation of terminal 200. Also, when the method of the first embodiment is used, terminal 200 can generate HARQ-ACK bits by appropriate encoding (or encoding rate) according to the reliability, delay request, or type of use case (or service) of the response signal, as shown in Fig. 14, which enables efficient PUCCH transmission in terms of resource utilization efficiency.

[0218] In this way, according to the present embodiment, it is possible to standardize the encoding process as much as possible depending on the processing capacity of the terminal 200, so that it is possible to reduce an increase in the amount of processing by the terminal 200 or a complexity of implementation.

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

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

[0221] Here, as an example of a case where the transmission method and parameters of the response signal or PUCCH are different, the reliability of the response signal may be different. For example, in URLLC, the target error rate of 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 difference can be made in the transmission method and parameters of the response signal or PUCCH between 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.

[0222] As an example of a case where the transmission method and parameters of the response signal or PUCCH are different, there may be a case where the delay requirement for the response signal is different or the use case (or service) is different. For example, the transmission method and parameters of the response signal or PUCCH may be different between a response signal corresponding to URLLC and a response signal corresponding to eMBB. While the former response signal requires high reliability or low delay, the latter response signal does not require such high reliability or low delay. As described above, URLLC has a high target error rate for the first data transmission (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 the downlink data.

[0223] Also, examples of differences in the transmission method of the response signal or PUCCH are not limited to reliability, delay request, or type of use case (service), and may include, for example, different physical layer parameters. For example, eMBB may be replaced with "slot-by-slot transmission", and URLLC may be replaced with "non-slot-by-slot transmission". Also, 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". Also, the present invention is not limited to transmissions corresponding to eMBB and URLLC, and may replace eMBB with a transmission having a longer transmission interval (for example, slot length or symbol length), and URLLC with a transmission having a shorter transmission interval than the transmission interval described above.

[0224] In addition, 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 each of the first transmission and the retransmission.

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

[0226] [Example 1: Scramble 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 a DCI that schedules downlink data transmission corresponding to each response signal.

[0227] For example, in DCI for PDSCH assuming eMBB, C-RNTI (Cell-Radio Network Temporary Identifier) ​​or CS-RNTI (Configured Scheduling-RNTI) or the like is used as a terminal-specific scrambling sequence. Thus, when the detected scrambling sequence is different from C-RNTI and CS-RNTI, terminal 200 determines that the reliability of the response signal is high, the delay requirement is strict, or the signal is URLLC. Also, when the detected scrambling sequence is 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 signal is eMBB.

[0228] 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 of the terminal 200, a delay request, or the type of use case (service). The determined information is output to the downlink control signal generating unit 109 of the base station 100. As described above, the downlink control signal generating unit 109 generates a DCI bit string using a scrambling sequence according to the reliability of downlink data of the terminal 200, a delay request, or the type of use case (or service).

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

[0230] [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.

[0231] 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.

[0232] For example, the terminal 200 has an MCS table set in the URLLC with a target BLER of 10. -1 On the other hand, if the MCS table set in the URLLC is for achieving the target BLER=10, the 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.

[0233] 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 generating unit 109, the encoding unit 103, and the modulation unit 105 of the base station 100. The downlink control signal generating unit 109 includes information related to the MCS table used for downlink data transmission in a bit string of DCI. 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.

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

[0235] [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 a response signal based on the “PDSCH-to-HARQ-ACK timing” or the number of transmission symbols of the PDSCH notified by DCI that schedules downlink data transmission corresponding to each response signal.

[0236] For example, when the PDSCH-to-HARQ-ACK timing is equal to or smaller than a predetermined value or the number of PDSCH transmission symbols is equal to or smaller than a predetermined number of symbols, terminal 200 determines that the response signal has a strict delay requirement or is a response signal for URLLC. On the other hand, when 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 response signal has a lenient delay requirement or is a response signal for eMBB.

[0237] The above-mentioned predetermined value or the 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.

[0238] For example, the control unit 101 of the base station 100 determines the PDSCH-to-HARQ-ACK timing or the number of transmission symbols of the PDSCH, which indicates the slot position for transmitting a response signal to the downlink data of 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 transmission symbols of the PDSCH in the bit string of the DCI.

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

[0240] [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.

[0241] 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.

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

[0243] For example, the control unit 101 of the base station 100 determines information related to a CQI table that is set for downlink data transmission of the terminal 200. The determined information is output to the higher-level control signal generating unit 106. The higher-level control signal generating unit 106 includes the information related to the CQI table in the higher-level control signal.

[0244] Meanwhile, decoding unit 208 of terminal 200 decodes the higher control signal and outputs the decoded result to control unit 211. Control unit 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 control signal.

[0245] [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 schedule downlink data transmission corresponding to each response signal.

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

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

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

[0249] The above describes the method for determining the "reliability, delay request, or type of use case (or service)" of the response signal. Note that the method for determining the "reliability, delay request, or type of use case (or service) of the response signal" is not limited to the above-mentioned examples 1 to 5, and may be a determination method based on other information related to the request conditions.

[0250] (3) In the above embodiment, a case where a response signal for downlink data transmission is transmitted using PUCCH has been described as an example. However, in the present disclosure, UCI transmitted using PUCCH is not limited to a response signal. For example, in the above embodiment, 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.

[0251] (4) The present disclosure can be realized by software, hardware, or software linked to hardware. Each functional block used in the description of the above embodiment may be realized, in part or in whole, as an LSI, which is an integrated circuit, and each process described in the above embodiment may be controlled, in part or in whole, by one LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of one chip to include some or all of the functional blocks. The LSI may have input and output data. Depending on the degree of integration, the LSI may be called an IC, a system LSI, a super LSI, or an ultra LSI. The method of integration is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. In addition, a field programmable gate array (FPGA) that can be programmed after LSI manufacture, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells inside the LSI may be used. The present disclosure may be realized as digital processing or analog processing. Furthermore, if a new integrated circuit technology that can replace LSI appears due to the progress of semiconductor technology or a derivative technology, it is possible to integrate the functional blocks using that technology. The application of biotechnology is also a possibility.

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

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

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

[0255] 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.

[0256] 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.

[0257] A terminal in one embodiment of the present disclosure includes a circuit that determines a processing mode for uplink control information or an uplink control channel used for transmitting the uplink control information in accordance with a requirement for the uplink control information, and a transmitter that transmits the uplink control information using the uplink control channel based on the determined processing mode.

[0258] In a terminal according to one embodiment of the present disclosure, the circuit applies different encoding methods to the uplink control information having different requirements, and the transmitter multiplexes and transmits the encoded uplink control information on the uplink control channel.

[0259] In a terminal according to one embodiment of the present disclosure, the requirements include reliability or delay requirements, and are mapped onto the uplink control channel in the order of the uplink control information for which a higher reliability is required, or in the order of the uplink control information for which a lower delay is required in the delay requirements.

[0260] In a terminal according to an embodiment of the present disclosure, the uplink control information is mapped in the uplink control channel in order from the frequency direction to the time direction.

[0261] In a terminal according to an embodiment of the present disclosure, the uplink control information is mapped in a distributed manner in the frequency direction.

[0262] In a terminal according to an embodiment of the present disclosure, the uplink control information that requires a higher reliability is mapped to a symbol that is closer to a symbol to which a reference signal is mapped in the uplink control channel.

[0263] In a terminal according to an embodiment of the present disclosure, the uplink control information for which a lower delay is required in the delay request is mapped to an earlier symbol of the uplink control channel.

[0264] In a terminal according to an embodiment of the present disclosure, a resource set for the uplink control channel is determined based on a total number of encoded bits of the uplink control information multiplexed onto the uplink control channel.

[0265] In a terminal according to an embodiment of the present disclosure, a maximum coding rate is set for each of the requirements for the uplink control information.

[0266] In a terminal according to an embodiment of the present disclosure, when a coding rate of the uplink control information exceeds a predetermined threshold, at least a portion of the uplink control information is dropped in the uplink control channel.

[0267] In a terminal according to an embodiment of the present disclosure, the predetermined threshold is the maximum coding rate.

[0268] In a terminal according to an embodiment of the present disclosure, the predetermined threshold is notified to the terminal from a base station.

[0269] In a terminal according to an embodiment of the present disclosure, the uplink control information to be dropped is determined according to a priority set for each of the requirements.

[0270] In a terminal according to one embodiment of the present disclosure, when the number of resource blocks calculated from the number of bits of the uplink control information and the maximum coding rate exceeds a predetermined threshold, at least a portion of the uplink control information is dropped in the uplink control channel.

[0271] In a terminal according to an embodiment of the present disclosure, information indicating a ratio of resources shared between the uplink control information having different requirements is notified from a base station to the terminal in the uplink control channel.

[0272] In a terminal according to an embodiment of the present disclosure, different resource determination methods are applied in the uplink control channel to the uplink control information having different requirements.

[0273] In a terminal in one embodiment of the present disclosure, the number of uplink control channels for transmitting the uplink control information in one slot is one or more, and the transmitter transmits the uplink control information having different requirements using different uplink control channels in the one slot.

[0274] In a terminal according to an embodiment of the present disclosure, the circuit configures resource sets included in different groups for the uplink control information having different requirements.

[0275] In a terminal according to an embodiment of the present disclosure, the circuit configures resource sets included in the same group for the uplink control information having different requirements.

[0276] In a terminal according to an embodiment of the present disclosure, the parameters related to the resource set are different for each of the uplink control information having different requirements.

[0277] In a terminal according to an embodiment of the present disclosure, the parameter is the number of resource blocks or a sequence length of the uplink control channel.

[0278] In a terminal according to an embodiment of the present disclosure, the parameter is a number of repetitions of the uplink control information.

[0279] In a terminal according to an embodiment of the present disclosure, a slot position for transmitting the uplink control information is set for each of the uplink control information having different requirement conditions.

[0280] In a terminal according to one embodiment of the present disclosure, when the transmission of the uplink control information having different requirements occurs at the same timing, the circuit drops all or punctures part of the uplink control channel having a lower priority based on the requirements.

[0281] In a terminal in one embodiment of the present disclosure, the uplink control information is a response signal to downlink data, the capability of the terminal regarding the processing time required from receiving the downlink data to transmitting the response signal is specified for each of the required conditions, timing information indicating the time from receiving the downlink data to transmitting the response signal is notified from a base station to the terminal, and the circuit determines the processing mode based on the timing information and the capability.

[0282] A communication method in one embodiment of the present disclosure determines a processing mode for uplink control information or an uplink control channel used to transmit the uplink control information in accordance with a requirement for the uplink control information, and transmits the uplink control information using the uplink control channel based on the determined processing mode.

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

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

[0285] 100 base stations 101,211 Control section 102 Data Generation Division 103,107,110,212 Encoding section 104 Retransmission control section 105, 108, 111, 213 Modulation section 106 Upper control signal generator 109 Downstream control signal generator 112,214 Signal allocation section 113,215 IFFT section 114,216 Transmitter 115,201 Antennas 116,202 Receiver 117,203 FFT section 118,204 Extraction part 119 Demodulation section 120,206,208,210 Decoding section 121 Judgment section 200 terminals 205 Downstream control signal demodulation section 207 Higher control signal demodulation section 209 Data demodulation section

Claims

1. a transmitter for transmitting information indicating a first uplink control channel (PUCCH) resource set for a first uplink control information having a first priority and a second PUCCH resource set for a second uplink control information having a second priority; a receiver for receiving at least one of the first uplink control information and the second uplink control information, The first uplink control information and the second uplink control information are multiplexed into one slot. Base station.

2. The first uplink control information and the second uplink control information are encoded by different encoding methods. The base station according to claim 1 .

3. a PUCCH resource set is determined based on a total number of bits after coding of the first uplink control information and the second uplink control information after coding; The base station according to claim 1 .

4. a maximum coding rate of the first uplink control information and a maximum coding rate of the second uplink control information are different from each other. The base station according to claim 1 .

5. the number of resource blocks used for the reception is determined based on a number of bits and a maximum coding rate of the first uplink control information, and a number of bits and a maximum coding rate of the second uplink control information. The base station according to claim 1 .

6. A first set of slot positions is determined for a response signal included in the first uplink control information, and a second set of slot positions is determined for a response signal included in the second uplink control information; Based on first information in downlink control information, one of the first priority and the second priority is determined, and based on the one of the priorities, one of the first set of slot positions and the second set of slot positions is determined; one slot position is determined from either the first set of slot positions or the second set of slot positions based on second information in the downlink control information; The base station according to claim 1 .

7. The base station is Transmitting information indicating a first uplink control channel (PUCCH) resource set for a first uplink control information having a first priority and a second PUCCH resource set for a second uplink control information having a second priority; receiving at least one of the first uplink control information and the second uplink control information; The first uplink control information and the second uplink control information are multiplexed into one slot. Communication methods.

8. The first uplink control information and the second uplink control information are encoded by different encoding methods. The communication method according to claim 7.

9. a PUCCH resource set is determined based on a total number of bits after coding of the first uplink control information and the second uplink control information after coding; The communication method according to claim 7.

10. a maximum coding rate of the first uplink control information and a maximum coding rate of the second uplink control information are different from each other. The communication method according to claim 7.

11. the number of resource blocks used for the reception is determined based on a number of bits and a maximum coding rate of the first uplink control information, and a number of bits and a maximum coding rate of the second uplink control information. The communication method according to claim 7.

12. A first set of slot positions is determined for a response signal included in the first uplink control information, and a second set of slot positions is determined for a response signal included in the second uplink control information; Based on first information in downlink control information, one of the first priority and the second priority is determined, and based on the one of the priorities, one of the first set of slot positions and the second set of slot positions is determined; one slot position is determined from either the first set of slot positions or the second set of slot positions based on second information in the downlink control information; The communication method according to claim 7.

13. transmitting information indicating a first uplink control channel (PUCCH) resource set for a first uplink control information having a first priority and a second PUCCH resource set for a second uplink control information having a second priority; a process of receiving at least one of the first uplink control information and the second uplink control information; The first uplink control information and the second uplink control information are multiplexed into one slot. Integrated circuits.