Terminal, communication method, and communication system

The terminal's multiplexing and encoding techniques for uplink control information address the challenge of transmitting unused CG PUSCH occasions, improving latency and resource utilization in advanced wireless communication standards, particularly for URLLC and XR applications.

WO2024236694A1PCT designated stage expired Publication Date: 2024-11-21NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2023/018122
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-15
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current communication systems face challenges in efficiently transmitting uplink control information, particularly regarding unused CG PUSCH occasions, which affects latency and resource utilization in advanced wireless communication standards like 5G and NR, especially in scenarios requiring low latency and high reliability such as URLLC and XR.

Method used

A terminal is configured to perform multiplexing based on a specific joint encoding setting for acknowledgment information and uplink control information, allowing for appropriate transmission of unused CG PUSCH occasions, using techniques like PUCCH carrier switching and joint encoding of HARQ-ACK and UTO-UCI, to optimize resource usage and reduce latency.

Benefits of technology

This approach enables efficient transmission of uplink control information, including indications of unused CG PUSCH occasions, thereby improving latency and resource utilization, particularly in low-latency and high-reliability scenarios like URLLC and XR, enhancing overall communication system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023018122_21112024_PF_FP_ABST
    Figure JP2023018122_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present invention provides a terminal comprising: a control unit that multiplexes confirmation response information and / or first uplink control information into a specific channel on the basis of a multiplexing method determined according to a first joint encoding setting of the confirmation response information and the first uplink control information, which indicates an unused uplink signal occasion; and a transmission unit that transmits a signal on the specific channel.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal, communication method and communication system

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

[0002] Long Term Evolution (LTE) has been specified for Universal Mobile Telecommunication System (UMTS) networks to achieve higher data rates and lower latency. Furthermore, successor systems to LTE are also being considered to achieve even greater bandwidth and speed than LTE. Examples of successor systems to LTE include LTE-Advanced (LTE-A), Future Radio Access (FRA), 5th generation mobile communication system (5G), 5G plus (5G+), Radio Access Technology (New-RAT), and New Radio (NR).

[0003] In NR, Release 16 specifies the configuration of a configured grant physical uplink scheduled channel (CG PUSCH) (see, for example, Non-Patent Document 1). The CG PUSCH includes a Type 1 CG PUSCH and a Type 2 CG PUSCH.

[0004] Additionally, Release 17 examines Extended Reality (XR), including virtual reality (VR) and mixed reality (MX), and considers XR scenarios, requirements, key performance indicators (KPIs), and evaluation methods. It states that the target requirements for XR should take into account capacity, latency (delay), mobility, and energy saving.

[0005] Furthermore, Release 18 agreed to support dynamic indication of unused CG PUSCH occasions by a terminal via Uplink Control Information (UCI).

[0006] TS38.331 V16.2.0 (2020-09)

[0007] There is room for further study on the method of transmitting uplink control information including information on unused CG PUSCH occasions.

[0008] One aspect of the present disclosure is to provide a terminal, a communication method, and a communication system that can appropriately transmit uplink control information including information on unused CG PUSCH occasions.

[0009] A terminal according to one aspect of the present disclosure includes a control unit that multiplexes the acknowledgement information and / or first uplink control information onto a specific channel based on a multiplexing method determined according to a setting of a first joint encoding of the acknowledgement information and first uplink control information indicating an occasion for an unused uplink signal, and a transmitting unit that transmits a signal on the specific channel.

[0010] FIG. 1 is a diagram illustrating an example of dual connectivity (DC). FIG. 2 is a diagram illustrating an example of PUCCH carrier switching. FIG. 3 is a diagram illustrating an overview of Type 1 HARQ-ACK CB. FIG. 4 is a diagram illustrating an overview of Type 2 HARQ-ACK CB. FIG. 5 is a diagram illustrating an example of generating a Type 1 HARQ-ACK CB. FIG. 6 is a diagram illustrating an example of generating a Type 1 HARQ-ACK CB. FIG. 7 is a diagram illustrating an example of determining candidate PDSCH reception opportunities in Step A-2. FIG. 8 is a diagram illustrating an example of PUSCH allocation by TBoMS. FIG. 9 is a diagram illustrating an example of CG PUSCH. FIG. 10 is a block diagram illustrating an example of the configuration of a base station according to the present embodiment. FIG. 11 is a block diagram illustrating an example of the configuration of a terminal according to the present embodiment. FIG. 12 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. FIG. 13 is a diagram illustrating an example of the configuration of a vehicle in an embodiment of the present invention.

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

[0012] In NR, Release 17 is studying various technologies for systems called Ultra-Reliable and Low Latency Communications (URLLC) and Industrial Internet of Things (IIoT). URLLC considers enhancing the terminal feedback function for Hybrid Automatic Repeat request-Acknowledgement (HARQ-ACK). HARQ-ACK is an example of information for acknowledgment (e.g., acknowledgment) for data received by the terminal. For these URLLC considerations, it was agreed to support dynamic and semi-static PUCCH carrier switching. Note that PUCCH carrier switching may also be called by other names, such as carrier switching for control information transmission.

[0013] PUCCH carrier switching is a technique applied when a base station communicates via multiple cells. Dual connectivity, which is an example of communication via multiple cells, and PUCCH carrier switching will be described below.

[0014] <Dual Connectivity> Figure 1 is a diagram showing an example of dual connectivity (DC). In the example of Figure 1, the base station 10-1 may be a master node (MN). The base station 10-2 may be a secondary node (SN). As shown in the example of Figure 1, in DC, carriers between different base stations are aggregated.

[0015] 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 Fig. 1, the terminal 20 establishes an RRC connection with the base station 10-1.

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

[0017] In the example of FIG. 1, the terminal 20 configures an Scell ​​in addition to a Pcell for the base station 10-1. The terminal 20 also configures an Scell ​​in addition to a PScell ​​for the base station 10-2. The terminal 20 transmits UCI of each carrier under the control of the base station 10-1 on the PUCCH of the Pcell. The terminal 20 also transmits UCI of each carrier under the control of the base station 10-2 on the PUCCH of the PScell. In the example of FIG. 1, the cell group (CG) under the control of the base station 10-1 may be referred to as a Master Cell-Group (MCG). The cell group under the control of the base station 10-2 may be referred to as a Secondary Cell-Group (SCG).

[0018] When DC is performed, terminal 20 may transmit PUCCH via a Pcell, a PScell, and / or a PUCCH-Scell. Generally, it is not expected that terminal 20 transmits PUCCH via an Scell ​​other than a Pcell, a PScell, and a PUCCH-Scell.

[0019] <PUCCH Carrier Switching> PUCCH carrier switching is being studied as a method for reducing the latency of HARQ-ACK feedback in the Time Division Duplex (TDD) system.

[0020] Fig. 2 is a diagram showing an example of PUCCH carrier switching. In the example of Fig. 2, a base station and a terminal communicate via cell 1 and cell 2. In the example of Fig. 2, cell 1 is a Pcell, and cell 2 is an Scell. The example of Fig. 2 also shows downlink (DL) slots and uplink (UL) slots in each cell.

[0021] In the example of FIG. 2 , the terminal receives data at timing S101 (receives a Physical Downlink Shared Channel (PDSCH)). The terminal attempts to transmit a HARQ-ACK for the data received at timing S101 at timing S102, but at timing S102, the slot of cell 1 is a downlink (DL) slot. Therefore, when the terminal transmits a HARQ-ACK in cell 1, the transmission of the HARQ-ACK is postponed until the transmission timing of a PUCCH in an uplink (UL) slot (e.g., timing S103 in FIG. 2 ), thereby increasing the latency of the HARQ-ACK transmission. Note that the transmission timing of a PUCCH in an uplink (UL) slot may be referred to as a PUCCH occasion.

[0022] In the example of Fig. 2, at timing S102, the slot of cell 2 is a UL slot. In the example of Fig. 2, if the terminal can transmit a HARQ-ACK for the data received at S101 in the PUCCH occasion at timing S102 of cell 2, the latency of the HARQ-ACK transmission can be reduced. URLLC requires low latency, particularly in the wireless section. For this reason, 3GPP (registered trademark) is considering PUCCH carrier switching, in which a terminal switches the carrier on which it transmits PUCCH, as an extension of URLLC technology.

[0023] In the following embodiments, "the same timing" may mean the exact same timing, or may mean that all or part of a time resource (for example, one or more symbols (which may be a resource with a time unit shorter than a symbol)) is the same or overlaps.

