Method performed by terminal or base station in wireless communication system and apparatus therefor

Abstract

A method performed by a terminal according to an embodiment of the disclosure can include the steps of receiving, through higher layer signaling, configuration information for a table configured such that each row has a plurality of fields for a plurality of cells, receiving downlink control information (DCI) for multi-cell scheduling, and determining a bandwidth part (BWP) of a cell scheduled together through the DCI based on BWP indication information of the DCI; wherein a BWP-specific parameter configured in the plurality of fields included in each row of the table is interpreted based on the determined BWP, and the size of each field in the plurality of fields is determined based on a BWP among BWPs configured in each cell in which the largest number of bits is required to indicate the BWP-specific parameter.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to a method and apparatus for transmitting or receiving downlink / uplink radio signals in a wireless communication system. Background Technology

[0002] Typically, wireless communication systems are evolving to provide communication services such as audio communication and data communication by covering a wider range of areas. Wireless communication is a multiple access system capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). For example, a multiple access system can be any of the following: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA).

[0003] In version 18 New Radio (NR), the introduction of Multi-Cell Scheduling (MC) Downlink Control Information (DCI) for scheduling multiple cells using a single DCI is being discussed. Summary of the Invention

[0004] Technical issues

[0005] The purpose of this disclosure is to provide a method and apparatus for efficiently performing wireless signal transmission / reception processes. For example, a method and apparatus may be provided for more efficiently performing higher-layer signaling associated with multi-cell scheduling (DCI).

[0006] The technical problems to be solved are not limited to these, and other technical problems not mentioned in this article can be found in the following description.

[0007] Technical solution

[0008] In one aspect of this disclosure, a method performed by a user equipment (UE) is provided. The method includes the steps of: receiving configuration information for a table via higher-layer signaling, the table being configured such that each row has multiple fields for multiple cells; receiving downlink control information (DCI) for multi-cell scheduling; and determining the BWP of cells co-scheduled via the DCI based on bandwidth portion (BWP) indication information based on the DCI. BWP-specific parameters configured in the multiple fields included in each row of the table can be interpreted based on the determined BWP, and the size of each of the multiple fields can be determined based on the BWP indicating the maximum number of bits required in the BWP configured for each cell.

[0009] A BWP that instructs specific parameters of a BWP based on the maximum number of bits required in the BWP configured for the first cell can determine the size of the first field among multiple fields for the first cell. Similarly, a second BWP that instructs specific parameters of a BWP based on the maximum number of bits required in the BWP configured for the second cell can determine the size of the second field among multiple fields for the second cell.

[0010] Based on the fact that the first BWP of the first cell requires L bits, the second BWP of the first cell requires M bits, and the third BWP of the first cell requires N bits to indicate specific parameters of the BWP, the size of the first field for the first cell among multiple fields can be determined as the maximum number of bits among L bits, M bits, and N bits.

[0011] Based on the requirement of Y bits to indicate the BWP-specific parameters of BWP#A determined by BWP indication information for the first cell among multiple cells, and based on the fact that the size of the first field for the first cell among multiple fields is determined to be X bits greater than Y bits, the UE can obtain the first BWP-specific parameters of BWP#A for the first cell by selecting Y bits from the X bits of the first field. The Y bits selected from the X bits of the first field can be Y LSBs.

[0012] DCI can include information used to indicate a row in a table.

[0013] DCI can schedule PDSCH or PUSCH on co-scheduled cells. DCI may include minimum scheduling offset indication information related to the minimum scheduling offset from DCI to PDSCH or PUSCH. The configuration of the minimum scheduling offset or its value may be the same for co-scheduled cells. The minimum scheduling offset can be min K0 or min K2, where min K0 may be related to the DCI-PDSCH offset, and min K2 may be related to the DCI-PUSCH offset. The minimum scheduling offset value may be for multi-cell scheduling, and the minimum scheduling offset value for multi-cell scheduling may be configured separately from the minimum scheduling offset value for single-cell scheduling.

[0014] In another aspect of this disclosure, a non-transitory computer-readable recording medium is provided, the non-transitory computer-readable recording medium recording instructions that, when executed by a processor of a UE, cause the UE to perform the method according to claim 1.

[0015] In another aspect of this disclosure, an apparatus is provided. The apparatus includes: a memory storing instructions; and a processor configured to perform operations by executing the instructions. Operations of the processor include: receiving configuration information for a table via higher-layer signaling, the table being configured such that each row has multiple fields for multiple cells; receiving a DCI for multi-cell scheduling; and determining BWPs for cells co-scheduled via the DCI based on BWP indication information. BWP-specific parameters configured in the multiple fields included in each row of the table can be interpreted based on the determined BWPs, and the size of each of the multiple fields can be determined based on the BWP indicating the maximum number of bits required in the BWP configured for each cell.

[0016] The device may also include a transceiver, and the device may be a UE for wireless communication.

[0017] The device may be a processing device configured to control a UE for wireless communication.

[0018] In another aspect of this disclosure, a method performed by a base station (BS) is provided. The method includes the steps of: transmitting configuration information for a table via higher-layer signaling, the table being configured such that each row has multiple fields for multiple cells; and transmitting a DCI for multi-cell scheduling. The BWP indication information of the DCI can indicate the BWP of cells co-scheduled via the DCI. The BWP-specific parameters configured in the multiple fields included in each row of the table can be interpreted based on the indicated BWP. The size of each of the multiple fields can be determined based on the BWP indicating the maximum number of bits required in the BWP configured for each cell.

[0019] In another aspect of this disclosure, a BS (Base Station) is provided. The BS includes: a memory storing instructions; and a processor configured to perform operations by executing the instructions. The processor's operations include: transmitting configuration information for a table via higher-layer signaling, the table being configured such that each row has multiple fields for multiple cells; and transmitting a DCI (Distributed Controlled Instruction) for multi-cell scheduling. The BWP (Browser Window) indication information for cells co-scheduled via the DCI can be indicated. BWP-specific parameters configured in the multiple fields included in each row of the table can be interpreted based on the indicated BWP. The size of each of the multiple fields can be determined based on the BWP indicating the maximum number of bits required in the BWP configured for each cell.

[0020] Beneficial effects

[0021] According to this disclosure, wireless signal transmission and reception can be performed efficiently in a wireless communication system. According to an implementation, when a table for multiple cells is configured in higher-layer signaling related to multi-cell scheduling (DCI), the size of the per-cell information field of the table can be set based on the maximum number of bits for the BWP of the corresponding cell, thereby minimizing scheduling constraints for the BWP-specific information of each cell provided by the multi-cell scheduling DCI.

[0022] The effects that can be obtained from this disclosure are not limited to those described above, and other effects not mentioned herein can be inferred from the following description. Attached Figure Description

[0023] Figure 1 The physical channel used in the 3rd Generation Partnership Project (3GPP) system, which serves as an exemplary wireless communication system, and the general signal transmission method using it are illustrated.

[0024] Figure 2 The structure of a radio frame is shown.

[0025] Figure 3 The resource grid for the time slot is shown.

[0026] Figure 4 An exemplary mapping of physical channels in a time slot is shown.

[0027] Figure 5 This illustrates an exemplary PDCCH / PDSCH receive and acknowledgment / negative acknowledgment (ACK / NACK) transmission process.

[0028] Figure 6 An exemplary Physical Uplink Shared Channel (PUSCH) transmission process is shown.

[0029] Figure 7 An example of carrier aggregation is shown.

[0030] Figure 8 An exemplary wireless communication system supporting unlicensed frequency bands is shown.

[0031] Figure 9 This demonstrates a method for occupying resources within an unlicensed frequency band.

[0032] Figures 10 to 12 This is a diagram illustrating the field structure and field interpretation in the multi-cell scheduling downlink control information (DCI) according to a corresponding embodiment of this disclosure.

[0033] Figure 13 This is a diagram illustrating the table configuration for multi-cell scheduling DCI according to an embodiment of the present disclosure.

[0034] Figure 14This is a diagram illustrating signal transmission and reception between a network and a user equipment (UE) according to embodiments of the present disclosure.

[0035] Figure 15 The flow of a method executed by a UE according to an embodiment of the present disclosure is illustrated.

[0036] Figure 16 The flow of a method performed by a base station (BS) according to an embodiment of the present disclosure is illustrated.

[0037] Figures 17 to 20 A communication system 1 and a wireless device applicable to this disclosure are shown. Detailed Implementation

[0038] The embodiments disclosed herein are applicable to various radio access technologies such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA). CDMA can be implemented as radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as radio technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rate GSM Evolution (EDGE). OFDMA can be implemented as radio technologies such as IEEE 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Global Microwave Access Interoperability (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS using E-UTRA (E-UMTS), and LTE-Advanced (A) is an evolution of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolution of 3GPP LTE / LTE-A.

[0039] As more and more communication devices require greater communication capacity, there is a need for enhanced mobile broadband communications compared to traditional radio access technologies (RATs). Furthermore, the ability to provide various services anytime, anywhere by connecting multiple devices and objects is another important consideration for next-generation communications. Communication system designs considering reliability and latency-sensitive services / UEs are also being discussed. Therefore, the introduction of new radio access technologies that consider enhanced mobile broadband (eMBB), massive MTC, and ultra-reliable low-latency communication (URLLC) is being discussed. In this disclosure, for simplicity, this technology will be referred to as NR (New Radio or New RAT).

[0040] For the sake of brevity, this disclosure primarily describes 3GPP NR, but the technical concepts herein are not limited thereto.

[0041] In this disclosure, the term "settings" may be replaced with "configuration," and the two are used interchangeably. Furthermore, conditional expressions (e.g., "if," "in the case of," or "when") may be replaced by "based on" or "in the state of." Additionally, the operation or software / hardware (SW / HW) configuration of the user equipment (UE) / base station (BS) can be derived / understood based on the satisfaction of corresponding conditions. When the processing on the receiving (or transmitting) side can be derived / understood from the processing on the transmitting (or receiving) side in signal transmission / reception between wireless communication devices (e.g., BS and UE), its description may be omitted. For example, signal determination / generation / encoding / transmission on the transmitting side can be understood as signal monitoring reception / decoding / determination on the receiving side. Furthermore, when referring to the UE performing (or not performing) a specific operation, this can also be interpreted as the BS expecting / assuming (or not expecting / assuming) the UE to perform that specific operation. Similarly, when referring to the BS performing (or not performing) a specific operation, this can also be interpreted as the UE expecting / assuming (or not expecting / assuming) the BS to perform that specific operation. In the following description, for ease of description, sections, implementation methods, examples, options, methods, and solutions are distinguished and indexed, but this does not mean that each of them necessarily constitutes an independent disclosure or that each of them should be implemented only individually. Unless explicitly contradictory, it can be deduced / understood that at least some sections, implementation methods, examples, options, methods, and solutions can be combined or omitted.

[0042] In a wireless communication system, a user equipment (UE) receives information from a base station (BS) via a downlink (DL) and transmits information to the BS via an uplink (UL). The information transmitted and received by the BS and UE includes data and various control information, and varies depending on the type / purpose of the information transmitted and received by the UE and BS, encompassing various physical channels.

[0043] Figure 1 The physical channel used in a 3GPP NR system and the general signal transmission method using it are shown.

[0044] When the UE is powered on again from a power-off state or enters a new cell, in step S101, the UE performs an initial cell search procedure (e.g., establishing synchronization with the BS). For this purpose, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE establishes synchronization with the BS based on the PSS / SSS and obtains information such as the cell identifier (ID). The UE can obtain broadcast information in the cell based on the PBCH. The UE can receive a DL reference signal (RS) during the initial cell search procedure to monitor the DL channel status.

[0045] After the initial cell search, in step S102, the UE can obtain more specific system information by receiving the Physical Downlink Control Channel (PDCCH) and receiving the Physical Downlink Shared Channel (PDSCH) based on the information in the PDCCH.

[0046] In steps S103 to S106, the UE may perform a random access procedure to access the BS. For random access, the UE may send a preamble to the BS on the Physical Random Access Channel (PRACH) (S103) and receive a response message for the preamble on the PDCCH and the corresponding PDSCH (S104). In the case of contention-based random access, the UE may further perform a contention resolution procedure by sending a PRACH (S105) and receiving the PDCCH and the corresponding PDSCH (S106).

[0047] Following the aforementioned process, the UE can receive the PDCCH / PDSCH (S107) and transmit the Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) (S108), as part of the general downlink / uplink signal transmission process. The control information sent from the UE to the BS is called Uplink Control Information (UCI). UCI includes Hybrid Automatic Repeat and Request Acknowledgment / Nack Acknowledgment (HARQ-ACK / NACK), Scheduling Request (SR), Channel State Information (CSI), etc. CSI includes Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), etc. Although UCI is usually transmitted on the PUCCH, it can be transmitted on the PUSCH when control information and service data need to be transmitted simultaneously. Additionally, UCI can be transmitted aperiodically via the PUSCH according to network requests / commands.

[0048] The purpose of the random access procedure (RACH procedure) is not limited to initial network access (e.g., S103 to S106). That is, the random access procedure can be used for a variety of purposes. For example, the random access procedure can be used for at least one of the following: RRC connection re-establishment procedure, handover, UE-triggered UL data transmission, transition from RRC_INACTIVE, SCell time alignment, system information request, beam fault recovery, or UL resource request. However, the random access procedure is not limited to these. The UE can obtain UL synchronization and / or UL transmission resources from the random access procedure.

