Terminal, base station, communication system, and communication method

Abstract

An uplink channel to be transmitted in a case that the DCI indicates multiplexing of a response related to retransmission control is determined.SOLUTION: In a wireless communication system, a terminal receives, from a base station, DCI for scheduling a first uplink shared channel (UL-SCH) in a certain slot when HARQ-ACK is transmitted in the certain slot and there is no corresponding uplink control channel, and determines the first UL-SCH as a candidate for multiplexing the HARQ-ACK and transmits the first UL-SCH to the base station when there are a plurality of UL-SCHs in the certain slot and the DCI indicates that the HARQ-ACK is multiplexed on the first UL-SCH. In the determination of the UL channel to be transmitted, in a case that multiple UL-SCHs exist in a certain slot and the HARQ-ACK codebook type and the DCI field satisfy certain conditions, the first UL-SCH is determined as a candidate for multiplexing the HARQ-ACK.SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] The present invention relates to a terminal, a base station, a communication system, and a communication method in a wireless communication system. [Background technology]

[0002] The 3GPP (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, this wireless communication system will be referred to as "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. In 5G, various wireless technologies and network architectures are being studied to meet the requirements of achieving a throughput of 10 Gbps or more while keeping the latency in wireless sections to 1 ms or less (for example, Non-Patent Document 1).

[0003] In addition, in NR, when a PUCCH (Physical Uplink Control Channel) including a HARQ-ACK (Hybrid automatic repeat request - Acknowledgement) overlaps with one or more PUSCHs (Physical Uplink Shared Channels) at least in the time domain, the HARQ-ACK is multiplexed into one of the PUSCHs (e.g., Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V16.5.0 (2021-03) [Non-patent document 2] 3GPP TS 38.213 V16.5.0 (2021-03) Summary of the Invention [Problem to be solved by the invention]

[0005] The number of bits of HARQ-ACK multiplexed into PUSCH is determined based on a DAI (Downlink Assignment Index) included in an UL grant, which is DCI (Downlink Control Information) that schedules PUSCH. For example, when the DAI included in the UL grant indicates multiplexing of HARQ-ACK and the PDCCH (Physical Downlink Control Channel) that schedules the PDSCH (Physical Downlink Shared Channel) corresponding to the HARQ-ACK cannot be received, the operation of the terminal has not been specified.

[0006] The present invention has been made in view of the above points, and has as its object to determine an uplink channel to transmit when an uplink grant indicates multiplexing of responses related to retransmission control. [Means for solving the problem]

[0007] According to the disclosed technology, a receiver includes a receiver unit that receives, from a base station, downlink control information (DCI) including a downlink assignment index (DAI) field and that schedules a first uplink shared channel in a certain slot; and a receiver unit that receives, when a plurality of uplink shared channels exist in the certain slot and when a hybrid automatic repeat request (HARQ-ACK) is received, that schedules a first uplink shared channel in a certain slot. a control unit configured to determine the first uplink shared channel as a candidate for multiplexing HARQ-ACK when the DAI field indicates that an HARQ-ACK (Channel State Information) is multiplexed onto the first uplink shared channel and when no uplink control channel corresponding to HARQ-ACK exists in the certain slot, and a transmitter configured to transmit the first uplink shared channel to the base station, wherein the control unit determines the first uplink shared channel as a candidate for multiplexing HARQ-ACK when a plurality of uplink shared channels exist in the certain slot and the DAI field is not 4 when a type 2 HARQ-ACK codebook is used or the DAI field is not 0 when a type 1 HARQ-ACK codebook is used and when no uplink control channel corresponding to HARQ-ACK exists in the certain slot, and the control unit determines that the uplink shared channel is a candidate for multiplexing HARQ-ACK when the uplink shared channel is a channel state information (CSI) field of aperiodic CSI (Channel State Information). In this case, a terminal is provided that determines candidates for multiplexing HARQ-ACK by giving priority to an uplink shared channel of a dynamic grant over other uplink shared channels if the uplink shared channel includes a serving cell information, giving priority to an uplink shared channel of a configured grant over an uplink shared channel of an uplink shared channel of a small serving cell index, and giving priority to an uplink shared channel with an earlier starting symbol. [Effects of the Invention]

[0008] According to the disclosed technology, a technology is provided that makes it possible to determine an uplink channel to transmit when an uplink grant indicates multiplexing of responses related to retransmission control. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example (1) of a wireless communication system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example (2) of a wireless communication system according to an embodiment of the present invention. [Figure 3] FIG. 1 shows an example (1) in which UL channels overlap. [Figure 4] FIG. 10 is a diagram showing an example (2) in which UL channels overlap. [Figure 5] FIG. 10 is a diagram showing an example (3) in which UL channels overlap. [Figure 6] FIG. 10 is a diagram showing an example (4) in which UL channels overlap. [Figure 7] FIG. 10 shows an example (5) of overlapping UL channels. [Figure 8] 1 is a flowchart illustrating an example (1) of UL transmission according to an embodiment of the present invention. [Figure 9] FIG. 1 is a diagram showing an example (1-1) of UL transmission according to an embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an example (1-2) of UL transmission according to an embodiment of the present invention. [Figure 11] 1A to 1C are diagrams illustrating an example (1-3) of UL transmission according to an embodiment of the present invention. [Figure 12] 10 is a flowchart illustrating an example (2) of UL transmission according to an embodiment of the present invention. [Figure 13] FIG. 2 is a diagram showing an example (2-1) of UL transmission according to an embodiment of the present invention. [Figure 14] FIG. 2 is a diagram showing an example (2-2) of UL transmission according to an embodiment of the present invention. [Figure 15] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 16] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to the embodiment of the present invention. [Figure 17]2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0011] In operation of the wireless communication system according to the embodiment of the present invention, an existing technology may be used as appropriate, such as the existing NR or LTE, but is not limited to the existing NR or LTE.

[0012] Fig. 1 is a diagram illustrating an example (1) of a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0013] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of OFDM symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. Furthermore, the TTI (Transmission Time Interval) in the time domain may be a slot, a subframe, or a unit of another name (for example, a subslot).

[0014] Base station 10 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (component carriers)) to communicate with terminal 20. In carrier aggregation, one PCell (primary cell) and one or more SCells (secondary cells) are used.

