Terminal, communication method, and communication system

Abstract

A terminal is provided with: a control unit that multiplexes acknowledgement response information and / or first uplink control information to a specific channel on the basis of a multiplexing method determined in accordance with the setting of first joint coding of the acknowledgement response information and the first uplink control information indicating the timing at which an uplink signal is not used; and a transmission unit that transmits a signal of a specific channel.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a terminal, a communication method, and a communication system. BACKGROUND

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) is standardized for the purpose of further high-speed data rates, low latency, and the like. In addition, a subsequent system to LTE is also being studied for the purpose of further broadbandization and high speed compared to LTE. There are, for example, systems called LTE-Advanced (LTE-A), Future Radio Access (FRA), 5th generation mobile communication system (5G), 5G plus (5G+), Radio Access Technology (New-RAT), New Radio (NR), and the like in the subsequent system to LTE.

[0003] In NR, in Release 16, the setting of CG PUSCH (Configured Grant Physical Uplink Shared Channel) is specified (for example, Non-Patent Literature 1). There are Type 1 CG PUSCH and Type 2 CG PUSCH in CG PUSCH.

[0004] In addition, in Release 17, research is being conducted on Extended Reality (XR) such as Virtual Reality (VR), mixed reality (MX), and the like, and the scenario, requirements, main performance evaluation indicators (Key Performance Indicator (KPI)), and evaluation methods of XR are being studied. As the requirements for XR, capacity, latency (delay), mobility, and energy saving are considered.

[0005] Further, in Release 18, consensus has been reached on supporting dynamic indication of an unused CG PUSCH occasion by a terminal based on uplink control information (UCI).

[0006] Prior Art Documents

[0007] Non-Patent Literature

[0008] Non-Patent Literature 1: TS 38.331 V16.2.0 (2020-09) SUMMARY

[0009] There is room for further study regarding a method of transmitting uplink control information including information related to an unused CG PUSCH occasion or the like.

[0010] One embodiment of the present disclosure provides a terminal, a communication method, and a communication system that can appropriately transmit uplink control information including information related to an unused CG PUSCH occasion or the like.

[0011] A terminal according to one embodiment of the present disclosure includes a control unit that multiplexes acknowledgement information and / or first uplink control information indicating a time of an unused uplink signal based on a multiplexing method determined based on a first joint encoding of the acknowledgement information and the first uplink control information, and a transmission unit that transmits a signal of a specific channel. BRIEF DESCRIPTION OF DRAWINGS

[0012] Figure 1 is a diagram illustrating an example of dual connectivity (DC).

[0013] Figure 2 is a diagram illustrating an example of PUCCH carrier switching.

[0014] Figure 3 is a diagram illustrating an outline of a Type 1 HARQ-ACK CB.

[0015] Figure 4 is a diagram illustrating an outline of a Type 2 HARQ-ACK CB.

[0016] Figure 5is a diagram illustrating an example of generation of a Type 1 HARQ-ACK CB (Type 1 HARQ-ACK CB).

[0017] Figure 6 is a diagram illustrating an example of generation of a Type 1 HARQ-ACK CB (Type 1 HARQ-ACK CB).

[0018] Figure 7 is a diagram illustrating an example of generation of a Type 1 HARQ-ACK CB (Type 1 HARQ-ACK CB).

[0019] Figure 8 is a diagram illustrating an example of determination of a candidate PDSCH reception opportunity of Step A-2 (Step A-2).

[0020] Figure 9 is a diagram illustrating an example of allocation of a TBoMS-based PUSCH.

[0021] Figure 10 is a diagram illustrating an example of a CG PUSCH.

[0022] Figure 11 is a block diagram showing an example of a structure of a base station according to the embodiment.

[0023] Figure 12 is a block diagram showing an example of a structure of a terminal according to the embodiment.

[0024] Figure 13 is a diagram showing an example of a hardware structure of a base station and a terminal according to the embodiment of the present disclosure.

[0025] Figure 14 is a diagram showing an example of a structure of a vehicle in the embodiment of the present application. DETAILED DESCRIPTION

[0026] Hereinafter, an embodiment according to an aspect of the present disclosure will be described with reference to the drawings.

[0027] In NR, in Release 17, various kinds of technologies are being researched regarding ways called Ultra-Reliable and Low Latency Communications (URLLC) and Industrial Internet of Things (IIoT). In the URLLC, the functional enhancement of feedback of a terminal for a Hybrid Automatic Repeat request-Acknowledgement (HARQ-ACK) is researched. The HARQ-ACK is an example of information related to an acknowledgement response (for example, an acknowledgement) of a terminal for received data. As a matter of research for these URLLC, consensus is reached on supporting dynamic and semi-static PUCCH carrier switching. In addition, the PUCCH carrier switching can also be called other names such as carrier switching for control information transmission.

[0028] The PUCCH carrier switching is a technology applied in a case where a base station communicates via multiple cells. Hereinafter, dual connectivity and the PUCCH carrier switching, which are examples of communication via multiple cells, are described.

[0029] < Dual Connectivity >

[0030] Figure 1 is a diagram illustrating an example of dual connectivity (DC). In the example of Figure 1 , the base station 10-1 can be a Master Node (MN). The base station 10-2 can be a Secondary Node (SN). As illustrated in the example of Figure 1 , in the DC, carriers between different base stations are bundled.

[0031] In the example of Figure 1 , the base station 10-1 communicates with the terminal 20 via a primary cell (Pcell) and a secondary cell (Scell). In the example of Figure 1 , the terminal 20 establishes an RRC connection with the base station 10-1.

[0032] In the case of DC, since there is a possibility that there is a delay in communication between the base station 10-1 and the base station 10-2, it is difficult to notify uplink control information (for example, Uplink Control Information (UCI)) received in the Pcell of the base station 10-1 to the base station 10-2 via a backhaul link (for example, a wired or wireless link connecting the base station 10-1 and the base station 10-2) and reflect it to the scheduling of the subordinate Scell of the base station 10-2. Therefore, in DC, in addition to the Pcell of the base station 10-1, 1 carrier subordinate to the base station 10-2 can be set as a Primary Scell (PScell), and PUCCH transmission can be supported in the PScell. In this case, the terminal 20 transmits UCI to the base station 10-2 via the PScell.

[0033] In Figure 1 the example, in addition to the Pcell, the terminal 20 is set with a Scell with respect to the base station 10-1. Further, in addition to the PScell, the terminal 20 is set with a Scell with respect to the base station 10-2. The terminal 20 transmits UCI of each carrier subordinate to the base station 10-1 through the PUCCH of the Pcell. Further, the terminal 20 transmits UCI of each carrier subordinate to the base station 10-2 through the PUCCH of the PScell. In Figure 1 the example, a cell group (CG) subordinate to the base station 10-1 can also be referred to as a Master Cell-Group (MCG). A cell group subordinate to the base station 10-2 can also be referred to as a Secondary Cell-Group (SCG).

[0034] In the case of DC, the terminal 20 can also perform PUCCH transmission via the Pcell, the PScell, and / or the PUCCH-Scell. In general, it is not assumed that the terminal 20 performs PUCCH transmission via a Scell other than the Pcell, the PScell, and the PUCCH-Scell.

[0035] <PUCCH carrier switching>

[0036] With respect to PUCCH carrier switching, in a Time Division Duplex (TDD) method, a reduction method of latency of HARQ-ACK feedback is being studied.

[0037] Figure 2 is a diagram illustrating an example of PUCCH carrier switching. In Figure 2In this example, the base station and the terminal communicate via cell 1 and cell 2. Figure 2 In the example, cell 1 is a P-cell, and cell 2 is an S-cell. Furthermore, in Figure 2 The example shows the downlink (DL) time slots and uplink (UL) time slots in each cell.

