The PDCCH delivers DCI. For example, the PDCCH (i.e., DCI) may carry information about a transport format and resource allocation of a DL shared channel (DL-SCH), resource allocation information of an uplink shared channel (UL-SCH), paging information on a paging channel (PCH), system information on the DL-SCH, information on resource allocation of a higher-layer control message such as an RAR transmitted on a PDSCH, a transmit power control command, information about activation/release of configured scheduling, and so on. The DCI includes a cyclic redundancy check (CRC). The CRC is masked with various identifiers (IDs) (e.g. a radio network temporary identifier (RNTI)) according to an owner or usage of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked by a UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is for a paging message, the CRC is masked by a paging-RNTI (P-RNTI). If the PDCCH is for system information (e.g., a system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for an RAR, the CRC is masked by a random access-RNTI (RA-RNTI).

FIG. 5 is a diagram illustrating a signal flow for a PDCCH transmission and reception process.

Referring to FIG. 5, a BS may transmit a control resource set (CORESET) configuration to a UE (S502). A CORESET is defined as a set of resource element groups (REGs) having a given numerology (e.g., an SCS, a CP length, and so on). A plurality of CORESETs for one UE may overlap with each other in the time/frequency domain. A CORESET may be configured by system information (e.g., a master information block (MIB)) or UE-specific higher-layer signaling (e.g., radio resource control (RRC) signaling). The UE-specific RRC signaling may include, for example, an RRC setup message, BWP configuration information, and so on.

- controlResourceSetId: indicates the ID of a CORESET.
- frequencyDomainResources: indicates the frequency resources of the CORESET. The frequency resources of the CORESET are indicated by a bitmap in which each bit corresponds to an RBG (e.g., six (consecutive) RBs). For example, the most significant bit (MSB) of the bitmap corresponds to a first RBG. RBGs corresponding to bits set to 1 are allocated as the frequency resources of the CORESET.
- duration: indicates the time resources of the CORESET. Duration indicates the number of consecutive OFDM symbols included in the CORESET. Duration has a value of 1 to 3.
- cce-REG-MappingType: indicates a control channel element (CCE)-REG mapping type. Interleaved and non-interleaved types are supported.
- interleaverSize: indicates an interleaver size.
- pdcch-DMRS-ScramblingID: indicates a value used for PDCCH DMRS initialization. When pdcch-DMRS-ScramblingID is not included, the physical cell ID of a serving cell is used.
- precoderGranularity: indicates a precoder granularity in the frequency domain.
- reg-BundleSize: indicates an REG bundle size.
- tci-PresentInDCI: indicates whether a transmission configuration index (TCI) field is included in DL-related DCI.
- tci-StatesPDCCH-ToAddList: indicates a subset of TCI states configured in pdcch-Config, used for providing quasi-co-location (QCL) relationships between DL RS(s) in an RS set (TCI-State) and PDCCH DMRS ports.

Further, the BS may transmit a PDCCH search space (SS) configuration to the UE (S504). A PDCCH SS set includes PDCCH candidates. A PDCCH candidate is CCE(s) that the UE monitors to receive/detect a PDCCH. The monitoring includes blind decoding (BD) of PDCCH candidates. One PDCCH (candidate) includes 1, 2, 4, 8, or 16 CCEs according to an aggregation level (AL). One CCE includes 6 REGs. Each CORESET configuration is associated with one or more SSs, and each SS is associated with one CORESET configuration. One SS is defined based on one SS configuration, and the SS configuration may include the following information/fields.

- searchSpaceld: indicates the ID of an SS.
- controlResourceSetId: indicates a CORESET associated with the SS.
- monitoringSlotPeriodicityAndOffset: indicates a periodicity (in slots) and offset (in slots) for PDCCH monitoring.
- monitoringSymbolsWithinSlot: indicates the first OFDM symbol(s) for PDCCH monitoring in a slot configured with PDCCH monitoring. The first OFDM symbol(s) for PDCCH monitoring is indicated by a bitmap with each bit corresponding to an OFDM symbol in the slot. The MSB of the bitmap corresponds to the first OFDM symbol of the slot. OFDM symbol(s) corresponding to bit(s) set to 1 corresponds to the first symbol(s) of a CORESET in the slot.
- nrofCandidates: indicates the number of PDCCH candidates (one of values 0, 1, 2, 3, 4, 5, 6, and 8) for each AL where AL={1, 2, 4, 8, 16}.
- searchSpaceType: indicates common search space (CSS) or UE-specific search space (USS) as well as a DCI format used in the corresponding SS type.

Subsequently, the BS may generate a PDCCH and transmit the PDCCH to the UE (S506), and the UE may monitor PDCCH candidates in one or more SSs to receive/detect the PDCCH (S508). An occasion (e.g., time/frequency resources) in which the UE is to monitor PDCCH

Table 3 shows the characteristics of each SS.

TABLE 3

Search

Type
Space
RNTI
Use Case

Type0-PDCCH
Common
SI-RNTI on a
SIB

primary cell
Decoding

Type0A-PDCCH
Common
SI-RNTI on a
SIB

primary cell
Decoding

Type1-PDCCH
Common
RA-RNTI or
Msg2, Msg4

TC-RNTI on a
decoding in

primary cell
RACH

Type2-PDCCH
Common
P-RNTI on a
Paging

primary cell
Decoding

Type3-PDCCH
Common
INT-RNTI,

SFI-RNTI,

TPC-PUSCH-RNTI,

TPC-PUCCH-RNTI,

TPC-SRS-RNTI,

C-RNTI,

MCS-C-RNTI, or

CS-RNTI(s)

UE
C-RNTI, or
User specific

Specific
MCS-C-RNTI, or
PDSCH

CS-RNTI(s)
decoding

Table 4 shows DCI formats transmitted on the PDCCH.

TABLE 4

DCI

format
Usage

0_0
Scheduling of PUSCH in one cell

0_1
Scheduling of PUSCH in one cell

1_0
Scheduling of PDSCH in one cell

1_1
Scheduling of PDSCH in one cell

2_0
Notifying a group of UEs of the slot format

2_1
Notifying a group of UEs of the PRB(s) and OFDM symbol(s)

where UE may assume no transmission is intended for the UE

2_2
Transmission of TPC commands for PUCCH and PUSCH

2_3
Transmission of a group of TPC commands for SRS

transmissions by one or more UEs

DCI format 0_0 may be used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 may be used to schedule a TB-based (or TB-level) PUSCH or a code block group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 may be used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 may be used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0/0_1 may be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0/1_1 may be referred to as DL grant DCI or DL scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., a dynamic slot format indicator (SFI)) to a UE, and DCI format 2_1 is used to deliver DL pre-emption information to a UE. DCI format 2_0 and/or DCI format 2_1 may be delivered to a corresponding group of UEs on a group common PDCCH which is a PDCCH directed to a group of UEs.

DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, whereas DCI format 0_1 and DCI format 1_1 may be referred to as non-fallback DCI formats. In the fallback DCI formats, a DCI size/field configuration is maintained to be the same irrespective of a UE configuration. In contrast, the DCI size/field configuration varies depending on a UE configuration in the non-fallback DCI formats.

NR may support a wider uplink/downlink bandwidth by aggregating multiple uplink/downlink carriers (i.e., carrier aggregation). A signal may be transmitted/received on multiple carriers by carrier aggregation. When carrier aggregation is applied, each of the carriers (refer to FIG. 3) may be referred to as a component carrier (CC). CCs may or may not be contiguous in the frequency domain. The bandwidth of each CC may be independently determined. In asymmetric carrier aggregation, the number of UL CCs may be different from the number of DL CCs. In NR, radio resources are divided into/managed as cells. A cell may consist of one DL CC and 0 to 2 UL CCs. For example, a cell may consist of (i) only one DL CC, (ii) one DC CC and one UL CC, or (ii) one DL CC and two UL CCs (including one supplementary UL CC). Cells are divided as follows. In the present disclosure, a cell may be interpreted according to a context, and may represent, for example, a serving cell. Unless otherwise stated, the operations of the present disclosure may be applied to each serving cell.

- Primary Cell (PCell): A cell operating at a primary frequency (e.g., primary component carrier (PCC)) at which a UE for which carrier aggregation is configured performs an initial connection establishment procedure or initiates a connection re-establishment procedure. In the case of dual connectivity (DC), a master cell group (MCG) cell operating at a primary frequency at which the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.
- Secondary Cell (SCell): A cell that provides additional radio resources, other than a special cell for a UE for which carrier aggregation is configured.
- Primary SCG Cell (PSCell): A secondary cell group (SCG) cell in which the UE performs random access when performing an RRC reconfiguration and synchronization procedure in the case of DC.
- Special Cell (SpCell): In the case of DC, the SpCell represents the PCell of the MCG or the PSCell of the SCG. In the other case (i.e., the case of non-DC), the special cell represents a PCell.
- Serving Cell (ServCell): Represents a cell configured for a UE in an RRC_CONNECTED state. When CA/DC is not configured, only one serving cell (i.e., PCell) exists. When CA/DC is configured, the serving cell represents a cell set including the SpCell(s) and all SCells.

