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

The method for processing downlink channels in wireless communication systems addresses the challenges of high data traffic and latency by optimizing channel reception and scheduling based on resource block allocation, enhancing efficiency and data rate for reduced capability terminals.

WO2024237529A1PCT designated stage expired Publication Date: 2024-11-21LG ELECTRONICS INC

Patent Information

Application Number
PCT/KR2024/005875
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-11-02
Filing Date
2024-04-30
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in efficiently managing downlink transmission and reception, particularly in supporting high data traffic, increased transmission rates, and low latency while maintaining energy efficiency, especially with the growing demand for narrowband services.

Method used

The method involves a terminal and base station communication system where downlink channels are processed based on physical resource block allocation thresholds, allowing for simultaneous reception and decoding of unicast/multicast channels within a narrowband, with the option to repeat or skip channel reception based on allocated resource blocks, enabling efficient scheduling and processing of multiple channels in a single slot.

Benefits of technology

This approach enhances the processing efficiency of downlink channels for reduced capability terminals, allowing for improved data rate and power management, thereby supporting increased data traffic and low latency requirements in next-generation wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024005875_21112024_PF_FP_ABST
    Figure KR2024005875_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed are a method and an apparatus for communicating in a wireless communication system. A method performed by a terminal, according to one embodiment of the present disclosure, comprises the steps of: receiving a first downlink channel and a second downlink channel, in a first slot, from a base station; and decoding the first downlink channel and the second downlink channel, on the basis of the number of physical resource blocks (PRBs), which are allocated to each of the first downlink channel and the second downlink channel, being less than or equal to a first threshold value, wherein the first downlink channel and the second downlink channel may partially or totally overlap in a time domain.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for performing downlink transmission and reception in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for performing downlink transmission and reception in a narrowband in a wireless communication system.

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users' demand for higher-speed services, necessitating a more advanced mobile communication system.

[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

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

[0005] The technical problem of the present disclosure is to provide a method and device for transmitting and receiving at least one unicast / multicast downlink in a narrowband.

[0006] The technical problem of the present disclosure is to provide a method and device for processing multiple unicast / multicast downlinks received simultaneously in a narrowband.

[0007] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0008] According to one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system includes the steps of: 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 to each of the first downlink channel and the second downlink channel being less than or equal to a first threshold, wherein the first downlink channel and the second downlink channel may partially or totally overlap in the time domain.

[0009] According to one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system includes the steps of: receiving a first downlink channel from a base station in slot n (where n is an integer greater than or equal to 0); and processing reception of the first downlink channel based on a number of physical resource blocks (PRBs) allocated to the first downlink channel being less than or equal to a second threshold; wherein reception of the first downlink channel may not be processed by the terminal based on the number of PRBs allocated to the first downlink channel exceeding the second threshold and reception of the first downlink channel being a repetitive reception or a second downlink channel being received in slot n+1.

[0010] According to one embodiment of the present disclosure, a method performed by a base station in a wireless communication system includes the steps of: transmitting information for scheduling a first downlink channel and a second downlink channel to a terminal in a first slot; and transmitting the first downlink channel and the second downlink channel to the terminal in the first slot, wherein the first downlink channel and the second downlink channel are decoded by the terminal 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, and the first downlink channel and the second downlink channel may partially or fully overlap in the time domain.

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

[0012] According to various embodiments of the present disclosure, a method and apparatus for transmitting and receiving at least one unicast / multicast downlink in a narrowband may be provided.

[0013] According to various embodiments of the present disclosure, a method and apparatus for processing multiple unicast / multicast downlinks received simultaneously in a narrowband can be provided.

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

[0015] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0016] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

[0017] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0018] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0019] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0020] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied.

[0021] FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0022] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.

[0023] FIG. 7 is a diagram for explaining a process in which a terminal performs communication according to one embodiment of the present disclosure.

[0024] FIG. 8 is a diagram for explaining a process in which a base station performs communication according to one embodiment of the present disclosure.

[0025] FIG. 9 is a diagram for explaining a case where multiple channels overlap in the time domain according to one embodiment of the present disclosure.

[0026] FIG. 10 is a diagram for explaining a case in which multiple channels do not overlap in the time domain according to one embodiment of the present disclosure.

[0027] FIG. 11 is a diagram for explaining a case in which an MBS PDSCH is repeatedly allocated in excess of a 5 MHz bandwidth according to one embodiment of the present disclosure.

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

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

[0030] FIG. 14 is a diagram illustrating a case in which multiple channels are scheduled in a single slot according to one embodiment of the present disclosure.

[0031] FIG. 15 is a diagram for explaining a case in which PRBs exceeding the number of PRBs corresponding to a 5 MHz bandwidth are scheduled in one slot according to one embodiment of the present disclosure.

[0032] FIG. 16 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0033] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

[0034] In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

[0035] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0036] In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0037] The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and / or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of " / " between words in this disclosure has the same meaning as "and / or" unless otherwise stated.

[0038] The present disclosure describes a wireless communication network or a wireless communication system, and an operation performed in a wireless communication network may be performed in a process of controlling the network and transmitting or receiving a signal from a device (e.g., a base station) that manages the wireless communication network, or may be performed in a process of transmitting or receiving a signal to or between terminals connected to the wireless network.

[0039] In the present disclosure, transmitting or receiving a channel means transmitting or receiving information or a signal through the channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

[0040] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0041] The following technologies can be used in various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA can be implemented using wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0042] For clarity, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS (Technical Specification) 36.xxx Release 8. Specifically, LTE technology after 3GPP TS 36.xxx Release 10 is referred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be referred to as a 3GPP system. "xxx" refers to a standard document detail number. LTE / NR may be collectively referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published prior to the present disclosure. For example, reference may be made to the following documents.

[0043] For 3GPP LTE, see TS 36.211 (Physical channels and modulation), TS 36.212 (Multiplexing and channel coding), TS 36.213 (Physical layer procedures), TS 36.300 (General description), and TS 36.331 (Radio resource control).

[0044] For 3GPP NR, see 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 (Overall description of NR and New Generation-Radio Access Network (NG-RAN)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0045] Abbreviations for terms that may be used in this disclosure are defined as follows.

[0046] - BM: beam management

[0047] - CQI: Channel Quality Indicator

[0048] - CRI: Channel state information - reference signal resource indicator

[0049] - CSI: Channel State Information

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

[0051] - CSI-RS: Channel state information - reference signal

[0052] - DMRS: Demodulation Reference Signal

[0053] - FDM: frequency division multiplexing

[0054] - FFT: fast Fourier transform

[0055] - IFDMA: interleaved frequency division multiple access

[0056] - IFFT: inverse fast Fourier transform

[0057] - L1-RSRP: Layer 1 reference signal received power

[0058] - L1-RSRQ: Layer 1 reference signal received quality

[0059] - MAC: Medium Access Control

[0060] - NZP: non-zero power

[0061] - OFDM: orthogonal frequency division multiplexing

[0062] - PDCCH: Physical downlink control channel

[0063] - PDSCH: Physical downlink shared channel

[0064] - PMI: precoding matrix indicator

[0065] - RE: resource element

[0066] - RI: Rank indicator

[0067] - RRC: Radio Resource Control

[0068] - RSSI: Received signal strength indicator

[0069] - Rx: Reception

[0070] - QCL: quasi co-location

[0071] - SINR: signal to interference and noise ratio

[0072] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH))

[0073] - TDM: Time Division Multiplexing

[0074] - TRP: transmission and reception point

[0075] - TRS: Tracking Reference Signal

[0076] - Tx: transmission

[0077] - UE: user equipment

[0078] - ZP: Zero Power

[0079] System General

[0080] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications compared to existing radio access technologies (RATs) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs that consider enhanced mobile broadband communication (eMBB), massive MTC (MMTC), and Ultra-Reliable and Low Latency Communication (URLLC) is being discussed. For convenience, these technologies are referred to as NR in this disclosure. NR is an expression representing an example of 5G RAT.

[0081] A new RAT system, including NR, uses OFDM or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, a single cell may support multiple numerologies. That is, terminals operating under different numerologies can coexist within a single cell.

[0082] A numerology corresponds to a single subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0083] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0084] Referring to Fig. 1, the NG-RAN consists of gNBs that provide 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 control plane (RRC) protocol termination for UE. The gNBs are interconnected via Xn interfaces. The gNBs are also connected to the NGC (New Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Function) via the N2 interface and to the UPF (User Plane Function) via the N3 interface.

[0085] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0086] NR systems can support multiple numerologies. Numerologies can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). Furthermore, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band. Furthermore, NR systems can support various frame structures corresponding to multiple numerologies.

[0087] Below, we examine OFDM numerologies and frame structures that can be considered in NR systems. The various OFDM numerologies supported in NR systems can be defined as shown in Table 1 below.

[0088] μΔf=2 μ ·15 [kHz]CP015 Normal 130 Normal 260 Normal, Extended 3120 Normal 4240 Normal

[0089] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands. When the SCS is 30 kHz / 60 kHz, it supports dense urban areas, lower latency, and wider carrier bandwidth. When the SCS is 60 kHz or higher, it supports a bandwidth larger than 24.25 GHz to overcome phase noise. The NR frequency band is defined by two types of frequency ranges (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. In addition, FR2 can mean millimeter wave (mmW).

[0090] Frequency Range Designation Corresponding Frequency Range Subcarrier Spacing FR1410MHz - 7125MHz 15, 30, 60kHz FR224250MHz - 52600MHz 60, 120, 240kHz

[0091] Regarding the frame structure in the NR system, the sizes of the various fields in the time domain are T c =1 / (Δf max ·N f ) is expressed as a multiple of the time unit. Here, Δf max =480·10 3 Hz and N f =4096. Downlink and uplink transmissions are T f =1 / (Δf max Nf / 100)·T c = It is organized into radio frames with a duration of 10ms. Here, each radio frame is T sf =(Δf max N f / 1000)·T c =1ms It consists of 10 subframes with an interval of . In this case, there may be one set of frames for uplink and one set of frames for downlink. In addition, transmission in uplink frame number i from a terminal is T earlier than the start of the corresponding downlink frame from the terminal. TA =(N TA +N TA,offset )T c It should start before. For the subcarrier spacing configuration μ, slots are n within a subframe. s μ ∈{0,..., N slot subframe,μ-1} are numbered in increasing order, and n within a radio frame. s,f μ ∈{0,..., N slot frame,μ -1} are numbered in increasing order. One slot is N symb slot It consists of consecutive OFDM symbols, and N symb slot is determined by CP. Slot n in subframe s μ The start of OFDM symbol n in the same subframe s μ N symb slotare aligned temporally with the start of the OFDM symbol. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or uplink slot can be used. Table 3 shows the number of OFDM symbols per slot (N) in a general CP. symb slot ), the number of slots per wireless frame (N slot frame,μ ), number of slots per subframe (N slot subframe,μ), and Table 4 shows the number of OFDM symbols per slot in the extended CP, the number of slots per radio frame, and the number of slots per subframe.

[0092] μN symb slot N slot frame,μ N slot subframe,μ01410111420221440431480841416016

[0093] μN symb slot N slot frame,μ N slot subframe,μ212404

[0094] FIG. 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, 1 subframe can include 4 slots. 1 subframe={1,2,4} slots illustrated in FIG. 2 is an example, and the number of slot(s) 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 fewer symbols. With respect to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered. Hereinafter, the physical resources that can be considered in an NR system will be described in detail. First, with respect to antenna ports, antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. If a large-scale property of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on another antenna port is carried, then two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale property includes one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing. FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0095] Referring to Figure 3, the resource grid is N in the frequency domain. RB μ N sc RB It consists of subcarriers, and one subframe is 14·2 μ It is described as an example, but not limited to, that it consists of OFDM symbols. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids consisting of subcarriers and 2 μ N symb (μ) is described by OFDM symbols. Here, N RB μ≤ N RB max,μ is. The above N RB max,μ represents the maximum transmission bandwidth, which may vary between uplink and downlink as well as between numerologies. In this case, one resource grid may be configured for μ and each antenna port p. Each element of the resource grid for μ and each antenna port p is referred to as a resource element and is uniquely identified by an index pair (k, l'). Here, k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, and l'=0,...,2 μ N symb (μ) -1 indicates the position of the symbol within the subframe. When indicating a resource element in a slot, the index pair (k,l) is used.

[0096] Here, l=0,...,N symb μ -1. The resource element (k,l') for μ and antenna port p is a complex value ak,l' (p,μ) . If there is no risk of confusion or if a particular antenna port or numerology is not specified, the indices p and μ can be dropped, resulting in a complex value of a k,l' (p) or a k,l' This can be. Also, a resource block (RB) is N in the frequency domain. sc RB =12 is defined as consecutive subcarriers.

[0097] Point A serves as a common reference point of the resource block grid and is obtained as follows.

[0098] - offsetToPointA for the Primary Cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the UE for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

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

[0100] Common resource blocks (CRBs) are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of CRB 0 for a subcarrier spacing setting μ coincides with 'point A'. CRB number n in the frequency domain CRB μThe relationship between the resource elements (k,l) and the subcarrier spacing setting μ is given by the following mathematical expression 1.

[0101]

[0102] In Equation 1, k is defined relative to point A such that k = 0 corresponds to the subcarrier centered at point A. Physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). BWP,i size,μ - Numbered from -1, where i is the number of the BWP. Physical resource block n in BWP i PRB and common resource block n CRB The relationship between them is given by the mathematical formula 2 below.

[0103]

[0104] N BWP,i start,μ is a common resource block where BWP starts relative to common resource block 0.

[0105] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0106] Referring to FIGS. 4 and 5, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot includes seven symbols, but in the case of an extended CP, one slot includes six symbols.

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

[0108] The NR system can support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, when considering multiple use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band within the CC. Alternatively, each terminal may have different maximum bandwidth capabilities. Considering this, the base station can instruct the terminal to operate only on a portion of the bandwidth rather than the entire bandwidth of the wideband CC, and this portion of bandwidth is conveniently defined as the bandwidth part (BWP). A BWP can be composed of consecutive RBs on the frequency axis and can correspond to a single numerology (e.g., subcarrier spacing, CP length, slot / mini-slot interval).

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

[0110] Additionally, the base station can instruct switching to another configured DL / UL BWP (e.g., via L1 signaling or MAC CE or RRC signaling). Alternatively, switching to a configured DL / UL BWP can be performed based on a timer when the timer value expires. In this case, the activated DL / UL BWP is defined as the active DL / UL BWP. However, in situations such as when the terminal is performing the initial access process or before the RRC connection is set up, the configuration for the DL / UL BWP may not be received. Therefore, in these situations, the DL / UL BWP assumed by the terminal is defined as the initially active DL / UL BWP.

[0111] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.

[0112] In wireless communication systems, terminals receive information from a base station via the downlink and transmit it to the base station via the uplink. The information transmitted and received between the base station and terminals includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0113] When a terminal is powered on or enters a new cell, it performs an initial cell search operation, such as synchronizing with the base station (S601). To this end, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell identifier (ID). Afterwards, the terminal can receive a physical broadcast channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search phase to check the downlink channel status.

[0114] A terminal that has completed initial cell search can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried on the PDCCH (S602).

