Base station, communication method, and integrated circuit

Abstract

To provide a terminal and a communication method for improving uplink transmission efficiency in radio communication.SOLUTION: A receiver, configured to receive uplink control information on a physical uplink control channel resource, where the uplink control information includes first HARQ-ACK information with a first priority and second HARQ-ACK information with a second priority higher than the first priority; When the uplink control information includes first HARQ-ACK information, second HARQ-ACK information and SchedulingRequest (SR) information with a second priority, the second HARQ-ACK information and the SR information are concatenated, and the uplink control information in which the concatenated information with the second priority and the first HARQ-ACK information are multiplexed is received on the physical uplink control channel resource, where the concatenated second HARQ-ACK information and SR information are jointly encoded; The concatenated information with the second priority and the first HARQ-ACK information are separately encoded.SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] In recent years, the expansion and diversification of wireless services has led to expectations for the dramatic development of the Internet of Things (IoT). Mobile communications are expanding from smartphones and other information terminals to a wide range of applications, including automobiles, homes, home appliances, and industrial equipment. To support this diversification, significant improvements in the performance and functionality of mobile communication systems are required, addressing various requirements, such as increased system capacity, an increased number of connected devices, and low latency. Fifth-generation mobile communication systems (5G) will provide flexible wireless communications to meet a wide variety of needs through enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC).

[0003] The 3rd Generation Partnership Project (3GPP), an international standardization organization, is currently working on the specification of New Radio (NR) as one of the 5G radio interfaces. NR supports functions that realize URLLC in addition to the high speed and large capacity that are the basic requirements for eMBB (see, for example, Non-Patent Documents 1-4). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.211 V16.3.0, "NR; Physical channels and modulation (Release 16)", September 2020. [Non-Patent Document 2] 3GPP TS 38.212 V16.3.0, "NR; Multiplexing and channel coding (Release 16)", September 2020. [Non-Patent Document 3] 3GPP TS 38.213 V16.3.0, "NR; Physical layer procedure for control (Release 16)", September 2020. [Non-Patent Document 4] 3GPP TS 38.214 V16.3.0, "NR; Physical layer procedures for data (Release 16)", September 2020. [Non-Patent Document 5] 3GPP TSG RAN Meeting #88e, RP-201310, "Revised WID: Enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR", Nokia, Nokia Shanghai Bell, June 29 - July 3, 2020. [Non-Patent Document 6] 3GPP TSG RAN WG1 Meeting #102e, R1-2005201, "Final Report of 3GPP TSG RAN WG1 #101-e v1.0.0 (Online meeting, 25th May - 5th June 2020)" MCC Support, August 2020. [Summary of the Invention]

[0005] However, there is room for further study on methods for improving uplink transmission efficiency in wireless communications.

[0006] Non-limiting embodiments of the present disclosure contribute to providing a terminal, a base station, and a communication method that can improve uplink transmission efficiency in wireless communication.

[0007] A terminal according to one embodiment of the present disclosure includes a control circuit that varies parameters used for transmitting a plurality of uplink control signals having different priorities according to information related to the size of at least one of the plurality of uplink control signals, and a transmission circuit that transmits the plurality of uplink control signals.

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

[0009] According to an embodiment of the present disclosure, it is possible to improve uplink transmission efficiency in wireless communication.

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

[0011] [Figure 1] FIG. 1 shows an example of transmission of an uplink signal. [Figure 2] Block diagram showing an example of the configuration of a part of a terminal [Figure 3] Block diagram showing an example of the configuration of a base station [Figure 4] Block diagram showing an example of a terminal configuration [Figure 5]FIG. 1 is a diagram showing an example of a combination of multiplexed signals according to the first embodiment; [Figure 6] 10 is a flowchart showing an example of a transmission operation in a terminal. [Figure 7] FIG. 10 is a diagram showing an example of a combination of multiplexed signals according to the second embodiment; [Figure 8] Diagram of an example architecture of a 3GPP NR system [Figure 9] Schematic diagram showing functional separation between NG-RAN and 5GC [Figure 10] Sequence diagram of the Radio Resource Control (RRC) connection setup / reconfiguration procedure [Figure 11] Schematic diagram showing usage scenarios for enhanced Mobile BroadBand (eMBB), massive Machine Type Communications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). [Figure 12] Block diagram illustrating an exemplary 5G system architecture for a non-roaming scenario DETAILED DESCRIPTION OF THE INVENTION

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

[0013] For example, a terminal (also referred to as User Equipment (UE)) may use an uplink control channel (e.g., PUCCH: Physical Uplink Control Channel) to transmit a response signal (ACK / NACK: Acknowledgement / Negative Acknowledgement, or also referred to as Hybrid Automatic Repeat Request (HARQ)-ACK) indicating an error detection result of a downlink data signal (e.g., PDSCH: Physical Downlink Shared Channel), downlink channel state information (CSI: Channel State Information), and an uplink radio resource allocation request (SR: Scheduling Request) to a base station (e.g., gNB). HARQ-ACK, CSI, and SR are also referred to as uplink control information (e.g., UCI: Uplink Control Information).

[0014] Furthermore, it is assumed that a terminal supporting NR supports, for example, multiple services (e.g., eMBB and URLLC) having different requirements. For example, in uplink transmissions of a terminal, UCI for multiple services having different requirements may occur simultaneously. Furthermore, for example, in a terminal, transmission resources (e.g., PUCCH resources) allocated for transmitting UCI for multiple services having different requirements may overlap in time.

[0015] In this case, for example, if a terminal has the capability to simultaneously transmit multiple channels (e.g., multiple PUCCHs), the terminal can simultaneously transmit UCI for each of multiple services having different requirements without considering the influence of each other. On the other hand, for example, if a terminal does not have the capability to simultaneously transmit multiple channels, the terminal may perform an operation such as transmitting a signal of any one of the multiple channels (e.g., multiple PUCCHs) (in other words, dropping transmission of other channels) or controlling the transmission power of each channel.

[0016] For example, the transmission priority of each UCI corresponding to a plurality of services (e.g., priority for each service) can be determined. In NR Rel. 16, for example, the priority in the physical (PHY) layer of UCI transmitted by a terminal can be set (see, for example, Non-Patent Document 3). For example, when UCI transmissions overlap in time, the terminal may transmit a UCI with a higher priority and drop the transmission of a UCI with a lower priority based on information regarding the priority of each UCI in the PHY layer.

[0017] Fig. 1 is a diagram showing an example of uplink signal transmission. Fig. 1 shows an example in which transmission of a HARQ-ACK for URLLC transmission set to high priority (HP) (hereinafter also referred to as "high priority HARQ-ACK") and transmission of a HARQ-ACK for eMBB set to low priority (LP) (hereinafter also referred to as "low priority HARQ-ACK") overlap in time. In the example shown in Fig. 1, the terminal drops the transmission of a HARQ-ACK for eMBB transmission set to low priority and transmits a HARQ-ACK for URLLC transmission set to high priority.

[0018] In this case, the terminal can transmit HARQ-ACK for URLLC transmission set to high priority without being affected by other channels (e.g., channels corresponding to eMBB transmission). On the other hand, HARQ-ACK for eMBB transmission set to low priority is not transmitted regardless of the decoding result (e.g., decoding success or decoding failure) of the PDSCH for eMBB transmission, making it difficult for the base station to determine whether the terminal has correctly decoded the PDSCH for eMBB transmission. Therefore, for example, the PDSCH for eMBB transmission is retransmitted regardless of the decoding result of the terminal, which may result in a degradation of frequency utilization efficiency of downlink transmission.

[0019] As a method for suppressing degradation of frequency utilization efficiency in downlink transmission, NR Rel. 17 is considering, for example, a method of multiplexing and transmitting UCIs having different priorities in the same uplink resource (e.g., PUCCH resource) (see, for example, Non-Patent Document 5). As an example, scenarios considered in NR Rel. 17 are multiplexing a high-priority HARQ-ACK and a low-priority HARQ-ACK, multiplexing a high-priority SR and a low-priority HARQ-ACK, and multiplexing a high-priority SR, a high-priority HARQ-ACK, and a low-priority HARQ-ACK (see, for example, Non-Patent Document 6).

[0020] Examples of coding methods that a terminal can use when multiplexing and transmitting high-priority UCI and low-priority UCI on the same PUCCH resource include a method of jointly coding the high-priority UCI and low-priority UCI (hereinafter referred to as "Joint coding"), a method of independently (or individually) coding the high-priority UCI and low-priority UCI (hereinafter referred to as "Separate coding"), and a method of combining Joint coding and Separate coding.

[0021] Joint coding is a method applied, for example, when UCIs having the same NR priority are multiplexed and transmitted on a PUCCH resource. Applying joint coding to multiplexing UCIs having different priorities is advantageous in terms of ease of implementation in a terminal. On the other hand, joint coding may result in inappropriate settings of at least one of the coding rate and resource allocation for UCIs with different priorities. For example, a lower coding rate may be set for a UCI that has a higher priority and requires higher reliability than other UCIs in order to meet the required conditions. Joint coding, for example, may be inefficient in terms of resource utilization efficiency because the same low coding rate as for UCIs with higher priorities is set for UCIs with lower priorities. Furthermore, joint coding may result in degradation of transmission quality for UCIs with higher priorities because, for example, when a coding rate is set according to the required conditions of a UCI with lower priority, the same coding rate is also set for UCIs with higher priorities.

[0022] Furthermore, in separate coding, for example, UCI with different priorities is coded separately, which can suppress the degradation of resource utilization efficiency or transmission quality described in joint coding. On the other hand, when multiple coding methods are used in separate coding, overhead may increase due to the addition of Cyclic Redundancy Check (CRC) bits for each coding method. Furthermore, for example, an increase in the number of coding methods applied by a terminal to transmit a PUCCH signal (e.g., UCI) may increase the amount of processing required for implementation in the terminal. For example, an increase in the number of coding methods using a polar coder adopted as a UCI coding method in NR is undesirable from the perspective of ease of implementation in the terminal.

[0023] Furthermore, when combining joint coding and separate coding, there is room for further consideration regarding the method of selecting between joint coding and separate coding.

[0024] Furthermore, in NR, a PUCCH format is defined according to the number of UCI bits. For example, when UCI of 2 bits or less is transmitted, either PUCCH format 0 or PUCCH format 1 is used. Here, UCI coding is not used for PUCCH format 0 and PUCCH format 1, so there is room for consideration of a transmission method when the total number of UCI bits after multiplexing is 2 bits or less.

[0025] Therefore, in one non-limiting embodiment of the present disclosure, a method for improving the transmission efficiency (e.g., resource utilization efficiency, transmission quality, or ease of implementation of a terminal) of uplink signals in a scenario in which transmissions of uplink signals (e.g., UCI) having different priorities overlap in time is described.

[0026] For example, the following features are available regarding NR wireless communication:

[0027] (1) For example, in NR, there is no suitable coding method for 1- or 2-bit UCI. Therefore, for example, when 1- or 2-bit UCI is multiplexed with other UCI, even if a coding method suitable for the other UCI is applied to the 1- or 2-bit UCI, it is difficult for the 1- or 2-bit UCI to obtain coding gain.

[0028] (2) For example, in NR, a block code (e.g., a Reed Muller (RM) code) is used for UCI of 3 bits or more and 11 bits or less. Although a CRC can be added to a block code, in NR, a CRC does not need to be added when encoding UCI of 3 bits or more and 11 bits or less from the viewpoint of overhead reduction.

[0029] Due to the above-mentioned features (1) and (2), for example, when the number of UCI bits for low priority or high priority is 1 or 2 bits, or when the number of UCI bits after multiplexing is relatively small (for example, below a threshold), applying joint coding can improve transmission efficiency compared to separate coding.

[0030] (3) For example, the larger the number of low-priority or high-priority UCI bits, the smaller the proportion of CRC overhead in the number of UCI bits. Also, the larger the number of UCI bits, the larger the amount of PUCCH resources. Therefore, for example, the larger the number of low-priority or high-priority UCI bits, the smaller the impact on the total UCI bits of an increase in CRC overhead due to individual encoding of UCI.

[0031] According to the above-mentioned feature (3), when the number of low-priority or high-priority UCI bits is relatively large (for example, when it is larger than a threshold), applying separate coding can improve transmission efficiency in terms of resource utilization efficiency compared to joint coding. Also, according to feature (2), when the number of UCI bits individually coded in separate coding is 11 bits or less, there is no need to add a CRC, so that a decrease in resource utilization efficiency can be suppressed.

[0032] (4) For example, from the viewpoint of ease of implementation in terminals, it is desirable to limit the number of encodings (e.g., the number of polar encodings). For example, when polar encoding is set for low-priority and high-priority UCIs, the number of encodings can be reduced by applying joint coding compared to separate coding, thereby improving transmission efficiency.

[0033] (5) For example, in NR, a PUCCH format is defined according to the number of UCI bits. For example, PUCCH format 0 or PUCCH format 1 may be set for UCI of 2 bits or less, and PUCCH format 2, 3, or 4 may be set for UCI of 3 bits or more.

