Terminal

Abstract

A terminal comprising: a control unit that multiplexes, on an uplink control channel, two or more pieces of uplink control information having different priority levels; and a communication unit that transmits an uplink signal using the uplink control channel on which the two or more pieces of uplink control information are multiplexed, wherein when executing re-selection of resources for the uplink control channel, the control unit determines resources of the uplink control channel on the basis of an effective payload size related to the two or more pieces of uplink control information and resource conditions related to the uplink control channel.

Description

[Technical Field]

[0001] The present disclosure relates to a terminal that performs wireless communication, and in particular to a terminal that performs multiplexing of uplink control information onto an uplink control channel. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] 3GPP Release 15 supports multiplexing of two or more uplink channels (a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH)) transmitted in the same slot.

[0004] Furthermore, in Release 17 of 3GPP, it was agreed to support multiplexing UCI (Uplink Control Information) having different priorities onto a PUCCH (for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "Enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication", RP-201310, 3GPP TSG RAN Meeting #86e, 3GPP, July 2020 Summary of the Invention

[0006] Under such circumstances, the inventors have conducted extensive research and found that, when multiplexing different UCIs, it is possible to appropriately perform channel coding of UCIs having different priorities by introducing a new scaling factor to be used for channel coding.

[0007] Therefore, the following disclosure has been made in consideration of such circumstances, and aims to provide a terminal that can appropriately perform channel coding of uplink control information multiplexed onto an uplink control channel.

[0008] One aspect of the present disclosure is a terminal including: a control unit that multiplexes two or more pieces of uplink control information having different priorities onto an uplink control channel; and a communication unit that transmits an uplink signal using the uplink control channel on which the two or more pieces of uplink control information are multiplexed, wherein when reselection of resources for the uplink control channel is performed, the control unit determines resources for the uplink control channel based on effective payload sizes for the two or more pieces of uplink control information and resource conditions for the uplink control channel. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing frequency ranges used in the wireless communication system 10. As shown in FIG. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Figure 4] FIG. 4 is a functional block diagram of the UE 200. [Figure 5] FIG. 5 is a diagram illustrating an example of operation. [Figure 6] FIG. 6 is a diagram showing an example of how to determine a coding rate. [Figure 7] FIG. 7 is a diagram showing an example of how to determine a coding rate. [Figure 8] FIG. 8 is a diagram showing an example of how to determine a coding rate. [Figure 9] FIG. 9 is a diagram showing an example of how to determine a coding rate. [Figure 10] FIG. 10 is a diagram illustrating an example of a hardware configuration of the UE 200. As shown in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0011] [Embodiment] (1) Overall configuration of the wireless communication system 1 is a schematic diagram of an overall configuration of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE 200).

[0012] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0013] The NG-RAN 20 includes a radio base station 100A (hereinafter, gNB100A) and a radio base station 100B (hereinafter, gNB100B). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG. 1.

[0014] The NG-RAN 20 actually includes multiple NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."

[0015] The gNB100A and gNB100B are radio base stations conforming to 5G and perform 5G radio communication with the UE200. The gNB100A, gNB100B, and UE200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements; Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs); and Dual Connectivity (DC), which simultaneously communicates between the UE and two NG-RAN nodes. DC may include Multi-RAT Dual Connectivity (MR-DC), which uses a Master Cell Group (MCG) and a Secondary Cell Group (SCG). Examples of MR-DC include E-UTRA-NR Dual Connectivity (EN-DC), NR-EUTRA Dual Connectivity (NE-DC), and NR-NR Dual Connectivity (NR-DC). Here, CCs (cells) used in CA may be considered to constitute the same cell group. The MCG and SCG may be considered to constitute the same cell group.

[0016] The wireless communication system 10 also supports a plurality of frequency ranges (FR).

[0017] 2, the wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR are as follows:

[0018] FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz~52.6 GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.

[0019] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0020] Furthermore, the wireless communication system 10 also supports frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz up to 114.25 GHz. For convenience, such high frequency bands may be referred to as "FR2x."

[0021] To solve the problem of increased phase noise in high frequency bands, when using bands above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) may be applied.

[0022] FIG. 3 shows an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. In FIG.

[0023] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc. may be used.

[0024] Also, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 or 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.

[0025] 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a BWP (Bandwidth Part), etc.

[0026] (2) Functional block configuration of wireless communication system Next, a description will be given of the functional block configuration of the wireless communication system 10. Specifically, a description will be given of the functional block configuration of the UE 200.

[0027] Fig. 4 is a functional block diagram of UE 200. As shown in Fig. 4, UE 200 includes radio signal transmitting / receiving unit 210, amplifier unit 220, modem unit 230, control signal / reference signal processing unit 240, encoding / decoding unit 250, data transmitting / receiving unit 260, and control unit 270.

[0028] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting / receiving unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0029] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0030] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100 or another gNB). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0031] The control signal / reference signal processor 240 performs processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0032] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

[0033] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0034] DMRS is a reference signal (pilot signal) known between the base station and the terminal for estimating the fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.

[0035] In addition to the DMRS and PTRS, the reference signals may include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0036] The channels include control channels and data channels, such as a PDCCH (Physical Downlink Control Channel), a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel), Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), and a Physical Broadcast Channel (PBCH).

[0037] Furthermore, the data channel includes a PDSCH (Physical Downlink Shared Channel) and a PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via the data channel. The data channel may be interpreted as a shared channel.

[0038] In an embodiment, the control signal and reference signal processor 240 configures a communication unit that transmits an uplink signal using an uplink control channel (PUCCH) on which two or more pieces of uplink control information (UCI (Uplink Control Information)) having different priorities are multiplexed. The uplink signal transmitted via the PUCCH includes at least the UCI. The UCI may include an acknowledgement (HARQ-ACK) for one or more TBs. The UCI may include a scheduling request (SR) requesting resource scheduling, and may also include channel state information (CSI) indicating the channel state.