[0115] Meanwhile, when accessing a base station for the first time or when there are no radio resources for signal transmission, the terminal may perform a random access procedure (RACH) for the base station (steps S603 to S606). To this end, the terminal may transmit a specific sequence as a preamble via the Physical Random Access Channel (PRACH) (steps S603 and S605) and receive a response message to the preamble via the Physical Data Channel Control Channel (PDCCH) and the corresponding PDSCH (steps S604 and S606). In the case of a contention-based RACH, a contention resolution procedure (Contention Resolution Procedure) may additionally be performed.

[0116] The terminal that has performed the procedure described above can then perform PDCCH / PDSCH reception (S607) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S608) as general uplink / downlink signal transmission procedures. In particular, the terminal receives downlink control information (DCI) through the PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on the purpose of use.

[0117] Meanwhile, the control information that the terminal transmits to the base station via the uplink or that the terminal receives from the base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In the case of the 3GPP LTE system, the terminal can transmit the above-described control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0118] Table 5 shows an example of the DCI format in the NR system.

[0119] DCI Format Utilization 0_0 Scheduling of PUSCH within a cell 0_1 Scheduling of one or multiple PUSCH within a cell, or indicating cell group (CG: cell group) downlink feedback information to the UE 0_2 Scheduling of PUSCH within a cell 1_0 Scheduling of PDSCH within a DL cell 1_1 Scheduling of PDSCH within a cell 1_2 Scheduling of PDSCH within a cell

[0120] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to scheduling of PUSCH (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid - Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined. DCI format 0_0 is used for scheduling of PUSCH in one cell. Information included in DCI format 0_0 is transmitted after being CRC (cyclic redundancy check) scrambled by C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI). DCI format 0_1 ​​is used to indicate scheduling of one or more PUSCHs in one cell, or configured grant (CG: configure grant) downlink feedback information to a UE. Information included in DCI format 0_1 ​​is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI.

[0121] DCI format 0_2 is used for scheduling PUSCH in a cell. The information contained in DCI format 0_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0122] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to scheduling of PDSCH (e.g., frequency resource allocation, time resource allocation, virtual resource block (VRB)-physical resource block (PRB) mapping, etc.), transport block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., antenna port, transmission configuration indicator (TCI), sounding reference signal (SRS) request, etc.), PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format may be predefined.

[0123] DCI format 1_0 is used for scheduling PDSCH in a DL cell. The information contained in DCI format 1_0 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0124] DCI format 1_1 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_1 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0125] DCI format 1_2 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0126] (e) Downlink transmission and reception method of RedCap terminal

[0127] As described above, services that consider eMBB, URLLC, and the massive Internet of Things (mIoT) are being provided on wireless communication systems (e.g., NR). For example, hybrid services that consider eMBB, URLLC, and mIoT may also be provided on wireless communication systems. Here, mIoT requires optimization of power consumption rather than high performance (e.g., high transmission speeds) such as carrier aggregation.

[0128] With the recent widespread use of smart factories and / or wearable devices, the need for new terminal types that take low power and URLLC into account is increasing. Accordingly, reduced capability (RedCap) terminals (i.e., R17 RedCap terminals) were introduced in 3GPP NR Release 17. RedCap terminals can perform communications using frequency resources in a narrow spectrum or narrow bandwidth. For example, RedCap terminals can reduce power consumption and cost by utilizing up to 20 MHz or 5 MHz of bandwidth instead of the conventional 100 MHz bandwidth.

[0129] Subsequently, eRedCap terminals were introduced in 3GPP NR Release 18. eRedCap terminals are similar to RedCap terminals in that they operate in a 20 MHz bandwidth. However, in the case of eRedCap terminals, 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 a unicast PUSCH / PDSCH corresponding to a bandwidth of up to 5 MHz can be allocated to an eRedCap terminal. At this time, the unicast PUSCH / PDSCH can be indicated / allocated to an eRedCap terminal through the FDRA (frequency domain resource assignment) field of the DCI, etc.

[0130] Additionally, for eRedCap terminals, various RNTI-based channels related to paging, system information block (SIB), RACH, etc. can be allocated within a 20 MHz bandwidth. That is, PRBs of various RNTI-based channels corresponding to a maximum bandwidth of 20 MHz can be allocated to eRedCap terminals (same as RedCap terminals).

[0131] An eRedCap terminal can process data (e.g., PRBs) corresponding to a bandwidth of up to 5 MHz within a unit slot. If a channel exceeding 5 MHz of bandwidth is scheduled / allocated, the eRedCap terminal may require additional processing time margin. For unicast channels, scheduling can be performed per slot, so that an eRedCap terminal can be allocated PRBs corresponding to the maximum bandwidth (e.g., 5 MHz) (e.g., 25 PRBs when the SCS is 15 kHz or 12 PRBs when the SCS is 30 kHz).

[0132] Additionally, for RedCap terminals (i.e., R17 RedCap terminals introduced in 3GPP Release 17), unicast channels can be scheduled on a bandwidth of up to 20 MHz, and the maximum data rate (date rate) can be 500 Mbps. For eRedCap terminals (i.e., RedCap terminals introduced in 3GPP Release 18), unicast channels can be scheduled on a bandwidth of up to 20 MHz or a bandwidth of 5 MHz, and the maximum data rate (date rate) can be 10 Mbps. Various embodiments of the present disclosure can be applied to eRedCap terminals in which unicast channels can be scheduled on a bandwidth of up to 5 MHz. However, this is only one embodiment, and various embodiments of the present disclosure can also be applied to R17 RedCap terminals or eRedCap terminals in which unicast channels can be scheduled on a bandwidth of 20 MHz.

[0133] The present disclosure relates to a method for efficiently receiving a downlink (DL) channel (e.g., a group common channel, etc.) related to a multicast broadcasting service (MBS) by the above-described (e)RedCap terminal (i.e., a terminal using a BWP of up to 20 MHz). Here, the MBS-related DL channel may include a DL channel (e.g., a PDSCH, etc.) scheduled by a DCI that is CRC-scrambled by an MCCH (MBS control channel)-RNTI, a G(group)-RNTI, or a G(group)-CS-RNTI. In describing the present disclosure, the MBS channel may collectively refer to an MBS-related (DL / UL) channel.

[0134] Unlike unicast channels, MBS-related channels can be transmitted to multiple terminals simultaneously. If an eRedCap terminal receives an MBS-related channel within a 5 MHz bandwidth, it may be inefficient for other terminals (e.g., R17 RedCap terminals) that also receive the MBS-related channel. If an eRedCap terminal can receive and use the same 20 MHz bandwidth as other common channels, the likelihood of sharing the channel with other terminals increases, potentially improving network operation efficiency.

[0135] An MBS channel can have both the SIB broadcast and unicast characteristics of a common channel. Therefore, in describing the present disclosure, MBS channels will be categorized into broadcast / broadcast channels and multicast / multicast channels (based on bandwidth). Specifically, when an MBS channel is transmitted to an eRedCap terminal, restrictions may be applied to the bandwidth over which the MBS channel is transmitted. If the bandwidth over which the MBS channel is transmitted is not restricted, additional margin may be applied to the processing time of the MBS channel.

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

[0137] As an example of the present disclosure, if the MBS channel is a broadcast channel, the eRedCap terminal can be allocated / scheduled for the MBS channel within a bandwidth of up to 20 MHz, in the same manner as the SIB. At this time, the broadcast channel can be scheduled by a DCI that is CRC scrambled by an MCCH-RNTI or a G-RNTI. Since the eRedCap terminal can receive the SIB within a bandwidth of up to 20 MHz, the eRedCap terminal can also be allocated / scheduled for the broadcast channel to which the HARQ process (i.e., the ACK / NACK response transmission / reception process, etc.) is not applied, within a bandwidth of up to 20 MHz.

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

[0139]

[0140]

[0141] Additionally, if ACK / NACK information transmission is not configured for MBS-based multicast channels, 20 MHz may be optionally used.

[0142] Additionally, a method for configuring a multicast HARQ feedback mode in the above-described methods may exist. For example, RRC signaling configuring an MBS-based HARQ mode may be transmitted to an eRedCap terminal, and the RRC signaling may include information disclosed in Table 8 below.

[0143] MBS-RNTI-SpecificConfig-r17 ::= SEQUENCE {mbs-RNTI-SpecificConfigId-r17 MBS-RNTI-SpecificConfigId-r17,groupCommon-RNTI-r17 CHOICE {g-RNTI RNTI-Value,g-CS-RNTI RNTI-Value},drx-ConfigPTM-r17 SetupRelease { DRX-ConfigPTM-r17} OPTIONAL, -- Need Mharq-FeedbackEnablerMulticast-r17 ENUMERATED {dci-enabler, enabled} OPTIONAL, -- Need Sharq-FeedbackOptionMulticast-r17 ENUMERATED {ack-nack, nack-only} OPTIONAL, -- Cond HARQFeedbackpdsch-AggregationFactor-r17 ENUMERATED {n2, n4, n8} OPTIONAL -- Cond G-RNTI}

[0144] As an example of the present disclosure, an enabler of HARQ may 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 may be indicated. As another example, an operation / mode related to HARQ-ACK feedback may be indicated via a HARQ-ACK feedback indication enabling / disabling field included in DCI format 4_1. The HARQ-ACK feedback indication enabling / disabling field may be set to 1 bit when "harq-FeedbackOptionMulticast" indicates "dci-enabler". When the HARQ-ACK Feedback Indication Enable / Disable field value is set to 1, the activation of HARQ-ACK feedback is indicated, and when the HARQ-ACK Feedback Indication Enable / Disable field value is set to 0, the deactivation of HARQ-ACK feedback may be indicated. When the RRC signaling "Harq-FeedbackEnable rMulticast-r17" is not transmitted, HARQ feedback may always be disabled. "Harq-FeedbackEnablerMulticast" may indicate whether the terminal should provide HARQ feedback for MBS multicast. The "dci-enabler" value set by "Harq-FeedbackEnablerMulticast" may mean whether the terminal should provide HARQ feedback for MBS multicast. The present disclosure will explain a case where HARQ-related operations are controlled via RRC or DCI when HARQ feedback is disabled.

[0145] Additionally, the present disclosure may be applied to a terminal that is not capable of processing the entire bandwidth of RF and has a number of PRBs that can be processed in the BB baseband limited to the number of PRBs corresponding to a 5 MHz bandwidth.

[0146] Furthermore, the present disclosure can be applied to both terminals that simultaneously process two channels when two channels are scheduled in a single slot, or to terminals that cannot process either channel. Processing either channel may be more beneficial from a service perspective than not processing both channels at all. Therefore, the present disclosure describes a method for prioritizing and simultaneously receiving two channels.

[0147] As an example of the present disclosure, an eRedCap terminal may not expect simultaneous scheduling of multiple channels in the same slot. Simultaneous scheduling / reception of multiple channels may include cases where the multiple channels overlap or do not overlap on an OFDM symbol. Furthermore, a PDSCH scheduled by an SI-RNTI may be based on the acquisition of a P-RNTI-triggered SI.

[0148] FIG. 7 is a diagram illustrating a process of a terminal performing communication according to one embodiment of the present disclosure. The terminals of FIGS. 7 and 8 may be, but are not limited to, enhanced reduced capability (eRedCap) terminals (i.e., terminals that support R18 redCap terminals). The terminals of FIG. 7 may include RedCap terminals or general terminals.

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

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

[0151] Accordingly, the base station can identify that the terminal can receive the first downlink channel and the second downlink channel, which are FDMed in a single slot. The base station can transmit information for scheduling the first downlink channel and the second downlink channel to the terminal in the first slot. In addition, the base station can transmit the first downlink channel and the second downlink channel to the terminal in the first slot.

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

[0153] And, the first downlink channel may be scheduled by first downlink control information (DCI) CRC-scrambled by C(cell)-RNTI or CS(configured scheduling)-RNTI, and the second downlink channel may be scheduled by second DCI CRC-scrambled by G(group)-RNTI or MCCH(MBS control channel)-RNTI.

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

[0155] Here, the first downlink channel and the second downlink channel may partially or completely overlap in the time domain. Furthermore, the PRBs allocated to each of the first downlink and the second downlink may not overlap (in the frequency domain).

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

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

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

[0159] The method described in the example of FIG. 7 can be performed by the first device (100) and the second device (200) of FIG. 16. That is, the terminal can be implemented as the first device (100) of FIG. 16, and the base station can be implemented as the second device (200). For example, one or more processors (102) of the first device (100) of FIG. 16 can receive the first downlink channel and the second downlink channel from the second device (200) in the first slot through one or more transceivers. That is, one or more processors (202) of the second device (200) can transmit the first downlink channel and the second downlink channel to the first device (100) through one or more transceivers (206). 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, one or more processors (102) can decode the first downlink channel and the second downlink channel.

[0160] Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 8 or the examples described below when executed by one or more processors (102).

[0161] FIG. 8 is a diagram for explaining a process in which a terminal performs communication according to one embodiment of the present disclosure.

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

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

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

[0165] Based on the number of PRBs allocated for the first downlink channel being less than or equal to the second threshold, the terminal can process reception of the first downlink channel (S820).

[0166] That is, based on the number of PRBs allocated for the first downlink channel being less than or equal to the second threshold, the terminal can process / decode scheduling of the first downlink channel.

[0167] Here, the second threshold value may be determined differently depending on the SCS value, similar to the first threshold value of FIG. 7. For example, based on the SCS being set to 15 kHz, the second threshold value may be 25. And, based on the SCS being set to 30 kHz, the first threshold value may be 12.

[0168] 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 repetitive reception or the second downlink channel is received in slot n+1, the reception of the first downlink channel may not be processed by the terminal. That is, 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 repetitive reception or the second downlink channel is received in slot n+1, the terminal may not be required to process the first downlink channel received in slot n.

[0169] The method described in the example of FIG. 9 can be performed by the first device (100) and the second device (200) of FIG. 16. That is, the terminal can be implemented as the first device (100) of FIG. 16, and the base station can be implemented as the second device (200). For example, one or more processors (102) of the first device (100) of FIG. 16 can receive a first downlink channel from the second device (200) in slot n (where n is an integer greater than or equal to 0) through one or more transceivers (106). That is, one or more processors (202) of the second device (200) can transmit the first downlink channel to the first device (100) in slot n (where n is an integer greater than or equal to 0) through one or more transceivers (206). Based on the number of PRBs allocated for the first downlink channel being less than or equal to the second threshold, one or more processors (102) can process reception of the first downlink channel.

[0170] Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 9 or the examples described below when executed by one or more processors (102).

[0171] Below, we describe various methods for a terminal (e.g., an eRedCap terminal) to receive an MBS channel in a narrowband.

[0172] Example 1

[0173] Example 1 relates to a method of operating bandwidth differently depending on the HARQ feedback form of multicasting.

[0174] For broadcasting (or broadcast channels / transmissions), there is no HARQ feedback, so the procedure can proceed similarly to the SIB or paging information transmission and reception procedure. However, for multicasting, three HARQ feedback modes (e.g., ACK / NACK mode, Nack-only mode, and NO HARQ mode) can be set / proceeded.