[0015] The base station 10 transmits a synchronization signal, system information, and the like to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, on the NR-PBCH or PDSCH, and is also called broadcast information. As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 on the DL (Downlink) and receives control signals or data from the terminal 20 on the UL (Uplink). Note that, here, signals transmitted on control channels such as the PUCCH (Physical Uplink Control Channel) and the PDCCH (Physical Downlink Control Channel) are called control signals, and signals transmitted on shared channels such as the PUSCH (Physical Uplink Shared Channel) and the PDSCH (Physical Downlink Shared Channel) are called data, but these names are merely examples.

[0016] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 may be referred to as a UE, and the base station 10 may be referred to as a gNB.

[0017] Terminal 20 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (component carriers)) to communicate with base station 10. In carrier aggregation, one PCell (primary cell) and one or more SCells (secondary cells) are used. Also, a PUCCH-SCell having a PUCCH may be used.

[0018] Fig. 2 is a diagram illustrating an example (2) of a wireless communication system according to an embodiment of the present invention. Fig. 2 shows a configuration example of a wireless communication system in which DC (Dual connectivity) is implemented. As shown in Fig. 2, a base station 10A serving as an MN (Master Node) and a base station 10B serving as an SN (Secondary Node) are provided. The base station 10A and the base station 10B are each connected to a core network. The terminal 20 can communicate with both the base station 10A and the base station 10B.

[0019] A cell group provided by base station 10A, which is an MN, is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN, is called an SCG (Secondary Cell Group). In addition, in a DC, an MCG is composed of one PCell and one or more SCells, and an SCG is composed of one PSCell (Primary SCG Cell) and one or more SCells.

[0020] The processing operations in this embodiment may be executed in the system configuration shown in FIG. 1, in the system configuration shown in FIG. 2, or in any other system configuration.

[0021] Here, in NR, for scheduling a PUSCH, a configured grant (CG) having type 1 configured by a higher layer and type 2 configured by a higher layer and activated by a lower layer, and a dynamic grant (DG) assigned by downlink control information (DCI) in the physical layer are specified. Furthermore, when multiple UL channels overlap in the time domain, the priority of the UL channels, the UL channels into which control information is multiplexed, the UL channels to be dropped, etc. are determined based on, for example, the type of UL channel and / or the type of control information.

[0022] 3 is a diagram showing an example (1) in which UL channels overlap. When the PUCCH and PUSCH overlap in the time domain as shown in FIG. 3, terminal 20 may perform the operations shown in 1)-3) below. Note that the operations shown in A1)-A3) below may also be performed when repetition transmission (Repetition) is not applied to the PUCCH.

[0023] A1) When UCI (Uplink Control Information) in the PUCCH is HARQ-ACK, the HARQ-ACK is multiplexed onto the PUSCH as shown in FIG. 3, the PUCCH is dropped, and the PUSCH is transmitted. A2) When the UCI in the PUCCH is CSI, if the PUSCH does not contain CSI, the PUSCH is multiplexed with CSI, the PUCCH is dropped, and the PUSCH is transmitted as shown in Figure 3. If the PUSCH contains CSI, the PUCCH is dropped without multiplexing and the PUSCH is transmitted. A3) When the UCI in the PUCCH is SR, if the PUSCH does not include an Uplink Shared Channel (UL-SCH), the PUSCH is dropped and the PUCCH is transmitted. If the PUSCH includes an UL-SCH, processing is performed at the Media Access Control (MAC) layer. At the MAC layer, if logical channel priority processing is not configured, the PUSCH (UL-SCH) is given priority and the PUCCH (SR) is dropped. If logical channel priority processing is configured, if the PUSCH is not linked to a random access response, is not the PUSCH of message A in two-step random access, and the logical channel associated with the SR has a higher priority than the UL-SCH, the PUSCH (SR) is given priority and the PUSCH (UL-SCH) is dropped; otherwise, the PUSCH (UL-SCH) is given priority and the PUCCH (SR) is dropped.

[0024] 4 is a diagram showing an example (2) in which UL channels overlap. As shown in FIG. 4, when a PUCCH and N PUSCHs overlap in the time domain, terminal 20 may determine to which PUSCH the operation shown in A1)-A3) above should be applied according to the rules shown in A'1)-A'4) below. Note that these rules are applied to both the case of CA (Carrier Aggregation) and the case of non-CA. Note that in the case of CA, the process for overlapping is limited to CCs of the same PUCCH group. In other words, it is assumed that the PUCCH and N PUSCHs are CCs of the same PUCCH group.

[0025] A'1) If there is a PUSCH among the N PUSCHs configured to transmit aperiodic CSI (hereinafter also referred to as "A-CSI"), A'2) If there are 1 or more M1 DG (Dynamic grant)-PUSCHs and 1 or more M2 CG (Configured grant)-PUSCHs, any of the M1 DG-PUSCHs A'3) If there are N PUSCHs across multiple serving cells, any one or more of M3 PUSCHs in the cell with the smallest serving cell ID A'4) Among one or more M4 PUSCHs in the same serving cell, the PUSCH with the earliest start symbol

[0026] That is, in the example of Fig. 4, A'1) causes the DG-PUSCH configured to transmit A-CSI in CC1 to have the highest priority of 1. A'3) causes the DG-PUSCH in CC0 to have a priority of 2. A'4) causes the preceding DG-PUSCH in CC2 to have a priority of 3, and the following DG-PUSCH to have a priority of 4. The priority of the CG-PUSCH is 5.

[0027] Furthermore, if PUSCH resources are allocated but there is no data to transmit, terminal 20 may perform the operations shown in B1)-B2) below.

[0028] B1) In the case of CG-PUSCH, if the MAC PDU contains a zero MAC SDU (no SDU) and the MAC PDU contains only a periodic BSR (Buffer Status Report) and no logical channel data or only a padding BSR, PUSCH transmission may be skipped. This allows skipping of PUSCH transmission regardless of the setting from the network.

[0029] B2) In the case of DG-PUSCH, if the parameter skipUplinkTxDynamic is set to true, the PUSCH corresponds to a C-RNTI (Cell Radio Network Temporary Identifier), the MAC PDU includes a zero MAC SDU (no SDU), and the MAC PDU includes only a periodic BSR (Buffer Status Report) and no logical channel data or only a padding BSR, PUSCH transmission may be skipped. In other cases, PUSCH transmission cannot be skipped. That is, terminal 20 generates and transmits an empty MAC PDU.