[0024] PUCCH carrier switching may refer to the case where, when a terminal attempts to transmit a PUCCH at a specific transmission timing of a Pcell (which may be a PScell ​​or a PUCCH-Scell), the slot of the specific transmission timing of the Pcell (which may be a PScell ​​or a PUCCH-Scell) is a DL slot, and therefore the terminal switches the cell from which the PUCCH is transmitted from the Pcell (which may be a PScell ​​or a PUCCH-Scell) to one of one or more Scells in which the slot with the same timing as the specific transmission timing is a UL slot (in the case of a PScell, an Scell ​​other than the PScell, and in the case of a PUCCH-Scell, an Scell ​​other than the PUCCH-Scell). Note that, in embodiments of the present invention, the unit of the specific transmission timing is not limited to a slot. For example, the specific transmission timing may be a timing in units of a subframe or a timing in units of a symbol.

[0025] Two methods are being considered for realizing PUCCH carrier switching. The first method is a method in which a base station dynamically instructs a terminal on a carrier for transmitting the PUCCH. The second method is a method in which a base station semi-statically sets a terminal on a carrier for transmitting the PUCCH. Note that in the following embodiments, "transmitting a PUCCH" and "transmitting a PUCCH" may refer to transmitting uplink control information via a PUCCH.

[0026] The terminal may notify the base station of terminal capability information (UE capability) that defines information about the terminal's capabilities regarding PUCCH transmission.

[0027] For example, information indicating whether the terminal supports switching of settings related to transmission of control information may be defined as the terminal capability information of the terminal. Switching of settings related to transmission of control information may be, for example, switching of resources (e.g., carriers or cells) used for transmitting the control information. Switching of resources used for transmitting the control information may be referred to as "PUCCH carrier switching." Furthermore, information indicating application of dynamic PUCCH carrier switching and / or semi-static PUCCH carrier switching may be defined as the terminal capability information of the terminal.

[0028] The configuration operation of the quasi-static PUCCH carrier switching may be based on the RRC (Radio Resource Control) setting of the PUCCH cell timing pattern of the PUCCH cell to which the quasi-static PUCCH carrier switching is applied, and the configuration operation of the quasi-static PUCCH carrier switching may be supported between cells of different numerologies.

[0029] In PUCCH carrier switching, PUCCH resources may be configured for each UL BWP (Uplink Bandwidth Part) (for example, for each candidate cell and the UL BWP of the candidate cell).

[0030] In the case of PUCCH carrier switching based on dynamic instruction of control information, the K1 value (offset) from PDSCH to HARQ-ACK may be interpreted based on the numerology of the dynamically instructed target PUCCH cell. Note that the control information may be control information for scheduling PUCCH, such as DCI (Downlink control information). Also, the numerology may be considered as slot or SCS (Subcarrier Spacing).

[0031] <HARQ-ACK Codebook> In URLLC, enhancements to the HARQ-ACK Codebook (HARQ-ACK CB) feedback function of terminals are being considered. Below, an overview of Type 1 HARQ-ACK CB and Type 2 HARQ-ACK CB is explained.

[0032] Note that Type 1 HARQ-ACK CB may be referred to as semi-static HARQ-ACK CB, and Type 2 HARQ-ACK CB may be referred to as dynamic HARQ-ACK CB. A terminal may be instructed which of Type 1 HARQ-ACK CB or Type 2 HARQ-ACK CB to apply by higher layer signaling such as RRC.

[0033] <Type 1 HARQ-ACK CB> Fig. 3 is a diagram illustrating an overview of Type 1 HARQ-ACK CB. "Scheduled" shown in Fig. 3 indicates, for example, a slot scheduled by DCI. CC indicates Component Carrier.

[0034] In Type 1 HARQ-ACK CB, the terminal generates a HARQ-ACK bit for the PDSCH regardless of whether a scheduled slot (PDSCH) exists. For example, the terminal may set a NACK for an unscheduled PDSCH, as shown in the "HARQ-ACK codebook" in FIG. 3.

[0035] <Type 2 HARQ-ACK CB> Figure 4 is a diagram illustrating an overview of Type 2 HARQ-ACK CB. (x, y) in Figure 4 indicates, for example, a slot scheduled by DCI. x corresponds to the C-DAI value, and y corresponds to the T-DAI value. DAI stands for Downlink Assignment Index. DAI indicates, for example, the allocation of a scheduled PDSCH in which HARQ-ACK is bundled into the HARQ-ACK CB.

[0036] In Type 2 HARQ-ACK CB, the terminal generates HARQ-ACK bits for the scheduled PDSCH. For example, the terminal may configure HARQ-ACK for the scheduled PDSCH as shown in the "HARQ-ACK codebook" in FIG. 4.

[0037] Note that C-DAI counts up from 1. For example, in the case of a 2-bit field, C-DAI repeats 1->2->3->0->... C-DAI is counted up for each slot at each opportunity to receive DCI for each CC, and even if the slot changes, it is counted up from the final value of the previous slot. T-DAI indicates the final value of C-DAI for each slot.

[0038] Next, an example of generating a Type 1 HARQ-ACK CB will be described.

[0039] <Type 1 HARQ-ACK CB Generation> Figures 5, 6, and 7 are diagrams explaining examples of generating a Type 1 HARQ-ACK CB. In Figure 5, it is assumed that the numerology of the serving cell and the numerology of the PUCCH cell are the same. In Figure 5, the set of K1 (offset from PDSCH to HARQ-ACK) is {1, 2, 3, 4}.

[0040] In Figure 6, it is assumed that the numerology of the serving cell and the numerology of the PUCCH cell are different. In Figure 6, the set of K1 is {1, 2, 3, 4, 5}.

[0041] The terminal may generate the HARQ-ACK CB based on the following Step A, Step A-1, Step A-2, and Step B.

[0042] Step A: The terminal determines a HARQ-ACK occasion for candidate PDSCH reception. For example, the terminal determines slot n+4 of the PUCCH cell in Fig. 5. For example, the terminal determines slot n+5 of the PUCCH cell in Fig. 6.

[0043] Step A-1: ​​The terminal determines the PDSCH slot window based on the K1 set. For example, the terminal interprets the K1 set in the numerology of the PUCCH cell and determines the PDSCH slot window shown in the dotted frame in Figure 5 or 6.

[0044] Step A-2: The terminal determines candidate PDSCH reception occasions for each K1 in each slot. For example, the terminal determines candidate PDSCH reception occasions for each K1 in FIG. A,c As shown in Figure 1, candidate PDSCH reception opportunities are determined for each slot.

[0045] Note that the candidate PDSCH reception opportunities are related to a set RI (Row index) in the Time Domain Resource Allocation (TDRA) table, as will be explained in Figure 8. Candidate PDSCH reception opportunities in the TDRA table that overlap with the UL configured by TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated are excluded. For candidate PDSCH reception opportunities that overlap in the time domain, the candidate PDSCH reception opportunities are determined based on specific rules.

[0046] Step B: The terminal may determine (generate) a HARQ-ACK (HARQ-ACK information bit, HARQ-ACK CB) for each element of the determined candidate PDSCH reception opportunity. For example, the terminal may determine (generate) a HARQ-ACK (HARQ-ACK information bit, HARQ-ACK CB) for each element of the determined candidate PDSCH reception opportunity. ACK In step S100, the next Type 1 HARQ-ACK CB may be generated.

[0047] Fig. 8 is a diagram illustrating an example of determining candidate PDSCH reception opportunities in Step A-2. The table shown in the upper left of Fig. 8 shows an example of TDRA. K0 indicates the offset between the DCI slot and the PDSCH slot. Start indicates the start symbol in the slot, and Length indicates the length from Start (the number of symbols allocated to the PDSCH). Mapping Type relates to the mapping type, which includes information about a symbol that can be set as the start symbol of the PDSCH in the slot.

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

[0049] The candidate PDSCH reception opportunities based on RI 0-8 of the TDRA shown in the upper left of Figure 8 are as shown in the upper right of Figure 8. However, candidate PDSCH reception opportunities in the TDRA table that overlap with the UL are excluded.

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

[0051] For candidate PDSCH reception opportunities that overlap in the time domain, the candidate PDSCH reception opportunities are determined based on a specific rule. Therefore, the final candidate PDSCH reception opportunities are as shown in the lower left of Figure 8, and M A,c is M A,c = {0,1,2,3}.

[0052] <TBoMS (Transport Block Processing over Multiple Slots)> It has been agreed that Coverage Enhancement (CE) for NR will be considered in Release 17. Regarding coverage enhancement, 3GPP specifies TBoMS, which transmits one transport block (TB) via a PUSCH allocated to N (N is a multiple) slots (e.g., Section 9 of 3GPP TS38.213). The transport block size (TBS) is determined based on the PUSCH resource elements spanning N slots.