The control information may be configured to be transmitted/received only through an SpCell. For example, UCI may be transmitted only through a SpCell (e.g., PCell). When an SCell in which PUCCH transmission is allowed (hereinafter, PUCCH-SCell) is configured, UCI may be transmitted even through the PUCCH-SCell. As another example, the BS may allocate a scheduling cell (set) to lower the complexity of the PDCCH blinding decoding (BD) at the UE side. For PDSCH reception/PUSCH transmission, the UE may perform PDCCH detection/decoding only in the scheduling cell. In addition, the BS may transmit the PDCCH only through the scheduling cell (set). For example, data (e.g., PDSCH, PUSCH) transmitted in one cell (or active BWP within a cell) (hereinafter, a cell may be replaced with a (active) BWP within the cell) may be scheduled through a PDCCH in the cell (Self-Carrier Scheduling (SCS)). In addition, the PDCCH for downlink allocation may be transmitted in cell #0 (i.e., a scheduling cell), and the corresponding PDSCH may be transmitted in cell #2 (i.e., a scheduled cell) (Cross-Carrier Scheduling (CCS)). The scheduling cell (set) may be configured in a UE-specific, UE-group-specific or cell-specific manner. The scheduling cell includes a special cell (e.g., PCell).

For CCS, a carrier indicator field (CIF) is used. The CIF may be disabled/enabled semi-statically by UE-specific (or UE group-specific) higher-layer signaling (e.g., RRC signaling). The CIF is an x-bit field (e.g., x=3) in the PDCCH (i.e., DCI) and may be used to indicate the (serving) cell index of the scheduled cell.

- CIF disabled: The CIF is not present in the PDCCH. The PDCCH in the scheduling cell allocates PDSCH/PUSCH resources in the same cell. That is, the scheduling cell is identical to the scheduled cell.
- CIF enabled: The CIF is present in the PDCCH. The PDCCH in the scheduling cell may allocate PDSCH/PUSCH resources in one of a plurality of cells using the CIF. The scheduling cell may be identical to or different from the scheduled cell. A PDSCH/PUSCH means a PDSCH or a PUSCH.

FIG. 9 illustrates exemplary scheduling in the case of multi-cell aggregation. Referring to FIG. 8, it is assumed that three cells are aggregated. When the CIF is disabled, only a PDCCH that schedules a PDSCH/PUSCH for each cell may be transmitted in each cell (SCS). On the other hand, when the CIF is enabled by UE-specific (or UE group-specific or cell-specific) higher-layer signaling, and cell A is configured as a scheduling cell, a PDCCH that schedules a PDSCH/PUSCH in another cell (i.e., a scheduled cell) as well as a PDCCH that schedules a PDSCH/PUSCH for cell A may be transmitted in cell A (CCS). In this case, no PDCCH that schedules a PDSCH/PUSCH for cell B/C is transmitted in cell B/C.