[0030] Furthermore, when a PUSCH resource is allocated but there is no data to transmit and the PUSCH and PUCCH overlap in the time domain, terminal 20 may perform the operations shown in C0) to C2) below.

[0031] C0) The operation may be determined depending on the implementation of the terminal 20. That is, if this case occurs, the base station 10 needs to perform blind decoding. Alternatively, the base station 10 performs scheduling so that this case does not occur.

[0032] In the case of C1) DG-PUSCH, it is assumed that all PUSCHs are transmitted, and the terminal 20 determines which PUSCHs UCI is to be multiplexed into. The terminal 20 cannot skip the PUSCHs into which it has determined that UCI is to be multiplexed, and always transmits them. The MAC layer generates a MAC PDU for the PUSCHs into which it has determined that UCI is to be multiplexed. Note that in C1), there is no LCH prioritization, and a single PHY priority is assumed. It may also be assumed that there is no PUSCH repeated transmission.

[0033] In the case of C2) CG-PUSCH, it is assumed that all PUSCHs are to be transmitted, and the terminal 20 determines which PUSCHs UCI is to be multiplexed into. The terminal 20 cannot skip the PUSCHs into which it has been determined that UCI is to be multiplexed, and always transmits them. The MAC layer generates a MAC PDU for the PUSCHs into which it has been determined that UCI is to be multiplexed. Note that in C2), there is no LCH prioritization, and it is assumed that there is a single PHY priority and no PUSCH repeated transmission.

[0034] Furthermore, with respect to a PUSCH configured to transmit SP (Semi Persistent)-CSI, terminal 20 may perform the operation shown in D1) or D2) below. Note that in the present invention, a cell may be replaced with a carrier or a CC.

[0035] D1) When a PUSCH configured to transmit SP-CSI and a PUSCH including a UL-SCH or a PUSCH including A-CSI overlap in the time domain in the same cell, terminal 20 may drop the PUSCH configured to transmit SP-CSI. Note that a piggyback function for transferring information from one PUSCH to another PUSCH may not be supported. D2) If a PUSCH configured to transmit SP-CSI and a PUSCH including UL-SCH or A-CSI do not overlap in the time domain in the same cell, terminal 20 may transmit the PUSCH configured to transmit SP-CSI.

[0036] In addition, when the PUCCH overlaps with the PUSCH configured to transmit SP-CSI, the operations or rules shown in A1)-A3) above and A'1)-A'4) above may be applied.

[0037] Here, the HARQ-ACK codebook may be configured to include bits for HARQ-ACK in at least one unit of the time domain (e.g., slot), the frequency domain (e.g., component carrier (CC)), the spatial domain (e.g., layer), the transport block (TB), and the group of code blocks constituting the TB (code block group (CBG)).

[0038] Note that CC is also called a cell, a serving cell, a carrier, etc. Furthermore, the bit is also called a HARQ-ACK bit, HARQ-ACK information, or a HARQ-ACK information bit, etc. The HARQ-ACK codebook is also called a PDSCH-HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook), a codebook, a HARQ codebook, a HARQ-ACK size, etc.

[0039] The number of bits (size) included in the HARQ-ACK codebook may be determined semi-statically or dynamically. A semi-static HARQ-ACK codebook is also called a type 1 HARQ-ACK codebook, a semi-static codebook, etc. A dynamic HARQ-ACK codebook is also called a type 2 HARQ-ACK codebook, a dynamic codebook, etc.

[0040] Whether to use the Type 1 HARQ-ACK codebook or the Type 2 HARQ-ACK codebook may be configured in the UE by a higher layer parameter (for example, pdsch-HARQ-ACK-Codebook).

[0041] In the case of a Type 1 HARQ-ACK codebook, the UE may feed back HARQ-ACK bits corresponding to a predetermined range (e.g., a range set based on higher layer parameters) regardless of whether PDSCH is scheduled or not.

[0042] The predetermined range may be determined based on at least one of a predetermined time period (e.g., a set of a predetermined number of candidate occasions for receiving a PDSCH or a predetermined number of monitoring occasions m of a PDCCH), the number of CCs configured or activated in a UE, the number of TBs (number of layers or ranks), the number of CBGs per TB, and whether spatial bundling is applied. The predetermined range is also called a HARQ-ACK bundling window, a HARQ-ACK feedback window, a bundling window, a feedback window, etc.

[0043] In the case of the type 1 HARQ-ACK codebook, the UE feeds back a NACK bit within a predetermined range even if no PDSCH is scheduled for the UE. Therefore, when the type 1 HARQ-ACK codebook is used, it is expected that the number of HARQ-ACK bits to be fed back will increase.

[0044] Meanwhile, in the case of a Type 2 HARQ-ACK codebook, the UE may feed back HARQ-ACK bits for the scheduled PDSCH within the predetermined range.

[0045] Specifically, the UE may determine the number of bits of the Type 2 HARQ-ACK codebook based on a predetermined field in the DCI (e.g., a Downlink Assignment Indicator (Index) (DAI) field). The DAI field may be split into a counter DAI (cDAI) and a total DAI (tDAI).

[0046] The counter DAI may indicate a counter value of downlink transmissions (PDSCH, data, TB) scheduled within a predetermined period. For example, the counter DAI in a DCI that schedules data within the predetermined period may indicate the number counted first in the frequency domain (e.g., CC) and then in the time domain within the predetermined period.

[0047] The total DAI may indicate the sum (total number) of data scheduled within a predetermined period. For example, the total DAI in a DCI that schedules data at a predetermined time unit (e.g., a PDCCH monitoring opportunity) within the predetermined period may indicate the total number of data scheduled up to the predetermined time unit (also referred to as a point, timing, etc.) within the predetermined period.

[0048] The UE may transmit one or more HARQ-ACK bits determined (generated) based on the above-mentioned Type 1 or Type 2 HARQ-ACK codebook using at least one of the uplink control channel (PUCCH) and the uplink shared channel (PUSCH).