[0049] Figure 2 The radio frame structure is shown. In NR, uplink and downlink transmissions are configured in frames. Each radio frame is 10ms long and is divided into two 5ms half-frames (HF). Each half-frame is further divided into five 1ms subframes (SF). Subframes are divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 orthogonal frequency division multiplexing (OFDM) symbols. When using a normal CP, each time slot includes 14 OFDM symbols. When using an extended CP, each time slot includes 12 OFDM symbols.

[0050] Table 1 illustrates, for example, how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS when using normal CP.

[0051] [Table 1] N slot symb Number of symbols in a time slot N frame,u slot Number of time slots in a frame N subframe,u slot Number of time slots in a subframe Table 2 shows the number of symbols per slot, the number of slots per frame, and the number of slots per subframe that vary according to SCS when using extended CP.

[0052] [Table 2]

[0053] The frame structure is only an example. The number of subframes, time slots, and symbols in a frame can vary.

[0054] In NR systems, OFDM parameter sets (e.g., SCS) can be configured differently for multiple cells aggregated for a single UE. Therefore, the (absolute time) duration of time resources (e.g., SF, time slots, or TTI) (referred to as time units (TU) for simplicity) consisting of the same number of symbols can be configured differently among the aggregated cells. Here, symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-Extended-OFDM (DFT-s-OFDM) symbols).

[0055] Figure 3 The resource grid shows a time slot. A time slot comprises multiple symbols in the time domain. For example, when using a normal CP, a time slot comprises 14 symbols. However, when using an extended CP, a time slot comprises 12 symbols. A carrier comprises multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple consecutive subcarriers in the frequency domain (e.g., 12 consecutive subcarriers). A bandwidth portion (BWP) can be defined as multiple consecutive physical RBs (PRBs) in the frequency domain and corresponds to a single set of parameters (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., five) BWPs. Data communication can be performed through enabled BWPs, and only one BWP can be enabled for a UE. In the resource grid, individual elements are called resource elements (REs), and a complex symbol can be mapped to individual REs.

[0056] Figure 4 This illustrates an exemplary mapping of physical channels within a time slot. The PDCCH can be transmitted in the DL control area, and the PDSCH can be transmitted in the DL data area. The PUCCH can be transmitted in the UL control area, and the PUSCH can be transmitted in the UL data area. The guard period (GP) provides a time gap for transmit-to-receive mode or receive-to-transmit mode switching at the BS and UE. Some symbols in the subframe during DL-UL handover can be configured as GP.

[0057] The physical channels will be described in more detail below.

[0058] The PDCCH transmits the DCI. For example, the PDCCH (i.e., the DCI) may carry information about the transmission format and resource allocation of the DL-SCH, resource allocation information for the Uplink Shared Channel (UL-SCH), paging information for the PCH, system information for the DL-SCH, resource allocation information for higher-layer control messages (e.g., RARs transmitted on the PDCCH), transmission power control commands, information about enabling / releasing configured schedules, etc. The DCI includes Cyclic Redundancy Check (CRC). The CRC is masked using various identifiers (IDs) (e.g., Radio Network Temporary Identifiers (RNTIs)) depending on the owner or purpose of the PDCCH. For example, if the PDCCH is used for a specific UE, the CRC is masked using the UE ID (e.g., Cell-RNTI (C-RNTI)). If the PDCCH is used for paging messages, the CRC is masked using the Paging-RNTI (P-RNTI). If the PDCCH is used for system information (e.g., System Information Block (SIB)), the CRC is masked by the System Information RNTI (SI-RNTI). When the PDCCH is used for RAR, the CRC is masked by the Random Access-RNTI (RA-RNTI).

[0059] The PDCCH comprises 1, 2, 4, 8, or 16 Control Channel Elements (CCEs) depending on its Aggregation Level (AL). A CCE is a logical allocation unit used to provide a specific code rate to the PDCCH based on the radio channel state. A CCE comprises six Resource Element Groups (REGs), each REG defined by one OFDM symbol × one (P)RB. The PDCCH is transmitted in a Control Resource Set (CORESET). A CORESET is defined as a set of REGs with a given set of parameters (e.g., SCS, CP length, etc.). Multiple CORESETs for a UE can overlap in the time / frequency domain. A CORESET can be configured by system information (e.g., Master Information Block (MIB)) or UE-specific higher-layer signaling (e.g., Radio Resource Control (RRC) signaling). Specifically, the number of RBs and symbols (up to 3) in a CORESET can be configured via higher-layer signaling.

[0060] For PDCCH reception / detection, the UE monitors PDCCH candidates. PDCCH candidates are the Common Enquiry Points (CCEs) that the UE should monitor to detect the PDCCH. Each PDCCH candidate is defined as having 1, 2, 4, 8, or 16 CCEs according to the Algorithm (AL). Monitoring includes (blind) decoding of the PDCCH candidates. The set of PDCCH candidates decoded by the UE is defined as the PDCCH Search Space (SS). The SS can be a Common Search Space (CSS) or a UE-Specific Search Space (USS). The UE can obtain the DCI by monitoring PDCCH candidates in one or more SSs configured by the MIB or higher-layer signaling. Each CORESET is associated with one or more SSs, and each SS is associated with a CORESET. SSs can be defined based on the following parameters.

[0061] - controlResourceSetId: CORESET associated with SS

[0062] - monitoringSlotPeriodicityAndOffset: PDCCH monitoring periodicity (slot) and PDCCH monitoring offset (slot).

[0063] - monitoringSymbolsWithinSlot: PDCCH monitoring symbols within a slot (e.g., the first symbol of CORESET).

[0064] - nrofCandidates: The number of PDCCH candidates (one of 0, 1, 2, 4, 8, 16) for each AL={1, 2, 4, 8, 16}. The timing when a UE needs to monitor PDCCH candidates (e.g., time / frequency resources) is defined as a PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings can be configured in a time slot.

[0065] Table 3 shows the characteristics of each SS.

[0066] [Table 3]

[0067] Table 4 shows the DCI format transmitted on the PDCCH.

[0068] [Table 4]

[0069] DCI format 0_0 can be used to schedule PUSCH based on TB (or TB level), and DCI format 0_1 ​​can be used to schedule PUSCH based on TB (or TB level) or PUSCH based on code block group (CBG) (or CBG level). DCI format 1_0 can be used to schedule PDSCH based on TB (or TB level), and DCI format 1_1 can be used to schedule PDSCH based on TB (or TB level) or PDSCH based on CBG (or CBG level) (or DL-licensed DCI). DCI formats 0_0 / 0_1 can be referred to as UL-licensed DCI or UL scheduling information, and DCI formats 1_0 / 1_1 can be referred to as DL-licensed DCI or DL ​​scheduling information. DCI format 2_0 is used to transmit dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to transmit DL preemption information to the UE. DCI formats 2_0 and / or DCI format 2_1 can be transmitted to the corresponding group of UEs on the group common PDCCH (PDCCH pointing to a group of UEs).

[0070] DCI formats 0_0 and 1_0 can be referred to as fallback DCI formats, while DCI formats 0_1 and 1_1 can be referred to as non-fallback DCI formats. In fallback DCI formats, the DCI size / field configuration remains the same regardless of the UE configuration. Conversely, in non-fallback DCI formats, the DCI size / field configuration varies depending on the UE configuration.

[0071] PDSCH transmits DL data (e.g., DL Shared Channel Transport Block (DL-SCH TB)) using modulation schemes such as Quadrature Phase Shift Keying (QPSK), 16-element Quadrature Amplitude Modulation (16QAM), 64QAM, or 256QAM. TBs are encoded as codewords. PDSCH can transmit up to two codewords. Scrambling and modulation mapping can be performed on a codeword basis, and modulation symbols generated from each codeword can be mapped to one or more layers. Each layer, along with a demodulation reference signal (DMRS), is mapped to a resource, and OFDM symbol signals are generated from the layer mapped with the DMRS and transmitted through the corresponding antenna port.

[0072] PUCCH transmits uplink control information (UCI). UCI includes the following information.

[0073] - SR (Schedule Request): Information used to request UL-SCH resources.

[0074] - HARQ (Hybrid Automatic Repeat Request) - ACK (Acknowledgement): A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the DL data packet was successfully received. A 1-bit HARQ-ACK can be sent in response to a single codeword. A 2-bit HARQ-ACK can be sent in response to two codewords. HARQ-ACK responses include positive ACK (simply ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. The term HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0075] - CSI (Channel State Information): Feedback information for the DL channel. MIMO-related feedback information includes RI and PMI.

[0076] Table 5 shows exemplary PUCCH formats. Based on the PUCCH transmission duration, PUCCH formats can be divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4).

[0077] [Table 5]

[0078] PUCCH format 0 transmits up to 2 bits of UCI and is mapped in a sequence-based manner for easy transmission. Specifically, the UE sends a specific UCI to the BS by transmitting one of multiple sequences on the PUCCH of PUCCH format 0. The UE only transmits the PUCCH of PUCCH format 0 in the PUCCH resource configured for the corresponding SR when the UE sends an affirmative SR.

[0079] PUCCH format 1 transmits up to 2 bits of UCI, and the modulation symbols of UCI are spread in the time domain with orthogonal overlay code (OCC) (configured differently depending on whether frequency hopping is performed). DMRS is transmitted in symbols that do not transmit modulation symbols (i.e., transmitted in time division multiplexing (TDM)).

[0080] PUCCH format 2 transmits more than 2 bits of UCI, and the modulation symbols of the DCI are transmitted using DMRS in frequency division multiplexing (FDM). The DMRS is located at a density of 1 / 3 in symbols #1, #4, #7, and #10 of a given RB. A pseudo-noise (PN) sequence is used for the DMRS sequence. Frequency hopping can be enabled for 2-symbol PUCCH format 2.

[0081] PUCCH format 3 does not support UE multiplexing within the same PRBS and transmits more than 2 bits of UCI. In other words, PUCCH resources in PUCCH format 3 do not include OCC. Modulation symbols are transmitted in TDM using DMRS.

[0082] PUCCH format 4 supports multiplexing of up to four UEs in the same PRBS and transmits more than 2 bits of UCI. In other words, PUCCH resources in PUCCH format 3 include OCC. Modulation symbols are transmitted in TDM using DMRS.

[0083] PUSCH transmits UL data (e.g., UL Shared Channel Transport Block (UL-SCH TB)) and / or UCI based on CP-OFDM or DFT-s-OFDM waveforms. When PUSCH is transmitted in DFT-s-OFDM waveform, the UE transmits PUSCH via transform precoding. For example, when transform precoding is not possible (e.g., disabled), the UE may transmit PUSCH using CP-OFDM waveform, while when transform precoding is possible (e.g., enabled), the UE may transmit PUSCH using either CP-OFDM or DFT-s-OFDM waveform. PUSCH transmission can be dynamically scheduled via UL authorization in DCI, or semi-statically scheduled via higher-layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling such as PDCCH) (configured scheduling or configured authorization). PUSCH transmission can be performed in a codebook-based or non-codebook-based manner.

[0084] Figure 5 This illustrates exemplary PDCCH / PDSCH reception and ACK / NACK transmission processing. (Refer to...) Figure 5 The UE can detect the PDCCH in slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1). The PDCCH indicates the DL assignment offset K0 with the PDSCH and the PDSCH offset K1 with the HARQ-ACK report. For example, DCI format 1_0 and DCI format 1_1 may include the following information.

[0085] - Frequency domain resource assignment: Indicates the set of RBs assigned to the PDSCH.

[0086] - Time-domain resource assignment: Indicates the starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of K0 and the PDSCH in the time slot.

[0087] - PDSCH-to-HARQ_feedback timer indicator: Indicates K1.

[0088] - HARQ process ID (4 bits): The HARQ process ID that indicates the data (e.g., PDSCH or TB).

[0089] After receiving the PDSCH in time slot #(n+K0) according to the scheduling information of time slot #n, the UE can send a UCI on the PUCCH in time slot #(n+K1). The UCI may include a HARQ-ACK response to the PDSCH. For convenience, Figure 5 The assumption that the SCS of the PDSCH is equal to the SCS of the PUCCH and that slot #n1 = slot #(n+K0) should not be construed as limiting this disclosure. When the SCSs are different, K1 can be indicated / interpreted based on the SCS of the PUCCH.

[0090] When the PDSCH is configured to carry a maximum of one TB, the HARQ-ACK response can be configured in one bit. When the PDSCH is configured to carry a maximum of two TBs, if spatial bundling is not configured, the HARQ-ACK response can be configured in two bits; if spatial bundling is configured, the HARQ-ACK response can be configured in one bit. When time slot #(n+K1) is designated as the timing for HARQ-ACK transmissions of multiple PDSCHs, the UCI transmitted in time slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0091] Whether a UE should perform spatial binding in response to a HARQ-ACK response can be configured for each cell group (e.g., via RRC / higher-layer signaling). For example, spatial binding can be configured for individual HARQ-ACK responses sent on the PUCCH and / or on the PUSCH.

[0092] When up to two (or more) TBs (or codewords) can be received at once in the corresponding serving cell (which may be scheduled by a DCI) (e.g., when higher-layer parameters...). maxNrofCodeWordsScheduledByDCI Spatial binding is supported when 2 TB is specified. More than four layers can be used for 2TB of transmission, and up to four layers can be used for 1TB of transmission. As a result, when spatial binding is configured for a corresponding cell group, spatial binding can be performed on serving cells within the cell group that can be scheduled for more than four layers. A UE that wants to send a HARQ-ACK response via spatial binding can generate a HARQ-ACK response by performing a (bit-wise) logical AND operation on the A / N bits of multiple TBs.