FIG. 10 illustrates an ACK/NACK transmission process. Referring to FIG. 10, the UE may detect a PDCCH in slot #n, where the PDCCH includes DL scheduling information (e.g., DCI formats 1_0 and 1_1), and the PDCCH indicates a DL assignment-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0 and 1_1 may include the following information.

- FDRA (frequency domain resource assignment): The FDRA field indicates an RB set allocated to a PDSCH
- TDRA (time domain resource assignment): The TDRA field indicates K0, i.e., the starting position (e.g., OFDM symbol index) and the length (e.g., the number of OFDM symbols) of a PDSCH in a slot. The TDRA field may be indicated by a start and length indicator value (SLIV).
- PDSCH-to-HARQ_feedback timing indicator: The PDSCH-to-HARQ_feedback timing indicator field indicates K1.
- HARQ process number (4 bits): The HARQ process number field indicates a HARQ process identity (ID) for data (e.g., PDSCH, TB, etc.).
- PUCCH resource indicator (PRI): The PRI field indicates a PUCCH resource to be used for UCI transmission among a plurality of PUCCH resources in a PUCCH resource set.

Thereafter, the UE may receive a PDSCH in slot #(n+K0) based on the scheduling information in slot #n and then transmit UCI over a PUCCH in slot #(n+K1). Here, the UCI includes a HARQ-ACK response for the PDSCH. When the PDSCH is configured to transmit a maximum of one TB, the HARQ-ACK response may be composed of one bit. When the PDSCH is configured to transmit a maximum of two TBs, the HARQ-ACK response may be composed of two bits if no spatial bundling is configured. However, if spatial bundling is configured, the HARQ-ACK response may be composed of one bit. If the HARQ-ACK transmission time for a plurality of PDSCHs is designated as slot #(n+K1), the UCI transmitted in slot #(n+K1) may include HARQ-ACK responses for the plurality of PDSCHs.

FIG. 11 illustrates a PUSCH transmission process. Referring to FIG. 11, the UE may detect a PDCCH in slot #n, where the PDCCH includes UL scheduling information (e.g., DCI formats 0_0 and 01). DCI formats 0_0 and 01 may include the following information.

- FDRA: The FDRA field indicates an RB set allocated to a PUSCH.
- TDRA: The TDRA field indicates a slot offset K2, i.e., the starting position (e.g., symbol index) and the length (e.g., the number of OFDM symbols) of a PUSCH in a slot. The starting symbol and length may be indicated by an SLIV or indicated separately.

Thereafter, the UE may transmit a PUSCH in slot #(n+K2) based on the scheduling information in slot #n, where the PUSCH includes a UL-SCH TB. When the PUCCH transmission time and the PUSCH transmission time overlap, UCI may be transmitted over the PUSCH (PUSCH piggyback).

Embodiment: A/N Feedback Considering Priority

FIG. 9 is a diagram showing an example of a Type-3 (one-shot) HARQ-ACK codebook transmission procedure. Here, the HARQ-ACK codebook may be used equivalently to a HARQ-ACK payload. The Type-3 HARQ-ACK codebook is introduced (in a form triggered through DCI) for HARQ-ACK feedback transmission suitable for a U (Unlicensed)-band situation, but may also be applied to an L (Licensed)-band.