[0049] Here, in NR, when a PUCCH including a HARQ-ACK (Hybrid automatic repeat request - Acknowledgement) overlaps with one or more PUSCHs at least in the time domain, the HARQ-ACK is multiplexed onto one of the PUSCHs. The number of bits of the HARQ-ACK multiplexed onto the PUSCH is determined based on a DAI (Downlink Assignment Index) included in an UL grant, which is DCI (Downlink Control Information) that schedules the PUSCH. Hereinafter, the DAI included in the UL grant will be referred to as UL-DAI.

[0050] Fig. 5 is a diagram showing an example (3) in which UL channels overlap. As shown in Fig. 5, in CC0, when a PUCCH including a HARQ-ACK corresponding to a PDCCH and a PDSCH received in slot n is placed in slot m, and in CC1, a PUSCH scheduled by a PDCCH with UL-DAI=1 set and received in slot n+1 is placed in slot m, and when the PUCCH and the PUSCH overlap, the HARQ-ACK that was to be transmitted on the PUCCH is multiplexed into the PUSCH and transmitted.

[0051] Fig. 6 is a diagram showing an example (4) of overlapping UL channels. As shown in Fig. 6, for example, when the DAI included in the UL grant in slot n+1 of CC1 indicates multiplexing of HARQ-ACK (e.g., UL-DAI=1), and the UL grant schedules a PUSCH in slot m, and a PDCCH scheduling a PDSCH corresponding to the HARQ-ACK is not received in any CC and any slot, that is, when there is no PUCCH including a HARQ-ACK that overlaps with the PUSCH, it has not been specified whether to multiplex a HARQ-ACK onto a PUSCH in slot m of CC1.

[0052] 7 is a diagram showing an example (5) in which UL channels overlap. As shown in FIG. 7, when a PUSCH in slot m is scheduled by a PDCCH in slot n+1 of CC1 in which UL-DAI indicates multiplexing (for example, UL-DAI=1 is set), and a PUSCH and A-CSI in slot m are scheduled by a PDCCH in slot n+2 of CC2 in which UL-DAI indicates multiplexing (for example, UL-DAI=1 is set), and when a PDCCH scheduling a PDSCH corresponding to the HARQ-ACK is not received in any CC and in any slot, that is, when there is no PUCCH including a HARQ-ACK that overlaps the two PUSCHs, it has not been specified how to transmit the PUSCH in slot m of CC1 and the PUSCH in slot m of CC2 (that is, whether to multiplex HARQ-ACK).

[0053] Furthermore, it is necessary to define the UE operation so that the transmission operation of HARQ-ACK and / or PUSCH is clear even when terminal 20 does not receive some of the UL grants indicating multiplexing of HARQ-ACK.

[0054] Note that each embodiment described below may be applied to channels with the same priority, and the priority may be either PHY or MAC priority.

[0055] In addition, when there is no DL allocation, the UL-DAI of the UL grant indicating the presence of HARQ-ACK multiplexing may be UL-DAI=1 when a type 1 HARQ-ACK codebook is used, or UL-DAI=1, 2, or 3 when a type 2 HARQ-ACK codebook is used.

[0056] In addition, when there is no DL allocation, the UL-DAI of the UL grant indicating no HARQ-ACK multiplexing may be UL-DAI=0 when a type 1 HARQ-ACK codebook is used, or UL-DAI=4 when a type 2 HARQ-ACK codebook is used.

[0057] Table 1 shows an example of DAI in a Type 2 HARQ-ACK codebook.

[0058] [Table 1]

[0059] As shown in Table 1, when a Type 2 HARQ-ACK codebook is used, the DAI field in the UL grant consists of 2 bits, and when (MSB, LSB) is (0,0), UL-DAI=1, when (0,1), UL-DAI=2, when (1,0), UL-DAI=3, and when (1,1), UL-DAI=4.

[0060] 8 is a flowchart for explaining an example (1) of UL transmission in the embodiment of the present invention. As shown in step S11, it is assumed that the following conditions 1)-3) are satisfied in terminal 20.

[0061] 1) A PUSCH is scheduled by an UL grant. 2) The UL-DAI included in the UL grant indicates a value corresponding to the presence of HARQ-ACK multiplexing. 3) No DL allocation corresponding to the HARQ-ACK to be multiplexed onto the PUSCH has been received.

[0062] In the following step S12, terminal 20 determines the operation based on a predetermined condition. Note that in the case of PUSCH repeated transmission, terminal 20 may apply step S12 to only some transmissions, or may apply step S12 to all transmissions.

[0063] Fig. 9 is a diagram showing an example (1-1) of UL transmission in an embodiment of the present invention. For example, the predetermined condition in step S12 may be that only one PUSCH exists in the slot (slot m in Fig. 9). When the predetermined condition is satisfied, terminal 20 may multiplex HARQ-ACK onto the PUSCH, as shown in Fig. 9. That is, regardless of whether a PUCCH including an HARQ-ACK overlaps, HARQ-ACK may be multiplexed onto the PUSCH. The same applies to the following examples.

[0064] If the numerology differs depending on the CC or cell, the slot in the cell in which the smallest SCS is set may be the slot that is the target of the condition in step S12. The same applies to the following embodiments.

[0065] By performing the above-described operation, the operation of the terminal 20 is determined, and blind decoding on the base station 10 side becomes unnecessary.

[0066] The predetermined condition in step S12 may be that, when a plurality of PUSCHs exist in a slot, the UL-DAI in only one of the corresponding UL grants indicates a value corresponding to HARQ-ACK multiplexing, and the UL-DAI in the remaining UL grants indicates a value corresponding to no HARQ-ACK multiplexing. When the predetermined condition is satisfied, terminal 20 may multiplex HARQ-ACK onto a PUSCH scheduled by an UL grant whose UL-DAI has a value corresponding to HARQ-ACK multiplexing.

[0067] Furthermore, the predetermined condition in step S12 may be that, when a plurality of PUSCHs exist in a slot, the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing in two or more corresponding UL grants. When the predetermined condition is satisfied, terminal 20 may multiplex HARQ-ACK in all PUSCHs scheduled by UL grants in which the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing.