[0038] exist Figure 2 In the example, the terminal receives data at a timed interval in S101 (receiving the Physical Downlink Shared Channel (PDSCH)). The terminal attempts to send a HARQ-ACK for the data received in S101 at a timed interval in S102, but at the timed interval in S102, the time slot of cell 1 becomes the downlink (DL) time slot. Therefore, if the terminal sends a HARQ-ACK through cell 1, the transmission of the HARQ-ACK is reserved until the timed interval of the PUCCH transmission in the uplink (UL) time slot (e.g., Figure 2 The timing of HARQ-ACK transmission increases as the timing of S103 (the timeout period) increases. Additionally, the timing of PUCCH transmission in the uplink (UL) time slot can also be referred to as the PUCCH timing.

[0039] exist Figure 2 In the example, during timing S102, the time slot of cell 2 becomes the UL time slot. Figure 2 In the example, if the terminal can send a HARQ-ACK for the data received in S101 during the PUCCH timing in S102 of cell 2, the latency of HARQ-ACK transmission can be reduced. Low latency within the radio interval is particularly required in URLLC. Therefore, as an extension of URLLC technology, 3GPP (registered trademark) is investigating PUCCH carrier handover for the carrier in which the terminal transmits PUCCH.

[0040] Additionally, in the following embodiments, the term "identical timing" can be either completely identical timing or all or part of time resources (e.g., one or more symbols (or resources with shorter time units than symbols)) being identical or overlapping.

[0041] The so-called PUCCH carrier handover can also refer to the following: When a terminal wants to transmit PUCCH at a specific transmission timing of a Pcell (which can also be a PScell ​​or PUCCH-Scell), the time slot of that specific transmission timing of the Pcell (which can also be a PScell ​​or PUCCH-Scell) becomes a DL time slot. Therefore, the terminal switches the cell from the Pcell (which can also be a PScell ​​or PUCCH-Scell) to any one of one or more Scells whose time slot is the same as that specific transmission timing and becomes a UL time slot (in the case of a PScell, it is an Scell ​​other than the PScell; in the case of a PUCCH-Scell, it is an Scell ​​other than the PUCCH-Scell). Furthermore, in embodiments of the present invention, the unit of the specific transmission timing is not limited to a time slot. For example, the specific transmission timing can be a timing per subframe or a timing per symbol.

[0042] Two methods for implementing PUCCH carrier switching are being investigated. The first method involves the base station dynamically instructing the terminal on the carrier used for PUCCH transmission. The second method involves the base station semi-statically setting the carrier for PUCCH transmission for the terminal. Additionally, in the following embodiments, "PUCCH transmission" and "transmitting PUCCH" can also refer to transmitting uplink control information via PUCCH.

[0043] The terminal may also notify the base station of terminal capability information (UE capability) that specifies information related to the terminal's capabilities in relation to PUCCH transmission.

[0044] For example, terminal capability information, as part of the terminal's specifications, may also specify whether the terminal supports settings related to the transmission of handover and control information. These settings may include, for example, switching the resources (e.g., carrier or cell) used in the transmission of control information. The resources used in the transmission of control information may also be referred to as "PUCCH carrier switching." Furthermore, terminal capability information may also specify information indicating the application of dynamic PUCCH carrier switching and / or semi-static PUCCH carrier switching.

[0045] The configuration operation for semi-static PUCCH carrier handover can also be based on the Radio Resource Control (RRC) that sets the PUCCH cell timing pattern of the PUCCH cell applying the semi-static PUCCH carrier handover. Furthermore, the configuration operation for semi-static PUCCH carrier handover can also be supported between cells with different parameter sets.

[0046] In PUCCH carrier handover, PUCCH resources can also be configured per UL BWP (Uplink Bandwidth Part) (e.g., each candidate cell and each UL BWP of that candidate cell).

[0047] In the case of PUCCH carrier handover based on dynamic indication of control information, the K1 value (offset) from PDSCH to HARQ-ACK can also be interpreted based on the parameter set (numerology) of the dynamically indicated target PUCCH cell. Alternatively, the control information can be PUCCH scheduling control information such as DCI (Downlink control information). Furthermore, the parameter set can also be understood as a time slot or SCS (Subcarrier Spacing).

[0048] <HARQ-ACK Codebook>

[0049] In URLLC, we study the enhancement of the terminal's HARQ-ACK codebook (HARQ-ACK CB) feedback functionality. Below, we provide an overview of Type 1 HARQ-ACK CB and Type 2 HARQ-ACK CB.

[0050] Additionally, Type 1 HARQ-ACK CB can also be referred to as semi-static HARQ-ACK CB. Type 2 HARQ-ACK CB can also be referred to as dynamic HARQ-ACK CB. Terminals can be instructed, for example, to apply either Type 1 HARQ-ACK CB or Type 2 HARQ-ACK CB via higher-level signaling such as RRC.

[0051] <Type 1 HARQ-ACK CB>

[0052] Figure 3 This is a diagram illustrating the overview of Type 1 HARQ-ACK CB. Figure 3 The term "scheduled" as shown refers, for example, to a time slot scheduled via DCI. CC stands for Component Carrier.

[0053] In Type 1 HARQ-ACK CB, the terminal generates the HARQ-ACK bits for the PDSCH regardless of whether a scheduled time slot (PDSCH) exists. For example, it can also be done as follows: Figure 3 As shown in the "HARQ-ACK codebook", the terminal sets NACK in the unscheduled PDSCH.

[0054] <Type 2 HARQ-ACK CB>

[0055] Figure 4 This is a diagram illustrating the overview of Type 2 HARQ-ACK CB. Figure 4 The (x, y) shown represents, for example, a time slot scheduled by DCI. x corresponds to the C-DAI value, and y corresponds to the T-DAI value. DAI is an abbreviation for Downlink assignment index. DAI, for example, represents the allocation of scheduled PDSCHs bundled with HARQ-ACK in HARQ-ACK CB.

[0056] In Type 2 HARQ-ACK CB, the terminal generates HARQ-ACK bits for the scheduled PDSCH. For example, it can also be done as follows: Figure 4 As shown in the "HARQ-ACK codebook", the terminal sets HARQ-ACK for the scheduled PDSCH.

[0057] Additionally, C-DAI is counted up starting from 1. For example, in the case of a 2-bit field, C-DAI repeats in the order of 1->2->3->0->… C-DAI is counted up for each time slot and for each DCI reception opportunity in each CC, even if the time slot changes, starting the count from the final value of the previous time slot. T-DAI represents the final value of C-DAI for each time slot.

[0058] Next, we will explain the generation example of Type 1 HARQ-ACK CB.

[0059] <Type 1 HARQ-ACK CB Generation>

[0060] Figure 5 , Figure 6 as well as Figure 7 This diagram illustrates a generation example of Type 1 HARQ-ACK CB. Figure 5 In this context, it is assumed that the parameter set of the serving cell is the same as that of the PUCCH cell. Figure 5 In this context, the set of K1 (the offset from PDSCH to HARQ-ACK) is {1, 2, 3, 4}.

[0061] exist Figure 6 In this scenario, it is assumed that the parameter set of the serving cell is different from that of the PUCCH cell. Figure 6 In the equation, the set of K1 is {1, 2, 3, 4, 5}.

[0062] The terminal can also generate HARQ-ACK CB based on the following steps: Step A, Step A-1, Step A-2, and Step B.

[0063] Step A

[0064] The terminal determines the HARQ-ACK opportunity (HARQ-ACK occasion) for candidate PDSCH reception. For example, in Figure 5 In this process, the terminal determines the n+4 time slot of the PUCCH cell. For example, in... Figure 6 In this process, the terminal determines the n+5 time slot of the PUCCH cell.

[0065] Step A-1

[0066] The terminal determines the PDSCH time slot window based on the K1 set. For example, the terminal interprets the K1 set from the parameter set of the PUCCH cell and determines... Figure 5 or Figure 6 The dashed box indicates the PDSCH time slot window.

[0067] Step A-2

[0068] The terminal determines the candidate PDSCH reception opportunity (candidate PDSCH reception occasion) for each K1 in each time slot. For example, ... Figure 7 M A,c As shown, the terminal determines the candidate PDSCH reception opportunity in each time slot.

[0069] In addition, the candidate PDSCH acceptance opportunity is Figure 8 This is explained in detail, but it is associated with the set RI (Row index) of the Time Domain Resource Allocation (TDRA) table. Candidate PDSCH reception opportunities within the TDRA table that overlap with the UL set by TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated are excluded. Among the candidate PDSCH reception opportunities that overlap in the time domain, the candidate PDSCH reception opportunities are determined based on specific rules.

[0070] Step B

[0071] The terminal can also determine (generate) the HARQ-ACK (HARQ-ACK information bits, HARQ-ACK CB) in each element of the determined candidate PDSCH reception opportunity. For example, the terminal can also determine the total number of HARQ-ACK information bits in the total number of O. ACKThe following type 1 HARQ-ACK CB (Type 1 HARQ-ACK CB) is generated.

[0072] [Mathematical formula 1]

[0073]

[0074] Figure 8 FIG. is a diagram illustrating a determination example of a candidate PDSCH reception opportunity for step A-2 (Step A-2). Figure 8 The table shown in the upper left of shows an example of TDRA. K0 represents the offset between the time slot of the DCI and the time slot of the PDSCH. Start represents the starting symbol within the time slot, and Length represents the length from the start (the number of symbols allocated to the PDSCH). The mapping type is associated with a mapping category that contains information related to the symbol that can be set as the starting symbol of the PDSCH within the time slot.

[0075] In Figure 8 The time slot format is shown in the upper right. In Figure 8 In the example of the time slot format shown, the last two symbols are semi-statically configured as UL.

[0076] Based on Figure 8 The candidate PDSCH reception opportunities for RI 0-8 of TDRA shown in the upper left of become Figure 8 Shown in the upper right of. However, the candidate PDSCH reception opportunities within the TDRA table that overlap with UL are excluded.

[0077] Therefore, the candidate PDSCH reception opportunities for RI2, RI3, and RI8 that overlap with UL are excluded, and the candidate PDSCH reception opportunities in a certain time slot become Figure 8 As shown in the lower right of. That is, the HARQ-ACKs for RI2, RI3, and RI8 are excluded from the generation set of the HARQ-ACK CB.

[0078] Among the candidate PDSCH reception opportunities that overlap in the time domain, the candidate PDSCH reception opportunities are determined based on specific rules. Therefore, the final candidate PDSCH reception opportunities become as Figure 8 Shown in the lower left of, and M in a certain time slot A,c Becomes M A,c ={0,1,{2,3}}.

[0079] <TBoMS (Transport Block processing over Multiple Slots)>[

[0080] In Release 17, a consensus was reached on studying coverage enhancement (CE) in NR. Furthermore, regarding coverage enhancement, 3GPP specifies TBoMS for transmitting a transport block (TB) via PUSCH allocated to N (N being multiple) time slots (e.g., Section 9 of 3GPP TS38.213). Additionally, TBS (Transport Block Size) is determined based on the PUSCH resource elements spanning N time slots.

[0081] In addition, Section 9 of TS 38.213 specifies that when a terminal transmits PUSCH in multiple time slots, and transmits PUCCH containing HARQ-ACK and / or CSI information in one or more time slots that overlap with the PUSCH transmission, the HARQ-ACK and / or CSI information shall be multiplexed in the PUSCH transmission in one or more time slots.

[0082] Figure 9 This is a diagram illustrating an example of PUSCH allocation based on TBoMS. Specifically, Figure 9 This illustrates an example of PUSCH allocation performed by TBoMS following both Type A repetition like TDRA (Time Domain Resource Allocation) and Type B repetition like TDRA. Additionally, Type A and B can refer to repetition types A and B.

[0083] Additionally, the number (N) of time slots allocated to 1TB is shown to the terminal via the higher-level parameter numberOfSlotsTBoMS.

[0084] The same code is assigned in each time slot.

[0085] UCI is multiplexed within overlapping PUSCHs in a single time slot. The number of coded modulation symbols for UCI is calculated based on the code block size of the overlapping time slot's UL-SCH.

[0086] TBoMS has the following advantages.

[0087] • Resources are allocated across multiple time slots, thus reducing the code rate.

[0088] • The gain of channel coding is increased due to the longer code sequence.

[0089] • Compared to sending multiple TBs, it can reduce the amount of headers at higher levels.

[0090] <CG PUSCH>

[0091] As mentioned above, in NR, in Release 16, the setting of CG PUSCH is specified (e.g., Non-Patent Document 1). There are Type 1 CG PUSCH and Type 2 CG PUSCH in CG PUSCH.

[0092] • Type 1 CG PUSCH

[0093] The transmission parameters for Type 1 CG PUSCH are provided by “configuredGrantConfig”, “pusch-Config”, and “rrc-ConfiguredUplinkGrant”. The activation and deactivation of Type 1 CG PUSCH depend on RRC-configuration, not on Downlink Control Information (DCI).

[0094] • Type 2 CG PUSCH

[0095] The transmission parameters for Type 2 CG PUSCH are provided by "configuredGrantConfig", "pusch-Config", and "activation DCI". Activation and deactivation of Type 2 CG PUSCH depend on RRC-configuration and DCI. One DCI can activate one CGPUSCH and deactivate multiple CG PUSCHs.

[0096] Furthermore, as mentioned above, in Release 17, XR is studied, and as a requirement for becoming an XR target, aspects such as capacity, latency, mobility, and energy efficiency are taken into consideration. Therefore, it is envisioned that CG PUSCH be applied in XR services, and that multiple CGs be used in the transmission of a single XR packet.

[0097] Figure 10 This is a diagram illustrating an example of CG PUSCH. The higher-level parameters `cg-nrofSlots` and `cg-nrofPUSCH-InSlot` are provided to the terminal. `cg-nrofSlots` represents the number of consecutive time slots allocated within a set CG cycle. `cg-nrofPUSCH-InSlot` represents the number of consecutive PUSCH allocations within a time slot. Figure 10 Examples of cg-nrofSlots = 3 and cg-nrofSlots = 2 are shown. The period set by CG PUSCH (the period during which CG PUSCH is sent, for example, ...) Figure 10 The three time slots shown repeat within the set CG cycle.

[0098] The initial PUSCH allocation is based on a higher-level setting that is based on TDRA or TS38.321 in Type 1 CG PUSCH. Alternatively, the initial PUSCH allocation is based on a UL license received in the DCI of Type 2 CG PUSCH. The remaining PUSCH allocations have the same length and mapping type as the initial PUSCH. Each PUSCH is appended seamlessly to the preceding PUSCH.

[0099] <CG-UCI for Unlicensed Spectrum>

[0100] In the current specification, regarding the transmission of CG-UCI (configured grand uplink control information) in the CG PUSCH, TS (technical specification) 38.212 stipulates that CG-UCI is transmitted in the CG PUSCH when "cg-RetransmissionTimer" is set as a higher-layer parameter. Here, cg-RetransmissionTimer is an example of a specific parameter. cg-RetransmissionTimer represents information related to the set retransmission timer. cg-RetransmissionTimer is set together with "harq-ProcID-Offset" as a higher-layer parameter. For cg-RetransmissionTimer, it is not set for operations under licensed spectrum, or it is not set simultaneously with "harq-ProcID-Offset2" as a higher-layer parameter. In addition, licensed spectrum corresponds to the band domain that requires license for use. On the other hand, unlicensed spectrum corresponds to the band domain that does not require license for use.

[0101] In other words, cg-RetransmissionTimer not being set can also correspond to the terminal operating within the licensed spectrum. Conversely, cg-RetransmissionTimer being set can also correspond to the terminal operating outside the licensed spectrum. The terminal operating outside the licensed spectrum can also correspond to the terminal operating within the unlicensed spectrum.

[0102] Furthermore, since cg-RetransmissionTimer is set together with harq-ProcID-Offset, setting cg-RetransmissionTimer corresponds to setting harq-ProcID-Offset. Additionally, since cg-RetransmissionTimer is not set simultaneously with harq-ProcID-Offset2, setting cg-RetransmissionTimer corresponds to harq-ProcID-Offset2 not being set, and harq-ProcID-Offset2 not being set corresponds to harq-ProcID-Offset2 being set.

[0103] <UCI reuse in PUSCH>

[0104] Regarding the UCI reported by the terminal in the PUSCH, offset values ​​are specified for determining the amount of resources used to multiplex HARQ-ACK information in the PUSCH, and offset values ​​are specified for determining the amount of resources used to multiplex CSI (Channel State Information) reports in the PUSCH.

[0105] Regarding the CSI report, it is envisioned that it is divided into two parts. Below, there are cases where the two parts of the CSI report are recorded as Part 1 CSI report and Part 2 CSI report. Alternatively, there are cases where the two parts of the CSI report are recorded as CSI part 1 and CSI part 2. Furthermore, there are cases where HARQ-ACK information is abbreviated as HARQ-ACK. Additionally, there are cases where HARQ ACK, CSI part 1, and CSI part 2 are recorded as HARQ ACK bits, CSI part 1 bits, and CSI part 2 bits, respectively. Furthermore, HARQ ACK bits, CSI part 1 bits, and CSI part 2 bits can each be a single bit of information or multiple bits of information.

[0106] In the current specification, during CG PUSCH transmission, the multiplexed HARQ-ACK, CSI part 1, and CSI part 2 are encoded separately. Furthermore, the resources for each of the multiplexed HARQ-ACK, CSI part 1, and CSI part 2 are determined separately.

[0107] Furthermore, in the current specification, there are cases where CG-UCI and HARQ-ACK are jointly encoded during the transmission of CG PUSCH.

[0108] Furthermore, in the current specification, priority is set for each UCI during rate matching. For example, in CGPUSCH transmission, the priority of HARQ-ACK in multiplexed HARQ-ACK, CSI part 1, and CSI part 2 is higher than that of CSI part 1 and CSI part 2, and the priority of CSI part 1 is higher than that of CSI part 2. Moreover, when CG-UCI and HARQ-ACK are jointly encoded, the priority of CG-UCI and HARQ-ACK is higher than that of CSI part 1 and CSI part 2.

[0109] <Consensus Matters>

[0110] In Release 18, the following points were agreed upon regarding CG enhancements in XR.

[0111] <Consensus Item 1>

[0112] At the RAN1 #111 meeting, the following consensus was reached on supporting the CG extension.

[0113] <Consensus Item 1-1>

[0114] Support: Dynamic indication of one or more unused CG PUSCH occasions based on Uplink Control Information (UCI) provided by the terminal.

[0115] For example, if an unused CG PUSCH opportunity exists, the terminal can use UCI to notify the unused CG PUSCH opportunity. Additionally, "UTO-UCI" is used as a term to indicate the UCI that provides information related to unused CG PUSCH opportunities. UTO is short for Unused Transmission Occasion.

[0116] <Consensus Items 1-2>

[0117] Supports multiple CG PUSCH events within a single CG PUSCH setting period.

[0118] For example, if multiple CG PUSCHs are set, the terminal can set multiple CG PUSCH timings during the period of one of the CG PUSCH settings.

[0119] <Consensus Item 2>

[0120] Furthermore, at the RAN1 #112bis meeting, the following consensus was reached regarding the dynamic indication of unused CG PUSCH timings.

[0121] <Consensus Item 2-1>

[0122] Option 1: If CG PUSCH is configured, include UTO-UCI in all CG PUSCHs sent (this is Option 1 of the corresponding consensus for RAN1#112). However, the details are not yet determined.

[0123] <Consensus Item 2-2>

[0124] UTO-UCI provides a bit map that corresponds to the CG PUSCH timing within a period / range. This bit indicates whether the CG PUSCH timing is "unused". However, details regarding the inclusion of the period / range have not yet been determined.

[0125] <Consensus Items 2-3>

[0126] For dynamic indication of unused CG PUSCH timings based on UCI, the "unused" CG PUSCH timings represented by the UTO-UCI within the CGPUSCH set by the CG PUSCH can be set as either continuous or discontinuous CG PUSCH timings in the time domain. However, it is not yet determined whether the period / range indicated by the UTO-UCI is limited to the period of a CG PUSCH setting. Furthermore, it is not yet determined whether or how unused CG PUSCH timings can be associated with multiple CG PUSCH settings.

[0127] <Consensus Item 3>

[0128] Furthermore, at the RAN1 #112bis meeting, the following consensus was reached regarding the dynamic indication of unused CG PUSCH timing.

[0129] The following consensus was reached: Regardless of whether other UCIs are reused in the PUSCH, the existing CG-UCI encoding and reuse process are reused for the encoding of "UTO-UCI" in the CG PUSCH. For example, the following adjustments can also be made during reuse.

[0130] • In the corresponding processing of encoding with CG-UCI and / or HARQ-ACK, use “UTO-UCI” instead of “CG-UCI”.

[0131] Regarding the determination of the β offset, the β offset is set for UTO-UCI. When the β offset is set for UTO-UCI, and UTO-UCI and HARQ-ACK are not jointly encoded, the β offset for UTO-UCI is used instead of the β offset for CG-UCI in β offset-related processing. Furthermore, when the β offset is set for UTO-UCI, and UTO-UCI and HARQ-ACK are jointly encoded, the β offset for HARQ-ACK is used instead of the β offset for CG-UCI in β offset-related processing.

[0132] Here, we will explain the joint encoding of CG-UCI and HARQ-ACK.

[0133] <Combined encoding of CG-UCI and HARQ-ACK>

[0134] When the UE is configured via ConfiguredGrantConfig to multiplex HARQ-ACK information in PUSCH transmissions containing CG-UCI (e.g., CGPUSCH transmissions), if the UE is provided with cg-UCI-Multiplexing, then the UE will multiplex the HARQ-ACK information in that PUSCH transmission (PUSCH transmission containing CG-UCI). Otherwise (e.g., if the UE is not provided with cg-UCI-Multiplexing), if the HARQ-ACK information and the PUSCH (e.g., PUSCH containing CG-UCI) have the same priority index, the UE will not transmit the PUSCH, but will multiplex the HARQ-ACK information in PUCCH transmissions or other PUSCH transmissions. Furthermore, if the HARQ-ACK information and the PUSCH (e.g., PUSCH containing CG-UCI) have different priority indices, the UE will not transmit the channel with the lower priority index.

[0135] For example, this describes a scenario where the UE supports the multiplexing of information with different priorities in PUCCH / PUSCH transmission. Furthermore, in the following description, the priority refers to either the smaller priority index or the larger priority index.

[0136] PUCCH transmissions with HARQ-ACK information, no repetition, and lower priority indexes overlap with PUCCH transmissions with only HARQ-ACK information, no repetition, and higher priority indexes.

[0137] In addition, it includes HARQ-ACK information with lower priority indexes, no repeated PUCCH transmissions and SR (Scheduling Request) and HARQ-ACK information with higher priority indexes, use of PUCCH resources with any of PUCCH formats 2 / 3 / 4, and no repeated PUCCH transmission overlap.

[0138] Furthermore, PUCCH transmissions with lower priority indices, no repetitions, and HARQ-ACK information overlap with PUSCH transmissions with higher priority indices, and vice versa.

[0139] The UE multiplexes HARQ-ACK information for indices with different priorities and SR information (if present) for the higher-priority index into the PUCCH transmission of the higher-priority index. Alternatively, the UE multiplexes HARQ-ACK information that it would provide in the PUCCH transmission of the lower-priority index into the PUSCH transmission of the higher-priority index.

[0140] In addition, the UE discards (if present) the CSI (Channel State Information) and / or SR carried in PUCCH transmissions with lower priority indexes.

[0141] If the UE needs to reuse the HARQ-ACK information of a higher priority index in the PUSCH transmission of a lower priority index, the UE will discard the negative SR (if it exists) carried in the PUCCH transmission of the higher priority index.

[0142] When the UE transmits a portion of the 2CSI report and a portion of the ICSI report that reuses the higher priority index, it discards the HARQ-ACK information of the lower priority index if it wants to reuse the HARQ-ACK information of the lower priority index.

[0143] In the PUSCH transmission of partial 2CSI reports and partial 1CSI reports of a lower priority index, if the UE wants to reuse the HARQ-ACK information of the lower priority index and the HARQ-ACK information of the higher priority index, the UE discards the partial 2CSI report of the lower priority index.

[0144] When a UE transmits a PUCCH using a PUCCH resource provided by a parameter such as n1PUCCH-AN with a higher priority index, and needs to reuse the HARQ-ACK information of a lower priority index, the UE discards the HARQ-ACK information of the lower priority index.

[0145] When the UE is reusing partial 2CSI reports, partial ICSI reports, and CG-UCI PUSCH transmissions of a lower priority index, and the UE wants to reuse the HARQ-ACK information of a higher priority index, the UE discards the partial 2CSI reports of the lower priority index.

[0146] <Research Matters>

[0147] During the 3GPP meeting, a consensus was reached on the following: regardless of whether other UCIs are reused in the PUSCH, the existing CG-UCI encoding and reuse process are reused for the encoding of "UTO-UCI" in the configured grant PUSCH.

[0148] Regarding this consensus, there is still room for research on the generation of bit sequences used for joint coding of HARQ-ACK and / or CG-UCI and UTO-UCI. Furthermore, joint coding can be equivalent to encoding as a whole or encoding together.

[0149] For example, if the generation of the bit sequence in each of the joint encoding of HARQ-ACK and UTO-UCI, the joint encoding of CG-UCI and UTO-UCI, and the joint encoding of HARQ-ACK, CG-UCI and UTO-UCI is ambiguous, inconsistencies in processing may occur between the terminal (e.g., UE) that encodes uplink control information containing at least one of HARQ-ACK, CG-UCI and UTO-UCI and the base station (e.g., gNB) that decodes it, potentially preventing the transmission of appropriate information.

[0150] Furthermore, there is room for research into the UE behavior when the joint encoding of UTO-UCI and HARQ-ACK is not set. Conversely, there is room for research into the UE behavior when the joint encoding of UTO-UCI and HARQ-ACK is set.

[0151] For example, if the joint encoding of UTO-UCI and HARQ-ACK is not set, and if the transmission method (e.g., multiplexing method) of each of UTO-UCI and HARQ-ACK is unclear, the UE may be unable to properly transmit at least one of UTO-UCI and HARQ-ACK.

[0152] Furthermore, for example, if the transmission method (e.g., multiplexing method) corresponding to the setting of joint encoding of UTO-UCI and HARQ-ACK, joint encoding (and / or multiplexing) of HARQ-ACK and other UCIs (e.g., CG-UCI) is unclear, the UE may be unable to properly transmit at least one of UTO-UCI, HARQ-ACK and other UCIs (e.g., CG-UCI).

[0153] Furthermore, for example, if multiplexing of HARQ-ACK and other UCIs (e.g., CG-UCI) is set, on the other hand, if joint encoding of UTO-UCI and HARQ-ACK is not set, the UE may be unable to properly transmit at least one of UTO-UCI, HARQ-ACK and other UCIs (e.g., CG-UCI).

[0154] Furthermore, for example, if the multiplexing of HARQ-ACK and other UCIs (e.g., CG-UCI) is not set, on the other hand, if the joint encoding of UTO-UCI and HARQ-ACK is set, the UE may be unable to properly transmit at least one of UTO-UCI, HARQ-ACK and other UCIs (e.g., CG-UCI).

[0155] In this embodiment, it will be explained as follows: For the research matters described above, by applying an appropriate transmission method (e.g., a multiplexing method) to at least one of HARQ-ACK, UTO-UCI and CG-UCI by the UE, it is possible to appropriately transmit uplink control information containing information related to the timing of unused CG PUSCH (e.g., UTO-UCI).

[0156] Additionally, "unused" may also include "not used" below. "CG PUSCH timing" may also be referred to as "CGPUSCH sending timing". "CG PUSCH setting" may also be referred to as "CG setting". "CG PUSCH setting period" may also be referred to as "CG PUSCH period" or "CG period". The CG period may also be periodic.

[0157] <Proposal 1>

[0158] Proposal 1 describes the scenarios where authorized spectrum is available, or where the CG-RetransmissionTimer is not set. In other words, this scenario is equivalent to the scenario where CG-UCI is not present.

[0159] In the case of Proposal 1, whether to support joint encoding of HARQ-ACK and UTO-UCI is set by a parameter. For example, this parameter could be an RRC parameter in the CG (configured grant) settings that differs from existing parameters, a new RRC parameter in the CG settings, or an existing parameter. Here, for example, the existing parameter could also be cg-UCI-Multiplexing. The parameter setting whether to support joint encoding of HARQ-ACK and UTO-UCI could also be an RRC parameter.

[0160] However, the parameter for setting whether to support the combined encoding of HARQ-ACK and UTO-UCI is not limited to the example set via RRC signaling. For example, this parameter can also be set (or provided) via other signaling (MAC CE / DCI, etc.). Furthermore, whether to support the combined encoding of HARQ-ACK and UTO-UCI can also be set explicitly or implicitly via one or more parameters.

[0161] The following, in Proposal 1, describes each of the cases where the joint encoding of HARQ-ACK and UTO-UCI is set, and the cases where the joint encoding of HARQ-ACK and UTO-UCI is not set.

[0162] <Proposal 1: Situations where joint coding is set>

[0163] When the joint encoding of HARQ-ACK and UTO-UCI is set, processing including process 1 and process 2 below can be applied. Additionally, the following processing can be used when the joint encoding of HARQ-ACK and UTO-UCI is set, and the UE needs to reuse HARQ-ACK information in a CG PUSCH containing UTO-UCI.

[0164] In addition, the scenario in which the UE reuses HARQ-ACK information in a CG PUSCH containing UTO-UCI can be the scenario in which the UE envisions sending a CG PUSCH containing UTO-UCI and HARQ-ACK information in the same transmission opportunity.

[0165] Solution 1:

[0166] The HARQ-ACK and UTO-UCI bits are combined. For example, the HARQ-ACK bit is appended to the UTO-UCI bit, or the UTO-UCI bit is appended to the HARQ-ACK bit. The bit resulting from the combination of the HARQ-ACK and UTO-UCI bits is called the "combined HARQ-ACK and UTO-UCI bit". In the "combined HARQ-ACK and UTO-UCI bit", the HARQ-ACK bit can be appended before or after the UTO-UCI bit.

[0167] Here, the HARQ-ACK bit represents the HARQ-ACK information. There can be one or more HARQ-ACK bits. Similarly, the UTO-UCI bit represents the UTO-UCI information. There can be one or more UTO-UCI bits. Furthermore, the HARQ-ACK, HARQ-ACK information, and HARQ-ACK bit can be interchanged. Additionally, the UTO-UCI and UTO-UCI bits can also be interchanged.

[0168] Solution 2:

[0169] In the traditional coding and rate matching process, the UE replaces the "HARQ-ACK bit" with the "combined HARQ-ACK and UTO-UCI bits". In other words, in the traditional coding and rate matching process, the processing related to the "HARQ-ACK bit" can also be applied to the "combined HARQ-ACK and UTO-UCI bits" by replacing the "HARQ-ACK bit" with the "combined HARQ-ACK and UTO-UCI bits".

[0170] For example, as in the current specification, in CG PUSCH transmission, where the multiplexed HARQ-ACK, CSI part 1, and CSI part 2 are encoded separately, the "combined bits of HARQ-ACK and UTO-UCI" are encoded separately from CSI part 1 and CSI part 2. Furthermore, as in the current specification, in rate matching, a priority is set for each UCI. For example, in CG PUSCH transmission, where the priority of HARQ-ACK is higher than that of CSI part 1 and CSI part 2 among the multiplexed HARQ-ACK, CSI part 1, and CSI part 2, the "combined bits of HARQ-ACK and UTO-UCI" are higher than those of CSI part 1 and CSI part 2.

[0171] As described above, when the joint coding of Proposal 1 is set, the behavior of the UE when the joint coding of UTO-UCI and HARQ-ACK is set can be clearly defined. For HARQ-ACK and UTO-UCI, the UE can apply an appropriate transmission method (e.g., multiplexing method) to appropriately transmit uplink control information containing information related to the timing of unused CG PUSCH (e.g., UTO-UCI).

[0172] <Proposal 1: Situation where joint coding is not set>

[0173] The case where the joint encoding of HARQ-ACK and UTO-UCI is not set is explained.

[0174] In this scenario, when the UE needs to reuse HARQ-ACK information in a CG PUSCH containing UTO-UCI, the processing applied differs depending on the priority settings of the CG PUSCH containing UTO-UCI and the HARQ-ACK information.

[0175] <Two cases with the same priority>

[0176] If the joint encoding of HARQ-ACK and UTO-UCI is not set, and the UE wants to reuse HARQ-ACK information in CGPUSCH containing UTO-UCI, and if the HARQ-ACK information and the PUSCH (CG PUSCH containing UTO-UCI) have the same priority index, it can apply any of the following three options.

[0177] <Two cases with the same priority: Option 1>

[0178] The UE does not send CG PUSCH. Furthermore, the UE multiplexes HARQ-ACK information in PUCCH transmission or in other PUSCH transmissions (e.g., PUSCH transmissions that are not CG PUSCH).

[0179] <Two cases with the same priority: Option 2>

[0180] The UE does not send UTO-UCI in the CG PUSCH. The UE multiplexes HARQ-ACK information in the CG PUSCH that does not contain UTO-UCI.

[0181] <Two cases with the same priority: Option 3>

[0182] The UE transmits a CG PUSCH containing UTO-UCI. The UE does not transmit (or discards) HARQ-ACK information. In this case, the UE may also reuse HARQ-ACK information in a PUCCH transmission or in other PUSCH transmissions (e.g., PUSCH transmissions that are not CGPUSCH).

[0183] <Two cases with different priorities>

[0184] If the joint encoding of HARQ-ACK and UTO-UCI is not set, and the UE wants to reuse HARQ-ACK information in CGPUSCH containing UTO-UCI, and HARQ-ACK information and PUSCH have different priority indices, it can apply either of the following two alternatives.

[0185] <Two cases with different priorities: Alt.1>

[0186] The UE does not transmit channels with low priority indices. In this case, the UE may also transmit channels with high priority indices. For example, if the priority index of the CG PUSCH containing the UTO-UCI is higher than the HARQ-ACK information, the UE transmits the CG PUSCH containing the UTO-UCI but does not transmit the HARQ-ACK information (discarding the HARQ-ACK information). Alternatively, if the priority index of the CG PUSCH containing the UTO-UCI is lower than the HARQ-ACK information, the UE does not transmit the CG PUSCH containing the UTO-UCI but transmits the HARQ-ACK information. For example, the HARQ-ACK information can be multiplexed in PUCCH transmissions or in other PUSCH transmissions (e.g., PUSCH transmissions that are not of that CG PUSCH).

[0187] <Two cases with different priorities: Alt.2>

[0188] The UE does not transmit UTO-UCI in the CG PUSCH. The UE multiplexes HARQ-ACK information in the CG PUSCH that does not contain UTO-UCI. For example, if the UE is provided with a parameter such as uci-MuxWithDiffPrio, the UE can also multiplex HARQ-ACK information in the CG PUSCH.

[0189] As described above, in the case where the joint coding of Proposal 1 is not set, the behavior of the UE when the joint coding of UTO-UCI and HARQ-ACK is not set can be clearly defined. For HARQ-ACK and UTO-UCI, the UE can apply an appropriate transmission method (e.g., multiplexing method) to appropriately transmit uplink control information containing information related to the timing of unused CG PUSCH (e.g., UTO-UCI).

[0190] For example, in the case where joint coding of Proposal 1 is not set, if a priority is set for each of UTO-UCI and HARQ-ACK, an appropriate transmission method corresponding to the priority can be applied, and the UE can appropriately transmit at least one of UTO-UCI and HARQ-ACK.

[0191] In Proposal 1, the UE's behavior can be clearly defined for both the case where the joint encoding of UTO-UCI and HARQ-ACK is set and the case where the joint encoding of UTO-UCI and HARQ-ACK is not set. Therefore, for HARQ-ACK and UTO-UCI, the UE can apply an appropriate transmission method (e.g., multiplexing method) to appropriately transmit uplink control information containing information related to the timing of unused CGPUSCH (e.g., UTO-UCI).

[0192] For example, in Proposal 1, the UE, based on a multiplexing method determined by the joint coding of HARQ-ACK (an example of acknowledgment information) and UTO-UCI (an example of first uplink control information indicating the timing of unused uplink signals), multiplexes HARQ-ACK and / or UTO-UCI onto a specific channel (e.g., CG PUSCH or other uplink channels) and transmits signals for that specific channel.

[0193] Furthermore, for example, in Proposal 1, when the joint encoding of HARQ-ACK and UTO-UCI is set, if the UE wants to multiplex and transmit HARQ-ACK information in a CG PUSCH containing UTO-UCI, it should multiplex HARQ-ACK in that CG PUSCH. Conversely, if the joint encoding of HARQ-ACK and UTO-UCI is not set, if the UE wants to multiplex and transmit HARQ-ACK information in a CG PUSCH containing UTO-UCI, it should multiplex HARQ-ACK to a CG PUSCH that excludes UTO-UCI, or to a channel different from that CG PUSCH.

[0194] <Proposal 2>

[0195] Proposal 2 addresses the scenarios involving unlicensed spectrum or when the CG-RetransmissionTimer is set. This scenario can also be equated to the possibility of CG-UCI.

[0196] In the case of Proposal 2, the UE applies joint encoding for both UTO-UCI and traditional CG-UCI. For example, this joint encoding is performed by appending UTO-UCI bits to CG-UCI bits, or by appending CG-UCI bits to UTO-UCI bits.

[0197] In Proposal 2, whether or not joint encoding of HARQ-ACK and UTO-UCI is supported is set by a parameter. For example, this parameter could be an RRC parameter in the CG settings that differs from existing parameters, a new RRC parameter in the CG settings, or an existing parameter. Here, for example, the existing parameter could also be cg-UCI-Multiplexing. The parameter setting whether joint encoding of HARQ-ACK and UTO-UCI is supported could also be an RRC parameter.

[0198] However, the parameter for setting whether to support the combined encoding of HARQ-ACK and UTO-UCI is not limited to the example set via RRC signaling. For example, this parameter can also be set (or provided) via other signaling (MAC CE / DCI, etc.). Furthermore, whether to support the combined encoding of HARQ-ACK and UTO-UCI can also be set explicitly or implicitly via one or more parameters.

[0199] This section describes the scenario where support for joint encoding of HARQ-ACK and UTO-UCI is set through another RRC parameter or a new RRC parameter. In this case, the following situations may occur.

[0200] Scenario 1 of Proposal 2: Other RRC parameters or new RRC parameters are set, while cg-UCI-Multiplexing is not set.

[0201] Scenario 2 of Proposal 2: Other RRC parameters or new RRC parameters are not set, but cg-UCI-Multiplexing is set.

[0202] Scenario 3 of Proposal 2: When other RRC parameters or new RRC parameters are set, and cg-UCI-Multiplexing is set.

[0203] <Scenario 1 of Proposal 2>

[0204] The so-called Proposal 2, Case 1, can be equivalent to setting the joint encoding of HARQ-ACK and UTO-UCI through other RRC parameters or new RRC parameters, on the other hand, not supporting the reuse of CG-UCI and HARQ-ACK information. Regarding Case 1, either of the following two alternatives should be applied.

[0205] <Alt.1 of Case 1 in Proposal 2>

[0206] The UE does not envision Scenario 1 of Proposal 2. In this case, the base station (e.g., gNB) does not perform operations such as setting only other RRC parameters or new RRC parameters, or setting one of cg-UCI-Multiplexing parameters without setting the other.

[0207] <Alt.2 of Case 1 in Proposal 2>

[0208] Scenario 1 allowing Proposal 2. In this case, the UE envisions Scenario 1 for Proposal 2. In this case, the base station (e.g., gNB) can also set other RRC parameters or new RRC parameters for the UE, without setting operations such as cg-UCI-Multiplexing. As in Alt.2, in Scenario 1 allowing Proposal 2, there are cases where different processing is applied based on the priority settings of each of the CG PUSCH and HARQ-ACK information containing UTO-UCI and CG-UCI.

[0209] <Alt.2 of Case 1 in Proposal 2: Cases with the same priority>

[0210] In Alt.2, if the UE needs to reuse HARQ-ACK information in a CG PUSCH containing both UTO-UCI and CG-UCI, and the HARQ-ACK information has the same priority index as the PUSCH (the CG PUSCH containing both UTO-UCI and CG-UCI), the UE will not send the PUSCH. Furthermore, the UE may reuse HARQ-ACK information in a PUCCH transmission or in other PUSCH transmissions (e.g., PUSCH transmissions that are not of the CG PUSCH). Alternatively, in this case, the UE may send a CG PUSCH containing both UTO-UCI and CG-UCI, but will not send (discard) HARQ-ACK information.

[0211] <Alt.2 of Proposal 2, Case 1: Cases with Different Priorities>

[0212] Furthermore, in Alt.2, if the UE needs to multiplex HARQ-ACK information within a CG PUSCH containing UTO-UCI, and the HARQ-ACK information has a different priority index than the PUSCH (a CG PUSCH containing both UTO-UCI and CG-UCI), the UE will not transmit the channel with the lower priority index. In this case, the UE can also transmit the channel with the higher priority index. For example, if the priority index of the CG PUSCH containing both UTO-UCI and CG-UCI is higher than the HARQ-ACK information, the UE transmits the CG PUSCH containing both UTO-UCI and CG-UCI without transmitting the HARQ-ACK information (discarding the HARQ-ACK information). Conversely, if the priority index of the CG PUSCH containing both UTO-UCI and CG-UCI is lower than the HARQ-ACK information, the UE does not transmit the CG PUSCH containing both UTO-UCI and CG-UCI, but transmits the HARQ-ACK information. For example, HARQ-ACK information can be multiplexed in PUCCH transmissions or in other PUSCH transmissions (e.g., PUSCH transmissions that are not part of this CGPUSCH).

[0213] As described above, in Proposal 2, Case 1 (e.g., the joint encoding of HARQ-ACK and UTO-UCI is set, on the other hand, the multiplexing of CG-UCI and HARQ-ACK information is not supported), a transmission method (e.g., a multiplexing method) corresponding to the setting of each can be applied, and the UE can appropriately transmit at least one of UTO-UCI, HARQ-ACK and other UCIs (e.g., CG-UCI).

[0214] <Scenario 2 of Proposal 2>

[0215] Proposal 2, scenario 2, refers to a situation where CG-UCI-Multiplexing is set, but other RRC parameters or new RRC parameters are not set. This scenario 2 can be equivalent to supporting the multiplexing of CG-UCI and HARQ-ACK information, but the joint encoding of HARQ-ACK and UTO-UCI is not set. For scenario 2, either of the following two alternatives should be applied.

[0216] <Alt.1 of Case 2 in Proposal 2>

[0217] UE does not assume scenario 2. In this scenario, the base station (e.g., gNB) does not perform operations such as setting only other RRC parameters or new RRC parameters, or setting only one of cg-UCI-Multiplexing parameters and not setting the other.

[0218] <Alt.2 of Case 2 in Proposal 2>

[0219] Case 2 where Proposal 2 is allowed. In this case, the UE envisions Case 2 of Proposal 2. In this case, the base station (e.g., gNB) can also perform operations such as setting cg-UCI-Multiplexing for the UE without setting other RRC parameters or new RRC parameters. As in Alt.2, in Case 2 where Proposal 2 is allowed, there are cases where different processing is applied based on the priority settings of each of the CG PUSCH and HARQ-ACK information containing UTO-UCI and CG-UCI.

[0220] <Alt.2 of Proposal 2, Case 2: Cases with the same priority>

[0221] In Alt.2, if the UE wants to reuse HARQ-ACK information in a CG PUSCH that contains UTO-UCI and CG-UCI, and the HARQ-ACK information and the PUSCH (the CG PUSCH containing UTO-UCI and CG-UCI) have the same priority index, it should apply any of the following three alternatives.

[0222] <Alt.2-1a>

[0223] The UE does not transmit this PUSCH (the CG PUSCH that includes UTO-UCI and CG-UCI). Furthermore, the UE reuses the HARQ-ACK information in PUCCH transmissions or in other PUSCH transmissions (e.g., PUSCH transmissions that are not this CG PUSCH).

[0224] <Alt.2-1b>

[0225] The UE does not send UTO-UCI in the CG PUSCH. In the CG PUSCH that does not contain UTO-UCI, the UE multiplexes the CG-UCI and HARQ-ACK information.

[0226] <Alt.2-1c>

[0227] The UE transmits a CG PUSCH containing both UTO-UCI and CG-UCI. The UE does not transmit (or discards) HARQ-ACK information. In this case, the UE may also reuse HARQ-ACK information in PUCCH transmissions or in other PUSCH transmissions (e.g., PUSCH transmissions that are not CG PUSCHs).

[0228] <Alt.2 of Proposal 2, Case 2: Cases with Different Priorities>

[0229] In addition, in Alt.2, if the UE wants to reuse HARQ-ACK information in a CG PUSCH that contains UTO-UCI and CG-UCI, and the HARQ-ACK information and the PUSCH (the CG PUSCH containing UTO-UCI and CG-UCI) have different priority indices, it should apply either of the following two alternatives.

[0230] <Alt.2-2a>

[0231] The UE does not transmit channels with low priority indices. In this case, the UE may also transmit channels with high priority indices. For example, if the priority index of a CG PUSCH containing both UTO-UCI and CG-UCI is higher than the HARQ-ACK information, the UE transmits the CG PUSCH containing both UTO-UCI and CG-UCI without transmitting HARQ-ACK information (or discards the HARQ-ACK information). For example, if the priority index of a CG PUSCH containing both UTO-UCI and CG-UCI is lower than the HARQ-ACK information, the UE does not transmit the CG PUSCH containing both UTO-UCI and CG-UCI, but transmits HARQ-ACK information. For example, HARQ-ACK information can be multiplexed in PUCCH transmissions or in other PUSCH transmissions (e.g., PUSCH transmissions that are not of that CG PUSCH).

[0232] <Alt.2-2b>

[0233] The UE does not transmit UTO-UCI in the CG PUSCH. The UE multiplexes HARQ-ACK information in the CG PUSCH. For example, when the UE is provided with uci-MuxWithDiffPrio, the UE can also multiplex HARQ-ACK information in the CG PUSCH. Furthermore, here, the CG PUSCH in which HARQ-ACK information is multiplexed includes CG-UCI. In other words, the UE multiplexes CG-UCI and HARQ-ACK information in the CGPUSCH that does not contain UTO-UCI.

[0234] As described above, in Case 2 of Proposal 2 (e.g., the joint encoding of HARQ-ACK and UTO-UCI is not set, on the other hand, the multiplexing of CG-UCI and HARQ-ACK information is supported), a transmission method (e.g., a multiplexing method) corresponding to the setting of each can be applied, and the UE can appropriately transmit at least one of UTO-UCI, HARQ-ACK and other UCIs (e.g., CG-UCI).

[0235] <Scenario 3 of Proposal 2>

[0236] Scenario 3 of Proposal 2 refers to a scenario where other or new RRC parameters are set, and CG-UCI-Multiplexing is configured. This scenario 3 can be equivalent to setting the joint encoding of HARQ-ACK and UTO-UCI, supporting the multiplexing of CG-UCI and HARQ-ACK information. Alternatively, scenario 3 can be replaced by a scenario where the multiplexing of HARQ-ACK, CG-UCI, and UTO-UCI is configured.

[0237] As in Proposal 2, Case 3, when the joint encoding of HARQ-ACK, CG-UCI and UTO-UCI is set, and the UE reuses HARQ-ACK information in the CG PUSCH containing UTO-UCI and CG-UCI, the following processing 1 and processing 2 can be applied.

[0238] Solution 1:

[0239] The bits of HARQ-ACK, CG-UCI, and UTO-UCI are merged. The case where the bits of HARQ-ACK, CG-UCI, and UTO-UCI are merged is referred to as the "merged bits of HARQ-ACK, CG-UCI, and UTO-UCI". For example, as a merging method, any of the following three alternatives can be applied.

[0240] <Alt.a>

[0241] The HARQ-ACK bit is appended after the CG-UCI bit, and the UTO-UCI bit is appended after the HARQ-ACK bit.

[0242] <Alt.b>

[0243] The UTO-UCI bit is appended after the CG-UCI bit, and the HARQ-ACK bit is appended after the UTO-UCI bit.

[0244] <Alt.c>

[0245] The CG-UCI bit is appended after the UTO-UCI bit, and the HARQ-ACK bit is appended after the CG-UCI bit.

[0246] Solution 2:

[0247] In the conventional coding and rate matching process, the UE replaces the "HARQ-ACK bit" with the "combined bits of HARQ-ACK, CG-UCI, and UTO-UCI". In other words, in the conventional coding and rate matching process, the processing related to the "HARQ-ACK bit" can also be applied to the "combined bits of HARQ-ACK, CG-UCI, and UTO-UCI" by replacing the "HARQ-ACK bit" with the "combined bits of HARQ-ACK, CG-UCI, and UTO-UCI". Furthermore, the conventional coding and rate matching process can also be the same as processing 2 in the case where joint coding is set in Proposal 1 above.

[0248] As described above, in Proposal 2, Situation 3 (e.g., joint encoding of HARQ-ACK and UTO-UCI is set, on the other hand, multiplexing of CG-UCI and HARQ-ACK information is supported), a transmission method (e.g., multiplexing method) corresponding to the setting of each can be applied, and the UE can appropriately transmit at least one of UTO-UCI, HARQ-ACK and other UCIs (e.g., CG-UCI).

[0249] Furthermore, the scenario where the joint coding of HARQ-ACK, CG-UCI, and UTO-UCI is set is not limited to scenario 3 in Proposal 2, where the UE is set to other RRC parameters or a new RRC parameter when support for the joint coding of HARQ-ACK and UTO-UCI is set through other RRC parameters or a new RRC parameter, and is thus set to cg-UCI-Multiplexing. The scenario where the joint coding of HARQ-ACK, CG-UCI, and UTO-UCI is set can also be where the UE is set to cg-UCI-Multiplexing when support for the joint coding of HARQ-ACK and UTO-UCI is set through cg-UCI-Multiplexing. Even in this scenario, the same processing as in scenario 3 of Proposal 2 can be performed.

[0250] In Proposal 2, for each of the three scenarios related to the setting of joint encoding of HARQ-ACK and UTO-UCI, and the setting of multiplexing of CG-UCI and HARQ-ACK information, the corresponding transmission method (e.g., multiplexing method) can be clearly defined and set. Therefore, the UE can appropriately transmit at least one of UTO-UCI, HARQ-ACK and other UCIs (e.g., CG-UCI).

[0251] For example, in Proposal 2, when joint coding of UTO-UCI (an example of first uplink control information) and CG-UCI (an example of second uplink control information) is applied, the UE reuses UTO-UCI and / or HARQ-ACK based on a reuse method determined by the setting of joint coding of UTO-UCI and HARQ-ACK and the setting of reuse of CG-UCI and HARQ-ACK.

[0252] <Overall Changes in Implementation Methods>

[0253] The following methods can be used to determine which of the multiple proposals, options, and / or choices to apply.

[0254] • It is set through high-level parameters.

[0255] • The UE is reported as a UE capability (UE capability(ies)).

[0256] • Recorded in the specification book.

[0257] • Determined based on the settings of higher-level parameters and the reported UE capabilities.

[0258] • The decision is made by combining two or more of the above-mentioned decisions.

[0259] • A time slot can also be replaced with a sub-time slot.

[0260] <UE capability>

[0261] The UE capability, which represents the capabilities of the UE, can contain the following information representing the UE's capabilities. Furthermore, the information representing the UE's capabilities can be equivalent to the information defining the UE's capabilities.

[0262] • Defines information on whether the UE supports dynamic indication of unused CG PUSCH timing based on UTO-UCI.

[0263] • Define whether the UE supports joint coding of HARQ-ACK and UTO-UCI.

[0264] • Defines whether the UE supports joint coding of HARQ-ACK, CG-UCI, and UTO-UCI.

[0265] <Examples of wireless communication systems>

[0266] The wireless communication system involved in this embodiment includes Figure 11 Base station 10 and shown Figure 12 The number of base stations 10 and terminals 20 shown is not particularly limited. For example, as Figure 1 As shown, it could also be a system in which two base stations 10 (base station 10-1 and base station 10-2) communicate with a terminal 20. The wireless communication system could be a wireless communication system following New Radio (NR) principles. For example, the wireless communication system could also be a wireless communication system following methods known as URLLC and / or IIoT.

[0267] Alternatively, wireless communication systems can also follow the protocols known as 5G, Beyond 5G, 5G Evolution, or 6G.

[0268] Base station 10 can also be referred to as an NG-RAN node, ng-eNB, eNodeB (eNB), or gNodeB (gNB). Terminal 20 can also be referred to as user equipment (UE). In addition, base station 10 can also be understood as a device contained in the network to which terminal 20 is connected.

[0269] Wireless communication systems can also include Next Generation Radio Access Network (NG-RAN). NG-RAN comprises multiple NG-RAN nodes, specifically gNBs (or ng-eNBs), connected to a 5G-compliant core network (5GC, not shown). Alternatively, NG-RAN and 5GC can also be referred to simply as "network".

[0270] Base station 10 and terminal 20 perform wireless communication. For example, the performed wireless communication follows NR (Normally Incoming). At least one of base station 10 and terminal 20 can also support massive MIMO (Multiple-Input Multiple-Output) for generating more directional beams (BM) by controlling wireless signals transmitted from multiple antenna elements. Furthermore, at least one of base station 10 and terminal 20 can also support carrier aggregation (CA) using multiple component carriers (CC). Additionally, at least one of base station 10 and terminal 20 can also support dual connectivity (DC) and the like for communication between terminal 20 and each of multiple base stations 10.

[0271] Wireless communication systems can also support multiple frequency bands. For example, a wireless communication system may support frequency range (FR) 1 and FR2. The frequency bands of each FR are as follows.

[0272] FR1: 410MHz~7.125GHz

[0273] FR2: 24.25GHz~52.6GHz

[0274] In FR1, sub-carrier spacing (SCS) of 15kHz, 30kHz, or 60kHz can be used, with a bandwidth (BW) of 5MHz to 100MHz. FR2 is, for example, a higher frequency than FR1. In FR2, SCS of 60kHz or 120kHz can be used, with a bandwidth (BW) of 50MHz to 400MHz. Furthermore, FR2 can also include an SCS of 240kHz.

[0275] The wireless communication system in this embodiment can also support frequency bands higher than FR2. For example, the wireless communication system in this embodiment can support frequency bands exceeding 52.6 GHz and up to 114.25 GHz. Such high-frequency bands can also be referred to as "FR2x".

[0276] Furthermore, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with larger sub-carrier spacing (SCS) than the examples described above can also be applied. Moreover, DFT-S-OFDM can be applied to both uplink and downlink, or either.

[0277] In wireless communication systems, a time division duplex (TDD) slot configuration pattern can also be set. For example, in the slot configuration pattern, a pattern can be specified that represents the order of two or more time slots among the time slots for transmitting downlink (DL) signals, time slots for transmitting uplink (UL) signals, time slots where DL signals, UL signals and guard symbols coexist, and time slots where the transmitted signals are flexibly changed.

[0278] Furthermore, in wireless communication systems, channel estimation for PUSCH (or PUCCH (Physical Uplink Control Channel)) can be performed using a demodulation reference signal (DMRS) per time slot. However, it is also possible to perform channel estimation for PUSCH (or PUCCH) using DMRS allocated to multiple time slots. Such channel estimation can also be referred to as joint channel estimation, or cross-slot channel estimation, among other names.

[0279] Terminal 20 can also transmit DMRS allocated to each of the multiple time slots in multiple time slots, so that base station 10 can perform joint channel estimation using DMRS.

[0280] Furthermore, in the wireless communication system, enhanced functions can be added to the feedback function from the terminal 20 to the base station 10. For example, enhanced functions can be added to the feedback function of the terminal for HARQ-ACK.

[0281] Next, the structures of base station 10 and terminal 20 will be described. Furthermore, the structures of base station 10 and terminal 20 described below are examples of functions associated with this embodiment. Functions not shown may also be present in base station 10 and terminal 20. Moreover, the functional divisions and / or names of functional units are not limited as long as they are functions capable of performing the operations involved in this embodiment.

[0282] <Base station structure>

[0283] Figure 11 This is a block diagram illustrating an example of the structure of the base station 10 according to this embodiment. The base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The base station 10 communicates wirelessly with the terminal 20 (see reference 103). Figure 12 ) to communicate.

[0284] Transmitting unit 101 sends downlink (DL) signals to terminal 20. For example, transmitting unit 101 transmits DL signals under the control of control unit 103.

[0285] The DL signal may also include, for example, downlink data signals and control information (e.g., Downlink Control Information (DCI)). Furthermore, the DL signal may also include scheduling information related to signal transmission of terminal 20 (e.g., UL authorization). Additionally, the DL signal may also include higher-layer control information (e.g., Radio Resource Control (RRC) control information). Furthermore, the DL signal may also include reference signals.

[0286] The channels used in transmitting DL signals may include, for example, data channels and control channels. For instance, the data channel may include a PDSCH (Physical Downlink Shared Channel), and the control channel may include a PDCCH (Physical Downlink Control Channel). For example, base station 10 uses the PDCCH to transmit control information and the PDSCH to transmit downlink data signals for terminal 20.

[0287] The reference signals included in the DL signal may include at least one of the following: Demodulation Reference Signal (DMRS), Phase Tracking Reference Signal (PTRS), Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information. For example, reference signals such as DMRS and PTRS are used for demodulation of downlink data signals and are transmitted using PDSCH.

[0288] The receiving unit 102 receives an uplink (UL) signal transmitted from the terminal 20. For example, the receiving unit 102 receives the UL signal under the control of the control unit 103.

[0289] The control unit 103 controls the communication operation of the base station 10, which includes the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102.

[0290] For example, the control unit 103 acquires data and control information from higher layers and outputs it to the transmitting unit 101. Furthermore, the control unit 103 outputs data and control information received from the receiving unit 102 to higher layers.

[0291] For example, the control unit 103 allocates resources (or channels) for transmitting and receiving DL signals and / or resources for transmitting and receiving UL signals based on signals received from the terminal 20 (e.g., data and control information) and / or data and control information obtained from higher layers. Information related to the allocated resources can be included in the control information sent to the terminal 20.

[0292] As an example of resource allocation used in the transmission and reception of UL signals, the control unit 103 sets the PUCCH resources. Information related to the PUCCH setting, such as the PUCCH cell timing mode (PUCCH setting information), can also be notified to the terminal 20 via RRC.

[0293] For example, in this embodiment, the base station 10 receives uplink control information (e.g., UCI) in the receiving unit 102. The received uplink control information may also be included in, for example, PUCCH and / or PUSCH. Furthermore, the uplink control information may also include at least one of HARQ-ACK, CG-UCI, and UTO-UCI.

[0294] <Terminal Structure>

[0295] Figure 12 This is a block diagram illustrating an example of the structure of the terminal 20 according to this embodiment. The terminal 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The terminal 20 communicates with the base station 10 wirelessly, for example.

[0296] The receiving unit 201 receives the DL signal transmitted from the base station 10. For example, the receiving unit 201 receives the DL signal under the control of the control unit 203.

[0297] The transmitting unit 202 transmits a UL signal to the base station 10. For example, the transmitting unit 202 transmits the UL signal under the control of the control unit 203.

[0298] The UL signal may include, for example, uplink data signals and control information (e.g., UCI). For example, it may include information related to the processing capabilities of terminal 20 (e.g., UE capability). In addition, the UL signal may also include reference signals.

[0299] The channels used in transmitting UL signals include, for example, data channels and control channels. For instance, the data channel includes PUSCH (Physical Uplink Shared Channel), and the control channel includes PUCCH (Physical Uplink Control Channel). For example, terminal 20 receives control information from base station 10 using PUCCH and transmits uplink data signals using PUSCH.

[0300] The reference signals included in the UL signal may include at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, reference signals such as DMRS and PTRS are used for demodulation of uplink data signals and are transmitted using an uplink channel (e.g., PUSCH).

[0301] The control unit 203 controls the communication operation of the terminal 20, which includes the receiving processing in the receiving unit 201 and the transmitting processing in the transmitting unit 202.

[0302] For example, control unit 203 obtains data and control information from higher layers and outputs it to transmitting unit 202. Furthermore, control unit 203 may output data and control information received from receiving unit 201 to higher layers, for example.

[0303] For example, control unit 203 controls the transmission of information fed back to base station 10. The information fed back to base station 10 may include, for example, HARQ-ACK, Channel State Information (CSI), and Scheduling Request (SR). The information fed back to base station 10 may be included in UCI. UCI is transmitted within the resources of PUCCH.

[0304] The control unit 203 configures the PUCCH resources based on configuration information received from the base station 10 (e.g., PUCCH cell timing mode configuration information notified via RRC and / or DCI). The control unit 203 determines the PUCCH resources to be used in transmitting information fed back to the base station 10. The transmitting unit 202, under the control of the control unit 203, transmits the information fed back to the base station 10 using the PUCCH resources determined by the control unit 203.

[0305] Furthermore, the channels used in transmitting DL signals and UL signals are not limited to the examples mentioned above. For instance, the channels used in transmitting DL signals and UL signals may include RACH (Random Access Channel) and PBCH (Physical Broadcast Channel). RACH can also be used, for example, to transmit Downlink Control Information (DCI) containing the Random Access Radio Network Temporary Identifier (RA-RNTI).

[0306] For example, in the terminal 20 of this embodiment, the control unit 203, based on the multiplexing method determined by the setting of the joint encoding of HARQ-ACK (an example of acknowledgment response information) and UTO-UCI (an example of first uplink control information indicating the timing of unused uplink signals), multiplexes HARQ-ACK and / or UTO-UCI to a specific channel (e.g., CGPUSCH or other uplink channels), and the transmitting unit 202 transmits signals for the specific channel.

[0307] Furthermore, for example, if the joint encoding of HARQ-ACK and UTO-UCI is set by the control unit 203, and the UE wants to multiplex and transmit HARQ-ACK information in a CG PUSCH containing UTO-UCI, then the control unit 203 will multiplex HARQ-ACK in that CG PUSCH. Furthermore, for example, if the joint encoding of HARQ-ACK and UTO-UCI is not set by the control unit 203, and the UE wants to multiplex and transmit HARQ-ACK information in a CG PUSCH containing UTO-UCI, then the control unit 203 will multiplex HARQ-ACK to a CG PUSCH that excludes UTO-UCI, or a channel different from that CG PUSCH.

[0308] Furthermore, for example, when the control unit 203 applies the joint encoding of UTO-UCI (an example of the first uplink control information) and CG-UCI (an example of the second uplink control information), it reuses UTO-UCI and / or HARQ-ACK based on the multiplexing method determined by the setting of the joint encoding of UTO-UCI and HARQ-ACK and the setting of multiplexing of CG-UCI and HARQ-ACK.

[0309] The above provides an explanation of this disclosure.

[0310] <Hardware architecture, etc.>

[0311] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by incorporating software into the aforementioned single device or multiple devices.

[0312] The functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural unit) that implements the sending function is called a transmitting unit or transmitter. Each of these functions is implemented in a way that is not particularly limited, as described above.

[0313] For example, the base station, terminal, etc. in one embodiment of this disclosure can also function as a computer for processing the communication method of this disclosure. Figure 13 This is a diagram illustrating an example of the hardware structure of a base station and a terminal according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0314] In addition, in the following description, the term "device" can be replaced with circuit, device, unit, etc. The hardware structure of base station 10 and terminal 20 can be configured to include one or more of the devices shown in the figure, or it can be configured not to include some of the devices.