[0093] For example, suppose a UE receives a DCI that schedules two TBs and receives the two TBs on the PDSCH based on the DCI. The UE performing spatial bundling can generate a single A / N bit by performing a logical AND operation between the first A / N bit of the first TB and the second A / N bit of the second TB. As a result, when both the first TB and the second TB are ACK, the UE reports the ACK bit value to the BS, and when at least one TB is NACK, the UE reports the NACK bit value to the BS.

[0094] For example, when only one TB is actually scheduled in a serving cell configured to receive two TBs, the UE can generate a single A / N bit by performing a logical AND operation on the A / N bit and bit value 1 of a TB. As a result, the UE reports the A / N bit of one TB to the BS.

[0095] Multiple parallel DL HARQ processes exist at the BS / UE for DL ​​transmission. While the BS awaits HARQ feedback indicating the success or failure of a previous DL transmission, multiple parallel HARQ processes allow for continuous DL transmission. Each HARQ process is associated with a HARQ buffer in the Media Access Control (MAC) layer. Each DL HARQ process manages status variables such as the number of MAC Physical Data Unit (PDU) transmissions, HARQ feedback to MAC PDUs in the buffer, and the current redundant version. Each HARQ process is identified by a HARQ process ID.

[0096] On the other hand, according to the HARQ-ACK bit (payload) configuration method, the HARQ-ACK codebook is mainly defined into three codebook types: Type 1, Type 2, and Type 3. In the case of Type 1 codebook, the HARQ-ACK payload is configured based on a combination of the candidate HARQ-ACK timing (K1) set (configured for the corresponding cell) and the candidate PDSCH timing (SLIV) set (e.g., a semi-static fixed-size codebook based on RRC signaling). In the case of Type 2 codebook, the codebook size can be dynamically changed based on the number of actually scheduled PDSCHs or the number of corresponding resource allocations (e.g., downlink assignment index DAI). In the case of Type 3 codebook, the HARQ-ACK payload is configured by mapping HARQ-ACK bits associated with the corresponding HPN (e.g., one-time A / N report) for each HARQ process number (HPN) according to the maximum HARQ process number (configured per cell for the corresponding cell). Recently, an enhanced Type 3 codebook has been added to the latest NR standard as a Type 3 codebook. The Enhanced Type 3 codebook does not report HARQ-ACK bits for all cells / HPNs at once to reduce signaling overhead. Instead, it reports HARQ-ACK bits for all cells / HPNs that are indicated to the Base Station (BS). A subset of cells / HPNs associated with the Enhanced Type 3 codebook is configured for the User Equipment (UE) via higher-layer signaling. Then, a DCI indication of the Enhanced Type 3 codebook can be triggered for one of the configured subsets for the UE. The UE can then report HARQ-ACKs for cells / HPNs belonging to the indicated subset.

[0097] In the case of a Type 1 codebook, with a set of multiple (e.g., N) candidate K1 values ​​(per cell for each cell) and A / N sub-payloads (including determining the A / N bit position / order corresponding to each SLIV that can be transmitted within the corresponding time slot) configured (defined as "SLIV pruning"), the combination of all SLIVs that can be transmitted (or scheduled to be transmitted) within the DL time slots before the K1 time slots starting from the A / N transmission time slot of each K1 value is calculated. The entire A / N codebook is then configured by concatenating such A / N sub-payloads to the N K1 values. In this case, the set of (N) DL time slots corresponding to each K1 value can be defined as a bundled window corresponding to the A / N transmission time slots.

[0098] In the case of a Type 2 HARQ-ACK codebook, the codebook for sending HARQ-ACK information on the same PUCCH / PUSCH is defined based on the counter-downlink assignment indicator (C-DAI) and total-DAI (T-DAI) values ​​indicated by the actually sent PDCCH. That is, the codebook is configured based on the PDCCH information actually sent to the UE. When the UE fails to detect a specific PDCCH, the UE sends a NACK on the corresponding PDCCH bit defined in the codebook. In this case, the UE can identify whether PDCCH detection has failed by the C-DAI and T-DAI values. The C-DAI is obtained by counting the cumulative number of {serving cell index, PDCCH monitoring time} pairs provided by PDSCH reception up to the current serving cell and the current PDCCH monitoring time. First, for multiple PDSCH receptions of the same {serving cell index, PDCCH monitoring time} pair, the PDSCH that was received first (i.e., assigned a lower C-DAI value) is counted first. Next, when multiple pairs of different {serving cell index, PDCCH monitoring timing} have the same PDCCH monitoring timing index, the pairs with the lower serving cell index are counted first.

[0099] In the case of a Type 3 codebook, specifically, the BS can configure either Mode 1, which involves feeding back both the HARQ-ACK and the corresponding NDI for the UE, or Mode 2, which involves feeding back only the HARQ-ACK without the NDI. When the UE is configured with Mode 1, the UE operates to feed back the HARQ-ACK and NDI received at the PDSCH for the corresponding HPN (indicated by the DCI) together with the HARQ process number (HPN).

[0100] Figure 6 An exemplary PUSCH transmission process is shown. (Refer to...) Figure 6 The UE can detect the PDCCH in time slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or 1_1). DCI format 1_0 or 1_1 may include the following information.

[0101] - Frequency domain resource assignment: Indicates the set of RBs assigned to PUSCH.

[0102] - Time-domain resource assignment: Indicates the slot offset K2 and the start position (e.g., OFDM symbol index) and duration (e.g., number of OFDM symbols) of the PUSCH within the slot. The start symbol and length of the PUSCH can be indicated by the start and length indicator value (SLIV) or separately.

[0103] Then, the UE can send the PUSCH in time slot #(n+K2) according to the scheduling information in time slot #n. The PUSCH includes the UL-SCH TB.

[0104] Carrier aggregation

[0105] NR can support wider uplink / downlink bandwidth by aggregating multiple uplink / downlink carriers (i.e., carrier aggregation). Signals can be transmitted / received across multiple carriers via carrier aggregation. When carrier aggregation is applied, each carrier (see Figure A2) can be called a component carrier (CC). CCs can be continuous or discontinuous in the frequency domain. The bandwidth of each CC can be determined independently. Asymmetric carrier aggregation, where the number of UL CCs differs from the number of DL CCs, is also possible.

[0106] - PCell (Primary Cell): When the UE is configured with carrier aggregation, the cell operating at the primary frequency (e.g., primary component carrier (PCC)) on which the UE performs the initial connection establishment procedure or initiates the connection reconstruction procedure. In the case of dual connectivity (DC), the primary cell group (MCG) cell operating at the primary frequency on which the UE performs the initial connection establishment procedure or initiates the connection reconstruction procedure.

[0107] - Secondary Cell (SCell): When the UE is configured with carrier aggregation, the cell that provides radio resources, other than the special cell.

[0108] - Primary SCG Cell (PSCell): In the case of DC, the secondary cell group (SCG) cell for random access is used by the UE when performing RRC reconfiguration and synchronization procedures.

[0109] - Special Cell (SpCell): In the case of DC, a special cell refers to the PCell of the MCG or the PSCell of the SCG. Otherwise (i.e., not in DC), a special cell refers to the PCell.

[0110] - Serving Cell (ServCell): Indicates the cell configured for a UE in the RRC_CONNECTED state. If CA / DA is not configured, only one serving cell (i.e., PCell) exists. If CA / DA is configured, the serving cell represents a set of cells including the special cell and all SCells.

[0111] Furthermore, control information can be configured to be sent and received only through specific cells. For example, UCI can be sent through a special cell (e.g., PCell). When a SCell that allows PUCCH transmission is configured (hereinafter, PUCCH-SCell), UCI can also be sent through PUCCH-SCell. As another example, the BS can allocate scheduling cells (sets) to reduce the complexity of PDCCH blind decoding (BD) on the UE side. For PDSCH reception / PUSCH transmission, the UE can perform PDCCH detection / decoding only in the scheduling cells. Additionally, the BS can send PDCCH only through the scheduling cells (sets). For example, PDCCH for downlink allocation can be sent in cell #0 (i.e., the scheduling cell), and the corresponding PDSCH (Cross-Carrier Scheduling (CCS)) can be sent in cell #2 (i.e., the scheduled cell). Scheduling cells (sets) can be configured in a UE-specific, UE-group-specific, or cell-specific manner. Scheduling cells include special cells (e.g., PCell).

[0112] For cross-carrier scheduling, the Carrier Indicator Field (CIF) is used. The CIF can be semi-statically disabled / enabled by UE-specific (or UE-group-specific) higher-layer (e.g., Radio Resource Control (RRC)) signaling. The CIF field is an x-bit field (e.g., x=3) in the PDCCH (i.e., DCI) and can be used to indicate the (serving) cell index of the scheduled cell.

[0113] - CIF disabled: CIF is not present in the PDCCH. The PDCCH on the scheduling cell is allocated PDSCH / PUSCH resources on the same cell. That is, the scheduling cell and the scheduled cell are the same.

[0114] - CIF Enabled: CIF is present in the PDCCH. Regarding the scheduling of the PDCCH, CIF can be used to allocate PDSCH / PUSCH resources on one of multiple cells. The scheduling cell can be the same as or different from the scheduled cell. PDSCH / PUSCH represents either PDSCH or PUSCH.

[0115] Figure 7 This is a diagram illustrating carrier aggregation. In Figure 7 In this scenario, assume three cells are aggregated. If CIF is disabled, only the PDCCH (Self-Carrier Scheduling (SCS)) for scheduling its PDSCH / PUSCH can be transmitted in each cell. On the other hand, if CIF is enabled via UE-specific (or UE-group-specific or cell-specific) higher-layer signaling and cell A is configured as the scheduling cell, not only can the PDCCH for scheduling cell A be transmitted in cell A, but also the PDCCH for scheduling the PDSCH / PUSCH of another cell (i.e., the scheduled cell) can be transmitted (Cross-Carrier Scheduling (CCS)). In this case, no PDCCH for scheduling its own cell is transmitted in cells B / C.

[0116] NR Shared Spectrum / Unlicensed Band (NR-U) Operation

[0117] Figure 8 This illustrates a wireless communication system supporting unlicensed frequency bands. For convenience, a cell operating in a licensed frequency band (hereinafter, L-band) is defined as an LCell, and the carrier of an LCell is defined as (DL / UL)LCC. A cell operating in an unlicensed frequency band (hereinafter, U-band) is defined as an UCell, and the carrier of an UCell is defined as (DL / UL)UCC. The carrier of a cell may represent the cell's operating frequency (e.g., center frequency). Cells / carriers (e.g., CC) may be collectively referred to as cells.

[0118] When carrier aggregation is supported, a UE can transmit and receive signals from the BS in multiple aggregated cells / carriers. If multiple control channels (CCs) are configured for a UE, one CC can be configured as the primary CC (PCC), and the others can be configured as secondary CCs (SCCs). Specific control information / channels (e.g., CSS PDCCH and PUCCH) can be configured to transmit and receive signals only in the PCC. Data can be transmitted and received in the PCC and / or SCC. Figure 8 In (a), the UE and BS transmit and receive signals in the LCC and UCC (Non-Standalone (NSA) mode). In this case, the LCC can be configured as the PCC and the UCC can be configured as the SCC. If multiple LCCs are configured for the UE, one specific LCC can be configured as the PCC and the other LCCs can be configured as the SCC. Figure 8 (a) corresponds to the LAA of the 3GPP LTE system. Figure 8(b) illustrates the scenario where the UE and BS transmit and receive signals in one or more UCCs without an LCC (SA mode). In this case, one UCC can be configured as a PCC, and the other UCCs can be configured as SCCs. For this purpose, PUCCH, PUSCH, and PRACH transmissions can be supported. Both NSA and SA modes are supported in the unlicensed frequency bands of the 3GPP NR system.

[0119] Unless otherwise specified, the following definitions apply to the terminology used in this disclosure.

[0120] - Channel: includes a carrier or a portion of a continuous RB that performs the Channel Access Procedure (CAP) in a shared spectrum.

[0121] - Channel Access Procedure (CAP): The process of assessing channel availability based on sensing before signal transmission to determine whether the channel is being used by other communication nodes. The basic unit of sensing is a sensing slot with a duration Tsl of 9µs. When the BS or UE senses the channel during the sensing slot duration, and the power detected is less than the energy detection threshold XThresh for at least 4µs within the sensing slot duration, the sensing slot duration Tsl can be considered idle. Otherwise, the 9µs sensing slot duration Tsl can be considered busy. CAP can also be referred to as Listen Before Talk (LBT).

[0122] - Channel occupancy: Transmission on the channel from BS / UE after CAP.

[0123] - Channel Occupancy Time (COT): The total time that the BS / UE and any BS / UE sharing the channel occupancy perform transmissions on the channel after the BS / UE's corresponding CAP. When determining COT, if the transmission gap is less than or equal to 25µs, the gap duration can also be included in the COT. Transmissions between the BS and its corresponding UE can share the COT.