[0068] Furthermore, the predetermined condition in step S12 may be that, when a plurality of such PUSCHs exist in a slot, the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing in two or more corresponding UL grants. Fig. 10 is a diagram showing an example (1-2) of UL transmission in an embodiment of the present invention. As shown in Fig. 10, when the predetermined condition is satisfied, terminal 20 may multiplex HARQ-ACK in any one of the PUSCHs scheduled by an UL grant in which the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing.

[0069] The one PUSCH may be a PUSCH determined based on a rule for determining a UCI multiplexing destination, or may be a PUSCH corresponding to the UL grant received most recently. The rule for determining a UCI multiplexing destination may be, for example, first to prioritize a PUSCH including A-CSI, second to prioritize a DG-PUSCH over a CG-PUSCH, third to prioritize a PUSCH with a smaller serving cell index, and fourth to prioritize a PUSCH with an earlier start symbol.

[0070] Furthermore, when a plurality of such PUSCHs exist in a slot, the case where the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing in two or more corresponding UL grants may be regarded as an error case. That is, terminal 20 may not assume a case where a plurality of such PUSCHs exist in a slot and the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing in two or more corresponding UL grants, but may assume a case where a plurality of such PUSCHs exist in a slot and the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing in only one of the corresponding UL grants.

[0071] Note that the case where a plurality of PUSCHs exist in a slot may be limited to the case where the PUSCHs overlap with each other, or may include the case where the PUSCHs do not overlap with each other.

[0072] By performing the above-described operation, the operation of the terminal 20 is determined, and blind decoding on the base station 10 side becomes unnecessary.

[0073] In addition, the specified condition in step S12 may be a case where there are multiple PUSCHs in a slot, a subslot-based PUCCH is used, the DL allocation corresponding to the HARQ-ACK to be multiplexed onto the PUSCH is limited to some subslots (i.e., a PUCCH including a HARQ-ACK exists in some subslots, not less than 0, and not in the remaining subslots), and the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing in two or more of the corresponding UL grants.

[0074] Fig. 11 is a diagram showing an example (1-3) of UL transmission in an embodiment of the present invention. As shown in Fig. 11, HARQ-ACK may be multiplexed onto all of the PUSCHs corresponding to the two or more UL grants. For example, if a PUCCH having an HARQ-ACK exists in a certain subslot, the HARQ-ACK may be multiplexed onto the PUSCH into which the HARQ-ACK should be multiplexed, and NACK may be multiplexed onto the remaining PUSCHs into which no HARQ-ACK should be multiplexed. Note that in Fig. 11, LP-PUCCH indicates a low-priority PUCCH, and LP-PUSCH indicates a low-priority PUSCH.

[0075] Furthermore, the predetermined condition in step S12 may be a case where a plurality of PUSCHs are present in a slot, a subslot-based PUCCH is used, DL allocation corresponding to the HARQ-ACK to be multiplexed onto the PUSCH is limited to some subslots (i.e., PUCCHs including HARQ-ACKs are present in zero or more subslots and not present in the remaining subslots), and the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing in two or more of the corresponding UL grants. The HARQ-ACK may be multiplexed onto some of the PUSCHs corresponding to the two or more UL grants. For example, if a PUCCH including HARQ-ACK is present in a certain subslot, the HARQ-ACK may be multiplexed onto the PUSCH onto which the HARQ-ACK should be multiplexed, but not onto the remaining PUSCHs onto which the HARQ-ACK should not be multiplexed.

[0076] In addition, an error case may be defined as a case where multiple PUSCHs exist in a slot, a subslot-based PUCCH is used, the DL allocation corresponding to the HARQ-ACK to be multiplexed onto the PUSCH is limited to some subslots (i.e., a PUCCH including a HARQ-ACK exists in some subslots, equal to or greater than 0, and not in the remaining subslots), and the UL-DAI indicates a value corresponding to the presence of HARQ-ACK multiplexing in two or more of the corresponding UL grants.

[0077] Furthermore, the operation in step S12 may be changed based on the number of bits of HARQ-ACK or UCI (for example, HARQ-ACK and CSI). When a type 1 HARQ-ACK codebook is used, the number of bits of HARQ-ACK may be determined based on the TDRA table and the settings of candidate K1 values. K1 may be the slot offset from PDSCH reception to PUCCH transmission, or may be a value indicated in the PDSCH-to-HARQ_feedback timing indicator field. When a type 2 HARQ-ACK codebook is used, the number of bits of HARQ-ACK may be the number of bits corresponding to (determined based on) the value of UL-DAI. Note that the operation in step S12 may be applied when only one PUSCH exists in a slot where a PUSCH is allocated, or when multiple PUSCHs exist.

[0078] If the number of bits of the HARQ-ACK or UCI is 1 or 2, it may or may not be multiplexed onto the PUSCH based on the UL-DAI. Alternatively, if the number of bits of the HARQ-ACK or UCI is 1 or 2, it may or may not be multiplexed onto the PUSCH based on the UE implementation.

[0079] Note that the case where the number of bits of HARQ-ACK or UCI is 1 or 2 means that when a Type 2 HARQ-ACK codebook is used, UL-DAI = 1 or 2, or when a second UL-DAI is present in the UL grant, (first UL-DAI, second UL-DAI) = (4,1), (1,4), (1,1), (4,2), or (2,4).

[0080] The terminal 20 may execute the operation of step S12 above in combination with any of the conditions of step S12 described above. By executing the operation of step S12 as described above when the number of bits of HARQ-ACK or UCI is 1 or 2, multiplexing is performed by puncturing in either case, and therefore the base station 10 can decode the UL-SCH without blind decoding.

[0081] If the number of bits of HARQ-ACK or UCI is 3 or more (for example, UCI may be HARQ-ACK and CSI), terminal 20 may perform any of the following 1)-3) as the operation in step S12.

[0082] 1) It may be handled as an error case or may be handled based on the UE implementation. 2) If only HARQ-ACK is 3 bits or more, it may be treated as an error case or may be handled based on the UE implementation. 3) When the HARQ-ACK and CSI (or A-CSI) are 3 bits or more, they may be multiplexed onto the PUSCH based on the UL-DAI.