[0315] The functions of base station 10 and terminal 20 are realized by reading specific software (programs) into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls communication based on communication device 1004, or controls at least one of reading and writing data in memory 1002 and storage device 1003.

[0316] The processor 1001, for example, enables the operating system to operate and control the computer as a whole. The processor 1001 may also be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, the control unit 103 and control unit 203 described above may also be implemented by the processor 1001.

[0317] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 203 of the terminal 20 can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks. The various processes described above refer to execution by one processor 1001, but they can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented using one or more chips. Additionally, programs can be transmitted from a network via electrical communication lines.

[0318] The memory 1002 may also be a computer-readable recording medium, such as at least one of ROM (Read-Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 can store programs (program code), software modules, etc., that are executable for implementing the communication method according to an embodiment of this disclosure.

[0319] Storage 1003 is a computer-readable recording medium, and may be comprised of at least one of the following: CD-ROM (Compact Disc ROM) or other optical discs; hard disk drives; flexible discs; optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs); smart cards; flash memory (e.g., cards, sticks, key drives); floppy disks; magnetic stripes; etc. Storage 1003 may also be referred to as an auxiliary storage device. The aforementioned storage medium may also be, for example, a database, server, or other suitable medium that includes at least one of memory 1002 and storage 1003.

[0320] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmitting unit 101, receiving unit 102, receiving unit 201, and transmitting unit 202 can also be implemented using the communication device 1004.