[0124] - DL Transmission Burst: A collection of transmissions from the BS without any gaps greater than 16µs. Transmissions from the BS separated by gaps exceeding 16µs are considered separate DL transmission bursts. The BS can perform transmissions after gaps within a DL transmission burst without sensing channel availability.

[0125] - UL Transmission Burst: A collection of transmissions from the UE without any gaps greater than 16µs. Transmissions from the UE separated by gaps exceeding 16µs are considered separate UL transmission bursts. The UE can perform transmissions after gaps within a UL transmission burst without sensing channel availability.

[0126] - Discovery Burst: This includes DL transmission bursts that are confined within a window and associated with a duty cycle of the signal and / or channel set. In LTE-based systems, a discovery burst can be a BS-initiated transmission, including the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Cell-Specific Reference Signal (CRS), and also includes non-zero power CSI-RS. In NR-based systems, a discovery burst can be a BS-initiated transmission, including at least an SS / PBCH block, and also includes a CORESET for scheduling PDSCHs with SIB1, PDSCHs carrying SIB1, and / or PDCCHs with non-zero power CS-RS.

[0127] Figure 9 This illustrates a method for occupying resources in an unlicensed frequency band. According to regional regulations regarding unlicensed frequency bands, communication nodes in an unlicensed frequency band need to determine whether other communication nodes are using the channel before signal transmission. Specifically, a communication node may first perform carrier sensing (CS) before signal transmission to check whether other communication nodes are transmitting signals. If it is determined that other communication nodes are not transmitting signals, this means confirming a free channel assessment (CCA). When a CCA threshold configured via higher-layer (e.g., RRC) signaling or a predefined CCA threshold exists, if energy above the CCA threshold is detected in the channel, the communication node can determine that the channel is busy; otherwise, the communication node can determine that the channel is idle. For reference, in the Wi-Fi standard (802.11ac), the CCA threshold is set to -62 dBm for non-Wi-Fi signals and -82 dBm for Wi-Fi signals. Upon determining that the channel is idle, the communication node can begin transmitting signals in the UCell. This process may be referred to as Listen-Before-Talk (LBT) or Channel Access Procedure (CAP). LBT and CAP can be used interchangeably.

[0128] Table 6 shows the exemplary CAPs supported in NR-U.

[0129] [Table 6]

[0130] Configuration of multi-cell scheduling DCI and its higher-layer configuration information

[0131] New Radio (NR) supports a wide range of spectrum across various frequency ranges. The expectation is to increase the use of spectrum for 5G advanced applications by reusing (reprocessing) frequency bands used in previous generations. Specifically, in the case of Frequency Range 1 (FR1), which is a low-frequency band, the available spectrum tends to become more segmented and dispersed. In the case of Frequency Range 2 (FR2) and some FR1 bands, the available spectrum may become wider, thus potentially requiring the operation of multiple carriers / cells within the band. That is, it is necessary to improve throughput and coverage by using this dispersed spectrum band or wider bandwidth spectrum in a more power-efficient and flexible manner.

[0132] Improving flexibility and spectrum / power efficiency is crucial when scheduling data across multiple cells, including intra-band and inter-band cells. However, in current 5G NR scheduling schemes, the DCI can only schedule PUSCH / PDSCH for a single cell. With future spectrum expansion / changes, the demand for simultaneous scheduling of multiple cells is expected to increase. To reduce the control overhead caused by scheduling, it is advantageous to perform PUSCH / PDSCH scheduling for multiple cells through a single DCI.

[0133] Therefore, in the case of carrier aggregation (CA) of multiple cells, a multi-cell scheduling scheme can be considered in version 18 for simultaneously scheduling multiple (serving) cells / component carriers (CCs) (and PDSCH / PUSCH transmissions via cells / CCs) through a single DCI, in order to reduce the DCI overhead required for PDSCH / PUSCH scheduling.

[0134] Therefore, a method for configuring and interpreting the corresponding fields included in a multi-cell DCI is proposed to design the structure of a multi-cell DCI for performing the aforementioned multi-cell scheduling. Although this disclosure primarily describes multi-cell scheduling operations for PDSCH or PUSCH transmissions, the operational principles of the proposed method can be equivalently applied to multi-cell scheduling for PUSCH or PDSCH transmissions. Furthermore, in this disclosure, a cell can represent the (active) bandwidth portion (BWP) configured / indicated for the cell.

[0135] In the following text, multi-cell scheduling DCI may be referred to as multi-cell DCI or simply DCI, and may include at least one of downlink (DL) licensed DCI for scheduling PDSCH and uplink (UL) licensed DCI for scheduling PUSCH.

[0136] In the following description, a reference cell may be determined based on at least one of the following i) to viii), but this disclosure is not limited thereto. Within a group of cells simultaneously scheduled via the same multi-cell DCI (i.e., a set of co-scheduled cells) (or within each cell subgroup described below), the reference cell may be: i) the cell with the lowest (or highest) cell index; ii) the cell with the earliest (or latest) start symbol of the indicated PDSCH / PUSCH transmission (if multiple cells have the earliest (or latest) start symbol of the PDSCH / PUSCH transmission, then the cell with the lowest (or highest) cell index among the multiple cells); iii) the cell with the earliest (or latest) end symbol of the indicated PDSCH / PUSCH transmission. The cells are: (iv) the cell with the lowest (or highest) cell index among the multiple cells if they have the earliest (or latest) end symbol of the PDSCH / PUSCH transmission; (v) the cell indicated by the Carrier Indicator Field (CIF) value or the cell pre-specified by RRC; (v) the cell with the lowest (or highest) cell index within the entire set of cells that can be scheduled through any multi-cell DCI (i.e., the set of schedulable cells); (vi) the cell indicated by the CIF value; (vii) the cell through which multi-cell DCI is transmitted; and / or (viii) the cell pre-specified by RRC.

[0137] - Shared Cell Common Method: A method in which only one field is configured in the multi-cell DCI and the value indicated by the corresponding DCI field is publicly applied to all cells (scheduled via multi-cell DCI).

[0138] - Shared State Extension Method: A method in which only one field is configured in the multi-cell DCI and each of the multiple states indicated by the corresponding DCI field is configured / set to be a combination of multiple pieces of information for multiple cells (instead of information for a single cell).

[0139] The fields applying the shared cell common method and / or shared state extension method proposed in this disclosure can be configured as follows: i) configuring only one field in a multi-cell DCI (i.e., a field commonly applied to all cells belonging to the co-scheduled cell set); ii) configuring one field (commonly applied) for each cell subgroup when all cells belonging to the co-scheduled cell set are grouped (configured) into one or more cell subgroups (i.e., configuring a separate / independent field for the cell subgroup); iii) configuring one field (commonly applied) for each cell subgroup when all cells belonging to the schedulable cell set are grouped (configured) into one or more cell subgroups (i.e., configuring a separate / independent field for the cell subgroup). (i.e., the shared cell common / shared state extension method and its based field / information configuration / indication scheme can be applied to each cell subgroup). In the above, each cell subgroup can be configured / set as one or more specific cells belonging to the co-scheduled cell set or the schedulable cell set (e.g., some cells or all corresponding cells belonging to the co-scheduled cell set or the schedulable cell set).

[0140] The DCI field applying the shared cell common method proposed in this disclosure has the following structure: In existing single-cell DCI-based scheduling, a table is pre-configured via RRC or Medium Access Control-Control Element (MAC-CE) including one or more status / indexes (configured with different parameters / values ​​(combinations) for each cell), and one of the status / indexes in the table is indicated by the corresponding DCI field (e.g., a size indicator and / or rate matching (RM) indicator and / or zero-power channel state information-reference signal (ZP) bound to the Physical Resource Block (PRB). In the event of a CSI-RS trigger and / or a Sounding Reference Signal (SRS) request, a specific state / index indicated by a DCI field publicly configured for a cell set (e.g., a co-scheduled cell set or cell subgroup) applying a shared cell common method can be applied as follows: Option X) The specific state / index can be interpreted / applied as a combination of parameters / values ​​corresponding to the state / index in a table configured for each cell belonging to the cell set (i.e., for each cell); Option Y) The combination of parameters / values ​​corresponding to the state / index in a table configured for a specific reference cell in the cell set can be publicly applied to cells belonging to the cell set; or Option Z) In the case of a separate common table to be publicly applied to the cell set via RRC / MAC-CE in the same manner as described above, the combination of parameters / values ​​corresponding to the state / index in the common table can be publicly applied to cells belonging to the cell set.

[0141] Additionally, for some cells, values ​​for the corresponding state / code point may not need to be configured. For example, for the i-th state / code point, cell #2 may have the value x, while no value can be configured for cell #1 and cell #N. To interpret the shared cell common DCI field, the UE can be configured with information (e.g., a table) including the values ​​to be applied to each cell. For example, for the shared cell common DCI field, a first table can be configured for cell #1, a second table for cell #2, ..., and an Nth table can be configured for cell #N.

[0142] For example, a table configured for single-cell (SC) scheduling for each cell can also be used for multi-cell (MC) scheduling. For example, in a state where an SC table is configured for each cell and referenced by an SC DCI in SC format, an MC table referenced by an MC DCI can correspond to a combination of SC tables for multiple cells.

[0143] [Related to Type 1A fields: Handling invalid states]

[0144] First, a more specific example of the above shared cell public method (specifically, option X) is provided below (in the following text, for convenience, the field based on this configuration is referred to as the "Type 1A" field).

[0145] Firstly, in existing single-cell DCI-based scheduling, for a specific DCI field (e.g., BWP indicator, Open-Loop Power Control Parameter Set Indicator (i.e., OLPC indicator), ChannelAccess-CPex-CAPC (for PUSCH) (i.e., PUSCH LBT), beta offset indicator, and PDCCH Monitoring Adaptation Indicator), when N (different) parameters / values ​​(combinations) corresponding to the N states / code points / indices indicated by the corresponding DCI field are pre-configured via RRC or MAC-CE, if one of the N states / code points / indices is indicated by the corresponding DCI field, the UE can perform PDSCH / PUSCH transmission / reception operations by applying the parameters / values ​​(combinations) configured for the indicated state / code point / indice. In this case, the size of the DCI field can be determined as ceil{log2(N)} bits, where N can be configured to different values ​​(or the same value) for each cell.

[0146] For reference, in this disclosure, ceil(X) represents the smallest integer greater than or equal to X, floor(X) represents the largest integer less than or equal to X, and the value obtained by performing a modulo B operation on A represents the remainder obtained when A is divided by B.

[0147] For specific DCI fields in multi-cell DCI-based scheduling, when parameters / values ​​(combinations) for each state / code point / index are pre-configured for each cell (applied to single-cell DCI-based scheduling) as described above, if a specific state / code point / index is indicated by the corresponding DCI field, the UE can interpret and apply the parameters / values ​​(combinations) configured cell-by-cell for each cell to perform PDSCH / PUSCH transmission / reception operations for each cell's scheduling. For example, Figure 10 An example is shown for the DCI field of option X according to the shared cell public method. Figure 10 For ease of description, it is assumed that the co-scheduled cell set includes four cells; therefore, the actual number of co-scheduled cells can be four or fewer. The configuration can be interpreted / configured independently for each cell. Figure 10 The value indicated by a state (code point) in the DCI field. For example, assuming a first state / code point (e.g., 00) is indicated, the first state / code point could represent value a for cell #1, value b for cell #2, and value c for cell #3. Configuring values ​​independently for each cell means including the possibility of configuring different values ​​for different cells. However, the meaning is not limited to this case, and it does not exclude the possibility of configuring the same value for two or more cells. That is, it is sufficient for the cell values ​​to be configured independently, and there may not be a constraint that the independently configured values ​​should be the same or different from each other.

[0148] In multi-cell DCI-based scheduling, for the entire schedulable cell set (or each co-schedulable cell set), the size of a specific DCI field can be determined based on N values ​​configured for each cell belonging to the cell set, as follows: According to alternative scheme A), the size of the corresponding DCI field can be determined as ceil{log2(N_max)} bits based on N_max, where N_max is the maximum value (in this case, the corresponding DCI field can have a structure indicating up to (first) N_max states / code points / indices). Alternatively, according to alternative scheme B), the size of the corresponding DCI field can be determined as ceil{log2(N_min)} bits based on N_min, where N_min is the minimum value (in this case, the corresponding DCI field can have a structure indicating only up to (first) N_min states / code points / indices). For example, refer to... Figure 10Cell #1 has the smallest number of states (i.e., N_min), and cell #4 has the largest number of states (i.e., N_max). According to alternative scheme A), the size of the corresponding DCI field is ceil{log2(N_max)} = 2 bits based on cell #4. According to alternative scheme B), the size of the corresponding DCI field is ceil{log2(N_min)} = 1 bit based on cell #1.

[0149] When alternative option A) is applied, some cells may not have the values ​​configured for the corresponding state / code point. For example, refer to Figure 10 For cells #1 and #2, it is not necessary to configure values ​​for the third state (DCI field value = 2) in the corresponding table. More generally, for cell X (e.g., a cell where N is set to N_low, where N_low is less than N_max), when a specific state / index is indicated by a specific DCI field (e.g., the state / index corresponding to a value greater than DCI field value = {N_low-1}, that is, the state / index after the N_low state / index), for cell X, there may not be any parameters / values ​​(combinations) configured for the corresponding state / index. Considering this situation, the following operation is proposed (for convenience, M = ceil{log2(N_max)}, K = ceil {log2(N_low)} (M ≥ K) and L = floor {log2(N_low)} (M ≥ L)).

