Method and apparatus for performing downlink transmission and reception in wireless communication system
The method enables efficient downlink transmission and reception in wireless communication systems by allowing terminals to decode multiple downlinks in a single slot based on resource block allocation, addressing the challenges of high data traffic and latency in next-generation mobile systems.
Patent Information
- Application Number
- PCT/KR2024/005881
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-11-02
- Filing Date
- 2024-04-30
- Publication Date
- 2024-11-21
AI Technical Summary
Current wireless communication systems face challenges in supporting explosive data traffic, high transmission rates, a large number of connected devices, very low end-to-end latency, and high energy efficiency, particularly in downlink transmission and reception, especially in narrowband scenarios.
The method involves a terminal and base station capable of receiving and transmitting unicast and multicast downlink channels in a single slot, with the terminal decoding channels based on the total sum of resource blocks allocated, allowing for efficient processing of multiple downlinks in a narrowband environment.
This approach enhances the capability of terminals to efficiently process downlink channels in a unit slot, improving data transmission efficiency and supporting the requirements of next-generation mobile communication systems.
Smart Images

Figure KR2024005881_21112024_PF_FP_ABST
Abstract
Description
Method and device for performing downlink transmission and reception in a wireless communication system
[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for performing downlink transmission and reception in a narrowband in a wireless communication system.
[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users' demand for higher-speed services, necessitating a more advanced mobile communication system.
[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.
[0004] The technical problem of the present disclosure is to provide a method and device for performing downlink transmission and reception in a wireless communication system.
[0005] The technical problem of the present disclosure is to provide a method and device for transmitting and receiving at least one unicast / multicast downlink in a narrowband.
[0006] The technical problem of the present disclosure is to provide a method and device for processing multiple unicast / multicast downlinks received simultaneously in a narrowband.
[0007] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.
[0008] In one embodiment of the present disclosure, a method performed by a terminal in a wireless communication system may include the steps of: transmitting first capability information indicating that reception of a unicast downlink channel and a multicast downlink channel is supported in a single slot to a base station; receiving information from the base station for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (where n is a natural number); and decoding at least one downlink channel of the one or more unicast downlink channels or the one or more multicast downlink channels based on a sum of physical resource blocks (RBs) allocated to each of the one or more unicast downlink channels and the one or more multicast downlink channels exceeding a threshold.
[0009] In another embodiment of the present disclosure, a method performed by a base station in a wireless communication system comprises the steps of: receiving, from a terminal, first capability information indicating that reception of a unicast downlink channel and a multicast downlink channel is supported in a single slot; and transmitting, to the terminal, information for scheduling at least one unicast downlink channel and at least one multicast downlink channel on slot n (where n is a natural number), wherein at least one downlink channel of the at least one unicast downlink channel or the at least one multicast downlink channel can be decoded by the terminal based on a sum of physical resource blocks (RBs) allocated to each of the at least one unicast downlink channel and the at least one multicast downlink channel exceeding a threshold.
[0010] According to various embodiments of the present disclosure, a method and apparatus for performing downlink transmission and reception in a wireless communication system can be provided.
[0011] According to various embodiments of the present disclosure, a method and apparatus for transmitting and receiving at least one unicast / multicast downlink in a narrowband may be provided.
[0012] According to various embodiments of the present disclosure, a method and apparatus for processing multiple unicast / multicast downlinks received simultaneously in a narrowband can be provided.
[0013] According to various embodiments of the present disclosure, an enhanced reduced capability (eRedCap) terminal can more efficiently process downlinks scheduled in a unit slot.
[0014] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.
[0015] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.
[0016] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.
[0017] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.
[0018] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.
[0019] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied.
[0020] FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.
[0021] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.
[0022] FIG. 7 is a diagram for explaining a process in which a terminal performs communication according to one embodiment of the present disclosure.
[0023] FIG. 8 is a diagram for explaining a process in which a base station performs communication according to one embodiment of the present disclosure.
[0024] FIG. 9 is a diagram illustrating a procedure for scheduling downlink channels by slot according to one embodiment of the present disclosure.
[0025] FIG. 10 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.
[0026] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.
[0027] In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.
[0028] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.
[0029] In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.
[0030] The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and / or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of " / " between words in this disclosure has the same meaning as "and / or" unless otherwise stated.
[0031] The present disclosure describes a wireless communication network or a wireless communication system, and an operation performed in a wireless communication network may be performed in a process of controlling the network and transmitting or receiving a signal from a device (e.g., a base station) that manages the wireless communication network, or may be performed in a process of transmitting or receiving a signal to or between terminals connected to the wireless network.
[0032] In the present disclosure, transmitting or receiving a channel means transmitting or receiving information or a signal through the channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.
[0033] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.
[0034] The following technologies can be used in various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA can be implemented using wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.
[0035] For clarity, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS (Technical Specification) 36.xxx Release 8. Specifically, LTE technology after 3GPP TS 36.xxx Release 10 is referred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be referred to as a 3GPP system. "xxx" refers to a standard document detail number. LTE / NR may be collectively referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published prior to the present disclosure. For example, reference may be made to the following documents.
[0036] For 3GPP LTE, see TS 36.211 (Physical channels and modulation), TS 36.212 (Multiplexing and channel coding), TS 36.213 (Physical layer procedures), TS 36.300 (General description), and TS 36.331 (Radio resource control).
[0037] For 3GPP NR, see TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (Overall description of NR and New Generation-Radio Access Network (NG-RAN)), and TS 38.331 (Radio Resource Control Protocol Specification).
[0038] Abbreviations for terms that may be used in this disclosure are defined as follows.
[0039] - BM: beam management
[0040] - CQI: Channel Quality Indicator
[0041] - CRI: Channel state information - reference signal resource indicator
[0042] - CSI: Channel State Information
[0043] - CSI-IM: Channel State Information - Interference Measurement
[0044] - CSI-RS: Channel state information - reference signal
[0045] - DMRS: Demodulation Reference Signal
[0046] - FDM: frequency division multiplexing
[0047] - FFT: fast Fourier transform
[0048] - IFDMA: interleaved frequency division multiple access
[0049] - IFFT: inverse fast Fourier transform
[0050] - L1-RSRP: Layer 1 reference signal received power
[0051] - L1-RSRQ: Layer 1 reference signal received quality
[0052] - MAC: Medium Access Control
[0053] - NZP: non-zero power
[0054] - OFDM: orthogonal frequency division multiplexing
[0055] - PDCCH: Physical downlink control channel
[0056] - PDSCH: Physical downlink shared channel
[0057] - PMI: precoding matrix indicator
[0058] - RE: resource element
[0059] - RI: Rank indicator
[0060] - RRC: Radio Resource Control
[0061] - RSSI: Received signal strength indicator
[0062] - Rx: Reception
[0063] - QCL: quasi co-location
[0064] - SINR: signal to interference and noise ratio
[0065] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH))
[0066] - TDM: Time Division Multiplexing
[0067] - TRP: transmission and reception point
[0068] - TRS: Tracking Reference Signal
[0069] - Tx: transmission
[0070] - UE: user equipment
[0071] - ZP: Zero Power
[0072] System General
[0073] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications compared to existing radio access technologies (RATs) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs that consider enhanced mobile broadband communication (eMBB), massive MTC (MMTC), and Ultra-Reliable and Low Latency Communication (URLLC) is being discussed. For convenience, these technologies are referred to as NR in this disclosure. NR is an expression representing an example of 5G RAT.
[0074] A new RAT system, including NR, uses OFDM or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, a single cell may support multiple numerologies. That is, terminals operating under different numerologies can coexist within a single cell.
[0075] A numerology corresponds to a single subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.
[0076] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.
[0077] Referring to Fig. 1, the NG-RAN consists of gNBs that provide NG-RA (NG-Radio Access) user plane (i.e., new AS (access stratum) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and control plane (RRC) protocol termination for UE. The gNBs are interconnected via Xn interfaces. The gNBs are also connected to the NGC (New Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Function) via the N2 interface and to the UPF (User Plane Function) via the N3 interface.
[0078] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.
[0079] NR systems can support multiple numerologies. Numerologies can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). Furthermore, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band. Furthermore, NR systems can support various frame structures corresponding to multiple numerologies.
[0080] Below, we examine OFDM numerologies and frame structures that can be considered in NR systems. The various OFDM numerologies supported in NR systems can be defined as shown in Table 1 below.
[0081] μΔf=2 μ ·15 [kHz]CP015 Normal 130 Normal 260 Normal, Extended 3120 Normal 4240 Normal
[0082] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands. When the SCS is 30 kHz / 60 kHz, it supports dense urban areas, lower latency, and wider carrier bandwidth. When the SCS is 60 kHz or higher, it supports a bandwidth larger than 24.25 GHz to overcome phase noise. The NR frequency band is defined by two types of frequency ranges (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. In addition, FR2 can mean millimeter wave (mmW).
[0083] Frequency Range Designation Corresponding Frequency Range Subcarrier Spacing FR1410MHz - 7125MHz 15, 30, 60kHz FR224250MHz - 52600MHz 60, 120, 240kHz
[0084] Regarding the frame structure in the NR system, the sizes of the various fields in the time domain are T c =1 / (Δf max ·N f ) is expressed as a multiple of the time unit. Here, Δf max =480·10 3 Hz and N f =4096. Downlink and uplink transmissions are T f =1 / (Δf max Nf / 100)·T c = It is organized into radio frames with a duration of 10ms. Here, each radio frame is T sf =(Δf max N f / 1000)·T c =1ms It consists of 10 subframes with an interval of . In this case, there may be one set of frames for uplink and one set of frames for downlink. In addition, transmission in uplink frame number i from a terminal is T earlier than the start of the corresponding downlink frame from the terminal. TA =(N TA +N TA,offset )T c It should start before. For the subcarrier spacing configuration μ, slots are n within a subframe. s μ ∈{0,..., N slot subframe,μ-1} are numbered in increasing order, and n within a radio frame. s,f μ ∈{0,..., N slot frame,μ -1} are numbered in increasing order. One slot is N symb slot It consists of consecutive OFDM symbols, and N symb slot is determined by CP. Slot n in subframe s μ The start of OFDM symbol n in the same subframe s μ N symb slotare aligned temporally with the start of the OFDM symbol. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or uplink slot can be used. Table 3 shows the number of OFDM symbols per slot (N) in a general CP. symb slot ), the number of slots per wireless frame (N slot frame,μ ), number of slots per subframe (N slot subframe,μ), and Table 4 shows the number of OFDM symbols per slot in the extended CP, the number of slots per radio frame, and the number of slots per subframe.
[0085] μN symb slot N slot frame,μ N slot subframe,μ01410111420221440431480841416016
[0086] μN symb slot N slot frame,μ N slot subframe,μ212404
[0087] FIG. 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, 1 subframe can include 4 slots. 1 subframe={1,2,4} slots illustrated in FIG. 2 is an example, and the number of slot(s) that can be included in 1 subframe is defined as in Table 3 or Table 4. In addition, a mini-slot can include 2, 4, or 7 symbols, or more or fewer symbols. With respect to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered. Hereinafter, the physical resources that can be considered in an NR system will be described in detail. First, with respect to antenna ports, antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship if the large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on another antenna port is carried. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.
[0088] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.
[0089] Referring to Figure 3, the resource grid is N in the frequency domain. RB μ N sc RB It consists of subcarriers, and one subframe is 14·2 μ It is described as an example, but not limited to, that it consists of OFDM symbols. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids consisting of subcarriers and 2 μ N symb (μ) is described by OFDM symbols. Here, N RB μ≤ N RB max,μ is. The above N RB max,μ represents the maximum transmission bandwidth, which may vary between uplink and downlink as well as between numerologies. In this case, one resource grid may be configured for μ and each antenna port p. Each element of the resource grid for μ and each antenna port p is referred to as a resource element and is uniquely identified by an index pair (k, l'). Here, k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, and l'=0,...,2 μ N symb (μ) -1 indicates the position of the symbol within the subframe. When indicating a resource element in a slot, the index pair (k,l) is used.
[0090] Here, l=0,...,N symb μ-1. The resource element (k,l') for μ and antenna port p is a complex value a k,l' (p,μ) . If there is no risk of confusion or if a particular antenna port or numerology is not specified, the indices p and μ can be dropped, resulting in a complex value of a k,l' (p) or a k,l' This can be. Also, a resource block (RB) is N in the frequency domain. sc RB =12 is defined as consecutive subcarriers.
[0091] Point A serves as a common reference point of the resource block grid and is obtained as follows.
[0092] - offsetToPointA for the Primary Cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the UE for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.
[0093] - absoluteFrequencyPointA represents the frequency-position of point A expressed as ARFCN (absolute radio-frequency channel number).
[0094] Common resource blocks (CRBs) are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of CRB 0 for a subcarrier spacing setting μ coincides with 'point A'. CRB number n in the frequency domain CRB μ The relationship between the resource elements (k,l) and the subcarrier spacing setting μ is given by the following mathematical expression 1.
[0095]
[0096] In Equation 1, k is defined relative to point A such that k = 0 corresponds to the subcarrier centered at point A. Physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). BWP,i size,μ - Numbered from -1, where i is the number of the BWP. Physical resource block n in BWP i PRB and common resource block n CRB The relationship between them is given by the mathematical formula 2 below.
[0097]
[0098] N BWP,i start,μ is a common resource block where BWP starts relative to common resource block 0.
[0099] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.
[0100] Referring to FIGS. 4 and 5, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot includes seven symbols, but in the case of an extended CP, one slot includes six symbols.
[0101] A carrier comprises multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) is defined as multiple consecutive (physical) resource blocks in the frequency domain, and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can comprise up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.
[0102] The NR system can support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, when considering multiple use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band within the CC. Alternatively, each terminal may have different maximum bandwidth capabilities. Considering this, the base station can instruct the terminal to operate only on a portion of the bandwidth rather than the entire bandwidth of the wideband CC, and this portion of bandwidth is conveniently defined as the bandwidth part (BWP). A BWP can be composed of consecutive RBs on the frequency axis and can correspond to a single numerology (e.g., subcarrier spacing, CP length, slot / mini-slot interval).
[0103] Meanwhile, the base station can configure multiple BWPs even within a single CC configured for a terminal. For example, in the PDCCH monitoring slot, a BWP occupying a relatively small frequency range can be configured, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, if UEs are concentrated on a specific BWP, some terminals can be configured to a different BWP for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, a portion of the spectrum in the middle of the entire bandwidth can be excluded and both BWPs can be configured within the same slot. In other words, the base station can configure at least one DL / UL BWP for a terminal associated with a wideband CC. The base station can activate at least one DL / UL BWP(s) among the configured DL / UL BWP(s) at a specific time (via L1 signaling, MAC CE (Control Element), RRC signaling, etc.).
[0104] Additionally, the base station can instruct switching to another configured DL / UL BWP (e.g., via L1 signaling or MAC CE or RRC signaling). Alternatively, switching to a configured DL / UL BWP can be performed based on a timer when the timer value expires. In this case, the activated DL / UL BWP is defined as the active DL / UL BWP. However, in situations such as when the terminal is performing the initial access process or before the RRC connection is set up, the configuration for the DL / UL BWP may not be received. Therefore, in these situations, the DL / UL BWP assumed by the terminal is defined as the initially active DL / UL BWP.
[0105] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.
[0106] In wireless communication systems, terminals receive information from a base station via the downlink and transmit it to the base station via the uplink. The information transmitted and received between the base station and terminals includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.
[0107] When a terminal is powered on or enters a new cell, it performs an initial cell search operation, such as synchronizing with the base station (S601). To this end, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell identifier (ID). Afterwards, the terminal can receive a physical broadcast channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search phase to check the downlink channel status.
[0108] A terminal that has completed initial cell search can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried on the PDCCH (S602).
[0109] Meanwhile, when accessing a base station for the first time or when there are no radio resources for signal transmission, the terminal may perform a random access procedure (RACH) for the base station (steps S603 to S606). To this end, the terminal may transmit a specific sequence as a preamble via the Physical Random Access Channel (PRACH) (steps S603 and S605) and receive a response message to the preamble via the Physical Data Channel Control Channel (PDCCH) and the corresponding PDSCH (steps S604 and S606). In the case of a contention-based RACH, a contention resolution procedure (Contention Resolution Procedure) may additionally be performed.
[0110] The terminal that has performed the procedure described above can then perform PDCCH / PDSCH reception (S607) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S608) as general uplink / downlink signal transmission procedures. In particular, the terminal receives downlink control information (DCI) through the PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on the purpose of use.
[0111] Meanwhile, the control information that the terminal transmits to the base station via the uplink or that the terminal receives from the base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In the case of the 3GPP LTE system, the terminal can transmit the above-described control information such as CQI / PMI / RI via PUSCH and / or PUCCH.
[0112] Table 5 shows an example of the DCI format in the NR system.
[0113] DCI Format Utilization 0_0 Scheduling of PUSCH within a cell 0_1 Scheduling of one or multiple PUSCH within a cell, or indicating cell group (CG: cell group) downlink feedback information to the UE 0_2 Scheduling of PUSCH within a cell 1_0 Scheduling of PDSCH within a DL cell 1_1 Scheduling of PDSCH within a cell 1_2 Scheduling of PDSCH within a cell
[0114] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to scheduling of PUSCH (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid - Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined. DCI format 0_0 is used for scheduling of PUSCH in one cell. Information included in DCI format 0_0 is transmitted with CRC (cyclic redundancy check) scrambled by C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI).
[0115] DCI format 0_1 is used to indicate scheduling of one or more PUSCHs in a single cell, or configure grant (CG: configure grant) downlink feedback information to the UE. The information contained in DCI format 0_1 is CRC-scrambled and transmitted using the C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI.
[0116] DCI format 0_2 is used for scheduling PUSCH in a cell. The information contained in DCI format 0_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.
[0117] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to scheduling of PDSCH (e.g., frequency resource allocation, time resource allocation, virtual resource block (VRB)-physical resource block (PRB) mapping, etc.), transport block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., antenna port, transmission configuration indicator (TCI), sounding reference signal (SRS) request, etc.), PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format may be predefined.
[0118] DCI format 1_0 is used for scheduling PDSCH in a DL cell. The information contained in DCI format 1_0 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.
[0119] DCI format 1_1 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_1 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.
[0120] DCI format 1_2 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.
[0121] (e) Downlink transmission and reception method of RedCap terminal
[0122] As described above, services that consider eMBB, URLLC, and the massive Internet of Things (mIoT) are being provided on wireless communication systems (e.g., NR). For example, hybrid services that consider eMBB, URLLC, and mIoT may also be provided on wireless communication systems. Here, mIoT requires optimization of power consumption rather than high performance (e.g., high transmission speeds) such as carrier aggregation.
[0123] With the recent widespread use of smart factories and / or wearable devices, the need for new terminal types that take low power and URLLC into account is increasing. Accordingly, reduced capability (RedCap) terminals were introduced in 3GPP NR Release 17. RedCap terminals can perform communications using frequency resources in a narrow spectrum or narrow bandwidth. For example, RedCap terminals can reduce power consumption and costs by utilizing up to 20 MHz or 5 MHz of bandwidth instead of the conventional 100 MHz.
[0124] Subsequently, eRedCap terminals were introduced in 3GPP NR Release 18. eRedCap terminals are similar to RedCap terminals in that they operate in a 20 MHz bandwidth. However, in the case of eRedCap terminals, unicast PDSCH and / or PUSCH (i.e., C-RNTI-based PDSCH and / or PUSCH) can be allocated within a bandwidth of up to 5 MHz. That is, a PRB of a unicast PUSCH / PDSCH corresponding to a bandwidth of up to 5 MHz can be allocated to an eRedCap terminal. At this time, the unicast PUSCH / PDSCH can be indicated / allocated to an eRedCap terminal through the FDRA (frequency domain resource assignment) field of the DCI, etc.
[0125] Additionally, for eRedCap terminals, various RNTI-based channels related to paging, system information block (SIB), RACH, etc. can be allocated within a 20 MHz bandwidth. That is, PRBs of various RNTI-based channels corresponding to a maximum bandwidth of 20 MHz can be allocated to eRedCap terminals (same as RedCap terminals).
[0126] Additionally, a PRB for a unicast PDSCH corresponding to a bandwidth of up to 5 MHz per slot can be allocated to an eRedCap terminal. Previously, when multiple unicast PDSCHs were scheduled on the same slot, the behavior of the eRedCap terminal was not clearly defined or configured.
[0127] Below, the operation of an eRedCap terminal when multiple unicast and / or multicast PDSCHs are scheduled for a single slot is specifically described. Furthermore, in the description of the present disclosure, "multicast PxSCH" may be replaced with "MBS PxSCH."
[0128] FIG. 7 is a diagram illustrating a process of a terminal performing communication according to an embodiment of the present disclosure. The terminals of FIGS. 7 and 8 may include enhanced reduced capability (eRedCap) terminals that support scheduling of unicast channels within a 5 MHz bandwidth. However, this is merely an example, and the terminals of FIGS. 7 and 8 may include eRedCap terminals or RedCap terminals that support scheduling of unicast channels within a 20 MHz bandwidth. As another example, the terminals of FIGS. 7 and 8 may also be non-RedCap terminals.
[0129] The terminal can transmit first capability information indicating that it supports reception of a unicast downlink channel and a multicast downlink channel in a single slot to the base station (S710).
[0130] That is, the terminal may transmit to the base station first capability information (e.g., "intraSlotTDM-UnicastGroupCommonPDSCH-r17") indicating that it can receive unicast channels and multicast channels within a single slot.
[0131] Additionally or alternatively, the terminal may transmit to the base station second capability information related to the number of downlink channels that the terminal can process within a single slot (e.g., the total number of unicast downlink channels and / or multicast downlink channels). Additionally or alternatively, the terminal may transmit to the base station information related to the terminal processing capability. However, this is only one embodiment, and the terminal may transmit to the base station various types of capability information described in the embodiments described below.
[0132] The terminal may receive information from the base station for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (where n is a natural number) (S720). That is, the terminal may receive information (e.g., downlink control information, etc.) for scheduling one or more unicast downlink channels and one or more multicast downlink channels on a single slot from the base station.
[0133] Based on the sum of the physical resource blocks (RBs) allocated to each of one or more unicast downlink channels and one or more multicast downlink channels exceeding a threshold, the terminal can decode at least one downlink channel among the one or more unicast downlink channels or the one or more multicast downlink channels (S730).
[0134] At this time, another downlink channel may be scheduled in slot n+1 adjacent to slot n, but is not limited thereto.
[0135] Specifically, the terminal can determine whether the total number of PRBs of each of one or more unicast downlink channels and one or more multicast downlink channels scheduled in slot n exceeds a threshold value based on information received according to step S720.
[0136] At this time, the threshold value can be determined based on the number of RBs of the downlink channel that can be allocated to a 5 MHz bandwidth or the second capability information.
[0137] For example, assume that the threshold is the number of RBs of a downlink channel that can be allocated to a 5 MHz bandwidth. Based on the subcarrier spacing (SCS) being set to 15 kHz, the number of RBs of a downlink channel that can be allocated to a 5 MHz bandwidth can be 25, and based on the SCS being set to 30 kHz, the number of RBs of a downlink channel that can be allocated to a 5 MHz bandwidth can be 12.
[0138] As another example, assume that the threshold is determined based on second capability information. In this case, the threshold may be determined / defined as a value less than or equal to the number of downlink channels that the terminal can process in a single slot.
[0139] The terminal can decode / process PRBs (i.e., PRBs of at least one downlink channel) within a threshold range among PRBs of one or more unicast downlink channels or each of the one or more multicast downlink channels. Here, the sum of RBs of each of the at least one downlink channels on which the terminal performs decoding may be less than or equal to the threshold. In addition, the terminal can drop channels other than at least one downlink channel (i.e., the downlink channel on which decoding is performed) among the at least one unicast downlink channel and the at least one multicast downlink channel.
[0140] For example, the terminal may determine the decoding order based on the order of the starting OFDM (orthogonal frequency division multiplexing) symbol of the at least one downlink channel. For example, among one or more unicast downlink channels and one or more multicast downlink channels, the downlink channel with the earliest starting OFDM symbol (i.e., the smallest starting OFDM symbol index) may be preferentially decoded.
[0141] That is, based on the sum of RBs allocated to each of one or more unicast downlink channels and one or more multicast downlink channels exceeding a threshold, the terminal can perform a decoding operation in the order of downlink channels scheduled first in the time domain among the downlink channels scheduled in slot n.
[0142] Additionally or alternatively, the terminal may determine the decoding order of each of the at least one downlink channel based on the size of the number of RBs of the at least one downlink channel. That is, based on whether the sum of the RBs allocated to each of the at least one unicast downlink channel and the at least one multicast downlink channel exceeds a threshold, the terminal may perform a decoding operation in the order of the downlink channel with the largest number of RBs among the downlink channels scheduled in slot n.
[0143] Additionally or alternatively, the terminal may determine a downlink channel to be dropped based on the order of the starting OFDM symbols of each of the one or more unicast downlink channels and the one or more multicast downlink channels. That is, the terminal may drop the downlink channel(s) from among the one or more unicast downlink channels and the one or more multicast downlink channels in a later scheduled order in the time domain.
[0144] As another example, the terminal may drop one or more unicast downlink channels and one or more multicast downlink channels for which feedback transmission is not configured. In other words, the terminal may drop a downlink channel scheduled in slot n for which feedback transmission is not configured.
[0145] For example, based on the fact that no other downlink channel is scheduled in slot n+1 adjacent to slot n, the terminal can decode both one or more unicast downlink channels and one or more multicast downlink channels.
[0146] The method described in the example of FIG. 7 can be performed by the first device (100) of FIG. 10. That is, the first terminal of FIG. 10 can be implemented as the first device (100). For example, one or more processors (102) of the first device (100) of FIG. 10 can transmit first capability information indicating that it supports reception of a unicast downlink channel and a multicast downlink channel in a single slot to a base station through one or more transceivers (106). The one or more processors (102) can receive information from the base station, through one or more transceivers (106), for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (n is a natural number). Based on the sum of RBs allocated to each of one or more unicast downlink channels and one or more multicast downlink channels exceeding a threshold, one or more processors (102) can decode at least one downlink channel among the one or more unicast downlink channels or the one or more multicast downlink channels.
[0147] Furthermore, one or more memories (104) of the first device (100) may store instructions for performing the method described in the example of FIG. 10 or the examples described below when executed by one or more processors (102).
[0148] FIG. 8 is a diagram for explaining a process in which a base station performs communication according to one embodiment of the present disclosure.
[0149] The base station can receive first capability information from the terminal indicating that it supports reception of a unicast downlink channel and a multicast downlink channel in a single slot (S810).
[0150] The base station can confirm that the terminal supports unicast / multicast reception in a single slot through the first capability information received from the terminal.
[0151] The base station can transmit to the terminal information for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (where n is a natural number) (S820). That is, the base station can confirm that the terminal supports reception of unicast / multicast downlink on a single slot through the first capability information, and transmit to the base station scheduling information for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n.
[0152] If the sum of the PRBs of each of one or more unicast downlink channels and one or more multicast downlink channels scheduled by the base station exceeds a threshold, at least one downlink channel among the one or more unicast downlink channels and the one or more multicast downlink channels may be decoded according to the method described in step S730.
[0153] The method described in the example of FIG. 8 can be performed by the second device (200) of FIG. 10. That is, the base station of FIG. 10 can be implemented as the second device (200). For example, one or more processors (202) of the second device (200) of FIG. 10 can receive first capability information indicating that reception of a unicast downlink channel and a multicast downlink channel is supported in a single slot from a terminal through one or more transceivers (206). The one or more processors (202) can transmit information for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (where n is a natural number) to the terminal through one or more transceivers (206).
[0154] Furthermore, one or more memories (204) of the second device (200) may store commands for performing the method described in the example of FIG. 8 or the examples described below when executed by one or more processors (202).
[0155] Hereinafter, the operation of an eRedCap terminal when multiple unicast or / and multicast PDSCHs are scheduled for each single slot will be specifically described with reference to FIGS. 7 and 8.
[0156] For RedCap terminals (i.e., RedCap terminals introduced in 3GPP Release 17), unicast channels can be scheduled on a bandwidth of up to 20 MHz, at which time the maximum data rate (date rate) can be 500 Mbps. For eRedCap terminals (i.e., RedCap terminals introduced in 3GPP Release 18), unicast channels can be scheduled on a bandwidth of up to 20 MHz or 5 MHz, at which time the maximum data rate (date rate) can be 10 Mbps.
[0157] As an example of the present disclosure, an eRedCap terminal can process data (e.g., PRB) corresponding to a bandwidth of up to 5 MHz within a unit slot. If a channel exceeding 5 MHz of bandwidth is scheduled / allocated, the eRedCap terminal may require additional processing time margin. In the case of a unicast channel, scheduling may be performed for each slot, and thus, a PRB corresponding to the maximum bandwidth (e.g., 5 MHz) may be allocated to the eRedCap terminal (e.g., 25 PRBs when the SCS is 15 kHz or 12 PRBs when the SCS is 30 kHz). If multiple unicast / multicast PDSCHs are scheduled within a single slot, the operation method of the eRedCap terminal needs to be defined / configured / instructed.
[0158] Meanwhile, an eRedCap terminal may report to the base station as capability information the maximum number of unicast PDSCHs (i.e., PDSCHs carrying one or more TBs) it supports per slot. For example, an eRedCap terminal may transmit to the base station UE capability information (e.g., "pdsch-ProcessingType1-DifferentTB-PerSlot") that defines / indicates whether the terminal, capable of processing time capability 1, supports reception of up to 2, 4, or 7 unicast PDSCHs for multiple transport blocks with scrambled PDSCHs using C-RNTI, TC-RNTI, MCS-C-RNTI, or CS-RNTI in one serving cell within the same slot per component carrier (CC) multiplexed only in the time domain. For example, an eRedCap terminal may report to the base station as UE capability information that it supports 2, 4, or 7 unicast PDSCHs per SCS (e.g., per SCS 15 / 30 / 60 / 120 kHz).
[0159] The above-described method can also be applied to CBG (code block group) or processing type 2. For example, an eRedCap terminal can transmit UE capability information (e.g., "pdsch-ProcessingType2") to a base station, indicating whether it supports PDSCH processing capability 2. The UE capability information can indicate whether the terminal supports PDSCH processing capability 2. The terminal can support this only if all serving cells are self-scheduled and all serving cells in the same band configured in the network for processing type 2 use the same subcarrier spacing. The terminal capability information can include the following parameters for each subcarrier spacing supported by the terminal.
[0160] - If "fallback" = 'sc', the terminal supports capability 2 processing time for the lowest cell index among the carriers set in the band for which the value is reported, and if fallback = 'cap1-only', the terminal can support only capability 1 in the band for which the value is reported.
[0161] - "DifferentTB-PerSlot" may indicate whether the UE supports processing type 2 for 1, 2, 4 and / or 7 unicast PDSCHs for different transport blocks per slot per CC. If so, the UE may indicate the number of CA serving cells that support that number of unicast PDSCHs for different TBs. If "pdsch-ProcessingType2" is indicated, the UE may include at least one of the information about the number of carriers for 1, 2, 4 or 7 transport blocks per slot in that field (i.e., "numberOfCarriers").
[0162] For example, assume that a terminal transmits terminal capability information to the base station indicating that it can process up to 7 unicast PDSCHs within a single slot. At this time, the base station may assume that a PRB corresponding to a bandwidth of up to 5 MHz per unicast PDSCH can be processed by the terminal, and may transmit PDCCH(s) for scheduling at least one unicast PDSCH to the terminal. Accordingly, the terminal can process up to 25 PRBs (e.g., when the SCS is 15 kHz) or up to 12 PRBs (e.g., when the SCS is 30 kHz) per unit slot. In the following, the operation of an eRedCap terminal when multiple unicasts are allocated to a unit slot will be described.
[0163] In describing the present disclosure, an eRedCap terminal supporting a unicast PDSCH scheduled on a bandwidth of up to 5 MHz is referred to as feature-1, and an eRedCap terminal supporting a unicast PDSCH scheduled on a bandwidth of up to 20 MHz is referred to as feature-2. In addition, the operations of various embodiments of the present disclosure can be equally applied to PUSCH transmission and reception. That is, "PDSCH" in various embodiments of the present disclosure can be replaced with "PUSCH."
[0164] Example 1
[0165] Embodiment 1 relates to a method for limiting multiple PxSCHs (x is U or D) for a specific feature of an eRedCap terminal. For example, for feature 1, the number of PxSCHs that can be processed in one slot may be limited, or transmission of terminal capability information (e.g., capability information related to terminal processing type 1 / 2, etc.) may be limited.
[0166] Example 1-1
[0167] In one embodiment of the present disclosure, for feature 1, the use of terminal capability parameters associated with terminal processing type 1 may be restricted. For example, feature 1 may be restricted to use only one unicast PDSCH in a single slot. In another example, feature 1 may be restricted to use only 2, 4, or 7 or fewer PDSCHs in a single slot.
[0168] Example 1-2
[0169] In one embodiment of the present disclosure, for feature 2, the use of terminal capability parameters associated with terminal processing type 1 may be restricted. For example, feature 2 may be restricted to use only one unicast PDSCH in a single slot. In another example, feature 2 may be restricted to use only 2, 4, or 7 or fewer PDSCHs in a single slot.
[0170] Example 1-3
[0171] In one embodiment of the present disclosure, for feature-1, use of capability information related to terminal processing types 1 and 2 for CBG may be restricted. Here, the capability information related to terminal processing types 1 and 2 for CBG may include i) information indicating whether a terminal capable of processing time capabilities 1 or / and 2 supports CBG-based reception using at most 1, at most 2, at most 4, or at most 7 unicast PDSCHs per slot per CC, and ii) information indicating whether a terminal capable of processing time capabilities 1 or / and 2 supports CBG-based reception using at most 1, at most 2, at most 4, or at most 7 unicast PUSCHs per slot per CC.
[0172] For example, the use of CBG of feature-1 may be restricted. As another example, feature-1 / 2 may be restricted to use only PDSCH / PUSCH of no more than 2, 4, or 7 in one slot.
[0173] Example 1-4
[0174] In another embodiment of the present disclosure, RRC parameters related to each of Embodiments 1-1, 1-2, and 1-3 may be defined, and the number of PDSCHs / PUSCHs that a terminal can process in a single slot may be set / indicated / defined / reported through the RRC parameters. In addition, the above-described examples may also be applied to CBG. In this case, the terminal capability parameters defined in Embodiments 1-1, 1-2, and 1-3 may not be used.
[0175] For example, an RRC parameter may be defined that sets the number of PDSCHs / PUSCHs that a terminal can process in a single slot. For example, a candidate for the number of PDSCHs / PUSCHs that a terminal can process in a single slot may be transmitted to the terminal through the RRC parameter, and the terminal may select and report one of the candidates for the corresponding number of PDSCHs / PUSCHs. In another example, multiple candidates for the number of PDSCHs / PUSCHs may be defined, and the terminal may select and report one of the candidates for the corresponding number of PDSCHs / PUSCHs.
[0176] For example, if an RRC parameter that sets the number of PDSCHs / PUSCHs that a terminal can process in a single slot is not newly defined, the terminal can use the terminal capability parameters defined in Embodiments 1-1, 1-2, and 1-3.
[0177] As another example, if multiple parameters that set the number of PDSCHs / PUSCHs that a terminal can process in a single slot are reported simultaneously, the base station can identify the value indicated by the newly defined parameters as the number of PDSCHs / PUSCHs that a terminal can process in a single slot.
[0178] Example 2
[0179] Embodiment 2 relates to a method for limiting the number of PRBs of multiple unicast PxSCHs (x is U or D) allocated on a single slot to be within a specific number, in the case of a specific feature of an eRedCap terminal. That is, Embodiment 2 can be applied to feature-1 or / and feature-2.
[0180] Embodiment 1 relates to a method for reducing the number of unicast PxSCHs that a terminal can process per slot in a situation where PRBs of unicast PxSCHs can be allocated at most X (e.g., 25 when SCS is 15 kHz or 12 when SCS is 30 kHz). However, Embodiment 2 relates to a method for a terminal to process PRBs of unicast(s) of N or less in a case where the number of PRBs of unicast PxSCHs that a terminal can process within a single slot is N or less.
[0181] For example, the maximum number of PRBs of a single unicast PxSCH that can be allocated within a single slot (in the case of Specific-1) may be 25 (if the SCS is 15 kHz) or 12 (if the SCS is 30 kHz). Here, if two or more unicast channels are allocated / scheduled, the UE can only process up to N PRBs within a single slot. Therefore, the base station can schedule so that the total sum of PRBs of multiple unicast PxSCHs within a unit slot is N or less.
[0182] For example, if a specific number or more of PRBs (i.e., PRBs of multiple unicast PDSCHs) are scheduled / allocated within a single slot, the terminal can decode the PRBs of the unicast PDSCHs in the order in which they were scheduled / received. In this case, the number of PRBs of the unicast PDSCHs that the terminal decodes may be N or less (or less than a specific number).
[0183] Example 2-1
[0184] In one embodiment of the present disclosure, N may be set / defined / indicated differently depending on the SCS. As another example, the value of N may be predefined. The value of N may be set / defined / indicated to a value less than the number of PRBs corresponding to the BWP (i.e., the maximum number of PRBs that can be set / allocated to the BWP).
[0185] Additionally or alternatively, the terminal may transmit the N value supported by the terminal to the base station via terminal capability information. The base station may schedule multiple PDSCHs based on the terminal capability information, and the number of PRBs of the multiple PDSCHs allocated within a unit slot may be N or less.
[0186] Example 2-2
[0187] In one embodiment of the present disclosure, when the value of N is not separately set / defined / indicated, the number of PRBs of a single unicast PxSCH that a terminal can process within a single slot may be defined as 25 (e.g., SCS is 15 kHz) or 12 (e.g., SCS is 30 kHz).
[0188] Example 2-3
[0189] As an example of the present disclosure, the number of PRBs that a terminal can process within a single slot may be set / defined / indicated based on the number of multiple unicast PxSCHs. In this case, the number of PRBs that the terminal can process within a single slot may be set as a multiple of a specific value (i.e., the M value). For example, the number of PRBs that the terminal can process within a single slot may be set / defined / indicated as "M * the maximum number of unicast PxSCHs that the terminal supports within a single slot."
[0190] At this time, the number of FDM-based multiple PDSCHs that can be supported within a single slot can be newly defined. The M value can be set / indicated by higher layer signaling (e.g., RRC, MAC CE, etc.) or predefined.
[0191] For example, assume that the M value is 10 and the maximum number of supportable unicast PDSCHs reported by the terminal in the terminal capability information (i.e., information on the maximum number of PDSCHs that the terminal can support per unit slot) is 4. In this case, the maximum number of PRBs of multiple PDSCHs that the terminal can process within a single slot may be 40. If more than 40 PRBs are allocated / scheduled within a single slot, the terminal may set / process the HARQ feedback of all PDSCHs to DTX (Discontinuous Transmission) or NACK (negative acknowledgment).
[0192] Example 2-4
[0193] As an example of the present disclosure, the number of PRBs that a terminal can process within a single slot can be dynamically set / defined / indicated based on the number of multiple unicast PxSCHs. In this case, the number of PRBs that the terminal can process within a single slot can be set to a multiple of a specific value (i.e., the M value). For example, the number of PRBs that the terminal can process within a single slot can be set / defined / indicated as "M * the number of PxSCHs scheduled for the corresponding slot."
[0194] At this time, the number of FDM-based multiple PDSCHs that can be supported within a single slot can be newly defined. The M value can be set / indicated by higher layer signaling (e.g., RRC, MAC CE, etc.) or predefined.
[0195] For example, assume that the M value is 10 and the maximum number of currently scheduled unicast PDSCHs (within a single / specific slot) is 4. In this case, the maximum number of PRBs of multiple PDSCHs that the UE can process within a single slot may be 40. That is, the UE can process PRBs of multiple unicast PDSCHs within 40 PRBs. If more than 40 PRBs are allocated / scheduled within a single slot, the UE may set / process the HARQ feedback of all PDSCHs to DTX (Discontinuous Transmission) or NACK (negative acknowledgment).
[0196] Example 2-5
[0197] Embodiment 2-5 relates to a case where multiple PxSCHs scheduled / allocated within a single slot include unicast PxSCHs and multicast (or multicast broadcast service (MBS) or / and group-common) PxSCHs (e.g., x is U or D). That is, Embodiment 2-5 relates to a case where unicast PxSCHs and multicast PxSCHs are scheduled / allocated within the same slot.
[0198] A terminal may transmit / report terminal capability information to a base station, indicating whether it supports unicast PxSCH and multicast PxSCH within the same slot. For example, the terminal capability information (e.g., "intraSlotTDM-UnicastGroupCommonPDSCH-r17") transmitted / reported by the terminal to the base station may indicate whether the terminal supports intra-slot TDM unicast PDSCH and group common PDSCH.
[0199] If there is more than one broadcast / multicast / unicast PDSCH in each slot, the value of the terminal capability information may indicate whether a minimum time separation (e.g., 4 OFDM symbols for 30 kHz, 7 OFDM symbols for 60 kHz) is required between the start times of any two broadcast / multicast / unicast PDSCHs within the duration of the slot for any two consecutive slots n and n+1.
[0200] For example, the UE capability information may indicate i) support of TDM between one unicast PDSCH and one group common PDSCH in a slot, ii) support of TDM between M (M>1) TDMed unicast PDSCHs and one group common PDSCH in a slot per CC, iii) support of TDM between N (N>1) group common PDSCHs in a slot per CC, iv) support of TDM between K (K>1) TDMed unicast PDSCHs and L (L>1) TDMed group common PDSCHs in a slot per CC, etc. In addition, the UE maximum number of TDMed PDSCH reception capabilities in a slot per CC may be maintained based on UE capability information (e.g., "pdsch-ProcessingType1-DifferentTB-PerSlot") that defines / indicates whether reception of up to 2, 4, or 7 unicast PDSCHs for multiple transport blocks with PDSCHs is supported. Additionally, one slot can support at most one broadcast PDSCH.
[0201] As an example of the present disclosure, a terminal may be restricted to process a PRB only when the sum of the number of PRBs of each of a multicast PDSCH and a unicast PDSCH that can be processed within one slot is less than or equal to a specific value. In this case, the specific value may be set / defined as the number of PRBs corresponding to a 5 MHz bandwidth (i.e., 25 (e.g., SCS is 15 kHz) or 12 (e.g., SCS is 30 kHz)), but is not limited thereto. In addition, the multicast PDSCH may be restricted to a PDSCH on which HARQ-based ACK / NACK feedback is transmitted.
[0202] As an example of the present disclosure, it is assumed that an eRedCap terminal can simultaneously process TDM-enabled multicast PDSCHs and unicast PDSCHs within a single slot. For example, the eRedCap terminal can transmit capability information to a base station indicating that it can simultaneously process TDM-enabled multicast PDSCHs and unicast PDSCHs within a single slot. Here, if the total number of PRBs of TDM-enabled MBS PDSCHs and unicast PDSCHs within a single slot is less than a specific value, the eRedCap terminal can process the corresponding PDSCHs.
[0203] Here, the specific value may be separately set or predefined by the base station through higher-layer signaling. As another example, if the specific value is not predefined, the specific value may be defined as the number of PRBs corresponding to a 5 MHz bandwidth.
[0204] At this time, the feedback mode for the multicast PDSCH can be set to ACK / NACK mode or NACK-only mode. Here, the NACK-only mode can be a general term for a mode in which the terminal transmits NACK information as feedback when the multicast PDSCH is not received, and does not transmit feedback when the multicast PDSCH is received.
[0205] For example, multicast PDSCH and / or unicast PDSCH may be limited to be scheduled within a single slot by a number of PRBs corresponding to 5 MHz or less. In addition, if the total number of PRBs allocated to unicast PDSCH and multicast PDSCH scheduled within a single slot exceeds a certain value, the eRedCap terminal may transmit ACK / NACK or DTX for the corresponding PDSCHs.
[0206] Example 3
[0207] Example 3 relates to a method for limiting the sum of PRBs of multiple unicast PxSCHs (x is U or D) on overlapping OFDM symbols to be within a specific value for a specific feature of an eRedCap terminal.
[0208] Embodiment 2 relates to a method for limiting the number of PRBs allocated to PxSCHs scheduled within one slot. Embodiment 3 relates to a method for limiting the allocation of PRBs lower than a specific K value within one slot (i.e., PRBs lower than a specific K value among PRBs allocated to the multiple PxSCHs) when multiple FDM-enabled PxSCHs within one slot overlap in the time domain (i.e., overlap on one or more OFDM symbols). Additionally or alternatively, when multiple FDM-enabled PxSCHs within one slot overlap in the time domain, an eRedCap terminal may process PRBs lower than a specific K value among PRBs allocated to the multiple PxSCHs scheduled within one slot.
[0209] Example 3-1
[0210] In one embodiment of the present disclosure, the value of K may be set / defined / indicated differently depending on the SCS. As another example, the value of K may be predefined. The value of K may be set / defined / indicated to a value less than the number of PRBs corresponding to the BWP (i.e., the maximum number of PRBs that can be set / allocated to the BWP).
[0211] Additionally or alternatively, the terminal may transmit the K value supported by the terminal to the base station via terminal capability information. The base station may schedule multiple PDSCHs (e.g., PDSCHs overlapping and FDMed in the time domain) based on the terminal capability information, and the number of PRBs of the multiple PDSCHs allocated within a unit slot may be K or less.
[0212] Example 3-2
[0213] In one embodiment of the present disclosure, when the K value is not separately set / defined / indicated, the number of PRBs of a single unicast PxSCH that a terminal can process within a single slot may be defined as 25 (e.g., SCS is 15 kHz) or 12 (e.g., SCS is 30 kHz).
[0214] Example 3-3
[0215] As an example of the present disclosure, the number of PRBs that a terminal can process within a single slot can be set / defined / indicated based on the number of multiple unicast PxSCHs. In this case, the number of PRBs that the terminal can process within a single slot can be set as a multiple of a specific value (i.e., the L value). For example, the number of PRBs that the terminal can process within a single slot can be set / defined / indicated as "L * the maximum number of unicast PxSCHs that the terminal supports within a single slot."
[0216] At this time, the number of FDM-based multiple PDSCHs that can be supported within a single slot can be newly defined. The L value can be set / indicated by higher layer signaling (e.g., RRC, MAC CE, etc.) or predefined.
[0217] For example, assume that the L value is 10 and the maximum number of supportable unicast PDSCHs reported by the terminal in the terminal capability information (i.e., information on the maximum number of PDSCHs that the terminal can support per unit slot) is 4. In this case, the maximum number of PRBs of multiple PDSCHs that the terminal can process within a single slot may be 40. If more than 40 PRBs are allocated / scheduled within a single slot, the terminal may set / process the HARQ feedback of all PDSCHs to DTX or NACK.
[0218] Example 3-4
[0219] As an example of the present disclosure, the number of PRBs that a terminal can process within a single slot can be dynamically set / defined / indicated based on the number of multiple unicast PxSCHs. In this case, the number of PRBs that the terminal can process within a single slot can be set to a multiple of a specific value (i.e., the L value). For example, the number of PRBs that the terminal can process within a single slot can be set / defined / indicated as "L * the number of PxSCHs scheduled for the corresponding slot."
[0220] At this time, the number of FDM-based multiple PDSCHs that can be supported within a single slot can be newly defined. The L value can be set / indicated by higher layer signaling (e.g., RRC, MAC CE, etc.) or predefined.
[0221] For example, assume that the L value is 10 and the maximum number of currently scheduled unicast PDSCHs (within a single / specific slot) is 4. In this case, the maximum number of PRBs of multiple PDSCHs that the UE can process within a single slot may be 40. That is, the UE can process PRBs of multiple unicast PDSCHs within 40 PRBs. If more than 40 PRBs are allocated / scheduled within a single slot, the UE may set / process the HARQ feedback of all PDSCHs to DTX or NACK.
[0222] Example 4
[0223] Example 4 relates to various ways of handling unicast / multicast PxSCH (where x is D or U) scheduled in a single slot.
[0224] Example 4-1
[0225] The method applied to multiple unicast PxSCHs scheduled / allocated to a single slot described in Embodiments 1, 2 and 3 can be applied to i) cases where multiple multicast PxSCHs are scheduled to a single slot and ii) cases where multiple multicasts and PxSCHs are applied to a single slot. If the feedback mode associated with the multicast PxSCH is a HARQ-based ACK / NACK mode or a Nack-only mode, the method described above can be applied to the multicast PxSCH.
[0226] For example, assume that a terminal can process up to seven PDSCHs in a specific slot, and that four unicast PDSCHs and three multicast PDSCHs are scheduled in the specific slot. In this case, the terminal can decode a total of seven multicast / unicast PDSCHs scheduled within the specific slot.
[0227] As another example of the present disclosure, for an eRedCap terminal, only one unicast PDSCH may be allocated to a single slot. That is, the base station may transmit information to the eRedCap terminal to schedule only one unicast PDSCH on a single slot, and the unicast PDSCH may be in an FDM or TDM relationship with another PDSCH (e.g., a multicast / broadcast PDSCH).
[0228] Example 4-2
[0229] For eRedCap terminals that support only unicast PDSCHs on a 5 MHz bandwidth, only one unicast PDSCH can be supported within a slot. In this case, multicast PDSCHs may also be restricted from being allocated to slots where unicast PDSCHs are scheduled. Furthermore, the feedback mode of the PDSCH may be either ACK / NACK mode or NACK-only mode.
[0230] At this time, the operations applied to unicast PDSCH and multicast PDSCH can also be applied to broadcast PDSCH, MSG (message) 2 (e.g., random access response corresponding to PRACH preamble) or MSG B (e.g., response message to MSG A) transmitted and received in a random access procedure.
[0231] Example 4-3
[0232] The method applied to multiple unicast PxSCHs scheduled / allocated to a single slot described in Embodiments 1, 2 and 3 can also be applied to PRACH transmission and reception operations. For example, the unicast or / and multicast PxSCHs in Embodiments 1, 2 and 3 can be replaced with PDSCHs or PUSCHs associated with a random access procedure. That is, the number of PDSCHs or PUSCHs associated with a random access procedure scheduled to a single slot may be limited so as not to exceed a certain number.
[0233] Example 5
[0234] Example 5 relates to a processing method when multiple unicast PDSCHs are scheduled within one slot.
[0235] An eRedCap terminal can process PRBs corresponding to a 5 MHz bandwidth in a single slot, and the number of PRBs corresponding to a 5 MHz bandwidth can be 25 (e.g., SCS is 15 kHz) or 12 (e.g., SCS is 30 kHz).
[0236] If the number of PRBs allocated to a single slot exceeds the number of PRBs corresponding to a 5 MHz bandwidth, additional processing time may be required for the single slot. For example, as illustrated in FIG. 9, if another PDSCH is scheduled on slot n+1, only PRBs corresponding to a 5 MHz bandwidth among the total PRBs can be processed in slot n. Hereinafter, a method for an eRedCap terminal to process or drop a unicast PDSCH in slot n will be described when the number of PRBs of multiple PDSCHs allocated to a single slot exceeds the number of PRBs corresponding to a 5 MHz bandwidth.
[0237] Example 5-1
[0238] In one embodiment of the present disclosure, the eRedCap terminal can drop the unicast PDSCH with the lowest time domain (i.e., OFDM symbol basis) among the plurality of unicast PDSCHs allocated to slot n. That is, the eRedCap terminal can process the PDSCH with the fastest time domain (i.e., OFDM symbol basis) and process the unicast PDSCH within a range that does not exceed the number of PRBs corresponding to a 5 MHz bandwidth.
[0239] Additionally, assume that multiple unicast PDSCHs (having a TDM relationship) are scheduled consecutively. As described above, the eRedCap terminal can process the earliest PDSCH in the time domain (i.e., based on the OFDM symbol). At this time, if the sum of the PRBs of the unicast PDSCH previously processed by the eRedCap terminal and the PRBs corresponding to a specific unicast PDSCH (i.e., a unicast PDSCH to be processed by the eRedCap terminal in the RHE) exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal can drop the specific PDSCH. In addition, if the sum of the PRBs of the unicast PDSCH previously processed by the eRedCap terminal and the PRBs corresponding to the PDSCH following the dropped PDSCH exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal can process the PDSCH following the dropped PDSCH.
[0240] That is, the eRedCap terminal can process unicast PDSCHs in the order of OFDM symbol start. In addition, if the sum of the PRBs of the processed unicast PDSCHs and the PRBs of a specific PDSCH that is fastest in the time domain among the unicast PDSCHs to be processed exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal can drop the specific PDSCH.
[0241] Example 5-2
[0242] In one embodiment of the present disclosure, if the number of PRBs of multiple PDSCHs allocated to a single slot (e.g., slot n) exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may drop unicast PDSCHs without HARQ feedback among the multiple PDSCHs. That is, the eRedCap terminal may preferentially process PDSCHs with HARQ feedback configured.
[0243] Example 5-3
[0244] In one embodiment of the present disclosure, when the number of PRBs of multiple PDSCHs allocated to a single slot (e.g., slot n) exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may process a unicast PDSCH with a smaller number of PRBs among the multiple PDSCHs or a unicast PDSCH with a larger number of PRBs among the multiple PDSCHs. That is, the eRedCap terminal may identify a PDSCH to be processed with priority among the multiple PDSCHs based on the number of PRBs, and may process at least one PDSCH within the range of the number of PRBs corresponding to a 5 MHz bandwidth.
[0245] For example, if there are PDSCHs among multiple PDSCHs having the same number of PRBs, the eRedCap terminal can first process a fast unicast PDSCH among the PDSCHs based on the time domain (i.e., based on the OFDM symbol).
[0246] Example 5-4
[0247] In one embodiment of the present disclosure, when the number of PRBs of multiple PDSCHs allocated to a single slot (e.g., slot n) exceeds the number of PRBs corresponding to a 5 MHz bandwidth, the eRedCap terminal may not decode all of the corresponding PDSCHs or may drop them.
[0248] As another example, the terminal may not expect PRBs to be allocated / scheduled in excess of the number of PRBs corresponding to a 5 MHz bandwidth in a single slot. That is, the base station may identify that the eRedCap terminal can process PRBs corresponding to a 5 MHz bandwidth in a single slot based on terminal capability information transmitted by the terminal or based on predefined terminal capabilities. Accordingly, the base station may not allocate PRBs in excess of the number of PRBs corresponding to a 5 MHz bandwidth in a single slot (e.g., slot n). Embodiment 5-4 may be applied regardless of whether another PDSCH is allocated to slot n+1. As another example, Embodiment 5-4 may be applied when another PDSCH is allocated to slot n+1.
[0249] Example 5-5
[0250] In one embodiment of the present disclosure, if the number of PRBs of multiple PDSCHs allocated to slot n exceeds the number of PRBs corresponding to a 5 MHz bandwidth, and no PDSCH is scheduled / allocated in slot n+1, the eRedCap terminal can process all of the multiple PDSCHs. For example, the eRedCap terminal can process multiple PDSCHs across slot n and slot n+1, but is not limited thereto.
[0251] Embodiments 5-1, 5-2, 5-3, 5-4, and 5-5 can be applied regardless of whether PDSCH is scheduled / allocated in slot n+1. However, this is only an embodiment, and Embodiments 5-1, 5-2, 5-3, 5-4, and 5-5 can be applied only when PDSCH is scheduled / allocated in slot n+1.
[0252] And, in Examples 5-1, 5-2, 5-3, 5-4 and 5-5, “unicast PDSCH” may be replaced with “multicast PDSCH” or / and “broadcast PDSCH”.
[0253] In addition, the eRedCap terminal can transmit a NACK for unicast PDSCH(s) requesting HARQ feedback among the PDSCH(s) dropped in Examples 5-1, 5-2, 5-3, 5-4, and 5-5 (i.e., PDSCHs that were not decoded) to the base station.
[0254] The above-described embodiments 1, 2, 3, 4, and 5 and their detailed embodiments can be executed / performed independently, but are not limited thereto. The embodiments 1, 2, 3, 4, and 5 and their detailed embodiments can also be executed / performed in combination with each other.
[0255] Through the various embodiments described above, when multiple PDSCHs are scheduled on one slot, the eRedCap terminal can efficiently perform decoding for at least one PDSCH within the capability range.
[0256] General devices to which the present disclosure may be applied
[0257] FIG. 10 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.
[0258] Referring to FIG. 10, the first device (100) and the second device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR).
[0259] A first device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure.
[0260] For example, the processor (102) may process information in the memory (104) to generate first information / signal and then transmit a wireless signal including the first information / signal through the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal through the transceiver (106) and then store information obtained from signal processing of the second information / signal in the memory (104).
[0261] The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.
[0262] The second device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.
[0263] Hereinafter, the hardware elements of the device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in the present disclosure.
[0264] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.
[0265] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.
[0266] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of the present disclosure, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208). In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.
[0267] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.
[0268] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.
[0269] The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on / in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and can include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory optionally includes one or more storage devices remotely located from the processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and / or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.
[0270] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.
[0271] The method proposed in this disclosure is explained with a focus on examples applied to 3GPP LTE / LTE-A and 5G systems, but can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.
Claims
1. A method performed by a terminal in a wireless communication system, the method comprising: A step of transmitting first capability information indicating that reception of a unicast downlink channel and a multicast downlink channel is supported in a single slot to a base station; A step of receiving information from the base station for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (n is a natural number); and A method comprising the step of decoding at least one downlink channel among the one or more unicast downlink channels or the one or more multicast downlink channels based on a total sum of physical resource blocks (RBs) allocated to each of the one or more unicast downlink channels and the one or more multicast downlink channels exceeding a threshold.
2. In paragraph 1, A method in which the above threshold is determined based on second capability information related to the number of RBs of downlink channels that can be allocated to a 5 MHz bandwidth or the number of downlink channels that the terminal can process in a single slot.
3. In paragraph 2, Based on the subcarrier spacing (SCS) being set to 15 kHz, the number of RBs of the downlink channel that can be allocated to the 5 MHz bandwidth is 25. Method wherein the number of RBs of downlink channels that can be allocated to the 5 MHz bandwidth is 12, based on the SCS being set to 30 kHz.
4. In paragraph 1, A method in which the decoding order of each of the at least one downlink channel is determined according to the order of the starting OFDM (orthogonal frequency division multiplexing) symbol of the at least one downlink channel.
5. In paragraph 1, A method in which a downlink channel to be dropped is determined according to the order of the start OFDM symbol of each of the one or more unicast channels and the one or more multicast channels.
6. In paragraph 1, A method in which the decoding order of each of the at least one downlink channel is determined according to the size of the number of RBs of the at least one downlink channel.
7. In paragraph 1, A method in which a downlink channel for which feedback transmission is not set among the at least one unicast downlink channel and the at least one multicast downlink channel is dropped by the terminal.
8. In paragraph 1, The sum of the RBs of each of the at least one downlink channels is less than or equal to the threshold, A method in which the remaining channels, excluding the at least one downlink channel among the at least one unicast downlink channel and the at least one multicast downlink channel, are dropped by the terminal.
9. In paragraph 1, A method in which another downlink channel is scheduled in slot n+1 adjacent to the above slot n.
10. In paragraph 1, A method in which both the one or more unicast downlink channels and the one or more multicast downlink channels are decoded by the terminal based on the fact that no other downlink channel is scheduled in slot n+1 adjacent to the slot n.
11. In paragraph 1, A method wherein the terminal is an enhanced reduced capability (eRedCap) terminal that supports scheduling of a unicast channel within a 5 MHz bandwidth.
12. In paragraph 1, A method wherein the downlink channel includes a physical downlink shared channel (PDSCH).
13. In a terminal performing communication in a wireless communication system, the terminal: one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting first capability information to a base station via the one or more transceivers, the first capability information indicating that reception of a unicast downlink channel and a multicast downlink channel is supported in a single slot; Receiving information for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (n is a natural number) from the base station through the one or more transceivers; and A terminal configured to decode at least one downlink channel among the one or more unicast downlink channels or the one or more multicast downlink channels based on a total sum of physical resource blocks (RBs) allocated to each of the one or more unicast downlink channels and the one or more multicast downlink channels exceeding a threshold.
14. A method performed by a base station in a wireless communication system, the method comprising: A step of receiving first capability information from a terminal indicating that reception of a unicast downlink channel and a multicast downlink channel is supported in a single slot; and A step of transmitting information for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (n is a natural number) to the terminal, A method in which at least one downlink channel among the one or more unicast downlink channels or the one or more multicast downlink channels is decoded by the terminal based on the sum of physical resource blocks (RBs) allocated to each of the one or more unicast downlink channels and the one or more multicast downlink channels exceeding a threshold.
15. In a base station performing communication in a wireless communication system, the base station: one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receiving first capability information from a terminal through one or more transceivers, the first capability information indicating that reception of a unicast downlink channel and a multicast downlink channel is supported in a single slot; Information for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (n is a natural number) is set to be transmitted to the terminal through the one or more transceivers, A base station, wherein at least one downlink channel among the one or more unicast downlink channels or the one or more multicast downlink channels is decoded by the terminal based on the sum of physical resource blocks (RBs) allocated to each of the one or more unicast downlink channels and the one or more multicast downlink channels exceeding a threshold.
16. In a processing device configured to control a terminal to perform communication in a wireless communication system, the processing device: one or more processors; and One or more computer memories operatively connected to said one or more processors and storing instructions that perform operations based on execution by said one or more processors, The above actions are: An operation of transmitting first capability information to a base station indicating that reception of a unicast downlink channel and a multicast downlink channel is supported in a single slot; An operation of receiving information from the base station for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (where n is a natural number); and A processing device comprising an operation of decoding at least one downlink channel among the one or more unicast downlink channels or the one or more multicast downlink channels based on a sum of physical resource blocks (RBs) allocated to each of the one or more unicast downlink channels and the one or more multicast downlink channels exceeding a threshold.
17. One or more non-transitory computer-readable media storing one or more instructions, The above one or more commands are executed by one or more processors, and the device performs communication in a wireless communication system: Transmitting first capability information to a base station indicating that reception of a unicast downlink channel and a multicast downlink channel is supported in a single slot; Receive information from the base station for scheduling one or more unicast downlink channels and one or more multicast downlink channels on slot n (where n is a natural number); and A computer-readable medium controlled to decode at least one downlink channel among the one or more unicast downlink channels or the one or more multicast downlink channels based on whether the sum of physical resource blocks (RBs) allocated to each of the one or more unicast downlink channels and the one or more multicast downlink channels exceeds a threshold.
Citation Information
Patent Citations
Apparatus and method performed by the same in wireless communication system
US20220322313A1
System and method for resource block determination for mulitcast and broadcast transmissions
US20230083445A1
Method and apparatus for receiving pdsch, and processor-readable storage medium
WO2022148184A1