Referring to FIG. 9, a UE may receive one or more PDSCHs from a BS (S902a to S902n). Thereafter, the UE may receive a HARQ-ACK one-shot feedback request from the BS through DCI (S904). Then, based on the HARQ-ACK one-shot feedback request, the UE may transmit the HARQ-ACK codebook to the BS (S906). The HARQ-ACK codebook may be transmitted through a PUCCH or a PUSCH. In the Type-3 HARQ-ACK codebook, the ACK/NACK (AN) information configured on the HARQ-ACK payload (for each of the fully configured (serving) cells) may be mapped according to a DL (PDSCH) HARQ process (hereinafter referred to as HARQ process, HARQp) index. A plurality of (e.g., 8 or 16) parallel HARQ processes may be present for each cell in the UE/BS. The plurality of parallel HARQ processes may allow DL transmissions to be performed consecutively while waiting for HARQ feedback regarding successful or unsuccessful reception of previous DL transmissions. Each HARQ process may be associated with a HARQ buffer of a medium access control (MAC) layer. Each HARQ process may manage state variables related to the number of transmissions of MAC PDUs (Physical Data Blocks) in the buffer, HARQ feedback for the MAC PDUs in the buffer, and the current redundancy version.

FIG. 10 shows a Type-3 (one-shot) HARQ-ACK codebook/payload. FIG. 10 shows a case in which two cells are configured, 16 (DL) HARQ processes are configured for cell #1, and 8 (DL) HARQ processes are configured for cell #2. Referring to FIG. 10, the HARQ-ACK payload may include AN information for all HARQ processes of all configured (serving) cells. AN information in the HARQ-ACK payload may be configured in the following order.

- (1) An order of increasing cell index when there are multiple cells
- (2) An order of increasing HARQp index for the same cell
- (3) An order of increasing TB (Transport Block) index for HARQp index
- (4) An order of increasing CBG (Codeblock Group) index for the same TB
- * (3) and (4) may not be applied according to a TB/CBG configuration situation.

Recently, in order to support data transmission/services in which reliability/latency performance is important, such as URLLC, service/protection priority (e.g., LP (low priority), and HP (high priority)) for each physical layer channel/signal (or transmission resource) may be semi-statically configured (via RRC signaling, etc.) or dynamically indicated (via DCI/MAC signaling, etc.).

In addition, for all HARQ process indexes configured in a specific cell, the corresponding PDSCH transmissions and/or HARQ-ACK feedback transmission for them may be configured or indicated with an HP, and in contrast, for all HARQ process indexes configured in other cells, the corresponding PDSCH transmissions and/or HARQ-ACK feedback transmission for them may be configured/indicated only with an LP. In addition, for some of the HARQ process indexes configured in the specific cell, the corresponding PDSCH transmissions and/or HARQ-ACK feedback transmission for them may be configured or indicated with an HP, and in contrast, for the remaining HARQ process indexes, the corresponding PDSCH transmissions and/or HARQ-ACK feedback transmission for them may be configured/indicated only with an LP. The HP/LP may be configured or indicated through RRC/MAC/DCI based on HARQ process index/PDSCH and/or the corresponding HARQ-ACK feedback.

Therefore, when HARQ-ACK feedback transmission based on a Type-3 codebook is triggered through DCI, the following is proposed for a method of configuring a HARQ-ACK payload based on a service/protection priority (e.g., HP and LP). Although not limited thereto, the method of the present disclosure may be applied when HARQ-ACK feedback transmission based on the Type-3 codebook is triggered through DCI configured with an HP or indicated with an HP.

FIG. 11 shows an example of a HARQ-ACK codebook transmission procedure according to an example of the present disclosure. Referring to FIG. 11, the UE may receive cell/HARQ process configuration information from the BS (S1104). The HARQ process configuration information may be defined for each cell as a part of cell configuration information. Here, the HARQ process configuration information may include information about the number of HARQ processes and priorities (e.g., HP and LP) related to the HARQ processes. As another method, the priorities (e.g., HP and LP) related to the HARQ process within a cell may be dynamically indicated as follows through DL DCI (format) for scheduling the cell.