[0321] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED light, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., touch panel).

[0322] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses used between each device.

[0323] Furthermore, the base station 10 and the terminal 20 can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or a FPGA (Field Programmable Gate Array), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0324] (Supplement to the implementation method)

[0325] The embodiments of this disclosure have been described above. However, the disclosed invention is not limited to those embodiments, and those skilled in the art will understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, those values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not substantial in this disclosure; items described in two or more items may be combined as needed, and items described in one item may be applied to items described in other items (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. The operation of multiple functional units may also be physically performed by one component, or the operation of one functional unit may also be physically performed by multiple components. The processing order of the embodiments may be changed as long as there is no contradiction. For ease of explanation, functional block diagrams have been used to describe the base station and the terminal, but such a device may also be implemented by hardware, software, or a combination thereof. According to embodiments of this disclosure, software operated by a processor of a base station and software operated by a processor of a terminal, according to embodiments of this disclosure, can also 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 other suitable storage media.

[0326] <Information notification and signaling>

[0327] The notification of information is not limited to the implementation methods described in this disclosure, and other methods may also be used. For example, the notification of information may also be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block)), SIB (System Information Block)), other signals, or combinations thereof. In addition, RRC signaling may also be referred to as RRC messages, such as RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0328] <Application System>

[0329] The implementations described in this disclosure can also be applied to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (New Radio), New radio access (NX), Future generation radio access (FX), 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-Wide Band), Bluetooth (registered trademark), systems utilizing other suitable systems, and at least one next-generation system derived from, extended by, modified by, created by, or defined based on these. Furthermore, multiple systems may be combined (e.g., a combination of LTE and at least one of LTE-A with 5G, etc.) for application.