[0150] 1) Alternative Option 1: For cell X, only (selected) K bits out of the M bits in the DCI field can be interpreted and applied. These K bits can be, for example, the first K bits (MSB) or the last K bits (LSB). For example, refer to... Figure 10 In the cases of cell #1 and cell #2, only one bit (MSB or LSB) of the total two bits included in the DCI field can be selected and applied. If the binary value of the selected bit (MSB or LSB) is 0, then value a can be applied to cell #1 and value b can be applied to cell #2.

[0151] A. There may be cases where the status / index corresponding to a field value greater than {N_low-1} is indicated by K bits, and in such cases, alternative schemes 2, 3, or 6 described below can be applied. For example, refer to... Figure 10In the cases of cells #1 and #2, only one bit (MSB or LSB) of the total two bits included in the DCI field can be selected and applied. If the binary value of the selected bit is 1, the value e can be applied to cell #2, but the value to be applied may not exist in the table of cell #1. To solve this problem, alternative scheme 3 or alternative scheme 6 can be applied.

[0152] B. Alternatively, for cells configured for multi-cell DCI scheduling, the N value configured for the DCI field based on the shared cell common method (specifically, option X) can be limited to 2. A (where A is a positive integer) in the form of.

[0153] C. For example, in the case of the BWP indicator field, when N_max=4 and N_low=2 is configured for cell X (see, for example, [link to relevant documentation]). Figure 10 When the UE operates on cell X (#2), it can interpret only the MSB1 bit or LSB1 bit in the BWP indicator field (in the multi-cell DCI) and treat the BWP index configured for its corresponding state as an indication.

[0154] D. As another example, in the case of the OLPC indicator field, when N_max=4 and N_low=2 is configured for cell X (see, for example, [link to relevant documentation]). Figure 10 When operating in cell #2, the UE can interpret only the MSB 1 bit or LSB 1 bit in the OLPC indicator field (in the multi-cell DCI) and treat the power control parameter set index configured for the corresponding state as an indication to operate for cell X.

[0155] E. As another example, in the case of the PUSCH LBT field, when N_max=8 and N_low=4 is configured for cell X, the UE can interpret only the MSB 2 bits or LSB 2 bits in the PUSCH LBT field (in multi-cell DCI) and regard the LBT-related parameters / values ​​(combinations) configured for the corresponding state as being instructed to operate for cell X.

[0156] 2) Alternative Option 2: When the status / index corresponding to a field value greater than {N_low-1} is indicated by the DCI field, specific parameters / values ​​(combinations) that are pre-configured / defined individually can be applied to cell X. For example, refer to Figure 10When the DCI field indicates a value greater than binary 00, Alternative Scheme 2 can be applied to cell #1. When the DCI field indicates a value greater than binary 01, Alternative Scheme 2 can also be applied to cell #2 (other than cell #1). When the DCI field indicates a value greater than binary 10, Alternative Scheme 2 can also be applied to cell #3 (other than cell #1 and cell #2).

[0157] A. A specific parameter / value (combination) can be configured / defined as a parameter / value (combination) associated with a specific one (e.g., lowest or highest) of N_low states / indices pre-configured for cell X.

[0158] B. For example, in the case of the BWP indicator field, when N_low=2 is configured for cell X and the state indicated by the BWP indicator field (in multi-cell DCI) has a value greater than 1 (i.e., bit 01) (i.e., when the corresponding state is bit 10 or 11 (instead of bit 00 or 01)), the UE can treat the BWP index configured for the lowest state 0 (or a specific state configured separately) as indicated for cell X and operate accordingly.

[0159] C. As another example, in the case of the OPLC indicator field, when N_low=2 is configured for cell X and the state indicated by the OPLC indicator field (in multi-cell DCI) has a value greater than 1 (i.e., bit 01), the UE can treat the power control parameter set index configured for the lowest state 0 (or a specific state configured separately) as indicated for cell X and operate accordingly.

[0160] D. As another example, in the case of the PUSCH LBT field, when N_low=4 is configured for cell X and the state indicated by the OPLC indicator field (in multi-cell DCI) has a value greater than 3 (i.e., bit 011), the UE can treat the LBT-related parameters / values ​​(combinations) configured for the lowest state 0 (or a specific state configured individually) as indicated for cell X and act accordingly.

[0161] 3) Alternative Option 3: When the DCI field indicates the status / index corresponding to a field value greater than {N_low-1}, the UE can assume that there is no PDSCH / PUSCH scheduling for cell X.

[0162] - For example, refer to Figure 10Assuming that Alternative Scheme 3 is applied alone (without Alternative Scheme 1), Alternative Scheme 3 can be applied to cell #1 when a value greater than binary value 00 is indicated by the DCI field, and Alternative Scheme 3 can also be applied to cell #2 (other than cell #1) when a value greater than binary value 01 is indicated by the DCI field.

[0163] - Assuming that alternative scheme 3 is applied in addition to alternative scheme 1 as described above, according to alternative scheme 1, in the case of cell #1, only one bit (MSB or LSB) of the total two bits included in the DCI field can be selected and applied. If the binary value of the selected bit is 1, then alternative scheme 3 can be applied to cell #1 because there is no value to be applied in the table for cell #1.

[0164] - When Alternative Option 3 is applied (regardless of whether Alternative Option 1 is applied), Alternative Option 3 can be applied to cell #3 if the DCI field indicates a value greater than the binary value 10.

[0165] A. According to the application of alternative scheme 3, the UE can ignore the PDSCH / PUSCH transmission / reception operation on cell X (and, in the case of PDSCH, the UE can feed back the corresponding HARQ-ACK as NACK).

[0166] B. For example, in the case of the BWP indicator field (or OLPC indicator field), when N_low=2 is configured for cell X and the state indicated by the BWP indicator field (or OLPC indicator field) (in multi-cell DCI) has a value greater than 1 (i.e., bit 01), the UE can operate by assuming that there is no PDSCH / PUSCH scheduling for cell X.

[0167] 4) Alternative Option 4: For cell X, the UE can additionally configure and apply {N_max-N_low}=N_gap parameters / values ​​(combinations) corresponding to the corresponding states / indices from state / index N_low to state / index N_max-1. For example, refer to... Figure 10 For cell #1, you can additionally configure mappings to binary values ​​01, 10, and 11. For cell #2, you can additionally configure mappings to binary values ​​10 and 11. For cell #3, you can additionally configure mappings to binary value 11.

[0168] A. Additional parameters / values ​​(combinations) can be configured to be associated with specific N_gap states / indices out of the N_low states / indices pre-configured for cell X.

[0169] B. For example, in the case of the BWP indicator field, when N_max=4 and N_low=2 is configured for cell X, the BWP index corresponding to the two states (i.e., state 2 and state 3) can be additionally configured and applied for cell X.

[0170] C. As another example, in the case of the OLPC indicator field, when N_max=4 and N_low=2 is configured for cell X, the power control parameter set index corresponding to the two states (i.e., state 2 and state 3) can be additionally configured and applied for cell X.

[0171] D. As another example, in the case of the PUSCH LBT field, when N_max=8 and N_low=4 is configured for cell X, LBT-related parameters / values ​​(combinations) corresponding to the four states from state 4 to state 7 can be additionally configured and applied for cell X.

[0172] 5) Alternative Option 5: For cell X, the UE can interpret and apply the state / index indicated by the DCI field as a state / index corresponding to the value obtained by performing a modulo N_low operation on the state / index indicated by the DCI field. For example, refer to Figure 10 The "mod 1 (DCI field value)" operation can be applied to cell #1, the "mod 2 (DCI field value)" operation can be applied to cell #2, and the "mod 3 (DCI field value)" operation can be applied to cell #3.

[0173] A. For example, when N_low=5 and N_max=8, the status / index {0,1,2,3,4,5,6,7} indicated by the DCI field can be interpreted and applied as the status / index {0,1,2,3,4,0,1,2} for cell X.

[0174] B. For example, in the case of the BWP indicator field, when N_max=4 and N_low=2 is configured for cell X, the UE can operate for cell X by interpreting and applying the states 0 / 1 / 2 / 3 indicated by the DCI field as states 0 / 1 / 0 / 1 respectively and treating the BWP index configured for the corresponding state as the indicated state.

[0175] C. As another example, in the case of the OLPC indicator field, when N_max=4 and N_low=2 is configured for cell X, the UE can operate for cell X by interpreting and applying the states 0 / 1 / 2 / 3 indicated by the DCI field as states 0 / 1 / 0 / 1 respectively and treating the power control parameter set index configured for the corresponding state as being indicated.

[0176] D. As another example, in the case of the PUSCH LBT field, when N_max=8 and N_low=4 is configured for cell X, the UE can operate for cell X by interpreting and applying the states 0 / 1 / 2 / 3 / 4 / 5 / 6 / 7 indicated by the DCI field as states 0 / 1 / 2 / 3 / 0 / 1 / 2 / 3 respectively and treating the LBT-related parameters / values ​​(combinations) configured for the corresponding states as being indicated.

[0177] 6) Alternative Option 6: When the status / index corresponding to a field value higher than {N_low-1} is indicated by the DCI field, the most recently indicated status / index can be applied to cell X and maintained.

[0178] - For example, refer to Figure 10 Assuming Alternative Scheme 6 is applied alone (without applying Alternative Scheme 1), when the DCI field of the currently received first DCI indicates a value greater than binary value 00, the indication of the second DCI preceding the first DCI can be applied to / maintained for cell #1 (the second DCI is the last DCI indicating a valid value (that is, the field value for cell #1 that is equal to or less than {N_low-1})). Alternative Scheme 6 can also be applied to cell #2 (other than cell #1) when the DCI field indicates a value greater than binary value 01.

[0179] - Assuming that alternative scheme 6 is applied in addition to alternative scheme 1 as described above, according to alternative scheme 1, in the case of cell #1, only one bit (MSB or LSB) of the total two bits included in the DCI field can be selected and applied. If the binary value of the selected bit is 1, the indication of the second DCI before the currently received first DCI can be applied / maintained for cell #1, because there is no value to be applied in the table of cell #1 (the second DCI is the last DCI that indicates a valid value (that is, the field value for cell #1 that is equal to or less than {N_low-1}).

[0180] - When Alternative Scheme 6 is applied (regardless of whether Alternative Scheme 1 is applied), if the DCI field indicates a value greater than the binary value 10, the indication of the second DCI before the currently received first DCI can be applied / maintained for cell #3 (the second DCI is the last DCI indicating a valid value (that is, the field value for cell #3 that is equal to or less than {N_low-1}).

[0181] A. Therefore, the UE can perform PDSCH / PUSCH transmission / reception operations on cell X by applying / maintaining the state / index of the most recent indication for cell X.

[0182] B. For example, in the case of the BWP indicator field (or OLPC indicator field), when N_low=2 is configured for cell X and the state indicated by the BWP indicator field (or OLPC indicator field) (in multi-cell DCI) has a value greater than 1 (i.e., bit 01), the UE can operate for cell X such that the most recently indicated current active BWP index (or most recently indicated power control parameter set index) is maintained / applied.

[0183] 7) Alternative Option 7: For cell X, the UE can interpret and apply only the first L bits (MSB) or only the last L bits (LSB) of the M bits in the DCI field.

[0184] A. In this case, for cell X, the DCI field can indicate only the lowest (or highest) of the N_low states / indices (configured for the single-cell (scheduling) DCI of cell X). L One status / index (and 2 configured for this) L (Combinations of parameters / values).

[0185] B. For example, in the case of the BWP indicator field, when N_max=4 and N_low=3 is configured for cell X, the UE can operate for cell X by interpreting only the MSB 1 bit or LSB 1 bit in the 2-bit BWP indicator field (in the multi-cell DCI) and treating the BWP index configured for the lowest (or highest) of the three states (corresponding to N_low) as the indication.

[0186] C. As another example, in the case of the OLPC indicator field, when N_max=4 and N_low=3 is configured for cell X, the UE can operate for cell X by interpreting only the MSB 1 bit or LSB 1 bit in the 2-bit OLPC indicator field (in multi-cell DCI) and treating the power control parameter set index configured for one of the lowest (or highest) states (corresponding to the three states of N_low) as being indicated.

[0187] D. As another example, in the case of the PUSCH LBT field, when N_max=8 and N_low=6 is configured for cell X, the UE can operate for cell X by interpreting only the MSB 2 bits or LSB 2 bits in the 3-bit PUSCH LBT field (in the multi-cell DCI) and treating the LBT-related parameters / values ​​(combinations) configured for one of the lowest (or highest) four states (corresponding to the six states of N_low) as instructions.

[0188] When the shared cell common method (based on option X) is applied to the BWP indicator field, one of the states indicated by the BWP indicator field in the multi-cell DCI can be configured to indicate "no BWP index switching" or "maintain current active BWP". When the corresponding state is indicated, the UE can operate to maintain the current active BWP without changing the BWP index for all cells scheduled through the DCI.

[0189] [Methods for configuring / setting (multi-cell) tables for shared state extension methods]