- If there is no priority indicator indicating an LP/HP in all DL DCI format(s) for scheduling PDSCH(s) on the cell, all HARQ processes configured in the cell in the HARQ-ACK feedback process are interpreted as being configured/indicated only with an LP.
- If there is a priority indicator indicating an LP/HP in at least one DL DCI format for scheduling a PDSCH on the cell, and the maximum number of the lowest (or highest) HARQ process indexes, which is to be indicated through all DL DCI formats with the priority indicator, is N, the lowest (or highest) HARQ process index N configured in the cell in the HARQ-ACK feedback process may be configured/indicated with an HP, while all other HARQ process indexes are interpreted as being configured/indicated only with an LP.

Then, the UE may receive a HARQ-ACK one-shot feedback request from the BS through DCI (S1104). Here, the DCI may be DCI including PDSCH scheduling or DCI including only a HARQ-ACK feedback request without PDSCH scheduling. In addition, the DCI may include priority information for an HARQ process/PDSCH requiring HARQ-ACK and/or the corresponding HARQ-ACK feedback. Then, based on the HARQ-ACK one-shot feedback request and priority information, the UE may transmit the HARQ-ACK codebook to the BS (S906). The HARQ-ACK codebook may be transmitted through a PUCCH or a PUSCH. Here, when the priority of HARQ feedback (target) is indicated with an LP based on the priority information, the HARQ-ACK codebook may be configured according to a conventional method (i.e., feedback AN for all configured cells/all HARQ processes; see FIGS. 9 to 10). When the priority of HARQ feedback (target) is indicated with an HP base on the priority information, the HARQ-ACK codebook may be configured based on the method proposed below.

[Proposed Method]

1) Opt 1

- A. Only for cell(s) in which a HARQ process index with PDSCH transmission and/or the corresponding HARQ-ACK feedback transmission to be configured with an HP or indicated with an LP is present, an HARQ-ACK payload is configured in the form of mapping ACK/NACK information corresponding to all HARQ process indexes configured to the respective corresponding cell(s).
- i. For example, as shown in FIG. 12, all 16 HARQ process indexes configured in cell 1 may be configured/indicated only with an LP (e.g., if there is no priority indicator indicating an LP/HP in all DL DCI format(s) for scheduling PDSCH(s) on cell 1), all 16 HARQ process indexes configured in cell 2 may be configured or indicated with an HP (e.g., if there is a priority indicator indicating an LP/HP in at least one DL DCI format for scheduling a PDSCH on cell 2 and it is possible to indicate all 16 HARQ process indexes through the corresponding DL DCI format), the lowest 8 process indexes among 16 HARQ process indexes configured in cell 3 may be configured or indicated with an HP, and in contrast, the highest 8 process indexes may be configured/indicated only with an LP (e.g., if it is possible to indicate only the lowest 8 HARQ process indexes through all DL DCI format(s) with a priority indicator indicating an LP/HP while scheduling PDSCH(s) on cell 3). In this case, if Opt 1 is applied, a HARQ-ACK payload may be configured by mapping ACK/NACK information to 16 HARQ process indexes of cell 2 and 16 HARQ process indexes of cell 3 (see FIG. 13).
  
  2) Opt 2
- A. For cell(s) in which an HARQ process index with PDSCH transmission and/or corresponding HARQ-ACK feedback transmission to be configured with an HP or indicated with an HP is present, an HARQ-ACK payload is configured by mapping ACK/NACK information only to an HARQ process index (with PDSCH transmission and/or corresponding HARQ-ACK feedback transmission) to be configured with an HP or indicated with an HP among HARQ process indexes configured to the respective corresponding cell(s).
- i. When the example of FIG. 12 is applied, if Opt 2 is applied, an HARQ-ACK payload may be configured by mapping ACK/NACK information only to 16 HARQ process indices of cell 2 and the lowest 8 HARQ process indexes of cell 3 (see FIG. 14).
  
  [Proposed Method]

