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

Abstract

A method and apparatus for performing communication in a wireless communication system are disclosed. A method performed by a terminal according to one embodiment of the present disclosure 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 the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel and the second downlink channel, respectively, is less than or equal to a first threshold, wherein the first downlink channel and the second downlink channel overlap partially or totally in the time domain.

Description

Technical Field

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

Background Art

[0002] Mobile communication systems have been developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded their scope to include data services as well as voice, and currently, due to the explosive increase in traffic, there is a shortage of resources, and users are also demanding faster services. Therefore, a more advanced mobile communication system is desired.

[0003] The requirements for next-generation mobile communication systems are large, acceptance of explosive data traffic, epochal increase in transmission rate per user, acceptance of a significantly increased number of connected devices, very low end-to-end latency, and support for high energy efficiency. For this purpose, various technologies such as dual connectivity, massive multiple input multiple output (Massive MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being studied.

Summary of the Invention

Problems to be Solved by the Invention

[0004] A technical problem of the present disclosure is to provide a method and apparatus 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 apparatus for transmitting and receiving at least one unicast / multicast downlink in a narrow band.

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

[0007] The technical problem to be achieved in the present disclosure is not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those having ordinary knowledge in the technical field to which the present disclosure belongs from the following description.

Means for Solving the Problems

[0008] A method performed by a terminal in a wireless communication system according to an embodiment of the present disclosure includes 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 that the number of physical resource blocks (PRBs) assigned to each of the first downlink channel and the second downlink channel is 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] A method performed by a terminal in a wireless communication system according to one embodiment of the present disclosure 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 the reception of the first downlink channel based on the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel is less than or equal to a second threshold, wherein the reception of the first downlink channel does not need to be processed by the terminal if the number of PRBs allocated to the first downlink channel exceeds the second threshold, or if the reception of the first downlink channel is repeated, or if the second downlink channel is received in slot n+1.

[0010] A method performed by a base station in a wireless communication system according to one embodiment of the present disclosure 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 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, and the first downlink channel and the second downlink channel may partially or completely overlap in the time domain. [Effects of the Invention]

[0011] Various embodiments of this disclosure can provide a method and apparatus for performing downlink transmission and reception in a wireless communication system.

[0012] Various embodiments of this disclosure can provide a method and apparatus for sending and receiving at least one unicast / multicast downlink in a narrowband manner.

[0013] Various embodiments of this disclosure can provide a method and apparatus for processing multiple unicast / multicast downlinks received simultaneously in a narrowband.

[0014] Various embodiments of this disclosure enable enhanced reduced capability (eRedCap) terminals to handle downlinks scheduled in a single slot more efficiently.

[0015] The effects derived from this disclosure are not limited to those mentioned above, and any other effects not mentioned above will be clearly understood by a person with ordinary skill in the art to which this disclosure pertains from the following description. [Brief explanation of the drawing]

[0016] The accompanying drawings, included as part of the detailed description to aid in understanding this disclosure, provide examples relating to this disclosure and illustrate the technical features of this disclosure together with the detailed description. [Figure 1] This figure illustrates the structure of a wireless communication system to which this disclosure can be applied. [Figure 2] This figure illustrates a frame structure in a wireless communication system to which this disclosure can be applied. [Figure 3] This figure illustrates a resource grid in a wireless communication system to which this disclosure can be applied. [Figure 4] This figure illustrates a physical resource block in a wireless communication system to which this disclosure can be applied. [Figure 5] This figure illustrates a slot structure in a wireless communication system to which this disclosure can be applied. [Figure 6] This figure illustrates physical channels used in wireless communication systems to which this disclosure can be applied, and general signal transmission and reception methods using them. [Figure 7]This is a diagram illustrating the process by which a terminal according to one embodiment of the present disclosure performs communication. [Figure 8] This is a diagram illustrating the process by which a base station according to one embodiment of the present disclosure performs communication. [Figure 9] This diagram illustrates a case in which multiple channels overlap in the time domain according to one embodiment of the present disclosure. [Figure 10] This figure illustrates a case in which multiple channels according to one embodiment of the present disclosure do not overlap in the time domain. [Figure 11] This figure illustrates an embodiment of the present disclosure in which an MBS PDSCH is repeatedly allocated with a bandwidth exceeding 5 MHz. [Figure 12] This figure illustrates an embodiment of the present disclosure in which one or more channels are scheduled to a single slot. [Figure 13] This figure illustrates an embodiment of the present disclosure in which one or more channels are scheduled to a single slot. [Figure 14] This figure illustrates an embodiment of the present disclosure in which multiple channels are scheduled to a single slot. [Figure 15] This figure illustrates an embodiment of the present disclosure in which a number of PRBs exceeding the number corresponding to a 5MHz bandwidth are scheduled in a single slot. [Figure 16] This is a block diagram illustrating an example of a wireless communication device according to one embodiment of the present disclosure. [Modes for carrying out the invention]

[0017] Preferred embodiments relating to this disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of this disclosure and is not intended to represent the only possible embodiments of this disclosure. The detailed description below includes specific details to provide a complete understanding of this disclosure. However, those skilled in the art will understand that this disclosure is implementable without such specific details.

[0018] In some cases, to avoid ambiguity of the concepts in this disclosure, known structures and devices may be omitted, or they may be shown in the form of block diagrams focusing on the core function of each structure and device.

[0019] In this disclosure, when one component is “connected,” “joined,” or “linked” to another component, this may include not only direct connections but also indirect connections between them where other components exist. Also, in this disclosure, the terms “includes” or “have” identify the presence of the referred features, stages, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, stages, operations, elements, components and / or groups thereof.

[0020] In this disclosure, terms such as “first,” “second,” etc., are used solely to distinguish one component from another, and are not used to limit the components, nor do they limit the order or importance of the components unless otherwise specified. Therefore, 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.

[0021] The terms used in this disclosure are for illustrative purposes relating to specific embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and in the attached claims, singular forms are intended to include plural forms unless otherwise specified in the context. The terms “and / or” used in this disclosure may refer to one of the related enumerated items, or to any and all possible combinations of two or more of them. In this disclosure, “ / ” between words has the same meaning as “and / or” unless otherwise specified.

[0022] This disclosure describes a wireless communication network or wireless communication system, where operations performed in the wireless communication network may occur in the process of a device (e.g., a base station) controlling the network and transmitting or receiving signals, or in the process of a terminal connected to the wireless network transmitting or receiving signals to or from the network.

[0023] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.

[0024] In the following, downlink (DL) refers to communication from the base station to the terminal, and uplink (UL) refers to communication from the terminal to the base station. In the downlink, the transmitter may be part of the base station, and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal, and the receiver may be part of the base station. The base station may be referred to as the first communication device, and the terminal as the second communication device. The term Base Station (BS) may be replaced with terms such as fixed station, Node B, eNB (evolved-Node B), gNB (Next Generation Node B), BTS (base transceiver system), Access Point (AP), network (5G network), AI (Artificial Intelligence) system / module, RSU (roadside unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. Furthermore, the term "Terminal" may be fixed or mobile, and may be replaced by 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 (roadside unit), robot, AI (Artificial Intelligence) module, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, and VR (Virtual Reality) device.

[0025] The following technologies may be used in various wireless connection systems such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA may be implemented by wireless technologies such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA may be implemented by wireless technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA may be implemented by 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: registered trademark: hereinafter the same) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) which uses E-UTRA, and LTE-A (Advanced) / LTE-A pro are advanced versions of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A / LTE-A pro.

[0026] For clarity, the explanation will be based on 3GPP communication systems (e.g., LTE-A, NR), but the technical concepts of this disclosure are not limited thereto. LTE refers to 3GPP TS (Technical Specification) 36.xxx Release 8 and later technologies. More specifically, LTE technology from 3GPP TS 36.xxx Release 10 onwards is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards is called LTE-A pro. 3GPP NR refers to TS 38.xxx Release 15 and later technologies. LTE / NR may be referred to as a 3GPP system. "xxx" means the standard document detail number. LTE / NR may be referred to as a 3GPP system. For background information, terminology, abbreviations, etc., used in this disclosure, refer to the standard documents published prior to this disclosure. For example, refer to the following documents.

[0027] For 3GPP LTE, you can refer to 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).

[0028] For 3GPP NR, you can refer to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Standard).

[0029] Abbreviations of terms used in this disclosure are defined as follows:

[0030] - BM: Beam Management

[0031] - CQI: Channel Quality Indicator

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

[0033] - CSI: Channel State Information

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

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

[0036] - DMRS: Demodulation reference signal

[0037] - FDM: Frequency Division Multiplexing

[0038] - FFT: Fast Fourier Transform

[0039] - IFDMA: Interleaved frequency division multiple access

[0040] - IFFT: Inverse Fast Fourier Transform

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

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

[0043] - MAC: Medium Access Control

[0044] - NZP: Non-Zero Power

[0045] - OFDM: Orthogonal frequency division multiplexing

[0046] - PDCCH: Physical Downlink Control Channel

[0047] - PDSCH: Physical Downlink Shared Channel

[0048] - PMI: Precoding matrix indicator

[0049] - RE: Resource element

[0050] - RI: Rank indicator

[0051] - RRC: Radio Resource Control

[0052] - RSSI: received signal strength indicator

[0053] - Rx: Reception

[0054] - QCL: quasi co-location

[0055] - SINR: Signal-to-interference and noise ratio

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

[0057] - TDM: time division multiplexing

[0058] - TRP: Transmission and Reception Point

[0059] - TRS: Tracking Reference Signal

[0060] - Tx: transmission

[0061] - UE: User equipment

[0062] - ZP: Zero Power

[0063] General System

[0064] As more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Massive Machine Type Communications (MTC), which connects multiple devices and things to provide various services anytime, anywhere, is also a major consideration in next-generation communications. In addition, communication system design that takes into account reliability and latency-sensitive services / terminals is being discussed. Thus, the introduction of next-generation RATs that consider eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc., is being discussed, and for convenience in this disclosure, this technology will be referred to as NR. NR is an expression representing an example of 5G RAT.

[0065] The new RAT system, including NR, uses an OFDM transmission scheme or a similar 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 with different numerologies may coexist within a single cell.

[0066] 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.

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

[0068] Referring to Figure 1, the NG-RAN consists of gNBs that provide control plane (RRC) protocol termination for the NG-RA (NG-Radio Access) user plane (i.e., the new AS (access stratum) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and UE. The gNBs are interconnected via the Xn interface. 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.

[0069] Figure 2 illustrates a frame structure in a wireless communication system to which this disclosure can be applied.

[0070] The NR system can support multiple numerologies, which may be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings may be derived by scaling the fundamental (reference) subcarrier spacing by an integer N (or μ). Furthermore, even assuming that very low subcarrier spacings are not used at very high carrier frequencies, the numerologies used may be selected independently of the frequency band. The NR system may also support various frame structures based on multiple numerologies.

[0071] The following describes the OFDM numerologies and frame structures that can be considered in the NR system. The multiple OFDM numerologies supported in the NR system may be defined as shown in Table 1 below.

[0072] [Table 1]

[0073] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, an SCS of 15kHz supports wide area in the traditional cellular band; an SCS of 30kHz / 60kHz supports dense-urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60kHz or higher supports bandwidths greater than 24.25GHz to overcome phase noise. An NR frequency band is defined as two types (FR1, FR2) of frequency ranges. FR1 and FR2 may be configured as shown in Table 2 below. Also, FR2 can mean millimeter wave (mmW).

[0074] [Table 2]

[0075] In relation to the frame structure in an NR system, the sizes of various fields in the time domain are T c = 1 / (Δf max ·N f It is expressed as a multiple of the time unit of ). Here, Δf max =480·10 3 It is Hz, N fis 4096. Downlink and uplink transmissions are at T f = 1 / (Δf max N f / 100)·T c are composed of radio frames having an interval of T = 10 ms. Here, each radio frame has T sf =(Δf max N f / 1000)·T c and is composed of 10 subframes having an interval of 1 ms. In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Also, the transmission at the uplink frame number i from the terminal must start T TA =(N TA +N TA,offset )T c before the start of the corresponding downlink frame at the terminal. For the subcarrier interval configuration μ, the slot is numbered in ascending order of n s μ ∈{0,...,N slot subframe,μ -1} within the subframe and in ascending order of n s,f μ ∈{0,...,N slot frame,μ -1} within the radio frame. One slot is composed of N symb slot consecutive OFDM symbols, and N symb slot is determined by the CP. In the subframe, the start of slot n s μ is the OFDM symbol n s μ N symb slotThe start and timing are aligned. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in the 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 ), Number of slots per wireless frame (N slot frame,μ ), Number of slots per subframe (N slot subframe,μ Table 4 shows the number of OFDM symbols per slot, the number of slots per wireless frame, and the number of slots per subframe in the extended CP.

[0076] [Table 3]

[0077] [Table 4]

[0078] Figure 2 shows an example where μ=2 (SCS is 60kHz), and referring to Table 3, one subframe may contain four slots. The one subframe = {1,2,4} slots shown in Figure 2 is just an example, and the number of slots that can be included in one subframe is defined as shown in Table 3 or Table 4. Also, a mini-slot may contain two, four, or seven symbols, or more or fewer symbols. In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. may be considered. The following describes in detail the physical resources that can be considered in an NR system. First, in relation to antenna ports, an antenna port is defined so that the channel on which symbols on the antenna port are carried can be inferred from the channels on which other symbols on the same antenna port are carried. Two antenna ports can be said to be in a QC / QCL (quasi co-located or quasi co-location) relationship if the large-scale property of the channel carrying symbols on one antenna port can be inferred from the channel carrying symbols on another antenna port. Here, the large-scale property includes one or more of the following: delay spread, Doppler spread, frequency shift, average received power, and received timing. Figure 3 illustrates a resource grid in a wireless communication system to which this disclosure can be applied.

[0079] Referring to Figure 3, the resource grid is N in the frequency domain. RB μ N sc RBIt consists of subcarriers, with one subframe being 14.2 μ This description exemplifies the use of OFDM symbols, but is not limited to them. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids and 2 subcarriers μ N symb (μ) This is explained by the OFDM symbol, where N RB μ ≤N RB max,μ The above N RB max,μ This represents the maximum transmit bandwidth, which may vary not only between the uplink and downlink but also between the numerology. In this case, one resource grid may be configured for each μ and antenna port p.

[0080] JPEG2026517926000006.jpg76168

[0081] Point A acts as the common reference point for the resource block grid and is obtained as follows:

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

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

[0084] Common resource blocks are numbered upwards from 0 in the frequency domain relative to the subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 relative to the subcarrier spacing setting μ coincides with 'point A'. In the frequency domain, common resource block number n... CRB μ The relationship between the resource element (k,l) and the subcarrier spacing μ is given by Equation 1 below.

[0085]

number

[0086] In Equation 1, k is defined relative to point A such that k=0 corresponds to a subcarrier centered at point A. The physical resource block ranges from 0 to N within the bandwidth part (BWP). BWP,i size,μ The numbers are assigned down to -1, where i is the BWP number. In BWP i, the physical resource block n PRB and common resource block n CRB The relationship between them is given by equation 2 below.

[0087]

number

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

[0089] Figure 4 illustrates a physical resource block in a wireless communication system to which this disclosure can be applied. Figure 5 illustrates a slot structure in a wireless communication system to which this disclosure can be applied.

[0090] Referring to Figures 4 and 5, a slot contains multiple symbols in the time domain. For example, in a general CP, one slot contains seven symbols, while in an extended CP, one slot contains six symbols.

[0091] A carrier wave contains 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 may correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier wave may contain up to N (e.g., 5) BWPs. Data communication takes place over activated BWPs, and only one BWP may be activated for a single terminal. In a resource grid, each element is called a Resource Element (RE) and may be mapped to a single complex symbol.

[0092] An NR system may support up to 400 MHz per component carrier (CC). If a terminal operating on such a wideband CC keeps its radio frequency (RF) chip on for the entire CC at all times, terminal battery consumption may increase. Alternatively, considering various use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing) may be supported for each frequency band within that CC. Alternatively, terminals may have different capabilities for the maximum bandwidth. Taking this into consideration, a base station may instruct terminals to operate only on a portion of the wideband CC's bandwidth rather than the entire bandwidth, and this portion of the bandwidth is conveniently defined as a bandwidth part (BWP). A BWP may consist of consecutive RBs on the frequency axis and may correspond to a single numerology (e.g., subcarrier spacing, CP length, slot / minislot interval).

[0093] On the other hand, a base station can configure multiple BWPs within a single CC configured on a terminal. For example, a PDCCH monitoring slot can be configured with a BWP occupying a relatively small frequency range, while a PDSCH instructed by the PDCCH may be scheduled on a larger BWP. Alternatively, if UEs are concentrated on a particular BWP, other BWPs may be configured on some terminals for load balancing. Or, considering frequency domain inter-cell interference cancellation between adjacent cells, a portion of the spectrum from the total bandwidth can be excluded, and both BWPs can be configured within the same slot. In other words, a base station can configure at least one DL / UL BWP on terminals associated with a broadband CC. A base station can activate at least one of the DL / UL BWPs configured at a given time (by L1 signaling, MAC CE (Control Element), or RRC signaling, etc.).

[0094] Furthermore, the base station can instruct switching to another configured DL / UL BWP (by L1 signaling, MAC CE, or RRC signaling, etc.). Alternatively, it may switch to a designated DL / UL BWP when a timer expires. In this case, the activated DL / UL BWP is defined as the active DL / UL BWP. However, in situations such as when a terminal is in the initial access process or before the RRC connection is set up, the configuration for the DL / UL BWP may not be received. In such situations, the DL / UL BWP assumed by the terminal is defined as the initial active DL / UL BWP.

[0095] Figure 6 illustrates physical channels used in wireless communication systems to which this disclosure can be applied, and general signal transmission and reception methods using them.

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

[0097] When a terminal is powered on or enters a new cell, it performs initial cell search operations, such as synchronizing with the base station (S601). To do this, 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 the cell identifier (ID). Subsequently, the terminal receives the physical broadcast channel (PBCH) from the base station to obtain intra-cell broadcast information. Meanwhile, during the initial cell search phase, the terminal can receive a downlink reference signal (DL RS) to check the downlink channel status.