[0175] Here, ACK / NACK mode is also applied to basic unicast transmission and reception procedures, and NO HARQ mode can be a general term for procedures in which ACK / NACK transmission is not performed, such as SIB or paging information transmission and reception procedures. NACK-only mode can be applied to MBS-based multicast channel transmission and reception procedures. NACK-only mode is a general term for a mode in which feedback information is not transmitted in an ACK situation, and NACK-based feedback is transmitted in a NACK situation.

[0176] As described above, for broadcast transmissions where HARQ ACK / NACK transmission is not configured, no additional relaxation procedure for processing time is required, so a bandwidth of up to 20 MHz can be utilized. However, in the case of ACK / NACK or NACK-only mode, additional relaxation time may be required when 20 MHz bandwidth is utilized. Therefore, in Embodiment 1, a bandwidth operation method according to the HARQ feedback type during multicast channel transmission and reception will be described.

[0177] Example 1-1

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

[0179] When the NO HARQ mode is set 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, multicasting 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 disabled mode is indicated via RRC signaling, multicasting operation can be performed within a bandwidth of up to 20 MHz.

[0180] Example 1-2

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

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

[0183] As an example of the present disclosure, 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 set via RRC signaling), thereby improving operational flexibility.

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

[0185] Additionally or alternatively, embodiments 1-1 and 1-2 may be configured to be utilized only when the terminal type is an eRedCap terminal via RRC signaling. As another example, the ACK / NACK mode or NACK-only mode may be configured to be applied exclusively to eRedCap terminals via RRC signaling.

[0186] 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 or NACK-only based transmission may 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 may not be performed. In this case, the network may recognize non-transmission of HARQ feedback as ACK or NACK.

[0187] Example 1-3

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

[0189] The above-described embodiment is a new HARQ mode, and the new HARQ mode can be set via RRC signaling for the eRedCap terminal. When the ACK / NACK mode or NACK-only mode is set, the base station can set a multicast channel with a number of PRBs greater than or less than the number corresponding to the 5 MHz bandwidth. In this case, if there is no HARQ feedback, the base station can recognize it as a NACK or ACK.

[0190] As another example of this, when the NACK-only mode is set, scheduling may be allowed for the number of PRBs corresponding to the 20 MHz bandwidth. Scheduling may be allowed for the number of PRBs corresponding to the 20 MHz bandwidth only when PUCCH resources for NACK-only based feedback transmission are set or when the NACK-only mode is set via RRC signaling.

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

[0192] Example 1-4

[0193] In one embodiment of the present disclosure, when MBS-related information is set (i.e., when broadcast or multicast data / channels are transmitted and received), repeated transmission may be performed / applied only within a specific bandwidth (e.g., 5 MHz BWP for eRedCap terminals). In this case, repeated operation may be performed only within the specific bandwidth, regardless of the presence or absence of HARQ feedback.

[0194] Example 1-5

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

[0196] Example 1-6

[0197] In one embodiment of the present disclosure, when repeated transmissions are performed, the HARQ feedback procedure may be omitted. In this case, when a multicast channel is transmitted and received, scheduling may be performed within the maximum bandwidth (e.g., up to 20 MHz for eRedCap terminals).

[0198] Example 1-7

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

[0200] Example 1-8

[0201] In one embodiment of the present disclosure, a multicast SPS PDSCH (i.e., an 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 a DCI CRC-scrambled with 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.

[0202] If more PRBs are scheduled than the number of PRBs corresponding to a given bandwidth by the initial PDCCH, PDSCH reception may be disrupted until SPS operation is deactivated. Therefore, SPS transmission may be restricted to a 5 MHz bandwidth.

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

[0204] When SPS transmission is enabled or disabled by 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, ACK / NACK transmission can also be performed when PRBs greater than the number of PRBs corresponding to a specific 5 MHz bandwidth are scheduled. In this case, when the base station instructs the eRedCap terminal to have a sufficient K1 value (i.e., a time delay value from the time when the PDSCH is transmitted until the ACK / NACK is transmitted) or cannot instruct an insufficient K1 value (i.e., when HARQ feedback transmission is difficult), the eRedCap terminal may unconditionally transmit NACK (e.g., skip or drop the PDSCH transmission) or perform an action according to the terminal implementation. As another example, a specific K1 value, x, can be indicated / defined / set, and the eRedCap terminal can expect a K1 greater than or equal to x. If a K1 less than or equal to x is indicated, the eRedCap terminal can transmit a NACK (e.g., skip or drop a PDSCH transmission) or perform an action depending on the terminal implementation.

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

[0206] Example 1-8

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

[0208] As an example of the present disclosure, when a HARQ process ID is disabled, a terminal (e.g., a non-RedCap terminal) is not expected to receive another PDCCH carrying a DCI that schedules a set of scheduled PDSCHs or slot aggregation PDSCHs for a given HARQ process or after reception of the last PDSCH or slot aggregation PDSCH for that HARQ process is finished. proc,1 For a given HARQ process starting from T , it may not be expected to receive another PDSCH without the corresponding PDCCH. That is, if consecutive PDCCHs are scheduled for the same HARQ process ID, the terminal may receive T proc,1During this time, it may not be expected to receive PDSCH or PDCCH. Meanwhile, since the eRedCap terminal can process PRBs corresponding to a 5 MHz bandwidth in a single slot, if PRBs exceeding the number corresponding to a 5 MHz bandwidth (e.g., PRBs of a multicast channel) are scheduled, additional time may be applied to the eRedCap terminal for PRB processing. Accordingly, the stability of multicast PDSCH processing of the eRedCap terminal may be increased.

[0209] Example 1-9

[0210] In one embodiment of the present disclosure, it is assumed that scheduling is performed continuously for inactive HARQ process IDs. Previously, T proc1 Additional processing time margin may be set / indicated for eRedCap terminals when scheduling PRBs higher than 5MHz (e.g., PRBs of multicast channels) is performed, although scheduling is not expected during that time.

[0211] For example, the processing time margin can be defined as 1 slot. That is, when a PRB corresponding to a 5MHz bandwidth is allocated, the terminal can be "T proc1 + 1 slot" (e.g., 1sm for 15 KHz SCS, 0.5ms for 30 KHz SCS) reception of another PDCCH may not be expected.

[0212] Example 1-10

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

[0214] Example 1-11

[0215] For eRedCap terminals, in the case of a disabled HARQ process ID, the process IDs may be restricted from being allocated consecutively.

[0216] Example 2

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

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

[0219] Example 2-1

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

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

[0222] As an example of the present disclosure, if a broadcast-based channel and a PDSCH scheduled with a DCI CRC-scrambled with a C-RNTI (hereinafter, a PDSCH associated with a C-RNTI) overlap in a single slot, the UE may drop the PDSCH associated with the C-RNTI. As another example, if a broadcast-based channel and a PDSCH scheduled with a DCI CRC-scrambled with a G-RNTI (hereinafter, a PDSCH associated with a G-RNTI) overlap in a single slot, the UE may drop the broadcast-based channel. However, this is only an embodiment, and if a broadcast-based channel and a PDSCH associated with a C-RNTI / G-RNTI overlap in a single slot, which channel to drop / skip may be predefined or set by an RRC signal.

[0223] Example 2-2

[0224] Example 2 relates to a terminal's handling when a multicast channel overlaps with another PDSCH. In this case, the multicast channel may be scheduled to a number of PRBs less than or equal to a 5 MHz bandwidth, regardless of the HARQ feedback mode, but this is not a limitation. In this case, the terminal can decode the entire channel, but eRedCap terminals may have difficulty decoding the entire channel. Therefore, the conditions described below may apply to Example 2.

[0225] For example, when HARQ feedback is configured for a multicast channel, the multicast channel can be scheduled for the number 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 the number of PRBs corresponding to a bandwidth of up to 20 MHz.

[0226] Example 2 relates to the processing operation of a terminal when a multicast channel overlaps with a unicast PDSCH in units of OFDM symbols in the time domain.

[0227] Furthermore, embodiment 2 can also be applied when ACK / NACK mode or NACK-only mode is set for MBS PDSCH (e.g., multicast PDSCH). In this case, feedback may not be transmitted from the terminal only when ACK / NACK mode is set. Feedback transmission may be performed differently depending on the terminal implementation, and HARQ feedback may be transmitted or omitted depending on the terminal capabilities.

[0228] Additionally, embodiment 2 can be applied when HARQ feedback disabling is set for multicasting.

[0229] Example 2-2-1

[0230] When a multicast channel overlaps with another PDSCH, the multicast channel may be scheduled to a number of PRBs less than or equal to a 5 MHz bandwidth, regardless of the HARQ feedback mode, but is not limited thereto. In this case, the terminal may not expect to decode multiple channels scheduled in a slot, and the method described below may be utilized.

[0231] As an example of the present disclosure, for MBS-based channels (e.g., broadcast-based channels and / or multicast channels), the scheduling described above may not be expected. For example, if HARQ deactivation mode is set for a multicast channel via RRC signaling, the terminal may decode the multicast channel and other PDSCH channels overlapping with the multicast channel. As another example, if HARQ deactivation mode is indicated for a multicast channel via DCI, the terminal may not expect the scheduling.

[0232] As another example of the present disclosure, a terminal may drop (or skip) an MBS-based channel (e.g., a broadcast-based channel or / and a multicast channel). When repeated transmission is performed, an MBS-based channel may be dropped (or skipped) on an OFDM symbol in an overlapping slot. For example, if an ACK / NACK mode or a NACK-only mode is set for a multicast channel, the terminal may drop (or skip) the multicast channel. As another example, if a HARQ deactivation mode is set for a multicast channel via RRC signaling (or DCI), the terminal may decode the multicast channel and another PDSCH channel overlapping with the multicast channel. As another example, if a HARQ deactivation mode is indicated for a multicast channel via DCI (or RRC signaling), the terminal may drop (or skip) the multicast channel.

[0233] Additionally or alternatively, if the sum of the 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 terminal may drop the multicast channel. In this case, the two channels may be FDMed in OFDM symbols. However, if the sum of the 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 terminal may decode both of the two channels.

[0234] Example 2-3

[0235] In one embodiment of the present disclosure, when the number of PRBs of a 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 terminal may skip without decoding either the multicast PDSCH or another channel overlapping with the multicast PDSCH. The method according to embodiment 2-3 may be used when the other channel overlapping with the multicast channel is a specific channel (e.g., a unicast PDSCH or paging triggered SI).

[0236] Example 2-4

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

[0238] Example 2-5

[0239] In one embodiment of the present disclosure, when HARQ feedback is set (for a multicast channel), the terminal may drop either the multicast PDSCH or another channel overlapping with the multicast PDSCH without decoding. The method according to embodiment 2-5 may be used when the other channel overlapping with the multicast channel is a specific channel (e.g., a unicast PDSCH or paging triggered SI).

[0240] Additionally, it is assumed that unicast PDSCH and multicast PDSCH overlap or do not overlap in a single slot in the time domain. In this case, if the sum of the PRBs of each of the unicast PDSCH and 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 terminal may transmit a NACK without decoding the multicast PDSCH. Accordingly, the terminal may induce retransmission from the base station.

[0241] Example 2-6

[0242] In one embodiment of the present disclosure, even if two channels (e.g., a unicast PDSCH and a multicast PDSCH, etc.) within one slot overlap or do not overlap 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 terminal may transmit a NACK as HARQ feedback for the multicast PDSCH or perform DTX processing for the multicast PDSCH.

[0243] 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 terminal can decode both the unicast PDSCH and the multicast PDSCH.

[0244] In Example 2-6, the "number of PRBs corresponding to a 5 MHz bandwidth" may be replaced with another specific value. Here, the other specific value may be determined / set by terminal capability information reported by the terminal to the base station or RRC signaling, and may also be predefined.

[0245] Example 2-7

[0246] In one embodiment of the present 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 terminal may decode the plurality of channels. In addition, the terminal may not expect a case where the sum of the number of PRBs allocated to a plurality of channels scheduled / allocated to a single slot exceeds the specific value.

[0247] For example, one of the plurality of channels may be a multicast channel (e.g., a multicast PDSCH). In addition, when the NO HARQ feedback mode is set, the terminal may decode two or more channels regardless of the number of PRBs of the MBS PDSCH.

[0248] As another example, if ACK / NACK mode or NACK-only mode is set for a multicast channel, the terminal may not expect the scheduling described above (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).

[0249] When HARQ deactivation mode is set for a multicast channel via RRC signaling (or DCI), the terminal can decode multiple channels overlapping in a single slot. Furthermore, when HARQ deactivation mode is indicated for a multicast channel via DCI (or RRC signaling), the terminal may not expect the scheduling described above.

[0250] Example 2-8

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

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

[0253] As another example, a terminal may transmit terminal capability information related to processing of an MBS channel and other channels overlapping it to the base station. Furthermore, the terminal may decode the MBS channel and other channels overlapping it in a single slot based on the terminal capabilities.

[0254] As another example, if the MBS channel is associated with the broadcast G-RNTI, the terminal can decode both the MBS channel and other channels. However, if the MBS channel is repeatedly transmitted, the terminal can drop the MBS channel.

[0255] As another example, if the MBS channel is a broadcast channel or a multicast channel, the terminal may not expect the scheduling described above. In this case, if the ACK / NACK mode or NACK-only mode is set for the multicast channel, the terminal may not expect the scheduling described above. If the HARQ disable mode is set for the multicast channel via RRC signaling, the terminal can decode both the multicast channel and other channels. If the HARQ disable mode is set for the multicast channel via DCI, the terminal may not expect the scheduling described above.

[0256] As another example, if the MBS channel is a broadcast channel or a multicast channel, the terminal may drop the MBS channel. For example, if the broadcast channel is a broadcast channel associated with MCCH-RNTI, the terminal may drop the unicast channel. If the MBS channel performs repeated transmission, the terminal may drop the MBS channel or the unicast channel in slots where overlap occurs between the MBS channel and the unicast channel. If the ACK / NACK mode or the NACK-only mode is set for the multicast channel, the terminal may drop the MBS channel or the unicast channel. If the HARQ disable mode is set for the multicast channel via RRC signaling, the terminal may decode both the multicast channel and other channels. If the HARQ disable mode is set for the multicast channel via DCI, the terminal may drop the multicast channel.

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

[0258] As another example, if the sum of PRBs of each of multiple 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 terminal may not perform feedback transmission for multiple channels or may process multiple channels as NACKs (when NACK-only or ACK / NACK is set).

[0259] As another example, if the sum of PRBs of each of multiple 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 NACK-only or ACK / NACK is set), feedback transmission for multiple channels may be performed depending on the terminal implementation.

[0260] Example 2-9

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

[0262] Example 2-10

[0263] Example 2-10 relates to a method in which unicast SPS PDSCH and multicast SPS PDSCH are transmitted overlapping on OFDM symbols in the same slot.

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

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

[0266] In another example of the present disclosure, one of a unicast channel (e.g., a unicast SPS PDSCH) and an MBS channel (e.g., a multicast SPS PDSCH) overlapping in the same slot may be dropped. Since the multicast SPS PDSCH is likely to have a lower priority than the unicast SPS channel, the terminal may drop the multicast SPS PDSCH, and the HARQ mode for the multicast SPS PDSCH may be set to a NO HARQ mode or a NACK may be transmitted for the multicast SPS PDSCH. However, among the unicast channel (e.g., a unicast SPS PDSCH) and the MBS channel (e.g., a multicast SPS PDSCH) overlapping in the same slot, the unicast channel may be dropped. That is, the priorities of the channels overlapping in the same slot may be defined / set in advance.