[0083] Terminal 20 may execute the operation of step S12 above in combination with any of the conditions of step S12 described above. When the number of bits of HARQ-ACK or UCI is 3 or more, executing the operation of step S12 as described above will cause blind decoding if multiplexed onto PUSCH by rate matching, so it is desirable to avoid this by scheduling. Note that when a PUSCH including A-CSI exists, it is determined that UCI is multiplexed onto the PUSCH of A-CSI, so a common understanding can be achieved between base station 10 and terminal 20.

[0084] Furthermore, terminal 20 may receive a bit relating to the importance of UCI in the UL grant. Note that, hereinafter, "1" indicates that UCI multiplexing is necessary, and "0" indicates that UCI multiplexing is not necessary, but this is not limiting. UCI may be HARQ-ACK or CSI.

[0085] When terminal 20 receives a bit "1" indicating the importance of UCI in an UL grant, it may multiplex UCI onto a PUSCH corresponding to the UL grant indicated by "1". Furthermore, when terminal 20 receives bits "1" indicating the importance of UCI in multiple UL grants, it may multiplex UCI onto all corresponding PUSCHs, or onto a PUSCH corresponding to the UL grant received most recently, or onto a PUSCH determined based on a rule for determining a UCI multiplexing destination. The rule for determining a UCI multiplexing destination may be, for example, first to prioritize a PUSCH including A-CSI, second to prioritize a DG-PUSCH over a CG-PUSCH, third to prioritize a PUSCH with a smaller serving cell index, and fourth to prioritize a PUSCH with an earlier start symbol.

[0086] As described above, by receiving a bit relating to the importance of UCI in the UL grant, the UCI multiplexing destination becomes clear, which simplifies the operation of the terminal 20 and makes it possible to avoid blind decoding by the base station 10.

[0087] 12 is a flowchart for explaining an example (2) of UL transmission in the embodiment of the present invention. As shown in step S21, it is assumed that the following conditions 1)-4) are satisfied in terminal 20.

[0088] 1) A PUSCH is scheduled by an UL grant. 2) The UL-DAI included in the UL grant indicates a value corresponding to no HARQ-ACK multiplexing. 3) A UL grant indicating a UL-DAI corresponding to HARQ-ACK multiplexing is not received. 4) The PUSCH overlaps with a PUCCH containing a HARQ-ACK.

[0089] In the next step S22, the terminal 20 performs one of the following operations 1) to 3).

[0090] 1) UCI ​​included in PUCCH is multiplexed onto PUSCH and transmitted. - Do not transmit PUCCH 2) UCI ​​included in PUCCH is not multiplexed onto PUSCH - Do not transmit PUCCH or - Simultaneous transmission of PUCCH and PUSCH 3) Send PUCCH and drop PUSCH

[0091] Fig. 13 is a diagram showing an example (2-1) of UL transmission in an embodiment of the present invention. As shown in Fig. 13, terminal 20 does not need to multiplex UCI included in PUCCH onto PUSCH. Terminal 20 may transmit PUCCH and PUSCH simultaneously, or may transmit PUSCH without transmitting PUCCH.

[0092] Fig. 14 is a diagram showing an example (2-2) of UL transmission in the embodiment of the present invention. As shown in Fig. 14, terminal 20 may multiplex UCI included in PUCCH onto PUSCH and transmit the PUCCH.

[0093] According to the above-described embodiment, in the operation of multiplexing HARQ-ACK or UCI onto PUSCH, even if either channel cannot be received, the operation of terminal 20 can be clarified.

[0094] That is, when the uplink grant indicates multiplexing of responses related to retransmission control, it is possible to determine the uplink channel to transmit.

[0095] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for executing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only the functions proposed in any of the embodiments.

[0096] <Base station 10> Fig. 15 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 15, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 15 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention. The transmitting unit 110 and the receiving unit 120 may be called a communication unit.

[0097] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of a higher layer from the received signal. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, DL data, etc. to the terminal 20. The transmitter 110 also transmits the setting information, etc., described in the embodiments.

[0098] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads out the information from the storage device as needed. The control unit 140 performs, for example, resource allocation and overall control of the base station 10. Note that the functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120. Furthermore, the transmitting unit 110 and the receiving unit 120 may be called a transmitter and a receiver, respectively.

[0099] <Terminal 20> Fig. 16 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 16, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 16 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be called a communication unit.

[0100] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The transmitter 210 also transmits HARQ-ACK, and the receiver 220 receives the setting information and the like described in the embodiments.

[0101] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220 in a storage device, and reads it out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The control unit 240 performs overall control of the terminal 20. Note that the functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220. Note that the transmitting unit 210 and the receiving unit 220 may be called a transmitter and a receiver, respectively.

[0102] (Hardware configuration) The block diagrams (FIGS. 15 and 16) used to explain the above embodiments show 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 be realized by combining the single device or the multiple devices with software.

[0103] 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, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, 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 these functions are implemented.

[0104] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 17 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0105] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 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.

[0106] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0107] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0108] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 15 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 16 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also 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.

[0109] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by 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 storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0110] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc 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. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0111] 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 referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0112] 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 performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0113] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by 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.

[0114] Furthermore, base station 10 and terminal 20 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, processor 1001 may be implemented using at least one of these pieces of hardware.

[0115] (Summary of the embodiment) As described above, according to the embodiments of the present invention, there is provided a terminal including: a receiver unit that receives a grant related to an uplink shared channel from a base station; a controller that, when a Downlink Assignment Index (DAI) included in the grant indicates that a Hybrid Automatic Repeat Request - Acknowledgement (HARQ-ACK) is multiplexed onto the uplink shared channel and when a downlink assignment corresponding to the HARQ-ACK to be multiplexed onto the uplink shared channel has not been received, determines whether to multiplex the HARQ-ACK onto the uplink shared channel; and a transmitter unit that transmits the uplink shared channel to the base station.

[0116] With the above configuration, even if the operation of multiplexing HARQ-ACK or UCI onto a PUSCH fails to receive either channel, it is possible to clarify the operation of terminal 20. That is, when an uplink grant indicates multiplexing of a response related to retransmission control, it is possible to determine the uplink channel to transmit.

[0117] When only one uplink shared channel exists in a slot in which the uplink shared channel is transmitted, the control unit may multiplex a HARQ-ACK onto the uplink shared channel. With this configuration, in the operation of multiplexing a HARQ-ACK or UCI onto a PUSCH, even if either channel cannot be received, the operation of the terminal 20 can be clarified.

