RU2764029C1 - Method for transmitting and receiving downlink data transmission channel and equipment for this - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: invention relates to wireless communication; it can be used to transmit and receive a downlink data transmission channel. In a method for receiving a downlink signal, user equipment (UE) receives, in the first bandwidth part (hereinafter – BWP) of downlink (hereinafter – DL), downlink control information (hereinafter – DCI) containing BWP switching information, which indicates the switching of the active DL BWP from the first DL BWP to the second DL BWP, and transport block (hereinafter – TB) information, which is associated with TB for a physical downlink shared channel (hereinafter – PDSCH). A transmission configuration indicator (TCI) is determined for a set of control resources (base set) in the second DL BWP, based on the fact that DCI received in the first DL BWP indicates the switching of the active DL BWP.

EFFECT: increase in the accuracy and efficiency of evaluating PDSCH on the second BWP of DL.

20 cl, 5 tbl, 22 dwg

Description

The field of technology to which the invention belongs

[1] The present invention relates to a method for transmitting and receiving a downlink data channel and equipment for doing so. More specifically, to a method and equipment for interpreting information included in a DCI (downlink control information) for transmitting and receiving a PDSCH when a DCI (downlink control information) received in an old BWP (bandwidth portion) schedules a PDSCH ( physical downlink shared channel) received in the new BWP.

State of the art

[2] As more and more communication devices require more data traffic along with current trends, the next generation fifth generation (5G) system should provide improved wireless broadband compared to the legacy LTE system. In the next generation 5G system, communication scenarios are divided into advanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), mass machine communication (mMTC), etc.

[3] In this document, eMBB is a next generation mobile communication scenario characterized by high spectral efficiency, high user data rate and high peak data rate, URLLC is a future generation mobile communication scenario characterized by ultra high reliability, ultra low delay and ultra-high availability (e.g. between a vehicle and everything (V2X), emergency services and remote control), and mMTC is a future generation mobile communication scenario characterized by low cost, low energy, short packets and mass traffic to connect (for example, Internet of Things (IoT) standard), according to current trends, a next-generation 5G system is required, which is an improvement of the wireless broadband system from LTE. In such a next-generation 5G system called NewRAT, communication scenarios are divided into advanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), mass machine communication (mMTC), etc.

The essence of the invention

Technical task

[4] An object of the present invention is to provide a method for transmitting and receiving a downlink data channel and equipment for doing so.

[5] Those skilled in the art should appreciate that the objectives that may be achieved by the present disclosure are not limited to those specifically described above, and the above and other objectives that the present disclosure may achieve should be more clearly be understood from the following detailed description.

Technical solution

[6] One general aspect of the present invention includes a method for receiving a physical downlink shared channel (PDSCH) by a user equipment (UE) in a wireless communication system, the method including: receiving, in a first part of the bandwidth (BWP) , downlink control information (DCI) that includes first information that indicates active BWP switching from the first BWP to the second BWP, and second information related to scheduling at least one transport block (TB) for the PDSCH. The method also includes receiving, in the second BWP, a PDSCH based on the first information and the second information, based on the number of TBs in the first TB group that can be scheduled through the second information being equal to one, and based on the number of TBs in the second TB group, which can be scheduled for a second BWP equal to two: from the second information associated with the scheduling of at least one TB, the information associated with the second TB from the second group of TBs is deactivated. Other embodiments of this aspect may include appropriate computer systems, hardware, and computer programs stored on one or more computer storage devices configured to perform the steps of the methods.

[7] Implementations may include one or more of the following features. A method in which the second information associated with scheduling at least one TB includes: a set of bits associated with a modulation and coding scheme (MCS), a new data indicator (NDI), and a spare version (RV). A method in which the information associated with the second TB is padded with zeros. The way in which the information associated with the second TB is ignored. A method in which the transmission configuration information (TCI) for the second BWP is identical to the TCI information associated with the DCI. A method in which the TCI information associated with the DCI includes: TCI information for a control resource set (base set) that is associated with the DCI. Implementations of the described technologies may include hardware, a method, or a process, or computer software on a machine-accessible medium.

[8] Another general aspect includes equipment configured to receive a physical downlink shared channel (PDSCH) in a wireless communication system, the equipment including: at least one processor; and at least one memory device operatively coupled to at least one processor and storing instructions that, when executed by at least one processor, perform operations including: receiving, in the first portion of the strip bandwidth (BWP), downlink control information (DCI), which includes first information that indicates the switching of the active BWP from the first BWP to the second BWP, and second information related to the scheduling of at least one transport block (TB ) for PDSCH. The operations also include receiving, in the second BWP, a PDSCH based on the first information and the second information, based on the number of TBs in the first TB group that can be scheduled through the second information equal to one, and based on the number of TBs in the second TB group, which can be scheduled for a second BWP equal to two: from the second information associated with the scheduling of at least one TB, the information associated with the second TB from the second group of TBs is deactivated. Other embodiments of this aspect may include appropriate computer systems, hardware, and computer programs stored on one or more computer storage devices configured to perform the steps of the methods.

[9] Implementations may include one or more of the following features. Equipment in which the second information associated with scheduling at least one TB includes: a set of bits associated with a modulation and coding scheme (MCS), a new data indicator (NDI) and a redundant version (RV). Equipment in which the information associated with the second TB is padded with zeros. Equipment where the information associated with the second TB is ignored. An equipment in which the transmission configuration information (TCI) for the second BWP is identical to the TCI information associated with the DCI. The equipment in which the TCI information associated with the DCI includes: TCI information for a control resource set (basic set) that is associated with the DCI. The implementation of the described technologies may include hardware, a method, or a process, or computer software on a machine-accessible medium.

[10] Another general aspect includes a user equipment (UE) configured to receive a physical downlink shared channel (PDSCH) in a wireless communication system, the UE including: a transceiver. The subscriber device also includes at least one processor; and at least one memory device operatively coupled to at least one processor and storing instructions that, when executed by at least one processor, perform operations including: receiving, in the first portion of the strip bandwidth (BWP), downlink control information (DCI) that includes (i) first information that indicates active BWP switching from the first BWP to the second BWP, and (ii) second scheduling related information of at least , one transport block (TB) for PDSCH. The operations also include receiving, in the second BWP, a PDSCH based on the first information and the second information, based on the number of TBs in the first TB group that can be scheduled through the second information equal to one, and based on the number of TBs in the second TB group, which can be scheduled for a second BWP equal to two: from the second information associated with the scheduling of at least one TB, the information associated with the second TB from the second group of TBs is deactivated. Other embodiments of this aspect may include appropriate computer systems, hardware, and computer programs stored on one or more computer storage devices configured to perform the steps of the methods.

[11] Another general aspect includes a method for transmitting a physical downlink shared channel (PDSCH) in a wireless communication system, the method including: transmitting, in a first part of the bandwidth (BWP), downlink control information (DCI) ) that includes first information that indicates the switch of the active BWP from the first BWP to the second BWP, and second information related to scheduling at least one transport block (TB) for the PDSCH. The method also includes transmitting, in the second BWP, a PDSCH based on the first information and the second information, based on the number of TBs in the first TB group that can be scheduled through the second information being equal to one, and based on the number of TBs in the second TB group, which can be scheduled for a second BWP equal to two: from the second information associated with the scheduling of at least one TB, the information associated with the second TB from the second group of TBs is deactivated. Other embodiments of this aspect may include appropriate computer systems, hardware, and computer programs stored on one or more computer storage devices configured to perform the steps of the methods.

[12] Another general aspect includes a base station (BS) configured to transmit a physical downlink shared channel (PDSCH) in a wireless communication system, the BS including: a transceiver. The base station also includes at least one processor; and at least one memory device operatively coupled to at least one processor and storing instructions that, when executed by at least one processor, perform operations including: transmitting, in the first part of the strip bandwidth (BWP), downlink control information (DCI), which includes first information that indicates the switching of the active BWP from the first BWP to the second BWP, and second information related to the scheduling of at least one transport block (TB ) for PDSCH. The operations also include transmitting, in the second BWP, the PDSCH based on the first information and the second information, based on the number of TBs in the first TB group that can be scheduled through the second information being one, and based on the number of TBs in the second TB group, which can be scheduled for a second BWP equal to two: from the second information associated with the scheduling of at least one TB, the information associated with the second TB from the second group of TBs is deactivated. Other embodiments of this aspect may include appropriate computer systems, hardware, and computer programs stored on one or more computer storage devices configured to perform the steps of the methods.

[13] All or part of the features described in this application may be implemented as a computer program product that includes instructions that are stored on one or more non-volatile computer-readable storage media and that are executed on one or more processing devices. All or part of the features described in this application may be implemented as equipment, method or electronic system, which may include one or more processing devices and a memory device to store executable instructions in order to implement the established functions.

Benefits of the Invention

[14] According to the present invention, it is possible to stably transmit and receive a downlink data channel without ambiguity even when the old BWP (parts of the bandwidth) configuration and the new BWP configuration are different.

[15] Persons skilled in the art should appreciate that the benefits that may be achieved with the present disclosure are not limited to those specifically described above, and other advantages of the present disclosure should be more clearly understood from the following detailed description, considered in conjunction with the accompanying drawings.

Brief description of the drawings

[16] FIG. 1 is a diagram showing an example of the structure of a control plane and a user plane of a wireless interface protocol between a terminal and an E-UTRAN based on the 3GPP radio access network standard;

[17] FIG. 2 is a diagram showing an example of a physical channel used in a 3GPP system and a general signaling method using it;

[18] FIG. 3-5 are diagrams showing examples of radio frame and slot structures used in a wireless communication system;

[19] FIG. 6 is a diagram showing an example of a hybrid beamforming structure from the point of view of a transceiver unit (TXRU) and a physical antenna;

[20] FIG. 7 is a diagram showing an example of a beam sweep operation for a synchronization signal and system information in a downlink transmission process;

[21] FIG. 8 is a diagram showing an example of a cell of a system supporting a new radio standard (NR) access technology;

[22] FIG. 9 is a diagram showing an example of HARQ-ACK timing in an NR system;

[23] FIG. 10-11 are diagrams showing examples of HARQ-ACK transmission in code block group (CBG) units in an NR system;

[24] FIG. 12-14 are diagrams showing examples of HARQ-ACK transmission in carrier aggregation (CA);

[25] FIG. 15-17 are diagrams showing examples of terminal, BS, and network operations for transmitting and receiving HARQ-ACK according to implementations of the present disclosure;

[26] FIG. 18 is a diagram showing an example in which the DCI schedules the PDSCH according to implementations of the present disclosure;

[27] FIG. 19-21 are diagrams showing examples of terminal, base station, and network operations for transmitting and receiving PDSCH according to implementations of the present disclosure; and

[28] FIG. 22 is a block diagram illustrating an example of the components of a wireless device according to implementations of the present disclosure.

Optimal Mode for Carrying Out the Invention

[29] Hereinafter, the structure, operation and other features of the present invention should be easily understood through the implementations of the present invention described with reference to the accompanying drawings. The implementations described below are examples where the technical features of the present invention are applied to a 3GPP system.

[30] Although the present disclosure describes an implementation of the present invention using an LTE system, an LTE-A system, and an NR system, implementations of the present invention may be applied to any suitable communication system that is compliant with the above standards.

[31] In addition, although the present invention uses specific terminology such as remote radio head (RRH), eNB, transmission point (TP), receiving point (RP), relay, etc., implementations of the present invention can be applied to more general systems that use similar features.

[32] 3GPP-based communication standards typically include downlink physical channels corresponding to resource elements carrying information originating from the upper layer, as well as downlink physical signals used by the physical layer, but corresponding to resource elements not carrying information initiated from the top level.

[33] For example, physical downlink channels may include a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), a physical multicast channel (PMCH), a physical control channel format indicator channel, a physical downlink control channel communication links (PDCCH); and a hybrid ARQ indicator physical channel (PHICH).

[34] The downlink physical signals may include a reference signal and a synchronization signal. Reference signal (RS), also referred to as "pilot signal", means a signal of a specific and predefined waveform that is known to gNBs and UEs. Examples of the downlink reference signals include, for example, a cell-specific RS, a UE-specific RS (UE-RS), a positioning RS (PRS), and a channel state information RS (CSI-RS).

[35] For uplink communication, 3GPP-based communication standards typically include uplink physical channels corresponding to resource elements carrying information originating from the upper layer, as well as uplink physical signals corresponding to resource elements used through the physical layer, but not carrying information initiated from the upper layer.

[36] For example, the physical uplink channels include a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), a physical random access channel (PRACH), a demodulation reference signal (DMRS) for an uplink control/data signal; and a sounding reference signal (SRS) used to measure the uplink channel.