[0267] As another example of the present disclosure, even if the same multicast (SPS) channel overlaps the same slot, the terminal may perform the above-described operation (e.g., dropping one of the multiple multicast (SPS) channels, etc.). As another example, the terminal may not expect the same multicast (SPS) channel to overlap the same slot.

[0268] Example 3

[0269] Example 3 relates to a method of processing multicast PDSCH in an RRC_Inactive state and an SDT (small data transmission) situation.

[0270] MBS-based PDSCH may include multicast PDSCH and broadcast-based PDSCH. In the case of broadcast-based PDSCH, the method according to embodiment 1 may be applied even in the RRC_Inactive state. In a basic wireless communication system, multicasting operations (e.g., multicast PDSCH transmission and reception operations) may not be performed in the RRC_Inactive state. However, for service continuity, multicast PDSCH transmission and reception procedures may be possible in the RRC_Inactive state, and the above-described operations may be performed by a narrowband device (e.g., an eRedCap terminal).

[0271] Example 3-1

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

[0273] At this time, for eRedCap terminals, scheduling may be possible within a bandwidth of up to 20 MHz. For example, if HARQ feedback-related information / commands are transmitted via higher-layer signaling or DCI, the terminal may not receive the corresponding service (e.g., multicast PDSCH). As another example, a NACK-only mode other than the NO HARQ mode may be configured for eRedCap terminals, allowing eRedCap terminals to check the overall service status even in an idle state while receiving services.

[0274] Example 3-2

[0275] In one embodiment of the present disclosure, in the case of SDT in the RRC_Inactive state, unlike Embodiment 1, it may be possible to set a NACK-only mode or an ACK / NACK mode with feedback for a general terminal (i.e., a non-RedCap terminal) or an eRedCap terminal.

[0276] The RRC_Inactive state is similar to the RRC_Idle state, making it inappropriate to allocate all uplink resources for feedback to a specific terminal. However, while SDT services can generally be provided in the RRC_Idle state, terminals can momentarily perform operations similar to those in the RRC_Connected state. Therefore, for SDT services, a mode that enables feedback to the terminal can be configured.

[0277] Additionally or alternatively, due to its high complexity, the ACK / NACK mode may not be suitable for RRC_inactive. Therefore, for SDT, only the NACK_only mode, where common PUCCH resources are limited, may be applied.

[0278] Additionally or alternatively, when feedback-related information is configured for an eRedCap terminal, the entire bandwidth may be utilized, or the number of PRBs corresponding to a specific bandwidth may be scheduled, depending on the type and format of the feedback. In this case, the method applied to the multicast PDSCH in the RRC_Connected state of Embodiment 1 may be utilized.

[0279] Example 4

[0280] Example 4 relates to various methods for processing a broadcast channel. As described above, an eRedCap terminal can process a broadcast channel within a bandwidth of up to 20 MHz. In general, when a downlink channel is scheduled by DCI 4_0 CRC-scrambled by MCCH-RNTI, the data rate of the downlink channel is likely to not exceed 10 Mbps. Therefore, the number of PRBs allocated to an MCCH-RNTI-based broadcast channel may be limited to no more than the number of PRBs corresponding to a 5 MHz bandwidth. In addition, the number of PRBs allocated to a G-RNTI-based broadcast channel may be limited to no more than the number of PRBs corresponding to a 20 MHz bandwidth.

[0281] Example 4-1

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

[0283] Since MCCH-RNTI-based channels include control information, they may not require a wide bandwidth. Furthermore, whether MCCH-RNTI-based PDSCHs are scheduled for the number of PRBs corresponding to a 5 MHz bandwidth may be predefined, but is not limited thereto. Whether MCCH-RNTI-based PDSCHs are scheduled for the number of PRBs corresponding to a 20 MHz bandwidth may also be predefined or configured via higher-layer signaling.

[0284] Example 4-2

[0285] In one embodiment of the present disclosure, the maximum number of PRBs that can be allocated for a multicast channel can be flexibly set / indicated by upper layer signaling or / and DCI for each HARQ mode and / or each 5 / 20 MHz bandwidth. 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.

[0286] For example, let's assume that a multicast channel needs to be allocated within a 5 MHz bandwidth. In this case, if the base station indicates a PRB corresponding to the 5 MHz bandwidth (i.e., a PRB of the multicast channel) through the FDRA of the PDCCH, the terminal can transmit an ACK / NACK to the base station, or transmit a NACK to the base station (e.g., in the case of a NACK-only HARQ feedback mode).

[0287] For eRedCap terminals, the terminal capability information (e.g., "fdm-BroadcastUnicast-r17") indicating whether overlapping of group-common PDSCH and unicast PDSCH for broadcast in RRC_connected state within a single slot is supported may not be applied. Accordingly, simultaneous reception of different PDSCHs may be restricted for eRedCap terminals, and additional margin may be added for processing time relaxation.

[0288] Example 4-3

[0289] In one embodiment of the present disclosure, for an eRedCap terminal, simultaneous reception of a broadcast MBS channel and a unicast PDSCH may not be supported. That is, for a broadcast MBS channel and a unicast PDSCH, terminal capability information (e.g., "fdm-BroadcastUnicast-r17") may not be applied to the eRedCap terminal.

[0290] Example 4-4

[0291] In one embodiment of the present disclosure, for an eRedCap terminal, simultaneous reception of a multicast MBS channel (e.g., a multicast PDSCH) and a unicast PDSCH may not be supported. That is, for a multicast MBS channel and a unicast PDSCH, terminal capability information (e.g., "fdm-BroadcastUnicast-r17") may not be applied to the eRedCap terminal.

[0292] Example 4-5

[0293] In one embodiment of the present disclosure, when simultaneous reception of different PDSCHs is supported in the same slot (e.g., overlapping of group-common PDSCH and unicast PDSCH for broadcast in RRC_connected state is supported in a single slot), the number of PDSCHs that can be FDMed in the same slot can be determined by terminal capability. That is, the eRedCap terminal can transmit terminal capability information related to the number of PDSCHs that can be FDMed in the same slot to the base station. Accordingly, the eRedCap terminal 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.

[0294] Example 4-6

[0295] In one embodiment of the present disclosure, in case of repeated transmission of MBS PDSCH, an eRedCap terminal can expect that PRBs are allocated within the number of PRBs corresponding to a 5 MHz bandwidth, regardless of the setting of HARQ feedback.

[0296] When MBS PDSCH repetitive transmission is enabled, eRedCap terminals can store the initially received information by adding buffers across slots. When MBS PDSCH repetitive transmission is enabled, the maximum buffer may need to be continuously set for MBS PDSCH allocation across a 20MHz bandwidth. Therefore, when MBS PDSCH repetitive transmission is enabled, the number of PRBs allocated to eRedCap terminals may be limited to a number corresponding to a 5MHz bandwidth.

[0297] Example 4-7

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

[0299] Example 4-8

[0300] In one embodiment of the present disclosure, when ACK / NACK mode or NACK-only mode is set, the eRedCap terminal can expect that the SPS multicast PDSCH is allocated / scheduled within the number of PRBs corresponding to a maximum bandwidth of 5 MHz.

[0301] Example 4-9

[0302] In one embodiment of the present disclosure, in the case of multicasting and broadcasting, for narrowband communication (i.e., communication of eRedCap terminals), PRBs corresponding to a specific bandwidth within a slot may be allocated / scheduled. For example, in the case of eRedCap terminals, multicast channels and / or broadcast channels corresponding to a number of PRBs corresponding to a 5 MHz bandwidth may be allocated / scheduled, similar to unicast PDSCH.

[0303] Example 4-10

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

[0305] As an example of the present disclosure, in the case of MCCH-RNTI, HARQ feedback may always be disabled. MBS broadcasting operations exceeding the number of PRBs corresponding to a 5MHz bandwidth may be possible. The aforementioned operations may be restricted to be possible only when scheduled with MCCH_RNTI. In the case of G-RNTI, since data may be scheduled in each slot, eRedCap terminals that can only schedule PRBs corresponding to a 5MHz bandwidth may encounter decoding-related issues.

[0306] In another example of the present disclosure, in the case of G-RNTI, the number of PRBs corresponding to broadcasting and multicasting may be the same. For example, when HARQ feedback is disabled, PRBs (e.g., PRBs of multicast or multicast channels) greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth may be used in the RRC_connected state or RRC_inactve state. Disabling HARQ feedback may be set by 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 may be used. All MBS channels scheduled by G-RNTI may be restricted to be scheduled within 5 MHz. An eRedCap terminal may have difficulty decoding PRBs corresponding to a 5 MHz bandwidth within a channel with a high probability of being scheduled continuously.

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

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

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

[0310] Meanwhile, the "dl-DataToUL-ACK list" includes values ​​for processing HARQ feedback, and the terminal can expect that one K1 value is indicated among values ​​greater than or equal to a specific value sufficient for processing HARQ feedback. And, the terminal can expect that a channel (e.g., multicast (SPS) PDSCH) is scheduled by G-CS-RNTI based on the K1 value. Since the above case requires HARQ feedback, it can be applied only when a parameter related to HARQ feedback enabling (e.g., "harq-FeedbackEnablingforSPSactive") is activated.

[0311] Example 4-11

[0312] Example 4-11 relates to a terminal processing method when multiple PDSCHs are scheduled in a single slot, as in Example 2.

[0313] Example 4-11-1

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

[0315] In another example of the present disclosure, a broadcast PDSCH and a unicast PDSCH may be scheduled in a single slot only if the broadcast PDSCH is scheduled by the MCCH-RNTI. If the broadcast PDSCH is scheduled by the G-RNTI, the G-RNTI may be considered identical to the C-RNTI, and it may be difficult for an eRedCap terminal to process both channels simultaneously. Therefore, the terminal may not expect the G-RNTI-related broadcast PDSCH and unicast PDSCH to be scheduled simultaneously.

[0316] Example 4-11-2

[0317] Example 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., HARQ feedback is disabled via RRC signaling), the following options may be applied.

[0318] Option 1: eRedCap terminals can decode multicast PDSCH and unicast PDSCH scheduled in a single slot.

[0319] Option 2: eRedCap terminals may not expect scheduling of multicast PDSCH and unicast PDSCH in a single slot.

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

[0321] Option 4: An eRedCap terminal may drop or skip a unicast PDSCH among the multicast PDSCHs and unicast PDSCHs scheduled in a single slot. In this case, the eRedCap terminal may not receive the unicast channel until the next slot.

[0322] As another example of the present disclosure, when HARQ feedback is enabled, the following options may be applied.

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

[0324] Option 2: eRedCap terminals may not expect scheduling of multicast PDSCH and unicast PDSCH in a single slot.

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

[0326] Example 4-12

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

[0328] The above-described operation can be applied not only to G-RNTI but also to channels scheduled by MCCH-RNTI. Furthermore, the above-described operation can be applied even when the eRedCap terminal is in the RRC_Inactive or RRC_Idle state. Furthermore, the above-described operation can be applied not only to G-RNTI but also to PDSCH reception associated with SI-RNTI or P-RNTI-triggered SI acquisition.

[0329] Specifically, an eRedCap terminal can decode only a specific number of PRBs (e.g., the number of PRBs corresponding to a 5 MHz bandwidth) in a single slot. Therefore, if more than a specific number of PRBs (e.g., PRBs allocated to a PDSCH) are scheduled in a single slot, a gap slot (e.g., at least one slot) adjacent to the single slot may be required. Accordingly, if more than a specific number of PRBs are scheduled in a single slot, at least one slot adjacent to the single slot (i.e., the slot set as a gap) cannot be scheduled with another channel.

[0330] For example, assume that a certain number or more of PRBs are scheduled in slot n. In this case, if a channel or another PDSCH associated with G-RNTI (or / and MCCH-RNTI) is scheduled on slot n+1, the eRedCap terminal may skip or not decode the channel or other PDSCH associated with G-RNTI (or / and MCCH-RNTI).

[0331] As another example, if a PDSCH scheduled by MSG 2 or MSG B or P-RNTI related to a random access procedure is received in slot n+1, the eRedCap terminal may first process the channel scheduled in slot n+1 even if it processes the MBS PDSCH scheduled in slot n. That is, considering the priority of the PDSCH scheduled by MSG 2 or MSG B or P-RNTI related to a random access procedure, the eRedCap terminal may skip the MBS PDSCH in slot n or decoding of the MBS PDSCH in slot n may not be expected.

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

[0333] As another example, if a PDSCH scheduled for slot n+1 needs to be decoded, the eRedCap terminal may skip the MBS PDSCH scheduled for slot n or may not expect decoding of the MBS PDSCH. As another example, the eRedCap terminal may abort the process in slot n.

[0334] As another example, for a channel scheduled in slot n+1 (e.g., a channel with HARQ feedback configured), the eRedCap terminal may skip the channel or may not expect decoding of the channel. For a channel without HARQ feedback, the eRedCap terminal may stop or skip decoding for the MBS PDSCH scheduled in slot n. If decoding for the MBS PDSCH scheduled in slot n is stopped, the eRedCap terminal may drop the stopped MBS PDSCH.

[0335] Example 4-13

[0336] In one embodiment of the present disclosure, it is assumed that when PRBs (e.g., PRBs of MBS PDSCH) corresponding to a bandwidth of 5 MHz or less are scheduled / allocated to slot n, another channel is also received in slot n. Embodiment 4-13 relates to a processing method in a case where another PDSCH is scheduled in slot n+1 in a situation where an eRedCap terminal must decode each channel scheduled in slot n. In this case, multiple PDSCHs scheduled in slot n may overlap in units of OFDM symbols, but are not limited thereto.

[0337] As an example of the present disclosure, when MBS PDSCH and another channel are scheduled in slot n as described above, the eRedCap terminal may drop MBS PDSCH.

[0338] As an example of the present disclosure, if there is no PDSCH requiring decoding in slot n+1, the eRedCap terminal can decode all of the multiple PDSCHs (i.e., MBS PDSCH and other PDSCHs, etc.) scheduled in slot n. At this time, the other PDSCHs scheduled in slot n and / or the PDSCHs requiring decoding in slot n+1 may all be unicast PDSCHs, but are not limited thereto. In addition, if there is no PDSCH requiring decoding in slot n+1, even if the sum of the PRBs of the MBS PDSCH and other PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal can decode all of the MBS PDSCH and other PDSCHs scheduled in slot n.

[0339] Example 4-14

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

[0341] As described above, the eRedCap terminal can process PRBs as many as the number of PRBs corresponding to a 5 MHz bandwidth in one 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 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 that the sum of the PRBs of each 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 may or may not overlap in the time domain. For example, the eRedCap terminal may skip (or drop) the MBS PDSCH or may not expect decoding of the MBS PDSCH. If the HARQ feedback for the MBS PDSCH is set to enable, the eRedCap terminal may transmit the feedback as a NACK. As another example, an eRedCap terminal may not expect the number of PRBs of an MBS PDSCH to exceed the number of PRBs corresponding to a 5 MHz bandwidth. As another example, an eRedCap terminal may process MBS PDSCH and unicast PDSCH in the received / scheduled order (i.e., the order of OFDM symbols within a slot), and may skip certain PRBs (e.g., PRBs exceeding a 5 MHz bandwidth range) or may not expect decoding of certain PRBs. In addition, an eRedCap terminal may transmit a NACK to the base station for a channel containing a specific PRB.