[0118] When a plurality of uplink shared channels are present in a slot in which the uplink shared channel is transmitted and when only a grant corresponding to one of the uplink shared channels among the plurality of uplink shared channels indicates that a HARQ-ACK is multiplexed onto the one uplink shared channel, the control unit may multiplex a HARQ-ACK onto the one uplink shared channel. With this configuration, in an operation of multiplexing a HARQ-ACK or UCI onto a PUSCH, even if either one of the channels cannot be received, the operation of terminal 20 can be clarified.

[0119] When a plurality of uplink shared channels are present in a slot in which the uplink shared channel is transmitted and when grants corresponding to two or more of the uplink shared channels indicate that a HARQ-ACK is multiplexed onto the two or more uplink shared channels, the control unit may multiplex a HARQ-ACK onto all or any one of the two or more uplink shared channels. With this configuration, in the operation of multiplexing a HARQ-ACK or UCI onto a PUSCH, even if any of the channels cannot be received, the operation of terminal 20 can be clarified.

[0120] The control unit may determine an operation related to multiplexing a HARQ-ACK onto the uplink shared channel based on a number of bits of the HARQ-ACK. With this configuration, in an operation of multiplexing a HARQ-ACK or UCI onto a PUSCH, the operation of multiplexing onto a PUSCH can be changed according to the number of bits of the HARQ-ACK.

[0121] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a terminal executes a reception procedure of receiving a grant related to an uplink shared channel from a base station, a control procedure of deciding whether to multiplex a Hybrid automatic repeat request - Acknowledgement (HARQ-ACK) onto the uplink shared channel when a Downlink Assignment Index (DAI) included in the grant indicates that a HARQ-ACK is to be multiplexed onto the uplink shared channel and when a downlink assignment corresponding to the HARQ-ACK to be multiplexed onto the uplink shared channel has not been received, and a transmission procedure of transmitting the uplink shared channel to the base station.

[0122] With the above configuration, even if the operation of multiplexing HARQ-ACK or UCI onto a PUSCH fails to receive either channel, it is possible to clarify the operation of terminal 20. That is, when an uplink grant indicates multiplexing of a response related to retransmission control, it is possible to determine the uplink channel to transmit.

[0123] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0124] 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., Radio Resource Control (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.

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

[0126] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein 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.

[0127] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, 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 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0128] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

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

[0130] In the present disclosure, 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).

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

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

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

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

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

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

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

[0138] In this disclosure, terms such as "base station (BS)," "radio base station," "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.

[0139] A base station can accommodate one or more (e.g., three) cells. 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 (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

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

[0142] 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, or the mobile body itself. 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 IoT (Internet of Things) device such as a sensor.

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

[0144] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

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

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

[0147] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0148] 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."

[0149] 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 or that the first element must in some way precede the second element.

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

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

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

[0153] Numerology may be communication parameters that apply 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 the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

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

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