[37] In the present disclosure, a physical downlink control channel (PDCCH), a physical control channel format indicator channel (PCFICH), a hybrid automatic repeat request indicator physical channel (PHICH), and a physical downlink shared channel (PDSCH) ), Physical Uplink Control Channel (PUCCH), Physical Uplink Control Channel (PUSCH), Physical Uplink Control Channel (PUSCH), and Physical Uplink Control Channel (PUSCH) (Uplink Shared Channel)/ PRACH (Physical Random Access Channel) means a set of time-frequency resources or a set of resource elements that carry downlink control information (DCI), control channel format indicator (CFI), downlink acknowledge/deny (DL ACK/ NACK) and DL data.

[38] Hereinafter, the expression that the user equipment (UE) transmits PUCCH/PUSCH/PRACH is used in the same sense as "transmit uplink control information/uplink data/random access signal on PUSCH/PUCCH/ PRACH, respectively". In addition, the expression that a g-node B (gNB) transmits PDCCH/PCFICH/PHICH/PDSCH is used in the same sense as "transmit downlink data/control information on PDCCH/PCFICH/PHICH/PDSCH", respectively. In the description below, the OFDM symbol/subcarrier/RE allocated with CRS/DMRS/CSI-RS/SRS/UE-RS is referred to as CRS/DMRS/CSI-RS/SRS/UE-RS symbol/carrier/subcarrier/ RE. For example, an OFDM symbol for which a tracking RS is allocated or configured is referred to as a "TRS symbol", a subcarrier for which a TRS is allocated or configured is referred to as a "TRS subcarrier", and an RE for which a TRS is allocated or configured is referred to as as "TRS RE". In addition, a subframe configured for TRS transmission is referred to as a "TRS subframe". The subframe in which the broadcast signal is transmitted is referred to as the "broadcast subframe" or "PBCH subframe", and the subframe in which the synchronization signal (eg, PSS and/or SSS) is transmitted is referred to as the "sync signal subframe" or "PSS/SSS -subframe". The OFDM symbols/subcarriers/REs for which a PSS/SSS is configured or specified are referred to as "PSS/SSS symbol/subcarrier/RE", respectively.

[39] In the present disclosure, a CRS port, a UE-RS port, a CSI-RS port, and a TRS port, respectively, are configured as an antenna port configured to transmit CRS, an antenna port configured to transmit UE -RS, an antenna port configured to transmit CSI-RS, and an antenna port configured to transmit TRS. Antenna ports configured to transmit CRS may differ from each other by location of REs occupied by CRS according to CRS ports, antenna ports configured to transmit UE-RS may differ from each other by location of REs occupied by UE- The RS according to the UE-RS ports and the antenna ports configured to transmit the CSI-RS may differ from each other by the RE positions occupied by the CSI-RS according to the CSI-RS ports. Therefore, the term "CRS/UE-RS/CSI-RS/TRS-port" is also used as a term for the pattern of REs occupied by CRS/UE-RS/CSI-RS/TRS in a specific resource area.

[40] FIG. 1 is a diagram illustrating an example of the structure of a control plane and a user plane of an air interface protocol between a UE and an E-UTRAN based on the 3GPP radio access network standard. The control plane means a path through which control messages used by the UE and the network are transmitted. The user plane means a path through which data generated in the application layer, such as voice data or Internet packet data, is transmitted.

[41] The physical (PHY) layer, which is the first layer, provides an upper layer information transfer service using a physical channel. The physical layer is connected to an upper medium access control (MAC) layer via a transmission channel (transport channel). Data moves between the MAC layer and the PHY layer over a transmission channel. Data is transferred between a transmitting side (eg, a transmitter) and a receiving side (eg, a receiving device) in a physical layer via a physical channel. The physical channel uses time and frequency as radio resources. For example, a physical channel may be modulated according to orthogonal frequency division multiple access (OFDMA) in the downlink and may be modulated according to single carrier frequency division multiple access (SC-FDMA) in the uplink.

[42] The medium access control (MAC) layer of the second layer provides a service to the radio link control (RLC) layer, which is the upper layer, via a logical channel. The RLC layer of the second layer supports reliable data transmission. In some implementations, the RLC layer function may be implemented as a functional block in the MAC. The Packet Data Convergence Protocol (PDCP) layer of the second layer performs a header compression function to reduce the amount of control information and efficiently transmit IP packets such as IPv4 and IPv6 packets on a low bandwidth wireless interface.

[43] The Radio Resource Control (RRC) layer, located at the bottom of the third layer, is defined in some implementations only in the control plane. The RRC layer is responsible for managing logical channels, transmission channels, and physical channels in connection with configuring, reconfiguring, and releasing radio bearers. The term "radio bearer" means services provided by the second layer for data transmission between the UE and the network. To this end, the terminal and the RRC layer of the network may exchange RRC messages with each other. If an RRC connection occurs between the UE and the RRC network layer, then the UE is in "RRC connected mode" and otherwise, the UE is in "RRC idle mode". The Non-Access Layer (NAS) at the top of the RRC layer performs functions such as session management and mobility management.

[44] A downlink transmission channel for transmitting data from a network to a terminal (eg, UE) includes, for example, BCH (Broadcast Channel) for transmitting system information, PCH (Paging Channel) for transmitting a paging message, SCH (shared channel) downlink to carry user traffic and control messages. In the case of traffic or a control message of a downlink multicast or broadcast service, these messages may be transmitted over the downlink SCH or may be transmitted over a separate downlink multicast channel (MCH). In some implementations, the uplink transmission channel for transmitting data from the UE to the network includes, for example, a RACH (random access channel) for transmitting an initial control message and an uplink SCH (shared channel) for transmitting user traffic or control messages. The logical channel mapped to a transmission channel includes, for example, a Broadcast Control Channel (BCCH), a Paging Control Channel (PCCH), a Common Control Channel (CCCH), a Multicast Control Channel (MCCH), and a Multicast Traffic Channel (MTCH).

[45] FIG. 2 is a diagram showing an example of a physical channel used in a 3GPP system and a general signaling method using it.

[46] When the UE turns on or re-enters a cell, the UE performs an initial cell search operation such as base station (BS) synchronization (S201). To this end, the UE receives a Primary Synchronization Channel (P-SCH) and a Secondary Synchronization Channel (S-SCH) from the BS, synchronizes with the BS, and acquires information such as a cell ID. The UE may then receive the physical broadcast channel from the BS and obtain the intra-cell broadcast information. In some implementations, the UE may receive a downlink reference signal (DL-RS) during the initial cell search step to check the status of the downlink channels.

[47] Upon completion of the initial cell search, the UE receives more detailed system information by receiving a Physical Downlink Control Channel (PDCCH) as well as a Physical Downlink Control Channel (PDSCH) according to the PDCCH information (S202).

[48] In some implementations, if the US connects to a base station (BS) as an initial connection, or if there is no signaling radio resource, then the UE may perform a random access (RACH) procedure for the BS (steps S203 to S206). To this end, the UE transmits a specific sequence via a Physical Random Access Channel (PRACH) as a preamble (S203 and S205) and receives a response message to this preamble on the PDCCH and the corresponding PDSCH (S204 and S206). In concurrent RACH scenarios, a collision resolution procedure may additionally be performed.

[49] The UE having performed the above procedure may then perform PDCCH/PDSCH reception (S207) and transmission of a Physical Uplink Shared Channel (PUSCH)/Physical Uplink Control Channel (PUCCH) (S208). For example, the UE may receive downlink control information (DCI) via the PDCCH. In such scenarios, the DCI may include control information such as resource allocation information for the UE, and the DCI formats may differ according to the purpose of use.

[50] In some implementations, the control information transmitted by the UE to the Node B via the uplink or received from the Node B by the UE includes, for example, a downlink/uplink ACK/NACK signal, a channel quality indicator (CQI ), a precoding matrix index (PMI), a rank indicator (RI), and the like. In some systems, such as systems compliant with the 3GPP LTE standard, the UE may transmit control information such as CQI/PMI/RI as described above via PUSCH and/or PUCCH.

[51] FIG. 3 illustrates an example of a radio frame structure used in NR.

[52] In NR, uplink and downlink transmission consists of frames. The radio frame may be 10 ms long and may be defined as two half-frames (HF) of 5 ms. Each half-frame may be defined as five sub-frames (SF) in 1 ms. A subframe may be divided into one or more slots, and the number of slots in a subframe may depend on the SCS (Subcarrier Spacing). Each slot may include 12 or 14 OFDM(A) symbols according to the cyclic prefix (CP). In some implementations, if CP is used, then each time slice contains 14 symbols. If extended CP is used, then each timeslice contains 12 symbols. The symbol may include, for example, an OFDM symbol (or CP-OFDM symbol) and an SC-FDMA symbol (or DFT-s-OFDM symbol).

[53] Table 1 illustrates an example of a normal CP in which the number of symbols per slot, the number of slots per frame, and the number of slots per subframe are different according to the SCS.

[54] Tab. one

SCS (15*2^u) N ^slot _symbol N ^{frame, u} _slot N ^{subframe, u} _slot 15 kHz (u=0) 14 10 One 30 kHz (u=1) 14 twenty 2 60 kHz (u=2) 14 40 4 120 kHz (u=3) 14 80 eight 240 kHz (u=4) 14 160 sixteen

[55] where N ^slot _symb is the number of symbols per time slice,

[56] N ^{frame, u} _slot is the number of slots per frame, and

[57] N ^{subframe, u} _slot is the number of slots per subframe.

[58] Table 2 illustrates an extended CP example in which the number of symbols per slot, the number of slots per frame, and the number of slots per subframe are different according to the SCS.

[59] Tab. 2

SCS (15*2^u) N ^slot _symbol N ^{frame, u} _slot N ^{subframe, u} _slot 60 kHz (u=2) 12 40 4

[60] In an NR system, OFDM(A) numerology (eg, SCS, CP length, etc.) may be set differently between multiple cells for one UE. Accordingly, the (absolute time) interval of a time resource (eg, SF, timeslot, or TTI) (for convenience, TU (time unit)) consisting of the same number of symbols may be defined differently between merged cells.

[61] FIG. 4 illustrates an example of an NR frame slot structure. The time slice includes a plurality of symbols in the time domain. For example, in the case of a normal CP, one slot includes seven symbols, while in the case of extended CP, one slot includes six symbols.

[62] The carrier includes a plurality of subcarriers in the frequency domain. An RB (resource block) is defined as a plurality (eg, 12) of consecutive subcarriers in the frequency domain. The BWP (part of the bandwidth) is defined as a set of consecutive RBs (or physical RBs) in the frequency domain, and may correspond to one numerology (eg, one SCS, one CP length, etc.). Each carrier may include up to N (eg, 5) BWPs.

[63] In some implementations, communication is performed via an activated BWP, and only one BWP can be activated per UE. In the resource grid form representation, each resource grid element is referred to as a resource element (RE) into which one complex symbol can be mapped.

[64] FIG. 5 illustrates an example of an autonomous time slice structure. In an NR system, a frame is characterized by an autonomous structure in which a DL control channel, DL or UL data, UL control channel, etc. can be contained in one time slice. For example, the first N symbols in the time slot may be used to transmit a DL control channel (hereinafter, the DL control region), and the last M symbols in the time slot may be used to transmit UL control channels (hereinafter, the UL-control region). management). N and M can be an integer of 0 or greater.

[65] The resource area (hereinafter referred to as the data area) between the DL control area and the UL control area can be used for DL data transmission or UL data transmission. For example, the following configuration may be implemented. Each section is listed in chronological order.

[66] 1. Configuration with DL only

[67] 2. Configuration with UL only

[68] 3. Mixed UL-DL Configuration

[69] - DL region + guard period (GP) + UL control region

[70] - DL control area + GP + UL area

[71] * DL area: (i) DL data area, (ii) DL control area + DL data area

[72] * UL area: (i) UL data area, (ii) UL data area + UL control area

[73] The PDCCH may be transmitted in the DL control region and the PDSCH may be transmitted in the DL data region. Similarly, in the UL control domain, PUCCH may be transmitted, and in the UL data domain, PUSCH may be transmitted. The PDCCH may carry downlink control information (DCI) such as, for example, DL data scheduling information, UL data scheduling information, and the like. The PUCCH may carry uplink control information (UCI) such as, for example, ACK/NACK information, DL CSI information and a scheduling request (SR), and the like.

[74] The GP provides a time gap in the process of switching from transmit mode to receive mode or switch from receive mode to transmit mode. A part of the symbols in the subframe may be set as GP for switching from DL to UL.

[75] In some implementations, an NR system may use a high frequency band, such as a millimeter frequency band of 6 GHz or more, to transmit data while maintaining a high data rate for a large number of users over a wide frequency band. However, in such scenarios, the millimeter band may have a frequency response in which signal attenuation due to distance is very sharp due to the high frequency nature of the band. Therefore, in order to compensate for such sudden fading characteristics, an NR system that uses at least a 6 GHz bandwidth can transmit a signal beam in a specific direction rather than in all directions so as to transmit a narrow beam. In such scenarios in which a service is performed using narrow beams, since the range of one base station may narrow, the base station can collect a plurality of narrow beams and provide services over a wide band that spans a plurality of narrow beams.