[0342] Example 4-15

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

[0344] As an example of the present disclosure, if a maximum of 7 PDSCHs can be processed within a specific slot, 4 unicast PDSCHs and 3 multicast PDSCHs can be processed within the specific slot. In this case, the eRedCap terminal can process the PDSCHs in the order scheduled in slot n, and can be expected to process the PDSCH(s) within a range that does not exceed the processing capability of a specific bandwidth.

[0345] For example, an eRedCap terminal may process MBS PDSCH(s) and unicast PDSCH(s) in the received / scheduled order (i.e., OFDM symbol order within a slot), and may skip certain PRBs (e.g., PRBs exceeding a 5 MHz bandwidth range) or may not expect decoding of certain PRBs. In addition, the eRedCap terminal may transmit a NACK to the base station for a channel containing a certain PRB.

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

[0347] Example 4-16

[0348] In one embodiment of the present disclosure, for an eRedCap terminal, one unicast PDSCH can be scheduled in one slot. An eRedCap terminal capable of processing a PRB corresponding to a 5 MHz bandwidth in one slot (e.g., a PRB of a unicast PDSCH) can only process one unicast PDSCH in one slot.

[0349] Example 4-17

[0350] In one embodiment of the present disclosure, a multicast PDSCH and a unicast PDSCH may be scheduled in the same slot. In this case, the HARQ feedback mode of the multicast PDSCH may be set to an ACK / NACK mode or a NACK-only HARQ feedback mode. As another example, the number of all PDSCHs scheduled in slot n may be counted without considering the feedback mode.

[0351] As another example of the present disclosure, the eRedCap terminal may process MBS PDSCH and unicast PDSCH in the received / scheduled order (i.e., OFDM symbol order within a slot), and may skip certain PRBs (e.g., PRBs exceeding a 5 MHz bandwidth range) or may not expect decoding of certain PRBs. In addition, the eRedCap terminal may transmit a NACK for a channel including a certain PRB to the base station.

[0352] Example 5

[0353] MBS PDSCH channels can be scheduled within a 5 MHz bandwidth, but may also be scheduled in areas exceeding the 5 MHz bandwidth. In this case, the likelihood of a multicast PDSCH or broadcast PDSCH being scheduled in consecutive slots may be higher than that of a SIB-based PDSCH or a paging-based PDSCH being scheduled in consecutive slots.

[0354] Meanwhile, as described above, an eRedCap terminal can process a unicast channel within a 5 MHz bandwidth in a single slot. For MBS PDSCH, although it can be allocated within the 5 MHz bandwidth, PRBs exceeding the number of PRBs corresponding to the 5 MHz bandwidth (i.e., PRBs of MBS PDSCH) may also be allocated.

[0355] If PRBs exceeding the number of PRBs corresponding to a 5 MHz bandwidth are allocated to a single slot and repeated transmissions are performed in consecutive slots, processing of PDSCHs scheduled in the next slot of that slot may become a problem.

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

[0357] As an example of the present disclosure, as illustrated in FIG. 11, if PRBs exceeding the number of PRBs corresponding to a 5 MHz bandwidth in slot n (i.e., PRBs of MBS PDSCH) are allocated, additional processing time may be required to process PDSCHs exceeding 5 MHz in the next slot. Accordingly, if repetitive transmission is not configured, some of the PDSCHs scheduled / received in slot n+1 may be processed. However, if PDSCHs are received continuously, processing of other PDSCHs may not be possible in the slot in which repetitive transmissions are received.

[0358] Below, the processing method is described when PRBs less than the number of PRBs corresponding to a bandwidth of 5 MHz (e.g., PRBs of MBS PDSCH) are scheduled when repetitive transmission is set / scheduled.

[0359] For eRedCap terminals, when repetitive transmission is enabled, scheduling restrictions on PRB allocation within the 5 MHz bandwidth can be defined / set. Accordingly, if another channel is scheduled / received while repetitive transmission is scheduled / performed, this may affect the decoding of each slot channel, as illustrated in Figure 11.

[0360] Therefore, in a situation where PRBs (e.g., PRBs of MBS PDSCH) can be scheduled within a range exceeding 5 MHz bandwidth, when repeated transmission is set / applied, the number of PRBs indicated through the FDRA field of DCI may be less than or equal to the number of PRBs corresponding to the 5 MHz bandwidth.

[0361] The embodiments described below relate to a processing method of an eRedCap terminal when (repetitive) transmission of a channel (e.g., MBS PDSCH) is scheduled within or exceeding a 5 MHz bandwidth.

[0362] Example 5-1

[0363] In one embodiment of the present disclosure, the eRedCap terminal may only process MBS PDSCHs scheduled / received in the first slot, and may not process MBS PDSCHs repeatedly transmitted in the remaining slots. That is, the eRedCap terminal may not decode or skip MBS PDSCHs scheduled in slots subsequent to slot n (i.e., slot n+1, slot n+2, slot n+3) in (a) of FIG. 11.

[0364] Example 5-2

[0365] In one embodiment of the present disclosure, the number of repetitions (of MBS PDSCH) can be set to one of 2, 4, or 8 via higher layer signaling. In this case, based on the number of repetitions being set to a number exceeding 2, the eRedCap terminal can only process channels that have been repeatedly transmitted at most 2 times. If the number of repetitions increases, problems related to decoding may occur, as illustrated in FIG. 11. As another example, a specific threshold related to the number of repetitions can be set / indicated / defined, and the eRedCap terminal can decode or drop all channels that have been repeatedly transmitted less than / more than the specific threshold.

[0366] Example 5-3

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

[0368] In Example 5, if even one MBS PDSCH is not received / decoded when repeated transmission is performed, the eRedCap terminal may transmit a NACK.

[0369] Example 6

[0370] Example 6 relates to a method of processing MBS PDSCH on a slot-by-slot basis for repeated transmission when PRBs (i.e., PRBs of MBS PDSCH) exceeding the number of PRBs corresponding to a 5 MHz bandwidth are scheduled in a specific slot.

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

[0372] As an example of the present disclosure, as illustrated in (b) of FIG. 11, when the MBS PDSCH of slot n+1 is scheduled / transmitted, an additional PDSCH is scheduled in slot n+2 except for the repeated MBS PDSCH, and the eRedCap terminal may 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 drop it.

[0373] Example 6-1

[0374] In one embodiment of the present disclosure, when an MBS PDSCH is processed in slot n, if not only is there a repeated transmission of the MBS PDSCH in the next slot, but another PDSCH is scheduled / received, the eRedCap terminal may not receive the MBS PDSCH processed in slot n in the next slot (e.g., slot n+1). That is, the eRedCap terminal may 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 terminal may decode the first MBS PDSCH in slot n.

[0375] Example 6-2

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

[0377] That is, eRedCap terminals can skip reception of MBS PDSCHs that are repeatedly transmitted. eRedCap terminals can receive the first MBS PDSCH among the repeatedly transmitted MBS PDSCHs even if another PDSCH is scheduled in the next slot. Even if repeated transmission is not performed, reception of the MBS PDSCH in slot n may be skipped or not decoded.

[0378] Example 6-3

[0379] In one embodiment of the present disclosure, the number of transmission repetitions may be set to one of 2 to 8 via DCI or RRC signaling to minimize PDSCHs that are not received when scheduling repeated transmissions.

[0380] Example 6-4

[0381] In one embodiment of the present disclosure, when multiple channels are received simultaneously in a given 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, the conditions for dropping the MBS PDSCH channel and performing repeated transmission may be applied.

[0382] Additionally, MBS PDSCHs that are not dropped during the repeated transmission process can be combined and decoded.

[0383] Example 6-5

[0384] In one embodiment of the present disclosure, when a repetitive transmission is set / scheduled and a channel is received and decoded in a particular slot, another channel can be received and decoded in a slot after skipping one slot in the particular slot.

[0385] Reception and decoding of a PDSCH scheduled for a specific slot or a slot skipped based on a specific slot may not be expected. That is, the PDSCH may be skipped or not received.

[0386] If even one channel decoding is not performed by the PDSCH of a specific slot and the next slot through the method according to Example 6, the eRedCap terminal can transmit a NACK for the channel that was not received to the base station.

[0387] Example 7

[0388] Example 7 relates to a processing method in the last slot when PRBs (i.e., PRBs of MBS PDSCH) exceeding the number of PRBs corresponding to a bandwidth of 5 MHz in a specific slot are scheduled and repeated transmission is set.

[0389] When repetitive transmission is configured, the terminal can perform decoding for the corresponding channel(s) for which channel reception has been performed up to the last slot for which repetitive transmission has been configured. The processing for the last slot for which repetitive transmission has been configured may be determined depending on whether another PDSCH is scheduled / received in the slot following the corresponding slot. That is, even if PRBs corresponding to a bandwidth of 5 MHz or more are scheduled in the preceding slots (i.e., slots in which all MBS PDSCHs are transmitted) excluding the last slot, the channel corresponding to the PRB and another PDSCH may be received simultaneously.

[0390] Example 7-1

[0391] In one embodiment of the present disclosure, when repetitive transmission is set, the MBS PDSCH of the slot in which the last repetitive transmission is performed may not be decoded if another PDSCH is scheduled in the slot following that slot.

[0392] Example 7-2

[0393] As one embodiment of the present disclosure, it is assumed that PRBs (e.g., PRBs of MBS PDSCHs) greater than the number of PRBs corresponding to a 5 MHz bandwidth are scheduled and repetitive transmissions are set. In this case, as disclosed in Example 4-12, it can be determined whether to drop the MBS PDSCH of the last slot in which repetitive transmissions are performed or to drop the MBS PDSCH of the slot following the last slot.

[0394] Example 7-3

[0395] In one embodiment of the present disclosure, when repetitive transmission is set, if another PDSCH is simultaneously transmitted in the last slot in which repetitive transmission is set or another PDSCH is scheduled in the next slot, the eRedCap terminal may not perform reception of the MBS PDSCH of the last slot and may perform decoding on the previously received MBS PDSCH.

[0396] As another example of the present disclosure, when PRBs (i.e., PRBs of MBS PDSCH) greater than the number of PRBs corresponding to a 5 MHz bandwidth are scheduled, repeated transmissions may be restricted from being set, or the eRedCap terminal may transmit a NACK to the base station without receiving the repeatedly transmitted MBS PDSCH.

[0397] As another example of the present disclosure, if it is not possible to decode both channels scheduled in one slot, the eRedCap terminal may decode one of the channels (e.g., PDSCH scheduled by SI (system information)-RNTI or PDSCH scheduled by P (paging)-RNTI) according to the priority of the two channels.

[0398] Example 8

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

[0400] That is, unlike Example 1, the eRedCap terminal can operate a 20 MHz bandwidth. At this time, if HARQ feedback exists and ACK / NACK or NACK-only mode is set, an additional time of X value may be required to be added to the terminal processing time. At this time, if there is no HARQ feedback, the X value may not be applied. Even if ACK / NACK and NACK-only mode are set and only the number of PRBs within 5 MHz BW is allocated, the X value may not be applied.

[0401] Example 8-1

[0402] In one embodiment of the present disclosure, when the NO HARQ mode is set, the X value may not be applied to the terminal processing type.

[0403] Example 8-2

[0404] In one embodiment of the present disclosure, when there is HARQ feedback, the eRedCap terminal can add an X value to the additional processing time. At this time, the X value can be applied to the same value or different values ​​according to the additional processing time capabilities 1 and 2. The X value can be applied differently depending on the SCS. In addition, the X value can be the same as the value applied to the decoding-related processing time of message 2 or message B in the RACH procedure. In addition, the X value can be applied even when the multicast channel is allocated within a 5 MHz bandwidth.

[0405] Example 8-3

[0406] In one embodiment of the present disclosure, when the NACK-only mode is set, the relaxation of additional processing time of the X value may not be applied to increase the flexibility of network operation.

[0407] Example 8-4

[0408] In one embodiment of the present 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), an additional processing time of the value X may be applied.

[0409] And, in the ACK / NACK or NACK-only mode, if the FDRA information of the PDCCH indicates a PRB 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 the X value may not be applied (X=0).

[0410] As an example of the present disclosure, for an MBS channel (e.g., a multicast channel), an eRedCap terminal may not expect scheduling exceeding 5 MHz. In this case, the base station may group eRedCap terminals that support 5 MHz and schedule MBS channels for the eRedCap terminals within the 5 MHz bandwidth.

[0411] As an example of the present disclosure, in the case of an MBS channel (e.g., a multicast channel), an eRedCap terminal can expect scheduling exceeding 5 MHz. In this case, there is no restriction on grouping of eRedCap terminals, and operations according to ACK / NACK mode can be considered. For example, timing relaxation may not be applied to the eRedCap terminal. In another example, timing relaxation may be applied to the eRedCap terminal. In another example, when a multicast PDSCH is scheduled in a bandwidth exceeding 5 MHz, timing relaxation may be applied to the eRedCap terminal. 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 may be determined depending on the ACK / NACK mode.

[0412] Example 9

[0413] Embodiment 9 relates to a method for processing multiple channels based on the sum of PRBs of multiple simultaneously received channels. That is, Embodiment 9 relates to a processing method when the sum of PRBs of simultaneously transmitted channels exceeds the PRB corresponding to a 5 MHz bandwidth. An eRedCap terminal can preferentially process important channels based on the priorities of simultaneously transmitted channels. Hereinafter, a case in which an MBS channel (e.g., a multicast channel and / or a broadcast channel) is received within a single slot with another channel will be described.

[0414] As an example of the present disclosure, as illustrated in FIG. 9, two channels may be scheduled / transmitted in one slot. In this case, the MBS PDSCH may include a broadcast PDSCH and / or an MBS PDSCH. In addition, the other PDSCH may include a PDSCH that may be scheduled by an SI-RNTI, a P-RNTI, an RA-RNTI, a C-RNTI, or an MsgB-RNTI.

[0415] Example 9-1

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

[0417] Example 9-2

[0418] In one embodiment of the present disclosure, when the sum of PRBs of two channels (e.g., MBS PDSCH and other PDSCH) scheduled in one slot exceeds the number of PRBs corresponding to a specific bandwidth (e.g., 25 when SCS is 15 kHz or 12 when SCS is 30 kHz), the operation of the eRedCap terminal may be determined depending on which RNTI the other PDSCH among the two channels is scheduled with.

[0419] For example, if another PDSCH is scheduled by the P-RNTI, the eRedCap terminal may drop or skip the MBS PDSCH. That is, the MBS PDSCH may not be decoded.

[0420] For example, if another PDSCH (e.g., a unicast PDSCH) is scheduled by the C-RNTI, the eRedCap terminal may drop or skip the unicast PDSCH. That is, the unicast PDSCH may not be decoded. In this case, HARQ feedback may exist for the MBS PDSCH, but HARQ feedback for the unicast PDSCH may not exist.

[0421] For example, if another PDSCH is scheduled by SI-RNTI, the eRedCap terminal may drop or skip the MBS PDSCH. In this case, HARQ feedback for the MBS PDSCH may be present.