[0330] <Processing procedures, etc.>

[0331] The processing procedures, timing, flowcharts, etc., of the various methods / implementations described in this disclosure may be rearranged in order, provided they do not contradict each other. For example, for the methods described in this disclosure, an exemplary order is used to indicate the elements of various steps, but the order is not limited to the specific order indicated.

[0332] <Base Station Operation>

[0333] In this disclosure, specific operations are described as being performed by the base station, but sometimes, depending on the circumstances, they are also performed by its upper node. Clearly, in a network consisting of one or more network nodes having a base station, various operations performed for communication with a terminal can be performed by the base station and at least one of other network nodes besides the base station (e.g., consider an MME or S-GW, but not limited to these). The above illustration depicts a single other network node besides the base station, but it could also be a combination of multiple other network nodes (e.g., an MME and an S-GW).

[0334] <Direction of input / output>

[0335] Information (see the items under <Information, Signals>) can be output from higher (or lower) layers to lower (or higher) layers. It can also be input and output via multiple network nodes.

[0336] Processing of input and output information, etc.

[0337] Input and output information can be stored in a specific location (e.g., memory) or managed using a management table. Input and output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0338] <Judgment Method>

[0339] The determination can be made by a value represented by 1 bit (0 or 1), by a true or false value (Boolean: true or false), or by a numerical comparison (e.g., a comparison with a specific value).