[0053] Note that Section 9 of TS 38.213 specifies that when a terminal transmits a PUSCH in multiple slots and transmits a PUCCH including HARQ-ACK and / or CSI information in one or more slots that overlap with the PUSCH transmission, the HARQ-ACK and / or CSI information is multiplexed in the PUSCH transmission in the one or more slots.

[0054] 9 is a diagram showing an example of PUSCH allocation by TBoMS. Specifically, FIG. 9 shows an example of PUSCH allocation by TBoMS in accordance with Type A repetition like TDRA (Time Domain Resource Allocation) and Type B repetition like TDRA. Note that Types A and B may mean Repetition types A and B.

[0055] The number of slots (N) allocated to 1TB is indicated to the terminal by the upper layer parameter numberOfSlotsTBoMS.

[0056] Each slot is assigned the same symbol.

[0057] The UCI is multiplexed into the overlapping PUSCH in one slot, and the number of coded modulation symbols for the UCI is calculated based on the code block size of the UL-SCH in the overlapping slot.

[0058] TBoMS has the following advantages: ・Resources are allocated across multiple slots, which reduces the coding rate (code rate). ・Channel coding gain is improved by lengthening the code sequence. ・The amount of headers in the upper layer can be reduced compared to when multiple TBs are transmitted.

[0059] <CG PUSCH> As described above, in NR, the configuration of the CG PUSCH was specified in Release 16 (for example, Non-Patent Document 1). The CG PUSCH includes Type 1 CG PUSCH and Type 2 CG PUSCH.

[0060] Type 1 CG PUSCH The transmission parameters of Type 1 CG PUSCH are provided by "configuredGrantConfig", "pusch-Config", and "rrc-ConfiguredUplinkGrant". Activation and deactivation of Type 1 CG PUSCH depend on the RRC-configuration and are independent of Downlink Control Information (DCI).

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

[0062] As mentioned above, XR is being considered in Release 17, and the target requirements for XR are to take into account capacity, latency, mobility, and energy saving. Therefore, it is assumed that CG PUSCH will be applied to XR services, and that multiple CGs will be used for one XR packet transmission.

[0063] FIG. 10 is a diagram illustrating an example of a CG PUSCH. The higher layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot are provided to a terminal. cg-nrofSlots indicates the number of consecutive slots allocated in a configured CG cycle. cg-nrofPUSCH-InSlot indicates the number of consecutive PUSCH allocations within a slot. FIG. 10 shows an example where cg-nrofSlots = 3 and cg-nrofSlots = 2. The period of the CG PUSCH configuration (the period during which the CG PUSCH is transmitted, for example, 3 slots shown in FIG. 10) is repeated in the configured CG cycle.

[0064] The first PUSCH allocation is based on higher layer configuration based on TDRA or TS38.321 in Type 1 CG PUSCH, or based on UL grant received in DCI in Type 2 CG PUSCH. The remaining PUSCH allocations have the same length and mapping type as the first PUSCH. Each PUSCH is appended without gaps after the previous PUSCH.

[0065] <CG-UCI for Unlicensed Spectrum> In the current specification, regarding the transmission of configured grand uplink control information (CG-UCI) in the CG PUSCH, technical specification (TS) 38.212 specifies that CG-UCI is transmitted in the CG PUSCH when the upper layer parameter "cg-RetransmissionTimer" is configured. Here, cg-RetransmissionTimer is an example of a specific parameter. cg-RetransmissionTimer indicates information about the retransmission timer to be configured. cg-RetransmissionTimer is configured together with the upper layer parameter "harq-ProcID-Offset." cg-RetransmissionTimer is not configured for operation in licensed spectrum, or is not configured simultaneously with the upper layer parameter "harq-ProcID-Offset2." Note that licensed spectrum refers to bands that require a license for use. On the other hand, unlicensed spectrum refers to bands that do not require a license to be used.

[0066] In other words, not configuring the cg-RetransmissionTimer may correspond to the terminal operating in a licensed spectrum. In other words, configuring the cg-RetransmissionTimer may correspond to the terminal not operating in a licensed spectrum. Not operating in a licensed spectrum may correspond to the terminal operating in an unlicensed spectrum.

[0067] Furthermore, since cg-RetransmissionTimer is set together with harq-ProcID-Offset, the setting of cg-RetransmissionTimer may correspond to the setting of harq-ProcID-Offset. Furthermore, since cg-RetransmissionTimer is not set at the same time as harq-ProcID-Offset2, the setting of cg-RetransmissionTimer may correspond to the setting of harq-ProcID-Offset2, and the setting of cg-RetransmissionTimer may correspond to the setting of harq-ProcID-Offset2.

[0068] <Multiplexing of UCI in PUSCH> For UCI reported by a terminal in a PUSCH, an offset value for determining the number of resources for multiplexing HARQ-ACK information in the PUSCH and an offset value for determining the number of resources for multiplexing a CSI (Channel State Information) report in the PUSCH are defined.

[0069] It is assumed that the CSI report is divided into two parts. Hereinafter, the two parts of the CSI report may be referred to as Part 1 CSI report and Part 2 CSI report. Alternatively, the two parts of the CSI report may be referred to as CSI part 1 and CSI part 2. Furthermore, the HARQ-ACK information may be simply referred to as HARQ-ACK. Note that the HARQ ACK, CSI part 1, and CSI part 2 may be referred to as HARQ ACK bits, CSI part 1 bits, and CSI part 2 bits. Note that the HARQ ACK bits, CSI part 1 bits, and CSI part 2 bits may each be 1-bit information or multiple-bit information.

[0070] In the current specifications, in transmitting a CG PUSCH, the multiplexed HARQ-ACK, CSI part 1, and CSI part 2 are coded separately. Furthermore, the resources for the multiplexed HARQ-ACK, CSI part 1, and CSI part 2 are determined separately.

[0071] Furthermore, in the current specifications, in transmitting a CG PUSCH, the CG-UCI may be jointly encoded with the HARQ-ACK.

[0072] Furthermore, in the current specifications, a priority is assigned to each UCI in rate matching. For example, in transmitting a CG PUSCH, among the multiplexed HARQ-ACK, CSI part 1, and CSI part 2, the priority of HARQ-ACK is higher than CSI part 1 and CSI part 2, and the priority of CSI part 1 is higher than CSI part 2. Furthermore, when CG-UCI and HARQ-ACK are jointly encoded, the priority of CG-UCI and HARQ-ACK is higher than CSI part 1 and CSI part 2.

[0073] <Agreement> In Release 18, the following points were agreed upon regarding CG enhancements in XR:

[0074] <Agreement 1> At the RAN1 #111 meeting, the following agreement was reached regarding support for CG extensions:

[0075] <Agreement 1-1> Supports dynamic indication of one or more unused CG PUSCH occasions by a terminal based on Uplink Control Information (UCI).

[0076] For example, if there is an unused CG PUSCH occasion, the terminal may notify the unused CG PUSCH occasion using UCI. Note that the term "UTO-UCI" is used to refer to UCI that provides information about an unused CG PUSCH occasion. UTO stands for Unused Transmission Occasion.

[0077] <Agreement 1-2> Support for multiple CG PUSCH occasions (multiple CG PUSCHs) during a single CG PUSCH configuration period.

[0078] For example, when multiple CG PUSCHs are configured, the terminal may configure multiple CG PUSCH occasions during the period of one of the CG PUSCH configurations.

[0079] <Agreement 2> Furthermore, at the RAN1 #112bis meeting, the following agreement was reached regarding the dynamic indication of unused CG PUSCH occasions:

[0080] <Agreement 2-1> Option 1: In the case of CG PUSCH configuration, all transmitted CG PUSCHs include UTO-UCI (this is Option 1 of the corresponding agreement in RAN1#112). However, the details are yet to be determined.

[0081] <Agreement 2-2> The UTO-UCI provides a bitmap in which bits correspond to CG PUSCH occasions within a period / range. This bit indicates whether a CG PUSCH occasion is "unused" or not. However, details including the period / range are yet to be determined.

[0082] <Agreement 2-3> For dynamic indication of unused CG PUSCH occasions based on UCI, "unused" CG PUSCH occasions indicated by UTO-UCI within the CG PUSCH of a CG PUSCH configuration can be contiguous or non-contiguous CG PUSCH occasions in the time domain. However, it is not yet determined whether the duration / range indicated by UTO-UCI is limited to the duration of one CG PUSCH configuration. It is also not yet determined whether and how unused CG PUSCH occasions can be associated with multiple CG PUSCH configurations.

[0083] <Agreement 3> Furthermore, at the RAN1 #112bis meeting, the following agreement was reached regarding the dynamic indication of unused CG PUSCH occasions:

[0084] It has been agreed that the existing CG-UCI coding and multiplexing procedures will be reused for coding "UTO-UCI" in CG PUSCH, regardless of whether other UCIs are multiplexed onto the PUSCH. For example, the following adjustments may be made in the reuse: - In the processing procedures corresponding to coding of CG-UCI and / or HARQ-ACK, "UTO-UCI" is used instead of "CG-UCI". - Regarding the determination of the β offset, the β offset is configured for UTO-UCI. In the case where the β offset is configured for UTO-UCI, if the UTO-UCI and HARQ-ACK are not jointly encoded, the β offset for UTO-UCI is used in the β offset processing instead of the β offset for CG-UCI. Furthermore, in the case where the β offset is configured for UTO-UCI, if the UTO-UCI and HARQ-ACK are jointly encoded, the β offset for HARQ-ACK is used in the β offset processing instead of the β offset for CG-UCI.

[0085] Here, joint encoding of CG-UCI and HARQ-ACK will be described.

[0086] <Joint Encoding of CG-UCI and HARQ-ACK> When a UE is configured by ConfiguredGrantConfig and multiplexes HARQ-ACK information in a PUSCH transmission (e.g., a CG PUSCH transmission) including CG-UCI, if the UE is provided with cg-UCI-Multiplexing, the UE multiplexes HARQ-ACK information in that PUSCH transmission (PUSCH transmission including 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., a PUSCH including CG-UCI) have the same priority index, the UE does not transmit that PUSCH and multiplexes HARQ-ACK information in a PUCCH transmission or another PUSCH transmission. Furthermore, if the HARQ-ACK information and the PUSCH (e.g., a PUSCH including CG-UCI) have different priority indices, the UE does not transmit a channel with a lower priority index.

[0087] For example, consider a case where a UE supports multiplexing of information of different priorities in PUCCH / PUSCH transmission. In the following description, the priority refers to one of two priorities: a smaller priority index and a larger priority index.

[0088] A PUCCH transmission with HARQ-ACK information, no repetition, and a lower priority index overlaps with a PUCCH transmission with only HARQ-ACK information, no repetition, and a higher priority index.

[0089] In addition, non-repeated PUCCH transmissions containing HARQ-ACK information of a lower priority index overlap with non-repeated PUCCH transmissions containing SR (Scheduling Request) and HARQ-ACK information of a higher priority index using PUCCH resources having either PUCCH format 2, 3, or 4.

[0090] Also, PUCCH transmissions with a smaller priority index, no repetition, and HARQ-ACK information overlap with PUSCH transmissions with a larger priority index, and PUCCH transmissions with a larger priority index, no repetition, and HARQ-ACK information overlap with PUSCH transmissions with a smaller priority index.

[0091] The UE multiplexes HARQ-ACK information of different priority indices and SR information of a higher priority index, if present, into a PUCCH transmission of a higher priority index. Alternatively, the UE multiplexes HARQ-ACK information that the UE intends to provide in a PUCCH transmission of a lower priority index into a PUSCH transmission of a higher priority index. Alternatively, the UE multiplexes HARQ-ACK information that the UE intends to provide in a PUCCH transmission of a higher priority index into a PUSCH transmission of a lower priority index.

[0092] The UE also drops the CSI (Channel State Information) and / or SR carried in PUCCH transmissions of lower priority indices, if any.

[0093] If the UE attempts to multiplex HARQ-ACK information of a higher priority index in a PUSCH transmission of a lower priority index, the UE shall drop any negative SRs carried in the PUCCH transmission of the higher priority index, if any.

[0094] If the UE attempts to multiplex HARQ-ACK information of a lower priority index in a PUSCH transmission that multiplexes a Part 2 CSI report and a Part I CSI report of a higher priority index, the UE drops the HARQ-ACK information of the lower priority index.

[0095] When a UE attempts to multiplex HARQ-ACK information of a lower priority index with HARQ-ACK information of a higher priority index in a PUSCH transmission that multiplexes a Part 2 CSI report with a lower priority index with a Part 1 CSI report with a lower priority index, the UE drops the Part 2 CSI report with the lower priority index.

[0096] If the UE attempts to multiplex HARQ-ACK information of a lower priority index in a PUCCH transmission of a higher priority index using PUCCH resources provided by the parameter n1PUCCH-AN, the UE drops the HARQ-ACK information of the lower priority index.

[0097] In a PUSCH transmission in which a UE multiplexes a Part 2 CSI report, a Part I CSI report, and CG-UCI with a lower priority index, if the UE attempts to multiplex HARQ-ACK information with a higher priority index, the UE drops the Part 2 CSI report with the lower priority index.

[0098] <Items for consideration> At the 3GPP meeting, it was agreed that the existing CG-UCI coding and multiplexing procedures will be reused for coding of "UTO-UCI" in configured grant PUSCH, regardless of whether other UCIs are multiplexed onto the PUSCH.

[0099] In this agreement, there is room for consideration regarding the generation of a bit sequence for joint encoding of the HARQ-ACK and / or CG-UCI and the UTO-UCI, where the joint encoding may correspond to joint encoding or co-encoding.

[0100] For example, if the generation of bit sequences in each of joint coding of HARQ-ACK and UTO-UCI, joint coding of CG-UCI and UTO-UCI, and joint coding of HARQ-ACK, CG-UCI, and UTO-UCI is not clear, a processing discrepancy may occur between a terminal (e.g., a UE) that encodes uplink control information including at least one of HARQ-ACK, CG-UCI, and UTO-UCI, and a base station (e.g., a gNB) that decodes it, and appropriate information may not be transmitted.

[0101] Furthermore, there is room for further study on the behavior of a UE when joint encoding of UTO-UCI and HARQ-ACK is not configured. There is also room for further study on the behavior of a UE when joint encoding of UTO-UCI and HARQ-ACK is configured.

[0102] For example, in a case where joint encoding of UTO-UCI and HARQ-ACK is not configured, if the respective transmission methods (e.g., multiplexing methods) of UTO-UCI and HARQ-ACK are not clear, the UE may not be able to properly transmit at least one of UTO-UCI and HARQ-ACK.

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

[0104] Furthermore, for example, if multiplexing of HARQ-ACK and other UCI (e.g., CG-UCI) is configured while joint encoding of UTO-UCI and HARQ-ACK is not configured, the UE may not be able to properly transmit at least one of UTO-UCI, HARQ-ACK, and other UCI (e.g., CG-UCI).

[0105] Furthermore, for example, if multiplexing of HARQ-ACK and other UCI (e.g., CG-UCI) is not configured, but joint encoding of UTO-UCI and HARQ-ACK is configured, the UE may not be able to properly transmit at least one of UTO-UCI, HARQ-ACK, and other UCI (e.g., CG-UCI).

[0106] In this embodiment, in response to the above considerations, it will be explained that the UE can appropriately transmit uplink control information including information on unused CG PUSCH occasions (e.g., UTO-UCI) by applying an appropriate transmission method (e.g., a multiplexing method) to at least one of the HARQ-ACK, UTO-UCI, and CG-UCI.

[0107] In the following, "unused" may include "unused". A "CG PUSCH occasion" may be referred to as a "CG PUSCH transmission occasion". A "CG PUSCH configuration" may be referred to as a "CG configuration". A "period of a CG PUSCH configuration" may be referred to as a "CG PUSCH period" or a "CG period". A CG period may be periodic.

[0108] <Proposal 1> Proposal 1 describes the case of licensed spectrum or the case where the cg-RetransmissionTimer is not configured, which may correspond to the case where the CG-UCI does not exist.

[0109] In the case of Proposal 1, whether joint encoding of HARQ-ACK and UTO-UCI is supported is configured by a certain parameter. For example, the certain parameter may be an RRC parameter different from an existing parameter in a configured grant (CG) configuration, a new RRC parameter in a CG configuration, or an existing parameter. Here, the existing parameter may be, for example, cg-UCI-Multiplexing. The parameter that configures whether joint encoding of HARQ-ACK and UTO-UCI is supported may be an example of an RRC parameter.

[0110] However, the parameter for setting whether to support joint encoding of HARQ-ACK and UTO-UCI is not limited to being set by RRC signaling. For example, this parameter may be set (or provided) by other signaling (such as MAC CE / DCI). Furthermore, whether to support joint encoding of HARQ-ACK and UTO-UCI may be set explicitly or implicitly by one or more parameters.

[0111] Below, in Proposal 1, a case where joint encoding of HARQ-ACK and UTO-UCI is configured and a case where joint encoding of HARQ-ACK and UTO-UCI is not configured will be described.

[0112] <Proposal 1: Case where joint encoding is configured> In a case where joint encoding of HARQ-ACK and UTO-UCI is configured, the following processes including Process 1 and Process 2 may be applied. Note that the following processes may be processes when joint encoding of HARQ-ACK and UTO-UCI is configured and when the UE intends to multiplex HARQ-ACK information in a CG PUSCH including UTO-UCI.

[0113] In addition, the case where the UE intends to multiplex HARQ-ACK information in a CG PUSCH including UTO-UCI may be the case where the UE expects to transmit a CG PUSCH including UTO-UCI and HARQ-ACK information at the same transmission opportunity.

[0114] Process 1: The HARQ-ACK and UTO-UCI bits are combined. For example, the HARQ-ACK bit is added to the UTO-UCI bit. Alternatively, the UTO-UCI bit is added to the HARQ-ACK bit. The combined HARQ-ACK and UTO-UCI bit is called a "combined HARQ-ACK and UTO-UCI bit." In the "combined HARQ-ACK and UTO-UCI bit," the HARQ-ACK bit may be added before or after the UTO-UCI bit.

[0115] Here, the HARQ-ACK bit is a bit indicating HARQ-ACK information. There may be one or more HARQ-ACK bits. Furthermore, the UTO-UCI bit is a bit indicating UTO-UCI. There may be one or more UTO-UCI bits. Furthermore, the HARQ-ACK, HARQ-ACK information, and HARQ-ACK bit may be mutually replaced. Furthermore, the UTO-UCI and the UTO-UCI bit may be mutually replaced.

[0116] Process 2: The UE replaces the "HARQ-ACK bit" with the "combined bit of HARQ-ACK and UTO-UCI" in the legacy coding and rate matching procedures. In other words, in the processing procedure related to the "HARQ-ACK bit" in the legacy coding and rate matching procedures, the "HARQ-ACK bit" is replaced with the "combined bit of HARQ-ACK and UTO-UCI", so that the processing procedure related to the "HARQ-ACK bit" may be applied to the "combined bit of HARQ-ACK and UTO-UCI".

[0117] For example, in the current specifications, when the multiplexed HARQ-ACK, CSI part 1, and CSI part 2 are coded separately in the transmission of a CG PUSCH, the "combined bits of HARQ-ACK and UTO-UCI" are coded separately from CSI part 1 and CSI part 2. Furthermore, in rate matching, as in the current specifications, a priority is assigned to each UCI. For example, in the transmission of a CG PUSCH, when 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" is higher than that of CSI part 1 and CSI part 2.

[0118] As described above, in the case where the joint encoding of Proposal 1 is configured, the behavior of the UE when joint encoding of UTO-UCI and HARQ-ACK is configured can be clarified, and the UE can apply an appropriate transmission method (e.g., multiplexing method) to the HARQ-ACK and UTO-UCI, and can appropriately transmit uplink control information including information on unused CG PUSCH occasions (e.g., UTO-UCI).

[0119] <Proposal 1: Case where joint encoding is not configured> A case where joint encoding of HARQ-ACK and UTO-UCI is not configured will be described.

[0120] In this case, when a UE attempts to multiplex HARQ-ACK information in a CG PUSCH including UTO-UCI, different processes are applied depending on the settings of two priorities: the priority of the CG PUSCH including UTO-UCI and the priority of the HARQ-ACK information.

[0121] <When the two priorities are the same> In the case where joint encoding of HARQ-ACK and UTO-UCI is not configured, if the UE attempts to multiplex HARQ-ACK information in a CG PUSCH including UTO-UCI, and the HARQ-ACK information and its PUSCH (CG PUSCH including UTO-UCI) have the same priority index, one of the following three options may be applied.

[0122] <Option 1 when the two priorities are the same> The UE does not transmit a CG PUSCH, and either multiplexes HARQ-ACK information in a PUCCH transmission or multiplexes HARQ-ACK information in another PUSCH transmission (e.g., a PUSCH transmission that is not a CG PUSCH).

[0123] <When the two priorities are the same: Option 2> The UE does not transmit UTO-UCI in the CG PUSCH. The UE multiplexes HARQ-ACK information in the CG PUSCH that does not include UTO-UCI.

[0124] <Option 3 when the two priorities are the same> The UE transmits a CG PUSCH including UTO-UCI. The UE does not transmit (or drops) HARQ-ACK information. In this case, the UE may multiplex HARQ-ACK information in a PUCCH transmission or in another PUSCH transmission (e.g., a PUSCH transmission that is not a CG PUSCH).

[0125] <When the two priorities are different> In the case where joint encoding of HARQ-ACK and UTO-UCI is not configured, if the UE attempts to multiplex HARQ-ACK information in a CG PUSCH including UTO-UCI and the HARQ-ACK information and the PUSCH have different priority indexes, one of the following two alternatives may be applied.

[0126] <When the two priorities are different: Alt. 1> The UE does not transmit a channel with a lower priority index. In this case, the UE may transmit a channel with a higher priority index. For example, if the priority index of the CG PUSCH including UTO-UCI is higher than that of the HARQ-ACK information, the UE transmits the CG PUSCH including UTO-UCI but does not transmit the HARQ-ACK information (drops the HARQ-ACK information). For example, if the priority index of the CG PUSCH including UTO-UCI is lower than that of the HARQ-ACK information, the UE does not transmit the CG PUSCH including UTO-UCI but transmits the HARQ-ACK information. For example, the HARQ-ACK information may be multiplexed in a PUCCH transmission or may be multiplexed in another PUSCH transmission (e.g., a PUSCH transmission other than the CG PUSCH).

[0127] <When the two priorities are different: Alt. 2> The UE does not transmit UTO-UCI in the CG PUSCH. The UE multiplexes HARQ-ACK information in the CG PUSCH that does not include UTO-UCI. For example, if the UE is provided with a parameter called uci-MuxWithDiffPrio, the UE may multiplex HARQ-ACK information in the CG PUSCH.

[0128] As described above, in the case where the joint encoding of Proposal 1 is not configured, the behavior of the UE when the joint encoding of UTO-UCI and HARQ-ACK is not configured can be clarified, and the UE can apply an appropriate transmission method (e.g., multiplexing method) to the HARQ-ACK and UTO-UCI, and can appropriately transmit uplink control information including information on unused CG PUSCH occasions (e.g., UTO-UCI).

[0129] For example, in the case where the joint encoding of Proposal 1 is not configured and priorities are set for UTO-UCI and HARQ-ACK, an appropriate transmission method according to the priority can be applied, and the UE can appropriately transmit at least one of UTO-UCI and HARQ-ACK.

[0130] As described above, Proposal 1 clarifies the behavior of the UE for both the case where joint encoding of UTO-UCI and HARQ-ACK is configured and the case where joint encoding of UTO-UCI and HARQ-ACK is not configured. As a result, the UE can apply an appropriate transmission method (e.g., multiplexing method) to the HARQ-ACK and UTO-UCI, and can appropriately transmit uplink control information including information on unused CG PUSCH occasions (e.g., UTO-UCI).

[0131] For example, in Proposal 1, the UE multiplexes the HARQ-ACK and / or the UTO-UCI onto a specific channel (e.g., CG PUSCH or other uplink channel) based on a multiplexing method determined according to the setting of joint encoding of the HARQ-ACK (an example of acknowledgement information) and the UTO-UCI (an example of first uplink control information indicating the occasion of an unused uplink signal), and transmits the signal of the specific channel.

[0132] Furthermore, for example, in Proposal 1, when joint encoding of HARQ-ACK and UTO-UCI is configured and the UE intends to multiplex and transmit HARQ-ACK information in a CG PUSCH including UTO-UCI, the UE multiplexes the HARQ-ACK in the CG PUSCH. Also, when joint encoding of HARQ-ACK and UTO-UCI is not configured and the UE intends to multiplex and transmit HARQ-ACK information in a CG PUSCH including UTO-UCI, the UE multiplexes the HARQ-ACK into a CG PUSCH excluding UTI-UCI or into a channel different from the CG PUSCH.

[0133] <Proposal 2> Proposal 2 describes the case of unlicensed spectrum or the case where the cg-RetransmissionTimer is configured. In other words, this case may correspond to the case where CG-UCI may exist.

[0134] In the case of Proposal 2, the UE applies joint encoding for the UTO-UCI and the legacy CG-UCI, for example, by adding the UTO-UCI bits after the CG-UCI bits or by adding the CG-UCI bits after the UTO-UCI bits.

[0135] In the case of Proposal 2, whether joint encoding of HARQ-ACK and UTO-UCI is supported is configured by a certain parameter. For example, the certain parameter may be an RRC parameter different from an existing parameter in a CG configuration, a new RRC parameter in a CG configuration, or an existing parameter. Here, the existing parameter may be, for example, cg-UCI-Multiplexing. The parameter that configures whether joint encoding of HARQ-ACK and UTO-UCI is supported may be an example of an RRC parameter.

[0136] However, the parameter for setting whether to support joint encoding of HARQ-ACK and UTO-UCI is not limited to being set by RRC signaling. For example, this parameter may be set (or provided) by other signaling (such as MAC CE / DCI). Furthermore, whether to support joint encoding of HARQ-ACK and UTO-UCI may be set explicitly or implicitly by one or more parameters.

[0137] The case where support for joint encoding of HARQ-ACK and UTO-UCI is configured by another RRC parameter or a new RRC parameter will be described. In this case, the following cases may exist: Case 1 of Proposal 2: A case where another RRC parameter or a new RRC parameter is configured, but cg-UCI-Multiplexing is not configured; Case 2 of Proposal 2: A case where another RRC parameter or a new RRC parameter is not configured, but cg-UCI-Multiplexing is configured; Case 3 of Proposal 2: A case where another RRC parameter or a new RRC parameter is configured, and cg-UCI-Multiplexing is configured.

[0138] <Case 1 of Proposal 2> Case 1 of Proposal 2 may correspond to a case where joint encoding of HARQ-ACK and UTO-UCI is configured by another or new RRC parameter, but multiplexing of CG-UCI and HARQ-ACK information is not supported. For this case 1, one of the following two alternatives is applied:

[0139] <Alt. 1 of Case 1 of Proposal 2> The UE does not assume Case 1 of Proposal 2. In this case, the base station (e.g., gNB) does not perform an operation of configuring the UE with only one of another RRC parameter or new RRC parameter and cg-UCI-Multiplexing, and not configuring the other.

[0140] <Alt. 2 of Case 1 of Proposal 2> Case 1 of Proposal 2 is permitted. In this case, the UE assumes Case 1 of Proposal 2. In this case, the base station (e.g., gNB) may configure different RRC parameters or new RRC parameters for the UE and perform an operation of not configuring cg-UCI-Multiplexing. When Case 1 of Proposal 2 is permitted as in Alt. 2, the processing applied may differ depending on the respective priority settings of the CG PUSCH including UTO-UCI and CG-UCI, and the HARQ-ACK information.

[0141] <Alt.2 of Case 1 of Proposal 2: When Priorities are the Same> In Alt.2, if a UE attempts to multiplex HARQ-ACK information in a CG PUSCH including UTO-UCI and CG-UCI, and the HARQ-ACK information and that PUSCH (CG PUSCH including UTO-UCI and CG-UCI) have the same priority index, the UE does not transmit that PUSCH. Then, the UE multiplexes the HARQ-ACK information in a PUCCH transmission, or multiplexes the HARQ-ACK information in another PUSCH transmission (e.g., a PUSCH transmission other than the CG PUSCH). Alternatively, in this case, the UE transmits a CG PUSCH including UTO-UCI and CG-UCI, and does not transmit (drops) the HARQ-ACK information.

[0142] <Alt.2 of Case 1 of Proposal 2: Different Priorities> In addition, in Alt.2, when a UE attempts to multiplex HARQ-ACK information in a CG PUSCH including UTO-UCI, and the HARQ-ACK information and its PUSCH (CG PUSCH including UTO-UCI and CG-UCI) have different priority indices, the UE does not transmit a channel with a lower priority index. In this case, the UE may transmit a channel with a higher priority index. For example, when the priority index of the CG PUSCH including UTO-UCI and CG-UCI is higher than that of the HARQ-ACK information, the UE transmits the CG PUSCH including UTO-UCI and CG-UCI, but does not transmit the HARQ-ACK information (drops the HARQ-ACK information). For example, if the priority index of the CG PUSCH including the UTO-UCI and the CG-UCI is smaller than that of the HARQ-ACK information, the UE does not transmit the CG PUSCH including the UTO-UCI and the CG-UCI, but transmits the HARQ-ACK information. For example, the HARQ-ACK information may be multiplexed in a PUCCH transmission or may be multiplexed in another PUSCH transmission (e.g., a PUSCH transmission other than the CG PUSCH).

[0143] As described above, in Case 1 of Proposal 2 (e.g., a case where joint encoding of HARQ-ACK and UTO-UCI is configured, but multiplexing of CG-UCI and HARQ-ACK information is not supported), a transmission method (e.g., a multiplexing method) according to each configuration can be applied, and the UE can appropriately transmit at least one of UTO-UCI, HARQ-ACK, and other UCI (e.g., CG-UCI).

[0144] <Case 2 of Proposal 2> Case 2 of Proposal 2 is a case where cg-UCI-Multiplexing is configured, but other or new RRC parameters are not configured. This case 2 may correspond to a case where multiplexing of CG-UCI and HARQ-ACK information is supported, but joint encoding of HARQ-ACK and UTO-UCI is not configured. For this case 2, one of the following two alternatives is applied:

[0145] <Alt. 1 of Case 2 of Proposal 2> The UE does not assume Case 2. In this case, the base station (e.g., gNB) does not perform an operation of configuring the UE with only one of another RRC parameter or new RRC parameter and cg-UCI-Multiplexing, and not configuring the other.

[0146] <Alt. 2 of Case 2 of Proposal 2> Case 2 of Proposal 2 is permitted. In this case, the UE assumes Case 2 of Proposal 2. In this case, the base station (e.g., gNB) may perform an operation of configuring cg-UCI-Multiplexing for the UE without configuring different or new RRC parameters. When Case 2 of Proposal 2 is permitted as in Alt. 2, the processing applied may differ depending on the respective priority settings of the CG PUSCH including UTO-UCI and CG-UCI, and the HARQ-ACK information.

[0147] <Alt. 2 of Case 2 of Proposal 2: When the priorities are the same> In Alt. 2, when a UE attempts to multiplex HARQ-ACK information in a CG PUSCH including UTO-UCI and CG-UCI, and the HARQ-ACK information and its PUSCH (CG PUSCH including UTO-UCI and CG-UCI) have the same priority index, one of the following three alternatives is applied.

[0148] <Alt.2-1a> The UE does not transmit the PUSCH (CG PUSCH including UTO-UCI and CG-UCI), and then the UE multiplexes the HARQ-ACK information in a PUCCH transmission, or multiplexes the HARQ-ACK information in another PUSCH transmission (e.g., a PUSCH transmission other than the CG PUSCH).

[0149] <Alt.2-1b> The UE does not transmit UTO-UCI in the CG PUSCH. The UE multiplexes CG-UCI and HARQ-ACK information in the CG PUSCH that does not include UTO-UCI.

[0150] <Alt. 2-1c> The UE transmits a CG PUSCH including UTO-UCI and CG-UCI. The UE does not transmit (or drops) HARQ-ACK information. In this case, the UE may multiplex the HARQ-ACK information in a PUCCH transmission or in another PUSCH transmission (e.g., a PUSCH transmission other than a CG PUSCH).

[0151] <Alt. 2 of Case 2 of Proposal 2: When Priorities are Different> In addition, in Alt. 2, when a UE attempts to multiplex HARQ-ACK information in a CG PUSCH including UTO-UCI and CG-UCI, and the HARQ-ACK information and its PUSCH (CG PUSCH including UTO-UCI and CG-UCI) have different priority indexes, one of the following two Alternatives is applied.

[0152] <Alt. 2-2a> The UE does not transmit a channel with a lower priority index. In this case, the UE may transmit a channel with a higher priority index. For example, if the priority index of a CG PUSCH including UTO-UCI and CG-UCI is higher than that of HARQ-ACK information, the UE transmits the CG PUSCH including UTO-UCI and CG-UCI, but does not transmit HARQ-ACK information (or drops the HARQ-ACK information). For example, if the priority index of a CG PUSCH including UTO-UCI and CG-UCI is lower than that of HARQ-ACK information, the UE does not transmit the CG PUSCH including UTO-UCI and CG-UCI, but transmits HARQ-ACK information. For example, the HARQ-ACK information may be multiplexed in a PUCCH transmission or may be multiplexed in another PUSCH transmission (e.g., a PUSCH transmission other than the CG PUSCH).

[0153] <Alt. 2-2b> The UE does not transmit UTO-UCI in the CG PUSCH. The UE multiplexes HARQ-ACK information in the CG PUSCH. For example, if uci-MuxWithDiffPrio is provided to the UE, the UE may multiplex HARQ-ACK information in the CG PUSCH. Note that the CG PUSCH into which the HARQ-ACK information is multiplexed includes CG-UCI. In other words, the UE multiplexes CG-UCI and HARQ-ACK information in a CG PUSCH that does not include UTO-UCI.

[0154] As described above, in Case 2 of Proposal 2 (e.g., a case where joint encoding of HARQ-ACK and UTO-UCI is not configured, but multiplexing of CG-UCI and HARQ-ACK information is supported), a transmission method (e.g., a multiplexing method) according to each configuration can be applied, and the UE can appropriately transmit at least one of UTO-UCI, HARQ-ACK, and other UCI (e.g., CG-UCI).

[0155] <Case 3 of Proposal 2> Case 3 of Proposal 2 is a case in which different or new RRC parameters are configured and cg-UCI-Multiplexing is configured. This case 3 may correspond to a case in which joint encoding of HARQ-ACK and UTO-UCI is configured and multiplexing of CG-UCI and HARQ-ACK information is supported. This case 3 may correspond to a case in which joint encoding of HARQ-ACK, CG-UCI, and UTO-UCI is configured. Alternatively, this case 3 may be replaced with a case in which multiplexing of HARQ-ACK, CG-UCI, and UTO-UCI is configured.

[0156] As in Case 3 of Proposal 2, when joint encoding of HARQ-ACK, CG-UCI, and UTO-UCI is configured and the UE multiplexes HARQ-ACK information in a CG PUSCH including UTO-UCI and CG-UCI, the following processes 1 and 2 may be applied.

[0157] Process 1: Bits of the HARQ-ACK, CG-UCI, and UTO-UCI are combined. The combined bits of the HARQ-ACK, CG-UCI, and UTO-UCI are sometimes referred to as "combined bits of the HARQ-ACK, CG-UCI, and UTO-UCI." For example, one of the following three alternatives is applied as a combining method.

[0158] <Alt. a> The HARQ-ACK bit is added after the CG-UCI, and the UTO-UCI bit is added after the HARQ-ACK bit.

[0159] <Alt.b> The UTO-UCI bit is added after the CG-UCI bit, and the HARQ-ACK bit is added after the UTO-UCI bit.

[0160] <Alt.c> A CG-UCI bit is added after the UTO-UCI bit, and a HARQ-ACK bit is added after the CG-UCI bit.

[0161] Process 2: In the legacy encoding and rate matching procedure, the UE replaces the "HARQ-ACK bit" with a "combined bit of HARQ-ACK, CG-UCI, and UTO-UCI." In other words, in the processing procedure related to the "HARQ-ACK bit" in the legacy encoding and rate matching procedure, the "HARQ-ACK bit" is replaced with a "combined bit of HARQ-ACK, CG-UCI, and UTO-UCI," so that the processing procedure related to the "HARQ-ACK bit" may be applied to the "combined bit of HARQ-ACK, CG-UCI, and UTO-UCI." Note that the legacy encoding and rate matching procedure may be the same as Process 2 in the case where joint encoding of Proposal 1 is configured, as described above.

[0162] As described above, in Case 3 of Proposal 2 (e.g., a case where joint encoding of HARQ-ACK and UTO-UCI is configured while multiplexing of CG-UCI and HARQ-ACK information is supported), a transmission method (e.g., a multiplexing method) according to each configuration can be applied, and the UE can appropriately transmit at least one of UTO-UCI, HARQ-ACK, and other UCI (e.g., CG-UCI).

[0163] Note that the case in which joint encoding of HARQ-ACK, CG-UCI, and UTO-UCI is configured is not limited to the case in which support for joint encoding of HARQ-ACK and UTO-UCI is configured by another RRC parameter or a new RRC parameter, and another RRC parameter or a new RRC parameter is configured in the UE, and cg-UCI-Multiplexing is configured, as in Case 3 of Proposal 2. The case in which joint encoding of HARQ-ACK, CG-UCI, and UTO-UCI is configured may also be the case in which support for joint encoding of HARQ-ACK and UTO-UCI is configured by cg-UCI-Multiplexing, and cg-UCI-Multiplexing is configured in the UE. Even in this case, processing similar to that in Case 3 of Proposal 2 may be performed.

[0164] As described above, in Proposal 2, the transmission method (e.g., the multiplexing method) according to the setting can be clarified for each of the three cases 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, so that the UE can appropriately transmit at least one of UTO-UCI, HARQ-ACK, and other UCI (e.g., CG-UCI).

[0165] For example, in Proposal 2, when joint encoding of UTO-UCI (an example of first uplink control information) and CG-UCI (an example of second uplink control information) is applied, the UE multiplexes UTO-UCI and / or HARQ-ACK based on a multiplexing method determined according to the setting of joint encoding of UTO-UCI and HARQ-ACK and the setting of multiplexing of CG-UCI and HARQ-ACK.

[0166] <Variations of the Overall Embodiment> Which of a plurality of proposals is applied, which of a plurality of options is applied, and / or which of a plurality of choices is applied may be determined in the following manner.

[0167] - Configured by higher layer parameters - Reported by the UE as UE capability(ies) - Described in the specification - Determined based on the higher layer parameter configuration and the reported UE capability - Determined by a combination of two or more of the above - Slots may be replaced by sub-slots

[0168] <UE capability> UE capability indicating the capabilities of the UE may include the following information indicating the capabilities of the UE: Note that the information indicating the capabilities of the UE may correspond to information defining the capabilities of the UE.

[0169] Information defining whether the UE supports reporting of dynamic indication of unused CG PUSCH occasions by UTO-UCI. Information defining whether the UE supports joint encoding of HARQ-ACK and UTO-UCI. Information defining whether the UE supports joint encoding of HARQ-ACK, CG-UCI and UTO-UCI.

[0170] <Example of Wireless Communication System> A wireless communication system according to this embodiment includes a base station 10 shown in FIG. 11 and a terminal 20 shown in FIG. 12. The number of base stations 10 and the number of terminals 20 are not particularly limited. For example, as shown in FIG. 1, the system may be one in which two base stations 10 (base station 10-1 and base station 10-2) communicate with one terminal 20. The wireless communication system may be a wireless communication system conforming to New Radio (NR). For example, the wireless communication system may be a wireless communication system conforming to a method called URLLC and / or IIoT.

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

[0172] The base station 10 may be called an NG-RAN Node, ng-eNB, eNodeB (eNB), or gNodeB (gNB). The terminal 20 may be called User Equipment (UE). The base station 10 may also be considered as a device included in a network to which the terminal 20 is connected.

[0173] The wireless communication system may include a Next Generation-Radio Access Network (hereinafter, referred to as NG-RAN). The NG-RAN includes multiple NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC, not shown). Note that the NG-RAN and 5GC may be simply referred to as a "network."