When a Type-2 (dynamic) codebook type is configured for HARQ-ACK feedback, counter-DAI information, which is a PDSCH (DCI) scheduling order value for determining an ACK/NACK mapping order on the HARQ-ACK payload, may be signaled through DCI.

FIG. 15 shows an example of a Type-2 (dynamic) HARQ-ACK codebook transmission procedure. In the Type-2 HARQ-ACK codebook, the size of the HARQ-ACK codebook/payload may be dynamically varied based on the counter-DAI (and total-DAI) in the DCI.

Referring to FIG. 15, the UE may receive DCI (i.e., DL grant DCI) for PDSCH scheduling from the BS (S1502). Here, the DCI may include PDSCH scheduling information, information about a PUCCH transmission time, and counter-DAI. The counter-DAI may represent an order value of {MO (monitoring occasion), cell}-pair related to PDSCH/(DL) SPS-release DCI, and may be calculated in a cell first manner. MO may represent a PDCCH monitoring occasion. The DCI may further include total-DAI. The total-DAI may represent the total number of {MO, cell}-pairs associated with PDSCH/(DL_SPS-release DCI, up to the current MO in which a PDCCH is detected, and is updated in units of MOs. Then, the UE may receive a PDSCH corresponding to the DCI (S1504) and may then transmit a HARQ-ACK codebook to the BS (S1506). The HARQ-ACK codebook may be transmitted through a PUCCH or a PUSCH. An AN information location of the Type-2 HARQ-ACK codebook/payload may be determined based on the counter-DAI, and (when total-DAI is signaled), an AN payload size may be determined based on the total-DAI.

Cross-CC scheduling may be configured between cells configured with different SCSs. In particular, when a cell with a large SCS is scheduled from a cell with a small SCS, a plurality of DCIs for scheduling the same (scheduled) cell need to be supported to be transmitted/detected through one PDCCH MO(monitoring occasion) (at the same time point) for smoother and more efficient scheduling. That is, the plurality of DCIs corresponding to the same {MO, cell} pair need to be supported to be transmitted/detected. Therefore, when the Type-2 (dynamic) codebook type is configured, a rule for determining an order of counter-DAI values between DCIs corresponding to the same {MO, cell} pair may be required. In addition, there may be a need for a rule for determining an order of a counter-DAI value (between DCIs corresponding to the same {MO, cell} pair) including PDSCH-less DCI that requires HARQ-ACK feedback without PDSCH scheduling, such as DCI indicating a release operation for an SPS PDSCH and DCI indicating conversion into a dormant BWP for an SCell. To this end, the following counter-DAI order determination method is proposed.

1) Opt 1

A. For DCI by which an earlier/advanced timing of PDSCH start symbol timing (which is lastly indicated including slot offset K0, which is DCI-to-PDSCH timing) is indicated through a Time Domain RA (TDRA) field, an earlier/advanced counter-DAI value may be configured.

i. When the PDSCH start symbol timings indicated by a plurality of DCIs are the same, the lower the lowest PRB index in the corresponding PDSCH resource or the earlier the indicated PDSCH last symbol timing, or the lower the CORESET (pool) index through which DCI is transmitted, an earlier/advanced counter-DAI value may be configured.

2) Opt 2

- A. An earlier/advanced counter-DAI value is configured for PDSCH-less DCI than DCI involving PDSCH scheduling (PDSCH-scheduling DCI).
- B. An earlier/advanced counter-DAI value is configured for PDSCH-scheduling DCI than PDSCH-less DCI.
- C. An earlier/advanced counter-DAI value is configured for DCI indicating PDSCH start symbol timing as an earlier/advanced time point between PDSCH-scheduling DCIs (and/or between PDSCH-less DCIs).
- i. When the PDSCH start symbol timings indicated by a plurality of DCIs are the same, the lower the lowest PRB index in the corresponding PDSCH resource or the earlier the indicated PDSCH last symbol timing, or the lower the CORESET (pool) index through which DCI is transmitted, an earlier/advanced counter-DAI value may be configured.
  
  3) Note 1