[0039] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or another gNB).

[0040] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0041] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0042] The control unit 270 controls each functional block constituting the UE 200. In particular, in the embodiment, the control unit 270 configures a control unit that multiplexes two or more UCIs having different priorities into a PUCCH. The control unit 270 applies a specific scaling factor to at least one of the two or more UCIs in channel coding of the two or more UCIs. The specific scaling factor may be referred to as omega_LP_HP, omega_HP, or omega_LP. The specific scaling factor is a parameter used in a case where coding rates of two or more UCIs having different priorities are determined separately.

[0043] In the following, a UCI having a first priority (hereinafter referred to as an LP (Low Priority) UCI) and a UCI having a second priority higher than the first priority (hereinafter referred to as an HP (High Priority) UCI) will be described as an example. omega_LP_HP may be a parameter applied to an LP UCI or may be a parameter applied to an HP UCI. The specific scaling factor satisfies the condition 0≦omega_LP_HP (omega_HP or omega_HP)≦1.

[0044] (3) Channel coding Channel coding will be described below. Specifically, channel coding of UCI in a case where different UCIs are multiplexed onto a PUCCH will be described. Here, a case where LP UCI and HP UCI are multiplexed will be exemplified. The UCI may be one or more information elements selected from HARQ-ACK, SR, CSI Part 1, and CSI Part 2.

[0045] (3.1) Application Example 1 In the following, application example 1 will be described. In application example 1, a specific scaling factor (omega_LP_HP) applied to either the LP UCI or the HP UCI will be described. Here, omega_LP_HP is applied to the LP UCI.

[0046] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate applied to the HP UCI or a coding rate applied to a High Priority (HP) PUCCH resource. These coding rates are coding rates before being multiplied by omega_LP_HP, and may be coding rates (original coding rates) used when UCIs with different priorities are not multiplexed.

[0047] The LP UCI coding rate (LP_UCI_coding_rate) may be the coding rate obtained by multiplying HP_UCI_coding_rate by omega_LP_HP.

[0048] (3.2) Application Example 2 In the following, application example 2 will be described. In application example 2, a specific scaling factor (omega_LP_HP) applied to either the LP UCI or the HP UCI will be described. Here, omega_LP_HP is applied to the HP UCI.

[0049] The HP UCI co-de-rate (HP_UCI_coding_rate) may be the coding rate obtained by dividing the LP_UCI_coding_rate by omega_LP_HP. In other words, the HP_UCI_coding_rate may be the coding rate obtained by multiplying the LP_UCI_coding_rate by the reciprocal of omega_LP_HP.

[0050] The coding rate of the LP UCI (LP_UCI_coding_rate) may be a coding rate applied to the LP UCI or a coding rate applied to the LP (Low Priority) PUCCH resource. These coding rates are coding rates before being multiplied by omega_LP_HP, and may be coding rates (original coding rates) used when UCIs with different priorities are not multiplexed.

[0051] (3.3) Application example 3 Application Example 3 will be described below. In Application Example 3, a specific scaling factor (omega_LP_HP) applied to one of the LP UCI and the HP UCI will be described. Here, Application Example 3 describes a case where the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4. In Application Example 3, a case where the LP_UCI_coding_rate can be changed without changing the HP_UCI_coding_rate will be described.

[0052] The coding rate of the HP UCI (HP_UCI_coding_rate) may be the coding rate applied to the HP UCI or the coding rate applied to the HP (High Priority) PUCCH resource. These coding rates are coding rates before being multiplied by omega_LP_HP and may be referred to as original coding rates.

[0053] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(omega_LP_HP*HP_UCI_coding_rate, Upper_bound_LP_UCI_coding_rate).

[0054] Upper_bound_LP_UCI_coding_rate represents the upper limit of the co-rate of the LP UCI, and is calculated based on the total number of REs (Resource Elements) of the PUCCH resource on which the LP_UCI is multiplexed, the HP_UCI_coding_rate, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload without bundling or partial dropping of LP UCI bits, or may be a payload with bundling or partial dropping of LP UCI bits.

[0055] (3.4) Application Example 4 Application example 4 will be described below. In application example 4, a specific scaling factor (omega_LP_HP) applied to either the LP UCI or the HP UCI will be described. Here, a case will be described in which the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4. In application example 4, a case will be described in which both the LP_UCI_coding_rate and the HP_UCI_coding_rate can be changed.

[0056] The HP UCI co-de-rate (HP_UCI_coding_rate) and the LP UCI coding rate (LP_UCI_coding_rate) may be calculated based on the total number of REs of the PUCCH resource in which the LP UCI and the HP UCI are multiplexed, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload in which LP UCI bit bundling or partial dropping is not performed, or may be a payload in which LP UCI bit bundling or partial dropping is performed.

[0057] However, a constraint may be imposed that the LP_UCI_coding_rate is a coding rate obtained by multiplying the HP_UCI_coding_rate by omega_LP_HP.

[0058] (3.5) Application Example 5 Application Example 5 will be described below. In Application Example 5, a case will be described in which a specific scaling factor (omega_LP) applied to an LP UCI and a specific scaling factor (omega_HP) applied to an HP UCI are defined separately. Application Example 5 illustrates a case in which omega_LP is not provided and omega_HP is provided.

[0059] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_HP. The original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.

[0060] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(HP_UCI_coding_rate, original coding rate), where the original coding rate may be the coding rate applied to the LP UCI or may be the coding rate applied to the LP PUCCH resource.

[0061] (3.6) Application Example 6 Application Example 6 will be described below. In Application Example 6, a case will be described in which a specific scaling factor (omega_LP) applied to an LP UCI and a specific scaling factor (omega_HP) applied to an HP UCI are defined separately. Application Example 5 will exemplify a case in which omega_LP is provided without omega_HP being provided.