[0174] The base station 10 performs wireless communication with the terminal 20. For example, the wireless communication performed complies with NR. At least one of the base station 10 and the terminal 20 may support Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements. Furthermore, at least one of the base station 10 and the terminal 20 may support Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CC). Furthermore, at least one of the base station 10 and the terminal 20 may support Dual Connectivity (DC), which performs communication between the terminal 20 and each of multiple base stations 10.

[0175] The wireless communication system may support multiple frequency bands. For example, the wireless communication system supports Frequency Range (FR) 1 and FR2. The frequency bands of each FR are, for example, as follows: FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz to 52.6 GHz

[0176] FR1 may use a sub-carrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and may use a bandwidth (BW) of 5 MHz to 100 MHz. FR2, for example, is a higher frequency than FR1. FR2 may use an SCS of 60 kHz or 120 kHz, and may use a bandwidth (BW) of 50 MHz to 400 MHz. FR2 may also include an SCS of 240 kHz.

[0177] The wireless communication system according to this embodiment may support a frequency band higher than the FR2 frequency band. For example, the wireless communication system according to this embodiment may support a frequency band exceeding 52.6 GHz up to 114.25 GHz. Such a high frequency band may be called "FR2x."

[0178] Alternatively, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) having a larger Sub-Carrier Spacing (SCS) than the above-mentioned example may be applied. Furthermore, DFT-S-OFDM may be applied to both the uplink and the downlink, or to either one of them.