[0190] When the shared state extension method proposed in this disclosure is applied to a specific DCI field (e.g., TDRA field, RM indicator, ZP CSI-RS trigger, TCI field, SRS request, SRS offset indicator, etc.), only one field can be configured in the multi-cell DCI (which is commonly applied to multiple co-scheduled cells). Each row in the table referenced by the corresponding field can be configured / set as a combination of cell-specific (PDSCH / PUSCH transmit / receive related) parameters / values ​​(sets) for multiple cells (belonging to the entire schedulable cell set) (rather than a single cell-specific (PDSCH / PUSCH transmit / receive related) parameters / values ​​(sets)). For example, in the case of the TDRA field, each row can be configured / set to a combination of {K0 or K2, SLIV, PDSCH or PUSCH mapping type A / B}; in the case of the RM indicator, each row can be configured / set to a combination of rate matching modes; in the case of ZP CSI-RS triggering, each row can be configured / set to a combination of aperiodic ZP CSI-RS resource set indices; in the case of the TCI field, each row can be configured / set to a combination of TCI states; in the case of SRS request, each row can be configured / set to a combination of aperiodic SRS resource set indices; and in the case of SRS offset indicator, each row can be configured / set to a combination of slot offsets. Therefore, when a specific code point (or state) is indicated by a field, a combination of parameters / values ​​(sets) of multiple cells configured in the rows (indexes) of the (multi-cell) table corresponding to the code point / state can be applied to PDSCH / PUSCH transmission / reception operations on co-scheduled cells.

[0191] Multi-cell tables, for example, can be used as Figure 11 The structure configuration shown can have the following structure: wherein, for each row (index) in the table, a combination of parameters / values ​​(sets) of multiple cells (belonging to the entire schedulable cell set) is configured (e.g., in...). Figure 11In the case of row index 0 in the table, the parameters / values ​​(sets) for cells 1 / 2 / 3 / 4 are configured as A0 / B0 / C0 / D0. The values ​​configured for each cell in each row of the multi-cell table can be configured as row indices in the (single-cell) table for the corresponding cell's single-cell (scheduling) DCI configuration (e.g., in the case of TDRA field, TCI field, ZP CSI-RS trigger, SRS request, or SRS offset indicator). Alternatively, the values ​​configured for each cell in each row of the multi-cell table can be configured as code points (or states) for specific fields in the corresponding cell's single-cell DCI (e.g., in the case of TCI field, RM indicator, ZP CSI-RS trigger, SRS request, or SRS offset indicator). Therefore, parameters / values ​​(sets) configured for the corresponding row index in the single-cell table, or parameters / values ​​(sets) configured for the corresponding field's code point / state in the single-cell DCI, can be configured in the rows of the multi-cell table. For example, in Figure 11 In row index 0 of the table, A0 / B0 / C0 / D0 corresponding to cells 1 / 2 / 3 / 4 can represent row index A0 / B0 / C0 / D0 configured in the single-cell table for cells 1 / 2 / 3 / 4, or it can represent the code point / state A0 / B0 / C0 / D0 field configured in the single-cell DCI for cells 1 / 2 / 3 / 4. Similarly, A0 / A1 / A2 corresponding to cell 1 in row indices 0 / 1 / 2 can represent row index A0 / A1 / A2 configured in the single-cell table for cell 1, or it can represent the code point / state A0 / A1 / A2 field configured in the single-cell DCI for cell 1.

[0192] For example, in the case of the RM indicator field, the corresponding field in the single-cell DCI can have a structure indicating whether rateMatchPatternGroup1 and rateMatchPatternGroup2 are applied via a 2-bit bitmap, and the corresponding code point (or state) 0 / 1 / 2 / 3 can be configured as the value for the corresponding cell in each row of the multi-cell table. As another example, in the case of the SRS request field, the corresponding field can have a structure (for cells configured with SUL carriers) indicating one of the non-SUL carrier and SUL carrier via the MSB 1 bit in the 3-bit field of the single-cell DCI and indicating the aperiodic SRS resource set index via the remaining 2 bits, or (for cells not configured with SUL carriers) indicating the aperiodic SRS resource set index via the 2-bit field of the single-cell DCI. Therefore, the corresponding code point (or state) 0 / 1 / 2 / 3 / 4 / 5 / 6 / 7 (for cells configured with SUL carriers) or the corresponding code point (or state) 0 / 1 / 2 / 3 (for cells not configured with SUL carriers) can be configured as the value for the corresponding cell in each row of the multi-cell table. Alternatively, through multi-cell DCI, SRS requests can be allowed only for non-SUL carriers (even for cells configured with SUL carriers). In this case, the code point (or state) 0 / 1 / 2 / 3 corresponding to the indication via the remaining 2 bits of the aperiodic SRS resource set index excluding the MSB 1 bit can be configured as the value for the corresponding cell in each row of the multi-cell table. As another alternative, through multi-cell DCI, SRS requests can be allowed only for the carriers among non-SUL carriers and SUL carriers that have been most recently indicated / configured / activated (for cells configured with SUL carriers). In this case, the code point (or state) 0 / 1 / 2 / 3 corresponding to the indication via the remaining 2 bits of the aperiodic SRS resource set index excluding the MSB 1 bit can be configured as the value for the corresponding cell in each row of the multi-cell table.

[0193] Considering that the BWP indicator field in the multi-cell DCI indicates the operation of the BWP index for multiple cells, the multi-cell table can be configured as follows.

[0194] 1) Option 1: Considering the indication operation based on the BWP indicator field of type 1A (alternative schemes A / B and / or alternative schemes 1 / 2 / 3 / 4 / 5 / 6 / 7), a multi-cell table can be configured for each code point (or state) corresponding to the code point (or state) (belonging to the entire schedulable cell set) based on a combination of cell-specific BWP indexes (belonging to the entire schedulable cell set) corresponding to the code point (or state).

[0195] A. For example, refer to Figure 12Assuming the entire schedulable cell set consists of cells 1 / 2 / 3, and for code points (or states) 0 / 1 / 2 in the BWP indicator field, BWP indices a0 / a1 / a2 correspond to cell 1 (or are indicated for cell 1), BWP indices b0 / b1 / b2 correspond to cell 2 (or are indicated for cell 2), and BWP indices c0 / c1 / c2 correspond to cell 3 (or are indicated for cell 3) (through indication operations based on the BWP indicator field of type 1A (i.e., based on alternative schemes A / B and / or alternative schemes 1 / 2 / 3 / 4 / 5 / 6 / 7)). According to option 1, as... Figure 12 As shown in (c), the code point and corresponding value of a second-type (shared state extension) field can be defined for the cell-specific BWP index combination {a0, b0, c0} corresponding to code point (or state) 0 of the BWP indicator field (which is a first-type field (e.g., type 1A)). Similarly, the code point and corresponding value of a second-type (shared state extension) field can be defined for each of the cell-specific BWP index combinations {a1, b1, c1} corresponding to code point (or state) 1 of the BWP indicator field and the cell-specific BWP index combinations {a2, b2, c2} corresponding to code point (or state) 2 of the BWP indicator field. Therefore, multiple cell tables (e.g., Figure 12 (c)).

[0196] B. When including cells that are configured to operate with only a specific BWP (index) via RRC and do not have a BWP index indication via DCI, for each of the code points (or states) in the BWP indicator field, the combination of cell-specific BWP indexes corresponding to the code point (or state) can be determined by including the corresponding specific BWP (index) of the cell, and a multi-cell table can be configured based on this.

[0197] i. For example, when only one specific BWP index c0 is configured for cell 3 in the example above, multiple cell tables can be configured for each of the cell-specific BWP index combinations {a0, b0, c0} corresponding to code point (or state) 0, the cell-specific BWP index combinations {a1, b1, c0} corresponding to code point (or state) 1, and the cell-specific BWP index combinations {a2, b2, c0} corresponding to code point (or state) 2.

[0198] C. Additionally, when including cells that are configured to operate by switching between multiple (e.g., N) BWPs (indexes) based on a specific timer without having a BWP index indicated by the DCI, for each of all code points (or states) in the BWP indicator field, N combinations of cell-specific BWP indexes corresponding to the code point (or state) can be determined by including each of the N BWPs (indexes) of the cell, and a multi-cell table can be configured based on this.

[0199] i. For example, when two BWP indices c0 / c1 based on a specific timer (handover) operation are configured for cell 3 in the example above, a multi-cell table can be configured for each of the cell-specific BWP index combinations {a0, b0, c0} and {a0, b0, c1} corresponding to code point (or state) 0, the cell-specific BWP index combinations {a1, b1, c0} and {a1, b1, c1} corresponding to code point (or state) 1, and the cell-specific BWP index combinations {a2, b2, c0} and {a2, b2, c1} corresponding to code point (or state) 2.

[0200] D. When all cells belonging to the entire schedulable cell set are configured to operate via RRC using only a specific BWP (index) without having a BWP index indication via DCI or by switching between multiple BWPs (indexes) based on a specific timer, a multi-cell table can be configured for each of all possible cell-specific BWP (index) combinations, or a multi-cell table can be configured and applied based on Option 2 below.

[0201] i. For example, when only one BWP index a0 is configured for cell 1, only one BWP index b0 is configured for cell 2, and only one BWP index c0 is configured for cell 3, a multi-cell table can be configured for only one cell-specific BWP index combination {a0, b0, c0}. As another example, when only one BWP index a0 is configured for cell 1, only one BWP index b0 is configured for cell 2, and two BWP indices c0 / c1 based on a specific timer (handover) operation are configured for cell 3, a multi-cell table can be configured for each of the two cell-specific BWP index combinations {a0, b0, c0} and {a0, b0, c1}. As another example, when two BWP indices a0 / a1 based on a specific timer (handover) operation are configured for cell 1, two BWP indices b0 / b1 based on a specific timer (handover) operation are configured for cell 2, and two BWP indices c0 / c1 based on a specific timer (handover) operation are configured for cell 3, a multi-cell table can be configured for each of the eight cell-specific BWP index combinations {a0, b0, c0}, {a0, b0, c1}, {a0, b1, c0}, {a0, b1, c1}, {a1, b0, c0}, {a1, b0, c1}, {a1, b1, c0}, and {a1, b1, c1}.

[0202] 2) Option 2: For each cell (belonging to the entire schedulable cell set), when a set of values ​​corresponding to the cell in each row of the multi-cell table is configured for each BWP index of the cell (e.g., a row index in a single-cell table or a code point / status field in a single-cell DCI field) (for convenience, this set is referred to as the "per-cell sub-table") (e.g., Figure 11 When {A0, A1, A2} in the table can be a per-cell sub-table corresponding to cell 1, the multi-cell table can be configured and applied by cascading the per-cell sub-tables of multiple cells according to the cell-specific (active) BWP index combination indicated by the multi-cell DCI.

[0203] A. For example, when the entire schedulable cell set consists of cells 1 and 2, the per-cell sub-table corresponding to the BWP indexes a0 / a1 of cell 1 is configured as {A0_0, A1_0} and {A0_1, A1_1}, and the per-cell sub-table corresponding to the BWP indexes b0 / b1 of cell 2 is configured as {B0_0, B1_0} and {B0_1, B1_1}. If the cell-specific (active) BWP index combination indicated by the multi-cell DCI is {a0, b0}, the multi-cell table can be configured and applied by cascading the per-cell sub-tables {A0_0, A1_0} and {B0_0, B1_0}.

[0204] 3) Option 3: When only one multi-cell table is configured for all cells (belonging to the schedulable cell set), the values ​​configured in the per-cell sub-table (e.g., row index in the single-cell table or code point / status field in the single-cell DCI) of the multi-cell table can be interpreted / applied to the values ​​configured in the BWP (index) (e.g., row index in the single-cell table or code point / status field in the single-cell DCI) of the corresponding cell, based on the cell-specific (active) BWP index combination indicated by the multi-cell DCI.

[0205] (1) When applying option 3, handle issues outside the scope.

[0206] Specifically, option 3 can be described as follows: When only one multi-cell table is configured for all cells (belonging to the schedulable cell set) (and for all BWPs configured for the cells) (e.g., having a table with...), Figure 11 When the table has the same structure as the table, the values ​​configured in the per-cell sub-table (or column) (e.g., row index in a single-cell table or code point / status field in a single-cell DCI) of the multi-cell table can be interpreted / applied to the values ​​configured in the corresponding cell-specific (active) BWP index (e.g., row index in a single-cell table or code point / status field in a single-cell DCI) based on the cell-specific (active) BWP index combination indicated by the BWP indicator field in the multi-cell DCI. For example, based on Figure 11 In the table, when a BWP index X is indicated for cell 1 via the BWP indicator field in a multi-cell DCI, the values ​​{A0, A1, A2, ...} configured in the columns associated with cell 1 in the table can be interpreted / applied as values ​​configured for BWP index X (e.g., a row index in a single-cell table or a code point / status field in a single-cell DCI). Similarly, when a BWP index Y is indicated for cell 1 via the BWP indicator field in a multi-cell DCI, the values ​​{A0, A1, A2, ...} can be interpreted / applied as values ​​configured for BWP index Y (e.g., a row index in a single-cell table or a code point / status field in a single-cell DCI).