[0034] In a non-limiting example of the present disclosure, for example, taking into consideration the above-described characteristics, the terminal may control multiplexing of UCI in a PUCCH based on at least one of parameters (or elements) related to uplink signals, such as the number of low-priority UCI bits, the number of high-priority UCI bits, the number of UCI bits after multiplexing, a PUCCH format, or a limit on the number of coding modes (e.g., information related to an upper limit on the number of coding modes in the terminal). For example, the terminal may vary the PUCCH transmission method or parameters based on these parameters related to uplink signals, or may flexibly set the PUCCH transmission method or parameters. In a non-limiting example of the present disclosure, the control of UCI multiplexing may include, for example, at least one of a UCI coding method (e.g., joint coding or separate coding), a method of mapping UCI to PUCCH resources, a PUCCH format after UCI multiplexing, and parameter settings related thereto.

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

[0036] 2 is a block diagram illustrating a configuration example of a portion of terminal 200 according to an embodiment of the present disclosure. In terminal 200 illustrated in FIG. 2, control unit 205 (e.g., corresponding to a control circuit) varies parameters used for transmitting multiple uplink control signals (e.g., UCI) having different priorities according to information related to the size (e.g., the number of bits) of at least one of the multiple uplink control signals. Transmitting unit 209 (e.g., corresponding to a transmitting circuit) transmits the multiple uplink control signals.

[0037] [Base station configuration] Fig. 3 is a block diagram showing an example configuration of a base station 100 according to embodiment 1. In Fig. 3, the base station 100 includes a control unit 101, a higher control signal generation unit 102, a downlink control information generation unit 103, an encoding unit 104, a modulation unit 105, a signal allocation unit 106, a transmission unit 107, a reception unit 108, an extraction unit 109, a demodulation unit 110, and a decoding unit 111.

[0038] The control unit 101 determines, for example, information related to a downlink signal for transmitting a downlink data signal (for example, a PDSCH). The information related to the downlink signal may include, for example, information such as a modulation and coding scheme (MCS) of the data signal transmitted in the PDSCH and radio resource allocation for the PDSCH. The control unit 101 outputs, for example, the determined information to the encoding unit 104, the modulation unit 105, and the signal allocation unit 106. Furthermore, the control unit 101 outputs, for example, the information related to the downlink signal to the downlink control information generation unit 103.

[0039] Furthermore, control unit 101 determines, for example, information related to the transmission of an uplink control signal (e.g., UCI) by terminal 200. The information related to the transmission of UCI may include, for example, information related to a UCI encoding method, a UCI mapping method to a PUCCH, a PUCCH format after UCI multiplexing, or parameters corresponding thereto. Control unit 101 outputs, for example, the determined information related to the transmission of UCI to extraction unit 109 and decoding unit 111.

[0040] Furthermore, control section 101 outputs information related to the transmission of the determined UCI to higher control signal generation section 102 or downlink control information generation section 103. The information output to higher control signal generation section 102 may include, for example, information related to a PUCCH resource set (for example, PUCCH resource candidates), information related to the maximum coding rate of UCI, or information related to the priority of UCI. The information output to downlink control information generation section 103 may include, for example, information indicating PUCCH resources to be allocated to terminal 200 in the PUCCH resource set, or information related to the priority of UCI.

[0041] In addition, the control unit 101 determines, for example, information regarding a downlink signal for transmitting an upper control signal or downlink control information (for example, a modulation and coding scheme (MCS) and radio resource allocation), and outputs the determined information to the encoding unit 104, the modulation unit 105, and the signal allocation unit 106.

[0042] The higher-level control signal generating section 102 generates a higher-level layer control signal bit sequence based on information input from the control section 101 , for example, and outputs the higher-level layer control signal bit sequence to the encoding section 104 .

[0043] The downlink control information generating unit 103 generates a downlink control information (e.g., DCI) bit string based on, for example, information input from the control unit 101, and outputs the generated DCI bit string to the encoding unit 104. Note that the control information may be transmitted to multiple terminals.

[0044] For example, based on information input from the control unit 101, the coding unit 104 codes downlink data (for example, a DL data signal), a bit string input from the higher control signal generation unit 102, or a DCI bit string input from the downlink control information generation unit 103. The coding unit 104 outputs the coded bit string to the modulation unit 105.

[0045] The modulation unit 105 modulates the coded bit sequence input from the coding unit 104, for example, based on information input from the control unit 101, and outputs the modulated signal (for example, a symbol sequence) to the signal allocation unit 106.

[0046] The signal allocation unit 106 maps the symbol sequence (including, for example, a downlink data signal or a control signal) input from the modulation unit 105 to the radio resource, for example, based on information indicating the radio resource input from the control unit 101. The signal allocation unit 106 outputs the downlink signal onto which the signal has been mapped to the transmission unit 107.

[0047] For example, transmitting unit 107 performs a transmission waveform generation process such as orthogonal frequency division multiplexing (OFDM) on the signal input from signal allocation unit 106. Furthermore, in the case of OFDM transmission that adds a cyclic prefix (CP), transmitting unit 107 performs an inverse fast Fourier transform (IFFT) process on the signal and adds a CP to the signal after IFFT. Furthermore, transmitting unit 107 performs RF processing such as D / A conversion or up-conversion on the signal, and transmits the radio signal to terminal 200 via an antenna.

[0048] The receiving unit 108 performs RF processing such as downconvert or A / D conversion on an uplink signal received from the terminal 200 via an antenna. In addition, in the case of OFDM transmission, the receiving unit 108 performs Fast Fourier Transform (FFT) processing on the received signal, and outputs the resulting frequency domain signal to the extracting unit 109.

[0049] The extraction unit 109 extracts, for example, based on information input from the control unit 101, a radio resource portion from which an uplink control signal (for example, a PUCCH) transmitted by the terminal 200 is transmitted, and outputs the extracted radio resource portion to the demodulation unit 110.

[0050] The demodulation unit 110 demodulates the uplink control signal (for example, PUCCH) input from the extraction unit 109, based on, for example, information input from the control unit 101. The demodulation unit 110 outputs the demodulation result to the decoding unit 111, for example.

[0051] The decoding unit 111 performs error correction decoding on an uplink control signal (for example, PUCCH) based on, for example, information input from the control unit 101 and a demodulation result input from the demodulation unit 110, and obtains a decoded received bit sequence (for example, UCI). Here, for example, when UCIs with different priorities are multiplexed, the decoding unit 111 may determine the coding method (for example, joint coding or separate coding) of the UCIs with different priorities based on a method described later, and perform error correction decoding on the PUCCH.

[0052] [Device configuration] 4 is a block diagram illustrating a configuration example of a terminal 200 according to an embodiment of the present disclosure. For example, in FIG. 4, the terminal 200 includes a receiving unit 201, an extracting unit 202, a demodulating unit 203, a decoding unit 204, a control unit 205, an encoding unit 206, a modulating unit 207, a signal allocating unit 208, and a transmitting unit 209.

[0053] The receiver 201 receives, for example, a downlink signal (for example, a downlink data signal or downlink control information) from the base station 100 via an antenna, and performs RF processing such as downconvert or A / D conversion on the radio received signal to obtain a received signal (baseband signal). When receiving an OFDM signal, the receiver 201 performs FFT processing on the received signal to convert the received signal into the frequency domain. The receiver 201 outputs the received signal to the extractor 202.

[0054] For example, based on information relating to the radio resource of the downlink control information input from the control unit 205, the extraction unit 202 extracts a radio resource portion that may include downlink control information from the received signal input from the receiving unit 201, and outputs the extracted radio resource portion to the demodulation unit 203. Furthermore, based on information relating to the radio resource of the data signal input from the control unit 205, the extraction unit 202 extracts a radio resource portion that includes downlink data, and outputs the extracted radio resource portion to the demodulation unit 203.

[0055] Demodulation section 203 demodulates the signal (for example, PDCCH or PDSCH) input from extraction section 202 based on information input from control section 205, for example, and outputs the demodulation result to decoding section 204.

[0056] The decoding unit 204 performs error correction decoding of the PDCCH or PDSCH using, for example, the demodulation result input from the demodulation unit 203, and obtains, for example, downlink reception data, an upper layer control signal, or downlink control information. The decoding unit 204 outputs the upper layer control signal and the downlink control information to the control unit 205, and outputs the downlink reception data. The decoding unit 204 may also generate a response signal (for example, ACK / NACK) based on the decoding result of the downlink reception data, and output the response signal to the coding unit 206.

[0057] The control unit 205 determines radio resources for PDSCH reception or PUCCH transmission, for example, based on a signal (for example, an upper layer control signal or downlink control information) input from the decoding unit 204. The control unit 205 outputs the determined information to the extraction unit 202 and the signal allocation unit 208, for example.

[0058] Control unit 205 may determine a UCI coding method, a UCI mapping method to a PUCCH, a PUCCH format after UCI multiplexing, and parameters corresponding thereto, based on information related to UCI transmission by terminal 200, which is obtained from, for example, a higher layer control signal or downlink control information. Control unit 205 outputs the determined information to, for example, coding unit 206, modulation unit 207, and signal allocation unit 208.

[0059] Encoding section 206 performs error correction coding on UCI (e.g., a UCI sequence) based on, for example, information input from control section 205 (e.g., a UCI coding method, a UCI mapping method to PUCCH, a PUCCH format after UCI multiplexing, and parameters corresponding thereto). Encoding section 206 outputs the coded bit string to modulation section 207. Furthermore, when multiplexing UCIs with different priorities, for example, encoding section 206 may determine the coding method (e.g., either joint coding or separate coding) for the UCIs with different priorities based on a method described later and perform error correction coding.

[0060] For example, the modulation unit 207 modulates the coded bit sequence input from the coding unit 206 and outputs the modulated signal (symbol sequence) to the signal allocation unit 208. For example, when coded bit sequences to which different coding methods (e.g., separate coding) are applied are input, the modulation unit 207 may perform modulation processing on each coded bit sequence.

[0061] The signal allocation unit 208 maps the signal input from the modulation unit 207 to a radio resource (e.g., a PUCCH radio resource) based on, for example, information input from the control unit 205, and outputs the uplink signal to which the signal is mapped to the transmission unit 209.

[0062] Transmitting unit 209 generates a transmission signal waveform, such as OFDM, for the signal input from signal allocating unit 208. Furthermore, in the case of OFDM transmission using a CP, for example, transmitting unit 209 performs IFFT processing on the signal and adds a CP to the signal after IFFT. Alternatively, when transmitting unit 209 generates a single-carrier waveform, a Discrete Fourier Transform (DFT) unit may be added (not shown) after modulating unit 207 or before signal allocating unit 208, for example. Furthermore, transmitting unit 209 performs RF processing, such as D / A conversion and up-conversion, on the transmission signal, and transmits the radio signal to base station 100 via an antenna.

[0063] [Example of Operation of Base Station 100 and Terminal 200] An example of the operation of base station 100 and terminal 200 having the above configuration will be described.

[0064] In this embodiment, as an example of UCI multiplexing, a case where a high priority HARQ-ACK (HP HARQ-ACK) and a low priority HARQ-ACK (LP HARQ-ACK) are multiplexed in the same PUCCH will be described.

[0065] For example, as shown in Fig. 5, cases will be explained according to the number of bits of the high priority HARQ-ACK and the number of bits of the low priority HARQ-ACK. In the example shown in Fig. 5, the high priority HARQ-ACK and the low priority HARQ-ACK are each divided into nine cases (Case 1-1 to Case 3-3): a case where the number of bits (e.g., HARQ-ACK payload size) is 2 bits or less, a case where the number of bits is 3 bits or more and 11 bits or less, and a case where the number of bits is 12 bits or more.

[0066] 5, HARQ-ACK bundling may be applied to both or either of the high priority HARQ-ACK and the low priority HARQ-ACK. When HARQ-ACK bundling is applied, the number of bits of each of the high priority HARQ-ACK and the low priority HARQ-ACK may be the number of bits before HARQ-ACK bundling or the number of bits after HARQ-ACK bundling. Alternatively, the number of bits for the high priority HARQ-ACK may be the number of bits before HARQ-ACK bundling, and the number of bits for the low priority HARQ-ACK may be the number of bits after HARQ-ACK bundling. Alternatively, the number of bits for the high priority HARQ-ACK may be the number of bits after HARQ-ACK bundling, and the number of bits for the low priority HARQ-ACK may be the number of bits before HARQ-ACK bundling.

[0067] Below, examples of UCI transmission methods in each of the cases (Case 1-1 to Case 3-3) shown in FIG. 5 will be described.

[0068] [Case 1-1] Case 1-1 is a case where the number of high-priority HARQ-ACK bits is 2 bits or less and the number of low-priority HARQ-ACK bits is 2 bits or less.

[0069] In Case 1-1, the PUCCH format for each HARQ-ACK before multiplexing is PUCCH format 0 or PUCCH format 1. Furthermore, the number of HARQ-ACK bits after multiplexing is 2 to 4 bits.

[0070] In Case 1-1, the number of bits after multiplexing is smaller than in other cases, so application of joint coding is effective. Also, in Case 1-1, the PUCCH format may be set according to the number of bits after multiplexing.

[0071] Below, Option 1-1-1 and Option 1-1-2 will be described as examples of UCI transmission methods in Case 1-1.

[0072] <option 1-1-1> When the total number of bits of the high priority HARQ-ACK and the low priority HARQ-ACK is 2 bits or less (for example, when the number of bits of the high priority HARQ-ACK and the number of bits of the low priority HARQ-ACK are both 1 bit), terminal 200 may multiplex and transmit the high priority HARQ-ACK and the low priority HARQ-ACK using PUCCH format 0 or PUCCH format 1. In other words, when the total number of bits is 2 bits or less, terminal 200 may perform joint coding using PUCCH format 0 or PUCCH format 1.