[0179] In a wireless communication system, a slot configuration pattern for time division duplexing (TDD) may be set. For example, the slot configuration pattern may specify a pattern indicating an order of two or more slots among a slot for transmitting a downlink (DL) signal, a slot for transmitting an uplink (UL) signal, a slot in which a DL signal, a UL signal, and a guard symbol are mixed, and a slot in which a signal to be transmitted is changed to flexible.

[0180] In addition, in a wireless communication system, a demodulation reference signal (DMRS) can be used for each slot to perform channel estimation of a PUSCH (or a PUCCH (Physical Uplink Control Channel)), and further, a DMRS allocated to each of multiple slots can be used to perform channel estimation of a PUSCH (or a PUCCH). Such channel estimation may be called joint channel estimation, or may be called by another name such as cross-slot channel estimation.

[0181] The terminal 20 may transmit, in multiple slots, the DMRS allocated to each of the multiple slots so that the base station 10 can perform joint channel estimation using the DMRS.

[0182] Furthermore, in the wireless communication system, an enhanced function may be added to the feedback function from the terminal 20 to the base station 10. For example, an enhanced function may be added to the feedback of the terminal regarding HARQ-ACK.

[0183] Next, the configurations of the base station 10 and the terminal 20 will be described. Note that the configurations of the base station 10 and the terminal 20 described below are examples of functions related to this embodiment. The base station 10 and the terminal 20 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to this embodiment.