[0098] Once the terminal has completed its initial cell search, it can receive the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) via the information carried on the PDCCH, thereby obtaining more specific system information (S602).

[0099] On the other hand, if the terminal is initially connected to a base station or does not have radio resources for signal transmission, it can perform a Random Access Procedure (RACH) to the base station (stages S603 to S606). To do this, the terminal transmits a specific sequence as a preamble over a Physical Random Access Channel (PRACH) (S603 and S605), and can receive a response message to the preamble on the PDCCH and the corresponding PDSCH (S604 and S606). In the case of a conflict-based RACH, a Contention Resolution Procedure can also be performed.

[0100] A terminal that has performed the procedures described above can then perform general uplink / downlink signal transmission procedures, such as receiving PDCCH / PDSCH (S607) and transmitting Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) (S608). In particular, the terminal receives Downlink Control Information (DCI) via PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format differs depending on its purpose of use.

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

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

[0103] [Table 5]

[0104] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 can include resource information related to PUSCH scheduling (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.), multiplex antenna related information (e.g., DMRS sequence initialization information, antenna ports, CSI requests, etc.), and power control information (e.g., PUSCH power control, etc.). The control information included in each DCI format may be predefined. DCI format 0_0 is used for PUSCH scheduling in a single cell. Information contained in DCI format 0_0 is transmitted after being scrambled with CRC (cyclic redundancy check) 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 instruct terminals on scheduling one or more pushes in a single cell, or configured grant (CG: configured grant) downlink feedback information. Information contained in DCI format 0_1 ​​is transmitted after being scrambled with CRC by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI.

[0105] DCI format 0_2 is used for scheduling pushes within a single cell. The information contained in DCI format 0_2 is CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI before transmission.

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

[0107] DCI format 1_0 is used for PDSCH scheduling in a single DL cell. The information contained in DCI format 1_0 is CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI before transmission.

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

[0109] DCI format 1_2 is used for PDSCH scheduling within a single cell. The information contained in DCI format 1_2 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0110] (e) Downlink transmission and reception method for RedCap terminals

[0111] As mentioned above, services that take into account eMBB, URLLC, and the massive internet of things (mIoT) are provided on wireless communication systems (e.g., NR). For example, a hybrid service that takes into account eMBB, URLLC, and mIoT may be provided on a wireless communication system. Here, mIoT requires optimization of power consumption rather than high performance such as carrier aggregation (e.g., high transmission speed).

[0112] In recent years, the widespread use of smart factories and / or wearable devices has increased the need for new terminal types that are low-power and URLLC-compliant. This led to the introduction of reduced capability (RedCap) terminals (i.e., R17 RedCap terminals) in 3GPP NR Release 17. RedCap terminals can communicate using narrow bandwidth or frequency resources on a narrow bandwidth. For example, RedCap terminals can reduce power consumption and costs by using up to 20MHz or 5MHz instead of the existing 100MHz bandwidth.

[0113] Subsequently, eRedCap terminals were introduced in 3GPP NR Release 18. eRedCap terminals are similar to RedCap terminals in that they operate in a 20MHz bandwidth. However, in the case of eRedCap terminals, unicast PDSCHs and / or PUSCHs (i.e., C-RNTI-based PDSCHs and / or PUSCHs) may be allocated within a maximum bandwidth of 5MHz. That is, PRBs of unicast PUSCH / PDSCHs corresponding to a maximum bandwidth of 5MHz may be allocated to eRedCap terminals. In this case, unicast PUSCH / PDSCHs may be indicated / allocated to eRedCap terminals by the DCI's FDRA (frequency domain resource assignment) field, etc.

[0114] Additionally, in the case of eRedCap terminals, various RNTI base channels related to paging, system information blocks (SIB), RACH, etc., may be allocated within a 20MHz bandwidth. That is, eRedCap terminals may be allocated PRBs for various RNTI base channels that support a maximum bandwidth of 20MHz (same as RedCap terminals).

[0115] An eRedCap terminal can process data (e.g., PRBs) corresponding to a maximum bandwidth of 5 MHz within a single slot. If channels exceeding a 5 MHz bandwidth are scheduled / allocated, the eRedCap terminal may require additional processing time margin. For unicast channels, scheduling may be performed separately for each slot, and thus the eRedCap terminal may be allocated PRBs corresponding to the maximum bandwidth (e.g., 5 MHz) (e.g., 25 PRBs if the SCS is 15 kHz, or 12 PRBs if the SCS is 30 kHz).

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

[0117] This disclosure relates to a method for an MBS (multicast broadcasting service) related downlink (DL) channel (e.g., a group common channel) to efficiently receive MBS-related downlink (DL) channels (e.g., a group common channel) as described above. Here, the MBS-related DL channels may include DL channels scheduled by DCI scrambled with CRC by MCCH (MBS control channel)-RNTI, G(group)-RNTI, or G(group)-CS-RNTI (e.g., PDSCH). When describing this disclosure, the term MBS channel can refer collectively to MBS-related (DL / UL) channels.

[0118] Unlike unicast channels, MBS-related channels can be transmitted to multiple terminals simultaneously. When an eRedCap terminal receives an MBS-related channel within a 5MHz bandwidth, it may be inefficient from the perspective of other types of terminals (e.g., R17 RedCap terminals) that also receive the same MBS-related channel. If an eRedCap terminal can receive / use the channel within a 20MHz bandwidth along with other common channels, the likelihood of sharing the channel with other types of terminals increases, which can improve efficiency from a network operation perspective.

[0119] An MBS channel may have all the SIB broadcast and unicast properties of a common channel. Therefore, when describing this disclosure, MBS channels will be described as being divided into broadcast / broadcasting channels and multicasting / multicasting channels (by bandwidth). That is, when an MBS channel is transmitted to an eRedCap terminal, a limit may be applied to the bandwidth to which the MBS channel is transmitted. If there is no limit to the bandwidth to which the MBS channel is transmitted, an additional margin may be applied to the processing time of the MBS channel.

[0120] When describing this disclosure, the fact that an eRedCap terminal drops a specific channel can be interpreted as meaning that it does not skip that channel, nor is it expected / required to decode that channel. Also, in the case of an eRedCap terminal, the fact that PRBs up to 20MHz bandwidth may be allocated / scheduled can be interpreted as meaning that PRBs exceeding a specific bandwidth (e.g., 5MHz) may be allocated / scheduled.

[0121] As an example of this disclosure, if the MBS channel is a broadcast channel, the eRedCap terminal may allocate / schedule the MBS channel within a maximum bandwidth of 20 MHz, in the same way as the SIB. In this case, the broadcast channel may be scheduled by DCI scrambled with CRC by MCCH-RNTI or G-RNTI. While the eRedCap terminal can receive the SIB within a maximum bandwidth of 20 MHz, the eRedCap terminal may also allocate / schedule the broadcast channel, to which the HARQ process (i.e., the ACK / NACK response transmission / reception process, etc.) does not apply, within a maximum bandwidth of 20 MHz.

[0122] As yet another example of this disclosure, if the MBS channel is a multicast channel, the multicast channel may be scheduled by DCI (e.g., DCI format 4_1 or 4_2) scrambled by G-RNTI or G-CS-RNTI. Multicast channels, like broadcast channels, may be scheduled / allocated within a maximum bandwidth of 20 MHz. However, if the HARQ process is applied to the multicast channel (i.e., if the ACK / NACK response transmission / reception process is applied), additional processing time (e.g., x ms or OFDM symbol length units) may be applied to the processing time predefined in Table 6 (PDSCH processing time for PDSCH processing capacity 1) and Table 7 (PDSCH processing time for PDSCH processing capacity 2).

[0123] [Table 6]

[0124] [Table 7]

[0125] Additionally, if ACK / NACK information transmission is not configured for an MBS-based multicast channel, 20MHz may be selectively used.

[0126] Additionally, there may be a method for setting the multicasting HARQ feedback mode in the method described above. For example, RRC signaling to set the MBS-based HARQ mode may be sent to the eRedCap terminal, and the RRC signaling may include the information disclosed in Table 8 below.

[0127] [Table 8]

[0128] As an example of this disclosure, the enabler for HARQ may be indicated / set by DCI and / or RRC signaling. When the enabler for HARQ is indicated by DCI, the ACK / NACK mode or NACK-only mode may be indicated. As yet another example, the HARQ-ACK feedback related operation / mode may be indicated by the HARQ-ACK feedback indicator enable / disabling field included in DCI format 4_1. The HARQ-ACK feedback indicator enable / disabling field may be set to 1 bit when "harq-FeedbackOptionMulticast" indicates "dci-enabler". When the HARQ-ACK feedback indicator enable / disabling field value is set to 1, the HARQ-ACK feedback is indicated to be enabled, and when the HARQ-ACK feedback indicator enable / disabling field value is set to 0, the HARQ-ACK feedback is indicated to be disabled. If the RRC signaling “Harq-FeedbackEnable rMulticast-r17” is not sent, HARQ feedback may always be deactivated. “Harq-FeedbackEnablerMulticast” can indicate whether a terminal must provide HARQ feedback for MBS multicast. The “dci-enabler” value set by “Harq-FeedbackEnablerMulticast” can mean whether a terminal must provide HARQ feedback for MBS multicast. This disclosure distinguishes between cases where HARQ-related behavior is controlled by RRC or DCI when HARQ feedback is deactivated.

[0129] In addition, this disclosure may apply not to terminals that can process the entire RF bandwidth, but to terminals where the number of PRBs that can be processed in the BB baseband is limited to the number of PRBs corresponding to a 5 MHz bandwidth.

[0130] Furthermore, this disclosure may apply to terminals that can process both channels simultaneously when two channels are scheduled in a single slot, or to terminals that cannot process either one of the channels. Processing even one of the two channels would be better from a service perspective than not being able to process either channel at all. Therefore, this disclosure describes a priority system for two channels and a method for simultaneous reception.

[0131] As an example of this disclosure, an eRedCap terminal does not need to 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 the OFDM symbol. Furthermore, a PDSCH scheduled by SI-RNTI may be based on the acquisition of a P-RNTI-triggered SI.

[0132] Figure 7 is a diagram illustrating the process by which a terminal communicates according to one embodiment of the present disclosure. The terminals in Figures 7 and 8 may, but are not limited to, enhanced reduced capability (eRedCap) terminals (i.e., terminals indicating support for R18 redCap terminals). The terminal in Figure 7 may include a RedCap terminal or a general terminal.

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

[0134] Prior to the S710 stage, the terminal can transmit capacity information to the base station indicating that it supports the reception of a first and second downlink channel that are frequency-division multiplexed (FDMed) in a single slot.

[0135] This allows the base station to identify that the terminal can receive the first and second downlink channels, which are FDM-processed in a single slot. The base station can then send information to the terminal in the first slot to schedule the first and second downlink channels. The base station can then send the first and second downlink channels to the terminal in the first slot.

[0136] As an example of this 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.

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

[0138] In other words, 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 one embodiment, and the (repeated) transmission of the first and / or second downlink channels may be set / instructed by MAC CE or RRC signaling.

[0139] Here, the first downlink channel and the second downlink channel may partially or totally overlap in the time domain. The PRBs assigned to the first downlink and the second downlink, respectively, do not need to overlap (in the frequency domain).

[0140] Based on the fact that the number of PRBs assigned to the first downlink channel and the second downlink channel is less than or equal to the first threshold, the terminal can decode the first downlink channel and the second downlink channel (S720).

[0141] For example, the first threshold may be 25 based on a subcarrier spacing (SCS) of 15 kHz, and the first threshold may be 12 based on a SCS of 30 kHz.

[0142] For example, if the number of PRBs assigned to the first downlink channel and the second downlink channel exceeds a first threshold, the terminal may skip decoding one of the two downlink channels.

[0143] The method illustrated in Figure 7 may be carried out by the first device 100 and the second device 200 in Figure 16. That is, a terminal may be embodied as the first device 100 in Figure 16, and a base station may be embodied as the second device 200. For example, one or more processors 102 of the first device 100 in Figure 16 can receive the first downlink channel and the second downlink channel from the second device 200 via one or more transceivers in the first slot. 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 via one or more transceivers 206. Based on the fact that the number of PRBs allocated to the first downlink channel and the second downlink channel is less than or equal to a first threshold, one or more processors 102 can decode the first downlink channel and the second downlink channel.

[0144] Furthermore, one or more memories 104 of the first device 100 can store instructions for performing the method described in the example in Figure 8 or in the examples described later, when executed by one or more processors 102.

[0145] Figure 8 is a diagram illustrating the process by which a terminal communicates according to one embodiment of the present disclosure.

[0146] The terminal can receive the first downlink channel from the base station in slot n (where n is a non-negative integer) (S810).

[0147] In other words, the terminal can receive information from the base station to schedule the first downlink channel in slot n.

[0148] 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 has been CRC scrambled by an MCCH-RNTI or G-RNTI.

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

[0150] In other words, based on the fact that the number of PRBs allocated to the first downlink channel is less than or equal to the second threshold, the terminal can process / decode the scheduling of the first downlink channel.

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

[0152] For example, if the number of PRBs allocated to the first downlink channel exceeds the second threshold, and the reception of the first downlink channel is repeated, or the second downlink channel is received in slot n+1, the reception of the first downlink channel does not need to be processed by the terminal. In other words, if the number of PRBs allocated to the first downlink channel exceeds the second threshold, and the reception of the first downlink channel is repeated, or the second downlink channel is received in slot n+1, the terminal does not need to be required to process the first downlink channel received in slot n.

[0153] The method illustrated in Figure 9 may be carried out by the first device 100 and the second device 200 in Figure 16. That is, a terminal may be embodied as the first device 100 in Figure 16, and a base station may be embodied as the second device 200. For example, one or more processors 102 of the first device 100 in Figure 16 can receive the first downlink channel from the second device 200 via one or more transceivers 106 in slot n (where n is a non-negative integer). That is, one or more processors 202 of the second device 200 can transmit the first downlink channel to the first device 100 via one or more transceivers 206 in slot n (where n is a non-negative integer). Based on the fact that the number of PRBs allocated to the first downlink channel is less than or equal to a second threshold, one or more processors 102 can process the reception of the first downlink channel.

[0154] Furthermore, one or more memories 104 of the first device 100 can store instructions for performing the method shown in the example in Figure 9 or described in the examples later, when executed by one or more processors 102.

[0155] The following describes various methods for a terminal (e.g., an eRedCap terminal) to receive MBS channels in a narrowband environment.

[0156] Example 1

[0157] Example 1 relates to a method for separately managing bandwidth according to the HARQ feedback configuration of multicasting.

[0158] For broadcasting (or broadcast channel / transmission), since there is no HARQ feedback, the procedure may be similar to that for sending and receiving SIB or paging information. However, for multicasting, three HARQ feedback modes (e.g., ACK / NACK mode, NACK-only mode, NO HARQ mode) may be set / executed.

[0159] Here, the ACK / NACK mode also applies to basic unicast transmit and receive procedures, and the NO HARQ mode can be used to refer to procedures in which ACK / NACK transmission is not performed, similar to the SIB or paging information transmit and receive procedures. The NACK-only mode may be applied to MBS-based multicast channel transmit and receive procedures. The NACK-only mode is a general term for modes in which feedback information is not transmitted when ACK is present, and NACK-based feedback is transmitted when NACK is present.

[0160] As described above, in the case of broadcasting transmissions where HARQ ACK / NACK transmission is not configured, no additional processing time relaxation procedure is required, and a bandwidth of up to 20 MHz may be used. However, in the case of ACK / NACK or NACK-only mode, if a 20 MHz bandwidth is used, additional relaxation time may be required. Therefore, in Example 1, the bandwidth management method using HARQ feedback during multicast channel transmission and reception will be described.

[0161] Example 1-1

[0162] Example 1-1 relates to a multicasting operation (i.e., operation of the transmit and receive procedure for multicast channels) within a maximum bandwidth of 20 MHz when NO HARQ mode is applied.

[0163] If the NO HARQ mode is set by higher-layer signaling (e.g., RRC signaling) or if the real-time HARQ mode is indicated as NO or dynamic in DCI format 4_2, a multicasting operation scheme may be performed within a bandwidth of up to 20 MHz. Additionally or alternatively, if the NO HARQ mode is indicated by DCI or if the HARQ deactivation mode is indicated by RRC signaling, a multicasting operation scheme may be performed within a bandwidth of up to 20 MHz.

[0164] Examples 1-2

[0165] Examples 1-2 relate to a scheme in which, when ACK / NACK mode or NACK-only mode is instructed / set, multicast channels are restricted to being allocated / scheduled within a 5MHz bandwidth. That is, when ACK / NACK mode or NACK-only mode is instructed / set, multicast channels may be allocated / scheduled in quantities equal to the number of PRBs corresponding to a 5MHz bandwidth.

[0166] If HARQ feedback is configured by upper-layer signaling, or if real-time HARQ mode is indicated as NO or dynamically in DCI format 4_2, multicast channels may be limited to being allocated / scheduled within a 5MHz bandwidth. Additionally or alternatively, if HARQ feedback is indicated to be enabled by DCI, or if NO HARQ mode is indicated by DCI, multicast channels may be allocated / scheduled to the number of PRBs corresponding to the 5MHz bandwidth.

[0167] As an example of this disclosure, multicast channel transmission and reception may be performed within a maximum bandwidth of 20 MHz only when NACK-only mode is applied (for example, when NACK-only mode is set by RRC signaling), which can improve operational flexibility.

[0168] Examples 1-1 and 1-2 may utilize the three HARQ feedback modes described above, but additional HARQ feedback modes may be used. For example, multicasting (i.e., sending and receiving multicast channels) may be performed only in RRC_inactive mode or RRC_connected mode. For example, RRC signaling may be configured to apply multicasting only in RRC_inactive mode or RRC_connected mode.

[0169] As an addition or alternative, RRC signaling may be configured to utilize Examples 1-1 and 1-2 only when the terminal type is an eRedCap terminal. In yet another example, RRC signaling may be configured to apply ACK / NACK mode or NACK-only mode exclusively to eRedCap terminals.

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

[0171] Examples 1-3

[0172] As one embodiment of the present disclosure, if the number of PRBs scheduled by multicasting exceeds the number of PRBs corresponding to a 5MHz bandwidth, the system is processed as NO HARQ mode, and if the number of PRBs scheduled by multicasting is less than or equal to the number of PRBs corresponding to a 5MHz bandwidth, an ACK or NACK may be transmitted.

[0173] The above-described embodiment is a new HARQ mode, which may be configured for the eRedCap terminal by RRC signaling. When an ACK / NACK mode or NACK-only mode is configured, the base station may configure multicast channels to be greater than or less than the number of PRBs corresponding to a 5MHz bandwidth. In this case, if there is no HARQ feedback, the base station can recognize this as a NACK or an ACK.

[0174] As yet another example of this disclosure, when NACK-only mode is set, scheduling may be permitted only for the number of PRBs corresponding to a 20 MHz bandwidth. Scheduling may be permitted only for the number of PRBs corresponding to a 20 MHz bandwidth if a PUCCH resource is set for NACK-only base feedback transmission or if NACK-only mode is set by RRC signaling.

[0175] Examples 1-3 relate to a method for processing / determining HARQ feedback based on the terminal's capacity, rather than based on the number of PRBs corresponding to a specific bandwidth, by deciding whether to send ACK / NACK (or NACK-only) or not send feedback. In other words, Examples 1-3 may be processed by the terminal implementation. Additionally or alternatively, when more than a certain number of PRBs are scheduled for an eRedCap terminal, the presence or absence of feedback transmission and reception may be determined by the terminal's capacity.

[0176] Examples 1-4

[0177] As one embodiment of this disclosure, when MBS-related information is set (i.e., when broadcast or multicast data / channel is sent or received), repetitive transmission may be performed / applied only within a specific bandwidth (e.g., 5 MHz BWP in the case of an eRedCap terminal). In this case, the repetitive operation may be performed only within the specific bandwidth regardless of whether HARQ feedback is present or not.

[0178] Examples 1-5

[0179] As one embodiment of the present disclosure, assume that in the case of a narrowband terminal (e.g., an eRedCap terminal), more PRBs are scheduled than the number of PRBs corresponding to the bandwidth that can be processed within a single slot (e.g., in the case of eRedCap, the number of PRBs corresponding to a 5MHz bandwidth). In this case, if feedback is required for the scheduling, the eRedCap terminal does not need to be expected to complete decoding within the PDSCH processing time, nor is it required to send feedback.

[0180] Examples 1-6

[0181] In one embodiment of this disclosure, the HARQ feedback procedure may be omitted when repeated transmissions are performed. In this case, when multicast channels are transmitted and received, scheduling may be performed within the maximum bandwidth (for example, up to 20 MHz in the case of an eRedCap terminal).

[0182] Examples 1-7

[0183] As one embodiment of the present disclosure, assume that the HARQ feedback mode for multicast PDSCH transmission is set to ACK / NACK mode or NACK-only mode. In this case, if more PRBs are scheduled than the number of PRBs corresponding to a specific bandwidth (for example, up to 5 MHz for eRedCap terminals), the terminal can transmit a PUCCH containing NACK information to the base station.

[0184] Examples 1-8

[0185] As one embodiment of the present disclosure, a multicast SPS PDSCH (i.e., SPS transmission) may be allocated / scheduled within a maximum bandwidth of 5 MHz. The above-described operation may also apply to PDSCHs scheduled by DCIs scrambled with G-CS-RNTI. As yet another example, the above-described operation may be applied until the SPS operation of the multicast SPS PDSCH is deactivated.

[0186] If the initial PDCCH schedules more PRBs than the number corresponding to a specific bandwidth, problems may occur with PDSCH reception until SPS operation is deactivated. Therefore, SPS transmission may be restricted to occur within a 5 MHz bandwidth.

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

[0188] When SPS transmission is activated or deactivated by DCI (e.g., DCI scrambled by G-CS-RNTI), ACK / NACK transmission may occur even if HARQ feedback is disabled for the first or last DCI. On the other hand, ACK / NACK transmission may also occur if more PRBs than the number corresponding to a specific 5MHz bandwidth are scheduled. In this case, if the base station cannot instruct the eRedCap terminal to provide a sufficient K1 value (i.e., the time delay value from the time the PDSCH is transmitted until the ACK / NACK is transmitted), or if it cannot provide an insufficient K1 value (i.e., if HARQ feedback transmission is difficult), the eRedCap terminal may unconditionally transmit a NACK (e.g., skip or drop the PDSCH transmission) or perform an action based on terminal implementation. As yet another example, a specific K1 value x may be instructed / defined / set, and the eRedCap terminal can expect a K1 value greater than or equal to x. When a K1 value less than or equal to x is indicated, the eRedCap terminal can send a NACK (for example, skip or drop the PDSCH transmission) or perform an action through terminal embodiment.

[0189] For example, in the case of G-RNTI, the number of PRBs (Prescription Relay Breakers) corresponding to a 5MHz bandwidth may be scheduled at or below the number of PRBs corresponding to a 5MHz bandwidth, depending on whether HARQ feedback is activated or deactivated. In the case of G-CS-RNTI, the number of PRBs corresponding to a 5MHz bandwidth may be scheduled at or below the number of PRBs corresponding to a 5MHz bandwidth, regardless of whether HARQ feedback is activated or deactivated.

[0190] Examples 1-8

[0191] As one embodiment of the present disclosure, if HARQ feedback and associated RRC signaling (e.g., "Harq-FeedbackEnablerMulticast-r17") are not sent to the terminal, HARQ feedback may be disabled. In this case, multicast PDSCH may be scheduled on a BWP of up to 20 MHz. If the HARQ feedback and associated RRC signaling are sent to the terminal, multicast PDSCH may be scheduled in numbers equal to the number of unicast-based terminal processing PRBs (e.g., for a RedCap terminal, the number of PRBs corresponding to a 5 MHz bandwidth).

[0192] As an example of this disclosure, when a HARQ process ID is deactivated, a terminal (e.g., a non-RedCap terminal) is not expected to receive another PDCCH that transmits a DCI scheduling a PDSCH or slot aggregation PDSCH set for a given HARQ process, or after the reception of the last PDSCH or slot aggregation PDSCH for that HARQ process has finished, T proc,1 For a given HARQ process starting up to , it is not necessary to expect to receive other PDSCHs without that PDCCH. That is, if consecutive PDCCHs are scheduled for the same HARQ process ID, the terminal will not expect to receive any other PDSCHs. proc,1During this time, it is not necessary to expect to receive a PDSCH or PDCCH. On the other hand, while an eRedCap terminal can process PRBs corresponding to a 5MHz bandwidth in a single slot, if more PRBs (e.g., PRBs for multicast channels) are scheduled than the number of PRBs corresponding to a 5MHz bandwidth, additional time may be applied to the eRedCap terminal for PRB processing. This can increase the stability of multicast PDSCH processing on the eRedCap terminal.

[0193] Examples 1-9

[0194] As one embodiment of this disclosure, we assume that scheduling is performed consecutively on a deactivated HARQ process ID. Conventionally, T proc,1 If scheduling is not expected to occur within a given time, but PRB scheduling of 5MHz or higher (e.g., PRB for multicast channels) is performed, an additional processing time margin may be set / instructed for the eRedCap terminal.

[0195] For example, the processing time margin may be defined as 1 slot. That is, if a PRB corresponding to a 5MHz bandwidth is allocated, the terminal will be "T proc1 With the +1 slot (for example, 1 sm for 15 kHz SCS and 0.5 ms for 30 kHz SCS), you don't need to expect reception of other PDC channels.

[0196] Examples 1-10

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

[0198] Examples 1-11

[0199] eRedCap terminals may be restricted from being assigned consecutive process IDs if they have a disabled HARQ process ID.

[0200] Example 2

[0201] Example 2 concerns a processing method when an MBS channel is FDM-processed in the same slot as other channels, but they overlap in OFDM symbols. Example 1 concerns a single MBS channel, while Example 2 concerns a case where multiple channels are multiplexed in the frequency domain within the same slot and overlap in OFDM symbols.

[0202] Specifically, Example 2 relates to a processing method when multiple PDSCH channels overlap in the time domain, as shown in Figure 9. Example 2 may be limited to the RRC_Connected state, but is not limited to that and may also be applied to the RRC_Inactive state. Furthermore, Example 2 relates to an eRedCap terminal capable of processing PDSCHs that can be allocated a 5MHz bandwidth in one slot.

[0203] Example 2-1

[0204] In one embodiment of the present disclosure, if broadcasting (i.e., a broadcast base channel) overlaps with other PDSCHs, the terminal can decode both the broadcast base channel and the other PDSCHs. In this case, the broadcast base channel may be limited to scheduling only as many PRBs as there are corresponding to a 5 MHz bandwidth.

[0205] For example, a broadcast base channel may overlap with a unicast PDSCH in a single slot. In this case, the broadcast base channel may include the MCCH-RNTI and its associated broadcast channel (i.e., the MBS PDSCH) and / or the MBS PDSCH. For example, scheduling may be limited to the number of PRBs corresponding to a 5MHz bandwidth only for the broadcast channel associated with the MCCH-RNTI, but not limited to this. The terminal can then transmit terminal capacity related to overlap processing between the broadcasting base channel and other channels to the base station.

[0206] As an example of this disclosure, if a broadcast base channel and a PDSCH scheduled by a DCI scrambled with C-RNTI (hereinafter referred to as a PDSCH associated with C-RNTI) overlap in a single slot, the terminal may drop the PDSCH associated with C-RNTI. As yet another example, if a broadcast base channel and a PDSCH scheduled by a DCI scrambled with G-RNTI (hereinafter referred to as a PDSCH associated with G-RNTI) overlap in a single slot, the terminal may drop the broadcast base channel. However, this is only one embodiment, and when a broadcast base channel and a PDSCH associated with C-RNTI / G-RNTI overlap in a single slot, which channel to drop / skip may be predefined or set by an RRC signal.

[0207] Example 2-2

[0208] Example 2 relates to a terminal processing method when a multicast channel overlaps with another PDSCH. In this case, the multicast channel may be limited to a number of PRBs corresponding to a 5MHz bandwidth, regardless of the HARQ feedback mode, but is not limited to this. In this case, the terminal can decode the entire channel, but eRedCap terminals may have difficulty decoding the entire channel. Therefore, the conditions described later may apply to Example 2.

[0209] For example, when HARQ feedback is configured for a multicast channel, the multicast channel may be scheduled for as many PRBs as there are corresponding to a maximum of 5 MHz bandwidth. As another example, when NO HARQ mode is configured by RRC signaling or NO HARQ feedback mode is indicated by DCI, the multicast channel may be scheduled for as many PRBs as there are corresponding to a maximum of 20 MHz bandwidth.

[0210] Example 2 relates to the processing behavior of a terminal when a multicast channel overlaps with a unicast PDSCH on an OFDM symbol basis in the time domain.

[0211] Furthermore, Embodiment 2 may also be applied when ACK / NACK mode or NACK-only mode is set for an MBS PDSCH (e.g., a multicast PDSCH). In this case, feedback does not need to be sent from the terminal only when ACK / NACK mode is set. The transmission of feedback may vary depending on the terminal embodiment, and HARQ feedback may be sent or omitted depending on the terminal capacity.

[0212] Furthermore, Example 2 may be applied when HARQ feedback deactivation is set for multicasting.

[0213] Example 2-2-1

[0214] When a multicast channel overlaps with another PDSCH, the multicast channel may be limited to scheduling no more than or equal to the number of PRBs corresponding to a 5MHz bandwidth, regardless of the HARQ feedback mode, but is not limited to this. In this case, the terminal does not need to expect decoding of multiple channels scheduled in the slot, and the method described later may be used.

[0215] As an example of this disclosure, in the case of an MBS-based channel (e.g., a broadcast-based channel and / or a multicast channel), the scheduling described above does not need to be expected. For example, if HARQ deactivation mode is set for a multicast channel by RRC signaling, the terminal can decode the multicast channel and other PDSCH channels overlapping with the multicast channel. As yet another example, if HARQ deactivation mode is instructed for a multicast channel by DCI, the terminal does not need to expect such scheduling.

[0216] As yet another example of this disclosure, a terminal may drop (or skip) an MBS base channel (e.g., a broadcast base channel and / or a multicast channel). If repeated transmissions occur, an MBS base channel may be dropped (or skipped) on an OFDM symbol in an overlapping slot. For example, if an ACK / NACK mode or NACK-only mode is set for a multicast channel, a terminal may drop (or skip) a multicast channel. As yet another example, if a multicast channel is set to HARQ deactivation mode by RRC signaling (or DCI), a terminal may decode the multicast channel and any other PDSCH channels overlapping with the multicast channel. As yet another example, if HARQ deactivation mode is indicated for a multicast channel by DCI (or RRC signaling), a terminal may drop (or skip) a multicast channel.

[0217] Additionally or alternatively, if the sum of the PRB counts for two channels (i.e., the multicast channel and the other PDSCH channel overlapping with the multicast channel) exceeds the number of PRBs corresponding to a 5MHz bandwidth, the terminal may drop the multicast channel. In this case, the two channels may be FDM'd with OFDM symbols. However, if the sum of the PRB counts for the multicast channel and the other PDSCH channel overlapping with the multicast channel is less than or equal to the number of PRBs corresponding to a 5MHz bandwidth, the terminal may decode both channels.

[0218] Examples 2-3

[0219] In one embodiment of the present disclosure, if the number of PRBs in a scheduled multicast PDSCH is equal to or greater than the number of PRBs corresponding to a 5MHz bandwidth (for example, when HARQ feedback is deactivated), the terminal may skip one of the multicast PDSCH or other channels overlapping with the multicast PDSCH without decoding it. The method according to Embodiment 2-3 may be used when the other channel overlapping with the multicast channel is a specific channel (for example, a unicast PDSCH or a paging-triggered SI).

[0220] Examples 2-4

[0221] In one embodiment of the present disclosure, when a multicast PDSCH is scheduled for a number of PRBs corresponding to a maximum bandwidth of 5 MHz (for example, when ACK / NACK mode or NACK-only mode is set), the terminal may drop one of the multicast PDSCH or 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 (for example, a unicast PDSCH or a paging-triggered SI).

[0222] Examples 2-5

[0223] In one embodiment of the present disclosure, when HARQ feedback is configured (for a multicast channel), the terminal may drop one of the multicast PDSCH or other channels overlapping with the multicast PDSCH without decoding it. The method according to Embodiment 2-5 may be used when the other channel overlapping with the multicast channel is a specific channel (for example, a unicast PDSCH or a paging-triggered SI).

[0224] Additionally, assume that unicast and multicast PDSCHs overlap or do not overlap in a single slot in the time domain. In this case, if the sum of the PRBs of the unicast and multicast PDSCHs (or the number of PRBs in one of the unicast or multicast PDSCHs) exceeds the number of PRBs corresponding to a 5MHz bandwidth and / or if HARQ feedback is configured, the terminal can send a NACK without decoding the multicast PDSCH. This allows the terminal to induce the base station to retransmit.

[0225] Examples 2-6

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

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

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

[0229] Example 2-7

[0230] In one embodiment of the present disclosure, a terminal can decode multiple channels if the sum of the number of PRBs assigned to multiple channels scheduled / assigned to a single slot (i.e., multiple overlapping channels in a single slot) is less than or equal to a specific value (e.g., the number of PRBs corresponding to a 5MHz bandwidth). The terminal does not need to expect that the sum of the number of PRBs assigned to multiple channels scheduled / assigned to a single slot will exceed the specific value.

[0231] As an example, one of the aforementioned multiple channels may be a multicast channel (e.g., a multicast PDSCH). When the NO HARQ feedback mode is set, the terminal can decode two or more channels regardless of the number of PRBs in the MBS PDSCH.

[0232] As another example, when ACK / NACK mode or NACK-only mode is configured for a multicast channel, the terminal does not need to expect the scheduling described above (for example, scheduling so that the sum of the number of PRBs assigned to multiple channels scheduled / assigned to a single slot is less than or greater than a certain value).

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

[0234] Example 2-8

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

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

[0237] As yet another example, a terminal can transmit terminal capacity information to a base station related to the processing of MBS channels and other overlapping channels. The terminal can then decode MBS channels and other channels overlapping in a single slot based on terminal capacity.

[0238] As yet another example, if the MBS channel is a broadcasting channel associated with G-RNTI, the terminal can decode the MBS channel and all other channels. However, if the MBS channel is transmitted repeatedly, the terminal may drop the MBS channel.

[0239] As yet another example, if the MBS channel is a broadcast channel or a multicast channel, the terminal does not need to expect the scheduling described above. In this case, if ACK / NACK mode or NACK-only mode is set for the multicast channel, the terminal does not need to expect the scheduling described above. If HARQ deactivation mode is set for the multicast channel by RRC signaling, the terminal can decode the multicast channel and all other channels. If HARQ deactivation mode is set for the multicast channel by DCI, the terminal does not need to expect the scheduling described above.

[0240] As further examples, a terminal can drop an MBS channel if it is a broadcast channel or a multicast channel. For example, a terminal can drop a unicast channel if it is a broadcast channel associated with MCCH-RNTI. When an MBS channel is repeatedly transmitted, a terminal can drop an MBS channel or a unicast channel in a slot where there is an overlap between the MBS channel and the unicast channel. A terminal can drop an MBS channel or a unicast channel if ACK / NACK mode or NACK-only mode is set for a multicast channel. A terminal can decode the multicast channel and all other channels if HARQ deactivation mode is set for a multicast channel by RRC signaling. A terminal can drop a multicast channel if HARQ deactivation mode is set for a multicast channel by DCI.

[0241] As yet another example, when ACK / NACK or NACK-only data is sent to a multicast channel, the terminal can decode the multicast and all other channels overlapping with the multicast. The above operation may only occur if NACK-only mode is configured. As yet another example, the above operation may only occur if NACK-only mode and the NACK-only mode PUCCH resource are configured.

[0242] As another example, when the sum of the PRBs for multiple overlapping channels (e.g., two channels) in a single slot is greater than or equal to the number of PRBs corresponding to a 5MHz bandwidth, the eRedCap terminal may either not transmit feedback to the multiple channels or may process the multiple channels as NACK (when NACK only or ACK / NACK is set).

[0243] As yet another example, when the sum of the PRBs of each of a plurality of channels (e.g., two channels) overlapped with a single slot is greater than the number of PRBs corresponding to a 5 MHz bandwidth, (when only NACK or ACK / NACK is set), feedback transmission for the plurality of channels may be performed by a terminal implementation.

[0244] Example 2-9

[0245] As an example 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.

[0246] Example 2-10

[0247] Example 2-10 relates to a method when a unicast SPS PDSCH and a multicast SPS PDSCH are transmitted and overlap on an OFDM symbol in the same slot.

[0248] As an example, a terminal may not expect a case where a unicast SPS PDSCH and a multicast SPS PDSCH overlap. When both of the two channels are transmitted by SPS or when one of the two channels is transmitted by SPS, the terminal may not expect a case where the unicast SPS PDSCH and the multicast SPS PDSCH overlap.

[0249] Since SPS-based transmission has lower flexibility than PDCCH-based dynamic scheduling, the base station does not have to schedule so that the unicast SPS PDSCH and the multicast SPS PDSCH overlap in one slot.

[0250] As yet another example of this disclosure, one of the overlapping unicast channels (e.g., unicast SPS PDSCH) and MBS channels (e.g., multicast SPS PDSCH) in the same slot may be dropped. Where 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 NO HARQ mode, or a NACK may be sent to the multicast SPS PDSCH. However, the unicast channel may be dropped among the overlapping unicast channels (e.g., unicast SPS PDSCH) and MBS channels (e.g., multicast SPS PDSCH) in the same slot. In other words, the priority of overlapping channels in the same slot may be predefined / set.

[0251] As yet another example of this disclosure, even if identical multicast (SPS) channels overlap in the same slot, the terminal can perform the actions described above (for example, dropping one of the multiple multicast (SPS) channels). As yet another example, the terminal does not need to expect identical multicast (SPS) channels to overlap in the same slot.

[0252] Example 3

[0253] Example 3 relates to a multicast PDSCH processing method in the RRC_Inactive state and the SDT (small data transmission) state.

[0254] The MBS-based PDSCH may include multicast PDSCH and broadcast-based PDSCH. In the case of broadcast-based PDSCH, the method according to Example 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) do not need to be performed in the RRC_Inactive state. However, multicast PDSCH transmission and reception procedures may be possible in the RRC_Inactive state for the sake of service continuity, and the above operations may be performed by a narrowband device (e.g., an eRedCap terminal).

[0255] Example 3-1

[0256] In one embodiment of this disclosure, the eRedCap terminal may be set to NO HARQ mode for multicast PDSCH while in the RRC_Inactive state. Therefore, the eRedCap terminal can expect scheduling of the entire bandwidth (e.g., scheduling of multicast PDSCH).

[0257] In this case, eRedCap terminals may be able to schedule within a maximum bandwidth of 20MHz. For example, when HARQ feedback-related information / commands are transmitted by higher-layer signaling or DCI, the terminal does not need to receive the service (e.g., multicast PDSCH). As another example, a NACK-only mode other than NO HARQ mode may be set for eRedCap terminals, and the eRedCap terminal can check the overall service status even when it is in an idle state receiving the service.

[0258] Example 3-2

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

[0260] Since the RRC_Inactive state is similar to the RRC_Idle state, it may be inappropriate to allocate all uplink resources for feedback to a specific terminal. However, SDT services can generally be provided in the RRC_Idle state, although terminals can momentarily behave like the RRC_Connected state. Therefore, in the case of SDT services, a mode that allows feedback to be provided to the terminal may be configured.

[0261] As an addition or alternative, due to the high complexity of the ACK / NACK mode, it is considered unsuitable for RRC_inactive. Therefore, in the case of SDT, it may be necessary to limit the application to only the NACK_only mode, where common PUCCH resources are limited.

[0262] As an addition or alternative, when feedback-related information is set for an eRedCap terminal, the entire bandwidth may be used depending on the type and form of feedback, or it may be scheduled up to the number of PRBs corresponding to a specific bandwidth. In this case, the method applied to the multicast PDSCH in the RRC_Connected state of Example 1 may be utilized.

[0263] Example 4

[0264] Example 4 relates to various methods for processing broadcast channels. As described above, the eRedCap terminal can process broadcast channels within a maximum bandwidth of 20 MHz. Generally, when a downlink channel is scheduled by DCI4_0 scrambled with CRC by MCCH-RNTI, the data rate of that downlink channel is unlikely to exceed 10 Mbps. Therefore, the number of PRBs allocated to an MCCH-RNTI-based broadcast channel may be limited to the number of PRBs corresponding to a 5 MHz bandwidth. Similarly, the number of PRBs allocated to a G-RNTI-based broadcast channel may be limited to the number of PRBs corresponding to a 20 MHz bandwidth.

[0265] Example 4-1

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

[0267] Since the MCCH-RNTI base channel contains control information, a wide bandwidth is not required for that channel. Furthermore, whether or not the number of MCCH-RNTI base PDSCHs scheduled corresponds to the number of PRBs corresponding to a 5MHz bandwidth may be predefined, but is not limited to this. Whether or not the number of MCCH-RNTI base PDSCHs scheduled corresponds to the number of PRBs corresponding to a 20MHz bandwidth may be predefined, or may be set by higher-layer signaling.

[0268] Example 4-2

[0269] As an example of an embodiment of the present disclosure, the maximum number of PRBs that may be allocated to a multicast channel may be flexibly set / instructed by upper layer signaling or / and DCI according to HARQ mode and / or 5 / 20 MHz bandwidth. Here, the HARQ mode may include at least one of an ACK / NACK mode, a NACK-only mode, a HARQ deactivation mode, or a DCI-enabler mode.

[0270] As an example, assume that the multicast channel should be allocated within a 5 MHz bandwidth. At this time, when the base station indicates the PRBs corresponding to the 5 MHz bandwidth (i.e., the PRBs of the multicast channel) by the FDRA of the PDCCH, the terminal can transmit ACK / NACK to the base station or transmit NACK to the base station (for example, in the case of the NACK-only HARQ feedback mode).

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

[0272] Example 4-3

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

[0274] Example 4-4

[0275] As one embodiment of this disclosure, in the case of an eRedCap terminal, simultaneous reception of multicasting MBS channels (e.g., multicast PDSCH) and unicast PDSCH does not need to be supported. That is, in the case of multicasting MBS channels and unicast PDSCH, terminal capacity information (e.g., "fdm-BroadcastUnicast-r17") does not need to be applied to the eRedCap terminal.

[0276] Examples 4-5

[0277] In one embodiment of this disclosure, when simultaneous reception of different PDSCHs is supported in the same slot (for example, when overlap of a group common PDSCH and a unicast PDSCH for broadcast in the RRC_connected state is supported in a single slot), the number of PDSCHs that can be FDM'd in the same slot may be determined by terminal capacity. That is, the eRedCap terminal can transmit the number of PDSCHs that can be FDM'd in the same slot and associated terminal capacity information to the base station. This allows the eRedCap terminal to expect that only the number of PRBs that can be processed in a single slot (for example, PRBs corresponding to a 5MHz bandwidth) will be allocated.

[0278] Examples 4-6

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

[0280] When MBS PDSCH repetition transmission is configured, the eRedCap terminal can save the first received information after adding buffers across the slots. When MBS PDSCH repetition transmission is configured, the maximum buffer must be continuously configured for MBS PDSCH allocation on a 20MHz bandwidth. Therefore, when MBS PDSCH repetition transmission is configured, the eRedCap terminal may be restricted to being allocated only a number of PRBs corresponding to a 5MHz bandwidth.

[0281] Examples 4-7

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

[0283] Examples 4-8

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

[0285] Examples 4-9

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

[0287] Examples 4-10

[0288] Examples 4-10 relate to the number of PRBs corresponding to the bandwidth of PDSCHs scheduled by various types of RNTIs.

[0289] As an example of this disclosure, in the case of MCCH-RNTI, the HARQ feedback may always be inactive. MBS broadcasting operation may be possible with a number of PRBs corresponding to a 5MHz bandwidth or more. The above operation may be restricted to only be possible when scheduled with MCCH_RNTI. In the case of G-RNTI, data may be scheduled for every slot, but in the case of an eRedCap terminal that can only schedule PRBs corresponding to a 5MHz bandwidth, decoding problems may occur.

[0290] As yet another example of this 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 deactivated, more than the number of PRBs corresponding to a 5MHz bandwidth (e.g., multicast or multicast channel PRBs) may be used in the RRC_connected state or RRC_active state. Deactivation of HARQ feedback may be set by RRC signaling. As yet another example, when HARQ feedback is activated, more than the number of PRBs corresponding to a 5MHz bandwidth (e.g., multicast channel PRBs) may be used. All MBS channels scheduled by G-RNTI may be restricted to be scheduled within 5MHz. eRedCap terminals may have difficulty decoding PRBs corresponding to a 5MHz bandwidth in channels that are likely to be scheduled consecutively.

[0291] As yet another example of this disclosure, G-CS-RNTI (i.e., SPS) may require an acknowledgment of HARQ feedback ACK in various cases, such as HARQ feedback deactivation, and the following options may apply.

[0292] Option 1: Only PRBs (for multicast channels) equal to or less than the number of PRBs corresponding to a 5MHz bandwidth may be allocated.

[0293] Option 2: More PRBs than the number of PRBs corresponding to a 5MHz bandwidth (e.g., PRBs for multicast channels) may be allocated (no new terminal processing time is defined). In this case, Option 2 may be applied when HARQ feedback is deactivated and parameters associated with HARQ feedback enabling for SPS PDSCH transmissions (e.g., "harq-FeedbackEnablingforSPSactive") are deactivated.

[0294] On the other hand, the “dl-DataToUL-ACK list” contains values ​​for processing HARQ feedback, and the terminal can expect that one K1 value will be indicated among a sufficiently large number of specific values ​​for processing HARQ feedback. The terminal can then expect that a channel (e.g., multicast (SPS)PDSCH) will be scheduled by G-CS-RNTI based on the K1 value. Since the above case requires HARQ feedback, it may only be applied when HARQ feedback enabling and related parameters (e.g., “harq-FeedbackEnablingforSPSactive”) are activated.

[0295] Example 4-11

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

[0297] Example 4-11-1

[0298] As an example of this 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.

[0299] As yet another example of this disclosure, a broadcast PDSCH and a unicast PDSCH may be scheduled in a single slot only if the broadcast PDSCH is scheduled by MCCH-RNTI. When a broadcast PDSCH is scheduled by G-RNTI, G-RNTI may be considered identical to C-RNTI, and it may be difficult for the eRedCap terminal to process both channels simultaneously. Therefore, the terminal does not need to expect that the G-RNTI-related broadcast PDSCH and unicast PDSCH will be scheduled simultaneously.

[0300] Example 4-11-2

[0301] Example 4-11-2 relates to the case where multicast PDSCH and unicast PDSCH are scheduled in a single slot. The following options may apply when HARQ feedback is deactivated (for example, when HARQ feedback is deactivated by RRC signaling).

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

[0303] Option 2: The eRedCap terminal does not need to expect multicast and unicast PDSCH scheduling to be handled in a single slot.

[0304] Option 3: The eRedCap terminal can drop or skip multicast PDSCHs among multicast PDSCHs and unicast PDSCHs scheduled in a single slot.

[0305] Option 4: The eRedCap terminal can drop or skip the unicast PDSCH among the multicast PDSCH and unicast PDSCH scheduled for a single slot. In this case, the eRedCap terminal does not need to receive unicast channels until the next slot after the aforementioned slot.

[0306] As yet another example of this disclosure, the following options may apply when HARQ feedback is activated.

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

[0308] Option 2: The eRedCap terminal does not need to expect multicast and unicast PDSCH scheduling to be handled in a single slot.

[0309] Option 3: The eRedCap terminal can drop or skip the unicast PDSCH among the multicast PDSCH and unicast PDSCH scheduled for a single slot. In this case, the eRedCap terminal does not need to receive unicast channels until the next slot after the aforementioned slot.

[0310] Example 4-12

[0311] As one embodiment of this disclosure, assume that a PDSCH (e.g., a multicast PDSCH) is scheduled by a DCI scrambled by G-RNTI. In this case, if more PRBs than the number of PRBs corresponding to a 5MHz bandwidth are scheduled in a single slot, a gap of a specific slot (e.g., one slot) may be applied / added to the single slot. That is, in order for more PRBs than the number of PRBs corresponding to a 5MHz bandwidth (i.e., the PRBs of the PDSCH) to be scheduled in a single slot, a gap adjacent to the single slot may be set / scheduled / instructed.

[0312] The above-described operation may apply not only to channels scheduled by G-RNTI but also to channels scheduled by MCCH-RNTI. Furthermore, the above-described operation may also apply when the eRedCap terminal is in the RRC_Inactive or RRC_Idle state. In addition, the above-described operation may apply not only to G-RNTI but also to PDSCH reception or P-RNTI-triggered SI acquisition operations associated with SI-RNTI.

[0313] Specifically, an eRedCap terminal can decode only a specific number of PRBs (e.g., the number of PRBs corresponding to a 5MHz bandwidth) in a single slot. Therefore, if more than a specific number of PRBs (e.g., PRBs assigned to PDSCHs) are scheduled in a single slot, an adjacent gap slot (e.g., at least one slot) may be required. This ensures that if more than a specific number of PRBs are scheduled in a single slot, no other channels should be scheduled in at least one slot adjacent to that slot (i.e., the slot configured as a gap).

[0314] As an example, let's assume that a certain number or more PRBs are scheduled in slot n. In this case, if a channel or other PDSCH associated with G-RNTI (or / and MCCH-RNTI) is scheduled on slot n+1, the eRedCap terminal does not need to skip or decode the channel or other PDSCH associated with G-RNTI (or / and MCCH-RNTI).

[0315] As yet another example, if a PDSCH scheduled by MSG 2, MSG B, or P-RNTI associated with a random access procedure is received in slot n+1, the eRedCap terminal may process the channel scheduled in slot n+1 first, even if it processes the MBS PDSCH scheduled in slot n. That is, considering the priority of PDSCHs scheduled by MSG 2, MSG B, or P-RNTI associated with 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.

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

[0317] As yet another example, if the eRedCap terminal needs to decode a PDSCH scheduled in slot n+1, it may skip the MBS PDSCH scheduled in slot n, or it may not be expected to decode that MBS PDSCH. As yet another example, the eRedCap terminal may interrupt the process in slot n.

[0318] As another example, in the case of a channel scheduled in slot n+1 (for example, a channel with HARQ feedback configured), the eRedCap terminal may skip the channel or not be expected to decode it. For channels without HARQ feedback, the eRedCap terminal may interrupt or skip decoding for an MBS PDSCH scheduled in slot n. If decoding for an MBS PDSCH scheduled in slot n is interrupted, the eRedCap terminal may drop the interrupted MBS PDSCH.

[0319] Example 4-13

[0320] As one embodiment of this disclosure, we assume that when slot n is scheduled / allocated with a number of PRBs (e.g., PRBs of an MBS PDSCH) equal to or less than the number of PRBs corresponding to a 5MHz bandwidth, other channels are also received in slot n. Embodiment 4-13 relates to a processing method when another PDSCH is scheduled in slot n+1, in a situation where the eRedCap terminal must decode each channel scheduled in slot n. In this case, the multiple PDSCHs scheduled in slot n may, but are not limited to, overlap on an OFDM symbol basis.

[0321] As an example of this disclosure, as described above, if an MBS PDSCH and other channels are scheduled in slot n, the eRedCap terminal can drop the MBS PDSCH.

[0322] As an example of this disclosure, if there are no PDSCHs that need to be decoded in slot n+1, the eRedCap terminal can decode all of the multiple PDSCHs scheduled in slot n (i.e., MBS PDSCH and other PDSCHs, etc.). In this case, the other PDSCHs scheduled in slot n and / or the PDSCHs that need to be decoded in slot n+1 may, but are not limited to, unicast PDSCHs. Furthermore, if there are no PDSCHs that need to be decoded in slot n+1, the eRedCap terminal can decode all of the MBS PDSCHs and other PDSCHs scheduled in slot n, even if the sum of the PRBs of each of the MBS PDSCHs and other PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to a 5MHz bandwidth.

[0323] Example 4-14

[0324] Example 2 relates to a processing method when multiple channels overlap within a single slot. On the other hand, as shown in Figure 10, within a single slot, multiple channels may not overlap in the time domain but may or may not overlap in the frequency domain. Examples 4-14 relate to various processing methods when multiple channels (e.g., unicast channels and / or multicast channels) are scheduled in a single slot, and methods when more than the number of PRBs corresponding to a 5MHz bandwidth are allocated in a single slot.

[0325] As described above, an eRedCap terminal can process as many PRBs as there are PRBs corresponding to a 5MHz bandwidth within a single slot. As an example, suppose that when an MBS PDSCH (e.g., a multicast PDSCH and / or a broadcast PDSCH) and a unicast channel are scheduled in slot n, the number of PRBs in the MBS PDSCH is equal to or greater than the number of PRBs corresponding to a 5MHz bandwidth, or the sum of the PRBs of the MBS PDSCH and the unicast channel is equal to or greater than the number of PRBs corresponding to a 5MHz bandwidth. In this case, the MBS PDSCH and the unicast channel may or may not overlap in the time domain. As an example, the eRedCap terminal may skip (or drop) the MBS PDSCH, or it may not expect to decode the MBS PDSCH. When HARQ feedback for an MBS PDSCH is set to enable, the eRedCap terminal may send the feedback as a NACK. As yet another example, the eRedCap terminal does not need to expect that the number of PRBs in an MBS PDSCH will be greater than or equal to the number of PRBs corresponding to a 5MHz bandwidth. As yet another example, the eRedCap terminal can process MBS PDSCHs and unicast PDSCHs in the received / scheduled order (i.e., OFDM symbol order within one slot), and certain PRBs (e.g., PRBs exceeding the 5MHz bandwidth range) may be skipped or decoding of certain PRBs may not be expected. The eRedCap terminal can then send a NACK to the base station for channels containing certain PRBs.

[0326] Examples 4-15

[0327] Examples 4-15 relate to a processing method when one or more MBS PDSCHs and one or more unicast PDSCHs are scheduled in slot n.

[0328] As an example of this disclosure, if a maximum of seven PDSCH processes can be performed within a specific slot, four unicast PDSCHs and three multicast PDSCHs may be processed within that slot. In this case, the eRedCap terminal can process the PDSCHs in the order they are scheduled in slot n and is expected to process the PDSCHs within a range that does not exceed the processing capacity of a specific bandwidth.

[0329] For example, an eRedCap terminal can process MBS PDSCHs and unicast PDSCHs in the order they are received / scheduled (i.e., OFDM symbol order within one slot), and may skip certain PRBs (e.g., PRBs exceeding a 5MHz bandwidth range) or not be expected to be decoded. The eRedCap terminal can then send a NACK to the base station for channels containing the specific PRBs.

[0330] For example, if the HARQ feedback mode is ACK / NACK mode or NACK-only mode, the number of multicast PDSCHs may be counted in the same way as unicast PDSCHs. If the HARQ feedback mode is NO HARQ mode, the number of multicast PDSCHs does not need to be counted. As yet another example, feedback may not be considered, or all multicast / unicast PDSCHs may be counted.

[0331] Example 4-16

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

[0333] Example 4-17

[0334] In one embodiment of this 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 ACK / NACK mode or NACK-only HARQ feedback mode. In yet another example, the number of all PDSCHs scheduled in slot n may be counted without considering the feedback mode.

[0335] As yet another example of this disclosure, an eRedCap terminal can process MBS PDSCHs and unicast PDSCHs in the order they are received / scheduled (i.e., OFDM symbol order within one slot), and certain PRBs (e.g., PRBs exceeding a 5 MHz bandwidth range) may be skipped or decoding of certain PRBs may not be expected. The eRedCap terminal can then transmit a NACK to the base station for channels containing certain PRBs.

[0336] Example 5

[0337] MBS PDSCH channels may be scheduled within a 5MHz bandwidth, but may also be scheduled in the region exceeding 5MHz bandwidth. In this case, multicast PDSCH or broadcast PDSCH will likely be scheduled in consecutive slots more likely than SIB-based PDSCH or paging-based PDSCH.

[0338] On the other hand, as mentioned above, the eRedCap terminal can process unicast channels within a 5MHz bandwidth in a single slot. In the case of the MBS PDSCH, it may be allocated within a 5MHz bandwidth, but it may also be allocated more PRBs (i.e., PRBs of the MBS PDSCH) than the number of PRBs corresponding to a 5MHz bandwidth.

[0339] If the number of PRBs allocated to a single slot exceeds the number of PRBs corresponding to a 5MHz bandwidth, and repetitive transmissions are performed in consecutive slots, processing of PDSCHs scheduled for the slot following that slot may become problematic.

[0340] This section describes the processing method when a PDSCH transmitted repeatedly in slot n+1 is received simultaneously with another PDSCH when a repetitive transmission is scheduled / configured and the number of PRBs scheduled in slot n exceeds the number of PRBs corresponding to a 5MHz bandwidth.

[0341] As an example of this disclosure, as shown in Figure 11, if the number of PRBs (i.e., PRBs for MBS PDSCHs) allocated to slot n exceeds the number of PRBs corresponding to a 5MHz bandwidth, additional processing time may be required to process PDSCHs exceeding 5MHz in the next slot. Therefore, if repetitive transmission is not set, some of the PDSCHs scheduled / received in slot n+1 may be processed. However, if PDSCHs are received consecutively, it may be impossible to process other PDSCHs in the slot where a repetitive transmission is received.

[0342] The following describes the processing method when repeated transmission is set / scheduled and the number of PRBs (e.g., PRBs of the MBS PDSCH) scheduled is less than or equal to the number of PRBs corresponding to a 5MHz bandwidth.

[0343] In the case of eRedCap terminals, when repetitive transmission is configured, restrictions may be defined / set on the scheduling of PRB allocations within the 5MHz bandwidth. This can affect the decoding of each slot channel if other channels are scheduled / received when repetitive transmission is scheduled / performed, as shown in Figure 11.

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

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

[0346] Example 5-1

[0347] In one embodiment of the present disclosure, the eRedCap terminal processes only the MBS PDSCH scheduled / received in the first slot, and does not need to process the MBS PDSCH that is repeatedly transmitted in the remaining slots. That is, the eRedCap terminal may not decode or skip the MBS PDSCH scheduled in slots n and later (i.e., slots n+1, n+2, and n+3) in Figure 11(a).

[0348] Example 5-2

[0349] As one embodiment of this disclosure, the number of repetitions (of the MBS PDSCH) may be set to one of 2, 4, or 8 by upper-layer signaling. In this case, based on the number of repetitions being set to a number greater than 2, the eRedCap terminal can only process channels that have been repetitively transmitted a maximum of 2 times. If the number of repetitions is large, decoding-related problems may occur as shown in Figure 11. As yet another example, a specific threshold associated with the number of repetitions may be set / instructed / defined, and the eRedCap terminal may decode or drop all channels that have been repetitively transmitted below / above the specific threshold.

[0350] Example 5-3

[0351] In one embodiment of the present disclosure, an eRedCap terminal can process only channels received in even-numbered or odd-numbered repeat slots. In this case, the type of slot processed by the eRedCap terminal (i.e., even-numbered or odd-numbered repeat slots) may be set / indicated by DCI or RRC signaling. The even-numbered or odd-numbered repeat slot may be determined based on the slot in which the channel transmission first occurs, or it may be determined based on the slot number.

[0352] In Example 5, when repeated transmission is performed, if no MBS PDSCH can be received / decoded, the eRedCap terminal can send a NACK.

[0353] Example 6

[0354] Example 6 relates to a method for processing MBS PDSCH on a slot-by-slot basis for repetitive transmissions when the number of PRBs (i.e., PRBs of MBS PDSCH) corresponding to a 5MHz bandwidth is greater than or equal to the number of PRBs (i.e., PRBs of MBS PDSCH) scheduled in a specific slot.

[0355] If a PDSCH is scheduled within or beyond a 5MHz bandwidth, the eRedCap terminal may require additional processing time (e.g., one slot). That is, if another PDSCH is scheduled in slot n+1 while processing an MBS PDSCH in slot n, the eRedCap terminal does not need to receive the MBS PDSCH (in slot n+1).

[0356] As an example of this disclosure, as shown in Figure 11(b), when an MBS PDSCH in slot n+1 is scheduled / transmitted, an additional PDSCH is scheduled in slot n+2, excluding the repeating MBS PDSCH. The eRedCap terminal can process the MBS PDSCH in slot n+1 and interrupt the processing of the MBS PDSCH in the middle (e.g., in the middle of slot n+1 or in slot n+2) and drop it.

[0357] Example 6-1

[0358] In one embodiment of this disclosure, if, while an MBS PDSCH is being processed in slot n, other PDSCHs are scheduled / received on the next slot in addition to the repeated transmission of an MBS PDSCH, the eRedCap terminal does not need to receive the MBS PDSCH processed in slot n in the next slot (e.g., slot n+1). That is, the eRedCap terminal does not need to process the reception of the repeated MBS PDSCH in slot n+1. In other words, even if other PDSCHs are scheduled in slot n+1, the eRedCap terminal can decode the first MBS PDSCH in slot n.

[0359] Example 6-2

[0360] As mentioned above, regardless of whether or not another PDSCH is received in the next slot (for example, slot n+1), if another PDSCH in slot n is an MBS PDSCH, the eRedCap terminal does not need to process the MBS PDSCH.

[0361] In other words, if an MBS PDSCH is transmitted repeatedly, the eRedCap terminal can skip processing its reception. The eRedCap terminal can receive the first of the repeatedly transmitted MBS PDSCHs even if another PDSCH is scheduled for the next slot. Even if no repeated transmission occurs, the reception of the MBS PDSCH in slot n may be skipped or not decoded.

[0362] Example 6-3

[0363] In one embodiment of this disclosure, the number of transmission repetitions may be set to any one of 2 to 8 by DCI or RRC signaling. This is to minimize the number of PDSCHs that cannot be received when scheduling repetitive transmissions.

[0364] Example 6-4

[0365] In one embodiment of the present disclosure, the above-described conditions for dropping an MBS PDSCH channel and the conditions for repeated transmission may be applied when multiple channels are received simultaneously in the slot (for example, when an MBS channel and another PDSCH overlap on an OFDM symbol basis) or when another PDSCH is scheduled in the next slot.

[0366] Furthermore, MBS PDSCHs that are not dropped during repeated transmission may be combined and decoded.

[0367] Example 6-5

[0368] In one embodiment of the present disclosure, if repetitive transmission is set / scheduled and a channel is received and decoded in a specific slot, other channels may be received and decoded in a slot one slot after the specific slot.

[0369] Reception and decoding of PDSCHs scheduled for a slot that is one slot above a specific slot is not expected. In other words, such PDSCHs are skipped or do not need to be received.

[0370] If no channel decoding is performed by the PDSCH of a specific slot and the next slot using the method according to Example 6, the eRedCap terminal can send a NACK to the base station for the channels that could not be received.

[0371] Example 7

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

[0373] When repeat transmission is configured, the terminal can decode the channel that it has received up to the last slot on which repeat transmission is configured. The processing for the last slot on which repeat transmission is configured may be determined by whether or not another PDSCH is scheduled / received in the slot following that slot. In other words, even if a PRB of 5MHz bandwidth or larger is scheduled on the slots preceding the last slot (i.e., the slots on which all MBS PDSCHs are transmitted), the channel corresponding to that PRB and other PDSCHs may be received simultaneously.

[0374] Example 7-1

[0375] As one embodiment of the present disclosure, when a repeat transmission is set, the MBS PDSCH of the slot in which the last repeat transmission is performed does not need to be decoded if another PDSCH is scheduled for the slot following that slot.

[0376] Example 7-2

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

[0378] Example 7-3

[0379] As one embodiment of the present disclosure, when repeated transmission is set, if another PDSCH is transmitted simultaneously in the last slot on which repeated transmission is set, or if another PDSCH is scheduled in the next slot, the eRedCap terminal does not need to receive the MBS PDSCH in the last slot and can decode the previously received MBS PDSCH.

[0380] As yet another example of this disclosure, if more PRBs (i.e., PRBs for MBS PDSCHs) are scheduled than the number of PRBs corresponding to a 5 MHz bandwidth, repeat transmissions may be restricted from being set up, or the eRedCap terminal may not receive the repeatedly transmitted MBS PDSCHs and send a NACK to the base station.

[0381] As yet another example of this disclosure, if both of the two channels scheduled for one slot cannot be decoded, the eRedCap terminal may decode either of the two channels (for example, the PDSCH scheduled by SI (system information)-RNTI or the PDSCH scheduled by P (paging)-RNTI) according to the priority of the two channels.

[0382] Example 8

[0383] As 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 relaxation time to the processing time.

[0384] In other words, unlike in Example 1, the eRedCap terminal can operate with a 20MHz bandwidth. In this case, if HARQ feedback is present and ACK / NACK or NACK-only mode is set, it may be necessary to add time equal to the X value to the terminal processing time. In this case, if HARQ feedback is not present, the X value does not need to be applied. The X value also does not need to be applied when ACK / NACK and NACK-only modes are set and only a number of PRBs within 5MHz BW is allocated.

[0385] Example 8-1

[0386] As one embodiment of this disclosure, when NO HARQ mode is set, the X value does not need to be applied to the terminal processing type.

[0387] Example 8-2

[0388] As one embodiment of this disclosure, when HARQ feedback is present, the eRedCap terminal may add an X value to the additional processing time. In this case, the X value may be the same or different values ​​applied by the additional processing time capacities 1 and 2. The X values ​​may be applied separately according to the SCS. The X value may be the same as the value applied to the decoding-related processing time of message 2 or message B in the RACH procedure. The X value may also be applied when the multicast channel is allocated within a 5 MHz bandwidth.

[0389] Example 8-3

[0390] As one embodiment of this disclosure, when NACK-only mode is set, the relaxation of the additional processing time for X values ​​does not need to be applied in order to increase the flexibility of network operation.

[0391] Example 8-4

[0392] As one embodiment of the present disclosure, an additional processing time for the X value may be applied when the FDRA information of the PDCCH in ACK / NACK or NACK-only mode indicates more than the number of PRBs corresponding to a 5MHz bandwidth (i.e., when the bandwidth of the channel scheduled by the FDRA information of the PDCCH exceeds 5MHz).

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

[0394] As an example of this disclosure, in the case of an MBS channel (e.g., a multicast channel), eRedCap terminals do not need to expect scheduling exceeding 5MHz. In this case, the base station can group eRedCap terminals that support 5MHz together and schedule the MBS channel for the eRedCap terminals within the 5MHz bandwidth.

[0395] As an example of this disclosure, in the case of an MBS channel (e.g., a multicast channel), the eRedCap terminal can expect scheduling exceeding 5MHz. In this case, there are no restrictions on the grouping of eRedCap terminals, and operation in ACK / NACK mode may be considered. As one example, timing relaxation may not be applied to the eRedCap terminal. As another example, timing relaxation may be applied to the eRedCap terminal. As yet another example, when a multicast PDSCH is scheduled to a bandwidth exceeding 5MHz, timing relaxation may be applied to the eRedCap terminal. As one example, when a multicast PDSCH is scheduled to a bandwidth exceeding 5MHz, the application of timing relaxation and the method of applying it may be determined by ACK / NACK mode.

[0396] Example 9

[0397] Example 9 relates to a method for processing multiple channels based on the sum of the PRBs of multiple channels received simultaneously. Specifically, Example 9 relates to a method for processing when the sum of the PRBs of channels transmitted simultaneously exceeds the PRB corresponding to a 5MHz bandwidth. The eRedCap terminal can prioritize the processing of important channels based on the priority of channels transmitted simultaneously. The following describes the case where MBS channels (e.g., multicast channels and / or broadcast channels) are received in the same slot as other channels.

[0398] As an example of this disclosure, as shown in Figure 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. The other PDSCH may include a PDSCH that can be scheduled by SI-RNTI, P-RNTI, RA-RNTI, C-RNTI, or MsgB-RNTI.

[0399] Example 9-1

[0400] As one embodiment of this disclosure, if the sum of the PRBs 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 in Figure 9.

[0401] Example 9-2

[0402] In one embodiment of the present disclosure, if the sum of PRBs of two channels scheduled in one slot (e.g., an MBS PDSCH and another PDSCH) exceeds the number of PRBs corresponding to a particular bandwidth (e.g., 25 if the SCS is 15kHz, or 12 if the SCS is 30kHz), the operation of the eRedCap terminal may be determined by which RNTI the other PDSCH of the two channels is scheduled to.

[0403] For example, if another PDSCH is scheduled by P-RNTI, the eRedCap terminal can drop or skip the MBS PDSCH. In other words, that MBS PDSCH does not need to be decoded.

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

[0405] 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 exist.

[0406] For example, if another PDSCH is scheduled by MCCH-RNTI, the PDSCH scheduled by MCCH-RNTI may be processed preferentially, while the PDSCH scheduled by G-RNTI may be dropped.

[0407] For example, if both PDSCHs are scheduled by G-RNTI, the PDSCH to be dropped may be determined by the respective priority of the PDCCHs that scheduled each of the two PDSCHs. In other words, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0409] Example 9-3

[0410] As one embodiment of the present disclosure, if the sum of the PRBs of the two channels scheduled in slot n exceeds the number of PRBs corresponding to a 5MHz bandwidth, and there is another PDSCH in slot n+1 that needs to be decoded, the eRedCap terminal can decode both channels.

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

[0412] Example 10

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

[0414] The MBS PDSCH may be scheduled to have a bandwidth exceeding 5 MHz (i.e., the number of PRBs in the MBS PDSCH may exceed the number of PRBs corresponding to a 5 MHz bandwidth). In this case, as shown in Figure 12(a), the processing time of the MBS PDSCH may exceed one slot relative to the eRedCap terminal.

[0415] The following describes the operation of the 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). In this case, the operation of the eRedCap terminal may differ depending on the type of PDSCH. The following operation may be applied regardless of whether the two channels (i.e., the MBS PDSCH and the additional PDSCH) overlap in the time domain.

[0416] Example 10-1

[0417] As one embodiment of the present disclosure, an eRedCap terminal may drop or skip one of two channels. For example, the eRedCap terminal may drop the MBS PDSCH channel from the two channels.

[0418] For example, if the additional PDSCH (i.e., unicast PDSCH) is scheduled by C-RNTI, the eRedCap terminal can drop the unicast PDSCH. That is, the unicast PDSCH does not need to be decoded. In this case, HARQ feedback exists for the MBS PDSCH, but HARQ feedback does not need to exist for the unicast PDSCH. Furthermore, the MBS PDSCH and the unicast PDSCH may overlap in slot n+1 on an OFDM symbol basis.

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

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

[0421] Example 10-2

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

[0423] For example, if one of the two channels (i.e., a unicast PDSCH) is scheduled by a C-RNTI, the eRedCap terminal can drop the unicast PDSCH. For example, the channel to be dropped may be determined by the priority of the DCIs that schedule each of the two channels. For instance, the channel scheduled by the DCI with the lower priority may be dropped.

[0424] As an example, if there is HARQ feedback for an MBS PDSCH, the eRedCap terminal can drop the unicast PDSCH from among the MBS PDSCH and unicast PDSCH. In this case, HARQ feedback for the unicast PDSCH does not need to exist. As yet another example, the eRedCap terminal can drop the MBS PDSCH from among two channels (for example, an MBS PDSCH and a unicast PDSCH).

[0425] Example 10-3

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

[0427] For example, if one of two channels (e.g., an MBS PDSCH and a unicast PDSCH) is scheduled by a C-RNTI, the eRedCap terminal can drop the unicast PDSCH. For example, the channel to be dropped may be determined by the priority of the DCIs that schedule each of the two channels. For example, the channel scheduled by the DCI with the lower priority may be dropped.

[0428] As an example, if there is HARQ feedback for an MBS PDSCH, the eRedCap terminal can drop the unicast PDSCH from among the MBS PDSCH and unicast PDSCH. In this case, HARQ feedback for the unicast PDSCH does not need to exist. As yet another example, the eRedCap terminal can drop the MBS PDSCH from among two channels (for example, an MBS PDSCH and a unicast PDSCH).

[0429] Example 11

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

[0431] HARQ feedback for MBS channels may or may not be present. If HARQ feedback is present, the MBS channel may be treated like a unicast PDSCH. If HARQ feedback is not present, the MBS channel may be treated like a general SIB transmitting PDSCH channel. Example 11 relates to an eRedCap terminal processing method for MBS channels with and without HARQ feedback.

[0432] If HARQ feedback is available for the MBS channel, Example 10 may be applied. If HARQ feedback is not available for the MBS channel, Example 9 may be applied. If HARQ feedback is available, one or more channels may be scheduled within a 5 MHz bandwidth. If HARQ feedback is not available, one or more channels may be scheduled within a 5 MHz bandwidth or beyond a 5 MHz bandwidth.

[0433] Example 11-1

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

[0435] For example, if one of two channels (i.e., a unicast PDSCH) is scheduled by C-RNTI, the eRedCap terminal can drop the unicast PDSCH. For example, if there is HARQ feedback for an MBS PDSCH, the eRedCap terminal can drop the unicast PDSCH from among the MBS PDSCH and unicast PDSCH. In this case, HARQ feedback for the unicast PDSCH does not need to exist. As yet another example, the eRedCap terminal can drop the MBS PDSCH from among two channels (e.g., an MBS PDSCH and a unicast PDSCH).

[0436] For example, if two channels (e.g., PDSCHs) are both scheduled by G-RNTI, the PDSCH to be dropped may be determined by the priority of the PDCCHs that scheduled each of the two PDSCHs. In other words, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0438] Example 11-1 may be applied when the sum of the number of PRBs in the two channels exceeds the number of PRBs corresponding to a 5 MHz bandwidth. That is, if the sum of the number of PRBs in the two channels does not exceed the number of PRBs corresponding to a 5 MHz bandwidth, both channels may be decoded.

[0439] Example 11-2

[0440] Example 11-2 relates to the operation of an eRedCap terminal in the absence of HARQ feedback and is described with reference to Figure 9. Regardless of whether the number of PRBs of an MBS channel scheduled for a particular slot exceeds the number of PRBs corresponding to a 5MHz bandwidth, if the sum of the number of PRBs of two channels exceeds the number of PRBs corresponding to a particular bandwidth (e.g., 5MHz), the eRedCap terminal may drop one of the two channels.

[0441] In one embodiment of the present disclosure, if the sum of PRBs of two channels scheduled in one slot (e.g., an MBS PDSCH and another PDSCH) exceeds the number of PRBs corresponding to a particular bandwidth (e.g., 25 if the SCS is 15kHz, or 12 if the SCS is 30kHz), the operation of the eRedCap terminal may be determined by which RNTI the other PDSCH of the two channels is scheduled to.

[0442] For example, if another PDSCH is scheduled by P-RNTI, the eRedCap terminal can drop or skip the MBS PDSCH. In other words, the MBS PDSCH does not need to be decoded.

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

[0444] 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 exist.

[0445] For example, if another PDSCH is scheduled by MCCH-RNTI, the PDSCH scheduled by MCCH-RNTI may be processed preferentially, while the PDSCH scheduled by G-RNTI may be dropped.

[0446] For example, if both PDSCHs are scheduled by G-RNTI, the PDSCH to be dropped may be determined by the priority of the PDCCH that scheduled each of the two PDSCHs. In other words, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0448] Example 11-3

[0449] As an example of this disclosure, if HARQ feedback is present, the operation associated with Figure 9 may apply. As yet another example, if there is no HARQ feedback, if the number of PRBs in the MBS PDSCH exceeds the number of PRBs corresponding to a 5MHz bandwidth, the operation associated with Figure 12(a) may apply. As yet another example, if there is no HARQ feedback, if the number of PRBs in the MBS PDSCH is less than or equal to the number of PRBs corresponding to a 5MHz bandwidth, the operation associated with Figure 12(b) may apply.

[0450] If other channels besides the MBS PDSCH channel are received in the same slot, the following actions may be performed. For example, an eRedCap terminal may either not consider the scheduling described below, or it may perform actions based on the terminal implementation.

[0451] For example, if another PDSCH is scheduled by P-RNTI, the eRedCap terminal can drop or skip the MBS PDSCH. In other words, the MBS PDSCH does not need to be decoded.

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

[0453] 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 exist.

[0454] For example, if another PDSCH is scheduled by MCCH-RNTI, the PDSCH scheduled by MCCH-RNTI may be processed preferentially, while the PDSCH scheduled by G-RNTI may be dropped.

[0455] For example, if both PDSCHs are scheduled by G-RNTI, the PDSCH to be dropped may be determined by the priority of the PDCCH that scheduled each of the two PDSCHs. In other words, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0457] Example 12

[0458] Example 12 relates to a method that utilizes Examples 9 and 10 according to the MBS casting type.

[0459] The MBS casting type may include broadcast type and multicast type. If the MBS casting type is broadcast type, Example 9 may apply. If the MBS casting type is multicast type, Example 10 may apply.

[0460] Example 12-1

[0461] As an example of this 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 for two or more channels is less than or equal to the number of PRBs corresponding to a 5MHz bandwidth, the eRedCap terminal can receive two or more channels in the same slot.

[0462] As an example of this disclosure, when an MBS PDSCH and another channel (e.g., another PDSCH) are simultaneously scheduled in the same slot, and the eRedCap terminal cannot receive both channels simultaneously, the method described later may be applied. In this case, the eRedCap terminal does not need to expect scheduling of both channels and can perform operations based on terminal implementation.

[0463] For example, if another PDSCH is scheduled by P-RNTI, the eRedCap terminal can drop or skip the MBS PDSCH. In other words, that MBS PDSCH does not need to be decoded.

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

[0465] 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 exist.

[0466] For example, if another PDSCH is scheduled by MCCH-RNTI, the PDSCH scheduled by MCCH-RNTI may be processed preferentially, while the PDSCH scheduled by G-RNTI may be dropped.

[0467] For example, if both PDSCHs are scheduled by G-RNTI, the PDSCH to be dropped may be determined by the priority of the PDCCH that scheduled each of the two PDSCHs. In other words, the PDSCH scheduled by the PDCCH with the lower priority may be dropped.

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

[0469] On the other hand, in the case of a broadcast channel, Example 10 may be applied, and in the case of a multicast channel, Example 9 may be applied. Furthermore, if the eRedCap terminal cannot decode both of the above two channels and decodes only one channel, Example 12-1 may be applied.

[0470] Example 13

[0471] As shown 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 G-RNTI, decoding of these channels does not need to be expected. As another example, if the PBCH and MBS channels are received simultaneously or separately, and at least one of each channel is scheduled by MCCH-RNTI, these channels may be decoded simultaneously.

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

[0473] Example 13-1

[0474] As one embodiment of the present disclosure, when a PBCH and an MBS PDSCH (for example, a PDSCH scheduled by MCCH-RNTI) are received simultaneously in one slot, the eRedCap terminal does not need to expect one of the PBCH and MBS PDSCH to be dropped / skipped, or to decode one of the PBCH and MBS PDSCH.

[0475] Here, the case of slot n-1 in Figure 13 (for example, the case where MBS-MCCH-PDSCH and PBCH are scheduled so that they do not overlap in the same slot) may or may not be included. If the sum of the number of PRBs for PBCH and MBS PDSCH is less than or equal to the number of PRBs corresponding to a 5MHz bandwidth, the eRedCap terminal can decode all of PBCH and MBS PDSCH.

[0476] Example 13-2

[0477] As one embodiment of the present disclosure, the eRedCap terminal does not need to expect that a PBCH and an MBS PDSCH (e.g., a PDSCH scheduled by MCCH-RNTI) will be scheduled simultaneously in one slot.

[0478] Here, the case of slot n-1 in Figure 13 (for example, the case where MBS-MCCH-PDSCH and PBCH are scheduled so that they do not overlap in the same slot) may or may not be included. Example 13-2 may be applied when the SCS is 30 kHz. Furthermore, Example 13-2 may be applied when the sum of the number of PRBs in PBCH and MBS PDSCH exceeds the number of PRBs corresponding to a 5 MHz bandwidth.

[0479] Examples 13-1 and 13-2 may be applied when the eRedCap terminal is in the RRC_Inactive or RRC idle state. The operations described in Examples 9-12 may be applied depending on the bandwidth scheduling range of the MBS channel, regardless of the presence or absence of HARQ feedback or the type of MBS casting.

[0480] Example 13-3

[0481] As one embodiment of this disclosure, when the number of PRBs in an MBS channel scheduled in a particular slot exceeds the number of PRBs corresponding to a 5MHz bandwidth, the operation related to Figure 12(a) may be applied. That is, the operations according to Example 10 and Example 10-1 may be applied to the PDSCH scheduled in the next slot relative to the particular slot.

[0482] Example 13-4

[0483] As one embodiment of this disclosure, the method described later may be applied when 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 other channels in the time domain. The method described later may also be applied to slot n-1 in Figure 12(b) where two channels do not overlap within the same slot.

[0484] - The eRedCap terminal can decode all MBS channels and other channels if the sum of the number of PRBs for the MBS channel and other channels does not exceed the number of PRBs corresponding to a 5MHz bandwidth.

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

[0486] As an example, if the other channel is a unicast channel, the eRedCap terminal can drop the unicast channel from among the two channels. Except in the case of NTN, HARQ feedback exists for unicast channels, and the eRedCap terminal can drop the unicast channel from among the two channels. As yet another example, the eRedCap terminal can drop the MBS channel from among the two channels.

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

[0488] As an example, whether or not an MBS channel and a unicast channel are dropped may be determined by the priority of the DCI that scheduled the MBS channel and the unicast channel, depending on whether or not HARQ feedback exists for both MBS channels and unicast channels. As yet another example, if or not HARQ feedback exists for both MBS channels and unicast channels, either one of the MBS channels or the unicast channel may be dropped. The type of channel to be dropped among the MBS channels and unicast channels may be predefined or may be set by higher-level signaling.

[0489] 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 slot reception of unicast and MBS channels.

[0490] Example 13-5

[0491] As one embodiment of the present disclosure, assume that an MBS channel and a unicast PDSCH are scheduled in the same slot. In this case, the MBS channel and the unicast PDSCH may overlap entirely or partially with one symbol in one slot.

[0492] The following describes the operation of the eRedCap terminal when it is not possible to receive both an MBS channel and a unicast PDSCH simultaneously. As an example, the channel to be dropped from among the MBS channels and unicasts may be determined by priority rules and the presence or absence of HARQ feedback. Here, the priority may be indicated by a priority indicator field included in the DCI. As yet another example, the priority may be set by RRC signaling or may be predefined.

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

[0494] For example, if both channels cannot be received simultaneously, the eRedCap terminal does not need to expect simultaneous reception scheduling for both channels.

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

[0496] For example, when HARQ feedback exists or does not exist for both MBS channels and unicast channels, the decision of whether or not an MBS channel and a unicast channel are dropped may be determined by the DCI priority setting that scheduled each channel. For instance, the priority of each channel may be indicated by a DCI priority indicator, and channels with lower priority may be dropped regardless of the presence or absence of HARQ feedback.

[0497] As another example, if HARQ feedback exists or does not exist for 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 from among the MBS channel and unicast channel may be predefined or determined by higher-level signaling.

[0498] As yet another example, either an MBS PDSCH or a unicast PDSCH may be dropped based on the priority set / instructed for each of the MBS PDSCH and unicast PDSCH. If the priorities of the MBS PDSCH and unicast PDSCH are the same, the type of channel to be dropped may be determined by the presence or absence of HARQ feedback. If the priorities and the presence or absence of HARQ feedback of the MBS PDSCH and unicast PDSCH are all the same, the unicast PDSCH may be dropped. As yet another example, if the priorities and the presence or absence of HARQ feedback of the MBS PDSCH and unicast PDSCH are all the same, the type of channel to be dropped from both channels may be predefined or determined by higher-level signaling. As mentioned above, instead of first checking the priorities of both channels and then checking the presence or absence of HARQ feedback, it is also possible to check the presence or absence of HARQ feedback and then check the priorities.

[0499] As yet another example, a bit field may be added to the DCI that schedules the MBS PDSCH. If the MBS PDSCH and unicast PDSCH overlap in the time domain and the eRedCap terminal cannot decode both the MBS PDSCH and unicast PDSCH, the bit field on the DCI can indicate which channels of the MBS PDSCH and unicast PDSCH to drop / decode.

[0500] Example 13-6

[0501] As one embodiment of the present disclosure, assume that an MBS channel and a unicast channel (e.g., a unicast PDSCH) are scheduled within a specific slot, and the number of PRBs in 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 number of PRBs allocated to the MBS channel and the unicast PDSCH (e.g., a PDSCH containing paging or SIBs) exceeds the number of PRBs corresponding to a 5 MHz bandwidth, decoding for any PDSCH that could be scheduled in the next slot after the specific slot does not need to be expected or skipped. For example, an eRedCap terminal does not need to expect scheduling of another PDSCH in the next slot after the specific slot, and the MBS PDSCH in the specific slot may be dropped when it receives another PDSCH in the next slot.

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

[0503] Example 13-7

[0504] In one embodiment of this disclosure, when the number of PRBs in an MCCH-RNTI and associated PDSCH (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 a slot like the PDSCH is not expected, or scheduling of the PBCH is not expected. Furthermore, the PDSCH and PBCH have an FDM relationship and may completely or partially overlap in OFDM symbols.

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

[0506] Example 13-8

[0507] As one embodiment of this disclosure, we assume that a unicast channel (or a PDSCH containing paging information or SIBs, or a PDSCH scheduled by a PDCCH scrambled with CRC by RA-RNTI) and an MBS PDSCH to which at least the number of PRBs corresponding to a 5 MHz bandwidth are allocated overlap on an OFDM symbol. However, the operation described below may also apply when the unicast channel and the MBS PDSCH do not overlap within the same slot.

[0508] In this case, the unicast channel may be dropped (or skipped) or not decoded, regardless of DCI priority or the presence or absence of HARQ feedback. If another channel that is not a unicast channel is scheduled together with the MBS PDSCH in the same slot, the MBS PDSCH may be dropped (or skipped) or not decoded.

[0509] For example, if a non-unicast channel and an MBS PDSCH (or any PDSCH with a number of PRBs equal to or greater than the number of PRBs corresponding to a 5MHz bandwidth) are simultaneously scheduled / received within the same slot, the MBS PDSCH does not need to be decoded by being dropped. In this case, the non-unicast PDSCH may include a unicast channel containing paging or SIBs. As yet another example, Example 13-8 may be applied when the terminal is in the RRC_Idle state or RRC_Inactive state.

[0510] Example 13-9

[0511] 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 a single slot, and the base station can expect to schedule each channel such that the sum of the number of PRBs for the unicast PDSCH and the MBS PDSCH is within the number of PRBs corresponding to a 5 MHz bandwidth.

[0512] Example 13-10

[0513] As one embodiment of the present disclosure, regardless of whether the number of PRBs of an MBS PDSCH (e.g., a broadcast PDSCH) exceeds 25, a terminal can decode all MBS PDSCHs and unicast PDSCHs when they are transmitted / scheduled simultaneously within a single slot. In this case, the MBS PDSCH and unicast PDSCH may partially or entirely overlap on the OFDM symbol.

[0514] Example 13-11

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

[0516] Example 13-12

[0517] 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 terminal may drop the MBS PDSCH regardless of the number of PRBs in the MBS PDSCH. In this case, the MBS PDSCH and the other PDSCH may overlap entirely or partially with OFDM symbols.

[0518] Example 13-13

[0519] As one embodiment of this disclosure, assume that an MBS PDSCH and other channels are transmitted / scheduled in slot n. If the sum of the number of PRBs for the MBS PDSCH and other channels exceeds the number of PRBs corresponding to a 5MHz bandwidth, then regardless of the number of PRBs for the MBS PDSCH, if there are no other PDSCHs in slot n+1, the terminal can decode the MBS PDSCH and all other channels. In this case, the MBS PDSCH and other channels may, but are not limited to, overlap in OFDM symbols.

[0520] For example, the other PDSCH may be a unicast PDSCH, but is not limited to that. If the other PDSCH is a unicast PDSCH, the terminal does not need to decode all MBS PDSCHs and unicast PDSCHs within slot n.

[0521] Examples 13-14

[0522] As one embodiment of this disclosure, assume that an MBS PDSCH and another channel are transmitted / scheduled in slot n. The terminal may drop the MBS PDSCH if the sum of the number of PRBs for the MBS PDSCH and the other channel is equal to or greater than the number of PRBs corresponding to a 5MHz bandwidth. In this case, the MBS PDSCH and the other channel may, but are not limited to, overlap in OFDM symbols. For example, when another PDSCH is scheduled in slot n+1, embodiments 13-14 may be applied.

[0523] As an example, the other PDSCHs mentioned above may include PDSCHs scheduled by SI-RNTIs that require decoding, paging PDSCHs, and so on.

[0524] In this disclosure, if it is not expected that both channels scheduled in one slot will be decoded, the PDSCHs in which channel contention occurs may include the PDSCH scheduled by SI-RNTI and the PDSCH associated with P-RNTI. Other PDSCHs scheduled in the next slot may include PDSCHs that are generally required to be decoded from the terminal's perspective.

[0525] Example 14

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

[0527] In other words, Embodiment 14 relates to a processing method for an eRedCap terminal when one or more MBS channels and one or more unicast PDSCHs are scheduled in one slot. However, this is only one embodiment, and the operation described in Embodiment 14 may also be applied when one MBS channel and one unicast PDSCH are scheduled in one slot.

[0528] In this case, if the sum of the number of PRBs for one or more MBS channels and one or more unicast PDSCHs is less than or equal to the number of PRBs corresponding to a 5MHz bandwidth, the eRedCap terminal can decode all of the one or more MBS channels and one or more unicast PDSCHs.

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

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

[0531] Now, let's assume that another PDSCH is scheduled in the next slot (for example, slot n+1). While the eRedCap terminal can process PRBs equal to the number of PRBs corresponding to a 5MHz bandwidth in one slot, if it cannot drop another PDSCH in the next slot, the eRedCap terminal can drop some of one or more MBS PDSCHs and one or more unicast PDSCHs. The eRedCap terminal can process PRBs in slot n up to the number of PRBs corresponding to a 5MHz bandwidth.

[0532] The following describes a method for determining which channels to drop from one or more MBS PDSCHs and one or more unicast PDSCHs in slot n. In Example 14, we can assume that the eRedCap terminal expects the sum of the number of PRBs of multiple unicast PDSCHs received in one slot to be less than or equal to the PRBs corresponding to a 5MHz bandwidth.

[0533] Example 14-1

[0534] 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 one or more MBS PDSCHs may be dropped by the terminal. In this case, the sum of the number of PRBs for 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 5MHz bandwidth.

[0535] Furthermore, even if removing some of one or more MBS PDSCHs causes the total number of PRBs scheduled in slot n to be less than or equal to the number of PRBs corresponding to a 5MHz bandwidth, all of the one or more MBS PDSCHs may be dropped by the terminal. In this case, all of the one or more unicast PDSCHs may also be dropped, or decoding may not be expected.

[0536] Example 14-2

[0537] 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 PDSCH with the latest starting symbol on the OFDM symbol may be sequentially dropped. In this case, the sum of the number of PRBs for 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 5MHz bandwidth.

[0538] For example, an eRedCap terminal can decode each channel (e.g., undropped multicast and unicast PDSCHs) within slot n, provided that the number of PRBs corresponds to a 5MHz bandwidth. For instance, an eRedCap terminal can decode one or more MBS PDSCHs in order from the PDSCH with the earliest start symbol, and if the number of decoded PRBs exceeds the number of PRBs corresponding to a 5MHz bandwidth, it can drop the corresponding MBS PDSCH. That is, as shown in Figure 14(a), intermediate MBS PDSCHs may be processed in slot n, and the last MBS PDSCH may be dropped.

[0539] As an addition or alternative, we assume that the MBS PDSCHs are TDM-decoded and scheduled consecutively. The eRedCap terminal can schedule one or more MBS PDSCHs in OFDM symbol order and can drop a corresponding MBS PDSCH if the number of decoded PRBs exceeds a certain value. The eRedCap terminal can then 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 as long as the number of PRBs decoded so far in slot n does not exceed the number of PRBs corresponding to a 5MHz bandwidth.

[0540] In other words, the eRedCap terminal can process one or more MBS PDSCHs in the order in which the OFDM symbols begin. When the eRedCap terminal processes the PRBs of a particular 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 OFDM symbol order as long as the number of PRBs does not exceed the 5MHz BW PRB count.

[0541] As described above, one or more MBS PDSCHs may be decoded first, followed by a unicast PDSCH; however, one or more unicast PDSCHs may be decoded first, followed by a multicast PDSCH. As yet another example, both MBS PDSCHs and unicast PDSCHs may be decoded within a 5MHz bandwidth according to their starting symbol order.

[0542] Example 14-3

[0543] In one embodiment of this 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 their respective priorities. Then, decoding of one or more PDSCHs may be performed within a 5 MHz bandwidth range.

[0544] Here, the priority of each MBS PDSCH may be indicated by the DCI that schedules each MBS PDSCH, or it may be set by higher-level signaling. As yet another example, the priority of each MBS PDSCH may be predefined. For example, the priority of a broadcasting PDSCH may be defined as the highest priority or the lowest priority. As yet another example, the priority of a broadcasting PDSCH may be set by higher-level signaling.

[0545] As one embodiment of this disclosure, assume that three or more PDSCHs are scheduled within one slot, and the sum of the PRBs of the three or more PDSCHs exceeds the number of PRBs corresponding to a 5MHz bandwidth.

[0546] As an example, if the sum of the PRB counts of the two highest-priority PDSCHs out of three or more PDSCHs is less than or equal to the number of PRBs corresponding to a 5MHz bandwidth, reception / decoding may be performed on the two PDSCHs, and reception of the remaining PDSCHs may be omitted. As yet another example, if the sum of the PRB counts of the two highest-priority PDSCHs out of three or more PDSCHs exceeds the number of PRBs corresponding to a 5MHz bandwidth, reception / decoding may be performed only on the PDSCH with the relatively higher priority among the two PDSCHs, and reception of the remaining PDSCHs may be omitted. As yet another example, reception / decoding may be performed only on the highest-priority PDSCH out of three or more PDSCHs, and reception of the remaining PDSCHs may be omitted.

[0547] Example 14-4

[0548] In one embodiment of this disclosure, the priority of each of the multiple PDSCHs scheduled in slot n may be determined by the RNTI associated with each of the multiple PDSCHs. That is, the PDSCHs scheduled in slot n may be dropped in order from the lowest priority. This allows the eRedCap terminal to decode PDSCHs within a 5MHz bandwidth range.

[0549] Example 14-5

[0550] In one embodiment of this disclosure, MBS PDSCHs with HARQ feedback may be retransmitted, while among multiple PDSCHs scheduled for slot n, MBS PDSCHs with HARQ feedback may be dropped in order. This allows the eRedCap terminal to decode PDSCHs within a 5MHz bandwidth range.

[0551] For example, if the total number of PRBs in MBS PDSCHs without HARQ feedback exceeds the number of PRBs corresponding to a 5MHz bandwidth, the eRedCap terminal can decode the MBS PDSCHs without HARQ feedback in the order of the starting OFDM symbols within the 5MHz bandwidth. As yet another example, the eRedCap terminal can first drop the MBS PDSCHs that do have HARQ feedback.

[0552] Example 14-6

[0553] In one embodiment of this disclosure, among multiple MBS PDSCHs scheduled within a specific slot, PDSCHs that are repeatedly scheduled may be preferentially dropped. The eRedCap terminal can then decode one or more PDSCHs that have not been dropped within a 5MHz bandwidth range.

[0554] Example 14-7

[0555] As 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 5MHz bandwidth.

[0556] As an example, if the sum of the PRB counts for an MBS PDSCH and multiple unicast PDSCHs exceeds the number of PRBs corresponding to a 5MHz bandwidth, all unicast PDSCHs scheduled for that slot may be dropped, or all multicast PDSCHs may be dropped. If all multicast PDSCHs are dropped, the eRedCap terminal can process unicast PDSCHs within a 5MHz bandwidth. As yet another example, if the sum of the PRB counts for an MBS PDSCH and multiple unicast PDSCHs exceeds the number of PRBs corresponding to a 5MHz bandwidth, all PDSCHs may be dropped.

[0557] Example 14-8

[0558] In one embodiment of this disclosure, if the sum of the number of PRBs of each of the multiple PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to a 5MHz bandwidth, the PDSCHs that are dropped may be identified by the PRB size of each of the multiple PDSCHs. The eRedCap terminal can then process at least one PDSCH that is not dropped within the 5MHz bandwidth.

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

[0560] In this case, if a method is applied that drops MBS PDSCHs scheduled later based on the initial OFDM symbol order, some MBS PDSCHs with 10 PBRs may remain. Therefore, the sum of the PRB counts of the unicast PDSCH and the remaining MBS PDSCH is 30, and thus the eRedCap terminal must also drop the remaining MBS PDSCH. Consequently, if another PDSCH is scheduled on slot n+1, the eRedCap terminal can drop the multiple MBS PDSCHs in order from the PDSCH with the largest / smallest PRB count.

[0561] As yet another example, if multiple MBS PDSCHs have the same number of PRBs, a method may be applied in which later scheduled MBS PDSCHs are dropped based on the starting OFDM symbol order.

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

[0563] Example 14-9

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

[0565] Example 14-10

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

[0567] The operations in Examples 14-1 to 14-10 may be carried out under the assumption that MBS PDSCH and / or unicast PDSCH are dropped based on the position of the OFDM symbol, whether or not repetitive transmission is set, whether or not there is HARQ feedback, priority and / or the number of PRBs, etc.

[0568] Furthermore, the operation according to Examples 14-1 to 14-10 may also be applied when the unicast PDSCH shown in Figure 14(a) becomes an MBS PDSCH (i.e., when three MBS PDSCHs are scheduled in one slot). Additionally, the same priority may be assigned to MBS PDSCHs and unicast PDSCHs scheduled in the same slot, and the priority-based or PRB-count-based dropping rules described above may be applied.

[0569] As an example, a drop rule based on the number of PRBs (for example, a rule that prioritizes dropping channels with a large / small number of PRBs) may be applied. As yet another example, unicast PDSCHs and / or MBS PDSCHs may be dropped based on the OFDM symbol start position or the presence or absence of HARQ. In other words, the above drop rules may be applied to both unicast PDSCHs and MBS PDSCHs.

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

[0571] If the total number of PRBs for unicast channels exceeds the number of PRBs corresponding to a 5MHz bandwidth, and no PDSCH is scheduled on the slot immediately following a particular slot, the eRedCap terminal can decode all channels on that particular slot.

[0572] Example 14-11

[0573] As one embodiment of this disclosure, when each channel is scheduled in slot n as shown in Figure 14(c), it is necessary to determine how the unicast channels are dropped. That is, when multiple unicast channels are TDM-scheduled within one slot, the eRedCap terminal can transmit terminal capacity information to the base station indicating whether it can assist in decoding multiple unicast channels and / or the number of decodeable channels. The eRedCap terminal may transmit / use the above-described terminal capacity information, or new capacity information may be defined for the eRedCap terminal. As yet another example, the eRedCap terminal does not have to assist in decoding / receiving multiple unicast channels or multiple MBS PDSCHs.

[0574] As an example of this disclosure, the eRedCap terminal can sequentially drop the MBS PDSCH with the latest starting symbol on the OFDM symbol (i.e., decode from the PDSCH with the earliest starting symbol position on the OFDM symbol). This allows the eRedCap terminal to decode one or more PDSCHs within a 5MHz bandwidth range.

[0575] Example 14-12

[0576] In one embodiment of this 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 their respective priorities. Then, decoding of one or more PDSCHs may be performed within a 5 MHz bandwidth range.

[0577] Here, the priority of each unicast PDSCH may be indicated by the DCI that schedules each unicast PDSCH, or it may be set by higher-level signaling. As yet another example, the priority of each unicast PDSCH may be predefined. For example, the priority of a broadcasting PDSCH may be defined as the highest priority or the lowest priority. As yet another example, the priority of a broadcasting PDSCH may be set by higher-level signaling.

[0578] As one embodiment of this disclosure, assume that three or more PDSCHs are scheduled within one slot, and the sum of the PRBs of the three or more PDSCHs exceeds the number of PRBs corresponding to a 5MHz bandwidth.

[0579] As an example, if the sum of the PRB counts of the two highest-priority PDSCHs out of three or more PDSCHs is less than or equal to the number of PRBs corresponding to a 5MHz bandwidth, reception / decoding may be performed on the two PDSCHs, and reception of the remaining PDSCHs may be omitted. As yet another example, if the sum of the PRB counts of the two highest-priority PDSCHs out of three or more PDSCHs exceeds the number of PRBs corresponding to a 5MHz bandwidth, reception / decoding may be performed only on the PDSCH with the relatively higher priority among the two PDSCHs, and reception of the remaining PDSCHs may be omitted. As yet another example, reception / decoding may be performed only on the highest-priority PDSCH out of three or more PDSCHs, and reception of the remaining PDSCHs may be omitted.

[0580] Examples 14-13

[0581] In one embodiment of this disclosure, unicast PDSCHs with HARQ feedback may be retransmitted, and among multiple PDSCHs scheduled in slot n, unicast PDSCHs with HARQ feedback may be dropped in order. This allows the eRedCap terminal to decode PDSCHs within a 5MHz bandwidth range.

[0582] For example, if the sum of the PRB counts for unicast PDSCHs without HARQ feedback exceeds the number of PRBs corresponding to a 5MHz bandwidth, the eRedCap terminal can decode the unicast PDSCHs without HARQ feedback in the order of their initial OFDM symbols within the 5MHz bandwidth. As yet another example, the eRedCap terminal can first drop unicast PDSCHs that do have HARQ feedback.

[0583] Example 14-14

[0584] In one embodiment of this disclosure, among multiple unicast PDSCHs scheduled within a specific slot, PDSCHs that are repeatedly scheduled may be preferentially dropped. The eRedCap terminal can then decode one or more PDSCHs that have not been dropped within a 5MHz bandwidth range.

[0585] Examples 14-15

[0586] As one embodiment of this disclosure, when multiple unicast PDSCHs are scheduled in one slot, the terminal may or may not expect that the total number of PRBs of the multiple unicast PDSCHs will not exceed 25. If the total number of PRBs of the multiple unicast PDSCHs exceeds 25, the terminal does not need to decode the multiple unicast PDSCHs.

[0587] Examples 14-16

[0588] In one embodiment of this disclosure, if the sum of the number of PRBs of each of the multiple PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to a 5MHz bandwidth, the PDSCHs that will be dropped may be identified by the PRB size of each of the multiple PDSCHs. For example, the eRedCap terminal can decode / drop unicast PDSCHs with large PRB sizes or PDSCHs with small PRB sizes. The eRedCap terminal can then process at least one PDSCH that has not been dropped within the 5MHz bandwidth.

[0589] Examples 14-17

[0590] As one embodiment of the present disclosure, if the sum of the number of PRBs for each of the multiple unicast PDSCHs scheduled in slot n does not exceed the number of PRBs corresponding to a 5MHz bandwidth, the eRedCap terminal can determine which of the multiple unicast PDSCHs to decode / drop.

[0591] Examples 14-18

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

[0593] The above-described embodiment relates to a method for determining which channels to drop among MBS PDSCH and unicast PDSCH when MBS PDSCH and unicast PDSCH are scheduled in a specific slot.

[0594] The method for determining which channels to drop among MBS PDSCH and unicast PDSCH may be based on factors such as the presence or absence of HARQ feedback for each channel, priority, presence or absence of repeat transmission settings, and channel type. The eRedCap terminal may consider the presence or absence of HARQ feedback for each channel, priority, presence or absence of repeat transmission settings, and channel type in that order when determining which channels to drop.

[0595] However, this is only one embodiment, and the eRedCap terminal can determine the presence or absence of HARQ feedback for each channel, its priority, whether or not it is set to repeat transmission, and the order of the channel types as factors for determining which channels to drop. In yet another example, the presence or absence of HARQ feedback for each channel, its priority, whether or not it is set to repeat transmission, and the order of the channel types as factors for determining which channels to drop may be predefined or set by higher-layer signaling.

[0596] For example, if a unicast channel and an MBS channel are scheduled in one slot, and the sum of the PRB numbers for the unicast channel and the MBS channel exceeds the number corresponding to a 5MHz bandwidth, the eRedCap terminal can decode / drop each channel as long as the number of PRBs in that slot does not exceed the number corresponding to a 5MHz bandwidth. In this case, the eRedCap terminal may preferentially drop the MBS channel, or preferentially drop the unicast channel. As yet another example, the eRedCap terminal may begin dropping OFDM symbols from the slowest / earliest channel, or may drop at least one channel depending on the presence or absence of HARQ feedback or the number of PRBs.

[0597] For example, an eRedCap terminal can determine the drop / decoding of a unicast PDSCH or MBS PDSCH scheduled in one slot within a 5MHz bandwidth based on priority, number of PRBs, and starting OFDM symbol position. As yet another example, an eRedCap terminal can determine the drop / decoding of a unicast PDSCH or MBS PDSCH scheduled in one slot within a 5MHz bandwidth based on the presence or absence of HARQ feedback, number of PRBs, or starting OFDM symbol position.

[0598] In other words, the decoding / dropping order / method of MBS / unicast channels may be determined by the cases described below. Each case indicates the factors to be given priority consideration in determining which channels to drop / decode. However, this is only one example, and further cases may exist.

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

[0600] Case 2: PDSCH type (MBS channel or unicast channel) > Number of PRBs (larger or smaller value) > Start OFDM symbol

[0601] Case 3: HARQ (presence or absence) > Starting OFDM symbol > PDSCH type (MBS or unicast)

[0602] Case 4: HARQ (presence or absence) > PDSCH type (MBS or unicast) > Starting OFDM symbol

[0603] In the above-described case, drop / decoding operations can be performed depending on whether the sum of the number of PRBs in each MBS PDSCH or unicast PDSCH exceeds the number of PRBs corresponding to a 5MHz bandwidth. For example, when an eRedCap terminal decodes sequentially scheduled channels, it can determine whether the sum of the number of PRBs in the decoded channels exceeds the number of PRBs corresponding to a 5MHz bandwidth.

[0604] For example, in Case 1, the eRedCap terminal can prioritize processing unicast PDSCHs. In this case, if the number of decoded PRBs does not exceed the number of PRBs corresponding to a 5MHz bandwidth, the eRedCap terminal can decode MBS PDSCHs. If the number of decoded PRBs exceeds the number of PRBs corresponding to a 5MHz bandwidth, further MBS PDSCHs to decode within the 5MHz bandwidth range may be determined. In this case, the MBS PDSCHs to decode / drop may be determined by the start OFDM symbol of the MBS PDSCH.

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

[0606] Example 15

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

[0608] In other words, in Example 15, the channel in a slot may be dropped if the number of PRBs scheduled in that slot exceeds the number of PRBs corresponding to a 5MHz bandwidth, without considering whether or not another PDSCH is scheduled in the next slot. In Figures 14(a) and (b), reception of a specific PDSCH may not be processed even if no other PDSCH exists in slot n+1. In this case, the method described above may be used when determining which PDSCH to drop among unicast PDSCHs and multicast PDSCHs in slot n.

[0609] Example 14 applies the above method when another PDSCH is scheduled in the next slot (e.g., slot n+1), and Example 15 relates to a drop method for each channel when a number of PRBs corresponding to a 5MHz bandwidth are scheduled in slot n, regardless of whether another PDSCH is scheduled in the next slot (e.g., slot n+1).

[0610] For example, in a situation like that shown in Figure 15(a) (for instance, when the sum of the number of PRBs for each channel scheduled in slot n exceeds the number of PRBs corresponding to a 5MHz bandwidth), if the method according to Example 14-2 is applied, since there are no other channels in slot n+1, the eRedCap terminal can decode all unicast PDSCHs and MBS PDSCHs.

[0611] However, when the method according to Example 15 is applied, slot n may process only the number of PRBs corresponding to the 5MHz bandwidth, regardless of whether or not 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 the 5MHz bandwidth, that channel may be dropped.

[0612] As an example, when the operation according to Example 15 is applied to Figure 15(a), the second MBS PDSCH with 30 PRBs may be dropped, and the first MBS PDSCH, the third unicast PDSCH, and the next MBS PDSCH may also be dropped. The above example illustrates the case where no priority is specified between unicast PDSCHs and MBS PDSCHs. When separate priorities are set / instructed / defined for each of the MBS PDSCHs or unicast PDSCHs, the types of channels decoded / dropped may differ, and this may also apply to Example 14.

[0613] As an example of this disclosure, when a priority is set / instructed / defined for a unicast channel, the PRBs of MBS PDSCHs may be added after the sum of the PRB counts of unicast PDSCHs is calculated, as shown in Figure 15(b). When the PRBs of MBS PDSCHs are added to the sum of the PRB counts of unicast PDSCHs according to OFDM order, the MBS PDSCH that is closest to the OFDM symbol (i.e., the MBS PDSCH with 6 PRBs) may be decoded. Then, when it is decided to decode the MBS PDSCH after the unicast channel (i.e., the PDSCH with 6 PRBs), the MBS PDSCH after the unicast channel (i.e., the PDSCH with 6 PRBs) may be decoded.

[0614] As an example of this disclosure, the processing order of unicast PDSCHs may be determined by the order of OFDMs. If additional processing of MBS PDSCHs is possible, the starting OFDM symbol may determine which PDSCHs are processed, or whether MBS PDSCHs after unicast channels are processed preferentially.

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

[0616] The operation according to Example 14 may be applied only when another PDSCH is scheduled in slot n+1 in Figure 15(a). If further processing of MBS channels is required when the sum of the number of PRBs of the unicast PDSCHs does not exceed the number of PRBs corresponding to the 5MHz bandwidth, the eRedCap terminal can process each MBS channel sequentially by OFDM symbol order. That is, the eRedCap terminal can decode each channel within the 5MHz bandwidth.

[0617] For example, if there are more MBS PDSCHs than the number of PRBs corresponding to a 5MHz bandwidth, all MBS PDSCHs and PDSCHs scheduled after them may be dropped.

[0618] For example, in Figure 15(a), because the MBS PDSCH has 8 PRBs, it may not be able to complete the processing of subsequent MBS PDSCHs. In contrast, in Figure 15(b), because the MBS PDSCH has 6 PRBs, it can process the PDSCH.

[0619] The embodiments described above may be applied regardless of whether the MBS PDSCH and unicast PDSCH are TDM'd by each other or whether the MBS PDSCH and unicast PDSCH overlap in OFDM symbols.

[0620] The eRedCap terminal can transmit terminal capacity information to the base station, which includes the number of MBS PDSCHs and unicast PDSCHs that can be processed in a single slot or consecutive slots. In this case, the terminal capacity information may be defined separately for the eRedCap terminal, in addition to the capacity information described above.

[0621] Furthermore, for MBS PDSCH and unicast PDSCH that could not be decoded due to being dropped, a NACK may be sent from the terminal to the base station.

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

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

[0624] As yet another example, in Example 15, regardless of whether a PDSCH is scheduled in the next slot, if the sum of the number of PRBs of the PDSCHs scheduled in slot n exceeds the number of PRBs corresponding to a 5MHz bandwidth, the above-described example may determine which of the MBS PDSCH channels will be dropped.

[0625] For example, if channel dropping is required, the eRedCap terminal can determine which of the remaining MBS and unicast PDSCHs to process within the 5MHz bandwidth, excluding MBS PDSCHs exceeding 5MHz bandwidth.

[0626] General equipment to which this disclosure applies

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

[0628] Referring to Figure 16, the first device 100 and the second device 200 can send and receive wireless signals using various wireless connectivity technologies (e.g., LTE, NR).

[0629] The first device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memories 104 and / or the transceivers 106 and be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed in this disclosure.

[0630] For example, the processor 102 may process the information in the memory 104 to generate first information / signal, and then transmit a wireless signal containing the first information / signal from the transceiver 106. Alternatively, after the processor 102 receives a wireless signal containing second information / signal from the transceiver 106, it may store the information obtained from signal processing of the second information / signal in the memory 104.

[0631] Memory 104 may be coupled to processor 102 and can store various information related to the operation of processor 102. For example, memory 104 may store software code including instructions for performing some or all of the processes controlled by processor 102, or for performing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed in this disclosure. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). Transceiver 106 may be coupled to processor 102 and can transmit and / or receive radio signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or receiver. Transceiver 106 may be replaced with an RF (Radio Frequency) unit. In this disclosure, device may mean communication modem / circuit / chip.

[0632] 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 may control the memory 204 and / or the transceiver 206 and be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed herein. For example, the processor 202 may process information in the memory 204 to generate third information / signals and then transmit a radio signal containing the third information / signals from the transceiver 206. Alternatively, the processor 202 may receive a radio signal containing fourth information / signals from the transceiver 206 and then store information obtained from signal processing of the fourth information / signals in the memory 204. The memory 204 may be linked to the processor 202 and can store various information related to the operation of the processor 202. For example, memory 204 may store software code that includes instructions for performing some or all of the processes controlled by processor 202, or for performing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). Transceiver 206 may be coupled with processor 202 and can transmit and / or receive radio signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or receiver. Transceiver 206 may be replaced with an RF unit. In this disclosure, device may mean communication modem / circuit / chip.

[0633] The hardware elements of devices 100,200 are described in more detail below. However, one or more protocol layers may be embodied by one or more processors 102,202. For example, one or more processors 102,202 may embodied 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 PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure. One or more processors 102,202 may generate messages, control information, data or information by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure. One or more processors 102,202 can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information by means of the functions, procedures, suggestions, and / or methods disclosed in this disclosure and provide them 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 can acquire PDUs, SDUs, messages, control information, data, or information by means of the descriptions, functions, procedures, suggestions, methods, and / or operation sequence diagrams disclosed in this disclosure.

[0634] One or more processors 102,202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102,202 may be embodied by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102,202. The descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be contained in 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, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions and / or sets of instructions.

[0635] One or more memories 104,204 may be connected to one or more processors 102,202 and can store various forms of data, signals, messages, information, programs, code, instructions and / or commands. One or more memories 104,204 may consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media and / or combinations thereof. One or more memories 104,204 may be located inside and / or outside of one or more processors 102,202. Furthermore, one or more memories 104,204 may be connected to one or more processors 102,202 by various technologies such as wired or wireless connections.

[0636] One or more transceivers 106,206 can transmit user data, control information, radio signals / channels, etc., as referred to in the methods and / or operation sequence diagrams of this disclosure, to one or more other devices. One or more transceivers 106,206 can receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure, from one or more other devices. For example, one or more transceivers 106,206 may be coupled with one or more processors 102,202 to transmit and receive radio signals. For example, one or more processors 102,202 can control one or more transceivers 106,206 to transmit user data, control information, or radio signals to one or more other devices. Also, one or more processors 102,202 can control one or more transceivers 106,206 to receive user data, control information, or radio signals from one or more other devices. Furthermore, one or more transceivers 106,206 may be connected 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, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure, via one or more antennas 108,208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106,206 may convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102,202. One or more transceivers 106,206 may convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102,202, from baseband signals to RF band signals. To this end, one or more transceivers 106,206 may include (analog) oscillators and / or filters.

[0637] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly mentioned. Each component or feature may be implemented in a form that does not combine with other components or features. It is also possible to combine some components and / or features to constitute embodiments of the present disclosure. The order of operations described in embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in other embodiments, or replaced by corresponding components or features of other embodiments. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to constitute embodiments, or may be included as new claims by amendment after filing.

[0638] It will be obvious to those skilled in the art that this disclosure can be embodied in other specific forms, provided that the essential features of this disclosure are not deviated from. Therefore, the above-mentioned detailed description should not be constrained in any way and should be considered illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of this disclosure are included within the scope of this disclosure.

[0639] The scope of this disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause an apparatus or computer to perform operations according to the methods of various embodiments, and non-transitory computer-readable medium on which such software or instructions are stored and executable on the apparatus or computer. Instructions available for programming a processing system that performs the features described in this disclosure may be stored on / in a storage medium or computer-readable storage medium, and the features described in this disclosure may be embodied using a computer program product including such storage medium. The storage medium may 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 may 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. Memory optionally includes one or more storage devices located remotely from the processor. Memory, or alternatively, non-volatile memory devices within memory, includes non-transitory computer-readable storage medium. The features described in this disclosure may be stored on any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of the processing system and cause the processing system to interact with other mechanisms that utilize the results relating to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems and execution environments / containers.

[0640] Here, the wireless communication technologies embodied in devices 100 and 200 of this disclosure may include, in addition to LTE, NR, and 6G, Narrowband Internet of Things (NB-IoT) for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be embodied by standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the names given above. Additionally or alternatively, the wireless communication technologies embodied in devices 100 and 200 of this disclosure may communicate based on LTE-M technology. In this case, 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 may be embodied by at least one of various standards, including 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or alternatively, wireless communication technologies embodied in devices 100,200 of this disclosure may include at least one of ZigBee, Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), and is not limited to the names mentioned above. For example, ZigBee technology can generate personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

[0641] [Industrial applicability] Although the method proposed in this disclosure has been described primarily in terms of its application to 3GPP LTE / LTE-A and 5G systems, it is applicable to a variety of other wireless communication systems as well.

[0642] [Claims when filing an international application] [Claim 1] A method performed by a terminal (user equipment: UE) in a wireless communication system, The first downlink channel and the second downlink channel are received from the base station (STA) in the first slot, The process includes the step of decoding the first downlink channel and the second downlink channel based on the fact that the number of physical resource blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold, The first downlink channel and the second downlink channel overlap partially or totally in the time domain. [Claim 2] The method according to claim 1, wherein capacity information indicating support for receiving the first downlink channel and the second downlink channel, which are frequency-division multiplexed (FDMed) in a single slot, is transmitted from the terminal to the base station. [Claim 3] The aforementioned first downlink channel is a unicast physical downlink shared channel (PDSCH), The method according to claim 1, wherein the second downlink channel is a multicast PDSCH or a broadcast PDSCH. [Claim 4] The method according to claim 1, wherein the PRBs assigned to the first downlink and the second downlink do not overlap with each other. [Claim 5] Based on the subcarrier spacing (SCS) being set to 15 kHz, the first threshold is 25. The method according to claim 1, wherein the first threshold is 12, based on the SCS being set to 30 kHz. [Claim 6] The method according to claim 1, wherein decoding for either the first downlink channel or the second downlink channel is skipped based on the number of PRBs assigned to each of the first downlink channel and the second downlink channel exceeding the threshold. [Claim 7] The first downlink channel is scheduled by first downlink control information (DCI) that has been scrambled by CRC (cyclic redundancy check) using C(cell)-RNTI (radio network temporary identifier) ​​or CS (configured scheduling)-RNTI. The method according to claim 1, wherein the second downlink channel is scheduled by a second DCI scrambled with CRC by a G(group)-RNTI or MCCH (multicast broadcast service control channel)-RNTI. [Claim 8] The method according to claim 1, wherein the terminal is an enhanced reduced capability (eRedCap) terminal. [Claim 9] A method performed by a terminal (user equipment: UE) in a wireless communication system, The first downlink channel is received from the base station (STA) in slot n (where n is a non-negative integer), The process includes the step of processing reception of the first downlink channel based on the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel is less than or equal to a second threshold, A method in which the reception of the first downlink channel is not processed by the terminal based on the number of PRBs allocated to the first downlink channel exceeding the second threshold, and the reception of the first downlink channel being repetitive or the reception of the second downlink channel in slot n+1. [Claim 10] A terminal (user equipment: UE) that performs communication in a wireless communication system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first downlink channel and the second downlink channel are received in the first slot from the base station (station:STA) via one or more transceivers; The system is configured to decode the first downlink channel and the second downlink channel based on whether the number of physical resource blocks (PRBs) allocated to each of the first downlink channels is less than or equal to a first threshold. The first downlink channel and the second downlink channel are terminals that partially or totally overlap in the time domain. [Claim 11] A method performed by a base station (STA) in a wireless communication system, The first step involves sending information to the terminal (user equipment: UE) in the first slot to schedule the first and second downlink channels. The process includes the step of transmitting the first downlink channel and the second downlink channel to the terminal in the first slot, Based on the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel and the second downlink channel is less than or equal to a first threshold, the first downlink channel and the second downlink channel are decoded by the terminal. The first downlink channel and the second downlink channel overlap partially or totally in the time domain, in a manner. [Claim 12] A base station (STA) that performs communication in a wireless communication system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: Information for scheduling the first downlink channel and the second downlink channel is transmitted to the terminal (user equipment: UE) via one or more transceivers in the first slot; The first downlink channel and the second downlink channel are configured to be transmitted to the terminal via the one or more transceivers in the first slot; Based on the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel and the second downlink channel is less than or equal to a first threshold, the first downlink channel and the second downlink channel are decoded by the terminal. A base station in which the first downlink channel and the second downlink channel partially or totally overlap in the time domain. [Claim 13] A processing device configured to control a terminal (user equipment: UE) for communication in a wireless communication system, One or more processors, The system comprises one or more computer memories that are operably connected to one or more processors and store instructions for performing actions based on execution by the one or more processors, The aforementioned operation is, The operation involves receiving the first downlink channel and the second downlink channel from the base station (STA) in the first slot, The operation includes decoding the first downlink channel and the second downlink channel based on the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel and the second downlink channel, respectively, is less than or equal to a first threshold, A processing device in which the first downlink channel and the second downlink channel partially or totally overlap in the time domain. [Claim 14] One or more non-transitory computer-readable media for storing one or more instructions, The aforementioned one or more instructions are executed by one or more processors, and a device that performs communication in a wireless communication system, The first downlink channel and the second downlink channel are received from the base station (STA) in the first slot; The system controls the decoding of the first and second downlink channels based on whether the number of physical resource blocks (PRBs) allocated to each of the first and second downlink channels is less than or equal to a first threshold. The first downlink channel and the second downlink channel are computer-readable media that partially or totally overlap in the time domain.

Claims

1. A method performed by a terminal (user equipment: UE) in a wireless communication system, The first downlink channel and the second downlink channel are received from the base station (STA) in the first slot, The process includes the step of decoding the first downlink channel and the second downlink channel based on the fact that the number of physical resource blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold, A method wherein the first downlink channel and the second downlink channel partially or totally overlap in the time domain.

2. The method according to claim 1, wherein capacity information indicating support for receiving the first downlink channel and the second downlink channel, which are frequency-division multiplexed (FDMeD) in a single slot, is transmitted from the terminal to the base station.

3. The first downlink channel is a unicast physical downlink shared channel (PDSCH), The method according to claim 1, wherein the second downlink channel is a multicast PDSCH or a broadcast PDSCH.

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

5. Based on the subcarrier spacing (SCS) being set to 15 kHz, the first threshold is 25. The method according to claim 1, wherein the first threshold is 12 based on the setting of the SCS to 30 kHz.

6. The method according to claim 1, wherein decoding for either the first downlink channel or the second downlink channel is skipped based on the number of PRBs assigned to each of the first downlink channel and the second downlink channel exceeding the threshold.

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

8. The method according to claim 1, wherein the terminal is an improved reduced capacity (eRedCap) terminal.

9. A method performed by a terminal (user equipment: UE) in a wireless communication system, The first downlink channel is received from the base station (STA) in slot n (where n is a non-negative integer), The process includes the step of processing reception of the first downlink channel based on the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel is less than or equal to a second threshold, A method in which the reception of the first downlink channel is not processed by the terminal based on the number of PRBs assigned to the first downlink channel exceeding the second threshold, and the reception of the first downlink channel being repeated or the reception of the second downlink channel in slot n+1.

10. A terminal (user equipment: UE) that performs communication in a wireless communication system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first downlink channel and the second downlink channel are received in the first slot from the base station (STA) via one or more transceivers; The system is configured to decode the first downlink channel and the second downlink channel based on whether the number of physical resource blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold; The first downlink channel and the second downlink channel are terminals that partially or totally overlap in the time domain.

11. A method performed by a base station (STA) in a wireless communication system, The first step involves sending information for scheduling the first and second downlink channels to the terminal (user equipment: UE) in the first slot, The process includes the step of transmitting the first downlink channel and the second downlink channel to the terminal in the first slot, Based on the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel and the second downlink channel, respectively, is 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. A base station (STA) that performs communication in a wireless communication system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: Information for scheduling the first downlink channel and the second downlink channel is transmitted to the terminal (user equipment: UE) via one or more transceivers in the first slot; The first downlink channel and the second downlink channel are configured to be transmitted to the terminal via the one or more transceivers in the first slot; Based on the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel and the second downlink channel, respectively, is 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 in which the first downlink channel and the second downlink channel partially or totally overlap in the time domain.

13. A processing device configured to control a terminal (user equipment: UE) for communication in a wireless communication system, One or more processors, The system comprises one or more computer memories that are operably connected to one or more processors and store instructions for performing actions based on execution by the one or more processors, The aforementioned operation is, The operation involves receiving the first downlink channel and the second downlink channel from the base station (STA) in the first slot, The operation includes decoding the first downlink channel and the second downlink channel based on the fact that the number of physical resource blocks (PRBs) allocated to the first downlink channel and the second downlink channel, respectively, is less than or equal to a first threshold, A processing device in which 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 for storing one or more instructions, The aforementioned one or more instructions are executed by one or more processors, and a device that performs communication in a wireless communication system, The first downlink channel and the second downlink channel are received from the base station (STA) in the first slot; The system is controlled to decode the first downlink channel and the second downlink channel based on whether the number of physical resource blocks (PRBs) allocated to each of the first downlink channel and the second downlink channel is less than or equal to a first threshold. The first downlink channel and the second downlink channel are computer-readable media that partially or totally overlap in the time domain.

Images