[0422] For example, if another PDSCH is scheduled by MCCH-RNTI, the PDSCH scheduled by MCCH-RNTI may be processed with priority, and the PDSCH scheduled by G-RNTI may be dropped.

[0423] For example, if both PDSCHs are scheduled by G-RNTI, the PDSCH to be dropped may be determined based on the priority of each PDCCH that scheduled each of the two PDSCHs. That is, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0425] Example 9-3

[0426] In one embodiment of the present 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 terminal may perform decoding for both channels.

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

[0428] Example 10

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

[0430] 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 the 5 MHz bandwidth). In this case, as illustrated in (a) of FIG. 12, the processing time of the MBS PDSCH can exceed one slot based on the eRedCap terminal.

[0431] Below, we describe the operation of an eRedCap terminal when an additional PDSCH is received while the number of PRBs of an MBS PDSCH scheduled on a specific slot exceeds the number of PRBs corresponding to a specific bandwidth (e.g., 5 MHz). The operation of the eRedCap terminal may vary depending on the type of PDSCH. The following operation can be applied regardless of whether the two channels (i.e., the MBS PDSCH and the additional PDSCH) overlap in the time domain.

[0432] Example 10-1

[0433] In one embodiment of the present disclosure, the eRedCap terminal may drop or skip one of the two channels. For example, the eRedCap terminal may drop the MBS PDSCH among the two channels.

[0434] For example, if the additional PDSCH (i.e., unicast PDSCH) is scheduled by C-RNTI, the eRedCap terminal may drop the unicast PDSCH. That is, the unicast PDSCH may not be decoded. In this case, HARQ feedback for the MBS PDSCH may exist, but HARQ feedback for the unicast PDSCH may not exist. In addition, in slot n+1, the MBS PDSCH and the unicast PDSCH may overlap in OFDM symbol units.

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

[0436] For example, if the additional PDSCH is scheduled by SI-RNTI, the MBS PDSCH may be dropped. In this case, HARQ feedback for the MBS PDSCH may be present.

[0437] Example 10-2

[0438] Fig. 12(b) illustrates a case where, unlike Fig. 12(a), the number of PRBs of the MBS PDSCH does not exceed the number of PRBs corresponding to a 5 MHz bandwidth. As illustrated in Fig. 12(b), when two channels overlap (i.e., overlap in one OFDM symbol unit) in slot n and slot n+1, the eRedCap terminal may drop / skip one of the two channels or the corresponding channel may not be decoded.

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

[0440] For example, if there is HARQ feedback for the MBS PDSCH, the eRedCap terminal may drop the unicast PDSCH among the MBS PDSCH and the unicast PDSCH. In this case, HARQ feedback for the unicast PDSCH may not exist. As another example, the eRedCap terminal may drop the MBS PDSCH among the two channels (e.g., the MBS PDSCH and the unicast PDSCH).

[0441] Example 10-3

[0442] In one embodiment of the present disclosure, except for slot n-1 of FIG. 9, if two channels overlap or do not overlap in the time domain, and the sum of the PRBs of the two channels does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may decode both channels. If the sum of the PRBs of the two channels exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may drop / skip one of the two channels, or the channel may not be decoded.

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

[0444] For example, if there is HARQ feedback for the MBS PDSCH, the eRedCap terminal may drop the unicast PDSCH among the MBS PDSCH and the unicast PDSCH. In this case, HARQ feedback for the unicast PDSCH may not exist. As another example, the eRedCap terminal may drop the MBS PDSCH among the two channels (e.g., the MBS PDSCH and the unicast PDSCH).

[0445] Example 11

[0446] Example 11 relates to a method of utilizing Examples 9 and 10 depending on the presence or absence of HARQ feedback.

[0447] HARQ feedback may or may not be present for an MBS channel. If HARQ feedback is present, the MBS channel can be considered as a unicast PDSCH. If HARQ feedback is not present, the MBS channel can be considered as a general SIB transmission PDSCH channel. Embodiment 11 describes how an eRedCap terminal processes an MBS channel with HARQ feedback and an MBS channel without HARQ feedback, respectively.

[0448] If there is HARQ feedback for the MBS channel, embodiment 10 may be applied. And, if there is no HARQ feedback for the MBS channel, embodiment 9 may be applied. If there is HARQ feedback, one or more channels may be scheduled within a 5 MHz bandwidth. If there is no HARQ feedback, one or more channels may be scheduled within a 5 MHz bandwidth or exceeding a 5 MHz bandwidth.

[0449] Example 11-1

[0450] Example 11-1 relates to the operation of an eRedCap terminal in the presence of HARQ feedback, and is described with reference to (b) of FIG. 12. As illustrated in (b) of FIG. 12, when multiple channels scheduled for the same slot overlap in the time domain (i.e., overlap in one OFDM symbol unit), regardless of whether the sum of the number of PRBs of each of the multiple channels exceeds the number of PRBs corresponding to a specific bandwidth (e.g., 5 MHz), the eRedCap terminal may drop / skip one of the two channels, or the corresponding channel may not be decoded.

[0451] For example, if one of the two channels (i.e., unicast PDSCH) is scheduled by C-RNTI, the eRedCap terminal may drop the unicast PDSCH. For example, if there is HARQ feedback for the MBS PDSCH, the eRedCap terminal may drop the unicast PDSCH among the MBS PDSCH and the unicast PDSCH. In this case, HARQ feedback for the unicast PDSCH may not exist. As another example, the eRedCap terminal may drop the MBS PDSCH among the two channels (e.g., MBS PDSCH and unicast PDSCH).

[0452] For example, if both channels (e.g., PDSCHs) are scheduled by G-RNTI, the PDSCH to be dropped may be determined based on the priority of each PDCCH that scheduled each of the two PDSCHs. That is, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0454] Example 11-1 can be applied when the sum of the number of PRBs of two channels exceeds the number of PRBs corresponding to a 5 MHz bandwidth. 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, both channels can be decoded.

[0455] Example 11-2

[0456] Example 11-2 relates to the operation of an eRedCap terminal 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 numbers of PRBs of two channels exceeds the number of PRBs corresponding to a specific bandwidth (e.g., 5 MHz), the eRedCap terminal may drop one of the two channels.

[0457] In one embodiment of the present disclosure, when the sum of PRBs of two channels (e.g., MBS PDSCH and other PDSCH) scheduled in one slot exceeds the number of PRBs corresponding to a specific bandwidth (e.g., 25 when SCS is 15 kHz or 12 when SCS is 30 kHz), the operation of the eRedCap terminal may be determined depending on which RNTI the other PDSCH among the two channels is scheduled with.

[0458] For example, if another PDSCH is scheduled by the P-RNTI, the eRedCap terminal may drop or skip the MBS PDSCH. That is, the MBS PDSCH may not be decoded.

[0459] For example, if another PDSCH (e.g., a unicast PDSCH) is scheduled by the C-RNTI, the eRedCap terminal may drop or skip the unicast PDSCH. That is, the unicast PDSCH may not be decoded. In this case, HARQ feedback may exist for the MBS PDSCH, but HARQ feedback for the unicast PDSCH may not exist.

[0460] For example, if another PDSCH is scheduled by SI-RNTI, the eRedCap terminal may drop or skip the MBS PDSCH. In this case, HARQ feedback for the MBS PDSCH may be present.

[0461] For example, if another PDSCH is scheduled by MCCH-RNTI, the PDSCH scheduled by MCCH-RNTI may be processed with priority, and the PDSCH scheduled by G-RNTI may be dropped.

[0462] For example, if both PDSCHs are scheduled by G-RNTI, the PDSCH to be dropped may be determined based on the priority of each PDCCH that scheduled each of the two PDSCHs. That is, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0464] Example 11-3

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

[0466] If a channel other than the MBS PDSCH channel is received in the same slot, the following actions may be performed. For example, an eRedCap terminal may not consider the scheduling described below or may perform actions based on the terminal implementation.

[0467] For example, if another PDSCH is scheduled by the P-RNTI, the eRedCap terminal may drop or skip the MBS PDSCH. That is, the MBS PDSCH may not be decoded.

[0468] For example, if another PDSCH (e.g., a unicast PDSCH) is scheduled by the C-RNTI, the eRedCap terminal may drop or skip the unicast PDSCH. That is, the unicast PDSCH may not be decoded. In this case, HARQ feedback may exist for the MBS PDSCH, but HARQ feedback for the unicast PDSCH may not exist.

[0469] For example, if another PDSCH is scheduled by SI-RNTI, the eRedCap terminal may drop or skip the MBS PDSCH. In this case, HARQ feedback for the MBS PDSCH may be present.

[0470] For example, if another PDSCH is scheduled by MCCH-RNTI, the PDSCH scheduled by MCCH-RNTI may be processed with priority, and the PDSCH scheduled by G-RNTI may be dropped.

[0471] For example, if both PDSCHs are scheduled by G-RNTI, the PDSCH to be dropped may be determined based on the priority of each PDCCH that scheduled each of the two PDSCHs. That is, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0473] Example 12

[0474] Example 12 relates to a method of utilizing Examples 9 and 10 according to the MBS casting type.

[0475] The MBS casting type may include a broadcast type and a multicast type. If the MBS casting type is a broadcast type, Example 9 may be applied. If the MBS casting type is a multicast type, Example 10 may be applied.

[0476] Example 12-1

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

[0478] As an example of the present disclosure, when an MBS PDSCH and another channel (e.g., another PDSCH) are simultaneously scheduled in the same slot, and an eRedCap terminal cannot receive both channels simultaneously, the method described below may be applied. In this case, the eRedCap terminal may not expect scheduling of the two channels and may perform operations according to the terminal implementation.

[0479] For example, if another PDSCH is scheduled by the P-RNTI, the eRedCap terminal may drop or skip the MBS PDSCH. That is, the MBS PDSCH may not be decoded.

[0480] For example, if another PDSCH (e.g., a unicast PDSCH) is scheduled by the C-RNTI, the eRedCap terminal may drop or skip the unicast PDSCH. That is, the unicast PDSCH may not be decoded. In this case, HARQ feedback may exist for the MBS PDSCH, but HARQ feedback for the unicast PDSCH may not exist.

[0481] For example, if another PDSCH is scheduled by SI-RNTI, the eRedCap terminal may drop or skip the MBS PDSCH. In this case, HARQ feedback for the MBS PDSCH may be present.

[0482] For example, if another PDSCH is scheduled by MCCH-RNTI, the PDSCH scheduled by MCCH-RNTI may be processed with priority, and the PDSCH scheduled by G-RNTI may be dropped.

[0483] For example, if both PDSCHs are scheduled by G-RNTI, the PDSCH to be dropped may be determined based on the priority of each PDCCH that scheduled each of the two PDSCHs. That is, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0485] Meanwhile, for a broadcast channel, embodiment 10 may be applied, and for a multicast channel, embodiment 9 may be applied. In addition, when decoding one channel because the eRedCap terminal cannot decode both channels, embodiment 12-1 may be applied.

[0486] Example 13

[0487] As illustrated in Figure 13, assume that the PBCH and MBS channels are received simultaneously or separately in a single slot. In this case, if at least one of the PBCH and MBS channels is scheduled by the G-RNTI, decoding of the channels may not be expected. As another example, if the PBCH and MBS channels are received simultaneously or separately, and at least one of the channels is scheduled by the MCCH-RNTI, the channels can be decoded simultaneously.

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

[0489] Example 13-1

[0490] In one embodiment of the present disclosure, when a PBCH and an MBS PDSCH (e.g., a PDSCH scheduled by MCCH-RNTI) are received simultaneously in one slot, an eRedCap terminal may drop / skip one of the PBCH and the MBS PDSCH, or may not expect one of the PBCH and the MBS PDSCH to be decoded.

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

[0492] Example 13-2

[0493] In one embodiment of the present disclosure, an eRedCap terminal may not expect PBCH and MBS PDSCH (e.g., PDSCH scheduled by MCCH-RNTI) to be scheduled simultaneously in one slot.

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

[0495] Embodiments 13-1 and 13-2 can be applied when the eRedCap terminal is in the RRC_Inactive or RRC idle state. 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 the MBS casting type.

[0496] Example 13-3

[0497] In one embodiment of the present disclosure, when the number of PRBs of an 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 Embodiment 10 and Embodiment 10-1 may be applied to a PDSCH scheduled for the next slot based on a specific slot.

[0498] Example 13-4

[0499] In one embodiment of the present disclosure, if the number of PRBs in an 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 methods described below may be applied. The methods described below may also be applied to slot n-1 of FIG. 12(b), where two channels within the same slot do not overlap each other.

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

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

[0502] For example, if the other channel is a unicast channel, the eRedCap terminal can drop the unicast channel among the two channels. Except for NTN, since HARQ feedback exists for unicast channels, the eRedCap terminal can drop the unicast channel among the two channels. As another example, the eRedCap terminal can drop the MBS channel among the two channels.

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

[0504] For example, if there is or is not HARQ feedback on both the MBS channel and the unicast channel, whether or not to drop the MBS channel and the unicast channel may be determined based on the priority of the DCI that scheduled each of the MBS channel and the unicast channel, respectively. In 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 may be dropped. The type of channel to be dropped among the MBS channel and the unicast channel may be predefined or set by higher-layer signaling.

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

[0506] Example 13-5

[0507] In one embodiment of the present disclosure, it is assumed that MBS channels and unicast PDSCHs are scheduled in the same slot. In this case, the MBS channel and unicast PDSCH may overlap completely or partially in a single symbol within a single slot.

[0508] The following describes the operation of an eRedCap terminal when it cannot simultaneously receive both an MBS channel and a unicast PDSCH. For example, the channel to be dropped between the MBS channel and the unicast channel can be determined based on priority rules and the presence or absence of HARQ feedback. Here, the priority can be indicated via the priority indicator field included in the DCI. Alternatively, the priority can be set or predefined via RRC signaling.

[0509] For example, if the other channel is a unicast channel, the eRedCap terminal can drop the unicast channel among the two channels. Except for the case of NTN, since HARQ feedback exists for unicast channels, the eRedCap terminal can drop the unicast channel among the two channels.

[0510] For example, if two channels cannot be received simultaneously, the eRedCap terminal may not expect simultaneous reception scheduling of both channels.

[0511] As another example, a channel with HARQ feedback among MBS and unicast channels may be dropped. For channels with HARQ feedback, retransmission of that channel may be expected. For example, if there is no HARQ feedback for a unicast channel and HARQ feedback for an MBS channel, the MBS channel may be dropped.

[0512] For example, if there is or is no HARQ feedback on both the MBS channel and the unicast channel, whether or not the MBS channel and the unicast channel are dropped can be determined based on the priority of the DCI that scheduled each MBS channel and the unicast channel, respectively. For example, the priority of the guest channel can be indicated through the priority indicator of the DCI, and a channel with a lower priority can be dropped regardless of the presence of HARQ feedback.

[0513] As another example, if there is or is no HARQ feedback on both the MBS channel and the unicast channel, either the MBS channel or the unicast channel may be dropped. The type of channel to be dropped among the MBS channel and the unicast channel may be predefined or set by higher-layer signaling.