[76] In the millimeter frequency band, i.e. in the millimeter wave (mmW) band, the wavelengths typically shorten and this allows multiple antenna elements to be installed in the same area. For example, in a 30 GHz band with a wavelength of approximately 1 cm, a total of 100 antenna elements can be installed in a 5 by 5 cm panel in a two-dimensional array at 0.5 lambda (wavelength) intervals. Therefore, in mmW, coverage or throughput can be increased by increasing beamforming gain across multiple antenna elements.

[77] In some implementations, as a technique for millimeter-band narrow beamforming, beamforming may be implemented in which energy is increased only in a particular direction by transmitting an identical signal using an appropriate phase difference to a large number of antennas in a base station, or U.E. Such beamforming schemes include (i) digital beamforming that creates a phase difference in the baseband digital signal, (ii) analog beamforming that creates a phase difference using time delay (i.e., cyclic shift) for the modulated analog signal, and (iii) hybrid beamforming using both digital beamforming and analog beamforming.

[78] In scenarios where a transceiver unit (TXRU) is provided to provide transmit power and phase control for each antenna element, then independent beamforming for each frequency resource can be realized. However, problems may arise in that a TXRU may not be cost effective in terms of setting a plurality of antenna elements to 100 or more. For example, the mmWave band may require a large number of antennas to compensate for sudden attenuation characteristics. In such scenarios, digital beamforming may require a number of RF components (eg, digital-to-analogue converter (DAC)), mixers, power amplifiers, line amplifiers, etc., at least as many as the number of antennas. In this regard, digital beamforming in the millimeter band may encounter such problems that the price of communication devices may increase.

[79] Therefore, when a large number of antennas are required, such as in the millimeter band, implementations may use analog beamforming or hybrid beamforming. In the analog beamforming scheme, a plurality of antenna elements are converted into one TXRU, and the beam direction is controlled by an analog phase shifter. In some scenarios, such an analog beamforming scheme may have the disadvantage that it may only form one beam direction in the entire frequency band and may not be able to perform frequency selective beamforming (BF). A hybrid BF is an intermediate form of a digital BF and an analog BF and has a certain number (eg, B) of TXRUs that is less than the number (eg, Q) of antenna elements. In the case of a hybrid BF, the number of beams that can be transmitted simultaneously may be limited to B or less, although the scenarios may vary depending on how the B TXRU and Q antenna elements are connected.

[80] As mentioned above, since digital beamforming performs signal processing for a digital baseband signal to be transmitted or received, it is possible to transmit or receive signals in different directions simultaneously using multiple beams. In contrast, since analog beamforming performs beamforming in the modulated state of an analog signal to be transmitted or received, it cannot simultaneously transmit or receive signals in multiple directions outside of the range covered by a single beam.

[81] In general, a base station communicates with multiple users (UEs) simultaneously using a wideband transmission or a multi-antenna characteristic. When a base station uses analog beamforming or hybrid beamforming and forms an analog beam in one beam direction, the base station may only be able to communicate with users included in the same analog beam direction due to analog beamforming characteristics.

[82] The implementations disclosed herein provide RACH resource allocation and resource utilization for a base station that allows, in some scenarios, to mitigate such constraint mismatches caused by hybrid beamforming or analog beamforming characteristics.

[83] FIG. 6 illustrates an example of a hybrid beamforming structure from the perspective of a transmit/receive unit (TXRU) and a physical antenna.

[84] In scenarios that use multiple antennas, a hybrid beamforming technique that combines digital beamforming and analog beamforming can be implemented. In analog beamforming (or RF beamforming), the transceiver (or RF module) performs precoding (or combining). In hybrid beamforming, the baseband unit and the transceiver (or RF unit) perform precoding (or combining), respectively. This may have the advantage of achieving performance that is close to digital beamforming while reducing the number of RF chains and the number of digital-to-analog (or analog-to-digital) converters.

[85] For convenience, the hybrid beamforming pattern may be represented by N TXRUs and M physical antennas. The digital beamforming for the L data layers to be transmitted at the transmitting end may be represented by an NxL matrix. The N converted digital signals can then be converted to analog signals via the TXRU, and after that analog beamforming represented by the MxN matrix is applied.

[86] In the example of FIG. 6, the number of digital beams is L, and the number of analog beams is N. Further, in the NR system, the base station can be configured to change the analog beamforming in units of symbols, and thus can provide more efficient beamforming for the UE. located in a specific area. Further, when N TXRUs and M RF antennas are defined as one antenna panel, a plurality of antenna panels to which independent NR hybrid beamforming is applicable can be realized. When a base station uses a plurality of analog beams, the analog beam that is advantageous for receiving signals may be different for each UE. Therefore, in some scenarios, for example, for synchronous signal, system information, paging, etc., a beam sweep operation may be implemented in which the base station changes several analog beams on a symbol-by-symbol basis for a particular time slice or subframe to provide reception capabilities for multiple UEs.

[87] FIG. 7 is a diagram illustrating an example of a beam sweep operation for a synchronization signal and system information in a downlink transmission process.

[88] In the example of FIG. 7, the physical resource or physical channel through which system information of the new RAT system is broadcast is referred to as xPBCH (Physical Broadcast Channel). In some implementations, analog beams belonging to different antenna panels may be simultaneously transmitted in the same symbol. To measure the channel for each analog beam as shown in FIG. 7, implementations may use a beam reference signal (BRS), which is the reference signal that is transmitted for the corresponding single analog beam. In some scenarios, the BRS may be defined for multiple antenna ports and each BRS antenna port may correspond to one analog beam. In some implementations, unlike BRS, the synchronization signal or xPBCH can be transmitted for all analog beams included in the analog beam group so that any UE can receive it well.

[89] FIG. 8 illustrates an example cell of a system supporting a new radio standard (NR) access technology.

[90] Referring to the example of FIG. 8, in some scenarios, the NR system may implement multiple TRPs that constitute one cell, unlike the scenario in which one base station forms one cell in the wireless communication system. In scenarios where a plurality of TRPs constitute one cell, even if the TRP for serving the UE is changed, it can be advantageous that transparent communication can be provided and UE mobility management is simplified.

[91] In some systems, for example, in systems that are compatible with LTE/LTE-A, PSS/SSS can be transmitted in all directions. In some implementations, a gNB using mmWave beamforms a signal such as PSS/SSS/PBCH by rotating the beam direction in an omnidirectional fashion. Transmitting/receiving signals while rotating the beam direction is referred to as "beam sweep" or "beam scan". In the present disclosure, beam sweep means the behavior on the transmitter side, and beam scanning means the behavior on the receiver side.

[92] For example, given that the gNB can have a maximum of N beam directions, the gNB can transmit signals (eg, PSS/SSS/PBCH) in N beam directions, respectively. In other words, the gNB can send synchronization signals (eg, PSS/SSS/PBCH) for each direction while sweeping the directions that the gNB can implement or support. Alternatively, if the gNB can generate N beams, then multiple beams can be bursted into one beam group, and the PSS/SSS/PBCH can be transmitted and/or received for each beam group. Each beam group may include one or more beams.

[93] A signal (eg, PSS/SSS/PBCH) that is transmitted in the same direction may be defined as one SS block, and multiple SS blocks may be implemented in one cell. In scenarios where multiple SS boxes are provided, the SS box index can be used to distinguish each SS box. For example, when the PSS/SSS/PBCH is transmitted in 10 beam directions in one system, then the PSS/SSS/PBCH in the same direction may constitute one SS block. In this system, 10 SS blocks can be understood as realizable. In the present disclosure, a beam index may be interpreted as an SS block index.

[94] Partial Bandwidth (BWP)

[95] In some implementations, an NR system may support a bandwidth per carrier up to 400 MHz per carrier. If a UE operating on such a broadband carrier always operates with the RF module enabled for the entire carrier, then the battery power consumption of the UE may increase. In addition, different usage scenarios (eg, eMBB, URLLC, mMTC, V2X, etc.) operating within the same wideband carrier, different amplitudes (eg, subcarrier spacing) can be supported for each frequency band within the respective carrier. In addition, the characteristics of the maximum bandwidth for each UE may be different.

[96] In view of these factors, the base station may instruct the UE to operate only in part of the bandwidth, and not in the entire bandwidth of the broadband carrier. The corresponding bandwidth in which the UE is instructed to operate is referred to as "part of the bandwidth" (BWP). In the frequency domain, the BWP is a subset of contiguous common resource blocks specified for numerology i in the bandwidth portion i of the carrier, and one numerology (eg, subcarrier spacing, CP length, slot/minislot length) may be specified.

[97] In some implementations, the base station may configure one or more BWPs in one carrier configured for the UE. Alternatively, some UEs may move to another BWP for load balancing when multiple UEs overload a particular BWP. Alternatively, suppression of inter-cell interference in the frequency domain between neighboring cells may be considered, and BWPs on both sides of the cell may be configured in the same time slot by eliminating some spectrums of the entire bandwidth.

[98] For example, a base station may configure at least one DL/UL BWP in a UE associated with a broadband carrier and activate at least one DL/UL BWP of the DL/UL BWPs specified at a particular time. . The base station may instruct to switch to the BWP or configure the value of the timer such that the UE switches to the designated DL/UL BWP when the timer expires. As an example, the base station may transmit at least one DL/UL BWP from multiple DL/UL BWPs (eg, by transmitting L1 signaling, MAC CE, or transmitting RRC signaling) or by switching to another configured DL /UL BWP (eg, by transmitting L1 signaling, a MAC Control Element (CE) as a MAC layer control signal, or transmitting RRC signaling) to allow the UE to switch to a predetermined DL/UL BWP when the timer expires.

[99] In some implementations, DCI format 1_1 or DCI format 0_1 may be used by the base station to instruct the UE to switch to another configured DL/UL BWP. An activated DL/UL BWP may be specifically referred to as an "active DL/UL BWP". If the UE is performing the initial access procedure, or if the UE has not yet established an RRC connection, then the UE may not accept the job for the DL/UL BWP. In such situations, the DL/UL BWP assumed by the UE is referred to as the "initial active DL/UL BWP".

[100] As used herein, the term "DL BWP" means a BWP for transmitting/receiving a downlink signal (eg, PDCCH and/or PDSCH), and the term "UL BWP" means a BWP for transmitting/receiving an uplink signal (eg PUCCH and/or PUSCH).

[101] Hybrid Automatic Repeat Request (HARQ)

[102] The following describes the operation in the HARQ-ACK mode with respect to the operation of the UE to generate messages with control information. The HARQ-ACK is information indicating whether or not the UE successfully receives the downlink physical channel. If the UE successfully receives the downlink physical channel, then the UE sends an acknowledgment (ACK) feedback to the base station. If the UE does not successfully receive the downlink physical channel, then the UE sends a denial of reception (NACK) feedback to the base station. HARQ in NR supports one HARQ-ACK feedback bit per transport block.

[103] FIG. 9 is a diagram showing an example of HARQ-ACK timing.

[104] In the example of FIG. 9, K0 denotes the number of slots from a slot having a PDCCH carrying a DL resource allocation (ie, a DL transmission grant) to a slot having a corresponding PDSCH transmission. K1 denotes the number of slots from the PDSCH slot to the slot of the corresponding HARQ-ACK transmission. K2 denotes the number of slots from a slot having a PDCCH (carrying a grant to a UL transmission) to a slot having a corresponding PUSCH transmission. Thus, K0, K1 and K2 can be summarized as shown in Table 3 below.

[105] Tab. 3

A B K0 DCI DL scheduling Corresponding DL data transmission K1 Receiving DL data Corresponding HARQ-ACK K2 DCI UL scheduling Corresponding transmission of UL data

[106] [107] The base station may provide the UE with HARQ-ACK feedback time synchronization dynamically in DCI or semi-statically through RRC signaling.

[108] In some implementations, such as systems that are NR compliant, different minimum HARQ processing times may be supported between UEs. The HARQ processing time includes a delay between the DL data reception timing and the corresponding HARQ-ACK transmission timing, and a delay between the UL grant reception timing and the corresponding UL data transmission timing. The UE transmits, to the base station, information regarding characteristics of its minimum HARQ processing time. From the UE's point of view, the HARQ ACK/NACK feedback for multiple DL transmissions in the time domain may be transmitted in the UL data/control domain. The timing between the reception of DL data and the corresponding ACK is indicated by DCI.

[109] Unlike some systems (eg, some systems that are LTE compliant) in which the HARQ process is performed for each transport block or codeword, the implementations disclosed herein (which may be NR compliant) support transmission based on code block groups with one/multi-bit feedback on HARQ-ACK. The transport block may be mapped to one or more CBs depending on the size of the TB. For example, in the channel coding process, a CRC code is appended to TB. If the CRC TB does not exceed a predetermined size, the CRC TB corresponds to one code block. If the TB with CRC exceeds the predetermined size, the TB is segmented into multiple CBs. In the NR system, the UE may be configured to receive transmissions based on the CBG, and retransmission may be scheduled to carry a subset of all TB CBs.

[110] Code Block Group (CBG) HARQ Process

[111] In some systems, such as LTE-compatible systems, a transport block (TB) based HARQ process is supported. In systems that are NR compliant, the CBG based HARQ process is supported with the TB based HARQ process.

[112] FIG. 10 illustrates an example of processing and structure of a TB. The example of FIG. 10 may be applied to DL-SCH (Shared Channel), PCH (Paging Channel), and MCH (Multicast Channel) data. In addition, UL TB (or UL transport channel data) can be handled similarly.

[113] Referring to the example of FIG. 10, the transmitting device performs a CRC (eg, 24-bit) (CRC TB) for error checking for TB. The transmitter may then divide the TB+CRC into a plurality of code blocks based on the size of the channel encoder. In one example, the maximum code block size in LTE is 6144 bits. Therefore, if the TB-size is equal to or less than 6144 bits, no code block is generated. If the TB-size exceeds 6144 bits, the TB is divided into 6144-bit units to constitute a plurality of code blocks. In each code block, a CRC (eg 24-bit) (CB CRC) is added separately for error checking. Each code block is channel-encoded and rate-matched, and then combined to form a codeword. In the TB-based HARQ process, data scheduling and the HARQ process are performed based on the TB, and CB CRC is used to determine early termination of TB decoding.

[114] FIG. 11 illustrates an example of a CBG based HARQ process. In a CBG-based HARQ process, data scheduling and the HARQ process may be performed in units of TB.

[115] Referring to the example of FIG. 11, the UE may receive, from a base station (eg, Node B), information regarding the number M of code block groups per transport block, and this information may be received via an upper layer signal (eg, an RRC signal) (S1102). Thereafter, the UE may receive an initial data transmission (via PDSCH) from the Node B (S1104). The data may include a transmission block (TB), and a TB may include a plurality of code blocks (CB), and the plurality of CBs may be grouped into one or more code block groups (CBG) in a TB. Here, some CBGs may include rounding up the number (K/M) of CBs, and the remaining CBs may include rounding down the number (in K/M) of CBs. The K parameter represents the number of CBs in the data.

[116] Based on whether or not the UE correctly receives the data, the UE may provide, as feedback, CBG-based ACK/NACK information regarding the data to the base station (S1106), and the base station may perform data retransmission for the data in CBG units (S1108). A/N information may be transmitted via PUCCH or PUSCH. In some implementations, the A/N information includes a plurality of A/N bits for data, with each A/N bit representing each A/N response that is generated for each CBG. In some scenarios, the A/N information payload data size may be kept identical based on M, regardless of the number of CBGs constituting the data.

[117] Scheme based on dynamic/semi-static HARQ-ACK codebooks

[118] NR supports a scheme based on dynamic HARQ-ACK codebooks and a scheme based on semi-static HARQ-ACK codebooks. The HARQ-ACK (or A/N) codebook may be replaced with working HARQ-ACK data.

[119] When a scheme based on dynamic HARQ-ACK codebooks is set, the size of the working A/N data varies depending on the number of actually scheduled DL data. To this end, the PDCCH associated with DL scheduling includes a counted DAI (downlink destination index) and a complete DAI. The calculated DAI indicates a scheduling sequence value {CC, slot} calculated as "CC (component carrier) (or cell) first", and is used to indicate the position of the A/N bit in the A/N codebook. The full DAI indicates the cumulative scheduling value on a per-slot basis up to the current slot and is used to determine the size of the A/N codebook.

[120] When a scheme based on semi-static A/N codebooks is set, the size of the A/N codebook is fixed (at the maximum value) regardless of the actual number of scheduled DL data. In particular, the (maximum) (size) of the A/N payload transmitted over one PUCCH in one slot is used for all CCs defined in the UE and all DL scheduling slots for which A/ time synchronization can be indicated. N-transmissions, or a combination of a PDSCH transmission slot or a PDCCH monitoring slot (hereinafter, bundling windows). For example, the DCI (PDCCH) for transmitting DL grants includes PDSCH-A/N timing information, and the PDSCH-A/N timing timing information may be one of a plurality of values (eg, k). For example, if the PDSCH is received in time slot #m, and the PDSCH-A/N timing information on the DCI (PDCCH) for granting a DL transmission scheduling the PDSCH indicates k, then the A/N information for the PDSCH may be transmitted in the time quantum #(m+k). For example, k may be provided, which is an element in the set {1, 2, 3, 4, 5, 6, 7, 8}. On the other hand, when the A/N information is transmitted in time slot #n, then the A/N information may include the maximum possible A/N based on the packetization window. Thus, the A/N information of slot #n may include an A/N corresponding to slot #(n-k). For example, in the case of k being an element of the set {1, 2, 3, 4, 5, 6, 7, 8}, the A/N information of the time slot #n corresponds to the A/N information from the time slot #(n- 8) up to time slice #(n-1) (i.e. the maximum A/N number). Here, the A/N information may be replaced by an A/N codebook and A/N work data. In addition, the time slice can be understood/replaced as a possible period for receiving DL data. As illustrated, the packetization window is determined based on the PDSCH-A/N timing with respect to the A/N timing, and the set for the PDSCH-A/N timing has a predetermined value (e.g., {1, 2, 3, 4 , 5, 6, 7, 8} and transmission of overhead (RRC-) signals.

[121] Later in this document, a method for transmitting/receiving a HARQ-ACK according to an implementation of the present disclosure is described in detail.

[122] In the fifth generation NR system, the bandwidth portion (BWP) changes dynamically and can achieve power saving and/or load balancing through RF switching/baseband switching.

[123] In addition, configuration based on HARQ-ACK codebooks, generation of CSI messages, and the like. may change based on BWP change. In particular, when carrier aggregation (CA) is applied, BWP is independent. It is necessary to set the configuration based on the HARQ-ACK codebooks and the CSI configuration method according to the change.

[124] In the present disclosure, for example, when different BWPs use a semi-static HARQ-ACK codebook and a dynamic HARQ-ACK codebook, use TB-based HARQ-ACK and CBG-based HARQ-ACK, the following describes the HARQ method -ACK transmissions in case the HARQ-ACK transmission methods are different for each BWP. In addition, the following describes the method of HARQ-ACK transmission in the process of changing the BWP through BWP switching. Implementations of the present disclosure are not limited to HARQ-ACK transmission and may extend to other UCI transmissions such as CSI.

[125] As such, a method for transmitting feedback on a HARQ-ACK in an NR system includes a scheme based on semi-static HARQ-ACK codebooks and a scheme based on dynamic HARQ-ACK codebooks.

[126] In the case of a scheme based on semi-static HARQ-ACK codebooks, considering all PDCCH monitoring periods associated with a particular PUCCH transmission time, considering the set of PDSCH-HARQ-ACK feedback timings given to the UE , HARQ, The UE may process NACK for a PDSCH (Physical Downlink Shared Channel) that is not scheduled during PDCCH monitoring periods.

[127] Of the PDSCH receive periods that can expect to receive the PDSCH in multiple slots based on the PDSCH-HARQ-ACK closed-loop timing associated with a particular PUCCH transmission time (i.e., the HARQ-ACK time -transmission), PDSCH receive periods other than the PDSCH receive periods that cannot be scheduled by the PDCCH of the PDSCH receive periods, i. e. PDSCH reception opportunities other than a PDSCH reception opportunity that cannot be scheduled by the PDCCH are referred to as "PDSCH reception opportunities".

[128] Of the PDSCH receive period candidates, the PDSCH receive period candidates that are not scheduled by the actual PDCCH monitoring periods and do not receive the PDSCH may be processed as a NACK.

[129] In some implementations, in the case of a scheme based on dynamic HARQ-ACK codebooks, the full DAI field and/or the counted DAI field are set in the DCI and generate/transmit HARQ-ACK bits for the PDSCH that is actually scheduled by the PDCCH capabilities. -monitoring based on the corresponding DAI value.

[130] In some implementations, when carrier aggregation is applied, the HARQ-ACK transmission for multiple cells may be multiplexed onto one PUCCH and transmitted.

[131] In this case, when a semi-static HARQ-ACK codebook is used, the order of the HARQ-ACK bits is the order of the PDCCH monitoring opportunities from the earliest in time, based on the combination of the PDCCH monitoring capabilities of each cell. When a dynamic HARQ-ACK codebook is used, as shown in FIG. 13, when a DCI that schedules a PDSCH in a corresponding cell actually exists, a HARQ-HARQ-ACK may be generated based on it.

[132] In some implementations, such as NR-compliant implementations, CBG-based retransmission and/or HARQ-ACK feedback may be defined per serving cell, and the number of CBG-based HARQ-ACK bits and/or maximum the number of HARQ-ACK bits based on the CBG may be set for each serving cell. If a semi-static HARQ-ACK codebook is used, it is necessary to generate a TB-based HARQ-ACK for each PDCCH monitoring period according to whether a CBG-based HARQ-ACK is specified for each cell, or the number of CBGs and/or the maximum number of CBGs based on the HARQ- ACK bit based on CBG. In some implementations, a TB-based HARQ-ACK may be generated with 1 bit or 2 bits according to the maximum number of TBs.

[133] In the case of using a dynamic HARQ-ACK codebook as shown in FIG. 14, HARQ-ACK bits are generated based on TB-based HARQ-ACK for all serving cells, in addition to serving cells for which CBG transmission is set, the number of CBGs to be scheduled for each serving cell is generated based on the maximum value the number of CBGs given in each serving cell. In some implementations, the maximum value of the number of CBGs may be twice the maximum specified number of TBs. On the other hand, in some systems (eg, systems that are NR compliant), downlink and uplink signals (eg, subcarrier spacing) may differ. Therefore, when determining the timing between the PDSCH and the HARQ-ACK feedback, the difference in signaling for the HARQ-ACK transmission and the feedback for the PDSCH must be taken into account. As such, K1 representing the offset value between the PDSCH and the PUCCH on which the HARQ-ACK is transmitted is expressed based on the PUCCH numerology. Therefore, if the slot in which the last PDSCH symbol overlaps is n, the PUCCH is transmitted in a slot corresponding to n+K1. However, if the PDSCH subcarrier interval is smaller than the PUCCH subcarrier interval, the time slice based on the PUCCH subcarrier interval may differ according to time domain resource allocation (time domain RA) for the time domain.

[134] In this case, a time domain RA table row set for a PDSCH-HARQ closed-loop time synchronization set in which the last PDSCH symbol in each PUCCH slot overlaps can be defined. More specifically, the last PDSCH symbol may be extracted from the SLIV of the time domain RA field. In this case, the last PDSCH symbol may be set such that it is limited to the last slot of the aggregated slots in consideration of slot aggregation. Alternatively, a maximum value of the number of PDSCH- (non-overlapping PDSCH-) combinations that do not overlap between PDSCHs can be set.

[135] On the other hand, if the PDSCH subcarrier interval exceeds the PUCCH subcarrier interval, the plurality of slots for the PDSCH may overlap with one slot based on the PUCCH subcarrier interval. In this case, the HARQ-ACK codebook may be calculated based on the maximum number of PDSCHs (non-overlapping PDSCHs) that do not overlap each slot. Specifically, a set for all PDSCH slots overlapping a particular PUCCH slot is set, a maximum value of the number of PDSCH- (non-overlapping PDSCH-) patterns that do not overlap for each PDSCH slot is set and added, and other timing with PDSCH-HARQ feedback can be reused. In this case, considering the aggregation of timeslices, the implementation may only apply to the last timeslice of the aggregated timeslice.

[136] By integrating the above methods, the following implementations can be extracted. For example, if the PUCCH is transmitted in PUCCH slot n, it may constitute a set of combinations of SLIV and PDSCH slots for the entire PDSCH in which the last symbol overlaps PUCCH slot n-k (where k is all values included in K1). In some implementations, if slot aggregation is specified, the last symbol may be the last symbol corresponding to the last slot of the aggregated slots. The SLIV and PDSCH slot combination including the uplink symbols in the set for the SLIV and/or PDSCH slot combination for all PDSCHs in which the last symbol overlaps may be omitted from the corresponding set. If the PDCCH monitoring period corresponding to the combination of SLIV and PDSCH slots is not set, the corresponding combination of SLIV and PDSCH slots may be excluded from the corresponding set. The maximum number of non-overlapping PDSCH combinations can be extracted by applying an algorithm to find non-overlapping PDSCHs in a certain set by performing the above procedure. At this time, the maximum number of combinations can be extracted for each PDSCH slot, and if slot aggregation is used, the extraction method can be modified.

[137] On the other hand, the PDCCH monitoring period may be different for each DCI format. For example, a DCI 1_0 PDCCH monitoring period may be composed of a subset of DCI 1_1 PDCCH monitoring periods. In this case, the time domain resource allocation set may differ according to the DCI format.

[138] Therefore, the configuration scheme based on the HARQ-ACK codebooks may be set to be different according to the DCI format. For example, if only the DCI format 1_1 is taken into account by the PDCCH monitoring period, then the HARQ-ACK codebook may be configured based on the rows of the time domain table RA, which may be indicated in the DCI format 1_1. On the other hand, when the DCI format 1_1 and the DCI format 1_0 can be monitored by the PDCCH monitoring period, the rows of the time domain table RA, which can be indicated in the DCI format 1_1, and the time lines, the HARQ-ACK codebook can be constructed on based on joining time domain RA tables.

[139] For example, a set of rows of a time domain PDSCH table RA and a DCI format pair (format pair) may be defined. For example, when PDCCH availability is determined for each row, the monitoring period of the PDCCH monitoring of the DCI format paired with the corresponding row may be checked to determine the corresponding set. That is, the DCI format PDCCH monitoring periods are confirmed based on the inter-slot offset value K0 for receiving the PDSCH from the slot in which the DCI is received by checking each row of the time domain RA table. If there is a PDCCH monitoring period at this point in time, it may be taken into account when constructing the HARQ-ACK codebook and otherwise omitted from the configuration based on the HARQ-ACK codebooks.

[140] On the other hand, the UE may only perform PDCCH monitoring in the current active DL BWP. In some implementations, the base set and/or search space may be independently specified for each BWP. The search space may include monitoring periods on the time axis for the PDCCH.

[141] However, if the PDCCH monitoring periods differ according to the BWP, the configuration based on the HARQ-ACK codebooks is likely to change dynamically as well. In addition, the range of PDSCH-HARQ-ACK closed-loop timing values can be set independently for each BWP, and the configuration based on the HARQ-ACK codebooks can be changed even in this case.

[142] When the BWP changes, an interval may occur in which the configuration based on the HARQ-ACK codebooks is ambiguous. For example, when the set of PDCCH monitoring opportunities associated with the BWP HARQ feedback time point before the change and the set of PDCCH monitoring opportunities associated with the BWP HARQ feedback time point after the change overlap, an ambiguity may occur in the HARQ based configuration. -ACK codebooks in overlapping PDCCH monitoring capabilities.

[143] In some implementations, the bits configuring the size of the HARQ-ACK codebook or the HARQ-ACK codebook may be changed in various ways according to circumstances. For example, the set for PDSCH-HARQ-ACK timing is specified in {4, 5, 6, 7} slots, in BWP # (set for time synchronization) is specified in {4, 6} slots.

[144] For example, when transmitting feedback on a HARQ-ACK in time slot n, it is assumed to operate in BWP # 1 up to time slot n-4 and to operate as BWP # 2 in time slot n-4. In this case, the UE may be ambiguous as to whether to send a 4-bit HARQ-ACK for slots n-7, n-6, n-5, and n-4 and/or a 2-bit HARQ-ACK for slots n-6 and n-4 in time slice n. In particular, considering the CA situation, the overall configuration based on the HARQ-ACK codebooks may need to change as the size of the HARQ-ACK changes. However, the aggregation relationship for the PDSCH-HARQ-ACK timing according to the above assumption can be extended by combining according to the PDCCH-PDSCH timing.

[145] More specific implementations of the method for constructing HARQ-ACK codebooks according to BWP switching are described below.

[146] First, the operation procedure of the UE, BS, and network according to the implementation of the present disclosure is described with reference to FIG. 15-17.

[147] FIG. 15 is a flowchart illustrating an example of operation of a UE according to an implementation of the present disclosure. Referring to FIG. 15, the UE may receive a plurality of BWPs to receive a downlink signal from a base station (S1501). In some implementations, the BWP set may be defined via upper layer signaling. Then, the UE receives, from the base station, DCI and/or upper layer signaling to activate the first BWP of the plurality of BWPs (S1503), and receives the first PDSCH via the activated first BWP (S1505). Thereafter, the UE receives, from the base station, a DCI to change the active BWP from the first BWP to the second BWP (S1507), and receives the second PDSCH via the second active BWP (S1509).

[148] The UE then transmits a HARQ-ACK for at least one of (i) the first PDSCH received via the BWP before the change, or (ii) the second PDSCH received via the changed BWP (S1511). In some implementations, the HARQ-ACK configuration method and transmission method may be implemented according to implementations 1-4, detailed below.

[149] Referring to FIG. 16, the following describes an example of operation of a base station according to an implementation of the present disclosure. In step S1601, the base station may configure a plurality of BWPs for downlink signaling to the UE. In some implementations, a plurality of BWPs may be configured via upper layer signaling. The base station transmits, to the UE, DCI and/or upper layer signaling to activate the first BWP of the plurality of BWPs (S1603), and transmits the first PDSCH via the activated first BWP (S1605). Thereafter, the base station transmits, to the UE, a DCI to change the active BWP from the first BWP to the second BWP (S1607) and transmits the second PDSCH via the second active BWP (S1609).

[150] The base station receives from the UE a HARQ-ACK for at least one of (i) the first PDSCH transmitted via the BWP before the change, or (ii) the second PDSCH transmitted via the modified BWP (S1611). In some implementations, the HARQ-ACK and the reception method are configured according to the first to fourth implementations, which are described in detail below.

[151] Considering the operations of FIG. 15 and 16 from the network point of view in FIG. 17, the base station configures a plurality of BWPs for downlink signaling to a UE via upper layer signaling (S1701), transmits a BWP from the plurality of BWPs, and transmits a DCI and/or upper layer signaling to activate the first BWP in the UE (S1703 ). Then, the base station transmits the first PDSCH through the activated first BWP (S1705). Next, the base station transmits a DCI to change the active BWP from the first BWP to the second BWP at the UE (S1707), and transmits the second PDSCH via the second active BWP (S1709).

[152] The UE transmits, to the base station, a HARQ-ACK for at least one of (i) the first PDSCH that is transmitted via the BWP before the BWP change, or (ii) the second PDSCH that is transmitted via the BWP after the BWP- changes (S1711). In some implementations, the UE configures the HARQ-ACK and the reception method according to the first to fourth implementations, which are described in detail below.

[153] Implementation 1

[154] When using a semi-static HARQ-ACK codebook, the UE does not expect the BWP to change. Alternatively, the UE may expect that the PDCCH monitoring period set or the DL association set associated with the HARQ-ACK feedback does not change even if the BWP changes.

[155] In some scenarios, in the case of the first implementation, one can exclude or expect not to change the configuration based on the HARQ-ACK codebooks even if the BWP changes.

[156] Implementation 2

[157] When a plurality of BWPs are set, the UE determines whether or not HARQ-ACK bits are generated based on the combination of downlink association sets or PDCCH monitoring periods for all given BWPs for each cell. In particular, when a semi-static HARQ-ACK codebook is used, HARQ-ACK bits may be generated for each PDCCH monitoring period for all given BWPs or for each PDCCH monitoring period in a downlink association set pooling. In this case, the number of HARQ-ACK bits may be one bit or two bits, depending on the number of TBs.

[158] On the other hand, when a dynamic HARQ-ACK codebook is used, HARQ-ACK bits may be generated according to PDSCH scheduling based on a combination of PDCCH monitoring periods or downlink association set for all given BWPs.

[159] In the second implementation, the number of HARQ-ACK bits may increase. In particular, in a semi-static HARQ-ACK codebook, the number of HARQ-ACK bits may be excessively large. However, even when the BWP changes dynamically and the PDCCH monitoring period, the PDCCH-PDSCH timing and/or the PDSCH-HARQ-ACK closed-loop timing set change dynamically, the HARQ-ACK configuration does not change.

[160] Implementation 3

[161] The UE may generate HARQ-ACK bits based on the active BWP, ie. active BWP (downlink) at the appropriate time of the feedback transmission on the HARQ-ACK. Alternatively, the HARQ-ACK bits may be generated based on the BWP (downlink) corresponding to the PDSCH closest to the viewpoint from the PDSCHs associated with the HARQ-ACK feedback.

[162] In particular, in the case of single cell basing, the HARQ-ACK for the PDSCH that is scheduled in the previous BWP may be discarded without transmission. In other words, when the UE configures the HARQ-ACK after the BWP is changed, the HARQ-ACK bit for the PDCSH scheduled in the BWP after the change is included in the HARQ-ACK configuration, and the HARQ-ACK for the PDSCH scheduled in the previous BWP- ACK bits may be sent without being included in the HARQ-ACK configuration.

[163] On the other hand, in a CA situation, the order between HARQ-ACK bits for a plurality of serving cells may be re-arranged such that coding for HARQ-ACK feedback may need to be performed again.

[164] However, such a problem can be avoided by setting the interval in which the BWP changes large enough and not performing new scheduling (on the downlink) within the interval. Alternatively, the HARQ-ACK feedback for scheduling (on the downlink) occurring in the inter-BWP handoff interval, i. e. in a BWP switch, is dispatched with the ability to match the BWP before the change or match the BWP after the change.

[165] In the case of the third implementation, the HARQ-ACK feedback detection performance can be improved by generating as many HARQ-ACK bits as required. In particular, in the case of a semi-static HARQ-ACK codebook, as many HARQ-ACK bits as required can be generated.

[166] In particular, in the case of a semi-static HARQ-ACK codebook, when generating the number of HARQ-ACK bits, the HARQ-ACK bit associated with the PDCCH monitoring periods for the BWP before the change is not generated, only the HARQ-ACK- bits associated with PDCCH monitoring periods may be generated. Thus, the number of HARQ-ACK bits is the number of PDSCH opportunities that can expect to receive the PDSCH in multiple slots according to the PDSCH-HARQ feedback timing associated with the HARQ-ACK feedback, and generate a HARQ- ACK bits as many times as the number of PDSCH opportunities associated with the changed BWP.

[167] In other words, the number of HARQ-ACK bits after the BWP switch is performed may be less than the number of HARQ-ACK bits when the BWP switch is not performed. However, after a certain period of time from when the BWP switch is performed, all possible PDSCH opportunities associated with the HARQ-ACK feedback may be present in slots after the BWP change. As time passes after the BWP change, the number of ACK bits may gradually increase. In other words, the bits for the PDSCH capabilities associated with the BWP before the change that are discarded on the HARQ-ACK bits are not included.

[168] Implementation 4

[169] When the UE determines that all the downlink BWPs indicated by the PDCCH scheduling PDSCH in the downlink association set corresponding to the HARQ-ACK feedback are identical, either when the PDCCH monitoring period set or feedback on the HARQ-ACK, the UE determines that the set of associations in the downlink is identical.

[170] For example, a set of downlink associations for HARQ-ACK feedback may only correspond to one particular BWP for each cell at a time. Different HARQ-ACK feedback may be performed in different orthogonal coverage code (OCC) and frequency/symbol domains when the HARQ-ACK feedback is split into an ACK/NACK resource indicator (ARI). For each different HARQ-ACK feedback, the BWPs associated with the downlink association set may be separately defined.

[171] In this case, the failover operation may be implemented during the BWP switching period. For example, in some implementations (for example, in an NR system), the UE receives only one DCI for failover, such as DCI format 1_0, and when the DAI value of the received DCI for failover is 1, it can only transmit HARQ -ACK bits for the corresponding DCI.

[172] In some implementations, the DCI for failover may be transmitted in a shared search space. In addition, when the UE detects the PDCCH and/or PDSCH in the first slot or first PDCCH monitoring periods in the downlink association set associated with the HARQ-ACK in the NR system, the UE may only transmit HARQ-ACK bits for corresponding PDSCH.

[173] Alternatively, the BWP switch may be directed to a non-failover DCI such that if the UE detects only one DCI with DAI=1, then regardless of the DCI format, it may send HARQ-ACK bits just for that. PDSCH. In this case, the DCI with DAI=1 may be the DCI scheduling the corresponding PDSCH. In particular, even if only one DCI with DAI=1 is transmitted in a SCell, i. e. DCI with DAI=1 is not transmitted in the other cell, HARQ-ACK bits for the corresponding PDSCH may be transmitted.

[174] However, in the case of using a semi-static HARQ-ACK codebook, there may be no DAI field for a non-failover DCI, and therefore the PDSCH is scheduled in the first PDCCH monitoring period corresponding to the downlink association set for HARQ. Only when a PDCCH is detected, a HARQ-ACK bit for the PDSCH may be transmitted. Thus, even if a semi-static HARQ-ACK codebook is specified, HARQ-ACK bits for all PDCCH monitoring periods associated with HARQ-ACK feedback are not generated, but HARQ-ACK bits associated with the operation may be generated. DCI-based failover with DAI=. At this time, during the BWP switchover period, the UE may use a DCI-based failover operation with DAI=1.

[175] In some implementations, the method of generating the HARQ-ACK codebooks according to the BWP change may differ depending on whether the HARQ-ACK codebook defined in the above implementation is a semi-static HARQ-ACK codebook or dynamic HARQ. -ACK encoding table. In addition, implementations of the present disclosure need not necessarily be performed separately, but may be performed in a combination of implementations. Thus, many of the methods included in the above implementations may be used in combination. For example, in an implementation of the present disclosure, a failover operation may always be supported.

[176] In addition, the set of associations in the downlink for the HARQ-ACK may differ according to the BWP index and/or ARI pattern indicated by the DCI. For example, if some of the various BWP peer PDCCH monitoring capabilities overlap, then based on the BWP index and/or ARI value in the DCI transmitted in the overlapping region, the UE may determine which BWP to which based on the set of downlink associations. links should be addressed when generating the HARQ-ACK codebook. Thus, if some PDCCH monitoring capabilities between different BWPs overlap, then the PDCCHs corresponding to the PDSCHs in the downlink association set of a particular BWP criterion may have the same BWP index and/or ARI. In particular, the ARI value may be classified according to whether or not the value of the ARI field is identical.

[177] In addition, when the set of PUCCH resources to be indicated by the ARI is different for each BWP, the operation of generating and transmitting HARQ-ACK codebooks can be performed based on whether or not the final selected PUCCH resource is identical.

[178] If the BWP indices are different and the ARIs are identical, the HARQ-ACKs for the PDSCH corresponding to different BWPs can be considered to be transmitted on the same channel. In particular, HARQ-ACKs for PDSCHs corresponding to different BWPs may be simultaneously transmitted after HARQ-ACKs are generated for each BWP and transmitted in parallel. In order to more efficiently reduce payload size, the HARQ-ACK may be generated by concatenation with respect to a set of associations in the downlink for BWP.

[179] In some implementations of the present disclosure, a semi-static HARQ-ACK codebook or a dynamic HARQ-ACK codebook may be specific to a UE regardless of the BWP, and when a codebook type is specified for each BWP, all of them may have the same exercise.

[180] In some implementations (eg, NR compliant systems), the way of configuring based on HARQ-ACK codebooks may be changed via upper layer signaling. In such scenarios, there may be a need to operate without ambiguity between the UE and the gNB during the RRC reset period. In this case, the potential ambiguity between the gNB and the UE can be reduced by operating in the failover operational mode described in the above implementations for a period.

[181] In the HARQ-ACK codebook type, whether or not a semi-static HARQ-ACK codebook or a dynamic HARQ-ACK codebook is configured may change according to the downlink BWP and/or the uplink BWP. For example, a semi-static HARQ-ACK codebook may be useful when the downlink association set size for HARQ-ACK feedback differs according to the downlink BWP, otherwise a dynamic HARQ-ACK codebook may be useful. .

[182] For example, if the DL association set is large, the size of the HARQ-ACK codebook may be large so that it can be configured as a dynamic HARQ-ACK codebook.

[183] On the other hand, when ambiguity may occur if a DAI-based dynamic HARQ-ACK codebook is used due to a change in channel quality or interference environment according to the downlink BWP, then a semi-static HARQ-ACK codebook may be used. In this case, since the BWP UE changes dynamically, the HARQ-ACK codebook type may also change dynamically.

[184] Since the PUCCH is to be transmitted in a PCcell (including the PSCell or PUCCH SCell), the type of the HARQ-ACK codebook may be determined according to the BWP (downlink) of the PCell. For example, the presence of a DAI field in a DCI in a SCell may be determined based on whether the codebook configured in the BWP PCell is a HARQ-ACK codebook or not a dynamic HARQ-ACK codebook. However, even in this case, the failover DCI may still have a calculated DAI field.

[185] On the other hand, the DAI field may be created or excluded based on the point in time at which the BWP actually changes. The UE assumes that the downlink BWP indicated by the PDCCH in the DL association set corresponding to the corresponding HARQ-ACK feedback is identical during the HARQ-ACK feedback. For example, all DCIs associated with HARQ-ACK feedback may be considered assuming a semi-static HARQ-ACK codebook or a dynamic HARQ-ACK codebook. In particular, the HARQ-ACK feedback may be divided into a BWP index and/or ARI value in the associated DCI, and DCIs corresponding to the same HARQ-ACK feedback channel or the same HARQ-ACK feedback channel group may have BWP index and/or ARI value with identical value.

[186] On the other hand, when the interval or BWP changes, for example, when the search space configuration changes, a failover operation may be performed. Here, the failover operation means a DCI-based operation having DAI=1 or a DCI discovery operation only in the first downlink association set PDCCH monitoring period of the configured cell.

[187] On the other hand, due to DCI-based BWP switching, there may be a discrepancy between the required DCI field size and the actual transmitted DCI field size in the changed BWP.

[188] For example, as can be seen in the example of FIG. 18, the DCI is received at the BWP before the change, and the BWP is then changed according to the received DCI indicator. Further, if the DCI schedules the PDSCH in the BWP (after the change) after the change, then discrepancies may occur between the number of required DCI bits depending on the settings for the BWP before the change and the number of DCI bits required depending on the settings for the BWP after the change. Thus, the size of the bits required for PDSCH scheduling sent to the BWP after the change may be different from the size of the DCI bits sent to the BWP before the actual change.

[189] In this case, the bit field for the relevant setting contained in the DCI field may be padded with zeros or truncated prior to interpreting the information contained in the DCI, depending on the relevant setting where inconsistencies may occur. Thus, when the UE interprets the DCI, it may interpret the DCI on the condition that the bit field for the relevant setting is padded with zeros or truncated.

[190] If the size of the bit field required for the modified BWP is less than or equal to the size of the bit field of the actually transmitted DCI, then the DCI may represent all possible values of the corresponding bit field such that the scheduling constraint due to the difference in field size does not occur. However, if the bitfield size required for the modified BWP is larger than the bitfield size actually transmitted by the DCI, then the DCI may not point to some bitfield value required for the modified BWP and may therefore restrict PDSCH scheduling.

[191] Therefore, according to some implementations of the present disclosure, UE DCI analysis technologies are described below that allow for mismatches that arise between the size of the DCI required for PDSCH scheduling due to the BWP change and the size of the DCI actually transmitted.

[192] Before explaining the analysis techniques for each DCI format, below with reference to FIG. 19-21, operation from the point of view of a UE, a base station, and a network according to an implementation of the present disclosure is described.

[193] FIG. 19 shows an example of an operation procedure according to the present disclosure from a UE's point of view. Referring to the example of FIG. 19, the UE receives (S1901) the DCI including the first information for changing the active BWP from the first BWP to the second BWP, and transmits the DCI included in the DCI based on the configurations for the PDSCH scheduling related information of the second BWP (S1903). In some implementations, the bits included in the DCI may be generated based on the configuration for the first BWP. To interpret the scheduling information for the PDSCH received in the second BWP, bits may be required based on the settings for the second BWP. If a discrepancy occurs between the number of bits required to interpret the PDSCH scheduling information and the number of bits included in the received DCI, then according to the embodiments described below, the UE may interpret the received DCI and obtain scheduling information for the PDSCH.

[194] If the UE receives PDSCH scheduling information via received DCI analysis according to the implementations detailed below, the PDSCH may be received in the second BWP based on the received PDSCH scheduling information (S1905).

[195] FIG. 20 is a diagram showing an example of a base station operation procedure according to an implementation of the present disclosure. Referring to FIG. 20, the BS may transmit, to the UE, a DCI including first information for changing the active BWP from the first BWP to the second BWP (S2001). In some implementations, in addition to changing the active BWP, the DCI may also include various PDSCH scheduling information. Although the PDSCH may be scheduled to be sent to the second BWP, the DCI shaping criterion may be a configuration for the first BWP. For example, the DCI bit size may be determined based on the configuration for the first BWP and may be inconsistent with the bit size required for the UE to actually schedule the PDSCH transmitted from the second BWP.

[196] Therefore, according to some implementations disclosed in this document, technologies are disclosed for processing each bit field in view of such a mismatch. However, if the bit size required for the second BWP exceeds the bit size of the DCI actually transmitted, then the BS may schedule the PDSCH in the second BWP accordingly. For example, the base station may take into account the DCI size ambiguity that may arise due to a mismatch between the target for the first BWP and the target for the second BWP, and may schedule the PDSCH in the second BWP, within a range that may be represented by the bit size of the actually transmitted DCI. The BS may transmit the PDSCH to the second BWP based on DCI (S2003).

[197] Referring to the example of FIG. 21, the base station may transmit, to the UE, a DCI including first information for changing the active BWP from the first BWP to the second BWP (S2101). In some implementations, the DCI may include various information for PDSCH scheduling, in addition to the first information for changing the active BWP. In this case, although the PDSCH may be scheduled to be sent to the second BWP, the DCI shaping criteria may be based on the configuration for the first BWP. For example, the DCI bit size may be determined based on the configuration for the first BWP and may be inconsistent with the bit size required for the UE to actually schedule the PDSCH transmitted from the second BWP.

[198] Therefore, according to some implementations disclosed in this document, technologies are disclosed for processing each bit field in view of such a mismatch. However, if the bit size required for the second BWP exceeds the bit size of the DCI actually transmitted, then the BS may schedule the PDSCH in the second BWP accordingly. For example, the base station may take into account the DCI size ambiguity that may arise due to a mismatch between the target for the first BWP and the target for the second BWP, and may schedule the PDSCH in the second BWP, within a range that may be represented by the bit size of the actually transmitted DCI.

[199] In some implementations, the UE receiving the DCI parses and obtains the PDSCH scheduling related information included in the DCI based on the configuration for the second BWP (S2103). In some implementations, the bits included in the DCI may be generated based on the configuration for the first BWP. To interpret the scheduling information for the PDSCH received in the second BWP, bits may be required based on the configurations for the second BWP. If a discrepancy occurs between the number of bits required to interpret the PDSCH scheduling information and the number of bits included in the received DCI, then according to the embodiments described below, the UE may interpret the received DCI and obtain scheduling information for the PDSCH.

[200] In some implementations, the BS may send the PDSCH to the second DCI-based BWP (S2105).

[201] The following provides a description of an example of technologies directed at scenarios in which a mismatch occurs between the DCI bit size required for the modified BWP and the DCI bit size actually transmitted for each DCI format for PDSCH scheduling.

[202] Table 4 shows an example of DCI format 0_1 fields that are padded with zeros or truncated before DCI analysis due to BWP switching.

[203] Tab. 4

DCI field Related parameter Related configuration Possible values Frequency Domain Resource Assignment resourceAllocation PUSCH-Config ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} rbg-Size PUSCH-Config ENUMERATED {config2} frequencyHoppingOffsetLists PUSCH-Config SEQUENCE(SIZE(1..4)) OF INTEGER(1...maxNrofPhysicalResourceBlocks-1) locationAndBandwidth BWP provided in BWP-UplinkCommon INTEGER (0...0.37949) Assigning Time Domain Resources pusch-AllocationList PUSCH-Config SEQUENCE (SIZE (1...maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocation Frequency hopping flag resourceAllocation PUSCH-Config ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} SRS resource indicator srs-ResourceIdList SRS-ResourceSet SEQUENCE (SIZE (1...maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId Usage SRS-ResourceSet ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching} maxRank PUSCH-Config INTEGER (1...4) txConfig PUSCH-Config ENUMERATED {codebook, nonCodebook} Precoding information and number of levels txConfig PUSCH-Config ENUMERATED {codebook, nonCodebook} transformPrecoder PUSCH-Config ENUMERATED {enabled, disabled} maxRank PUSCH-Config INTEGER (1...4) codebookSubset PUSCH-Config ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent} Antenna ports transformPrecoder PUSCH-Config ENUMERATED {enabled, disabled} txConfig PUSCH-Config ENUMERATED {codebook, nonCodebook} maxRank PUSCH-Config INTEGER (1...4) dmrs-Type DMRS-UplinkConfig provided in PUSCH-Config ENUMERATED {type2} maxLength DMRS-UplinkConfig provided in PUSCH-Config ENUMERATED {len2} PTRS-DMRS association transformPrecoder PUSCH-Config ENUMERATED {enabled, disabled} maxRank PUSCH-Config INTEGER (1...4) phaseTrackingRS DMRS-UplinkConfig provided in PUSCH-Config SetupRelease{PTRS-UplinkConfig} Beta bias indicator betaOffsets UCI-OnPUSCH provided in PUSCH-Config CHOICE {
dynamic SEQUENCE (SIZE (4)) OF BetaOffsets, semiStatic BetaOffsets } Initializing the DMRS sequence transformPrecoder PUSCH-Config ENUMERATED {enabled, disabled}

[204] [205] Referring to Table 4, when parsing the DCI field included in the DCI format 0_1 according to the BWP change, when performing zero padding on the bit field to allocate time-frequency domain resources, scheduling flexibility may be limited. However, the complexity of the system can be reduced. In addition, when frequency hopping is performed, padding with zeros may correspond to using the non-hopping mode for PUSCH transmission. On the other hand, since the sounding reference signal (SRS) is transmitted after the active UL (uplink) BWP changes, the gNB schedules a DCI format 0_1 indicating the UL BWP change without precise information regarding the channel state or beam information for the new bwp. In addition, when a BWP change is initiated, a transmission configuration indicator (TCI), a modulation and coding scheme (MCS), and/or a scheduling request indicator (SRI) due to a BWP change cannot be used because the DCI for failover (e.g., DCI format indicator 0_0)) may not be accurate. On the other hand, information regarding the new BWP may not be accurate regardless of the number of bits available for each DCI field.

[206] Similarly, at the antenna port or PTRS-DMRS association, since the gNB cannot accurately determine the most appropriate DMRS port to transmit PUSCH or PTRS before SRS reception, the bit field size associated with the antenna port or PTRS-DMRS , is not limited. In other words, the new BWP-associated antenna port or PTRS-DMRS association information may be inaccurate regardless of the bit field size limitation because the base station cannot accurately ascertain the antenna port or PTRS-DMRS association information for the BWP after the change.

[207] In scenarios where the beta bias indicator is moderately set as a semi-static beta bias, a dynamic beta bias indicator can be used. On the other hand, one of the values that may be indicated by the beta bias indicator may need to be moderately set. For example, a moderately set value may be indicated using index 0 of the bit field.

[208] Initialization of the DMRS sequence may be used to support MU-MIMO (Multi-User Multiple Input Multiple Output Technology). Even if the DCI format 0_1 indicating the UL BWP change does not have a bit field for DMRS initialization, or the DMRS initialization value is set to 0, the gNB may set the DMRS to 1 to support other UEs for the MU. A DCI indicating initialization may be dispatched.

[209] To summarize the above description, no restrictions are placed on the selection of a DCI format 0_1 bitfield even if a significant portion of the bitfields for the BWP is truncated after the change. Therefore, even when the BWP is changed, the DCI format 0_1 bit fields can be used as is. However, regardless of the bit field size, information regarding some DCI fields, such as SRS resource indicator, precoding information, number of layers, antenna port, and/or PTRS-DMRS association information, may not be accurate.

[210] Table 5 below shows an example of DCI format 1_1 fields that are padded with zeros or truncated before DCI analysis due to a BWP change.

[211] Tab. 5

DCI field Related parameter Related configuration Possible values Frequency Domain Resource Assignment resourceAllocation PDSCH-Config ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} rbg-Size PDSCH-Config ENUMERATED {config1, config2} locationAndBandwidth BWP provided in BWP-DownlinkCommon INTEGER (0...0.37949) Assigning Time Domain Resources pusch-AllocationList PDSCH-Config SEQUENCE (SIZE (1...maxNrofUL-Allocations)) OF PDSCH-TimeDomainResourceAllocation VRB-PRB Conversion resourceAllocation PDSCH-Config ENUMERATED {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} PRB Packet Size Indicator prb-BundlingType PDSCH-Config CHOICE {
static SEQUENCE {bundleSize ENUMERATED {n4, wideband}
},
dynamic SEQUENCE {bundleSizeSet1 ENUMERATED {n4, wideband, n2-wideband, n4-wideband}
bundleSizeSet2 ENUMERATED {n4, wideband}} Speed matching indicator rateMatchPatternToAddModList PDSCH-Config SEQUENCE(SIZE(1..maxNrofRateMatchPatterns)) OF RateMatchPattern ZP CSI-RS trigger zp-CSI-RS-ResourceToAddModList PDSCH-Config SEQUENCE(SIZE(1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-Resource For transport block 2 maxNrofCodeWordsScheduledByDCI PDSCH-Config ENUMERATED {n1, n2} Antenna port(s) dmrs-Type DMRS-DownlinkConfig provided in PDSCH-Config ENUMERATED {type2} maxLength DMRS-DownlinkConfig provided in PDSCH-Config ENUMERATED {len2} Transmission configuration indicator tci-PresentInDCI ControlResourceSet provided in PDCCH-Config ENUMERATED {enabled} Initializing the DMRS sequence scramblingID1 DMRS-DownlinkConfig provided in PDSCH-Config INTEGER (0...65535)

[212] [213] By performing zero-padding on a bit field to allocate time-frequency domain resources, scheduling flexibility may be limited, but system complexity may be reduced. If the VRB-PRB transform field is padded with zeros, then the non-interleaved VRB-PRB transform may be used for the PDSCH transmission.

[214] If the PRB packetization size indicator is padded with zeros, then the second PRB packetization size value may be used for PDSCH reception. In some scenarios, even this may not be disadvantageous in terms of scheduling flexibility compared to a semi-static PRB burst size.

[215] The rate matching indicator or ZP CSI-RS flip-flop can be significant only if the rate matching pattern or ZP CSI-RS-template to be indicated (by the rate matching indicator or by the ZP CSI-RS flip-flop) overlaps ( partially or completely) with assigned resources, which are indicated by allocation of time-frequency domain resources. Therefore, even if there is a limit on the size of the bit field of the rate negotiation indicator or ZP CSI-RS flip-flop, the gNB can perform such control to prevent allocated resources from overlapping with the rate negotiation pattern or ZP CSI-RS pattern that cannot be indicated by the indicator. rate matching or ZP CSI-RS flip-flop, respectively. Therefore, limiting the size of the bit field of the rate matching indicator or ZP of the CSI-RS flip-flop is not problematic for the operation of the UE and the operation of the base station.

[216] In the bit field for transport block 2, if a DCI format of 1_1 indicating a change in the active DL BWP can schedule only one transport block, but the new BWP (i.e., the changed BWP) supports up to two transport blocks, then in some implementations, the second transmission block may be deactivated. In other words, according to some implementations, if the BWP before the change, in which the DCI format 1_1 indicating the change of the active DL BWP, supports only one transport block, but the new BWP supports up to two transport blocks, then the second transport block may be deactivated. Therefore, in this case, the condition may be implemented to deactivate the transport block, at the time of determining the size of the transport block.

[217] As a specific example, even if the maxNrofCodeWordsScheduledByDCI parameter configured by the upper layers indicates that two codeword transmissions are activated, if the DCI indicating an active BWP change contains only one set of MCS, NDI, and RV bit fields, then only one transport block can be activated. For example, even if maxNrofCodeWordsScheduledByDCI is set to 2 for the BWP after the change by the top layer, if there is only one set of MCS, NDI, and RV bitfields in the DCI that indicates a change to the active BWP sent to the BWP before the change, then the second transport block may be deactivated.

[218] Here, if the second transport block is deactivated, then according to some implementations, the UE can detect DCI, provided that the MCS, NDI, and RV bitfield sets for the second transport block in DCI format 1_1 are transmitted zero-padded. Alternatively, the UE may ignore the MCS, NDI, and RV bitfield sets for the second transport block in DCI format 1_1. In some implementations, the UE may perform both actions. Thus, the UE may ignore the field set, provided that the MCS, NDI, and RV bit field sets for the second transport block in DCI format 1_1 are padded with zeros.

[219] In some implementations, DMRS initialization may be used to support MU-MIMO. For example, even in scenarios where the DCI format 1_1 (indicating the DL BWP switch) does not have a bit field for DMRS initialization (and thus the value for DMRS initialization is set to 0), the gNB may still schedule DCI indicating initialization of DMRS sequence 1 for another UE to support operation in MU-MIMO mode.

[220] In other words, for some DCI fields (eg, antenna ports or transmission configuration indicator (TCI)), regardless of the size of the bit field, the network may not know the information for the field corresponding to the BWP after the switch. Therefore, even if the bitfield is truncated significantly to match the new BWP after the switch, there are no restrictions on the selection of the bitfield for DCI format 1_1.

[221] For MIMO-related parameters, since the CSI-RS or SRS must be transmitted after the BWP switch, the gNB may not be able to perform channel estimation or beam detection for the new BWP (i.e., post-switch BWP) to schedule the PDSCH or PUSCH . In this case, as opposed to using the DCI-Specified Transmit Precoding Matrix Indicator (TPMI), antenna ports, scheduling request indicator (SRI), or transmission configuration indicator (TCI), the default setting can be used instead, similar to the initial transmission prior to RRC (Radio Resource Control) configuration.

[222] As a specific example, if the PUSCH is scheduled by a DCI that indicates a BWP active UL switch, then the beam information for the PUSCH transmission may reuse beam information identical to the beam information of the PUCCH resource having the lowest index of the PUCCH resources. In addition, if the PDSCH is scheduled by a DCI that indicates active DL BWP switching, then the beam information for the PDSCH transmission may reuse beam information identical to the beam information of the control resource set (base set) having the lowest index among the base sets.

[223] In some implementations, such operations may ignore DCI fields that are not present in the DCI failover format such that the operations behave similarly to the PDSCH/PUSCH scheduling operations that are scheduled by the failover DCI. In other words, if a default setting is intended, the ability to ignore DCI fields that do not exist in the DCI failover format may be considered to make it easier for DCI to direct a BWP change.

[224] For example, consider a scenario in which a DCI schedules a PDSCH transmission to a BWP after a switch, and in which this DCI indicates a BWP switch. In such scenarios, the quasi-collocation information (QCL), the spatial relationship information, or the transmission configuration indicator (TCI) information can presumably be identical to the base set information with the lowest index.

[225] For example, after changing the BWP by the DCI indicating the BWP switching, the QCL information, the spatial relationship information, or the TCI information for the PDSCH transmission scheduled in the BWP may be the same as the QCL information, the spatial relationship information, or the TCI information. , which is configured for the base set associated with the DCI, indicating the BWP change. Alternatively, it may be assumed that the new BWP (ie, BWP after handover) is equal to QCL information, spatial relationship information, or TCI information for the PDSCH that is scheduled by the DCI for failover.

[226] Similarly, in a PUSCH transmission that is scheduled by a DCI indicating a BWP switch, it can be assumed that the QCL information, the spatial relationship information, or the SRS resource indicator information is the same as the PUCCH with the lowest index, or that it is the same as the QCL. -information, spatial relationship information, or SRS resource indicator information for Msg3 in the new BWP (after switching). In particular, the techniques described above can be applied in conjunction with a DCI to change the BWP.

[227] In some implementations, DCI-based BWP change may occur flexibly, and in some cases, default setting-based operations may be performed only for a particular combination of MIMO-related parameters to use the value of a MIMO parameter based on DCI indicators. . For example, when the MIMO-related parameters are set to 0, an operation can be performed according to the default setting.

[228] FIG. 22 shows an example of radio communication equipment according to an implementation of the present disclosure.

[229] The wireless communication equipment illustrated in FIG. 22 may represent a terminal and/or a base station according to an implementation of the present disclosure. However, the wireless communications equipment of FIG. 22 is not necessarily limited to the terminal and/or base station according to the present disclosure, and may implement various types of equipment such as a vehicle communication system or equipment, wearable equipment, laptop computer, and so on.

[230] In the example of FIG. 22, a terminal and/or base station according to an implementation of the present disclosure includes at least one processor 10, such as a digital signal processor or microprocessor, a transceiver 35, a power control module 5, an antenna 40, a battery 55 , a display 15, a keypad 20, at least one storage device 30, a Subscriber Identity Module (SIM) card 25, a speaker 45 and a microphone 50, and the like. In addition, the terminal and/or base station may include one antenna or multiple antennas. Transceiver 35 may also be referred to as an RF module.

[231] At least one processor 10 may be configured to implement the functions, procedures, and/or methods described in FIG. 1-21. In at least some of the implementations described in FIG. 1-21, at least one processor 10 may implement one or more protocols, such as air interface protocol layers (eg, function layers).

[232] At least one storage device 30 is connected to at least one processor 10 and stores information associated with the operation of at least one processor 10. At least one storage device 30 may be internal or external , for at least one processor 10 and may be connected to at least one processor 10 through a variety of technologies, such as through a wired or wireless connection.

[233] The user may enter various types of information (eg, instructional information such as a telephone number) through various technologies, such as pressing a button on the keypad 20 or voice activation using the microphone 50. The at least one processor 10 executes the corresponding functions such as receiving and/or processing user information and dialing a telephone number.

[234] It is also possible to retrieve data (eg, work data) from the SIM card 25 or at least one storage device 30 to perform the corresponding functions. In addition, at least one processor 10 may receive and process GPS information from the GPS chip to obtain location information of the terminal and/or base station, such as vehicle navigation, a map service, and the like, or perform functions related to location information. In addition, at least one processor 10 may display these various types of information and data on the display 15 for reference and convenience of the user.

[235] The transceiver 35 is connected to at least one processor 10 to transmit and/or receive radio signals, such as RF signals. At this time, at least one processor 10 may control the transceiver 35 to initiate communications and transmit wireless signals including various types of information or data, such as voice data. The transceiver 35 may include a receiver for receiving a radio signal and a transmitter for transmitting. The antenna 40 facilitates the transmission and reception of radio signals. In some implementations, upon receiving a radio signal, transceiver 35 may transmit and convert the signal to baseband frequency for processing by at least one processor 10. The processed signals may be processed according to various techniques, such as conversion to audible or read information, and such signals can be output through the speaker 45.

[236] In some implementations, the sensor may also be coupled to at least one processor 10. The sensor may include one or more sensors configured to detect various types of information including speed, acceleration, light, vibration, and etc. The at least one processor 10 receives and processes sensor information received from the sensor, such as proximity, position, image, and the like, thereby performing various functions such as collision avoidance and autonomous driving.

[237] Meanwhile, various components such as a camera, a USB port, and the like may be further included in the terminal and/or the base station. For example, the camera may further be connected to at least one processor 10 which may be used for a variety of services such as autonomous navigation, vehicle safety services, and the like.

[238] FIG. 22 merely illustrates one example of the equipment constituting a terminal and/or a base station, and the present disclosure is not limited thereto. For example, some components such as keypad 20, global positioning system (GPS) chip, sensor, speaker 45, and/or microphone 50 may be excluded for terminal and/or base station implementations in some implementations.

[239] In particular, in order to implement implementations of the present disclosure, the following describes an example of operations of the wireless communication device shown in FIG. 22 in the case of a terminal according to an implementation of the present disclosure. If the wireless communications equipment is a terminal according to an implementation of the present disclosure, at least one processor 10 may include a transceiver 35 to receive a DCI containing first information for changing an active BWP from a first BWP to a second BWP, and may interpret and obtain PDSCH scheduling related information included in the DCI based on the configuration for the second BWP. The bits included in the DCI may be generated based on the configuration for the first BWP, and the bits based on the configurations for the second BWP may be required in order to interpret the scheduling information for the PDSCH received in the second BWP. If a discrepancy occurs between the number of bits required to interpret the PDSCH scheduling information and the number of bits included in the received DCI, then the DCI may be interpreted according to the implementations described based on FIG. 1-21 and tab. 4-5 to obtain scheduling information for the PDSCH.

[240] If at least one processor 10 obtains the PDSCH scheduling information via DCI interpretation in accordance with the implementations described based on FIG. 1-21 and tab. 4-5, at least one processor 10 may control the transceiver 35 to receive the PDSCH in the second BWP based on the received PDSCH scheduling information.

[241] In some implementations of the present disclosure, when the wireless communication equipment shown in FIG. 15 is a base station, at least one processor 10 can control the transceiver 35 to send to the UE a DCI that includes first information for changing the active BWP from the first BWP to the second BWP. In this case, the DCI may include various information for PDSCH scheduling, in addition to changing the active BWP. In this case, the PDSCH, for example, may be scheduled to be transmitted to the second BWP. Thus, the DCI bit size may be determined based on the assignment for the first BWP and may be inconsistent with the bit size required for the UE to actually schedule the PDSCH transmitted from the second BWP. In such scenarios, the interpretation of each bit field caused by such a mismatch may be performed in accordance with the implementations described based on FIG. 1-21 and tab. 4-5.

[242] However, if the bit size required for the second BWP exceeds the bit size of the DCI actually transmitted, then the BS may schedule the PDSCH in the second BWP accordingly. For example, if UE 10 has a mismatch between the configurations for the first BWP and the configurations for the second BWP, given the DCI size ambiguity that may occur, then the PDSCH in the second BWP may be scheduled, within a range that may be represented by the size in bits of the actually transmitted DCI . Meanwhile, the base station can control the transceiver 35 to transmit the PDSCH to the second BWP based on DCI.

[243] The implementations described above are implementations in which the elements and features of the present disclosure are combined in a predefined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented in a form that is not combinable with other components or features. It is also possible to construct implementations of the present disclosure by combining certain elements and/or features. The order of operations described in implementations of this disclosure may vary. Some configurations or features in certain implementations may be included in other implementations or may be replaced by corresponding configurations or features in other implementations. Obviously, claims that are not explicitly recited in the claims can be combined with the ability to form an implementation or be included in a new claim by post-filing amendment.

[244] A particular operation described herein as being performed by a base station may be performed by its upper node, in some cases. Thus, it is clear that various operations performed for communication with a terminal in a network including a plurality of network nodes including a base station may be performed by the base station or by a network node other than the base station. The base station may be replaced by terms such as fixed station, Node B, evolved Node B (eNB), access point, and the like.

[245] Implementations according to the present invention may be implemented by various means, such as hardware, firmware, software, or a combination of the above. In the case of a hardware implementation, an implementation of the present disclosure may include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processors (DSPDs), field programmable gate arrays (PLDs), processors , controllers, microcontrollers, microprocessors, etc.

[246] In the case of implementation by firmware or software, an implementation of the present invention may be implemented in the form of a module, procedure, function, or the like. to perform the functions or operations described above. The program code may be stored in a storage device and sent by the processor. The memory may be located inside or outside the processor and may communicate with the processor through various known means.

[247] Specialists in the art should be obvious that the present invention can be implemented in other specific forms without departing from the essence of the disclosure of the essence. Accordingly, the foregoing description is not to be construed in a limiting sense in all respects and is to be considered illustrative. The scope of the present invention is to be determined by a rational interpretation of the appended claims, and all changes within the scope of the equivalents of the present disclosure are included within the scope of the present invention.

Industrial Applicability

[248] Although the method and equipment for transmitting and receiving a downlink data channel are described with reference to the fifth generation NewRAT system, the present disclosure may apply to various wireless communication systems other than the fifth generation NewRAT system.

Claims (61)

1. A method for receiving a downlink signal by a user equipment (UE) in a wireless communication system, the method comprising: - receive, in the first part of the downlink (DL) bandwidth (BWP), downlink control information (DCI) containing (i) BWP-switching information that indicates active DL BWP switching from the first DL BWP to the second DL BWP , and (ii) transport block (TB) information that is associated with a TB for a physical downlink shared channel (PDSCH); - based on configuring the UE to receive at most 1 TB for PDSCH in the first DL BWP and at most 2 TB for PDSCH in the second DL BWP: treat DCI including TB information in DCI as associated with only one TB of 2 TB configured for PDSCH in the second DL BWP; and receiving the PDSCH in the second DL BWP based on the BWP switching information and TB information, wherein the DCI processing includes receiving a transmission configuration indicator (TCI) for the control resource set (basic set) in the second DL BWP based on the fact that the DCI received in the first DL BWP indicates active DL BWP switching. 2. The method of claim 1, wherein processing the DCI including the TB information in the DCI as being associated with only one TB out of the 2 TBs configured for the PDSCH in the second DL BWP comprises: - processing the first TB information, which is associated with one TB of 2 TB; and - determine that the second TB information, which is associated with another TB of 2 TB, consists of padding with zeros. 3. The method of claim 1, wherein processing the DCI including the TB information in the DCI as being associated with only one TB out of the 2 TBs configured for the PDSCH in the second DL BWP comprises: - processing the first TB information, which is associated with one TB of 2 TB; and - ignore the second TB information, which is associated with another TB of 2 TB. 4. The method of claim 3, wherein ignoring the second TB information comprises: - process the TB information in DCI by ignoring the bit fields for the modulation and coding scheme (MCS), new data indicator (NDI) and spare version (RV) for another TB of 2 TB. 5. The method of claim 1, wherein processing the DCI including the TB information in the DCI as being associated with only one TB out of the 2 TBs configured for the PDSCH in the second DL BWP comprises: - processing the first TB information, which is associated with one TB of 2 TB; and - determine that the second TB information, which is associated with another TB of 2 TB, is deactivated. 6. The method of claim 1, wherein configuring the UE to receive at most 1 TB for PDSCH in the first DL BWP and at most 2 TB for PDSCH in the second DL BWP is based on the following steps, in which: - receive, by the UE via the first signaling of the RRC layer, the first parameter maxNrofCodeWordsScheduledByDCI for the first DL BWP, which is equal to 1, and - receive, by the UE through the second signaling RRC layer, the second parameter maxNrofCodeWordsScheduledByDCI for the second DL BWP, which is equal to 2. 7. The method of claim 1, wherein the first DL BWP consists of a first plurality of physical resource blocks (PRBs) that are contiguous in frequency, and - wherein the second DL BWP consists of a second set of PRBs that are contiguous in frequency. 8. The method of claim 1, wherein the active DL BWP consists of a plurality of physical resource blocks (PRBs) that are contiguous in frequency, and wherein the UE is configured to receive the PDSCH. 9. The method of claim 1, wherein the wireless communication system is a 3rd Generation Partnership Project (3GPP) wireless communication system. 10. A processor-readable medium containing instructions stored thereon for performing the method of claim 1. 11. Equipment configured to control a user equipment (UE) to receive a downlink signal in a wireless communication system, the equipment comprising: - at least one processor; and - at least one storage device operatively connected to at least one processor and storing instructions that, when executed by at least one processor, perform operations comprising: - receiving, in the first downlink (DL) bandwidth part (BWP), downlink control information (DCI) containing (i) BWP switching information that indicates active DL BWP switching from the first DL BWP to the second DL BWP , and (ii) transport block (TB) information that is associated with a TB for a physical downlink shared channel (PDSCH); - based on configuring the UE to receive at most 1 TB for PDSCH in the first DL BWP and at most 2 TB for PDSCH in the second DL BWP: processing DCI including TB information in DCI as associated with only one TB of 2 TB configured for PDSCH in the second DL BWP; and - receiving the PDSCH in the second DL BWP based on the BWP switching information and TB information, wherein the DCI processing includes receiving a transmission configuration indicator (TCI) for the control resource set (basic set) in the second DL BWP based on the fact that the DCI received in the first DL BWP indicates active DL BWP switching. 12. The equipment of claim 11, wherein the processing of the DCI including the TB information in the DCI as being associated with only one TB of the 2 TBs configured for the PDSCH in the second DL BWP comprises: - processing the first TB-information, which is associated with one TB out of 2 TB; and - determining that the second TB information, which is associated with another TB of 2 TB, consists of padding with zeros. 13. The equipment of claim 11, wherein the processing of a DCI including TB information in the DCI as associated with only one TB of the 2 TBs configured for the PDSCH in the second DL BWP comprises: - processing the first TB-information, which is associated with one TB out of 2 TB; and - ignoring the second TB-information, which is associated with another TB of 2 TB. 14. Equipment according to claim 13, in which ignoring the second TB information contains: - processing TB information in DCI by ignoring bit fields for modulation and coding scheme (MCS), new data indicator (NDI) and spare version (RV) for another TB of 2 TB. 15. The equipment of claim 11, wherein the UE is configured to receive at most 1 TB for PDSCH in the first DL BWP and at most 2 TB for PDSCH in the second DL BWP based on the following: - receiving, by the UE via the first RRC layer signaling, the first parameter maxNrofCodeWordsScheduledByDCI for the first DL BWP, which is equal to 1, and - receiving, by the UE via the second RRC layer signaling, the second parameter maxNrofCodeWordsScheduledByDCI for the second DL BWP, which is equal to 2. 16. A user equipment (UE) configured to receive a downlink signal in a wireless communication system, the UE comprising: - receiving-transmitting device; - at least one processor; and - at least one storage device operatively connected to at least one processor and storing instructions that, when executed by at least one processor, perform operations comprising: - receiving, in the first downlink (DL) bandwidth part (BWP), downlink control information (DCI) containing (i) BWP switching information that indicates active DL BWP switching from the first DL BWP to the second DL BWP , and (ii) transport block (TB) information that is associated with a TB for a physical downlink shared channel (PDSCH); - based on configuring the UE to receive at most 1 TB for PDSCH in the first DL BWP and at most 2 TB for PDSCH in the second DL BWP: processing DCI including TB information in DCI as associated with only one TB of 2 TB configured for PDSCH in the second DL BWP; and - receiving the PDSCH in the second DL BWP based on the BWP switching information and TB information, wherein the DCI processing includes receiving a transmission configuration indicator (TCI) for the control resource set (basic set) in the second DL BWP based on the fact that the DCI received in the first DL BWP indicates active DL BWP switching. 17. The UE of claim 16, wherein processing the DCI including TB information in the DCI as associated with only one TB of the 2 TBs configured for the PDSCH in the second DL BWP comprises: - processing the first TB-information, which is associated with one TB out of 2 TB; and - determining that the second TB information, which is associated with another TB of 2 TB, consists of padding with zeros. 18. The UE of claim 16, wherein processing the DCI including TB information in the DCI as associated with only one TB of the 2 TBs configured for the PDSCH in the second DL BWP comprises: - processing the first TB information, which is associated with one TB out of 2 TB; and - ignoring the second TB-information, which is associated with another TB from 2 TB. 19. The UE of claim 18, wherein ignoring the second TB information comprises: - processing TB information in DCI by ignoring bit fields for modulation and coding scheme (MCS), new data indicator (NDI) and spare version (RV) for another TB of 2 TB. 20. The UE of claim 16, wherein configuring the UE to receive at most 1 TB for PDSCH in the first DL BWP and at most 2 TB for PDSCH in the second DL BWP is based on the following: - receiving, by the UE via the first RRC layer signaling, the first parameter maxNrofCodeWordsScheduledByDCI for the first DL BWP, which is equal to 1, and - receiving, by the UE through the second signaling of the RRC layer, the second parameter maxNrofCodeWordsScheduledByDCI for the second DL BWP, which is equal to 2.

Images