[0340] <Changes in methods, etc.>

[0341] The various methods / implementations described in this disclosure can be used individually, in combination, or switched during execution. Furthermore, notification of specific information (e.g., a "It is X" notification) is not limited to explicit notification; it can also be implicit (e.g., not notifying the recipient of that specific information).

[0342] The present disclosure has been described in detail above, but it will be apparent 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 ways without departing from the spirit and scope of the present disclosure as determined by the claims. Therefore, the description in this disclosure is for illustrative purposes only and is not intended to be restrictive in any way.

[0343] <Software>

[0344] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0345] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0346] <Information, Signals>

[0347] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0348] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and the symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as a carrier frequency, cell, frequency carrier, etc.

[0349] <Systems, Networks>

[0350] The terms “system” and “network” are used interchangeably in this disclosure.

[0351] <Parameters, Channel Name>

[0352] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by an index.

[0353] The names used for the parameters described above are not limiting names in any respect. Furthermore, the mathematical formulas, etc., using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0354] <base station>

[0355] In this disclosure, the terms "base station (BS)," "wireless 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" are used interchangeably. There are also instances where terms such as macro cell, small cell, femtocell, and picocell are used to refer to base stations.

[0356] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its overall coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0357] In this disclosure, the information sent by the base station to the terminal can also be rewritten as the base station instructing the terminal to perform information-based control / operation.