- A. In the case of PDSCH-less DCI, the corresponding PDSCH start symbol timing may be determined as the PDSCH start symbol timing virtually indicated through a TDRA field although there is no PDSCH transmission actually scheduled from the corresponding DCI.
- B. In the case of the SPS PDSCH release DCI, the corresponding PDSCH start symbol timing may be applied as the PDSCH start symbol timing indicated by the DCI that activates (at a previous time) SPS PDSCH transmission targeted for release through the corresponding DCI.

Various descriptions, functions, procedures, proposals, methods, and/or operational flow charts of the present disclosure may be applied to, but not limited to, various fields requiring wireless communication/connection (e.g., 5G) between devices.

With reference to the drawings, the present disclosure will be described in greater detail. In the following drawings/description, like reference numerals may denote the same or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise specified.

According to the present disclosure, at least one memory (e.g., 104 or 204) may store instructions or programs which, when executed, cause at least one processor operably coupled to the at least one memory to perform operations according to various embodiments or implementations of the present disclosure.

According to the present disclosure, a computer-readable storage medium may store at least one instruction or computer program which, when executed by at least one processor, cause the at least one processor to perform operations according to various embodiments or implementations of the present disclosure.

According to the present disclosure, a computer program is stored in at least one computer readable (non-volatile) storage medium, and may include program code that, when executed, performs operations (by the at least one processor) according to some embodiments or implementations of the present disclosure. The computer program may be provided in the form of a computer program product. The computer program product may include at least one computer-readable (non-volatile) storage medium. The computer-readable storage medium may include program code that, when executed, performs operations (by the at least one processor) according to some embodiments or implementations of the present disclosure.

According to various embodiments of the present disclosure, a processing device or apparatus may include the at least one processor and at least one computer memory connected to the at least one processor. The at least one computer memory may store instructions or programs which, when executed, cause the at least one processor operably coupled to the at least one memory to perform operations according to various embodiments or implementations of the present disclosure.

A communication device according to the present disclosure may include at least one processor, and at least one computer memory operatively connected to the at least one processor, and configured to store instructions such that the at least one processor performs specific operations by executing the instructions.

FIG. 16 illustrates a communication system 1 applied to the present disclosure.

Referring to FIG. 16, a communication system 1 applied to the present disclosure includes wireless devices, Base Stations (BSs), and a network. Herein, the wireless devices represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G New RAT (NR)) or Long-Term Evolution (LTE)) and may be referred to as communication/radio/5G devices. The wireless devices may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an eXtended Reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an Artificial Intelligence (AI) device/server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter. For example, the BSs and the network may be implemented as wireless devices and a specific wireless device 200a may operate as a BS/network node with respect to other wireless devices.

The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs/network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g. Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

Wireless communication/connections 150a, 150b, or 150c may be established between the wireless devices 100a to 100f/BS 200, or BS 200/BS 200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150a, sidelink communication 150b (or, D2D communication), or inter BS communication (e.g. relay, Integrated Access Backhaul (IAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections 150a and 150b. For example, the wireless communication/connections 150a and 150b may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.

FIG. 17 illustrates wireless devices applicable to the present disclosure.

Referring to FIG. 17, a first wireless device 100 and a second wireless device 200 may transmit radio signals through a variety of RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to {the wireless device 100x and the BS 200} and/or {the wireless device 100x and the wireless device 100x} of FIG. 16.

The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and/or a receiver. The transceiver(s) 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and/or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s) 206. The processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and/or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.

The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories 104 and 204 may be configured by Read-Only Memories (ROMs), Random Access Memories (RAMs), Electrically Erasable Programmable Read-Only Memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

The one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas 108 and 208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers 106 and 206 may convert received radio signals/channels etc. from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.

FIG. 18 illustrates another example of a wireless device applied to the present disclosure. The wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 16).

Referring to FIG. 18, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 17 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices