Method and apparatus for performing downlink transmission and reception in wireless communication system

Abstract

A method and apparatus for communicating in a wireless communication system are disclosed. According to one embodiment of the present disclosure, a method performed by a terminal comprises the steps of: receiving a first downlink channel and a second downlink channel from a base station in a first time slot; and decoding the first downlink channel and the second downlink channel on the basis that the number of physical resource blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold value, the first downlink channel and the second downlink channel may partially or fully overlap in the time domain.

Description

TECHNICAL FIELD

[0001] The disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for performing downlink transmission and reception in a narrow band in a wireless communication system. BACKGROUND

[0002] A mobile communication system has been developed to provide a voice service while guaranteeing the mobility of a user. However, the mobile communication system has been expanded to a data service as well as a voice service, and currently, an explosive increase in traffic has led to a shortage of resources, and users have demanded faster services, and thus a more advanced mobile communication system has been required.

[0003] Overall requirements for the next-generation mobile communication system should be able to support the accommodation of explosive data traffic, a significant increase in transmission rate per user, the accommodation of a significantly increased number of connected devices, a very low end-to-end latency, and high energy efficiency. To this end, various techniques such as dual connectivity, massive multiple input multiple output (massive MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, device networking, etc. have been researched. SUMMARY

[0004] TECHNICAL PROBLEM

[0005] The technical problem of the disclosure is to provide a method and apparatus for performing downlink transmission and reception in a wireless communication system.

[0006] The technical problem of the disclosure is to provide a method and apparatus for transmitting and receiving at least one unicast / multicast downlink in a narrow band.

[0007] The technical problem of the disclosure is to provide a method and apparatus for processing a plurality of unicast / multicast downlinks simultaneously received in a narrow band.

[0008] The technical objects to be achieved by the disclosure are not limited to the aforementioned technical objects, and other technical objects not described herein will be clearly understood by a person skilled in the art from the following description.

[0009] TECHNICAL SOLUTION

[0010] According to one embodiment of the disclosure, a method performed by a user equipment (UE) in a wireless communication system can include receiving a first downlink channel and a second downlink channel from a base station in a first slot, and decoding the first downlink channel and the second downlink channel based on a number of physical resource blocks (PRBs) allocated for each of the first downlink channel and the second downlink channel being less than or equal to a first threshold, and the first downlink channel and the second downlink channel can be partially or completely overlapped in a time domain.

[0011] According to one embodiment of the disclosure, a method performed by a user equipment (UE) in a wireless communication system can include receiving a first downlink channel from a base station in a slot n (where n is an integer greater than or equal to 0), and based on a number of physical resource blocks (PRBs) allocated to the first downlink channel being less than or equal to a second threshold, processing reception of the first downlink channel, and based on the number of PRBs allocated to the first downlink channel exceeding the second threshold, and the first downlink channel reception being a repeated reception or a second downlink channel being received in a slot n+1, the UE can not process reception of the first downlink channel.

[0012] According to one embodiment of the disclosure, a method performed by a base station in a wireless communication system can include transmitting, to a user equipment (UE), information for scheduling a first downlink channel and a second downlink channel in a first slot, and transmitting, to the UE, the first downlink channel and the second downlink channel in the first slot, and based on a number of physical resource blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel being less than or equal to a first threshold, the first downlink channel and the second downlink channel can be decoded by the UE, and the first downlink channel and the second downlink channel can be partially or completely overlapped in a time domain.

[0013] Technical effects

[0014] According to various embodiments of the disclosure, a method and an apparatus for performing downlink transmission and reception in a wireless communication system can be provided.

[0015] According to various embodiments of the disclosure, a method and an apparatus for transmitting and receiving at least one unicast / multicast downlink in a narrow band can be provided.

[0016] According to various embodiments of the disclosure, a method and an apparatus for processing a plurality of unicast / multicast downlinks simultaneously received in a narrow band can be provided.

[0017] According to various embodiments of the disclosure, an enhanced reduced capability (eRedCap) UE can more efficiently process downlinks scheduled in a unit slot.

[0018] Effects achievable by the disclosure are not limited to the above-mentioned effects, and other effects not described herein can be clearly understood by those skilled in the art from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0019] The accompanying drawings, which are included as part of the detailed description to understand the disclosure, provide embodiments of the disclosure and describe technical features of the disclosure through the detailed description.

[0020] FIG. 1A structure of a wireless communication system to which the disclosure can be applied is illustrated.

[0021] FIG. 2 A frame structure in a wireless communication system to which the disclosure can be applied is illustrated.

[0022] FIG. 3 A resource grid in a wireless communication system to which the disclosure can be applied is illustrated.

[0023] FIG. 4 A physical resource block in a wireless communication system to which the disclosure can be applied is illustrated.

[0024] FIG. 5 A slot structure in a wireless communication system to which the disclosure can be applied is illustrated.

[0025] FIG. 6 A physical channel used in a wireless communication system to which the disclosure can be applied and a general signal transmission and reception method using the same are illustrated.

[0026] FIG. 7 is a diagram illustrating a procedure in which a UE performs communication according to an embodiment of the disclosure.

[0027] FIG. 8 is a diagram illustrating a procedure in which a base station performs communication according to an embodiment of the disclosure.

[0028] FIG. 9 is a diagram illustrating a case in which a plurality of channels overlap in a time domain according to an embodiment of the disclosure.

[0029] FIG. 10 is a diagram illustrating a case in which a plurality of channels do not overlap in a time domain according to an embodiment of the disclosure.

[0030] FIG. 11 is a diagram illustrating a case in which an MBS PDSCH is repeatedly allocated in a bandwidth of more than 5 MHz according to an embodiment of the disclosure.

[0031] FIG. 12 is a diagram illustrating a case in which one or more channels are scheduled in a single slot according to an embodiment of the disclosure.

[0032] FIG. 13 is a diagram illustrating a case in which one or more channels are scheduled in a single slot according to an embodiment of the disclosure.

[0033] FIG. 14 is a diagram illustrating a case in which a plurality of channels are scheduled in a single slot according to an embodiment of the disclosure.

[0034] FIG. 15is a diagram illustrating a case where more PRBs than the number of PRBs corresponding to a 5 MHz bandwidth are scheduled in a single slot according to an embodiment of the disclosure.

[0035] FIG. 16 A block diagram of a wireless communication device according to an embodiment of the disclosure is illustrated. DETAILED DESCRIPTION

[0036] Hereinafter, embodiments according to the disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed by the accompanying drawings is intended to describe exemplary embodiments of the disclosure, and is not intended to represent the only embodiment that can implement the disclosure. The following detailed description includes specific details to provide a complete understanding of the disclosure. However, those skilled in the relevant art will know that the disclosure can be implemented without the specific details.

[0037] In some cases, known structures and devices can be omitted, or can be shown in the form of a block diagram based on the core function of each structure and device in order to facilitate the prevention of the concept of the disclosure from being ambiguous.

[0038] In the disclosure, when an element is referred to as being "connected", "combined", or "linked" to another element, it can include an indirect connection relationship between the other element and a further element existing therebetween as well as a direct connection relationship. In addition, in the disclosure, the term "include" or "have" designates the existence of the mentioned features, steps, operations, components, and / or elements, but does not exclude the existence or addition of one or more other features, stages, operations, components, elements, and / or groups thereof.

[0039] In the disclosure, terms such as "first", "second", and the like are used only to distinguish one element from another element, and are not used to limit the elements, unless otherwise specified, and do not limit the order or importance between the elements, etc. Therefore, within the scope of the disclosure, a first element in an embodiment can be referred to as a second element in another embodiment, and likewise, a second element in an embodiment can be referred to as a first element in another embodiment.

[0040] The terms used in the disclosure are intended to describe the specific embodiments, and are not intended to limit the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form, unless the context clearly dictates otherwise. The term "and / or" used in the disclosure can refer to one of the relevant listed items, or mean that it refers to and includes any and all possible combinations of two or more of them. In addition, unless otherwise specified, " / " and "and / or" between words in the disclosure have the same meaning.

[0041] The present disclosure describes a wireless communication network or a wireless communication system, and operations performed in a wireless communication network can be performed in a process in which a device (e.g., a base station) controlling a network and transmitting or receiving a signal of a corresponding wireless communication network controls the network, or can be performed in a process in which a terminal associated with a corresponding wireless network transmits or receives a signal between the network or the terminal.

[0042] In the present disclosure, a transmission or reception channel includes the meaning of transmitting or receiving information or a signal through a corresponding channel. For example, transmitting a control channel means transmitting control information or a control signal through a control channel. Similarly, transmitting a data channel means transmitting data information or a data signal through a data channel.

[0043] Hereinafter, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter can be a part of a base station, and a receiver can be a part of a terminal. In the uplink, a transmitter can be a part of a terminal, and a receiver can be a part of a base station. The base station can be expressed as a first communication device, and the terminal can be expressed as a second communication device. The base station (BS) can be replaced with terms such as a fixed station, a Node B, an eNB (evolved Node B), a gNB (next-generation Node B), a BTS (base transceiver system), an access point (AP), a network (5G network), an AI (artificial intelligence) system / module, an RSU (roadside unit), a robot, a drone (UAV: unmanned aerial vehicle), an AR (augmented reality) device, a VR (virtual reality) device, etc. In addition, the terminal can be fixed as well as mobile, and can be replaced with terms such as a UE (user equipment), a MS (mobile station), a UT (user terminal), a MSS (mobile subscriber station), a SS (subscriber station), an AMS (advanced mobile station), a WT (wireless terminal), an MTC (machine type communication) device, an M2M (machine-to-machine) device, a D2D (device-to-device) device, a vehicle, an RSU (roadside unit), a robot, an AI (artificial intelligence) module, a drone (UAV: unmanned aerial vehicle), an AR (augmented reality) device, a VR (virtual reality) device, etc.

[0044] The following description can be used for various radio access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, and the like. CDMA can be implemented by radio technology such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented by radio technology such as GSM (Global System for Mobile Communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented by radio technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), and the like. UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (Third Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) using E-UTRA, and LTE-A (Advanced) / LTE-A pro is a high-speed version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is a high-speed version of 3GPP LTE / LTE-A / LTE-A pro.

[0045] For the sake of clarity, the description is made based on a 3GPP communication system (e.g., LTE-A, NR), but the technical idea of the disclosure is not limited thereto. LTE means a technology after Release 8 of 3GPP TS (Technical Specification) 36.xxx. Specifically, LTE technology in or after Release of 3GPP TS 36.xxx is referred to as LTE-A, and LTE technology in or after Release 13 of 3GPP TS 36.xxx is referred to as LTE-A pro. 3GPP NR means a technology in or after Release of TS 38.xxx. LTE / NR can be referred to as a 3GPP system. "xxx" means a detailed number of a standard document. LTE / NR can be generally referred to as a 3GPP system. For background technologies, terms, abbreviations, etc. used to describe the disclosure, matters described in standard documents disclosed before the disclosure can be referred to. For example, the following documents can be referred to.

[0046] For 3GPP LTE, TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (Overall Description), TS 36.331 (Radio Resource Control) can be referred to.

[0047] For 3GPP NR, reference can be made to TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (NR and NG-RAN (New Generation-Radio Access Network) overall description), TS 38.331 (Radio Resource Control protocol specification).

[0048] Abbreviations of terms that can be used in this disclosure are defined as follows.

[0049] - BM: Beam Management

[0050] - CQI: Channel Quality Indicator

[0051] - CRI: Channel State Information-Reference Signal Resource Indicator

[0052] - CSI: Channel State Information

[0053] - CSI-IM: Channel State Information-Interference Measurement

[0054] - CSI-RS: Channel State Information-Reference Signal

[0055] - DMRS: Demodulation Reference Signal

[0056] - FDM: Frequency Division Multiplexing

[0057] - FFT: Fast Fourier Transform

[0058] - IFDMA: Interleaved Frequency Division Multiple Access

[0059] - IFFT: Inverse Fast Fourier Transform

[0060] - L1-RSRP: Layer 1 Reference Signal Received Power

[0061] - L1-RSRQ: Layer 1 Reference Signal Received Quality

[0062] - MAC: Medium Access Control

[0063] - NZP: Non-Zero Power

[0064] - OFDM: Orthogonal Frequency Division Multiplexing

[0065] - PDCCH: Physical Downlink Control Channel

[0066] - PDSCH: Physical Downlink Shared Channel

[0067] - PMI: Precoding Matrix Indicator

[0068] - RE: Resource Element

[0069] - RI: Rank Indicator

[0070] - RRC: Radio Resource Control

[0071] - RSSI: Received Signal Strength Indicator

[0072] - Rx: Reception

[0073] - QCL: Quasi Co-Location

[0074] - SINR: Signal to Interference Noise Ratio

[0075] - SSB (or SS / PBCH Block): Synchronization Signal Block (including PSS (Primary Synchronization Signal), SSS (Secondary Synchronization Signal), and PBCH (Physical Broadcast Channel))

[0076] - TDM: Time Division Multiplexing

[0077] - TRP: Transmission and Reception Point

[0078] - TRS: Tracking Reference Signal

[0079] - Tx: Transmission

[0080] - UE: User Equipment

[0081] - ZP: Zero Power

[0082] Overall system

[0083] As more communication devices require higher capacity, there has been a demand for improved mobile broadband communication compared to existing radio access technologies (RATs). In addition, massive MTC (Machine Type Communication) that provides various services anytime anywhere by connecting multiple devices and things is also one of the main issues to be considered in the next-generation communication. In addition, communication system design considering services / terminals sensitive to reliability and latency is also discussed. Therefore, the introduction of the next-generation RAT considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (ultra-reliable and low-latency communication), etc. is discussed, and for convenience, the corresponding technology is referred to as NR in the present disclosure. NR is an expression indicating an example of a 5G RAT.

[0084] A new RAT system including the NR uses an OFDM transmission method or a transmission method similar thereto. The new RAT system can follow OFDM parameters different from those of the LTE. Alternatively, the new RAT system follows the parameters of the existing LTE / LTE-A as they are, but can support a wider system bandwidth (for example, 100 MHz). Alternatively, one cell can support multiple numerologies. In other words, terminals operating according to different numerologies can coexist in one cell.

[0085] A numerology corresponds to one subcarrier spacing in a frequency domain. Different numerologies can be defined as a reference subcarrier spacing is scaled by an integer N.

[0086] FIG. 1 A structure of a wireless communication system to which the disclosure can be applied is exemplified.

[0087] Referring to FIG. 1 , the NG-RAN is configured with gNBs providing a control plane (RRC) protocol end for NG-RA (NG Radio Access) user plane (i.e., new AS (Access Stratum) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and UEs. The gNBs are interconnected through the Xn interface. Further, the gNBs are connected to the NGC (New Generation Core) through the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Function) through the N2 interface, and to the UPF (User Plane Function) through the N3 interface.

[0088] FIG. 2 A frame structure in a wireless communication system to which the disclosure can be applied is exemplified.

[0089] The NR system can support multiple numerologies. Here, a numerology can be defined by a subcarrier spacing and a cyclic prefix (CP) overhead. Here, multiple subcarrier spacings can be derived by scaling a basic (reference) subcarrier spacing by an integer N (or, μ). Further, although it is assumed that a very low subcarrier spacing is not used in a very high carrier frequency, a numerology to be used can be selected independently of a frequency band. Further, various frame structures according to multiple numerologies can be supported in the NR system.

[0090] Hereinafter, OFDM numerologies and frame structures that can be considered in the NR system will be described. Multiple OFDM numerologies supported in the NR system can be defined as in Table 1 below.

[0091] [Table 1]

[0092]

[0093] NR supports multiple numerologies (or subcarrier spacings (SCSs)) for supporting various 5G services. For example, when the SCS is 15 kHz, wide areas of legacy cellular bands are supported; and when the SCS is 30 kHz / 60 kHz, dense cities, lower latency, and wider carrier bandwidths are supported; and when the SCS is 60 kHz or more, bandwidths exceeding 24.25 GHz are supported to overcome phase noise. NR bands are defined as two types (FR1, FR2) of frequency ranges. FR1, FR2 can be configured as in Table 2 below. In addition, FR2 can mean millimeter wave (mmW).

[0094] [Table 2]

[0095]

[0096]

[0097] [Table 3]

[0098]

[0099] [Table 4]

[0100]

[0101] FIG. 2 is an example of μ = 2 (SCS of 60 kHz), see Table 3, 1 subframe can include 4 slots. As shown in FIG. 2 1 subframe = {1, 2, 4} is an example, the number of slots that can be included in 1 subframe is defined as in Table 3 or Table 4. In addition, a mini-slot can include 2, 4, or 7 symbols or more or less symbols. With respect to physical resources in the NR system, an antenna port, a resource grid, a resource element, a resource block, a carrier part, etc. can be considered. Hereinafter, the physical resources that can be considered in the NR system will be described in detail. First, with respect to the antenna port, the antenna port is defined such that a channel carrying a symbol in the antenna port can be inferred from a channel carrying other symbols in the same antenna port. When a large-scale property of a channel in which a symbol in one antenna port is carried can be inferred from a channel in which a symbol of another antenna port is carried, it can be said that 2 antenna ports are in a QC / QCL (Quasi Co-Location or Quasi Co-located) relationship. In this case, the large-scale property includes at least one of a delay spread, a Doppler spread, a frequency shift, an average received power, a received timing. FIG. 3 A resource grid in a wireless communication system to which the present disclosure is applicable is exemplified.

[0102] Referring to FIG. 3 , a resource grid is exemplarily described as being configured with N RB μ N scRB one subcarrier, and one subframe is configured with 14·2 μ OFDM symbols, but is not limited thereto. In the NR system, a transmitted signal is described by one or more resource grids of N μ N symb （μ） OFDM symbols and configured with N RB μ N sc RB subcarriers. Here, N RB μ ≤N RB max,μ . N RB max,μ denotes the maximum transmission bandwidth, which can be different between uplink and downlink and between numerologies. In this case, one resource grid can be configured per μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element and is uniquely identified by the index pair (k, l'). Here, k = 0,..., N RB μ N sc RB - 1 is an index in the frequency domain, and l' = 0,..., 2 μ N symb （μ） - 1 refers to a symbol position in a subframe. When referring to a resource element in a slot, the index pair (k, l) is used.

[0103] Here, l = 0,..., N symb μ - 1. The resource element (k, l') for μ and antenna port p corresponds to a complex value a k,l' （p,μ） When there is no risk of confusion or when a specific antenna port or numerology is not specified, the index p and μ can be dropped, and then the complex value can be ak,l' (p) or ak,l'. In addition, a resource block (RB) is defined as N sc RB = 12 contiguous subcarriers in the frequency domain.

[0104] A point plays a role of a common reference point of a resource block grid and is obtained as follows.

[0105] - offsetToPointA of a primary cell (PCell) downlink denotes a frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping with an SS / PBCH block used by a terminal for initial cell selection. It is expressed in units of resource blocks assuming a subcarrier spacing of 15 kHz for FR1 and 60 kHz for FR2.

[0106] - absoluteFrequencyPointA represents the frequency position of point A, expressed in ARFCN (absolute radio frequency channel number).

[0107] For a subcarrier spacing configuration μ, the common resource blocks are numbered upwards from 0 in the frequency domain. The center of subcarrier 0 of common resource block 0 for subcarrier spacing configuration μ is the same as "point A". The common resource block number n for subcarrier spacing configuration μ in the frequency domain is given by the following equation 1. CRB μ The relationship between the common resource block number n and the resource element (k, l) is given by the following equation 1.

[0108] [Equation 1]

[0109]

[0110] In equation 1, k is defined with respect to point A such that k = 0 corresponds to the subcarrier centered at point A. The physical resource blocks are numbered from 0 to nBWP-1 in the bandwidth part (BWP) and i is the number of the BWP. The physical resource block n PRB and the common resource block n CRB are related by the following equation 2.

[0111] [Equation 2]

[0112]

[0113] is the common resource block where the BWP starts with respect to the common resource block 0.

[0114] FIG. 4 A wireless communication system in which the present disclosure can be applied is exemplified. Also, FIG. 5 A slot structure in a wireless communication system in which the present disclosure can be applied is exemplified.

[0115] Referring to FIG. 4 and FIG. 5 , a slot includes a plurality of symbols in the time domain. For example, 1 slot includes 7 symbols for a normal CP, but 1 slot includes 6 symbols for an extended CP.

[0116] A carrier includes multiple subcarriers in a frequency domain. A RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in a frequency domain. A BWP (Bandwidth Part) is defined as multiple consecutive (physical) resource blocks in a frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through an activated BWP, and only one BWP can be activated for one terminal. In a resource grid, each element is referred to as a resource element (RE) and one complex symbol can be mapped.

[0117] In an NR system, each component carrier (CC) can support up to 400 MHz. If a terminal operating in such a wideband CC always operates to turn on a radio frequency (RF) chip for the entire CC, terminal battery consumption can increase. Alternatively, when considering multiple application cases operating in one wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing, etc.) can be supported in each frequency band in the corresponding CC. Alternatively, each terminal can have different capabilities for a maximum bandwidth. In consideration of this, a base station can instruct a terminal to operate only in a partial bandwidth, rather than in the full bandwidth of a wideband CC, and for convenience, the corresponding partial bandwidth is defined as a bandwidth part (BWP). A BWP can be configured with consecutive RBs on a frequency axis and can correspond to one numerology (e.g., subcarrier spacing, CP length, slot / min-slot duration).

[0118] In addition, a base station can configure multiple BWPs even in one CC configured to a terminal. For example, a BWP occupying a relatively small frequency domain can be configured in a PDCCH monitoring slot, and a PDSCH indicated by a PDCCH can be scheduled in a larger BWP. Alternatively, when UEs are congested in a specific BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, considering frequency-domain inter-cell interference cancellation between neighboring cells, etc., some middle spectrum of the full bandwidth can be excluded, and BWPs on both edges can be configured in the same slot. In other words, a base station can configure at least one DL / UL BWP to a terminal associated with a wideband CC. The base station can activate at least one of the configured DL / UL BWPs at a specific time (through L1 signaling or a MAC CE (Control Element) or RRC signaling, etc.).

[0119] Further, the base station can indicate (through L1 signaling or MAC CE or RRC signaling, etc.) to switch to other configured DL / UL BWP. Alternatively, based on a timer, when the timer value expires, it can switch to the determined DL / UL BWP. Here, the activated DL / UL BWP is defined as the active DL / UL BWP. However, before the terminal performs the initial access procedure or sets up the RRC connection, it can not receive the configuration on the DL / UL BWP, so the DL / UL BWP assumed by the terminal in these cases is defined as the initial active DL / UL BWP.

[0120] FIG. 6 A physical channel used in a wireless communication system to which the disclosure can be applied and a general signal transmission and reception method using the same are exemplified.

[0121] In a wireless communication system, a terminal receives information from a base station through a downlink and transmits information to the base station through an uplink. The information transmitted and received by the base station and the terminal includes data and various control information, and there are various physical channels according to the type / use of the information they transmit and receive.

[0122] When the terminal is turned on or newly enters a cell, it performs an initial cell search including synchronization with a base station, etc. (S601). For the initial cell search, the terminal can synchronize with the base station by receiving a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station and acquire information such as a cell identifier (ID), etc. Then, the terminal can acquire broadcast information in the cell by receiving a physical broadcast channel (PBCH) from the base station. Meanwhile, the terminal can check a downlink channel state by receiving a downlink reference signal (DL RS) in the initial cell search stage.

[0123] The terminal that completes the initial cell search can acquire more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S602).

[0124] Further, when the terminal first accesses the base station or does not have a radio resource for signal transmission, it can perform a random access (RACH) procedure to the base station (S603 to S606). For the random access procedure, the terminal can transmit a specific sequence as a preamble through a physical random access channel (PRACH) (S603 and S605), and can receive a response message to the preamble through a PDCCH and a corresponding PDSCH (S604 and S606). A contention-based RACH can additionally perform a contention resolution procedure.

[0125] The terminal which performs the above-described procedure later can perform PDCCH / PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel) / PUCCH (Physical Uplink Control Channel) transmission (S608) as a general uplink / downlink signal transmission procedure. Specifically, the terminal receives downlink control information (DCI) through the PDCCH. Here, the DCI includes control information such as resource allocation information for the terminal, and the format varies according to its use purpose.

[0126] Meanwhile, control information transmitted by the terminal to the base station through the uplink or received by the terminal from the base station includes a downlink / uplink ACK / NACK (acknowledgement / non-acknowledgement) signal, a CQI (Channel Quality Indicator), a PMI (Precoding Matrix Indicator), an RI (Rank Indicator), etc. For the 3GPP LTE system, the terminal can transmit the above-described control information of the CQI / PMI / RI, etc. through the PUSCH and / or the PUCCH.

[0127] Table 5 represents an example of a DCI format in the NR system.

[0128] [Table 5]

[0129]