[0184] <Configuration of Base Station> Fig. 11 is a block diagram showing an example of the configuration of base station 10 according to this embodiment. Base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. Base station 10 communicates with terminal 20 (see Fig. 12) wirelessly.

[0185] The transmitter 101 transmits a downlink (DL) signal to the terminal 20. For example, the transmitter 101 transmits the DL signal under the control of the controller 103.

[0186] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating scheduling related to signal transmission of the terminal 20 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of Radio Resource Control (RRC)). The DL signal may also include a reference signal.

[0187] The channels used for transmitting DL signals include, for example, a data channel and a control channel. For example, 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, the base station 10 transmits control information to the terminal 20 using the PDCCH and transmits downlink data signals using the PDSCH.

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

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

[0190] The control unit 103 controls the communication operations of the base station 10 , including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102 .

[0191] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.

[0192] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on signals (e.g., data and control information, etc.) received from the terminal 20 and / or data and control information, etc. acquired from a higher layer. Information on the allocated resources may be included in control information transmitted to the terminal 20.

[0193] The control unit 103 sets PUCCH resources as an example of allocation of resources used for transmitting and receiving UL signals. Information related to PUCCH configuration such as a PUCCH cell timing pattern (PUCCH configuration information) may be notified to the terminal 20 by RRC.

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

[0195] 12 is a block diagram showing an example of the configuration of terminal 20 according to this embodiment. Terminal 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. Terminal 20 communicates with base station 10, for example, wirelessly.

[0196] The receiving unit 201 receives a 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.

[0197] The transmitting unit 202 transmits the 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.

[0198] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capability of the terminal 20 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

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

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

[0201] The control unit 203 controls the communication operations of the terminal 20 , including the reception processing in the receiving unit 201 and the transmission processing in the transmitting unit 202 .

[0202] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the upper layer.

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

[0204] The control unit 203 sets PUCCH resources based on configuration information (for example, configuration information such as a PUCCH cell timing pattern and / or DCI notified by RRC) received from the base station 10. The control unit 203 determines the PUCCH resources to be used for transmitting information to be fed back to the base station 10. Under the control of the control unit 203, the transmission unit 202 transmits the information to be fed back to the base station 10 in the PUCCH resources determined by the control unit 203.

[0205] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned example. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

[0206] For example, in the terminal 20 of this embodiment, the control unit 203 multiplexes the HARQ-ACK and / or the UTO-UCI onto a specific channel (e.g., a CG PUSCH or another uplink channel) based on a multiplexing method determined according to the setting of joint encoding of the HARQ-ACK (an example of acknowledgement information) and the UTO-UCI (an example of first uplink control information indicating the occasion of an unused uplink signal), and the transmitting unit 202 transmits the signal of the specific channel.

[0207] Furthermore, for example, when joint encoding of HARQ-ACK and UTO-UCI is configured and the UE intends to multiplex and transmit HARQ-ACK information in a CG PUSCH including UTO-UCI, control unit 203 multiplexes the HARQ-ACK in the CG PUSCH. Also, for example, when joint encoding of HARQ-ACK and UTO-UCI is not configured and the UE intends to multiplex and transmit HARQ-ACK information in a CG PUSCH including UTO-UCI, control unit 203 multiplexes the HARQ-ACK into a CG PUSCH excluding UTI-UCI or into a channel different from the CG PUSCH.

[0208] Furthermore, for example, when joint encoding of UTO-UCI (an example of first uplink control information) and CG-UCI (an example of second uplink control information) is applied, the control unit 203 multiplexes the UTO-UCI and / or HARQ-ACK based on a multiplexing method determined according to the setting of joint encoding of UTO-UCI and HARQ-ACK and the setting of multiplexing of CG-UCI and HARQ-ACK.

[0209] The present disclosure has been described above.

[0210] <Hardware Configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

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

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

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

[0214] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

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

[0216] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 203 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

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

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

[0219] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.

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

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

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

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

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

[0225] <Applicable Systems> The embodiments described in the present disclosure are applicable to LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 (WiMAX (registered trademark The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0226] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

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

[0228] <Direction of Input / Output> Information, etc. (see <Information, Signal>) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.

[0229] <Handling of Input / Output Information, etc.> Input / output information, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information, etc. may be overwritten, updated, or added. Output information, etc. may be deleted. Input information, etc. may be sent to another device.

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

[0231] <Variations of Aspects, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation. In addition, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

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

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

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

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

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

[0237] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0238] <Parameter and Channel Names> Furthermore, the information, parameters, and the like described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

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

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

[0241] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0242] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

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

[0245] <Base Station / Mobile Station> At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

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

[0247] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station may be configured to have the functions of the terminal described above.

[0248] Fig. 14 shows an example configuration of a vehicle 2001. As shown in Fig. 14, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0249] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0250] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

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

[0252] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

[0253] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0254] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0255] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029, which are provided in the vehicle 2001.

[0256] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0257] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0258] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

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

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

[0261] <Reference Signal> A reference signal can also be abbreviated as RS (Reference Signal), and may also be called a pilot depending on the applicable standard.

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

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

[0264] <Means> The "means" in the configuration of each device above may be replaced with "section," "circuit," "device," etc.

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

[0266] <Time Units such as TTI, Frequency Units such as RB, and Radio Frame Configuration> A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0285] <Maximum Transmit Power> The "maximum transmit power" in the present disclosure may refer to the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

[0288] One aspect of the present disclosure is useful in wireless communication systems.

[0289] 10 Base station 20 Terminal 101, 202 Transmitter 102, 201 Receiver 103, 203 Controller

Claims

1. A terminal comprising: a control unit that multiplexes acknowledgement information and / or first uplink control information onto a specific channel based on a multiplexing method determined in accordance with a setting of a first joint encoding of the acknowledgement information and first uplink control information indicating an occasion of an unused uplink signal; and a transmitting unit that transmits a signal of the specific channel.

2. The terminal described in claim 1, wherein when the first joint encoding is set and the terminal is to transmit a first uplink channel including the first uplink control information and the acknowledgement information, the control unit multiplexes the acknowledgement information onto the first uplink channel including the first uplink control information.

3. The terminal described in claim 1, wherein, when the first joint encoding is not set and the terminal is attempting to transmit a first uplink channel including the first uplink control information and the acknowledgement information, the control unit multiplexes the acknowledgement information onto a first uplink channel excluding the first uplink control information, or onto a second uplink channel different from the first uplink channel.

4. The terminal described in claim 1, wherein, when a second joint encoding of the first uplink control information and second uplink control information different from the first uplink control information is applied, the control unit determines the multiplexing method depending on a setting of the first joint encoding and a setting of multiplexing the second uplink control information and the acknowledgement information.

5. A communication method in which a terminal multiplexes the acknowledgement information and / or the first uplink control information onto a specific channel based on a multiplexing method determined in accordance with a setting of a first joint encoding of the acknowledgement information and the first uplink control information, and transmits a signal of the specific channel.

6. A communication system comprising: a terminal including: a control unit that multiplexes the acknowledgement information and / or the first uplink control information onto a specific channel based on a multiplexing method determined in accordance with a setting of a first joint encoding of the acknowledgement information and the first uplink control information; a transmitting unit that transmits a signal of the specific channel; and a base station including: a receiving unit that receives a signal of the specific channel.