[0157] 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 (for example, 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.

[0158] 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 wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

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

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

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

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

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

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

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

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

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

[0168] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set for the terminal 20 within one carrier.

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

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

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

[0172] 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."

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

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

[0175] <Additional Notes> The above-described embodiment can be further described as follows.

[0176] (Appendix 1) a receiver for receiving a grant related to an uplink shared channel from a base station; a control unit that determines whether to multiplex a Hybrid Automatic Repeat Request - Acknowledgement (HARQ-ACK) onto the uplink shared channel when a Downlink Assignment Index (DAI) included in the grant indicates that a Hybrid Automatic Repeat Request - Acknowledgement (HARQ-ACK) is multiplexed onto the uplink shared channel and when a downlink assignment corresponding to the HARQ-ACK to be multiplexed onto the uplink shared channel has not been received; a transmitter that transmits the uplink shared channel to the base station.

[0177] (Appendix 2) 2. The terminal according to claim 1, wherein, when only one uplink shared channel exists in a slot in which the uplink shared channel is transmitted, the controller multiplexes a HARQ-ACK onto the uplink shared channel.

[0178] (Appendix 3) the control unit multiplexes a HARQ-ACK onto the one uplink shared channel when a plurality of uplink shared channels are present in a slot in which the uplink shared channel is transmitted and when only a grant corresponding to one of the uplink shared channels among the plurality of uplink shared channels indicates that a HARQ-ACK is multiplexed onto the one uplink shared channel.

[0179] (Appendix 4) 2. The terminal according to claim 1, wherein, when a plurality of uplink shared channels are present in a slot in which the uplink shared channel is transmitted and when grants corresponding to two or more of the uplink shared channels among the plurality of uplink shared channels indicate that a HARQ-ACK is multiplexed onto the two or more uplink shared channels, the controller multiplexes a HARQ-ACK onto all or any one of the two or more uplink shared channels.

[0180] (Appendix 5) 2. The terminal according to claim 1, wherein the control unit determines an operation related to multiplexing HARQ-ACK onto the uplink shared channel based on a number of bits of HARQ-ACK.

[0181] (Appendix 6) a receiving procedure for receiving a grant related to an uplink shared channel from a base station; a control procedure for determining whether to multiplex a Hybrid Automatic Repeat Request - Acknowledgement (HARQ-ACK) onto the uplink shared channel when a Downlink Assignment Index (DAI) included in the grant indicates that a Hybrid Automatic Repeat Request - Acknowledgement (HARQ-ACK) is multiplexed onto the uplink shared channel and when a downlink assignment corresponding to the HARQ-ACK multiplexed onto the uplink shared channel has not been received; a transmission procedure of transmitting the uplink shared channel to the base station, the terminal executing the communication method. [Explanation of symbols]

[0182] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device

Claims

1. a receiving unit configured to receive, from a base station, downlink control information (DCI) including a downlink assignment index (DAI) field and scheduling a first uplink shared channel in a certain slot; a control unit that determines the first uplink shared channel as a candidate for multiplexing a HARQ-ACK, when a plurality of uplink shared channels exist in the certain slot, when the DAI field indicates that a HARQ-ACK (Hybrid automatic repeat request - Acknowledgement) is multiplexed onto the first uplink shared channel, and when no uplink control channel corresponding to the HARQ-ACK exists in the certain slot; a transmitter that transmits the first uplink shared channel to the base station, the control unit determines the first uplink shared channel as a candidate for multiplexing HARQ-ACK when a plurality of uplink shared channels exist in the certain slot, and when the DAI field is not 4 when a type 2 HARQ-ACK codebook is used, or when the DAI field is not 0 when a type 1 HARQ-ACK codebook is used, and when an uplink control channel corresponding to HARQ-ACK does not exist in the certain slot; The control unit determines candidates for multiplexing HARQ-ACK in a terminal by giving priority to an uplink shared channel that includes aperiodic CSI (Channel State Information) over other uplink shared channels, giving priority to an uplink shared channel of a dynamic grant over an uplink shared channel of a configured grant, giving priority to an uplink shared channel with a small serving cell index, and giving priority to an uplink shared channel with an earlier start symbol.

2. a transmitter configured to transmit, to a terminal, Downlink Control Information (DCI), the DCI including a Downlink Assignment Index (DAI) field and scheduling a first uplink shared channel in a certain slot; a control unit that determines the first uplink shared channel as a candidate for multiplexing a HARQ-ACK, when a plurality of uplink shared channels exist in the certain slot, when the DAI field indicates that a HARQ-ACK (Hybrid automatic repeat request - Acknowledgement) is multiplexed onto the first uplink shared channel, and when no uplink control channel corresponding to the HARQ-ACK exists in the certain slot; a receiving unit that receives the first uplink shared channel from the terminal, the control unit determines the first uplink shared channel as a candidate for multiplexing HARQ-ACK when a plurality of uplink shared channels exist in the certain slot, and when the DAI field is not 4 when a type 2 HARQ-ACK codebook is used, or when the DAI field is not 0 when a type 1 HARQ-ACK codebook is used, and when an uplink control channel corresponding to HARQ-ACK does not exist in the certain slot; The control unit determines candidates for multiplexing HARQ-ACK in a base station by giving priority to an uplink shared channel that includes aperiodic CSI (Channel State Information) over other uplink shared channels, giving priority to an uplink shared channel with a dynamic grant over an uplink shared channel with a configured grant, giving priority to an uplink shared channel with a small serving cell index, and giving priority to an uplink shared channel with an earlier start symbol.

3. A communication system including a terminal and a base station, The terminal a receiving unit configured to receive, from a base station, downlink control information (DCI) including a downlink assignment index (DAI) field and scheduling a first uplink shared channel in a certain slot; a control unit that determines the first uplink shared channel as a candidate for multiplexing a HARQ-ACK, when a plurality of uplink shared channels exist in the certain slot, when the DAI field indicates that a HARQ-ACK (Hybrid automatic repeat request - Acknowledgement) is multiplexed onto the first uplink shared channel, and when no uplink control channel corresponding to the HARQ-ACK exists in the certain slot; a transmitter that transmits the first uplink shared channel to the base station, the control unit determines the first uplink shared channel as a candidate for multiplexing HARQ-ACK when a plurality of uplink shared channels exist in the certain slot, and when the DAI field is not 4 when a type 2 HARQ-ACK codebook is used, or when the DAI field is not 0 when a type 1 HARQ-ACK codebook is used, and when an uplink control channel corresponding to HARQ-ACK does not exist in the certain slot; the control unit determines candidates for multiplexing HARQ-ACK by giving priority to an uplink shared channel including aperiodic CSI (Channel State Information) over other uplink shared channels, giving priority to an uplink shared channel of a dynamic grant over an uplink shared channel of a configured grant, giving priority to an uplink shared channel having a small serving cell index, and giving priority to an uplink shared channel having an earlier start symbol; The base station a transmitter configured to transmit, to the terminal, a DCI including the DAI field and scheduling the first uplink shared channel in the certain slot; a control unit that determines the first uplink shared channel as a candidate for multiplexing the HARQ-ACK when a plurality of uplink shared channels exist in the certain slot, when the DAI field indicates that the HARQ-ACK is multiplexed onto the first uplink shared channel, and when no uplink control channel corresponding to the HARQ-ACK exists in the certain slot; a receiving unit that receives the first uplink shared channel from the terminal, the control unit determines the first uplink shared channel as a candidate for multiplexing HARQ-ACK when a plurality of uplink shared channels exist in the certain slot, and when the DAI field is not 4 when a type 2 HARQ-ACK codebook is used, or when the DAI field is not 0 when a type 1 HARQ-ACK codebook is used, and when an uplink control channel corresponding to HARQ-ACK does not exist in the certain slot; The control unit determines candidates for multiplexing HARQ-ACK by prioritizing an uplink shared channel that includes aperiodic CSI (Channel State Information) over other uplink shared channels, prioritizing an uplink shared channel with a dynamic grant over an uplink shared channel with a configured grant, prioritizing an uplink shared channel with a small serving cell index, and prioritizing an uplink shared channel with an earlier start symbol.

4. receiving, from a base station, downlink control information (DCI) including a downlink assignment index (DAI) field and scheduling a first uplink shared channel in a slot; determining the first uplink shared channel as a candidate for multiplexing a HARQ-ACK, when a plurality of uplink shared channels exist in the certain slot, when the DAI field indicates that a HARQ-ACK (Hybrid automatic repeat request - Acknowledgement) is multiplexed onto the first uplink shared channel, and when no uplink control channel corresponding to the HARQ-ACK exists in the certain slot; transmitting the first uplink shared channel to the base station; determining the first uplink shared channel as a candidate for multiplexing HARQ-ACK when there are a plurality of uplink shared channels in the certain slot, and when a type 2 HARQ-ACK codebook is used and the DAI field is not 4, or when a type 1 HARQ-ACK codebook is used and the DAI field is not 0, and when there is no uplink control channel corresponding to HARQ-ACK in the certain slot; and a procedure for determining candidates for multiplexing HARQ-ACK by giving priority to an uplink shared channel containing aperiodic CSI (Channel State Information) over other uplink shared channels, giving priority to an uplink shared channel with a dynamic grant over an uplink shared channel with a configured grant, giving priority to an uplink shared channel with a small serving cell index, and giving priority to an uplink shared channel with an earlier start symbol, in a communication method executed by a terminal.

Images