[0062] The HP UCI coding rate (HP_UCI_coding_rate) may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource. These coding rates may be referred to as original coding rates.

[0063] The coding rate of the LP UCI (LP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_LP. The original coding rate may be the coding rate applied to the LP UCI or the coding rate applied to the LP PUCCH resource.

[0064] However, a constraint may be imposed that the LP_UCI_coding_rate does not become larger than the HP_UCI_coding_rate.

[0065] (3.7) Application Example 7 Application Example 7 will be described below. In Application Example 7, a case will be described in which a specific scaling factor (omega_LP) applied to the LP UCI and a specific scaling factor (omega_HP) applied to the HP UCI are defined separately. Application Example 7 illustrates a case in which both omega_LP and omega_HP are provided.

[0066] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_HP. The original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.

[0067] The coding rate of the LP UCI (LP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_LP. The original coding rate may be the coding rate applied to the LP UCI or the coding rate applied to the LP PUCCH resource.

[0068] However, a constraint may be imposed that the LP_UCI_coding_rate does not become larger than the HP_UCI_coding_rate.

[0069] (3.8) Application Example 8 Application Example 8 will be described below. In Application Example 8, a case will be described in which a specific scaling factor (omega_LP) applied to an LP UCI and a specific scaling factor (omega_HP) applied to an HP UCI are defined separately. Here, a case will be described in which the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4. Application Example 8 illustrates a case in which omega_HP is provided without omega_LP being provided.

[0070] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_HP. The original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.

[0071] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(Upper_bound_LP_UCI_coding_rate, HP_UCI_coding_rate, original coding rate).

[0072] Upper_bound_LP_UCI_coding_rate represents the upper limit of the co-rate of the LP UCI and is calculated based on the total number of REs (Resource Elements) of the PUCCH resource onto which the LP_UCI is multiplexed, the HP_UCI_coding_rate, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload without bundling or partial dropping of LP UCI bits, or may be a payload with bundling or partial dropping of LP UCI bits. The original coding rate may be the coding rate applied to the LP UCI or the coding rate applied to the LP PUCCH resource.

[0073] (3.9) Application Example 9 Application Example 9 will be described below. In Application Example 9, a case will be described in which a specific scaling factor (omega_LP) applied to an LP UCI and a specific scaling factor (omega_HP) applied to an HP UCI are defined separately. Here, a case will be described in which the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4. Application Example 9 illustrates a case in which omega_LP is provided without omega_HP being provided.

[0074] The HP UCI coding rate (HP_UCI_coding_rate) may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource. These coding rates may be referred to as original coding rates.

[0075] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(Upper_bound_LP_UCI_coding_rate, omega_LP*original coding rate).

[0076] Upper_bound_LP_UCI_coding_rate represents the upper limit of the co-rate of the LP UCI and is calculated based on the total number of REs (Resource Elements) of the PUCCH resource onto which the LP_UCI is multiplexed, the HP_UCI_coding_rate, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload without bundling or partial dropping of LP UCI bits, or may be a payload with bundling or partial dropping of LP UCI bits. The original coding rate may be the coding rate applied to the LP UCI or the coding rate applied to the LP PUCCH resource.

[0077] However, a constraint may be imposed that the LP_UCI_coding_rate does not become larger than the HP_UCI_coding_rate.

[0078] (3.10) Application Example 10 Application Example 10 will be described below. In Application Example 10, a case will be described in which a specific scaling factor (omega_LP) applied to an LP UCI and a specific scaling factor (omega_HP) applied to an HP UCI are defined separately. Here, a case will be described in which the PUCCH format is one of PUCCH Format 2, PUCCH Format 3, and PUCCH Format 4. In Application Example 10, a case in which both omega_LP and omega_HP are provided will be illustrated.

[0079] The coding rate of the HP UCI (HP_UCI_coding_rate) may be a coding rate obtained by multiplying the original coding rate by omega_HP. The original coding rate may be the coding rate applied to the HP UCI or the coding rate applied to the HP PUCCH resource.

[0080] The LP UCI coding rate (LP_UCI_coding_rate) may be expressed as LP_UCI_coding_rate=min(Upper_bound_LP_UCI_coding_rate, omega_LP*original coding rate).

[0081] Upper_bound_LP_UCI_coding_rate represents the upper limit of the co-rate of the LP UCI and is calculated based on the total number of REs (Resource Elements) of the PUCCH resource onto which the LP_UCI is multiplexed, the HP_UCI_coding_rate, the HP UCI payload, and the LP UCI payload. The LP UCI payload may be a payload without bundling or partial dropping of LP UCI bits, or may be a payload with bundling or partial dropping of LP UCI bits. The original coding rate may be the coding rate applied to the LP UCI or the coding rate applied to the LP PUCCH resource.

[0082] However, a constraint may be imposed that the LP_UCI_coding_rate does not become larger than the HP_UCI_coding_rate.

[0083] (4) Notification method The method of notifying the above-mentioned specific scaling factors (omega_LP_HP, omega_HP, omega_LP) will be described below.

[0084] (4.1) Radio Resource Control Message The UE 200 may apply the specific scaling factor based on a radio resource control message (RRC message) that includes an information element that specifies the specific scaling factor.

[0085] First, the RRC message may include an information element specifying the above-mentioned omega_LP_HP. The omega_LP_HP is a parameter used in the above-mentioned application examples 1 to 4. The omega_LP_HP may be associated with UCIs having different priorities. For example, the UCIs having different priorities may include an LP HARQ-ACK and an HP HARQ-ACK, or may include an HP HARQ-ACK and an LP CSI.

[0086] Here, an omega_LP_HP that is commonly applied to UCIs having different priorities may be set regardless of the combination of HP UCIs and LP UCIs multiplexed onto the PUCCH. A different omega_LP_HP may be set for each combination of HP UCIs and LP UCIs multiplexed onto the PUCCH. A combination of HP UCIs and LP UCIs may be referred to as a multiplexing case.

[0087] Second, the RRC message may include an information element specifying the above-mentioned omega_HP. The omega_HP is a parameter used in the above-mentioned applications 5, 7, 8, and 10. The omega_HP may be associated with a UCI having a high priority (HP UCI). For example, the HP UCI may include an HP HARQ-ACK or an HP SR.

[0088] Here, an omega_HP that is commonly applied to UCIs having different priorities may be set regardless of the combination of HP UCIs and LP UCIs multiplexed onto the PUCCH. A different omega_HP may be set for each combination of HP UCIs and LP UCIs multiplexed onto the PUCCH.

[0089] Third, the RRC message may include an information element specifying the above-mentioned omega_LP. The omega_LP is a parameter used in the above-mentioned Applications 6, 7, 9, and 10. The omega_LP may be associated with a UCI having a low priority (LP UCI). For example, the LP UCI may include a LP HARQ-ACK and a LP CSI.

[0090] Here, an omega_LP that is commonly applied to UCIs having different priorities may be set regardless of the combination of HP UCIs and LP UCIs multiplexed onto the PUCCH. A different omega_LP may be set for each combination of HP UCIs and LP UCIs multiplexed onto the PUCCH.

[0091] (4.2) Downlink Control Information The UE 200 may apply a specific scaling factor based on downlink control information (DCI) including an information element specifying the specific scaling factor. In such a case, the setting of possible values ​​of the specific scaling factor may be performed by an RRC message. The DCI may include a field for storing an information element that explicitly specifies the set configured by the RRC message.

[0092] First, a case will be described in which a specific scaling factor is specified to be applied to one UCI multiplexing by one DCI.

[0093] In such a case, a specific DCI format specific to UE 200 may be used as the DCI format. The specific DCI format may include a DCI format for scheduling a PDSCH with HARQ-ACK, or may include another DCI format for scheduling PUCCHs. In such a case, the DCI may have the following fields:

[0094] The DCI may include a field for storing an information element for specifying the above-mentioned omega_LP_HP. The omega_LP_HP is a parameter used in the above-mentioned application examples 1 to 4.

[0095] The DCI may include a field for storing an information element specifying either omega_HP or omega_LP (omega_XP) described above. omega_HP is a parameter used in the above-described applications 5, 7, 8, and 10. omega_LP is a parameter used in the above-described applications 6, 7, 9, and 10. For example, omega_XP included in the DCI for an HP UCI may be interpreted as omega_HP. omega_XP included in the DCI for an LP UCI may be interpreted as omega_LP.

[0096] The DCI may include a field for storing the information element specifying the above-mentioned omega_HP and a field for storing the information element specifying the omega_LP.

[0097] The DCI may include a field for storing an information element specifying the above-mentioned omega_LP_HP and a field for storing an information element for specifying either the above-mentioned omega_HP or omega_LP (omega_XP). For example, the DCI for an HP UCI may include an information element specifying omega_LP_HP and an information element specifying omega_XP that is interpreted as omega_HP. The DCI for an LP UCI may include an information element specifying omega_LP_HP and an information element specifying omega_XP that is interpreted as omega_LP.

[0098] The DCI may include a field for storing an information element that specifies the above-mentioned omega_LP_HP, a field for storing an information element that specifies the above-mentioned omega_HP, and a field for storing an information element that specifies the omega_LP.

[0099] In these cases, when an information element specifying the omega_LP_HP is included in the DCI, the following constraints may be imposed. Specifically, the constraints may include a condition that the omega_LP_HP included in the DCI for the HP UCI must not differ from the omega_LP_HP included in the DCI for the LP UCI. The constraints may include a condition that the omega_LP_HP included in the DCI for the HP UCI is not applied, but the omega_LP_HP included in the DCI for the HP UCI is applied. The constraints may include a condition that the omega_LP_HP included in the DCI for the LP UCI is not applied, but the omega_LP_HP included in the DCI for the HP UCI is applied.

[0100] Furthermore, when the DCI includes fields for storing information elements specifying both the omega_HP and the omega_LP, the following constraints may be imposed. Specifically, the constraints may include a condition that the omega_HP included in the DCI for the HP UCI must not differ from the omega_LP included in the DCI for the LP UCI. The constraints may include a condition that the omega_HP included in the DCI for the HP UCI is applied, but the omega_LP included in the DCI for the HP UCI is not applied. The constraints may include a condition that the omega_HP included in the DCI for the HP UCI is applied, but the omega_LP included in the DCI for the LP UCI is not applied.

[0101] Secondly, a case will be described in which a specific scaling factor is designated by one DCI and is continuously applied to multiplexing of UCIs within a specific period.

[0102] In such a case, a specific DCI format may be used as the DCI format. The specific DCI format may include a newly introduced DCI format or an existing DCI format (0_0, 0_1, 0_2, 1_0, 1_1, 1_2) that does not involve scheduling of data or PUCCH. The specific DCI format commonly applied to the group may include an existing format (Group Common DCI Format) or a newly introduced DCI format. In such a case, the DCI may have the following fields.

[0103] The DCI may include a field for storing an information element for specifying the above-mentioned omega_LP_HP. The omega_LP_HP is a parameter used in the above-mentioned application examples 1 to 4.

[0104] The DCI may include a field for storing an information element specifying the above-mentioned omega_HP, which is a parameter used in the above-mentioned applications 5, 7, 8, and 10.

[0105] The DCI may include a field for storing an information element that specifies the above-mentioned omega_LP, which is a parameter used in the above-mentioned applications 6, 7, 9, and 10.

[0106] The DCI may include a field for storing an information element specifying the above-mentioned omega_HP, and a field for storing an information element specifying the above-mentioned omega_LP.

[0107] The DCI may include a field for storing an information element for specifying the above-mentioned omega_LP_HP, and a field for storing an information element for specifying the above-mentioned omega_HP.

[0108] The DCI may include a field for storing an information element for specifying the above-mentioned omega_LP_HP, and a field for storing an information element for specifying the above-mentioned omega_LP.

[0109] The DCI may include a field for storing an information element that specifies the above-mentioned omega_LP_HP, a field for storing an information element that specifies the above-mentioned omega_HP, and a field for storing an information element that specifies the above-mentioned omega_LP.

[0110] In such a case, the information element (specific scaling factor) included in the DCI may be applied to multiplexing of all UCIs regardless of the combination of HP UCIs and LP UCIs multiplexed onto the PUCCH.

[0111] A specific scaling factor may be applied to a multiplexing case set as a combination of HP UCI and LP UCI multiplexed onto the PUCCH (hereinafter, a multiplexing case). The multiplexing case may be set by an RRC message. The DCI may include a field for storing a different specific scaling factor for each multiplexing case. The DCI may distinguish, by number, a combination of UCIs to which a specific scaling factor is applied. For example, omega_LP_HP_1 may be applied to a combination of LP HARQ-ACK and HP HARQ-ACK, and omega_LP_HP_2 may be applied to a combination of HP HARQ-ACK and LP HARQ-ACK. omega_HP_1 may be applied to HP HARQ-ACK, and omega_HP_2 may be applied to HP SR. omega_LP_1 may be applied to LP HARQ-ACK, and omega_LP_2 may be applied to LP CSI.

[0112] A specific scaling factor may be applied to a multiplexing case specified by the DCI. Two or more multiplexing cases may be configured by an RRC message, and one of the configured multiplexing cases may be specified by the DCI. As described above, the DCI may include a field that stores a different specific scaling factor for each multiplexing case. The DCI may distinguish, by a number, a combination of UCIs to which a specific scaling factor is applied.

[0113] Furthermore, a mechanism for deactivating a specific scaling factor may be introduced. For example, a timer may be introduced to measure the period during which the specific scaling factor is applied, and the specific scaling factor may be deactivated when the timer expires. The timer may measure the period in symbol units or slot units. Alternatively, a DCI including an information element instructing the deactivation of a specific scaling factor may be introduced.

[0114] (5) Device capabilities The UE 200 may transmit a UE Capability including an information element regarding application of a specific scaling factor to the NG-RAN 20. In other words, the UE 200 may apply a specific scaling factor based on the capability of the UE 200. The information element regarding application of a specific scaling factor may be an information element indicating that the UE 200 supports multiplexing of UCIs having different priorities. The information element regarding application of a specific scaling factor may be an information element indicating that the UE 200 supports a specific scaling factor.

[0115] (6) Example of operation An example of the operation of the embodiment will be described below, focusing mainly on multiplexing UCI onto PUCCH.

[0116] 5, in step S10, the UE 200 transmits a message including UE Capability to the NG-RAN 20. The UE Capability may include an information element regarding application of a specific scaling factor.

[0117] In step S11, the UE 100 receives an RRC message from the NG-RAN 20. The RRC message may include an information element that specifies a specific scaling factor. The RRC message may include an information element that specifies a setting of values ​​that the specific scaling factor can take. The RRC message may include an information element that specifies a setting of a multiplexing set to which the specific scaling factor is applied.

[0118] In step S12, the UE 200 receives one or more DCIs via the PDCCH from the NG-RAN 20. The DCIs may include an information element specifying a specific scaling factor. The format of the DCIs may be the specific DCI format described above.

[0119] In step S13, the UE 200 transmits an uplink signal using a PUCCH in which UCIs having different priorities are multiplexed.

[0120] (7) Actions and Effects In the embodiment, the UE 200 performs channel coding of UCIs having different priorities by using a newly introduced specific scaling factor. With this configuration, when UCIs having different priorities are multiplexed onto a PUCCH, the UE 200 can appropriately perform channel coding of the UCIs multiplexed onto the PUCCH.

[0121] [Change Example 1] Modification 1 of the embodiment will be described below, focusing mainly on the differences from the embodiment.

[0122] In Modification 1, handling of PUCCH resources in a case where UCIs having different priorities are multiplexed onto a PUCCH will be described. In the following, the following abbreviations will be used to mean the following.

[0123] O_HP_UCI: HP UCI bit string to be multiplexed r_HP_UCI...Determined (target) code rate for HP UCI multiplexed onto multiple resources O_CRC,HP,UCI...CRC bit string for multiplexed HP UCI O_LP_UCI: LP UCI bit string to be multiplexed r_LP_UCI...Determined (target) code rate for LP UCI multiplexed onto multiple resources O_CRC,LP,UCI...CRC bit string for multiplexed LP UCI When there are different HP UCIs of M contained in different HP UCI types and different LP UCIs of N contained in different LP UCI types, the following meanings are used for each abbreviation.

[0124] O^m_HP_UCI...mth multiplexed HP UCI bit string r^m_HP_UCI: Determined (target) code rate for the m-th HP UCI multiplexed onto multiple resources O^m_CRC,HP,UCI...CRC bit string for the mth multiplexed HP UCI O^n_LP_UCI...nth multiplexed LP UCI bit string r^n_LP_UCI: Determined (target) code rate for the nth LP UCI multiplexed onto multiple resources O^n_CRC,LP,UCI...CRC bit string for the nth multiplexed LP UCI Specifically, when PUCCH resource reselection is performed, UE 200 (control unit 270) determines PUCCH resources based on at least one of valid payload sizes for two or more UCIs and resource conditions for the PUCCH. UE 200 (control unit 270) may determine valid payload sizes for two or more UCIs based on whether further separate coding of two or more UCIs is performed. UE 200 (control unit 270) may determine resource conditions for the PUCCH based on whether further separate coding of two or more UCIs is performed. UE 200 (control unit 270) may determine valid payload sizes for two or more UCIs and resource conditions for the PUCCH based on one or more code rates selected from code rates of two or more UCIs.

[0125] (1) Application example 1 In application example 1, the UCI resource of the original HP (or LP) is used without reselecting the PUCCH resource (set).

[0126] (2) Overview of Application Example 2 In the overview of application example 2, reselection of a PUCCH resource (set) is performed. The reselection of a PUCCH resource (set) is performed based on the payload size of an effective UCI (e.g., O_eff_UCI) and resource conditions. O_eff_UCI or resource conditions are determined as follows:

[0127] In Application Example 2-1, O_eff_UCI or the resource condition is determined based on an effective code rate r_e. When there is no further separate coding between HP UCI bits or between LP UCI bits, r_e may be determined based on one or more parameters selected from a target code rate r of the PUCCH resource, a code rate r_HP_UCI of the HP UCI, and a code rate r_LP_UCI of the LP UCI. When there is further separate coding between HP UCI bits or between LP UCI bits, r_e may be determined based on one or more parameters selected from a target code rate r of the PUCCH resource r, a code rate r^m_HP_UCI of the HP UCI, and a code rate r^n_LP_UCI of the LP UCI.

[0128] In Application Example 2-2, the code rates of the LP UCI and HP UCI are used as is for O_eff_UCI or resource conditions. When there is no further separate coding between HP UCI bits or between LP UCI bits, the code rate r_HP_UCI of the HP UCI and the code rate r_LP_UCI of the LP UCI are used for r_e. When there is further separate coding between HP UCI bits or between LP UCI bits, the code rate r^m_HP_UCI of the HP UCI and the code rate r^n_LP_UCI of the LP UCI are used for r_e.

[0129] In application example 2-3, an effective code rate r_e_HP of the HP UCI and an effective code rate r_e_LP of the LP UCI may be determined. The effective code rate r_e_HP of the HP UCI is determined based on the code rate r^m_HP_UCI of the HP UCI, and the effective code rate r_e_LP of the LP UCI is determined based on the code rate r^n_LP_UCI of the LP UCI.

[0130] (2.1) Details of Application Example 2 Here, we will explain a case in which reselection of PUCCH resources (sets) is performed from among PUCCH resources configured for at least one of HP UCI and LP UCI, taking into account the multiplexing of HP UCI bits and LP UCI bits.

[0131] For example, the reselection of the PUCCH resource(s) is performed based on the effective UCI payload size (O_eff_UCI) and the UCI payload size range (eg, maxPayloadSize set by RRC) of the PUCCH resource(s) candidates.

[0132] Consider the case where the payload size of the effective UCI (O_eff_UCI) is included in the candidate UCI payload size range (maxPayloadSize) of a specific PUCCH resource (set), as Case 1. In such a case, the specific PUCCH resource (set) is selected.

[0133] Consider Case 2, where the payload size of the effective UCI (O_eff_UCI) is larger than the candidate UCI payload size range (maxPayloadSize) of all PUCCH resource (set). In such a case, the PUCCH resource (set) with the largest UCI payload size range (maxPayloadSize) may be selected. Some of the LP UCI bits may be dropped, or some of the LP UCI bits may be bundled. Alternatively, the code rate of the LP UCI (or / and the code rate of the HP UCI) may be adjusted so that the payload size of the effective UCI (O_eff_UCI) is included in the candidate UCI payload size range (maxPayloadSize) of a specific PUCCH resource (set). For example, if the effective UCI payload size (O_eff_UCI) of the candidates for the PUCCH resource (set) is [0, 2], [2, N2], [N2, N3], or [N3, N4], and the condition N2≦O_eff_UCI≦N3 is satisfied, the third candidate for the PUCCH resource (set) is selected. On the other hand, if the condition N4≦O_eff_UC is satisfied, the PUCCH resource (set) with the largest UCI payload size range (maxPayloadSize) may be selected, and some LP UCI bits may be dropped or bundled, or the code rate may be adjusted.

[0134] First, consider the effective UCI payload size (O_eff_UCI). The effective UCI payload size (O_eff_UCI) may be defined as follows:

[0135] Consider the case where there is no further separate coding between HP UCIs or between LP UCIs in Case A. In such a case, the effective UCI payload size (O_eff_UCI) may be expressed as follows:

[0136]

number

[0137] r_e may be determined based on one or more parameters selected from the target code rate r of the PUCCH resource, the code rate r_HP_UCI of the HP UCI, and the code rate r_LP_UCI of the LP UCI. Seven methods (Alt) shown in FIG. 6 are possible for determining r_e.

[0138] "X≧0" may be an RRC setting or may be a predetermined fixed value. "X≧0" may be determined based on the bit sequence of the HP UCI to be multiplexed (O_HP_UCI) and the bit sequence of the LP UCI to be multiplexed (O_LP_UCI).

[0139] Alternatively, the effective UCI payload size (O_eff_UCI) may be expressed as follows:

[0140]

number

[0141] "X1≧0" and "X1≧0" may be RRC settings or may be predetermined fixed values. "X1≧0" may be determined based on the bit sequence of the HP UCI to be multiplexed (O_HP_UCI), and "X1≧0" may be determined based on the bit sequence of the LP UCI to be multiplexed (O_LP_UCI).

[0142] It should be noted that X, X1, and X2 are parameters introduced to address the possibility of additional influence on the CRC bits in separate coding.

[0143] Consider the case where there is additional separate coding between HP UCIs or between LP UCIs in Case B. In such a case, the effective UCI payload size (O_eff_UCI) may be expressed as follows:

[0144]

number

[0145] r_e may be determined based on one or more parameters selected from the target code rate r of the PUCCH resource, the code rate r^m_HP_UCI of the m-th HP UCI, and the code rate r^n_LP_UCI of the n-th LP UCI. Seven methods (Alt) shown in Figures 7 and 8 are possible for determining r_e.

[0146] "X≧0" may be an RRC setting or may be a predetermined fixed value. "X≧0" may be determined based on the bit sequence of the HP UCI to be multiplexed (O_HP_UCI) and the bit sequence of the LP UCI to be multiplexed (O_LP_UCI).

[0147] Alternatively, the effective UCI payload size (O_eff_UCI) may be expressed as follows:

[0148]

number

[0149] Here, as a method for determining the effective UCI payload size (O_eff_UCI), three methods (Alt) shown in FIG. 9 are possible.

[0150] "X1≧0" and "X1≧0" may be RRC settings or may be predetermined fixed values. "X1≧0" may be determined based on the bit sequence of the HP UCI to be multiplexed (O^m_HP_UCI), and "X1≧0" may be determined based on the bit sequence of the LP UCI to be multiplexed (O^n_LP_UCI).

[0151] Alternatively, the effective UCI payload size (O_eff_UCI) may be expressed as follows:

[0152]

number

[0153] Here, as a method for determining the effective UCI payload size (O_eff_UCI), three methods (Alt) are possible, similar to the above-described FIG.

[0154] "X1≧0" and "X1≧0" may be RRC settings or may be predetermined fixed values. "X1≧0" may be determined based on the bit sequence of the HP UCI to be multiplexed (O^m_HP_UCI), and "X1≧0" may be determined based on the bit sequence of the LP UCI to be multiplexed (O^n_LP_UCI).

[0155] Second, consider resource requirements. The resource requirements may be determined based on the code rate. The code rate may be defined as follows:

[0156] Consider the case where there is no further separate coding between HP UCIs or LP UCIs in case A. In such a case, reselection of PUCCH resource (set) may be performed based on the effective code rate r_e in the following manner.

[0157] In case 1, if the following conditions are met for PUCCH resource index #0, PUCCH resource index #0 is selected.

[0158]

number

[0159] In case 2, if the following conditions are met for PUCCH resource indexes #j and #j+1, PUCCH resource index #j+1 is selected.

[0160]

number

[0161] In case 3, consider the case where the following condition is satisfied for PUCCH resource index #j-1, and the index of the candidate with the largest resource among the PUCCH resource candidates is PUCCH resource index #j-1. In such a case, PUCCH resource index #j-1 may be selected. Alternatively, dropping or bundling of some LP UCIs may be performed until the above-mentioned case 1 or case 2 is satisfied.

[0162]

number

[0163] As a method for determining r_e, the seven methods (Alt) shown in FIG. 6 described above are conceivable.

[0164] Furthermore, based on the r_HP_UCI and r_LP_UCI, reselection of the PUCCH resource (set) may be performed in the following manner.

[0165] In case 4, if the following conditions are met for PUCCH resource index #0, PUCCH resource index #0 is selected.

[0166]

number

[0167] In case 5, if the following conditions are met for PUCCH resource indexes #j and #j+1, PUCCH resource index #j+1 is selected.

[0168]

number

[0169] In case 6, consider the case where the following condition is satisfied for PUCCH resource index #j-1, and the index of the candidate with the largest resource among the PUCCH resource candidates is PUCCH resource index #j-1. In such a case, PUCCH resource index #j-1 may be selected. Alternatively, dropping or bundling of some LP UCIs may be performed until the above-mentioned case 4 or case 5 is satisfied.

[0170]

number

[0171] Consider the case where there is additional separate coding between HP UCIs or between LP UCIs in case B. In such a case, PUCCH resource (set) reselection may be performed based on the effective code rate r_e in the following manner.

[0172] In case 1, if the following conditions are met for PUCCH resource index #0, PUCCH resource index #0 is selected.

[0173]

number

[0174] In case 2, if the following conditions are met for PUCCH resource indexes #j and #j+1, PUCCH resource index #j+1 is selected.

[0175]

number

[0176] In case 3, consider the case where the following condition is satisfied for PUCCH resource index #j-1, and the index of the candidate with the largest resource among the PUCCH resource candidates is PUCCH resource index #j-1. In such a case, PUCCH resource index #j-1 may be selected. Alternatively, dropping or bundling of some LP UCIs may be performed until the above-mentioned case 1 or case 2 is satisfied.

[0177]

number

[0178] As a method for determining r_e, the seven methods (Alt) shown in FIG. 6 described above are conceivable.

[0179] Furthermore, based on the r_e_HP_UCI and r_e_LP_UCI, reselection of PUCCH resources (sets) may be performed in the following manner.

[0180] In case 4, if the following conditions are met for PUCCH resource index #0, PUCCH resource index #0 is selected.

[0181]

number

[0182] In case 5, if the following conditions are met for PUCCH resource indexes #j and #j+1, PUCCH resource index #j+1 is selected.

[0183]

number

[0184] In case 6, consider the case where the following condition is satisfied for PUCCH resource index #j-1, and the index of the candidate with the largest resource among the PUCCH resource candidates is PUCCH resource index #j-1. In such a case, PUCCH resource index #j-1 may be selected. Alternatively, dropping or bundling of some LP UCIs may be performed until the above-mentioned case 4 or case 5 is satisfied.

[0185]

number

[0186] In addition, based on r^m_HP_UCI and r^n_LP_UCI, reselection of PUCCH resource (set) may be performed in the following manner.

[0187] In case 7, if the following condition is met for PUCCH resource index #0, PUCCH resource index #0 is selected.

[0188]

number

[0189] In case 8, if the following conditions are met for PUCCH resource indexes #j and #j+1, PUCCH resource index #j+1 is selected.

[0190]

number

[0191] In case 9, consider the case where the following condition is satisfied for PUCCH resource index #j-1, and the index of the candidate with the largest resource among the PUCCH resource candidates is PUCCH resource index #j-1. In such a case, PUCCH resource index #j-1 may be selected. Alternatively, dropping or bundling of some LP UCIs may be performed until the above-mentioned case 7 or case 8 is satisfied.

[0192]

number

[0193] [Change Example 2] Modification 2 of the embodiment will be described below, focusing mainly on the differences from the embodiment.

[0194] In Modification 2, a case will be described in which the maximum number of PRBs (M^PUCCH_RB) of the selected PUCCH resource is not sufficient to multiplex the HP UCI bit and the LP UCI bit.

[0195] In such a case, UE 200 may drop some of the LP UCIs until there are enough PRBs. UE 200 may bundle some of the LP UCIs until there are enough PRBs. UE 200 may adjust the coding rate of the LP UCIs until there are enough PRBs. UE 200 may adjust the coding rates of the HP UCIs and LP UCIs while guaranteeing the coding rate of the HP UCIs until there are enough PRBs. UE 200 may drop some of the coded LP UCIs in rate matching.

[0196] [Other embodiments] The present invention has been described above in accordance with the embodiments, but it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0197] Although not specifically mentioned in the above disclosure, the specific scaling factors (omega_LP_HP, omega_HP, omega_LP) may be set by higher layer parameters. The specific scaling factors may be predetermined in the wireless communication system. The specific scaling factors may be set by higher layer parameters and reported from the UE 200 to the NG-RAN 20 as UE Capability.

[0198] Although not specifically mentioned in the above disclosure, an information element specifying a specific scaling factor may be included in a MAC CE message. For example, the application of the above-mentioned DCI may be realized by MAC CE notification.

[0199] Although not specifically mentioned in the above disclosure, the priority may be determined as follows: For example, the priority of HARQ-ACK may be higher than the priority of SR; the priority for URLLC (Ultra Reliable and Low Latency Communications) may be higher than the priority for eMBB (enhanced Mobile BroadBand).

[0200] Although not specifically mentioned in the above disclosure, in multiplexing of HP UCI and LP UCI with separate coding, the target coding rate (e.g., r_HP_UCI, r_^m_HP_UCI, r^n_LP_UCI, etc.) may be determined based on an indication from the gNB or by other methods.

[0201] Although not specifically mentioned in the above disclosure, information elements required for separate coding (e.g., target coding rate) may be set by higher layer parameters. Information elements required for separate coding may be reported from UE 200 as UE Capability. Information elements required for separate coding may be determined in advance. Information elements required for separate coding may be set based on higher layer parameters and UE Capability. Information elements required for separate coding may be determined based on the type of UCI included in the UCI bits to be multiplexed.

[0202] Although not specifically mentioned in the above disclosure, the UE capability may include an information element indicating whether the UE 200 supports separate coding of UCIs with different priorities. The UE capability may also include an information element indicating whether the UE 200 has a function to select a PUCCH resource (set) based on the code rates of the LP UCI and the HP UCI.

[0203] The block diagram (FIG. 4) used in the description of the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0204] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0205] Furthermore, the above-described UE 200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 10 is a diagram showing an example of the hardware configuration of the device. As shown in Fig. 10, the device may be configured as a computer including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0206] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0207] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0208] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0209] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0210] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0211] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., that can execute a method according to an embodiment of the present disclosure.

[0212] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0213] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0214] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0215] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0216] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0217] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0218] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0219] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G) may also be applied.

[0220] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0221] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0222] Information and signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and may be input and output via multiple network nodes.

[0223] The input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be sent to another device.

[0224] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0225] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0226] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0227] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0228] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0229] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0230] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0231] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0232] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0233] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0234] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0235] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0236] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0237] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0238] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0239] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as uplink channel and downlink channel may be read as side channel.

[0240] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0241] A radio frame may be composed of one or more frames in the time domain, each of which may be called a subframe.

[0242] A subframe may further be composed of one or more slots in the time domain, and may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0243] Numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.

[0244] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol). A slot may be a time unit based on numerology.

[0245] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0246] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0247] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0248] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

[0249] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0250] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0251] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0252] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0253] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0254] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0255] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0256] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0257] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0258] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0259] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0260] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0261] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0262] The reference signal may also be abbreviated as Reference Signal (RS), and may also be called a pilot depending on the applicable standard.

[0263] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0264] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0265] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0266] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0267] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0268] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0269] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0270] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0271] 10. Wireless communication systems 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus

Claims

1. A control unit that multiplexes first uplink control information having a first priority and second uplink control information having a second priority different from the first priority onto an uplink control channel; a transmitter that transmits the first uplink control information and the second uplink control information via the uplink control channel; Equipped with the controller determines a resource set for the uplink control channel based on a total size of the first uplink control information and the second uplink control information and a payload size range. Terminal.

2. A receiver for receiving an information element indicating a maximum value of the payload size range. The terminal according to claim 1 .

3. The first uplink control information and the second uplink control information are acknowledgements to downlink data. The terminal according to claim 1 .

4. A terminal and a base station, the terminal comprises: a control unit that multiplexes first uplink control information having a first priority and second uplink control information having a second priority different from the first priority onto an uplink control channel; the base station includes a receiving unit that receives the first uplink control information and the second uplink control information via the uplink control channel; the controller determines a resource set for the uplink control channel based on a total size of the first uplink control information and the second uplink control information and a payload size range. Wireless communication system.

5. A step of multiplexing first uplink control information having a first priority and second uplink control information having a second priority different from the first priority onto an uplink control channel; transmitting the first uplink control information and the second uplink control information via the uplink control channel; determining a resource set for the uplink control channel based on a total size and a payload size range of the first uplink control information and the second uplink control information; A wireless communication method comprising:

Images