[0207] The values ​​of the columns (or sub-tables) for each cell in a multi-cell table can be configured using the maximum number of bits among the number of bits used to configure the corresponding row in the single-cell table (for the corresponding BWP of the corresponding cell), or using the maximum number of bits among the number of bits corresponding to the size of the field in the single-cell DCI (for the corresponding BWP of the corresponding cell). Figure 13 This is a diagram illustrating the table configuration for multi-cell scheduling DCI according to embodiments of this disclosure. Figure 13In (d), the table configuration is for the shared state extension method and can be provided via higher-level signaling (e.g., RRC). Specific DCI fields included in the MC DCI can indicate specific rows (here, rows can also be referred to as entries) in the configuration table, and these specific DCI fields can be shared state extension DCI fields used to indicate BWP-specific parameters other than TDRA (e.g., RM indicator, ZP CSI-RS trigger, TCI field, SRS request, SRS offset indicator, etc.). See reference... Figure 13 In (a), four BWPs are configured for cell 1, two for cell 2, three for cell 3, and four for cell 4. BWP-specific parameter configurations can be provided for each BWP, and the number of BWP-specific parameters configured for each BWP can be independent. For example, A BWP-specific parameters can be configured for BWP1 in cell 1, E BWP-specific parameters can be configured for BWP1 in cell 2, I BWP-specific parameters can be configured for BWP1 in cell 3, and M BWP-specific parameters can be configured for BWP1 in cell 4. Under this configuration, the SC DCI can indicate the BWP-specific parameters through a specific DCI field (referred to as the first DCI field for convenience). For example, refer to... Figure 13 (c) The first DCI field of the SC DCI for BWP1 in cell 4 can indicate one of the M BWP-specific parameters configured for BWP1 in cell 4. In this case, the size of the first DCI field can be configured to (at least) [value missing]. ┌ (log2M) ┐ One bit. Here, ┌ ┐ This represents the upper limit function. Figure 13 The table (d) has four per-cell columns, where the term "column" can also be referred to by another term such as information, field, or sequence. The size of the per-cell columns can be configured independently for each cell in the table. For example, the size of the per-cell columns for cell 1 can be configured based on the maximum number of bits required to indicate specific BWP parameters. For example, it can be based on Max( ┌ (log2A) ┐ , ┌ (log2B) ┐ , ┌ (log2C) ┐ , ┌ (log2D) ┐ (or equivalently,) ┌ (log2Max(A, B, C, D)) ┐ Configure the size of each cell column in cell 1. This can be based on Max( ┌(log2E) ┐ , ┌ (log2F) ┐ (or equivalently,) ┌ (log2Max(E, F)) ┐ Configure the size of the per-cell column for cell 2. The MC DCI can include a BWP indicator field and a BWP-specific parameter indicator field, and Figure 13 The rows of table (d) can be indicated by the BWP-specific parameter indicator field. Through the row indicator, a BWP-specific parameter index can be provided for each cell, and the indicated BWP-specific parameter index can be interpreted based on the indicated BWP. For example, when BWP 2 is indicated via the BWP indicator field, the indicated BWP-specific parameter index for cell 1 could be... Figure 13 The index of one of the B BWP-specific parameters in the BWP2 configuration for cell 1 shown in (a) indicates the BWP-specific parameter.

[0208] In this scenario, if the BWP (index) in the multi-cell DCI is configured with a number of bits (Y) smaller than the maximum number of bits (X) for the cell indication (for a row in the single-cell table or a field in the single-cell DCI), then only the Y bits corresponding to the LSBs of the X bit values ​​configured in the cell's column (multi-cell table) can be interpreted / applied for the BWP (index) (as a row index in the single-cell table configured for the BWP (index) or as a code point / state in a field in the single-cell DCI configured for the BWP (index)). In the above case, if the value corresponding to the Y bits is an unconfigured / invalid value in the single-cell table or single-cell DCI of the BWP (index), the UE can ignore PUSCH / PDSCH transmission / reception on that cell by assuming no scheduling exists for that cell. Alternatively, the UE can discard the DCI by treating the multi-cell DCI as an error or apply one of alternative schemes 1 / 2 / 3 / 4 / 5 / 6 / 7.

[0209] (2) Minimum applicable scheduling offset (min K0 / K2) indicator field

[0210] The minimum value of the offset (K0) between the DCI (or PDCCH) and the PDSCH indicated to the UE via the DCI for scheduling the PDSCH is called min K0, and the minimum value of the offset (K2) between the DCI (or PDCCH) and the PUSCH indicated to the UE via the DCI for scheduling the PUSCH is called min K2. The DCI may include a minimum applicable scheduling offset indicator field for indicating min K0 / min K2. When min K0 / min K2 is indicated via the minimum applicable scheduling offset indicator field in the DCI, the UE may not expect the indicated K0 / K2 values ​​to be less than the indicated values ​​of min K0 / min K2 via the DL-licensed / UL-licensed DCI.

[0211] To support effective UE power saving operations in multi-cell scheduling through the indication of min K0 / K2, the presence / absence of min K0 / K2 can be configured uniformly for cells belonging to the entire schedulable cell set or cells belonging to each co-schedulable cell set (e.g., the value of min K0 / K2 can be specified to be configured for all corresponding cells or not configured for all corresponding cells, or the presence / absence and / or value of min K0 / K2 can be configured based on the schedulable cell set or co-schedulable cell set (typically for all cells belonging to the corresponding set)). Alternatively, the value of min K0 / K2 can be specified to be the same for all or some cells belonging to the schedulable cell set or co-schedulable cell set. Furthermore, for the same cell, the presence / absence and / or value of min K0 / K2 can be configured separately / independently for existing single-cell DCI formats and multi-cell DCI formats.

[0212] Figure 14 This is a diagram illustrating signal transmission / reception between the network and the UE according to an embodiment of this disclosure.

[0213] Reference Figure 14 The UE can receive higher-layer signaling from the network at least once (A05). The higher-layer signaling may include at least one of the following: information for configuring multiple cells, BWP configuration information for each cell, BWP-specific parameter configuration information for each BWP, and configuration information for multi-cell scheduling. The configuration information for multi-cell scheduling may include a table (e.g., ...) associated with the row (entry) indicated by the DCI field of the DCI for multi-cell scheduling. Figure 13The configuration of (d) is as follows. In this case, each row can have multiple fields for multiple cells (e.g., multiple per-cell columns). The size of each of the multiple fields can be determined based on the maximum number of bits required in the BWP configured for each cell to indicate BWP-specific parameters. Among the multiple fields, the size of the first field for the first cell can be determined based on the maximum number of bits required in the BWP configured for the first cell to indicate BWP-specific parameters. Among the multiple fields, the size of the second field for the second cell can be determined based on the maximum number of bits required in the BWP configured for the second cell to indicate BWP-specific parameters. Based on the requirement of L bits in the first BWP for the first cell, M bits in the second BWP for the first cell, and N bits in the third BWP for the first cell to indicate BWP-specific parameters, the size of the first field for the first cell among the multiple fields can be determined as the maximum number of bits among L bits, M bits, and N bits.

[0214] The UE can receive DCI (A10) for multi-cell scheduling from the network. The DCI for multi-cell scheduling may include a BWP indication field and a BWP-specific parameter indication field. The BWP-specific parameter indication field may indicate one of the rows in a table, and the information of each field included in the indicated row can be interpreted based on the BWP indicated by the BWP indication field. Based on the requirement of Y bits to indicate the BWP-specific parameter of BWP#A indicated by the BWP indication information for the first cell among multiple cells, and based on the fact that the size of the first field for the first cell among multiple fields is determined to be X bits greater than Y bits, the BS can provide the first BWP-specific parameter of BWP#A for the first cell by selecting Y bits from the X bits of the first field. The Y bits selected from the X bits of the first field can be Y LSBs.

[0215] The DCI may include minimum scheduling offset indication information. Whether a minimum scheduling offset is configured or not, or the value of the minimum scheduling offset, may be the same for co-scheduled cells. The minimum scheduling offset may be min K0 or min K2, where min K0 may be related to the DCI and PDSCH offset, and min K2 may be related to the DCI and PUSCH offset. The value of the minimum scheduling offset may be for multi-cell scheduling, and the minimum scheduling offset value for multi-cell scheduling may be configured separately from the minimum scheduling offset value for single-cell scheduling (e.g., via higher-layer signaling).

[0216] DCI can schedule PDSCH or PUSCH on co-scheduled cells.

[0217] The UE can receive PDSCH or send PUSCH (A15) on a co-scheduled cell based on DCI.

[0218] Figure 15 The flow of a method executed by a UE according to an embodiment of the present disclosure is illustrated.

[0219] Reference Figure 15 The UE can receive configuration information (B05) for a table that is configured to have multiple fields for multiple cells in each row via higher-layer signaling.

[0220] The UE can receive DCI (B10) for multi-cell scheduling.

[0221] The UE can determine the BWP (B15) of the cell co-scheduled through DCI based on the BWP indication information of DCI.

[0222] The UE can obtain BWP-specific parameters (B20) for the BWP of a co-scheduled cell based on a determined BWP and a table. The BWP-specific parameters configured in multiple fields included in each row of the table can be interpreted based on the determined BWP. The size of each of the multiple fields can be determined by the BWP determination, which indicates the maximum number of bits required in the BWP configured for each cell to indicate the BWP-specific parameters.

[0223] Among the multiple fields, the size of the first field for the first cell can be determined by the BWP, which indicates the maximum number of bits required in the BWP configured for the first cell to specify the BWP parameters. Similarly, the size of the second field for the second cell can be determined by the BWP, which indicates the maximum number of bits required in the BWP configured for the second cell to specify the BWP parameters.

[0224] Based on the fact that the first BWP of the first cell requires L bits, the second BWP of the first cell requires M bits, and the third BWP of the first cell requires N bits to indicate specific parameters of the BWP, the size of the first field for the first cell among multiple fields can be determined as the maximum number of bits among L bits, M bits, and N bits.

[0225] Based on the requirement of Y bits to indicate the BWP-specific parameters of BWP#A determined by BWP indication information for the first cell among multiple cells, and based on the fact that the size of the first field for the first cell among multiple fields is determined to be X bits greater than Y bits, the UE can obtain the first BWP-specific parameters of BWP#A for the first cell by selecting Y bits from the X bits of the first field. The Y bits selected from the X bits of the first field can be Y LSBs.

[0226] DCI can include information used to indicate a row in a table.

[0227] DCI can schedule PDSCH or PUSCH on co-scheduled cells. DCI may include minimum scheduling offset indication information related to the minimum scheduling offset from DCI to PDSCH or PUSCH. The configuration of the minimum scheduling offset or its value may be the same for co-scheduled cells. The minimum scheduling offset can be min K0 or min K2, where min K0 may be related to the DCI-PDSCH offset, and min K2 may be related to the DCI-PUSCH offset. The minimum scheduling offset value may be for multi-cell scheduling, and the minimum scheduling offset value for multi-cell scheduling may be configured separately from the minimum scheduling offset value for single-cell scheduling.

[0228] Figure 16 The flow of a method performed by a BS according to an embodiment of the present disclosure is illustrated.

[0229] Reference Figure 16 The BS can send configuration information (C05) for a table configured so that each row has multiple fields for multiple cells via higher-layer signaling. The size of each of the multiple fields can be determined by the BWP indicating BWP-specific parameters based on the maximum number of bits required in the BWP configured for each cell. Among the multiple fields, the size of the first field for the first cell can be determined by the BWP indicating BWP-specific parameters based on the maximum number of bits required in the BWP configured for the first cell. Among the multiple fields, the size of the second field for the second cell can be determined by the BWP indicating BWP-specific parameters based on the maximum number of bits required in the BWP configured for the second cell. Given that the first BWP for the first cell requires L bits, the second BWP for the first cell requires M bits, and the third BWP for the first cell requires N bits to indicate BWP-specific parameters, the size of the first field for the first cell among the multiple fields can be determined as the maximum number of bits among L bits, M bits, and N bits.

[0230] The BS can determine the BWP (C10) of the cell to be co-scheduled by the DCI for multi-cell scheduling. The BS can indicate the BWP of the cell to be co-scheduled by the DCI based on the BWP indication information of the DCI.

[0231] The BS can send DCI (C15) for multi-cell scheduling.

[0232] BWP-specific parameters can be configured in multiple fields in each row of the table based on the indicated BWP interpretation.

[0233] Based on the requirement of Y bits to indicate the BWP-specific parameters of BWP#A for the first cell among multiple cells, as indicated by the BWP indication information, and based on the fact that the size of the first field for the first cell among multiple fields is determined to be X bits greater than Y bits, the BS can provide the first BWP-specific parameters of BWP#A for the first cell by selecting Y bits from the X bits of the first field. The Y bits selected from the X bits of the first field can be Y LSBs.

[0234] DCI can include information used to indicate a row in a table.

[0235] DCI can schedule PDSCH or PUSCH on co-scheduled cells. DCI may include minimum scheduling offset indication information related to the minimum scheduling offset from DCI to PDSCH or PUSCH. The configuration of the minimum scheduling offset or its value may be the same for co-scheduled cells. The minimum scheduling offset can be min K0 or min K2, where min K0 may be related to the DCI-PDSCH offset, and min K2 may be related to the DCI-PUSCH offset. The minimum scheduling offset value may be for multi-cell scheduling, and the minimum scheduling offset value for multi-cell scheduling may be configured separately from the minimum scheduling offset value for single-cell scheduling.

[0236] Figure 17 A communication system 1 applied to this disclosure is shown.

[0237] Reference Figure 17The communication system 1 applied to this disclosure includes wireless devices, base stations (BS), and networks. Herein, a wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G New RAT (NR) or Long Term Evolution (LTE)) and may be referred to as a communication / radio / 5G device. Wireless devices may include (but are not limited to) robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, Internet of Things (IoT) devices 100f, and artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Herein, vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and may take the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses) and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, the BS and network may be implemented as wireless devices, and a particular wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0238] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can perform direct communication with each other (e.g., sidelink communication) without going through the BS / network. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0239] Wireless communication / connections 150a, 150b, or 150c can be established between wireless devices 100a to 100f / BS 200 or between BS 200 and BS 200. In this document, wireless communication / connections can be established via 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)). Wireless devices and BS / wireless devices can transmit / receive radio signals to / from each other via wireless communication / connections 150a and 150b. For example, wireless communication / connections 150a and 150b can transmit / receive signals via various physical channels. For this purpose, at least a portion of the configuration information for configuring the process of transmitting / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes can be performed based on various proposals of this disclosure.