[0358] <Mobile Station>

[0359] In this disclosure, the terms “Mobile Station (MS),” “user terminal,” “user equipment (UE),” and “terminal” are used interchangeably.

[0360] For those skilled in the art, there are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0361] <Base station / Mobile station>

[0362] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a communication device, etc. Additionally, at least one of the base station and the mobile station can also be equipment mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object with an arbitrary speed of movement. Furthermore, it naturally includes situations where the mobile body is stationary. Examples of mobile bodies include vehicles, transport vehicles, automobiles, autonomous two-wheelers, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trailers, rickshaws, ships (boats and other watercraft), airplanes, rockets, artificial satellites, drones (registered trademark), multi-rotor aircraft, quadcopters, balloons, and objects mounted on them, and are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operating commands. It can be a means of transportation (e.g., vehicles, airplanes, etc.), a mobile body that moves unmanned (e.g., drones, autonomous vehicles, etc.), or a robot (humanized or unmanned). In addition, at least one of the base station and the mobile station also includes a device that is not necessarily mobile during the communication operation. For example, at least one of the base station and the mobile station can also be an IoT (Internet of Things) device such as a sensor.

[0363] Furthermore, the base station in this disclosure can also be replaced by a terminal. For example, embodiments of this disclosure can also be applied to structures where communication between the base station and the terminal is replaced by communication between multiple terminals (e.g., also referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the structure can also be configured such that the terminal has the functions of the base station described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc., can also be replaced with side channel.

[0364] Similarly, the terminal in this disclosure can also be replaced by a base station. In this case, it can also be configured such that the base station 10 has the functions of the terminal 20 described above.

[0365] exist Figure 14 An example of the structure of vehicle 2001 is shown. For example... Figure 14 As shown, the vehicle 2001 includes a drive unit 2002, a steering control unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gear shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. The various methods / implementations described in this disclosure can also be applied to communication devices mounted on the vehicle 2001, for example, to the communication module 2013.

[0366] The drive unit 2002 is configured, for example, as an engine, a motor, or a combination of an engine and a motor. The steering unit 2003 is configured to include at least a steering wheel (also called a handlebar) and to perform directional control on at least one of the front and rear wheels based on the operation of the steering wheel by the user.

[0367] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021-2029 of the vehicle 2001 are input into the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

[0368] The signals from various sensors 2021 to 2029 include current signals from current sensor 2021 that senses the current of the motor, speed signals of the front and rear wheels obtained by speed sensor 2022, air pressure signals of the front and rear wheels obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depress amount signals obtained by accelerator pedal sensor 2029, brake pedal depress amount signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0369] The information service unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0370] The information service unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that implement output to the outside (e.g., display, speaker, LED light, touch panel, etc.).