[0130] Referring to Table 5, the DCI formats 0_0, 0_1, and 0_2 can include resource information (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to a transport block (TB) (e.g., MCS (Modulation and Coding Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), information related to HARQ (Hybrid-Automatic Repeat and Request) (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS (Demodulation Reference Signal) sequence initialization information, antenna port, CSI (Channel State Information) request, etc.), power control information related to scheduling of PUSCH (e.g., PUSCH power control, etc.), and control information included in each DCI format can be predefined. The DCI format 0_0 is used to schedule PUSCH in one cell. Information included in the DCI format 0_0 is CRC (Cyclic Redundancy Check) scrambled by C-RNTI (Cell Radio Network Temporary Identifier) or CS-RNTI (Configured Scheduling RNTI) or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and is transmitted. The DCI format 0_1 is used to indicate scheduling of one or more PUSCHs or to configure a terminal with grant (CG) downlink feedback information in one cell. Information included in the DCI format 0_1 is scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI (Semi-Persistent CSI RNTI) or MCS-C-RNTI and is transmitted.

[0131] The DCI format 0_2 is used to schedule PUSCH in one cell. Information included in the DCI format 0_2 is scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI and is transmitted.

[0132] Next, the DCI formats 1_0, 1_1, and 1_2 can include resource information (e.g., frequency resource allocation, time resource allocation, VRB (Virtual Resource Block)-PRB (Physical Resource Block) mapping, etc.), information related to a transport block (TB) (e.g., MCS, NDI, RV, etc.), information related to HARQ (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., antenna port, TCI (Transmission Configuration Indicator), SRS (Sounding Reference Signal) request, etc.), information related to PUCCH with respect to scheduling of PDSCH (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format can be predefined.

[0133] The DCI format 1_0 is used for scheduling of PDSCH in one DL cell. The information included in the DCI format 1_0 is CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI and transmitted.

[0134] The DCI format 1_1 is used for scheduling of PDSCH in one cell. The information included in the DCI format 1_1 is CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI and transmitted.

[0135] The DCI format 1_2 is used for scheduling of PDSCH in one cell. The information included in the DCI format 1_2 is CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI and transmitted.

[0136] (e) Downlink transmission and reception method of RedCap UE

[0137] As described above, services considering eMBB, URLLC, and massive Internet of Things (mIoT) are being provided on a wireless communication system (e.g., NR, etc.). For example, a mixed service considering eMBB, URLLC, and mIoT can be provided on a wireless communication system. Here, mIoT requires optimization of power consumption rather than high performance (e.g., high transmission speed, etc.), such as carrier aggregation.

[0138] With recent widespread use of smart factories and / or wearable devices, the demand for a new UE type considering low power and URLLC is increasing. Accordingly, a reduced capability (RedCap) UE (i.e., R17 RedCap UE) is introduced in 3GPP NR Release 17. The RedCap UE can perform communication using a frequency resource on a narrow spectrum or narrow bandwidth. For example, the RedCap UE can reduce power consumption and cost by utilizing a bandwidth of up to 20 MHz or 5 MHz instead of the existing 100 MHz bandwidth.

[0139] Thereafter, an eRedCap UE is introduced in 3GPP NR Release 18. However, in the case of the eRedCap UE, unicast PDSCH and / or PUSCH (i.e., C-RNTI-based PDSCH and / or PUSCH) can be allocated within a bandwidth of up to 5 MHz. That is, a PRB of unicast PUSCH / PDSCH corresponding to a bandwidth of up to 5 MHz can be allocated to the eRedCap UE. In this case, the unicast PUSCH / PDSCH can be indicated / allocated to the eRedCap UE through an FDRA (frequency domain resource assignment) field of DCI, etc.

[0140] In addition, for the eRedCap UE, various RNTI-based channels related to paging, system information blocks (SIBs), RACH, etc. can be allocated within a 20 MHz bandwidth. That is, PRBs of various RNTI-based channels corresponding to the maximum bandwidth of 20 MHz can be allocated to the eRedCap UE (the same as the RedCap UE).

[0141] The eRedCap UE can process data (e.g., PRBs) corresponding to a bandwidth of up to 5 MHz within a unit slot. If a channel exceeding the 5 MHz bandwidth is scheduled / allocated, the eRedCap UE can need an additional processing time margin. In the case of a unicast channel, scheduling can be performed for each slot, and thus, PRBs corresponding to the maximum bandwidth (e.g., 5 MHz) can be allocated to the eRedCap UE (e.g., 25 PRBs when the SCS is 15 kHz, or 12 PRBs when the SCS is 30 kHz).

[0142] In addition, for the RedCap UE (i.e., the R17 RedCap UE introduced in 3GPP Release 17), a unicast channel can be scheduled over a bandwidth of up to 20 MHz, and the maximum data rate (data rate) can be 500 Mbps. For the eRedCap UE (i.e., the RedCap UE introduced in 3GPP Release 18), a unicast channel can be scheduled over a bandwidth of up to 20 MHz or a bandwidth of 5 MHz, and the maximum data rate (data rate) can be 10 Mbps. Various embodiments of the disclosure can be applied to the eRedCap UE in which a unicast channel can be scheduled over a bandwidth of up to 5 MHz. However, this is only one embodiment, and various embodiments of the disclosure can also be applied to the R17 RedCap terminal or the eRedCap UE in which a unicast channel can be scheduled over a bandwidth of 20 MHz.

[0143] The disclosure relates to a method for efficiently receiving a downlink (DL) channel (e.g., a group common channel, etc.) related to a multicast broadcast service (MBS) by the above-described (e)RedCap UE (i.e., a UE using a BWP of up to 20 MHz). Here, the MBS-related DL channel can include a DL channel (e.g., a PDSCH, etc.) scheduled by a DCI scrambled with an MCCH (MBS control channel)-RNTI, a G (group)-RNTI, or a G (group)-CS-RNTI with a CRC. In describing the disclosure, the MBS channel can be collectively referred to as an MBS-related (DL / UL) channel.

[0144] Unlike a unicast channel, an MBS-related channel can be transmitted to multiple terminals at the same time. When an eRedCap UE receives an MBS-related channel within a 5 MHz bandwidth range, this can not be efficient from the perspective of other types of UEs (e.g., R17 RedCap UEs) that also receive the MBS-related channel. When an eRedCap UE can receive / use the same 20 MHz bandwidth as other common channels, the possibility of sharing channels with other types of UEs increases, and thus efficiency can be improved from the perspective of network operation.

[0145] An MBS channel can have SIB broadcast and unicast properties of a common channel. Accordingly, in describing the present disclosure, the MBS channel will be described by dividing the MBS channel into a broadcast / broadcast channel and a multicast / multicast channel (in terms of bandwidth). That is, when an MBS channel is transmitted to an eRedCap UE, a restriction can be imposed on the bandwidth on which the MBS channel is transmitted. If the bandwidth on which the MBS channel is transmitted is not restricted, an additional margin can be imposed on the processing time of the MBS channel.

[0146] In describing the present disclosure, the fact that an eRedCap terminal drops a certain channel can mean that the certain channel is not skipped or that the certain channel is not expected / required to be decoded. Furthermore, for an eRedCap UE, the fact that PRBs of a bandwidth up to 20 MHz can be allocated / scheduled can mean that PRBs exceeding a certain bandwidth (e.g., 5 MHz) can be allocated / scheduled.

[0147] As an example of the present disclosure, if an MBS channel is a broadcast channel, similar to an SIB, an eRedCap UE can be allocated / scheduled for the MBS channel within a bandwidth up to 20 MHz. Here, the broadcast channel can be scheduled by a DCI CRC scrambled by an MCC-RNTI or a G-RNTI. Since an eRedCap UE can receive an SIB within a bandwidth up to 20 MHz, the eRedCap UE can also be allocated / scheduled for a broadcast channel within a bandwidth up to 20 MHz, which is not applied to a HARQ procedure (i.e., an ACK / NACK response transmission / reception procedure, etc.).

[0148] In another example of the disclosure, when the MBS channel is a multicast channel, the multicast channel can be scheduled by a DCI (e.g., DCI format 4_1 or 4_2) CRC scrambled by a G-RNTI or G-CS-RNTI. In the case of the multicast channel, it can also be scheduled / allocated within a bandwidth of up to 20 MHz like the broadcast channel. However, when the HARQ procedure for the multicast channel is applied (i.e., when the ACK / NACK response transmission / reception procedure is applied), an additional processing time (e.g., x ms or a value of a symbol length unit of OFDM) can be applied to the processing time predefined in Table 6 (PDSCH processing time for PDSCH processing capability 1) and Table 7 (PDSCH processing time for PDSCH processing capability 2).

[0149] [Table 6]

[0150]

[0151] [Table 7]

[0152]

[0153] In addition, if ACK / NACK information transmission is not configured for the MBS-based multicast channel, 20 MHz can be optionally used.

[0154] In addition, in the above-described method, there can be a method for configuring a HARQ feedback mode for multicast. For example, RRC signaling for configuring an MBS-based HARQ mode can be transmitted to an eRedCap UE, and the RRC signaling can include the information disclosed in Table 8 below.

[0155] [Table 8]

[0156]

[0157] As an example of the disclosure, an enabler of HARQ can be indicated / configured via DCI or / and RRC signaling. When the enabler of HARQ is indicated via DCI, an ACK / NACK mode or a NACK-only mode can be indicated. As another example, an operation / mode related to HARQ-ACK feedback can be indicated via a HARQ-ACK feedback indication enabler field included in DCI format 4_1. When "harq-FeedbackOptionMulticast" indicates "dci-enabler", the HARQ-ACK feedback indication enabler field can be set to 1 bit. When the HARQ-ACK feedback indication enabler field value is set to 1, HARQ-ACK feedback is indicated to be enabled, and when the HARQ-ACK feedback indication enabler field value is set to 0, HARQ-ACK feedback can be indicated to be disabled. When RRC signaling "Harq-FeedbackEnablerMulticast-r17" is not transmitted, HARQ feedback can always be disabled. "Harq-FeedbackEnablerMulticast" can indicate whether the UE should provide HARQ feedback for MBS multicast. The "dci-enabler" value configured by "Harq-FeedbackEnablerMulticast" can mean whether the terminal should provide HARQ feedback for MBS multicast. The disclosure will explain the case where HARQ-related operations are controlled via RRC or DCI when HARQ feedback is disabled.

[0158] In addition, the disclosure can be applied to a terminal that cannot process the entire bandwidth of RF but has the number of PRBs that can be processed in the BB baseband (limited to the number of PRBs corresponding to a 5 MHz bandwidth).

[0159] Further, the disclosure can be applied to two UEs that simultaneously process two channels when the two channels are scheduled in a single slot, or to a UE that cannot process either channel. Processing either channel can be more service-oriented than not processing both channels. Accordingly, the disclosure describes a method for prioritizing and simultaneously receiving two channels.

[0160] As an example of the disclosure, an eRedCap UE can not expect multiple channels to be simultaneously scheduled in the same slot. The simultaneous scheduling / reception of multiple channels can include a case where the multiple channels overlap or do not overlap with respect to OFDM symbols. In addition, a PDSCH scheduled by an SI-RNTI can be based on acquisition of an SI triggered by a P-RNTI.

[0161] FIG. 7 FIG. 1 is a diagram illustrating a process in which a terminal performs communication according to an embodiment of the disclosure. FIG. 7 and FIG. 8The terminal can be, but is not limited to, an enhanced reduced capability (eRedCap) UE (i.e., a UE supporting an R18 redCap UE). FIG. 7 The UE can include a RedCap UE or a general UE.

[0162] The UE can receive, from the base station, a first downlink channel and a second downlink channel in a first slot (S710).

[0163] Prior to step S710, the UE can transmit, to the base station, capability information indicating that it supports reception of the first downlink channel and the second downlink channel that are frequency division multiplexed (FDMed) in a single slot.

[0164] Accordingly, the base station can identify that the UE can receive the first downlink channel and the second downlink channel that are FDMed in a single slot. The base station can transmit, to the UE, information for scheduling the first downlink channel and the second downlink channel in the first slot. Further, the base station can transmit, to the UE, the first downlink channel and the second downlink channel in the first slot.

[0165] As an example of the present disclosure, the first downlink channel can be a unicast physical downlink shared channel (PDSCH), and the second downlink channel can be a multicast PDSCH or a broadcast PDSCH.

[0166] Also, the first downlink channel can be scheduled by first downlink control information (DCI) that is CRC scrambled by a C (cell)-RNTI or a CS (configured scheduling)-RNTI, and the second downlink channel can be scheduled by second DCI that is CRC scrambled by a G (group)-RNTI or a MCCH (MBS control channel)-RNTI.

[0167] That is, the information for scheduling the first downlink channel transmitted by the base station can be the first DCI, and the information for scheduling the second downlink channel can be the second DCI. However, this is only an example, and the (repeated) transmission of the first downlink channel and / or the second downlink channel can be configured / indicated by a MAC CE or RRC signaling.

[0168] Here, the first downlink channel and the second downlink channel can partially or completely overlap in the time domain. Also, the PRBs allocated to each of the first downlink and the second downlink can not overlap with each other (in the frequency domain).

[0169] Based on the number of PRBs allocated for each of the first downlink channel and the second downlink channel being less than or equal to a first threshold value, the UE can decode the first downlink channel and the second downlink channel (S720).

[0170] For example, based on a subcarrier spacing (SCS) being set to 15 kHz, the first threshold can be 25, and based on the SCS being set to 30 kHz, the first threshold can be 12.

[0171] For example, based on a number of PRBs allocated for each of the first downlink channel and the second downlink channel exceeding the first threshold, the UE can skip decoding of one of the first downlink channel and the second downlink channel.

[0172] FIG. 7 The method described in the example of FIG. 10 can be performed by FIG. 16 The first device (100) and the second device (200) of FIG. 10 can be implemented as FIG. 16 The first device (100) of FIG. 10 can be implemented as a UE, and the second device (200) of FIG. 10 can be implemented as a base station. For example, FIG. 16 The one or more processors (102) of the first device (100) of FIG. 10 can receive, from the second device (200), the first downlink channel and the second downlink channel in the first slot through the one or more transceivers. That is, the one or more processors (202) of the second device (200) can transmit, to the first device (100), the first downlink channel and the second downlink channel through the one or more transceivers (206). Based on a number of PRBs allocated for each of the first downlink channel and the second downlink channel being less than or equal to the first threshold, the one or more processors (102) can decode the first downlink channel and the second downlink channel.

[0173] Further, the one or more memories (104) of the first device (100) can store instructions to, when executed by the one or more processors (102), perform the method described in the example of FIG. 10 or the example described below. FIG. 8 The one or more memories (104) of the first device (100) can store instructions to, when executed by the one or more processors (102), perform the method described in the example of FIG. 10 or the example described below.

[0174] FIG. 8 FIG. 10 is a diagram for explaining a process in which a UE performs communication according to an embodiment of the disclosure.

[0175] The UE can receive, from the base station, the first downlink channel in a slot n (S810), where n is an integer greater than or equal to 0.

[0176] That is, the UE can receive, from the base station, information for scheduling the first downlink channel in the slot n.

[0177] Here, the first downlink channel can be at least one of a unicast channel, a multicast channel, or a broadcast channel. For example, the first downlink channel can include a PDSCH scheduled by a DCI CRC scrambled by an MCCH-RNTI or a G-RNTI.

[0178] The UE can process reception of the first downlink channel if the number of PRBs allocated for the first downlink channel is less than or equal to the second threshold (S820).

[0179] In other words, the UE can process / decode the scheduling of the first downlink channel if the number of PRBs allocated to the first downlink channel is less than or equal to the second threshold.

[0180] Here, the second threshold can be determined differently depending on the SCS value, similar to FIG. 7 The first threshold. For example, if the SCS is set to 15 kHz, the second threshold could be 25. And, if the SCS is set to 30 kHz, the first threshold could be 12.

[0181] For example, if the number of PRBs allocated for the first downlink channel exceeds the second threshold, and the reception of the first downlink channel is a repeated reception or the second downlink channel is received in time slot n+1, then the UE may not process the reception of the first downlink channel. In other words, if the number of PRBs allocated for the first downlink channel exceeds the second threshold, and the reception of the first downlink channel is a repeated reception or the second downlink channel is received in time slot n+1, then the UE may not be required to process the first downlink channel received in time slot n.

[0182] FIG. 9 The methods described in the examples can be derived from... FIG. 16 The first device (100) and the second device (200) perform the operation. That is, the UE can be implemented as... FIG. 16 The first device (100) and the base station can be implemented as the second device (200). For example, FIG. 16 One or more processors (102) of the first device (100) may receive the first downlink channel from the second device (200) via one or more transceivers (106) in time slot n (n is an integer greater than or equal to 0). That is, one or more processors (202) of the second device (200) may transmit the first downlink channel to the first device (100) via one or more transceivers (206) in time slot n (n is an integer greater than or equal to 0). Based on the fact that the number of PRBs allocated for the first downlink channel is less than or equal to a second threshold, one or more processors (102) may process the reception of the first downlink channel.

[0183] Furthermore, one or more memories (104) of the first device (100) may store information for execution by one or more processors (102) in order to perform the operation. FIG. 9commands of the methods described in the examples above or in the examples described below.

[0184] Hereinafter, various methods for a UE (e.g., eRedCap UE) to receive an MBS channel in a narrow band are described.

[0185] Embodiment 1

[0186] Embodiment 1 relates to a method of operating bandwidth differently according to the form of HARQ feedback for multicast.

[0187] In the case of broadcast (or broadcast channel / transmission), since there is no HARQ feedback, the procedure can be performed similarly to the SIB or paging information transmission / reception procedure. However, in the case of multicast, three HARQ feedback modes (e.g., ACK / NACK mode, only NACK mode, NO HARQ mode) can be configured / operated.

[0188] Here, the ACK / NACK mode also applies to the basic unicast transmission and reception procedure, and the NO HARQ mode can be a general term for a procedure in which ACK / NACK transmission is not performed, such as the SIB or paging information transmission and reception procedure. The only NACK mode can apply to the MBS-based multicast channel transmission and reception procedure. The only NACK mode is a general term for a mode in which feedback information is not transmitted in the ACK case and NACK-based feedback is transmitted in the NACK case.

[0189] As described above, in the case of broadcast transmission without HARQ-ACK / NACK transmission establishment, no additional relaxation procedure of processing time is required, so a bandwidth of up to 20 MHz can be used. However, in the case of the ACK / NACK or only NACK mode, when a 20 MHz bandwidth is used, an additional relaxation time can be required. Therefore, in Embodiment 1, a method of bandwidth operation according to the form of HARQ feedback during multicast channel transmission and reception will be described.

[0190] Embodiment 1-1

[0191] Embodiment 1-1 relates to a method of operating multicast (i.e., operating the transmission and reception procedure of the multicast channel) within a bandwidth of up to 20 MHz when the NO HARQ mode is applied.

[0192] When the NO HARQ mode is configured via higher layer signaling (e.g., RRC signaling) or the real-time HARQ mode is indicated as NO or dynamic in DCI format 4_2, the multicast operation can be performed within a bandwidth of up to 20 MHz. Additionally or alternatively, when the NO HARQ mode is indicated via DCI or the HARQ disable mode is indicated via RRC signaling, the multicast operation can be performed within a bandwidth of up to 20 MHz.

[0193] Embodiment 1-2

[0194] Embodiment 1-2 relates to a method in which the multicast channel is limited to being allocated / scheduled within a 5 MHz bandwidth when the ACK / NACK mode or the NACK only mode is indicated / configured. That is, when the ACK / NACK mode or the NACK only mode is indicated / configured, the multicast channel can be allocated / scheduled as many times as the number of PRBs corresponding to the 5 MHz bandwidth.

[0195] When the HARQ feedback is established via higher layer signaling or the real-time HARQ mode is indicated as NO or dynamically indicated in DCI format 4_2, the multicast channel can be limited to being allocated / scheduled within a 5 MHz bandwidth. Additionally or alternatively, when the HARQ feedback is enabled via DCI or the NO HARQ mode is indicated via DCI, the multicast channel can be allocated / scheduled for a number of PRBs corresponding to the 5 MHz bandwidth.

[0196] As an example of the present disclosure, the multicast channel transmission and reception can be performed within a bandwidth of up to 20 MHz only when the NACK only mode is applied (e.g., when the NACK only mode is configured via RRC signaling), thereby improving operational flexibility.

[0197] Embodiments 1-1 and 1-2 can be utilized in the above-described three HARQ feedback modes, but an additional HARQ feedback mode can be utilized. For example, the multicast (i.e., the transmission and reception of the multicast channel) can be performed only in the RRC_inactive mode or the RRC_connected mode. For example, the multicast can be configured via RRC signaling to be applied only in the RRC_inactive mode or the RRC_connected mode.

[0198] Additionally or alternatively, embodiments 1-1 and 1-2 can be configured via RRC signaling to be used only when the UE type is an eRedCap UE. As another example, the ACK / NACK mode or the NACK only mode can be configured via RRC signaling to be applied only to the eRedCap UE.

[0199] That is, if the number of allocated PRBs indicated through the FDRA field of the PDCCH is less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, ACK / NACK-based or NACK-only-based transmission can be performed. If the number of allocated PRBs indicated through the FDRA field of the PDCCH is greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, HARQ feedback transmission can not be performed. In this case, the network can identify the non-transmission of HARQ feedback as ACK or NACK.

[0200] Embodiment 1-3

[0201] In one embodiment of the disclosure, when the number of PRBs scheduled in the multicast exceeds the number of PRBs corresponding to a 5 MHz bandwidth, it is processed in the NO HARQ mode, and when the number of PRBs scheduled in the multicast is less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, ACK or NACK can be transmitted.

[0202] The above-described embodiment is a new HARQ mode, and the new HARQ mode can be configured for an eRedCap UE via RRC signaling. When the ACK / NACK mode or the NACK-only mode is configured, the base station can configure a multicast channel having a number of PRBs greater than or equal to a 5 MHz bandwidth. In this case, if there is no HARQ feedback, the base station can identify it as NACK or ACK.

[0203] As another example thereof, when the NACK-only mode is configured, scheduling for the number of PRBs corresponding to a 20 MHz bandwidth can be allowed. Scheduling for the number of PRBs corresponding to a 20 MHz bandwidth can be allowed only when a PUCCH resource for NACK-only-based feedback transmission is configured or when the NACK-only mode is configured via RRC signaling.

[0204] Embodiment 1-3 relates to a method of performing ACK / NACK transmission (or NACK-only transmission) or not transmitting feedback according to the capability of the UE, rather than processing / determining HARQ feedback based on the number of PRBs corresponding to a specific bandwidth. That is, Embodiment 1-3 can be processed according to the UE implementation. Additionally or alternatively, when a specific number or more of PRBs are scheduled for an eRedCap UE, whether to transmit or receive feedback can be determined according to the UE capability.

[0205] Embodiment 1-4

[0206] In one embodiment of the disclosure, when MBS-related information is configured (i.e., when broadcast or multicast data / channels are transmitted and received), repetition transmission can be performed / applied only in a specific bandwidth (e.g., 5 MHz BWP in the case of an eRedCap UE). In this case, the repetition operation can be performed only in the specific bandwidth regardless of the presence or absence of HARQ feedback.

[0207] Embodiment 1-5

[0208] In one embodiment of the disclosure, for a narrowband UE (e.g., an eRedCap UE), it is assumed that the number of PRBs is greater than or equal to the number of PRBs corresponding to the bandwidth that can be processed in a single slot (e.g., the number of PRBs corresponding to a 5 MHz bandwidth in the case of an eRedCap UE) is scheduled. In this case, if feedback on the scheduling is required, it can not be desirable for the eRedCap UE to complete decoding within the PDSCH processing time, or it can not be necessary for the eRedCap UE to transmit feedback.

[0209] Embodiment 1-6

[0210] In one embodiment of the disclosure, when repetition transmission is performed, the HARQ feedback procedure can be omitted. In this case, when a multicast channel is transmitted and received, scheduling can be performed within a maximum bandwidth (e.g., up to 20 MHz for an eRedCap UE).

[0211] Embodiment 1-7

[0212] In one embodiment of the disclosure, it is assumed that the HARQ feedback mode for multicast PDSCH transmission is configured as an ACK / NACK mode or a NACK-only mode. In this case, if more PRBs than the number of PRBs corresponding to a specific bandwidth (e.g., up to 5 MHz for an eRedCap UE) are scheduled, the UE can transmit a PUCCH including NACK information to the base station.

[0213] Embodiment 1-8

[0214] In one embodiment of the disclosure, a multicast SPS PDSCH (i.e., SPS transmission) can be allocated / scheduled within a bandwidth of up to 5 MHz. The above-described operation can also be applied to a PDSCH scheduled by DCI with CRC scrambled by a G-CS-RNTI. As another example, the above-described operation can be applied until the SPS operation of the multicast SPS PDSCH is deactivated.

[0215] If the number of PRBs corresponding to a certain bandwidth is exceeded by the PRBs scheduled by the initial PDCCH, a problem in PDSCH reception can occur until the SPS operation is deactivated. Accordingly, the SPS transmission can be limited to be performed within the 5 MHz bandwidth.

[0216] For the SPS transmission, the activation or deactivation can be configured through RRC signaling rather than through PDDCH. In this case, since the number of PRBs can be configured through RRC signaling, HARQ feedback can be disabled for the 20 MHz bandwidth.

[0217] When the SPS transmission is activated or deactivated through DCI (e.g., DCI CRC scrambled by G-CS-RNTI), ACK / NACK transmission can be performed even if HARQ feedback is disabled for the first or last DCI. Meanwhile, when PRBs greater than the number of PRBs corresponding to a certain 5 MHz bandwidth are scheduled, ACK / NACK transmission can also be performed. In this case, when the base station indicates that the eRedCap UE has a sufficient K1 value (i.e., a time delay value from the time of transmitting the PDSCH until the time of transmitting the ACK / NACK) or cannot indicate an insufficient K1 value (i.e., when HARQ feedback transmission is difficult), the eRedCap UE can unconditionally transmit NACK (e.g., skip or drop the PDSCH transmission) or perform an operation according to the UE implementation. As another example, a specific K1 value x can be indicated / defined / configured, and the eRedCap UE can expect a K1 greater than or equal to x. If a K1 less than or equal to x is indicated, the eRedCap UE can transmit NACK (e.g., skip or drop the PDSCH transmission) or perform an action according to the UE implementation.

[0218] For example, in the case of G-RNTI, PRBs greater or less than the number of PRBs corresponding to a 5 MHz bandwidth can be scheduled according to whether HARQ feedback is enabled / disabled. In the case of G-CS-RNTI, PRBs less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth can be scheduled regardless of whether HARQ feedback is enabled / disabled.

[0219] Embodiment 1-8

[0220] In one embodiment of the disclosure, HARQ feedback disabling can be applied if RRC signaling related to HARQ feedback (e.g., "Harq-FeedbackEnablerMulticast-r17") is not transmitted to the UE. In this case, the multicast PDSCH can be scheduled on a BWP of up to 20 MHz. If the RRC signaling related to HARQ feedback is transmitted to the UE, the multicast PDSCH can be scheduled as many times as the number of PRBs based on the unicast-based UE processing (e.g., in the case of a RedCap UE, the number of PRBs corresponds to a 5 MHz bandwidth).

[0221] As an example of the disclosure, when a HARQ process ID is disabled, it can not be desirable for the UE (e.g., a non-RedCap UE) to receive another PDCCH carrying DCI scheduling a PDSCH or a set of slot-aggregated PDSCHs for a given HARQ process, or it can not be desirable for the UE to receive another PDSCH for a HARQ process starting from T proc,1 after the completion of the reception of the last PDSCH or slot-aggregated PDSCH for the given HARQ process without the PDCCH. That is, when consecutive PDCCHs are scheduled for the same HARQ process ID, it can not be desirable for the UE to receive a PDSCH or a PDCCH during T proc,1 Meanwhile, since the eRedCap UE can process PRBs corresponding to a 5 MHz bandwidth in a single slot, if more PRBs than the number of PRBs corresponding to a 5 MHz bandwidth (e.g., PRBs of a multicast channel) are scheduled, additional time can be applied to the eRedCap UE for PRB processing. Accordingly, the stability of the multicast PDSCH processing of the eRedCap UE can be improved.

[0222] Embodiment 1-9

[0223] In one embodiment of the disclosure, it is assumed that scheduling is continuously performed for a deactivated HARQ process ID. Although such scheduling is not desirable during time T proc1 , an additional processing time margin can be configured / indicated for the eRedCap UE when scheduling is performed for PRBs of 5 MHz or more (e.g., PRBs of a multicast channel).

[0224] For example, the processing time margin can be defined as 1 slot. That is, when PRBs corresponding to a 5 MHz bandwidth are allocated, the UE can not be expected to receive another PDCCH for "T proc1 + 1 slot" (e.g., 1 sm in 15 kHz SCS and 0.5 ms in 30 kHz SCS).

[0225] Embodiment 1-10

[0226] In one embodiment of the disclosure, when the same HARQ process ID is allocated to the disabled HARQ process ID, the number of PRBs of the multicast PDSCH can be limited to the number of PRBs corresponding to a 5 MHz bandwidth. Also, for other process IDs, the number of PRBs of the multicast PDSCH can be greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth.

[0227] Embodiment 1-11

[0228] In the case of eRedCap UE, in the case of the disabled HARQ process ID, it can be limited that the process ID is allocated consecutively.

[0229] Embodiment 2

[0230] Embodiment 2 relates to a processing method when an MBS channel is FDMed with another channel in the same slot but overlaps in the OFDM symbol. Embodiment 1 relates to a single MBS channel, and Embodiment 2 relates to the case where multiple channels are multiplexed in the frequency domain within the same slot and overlap in the OFDM symbol.

[0231] That is, Embodiment 2 relates to a processing method when multiple PDSCH channels overlap in the time domain, as shown in FIG. 9 Embodiment 2 can be limited to the RRC_Connected state, but is not limited thereto, and can also be applied to the RRC_Inactive state. In addition, Embodiment 2 relates to eRedCap UE capable of processing PDSCH that can be allocated to a 5 MHz bandwidth in one slot.

[0232] Embodiment 2-1

[0233] In one embodiment of the disclosure, when a broadcast (i.e., a broadcast-based channel) overlaps with another PDSCH, the UE can decode both the broadcast-based channel and the other PDSCH. In this case, the broadcast-based channel can be limited to being scheduled in a number of PRBs corresponding to a 5 MHz bandwidth.

[0234] For example, the broadcast-based channel can overlap with unicast PDSCH in a single slot. In this case, the broadcast-based channel can include a broadcast channel associated with MCCH-RNTI (i.e., MBS PDSCH) and / or MBS PDSCH. For example, the scheduling can be limited to only the number of PRBs corresponding to a 5 MHz bandwidth for the broadcast channel associated with the MCCH-RNTI, but is not limited thereto. In addition, the UE can transmit a UE capability related to the overlap handling between the broadcast-based channel and other channels to the base station.

[0235] As an example of the disclosure, if the broadcast-based channel and a PDSCH scheduled with DCI CRC scrambled with C-RNTI (hereinafter, PDSCH associated with C-RNTI) overlap in a single slot, the UE can discard the PDSCH associated with C-RNTI. As another example, if the broadcast-based channel and a PDSCH scheduled with DCI CRC scrambled with G-RNTI (hereinafter, PDSCH associated with G-RNTI) overlap in a single slot, the UE can discard the broadcast-based channel. However, this is only an implementation, and which channel to discard / skip if the broadcast-based channel and the PDSCH associated with C-RNTI / G-RNTI overlap in a single slot can be predefined or configured through an RRC signal.

[0236] Embodiment 2-2

[0237] Embodiment 2 relates to a UE processing method when a multicast channel overlaps with another PDSCH. In this case, the multicast channel can be scheduled to a plurality of PRBs corresponding to a 5 MHz bandwidth or less regardless of the HARQ feedback mode, but is not limited thereto. In this case, the UE can decode the entire channel, but an eRedCap UE can have difficulty in decoding the entire channel. Accordingly, Embodiment 2 can be limited to the conditions described below.

[0238] For example, when the HARQ feedback is configured for the multicast channel, the multicast channel can be scheduled for a plurality of PRBs corresponding to a bandwidth of up to 5 MHz. As another example, when the NO HARQ mode is configured via RRC signaling or the NO HARQ feedback mode is indicated via DCI, the multicast channel can be scheduled for a plurality of PRBs corresponding to a bandwidth of up to 20 MHz.

[0239] Embodiment 2 relates to a UE's handling operation when a multicast channel overlaps with a unicast PDSCH in the time domain in OFDM symbol units.

[0240] Further, when ACK / NACK mode or NACK only mode is configured for MBS PDSCH (e.g., multicast PDSCH), embodiment 2 can also be applied. In this case, feedback can not be transmitted from the UE only when ACK / NACK mode is configured. Depending on the UE implementation, feedback transmission can be performed differently, and depending on the UE capability, HARQ feedback can be transmitted or omitted.

[0241] Further, when HARQ feedback disabling is configured for multicast, embodiment 2 can be applied.

[0242] Embodiment 2-2-1

[0243] When a multicast channel overlaps with another PDSCH, the multicast channel can be scheduled to multiple PRBs less than or equal to 5 MHz bandwidth regardless of the HARQ feedback mode, but not limited thereto. In this case, the UE can not be expected to decode multiple channels scheduled in a slot, and can utilize the methods described below.

[0244] As an example of the present disclosure, for MBS based channels (e.g., broadcast based channels and / or multicast channels), the above scheduling can not be expected. For example, if HARQ disabling mode is configured for a multicast channel via RRC signaling, the UE can decode the multicast channel and another PDSCH channel overlapping with the multicast channel. As another example, if HARQ disabling mode is indicated for a multicast channel via DCI, the UE can not be expected for the scheduling.

[0245] In another example of the present disclosure, the UE can drop (or skip) MBS based channels (e.g., broadcast based channels or / and multicast channels). When repetition transmission is performed, the MBS based channels can be dropped (or skipped) on OFDM symbols in overlapping slots. For example, when ACK / NACK mode or NACK only mode is configured for a multicast channel, the UE can drop (or skip) the multicast channel. In another example, when HARQ disabling mode is configured for a multicast channel via RRC signaling (or DCI), the UE can decode the multicast channel and another PDSCH channel overlapping with the multicast channel. In another example, when HARQ deactivation mode is indicated for a multicast channel via DCI (or RRC signaling), the UE can drop (or skip) the multicast channel.

[0246] Additionally or alternatively, if the sum of the number of PRBs of each of the two channels (i.e., the multicast channel and another PDSCH channel overlapping with the multicast channel) exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the UE can drop the multicast channel. In this case, the two channels can be FDMed per OFDM symbol. However, if the sum of PRBs of each of the multicast channel and another PDSCH channel overlapping with the multicast channel is less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, the UE can decode both of the two channels.

[0247] Embodiment 2-3

[0248] In one embodiment of the disclosure, when the number of PRBs of the scheduled multicast PDSCH is greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth (e.g., when HARQ feedback is disabled), the UE can skip to not decode either of the multicast PDSCH or another channel overlapping with the multicast PDSCH. When the other channel overlapping with the multicast channel is a specific channel (e.g., unicast PDSCH or paging-triggered SI), the method according to Embodiment 2-3 can be used.

[0249] Embodiment 2-4

[0250] In one embodiment of the disclosure, when the multicast PDSCH is scheduled for a number of PRBs corresponding to a bandwidth of up to 5 MHz (e.g., when ACK / NACK mode or NACK only mode is configured), the UE can drop one of the multicast PDSCH or other channels overlapping with the multicast PDSCH without decoding it. When the other channel overlapping with the multicast channel is a specific channel (e.g., unicast PDSCH or paging-triggered SI), the method according to Embodiment 2-4 can be used.

[0251] Embodiment 2-5

[0252] In one embodiment of the disclosure, when HARQ feedback is configured (for the multicast channel), the UE can drop one of the multicast PDSCH or another channel overlapping with the multicast PDSCH without decoding it. When the other channel overlapping with the multicast channel is a specific channel (e.g., unicast PDSCH or paging-triggered SI), the method according to Embodiment 2-5 can be used.

[0253] In addition, it is assumed that the unicast PDSCH and the multicast PDSCH overlap or do not overlap in one slot in the time domain. In this case, if the sum of the number of PRBs of each of the unicast PDSCH and the multicast PDSCH (or the number of PRBs of either the unicast PDSCH or the multicast PDSCH) exceeds the number of PRBs corresponding to a 5 MHz bandwidth and / or if HARQ feedback is configured, the UE can transmit a NACK without decoding the multicast PDSCH. Accordingly, the UE can cause retransmission from the base station.

[0254] Embodiment 2-6

[0255] In one embodiment of the disclosure, even if two channels (e.g., a unicast PDSCH and a multicast PDSCH, etc.) within one slot overlap or do not overlap with each other in the time domain, if the sum of the number of PRBs of each of the unicast PDSCH and the multicast PDSCH exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the UE can transmit a NACK as HARQ feedback for the multicast PDSCH or perform DTX processing on the multicast PDSCH.

[0256] As another example, if the sum of the number of PRBs of each of the unicast PDSCH and the multicast PDSCH is less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, the UE can decode both the unicast PDSCH and the multicast PDSCH.

[0257] In Embodiment 2-6, the number of PRBs corresponding to a 5 MHz bandwidth can be replaced with another specific value. Here, the other specific value can be determined / configured through UE capability information reported by the UE to the base station or RRC signaling, and can also be pre-defined.

[0258] Embodiment 2-7

[0259] In one embodiment of the disclosure, if the sum of the number of PRBs allocated to a plurality of channels scheduled / allocated to a single slot (i.e., a plurality of overlapping channels in a single slot) is less than or equal to a specific value (e.g., the number of PRBs corresponding to a 5 MHz bandwidth), the UE can decode the plurality of channels. In addition, the UE can not expect a case where the sum of the number of PRBs allocated to the plurality of channels scheduled / allocated to a single slot exceeds the specific value.

[0260] For example, one of the plurality of channels can be a multicast channel (e.g., a multicast PDSCH). And, when a NO HARQ feedback mode is configured, the UE can decode two or more channels regardless of the number of PRBs of the MBS PDSCH.

[0261] As another example, when ACK / NACK mode or NACK only mode is configured for a multicast channel, the UE can not expect the above scheduling (e.g., scheduling such that the sum of the number of PRBs allocated to multiple channels scheduled / allocated to a single slot is less than or greater than a certain value).

[0262] When HARQ disabled mode is configured for a multicast channel via RRC signaling (or DCI), the UE can decode multiple channels that overlap in a single slot. Also, when HARQ disabled mode is indicated for a multicast channel via DCI (or RRC signaling), the UE can not expect the above scheduling.

[0263] Embodiment 2-8

[0264] Embodiment 2-8 relates to UE operations when an MBS channel (e.g., multicast PDSCH or broadcast PDSCH) overlaps with another channel (e.g., unicast channel) and the sum of PRBs of each of the MBS PDSCH and the other channel is greater than or equal to a certain PRB value (e.g., the number of PRBs corresponding to 5 MHz bandwidth).

[0265] For example, if the MBS channel is a broadcast channel associated with MCC-RNTI, the UE can decode both the MBS channel and the other channel.

[0266] As another example, the UE can transmit UE capability information related to processing of the MBS channel and the other channel overlapping therewith to the base station. Then, the UE can decode the MBS channel and the other channel overlapping therewith in a single slot according to the UE capability.

[0267] As another example, if the MBS channel is a channel associated with a broadcasted G-RNTI, the UE can decode both the MBS channel and the other channel. However, if the MBS channel is repeatedly transmitted, the UE can discard the MBS channel.

[0268] As another example, if the MBS channel is a broadcast channel or a multicast channel, the UE can not expect the above scheduling. In this case, if ACK / NACK mode or NACK only mode is configured for a multicast channel, the UE can not expect the above scheduling. If HARQ disabled mode is configured for a multicast channel via RRC signaling, the UE can decode both the multicast channel and the other channel. If HARQ disabled mode is configured for a multicast channel via DCI, the UE can not expect the above scheduling.

[0269] As another example, if the MBS channel is a broadcast channel or a multicast channel, the UE can drop the MBS channel. For example, if the broadcast channel is a broadcast channel associated with a MCCH-RNTI, the UE can drop the unicast channel. If the MBS channel performs repetition transmission, the UE can drop the MBS channel or the unicast channel in a slot where the MBS channel overlaps with the unicast channel. If an ACK / NACK mode or a NACK-only mode is configured for the multicast channel, the UE can drop the MBS channel or the unicast channel. If a HARQ disable mode is configured for the multicast channel via RRC signaling, the UE can decode both the multicast channel and the other channel. If a HARQ disable mode is configured for the multicast channel via DCI, the UE can drop the multicast channel.

[0270] As another example, when ACK / NACK or NACK-only data is transmitted for a multicast channel, the UE can decode both the multicast and the other channel overlapping with the multicast. The above operation can be performed only when a NACK-only mode is configured. As another example, the above operation can be performed only when a NACK-only mode and a NACK-only mode PUCCH resource are configured.

[0271] As another example, if the sum of PRBs of each of a plurality of overlapping channels (e.g., two channels) in a single slot is greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap UE can not perform feedback transmission for the plurality of channels or can treat the plurality of channels as NACK (when a NACK-only or ACK / NACK is configured).

[0272] As another example, if the sum of PRBs of each of a plurality of overlapping channels (e.g., two channels) in a single slot is greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth (when a NACK-only or ACK / NACK is configured), feedback transmission for the plurality of channels can be performed depending on UE implementation.

[0273] Embodiment 2-9

[0274] In one embodiment of the disclosure, when ACK / NACK feedback for a multicast channel is required, HARQ feedback transmission for the multicast channel can be omitted or NACK transmission can be performed.

[0275] Embodiment 2-10

[0276] Embodiment 2-10 relates to a method in which a unicast SPS PDSCH and a multicast SPS PDSCH are transmitted with respect to OFDM symbols overlapping in the same slot.

[0277] For example, the UE can not expect a case where the unicast SPS PDSCH and the multicast SPS PDSCH overlap. If both channels are transmitted as SPS, or if one of the two channels is transmitted as SPS, the UE can not expect a case where the unicast SPS PDSCH and the multicast SPS PDSCH overlap.

[0278] Since SPS-based transmission has less flexibility than PDCCH-based dynamic scheduling, the base station can not schedule the unicast SPS PDSCH and the multicast SPS PDSCH to overlap in one slot.

[0279] In another example of the disclosure, one of the unicast channel (e.g., unicast SPS PDSCH) and the MBS channel (e.g., multicast SPS PDSCH) overlapping in the same slot can be discarded. Since the multicast SPS PDSCH can have a lower priority than the unicast SPS channel, the UE can discard the multicast SPS PDSCH, and the HARQ mode for the multicast SPS PDSCH can be configured as a NO HARQ mode, or a NACK can be transmitted for the multicast SPS PDSCH. However, among the unicast channel (e.g., unicast SPS PDSCH) and the MBS channel (e.g., multicast SPS PDSCH) overlapping in the same slot, the unicast channel can be discarded. That is, the priority of the channels overlapping in the same slot can be defined / configured in advance.

[0280] As another example of the disclosure, even if the same multicast (SPS) channel overlaps with the same slot, the UE can perform the above-described operation (e.g., discard one of a plurality of multicast (SPS) channels, etc.). As another example, the UE can not expect the same multicast (SPS) channel to overlap with the same slot.

[0281] Embodiment 3

[0282] Embodiment 3 relates to a method of handling a multicast PDSCH in an RRC_Inactive state and an SDT (Small Data Transmission) case.

[0283] The MBS-based PDSCH can include a multicast PDSCH and a broadcast-based PDSCH. In the case of a broadcast-based PDSCH, the method according to Embodiment 1 can be applied even in an RRC_Inactive state. In a basic wireless communication system, a multicast operation (e.g., transmission and reception of a multicast PDSCH) can not be performed in an RRC_Inactive state. However, for service continuity, a multicast PDSCH transmission and reception procedure can be possible in an RRC_Inactive state, and the above-described operation can be performed by a narrowband device (e.g., an eRedCap UE).

[0284] Embodiment 3-1

[0285] In one embodiment of the disclosure, a NO HARQ mode for multicast PDSCH can be configured for an eRedCap UE in an RRC_Inactive state. Accordingly, the eRedCap UE can expect scheduling of the entire bandwidth (e.g., scheduling of the multicast PDSCH).

[0286] Here, for the eRedCap UE, scheduling within a bandwidth of up to 20 MHz is possible. For example, if HARQ feedback related information / commands are transmitted through higher layer signaling or DCI, etc., the UE can not receive the corresponding service (e.g., multicast PDSCH). As another example, a NACK only mode in addition to the NO HARQ mode can be configured for the eRedCap UE, and the eRedCap UE can check the overall service status even in an idle state when receiving the service.

[0287] Embodiment 3-2

[0288] In one embodiment of the disclosure, in the case of an SDT in an RRC_Inactive state, unlike Embodiment 1, a NACK only mode or an ACK / NACK mode with feedback can be configured for a general UE (i.e., a non-RedCap UE) or an eRedCap UE.

[0289] Since the RRC_Inactive state is similar to the RRC_Idle (RRC_Idle) state, it can not be suitable to allocate all uplink resources for feedback to a specific UE. However, although it is generally possible to provide an SDT service in an RRC_Idle state, the UE can temporarily perform an operation similar to that in an RRC_Connected state. Accordingly, for an SDT service, a mode that enables feedback to the UE can be configured.

[0290] Additionally or alternatively, due to the high complexity of the ACK / NACK mode, the ACK / NACK mode can not be suitable for RRC_Inactive. Accordingly, for an SDT, only a NACK only mode with limited common PUCCH resources can be applied.

[0291] Additionally or alternatively, when feedback related information is configured for an eRedCap UE, the entire bandwidth can be used, or a plurality of PRBs corresponding to a specific bandwidth can be scheduled, depending on the type and form of feedback. In this case, the method applied to the multicast PDSCH in the RRC_Connected state of Embodiment 1 can be utilized.

[0292] Embodiment 4

[0293] Embodiment 4 relates to various methods for processing a broadcast channel. As described above, an eRedCap UE can process a broadcast channel within a bandwidth of up to 20 MHz. In general, when a downlink channel is scheduled by a DCI 4_0 with CRC scrambled by a MCCH-RNTI, a data rate of the downlink channel can not exceed 10 Mbps. Accordingly, a number of PRBs allocated to a broadcast channel based on the MCCH-RNTI can be limited to not exceed a number of PRBs corresponding to a 5 MHz bandwidth. Further, a number of PRBs allocated to a broadcast channel based on a G-RNTI can be limited to not exceed a number of PRBs corresponding to a 20 MHz bandwidth.

[0294] Embodiment 4-1

[0295] In one embodiment of the disclosure, in the case of broadcasting, a PDSCH based on a MCCH-RNTI (i.e., a PDSCH scheduled by a MCCH-RNTI) can be scheduled within 5 MHz. That is, a number of PRBs allocated to the PDSCH based on the MCCH-RNTI can be limited to be less than or equal to a number of PRBs corresponding to a 5 MHz bandwidth.

[0296] Since a channel based on a MCCH-RNTI includes control information, a wide bandwidth can not be required for the channel. Further, whether a PDSCH based on a MCCH-RNTI is scheduled for a number of PRBs corresponding to a 5 MHz bandwidth can be predefined, but is not limited thereto. Whether the PDSCH based on the MCCH-RNTI is scheduled for a number of PRBs corresponding to a 20 MHz bandwidth can be predefined or can be configured through higher layer signaling.

[0297] Embodiment 4-2

[0298] In one embodiment of the disclosure, a maximum number of PRBs that can be allocated for a multicast channel can be flexibly configured / indicated per HARQ mode and / or per 5 / 20 MHz bandwidth through higher layer signaling or / and DCI. Here, the HARQ mode can include at least one of an ACK / NACK mode, a NACK only mode, a HARQ disabled mode, or a DCI-enabled mode.

[0299] For example, it is assumed that a multicast channel needs to be allocated within a 5 MHz bandwidth. In this case, if the base station indicates PRBs corresponding to a 5 MHz bandwidth (i.e., PRBs of the multicast channel) through FDRA of a PDCCH, the UE can transmit ACK / NACK to the base station or transmit NACK to the base station (e.g., in the case of a NACK only HARQ feedback mode).

[0300] For eRedCap UEs, UE capability information (e.g., "fdm-BroadcastUnicast-r17") indicating whether overlap of group common PDSCH for broadcast and unicast PDSCH in RRC_CONNECTED state within a single slot is supported can not be applied. Thus, for eRedCap UEs, simultaneous reception of different PDSCHs can be restricted, and a margin can be added for processing time relaxation.

[0301] Embodiment 4-3

[0302] In one embodiment of the disclosure, for eRedCap UEs, simultaneous reception of broadcast MBS channel and unicast PDSCH can not be supported. That is, for broadcast MBS channel and unicast PDSCH, UE capability information (e.g., "fdm-BroadcastUnicast-r17") can not be applied to eRedCap UEs.

[0303] Embodiment 4-4

[0304] In one embodiment of the disclosure, for eRedCap UEs, simultaneous reception of multicast MBS channel (e.g., multicast PDSCH) and unicast PDSCH can not be supported. That is, for multicast MBS channel and unicast PDSCH, UE capability information (e.g., "fdm-BroadcastUnicast-r17") can not be applied to eRedCap UEs.

[0305] Embodiment 4-5

[0306] In one embodiment of the disclosure, when simultaneous reception of different PDSCHs in the same slot is supported (e.g., overlap of group common PDSCH for broadcast and unicast PDSCH in RRC_CONNECTED state within a single slot is supported), the number of PDSCHs that can be FDMed in the same slot can be determined by UE capability. That is, an eRedCap UE can transmit UE capability information related to the number of PDSCHs that can be FDMed in the same slot to a base station. Thus, the eRedCap UE can expect that only the number of PRBs that can be processed in a single slot (e.g., PRBs corresponding to a 5 MHz bandwidth) will be allocated.

[0307] Embodiment 4-6

[0308] In one embodiment of the disclosure, in the case of repeated transmission of the MBS PDSCH, the eRedCap UE can expect to be allocated PRBs within the number of PRBs corresponding to a 5 MHz bandwidth regardless of the configuration of HARQ feedback.

[0309] When the repeated transmission of the MBS PDSCH is configured, the eRedCap UE can store the information received first after adding a cross-slot buffer. When the repeated transmission of the MBS PDSCH is configured, it can be necessary to continuously configure the maximum buffer for allocating the MBS PDSCH over a 20 MHz bandwidth. Accordingly, when the repeated transmission of the MBS PDSCH is configured, the number of PRBs allocated to the eRedCap UE can be limited to the number corresponding to a 5 MHz bandwidth.

[0310] Embodiment 4-7

[0311] In one embodiment of the disclosure, when the eRedCap UE is in an RRC_CONNECTED mode, a multicast PDSCH can be scheduled within a bandwidth of up to 20 MHz. In this case, the UE can be configured with a NO HARQ mode via RRC signaling. As another example, when a NACK-only mode or an ACK / NACK mode is configured, feedback for the multicast PDSCH can be ignored, or an RRC connection failure can occur.

[0312] Embodiment 4-8

[0313] In one embodiment of the disclosure, when an ACK / NACK mode or a NACK-only mode is configured, the eRedCap UE can expect the SPS multicast PDSCH to be allocated / scheduled within a number of PRBs corresponding to a maximum bandwidth of 5 MHz.

[0314] Embodiment 4-9

[0315] In one embodiment of the disclosure, in the case of multicast and broadcast, for narrowband communication (i.e., communication of the eRedCap UE), PRBs corresponding to a specific bandwidth within a slot can be allocated / scheduled. For example, in the case of the eRedCap UE, a multicast channel and / or a broadcast channel corresponding to a 5 MHz bandwidth can be allocated / scheduled, similar to a unicast PDSCH.

[0316] Embodiment 4-10

[0317] Embodiment 4-10 relates to the number of PRBs corresponding to the bandwidth of a PDSCH scheduled by various types of RNTI.

[0318] As an example of the disclosure, in the case of MCCH-RNTI, HARQ feedback can always be disabled. For the number of PRBs greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, MBS broadcast operation can be possible. The above operation can be limited to be possible only when scheduled with MCCH_RNTI. In the case of G-RNTI, since data can be scheduled in every slot, an eRedCap UE that can only schedule PRBs equal to the number of PRBs corresponding to a 5 MHz bandwidth can experience decoding-related problems.

[0319] In another example of the disclosure, in the case of G-RNTI, the number of PRBs corresponding to broadcast and multicast can be the same. For example, when HARQ feedback is disabled, PRBs greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth (e.g., PRBs of a multicast or multicast channel) can be used in an RRC_Connected state or an RRC_Inactive state. The disabling of HARQ feedback can be configured through RRC signaling. In another example, when HARQ feedback is enabled, PRBs greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth can be used. All MBS channels scheduled through G-RNTI can be limited to be scheduled within 5 MHz. An eRedCap UE can have difficulty in being continuously scheduled with a high probability to decode PRBs corresponding to a 5 MHz bandwidth within a channel.

[0320] As another example of the disclosure, for G-CS-RNTI (i.e., SPS), confirmation transmission for HARQ feedback ACK can be required in various cases such as HARQ feedback deactivation, and the following options can be applied.

[0321] Option 1: Only PRBs less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth (e.g., PRBs of a multicast channel) can be allocated.

[0322] Option 2: A plurality of PRBs (e.g., PRBs of a multicast channel) corresponding to a 5 MHz bandwidth can be allocated (a new UE processing time is not defined). In this case, when HARQ feedback is disabled and a parameter related to HARQ feedback enabling for SPS PDSCH transmission (e.g., "harq-FeedbackEnablingforSPSactive") is disabled, Option 2 can be applied.

[0323] Meanwhile, the 'dl-DataToUL-ACK list' includes a value for processing HARQ feedback, and the UE can expect to indicate one K1 value among values greater than or equal to a certain value sufficient to process HARQ feedback. Also, the UE can expect that a channel (e.g., multicast (SPS) PDSCH) is scheduled by a G-CS-RNTI based on the K1 value. Since the above case requires HARQ feedback, it can only be applied when a parameter related to HARQ feedback enabling (e.g., 'harq-FeedbackEnablingforSPSactive') is enabled.

[0324] Embodiment 4-11

[0325] Embodiment 4-11 relates to a UE processing method when multiple PDSCHs are scheduled in a single slot as in Embodiment 2.

[0326] Embodiment 4-11-1

[0327] As an example of the disclosure, when a broadcast PDSCH and a unicast PDSCH are scheduled in a single slot, the UE can decode both the broadcast PDSCH and the unicast PDSCH.

[0328] In another example of the disclosure, only when a broadcast PDSCH is scheduled by an MCCH-RNTI, a broadcast PDSCH and a unicast PDSCH can be scheduled in a single slot. If a broadcast PDSCH is scheduled by a G-RNTI, the G-RNTI can be considered the same as a C-RNTI, and an eRedCap UE can have difficulty in simultaneously processing two channels. Therefore, the UE can not expect a G-RNTI related broadcast PDSCH and a unicast PDSCH to be simultaneously scheduled.

[0329] Embodiment 4-11-2

[0330] Embodiment 4-11-2 relates to a case where a multicast PDSCH and a unicast PDSCH are scheduled in a single slot. If HARQ feedback is disabled (e.g., if HARQ feedback is disabled via RRC signaling), the following options can be applied.

[0331] Option 1: The eRedCap UE can decode a multicast PDSCH and a unicast PDSCH scheduled in a single slot.

[0332] Option 2: The eRedCap UE can not expect a multicast PDSCH and a unicast PDSCH to be scheduled in a single slot.

[0333] Option 3: The eRedCap UE can drop or skip a multicast PDSCH among a multicast PDSCH and a unicast PDSCH scheduled in a single slot.

[0334] Option 4: The eRedCap UE can drop or skip the unicast PDSCH among the multicast PDSCH and the unicast PDSCH scheduled in a single slot. In this case, the eRedCap UE can not receive the unicast channel until the next slot of the slot.

[0335] As another example of the disclosure, when HARQ feedback is enabled, the following options can be applied.

[0336] Option 1: The eRedCap UE can drop the multicast PDSCH among the multicast PDSCH and the unicast PDSCH scheduled in a single slot, or transmit NACK HARQ feedback for the multicast PDSCH to the base station.

[0337] Option 2: The eRedCap UE can not expect the multicast PDSCH and the unicast PDSCH to be scheduled in a single slot.

[0338] Option 3: The eRedCap UE can drop or skip the unicast PDSCH among the multicast PDSCH and the unicast PDSCH scheduled in a single slot. In this case, the eRedCap UE can not receive the unicast channel until the next slot of the slot.

[0339] Embodiment 4-12

[0340] In one embodiment of the disclosure, it is assumed that the PDSCH (e.g., multicast PDSCH, etc.) is scheduled via the DCI CRC scrambled by the G-RNTI. In this case, if more than or equal to the number of PRBs corresponding to the 5 MHz bandwidth is scheduled in a single slot, a gap of a certain slot (e.g., 1 slot, etc.) can be applied / added to the single slot. That is, in order to schedule more than or equal to the number of PRBs corresponding to the 5 MHz bandwidth (i.e., the PRBs of the PDSCH) in a single slot, a gap adjacent to the single slot can be configured / scheduled / indicated.

[0341] The above-described operation can be applied to a channel scheduled by the MCC-RNTI as well as the G-RNTI. Furthermore, even when the eRedCap UE is in the RRC_Inactive or RRC_Idle state, the above-described operation can be applied. Furthermore, the above-described operation can be applied to PDSCH reception or P-RNTI triggered SI acquisition operation related to the SI-RNTI as well as the G-RNTI.

[0342] Specifically, the eRedCap UE can decode only a certain number of PRBs (e.g., the number of PRBs corresponding to a 5 MHz bandwidth) in a single slot. Therefore, if a certain number or more of PRBs are scheduled in a single slot (e.g., PRBs allocated to a PDSCH), a gap slot (e.g., at least 1 slot) adjacent to the single slot can be required. Therefore, if a certain number or more of PRBs are scheduled in a single slot, another channel cannot be scheduled in at least one slot adjacent to the single slot (i.e., a slot configured as a gap).

[0343] For example, it is assumed that a certain number or more of PRBs are scheduled in slot n. In this case, if a channel related to a G-RNTI (or / and MCCH-RNTI) or another PDSCH is scheduled on slot n+1, the eRedCap UE can skip or not decode the channel related to the G-RNTI (or / and MCCH-RNTI) or the other PDSCH.

[0344] As another example, if a PDSCH scheduled by MSG 2 or MSG B or a P-RNTI related to a random access procedure is received in slot n+1, the eRedCap UE can first process the channel scheduled in slot n+1 even though the MBS PDSCH scheduled in slot n is processed. That is, the eRedCap UE can skip the MBS PDSCH in slot n or can not be expected to decode the MBS PDSCH in slot n considering the priority of the PDSCH scheduled by MSG 2 or MSG B or the P-RNTI related to the random access procedure.

[0345] As another example, if a PDSCH is scheduled in slot n+1 by a specific RA-RNTI (e.g., msgB-RNTI) or P-RNTI (or SI-RNTI), the eRedCap UE can skip PRBs (e.g., PRBs of the MBS PDSCH) exceeding the number of PRBs corresponding to a 5 MHz bandwidth scheduled in slot n or can not be expected to decode the corresponding MBS PDSCH.

[0346] As another example, if the PDSCH scheduled for slot n+1 needs to be decoded, the eRedCap UE can skip or can not be expected to decode the MBS PDSCH scheduled for slot n. As another example, the eRedCap UE can abort the procedure in slot n.

[0347] As another example, for a channel scheduled in slot n+1 (e.g., a channel for which HARQ feedback is configured), the eRedCap UE can skip the channel or can not expect decoding of the channel. For a channel without HARQ feedback, the eRedCap UE can stop or skip decoding of the MBS PDSCH scheduled in slot n. If the decoding of the MBS PDSCH scheduled in slot n is stopped, the eRedCap UE can discard the stopped MBS PDSCH.

[0348] Embodiment 4-13

[0349] In one embodiment of the disclosure, it is assumed that when a PRB corresponding to a bandwidth of 5 MHz or less (e.g., a PRB of the MBS PDSCH) is scheduled / allocated to slot n, another channel is also received in slot n. Embodiment 4-13 relates to a processing method in the case where another PDSCH is scheduled in slot n+1 in the case where the eRedCap UE has to decode every channel scheduled in slot n. In this case, a plurality of PDSCHs scheduled in slot n can overlap in units of OFDM symbols, but are not limited thereto.

[0350] As an example of the disclosure, when the MBS PDSCH and another channel are scheduled in slot n as described above, the eRedCap UE can discard the MBS PDSCH.

[0351] As an example of the disclosure, if there is no PDSCH that needs to be decoded in slot n+1, the eRedCap UE can decode all of the plurality of PDSCHs (i.e., the MBS PDSCH and other PDSCHs, etc.) scheduled in slot n. Here, the other PDSCHs scheduled in slot n and / or the PDSCHs that need to be decoded in slot n+1 can all be unicast PDSCHs, but are not limited thereto. In addition, if there is no PDSCH that needs to be decoded in slot n+1, even if the sum of the number of PRBs of the MBS PDSCH and the other PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to a bandwidth of 5 MHz, the eRedCap UE can decode all of the MBS PDSCH and the other PDSCHs scheduled in slot n.

[0352] Embodiment 4-14

[0353] Embodiment 2 relates to a processing method when a plurality of channels overlap within a single slot. Meanwhile, as FIG. 10As shown, multiple channels within a single slot can or can not overlap in the frequency domain, although they do not overlap in the time domain. Embodiment 4-14 relates to various processing methods when multiple channels (e.g., unicast channels and / or multicast channels) are scheduled within a single slot, and methods when more PRBs than the number of PRBs corresponding to a 5 MHz bandwidth are allocated within a single slot.

[0354] As described above, an eRedCap UE can process as many PRBs as the number of PRBs corresponding to a 5 MHz bandwidth within a slot. For example, when an MBS PDSCH (e.g., a multicast PDSCH or / and a broadcast PDSCH, etc.) and a unicast channel are scheduled in a slot n, it is assumed that the number of PRBs of the MBS PDSCH is greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, or the sum of the number of PRBs of the MBS PDSCH and the unicast channel is greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth. In this case, the MBS PDSCH and the unicast channel can or can not overlap in the time domain. For example, the eRedCap UE can skip (or discard) the MBS PDSCH, or can not expect decoding of the MBS PDSCH. If HARQ feedback for the MBS PDSCH is enabled, the eRedCap UE can transmit feedback as NACK. As another example, the eRedCap UE can not expect the number of PRBs of the MBS PDSCH to exceed the number of PRBs corresponding to a 5 MHz bandwidth. As another example, the eRedCap UE can process the MBS PDSCH and the unicast PDSCH in the order of reception / scheduling (i.e., the order of OFDM symbols within a slot), and can skip or can not expect decoding of certain PRBs (e.g., PRBs exceeding the range of a 5 MHz bandwidth). In addition, the eRedCap UE can transmit NACK for a channel containing a certain PRB to the base station.

[0355] Embodiment 4-15

[0356] Embodiment 4-15 relates to a processing method when one or more MBS PDSCHs and one or more unicast PDSCHs are scheduled in a slot n.

[0357] As an example of the present disclosure, if up to 7 PDSCHs can be processed within a certain slot, 4 unicast PDSCHs and 3 multicast PDSCHs can be processed within the certain slot. In this case, the eRedCap UE can process the PDSCHs in the order of scheduling in the slot n, and can expect processing of the PDSCHs within the range of processing capability not exceeding a certain bandwidth.

[0358] For example, the eRedCap UE can process the MBS PDSCH and the unicast PDSCH in the order of reception / scheduling (i.e., the order of OFDM symbols within a slot), and can skip or can not expect decoding for certain PRBs (e.g., PRBs beyond the 5 MHz bandwidth range). In addition, the eRedCap UE can send a NACK to the base station for the channel including the certain PRBs.

[0359] For example, if the HARQ feedback mode is ACK / NACK mode or NACK only mode, the number of multicast PDSCHs can be counted together with the number of unicast PDSCHs. If the HARQ feedback mode is NO HARQ mode, the number of multicast PDSCHs can not be counted. In another example, the feedback can not be considered, or both multicast and unicast PDSCHs can be counted.

[0360] Embodiment 4-16

[0361] In one embodiment of the disclosure, in the case of an eRedCap UE, one unicast PDSCH can be scheduled in one slot. The eRedCap UE capable of processing PRBs corresponding to 5 MHz bandwidth in one slot (e.g., PRBs of unicast PDSCH) can process only one unicast PDSCH in one slot.

[0362] Embodiment 4-17

[0363] In one embodiment of the disclosure, a multicast PDSCH and a unicast PDSCH can be scheduled in the same slot. In this case, the HARQ feedback mode of the multicast PDSCH can be configured as ACK / NACK mode or NACK only HARQ feedback mode. As another example, the number of all PDSCHs scheduled in slot n can be counted without considering the feedback mode.

[0364] As another example of the disclosure, the eRedCap UE can process the MBS PDSCH and the unicast PDSCH in the order of reception / scheduling (i.e., the order of OFDM symbols within a slot), and can skip or can not expect decoding for certain PRBs (e.g., PRBs beyond the 5 MHz bandwidth range). In addition, the eRedCap UE can send a NACK to the base station for the channel including the certain PRBs.

[0365] Embodiment 5

[0366] The MBS PDSCH channel can be scheduled within a 5 MHz bandwidth, but can also be scheduled in a region exceeding the 5 MHz bandwidth. In this case, the possibility that the multicast PDSCH or the broadcast PDSCH will be scheduled in consecutive slots can be higher than the possibility that the SIB-based PDSCH or the paging-based PDSCH will be scheduled in consecutive slots.

[0367] Further, as described above, the eRedCap UE can process a unicast channel within a 5 MHz bandwidth in a single slot. In the case of the MBS PDSCH, PRBs can be allocated within the 5 MHz bandwidth, but PRBs exceeding the number of PRBs corresponding to the 5 MHz bandwidth (i.e., PRBs of the MBS PDSCH) can also be allocated.

[0368] If the repeated transmission is performed in consecutive slots, and PRBs exceeding the number of PRBs corresponding to the 5 MHz bandwidth are allocated to a single slot, the processing of the PDSCH scheduled in the next slot of the slot can be problematic.

[0369] When the repeated transmission is scheduled / configured and PRBs exceeding the number of PRBs corresponding to the 5 MHz bandwidth are scheduled in slot n, a processing method when the PDSCH repeatedly transmitted in slot n+1 and another PDSCH are received together is described.

[0370] As an example of the present disclosure, as FIG. 11 indicated, if PRBs exceeding the number of PRBs corresponding to the 5 MHz bandwidth in slot n (i.e., PRBs of the MBS PDSCH) are allocated, additional processing time can be required to process the PDSCH exceeding 5 MHz in the next slot. Therefore, if the repeated transmission is not configured, some PDSCHs scheduled / received in slot n+1 can be processed. However, if the PDSCHs are received consecutively, other PDSCHs can not be processed in the slot in which the repeated transmission is received.

[0371] Hereinafter, when the repeated transmission is configured / scheduled, a processing method when PRBs less than the number of PRBs corresponding to the bandwidth of 5 MHz (e.g., PRBs of the MBS PDSCH) are scheduled is described.

[0372] For the eRedCap UE, when the repeated transmission is configured, a restriction on the allocation of PRBs within the 5 MHz bandwidth can be defined / configured. Therefore, when the repeated transmission is scheduled / performed and another channel is scheduled / received, this can affect the decoding of the channel for each slot, as FIG. 11 indicated.

[0373] Therefore, in a case where a PRB (e.g., a PRB of an MBS PDSCH) can be scheduled in a range of more than 5 MHz bandwidth, when repetition transmission is configured / applied, the number of PRBs indicated by the FDRA field of the DCI can be less than or equal to the number of PRBs corresponding to 5 MHz bandwidth.

[0374] Embodiments described below relate to a processing method of an eRedCap UE when (repetition) transmission of a channel (e.g., an MBS PDSCH) is scheduled within 5 MHz bandwidth or more than 5 MHz bandwidth.

[0375] Embodiment 5-1

[0376] In one embodiment of the disclosure, an eRedCap UE can process only an MBS PDSCH scheduled / received in a first slot, and can not process an MBS PDSCH repeatedly transmitted in remaining slots. That is, the eRedCap UE can not decode or skip an MBS PDSCH scheduled in slots (i.e., slot n+1, slot n+2, slot n+3) after a slot n of (a) of FIG. 10. FIG. 11

[0377] Embodiment 5-2

[0378] In one embodiment of the disclosure, the number of repetition transmissions (of an MBS PDSCH) can be configured as one of 2, 4, or 8 via higher layer signaling. In this case, based on the number of repetition transmissions configured to be more than 2, an eRedCap UE can process only a channel that has been repeatedly transmitted at most 2 times. If the number of repetitions increases, a problem related to decoding can occur as shown in FIG. 11. As another example, a specific threshold value related to the number of repetition transmissions can be configured / indicated / defined, and an eRedCap UE can decode or discard all channels that have been repeatedly transmitted less than / greater than the specific threshold value. FIG. 11

[0379] Embodiment 5-3

[0380] In one embodiment of the disclosure, an eRedCap UE can process only a channel received in an even repetition slot or an odd repetition slot. In this case, the type of a slot (i.e., an even repetition slot or an odd repetition slot) processed by an eRedCap UE can be configured / indicated via DCI or RRC signaling. The even repetition slot or the odd repetition slot can be determined based on a slot in which channel transmission is first performed, but can also be determined based on a slot number.

[0381] ​​In embodiment 5, the eRedCap UE can transmit NACK when performing repetition transmission and even without receiving / decoding one MBS PDSCH.

[0382] Embodiment 6

[0383] Embodiment 6 relates to a method of processing MBS PDSCH on a per-slot basis for repetition transmission when more PRBs than the number of PRBs corresponding to 5 MHz bandwidth (i.e., PRBs of MBS PDSCH) are scheduled in a specific slot.

[0384] When a PDSCH is scheduled within 5 MHz bandwidth or in a range exceeding 5 MHz bandwidth, the eRedCap UE can need an additional processing time (e.g., 1 slot). That is, when processing MBS PDSCH in slot n, if another PDSCH is scheduled in slot n+1, the eRedCap UE can not receive the MBS PDSCH (in slot n+1).

[0385] As an example of the present disclosure, as shown in (b) of FIG. 11, when the MBS PDSCH of slot n+1 is scheduled / transmitted, an additional PDSCH other than the repeated MBS PDSCH is scheduled in slot n+2, and the eRedCap UE can process the MBS PDSCH of slot n+1 and stop processing the corresponding MBS PDSCH in the middle (e.g., in the middle of slot n+1 or slot n+2) and discard it. FIG. 11

[0386] Embodiment 6-1

[0387] In one embodiment of the present disclosure, when processing MBS PDSCH in slot n, if not only repetition transmission of MBS PDSCH exists on the next slot, but another PDSCH is scheduled / received, the eRedCap UE can not receive the MBS PDSCH processed in slot n in the next slot (e.g., slot n+1). That is, the eRedCap UE can not process reception of the repeated MBS PDSCH in slot n+1. That is, even if another PDSCH is scheduled in slot n+1, the eRedCap UE can decode the first MBS PDSCH in slot n.

[0388] Embodiment 6-2

[0389] ​As described above, if another PDSCH in slot n is an MBS PDSCH, the eRedCap UE can not process the MBS PDSCH regardless of whether another PDSCH is received in the next slot (e.g., slot n+1).

[0390] That is, the eRedCap UE can skip reception of the MBS PDSCH repeatedly transmitted. Even if another PDSCH is scheduled in the next slot, the eRedCap UE can receive the first MBS PDSCH among the MBS PDSCHs repeatedly transmitted. Even if repetition is not performed, reception of the MBS PDSCH in slot n can be skipped or not decoded.

[0391] Embodiment 6-3

[0392] In one embodiment of the disclosure, the number of transmissions can be configured to one of 2 to 8 via DCI or RRC signaling. This is to minimize the PDSCH not received when scheduling repetition.

[0393] Embodiment 6-4

[0394] In one embodiment of the disclosure, when multiple channels are simultaneously received in a slot (e.g., when an MBS channel and another PDSCH overlap in OFDM symbol units) or when another PDSCH is scheduled in the next slot, conditions for dropping the MBS PDSCH channel and performing repetition can be applied.

[0395] In addition, the MBS PDSCHs not dropped during the process of repetition can be combined and decoded.

[0396] Embodiment 6-5

[0397] In one embodiment of the disclosure, when repetition is configured / scheduled and a channel is received and decoded in a certain slot, another channel can be received and decoded in a slot after skipping one of the certain slots.

[0398] It can not be desirable to receive and decode the PDSCH based on the slot skipped by the certain slot and scheduled for the slot. That is, the PDSCH can be skipped or not received.

[0399] If, by the method according to Embodiment 6, the PDSCHs of the certain slot and the next slot do not perform even one channel decoding, the eRedCap UE can transmit NACK for the channel not received to the base station.

[0400] Embodiment 7

[0401] Embodiment 7 relates to a processing method in the last slot when PRBs (i.e., PRBs of the MBS PDSCH) exceeding the number of PRBs corresponding to a bandwidth of 5 MHz are scheduled in a certain slot and repetition transmission is configured.

[0402] When repetition transmission is configured, the UE can perform decoding on a corresponding channel for which channel reception has been performed until the last slot for which repetition transmission has been configured. The processing of the last slot for which repetition transmission has been configured can be determined according to whether another PDSCH has been scheduled / received in a slot after the corresponding slot. That is, even if PRBs corresponding to a bandwidth of 5 MHz or more are scheduled on previous slots excluding the last slot (i.e., slots in which all MBS PDSCHs are transmitted), the channel corresponding to the PRBs and another PDSCH can be simultaneously received.

[0403] Embodiment 7-1

[0404] In one embodiment of the disclosure, when repetition transmission is configured, if another PDSCH is scheduled in a slot after the slot, the MBS PDSCH of the slot in which the last repetition transmission is performed can not be decoded.

[0405] Embodiment 7-2

[0406] In one embodiment of the disclosure, it is assumed that PRBs (e.g., PRBs of the MBS PDSCH) greater than or equal to the number of PRBs corresponding to a bandwidth of 5 MHz are scheduled and repetition transmission is configured. At this time, as disclosed in Embodiment 4-12, it can be determined whether to discard the MBS PDSCH of the last slot in which repetition transmission is performed or to discard the MBS PDSCH of the slot after the last slot.

[0407] Embodiment 7-3

[0408] In one embodiment of the disclosure, when repetition transmission is configured, if another PDSCH is simultaneously transmitted in the last slot in which repetition transmission is configured or is scheduled in the next slot, the eRedCap UE can not perform reception of the MBS PDSCH of the last slot, and can perform decoding on the previously received MBS PDSCH.

[0409] In another example of the disclosure, when PRBs (i.e., PRBs of the MBS PDSCH) exceeding the number of PRBs corresponding to a bandwidth of 5 MHz are scheduled, repetition transmission is limited to be configured, or the eRedCap UE can transmit NACK to the base station without receiving the MBS PDSCH of the repetition transmission.

[0410] As another example of the disclosure, if it is not possible to decode two channels scheduled in one slot, the eRedCap UE can decode one of the channels according to the priority of the two channels (e.g., PDSCH scheduled by SI (System Information)-RNTI or PDSCH scheduled by P (Paging)-RNTI).

[0411] Embodiment 8

[0412] In one embodiment of the disclosure, the eRedCap UE can operate a multicast channel within a 20 MHz bandwidth. When HARQ feedback is configured for the multicast channel, the eRedCap UE can add a relaxation time to the processing time.

[0413] That is, unlike Embodiment 1, the eRedCap UE can operate a 20 MHz bandwidth. Here, if there is HARQ feedback and ACK / NACK or NACK only mode is configured, it can be necessary to add an additional time of X value to the UE processing time. Here, if there is no HARQ feedback, the X value can not be applied. Even if ACK / NACK and NACK only mode are configured and only the number of PRBs within 5 MHz BW is allocated, the X value can not be applied.

[0414] Embodiment 8-1

[0415] In one embodiment of the disclosure, when NO HARQ mode is configured, the X value can not be applied to the UE processing type.

[0416] Embodiment 8-2

[0417] In one embodiment of the disclosure, when there is HARQ feedback, the eRedCap UE can add an X value to the additional processing time. Here, the X value can be applied to the same value or different values according to additional processing time capabilities 1 and 2. An X value that differs according to SCS can be applied. In addition, the X value can be the same as the value of the decoding-related processing time applied to message 2 or message B in the RACH procedure. Furthermore, even when a multicast channel is allocated within a 5 MHz bandwidth, the X value can be applied.

[0418] Embodiment 8-3

[0419] In one embodiment of the disclosure, when NACK only mode is configured, the relaxation of the additional processing time of the X value can not be applied to increase the flexibility of network operation.

[0420] Embodiment 8-4

[0421] In one embodiment of the disclosure, when the FDRA information of the PDCCH in the ACK / NACK or NACK only mode indicates PRBs greater than the number of PRBs corresponding to a 5 MHz bandwidth (i.e., when the bandwidth of the channel scheduled by the FDRA information of the PDCCH exceeds 5 MHz), the additional processing time of value X can be applied.

[0422] Also, in the ACK / NACK or NACK only mode, if the FDRA information of the PDCCH indicates PRBs less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth (i.e., if the bandwidth of the channel scheduled by the FDRA information of the PDCCH is less than or equal to 5 MHz), the additional processing time of value X (X = 0) can not be applied.

[0423] As an example of the disclosure, in the case of an MBS channel (e.g., a multicast channel), an eRedCap UE can not expect scheduling over 5 MHz. In this case, the base station can group eRedCap UEs supporting 5 MHz together and schedule the MBS channel for the eRedCap UEs within a 5 MHz bandwidth.

[0424] As an example of the disclosure, in the case of an MBS channel (e.g., a multicast channel), an eRedCap UE can expect scheduling over 5 MHz. In this case, there is no restriction on the grouping of eRedCap UEs, and operation according to the ACK / NACK mode can be considered. For example, timing relaxation can be applied to the eRedCap UE. In another example, timing relaxation can not be applied to the eRedCap UE. In another example, when a multicast PDSCH is scheduled in a bandwidth exceeding 5 MHz, timing relaxation can be applied to the eRedCap UE. For example, when a multicast PDSCH is scheduled in a bandwidth exceeding 5 MHz, whether to apply timing relaxation and how to apply timing relaxation can be determined depending on the ACK / NACK mode.

[0425] Embodiment 9

[0426] Embodiment 9 relates to a method for processing a plurality of channels based on the sum of PRBs of the plurality of channels received simultaneously. That is, Embodiment 9 relates to a processing method in the case where the sum of PRBs of channels transmitted simultaneously exceeds PRBs corresponding to a 5 MHz bandwidth. An eRedCap UE can prioritize processing of important channels based on the priority of channels transmitted simultaneously. Hereinafter, a case where an MBS channel (e.g., a multicast channel and / or a broadcast channel) is received together with another channel within a slot will be described.

[0427] As an example of the disclosure, asFIG. 9 As illustrated, two channels can be scheduled / transmitted in one slot. Here, the MBS PDSCH can include a broadcast PDSCH and / or an MBS PDSCH. Also, the other PDSCH can include a PDSCH that can be scheduled by an SI-RNTI, a P-RNTI, a RA-RNTI, a C-RNTI, or a MsgB-RNTI.

[0428] Embodiment 9-1

[0429] In one embodiment of the disclosure, if the sum of PRBs of each of the plurality of channels received in the same slot does not exceed the number of PRBs corresponding to a certain bandwidth, the eRedCap UE can receive / decode all of the plurality of channels. That is, the eRedCap UE can receive / decode all channels scheduled in each slot of FIG. 9 .

[0430] Embodiment 9-2

[0431] In one embodiment of the disclosure, when the sum of PRBs of two channels (e.g., an MBS PDSCH and another PDSCH) scheduled in one slot exceeds the number of PRBs corresponding to a certain bandwidth (e.g., 25 when the SCS is 15 kHz, or 12 when the SCS is 30 kHz), the operation of the eRedCap UE can be determined in accordance with another PDSCH among the two channels with the RNTI by which it is scheduled.

[0432] For example, if another PDSCH is scheduled by a P-RNTI, the eRedCap UE can discard or skip the MBS PDSCH. That is, the MBS PDSCH can not be decoded.

[0433] For example, if another PDSCH (e.g., a unicast PDSCH) is scheduled by a C-RNTI, the eRedCap UE can discard or skip the unicast PDSCH. That is, the unicast PDSCH can not be decoded. In this case, there can be HARQ feedback for the MBS PDSCH, but there can be no HARQ feedback for the unicast PDSCH.

[0434] For example, if another PDSCH is scheduled by an SI-RNTI, the eRedCap UE can discard or skip the MBS PDSCH. In this case, there can be HARQ feedback for the MBS PDSCH.

[0435] For example, if another PDSCH is scheduled through the MCC-RNTI, the PDSCH scheduled through the MCC-RNTI can be processed preferentially, and the PDSCH scheduled through the G-RNTI can be discarded.

[0436] For example, if two PDSCHs are scheduled through the G-RNTI, the PDSCH to be discarded can be determined based on the priority of each PDCCH scheduling each of the two PDSCHs. That is, the PDSCH scheduled through the PDCCH having a lower priority can be discarded.

[0437] For example, if different MBS PDSCHs are scheduled in the same slot, the MBS PDSCH located later in terms of OFDM symbol position can be discarded.

[0438] Embodiment 9-3

[0439] In one embodiment of the disclosure, if the sum of PRBs of two channels scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, and if there is another PDSCH to be decoded in slot n+1, the eRedCap UE can perform decoding on the two channels.

[0440] When multiple channels are scheduled for the same slot and the multiple channels overlap each other, the operation described in Embodiment 9 can be applied. That is, when multiple channels scheduled for the same slot overlap each other, Embodiment 9 can be applied depending on whether the sum of PRBs of the multiple channels exceeds the number of PRBs corresponding to a 5 MHz bandwidth. However, this is only one embodiment, and Embodiment 9 can be applied even when multiple channels scheduled for the same slot do not overlap each other.

[0441] Embodiment 10

[0442] Embodiment 10 relates to a method for processing simultaneously received channels depending on whether the number of PRBs of an MBS channel exceeds a certain number of PRBs.

[0443] The MBS PDSCH can be scheduled to exceed a bandwidth of 5 MHz (i.e., the number of PRBs of the MBS PDSCH exceeds the number of PRBs corresponding to a bandwidth of 5 MHz). In this case, as shown in (a) of FIG. 10, the processing time of the MBS PDSCH can exceed one slot based on the eRedCap UE. FIG. 12

[0444] ​Hereinafter, the operation of the eRedCap UE when an additional PDSCH is received when the number of PRBs of the MBS PDSCH scheduled on a specific slot exceeds the number of PRBs corresponding to a specific bandwidth (for example, 5 MHz) is described. In this case, the operation of the eRedCap UE can vary depending on the type of PDSCH. The following operations can be applied regardless of whether the two channels (i.e., the MBS PDSCH and the additional PDSCH) overlap in the time domain.

[0445] Embodiment 10-1

[0446] In one embodiment of the disclosure, the eRedCap UE can discard or skip one of the two channels. For example, the eRedCap UE can discard the MBS PDSCH among the two channels.

[0447] For example, if the additional PDSCH (i.e., the unicast PDSCH) is scheduled by the C-RNTI, the eRedCap UE can discard the unicast PDSCH. That is, the unicast PDSCH can not be decoded. In this case, there can be HARQ feedback for the MBS PDSCH, but there can be no HARQ feedback for the unicast PDSCH. Also, in slot n+1, the MBS PDSCH and the unicast PDSCH can overlap in the OFDM symbol unit.

[0448] For example, if the additional PDSCH is scheduled by the P-RNTI, the MBS PDSCH can be discarded. For example, the MBS PDSCH in slot n-1 as shown in (a) of FIG. 12 may be discarded.

[0449] For example, if the additional PDSCH is scheduled by the SI-RNTI, the MBS PDSCH can be discarded. In this case, there can be HARQ feedback for the MBS PDSCH.

[0450] Embodiment 10-2

[0451] Unlike (a) of FIG. 12 , (b) of FIG. 12 shows a case where the number of PRBs of the MBS PDSCH does not exceed the number of PRBs corresponding to the 5 MHz bandwidth. As shown in (b) of FIG. 12 , when the two channels overlap in slot n and slot n+1 (i.e., overlap in one OFDM symbol unit), the eRedCap UE can discard / skip one of the two channels, or the corresponding channel can not be decoded.

[0452] For example, if one of the two channels (i.e., unicast PDSCH) is scheduled by C-RNTI, the eRedCap UE can drop the unicast PDSCH. For example, the channel to be dropped can be determined based on the priority of each DCI scheduling each of the two channels. For example, the channel scheduled by the DCI with lower priority can be dropped.

[0453] For example, if there is HARQ feedback for the MBS PDSCH, the eRedCap UE can drop the unicast PDSCH among the MBS PDSCH and the unicast PDSCH. Here, there can be no HARQ feedback for the unicast PDSCH. As another example, the eRedCap UE can drop the MBS PDSCH among the two channels (e.g., MBS PDSCH and unicast PDSCH).

[0454] Embodiment 10-3

[0455] In one embodiment of the disclosure, in addition to FIG. 9 If the two channels overlap or do not overlap in the time domain and the sum of PRBs of the two channels does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, except for slot n-1 of

[0456] For example, if the unicast PDSCH among the two channels (e.g., MBS PDSCH and unicast PDSCH) is scheduled by C-RNTI, the eRedCap UE can drop the unicast PDSCH. For example, the channel to be dropped can be determined based on the priority of each DCI scheduling each of the two channels. For example, the channel scheduled by the DCI with lower priority can be dropped.

[0457] For example, if there is HARQ feedback for the MBS PDSCH, the eRedCap UE can drop the unicast PDSCH among the MBS PDSCH and the unicast PDSCH. Here, there can be no HARQ feedback for the unicast PDSCH. As another example, the eRedCap UE can drop the MBS PDSCH among the two channels (e.g., MBS PDSCH and unicast PDSCH).

[0458] Embodiment 11

[0459] Embodiment 11 relates to the method of Embodiment 9 and Embodiment 10 depending on the presence or absence of HARQ feedback.

[0460] For the MBS channel, there can be or can not be HARQ feedback. If there is HARQ feedback, the MBS channel can be considered as a unicast PDSCH. If there is no HARQ feedback, the MBS channel can be considered as a general SIB transmission PDSCH channel. Embodiment 11 relates to the processing method of eRedCap UE for the MBS channel with HARQ feedback and the MBS channel without HARQ feedback, respectively.

[0461] If there is HARQ feedback for the MBS channel, Embodiment 10 can be applied. And, if there is no HARQ feedback for the MBS channel, Embodiment 9 can be applied. If there is HARQ feedback, one or more channels can be scheduled within the 5 MHz bandwidth. If there is no HARQ feedback, one or more channels can be scheduled within the 5 MHz bandwidth or beyond the 5 MHz bandwidth.

[0462] Embodiment 11-1

[0463] Embodiment 11-1 relates to the operation of eRedCap UE in the case where there is HARQ feedback, and is described with reference to (b) of FIG. 12 As shown in (b) of FIG. 12 If the multiple channels scheduled for the same slot overlap in the time domain (i.e., overlap within a single OFDM symbol), the eRedCap UE can discard / skip one of the two channels, or the channel can not be decoded, regardless of whether the sum of PRBs of each channel exceeds the number of PRBs corresponding to a certain bandwidth (e.g., 5 MHz) or not.

[0464] For example, if one of the two channels (i.e., unicast PDSCH) is scheduled by C-RNTI, the eRedCap UE can discard the unicast PDSCH. For example, if there is HARQ feedback for the MBS PDSCH, the eRedCap UE can discard the unicast PDSCH among the MBS PDSCH and the unicast PDSCH. In this case, there can be no HARQ feedback for the unicast PDSCH. As another example, the eRedCap UE can discard the MBS PDSCH (e.g., MBS PDSCH and unicast PDSCH) among the two channels.

[0465] For example, if two channels (e.g., PDSCHs) are scheduled through a G-RNTI, a PDSCH to be dropped can be determined based on a priority of each PDCCH scheduling each of the two PDSCHs. That is, a PDSCH scheduled through a PDCCH having a lower priority can be dropped.

[0466] For example, if different MBS PDSCHs are scheduled in the same slot, an MBS PDSCH located later in terms of OFDM symbol position can be dropped.

[0467] When the sum of the number of PRBs of two channels exceeds the number of PRBs corresponding to a 5 MHz bandwidth, Embodiment 11-1 can be applied. That is, when the sum of the number of PRBs of two channels does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the two channels can be decoded.

[0468] Embodiment 11-2

[0469] Embodiment 11-2 relates to the operation of an eRedCap UE in the absence of HARQ feedback, and is described with reference to FIG. 9 Regardless of whether the number of PRBs of an MBS channel scheduled in a specific slot exceeds the number of PRBs corresponding to a 5 MHz bandwidth, if the sum of the number of PRBs of two channels exceeds the number of PRBs corresponding to a specific bandwidth (e.g., 5 MHz), the eRedCap UE can drop one of the two channels.

[0470] In one embodiment of the disclosure, when the sum of the PRBs of two channels (e.g., an MBS PDSCH and another PDSCH) scheduled in one slot exceeds the number of PRBs corresponding to a specific bandwidth (e.g., 25 when the SCS is 15 kHz, or 12 when the SCS is 30 kHz), the operation of the eRedCap UE can be determined in accordance with another PDSCH among the two channels with the RNTI by which it is scheduled.

[0471] For example, if another PDSCH is scheduled through a P-RNTI, the eRedCap UE can drop or skip the MBS PDSCH. That is, the MBS PDSCH can not be decoded.

[0472] For example, if another PDSCH (e.g., a unicast PDSCH) is scheduled through a C-RNTI, the eRedCap UE can drop or skip the unicast PDSCH. That is, the unicast PDSCH can not be decoded. In this case, there can be HARQ feedback for the MBS PDSCH, but there can be no HARQ feedback for the unicast PDSCH.

[0473] For example, if another PDSCH is scheduled through the SI-RNTI, the eRedCap UE can drop or skip the MBS PDSCH. In this case, there can be HARQ feedback for the MBS PDSCH.

[0474] For example, if another PDSCH is scheduled through the MCC-RNTI, the PDSCH scheduled through the MCC-RNTI can be processed preferentially, and the PDSCH scheduled through the G-RNTI can be dropped.

[0475] For example, if two PDSCHs are scheduled through the G-RNTI, the PDSCH to be dropped can be determined based on the priority of each PDCCH scheduling each of the two PDSCHs. That is, the PDSCH scheduled through the PDCCH having a lower priority can be dropped.

[0476] For example, if different MBS PDSCHs are scheduled in the same slot, the MBS PDSCH located later in terms of OFDM symbol position can be dropped.

[0477] Embodiment 11-3

[0478] As an example of the disclosure, when there is HARQ feedback, operations related to FIG. 9 may be applied. As another example, when there is no HARQ feedback, if the number of PRBs of the MBS PDSCH exceeds the number of PRBs corresponding to a 5 MHz bandwidth, operations related to (a) of FIG. 12 may be applied. As another example, when there is no HARQ feedback, if the number of PRBs of the MBS PDSCH is less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, operations related to (b) of FIG. 12 may be applied.

[0479] If a channel other than the MBS PDSCH channel is received in the same slot, the operations described below can be performed. For example, the eRedCap UE can not consider the scheduling described below, or can perform operations according to UE implementation.

[0480] For example, if another PDSCH is scheduled through the P-RNTI, the eRedCap UE can drop or skip the MBS PDSCH. That is, the MBS PDSCH can not be decoded.

[0481] For example, if another PDSCH (e.g., unicast PDSCH) is scheduled through the C-RNTI, the eRedCap UE can drop or skip the unicast PDSCH. That is, the unicast PDSCH can not be decoded. In this case, there can be HARQ feedback for the MBS PDSCH, but there can be no HARQ feedback for the unicast PDSCH.

[0482] For example, if another PDSCH is scheduled through the SI-RNTI, the eRedCap UE can drop or skip the MBS PDSCH. In this case, there can be HARQ feedback for the MBS PDSCH.

[0483] For example, if another PDSCH is scheduled through the MCC-RNTI, the PDSCH scheduled through the MCC-RNTI can be processed preferentially, and the PDSCH scheduled through the G-RNTI can be dropped.

[0484] For example, if two PDSCHs are scheduled through the G-RNTI, the PDSCH to be dropped can be determined based on the priority of each PDCCH scheduling each of the two PDSCHs. That is, the PDSCH scheduled by the PDCCH having a lower priority can be dropped.

[0485] For example, if different MBS PDSCHs are scheduled in the same slot, the MBS PDSCH located later in terms of OFDM symbol position can be dropped.

[0486] Embodiment 12

[0487] Embodiment 12 relates to a method of using Embodiments 9 and 10 according to an MBS broadcast type.

[0488] The MBS broadcast type can include a broadcast type and a multicast type. If the MBS broadcast type is the broadcast type, Embodiment 9 can be applied. If the MBS broadcast is the multicast type, Embodiment 10 can be applied.

[0489] Embodiment 12-1

[0490] As an example of the present disclosure, if the eRedCap UE can receive two or more channels in the same slot, the eRedCap UE can receive two channels. For example, if the total number of PRBs of the two or more channels is less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap UE can receive the two or more channels in the same slot.

[0491] As an example of the disclosure, when an MBS PDSCH and another channel (e.g., another PDSCH) are simultaneously scheduled in the same slot and an eRedCap UE cannot receive both channels at the same time, the method described below can be applied. In this case, the eRedCap UE can not expect to schedule both channels, and can perform operations according to UE implementation.

[0492] For example, if another PDSCH is scheduled through P-RNTI, the eRedCap UE can discard or skip the MBS PDSCH. That is, the MBS PDSCH can not be decoded.

[0493] For example, if another PDSCH (e.g., unicast PDSCH) is scheduled through C-RNTI, the eRedCap UE can discard or skip the unicast PDSCH. That is, the unicast PDSCH can not be decoded. In this case, there can be HARQ feedback for the MBS PDSCH, but there can be no HARQ feedback for the unicast PDSCH.

[0494] For example, if another PDSCH is scheduled through SI-RNTI, the eRedCap UE can discard or skip the MBS PDSCH. In this case, there can be HARQ feedback for the MBS PDSCH.

[0495] For example, if another PDSCH is scheduled through MCC-RNTI, the PDSCH scheduled through MCC-RNTI can be processed preferentially, and the PDSCH scheduled through G-RNTI can be discarded.

[0496] For example, if two PDSCHs are scheduled through G-RNTI, the PDSCH to be discarded can be determined based on the priority of each PDCCH scheduling each of the two PDSCHs. That is, the PDSCH scheduled by the PDCCH having a lower priority can be discarded.

[0497] For example, if different MBS PDSCHs are scheduled in the same slot, the MBS PDSCH located later in terms of OFDM symbol position can be discarded.

[0498] In addition, for a broadcast channel, embodiment 10 can be applied, and for a multicast channel, embodiment 9 can be applied. In addition, when one channel is decoded because the eRedCap UE cannot decode both channels, embodiment 12-1 can be applied.

[0499] Embodiment 13

[0500] As FIG. 13As shown, it is assumed that the PBCH and the MBS channel are received simultaneously or separately in a single slot. In this case, if at least one of the PBCH and the MBS channel is scheduled through the G-RNTI, decoding of the corresponding channel can not be expected. As another example, if the PBCH channel and the MBS channel are received simultaneously or separately, and at least one of the channels is scheduled through the MCCH RNTI, the corresponding channel can be decoded simultaneously.

[0501] The number of PRBs that the eRedCap UE can process in a single slot is 25 (e.g., SCS is 15 / 30 kHz) or 12 (e.g., SCS is 30 / 60 kHz), and the number of PRBs of the PBCH can be 20. Hereinafter, a decoding method of other channels of the eRedCap UE is described.

[0502] Embodiment 13-1

[0503] In one embodiment of the disclosure, when the PBCH and the MBS PDSCH (e.g., PDSCH scheduled through the MCCH-RNTI) are received simultaneously in one slot, the eRedCap UE can discard / skip one of the PBCH and the MBS PDSCH, or can not expect decoding of one of the PBCH and the MBS PDSCH.

[0504] Here, a case of slot n-1 (e.g., a case in which the MBS-MCCH-PDSCH and the PBCH are scheduled without overlapping in the same slot) can not be included or included. FIG. 13 If the sum of the number of PRBs of each of the PBCH and the MBS PDSCH is less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap UE can decode both the PBCH and the MBS PDSCH.

[0505] Embodiment 13-2

[0506] In one embodiment of the disclosure, the eRedCap UE can not expect that the PBCH and the MBS PDSCH (e.g., PDSCH scheduled through the MCCH-RNTI) are scheduled simultaneously in one slot.

[0507] Here, a case of slot n-1 (e.g., a case in which the MBS-MCCH-PDSCH and the PBCH are scheduled without overlapping in the same slot) can not be included or included. FIG. 13 When the SCS is 30 kHz, embodiment 13-2 can be applied. In addition, when the total number of PRBs of each of the PBCH and the MBS PDSCH exceeds the number of PRBs corresponding to a 5 MHz bandwidth, embodiment 13-2 can be applied.

[0508] When the eRedCap UE is in the RRC_Inactive or RRC_Idle state, embodiments 13-1 and 13-2 can be applied. The operations described in embodiments 9 to 12 can be applied according to the bandwidth scheduling range of the MBS channel, regardless of the presence or absence of HARQ feedback or MBS broadcast type.

[0509] Embodiment 13-3

[0510] In one embodiment of the disclosure, when the number of PRBs of the MBS channel scheduled for a specific slot exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the operation related to (a) of FIG. 12 may be applied. That is, the operation according to embodiments 10 and 10-1 can be applied to the PDSCH scheduled for the next slot based on the specific slot.

[0511] Embodiment 13-4

[0512] In one embodiment of the disclosure, if the number of PRBs of the MBS channel does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, and the MBS channel overlaps with another channel in the time domain, the method described below can be applied. The method described below can also be applied to FIG. 12 slot n-1 of (b) of

[0513] - If the sum of the number of PRBs of the MBS channel and each other channel does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap UE can decode both the MBS channel and the other channel.

[0514] - If the sum of the number of PRBs of the MBS channel and each other channel exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap UE can not expect simultaneous scheduling of the two channels or can discard one channel.

[0515] For example, if the other channel is a unicast channel, the eRedCap UE can discard the unicast channel among the two channels. Except for the case of NTN, since there is HARQ feedback for the unicast channel, the eRedCap UE can discard the unicast channel among the two channels. As another example, the eRedCap UE can discard the MBS channel among the two channels.

[0516] As another example, if the other channel is a unicast channel, a channel with HARQ feedback among the MBS channel and the unicast channel can be dropped. In the case of a channel with HARQ feedback, retransmission of the channel can be expected. For example, if there is no HARQ feedback for the unicast channel and no HARQ feedback for the MBS channel, the MBS channel can be dropped.

[0517] For example, if there is or is not HARQ feedback on both the MBS channel and the unicast channel, whether to drop the MBS channel and the unicast channel can be determined based on a priority of DCI scheduling each of the MBS channel and the unicast channel. As another example, if there is or is not HARQ feedback on both the MBS channel and the unicast channel, one of the MBS channel and the unicast channel can be dropped. The type of channel to be dropped among the MBS channel and the unicast channel can be predefined or configured through higher layer signaling.

[0518] For example, if the eRedCap UE can simultaneously receive the unicast channel and the MBS channel in a single slot, the UE can transmit UE capability information (e.g., "fdm-BroadcastUnicast-r17") indicating that it supports simultaneous slots of the unicast channel and the MBS channel to the base station.

[0519] Embodiment 13-5

[0520] In one embodiment of the disclosure, it is assumed that the MBS channel and the unicast PDSCH are scheduled in the same slot. In this case, the MBS channel and the unicast PDSCH can all or partially overlap in one symbol within one slot.

[0521] The operation of the eRedCap UE when it cannot simultaneously receive the MBS channel and the unicast PDSCH is described below. For example, the channel to be dropped among the MBS channel and the unicast channel can be determined based on a priority rule and the presence or absence of HARQ feedback. Here, the priority can be indicated by a priority indicator field included in the DCI. Alternatively, the priority can be configured through RRC signaling or predefined.

[0522] For example, if the other channel is a unicast channel, the eRedCap UE can drop the unicast channel among the two channels. Except for the case of an NTN, since there is HARQ feedback for the unicast channel, the eRedCap UE can drop the unicast channel among the two channels.

[0523] For example, if the two channels cannot be simultaneously received, the eRedCap UE can not expect simultaneous reception scheduling of the two channels.

[0524] As another example, the channel with HARQ feedback among the MBS channel and the unicast channel can be dropped. For the channel with HARQ feedback, retransmission of the channel can be expected. For example, if there is no HARQ feedback for the unicast channel and no HARQ feedback for the MBS channel, the MBS channel can be dropped.

[0525] For example, if there is or is not HARQ feedback on both the MBS channel and the unicast channel, whether to drop the MBS channel and the unicast channel can be determined based on a priority of DCI scheduling each of the MBS channel and the unicast channel. For example, the priority of the guest channel can be indicated by a priority indicator of the DCI, and the channel with lower priority can be dropped regardless of whether there is HARQ feedback.

[0526] As another example, if there is or is not HARQ feedback on both the MBS channel and the unicast channel, one of the MBS channel and the unicast channel can be dropped. The type of the channel to be dropped among the MBS channel and the unicast channel can be configured or predefined by higher layer signaling.

[0527] As another example, one of the MBS PDSCH and the unicast PDSCH can be dropped based on the priority configured / indicated for the MBS PDSCH and the unicast PDSCH, respectively. If the priorities of the MBS PDSCH and the unicast PDSCH are the same, the type of the channel to be dropped can be determined according to the presence or absence of HARQ feedback. If the priorities of the HARQ feedback and the presence or absence of the MBS PDSCH and the unicast PDSCH are the same, the unicast PDSCH can be dropped. As another example, if the priorities of the HARQ feedback and the presence or absence of the MBS PDSCH and the unicast PDSCH are the same, the type of the channel to be dropped among the two channels can be configured or predefined by higher layer signaling. As described above, instead of first checking the priorities of the two channels and then checking the presence or absence of the HARQ feedback, the presence or absence of the HARQ feedback can be checked, and then the priority can be checked.

[0528] As another example, a bit field can be added to the DCI scheduling the MBS PDSCH. If the MBS PDSCH and the unicast PDSCH overlap in the time domain and the eRedCap UE cannot decode both the MBS PDSCH and the unicast PDSCH, the bit field on the DCI can indicate which channel among the MBS PDSCH and the unicast PDSCH to drop / decode.

[0529] Embodiment 13-6

[0530] In one embodiment of the disclosure, it is assumed that an MBS channel and a unicast channel (e.g., a unicast PDSCH) are scheduled within a specific slot, and the number of PRBs of the MBS channel is less than or equal to the number of PRBs corresponding to a bandwidth of 5 MHz. In this case, if the total number of PRBs allocated to each of the MBS channel and the unicast PDSCH (e.g., a PDSCH including a paging or an SIB) exceeds the number of PRBs corresponding to the bandwidth of 5 MHz, it can not be expected or can not skip decoding of a PDSCH that can be scheduled in a slot after the specific slot. For example, the eRedCap UE can not expect another PDSCH to be scheduled in a slot after the specific slot, and if another PDSCH in the next slot is received, the MBS PDSCH in the specific slot can be discarded.

[0531] In one embodiment of the disclosure, when an MBS PDSCH allocated with PRBs less than or equal to the number of PRBs corresponding to a unicast channel and a bandwidth of 5 MHz is received in one slot (in this case, the unicast channel and the MBS PDSCH can or can not overlap each other), it can not be guaranteed which PDSCH the (e)RedCap UE will process until the next slot, and it can be guaranteed that the (e)RedCap UE processes both channels in the slot. If no PDSCH is scheduled in the next slot, the (e)RedCap UE can decode both channels in the slot. In this case, the sum of the number of PRBs of each of the unicast channel and the MBS PDSCH can exceed the number of PRBs corresponding to the bandwidth of 5 MHz, and the unicast channel and the MBS PDSCH can partially or completely overlap within the slot. In addition, if a specific PDSCH is received in the next slot, the MBS PDSCH in the slot can be discarded. As another example, the MBS PDSCH decoding in the slot can not be expected or can be skipped regardless of receiving a specific PDSCH in the next slot.

[0532] Embodiment 13-7

[0533] In one embodiment of the disclosure, when the number of PRBs of a PDSCH (e.g., a PDSCH scheduled by an MCCH-RNTI) associated with the MCCH-RNTI exceeds the number of PRBs corresponding to a bandwidth of 5 MHz, decoding of a PBCH simultaneously transmitted in the same slot as the PDSCH can not be expected or scheduling of the PBCH can not be expected. In addition, the PDSCH and the PBCH have an FDM relationship and can completely or partially overlap in an OFDM symbol.

[0534] If the PDSCH scheduled by the PBCH and the MCCH-RNTI partially or fully overlap within a single slot, the UE can expect that both channels are scheduled (e.g., PDSCH scheduled by the PBCH and / or the MCCH-RNTI) within the 5 MHz bandwidth. Also, the UE can expect to receive the PDSCH scheduled by the MCC-RNTI within the 5 MHz bandwidth regardless of whether the PBCH is received within a single slot or not.

[0535] Embodiment 13-8

[0536] In one embodiment of the disclosure, it is assumed that the unicast channel (or PDSCH scheduled by PDCCH CRC scrambled by RA-RNTI including paging information or SIB) and the MBS PDSCH allocated with the number of PRBs greater than or equal to the bandwidth of 5 MHz overlap with respect to OFDM symbols. However, even when the unicast channel and the MBS PDSCH do not overlap within the same slot, the operation described below can be applied.

[0537] Here, the unicast channel can be dropped (or skipped) or not decoded regardless of the priority of the DCI or the presence or absence of HARQ feedback. If a channel other than the unicast channel (such as the MBS PDSCH) is scheduled within a slot, the MBS PDSCH can be dropped (or skipped) or not decoded.

[0538] For example, if a non-unicast channel and an MBS PDSCH allocated with the number of PRBs greater than or equal to the number of PRBs corresponding to the 5 MHz bandwidth (or regardless of the number of PRBs) are simultaneously scheduled / received within a slot, the MBS PDSCH can not be decoded because it is dropped. In this case, the non-unicast PDSCH can include unicast including paging or SIB. As another example, when the UE is in the RRC_IDLE state or the RRC_INACTIVE state, Embodiment 13-8 can also be applied.

[0539] Embodiment 13-9

[0540] In one embodiment of the disclosure, the unicast PDSCH and the MBS (e.g., multicast or broadcast) PDSCH can or can not overlap with respect to OFDM symbols within one slot, and the base station can expect to schedule each channel such that the sum of the number of PRBs of each of the unicast PDSCH and the MBS PDSCH is within the number of PRBs corresponding to the 5 MHz bandwidth.

[0541] Embodiment 13-10

[0542] In one embodiment of the disclosure, regardless of whether the number of PRBs of the MBS PDSCH (e.g., broadcast PDSCH) exceeds 25, when the MBS PDSCH and the unicast PDSCH are simultaneously transmitted / scheduled within one slot, the UE can decode both the MBS PDSCH and the unicast PDSCH. In this case, the MBS PDSCH and the unicast PDSCH can partially or completely overlap with respect to the OFDM symbol.

[0543] Embodiment 13-11

[0544] In one embodiment of the disclosure, in a case where multiple channels are simultaneously transmitted / scheduled on a specific slot and one of the multiple channels must be dropped, the UE can receive both the MBS PDSCH and another PDSCH in which a slot in which repetition transmission is configured. The UE can determine which of the two channels to drop by comparing the MBS PDSCH and the other PDSCH which are simultaneously transmitted in the slot in which repetition transmission is configured. If repetition transmission is not configured, simultaneous reception of the two channels can be limited or PDSCH reception / scheduling in the next slot can be considered.

[0545] Embodiment 13-12

[0546] In one embodiment of the disclosure, when the MBS PDSCH is received in the same slot as another PDSCH (e.g., a PDSCH scheduled by an SI-RNTI, a paging PDSCH, or a PDSCH associated with a RA-RNTI (or msgB-RNTI), etc.), the UE can drop the MBS PDSCH regardless of the number of PRBs of the MBS PDSCH. In this case, the MBS PDSCH and the other PDSCH can completely or partially overlap in the OFDM symbol.

[0547] Embodiment 13-13

[0548] In one embodiment of the disclosure, it is assumed that the MBS PDSCH and another channel are transmitted / scheduled in slot n. If the sum of the number of PRBs of the MBS PDSCH and each other channel exceeds the number of PRBs corresponding to a 5 MHz bandwidth, and if there is no other PDSCH in slot n+1, regardless of the number of PRBs of the MBS PDSCH, the UE can decode both the MBS PDSCH and the other channel. In this case, the MBS PDSCH and each other channel can overlap in the OFDM symbol, but are not limited thereto.

[0549] For example, the other PDSCH can be, but is not limited to, a unicast PDSCH. If the other PDSCH is a unicast PDSCH, the UE can not decode both the MBS PDSCH and the unicast PDSCH within the slot n.

[0550] Embodiment 13-14

[0551] In one embodiment of the disclosure, it is assumed that the MBS PDSCH and another channel are transmitted / scheduled in the slot n. If the sum of the number of PRBs of the MBS PDSCH and each other channel is greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, the UE can discard the MBS PDSCH. In this case, the MBS PDSCH and each other channel can overlap in the OFDM symbol, but are not limited thereto. For example, when another PDSCH is scheduled in the slot n+1, Embodiments 13-14 can be applied.

[0552] For example, the other PDSCH can include a PDSCH scheduled by an SI-RNTI requiring decoding, a paging PDSCH, etc.

[0553] In the disclosure, if both of the two channels scheduled in one slot are expected to be decoded, the PDSCH on which inter-channel contention is performed can include a PDSCH scheduled by an SI-RNTI and a PDSCH associated with a P-RNTI. In addition, another PDSCH scheduled in the next slot can include a PDSCH that generally requires decoding from a UE perspective.

[0554] Embodiment 14

[0555] Embodiment 14 relates to a case where a plurality of MBS channels and a unicast PDSCH are received in one slot. In this case, a PDSCH scheduled in the next slot can be considered.

[0556] That is, Embodiment 14 relates to a processing method of an eRedCap UE when one or more MBS channels and one or more unicast PDSCHs are scheduled in one slot. However, this is only one embodiment, and when one MBS channel and one unicast PDSCH are scheduled in one slot, the operations described in Embodiment 14 can also be applied.

[0557] Here, if the sum of the number of PRBs of each of the one or more MBS channels and the one or more unicast PDSCHs is less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap UE can decode both the one or more MBS channels and the one or more unicast PDSCHs.

[0558] As an example of the present disclosure, assume that one or more MBS channels (e.g., MBS PDSCHs) and one or more unicast PDSCHs are scheduled in slot n, and another PDSCH is scheduled in slot n+1.

[0559] If the sum of PRBs per MBS PDSCH and unicast PDSCH exceeds the number of PRBs corresponding to 5 MHz bandwidth (e.g., 25 for 15 kHz SCS, or 12 for 30 kHz SCS), and no other PDSCH is scheduled for the next slot (e.g., slot n+1), the eRedCap UE can decode both the one or more MBS PDSCHs and the one or more unicast PDSCHs. The eRedCap UE can support an additional timeline processing time relaxation of about one slot even if the number of PRBs per channel exceeds the number of PRBs corresponding to 5 MHz bandwidth.

[0560] Here, assume that another PDSCH is scheduled in the next slot (e.g., slot n+1). Since the eRedCap UE can process PRBs corresponding to 5 MHz bandwidth in one slot, if it cannot drop the other PDSCH in the next slot, the eRedCap UE can drop some of the one or more MBS PDSCHs and the one or more unicast PDSCHs. The eRedCap UE can process PRBs within the number of PRBs corresponding to 5 MHz bandwidth in slot n.

[0561] Hereinafter, a method for determining a dropped channel among the one or more MBS PDSCHs and the one or more unicast PDSCHs in slot n is described. In embodiment 14, it can be assumed that the eRedCap UE expects the sum of the number of PRBs of a plurality of unicast PDSCHs received within one slot to be less than or equal to PRBs corresponding to 5 MHz bandwidth.

[0562] Embodiment 14-1

[0563] In one embodiment of the present disclosure, when one or more MBS PDSCHs and one or more unicast PDSCHs are scheduled in slot n, the UE can drop all of the one or more MBS PDSCHs. In this case, the sum of the number of PRBs of each of the one or more MBS PDSCHs and the one or more unicast PDSCHs scheduled in slot n can exceed, but is not limited to, the number of PRBs corresponding to 5 MHz bandwidth.

[0564] Further, even if the total number of PRBs scheduled in slot n becomes less than or equal to the number of PRBs corresponding to a 5 MHz bandwidth due to the removal of some of the one or more MBS PDSCHs, the UE can discard one or more MBS PDSCHs. In this case, one or more unicast PDSCHs can also be discarded in their entirety, or it can not be desirable to decode them.

[0565] Embodiment 14-2

[0566] In one embodiment of the disclosure, when one or more MBS PDSCHs and one or more unicast PDSCHs are scheduled in slot n, the MBS PDSCHs whose starting symbols are last on the OFDM symbols can be discarded in order. In this case, the sum of the number of PRBs of each of the one or more MBS PDSCHs and the one or more unicast PDSCHs scheduled in slot n can exceed the number of PRBs corresponding to a 5 MHz bandwidth, but is not limited thereto.

[0567] For example, the eRedCap UE can decode each channel (e.g., multicast PDSCHs and unicast PDSCHs that are not discarded, etc.) within the number of PRBs corresponding to a 5 MHz bandwidth within slot n. For example, the eRedCap UE can decode one or more MBS PDSCHs starting with a PDSCH having an earlier starting symbol, and can discard the corresponding MBS PDSCH when the number of decoded PRBs exceeds the number of PRBs corresponding to a 5 MHz bandwidth. That is, as shown in (a) of FIG. 13, the middle MBS PDSCH in slot n can be processed, and the last MBS PDSCH can be discarded. FIG. 14

[0568] Additionally or alternatively, it is assumed that MBS PDSCHs are sequentially scheduled in TDM. The eRedCap UE can schedule one or more MBS PDSCHs in OFDM symbol order, and if the number of decoded PRBs exceeds a certain value, the corresponding MBS PDSCH can be discarded. Further, the eRedCap UE can decode one or more unicast PDSCHs scheduled after the discarded MBS PDSCH. Here, the eRedCap UE can decode one or more unicast PDSCHs within the range in which the number of PRBs decoded so far in slot n does not exceed the number of PRBs corresponding to a 5 MHz bandwidth.

[0569] ​That is, the eRedCap UE can process one or more MBS PDSCHs in the order of the starting of OFDM symbols. Further, when the eRedCap UE processes PRBs of a specific MBS PDSCH, if the total number of decoded PRBs exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the corresponding MBS PDSCH is discarded, and within the range of not exceeding the number of PRBs in the 5 MHz BW, one or more channels (e.g., unicast PDSCH) can be decoded in the order of OFDM symbols.

[0570] As described above, one or more MBS PDSCHs can be decoded first, followed by unicast PDSCHs, but are not limited thereto. One or more unicast PDSCHs can be decoded first, followed by multicast PDSCHs. As another example, MBS PDSCHs and unicast PDSCHs can be decoded in the order of the starting symbols of the 5 MHz bandwidth without distinction.

[0571] Embodiment 14-3

[0572] In one embodiment of the disclosure, when one or more MBS PDSCHs and one or more unicast PDSCHs are scheduled in a slot n, one or more MBS PDSCHs can be discarded according to the priority of each MBS PDSCH. In addition, decoding of one or more PDSCHs can be performed within the range of 5 MHz bandwidth.

[0573] Here, the priority of each MBS PDSCH can be indicated by DCI scheduling each MBS PDSCH, and can also be configured by higher layer signaling. As another example, the priority of each MBS PDSCH can be predefined. For example, the priority of a broadcast PDSCH can be defined as the highest priority or the lowest priority. As another example, the priority of a broadcast PDSCH can be configured by higher layer signaling.

[0574] In one embodiment of the disclosure, it is assumed that three or more PDSCHs are scheduled within one slot, and the sum of PRBs of the three or more PDSCHs exceeds the number of PRBs corresponding to a 5 MHz bandwidth.

[0575] For example, if the sum of the number of PRBs of two PDSCHs having the highest priority among three or more PDSCHs is less than or equal to the number of PRBs corresponding to a bandwidth of 5 MHz, reception / decoding of the two PDSCHs can be performed, and reception of the remaining PDSCHs can be omitted. As another example, if the sum of the number of PRBs of two PDSCHs having the highest priority among three or more PDSCHs exceeds the number of PRBs corresponding to a bandwidth of 5 MHz, only the PDSCH having a higher priority among the two PDSCHs can be received / decoded, and reception of the remaining PDSCHs can be omitted. As another example, only the PDSCH having the highest priority among three or more PDSCHs can be received / decoded, and reception of the remaining PDSCHs can be omitted.

[0576] Embodiment 14-4

[0577] In one embodiment of the disclosure, the priority of each of the plurality of PDSCHs scheduled for slot n can be determined based on an RNTI associated with each of the plurality of PDSCHs. That is, among the plurality of PDSCHs scheduled for slot n, the PDSCH having a lower priority can be discarded first. Accordingly, the eRedCap UE can decode the PDSCH within the 5 MHz bandwidth range.

[0578] Embodiment 14-5

[0579] In one embodiment of the disclosure, the MBS PDSCH having HARQ feedback can be retransmitted, and the MBS PDSCH having HARQ feedback can be discarded from among the plurality of PDSCHs scheduled in slot n. Accordingly, the eRedCap UE can decode the PDSCH within the 5 MHz bandwidth range.

[0580] For example, if the sum of the number of PRBs of the MBS PDSCHs having no HARQ feedback exceeds the number of PRBs corresponding to a bandwidth of 5 MHz, the eRedCap UE can decode the MBS PDSCHs having no HARQ feedback within the 5 MHz bandwidth in the order of the starting OFDM symbol. As another example, the eRedCap UE can discard the MBS PDSCHs having HARQ feedback first.

[0581] Embodiment 14-6

[0582] In one embodiment of the disclosure, among the plurality of MBS PDSCHs scheduled in a certain slot, a repeatedly configured PDSCH can be preferentially dropped. In addition, the eRedCap UE can decode one or more PDSCHs not dropped within the 5 MHz bandwidth range.

[0583] Embodiment 14-7

[0584] In one embodiment of the disclosure, when a plurality of MBS PDSCHs and a plurality of unicast PDSCHs are scheduled on one slot, the eRedCap UE can expect that the sum of the number of PRBs of the plurality of MBS PDSCHs and the plurality of unicast PDSCHs on one slot is less than or equal to the number of PRBs corresponding to the 5 MHz bandwidth.

[0585] For example, if the sum of the number of PRBs of the MBS PDSCH and the plurality of unicast PDSCHs exceeds the number of PRBs corresponding to the 5 MHz bandwidth, all unicast PDSCHs scheduled in the slot can be dropped, or all multicast PDSCHs can be dropped. If all multicast PDSCHs are dropped, the eRedCap UE can process the unicast PDSCH within the 5 MHz bandwidth. As another example, if the sum of the number of PRBs of the MBS PDSCH and the plurality of unicast PDSCHs exceeds the number of PRBs corresponding to the 5 MHz bandwidth, all PDSCHs can be dropped.

[0586] Embodiment 14-8

[0587] In one embodiment of the disclosure, when the sum of the number of PRBs of each PDSCH in the plurality of PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to the 5 MHz bandwidth, the PDSCH to be dropped can be identified according to the PRB size of each PDSCH in the plurality of PDSCHs. In addition, the eRedCap UE can process at least one PDSCH not dropped within the 5 MHz bandwidth.

[0588] For example, referring to FIG. 14In this case, if the method of discarding the later-scheduled MBS PDSCH based on the starting OFDM symbol order is applied, the MBS PDSCH having 10 PBR among the MBS PDSCHs can be kept. Therefore, since the total number of PRBs of the unicast PDSCH and the remaining MBS PDSCH is 30, the eRedCap UE must also discard the remaining MBS PDSCH. Therefore, if another PDSCH is scheduled on slot n+1, the eRedCap UE can discard the PDSCH having a large / small number of PRBs among the plurality of MBS PDSCHs.

[0589] In this case, if the method of discarding the later-scheduled MBS PDSCH based on the starting OFDM symbol order is applied, the MBS PDSCH having 10 PBR among the MBS PDSCHs can be kept. Therefore, since the total number of PRBs of the unicast PDSCH and the remaining MBS PDSCH is 30, the eRedCap UE must also discard the remaining MBS PDSCH. Therefore, if another PDSCH is scheduled on slot n+1, the eRedCap UE can discard the PDSCH having a large / small number of PRBs among the plurality of MBS PDSCHs.

[0590] As another example, when the number of PRBs of the plurality of MBS PDSCHs is the same, the method of discarding the later-scheduled MBS PDSCH based on the starting OFDM symbol order can be applied.

[0591] As another example, the eRedCap UE can decode the plurality of channels within the 5 MHz bandwidth range in the order in which the PDSCHs are scheduled in slot n. The eRedCap UE can decode the PDSCHs that are sequentially scheduled in slot n, and can ensure that the total number of decoded PRBs does not exceed the number of PRBs corresponding to the 5 MHz bandwidth.

[0592] Embodiment 14-9

[0593] In an embodiment of the disclosure, if the total number of the number of PRBs of each of the plurality of PDSCHs scheduled in slot n does not exceed the number of PRBs corresponding to the 5 MHz bandwidth, the eRedCap UE can determine which PDSCH among the unicast PDSCH and the MBS PDSCH to decode / discard.

[0594] Embodiment 14-10

[0595] In one embodiment of the disclosure, the eRedCap UE can or can not receive the unicast PDSCH or the MBS PDSCH when the sum of the number of PRBs of one or more unicast PDSCHs and one or more multicast PDSCHs scheduled in a slot n (at the same time) exceeds the number of PRBs corresponding to a 5 MHz bandwidth. The way in which the eRedCap UE receives either of the unicast PDSCH or the MBS PDSCH can be configured through higher layer signaling or can be performed through UE implementation.

[0596] The operations according to Embodiments 14-1 to 14-10 can be performed under the assumption of dropping the MBS PDSCH or / and the unicast PDSCH based on the location of the OFDM symbol, whether repetition transmission is configured, whether HARQ feedback exists, priority, or / and the number of PRBs, etc.

[0597] In addition, the operations according to Embodiments 14-1 to 14-10 can be applied to the case where the unicast PDSCH shown in (a) of the above Table 14-1 becomes an MBS PDSCH (i.e., the case where three MBS PDSCHs are scheduled in one slot). In addition, the same priority can be assigned to the MBS PDSCH and the unicast PDSCH scheduled in the same slot, and the above-described dropping rule based on priority or based on the number of PRBs can be applied. FIG. 14

[0598] For example, the dropping rule based on the number of PRBs (e.g., the rule of preferentially dropping the channel having a large / small number of PRBs) can be applied. As another example, the unicast PDSCH and / or the MBS PDSCH can be dropped based on the OFDM symbol start position or the presence or absence of HARQ. In other words, regardless of whether the unicast PDSCH or the MBS PDSCH is distinguished, the above-described dropping rule can be applied.

[0599] As another example, if the sum of the PRBs of the plurality of unicast channels and the MBS PDSCH scheduled in a certain slot exceeds the PRBs corresponding to a 5 MHz bandwidth, and a PDSCH is scheduled in the next slot of the certain slot, the MBS PDSCH of the certain slot can be dropped. Even if the MBS PDSCH of the certain slot is dropped, the sum of the PRBs of the unicast channels can still exceed the PRBs corresponding to a 5 MHz bandwidth.

[0600] If the total number of PRBs of the unicast channels exceeds the number of PRBs corresponding to a 5 MHz bandwidth, and if no PDSCH is scheduled on the next slot of the certain slot, the eRedCap UE can decode all channels on the certain slot.

[0601] ​Embodiment 14-11

[0602] In one embodiment of the disclosure, when each channel is scheduled in slot n as shown in (c) of FIG. 13, Figure 14 That is, when a plurality of unicast channels are scheduled in one slot in TDM, the eRedCap UE can transmit UE capability information indicating whether decoding of a plurality of unicast channels and / or the number of channels that can be decoded is supported to the base station. The eRedCap UE can transmit / use the above-described UE capability information, or the capability information for the eRedCap UE can be newly defined. As another example, the eRedCap UE can not support decoding / reception of a plurality of unicast channels or a plurality of MBS PDSCHs.

[0603] As an example of the disclosure, the eRedCap UE can sequentially discard the MBS PDSCHs with respect to the OFDM symbols having the latest starting symbol (i.e., decode the PDSCHs with respect to the OFDM symbols having the earliest starting symbol). Accordingly, the eRedCap UE can decode one or more PDSCHs within the 5 MHz bandwidth range.

[0604] Embodiment 14-12

[0605] In one embodiment of the disclosure, when one or more MBS PDSCHs and one or more unicast PDSCHs are scheduled in slot n, one or more unicast PDSCHs can be discarded according to the priority of each unicast PDSCH. In addition, decoding of one or more PDSCHs can be performed within the 5 MHz bandwidth range.

[0606] Here, the priority of each unicast PDSCH can be indicated by DCI scheduling each unicast PDSCH, and can also be configured by higher layer signaling. As another example, the priority of each unicast PDSCH can also be predefined. For example, the priority of a broadcast PDSCH can be defined as the highest priority or the lowest priority. As another example, the priority of a broadcast PDSCH can be configured by higher layer signaling.

[0607] In one embodiment of the disclosure, it is assumed that three or more PDSCHs are scheduled in one slot, and the sum of PRBs of the three or more PDSCHs exceeds the number of PRBs corresponding to the 5 MHz bandwidth.

[0608] For example, if the sum of the number of PRBs of two PDSCHs having the highest priority among three or more PDSCHs is less than or equal to the number of PRBs corresponding to a bandwidth of 5 MHz, reception / decoding of the two PDSCHs can be performed, and reception of the remaining PDSCHs can be omitted. As another example, if the sum of the number of PRBs of two PDSCHs having the highest priority among three or more PDSCHs exceeds the number of PRBs corresponding to a bandwidth of 5 MHz, only the PDSCH having a higher priority among the two PDSCHs can be received / decoded, and reception of the remaining PDSCHs can be omitted. As another example, only the PDSCH having the highest priority among three or more PDSCHs can be received / decoded, and reception of the remaining PDSCHs can be omitted.

[0609] Embodiment 14-13

[0610] In one embodiment of the disclosure, a unicast PDSCH with HARQ feedback can be retransmitted, and can be discarded starting from a unicast PDSCH with HARQ feedback among a plurality of PDSCHs scheduled in a slot n. Accordingly, the eRedCap UE can decode the PDSCHs within a 5 MHz bandwidth range.

[0611] For example, if the sum of the number of PRBs of unicast PDSCHs without HARQ feedback exceeds the number of PRBs corresponding to a bandwidth of 5 MHz, the eRedCap UE can decode the unicast PDSCHs without HARQ feedback in the 5 MHz bandwidth in order of the starting OFDM symbol. As another example, the eRedCap UE can first discard the unicast PDSCHs with HARQ feedback.

[0612] Embodiment 14-14

[0613] In one embodiment of the disclosure, among a plurality of unicast PDSCHs scheduled within a certain slot, a repeatedly configured PDSCH can be preferentially discarded. In addition, the eRedCap UE can decode one or more PDSCHs within a 5 MHz bandwidth range that are not discarded.

[0614] Embodiment 14-15

[0615] In one embodiment of the disclosure, when a plurality of unicast PDSCHs are scheduled in one slot, the UE can or can not expect that the plurality of unicast PDSCHs are scheduled such that the sum of the number of PRBs does not exceed 25. Further, when the sum of the number of PRBs of the plurality of unicast PDSCHs exceeds 25, the UE can not decode the plurality of unicast PDSCHs.

[0616] Embodiment 14-16

[0617] In one embodiment of the disclosure, if the sum of the number of PRBs of each of the plurality of PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap UE can identify a PDSCH to be dropped according to the PRB size of each of the plurality of PDSCHs. For example, the eRedCap UE can perform decoding / dropping for a PDSCH having a large PRB size or a unicast PDSCH. In addition, the eRedCap UE can process at least one PDSCH that is not dropped within the 5 MHz bandwidth.

[0618] Embodiment 14-17

[0619] In one embodiment of the disclosure, if the sum of the number of PRBs of each of the plurality of unicast PDSCHs scheduled in slot n does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap UE can determine a PDSCH to be decoded / dropped among the plurality of unicast PDSCHs.

[0620] Embodiment 14-18

[0621] In one embodiment of the disclosure, when a plurality of unicast PDSCHs are scheduled in slot n, the eRedCap UE can not decode the plurality of unicast PDSCHs. In this case, the sum of the number of PRBs of each of the plurality of unicast PDSCHs can exceed the number of PRBs corresponding to a 5 MHz bandwidth, but is not limited thereto.

[0622] The above-described embodiments relate to a method for determining a channel to be dropped among an MBS PDSCH and a unicast PDSCH when the MBS PDSCH and the unicast PDSCH are scheduled in a specific slot.

[0623] The method for determining which channel to drop among the MBS PDSCH and the unicast PDSCH can be based on the presence or absence of HARQ feedback for each channel, priority, the presence or absence of repetition transmission configuration, channel type, etc. The eRedCap UE can determine which channel to drop by considering in the following order for each channel: the presence or absence of HARQ feedback, priority, the presence or absence of repetition transmission configuration, and channel type.

[0624] However, this is only one implementation, and the eRedCap UE can determine the presence or absence of HARQ feedback, priority, presence or absence of repetition transmission configuration, and channel type for each channel in order as factors for determining which channels to drop. As another example, the order of the presence or absence of HARQ feedback, priority, presence or absence of repetition transmission configuration, and channel type for each channel as factors for determining which channels to drop can be configured through higher layer signaling or predefined.

[0625] For example, if a unicast channel and an MBS channel are scheduled in one slot, and the sum of the number of PRBs of each unicast channel and MBS channel exceeds the number corresponding to a 5 MHz bandwidth, the eRedCap UE can decode / drop each channel within the range of the number of PRBs not exceeding the number corresponding to a 5 MHz bandwidth in one slot. In this case, the eRedCap UE can drop the MBS channel having priority, but can also drop the unicast channel having priority. As another example, the eRedCap UE can drop the channel having the latest / earliest OFDM symbol, or drop at least one channel depending on the presence or absence of HARQ feedback or the number of PRBs.

[0626] For example, the eRedCap UE can determine whether to drop / decode the unicast PDSCH or MBS PDSCH scheduled for one slot within a 5 MHz bandwidth in the order of priority, the number of PRBs, and the starting OFDM symbol position. As another example, the eRedCap UE can determine whether to drop / decode the unicast PDSCH or MBS PDSCH scheduled for one slot within a 5 MHz bandwidth in the order of the presence or absence of HARQ feedback, the number of PRBs, or the starting OFDM symbol position.

[0627] That is, the decoding / dropping order / method of the MBS / unicast channel can be determined based on the cases described below. Each case represents a priority factor to be considered when determining which channel to drop / decode. However, this is only one example, and additional cases can exist.

[0628] Case 1: PDSCH type (MBS channel or unicast channel) > starting OFDM symbol

[0629] Case 2: PDSCH type (MBS channel or unicast channel) > number of PRBs (large or small) > starting OFDM symbol

[0630] Case 3: HARQ (with or without) > starting OFDM symbol > PDSCH type (MBS or unicast)

[0631] Case 4: HARQ (with or without) > PDSCH type (MBS or unicast) > starting OFDM symbol

[0632] The above cases can perform the dropping / decoding operation depending on whether the sum of the number of PRBs of each MBS PDSCH or unicast PDSCH exceeds the number of PRBs corresponding to a 5 MHz bandwidth. For example, when decoding the channels scheduled in sequence, the eRedCap UE can determine whether the sum of the number of PRBs of the decoded channels exceeds the number of PRBs corresponding to a 5 MHz bandwidth.

[0633] For example, in Case 1, the eRedCap UE can process the unicast PDSCH having priority. At this time, if the number of decoded PRBs does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap UE can decode the MBS PDSCH. If the number of decoded PRBs exceeds the number of PRBs corresponding to a 5 MHz bandwidth, it can be determined that the MBS PDSCH to be additionally decoded within the 5 MHz bandwidth range. Here, the MBS PDSCH to be decoded / dropped can be determined according to the starting OFDM symbol of the MBS PDSCH.

[0634] For example, if the number of PRBs of the MBS PDSCH in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, or the sum of the number of PRBs of the MBS PDSCH or unicast PDSCH scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the base station can inform the UE that there is a PDCCH scheduling a specific channel on slot n or / and slot n+1 in slot n+1.

[0635] Embodiment 15

[0636] Embodiment 15 relates to a case where a plurality of MBS channels and unicast PDSCHs are received in one slot (e.g., slot n). In this case, the PDSCHs scheduled in the next slot (e.g., slot n+1) can not be considered.

[0637] That is, in Embodiment 15, if PRBs exceeding the number of PRBs corresponding to a 5 MHz bandwidth are scheduled on a slot, the channels of the slot can be dropped regardless of whether another PDSCH is scheduled on the next slot. In this case, when determining which PDSCH among the unicast PDSCH and the multicast PDSCH is to be dropped in slot n, the above-described method can be used. Figure 14 In (a) and (b) of the above, reception of a specific PDSCH can not be processed even if there is no other PDSCH on slot n+1. In this case, when determining which PDSCH among the unicast PDSCH and the multicast PDSCH is to be dropped in slot n, the above-described method can be used.

[0638] Embodiment 14 is a method of applying the above-described method when another PDSCH is scheduled in the next slot (e.g., slot n+1), and embodiment 15 is a method of dropping each channel regardless of whether another PDSCH is scheduled in the next slot (e.g., slot n+1) when PRBs corresponding to a 5 MHz bandwidth are scheduled in slot n.

[0639] For example, in the case of (a) of Figure 15 If the method according to embodiment 14-2 is applied, the eRedCap UE can decode all unicast PDSCHs and MBS PDSCHs since there is no other channel in slot n+1, for example, in the case of (a) of

[0640] However, when the method according to embodiment 15 is applied, the number of PRBs corresponding to a 5 MHz bandwidth can be processed in slot n regardless of whether another PDSCH is scheduled in slot n+1. If the number of PRBs corresponding to the MBS PDSCH scheduled in slot n+1 exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the corresponding channel can be dropped.

[0641] For example, when the operation according to embodiment 15 is applied to (a) of Figure 15 The second MBS PDSCH whose PRB count is 30 can be dropped, and the first MBS PDSCH, the third unicast PDSCH, and the next MBS PDSCH can be dropped, for example, in the case of (a) of

[0642] As an example of the present disclosure, when a priority is configured / indicated / defined for a unicast channel, the number of PRBs of the MBS PDSCH can be added after the sum of the number of PRBs of the unicast PDSCH is calculated as in (b) of Figure 15 When the PRBs of the MBS PDSCH are added to the sum of the number of PRBs of the unicast PDSCH in OFDM order, the earliest MBS PDSCH (i.e., the MBS PDSCH having 6 PRBs) in terms of OFDM symbols can be decoded. Also, when it is determined to decode the MBS PDSCH after the unicast channel, the MBS PDSCH (i.e., the PDSCH having 6 PRBs) after the unicast channel can be decoded.

[0643] As an example of the disclosure, the processing order of the unicast PDSCH can be determined according to the order of OFDM. If additional processing of the MBS PDSCH is possible, the PDSCH to be processed can be determined according to the starting OFDM symbol, or it can be determined whether to process the MBS PDSCH following the unicast channel with priority.

[0644] When priorities are configured / defined between channels, the high-priority (unicast) channel can be decoded according to the OFDM symbol order. If the sum of the number of PRBs of the high-priority channel does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the decoding / dropping order of the MBS PDSCH can also be determined in sequence according to the OFDM symbol order. However, this is only one embodiment, and the MBS PDSCH can be processed with priority.

[0645] The operation according to Embodiment 14 can be applied only when another PDSCH is scheduled in slot n+1 in (a) of Figure 15 In the case where the total number of PRBs of the unicast PDSCH does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, if additional processing of the MBS channel is required, the eRedCap UE can process each MBS channel in sequence according to the OFDM symbol order. That is, the eRedCap UE can decode each channel within a 5 MHz bandwidth.

[0646] For example, if there is an MBS PDSCH exceeding the number of PRBs corresponding to a 5 MHz bandwidth, the MBS PDSCH and all PDSCHs scheduled after the MBS PDSCH can be dropped.

[0647] For example, in the case of (a) of Figure 15 Since the MBS PDSCH has 8 PRBs, the processing of the subsequent MBS PDSCH can not be completed. In addition, in the case of (b) of Figure 15 Since the MBS PDSCH has 6 PRBs, the corresponding PDSCH can be processed.

[0648] The above-described embodiments can be applied regardless of whether the MBS PDSCH and the unicast PDSCH are TDMed with each other or whether the MBS PDSCH and the unicast PDSCH overlap in the OFDM symbol.

[0649] The eRedCap UE can transmit UE capability information including the number of MBS PDSCHs and unicast PDSCHs that can be processed in a single slot or consecutive slots to the base station. In this case, in addition to the above-described capability information, UE capability information can be defined separately for the eRedCap UE.

[0650] Further, for the MBS PDSCH and unicast PDSCH that cannot be decoded due to being discarded, a NACK can be transmitted from the UE to the base station.

[0651] The above-described embodiments can be applied regardless of whether the MBS PDSCH and unicast PDSCH overlap within a single slot, and regardless of whether the sum of the number of PRBs of the channels exceeds the number of PRBs corresponding to a 5 MHz bandwidth. That is, the above-described embodiments can be applied even if only one or more MBS PDSCHs / unicast PDSCHs are scheduled in the same slot.

[0652] For example, in Embodiment 14, even if the total number of PRBs of the MBS PDSCH scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, decoding of the MBS PDSCH is possible if there is no other PDSCH in the next slot (e.g., slot n+1).

[0653] As another example, in Embodiment 15, even if the sum of the number of PRBs of the PDSCH scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, whether to discard a channel among the MBS PDSCH channels can be determined according to the above-described embodiments regardless of whether a PDSCH is scheduled in the next slot.

[0654] For example, if channel discarding is required, the eRedCap UE can decide which PDSCH among the remaining MBS PDSCHs and unicast PDSCHs (excluding the MBS PDSCHs exceeding the 5 MHz bandwidth) within the 5 MHz bandwidth to process.

[0655] General devices to which the present disclosure can be applied

[0656] Figure 10 A block diagram of a wireless communication device according to an embodiment of the disclosure is illustrated.

[0657] Referring to Figure 10 , the first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals through various radio access technologies (e.g., LTE, NR).

[0658] The first wireless device 100 can include one or more processors 102 and one or more memories 104, and can additionally include one or more transceivers 106 and / or one or more antennas 108. The processor 102 can control the memory 104 and / or the transceiver 106, and can be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in the disclosure.

[0659] For example, the processor 102 can process information in the memory 104 to generate first information / signal, and then transmit a wireless signal including the first information / signal through the transceiver 106. Also, the processor 102 can receive a wireless signal including second information / signal through the transceiver 106, and then store information obtained from signal processing of the second information / signal in the memory 104.

[0660] The memory 104 can be connected to the processor 102 and can store various information related to the operation of the processor 102. For example, the memory 104 can store software codes including commands for performing all or part of processes controlled by the processor 102 or for performing descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor 102 and the memory 104 can be a part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 can be connected to the processor 102 and can transmit and / or receive a wireless signal through one or more antennas 108. The transceiver 106 can include a transmitter and / or a receiver. The transceiver 106 can be used together with an RF (Radio Frequency) unit. In the present disclosure, a wireless device can mean a communication modem / circuit / chip.

[0661] The second wireless device 200 can include one or more processors 202 and one or more memories 204, and can additionally include one or more transceivers 206 and / or one or more antennas 208. The processor(s) 202 can control the memory(s) 204 and / or the transceiver(s) 206, and can be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. For example, the processor(s) 202 can generate third information / signal by processing information in the memory(s) 204, and then transmit a wireless signal including the third information / signal through the transceiver(s) 206. Also, the processor(s) 202 can receive a wireless signal including fourth information / signal through the transceiver(s) 206, and then store information obtained by signal processing of the fourth information / signal in the memory(s) 204. The memory(s) 204 can be connected to the processor(s) 202 and can store various information related to operations of the processor(s) 202. For example, the memory(s) 204 can store software code including commands for performing all or part of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure. Here, the processor(s) 202 and the memory(s) 204 can be part of a communication modem / circuitry / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver(s) 206 can be connected to the processor(s) 202 and can transmit and / or receive a wireless signal through the one or more antennas 208. The transceiver(s) 206 can include a transmitter and / or a receiver. The transceiver(s) 206 can be used together with an RF unit. In the present disclosure, a wireless device can mean a communication modem / circuitry / chip.

[0662] Hereinafter, the hardware elements of the wireless devices 100, 200 will be described in more detail. Without limitation, one or more protocol layers can be implemented by the one or more processors 102, 202. For example, the one or more processors 102, 202 can implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). The one or more processors 102, 202 can generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts included in the present disclosure. The one or more processors 102, 202 can generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. The one or more processors 102, 202 can generate signals (e.g., baseband signals) including the PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure to provide the same to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure.

[0663] The one or more processors 102, 202 can be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102, 202 can be implemented by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processors Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) can be included in the one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure can be implemented by using firmware or software, and the firmware or software can be implemented as including modules, procedures, functions, and the like. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts in the present disclosure can be included in the one or more processors 102, 202, or can be stored in the one or more memories 104, 204 and driven by the one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure can be implemented by using firmware or software in the form of codes, commands, and / or command sets.

[0664] One or more memories 104, 204 can be connected to one or more processors 102, 202 and can store data, signals, messages, information, programs, codes, instructions, and / or commands in various forms. One or more memories 104, 204 can be configured with ROM, RAM, EPROM, flash memory, hard drives, registers, cache memories, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 can be located internal and / or external to one or more processors 102, 202. In addition, one or more memories 104, 204 can be connected to one or more processors 102, 202 by various technologies such as wired or wireless connections.

[0665] The one or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc. mentioned in the methods and / or operational flowcharts, etc. of the disclosure to one or more other apparatuses. The one or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts, etc. disclosed in the disclosure from one or more other apparatuses. For example, the one or more transceivers 106, 206 can be connected to the one or more processors 102, 202 and can transmit and receive wireless signals. For example, the one or more processors 102, 202 can control the one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other apparatuses. In addition, the one or more processors 102, 202 can control the one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other apparatuses. In addition, the one or more transceivers 106, 206 can be connected to the one or more antennas 108, 208, and the one or more transceivers 106, 206 can be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts, etc. disclosed in the disclosure through the one or more antennas 108, 208. In the disclosure, the one or more antennas can be a plurality of physical antennas or a plurality of logical antennas (for example, antenna ports). The one or more transceivers 106, 206 can convert received wireless signals / channels, etc. from RF band signals to baseband signals to process received user data, control information, wireless signals / channels, etc. by using the one or more processors 102, 202. The one or more transceivers 106, 206 can convert user data, control information, wireless signals / channels, etc. processed by using the one or more processors 102, 202 from baseband signals to RF band signals. Accordingly, the one or more transceivers 106, 206 can include (analog) oscillators and / or filters.

[0666] The above-described embodiments are combinations of elements and features of the disclosure in a predetermined form. Each of the elements or features should be considered selectively unless explicitly mentioned otherwise. Each of the elements or features can be implemented in a form not combined with the other elements or features. In addition, embodiments of the disclosure can include a combination of some elements and / or features. The order of the operations described in the embodiments of the disclosure can be changed. Some elements or features of one embodiment can be included in other embodiments, or can be replaced with corresponding elements or features of other embodiments. It is obvious that the embodiments can include claims not explicitly mentioned in relation to other claims, or can be included as new claims by modification after the application.

[0667] It will be apparent to those skilled in the relevant arts that the present disclosure can be implemented in other specific forms without departing from the spirit or essential character of the disclosure. The detailed description is, therefore, not to be taken in a limiting sense. The scope of the present disclosure is defined by the reasonable interpretation of the appended claims, and all variations within the equivalency range of the disclosure are intended to be embraced thereby.

[0668] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that perform operations according to the methods of various embodiments, and non-transitory computer-readable media that cause the software or instructions, etc. to be stored and executable in an apparatus or computer. Commands that can be used to program processing systems to perform the features described in the present disclosure can be stored in a storage medium or computer readable medium and can be implemented as computer programs that are executable by the processing system. The storage medium can include high-speed random access memory such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, but is not limited to such and can include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory optionally includes one or more storage devices remotely located from the processing system. The memory, or alternatively the non-volatile memory device(s) within the memory, comprises a non-transitory computer readable storage medium. The features described in the present disclosure can be stored in any kind of machine readable medium to control the hardware of the processing system and can be integrated into software and / or firmware that allows the processing system to interact with other mechanisms with results from embodiments of the present disclosure. Such software or firmware can include application code, device drivers, operating systems, and execution environments / containers, but is not limited to such.

[0669] Here, the wireless communication technology implemented in the wireless device 100, 200 of the present disclosure can include narrowband Internet of Things for low-power communication and LTE, NR, and 6G. Here, for example, the NB-IoT technology can be an example of LPWAN (Low Power Wide Area Network) technology, can be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device 100, 200 of the present disclosure can perform communication based on LTE-M technology. Here, for example, the LTE-M technology can be an example of LPWAN technology and can be referred to by various names such as eMTC (enhanced Machine Type Communication) or the like. For example, the LTE-M technology can be implemented in at least any of various standards including 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device 100, 200 of the present disclosure can include at least any of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above names. For example, the ZigBee technology can generate a PAN (Personal Area Network) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 or the like, and can be referred to by various names.

[0670] Industrial applicability

[0671] The method proposed by the present disclosure is mainly explained based on examples applied to 3GPP LTE / LTE-A, 5G system, but can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A, 5G system.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising the following steps: In the first time slot, the first downlink channel and the second downlink channel are received from the base station; as well as Based on the fact that the number of Physical Resource Blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold, the first downlink channel and the second downlink channel are decoded. The first downlink channel and the second downlink channel partially or completely overlap in the time domain.

2. The method according to claim 1, wherein, The UE sends information to the base station indicating its ability to receive the first downlink channel and the second downlink channel in a single time slot using frequency division multiplexing (FDMed).

3. The method according to claim 1, wherein, The first downlink channel is the unicast Physical Downlink Shared Channel (PDSCH), and The second downlink channel is a multicast PDSCH or a broadcast PDSCH.

4. The method according to claim 1, wherein, The PRBs assigned to each of the first downlink and the second downlink do not overlap.

5. The method according to claim 1, wherein, Based on the subcarrier spacing SCS being configured to 15 kHz, the first threshold being 25, and Based on the SCS being configured to 30 kHz, the first threshold is 12.

6. The method according to claim 1, wherein, Decoding of one of the first downlink channel and the second downlink channel is skipped if the number of PRBs allocated to each of the first downlink channel and the second downlink channel exceeds the threshold.

7. The method according to claim 1, wherein, The first downlink channel is scheduled via first downlink control information (DCI). The first DCI is scrambled using cyclic redundancy check (CRC) using either the cell radio network temporary identifier (C-RNTI) or the configured scheduling CS-RNTI. The second downlink channel is scheduled through the second DCI, which performs CRC scrambling through the group G-RNTI or the multicast broadcast service control channel MCCH-RNTI.

8. The method according to claim 1, wherein, The UE is an enhanced redcap UE with enhanced redcap capability.

9. A method performed by a user equipment (UE) in a wireless communication system, the method comprising the following steps: Receive the first downlink channel from the base station in time slot n, where n is an integer greater than or equal to 0; and The reception of the first downlink channel is processed based on the fact that the number of Physical Resource Blocks (PRBs) allocated to the first downlink channel is less than or equal to a second threshold. Wherein, if the number of PRBs allocated to the first downlink channel exceeds the second threshold, and the reception of the first downlink channel is repeated reception or the second downlink channel is received in time slot n+1, the UE does not process the reception of the first downlink channel.

10. A user equipment (UE) in a wireless communication system, the UE comprising: At least one transceiver; as well as At least one processor, said at least one processor being coupled to said at least one transceiver, Wherein, the at least one processor is configured to: The at least one transceiver receives a first downlink channel and a second downlink channel from the base station in a first time slot; and Based on the fact that the number of Physical Resource Blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold, the first downlink channel and the second downlink channel are decoded. The first downlink channel and the second downlink channel partially or completely overlap in the time domain.

11. A method performed by a base station in a wireless communication system, the method comprising the following steps: Send information to the user equipment (UE) for scheduling the first downlink channel and the second downlink channel in the first time slot; as well as In the first time slot, the first downlink channel and the second downlink channel are transmitted to the UE. Wherein, based on the fact that the number of Physical Resource Blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold, the first downlink channel and the second downlink channel are decoded by the UE, and The first downlink channel and the second downlink channel partially or completely overlap in the time domain.

12. A base station in a wireless communication system, the base station comprising: At least one transceiver; as well as At least one processor, the at least one processor being coupled to the at least one transceiver; Wherein, the at least one processor is configured to: Information for scheduling a first downlink channel and a second downlink channel in a first time slot is transmitted to the user equipment (UE) via the at least one transceiver; and The first downlink channel and the second downlink channel are transmitted to the UE in the first time slot via the at least one transceiver. Wherein, based on the fact that the number of Physical Resource Blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold, the first downlink channel and the second downlink channel are decoded by the UE, and The first downlink channel and the second downlink channel partially or completely overlap in the time domain.

13. A processing apparatus configured to control a user equipment (UE) in a wireless communication system, the processing apparatus comprising: At least one processor; as well as At least one computer memory, operatively coupled to the at least one processor and storing instructions for performing operations when executed by the at least one processor. The operation includes: In the first time slot, the first downlink channel and the second downlink channel are received from the base station; and Based on the fact that the number of Physical Resource Blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold, the first downlink channel and the second downlink channel are decoded. The first downlink channel and the second downlink channel partially or completely overlap in the time domain.

14. At least one non-transitory computer-readable medium, said at least one non-transitory computer-readable medium storing at least one instruction, wherein, The at least one instruction executed by at least one processor controls a device in a wireless communication system to perform the following operations: In the first time slot, the first downlink channel and the second downlink channel are received from the base station; as well as Based on the fact that the number of Physical Resource Blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold, the first downlink channel and the second downlink channel are decoded. The first downlink channel and the second downlink channel partially or completely overlap in the time domain.

Images