[0240] Figure 18 A wireless device applicable to this disclosure is shown.

[0241] Reference Figure 18 The first wireless device 100 and the second wireless device 200 can transmit radio signals via various RATs (e.g., LTE and NR). In this document, {first wireless device 100 and second wireless device 200} can correspond to... Figure 17 {Wireless Device 100x and BS 200} and / or {Wireless Device 100x and Wireless Device 100x}.

[0242] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and additionally include one or more transceivers 106 and / or one or more antennas 108. The processors 102 may control the memories 104 and / or the transceivers 106, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a radio signal including the first information / signal via the transceivers 106. The processor 102 may receive a radio signal including a second information / signal via the transceivers 106, and then store the information obtained by processing the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information relating to the operation of the processor 102. For example, the memory 104 may store software code including commands for performing some or all of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. In this document, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used interchangeably with radio frequency (RF) units. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0243] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and additionally include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or the transceivers 206, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processors 202 may process information in the memories 204 to generate a third information / signal, and then transmit a radio signal including the third information / signal via the transceivers 206. The processors 202 may receive a radio signal including a fourth information / signal via the transceivers 206, and then store the information obtained by processing the fourth information / signal in the memories 204. The memories 204 may be connected to the processors 202 and may store various information relating to the operation of the processors 202. For example, the memories 204 may store software code including commands for executing some or all of the processes controlled by the processors 202 or for executing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. In this document, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used interchangeably with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0244] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers may be implemented by (but are not limited to) one or more processors 102 and 202. For example, 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). One or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. 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, processes, proposals, methods, and / or operation flowcharts disclosed in this document, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) and acquire PDUs, SDUs, messages, control information, data, or information from one or more transceivers 106 and 206, according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document.

[0245] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. 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 one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document can be implemented using firmware or software in the form of code, commands, and / or command sets.

[0246] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories 104 and 204 may be configured with read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0247] One or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the methods and / or operation flowcharts of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 may perform controls to enable one or more transceivers 106 and 206 to transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may perform controls to enable one or more transceivers 106 and 206 to receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and 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, processes, proposals, methods, and / or operation flowcharts disclosed herein via one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals for processing by one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc., processed by one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0248] Figure 19 Another example of a wireless device applied to this disclosure is shown. The wireless device may vary depending on usage / service (see reference). Figure 17 It is realized in various forms.

[0249] Reference Figure 19 Wireless devices 100 and 200 can correspond to Figure 18The wireless devices 100 and 200 are configured with various elements, components, units / parts, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include... Figure 18 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, transceiver 114 may include Figure 18 The device comprises one or more transceivers 106 and 206 and / or one or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory unit 130, and add-on components 140, and controls the overall operation of the wireless device. For example, control unit 120 may control the electrical / mechanical operation of the wireless device based on programs / code / commands / information stored in memory unit 130. Control unit 120 may transmit information stored in memory unit 130 to an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store information received from an external source (e.g., other communication devices) via communication unit 110 in memory unit 130 via a wireless / wired interface.

[0250] The additional component 140 can be configured differently depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device can be configured according to (but is not limited to) a robot ( Figure 17 100a), vehicles ( Figure 17 100b-1 and 100b-2), XR device ( Figure 17 100c), handheld device ( Figure 17 100d), home appliances ( Figure 17 100e), IoT devices ( Figure 17 100f), digital broadcast user equipment, holographic devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environment devices, AI servers / devices ( Figure 17 400), BS ( Figure 17 This can be achieved through 200 network nodes, etc. Wireless devices can be used in mobile or fixed locations depending on the use case / service.

[0251] exist Figure 19In wireless devices 100 and 200, all elements, components, units / parts, and / or modules may be interconnected via wired interfaces, or at least a portion thereof may be wirelessly connected via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 may be wired connected, and control unit 120 and first cells (e.g., 130 and 140) may be wirelessly connected via communication unit 110. The various elements, components, units / parts, and / or modules within wireless devices 100 and 200 may also include one or more elements. For example, control unit 120 may be configured as a collection of one or more processors. As an example, control unit 120 may be configured as a collection of communication control processors, application processors, electronic control units (ECUs), graphics processing units, and memory control processors. As another example, memory unit 130 may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0252] Figure 20 The illustration shows a vehicle or autonomous vehicle applicable to this disclosure. The vehicle or autonomous vehicle may be a mobile robot, car, train, manned / unmanned aerial vehicle (AV), vessel, etc.

[0253] Reference Figure 20 The vehicle or autonomous vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as part of the communication unit 110. Blocks 110 / 130 / 140a to 140d respectively correspond to... Figure 19 Blocks 110 / 130 / 140.

[0254] Communication unit 110 can send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. Control unit 120 can perform various operations by controlling the components of the vehicle or autonomous vehicle 100. Control unit 120 may include an electronic control unit (ECU). Drive unit 140a enables the vehicle or autonomous vehicle 100 to move on a road. Drive unit 140a may include an engine, motor, powertrain, wheels, brakes, steering mechanism, etc. Power supply unit 140b can supply power to the vehicle or autonomous vehicle 100 and includes wired / wireless charging circuitry, battery, etc. Sensor unit 140c can acquire vehicle status, surrounding environment information, user information, etc. Sensor unit 140c may include inertial measurement unit (IMU) sensors, collision sensors, wheel sensors, speed sensors, slope sensors, weight sensors, heading sensors, position modules, vehicle forward / reverse sensors, battery sensors, fuel sensors, tire sensors, steering sensors, temperature sensors, depth sensors, ultrasonic sensors, lighting sensors, pedal position sensors, etc. Autonomous driving unit 140d can implement technologies for maintaining the vehicle within its lane, technologies for automatically adjusting speed (e.g., adaptive cruise control), technologies for autonomously driving along a determined path, and technologies for automatically setting a route if a destination is set, etc.

[0255] For example, communication unit 110 can receive map data, traffic information data, etc., from an external server. Autonomous driving unit 140d can generate an autonomous driving path and driving plan from the acquired data. Control unit 120 can control drive unit 140a, enabling the vehicle or autonomous vehicle 100 to move along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, communication unit 110 can periodically or non-periodically acquire recent traffic information data from an external server and acquire surrounding traffic information data from neighboring vehicles. During autonomous driving, sensor unit 140c can acquire vehicle status and / or surrounding environment information. Autonomous driving unit 140d can update the autonomous driving path and driving plan based on newly acquired data / information. Communication unit 110 can transmit information about vehicle location, autonomous driving path, and / or driving plan to an external server. The external server can predict traffic information data using AI technology, etc., based on information collected from the vehicle or autonomous vehicle, and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0256] The above embodiments correspond to combinations of the elements and features of this disclosure in a prescribed form. Unless explicitly stated otherwise, each element or feature may be considered optional. Each element or feature may be implemented without combination with other elements or features. Furthermore, embodiments of this disclosure can be implemented by partially combining elements and / or features together. The order of operations described for various embodiments of this disclosure may be modified. Some configurations or features of one embodiment may be included in another embodiment, or may replace corresponding configurations or features of another embodiment. Additionally, it will be readily understood that embodiments are configured by combining claims not expressly referenced in the appended claims, or may be included as new claims after filing the application.

[0257] Those skilled in the art will understand that this disclosure may be practiced in other specific forms besides those set forth herein without departing from the spirit and essential characteristics of this disclosure. Therefore, the above embodiments should be construed in all respects as illustrative rather than restrictive. The scope of this disclosure should be determined by the appended claims and their legal equivalents, and not by the foregoing description, and all changes falling within the meaning and scope of the appended claims are intended to be covered therewith.

[0258] Industrial applicability

[0259] This disclosure applies to UE, BS or other devices in wireless mobile communication systems.

Claims

1. A method performed by a user equipment (UE), the method comprising the following steps: Configuration information for a table is received via higher-layer signaling, the table being configured such that each row has multiple fields for multiple cells; Receive downlink control information (DCI) for multi-cell scheduling; as well as The BWP of the cell co-scheduled through the DCI is determined based on the Bandwidth Part (BWP) indication information of the DCI. The BWP-specific parameters, configured in the plurality of fields in each row of the table, are based on a determined BWP interpretation. Specifically, the size of each of the multiple fields is determined by the BWP that instructs specific parameters of the BWP based on the maximum number of bits required in the BWP configured for each cell.

2. The method according to claim 1, wherein, The first BWP, based on the maximum number of bits required in the BWP configured for the first cell, instructs the BWP specific parameters to determine the size of the first field among the plurality of fields for the first cell. Specifically, the second BWP, which instructs the BWP specific parameters based on the maximum number of bits required in the BWP configured for the second cell, determines the size of the second field among the plurality of fields for the second cell.

3. The method according to claim 1, wherein, Based on the fact that the first BWP of the first cell requires L bits, the second BWP of the first cell requires M bits, and the third BWP of the first cell requires N bits to indicate specific parameters of the BWP, the size of the first field for the first cell among the multiple fields is determined to be the maximum number of bits among the L bits, the M bits, and the N bits.

4. The method according to claim 1, wherein, Based on the requirement of Y bits to indicate the BWP-specific parameters of the first BWP determined based on the BWP indication information for the first cell among the plurality of cells, and based on the fact that the size of the first field for the first cell among the plurality of fields is determined to be X bits greater than the Y bits, the UE obtains the first BWP-specific parameters of the first BWP for the first cell by selecting the Y bits from the X bits of the first field.

5. The method according to claim 4, wherein, The Y bits selected from the X bits of the first field are the Y least significant bits (LSBs).

6. The method according to claim 1, wherein, The DCI includes information used to indicate a row in the table.

7. The method according to claim 1, in, The DCI schedules either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH) on the co-scheduled cell. The DCI includes minimum scheduling offset indication information related to the minimum scheduling offset from the DCI to the PDSCH or the PUSCH, and The configuration of the minimum scheduling offset or the value of the minimum scheduling offset are the same for the co-scheduled cells.

8. The method according to claim 7, wherein, The minimum scheduling offset is either min K0 or min K2. Among them, min K0 and DCI are related to the PDSCH offset, and Among them, min K2 and DCI are related to the PUSCH offset.

9. The method according to claim 7, wherein, The value of the minimum scheduling offset is for the multi-cell scheduling, and The minimum scheduling offset value for multi-cell scheduling is configured separately from the minimum scheduling offset value for single-cell scheduling.

10. A non-transitory computer-readable recording medium having instructions recorded thereon, the instructions causing the user equipment (UE) to perform the method according to claim 1 when executed by a processor of the user equipment (UE).

11. An apparatus comprising: The memory stores instructions; as well as A processor configured to perform operations by executing the instructions. The operations of the processor include: Configuration information for a table is received via higher-layer signaling, the table being configured such that each row has multiple fields for multiple cells; Receive downlink control information (DCI) for multi-cell scheduling; and The BWP of the cell co-scheduled through the DCI is determined based on the Bandwidth Part (BWP) indication information of the DCI. The BWP-specific parameters, configured in the plurality of fields in each row of the table, are based on a determined BWP interpretation. Specifically, the size of each of the multiple fields is determined by the BWP that instructs specific parameters of the BWP based on the maximum number of bits required in the BWP configured for each cell.

12. The apparatus of claim 11, further comprising a transceiver. in, The device is a user equipment (UE) for wireless communication.

13. The apparatus according to claim 11, wherein, The apparatus is a processing apparatus configured to control a user equipment (UE) used for wireless communication.

14. A method performed by a base station (BS), the method comprising the following steps: Configuration information for a table is sent via higher-layer signaling, the table being configured such that each row has multiple fields for multiple cells; as well as Send downlink control information (DCI) for multi-cell scheduling. Specifically, the Bandwidth Partial (BWP) indication information based on the DCI indicates the BWP of the cell co-scheduled through the DCI. The BWP interpretation based on the instruction is included in the BWP-specific parameters configured in the plurality of fields in each row of the table, and Specifically, the size of each of the multiple fields is determined by the BWP that instructs specific parameters of the BWP based on the maximum number of bits required in the BWP configured for each cell.

15. A base station (BS), the BS comprising: The memory stores instructions; as well as A processor configured to perform operations by executing the instructions. The operations of the processor include: Configuration information for a table is sent via higher-layer signaling, the table being configured such that each row has multiple fields for multiple cells; and Send downlink control information (DCI) for multi-cell scheduling. Specifically, the Bandwidth Partial (BWP) indication information based on the DCI indicates the BWP of the cell co-scheduled through the DCI. The BWP interpretation based on the instruction is included in the BWP-specific parameters configured in the plurality of fields in each row of the table, and Specifically, the size of each of the multiple fields is determined by the BWP that instructs specific parameters of the BWP based on the maximum number of bits required in the BWP configured for each cell.

Images