[0371] The driver assistance system unit 2030 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-resolution (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 2030 sends and receives various information via a communication module 2013 and implements driver assistance or autonomous driving functions.

[0372] The communication module 2013 can communicate with the microprocessor 2031 and the constituent elements of the vehicle 2001 via a communication port. For example, the communication module 2013 sends and receives data with the drive unit 2002, steering control unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, microprocessor 2031 in the electronic control unit 2010, and memory (ROM, RAM) 2032 and sensors 2021 to 2029 in the vehicle 2001 via the communication port 2033.

[0373] The communication module 2013 can be controlled by the microprocessor 2031 of the electronic control unit 2010 and is a communication device capable of communicating with external devices. For example, it can send and receive various types of information wirelessly with external devices. The communication module 2013 can be located either inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

[0374] The communication module 2013 can also wirelessly transmit to an external device at least one of the signals input to the electronic control unit 2010 from the various sensors 2021-2029 described above, information obtained based on these signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2029, and the information service unit 2012 can also be referred to as input units that receive input. For example, the PUSCH transmitted by the communication module 2013 can also contain information based on the aforementioned input.

[0375] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it to the information service unit 2012 of the vehicle 2001. The information service unit 2012 can also be referred to as an output unit that outputs information (e.g., outputs information to devices such as displays and speakers based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)). Furthermore, the communication module 2013 stores the various information received from external devices in a memory 2032 that can be utilized by the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., of the vehicle 2001 based on the information stored in the memory 2032.

[0376] <Meaning and Explanation of Terms>

[0377] The terms "determining" and "determining" as used in this disclosure encompass a wide variety of actions. For example, "determining" or "determining" can include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining. Furthermore, "determining" or "determining" can include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory). Additionally, "determining" or "determining" can include actions such as resolving, selecting, choosing, establishing, and comparing. That is, "judgment" and "decision" can include situations where certain actions are regarded as having been "judged" or "decided". In addition, "judgment (decision)" can also be rewritten as "assuming", "expecting", "considering", etc.

[0378] The terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connection or combination between elements can be physical, logical, or a combination thereof. For example, “connected” can also be replaced by “access.” In the context of this disclosure, it is possible to consider two elements being mutually “connected” or “coupled” using at least one or more wires, cables, or printed electrical connections, and as several non-limiting and non-exclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (both visible and invisible) region.

[0379] <Reference Signal>

[0380] The reference signal can also be abbreviated as RS (Reference Signal), and can also be referred to as Pilot according to the applied standard.

[0381] <The meaning of "based on">

[0382] In the present disclosure, the description such as "based on" used herein does not mean "only based on" unless otherwise specified. In other words, the description such as "based on" means both "only based on" and "at least based on".

[0383] <"First", "Second">

[0384] Any reference to elements using the designations such as "first", "second", etc. used in the present disclosure does not comprehensively limit the quantity or order of these elements. These designations can be used in the present disclosure as a convenient method for distinguishing between two or more elements. Therefore, the reference to the first and second elements does not mean that only two elements can be adopted, or that the first element must take precedence over the second element in a certain form.

[0385] <Unit>

[0386] The "unit" in the structure of each of the above devices can also be replaced by "section", "circuit", "equipment", etc.

[0387] <Open form>

[0388] In the present disclosure, when using "include", "including", and their variants, these terms, like the term "comprising", mean inclusive. Further, the term "or" used in the present disclosure does not mean exclusive or.

[0389] <Time units such as TTI, frequency units such as RB, radio frame structure>

[0390] A radio frame can also be composed of one or more frames in the time domain. One or more frames in the time domain can also be referred to as sub - frames. Further, a sub - frame can also be composed of one or more time slots in the time domain. A sub - frame can also be a fixed time length (e.g., 1 ms) independent of numerology.

[0391] A parameter set can also be a set of communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, a parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0392] In the time domain, a time slot can also be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can also be a time unit based on a set of parameters.

[0393] A time slot can also contain multiple mini-time slots. Each mini-time slot can also consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can also consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-time slot can also be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-time slots can also be called PDSCH (or PUSCH) mapping type B.

[0394] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also be referred to by their respective other names.

[0395] For example, a subframe can also be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0396] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0397] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0398] In addition, where one time slot or one mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also be the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0399] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in LTE Rel.8-12), standard TTI, long TTI, normal subframe, standard subframe, long subframe, time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, mini time slot, sub-time slot, time slot, etc.

[0400] In addition, long TTIs (e.g., normal TTIs, subframes, etc.) can be replaced with TTIs with a duration of more than 1ms, and short TTIs (e.g., shortened TTIs, etc.) can be replaced with TTIs with a duration of less than long TTIs but more than 1ms.

[0401] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0402] Furthermore, the time domain of an RB can also contain one or more symbols, or it can be the length of a time slot, a mini-time slot, a subframe, or a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0403] In addition, one or more RBs can also be referred to as Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB Pair, RB Pair, etc.

[0404] Furthermore, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0405] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of that carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0406] A BWP can also include a UL BWP and a DL BWP. For a UE, one or more BWPs can be set within a single carrier.

[0407] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Furthermore, terms such as "cell" and "carrier" in this disclosure can be replaced with "BWP".

[0408] The structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0409] Maximum transmit power

[0410] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0411] <article>

[0412] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0413] "Differences"

[0414] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0415] Industrial availability

[0416] One aspect of this disclosure is useful for wireless communication systems.

[0417] Explanation of reference numerals in the attached figures

[0418] 10 Base stations; 20 Terminals; 101 and 202 Transmitting units; 102 and 201 Receiving units; 103 and 203 Control units.

Claims

1. A terminal, comprising: The control unit, based on a multiplexing method determined according to the setting of a first joint encoding of acknowledgment response information and first uplink control information indicating the timing of unused uplink signals, multiplexes the acknowledgment response information and / or the first uplink control information to a specific channel; and The transmitting unit transmits signals for the specific channel.

2. The terminal according to claim 1, wherein, When the first joint encoding is set, if the terminal needs to send a first uplink channel containing the first uplink control information and the acknowledgment information, the control unit will multiplex the acknowledgment information to the first uplink channel containing the first uplink control information.

3. The terminal according to claim 1, wherein, If the first joint encoding is not set, and the terminal needs to send a first uplink channel containing the first uplink control information and the acknowledgment information, the control unit will multiplex the acknowledgment information to a first uplink channel that excludes the first uplink control information, or a second uplink channel that is different from the first uplink channel.

4. The terminal according to claim 1, wherein, When applying the second joint encoding of the first uplink control information and the second uplink control information that is different from the first uplink control information, the control unit determines the multiplexing method according to the setting of the first joint encoding, the setting of multiplexing of the second uplink control information and the acknowledgment response information.

5. A communication method, terminal: Based on a multiplexing method determined by the setting of a first joint coding of acknowledgment information and first uplink control information, the acknowledgment information and / or the first uplink control information are multiplexed onto a specific channel; and Send a signal through the specific channel.

6. A communication system comprising a terminal and a base station, The terminal has: The control unit, based on a multiplexing method determined according to the setting of a first joint encoding of the acknowledgment response information and the first uplink control information, multiplexes the acknowledgment response information and / or the first uplink control information to a specific channel; and The transmitting unit transmits signals for the specific channel. The base station has the following features: The receiving unit receives signals from the specific channel.

Images