[0073] Furthermore, as the PUCCH resource for multiplexing a plurality of HARQ-ACKs, for example, the PUCCH resource (or PUCCH resource set) for the high priority HARQ-ACK may be used.

[0074] Furthermore, when the total number of bits of the high priority HARQ-ACK and the low priority HARQ-ACK is 3 or more (for example, when either or both of the number of bits of the high priority HARQ-ACK or the number of bits of the low priority HARQ-ACK is 2 bits), terminal 200 may multiplex and transmit the high priority HARQ-ACK and the low priority HARQ-ACK using PUCCH format 2, 3, or 4. In other words, when the total number of bits is 3 or more, terminal 200 may perform joint coding using PUCCH format 2, 3, or 4.

[0075] Furthermore, when the total number of bits is 3 or more, for example, terminal 200 may jointly code the high-priority HARQ-ACK and the low-priority HARQ-ACK using a block code (for example, an RM code). Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, the PUCCH resource (or a PUCCH resource set) for the high-priority HARQ-ACK may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Document 2 or 3).

[0076] The coding method, resource mapping, and PUCCH format selection method in Option 1-1-1 are the same as the methods used when multiplexing HARQ-ACKs of the same priority in NR Rel. 15 / 16, for example, and therefore have the advantage of simplifying implementation in terminal 200.

[0077] < / option> <option 1-1-2> When the total number of bits of the high priority HARQ-ACK and the low priority HARQ-ACK is 2 bits or less (for example, when the number of bits of the high priority HARQ-ACK and the number of bits of the low priority HARQ-ACK are both 1 bit), terminal 200 may multiplex and transmit the high priority HARQ-ACK and the low priority HARQ-ACK using PUCCH format 0 or PUCCH format 1. In other words, when the total number of bits is 2 bits or less, terminal 200 may perform joint coding using PUCCH format 0 or PUCCH format 1.

[0078] Furthermore, as the PUCCH resource for multiplexing a plurality of HARQ-ACKs, for example, the PUCCH resource (or PUCCH resource set) for the high priority HARQ-ACK may be used.

[0079] Furthermore, when the total number of bits for the high priority HARQ-ACK and the low priority HARQ-ACK is 3 bits (for example, when one of the number of high priority HARQ-ACK bits and the number of low priority HARQ-ACK bits is 1 bit and the other is 2 bits), and when the PUCCH resource for the high priority HARQ-ACK is PUCCH format 0, terminal 200 may multiplex and transmit the high priority HARQ-ACK and the low priority HARQ-ACK using PUCCH format 0. In other words, terminal 200 may perform joint coding using PUCCH format 0.

[0080] Furthermore, when the total number of bits for the high priority HARQ-ACK and the low priority HARQ-ACK is 3 bits (for example, when one of the number of bits for the high priority HARQ-ACK and the number of bits for the low priority HARQ-ACK is 1 bit and the other is 2 bits), and when the PUCCH resource for the high priority HARQ-ACK is PUCCH format 1, or when the total number of bits for the high priority HARQ-ACK and the low priority HARQ-ACK is 4 bits, terminal 200 may multiplex and transmit the high priority HARQ-ACK and the low priority HARQ-ACK using PUCCH format 2, 3, or 4. In other words, terminal 200 may perform joint coding using PUCCH format 2, 3, or 4.

[0081] When the total number of bits is 3 bits and the PUCCH resource for the high-priority HARQ-ACK is PUCCH format 1, or when the total number of bits is 4 bits, for example, terminal 200 may perform joint coding on the high-priority HARQ-ACK and the low-priority HARQ-ACK using a block code (for example, an RM code). Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, the PUCCH resource (or a PUCCH resource set) for the high-priority HARQ-ACK may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Document 2 or 3).

[0082] Here, NR specifies a method of multiplexing and transmitting an SR without changing the PUCCH format when terminal 200 transmits an HARQ-ACK using PUCCH format 0 (see, for example, Non-Patent Document 3). For example, terminal 200 can transmit information (for example, information indicating eight patterns) including a 2-bit HARQ-ACK and a 1-bit SR (for example, information indicating the presence or absence of an SR) using eight cyclic shift sequences. In Option 1-1-2, for example, when the total number of bits of the high-priority HARQ-ACK and the low-priority HARQ-ACK is 3 bits and the PUCCH resource for the high-priority HARQ-ACK is PUCCH format 0, terminal 200 may transmit a total of 3-bit HARQ-ACK using eight cyclic shift sequences, similar to the method of multiplexing an HARQ-ACK and an SR in NR.

[0083] In Option 1-1-2, for example, if the total number of bits is 3 and the PUCCH resource for the high-priority HARQ-ACK is PUCCH format 0, there is no need to change the PUCCH format for the high-priority HARQ-ACK. For example, transmission using PUCCH format 0 is a one-resource block transmission, and therefore resource utilization efficiency can be improved compared to PUCCH format 2 or 3.

[0084] Note that Option 1-1-2 has described a case in which, when the number of bits after UCI multiplexing is 3 and the PUCCH resource for the high priority HARQ-ACK is PUCCH format 0, terminal 200 multiplexes and transmits the high priority HARQ-ACK and the low priority HARQ-ACK using PUCCH format 0. Similarly, for example, when the number of bits after UCI multiplexing is 3 and the PUCCH resource for the high priority HARQ-ACK is PUCCH format 1, terminal 200 may multiplex and transmit the high priority HARQ-ACK and the low priority HARQ-ACK using PUCCH format 1. In this case, by setting the modulation scheme applied to PUCCH format 1 to 8PSK (8-Phase Shift Keying), terminal 200 can transmit 3 bits of UCI using PUCCH format 1.

[0085] [Case 1-2] Case 1-2 is a case where the number of bits of the high priority HARQ-ACK is 2 bits or less, and the number of bits of the low priority HARQ-ACK is 3 bits or more and 11 bits or less.

[0086] In Case 1-2, the PUCCH format for the high-priority HARQ-ACK before multiplexing is PUCCH format 0 or PUCCH format 1. On the other hand, the PUCCH format for the low-priority HARQ-ACK before multiplexing is PUCCH format 2, 3, or 4.

[0087] Furthermore, the number of HARQ-ACK bits after multiplexing is 4 to 13. Therefore, in Case 1-2, PUCCH format 2, 3, or 4 may be set as the PUCCH format for multiplexing HARQ-ACK.

[0088] In addition, in the case of Case 1-2, there is room for further consideration regarding the encoding method and resource mapping method. Below, Option 1-2-1 and Option 1-2-2 will be described as examples of UCI transmission methods in Case 1-2.

[0089] < / option> <option 1-2-1> For example, terminal 200 may perform joint coding on the high priority HARQ-ACK and the low priority HARQ-ACK, multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0090] Furthermore, when the total number of bits of the high priority HARQ-ACK and the low priority HARQ-ACK is 11 bits or less, terminal 200 may, for example, jointly code the multiplexed HARQ-ACK using a block code (RM code). On the other hand, when the total number of bits is 12 bits or more, terminal 200 may, for example, jointly code the multiplexed HARQ-ACK using a polar code.

[0091] Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, a PUCCH resource (or a PUCCH resource set) for high-priority HARQ-ACKs may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Document 2 or 3).

[0092] The coding method and resource mapping in Option 1-2-1 are the same as the method used when multiplexing HARQ-ACKs of the same priority in NR Rel. 15 / 16, for example, and therefore have the advantage of simplifying the implementation of terminal 200.

[0093] < / option> <option 1-2-2> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0094] Furthermore, terminal 200 may, for example, encode the low-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources based on a method similar to that of NR Rel. 15 / 16 (see, for example, Non-Patent Documents 2 and 3).

[0095] Furthermore, terminal 200 may, for example, puncture the high-priority HARQ-ACK into a portion of the resources to which the low-priority HARQ-ACK is mapped, and map the high-priority HARQ-ACK to a PUCCH resource. Furthermore, terminal 200 may, for example, encode the high-priority HARQ-ACK using a repetition code.

[0096] The amount of resources (for example, the number of resource elements (RE)) to be allocated to 1 or 2 bits of high-priority HARQ-ACK in the PUCCH may be determined, for example, according to the following equation (1).

number

[0097] In formula (1), O ACK indicates the number of high-priority HARQ-ACK bits, coderate indicates the coding rate set for the high-priority HARQ-ACK, and Modulation order indicates the modulation index of PUCCH format 2, 3, or 4.

[0098] In addition, in the PUCCH resource, the high priority HARQ-ACK may be mapped to a resource element (RE) different from the RE to which the reference signal (RS) is mapped, or may be mapped to a symbol closer to the RS symbol, in accordance with the frequency-first-time-second manner.

[0099] The coding method in Option 1-2-2 makes it possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority. Also, in Option 1-2-2, even if separate coding is applied, the number of bits (e.g., 4 to 13 bits) of each of the high-priority HARQ-ACK and the low-priority HARQ-ACK is relatively small, and CRC is unlikely to be added, so that an increase in overhead due to CRC is unlikely to occur.

[0100] In addition, in Option 1-2-2, the resource mapping of the low priority HARQ-ACK is the same as that of NR Rel. 15 / 16, and the high priority HARQ-ACK is punctured and mapped to the PUCCH resource to which the low priority HARQ-ACK is mapped, thereby suppressing an increase in the amount of implementation processing in terminal 200.

[0101] < / option> <option 1-2-3> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0102] Terminal 200 may also encode the high-priority HARQ-ACK using a repetition code and map the encoded UCI bits to PUCCH resources. Terminal 200 may also encode the low-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources.

[0103] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "HARQ-ACK bit," "CSI Part 1," and "CSI Part 2" in NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "HARQ-ACK bit" and "CSI Part 1" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and "CSI Part 2" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resource, the modulation symbol sequence modulating the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, and the high-priority HARQ-ACK bit may be mapped to a symbol closer to the RS symbol. Also, for example, in the PUCCH resource, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped. In other words, the mapping to REs may be such that the high-priority HARQ-ACK bits are mapped first, and then the low-priority HARQ-ACK bits are mapped to the remaining PUCCH resources.

[0104] The coding method in Option 1-2-3 makes it possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority. Also, in Option 1-2-3, even if separate coding is applied, the number of bits (e.g., 4 to 13 bits) of each of the high-priority HARQ-ACK and the low-priority HARQ-ACK is relatively small, and CRC is unlikely to be added, so that an increase in overhead due to CRC is unlikely to occur.

[0105] Furthermore, for resource mapping in Option 1-2-3, the resource mapping method for PUCCH (for example, HARQ-ACK and CSI) of NR Rel. 15 / 16 can be used, so that an increase in the amount of implementation processing in terminal 200 can be suppressed.

[0106] [Cases 1-3] Case 1-3 is a case where the number of bits of the high priority HARQ-ACK is 2 bits or less and the number of bits of the low priority HARQ-ACK is 12 bits or more.

[0107] In Cases 1-3, the PUCCH format for the high-priority HARQ-ACK before multiplexing is PUCCH format 0 or PUCCH format 1. Meanwhile, the PUCCH format for the low-priority HARQ-ACK before multiplexing is PUCCH format 2, 3, or 4.

[0108] Furthermore, the number of HARQ-ACK bits after multiplexing is equal to or greater than 13. Therefore, in Cases 1-3, PUCCH format 2, 3, or 4 may be set as the PUCCH format for multiplexing HARQ-ACK.

[0109] In addition, in the case of Case 1-3, there is room for further consideration regarding the encoding method and resource mapping method. Below, Option 1-3-1 and Option 1-3-2 will be described as examples of UCI transmission methods in Case 1-3.

[0110] < / option> <option 1-3-1> Terminal 200 may, for example, jointly code the high priority HARQ-ACK and the low priority HARQ-ACK, multiplex them using PUCCH format 2, 3, or 4, and transmit them. Terminal 200 may also jointly code the multiplexed HARQ-ACK using a polar code, for example.

[0111] Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, a PUCCH resource (or a PUCCH resource set) for high-priority HARQ-ACKs may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Document 2 or 3).

[0112] The coding method and resource mapping in Option 1-3-1 are the same as the method used when multiplexing HARQ-ACKs of the same priority in NR Rel. 15 / 16, for example, and therefore have the advantage of simplifying implementation in terminal 200.

[0113] < / option> <option 1-3-2> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0114] Furthermore, terminal 200 may, for example, encode the low-priority HARQ-ACK using a polar code and map the encoded HARQ-ACK bits to PUCCH resources based on a method similar to the NR Rel. 15 / 16 method (see, for example, Non-Patent Documents 2 and 3).

[0115] Furthermore, terminal 200 may, for example, puncture the high-priority HARQ-ACK into a portion of the resources to which the low-priority HARQ-ACK is mapped, and map the high-priority HARQ-ACK to a PUCCH resource. Furthermore, terminal 200 may, for example, encode the high-priority HARQ-ACK using a repetition code.

[0116] The amount of resources (for example, the number of REs) to be allocated to 1 or 2 bits of high-priority HARQ-ACK in the PUCCH may be determined, for example, according to the following equation (2).

number

[0117] In formula (2), O ACK indicates the number of high-priority HARQ-ACK bits, coderate indicates the coding rate set for the high-priority HARQ-ACK, and Modulation order indicates the modulation index of PUCCH format 2, 3, or 4.

[0118] Furthermore, in the PUCCH resource, the high priority HARQ-ACK may be mapped to a RE different from the RE to which the RS is mapped, or may be mapped to a symbol closer to the RS symbol, according to the Frequency-first-time-second manner.

[0119] The coding method in Option 1-3-2 makes it possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority. Also, in Option 1-3-2, even if separate coding is applied, the number of bits (e.g., 4 to 13 bits) of each of the high-priority HARQ-ACK and the low-priority HARQ-ACK is relatively small, and CRC is unlikely to be added, so that an increase in overhead due to CRC is unlikely to occur.

[0120] In addition, in Option 1-3-2, the resource mapping of the low priority HARQ-ACK is the same as that of NR Rel. 15 / 16, and the high priority HARQ-ACK is punctured and mapped to the PUCCH resource to which the low priority HARQ-ACK is mapped, thereby suppressing an increase in the amount of implementation processing in terminal 200.

[0121] < / option> <option 1-3-3> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0122] Terminal 200 may also encode the high-priority HARQ-ACK using a repetition code and map the encoded UCI bits to PUCCH resources. Terminal 200 may also encode the low-priority HARQ-ACK using a polar code and map the encoded UCI bits to PUCCH resources.

[0123] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "HARQ-ACK bit," "CSI Part 1," and "CSI Part 2" in NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "HARQ-ACK bit" and "CSI Part 1" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and "CSI Part 2" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resource, the modulation symbol sequence modulating the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, and the high-priority HARQ-ACK bit may be mapped to a symbol closer to the RS symbol. Also, for example, in the PUCCH resource, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped. In other words, the mapping to REs may be such that the high-priority HARQ-ACK bits are mapped first, and then the low-priority HARQ-ACK bits are mapped to the remaining PUCCH resources.

[0124] The coding method in Option 1-3-3 makes it possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority. Also, in Option 1-3-3, even if separate coding is applied, the number of bits (e.g., 4 to 13 bits) of the high-priority HARQ-ACK is relatively small, and CRC is unlikely to be added, so that an increase in overhead due to CRC is unlikely to occur.

[0125] Furthermore, for resource mapping in Option 1-3-3, the resource mapping method for PUCCH (for example, HARQ-ACK and CSI) of NR Rel. 15 / 16 can be used, so that an increase in the amount of implementation processing in terminal 200 can be suppressed.

[0126] [Case 2-1] Case 2-1 is a case where the number of bits of the high priority HARQ-ACK is 3 bits or more and 11 bits or less, and the number of bits of the low priority HARQ-ACK is 2 bits or less.

[0127] In Case 2-1, the PUCCH format for the high-priority HARQ-ACK before multiplexing is PUCCH format 2, 3, or 4. On the other hand, the PUCCH format for the low-priority HARQ-ACK before multiplexing is PUCCH format 0 or PUCCH format 1.

[0128] Furthermore, the number of HARQ-ACK bits after multiplexing is 4 to 13. Therefore, in Case 2-1, PUCCH format 2, 3, or 4 may be set as the PUCCH format used for multiplexing HARQ-ACK.

[0129] In addition, in the case of Case 2-1, there is room for further consideration regarding the encoding method and resource mapping method. Below, Option 2-1-1, Option 2-1-2, and Option 2-1-3 will be described as examples of UCI transmission methods in Case 2-1.

[0130] < / option> <option 2-1-1> For example, terminal 200 may perform joint coding on the high priority HARQ-ACK and the low priority HARQ-ACK, multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0131] Furthermore, when the total number of bits of the high priority HARQ-ACK and the low priority HARQ-ACK is 11 bits or less, terminal 200 may, for example, jointly code the multiplexed HARQ-ACK using a block code (RM code). On the other hand, when the total number of bits is 12 bits or more, terminal 200 may, for example, jointly code the multiplexed HARQ-ACK using a polar code.

[0132] Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, a PUCCH resource (or a PUCCH resource set) for high-priority HARQ-ACKs may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Document 2 or 3).

[0133] The coding method and resource mapping in Option 2-1-1 are the same as the method used when multiplexing HARQ-ACKs of the same priority in NR Rel. 15 / 16, for example, and therefore have the advantage of simplifying implementation in terminal 200.

[0134] < / option> <option 2-1-2> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0135] Furthermore, terminal 200 may encode the high-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources. The amount of resources (e.g., the number of REs) to be allocated to the high-priority HARQ-ACK in the PUCCH may be determined, for example, according to the following equation (3).

number

[0136] In formula (3), O ACK indicates the number of high-priority HARQ-ACK bits, coderate indicates the coding rate set for the high-priority HARQ-ACK, and Modulation order indicates the modulation index of PUCCH format 2, 3, or 4.

[0137] Furthermore, terminal 200 may encode the low priority HARQ-ACK using a repetition code, and map the encoded UCI bits to a PUCCH resource, for example.

[0138] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "UCI bit" and the "UL-SCH" in the PUSCH of NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "UCI bit" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and the "UL-SCH" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resources, the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, or may be mapped to a symbol closer to the RS symbol. Also, in the PUCCH resources, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped.

[0139] The coding method in Option 2-1-2 makes it possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority. Also, in Option 2-1-2, even if separate coding is applied, the number of bits (e.g., 4 to 13 bits) of each of the high-priority HARQ-ACK and the low-priority HARQ-ACK is relatively small, so that CRC is unlikely to be added, and therefore overhead due to CRC is unlikely to increase.

[0140] < / option> <option 2-1-3> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0141] Terminal 200 may also encode the high-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources. Terminal 200 may also encode the low-priority HARQ-ACK using a repetition code and map the encoded UCI bits to PUCCH resources.

[0142] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "HARQ-ACK bit," "CSI Part 1," and "CSI Part 2" in NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "HARQ-ACK bit" and "CSI Part 1" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and "CSI Part 2" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resource, the modulation symbol sequence modulating the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, and the high-priority HARQ-ACK bit may be mapped to a symbol closer to the RS symbol. Also, for example, in the PUCCH resource, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped. In other words, the mapping to REs may be such that the high-priority HARQ-ACK bits are mapped first, and then the low-priority HARQ-ACK bits are mapped to the remaining PUCCH resources.

[0143] The coding method in Option 2-1-3 makes it possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority. Also, in Option 2-1-3, even if separate coding is applied, the number of bits (e.g., 4 to 13 bits) for each of the high-priority HARQ-ACK and the low-priority HARQ-ACK is relatively small, and CRC is unlikely to be added, so that an increase in overhead due to CRC is unlikely to occur.

[0144] Furthermore, for resource mapping in Option 2-1-3, the resource mapping method for PUCCH (for example, HARQ-ACK and CSI) of NR Rel. 15 / 16 can be used, so that an increase in the amount of implementation processing in terminal 200 can be suppressed.

[0145] [Case 2-2] Case 2-2 is a case where the number of bits of the high priority HARQ-ACK is 3 or more and 11 or less, and the number of bits of the low priority HARQ-ACK is 3 or more and 11 or less.

[0146] In Case 2-2, the PUCCH format for the high priority HARQ-ACK and low priority HARQ-ACK before multiplexing is PUCCH format 2, 3, or 4.

[0147] Furthermore, the number of HARQ-ACK bits after multiplexing is 6 to 22. Therefore, in Case 2-2, PUCCH format 2, 3, or 4 may be set as the PUCCH format used for multiplexing HARQ-ACK.

[0148] In addition, in the case of Case 2-2, there is room for further consideration regarding the encoding method and resource mapping method. Below, Option 2-2-1, Option 2-2-2, and Option 2-2-3 will be described as examples of UCI transmission methods in Case 2-2.

[0149] < / option> <option 2-2-1> For example, terminal 200 may perform joint coding on the high priority HARQ-ACK and the low priority HARQ-ACK, multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0150] Furthermore, when the total number of bits of the high priority HARQ-ACK and the low priority HARQ-ACK is 11 bits or less, terminal 200 may, for example, jointly code the multiplexed HARQ-ACK using a block code (RM code). On the other hand, when the total number of bits is 12 bits or more, terminal 200 may, for example, jointly code the multiplexed HARQ-ACK using a polar code.

[0151] Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, a PUCCH resource (or a PUCCH resource set) for high-priority HARQ-ACKs may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Documents 2 and 3).

[0152] The coding method and resource mapping in Option 2-2-1 are the same as the method used when multiplexing HARQ-ACKs of the same priority in NR Rel. 15 / 16, for example, and therefore have the advantage of simplifying implementation in terminal 200.

[0153] < / option> <option 2-2-2> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0154] Furthermore, terminal 200 may encode the high-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources. The amount of resources (e.g., the number of REs) to be allocated to the high-priority HARQ-ACK in the PUCCH may be determined according to, for example, the following equation (4).

number

[0155] In formula (4), O ACK indicates the number of high-priority HARQ-ACK bits, coderate indicates the coding rate set for the high-priority HARQ-ACK, and Modulation order indicates the modulation index of PUCCH format 2, 3, or 4.

[0156] Furthermore, terminal 200 may encode the low priority HARQ-ACK using a block code (for example, an RM code) and map the encoded UCI bits to a PUCCH resource, for example.

[0157] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "UCI bit" and the "UL-SCH" in the PUSCH of NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "UCI bit" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and the "UL-SCH" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resources, the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, or may be mapped to a symbol closer to the RS symbol. Also, in the PUCCH resources, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped.

[0158] The coding method in Option 2-2-2 makes it possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority. Also, in Option 2-2-2, even if separate coding is applied, the number of bits (e.g., 6 to 22 bits) for each of the high-priority HARQ-ACK and the low-priority HARQ-ACK is relatively small, and CRC is unlikely to be added, so that an increase in overhead due to CRC is unlikely to occur.

[0159] < / option> <option 2-2-3> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0160] Terminal 200 may also encode the high-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources. Terminal 200 may also encode the low-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources.

[0161] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "HARQ-ACK bit," "CSI Part 1," and "CSI Part 2" in NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "HARQ-ACK bit" and "CSI Part 1" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and "CSI Part 2" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resource, the modulation symbol sequence modulating the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, and the high-priority HARQ-ACK bit may be mapped to a symbol closer to the RS symbol. Also, for example, in the PUCCH resource, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped. In other words, the mapping to REs may be such that the high-priority HARQ-ACK bits are mapped first, and then the low-priority HARQ-ACK bits are mapped to the remaining PUCCH resources.

[0162] The coding method in Option 2-2-3 makes it possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority. Also, in Option 2-2-3, even if separate coding is applied, the number of bits (e.g., 6 to 22 bits) for each of the high-priority HARQ-ACK and the low-priority HARQ-ACK is relatively small, and CRC is unlikely to be added, so that an increase in overhead due to CRC is unlikely to occur.

[0163] Furthermore, for resource mapping in Option 2-2-3, the resource mapping method for PUCCH (for example, HARQ-ACK and CSI) of NR Rel. 15 / 16 can be used, so that an increase in the amount of implementation processing in terminal 200 can be suppressed.

[0164] [Case 2-3] Case 2-3 is a case where the number of bits of the high priority HARQ-ACK is 3 bits or more and 11 bits or less, and the number of bits of the low priority HARQ-ACK is 12 bits or more.

[0165] In Case 2-3, the PUCCH format for the high priority HARQ-ACK and low priority HARQ-ACK before multiplexing is PUCCH format 2, 3 or 4.

[0166] Furthermore, the number of HARQ-ACK bits after multiplexing is equal to or greater than 15. Therefore, in Case 2-3, PUCCH format 2, 3, or 4 may be set as the PUCCH format used for multiplexing HARQ-ACK.

[0167] In addition, in the case of Case 2-3, there is room for further consideration regarding the encoding method and resource mapping method. Below, Option 2-3-1, Option 2-3-2, and Option 2-3-3 will be described as examples of UCI transmission methods in Case 2-3.

[0168] < / option> <option 2-3-1> For example, terminal 200 may perform joint coding on the high priority HARQ-ACK and the low priority HARQ-ACK, multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0169] Furthermore, terminal 200 may perform joint coding on the multiplexed HARQ-ACK using polar codes, for example.

[0170] Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, a PUCCH resource (or a PUCCH resource set) for high-priority HARQ-ACKs may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Documents 2 and 3).

[0171] The coding method and resource mapping in Option 2-3-1 are the same as the method used when multiplexing HARQ-ACKs of the same priority in NR Rel. 15 / 16, for example, and therefore have the advantage of simplifying implementation in terminal 200.

[0172] < / option> <option 2-3-2> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0173] Furthermore, terminal 200 may encode the high-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources. The amount of resources (e.g., the number of REs) to be allocated to the high-priority HARQ-ACK in the PUCCH may be determined according to, for example, the following equation (5).

number

[0174] In equation (5), O ACK indicates the number of high-priority HARQ-ACK bits, coderate indicates the coding rate set for the high-priority HARQ-ACK, and Modulation order indicates the modulation index of PUCCH format 2, 3, or 4.

[0175] Furthermore, terminal 200 may encode the low priority HARQ-ACK using a polar code, and map the encoded UCI bits to a PUCCH resource, for example.

[0176] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "UCI bit" and the "UL-SCH" in the PUSCH of NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "UCI bit" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and the "UL-SCH" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resources, the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, or may be mapped to a symbol closer to the RS symbol. Also, in the PUCCH resources, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped.

[0177] The coding method in Option 2-3-2 allows for setting appropriate coding rates or resource allocation for each HARQ-ACK with different priorities. Also, in Option 2-3-2, even if separate coding is applied, the number of bits for high-priority HARQ-ACK is relatively small and CRC is unlikely to be added, so that overhead due to CRC is unlikely to increase.

[0178] < / option> <option 2-3-3> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0179] Terminal 200 may also encode the high-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources. Terminal 200 may also encode the low-priority HARQ-ACK using a polar code and map the encoded UCI bits to PUCCH resources.

[0180] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "HARQ-ACK bit," "CSI Part 1," and "CSI Part 2" in NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "HARQ-ACK bit" and "CSI Part 1" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and "CSI Part 2" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resource, the modulation symbol sequence modulating the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, and the high-priority HARQ-ACK bit may be mapped to a symbol closer to the RS symbol. Also, for example, in the PUCCH resource, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped. In other words, the mapping to REs may be such that the high-priority HARQ-ACK bits are mapped first, and then the low-priority HARQ-ACK bits are mapped to the remaining PUCCH resources.

[0181] The coding method in Option 2-3-3 allows for setting appropriate coding rates or resource allocation for each HARQ-ACK with different priorities. Also, in Option 2-3-3, even if separate coding is applied, the number of bits for high-priority HARQ-ACK is relatively small and CRC is unlikely to be added, so overhead due to CRC is unlikely to increase.

[0182] Furthermore, for resource mapping in Option 2-3-3, the resource mapping method for PUCCH (for example, HARQ-ACK and CSI) of NR Rel. 15 / 16 can be used, so that an increase in the amount of implementation processing in terminal 200 can be suppressed.

[0183] [Case 3-1] Case 3-1 is a case where the number of high-priority HARQ-ACK bits is 12 bits or more and the number of low-priority HARQ-ACK bits is 2 bits or less.

[0184] In Case 3-1, the PUCCH format for the high-priority HARQ-ACK before multiplexing is PUCCH format 2, 3, or 4. On the other hand, the PUCCH format for the low-priority HARQ-ACK before multiplexing is PUCCH format 0 or PUCCH format 1.

[0185] Furthermore, the number of HARQ-ACK bits after multiplexing is equal to or greater than 13. Therefore, in Case 2-1, PUCCH format 2, 3, or 4 may be set as the PUCCH format used for multiplexing HARQ-ACK.

[0186] In addition, in the case of Case 3-1, there is room for further consideration regarding the encoding method and resource mapping method. Below, Option 3-1-1, Option 3-1-2, and Option 3-1-3 will be described as examples of UCI transmission methods in Case 3-1.

[0187] < / option> <option 3-1-1> For example, terminal 200 may perform joint coding on the high priority HARQ-ACK and the low priority HARQ-ACK, multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0188] Furthermore, terminal 200 may perform joint coding on the multiplexed HARQ-ACK using polar codes, for example.

[0189] Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, a PUCCH resource (or a PUCCH resource set) for high-priority HARQ-ACKs may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Document 2 or 3).

[0190] The coding method and resource mapping in Option 3-1-1 are the same as the method used when multiplexing HARQ-ACKs of the same priority in NR Rel. 15 / 16, for example, and therefore have the advantage of simplifying implementation in terminal 200.

[0191] < / option> <option 3-1-2> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0192] Furthermore, terminal 200 may encode the high-priority HARQ-ACK using Polar coding and map the encoded UCI bits to PUCCH resources. The amount of resources (e.g., the number of REs) to be allocated to the high-priority HARQ-ACK in the PUCCH may be determined according to, for example, the following equation (6).

number

[0193] In equation (6), O ACK indicates the number of high-priority HARQ-ACK bits, coderate indicates the coding rate set for the high-priority HARQ-ACK, and Modulation order indicates the modulation index of PUCCH format 2, 3, or 4.

[0194] Furthermore, terminal 200 may encode the low priority HARQ-ACK using a repetition code, and map the encoded UCI bits to a PUCCH resource, for example.

[0195] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "UCI bit" and the "UL-SCH" in the PUSCH of NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "UCI bit" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and the "UL-SCH" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resources, the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, or may be mapped to a symbol closer to the RS symbol. Also, in the PUCCH resources, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped.

[0196] The coding method in Option 3-1-2 allows for setting appropriate coding rates or resource allocation for each HARQ-ACK with different priorities. Also, in Option 3-1-2, even if separate coding is applied, the number of bits for low-priority HARQ-ACK is relatively small and CRC is unlikely to be added, so overhead due to CRC is unlikely to increase.

[0197] < / option> <option 3-1-3> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them into PUCCH format 2, 3, or 4, and transmit them.

[0198] Terminal 200 may also encode the high-priority HARQ-ACK using a polar code and map the encoded UCI bits to PUCCH resources. Terminal 200 may also encode the low-priority HARQ-ACK using a repetition code and map the encoded UCI bits to PUCCH resources.

[0199] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "HARQ-ACK bit," "CSI Part 1," and "CSI Part 2" in NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "HARQ-ACK bit" and "CSI Part 1" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and "CSI Part 2" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resource, the modulation symbol sequence modulating the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, and the high-priority HARQ-ACK bit may be mapped to a symbol closer to the RS symbol. Also, for example, in the PUCCH resource, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped. In other words, the mapping to REs may be such that the high-priority HARQ-ACK bits are mapped first, and then the low-priority HARQ-ACK bits are mapped to the remaining PUCCH resources.

[0200] The coding method in Option 3-1-3 allows for setting appropriate coding rates or resource allocation for each HARQ-ACK with different priorities. Also, in Option 3-1-3, even if separate coding is applied, the number of bits for low-priority HARQ-ACK is relatively small and CRC is unlikely to be added, so overhead due to CRC is unlikely to increase.

[0201] Furthermore, for resource mapping in Option 3-1-3, the resource mapping method for PUCCH (for example, HARQ-ACK and CSI) of NR Rel. 15 / 16 can be used, so that an increase in the amount of implementation processing in terminal 200 can be suppressed.

[0202] [Case 3-2] Case 3-2 is a case where the number of high-priority HARQ-ACK bits is 12 bits or more, and the number of low-priority HARQ-ACK bits is 3 bits or more and 11 bits or less.

[0203] In Case 3-2, the PUCCH format for the high-priority HARQ-ACK and low-priority HARQ-ACK before multiplexing is PUCCH format 2, 3, or 4.

[0204] Furthermore, the number of HARQ-ACK bits after multiplexing is equal to or greater than 15. Therefore, in Case 3-2, PUCCH format 2, 3, or 4 may be set as the PUCCH format used for HARQ-ACK multiplexing.

[0205] In addition, in the case of Case 3-2, there is room for further consideration regarding the encoding method and resource mapping method. Below, Option 3-2-1, Option 3-2-2, and Option 3-2-3 will be described as examples of UCI transmission methods in Case 3-2.

[0206] < / option> <option 3-2-1> For example, terminal 200 may perform joint coding on the high priority HARQ-ACK and the low priority HARQ-ACK, multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0207] Furthermore, terminal 200 may perform joint coding on the multiplexed HARQ-ACK using polar codes, for example.

[0208] Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, a PUCCH resource (or a PUCCH resource set) for high-priority HARQ-ACKs may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Documents 2 and 3).

[0209] The coding method and resource mapping in Option 3-2-1 are the same as the method used when multiplexing HARQ-ACKs of the same priority in NR Rel. 15 / 16, for example, and therefore have the advantage of being easy to implement in terminal 200.

[0210] < / option> <option 3-2-2> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0211] Furthermore, terminal 200 may encode the high-priority HARQ-ACK using Polar coding and map the encoded UCI bits to PUCCH resources. The amount of resources (e.g., the number of REs) to be allocated to the high-priority HARQ-ACK in the PUCCH may be determined, for example, according to the following equation (7).

number

[0212] In equation (7), O ACK indicates the number of high-priority HARQ-ACK bits, coderate indicates the coding rate set for the high-priority HARQ-ACK, and Modulation order indicates the modulation index of PUCCH format 2, 3, or 4.

[0213] Furthermore, terminal 200 may encode the low priority HARQ-ACK using a block code (for example, an RM code) and map the encoded UCI bits to a PUCCH resource, for example.

[0214] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "UCI bit" and the "UL-SCH" in the PUSCH of NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "UCI bit" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and the "UL-SCH" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resources, the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, or may be mapped to a symbol closer to the RS symbol. Also, in the PUCCH resources, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped.

[0215] The coding method in Option 3-2-2 allows for setting appropriate coding rates or resource allocation for each HARQ-ACK with different priorities. Also, in Option 3-2-2, even if separate coding is applied, the number of bits for low-priority HARQ-ACK is relatively small and CRC is unlikely to be added, so overhead due to CRC is unlikely to increase.

[0216] < / option> <option 3-2-3> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0217] Terminal 200 may also encode the high-priority HARQ-ACK using a polar code and map the encoded UCI bits to PUCCH resources. Terminal 200 may also encode the low-priority HARQ-ACK using a block code (e.g., an RM code) and map the encoded UCI bits to PUCCH resources.

[0218] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "HARQ-ACK bit," "CSI Part 1," and "CSI Part 2" in NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "HARQ-ACK bit" and "CSI Part 1" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and "CSI Part 2" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resource, the modulation symbol sequence modulating the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, and the high-priority HARQ-ACK bit may be mapped to a symbol closer to the RS symbol. Also, for example, in the PUCCH resource, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped. In other words, the mapping to REs may be such that the high-priority HARQ-ACK bits are mapped first, and then the low-priority HARQ-ACK bits are mapped to the remaining PUCCH resources.

[0219] The coding method in Option 3-2-3 allows for setting appropriate coding rates or resource allocation for each HARQ-ACK with different priorities. Also, in Option 3-2-3, even if separate coding is applied, the number of bits for low-priority HARQ-ACK is relatively small, so CRC is unlikely to be added, and therefore overhead due to CRC is unlikely to increase.

[0220] Furthermore, for resource mapping in Option 3-2-3, the resource mapping method for PUCCH (for example, HARQ-ACK and CSI) of NR Rel. 15 / 16 can be used, so that an increase in the amount of implementation processing in terminal 200 can be suppressed.

[0221] [Case 3-3] Case 3-3 is a case where the number of bits of the high priority HARQ-ACK is 12 or more, and the number of bits of the low priority HARQ-ACK is 12 or more.

[0222] In Case 3-3, the PUCCH format for the high priority HARQ-ACK and low priority HARQ-ACK before multiplexing is PUCCH format 2, 3, or 4.

[0223] Furthermore, the number of HARQ-ACK bits after multiplexing is equal to or greater than 24. Therefore, in Case 3-3, PUCCH format 2, 3, or 4 may be set as the PUCCH format used for HARQ-ACK multiplexing.

[0224] In addition, in the case of Case 3-3, there is room for further consideration regarding the encoding method and resource mapping method. Below, Option 3-3-1, Option 3-3-2, and Option 3-3-3 will be described as examples of UCI transmission methods in Case 3-3.

[0225] < / option> <option 3-3-1> For example, terminal 200 may perform joint coding on the high priority HARQ-ACK and the low priority HARQ-ACK, multiplex them into PUCCH format 2, 3 or 4, and transmit them.

[0226] Furthermore, terminal 200 may perform joint coding on the multiplexed HARQ-ACK using polar codes, for example.

[0227] Furthermore, for the PUCCH resource for multiplexing multiple HARQ-ACKs, for example, a PUCCH resource (or a PUCCH resource set) for high-priority HARQ-ACKs may be used. Furthermore, the resource mapping method for HARQ-ACK bits to PUCCH resources may be the same as the operation of NR Rel. 15 / 16 (for example, see Non-Patent Documents 2 and 3).

[0228] The coding method and resource mapping in Option 3-3-1 are the same as the method used when multiplexing HARQ-ACKs of the same priority in NR Rel. 15 / 16, for example, and therefore have the advantage of being easy to implement in terminal 200.

[0229] < / option> <option 3-3-2> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0230] Furthermore, terminal 200 may encode the high-priority HARQ-ACK using a polar code and map the encoded UCI bits to PUCCH resources. The amount of resources (e.g., the number of REs) to be allocated to the high-priority HARQ-ACK in the PUCCH may be determined according to, for example, the following equation (8).

number

[0231] In equation (8), O ACK indicates the number of high-priority HARQ-ACK bits, coderate indicates the coding rate set for the high-priority HARQ-ACK, and Modulation order indicates the modulation index of PUCCH format 2, 3, or 4.

[0232] Furthermore, terminal 200 may encode the low priority HARQ-ACK using a polar code, and map the encoded UCI bits to a PUCCH resource, for example.

[0233] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "UCI bit" and the "UL-SCH" in the PUSCH of NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "UCI bit" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and the "UL-SCH" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resources, the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, or may be mapped to a symbol closer to the RS symbol. Also, in the PUCCH resources, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped.

[0234] In the coding method of Option 3-3-2, it is possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority.

[0235] < / option> <option 3-3-3> For example, terminal 200 may encode the high priority HARQ-ACK and the low priority HARQ-ACK independently (for example, by separate coding), multiplex them using PUCCH format 2, 3, or 4, and transmit them.

[0236] Terminal 200 may also encode the high-priority HARQ-ACK using a polar code and map the encoded UCI bits to PUCCH resources. Terminal 200 may also encode the low-priority HARQ-ACK using a polar code and map the encoded UCI bits to PUCCH resources.

[0237] The mapping of the high-priority HARQ-ACK and the low-priority HARQ-ACK to PUCCH resources of PUCCH format 2, 3, or 4 may be performed using a method similar to the mapping relationship between the "HARQ-ACK bit," "CSI Part 1," and "CSI Part 2" in NR Rel.15 / 16 (see, for example, Non-Patent Documents 2 and 3). For example, the "HARQ-ACK bit" and "CSI Part 1" in the mapping method of NR Rel.15 / 16 may be replaced with the "high-priority HARQ-ACK," and "CSI Part 2" in the mapping method of NR Rel.15 / 16 may be replaced with the "low-priority HARQ-ACK." For example, in the PUCCH resource, the modulation symbol sequence modulating the high-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS is mapped according to the frequency-first-time-second format, and the high-priority HARQ-ACK bit may be mapped to a symbol closer to the RS symbol. Also, for example, in the PUCCH resource, the low-priority HARQ-ACK may be mapped to an RE different from the RE to which the RS and the high-priority HARQ-ACK are mapped. In other words, the mapping to REs may be such that the high-priority HARQ-ACK bits are mapped first, and then the low-priority HARQ-ACK bits are mapped to the remaining PUCCH resources.

[0238] In the coding method in Option 3-3-3, it is possible to set an appropriate coding rate or resource allocation for each HARQ-ACK with a different priority.

[0239] Furthermore, for resource mapping in Option 2-3-3, the resource mapping method for PUCCH (for example, HARQ-ACK and CSI) of NR Rel. 15 / 16 can be used, so that an increase in the amount of implementation processing in terminal 200 can be suppressed.

[0240] The above describes examples of UCI transmission methods in the cases (Case 1-1 to Case 3-3) shown in FIG.

[0241] In the above example, a case has been described in which the PUCCH resource for a high priority HARQ-ACK is used as the PUCCH resource for multiplexing multiple HARQ-ACKs, but this is not limited to this and other resources may also be used.

[0242] Next, an example of processing in the terminal 200 will be described.

[0243] FIG. 6 is a flowchart showing an example of an operation related to UCI transmission in terminal 200 when transmission of high-priority UCI (for example, HARQ-ACK) and transmission of low-priority UCI (for example, HARQ-ACK) overlap in time.

[0244] 6, terminal 200 acquires information on at least one of high-priority UCI and low-priority UCI (ST101). This information may include, for example, information on the number of UCI bits or the PUCCH resource (or PUCCH format) used to transmit the UCI.

[0245] Terminal 200 determines, for example, the number of bits of the high-priority UCI (ST102). For example, terminal 200 may determine to which of a plurality of groups according to the number of UCI bits the number of bits (or payload size) of the high-priority UCI indicated in the information acquired in the processing of ST101 is classified. For example, in the example of Fig. 6, terminal 200 may determine whether the number of bits of the high-priority UCI is 2 bits or less, 3 bits or more and 11 bits or less, or 12 bits or more.

[0246] Terminal 200 determines, for example, the number of bits of the low-priority UCI (ST103). For example, terminal 200 may determine to which of a plurality of groups according to the number of UCI bits the number of bits (or payload size) of the low-priority UCI indicated in the information acquired in the processing of ST101 is classified. For example, in the example of Fig. 6, terminal 200 may determine whether the number of bits of the low-priority UCI is 2 bits or less, 3 bits or more and 11 bits or less, or 12 bits or more.

[0247] Terminal 200 identifies a combination of the number of bits of the high-priority UCI and the low-priority UCI (for example, any of Case 1-1 to Case 3-3 shown in FIG. 5) based on the determination results of ST102 and ST103 (ST104). Note that the method of identifying the Case is not limited to the method shown in FIG. 6. For example, terminal 200 may identify the Case by determining the number of bits of the high-priority UCI after determining the number of bits of the low-priority UCI, or may identify the Case based on the combination of the number of bits of both the high-priority UCI and the low-priority UCI.

[0248] Terminal 200 multiplexes UCI having different priorities onto a PUCCH based on the identified case and transmits the multiplexed UCI (ST105). For example, terminal 200 may determine at least one of the UCI coding method (e.g., joint coding or separate coding) corresponding to the identified case, the UCI mapping method onto the PUCCH, and the PUCCH format after multiplexing.

[0249] An example of the operation of the terminal 200 has been described above.

[0250] As described above, there are one or more options that can be applied to each case. In this embodiment, for example, the terminal 200 may operate based on a combination of options for each case.

[0251] For example, the combinations of options for each case may be Option 1-1-1, Option 1-2-2, Option 1-3-2, Option 2-1-2, Option 2-2-2, Option 2-3-2, Option 3-1-2, Option 3-2-2, and Option 3-3-1. In these combinations, terminal 200 applies joint coding when the number of bits of the high-priority HARQ-ACK and the low-priority HARQ-ACK are both 2 bits or less, or when the number of bits of the high-priority HARQ-ACK and the low-priority HARQ-ACK are both 12 bits or more (e.g., Case 1-1-1 and Case 3-3-1), and applies separate coding in other cases (e.g., Option 1-2-2, Option 1-3-2, Option 2-1-2, Option 2-2-2, Option 2-3-2, Option 3-1-2, and Option 3-2-2). With this combination, for example, when the number of HARQ-ACK bits is small (e.g., 2 bits or less) and the impact on resource utilization efficiency is small, terminal 200 can apply joint coding, or PUCCH format 0 or PUCCH format 1, which are suitable for transmitting 1 or 2 bits. Also, with this combination, when the number of HARQ-ACK bits is large (e.g., 12 bits or more), terminal 200 can suppress an increase in the number of codes (e.g., the number of polar codes) by applying, for example, one code using joint coding.

[0252] Furthermore, for example, in the above-described example combinations, Option 1-1-2 may be used instead of Option 1-1-1. In this case, terminal 200 can use PUCCH format 0 even when the total number of bits for high-priority HARQ-ACK and low-priority HARQ-ACK is 3, for example.

[0253] Furthermore, for example, in the above-described example combination, Option 2-3-3 may be used instead of Option 2-3-2. In this case, terminal 200 can apply, for example, to low-priority HARQ-ACK, a method of encoding and resource mapping similar to that for CSI Part 2 in Rel.15 / 16, and therefore it is possible to suppress an increase in the amount of processing implemented in terminal 200.

[0254] As another example, the combination of Options for each Case may be Option 1-1-1, Option 1-2-1, Option 1-3-1, Option 2-1-1, Option 2-2-2, Option 2-3-2 or 2-3-3, Option 3-1-1, Option 3-2-2 (or Option 3-2-3), and Option 3-3-2 (or Option 3-3-3). With this combination, terminal 200 applies joint coding when the number of bits of either the high-priority HARQ-ACK or the low-priority HARQ-ACK is 2 bits or less, regardless of the total number of bits of the high-priority HARQ-ACK and the low-priority HARQ-ACK. With this combination example, terminal 200 does not need to use a repetition code that is not optimized for transmission of 1 or 2 bits, and therefore transmission quality can be improved.

[0255] Note that the combination of Options for each Case is not limited to the above-mentioned example, and other combinations may be used. For example, at least one of the HARQ-ACK coding method (e.g., joint coding or separate coding), the HARQ-ACK mapping method to the PUCCH, and the PUCCH format after multiplexing may be controlled according to one or more of the following elements: the number of low-priority HARQ-ACK bits, the number of high-priority HARQ-ACK bits, the total number of bits, the PUCCH format, and restrictions on the number of coding bits.

[0256] As described above, according to the present embodiment, terminal 200 determines parameters to be used for transmitting (e.g., multiplexing) multiple UCIs having different priorities, according to information on the size (e.g., number of bits) of at least one of the multiple UCIs. Through this control, terminal 200 can appropriately set the coding method, PUCCH format, or resource mapping method for multiplexing UCIs, for example, based on the number of bits of each of the multiplexed UCIs or the total number of bits of the multiplexed UCIs. Thus, according to the present embodiment, even when transmissions of UCIs having different priorities overlap in time, it is possible to improve UCI transmission efficiency (e.g., resource utilization efficiency, transmission quality, or ease of implementation of terminal 200).

[0257] (Modification of the first embodiment) For example, a scenario is assumed in which the number of bits of HARQ-ACK for URLLC transmission set to high priority is set to a smaller number of bits in consideration of low latency or high reliability. Therefore, a situation in which transmission of a high-priority HARQ-ACK with a larger number of bits (for example, a value larger than a threshold X described later) overlaps in time with transmission of a low-priority HARQ-ACK is unlikely to occur.

[0258] Therefore, for example, in the first embodiment, the case where HARQ-ACKs having different priorities are multiplexed onto a PUCCH may also be the case where the number of bits of the high-priority HARQ-ACK is equal to or less than threshold X. For example, if the number of bits of the high-priority HARQ-ACK is greater than threshold X, terminal 200 may apply the operation of NR Rel. 16, drop the low-priority HARQ-ACK, and transmit the high-priority HARQ-ACK.

[0259] According to this modification, the implementation of the terminal 200 can be further simplified.

[0260] For example, when the threshold X bits is 2 bits (when X=2), terminal 200 may control UCI multiplexing based on the combination of options for each case in the above-mentioned Cases 1-1, 1-2, and 1-3 (for example, when the high-priority HARQ-ACK is 2 bits or less). On the other hand, when corresponding to a case different from the above cases (in other words, when the high-priority HARQ-ACK is 3 bits or more), terminal 200 may drop the low-priority HARQ-ACK and transmit the high-priority HARQ-ACK.

[0261] Furthermore, for example, when threshold X bits is 11 bits (when X=11), terminal 200 may control UCI multiplexing based on the combination of options for each case in the above-mentioned Case 1-1, Case 1-2, Case 1-3, Case 2-1, Case 2-2, and Case 2-3 (in other words, when the high-priority HARQ-ACK is 11 bits or less).On the other hand, when corresponding to a case different from the above-mentioned cases (in other words, when the high-priority HARQ-ACK is 12 bits or more), terminal 200 may drop the low-priority HARQ-ACK and transmit the high-priority HARQ-ACK.

[0262] The threshold value X is not limited to 2 bits or 11 bits, and may be other values.

[0263] (Embodiment 2) In this embodiment, as an example, a case will be described in which an SR corresponding to a service set to high priority (hereinafter referred to as a "high priority SR") and a HARQ-ACK for a service set to low priority (low priority HARQ-ACK) are multiplexed onto the same PUCCH.

[0264] SR is 1-bit information. Therefore, as shown in Fig. 7, cases will be explained according to the number of bits of low-priority HARQ-ACK. In the example shown in Fig. 7, the low-priority HARQ-ACK is divided into a case where the number of bits (for example, HARQ-ACK payload size) is 2 bits or less (Case 1-1'), a case where the number of bits is 3 bits or more and 11 bits or less (Case 1-2'), and a case where the number of bits is 12 bits or more (Case 1-3').

[0265] Note that HARQ-ACK bundling may be applied to low-priority HARQ-ACKs in Fig. 7. When HARQ-ACK bundling is applied, the number of bits of low-priority HARQ-ACKs may be the number of bits before HARQ-ACK bundling or the number of bits after HARQ-ACK bundling.

[0266] Below, examples of UCI transmission methods in each of the cases (Case 1-1', Case 1-2', and Case 1-3') shown in FIG. 7 will be described.

[0267] [Case 1-1'] Case 1-1' is a case where the number of low-priority HARQ-ACK bits is 2 bits or less.

[0268] In Case 1-1′, the PUCCH format for SR and HARQ-ACK before multiplexing is PUCCH format 0 or PUCCH format 1.

[0269] When a low-priority HARQ-ACK is transmitted using PUCCH format 0, if the PUCCH resource for the low-priority HARQ-ACK overlaps in time with the PUCCH resource set for transmitting a high-priority SR, terminal 200 may multiplex the low-priority HARQ-ACK and the high-priority SR onto the PUCCH resource and transmit the multiplexed PUCCH resource. The PUCCH resource may be determined based on the PUCCH resource allocated for transmitting the low-priority HARQ-ACK, for example. This multiplexing method is similar to the method used when multiplexing an SR and a HARQ-ACK of the same priority in NR Rel. 15 / 16, for example, and therefore has the advantage of simplifying the implementation of terminal 200.

[0270] Furthermore, for example, when the PUCCH resource set for transmitting a high-priority SR is PUCCH format 0 and the PUCCH resource set for transmitting a low-priority HARQ-ACK is PUCCH format 1, if the PUCCH resource for the low-priority HARQ-ACK and the PUCCH resource for the high-priority SR overlap in time, terminal 200 may apply Option 1, Option 2, or Option 3 below.

[0271] < / option> <option 1> In Option 1, terminal 200 does not multiplex SRs and HARQ-ACKs having different priorities (in other words, does not support multiplexing).

[0272] For example, in NR Rel.15, when SR and HARQ-ACK of the same priority are multiplexed, the terminal drops the SR transmission and transmits the HARQ-ACK using the PUCCH assigned to the HARQ-ACK. Also, in NR Rel.16, when SR and HARQ-ACK of different priorities are multiplexed, the terminal drops the HARQ-ACK transmission and transmits the SR using the PUCCH assigned to the SR. From the operation of NR Rel.15 / 16, it can also be understood that multiplexing of high-priority SR and low-priority HARQ-ACK of different priorities does not need to be supported.

[0273] Option 1 is similar to the case where SRs and HARQ-ACKs with different priorities are multiplexed in NR Rel. 16, and therefore has the advantage of being easy to implement in terminal 200.

[0274] < / option> <option 2> In Option 2, terminal 200 varies the cyclic shift sequence applied to symbols that temporally overlap with PUCCH resources for transmitting high-priority SRs among the symbols of PUCCH format 1 that transmit low-priority HARQ-ACKs, depending on whether or not a high-priority SR is present (for example, positive SR or negative SR). Thus, base station 100 can determine whether or not an SR is present (for example, positive SR or negative SR) based on, for example, the cyclic shift sequence applied to a symbol.

[0275] In this way, in Option 2, terminal 200 can multiplex and transmit high-priority SRs on the PUCCH resources of low-priority HARQ-ACKs without dropping the transmission of low-priority HARQ-ACKs. The method of Option 2 can be considered, for example, as a type of joint coding of high-priority SRs and low-priority HARQ-ACKs.

[0276] < / option> <option 3> In Option 3, terminal 200 punctures symbols that temporally overlap with PUCCH resources for transmitting high-priority SRs among symbols of PUCCH format 1 used to transmit low-priority HARQ-ACKs, and multiplexes and transmits PUCCH format 0 for high-priority SRs on the PUCCH resources for low-priority HARQ-ACKs. The method of Option 3 can be considered, for example, as a type of separate coding.

[0277] Option 1, Option 2, and Option 3 have been described above for the case where transmission of a high-priority SR using PUCCH format 0 and transmission of a low-priority HARQ-ACK using PUCCH format 1 overlap in time.

[0278] Next, for example, when the PUCCH resource set for transmitting a high-priority SR is PUCCH format 1 and the PUCCH resource set for transmitting a low-priority HARQ-ACK is PUCCH format 1, if the PUCCH resource for the low-priority HARQ-ACK and the PUCCH resource for the high-priority SR overlap in time, terminal 200 may apply Option 1 or Option 2 below.

[0279] < / option> <option 1> In Option 1, terminal 200 multiplexes a low-priority HARQ-ACK and a high-priority SR into a PUCCH and transmits the multiplexed signal.

[0280] For example, in the case of positive SR (or with SR), terminal 200 may transmit a low-priority HARQ-ACK using a PUCCH resource allocated to a high-priority SR, whereas, for example, in the case of negative SR (or without SR), terminal 200 may transmit a low-priority HARQ-ACK using a PUCCH resource allocated to a low-priority HARQ-ACK.

[0281] Base station 100 may determine whether there is a high-priority SR (positive or negative) based on the PUCCH resource on which the low-priority HARQ-ACK was actually transmitted. For example, base station 100 may determine that there is a positive SR when a low-priority HARQ-ACK is received in a PUCCH resource for a high-priority SR, and may determine that there is a negative SR when a low-priority HARQ-ACK is received in a PUCCH resource for a low-priority HARQ-ACK.

[0282] Option 1 is similar to the method used when multiplexing SR and HARQ-ACK with the same priority in NR Rel.15 / 16, for example, and therefore has the advantage of being easy to implement in terminal 200.

[0283] < / option> <option 2> In Option 1, the PUCCH resource of the low-priority HARQ-ACK may be used for the high-priority SR transmission, which may not satisfy the delay requirement of the high-priority SR. Therefore, in Option 2, for example, terminal 200 may multiplex one bit of the high-priority SR and one bit of the low-priority HARQ-ACK using the PUCCH resource allocated to the high-priority SR.

[0284] For example, terminal 200 may add one bit of HARQ-ACK to one bit indicating the presence or absence of an SR (for example, at the end of the one bit) and transmit a two-bit UCI bit string using PUCCH format 1. For example, if the number of low-priority HARQ-ACK bits is two bits, terminal 200 may apply HARQ-ACK bundling to compress it to one bit and multiplex the compressed HARQ-ACK into the high-priority SR.

[0285] In Option 2, terminal 200 can use the PUCCH resource allocated to the high-priority SR for transmitting the high-priority SR, so that the high-priority SR transmission is less affected by the PUCCH resource of the low-priority HARQ-ACK. Therefore, according to Option 2, it becomes easier to satisfy the delay requirement of the high-priority SR.

[0286] Option 1 and Option 2 have been described above when the transmission of a high-priority SR using PUCCH format 1 and the transmission of a low-priority HARQ-ACK using PUCCH format 1 overlap in time.

[0287] [Case 1-2'] Case 1-2' is a case where the number of low-priority HARQ-ACK bits is 3 bits or more and 11 bits or less.

[0288] In Case 1-2′, the PUCCH format for the high-priority SR before multiplexing is PUCCH format 0 or PUCCH format 1. Meanwhile, the PUCCH format for the low-priority HARQ-ACK before multiplexing is PUCCH format 2, 3, or 4.

[0289] Furthermore, the total number of bits for the high-priority SR and low-priority HARQ-ACK after multiplexing is 4 to 13. Therefore, in Case 1-2′, PUCCH format 2, 3, or 4 may be set as the PUCCH format used for multiplexing SR and HARQ-ACK.

[0290] Furthermore, the coding method and resource mapping method in Case 1-2' can be realized by replacing "high priority HARQ-ACK" in Case 1-2 of the first embodiment with "high priority SR", for example.

[0291] [Case 1-3'] Case 1-3' is a case where the number of low-priority HARQ-ACK bits is 12 bits or more.

[0292] In Cases 1-3′, the PUCCH format for the high-priority SR before multiplexing is PUCCH format 0 or PUCCH format 1. Meanwhile, the PUCCH format for the low-priority HARQ-ACK before multiplexing is PUCCH format 2, 3, or 4.

[0293] Furthermore, the total number of bits for the high-priority SR and low-priority HARQ-ACK after multiplexing is equal to or greater than 13. Therefore, in Cases 1-3′, PUCCH format 2, 3, or 4 may be set as the PUCCH format used for multiplexing SR and HARQ-ACK.

[0294] Furthermore, the coding method and resource mapping method in Cases 1-3' can be realized by replacing "high priority HARQ-ACK" in Cases 1-3 of the first embodiment with "high priority SR", for example.

[0295] In this way, according to the present embodiment, even when transmission of a high priority SR and transmission of a low priority HARQ-ACK overlap in time, terminal 200 can multiplex and transmit the SR and HARQ-ACK in the PUCCH.

[0296] (Embodiment 3) In this embodiment, as an example, a case will be described in which a high-priority SR and a high-priority HARQ-ACK, and a low-priority HARQ-ACK are multiplexed in the same PUCCH.

[0297] In this embodiment, the order of multiplexing these three or more UCIs may be such that terminal 200 first performs multiplexing processing between UCIs having the same priority, and then performs multiplexing processing between UCIs having different priorities.

[0298] For example, terminal 200 may apply a method of multiplexing an SR and HARQ-ACK of the same priority in NR Rel. 15 / 16 to a high-priority SR and a high-priority HARQ-ACK (see, for example, Non-Patent Documents 2 and 3). Next, terminal 200 may perform an operation in which the "high-priority HARQ-ACK" in the above-mentioned first embodiment is replaced with "UCI after multiplexing high-priority SR and high-priority HARQ-ACK." This makes it possible to multiplex UCIs with different priorities, for example, high-priority SR+HARQ-ACK and low-priority HARQ-ACK.

[0299] According to this embodiment, terminal 200 can apply the same multiplexing operation as NR Rel.15 / 16 to multiplexing UCIs having the same priority, and can apply, for example, the HARQ-ACK multiplexing method described in embodiment 1 to multiplexing UCIs having different priorities, which is advantageous in terms of ease of implementation of terminal 200.

[0300] (Fourth embodiment) In this embodiment, as in the third embodiment, a case will be described as an example in which a high-priority SR and a high-priority HARQ-ACK, and a low-priority HARQ-ACK are multiplexed in the same PUCCH.

[0301] In this embodiment, unlike the third embodiment, when multiplexing high-priority SR and high-priority HARQ-ACK, the method of multiplexing SR and HARQ-ACK of the same priority in NR Rel. 15 / 16 is not applied.

[0302] For example, terminal 200 concatenates a high-priority SR bit and a high-priority HARQ-ACK bit. Terminal 200 may then perform an operation in which the "high-priority HARQ-ACK" in the first embodiment described above is replaced with "UCI after concatenation of high-priority SR and high-priority HARQ-ACK." This makes it possible to realize multiplexing of UCIs having different priorities, for example, high-priority SR+HARQ-ACK and low-priority HARQ-ACK.

[0303] In addition, in this embodiment, regardless of whether or not there is an SR (for example, positive SR or negative SR) and whether or not the SR resource and the HARQ-ACK resource overlap in time, a bit for one SR may be reserved for the high-priority HARQ-ACK bit string.

[0304] For example, in the third embodiment, when the PUCCH resource set for transmitting a high-priority SR is PUCCH format 0 and the high-priority HARQ-ACK is transmitted using PUCCH format 1, if the PUCCH resource for the high-priority HARQ-ACK overlaps in time with the PUCCH resource for transmitting the high-priority SR, in multiplexing of SRs and HARQ-ACKs of the same priority in NR Rel.15 / 16, the transmission of the SR is dropped and the HARQ-ACK is transmitted using the PUCCH allocated to the HARQ-ACK. Thus, in the third embodiment, after the high-priority SR is dropped, it is multiplexed with the high-priority UCI and the low-priority HARQ-ACK.

[0305] On the other hand, in this embodiment, terminal 200 can multiplex a high-priority SR and a high-priority HARQ-ACK, while multiplexing a high-priority UCI and a low-priority HARQ-ACK. In other words, in this embodiment, terminal 200 does not need to drop a high-priority SR.

[0306] The above describes the embodiments according to the example of the present disclosure.

[0307] (Other embodiments) (1) In each of the above-described embodiments, for example, as shown in Figures 5 and 6, the operation of terminal 200 corresponding to each of multiple cases (combinations) according to the number of bits of high-priority UCI and low-priority UCI has been described. However, terminal 200 may apply operations corresponding to some of the multiple cases shown in Figures 5 and 6, and may not apply operations corresponding to the remaining cases.

[0308] In other words, it is possible to apply an operation in which at least one of the multiple cases described in each of the above-mentioned embodiments is extracted. For example, as in the modified example of the first embodiment, the terminal 200 may apply operations corresponding to Case 1-1, Case 1-2, and Case 1-3 of the nine cases shown in Figures 5 and 6, and not apply operations corresponding to the other cases. Furthermore, for example, the terminal 200 may apply operations corresponding to Case 1-1, Case 2-2, and Case 3-3 of the nine cases shown in Figures 5 and 6, and not apply operations corresponding to the other cases. Note that the case extracted from the multiple cases described in each of the above-mentioned embodiments is not limited to the above-mentioned examples, and may be any case.

[0309] Similarly, in FIG. 7 of the second embodiment, terminal 200 may apply an operation corresponding to at least one of three cases, Case 1-1′, Case 1-2′, and Case 1-3′, and may not apply other operations.

[0310] (2) In the above-described embodiments, for example, in Fig. 5, the case where terminal 200 controls UCI multiplexing based on the number of bits of both high-priority UCI and low-priority UCI has been described, but this is not limiting. For example, terminal 200 may control UCI multiplexing based on the number of bits of either high-priority UCI or low-priority UCI.

[0311] For example, when based on the number of bits of high-priority UCI, terminal 200 may apply joint coding when the number of bits of high-priority UCI is 2 bits or less, and may apply separate coding when the number of bits of high-priority UCI is 3 bits or more. Alternatively, terminal 200 may apply joint coding when the number of bits of high-priority UCI is 11 bits or less, and may apply separate coding when the number of bits of high-priority UCI is 12 bits or more. Note that, in addition to controlling the coding method such as joint coding and separate coding described above, terminal 200 may also control other operations related to UCI multiplexing (for example, determine parameters corresponding to the PUCCH format or resource mapping method) based on the number of bits of high-priority UCI.

[0312] Similarly, for example, when based on the number of bits of low-priority UCI, terminal 200 may apply joint coding when the number of bits of low-priority UCI is 2 bits or less, and may apply separate coding when the number of bits of low-priority UCI is 3 bits or more. Alternatively, terminal 200 may apply joint coding when the number of bits of low-priority UCI is 11 bits or less, and may apply separate coding when the number of bits of low-priority UCI is 12 bits or more. Note that, in addition to controlling the coding method such as joint coding and separate coding described above, terminal 200 may also control other operations related to UCI multiplexing (for example, determine parameters corresponding to the PUCCH format or resource mapping method) based on the number of bits of low-priority UCI.

[0313] (3) In the above-described embodiments, the number of bits of a UCI is classified into three ranges: 2 bits or less, 3 bits or more and 11 bits or less, and 12 bits or more. However, the ranges into which the number of bits of a UCI is classified are not limited to three. For example, the number of bits of a UCI may be classified into two ranges, or into four or more ranges. Furthermore, for example, the number of ranges into which the number of bits of a high-priority UCI is classified may be different from the number of ranges into which the number of bits of a low-priority UCI is classified.

[0314] Furthermore, for example, as shown in Figure 6 or Figure 8, the case has been described in which two thresholds, "2 bits" and "11 bits," are set as thresholds for classifying the number of bits of UCI, but the thresholds for classifying the number of bits of UCI are not limited to the examples shown in the above-mentioned embodiments and may be other values. Furthermore, the thresholds for classifying the number of bits of UCI may be different values ​​for high-priority UCI and low-priority UCI. For example, the thresholds may be set based on the type of PUCCH format or encoding method.

[0315] (4) In the above-described embodiments, examples have been described in which the high-priority UCI is HARQ-ACK or SR and the low-priority UCI is HARQ-ACK, but the high-priority UCI and the low-priority UCI may be, for example, any of HARQ-ACK, SR, and CSI. Furthermore, instead of at least one of the high-priority UCI and the low-priority UCI, another uplink signal or channel different from UCI may be applied.

[0316] (5) In each of the above-described embodiments, multiplexing of two UCIs (e.g., two HARQ-ACKs, or one SR and one HARQ) and multiplexing of three UCIs (e.g., two HARQ-ACKs and one SR) have been described, but the number of UCIs to be multiplexed is not limited to two or three and may be four or more.

[0317] (6) In each of the above-described embodiments, the case where terminal 200 controls the transmission of UCI having different priorities based on the number of bits of the UCI has been described. However, in controlling the transmission of UCI, terminal 200 may control the transmission of UCI based on other parameters, not limited to the number of bits of the UCI.

[0318] For example, terminal 200 may control UCI multiplexing based on the PUCCH format of each UCI having a different priority. For example, in the case of PUCCH format 0 or PUCCH format 1, terminal 200 may apply the same operation as when the number of UCI bits is 2 or less in each of the above-mentioned embodiments. Also, in the case of PUCCH format 2, 3, or 4, terminal 200 may apply the same operation as when the number of UCI bits is 3 or more in each of the above-mentioned embodiments.

[0319] Furthermore, for example, terminal 200 may control UCI multiplexing based on information related to the number of encodings for UCI (for example, an upper limit value for the number of encodings). For example, terminal 200 may apply separate coding when the number of encodings by polar codes when assuming the application of separate coding is less than a threshold (for example, less than two), and may apply joint coding when the number of encodings by polar codes when assuming the application of separate coding is equal to or greater than a threshold (for example, two or more).

[0320] Furthermore, terminal 200 may control UCI multiplexing based on a combination of at least two of the number of UCI bits, the PUCCH format, and the thresholds related to the number of codes, for example.

[0321] Furthermore, the above embodiment has been described assuming uplink communication between base station 100 and terminal 200. However, an embodiment of the present disclosure is not limited to this and may be applied to downlink communication or communication between terminals (for example, sidelink communication).

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

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

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

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

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

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

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

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

[0330] (frequency band) The present disclosure may be applied to both licensed and unlicensed bands.

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

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

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

[0334] <5G NR system architecture and protocol stack> 3GPP is working on the next release of fifth-generation cellular technology (also known as 5G), which includes the development of New Radio Access Technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, allowing for the prototyping and commercial deployment of 5G NR compliant devices (e.g., smartphones).

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

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

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

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

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

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

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

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

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

[0344] The Access and Mobility Management Function (AMF) hosts the following main functions: - Ability to terminate Non-Access Stratum (NAS) signaling; - NAS signaling security; - Access Stratum (AS) security control; - 3GPP Core Network (CN) inter-node signaling for mobility between access networks; - Reachability to idle mode UEs (including control and execution of paging retransmissions); - Managing the registration area; - Support for intra-system and inter-system mobility; - Access authentication; - Access authorization, including checking roaming privileges; - Mobility management control (subscription and policy); - Network slicing support; - Selection of Session Management Function (SMF).

[0345] Additionally, the User Plane Function (UPF) hosts the following main functions: - Anchor points for intra-RAT / inter-RAT mobility (if applicable); - External PDU (Protocol Data Unit) session points for interconnection with data networks; - Packet routing and forwarding; - Packet inspection and policy rule enforcement for the user plane part; - Traffic usage reporting; - uplink classifier to support routing of traffic flows to the data network; - A Branching Point for supporting a multi-homed PDU session; - QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement); - Verification of uplink traffic (mapping to the QoS flow of the SDF); - Buffer for downlink packets and trigger function for downlink data notification.

[0346] Finally, the Session Management Function (SMF) hosts the following main functions: - Session management; - Assignment and management of IP addresses for the UE; - Selection and control of the UPF; - A function for setting traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination; - Enforcement of control part policies and QoS; - Notification of downlink data.

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

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

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

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

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

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

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

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

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

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

[0357] Furthermore, for NR URLLC, several technical enhancements are possible from the perspective of the physical layer. These technical enhancements include enhancements to the PDCCH (Physical Downlink Control Channel) related to compact DCI, repetition of the PDCCH, and increased monitoring of the PDCCH. Also, the enhancement of UCI (Uplink Control Information) is related to the enhancement of enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback. Additionally, enhancements to the PUSCH related to mini-slot level hopping, and enhancements to retransmission / repetition are possible. The term "mini-slot" refers to a Transmission Time Interval (TTI) that contains fewer symbols than a slot (a slot has 14 symbols).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0371] A terminal according to one embodiment of the present disclosure includes a control circuit that varies parameters used for transmitting a plurality of uplink control signals having different priorities according to information related to the size of at least one of the plurality of uplink control signals, and a transmission circuit that transmits the plurality of uplink control signals.

[0372] In one embodiment of the present disclosure, the information about the size indicates the total number of bits of the plurality of uplink control signals.

[0373] In one embodiment of the present disclosure, the information regarding the size indicates a format of a channel used to transmit at least one of the plurality of uplink control signals.

[0374] In one embodiment of the present disclosure, the control circuit performs multiplexing control on the plurality of uplink control signals based on information regarding the coding number for the uplink control signals.

[0375] In one embodiment of the present disclosure, the parameters correspond to at least one of an encoding method for the plurality of uplink control signals, a resource mapping method for the plurality of uplink control signals, and a channel format used to transmit the multiplexed signal.

[0376] In one embodiment of the present disclosure, the encoding method includes a first encoding method for collectively encoding the plurality of uplink control signals, and a second encoding method for individually encoding the plurality of uplink control signals.

[0377] In one embodiment of the present disclosure, the control circuit sets the first encoding method when the sizes of both the first uplink control signal and the second uplink control signal are equal to or less than a first threshold, or when the sizes of both the first uplink control signal and the second uplink control signal are greater than a second threshold that is greater than the first threshold, and sets the second encoding method when the size of at least one of the first uplink control signal and the second uplink control signal is greater than the first threshold and equal to or less than the second threshold.

[0378] In one embodiment of the present disclosure, the control circuit sets the first encoding method when the size of at least one of the first uplink control signal and the second uplink control signal is equal to or smaller than a threshold, and sets the second encoding method when the size of both the first uplink control signal and the second uplink control signal is greater than the threshold.

[0379] In one embodiment of the present disclosure, the control circuit sets the first encoding method when the size of either one of a first uplink control signal and a second uplink control signal is equal to or smaller than a threshold, and sets the second encoding method when the size of either one of the uplink control signals is larger than the threshold.

[0380] In one embodiment of the present disclosure, the code used in the encoding method includes a repetition code, a Reed Muller code, or a polar code.

[0381] In one embodiment of the present disclosure, the plurality of uplink control signals include a response signal of a first priority and a response signal of a second priority higher than the first priority.

[0382] In one embodiment of the present disclosure, the plurality of uplink control signals include a response signal with a first priority and a scheduling request with a second priority higher than the first priority.

[0383] In one embodiment of the present disclosure, the plurality of uplink control signals include a response signal of a first priority, a response signal of a second priority higher than the first priority, and a scheduling request of the second priority.

[0384] In a communication method according to one embodiment of the present disclosure, a terminal varies parameters used for transmitting multiple uplink control signals having different priorities depending on information regarding the size of at least one of the multiple uplink control signals, and transmits the multiple uplink control signals.

[0385] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2020-212654, filed on December 22, 2020, are incorporated herein by reference in their entirety. [Industrial Applicability]

[0386] One embodiment of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0387] 100 base stations 101, 205 Control section 102 Upper control signal generation unit 103 Downlink control information generation unit 104, 206 Encoding section 105, 207 Modulation section 106, 208 Signal allocation section 107, 209 Transmission unit 108, 201 Receiver 109, 202 Extraction part 110, 203 Demodulation section 111, 204 Decoding section 200 devices< / option>

Claims

1. a control circuit for determining physical uplink control channel resources; a receiver for receiving uplink control information on the physical uplink control channel resource; the uplink control information includes first HARQ-ACK information having a first priority and second HARQ-ACK information having a second priority higher than the first priority; When the uplink control information includes the first HARQ-ACK information, the second HARQ-ACK information, and Scheduling Request (SR) information having the second priority, the second HARQ-ACK information and the SR information are concatenated, and the uplink control information in which the concatenated information having the second priority and the first HARQ-ACK information are multiplexed is received on the physical uplink control channel resource; The concatenated second HARQ-ACK information and the SR information are jointly encoded, and the concatenated information having the second priority and the first HARQ-ACK information are separately encoded. Base station.

2. the physical uplink control channel resource is determined from the physical uplink control channel resource set having the second priority; The base station of claim 1 .

3. If the number of bits of the uplink control information is 2 bits or less, the uplink control information is transmitted using format 0 or format 1 of a physical uplink control channel. The base station of claim 1 .

4. If the number of bits of the uplink control information is greater than 2, the uplink control information is transmitted using format 2, 3 or 4 of the physical uplink control channel. The base station of claim 1 .

5. The first HARQ-ACK information and the second HARQ-ACK information are encoded separately. The base station of claim 4.

6. The first HARQ-ACK information is encoded using a block code, and the second HARQ-ACK information is encoded using repetition. The base station of claim 1 .

7. Mapping the first HARQ-ACK information to resources is determined based on total resources and mapping the second HARQ-ACK information to resources. The base station of claim 1 .

8. The first HARQ-ACK information is encoded using a polar code, and the second HARQ-ACK information is encoded using repetition. The base station of claim 1 .

9. The first HARQ-ACK information is encoded using a block code, and the second HARQ-ACK information is encoded using a polar code. The base station of claim 1 .

10. If another uplink control information includes the first HARQ-ACK information having the first priority and Scheduling Request information having the second priority, the SR information is transmitted and the first HARQ-ACK information is dropped. The base station of claim 1 .

11. determining physical uplink control channel resources; receiving uplink control information on the physical uplink control channel resource; the uplink control information includes first HARQ-ACK information having a first priority and second HARQ-ACK information having a second priority higher than the first priority; When the uplink control information includes the first HARQ-ACK information, the second HARQ-ACK information, and Scheduling Request (SR) information having the second priority, the second HARQ-ACK information and the SR information are concatenated, and the uplink control information in which the concatenated information having the second priority and the first HARQ-ACK information are multiplexed is received on the physical uplink control channel resource; The concatenated second HARQ-ACK information and the SR information are jointly encoded, and the concatenated information having the second priority and the first HARQ-ACK information are separately encoded. Communication method.

12. the physical uplink control channel resource is determined from the physical uplink control channel resource set having the second priority; The communication method according to claim 11.

13. If the number of bits of the uplink control information is 2 bits or less, the uplink control information is transmitted using format 0 or format 1 of a physical uplink control channel. The communication method according to claim 11.

14. If the number of bits of the uplink control information is greater than 2, the uplink control information is transmitted using format 2, 3 or 4 of the physical uplink control channel. The communication method according to claim 11.

15. The first HARQ-ACK information and the second HARQ-ACK information are encoded separately. The communication method according to claim 14.

16. The first HARQ-ACK information is encoded using a block code, and the second HARQ-ACK information is encoded using repetition. The communication method according to claim 11.

17. Mapping the first HARQ-ACK information to resources is determined based on total resources and mapping the second HARQ-ACK information to resources. The communication method according to claim 11.

18. The first HARQ-ACK information is encoded using a polar code, and the second HARQ-ACK information is encoded using repetition. The communication method according to claim 11.

19. The first HARQ-ACK information is encoded using a block code, and the second HARQ-ACK information is encoded using a polar code. The communication method according to claim 11.

20. If another uplink control information includes the first HARQ-ACK information having the first priority and Scheduling Request information having the second priority, the SR information is transmitted and the first HARQ-ACK information is dropped. The communication method according to claim 11.

21. determining physical uplink control channel resources; receiving uplink control information on the physical uplink control channel resource; the uplink control information includes first HARQ-ACK information having a first priority and second HARQ-ACK information having a second priority higher than the first priority; When the uplink control information includes the first HARQ-ACK information, the second HARQ-ACK information, and Scheduling Request (SR) information having the second priority, the second HARQ-ACK information and the SR information are concatenated, and the uplink control information in which the concatenated information having the second priority and the first HARQ-ACK information are multiplexed is received on the physical uplink control channel resource; The concatenated second HARQ-ACK information and the SR information are jointly encoded, and the concatenated information having the second priority and the first HARQ-ACK information are separately encoded. Integrated circuit.

Images