[0514] As another example, one of the MBS PDSCH and the unicast PDSCH may be dropped based on the priorities set / 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 channel to be dropped may be determined based on the presence or absence of HARQ feedback. If the priorities and the presence or absence of HARQ feedback of the MBS PDSCH and the unicast PDSCH are the same, the unicast PDSCH may be dropped. As another example, if the priorities and the presence or absence of HARQ feedback of the MBS PDSCH and the unicast PDSCH are the same, the type of channel to be dropped among the two channels may be predefined or set by higher layer signaling. As described above, rather than first checking the priorities of the two channels and then checking the presence or absence of HARQ feedback, the presence or absence of HARQ feedback may be checked first and then the priority may be checked.

[0515] As another example, a bit field may 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 terminal cannot decode both the MBS PDSCH and the unicast PDSCH, the bit field in the DCI may indicate which channel among the MBS PDSCH and the unicast PDSCH to drop / decode.

[0516] Example 13-6

[0517] In one embodiment of the present 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 5 MHz bandwidth. In this case, if the sum of the numbers of PRBs allocated to each of the MBS channel and the unicast PDSCH (e.g., a PDSCH including paging or SIB) exceeds the number of PRBs corresponding to a 5 MHz bandwidth, decoding of any PDSCH that may be scheduled in the next slot of the specific slot may not be expected or may not be skipped. For example, an eRedCap terminal may not expect scheduling of another PDSCH in the next slot of the specific slot, and if another PDSCH in the next slot is received, the MBS PDSCH of the specific slot may be dropped.

[0518] In one embodiment of the present disclosure, when an MBS PDSCH with a PRB allocated less than or equal to a number of PRBs corresponding to a unicast channel and a bandwidth of 5 MHz is received in one slot (in which case, the unicast channel and the MBS PDSCH may or may not overlap each other), (e) it may not be guaranteed which PDSCH the RedCap terminal will process until the next slot, and (e) processing of two channels by the RedCap terminal in the slot may be guaranteed. If no PDSCH is scheduled in the next slot, (e) the RedCap terminal may decode both channels in the slot. In this case, the sum of the numbers of PRBs of each of the unicast channel and the MBS PDSCH may exceed the number of PRBs corresponding to a bandwidth of 5 MHz, and the unicast channel and the MBS PDSCH may partially or completely overlap in the slot. In addition, when a specific PDSCH is received in the next slot, the MBS PDSCH in the slot may be dropped. As another example, MBS PDSCH decoding in a slot may not be expected or may be skipped regardless of reception of a particular PDSCH in the next slot.

[0519] Example 13-7

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

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

[0522] Example 13-8

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

[0524] At this time, the unicast channel may be dropped (or skipped) or not decoded, regardless of the DCI priority or the presence of HARQ feedback. If a non-unicast channel is scheduled within a slot, such as the MBS PDSCH, the MBS PDSCH may be dropped (or skipped) or not decoded.

[0525] For example, if a non-unicast channel and an MBS PDSCH with a PRB allocated greater than the number of PRBs corresponding to a 5 MHz bandwidth (or regardless of the number of PRBs) are scheduled / received simultaneously within a slot, the MBS PDSCH may not be decoded as it is dropped. In this case, the non-unicast PDSCH may include a unicast including paging or SIB. As another example, embodiment 13-8 may also be applied when the terminal is in the RRC_Idle state or RRC_Inactive state.

[0526] Example 13-9

[0527] In one embodiment of the present disclosure, a unicast PDSCH and an MBS (e.g., multicast or broadcast) PDSCH may or may not overlap on an OFDM symbol within one slot, and the base station may 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 a 5 MHz bandwidth.

[0528] Example 13-10

[0529] In one embodiment of the present 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 terminal can decode both the MBS PDSCH and the unicast PDSCH. In this case, the MBS PDSCH and the unicast PDSCH may partially or completely overlap on the OFDM symbol.

[0530] Example 13-11

[0531] In one embodiment of the present disclosure, in a situation where multiple channels are simultaneously transmitted / scheduled on a specific slot and one of the multiple channels must be dropped, the terminal can receive both the MBS PDSCH and another PDSCH of the slot in which repeated transmission is configured. The terminal can determine which of the two channels to drop by comparing the MBS PDSCH and another PDSCH simultaneously transmitted in the last slot in which repeated transmission is configured. If repeated transmission is not configured, simultaneous reception of the two channels or consideration of PDSCH reception / scheduling in the next slot may be limited.

[0532] Example 13-12

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

[0534] Example 13-13

[0535] In one embodiment of the present disclosure, it is assumed that an MBS PDSCH and another channel are transmitted / scheduled in slot n. If the sum of the PRBs of the MBS PDSCH and each of the other channels 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 of the other channels may overlap in an OFDM symbol, but this is not limited thereto.

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

[0537] Examples 13-14

[0538] In one embodiment of the present disclosure, it is assumed that an 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 of the other channels is greater than or equal to the number of PRBs corresponding to a 5 MHz bandwidth, the UE may drop the MBS PDSCH. In this case, the MBS PDSCH and each of the other channels may overlap in OFDM symbols, but this is not limited thereto. For example, Embodiments 13-14 may be applied when another PDSCH is scheduled in slot n+1.

[0539] For example, the other PDSCH may include a PDSCH scheduled by SI-RNTI that requires decoding, a paging PDSCH, etc.

[0540] In the present disclosure, if it is not expected that both channels scheduled in one slot will be decoded, the PDSCHs on which inter-channel contention is performed may include a PDSCH scheduled by an SI-RNTI and a PDSCH associated with a P-RNTI. Furthermore, another PDSCH scheduled in the next slot may include a PDSCH that generally requires decoding from the terminal perspective.

[0541] Example 14

[0542] Example 14 relates to a case where multiple MBS channels and unicast PDSCHs are received in a single slot. In this case, the PDSCH scheduled in the next slot may be considered.

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

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

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

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

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

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

[0549] Example 14-1

[0550] In one embodiment of the present disclosure, when one or more MBS PDSCHs and one or more unicast PDSCHs are scheduled in slot n, all of the one or more MBS PDSCHs may be dropped by the terminal. In this case, the sum of the number of PRBs of each of the one or more MBS PDSCHs and one or more unicast PDSCHs scheduled in slot n may exceed, but is not limited to, the number of PRBs corresponding to a 5 MHz bandwidth.

[0551] Furthermore, even if the total number of PRBs scheduled for slot n becomes less than or equal to the PRBs corresponding to the 5 MHz bandwidth due to the removal of some of one or more MBS PDSCHs, one or more MBS PDSCHs may be dropped by the terminal. In this case, one or more unicast PDSCHs may also be dropped entirely or decoding may not be expected.

[0552] Example 14-2

[0553] 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 MBS PDSCHs whose starting symbol is the latest on the OFDM symbol may be sequentially dropped. In this case, the sum of the number of PRBs of each of the one or more MBS PDSCHs and one or more unicast PDSCHs scheduled in slot n may exceed the number of PRBs corresponding to a 5 MHz bandwidth, but is not limited thereto.

[0554] For example, an eRedCap terminal can decode each channel (e.g., non-dropped multicast PDSCH and unicast PDSCH, etc.) within the number of PRBs corresponding to a 5 MHz bandwidth within slot n. For example, an eRedCap terminal can decode one or more MBS PDSCHs starting from a PDSCH with an earlier start symbol, and can drop the corresponding MBS PDSCH when the number of decoded PRBs exceeds the number of PRBs corresponding to a 5 MHz bandwidth. That is, as illustrated in (a) of FIG. 14, the middle MBS PDSCH in slot n can be processed, and the latest MBS PDSCH can be dropped.

[0555] Additionally or alternatively, it is assumed that MBS PDSCHs are sequentially scheduled in TDM. The eRedCap terminal 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 dropped. In addition, the eRedCap terminal can decode one or more unicast PDSCHs scheduled after the dropped MBS PDSCH. In this case, the eRedCap terminal can decode one or more unicast PDSCHs within a range where the number of PRBs decoded so far in slot n does not exceed the number of PRBs corresponding to a 5 MHz bandwidth.

[0556] That is, the eRedCap terminal can process one or more MBS PDSCHs in the order of the start of OFDM symbols. In addition, when the eRedCap terminal processes the PRB of a specific MBS PDSCH, if the total number of decoded PRBs exceeds the number of PRBs corresponding to a 5MHz bandwidth, the corresponding MBS PDSCH is dropped and one or more channels (e.g., unicast PDSCHs) can be decoded in the order of OFDM symbols within a range that does not exceed the number of PRBs in the 5MHz BW.

[0557] As described above, one or more MBS PDSCHs may be decoded first, followed by a unicast PDSCH, but is not limited thereto. One or more unicast PDSCHs may be decoded first, followed by a multicast PDSCH. As another example, MBS PDSCHs and unicast PDSCHs may be decoded within a 5 MHz bandwidth in the order of their starting symbols, without distinction.

[0558] Example 14-3

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

[0560] Here, the priority of each MBS PDSCH can be indicated by the DCI scheduling each MBS PDSCH, or can be set by higher-layer signaling. Alternatively, the priority of each MBS PDSCH can be predefined. For example, the priority of the broadcast PDSCH can be defined as either the highest or lowest priority. Alternatively, the priority of the broadcast PDSCH can be set by higher-layer signaling.

[0561] As one embodiment of the present 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.

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

[0563] Example 14-4

[0564] In one embodiment of the present disclosure, the priority of each of the plurality of PDSCHs scheduled for slot n may be determined based on the RNTI associated with each of the plurality of PDSCHs. That is, among the plurality of PDSCHs scheduled for slot n, PDSCHs with lower priorities may be dropped first. Accordingly, the eRedCap terminal may decode PDSCH(s) within a 5 MHz bandwidth range.

[0565] Example 14-5

[0566] In one embodiment of the present disclosure, MBS PDSCHs with HARQ feedback may be retransmitted, and MBS PDSCHs with HARQ feedback may be dropped from among the multiple PDSCHs scheduled in slot n. Accordingly, the eRedCap terminal may decode PDSCH(s) within a 5 MHz bandwidth range.

[0567] For example, if the sum of the number of PRBs of MBS PDSCHs without HARQ feedback exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may decode MBS PDSCH(s) without HARQ feedback in the starting OFDM symbol order within the 5 MHz bandwidth. As another example, the eRedCap terminal may first drop MBS PDSCHs with HARQ feedback.

[0568] Example 14-6

[0569] In one embodiment of the present disclosure, among multiple MBS PDSCHs scheduled within a specific slot, a PDSCH that is repeatedly configured may be dropped preferentially. Furthermore, the eRedCap terminal may decode one or more PDSCH(s) that are not dropped within a 5 MHz bandwidth range.

[0570] Example 14-7

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

[0572] For example, if the sum of the PRB numbers of the MBS PDSCH and multiple unicast PDSCHs exceeds the PRB number corresponding to a 5 MHz bandwidth, all unicast PDSCHs scheduled in the slot may be dropped or all multicast PDSCHs may be dropped. If all multicast PDSCHs are dropped, the eRedCap terminal can process unicast PDSCH(s) within the 5 MHz bandwidth. As another example, if the sum of the PRB numbers of the MBS PDSCH and multiple unicast PDSCHs exceeds the PRB number corresponding to a 5 MHz bandwidth, all PDSCHs may be dropped.

[0573] Example 14-8

[0574] In one embodiment of the present disclosure, if the sum of the number of PRBs of each of a plurality of PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, a PDSCH to be dropped can be identified based on the PRB size of each of the plurality of PDSCHs. In addition, the eRedCap terminal can process at least one PDSCH that is not dropped within the 5 MHz bandwidth.

[0575] For example, referring to (b) of FIG. 14, all of the multiple MBS PDSCHs may be dropped, or one MBS PDSCH may be dropped. For example, the sum of the PRB numbers of the multiple PDSCHs scheduled in slot n (e.g., 34) may exceed the number of PRBs corresponding to a 5 MHz bandwidth (e.g., 25 when SCS is 15 kHz). In this case, if an MBS PDSCH with a large number of PRBs among the MBS PDSCHs is dropped, the last PDSCH with 4 PRBs may not be dropped. Accordingly, the eRedCap terminal can decode the unicast PDSCH and the MBS PDSCH with 4 PRBs in slot n even if there is another PDSCH in slot n+1.

[0576] At this time, if the method of dropping the MBS PDSCH scheduled later based on the starting OFDM symbol order is applied, an MBS PDSCH with a PBR of 10 may remain among the MBS PDSCHs. Accordingly, since the total number of PRBs of the unicast PDSCH and the remaining MBS PDSCHs is 30, the eRedCap terminal must also drop the remaining MBS PDSCHs. Accordingly, if another PDSCH is scheduled on slot n+1, the eRedCap terminal can drop the PDSCH with a larger / smaller PRB number among the multiple MBS PDSCHs.

[0577] As another example, if the number of PRBs of multiple MBS PDSCHs is the same, a method of dropping MBS PDSCHs scheduled later based on the starting OFDM symbol order may be applied.

[0578] As another example, an eRedCap terminal can decode multiple channels within a 5 MHz bandwidth range in the order scheduled in slot n. The eRedCap terminal can decode PDSCHs sequentially scheduled in slot n, and ensure that the sum of the number of decoded PRBs does not exceed the number of PRBs corresponding to the 5 MHz bandwidth.

[0579] Example 14-9

[0580] In one embodiment of the present disclosure, if the sum of the number of PRBs of each of a plurality of PDSCHs scheduled in slot n does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may determine which PDSCH among the unicast PDSCH and the MBS PDSCH to decode / drop.

[0581] Example 14-10

[0582] In one embodiment of the present disclosure, if the sum of the number of PRBs of one or more unicast PDSCHs and one or more multicast PDSCHs scheduled (simultaneously) in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may or may not receive either the unicast PDSCH or the MBS PDSCH. The manner in which the eRedCap terminal receives either the unicast PDSCH or the MBS PDSCH may be configured by higher layer signaling or may be performed by the terminal implementation.

[0583] The operations according to embodiments 14-1 to 14-10 may be performed under the assumption that the MBS PDSCH or / and the unicast PDSCH are dropped based on the position of the OFDM symbol, whether or not repetitive transmission is set, whether or not HARQ feedback is present, the priority or / and the number of PRBs, etc.

[0584] In addition, the operations according to embodiments 14-1 to 14-10 may be applied to a case where the unicast PDSCH illustrated in (a) of FIG. 14 becomes an MBS PDSCH (i.e., a case where three MBS PDSCHs are scheduled in one slot). Additionally, the same priority may be assigned to MBS PDSCH(s) and unicast PDSCH(s) scheduled in the same slot, and the priority-based or PRB number-based dropping rules described above may be applied.

[0585] For example, a drop rule based on the number of PRBs (e.g., a rule that preferentially drops channels with a large / small number of PRBs) may be applied. Another example is that unicast PDSCHs and / or MBS PDSCHs may be dropped based on the OFDM symbol starting position or the presence or absence of HARQ. In other words, the above-described drop rule may be applied regardless of whether unicast PDSCHs or MBS PDSCHs are distinguished.

[0586] As another example, if the sum of the PRBs of multiple unicast channels and MBS PDSCHs scheduled for a specific slot exceeds the PRB count corresponding to a 5MHz bandwidth, and a PDSCH is scheduled for the slot following the specific slot, the MBS PDSCH of the specific slot may be dropped. Even if the MBS PDSCH of the specific slot is dropped, the sum of the PRBs of the unicast channels may still exceed the PRB count corresponding to a 5MHz bandwidth.

[0587] If the sum of the number of PRBs of unicast channels exceeds the number of PRBs corresponding to a 5 MHz bandwidth, and if no PDSCH is scheduled on the next slot of a specific slot, the eRedCap terminal may decode all channels on the specific slot.

[0588] Example 14-11

[0589] In one embodiment of the present disclosure, when each channel is scheduled in slot n as illustrated in (c) of FIG. 14, a method for dropping unicast channels must be determined. That is, when multiple unicast channels are scheduled in TDM within one slot, the eRedCap terminal may transmit terminal capability information indicating whether decoding of multiple unicast channels is supported and / or the number of channels that can be decoded to the base station. The eRedCap terminal may transmit / use the above-described terminal capability information, or capability information for the eRedCap terminal may be newly defined. As another example, the eRedCap terminal may not support decoding / reception of multiple unicast channels or multiple MBS PDSCHs.

[0590] As an example of the present disclosure, an eRedCap terminal can sequentially drop MBS PDSCHs with the latest starting symbol on an OFDM symbol (i.e., decode PDSCHs starting from the PDSCHs with the earliest starting symbol on an OFDM symbol). Accordingly, the eRedCap terminal can decode one or more PDSCHs within a 5 MHz bandwidth range.

[0591] Example 14-12

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

[0593] Here, the priority of each unicast PDSCH can be indicated by the DCI scheduling each unicast PDSCH, or can be set by higher-layer signaling. As another example, the priority of each unicast 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 set by higher-layer signaling.

[0594] As one embodiment of the present 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.

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

[0596] Example 14-13

[0597] In one embodiment of the present disclosure, a unicast PDSCH with HARQ feedback may be retransmitted, and may be dropped starting from among the unicast PDSCHs with HARQ feedback among the multiple PDSCHs scheduled in slot n. Accordingly, the eRedCap terminal may decode PDSCH(s) within a 5 MHz bandwidth range.

[0598] For example, if the sum of the number of PRBs of unicast PDSCHs without HARQ feedback exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may decode unicast PDSCH(s) without HARQ feedback in the starting OFDM symbol order within the 5 MHz bandwidth. As another example, the eRedCap terminal may first drop unicast PDSCHs with HARQ feedback.

[0599] Example 14-14

[0600] In one embodiment of the present disclosure, among multiple unicast PDSCHs scheduled within a specific slot, a PDSCH that is repeatedly configured may be dropped preferentially. Furthermore, the eRedCap terminal may decode one or more PDSCH(s) that are not dropped within a 5 MHz bandwidth range.

[0601] Examples 14-15

[0602] In one embodiment of the present disclosure, when multiple unicast PDSCHs are scheduled in one slot, the terminal may or may not expect that the multiple unicast PDSCHs are scheduled so that the sum of the PRB numbers does not exceed 25. In addition, when the sum of the PRB numbers of the multiple unicast PDSCHs exceeds 25, the terminal may not decode the multiple unicast PDSCHs.

[0603] Examples 14-16

[0604] In one embodiment of the present disclosure, if the sum of the number of PRBs of each of a plurality of PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, a PDSCH to be dropped can be identified based on the PRB size of each of the plurality of PDSCHs. For example, an eRedCap terminal can perform decoding / dropping on a unicast PDSCH with a large PRB size or a PDSCH with a small PRB size. In addition, the eRedCap terminal can process at least one PDSCH that is not dropped within the 5 MHz bandwidth.

[0605] Example 14-17

[0606] In one embodiment of the present disclosure, if the sum of the number of PRBs of each of a plurality of unicast PDSCHs scheduled in slot n does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may determine a PDSCH to decode / drop among the plurality of unicast PDSCHs.

[0607] Example 14-18

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

[0609] The above-described embodiment relates to a method for determining a channel to be dropped among MBS PDSCH(s) and unicast PDSCH(s) when MBS PDSCH(s) and unicast PDSCH(s) are scheduled in a specific slot.

[0610] The method for determining which channels to drop among MBS PDSCH(s) and unicast PDSCH(s) can be based on the presence or absence of HARQ feedback, priority, presence or absence of repetitive transmission settings, channel type, etc. for each channel. To determine which channels to drop, the eRedCap terminal can consider the presence or absence of HARQ feedback, priority, presence or absence of repetitive transmission settings, and channel type in that order for each channel.

[0611] However, this is only one embodiment, and the eRedCap terminal may determine the presence or absence of HARQ feedback, priority, presence or absence of repetitive transmission settings, and the order of channel types for each channel as factors for determining which channels to drop. As another example, the presence or absence of HARQ feedback, priority, presence or absence of repetitive transmission settings, and the order of channel types for each channel as factors for determining which channels to drop may be predefined or set by upper layer signaling.

[0612] For example, if unicast channel(s) and MBS channel(s) 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 terminal can decode / drop each channel within a range not exceeding the number of PRBs corresponding to a 5 MHz bandwidth in one slot. In this case, the eRedCap terminal may drop the MBS channel preferentially, but may also drop the unicast channel preferentially. As another example, the eRedCap terminal may drop the channel with the latest / earliest OFDM symbol first, or drop at least one channel depending on the presence or absence of HARQ feedback or the number of PRBs.

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

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

[0615] Case 1: Type of PDSCH (MBS channel or unicast channel) > Start OFDM symbol

[0616] Case 2: Type of PDSCH (MBS channel or unicast channel > Number of PRBs (large or small value) > Start OFDM symbol

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

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

[0619] The above-described cases can perform drop / decode operations depending on whether the sum of the PRBs of each MBS PDSCH or unicast PDSCH exceeds the PRB count corresponding to a 5 MHz bandwidth. For example, when decoding sequentially scheduled channels, an eRedCap terminal can determine whether the sum of the PRB counts of the decoded channels exceeds the PRB count corresponding to a 5 MHz bandwidth.

[0620] For example, in case 1, the eRedCap terminal can prioritize unicast PDSCHs. At this time, if the number of decoded PRBs does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal can decode MBS PDSCHs. If the number of decoded PRBs exceeds the number of PRBs corresponding to a 5 MHz bandwidth, an MBS PDSCH to be additionally decoded within the 5 MHz bandwidth range can be determined. At this time, the MBS PDSCH to be decoded / dropped can be determined based on the start OFDM symbol of the MBS PDSCH.

[0621] For example, if the number of PRBs of MBS PDSCH in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, or if the sum of the number of PRBs of MBS PDSCH(s) or unicast PDSCH(s) scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the base station may notify the terminal that a PDCCH scheduling a specific channel on slot n or / and slot n+1 exists in slot n+1.

[0622] Example 15

[0623] Example 15 relates to a case where multiple MBS channels and unicast PDSCHs are received in a single slot (e.g., slot n). In this case, a PDSCH scheduled in the next slot (e.g., slot n+1) may not be considered.

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

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

[0626] For example, in a situation such as (a) of FIG. 15 (e.g., when the sum of the number of PRBs of each channel scheduled in slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth), if the method according to embodiment 14-2 is applied, since there is no other channel in slot n+1, the eRedCap terminal can decode all unicast PDSCHs and MBS PDSCHs.

[0627] However, when the method according to Example 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 channels can be dropped.

[0628] For example, when the operation according to embodiment 15 is applied to (a) of FIG. 15, the second MBS PDSCH with a PRB count of 30 may be dropped, and the first MBS PDSCH, the third unicast PDSCH, and the next MBS PDSCH may be dropped. The above example is an example when the priority between the unicast PDSCH and the MBS PDSCH is not specified. If a separate priority is set / indicated / defined for each of the MBS PDSCH or the unicast PDSCH, the type of channel to be decoded / dropped may vary, and this may also be applied to embodiment 14.

[0629] As an example of the present disclosure, when a priority is set / indicated / defined for a unicast channel, the sum of the number of PRBs of unicast PDSCHs may be calculated as in (b) of FIG. 15, and then the PRB of the MBS PDSCH may be added. When the PRB of the MBS PDSCH is added to the sum of the number of PRBs of unicast PDSCHs in OFDM order, the MBS PDSCH that is the earliest in terms of OFDM symbols (i.e., the MBS PDSCH with 6 PRBs) may be decoded. In addition, when it is determined to decode the MBS PDSCH behind the unicast channel, the MBS PDSCH behind the unicast channel (i.e., the PDSCH with 6 PRBs) may be decoded.

[0630] As an example of the present disclosure, the processing order of unicast PDSCHs may be determined based on the OFDM sequence. If additional processing of MBS PDSCHs is possible, the PDSCH to be processed may be determined based on the starting OFDM symbol, or whether an MBS PDSCH following a unicast channel will be processed with priority may be determined.

[0631] When priorities are set / defined between channels, higher priority (unicast) channels can be decoded according to OFDM symbol order. If the sum of the number of PRBs of the higher priority channels does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, the decoding / drop order of MBS PDSCHs can also be sequentially determined according to OFDM symbol order. However, this is only an example, and MBS PDSCHs may be processed preferentially.

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

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

[0634] For example, in the case of (a) of Fig. 15, the processing of the subsequent MBS PDSCH may not be completed due to the MBS PDSCH having 8 PRBs. In addition, in the case of (b) of Fig. 15, the corresponding PDSCH may be processed due to the MBS PDSCH having 6 PRBs.

[0635] The embodiments described above can be applied regardless of whether the MBS PDSCH and the unicast PDSCH are TDM'd with each other or whether the MBS PDSCH and the unicast PDSCH overlap in an OFDM symbol.

[0636] An eRedCap terminal can transmit terminal 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, the terminal capability information may be defined separately for the eRedCap terminal in addition to the aforementioned capability information.

[0637] Additionally, NACK may be transmitted from the terminal to the base station for MBS PDSCH and unicast PDSCH that could not be decoded due to being dropped.

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

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

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

[0641] For example, if a channel drop is required, the eRedCap terminal can decide which PDSCH to process among the remaining MBS PDSCHs and unicast PDSCHs within the 5 MHz bandwidth, excluding MBS PDSCHs exceeding the 5 MHz bandwidth.

[0642] General devices to which the present disclosure may be applied

[0643] FIG. 10 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

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

[0645] A first device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure.

[0646] For example, the processor (102) may 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). In addition, the processor (102) may 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).

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

[0648] The second device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0649] Hereinafter, the hardware elements of the device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain 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.

[0650] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0651] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0652] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of the present disclosure, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208). In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0653] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0654] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0655] The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on / in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, 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 processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and / or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0656] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 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-described names. Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0657] The method proposed in this disclosure is explained with a focus on examples applied to 3GPP LTE / LTE-A and 5G systems, but can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: A step of receiving a first downlink channel and a second downlink channel from a base station in a first slot; and A step of decoding the first downlink channel and the second downlink channel based on the 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 value, A method wherein the first downlink channel and the second downlink channel partially or totally overlap in the time domain.

2. In paragraph 1, A method in which capability information indicating that reception of the first downlink channel and the second downlink channel that are frequency division multiplexed (FDMed) in a single slot is supported is transmitted from the terminal to the base station.

3. In paragraph 1, The above first downlink channel is a unicast physical downlink shared channel (PDSCH), A method wherein the second downlink channel is a multicast PDSCH or a broadcast PDSCH.

4. In paragraph 1, A method in which PRBs allocated to each of the first downlink and the second downlink do not overlap each other.

5. In paragraph 1, Based on the subcarrier spacing (SCS) being set to 15 kHz, the first threshold is 25, Based on the SCS being set to 30 kHz, the first threshold is 12.

6. In paragraph 1, A method in which decoding for one of the first downlink channel and the second downlink channel is skipped based on the number of PRBs allocated for each of the first downlink channel and the second downlink channel exceeding the threshold.

7. In paragraph 1, The first downlink channel is scheduled by first downlink control information (DCI) scrambled with CRC (cyclic redundancy check) by C(cell)-RNTI (radio network temporary identifier) ​​or CS (configured scheduling)-RNTI, A method in which the second downlink channel is scheduled by a second DCI that is CRC scrambled by a G(group)-RNTI or an MCCH (multicast broadcast service control channel)-RNTI.

8. In paragraph 1, A method wherein the above terminal is an enhanced reduced capability (eRedCap) terminal.

9. A method performed by a terminal in a wireless communication system, the method comprising: A step of receiving a first downlink channel from a base station in slot n (n is an integer greater than or equal to 0); and A step of processing reception of the first downlink channel based on the number of physical resource blocks (PRBs) allocated to the first downlink channel being less than or equal to a second threshold value, A method in which the number of PRBs allocated for the first downlink channel exceeds the second threshold, and the reception of the first downlink channel is a repetitive reception or the second downlink channel is received in slot n+1, so that reception of the first downlink channel is not processed by the terminal.

10. In a terminal performing communication in a wireless communication system, the terminal: one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receiving a first downlink channel and a second downlink channel from a base station in a first slot through the one or more transceivers; and Based on the 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 value, the first downlink channel and the second downlink channel are set to be decoded, A terminal in which the first downlink channel and the second downlink channel partially or totally overlap in the time domain.

11. A method performed by a base station in a wireless communication system, the method comprising: A step of transmitting information for scheduling a first downlink channel and a second downlink channel to a terminal in a first slot; and A step of transmitting the first downlink channel and the second downlink channel to the terminal in the first slot, Based on the 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 are decoded by the terminal, A method wherein the first downlink channel and the second downlink channel partially or totally overlap in the time domain.

12. In a base station performing communication in a wireless communication system, the base station: one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting information for scheduling a first downlink channel and a second downlink channel to a terminal through one or more transceivers in a first slot; and The first downlink channel and the second downlink channel are set to be transmitted to the terminal through the one or more transceivers in the first slot, Based on the 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 are decoded by the terminal, A base station wherein the first downlink channel and the second downlink channel partially or totally overlap in the time domain.

13. In a processing device configured to control a terminal to perform communication in a wireless communication system, the processing device: one or more processors; and One or more computer memories operatively connected to said one or more processors and storing instructions that perform operations based on execution by said one or more processors, The above actions are: An operation of receiving a first downlink channel and a second downlink channel from a base station in a first slot; and An operation of decoding the first downlink channel and the second downlink channel based on the 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 value, A processing device wherein the first downlink channel and the second downlink channel partially or totally overlap in the time domain.

14. One or more non-transitory computer-readable media storing one or more instructions, The above one or more commands are executed by one or more processors, and the device performs communication in a wireless communication system: Receive a first downlink channel and a second downlink channel from a base station in a first slot; and Based on the 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 value, the first downlink channel and the second downlink channel are controlled to be decoded, A computer-readable medium wherein the first downlink channel and the second downlink channel partially or totally overlap in the time domain.

Citation Information

Patent Citations

  • Apparatus and method performed by the same in wireless communication system

    US20220322313A1

  • Method and apparatus for receiving pdsch, and processor-readable storage medium

    WO2022148184A1

Cited By

  • Reduced capability for broadcast and multicast in RRC inactive state

    US20240389120A1

  • Supporting multicast or broadcast operations with enhanced reduced capacity user equipment

    WO2025024199A3