Patent Application
20250023669
The present disclosure relates to a wireless communication system, and in more detail, relates to a method and an apparatus of transmitting and receiving uplink control information in a wireless communication system.
A mobile communication system has been developed to provide a voice service while guaranteeing mobility of users. However, a mobile communication system has extended even to a data service as well as a voice service, and currently, an explosive traffic increase has caused shortage of resources and users have demanded a faster service, so a more advanced mobile communication system has been required.
The requirements of a next-generation mobile communication system at large should be able to support accommodation of explosive data traffic, a remarkable increase in a transmission rate per user, accommodation of the significantly increased number of connected devices, very low End-to-End latency and high energy efficiency. To this end, a variety of technologies such as Dual Connectivity, Massive Multiple Input Multiple Output (Massive MIMO), In-band Full Duplex, Non-Orthogonal Multiple Access (NOMA), Super wideband Support, Device Networking, etc. have been researched.
A technical object of the present disclosure is to provide a method and apparatus for transmitting one or more hybrid automatic repeat and request (HARQ)-acknowledgment (ACK) information.
A technical object of the present disclosure is to provide a method and apparatus for transmitting and receiving a HARQ-ACK codebook composed of HARQ-ACK information for a unicast physical downlink shared channel (PDSCH) and/or a multicast PDSCH.
The technical objects to be achieved by the present disclosure are not limited to the above-described technical objects, and other technical objects which are not described herein will be clearly understood by those skilled in the pertinent art from the following description.
A method for performing uplink transmission by a user equipment (UE) in a wireless communication system according to an aspect of the present disclosure may comprise: receiving at least one of a first unicast physical downlink shared channel (PDSCH) or a first multicast PDSCH, based on a first quasi co-located (QCL) reference signal (RS); receiving at least one of a second unicast PDSCH or a second multicast PDSCH, based on a second QCL RS; and transmitting hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information through one or more physical uplink control channels (PUCCHs). Herein, the HARQ-ACK information may include a first sub HARQ-ACK codebook and a second sub HARQ-ACK codebook determined based on the first unicast PDSCH, the first multicast PDSCH, the second unicast PDSCH, and the second multicast PDSCH.
A method for performing uplink reception by a base station in a wireless communication system according to an additional aspect of the present disclosure may comprise: transmitting at least one of a first unicast physical downlink shared channel (PDSCH) or a first multicast PDSCH, based on a first quasi co-located (QCL) reference signal (RS); transmitting at least one of a second unicast PDSCH or a second multicast PDSCH, based on a second QCL RS; and receiving hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information through one or more physical uplink control channels (PUCCHs). Herein, the HARQ-ACK information may include a first sub HARQ-ACK codebook and a second sub HARQ-ACK codebook determined based on the first unicast PDSCH, the first multicast PDSCH, the second unicast PDSCH, and the second multicast PDSCH.
According to an embodiment of the present disclosure, a UE that receives multiple PDSCHs in which FDM and TDM schemes are mixed may efficiently construct an HARQ-ACK codebook based on specific rules and/or UE capability.
According to an embodiment of the present disclosure, a UE that simultaneously receives one or more unicast PDSCHs and one or more multicast PDSCHs may efficiently construct an HARQ-ACK codebook for corresponding PDSCH(s).
According to an embodiment of the present disclosure, HARQ-ACK information transmission for unicast/multicast PDSCH reception may be performed even when M-TRP transmission and reception is configured.
Effects achievable by the present disclosure are not limited to the above-described effects, and other effects which are not described herein may be clearly understood by those skilled in the pertinent art from the following description.
Accompanying drawings included as part of detailed description for understanding the present disclosure provide embodiments of the present disclosure and describe technical features of the present disclosure with detailed description.
Hereinafter, embodiments according to the present disclosure will be described in detail by referring to accompanying drawings. Detailed description to be disclosed with accompanying drawings is to describe exemplary embodiments of the present disclosure and is not to represent the only embodiment that the present disclosure may be implemented. The following detailed description includes specific details to provide complete understanding of the present disclosure. However, those skilled in the pertinent art knows that the present disclosure may be implemented without such specific details.
In some cases, known structures and devices may be omitted or may be shown in a form of a block diagram based on a core function of each structure and device in order to prevent a concept of the present disclosure from being ambiguous.
In the present disclosure, when an element is referred to as being “connected”, “combined” or “linked” to another element, it may include an indirect connection relation that yet another element presents therebetween as well as a direct connection relation. In addition, in the present disclosure, a term, “include” or “have”, specifies the presence of a mentioned feature, step, operation, component and/or element, but it does not exclude the presence or addition of one or more other features, stages, operations, components, elements and/or their groups.
In the present disclosure, a term such as “first”, “second”, etc. is used only to distinguish one element from other element and is not used to limit elements, and unless otherwise specified, it does not limit an order or importance, etc. between elements. Accordingly, within a scope of the present disclosure, a first element in an embodiment may be referred to as a second element in another embodiment and likewise, a second element in an embodiment may be referred to as a first element in another embodiment.
A term used in the present disclosure is to describe a specific embodiment, and is not to limit a claim. As used in a described and attached claim of an embodiment, a singular form is intended to include a plural form, unless the context clearly indicates otherwise. A term used in the present disclosure, “and/or”, may refer to one of related enumerated items or it means that it refers to and includes any and all possible combinations of two or more of them. In addition, “/” between words in the present disclosure has the same meaning as “and/or”, unless otherwise described.
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 in which a device (e.g., a base station) controlling a corresponding wireless communication network controls a network and transmits or receives a signal, or may be performed in a process in which a terminal associated to a corresponding wireless network transmits or receives a signal with a network or between terminals.
In the present disclosure, transmitting or receiving a channel includes a meaning of transmitting or receiving information or a signal through a corresponding channel. For example, transmitting a control channel means that control information or a control signal is transmitted through a control channel. Similarly, transmitting a data channel means that data information or a data signal is transmitted through a data channel.
Hereinafter, a downlink (DL) means a communication from a base station to a terminal and an uplink (UL) means a communication from a terminal to a base station. In a downlink, a transmitter may be part of a base station and a receiver may be part of a terminal. In an 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 substituted with a term such as a fixed station, a Node B, an eNB (evolved-NodeB), a gNB (Next Generation NodeB), a BTS (base transceiver system), an Access Point (AP), a Network (5G network), an AI (Artificial Intelligence) system/module, an RSU (road side unit), a robot, a drone (UAV: Unmanned Aerial Vehicle), an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be substituted with a term such as a UE (User Equipment), an MS (Mobile Station), a UT (user terminal), an MSS (Mobile Subscriber Station), an SS(Subscriber Station), an AMS (Advanced Mobile Station), a WT (Wireless terminal), an MTC (Machine-Type Communication) device, an M2M (Machine-to-Machine) device, a D2D (Device-to-Device) device, a vehicle, an RSU (road side unit), a robot, an AI (Artificial Intelligence) module, a drone (UAV: Unmanned Aerial Vehicle), an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc.
The following description may be used for a variety of radio access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by a wireless technology such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA may be implemented by a radio technology such as GSM (Global System for Mobile communications)/GPRS (General Packet Radio Service)/EDGE (Enhanced Data Rates for GSM Evolution). OFDMA may be implemented by a radio technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is a part of a UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of an E-UMTS (Evolved UMTS) using E-UTRA and LTE-A (Advanced)/LTE-A pro is an advanced version of 3GPP LTE. 3GPP NR(New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE/LTE-A/LTE-A pro.
To clarify description, it is described based on a 3GPP communication system (e.g., LTE-A, NR), but a technical idea of the present disclosure is not limited thereto. LTE means a technology after 3GPP TS (Technical Specification) 36.xxx Release 8. In detail, an LTE technology in or after 3GPP TS 36.xxx Release 10 is referred to as LTE-A and an LTE technology in or after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR means a technology in or after TS 38.xxx Release 15. LTE/NR may be referred to as a 3GPP system. “xxx” means a detailed number for a standard document. LTE/NR may be commonly referred to as a 3GPP system. For a background art, a term, an abbreviation, etc. used to describe the present disclosure, matters described in a standard document disclosed before the present disclosure may be referred to. For example, the following document may be referred to.
For 3GPP LTE, TS 36.211 (physical channels and modulation), TS 36.212 (multiplexing and channel coding), TS 36.213 (physical layer procedures), TS 36.300 (overall description), TS 36.331 (radio resource control) may be referred to.
For 3GPP NR, TS 38.211 (physical channels and modulation), TS 38.212 (multiplexing and channel coding), TS 38.213 (physical layer procedures for control), TS 38.214 (physical layer procedures for data), TS 38.300 (NR and NG-RAN(New Generation-Radio Access Network) overall description), TS 38.331 (radio resource control protocol specification) may be referred to.
Abbreviations of terms which may be used in the present disclosure is defined as follows.
As more communication devices have required a higher capacity, a need for an improved mobile broadband communication compared to the existing radio access technology (RAT) has emerged. In addition, massive MTC (Machine Type Communications) providing a variety of services anytime and anywhere by connecting a plurality of devices and things is also one of main issues which will be considered in a next-generation communication. Furthermore, a communication system design considering a service/a terminal sensitive to reliability and latency is also discussed. As such, introduction of a next-generation RAT considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc. is discussed and, for convenience, a corresponding technology is referred to as NR in the present disclosure. NR is an expression which represents an example of a 5G RAT.
A new RAT system including NR uses an OFDM transmission method or a transmission method similar to it. A new RAT system may follow OFDM parameters different from OFDM parameters of LTE. Alternatively, a new RAT system follows a numerology of the existing LTE/LTE-A as it is, but may support a wider system bandwidth (e.g., 100 MHz). Alternatively, one cell may support a plurality of numerologies. In other words, terminals which operate in accordance with different numerologies may coexist in one cell.
A numerology corresponds to one subcarrier spacing in a frequency domain. As a reference subcarrier spacing is scaled by an integer N, a different numerology may be defined.
In reference to
A NR system may support a plurality of numerologies. Here, a numerology may be defined by a subcarrier spacing and a cyclic prefix (CP) overhead. Here, a plurality of subcarrier spacings may be derived by scaling a basic (reference) subcarrier spacing by an integer N (or, μ). In addition, although it is assumed that a very low subcarrier spacing is not used in a very high carrier frequency, a used numerology may be selected independently from a frequency band. In addition, a variety of frame structures according to a plurality of numerologies may be supported in a NR system.
Hereinafter, an OFDM numerology and frame structure which may be considered in a NR system will be described. A plurality of OFDM numerologies supported in a NR system may be defined as in the following Table 1.
NR supports a plurality of numerologies (or subcarrier spacings (SCS)) for supporting a variety of 5G services. For example, when a SCS is 15 kHz, a wide area in traditional cellular bands is supported, and when a SCS is 30 kHz/60 kHz, dense-urban, lower latency and a wider carrier bandwidth are supported, and when a SCS is 60 kHz or higher, a bandwidth wider than 24.25 GHz is supported to overcome a phase noise.
An NR frequency band is defined as a frequency range in two types (FR1, FR2). FR1, FR2 may be configured as in the following Table 2. In addition, FR2 may mean a millimeter wave (mmW).
Regarding a frame structure in an NR system, a size of a variety of fields in a time domain is expresses as a multiple of a time unit of Tc=1/(Δfmax·Nf). Here, Δfmax is 480·103 Hz and Nf is 4096. Downlink and uplink transmission is configured (organized) with a radio frame having a duration of Tf=1/(ΔfmaxNf/100)·Tc=10 ms. Here, a radio frame is configured with 10 subframes having a duration of Tsf=(ΔfmaxNf/1000)·Tc=1 ms, respectively. In this case, there may be one set of frames for an uplink and one set of frames for a downlink. In addition, transmission in an uplink frame No. i from a terminal should start earlier by TTA=(NTA+NTA,offset)Tc than a corresponding downlink frame in a corresponding terminal starts. For a subcarrier spacing configuration μ, slots are numbered in an increasing order of nsμ∈{0, . . . , Nslotsubframe,μ−1} in a subframe and are numbered in an increasing order of nsfμ∈{0, . . . , Nslotframe,μ−1} in a radio frame. One slot is configured with Nsymbslot consecutive OFDM symbols and Nsymbslot is determined according to CP. A start of a slot nsμ in a subframe is temporally arranged with a start of an OFDM symbol nsμNsymbslot in the same subframe. All terminals may not perform transmission and reception at the same time, which means that all OFDM symbols of a downlink slot or an uplink slot may not be used.
Table 3 represents the number of OFDM symbols per slot (Nsymbslot, the number of slots per radio frame (Nslotframe,μ) and the number of slots per subframe (Nslotsubframe, μ) in a normal CP and Table 4 represents the number of OFDM symbols per slot, the number of slots per radio frame and the number of slots per subframe in an extended CP.
Regarding a physical resource in a NR system, an antenna port, a resource grid, a resource element, a resource block, a carrier part, etc. may be considered. Hereinafter, the physical resources which may be considered in an NR system will be described in detail.
First, in relation to an antenna port, an antenna port is defined so that a channel where a symbol in an antenna port is carried can be inferred from a channel where other symbol in the same antenna port is carried. When a large-scale property of a channel where a symbol in one antenna port is carried may be inferred from a channel where a symbol in other antenna port is carried, it may be said that 2 antenna ports are in a QC/QCL (quasi co-located or quasi co-location) relationship. In this case, the large-scale property includes at least one of delay spread, doppler spread, frequency shift, average received power, received timing.
In reference to
Point A plays a role as a common reference point of a resource block grid and is obtained as follows.
Common resource blocks are numbered from 0 to the top in a frequency domain for a subcarrier spacing configuration. The center of subcarrier 0 of common resource block 0 for a subcarrier spacing configuration μ is identical to ‘point A’. A relationship between a common resource block number nCRBμ and a resource element (k,l) for a subcarrier spacing configuration μ in a frequency domain is given as in the following Equation 1.
In Equation 1, k is defined relatively to point A so that k=0 corresponds to a subcarrier centering in point A. Physical resource blocks are numbered from 0 to NBWP,isize,μ−1 in a bandwidth part (BWP) and i is a number of a BWP. A relationship between a physical resource block nPRB and a common resource block nCRB in BWP i is given by the following Equation 2.
NBWP,isize,μ is a common resource block that a BWP starts relatively to common resource block 0.
In reference to
A carrier includes a plurality of subcarriers in a frequency domain. An RB (Resource Block) is defined as a plurality of (e.g., 12) consecutive subcarriers in a frequency domain. A BWP (Bandwidth Part) is defined as a plurality of consecutive (physical) resource blocks in a frequency domain and may correspond to one numerology (e.g., an SCS, a CP length, etc.). A carrier may include a maximum N (e.g., 5) BWPs. A data communication may be performed through an activated BWP and only one BWP may be activated for one terminal. In a resource grid, each element is referred to as a resource element (RE) and one complex symbol may be mapped.
In an NR system, up to 400 MHz may be supported per component carrier (CC). If a terminal operating in such a wideband CC always operates turning on a radio frequency (FR) chip for the whole CC, terminal battery consumption may increase. Alternatively, when several application cases operating in one wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.) are considered, a different numerology (e.g., a subcarrier spacing, etc.) may be supported per frequency band in a corresponding CC. Alternatively, each terminal may have a different capability for the maximum bandwidth. By considering it, a base station may indicate a terminal to operate only in a partial bandwidth, not in a full bandwidth of a wideband CC, and a corresponding partial bandwidth is defined as a bandwidth part (BWP) for convenience. A BWP may be configured with consecutive RBs on a frequency axis and may correspond to one numerology (e.g., a subcarrier spacing, a CP length, a slot/a mini-slot duration).
Meanwhile, a base station may configure a plurality of BWPs even in one CC configured to a terminal. For example, a BWP occupying a relatively small frequency domain may be configured in a PDCCH monitoring slot, and a PDSCH indicated by a PDCCH may be scheduled in a greater BWP. Alternatively, when UEs are congested in a specific BWP, some terminals may be configured with other BWP for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, etc., some middle spectrums of a full bandwidth may be excluded and BWPs on both edges may be configured in the same slot. In other words, a base station may configure at least one DL/UL BWP to a terminal associated with a wideband CC. A base station may activate at least one DL/UL BWP of configured DL/UL BWP(s) at a specific time (by L1 signaling or MAC CE (Control Element) or RRC signaling, etc.). In addition, a base station may indicate switching to other configured DL/UL BWP (by L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, based on a timer, when a timer value is expired, it may be switched to a determined DL/UL BWP. Here, an activated DL/UL BWP is defined as an active DL/UL BWP. But, a configuration on a DL/UL BWP may not be received when a terminal performs an initial access procedure or before a RRC connection is set up, so a DL/UL BWP which is assumed by a terminal under these situations is defined as an initial active DL/UL BWP.
In a wireless communication system, a terminal receives information through a downlink from a base station and transmits information through an uplink to a base station. Information transmitted and received by a base station and a terminal includes data and a variety of control information and a variety of physical channels exist according to a type/a usage of information transmitted and received by them.
When a terminal is turned on or newly enters a cell, it performs an initial cell search including synchronization with a base station or the like (S601). For the initial cell search, a terminal may synchronize with a base station by receiving a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from a base station and obtain information such as a cell identifier (ID), etc. After that, a terminal may obtain broadcasting information in a cell by receiving a physical broadcast channel (PBCH) from a base station. Meanwhile, a terminal may check out a downlink channel state by receiving a downlink reference signal (DL RS) at an initial cell search stage.
A terminal which completed an initial cell search may obtain more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S602).
Meanwhile, when a terminal accesses to a base station for the first time or does not have a radio resource for signal transmission, it may perform a random access (RACH) procedure to a base station (S603 to S606). For the random access procedure, a terminal may transmit a specific sequence as a preamble through a physical random access channel (PRACH) (S603 and S605) and may receive a response message for a preamble through a PDCCH and a corresponding PDSCH (S604 and S606). A contention based RACH may additionally perform a contention resolution procedure.
A terminal which performed the above-described procedure subsequently may perform PDCCH/PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel)/PUCCH (physical uplink control channel) transmission (S608) as a general uplink/downlink signal transmission procedure. In particular, a terminal receives downlink control information (DCI) through a PDCCH. Here, DCI includes control information such as resource allocation information for a terminal and a format varies depending on its purpose of use.
Meanwhile, control information which is transmitted by a terminal to a base station through an uplink or is received by a terminal from a base station includes a downlink/uplink ACK/NACK (Acknowledgement/Non-Acknowledgement) signal, a CQI (Channel Quality Indicator), a PMI (Precoding Matrix Indicator), a RI (Rank Indicator), etc. For a 3GPP LTE system, a terminal may transmit control information of the above-described CQI/PMI/RI, etc. through a PUSCH and/or a PUCCH.
Table 5 represents an example of a DCI format in an NR system.
In reference to Table 5, DCI formats 0_0, 0_1 and 0_2 may include resource information (e.g., UL/SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to a transport block (TB) (e.g., MCS (Modulation Coding and Scheme), a NDI (New Data Indicator), a RV (Redundancy Version), etc.), information related to a HARQ (Hybrid—Automatic Repeat and request) (e.g., a process number, a DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, an antenna port, a CSI request, etc.), power control information (e.g., PUSCH power control, etc.) related to scheduling of a PUSCH and control information included in each DCI format may be pre-defined.
DCI format 0_0 is used for scheduling of a PUSCH in one cell. Information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled by a C-RNTI (Cell Radio Network Temporary Identifier) or a CS-RNTI (Configured Scheduling RNTI) or a MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.
DCI format 0_1 is used to indicate scheduling of one or more PUSCHs or configure grant (CG) downlink feedback information to a terminal in one cell. Information included in DCI format 0_1 is CRC scrambled by a C-RNTI or a CS-RNTI or a SP-CSI-RNTI (Semi-Persistent CSI RNTI) or a MCS-C-RNTI and transmitted.
DCI format 0_2 is used for scheduling of a PUSCH in one cell. Information included in DCI format 0_2 is CRC scrambled by a C-RNTI or a CS-RNTI or a SP-CSI-RNTI or a MCS-C-RNTI and transmitted.
Next, DCI formats 10, 1_1 and 1_2 may include resource information (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), information related to a transport block (TB)(e.g., MCS, NDI, RV, etc.), information related to a HARQ (e.g., a process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., an antenna port, a TCI (transmission configuration indicator), a SRS (sounding reference signal) request, etc.), information related to a PUCCH (e.g., PUCCH power control, a PUCCH resource indicator, etc.) related to scheduling of a PDSCH and control information included in each DCI format may be pre-defined.
DCI format 1_0 is used for scheduling of a PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled by a C-RNTI or a CS-RNTI or a MCS-C-RNTI and transmitted.
DCI format 1_1 is used for scheduling of a PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled by a C-RNTI or a CS-RNTI or a MCS-C-RNTI and transmitted.
DCI format 1_2 is used for scheduling of a PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled by a C-RNTI or a CS-RNTI or a MCS-C-RNTI and transmitted.
An antenna port is defined so that a channel where a symbol in an antenna port is transmitted can be inferred from a channel where other symbol in the same antenna port is transmitted. When a property of a channel where a symbol in one antenna port is carried may be inferred from a channel where a symbol in other antenna port is carried, it may be said that 2 antenna ports are in a QC/QCL (quasi co-located or quasi co-location) relationship.
Here, the channel property includes at least one of delay spread, doppler spread, frequency/doppler shift, average received power, received timing/average delay, or a spatial RX parameter. Here, a spatial Rx parameter means a spatial (Rx) channel property parameter such as an angle of arrival.
A terminal may be configured at list of up to M TCI-State configurations in a higher layer parameter PDSCH-Config to decode a PDSCH according to a detected PDCCH having intended DCI for a corresponding terminal and a given serving cell. The M depends on UE capability.
Each TCI-State includes a parameter for configuring a quasi co-location relationship between ports of one or two DL reference signals and a DM-RS of a PDSCH.
A quasi co-location relationship is configured by a higher layer parameter qcl-Type1 for a first DL RS and qcl-Type2 for a second DL RS (if configured). For two DL RSs, a QCL type is not the same regardless of whether a reference is a same DL RS or a different DL RS.
A quasi co-location type corresponding to each DL RS is given by a higher layer parameter qcl-Type of QCL-Info and may take one of the following values.
For example, when a target antenna port is a specific NZP CSI-RS, it may be indicated/configured that a corresponding NZP CSI-RS antenna port(s) is quasi-colocated with a specific TRS with regard to QCL-Type A and is quasi-colocated with a specific SSB with regard to QCL-Type D. A terminal received such indication/configuration may receive a corresponding NZP CSI-RS by using a doppler, delay value measured in a QCL-TypeA TRS and apply a Rx beam used for receiving QCL-TypeD SSB to reception of a corresponding NZP CSI-RS.
UE may receive an activation command by MAC CE signaling used to map up to 8 TCI states to a codepoint of a DCI field ‘Transmission Configuration Indication’.
A coordinated multi point (CoMP) scheme refers to a scheme in which a plurality of base stations effectively control interference by exchanging (e.g., using an X2 interface) or utilizing channel information (e.g., RI/CQI/PMI/LI (layer indicator), etc.) fed back by a terminal and cooperatively transmitting to a terminal. According to a scheme used, a CoMP may be classified into joint transmission (JT), coordinated Scheduling (CS), coordinated Beamforming (CB), dynamic Point Selection (DPS), dynamic Point Blocking (DPB), etc.
M-TRP transmission schemes that M TRPs transmit data to one terminal may be largely classified into i) eMBB M-TRP transmission, a scheme for improving a transfer rate, and ii) URLLC M-TRP transmission, a scheme for increasing a reception success rate and reducing latency.
In addition, with regard to DCI transmission, M-TRP transmission schemes may be classified into i) M-TRP transmission based on M-DCI (multiple DCI) that each TRP transmits different DCIs and ii) M-TRP transmission based on S-DCI (single DCI) that one TRP transmits DCI. For example, for S-DCI based M-TRP transmission, all scheduling information on data transmitted by M TRPs should be delivered to a terminal through one DCI, it may be used in an environment of an ideal BackHaul (ideal BH) where dynamic cooperation between two TRPs is possible.
A UE may recognize PUSCH (or PUCCH) scheduled by DCI received in different control resource sets (CORESETs)(or CORESETs belonging to different CORESET groups) as PUSCH (or PUCCH) transmitted to different TRPs or may recognize PDSCH (or PDCCH) from different TRPs. In addition, the below-described method for UL transmission (e.g., PUSCH/PUCCH) transmitted to different TRPs may be applied equivalently to UL transmission (e.g., PUSCH/PUCCH)transmitted to different panels belonging to the same TRP.
Hereinafter, a CORESET group ID described/mentioned in the present disclosure may mean an index/identification information (e.g., an ID, etc.) for distinguishing a CORESET for each TRP/panel. In addition, a CORESET group may be a group/union of CORESET distinguished by an index/identification information (e.g., an ID)/the CORESET group ID, etc. for distinguishing a CORESET for each TRP/panel. In an example, a CORESET group ID may be specific index information defined in a CORESET configuration. In this case, a CORESET group may be configured/indicated/defined by an index defined in a CORESET configuration for each CORESET. Additionally/alternatively, a CORESET group ID may mean an index/identification information/an indicator, etc. for distinguishment/identification between CORESETs configured/associated with each TRP/panel. Hereinafter, a CORESET group ID described/mentioned in the present disclosure may be expressed by being substituted with a specific index/specific identification information/a specific indicator for distinguishment/identification between CORESETs configured/associated with each TRP/panel. The CORESET group ID, i.e., a specific index/specific identification information/a specific indicator for distinguishment/identification between CORESETs configured/associated with each TRP/panel may be configured/indicated to a terminal through higher layer signaling (e.g., RRC signaling)/L2 signaling (e.g., MAC-CE)/L1 signaling (e.g., DCI), etc. In an example, it may be configured/indicated so that PDCCH detection will be performed per each TRP/panel in a unit of a corresponding CORESET group (i.e., per TRP/panel belonging to the same CORESET group). Additionally/alternatively, it may be configured/indicated so that uplink control information (e.g., CSI, HARQ-A/N (ACK/NACK), SR (scheduling request)) and/or uplink physical channel resources (e.g., PUCCH/PRACH/SRS resources) are separated and managed/controlled per each TRP/panel in a unit of a corresponding CORESET group (i.e., per TRP/panel belonging to the same CORESET group). Additionally/alternatively, HARQ A/N (process/retransmission) for PDSCH/PUSCH, etc. scheduled per each TRP/panel may be managed per corresponding CORESET group (i.e., per TRP/panel belonging to the same CORESET group).
For example, a higher layer parameter, ControlResourceSet information element (IE), is used to configure a time/frequency control resource set (CORESET). In an example, the control resource set (CORESET) may be related to detection and reception of downlink control information. The ControlResourceSet IE may include a CORESET-related ID (e.g., controlResourceSetID)/an index of a CORESET pool for a CORESET (e.g., CORESETPoolIndex)/a time/frequency resource configuration of a CORESET/TCI information related to a CORESET, etc. In an example, an index of a CORESET pool (e.g., CORESETPoolIndex) may be configured as 0 or 1. In the description, a CORESET group may correspond to a CORESET pool and a CORESET group ID may correspond to a CORESET pool index (e.g., CORESETPoolIndex).
Hereinafter, a method for improving reliability in Multi-TRP will be described.
As a transmission and reception method for improving reliability using transmission in a plurality of TRPs, the following two methods may be considered.
In reference to
In reference to
According to methods illustrated in
In addition, the above-described contents related to multiple TRPs are described based on an SDM (spatial division multiplexing) method using different layers, but it may be naturally extended and applied to a FDM (frequency division multiplexing) method based on a different frequency domain resource (e.g., RB/PRB (set), etc.) and/or a TDM (time division multiplexing) method based on a different time domain resource (e.g., a slot, a symbol, a sub-symbol, etc.).
Multi-TRP scheduled by at least one DCI may be performed as follows:
i) Scheme 1 (SDM): n (n is a natural number) TCI states in a single slot in overlapping time and frequency resource allocation
In schemes 1a and 1c described above, the same MCS is applied to all layers or sets of layers.
ii) Scheme 2 (FDM): n (n is a natural number) TCI states in a single slot in non-overlapping frequency resource allocation. Each non-overlapping frequency resource allocation is associated with one TCI state. The same single/multiple DMRS port(s) is associated with all non-overlapping frequency resource allocations.
In scheme 2a, the same MCS is applied to all non-overlapping frequency resource allocations.
iii) Scheme 3 (TDM): n (n is a natural number) TCI states in a single slot in non-overlapping time resource allocation. Each transmission occasion of a TB has one TCI and one RV with time granularity of a mini-slot. All transmission occasion(s) in a slot use a common MCS with the same single or multiple DMRS port(s). An RV/TCI state may be the same or different among transmission occasions.
iv) Scheme 4 (TDM): n (n is a natural number) TCI states in K (n<=K, K is a natural number) different slots. Each transmission occasion of a TB has one TCI and one RV. All transmission occasion(s) across K slots use a common MCS with the same single or multiple DMRS port(s). An RV/TCI state may be the same or different among transmission occasions.
Hereinafter, in the present disclosure, DL MTRP-URLLC means that M-TRPs transmit the same data (e.g., transport block, TB)/DCI by using a different layer/time/frequency resource. For example, TRP 1 transmits the same data/DCI in resource 1 and TRP 2 transmits the same data/DCI in resource 2. UE configured with a DL MTRP-URLLC transmission method receives the same data/DCI by using a different layer/time/frequency resource. Here, UE is indicated which QCL RS/type (i.e., a DL TCI (state)) should be used in a layer/time/frequency resource receiving the same data/DCI from a base station. For example, when the same data/DCI is received in resource 1 and resource 2, a DL TCI state used in resource 1 and a DL TCI state used in resource 2 may be indicated. UE may achieve high reliability because it receives the same data/DCI through resource 1 and resource 2. Such DL MTRP URLLC may be applied to a PDSCH/a PDCCH.
Conversely, UL MTRP-URLLC means that M-TRPs receive the same data/UCI from UE by using a different layer/time/frequency resource. For example, TRP 1 receives the same data/UCI from UE in resource 1 and TRP 2 receives the same data/UCI from UE in resource 2 and shares received data/UCI through a backhaul link connected between TRPs. UE configured with a UL MTRP-URLLC transmission method transmits the same data/UCI by using a different layer/time/frequency resource. Here, UE is indicated which Tx beam and which Tx power (i.e., a UL TCI state) should be used in a layer/time/frequency resource transmitting the same data/DCI from a base station. For example, when the same data/UCI is received in resource 1 and resource 2, a UL TCI state used in resource 1 and a UL TCI state used in resource 2 may be indicated. Such UL MTRP URLLC may be applied to a PUSCH/a PUCCH.
In addition, in methods proposed in the present disclosure, when a specific TCI state (or a TCI) is used (/mapped) in receiving data/DCI/UCI for any frequency/time/space resource, it may mean that a DL estimates a channel from a DMRS by using a QCL type and a QCL RS indicated by a corresponding TCI state in that frequency/time/space resource and receives/demodulates data/DCI to an estimated channel. It may mean that an UL transmits/modulates a DMRS and data/UCI by using a Tx beam and/or Tw power indicated by a corresponding TCI state in that frequency/time/space resource.
The UL TCI state has Tx beam and/or Tx power information of UE and spatial relation information, etc. instead of a TCI state may be configured to UE through other parameter. An UL TCI state may be directly indicated to UL grant DCI or may mean spatial relation information of an SRS resource indicated by an SRI (SRS resource indicator) field of UL grant DCI. Alternatively, it may mean an OL (open loop) Tx power control parameter connected to a value indicated by a SRI field of UL grant DCI (j: an index for open loop parameter Po and alpha (a) (up to 32 parameter value sets per cell), q_d: an index of a DL RS resource for PL (pathloss) measurement (measurement of up to 3 per cell), 1: a closed loop power control process index (up to 2 processes per cell)).
On the other hand, it is assumed that MTRP-eMBB means that M-TRPs transmit other data by using a different layer/time/frequency, UE configured with a MTRP-eMBB transmission method is indicated multiple TCI states with DCI and data received by using a QCL RS of each TCI state is different data.
In addition, whether of MTRP URLLC transmission/reception or MTRP eMBB transmission/reception may be understood by UE by separately classifying a RNTI for MTRP-URLLC and a RNTI for MTRP-eMBB and using them. In other words, when CRC masking of DCI is performed by using a RNTI for URLLC, it is considered as URLLC transmission and when CRC masking of DCI is performed by using a RNTI for eMBB, it is considered as eMBB transmission. Alternatively, a base station may configure MTRP URLLC transmission/reception or may configure MTRP eMBB transmission/reception to UE through other new signaling.
In the present disclosure, for convenience of a description, a proposal is applied by assuming cooperative transmission/reception between 2 TRPs, but it may be extended and applied in 3 or more multi-TRP environments and it may be also extended and applied in multi-panel environments. A different TRP may be recognized by UE as a different transmission configuration indication (TCI) state. That is, when UE receives/transmits data/DCI/UCI by using TCI state 1, it means that data/DCI/UCI is received/transmitted from/to TRP 1.
A proposal of the present disclosure may be utilized in a situation where MTRP cooperatively transmits a PDCCH (the same PDCCH is repetitively or partitively transmitted) and some proposals may be utilized even in a situation where MTRP cooperatively transmits a PDSCH or cooperatively receives a PUSCH/a PUCCH.
In addition, in the present disclosure below, the meaning that a plurality of base stations (i.e., MTRP) repetitively transmits the same PDCCH may mean the same DCI is transmitted by a plurality of PDCCH candidates, and it is equivalent with the meaning that a plurality of base stations repetitively transmits the same DCI. The same DCI may mean two DCI with the same DCI format/size/payload. Alternatively, although two DCI have a different payload, it may be considered the same DCI when a scheduling result is the same. For example, a TDRA (time domain resource allocation) field of DCI relatively determines a slot/symbol position of data and a slot/symbol position of A/N (ACK/NACK) based on a reception time of DCI. Here, if DCI received at a time of n and DCI received at a time of n+1 represent the same scheduling result to UE, a TDRA field of two DCI is different, and consequentially, a DCI payload is different. R, the number of repetitions, may be directly indicated or mutually promised by a base station to UE. Alternatively, although a payload of two DCI is different and a scheduling result is not the same, it may be considered the same DCI when a scheduling result of one DCI is a subset of a scheduling result of other DCI. For example, when the same data is repetitively transmitted N times through TDM, DCI 1 received before first data indicates N data repetitions and DCI 2 received after first data and before second data indicates N-1 data repetitions. Scheduling data of DCI 2 becomes a subset of scheduling data of DCI 1 and two DCI is scheduling for the same data, so in this case, it may be considered the same DCI.
In addition, in the present disclosure below, when a plurality of base stations (i.e., MTRP) divide and transmit the same PDCCH, it may mean that one DCI is transmitted through one PDCCH candidate, but TRP 1 transmits some resources in which the PDCCH candidate is defined and TRP 2 transmits the remaining resources. For example, when TRP 1 and TRP 2 divide and transmit a PDCCH candidate corresponding to an aggregation level m1+m2, the PDCCH candidate is divided into PDCCH candidate 1 corresponding to aggregation level m1 and PDCCH candidate 2 corresponding to aggregation level m2, and TRP 1 transmits the PDCCH candidate 1 and TRP 2 transmits the PDCCH candidate 2 using different time/frequency resources. After receiving the PDCCH candidate 1 and the PDCCH candidate 2, a UE generates a PDCCH candidate corresponding to aggregation level m1+m2 and attempts DCI decoding.
When the same DCI is divided and transmitted to several PDCCH candidates, there may be two implementation methods.
First, a DCI payload (control information bits+CRC) may be encoded through one channel encoder (e.g., a polar encoder), coded bits obtained as a result may be divided into two TRPs and transmitted. In this case, an entire DCI payload may be encoded in coded bits transmitted by each TRP, or only a part of a DCI payload may be encoded. Second, a DCI payload (control information bits+CRC) may be divided into two (DCI 1 and DCI 2) and each can be encoded through a channel encoder (e.g., polar encoder). Thereafter, two TRPs may transmit coded bits corresponding to DCI 1 and coded bits corresponding to DCI 2, respectively.
In summary, it may be as follows that a plurality of base stations (i.e., MTRP) divide/repeat the same PDCCH and transmit over a plurality of monitoring occasions (MO).
That is, it may be understood that a PDCCH is transmitted multiple times over several transmission occasions (TO) regardless of repeated transmission or divided transmission of the PDCCH. Here, a TO means a specific time/frequency resource unit in which a PDCCH is transmitted. For example, if a PDCCH is transmitted multiple times (in a specific resource block (RB)) over slots 1, 2, 3, and 4, a TO may mean each slot, or if a PDCCH is transmitted multiple times (in a specific slot) over RB sets 1, 2, 3, and 4, a TO may mean each RB set, or if a PDCCH is transmitted multiple times over different times and frequencies, a TO may mean each time/frequency resource. In addition, a TCI state used for DMRS channel estimation for each TO may be configured differently, and it may be assumed that TOs in which a TCI state is configured differently are transmitted by different TRPs/panels. When a plurality of base stations repeatedly transmits or dividedly transmits a PDCCH, it means that the PDCCH is transmitted over a plurality of TOs, and the union of TCI states configured in corresponding TOs is configured with two or more TCI states. For example, if a PDCCH is transmitted over TOs 1, 2, 3, 4, TCI states 1, 2, 3, 4 may be configured in each of TOs 1, 2, 3, 4, respectively, which means that TRP i transmits cooperatively a PDCCH in TO i.
For a plurality of TOs indicated to a UE to repeatedly transmit or dividedly transmit a PDCCH/PDSCH/PUSCH/PUCCH, UL transmits to a specific TRP or DL receives from a specific TRP in each TO. Here, a UL TO (or TO of TRP 1) transmitted to TRP 1 means a TO using the first value among two spatial relations, two UL TCIs, two UL power control parameters and/or two pathloss reference signals (PLRS) indicated to a UE, and a UL TO (or TO of TRP 2) transmitted to TRP 2 means a TO using the second value among two spatial relations, two UL TCIs, two UL power control parameters and/or two PLRSs indicated to a UE. Similarly, for DL transmission, a DL TO (or TO of TRP 1) transmitted by TRP 1 means a TO using the first value among two DL TCI states (e.g., when two TCI states are configured in CORESET) indicated to a UE, and a DL TO (or TO of TRP 2) transmitted by TRP 2 means a TO using the second value among two DL TCI states (e.g., when two TCI states are configured in CORESET) indicated to a UE.
The proposal of the present disclosure can be extended and applied to various channels such as PUSCH/PUCCH/PDSCH/PDCCH.
The proposal of the present disclosure can be extended and applied to both a case of repeated transmission and a case of divided transmission the channel on different time/frequency/spatial resources.
Data transmission and HARQ (Hybrid Automatic Repeat and request)-ACK (Acknowledgement) Process
Referring to
Thereafter, a UE may receive a PDSCH in slot #(n+K0) according to scheduling information of slot #n, and then transmit UCI through a PUCCH in slot #(n+K1). Here, UCI includes a HARQ-ACK response for a PDSCH. If a PDSCH is configured to transmit up to 1 TB, a HARQ-ACK response may be composed of 1-bit. When a PDSCH is configured to transmit up to two TBs, a HARQ-ACK response may be composed of 2-bits if spatial bundling is not configured and 1-bit if spatial bundling is configured. When a HARQ-ACK transmission time for a plurality of PDSCHs is designated as slot #(n+K1), UCI transmitted in slot #(n+K1) includes HARQ-ACK responses for a plurality of PDSCHs.
3GPP MBMS can be divided into i) a single frequency network (SFN) method in which a plurality of base station cells are synchronized to transmit the same data through a physical multicast channel (PMCH) and ii) SC-PTM (Single Cell Point To Multipoint) method broadcasting within a cell coverage through a PDCCH/PDSCH channel. The SFN method is used to provide broadcasting services over a wide area (e.g., MBMS area) through semi-statically allocated resources, while the SC-PTM method is mainly used to provide broadcasting services only within a cell coverage through dynamic resources.
The SC-PTM provides one logical channel, an SC-MCCH (Single Cell Multicast Control Channel) and one or a plurality of logical channels, an SC-MTCH (Single Cell Multicast Traffic Channel). These logical channels are mapped to a downlink shared channel (DL-SCH), which is a transport channel, and a PDSCH, which is a physical channel. A PDSCH transmitting SC-MCCH or SC-MTCH data is scheduled through a PDCCH indicated by a group-RNTI (G-RNTI). In this case, a temporary multicast group ID (TMGI) corresponding to a service identifier (ID) may be mapped one-to-one with a specific G-RNTI value. Therefore, if a base station provides multiple services, multiple G-RNTI values may be allocated for SC-PTM transmission. One or a plurality of UEs may perform PDCCH monitoring using a specific G-RNTI to receive a specific service. Here, a DRX on-duration period may be configured exclusively for an SC-PTM for a specific service/specific G-RNTI. In this case, the UEs wake up only for a specific on-duration period and perform PDCCH monitoring for the G-RNTI.
BWP: BandWidth Part (It may be composed of continuous resource blocks (RBs) on a frequency axis. It may correspond to one numerology (e.g., SCS, CP length, slot/mini-slot duration, etc.). In addition, a plurality of BWPs may be configured in one carrier (the number of BWPs per carrier may also be limited), but the number of activated BWPs may be limited to a part (e.g., one) per carrier.)
TCI: Transmission Configuration Indication (One TCI state includes a QCL relationship between DM-RS ports of a PDSCH, DM-RS ports of a PDCCH, or CSI-RS port(s) of a CSI-RS resource and one or more DL RSs. For ‘Transmission Configuration Indication’ among fields in DCI that schedules a PDSCH, a TCI state index corresponding to each code point constituting the field is activated by a MAC control element (CE), and a TCI state configuration for each TCI state index is configured through RRC signaling. In the Rel-16 NR system, a corresponding TCI state is configured between DL RSs, but a configuration between a DL RS and a UL RS or between a UL RS and a UL RS may be allowed in a future release. Examples of a UL RS include an SRS, a PUSCH DM-RS, and a PUCCH DM-RS.)
The above contents (3GPP system, frame structure, NR system, etc.) can be applied in combination with methods proposed in the present disclosure to be described later, or it may be supplemented to clarify the technical characteristics of the methods proposed in the present disclosure. In this disclosure, ‘/’ means ‘and’, ‘or’, or ‘and/or’ depending on the context.
In the prior art, a base station may configure a UE-specific SPS configuration for a specific UE and allocate a repeated downlink SPS transmission resource according to a configured period. Here, DCI of a UE-specific PDCCH may indicate activation (SPS activation) of a specific SPS configuration index, and accordingly, the corresponding UE can repeatedly receive an SPS transmission resource according to a configured period. This SPS transmission resource is used for initial HARQ (hybrid automatic repeat request) transmission, and a base station may allocate a retransmission resource of a specific SPS configuration index through DCI of a UE-specific PDCCH. For example, when a UE reports a HARQ NACK for an SPS transmission resource, a base station can allocate a retransmission resource to DCI so that a UE can receive downlink retransmission. In addition, DCI of a UE-specific PDCCH may indicate deactivation (SPS release or SPS deactivation) of a specific SPS configuration index, and a UE receiving this does not receive the indicated SPS transmission resource. Here, a cyclic redundancy check (CRC) of DCI for activation/retransmission/deactivation of the SPS is scrambled with Configured Scheduling-RNTI (CS-RNTI).
Rel-17 NR intends to introduce a DL broadcast or DL multicast transmission method to support a Multicast Broadcast Service (MBS) service similar to LTE MBMS. A base station provides a point-to-multipoint (PTM) transmission method and/or a point-to-point (PTP) transmission method for DL broadcast or DL multicast transmission.
In a PTM transmission method for an MBS, a base station transmits a group common PDCCH and a group common PDSCH to a plurality of UEs, and a plurality of UEs simultaneously receive the same group common PDCCH and group common PDSCH transmission to decode the same MBS data.
On the other hand, in a PTP transmission scheme for an MBS, a base station transmits a UE-specific PDCCH and a UE-specific PDSCH to a specific UE, and only the corresponding UE receives the UE-specific PDCCH and the UE-specific PDSCH. Here, when there are a plurality of UEs receiving the same MBS service, a base station separately transmits the same MBS data to individual UEs through different UE-specific PDCCHs and UE-specific PDSCHs. That is, the same MBS data is provided to a plurality of UE, but different channels (i.e., PDCCH, PDCCH) are used for each UE.
As described above, in a PTM transmission method, a base station transmits a plurality of group common PDSCHs to a plurality of UEs. Here, a base station can receive UE's HARQ-ACKs for a group common PDSCH through a UE-specific PUCCH resource from a plurality of UEs.
Here, when a transport block (TB) for a multicast PDSCH (or group common PDSCH) is successfully decoded, a UE transmits an ACK as HARQ-ACK information. On the other hand, if a transport block (TB) is not successfully decoded, a UE transmits a NACK as HARQ-ACK information. This HARQ-ACK transmission method is referred to as an ACK/NACK based HARQ-ACK method (mode). In general, a UE may transmit an ACK/NACK based HARQ-ACK using a UE-specific PUCCH resource.
On the other hand, when a NACK only based HARQ-ACK method (mode) is configured for a multicast PDSCH (or group common PDSCH), a UE does not perform PUCCH transmission in case of an ACK and a UE perform PUCCH transmission in case of a NACK. Here, a PUCCH is a group common PUCCH resource, and only NACK can be transmitted as HARQ-ACK information.
Hereinafter, in the present disclosure, a DCI format (or PDCCH) for scheduling reception of a PDSCH carrying an MBS service (i.e., MBS TB) may be referred to as an MBS DCI format (or PDCCH) or a multicast DCI format (or PDCCH). For example, a DCI format (or PDCCH) with a CRC scrambled by a G-RNTI (group-RNTI) or a G-CS-RNTI ((group-configured scheduling-RNTI) scheduling PDSCH reception may be referred to as an MBS DCI format (or PDCCH) or a multicast DCI format (or PDCCH). Here, unless otherwise described in the present disclosure, an MBS DCI format (or PDCCH) or a multicast DCI format (or PDCCH) may include both a group common DCI format (or PDCCH) according to a PTM method for an MBS and a UE specific DCI format (or PDCCH) according to a PTP method for an MBS.
In addition, unless otherwise described in the present disclosure (e.g., distinction between a PDSCH by dynamic scheduling and a PDSCH by SPS), a PDSCH scheduled by an MBS DCI format (or PDCCH) or a multicast DCI format (or PDCCH) (also, a PDSCH scheduled by UE specific DCI format (or PDCCH) of a PTP method) and a group common SPS PDSCH may be collectively referred to as an MBS PDSCH or a multicast PDSCH. In other words, unless otherwise described in the present disclosure, an MBS PDSCH or multicast PDSCH may include both a group common PDSCH according to a PTM method for an MBS and a UE specific PDSCH according to a PTP method for an MBS.
In addition, HARQ-ACK information associated with a multicast (or MBS) DCI format (or PDCCH) or multicast PDSCH may be referred to as MBS HARQ-ACK information or multicast HARQ-ACK information. Unless otherwise described in the present disclosure, such MBS HARQ-ACK information or multicast HARQ-ACK information may be transmitted through a UE specific PUCCH/PUSCH according to a PTP/PTM method or may be transmitted through a group common PUCCH/PUSCH according to a PTM method.
In addition, unless otherwise described in the present disclosure (e.g., distinction between a PDSCH by dynamic scheduling and a PDSCH by SPS), a PDSCH scheduled by a unicast DCI format (or PDCCH) and a UE-specific SPS PDSCH may be collectively referred to as a unicast/UE-specific PDSCH.
In addition, in the present disclosure, when a transport block (TB) for an MBS PDSCH or multicast PDSCH is successfully decoded, a UE may transmit an ACK as HARQ-ACK information. On the other hand, if a TB for an MBS PDSCH or multicast PDSCH is not successfully decoded, a UE may transmit a NACK as HARQ-ACK information. This HARQ-ACK transmission method is referred to as an ACK/NACK based HARQ-ACK method (mode).
On the other hand, if a TB for an MBS PDSCH or multicast PDSCH is successfully decoded, a UE may not transmit HARQ-ACK information (i.e., ACK) through a PUCCH (or PUSCH). On the other hand, if a TB for an MBS PDSCH or multicast PDSCH is not successfully decoded, a UE may transmit a NACK as HARQ-ACK information. This HARQ-ACK transmission method is referred to as an NACK based HARQ-ACK method (mode). In other words, when a NACK only based HARQ-ACK method (mode) is configured, a UE may not transmit a PUCCH (or PUSCH) in case of an ACK, and may transmit a PUCCH (or PUSCH) only in case of a NACK.
In addition, in the present disclosure, a sub-slot, a mini-slot, and a symbol slot all represent a time unit smaller than one slot, and unless clearly distinguished and described for each in the present disclosure, all may be interpreted in the same meaning. Also, all of the above terms may be regarded/interpreted as one or more symbols in a slot.
1. Although not shown in
A. The message/information may be transmitted through any one of uplink control information (UCI), a MAC control element (CE), and an RRC message.
B. An interested MBS service in the message/information may mean either TMGI or G-RNTI included in a DL message received from a base station.
For example, the DL message may be a service availability message including TMGI #1, TMGI #3, TMGI #5 and TMGI #10. If a UE is interested in TMGI #5, the UE may indicate an order of TMGI #5 in the message/information. That is, the UE may report ‘3’ to the base station.
As another example, the DL message may be a service availability message including G-RNTI #1, G-RNTI #3, G-RNTI #5 and G-RNTI #10. If a UE is interested in G-RNTI #10, the UE may indicate an order of G-RNTI #10 in the message/information. That is, the UE may report ‘4’ to the base station.
2. Upon receiving the message/information, a base station may transmit at least one of i) a common frequency resource (CFR) configuration, ii) one or more group common PDSCH configurations including TCI states for one or more G-RNTI value(s), iii) a search space (SS) configuration including TCI states for one or more G-RNTI value(s) to the UE through an RRC message (S901a, S901b).
Although one RRC message is illustrated in
Upon receiving an RRC message from a base station, a UE may configure one or more group common PDSCH (e.g., group common SPS PDSCH) configurations according to the RRC message.
A. An RRC message may be a group common message transmitted on a PTM multicast control channel (MCCH) or a UE-specific message transmitted on a UE-specific dedicated control channel (DCCH).
B. A UE may be configured with at least a G-RNTI value for each MBS CFR or each serving cell. Alternatively, in addition to this, a GC-CS-RNTI (group common-configured scheduling-RNTI) may also be configured, and may be used for activating, retransmitting, or releasing one or more group common SPS configurations.
C. Each PDSCH configuration (e.g., RRC parameter PDSCH-config) may include at least information elements (IE) for multicast and/or broadcast as shown in Table 6 below.
Table 6 illustrates the PDSCH-Config IE used to configure PDSCH parameters.
Table 7 illustrates a description of the fields of the PDSCH-config of
3. When a search space (SS) for a configured CFR is configured, a UE monitors a PDCCH on the SS configured in the CFR configured to receive DCI with a CRC scrambled with a G-RNTI or a G-CS-RNTI (S902a, S902b).
4. If a data unit is available in a Multicast Traffic Channel (MTCH) of an MBS radio bearer (MRB) for an MBS service, according to a service-to-resource mapping, a base station constructs and transmits a transport block (TB) including a data unit for an SPS PDSCH occasion, i) associated with an MTCH of an MRB for an MBS service, ii) associated with a TMGI of an MBS service, iii) associated with a short ID of an MBS service, or iv) associated with a G-RNTI mapped to an MBS service.
In the case of group common dynamic scheduling of a TB, a base station transmits DCI to a UE on a PDCCH (S903a, S903b).
Here, a CRC of the DCI may be scrambled by a G-RNTI, a G-CS-RNTI or a CS-RNTI. Also, a PDCCH may be a group common PDCCH or a UE specific PDCCH.
In
The DCI may include the following information (fields).
In addition, the DCI may include information on a frequency domain resource assignment, a time domain resource assignment, a VRB-to-PRB mapping, and a PRB bundling size indicator, a rate matching indicator, a ZP CSI-RS trigger, a modulation and coding scheme, a new data indicator (NDI), a redundancy version, a HARQ process number, a downlink assignment index, a transmit power control (TPC) command for a scheduled PUCCH, a PUCCH resource Indicator (PRI), a PDSCH-to-HARQ_feedback timing indicator (PDSCH-to-HARQ_feedback timing indicator), antenna port(s), a transmission configuration indication (TCI), an SRS request, a DMRS sequence initialization, and a priority indicator.
In the case of group common dynamic scheduling, a base station may provide a UE with one or more of the following service-to-resource mappings for an MBS service identified by a TMGI or a G-RNTI or a GC-CS-RNTI i) by a group common or UE-specific RRC message or ii) by a group common or UE-specific MAC CE. Data of an MBS service can be carried over an MBS radio bearer (MRB) of an MTCH associated with an MBS service, which is a multicast traffic logical channel. An RRC message may be a group common message transmitted through a PTM Multicast Control Channel (MCCH) or a UE-specific message transmitted through a UE-specific Dedicated Control Channel (DCCH). DCI scheduling a PDSCH carrying MBS service data may also indicate one or more of a short ID, an MTCH ID, an MRB ID, a G-RNTI value, and a TMGI value for an MBS service.
5. If a UE receives DCI with a CRC scrambled by a G-RNTI of interest in receiving, based on i) a mapping between MBS services and a HARQ process number (HPN) indicated in DCI and/or ii) (if available) a mapping between MBS services and an indicated short ID(s) in DCI, a UE may determine an MBS service related to one or more of short ID, MTCH ID, MRB ID, G-RNTI value, and TMGI value for each PDSCH occasion.
A base station may transmit a PDSCH carrying corresponding MBS service data to a UE (S904a, S904b) (In
On the other hand, different from the example of
Then, according to the decoding state of PDSCH transmission, a UE transmits HARQ feedback to a base station.
6. A UE receiving group common DCI indicating PUCCH resource(s) for an MBS HARQ-ACK may transmit a HARQ-ACK to a base station through a PUCCH after receiving a PDSCH scheduled by DCI as follows (S906a).
A. In the case of PTM method 1, group common DCI may indicate a single PUCCH resource indicator (PRI) and a single PDSCH-to-HARQ_feedback timing indicator (K1) for at least an ACK/NACK based HARQ-ACK.
B. In case of UE-specific PUCCH resource allocation for an ACK/NACK based HARQ-ACK for group common DCI, different UEs in a group can be configured with different values of at least of a PUCCH resource and a candidate DL data-UL ACK (e.g., dl-DataToUL-ACK) in a UE-dedicated PUCCH configuration (e.g., PUCCH-config) for multicast or unicast (if PUCCH-config for multicast is not configured).
Different PUCCH resources may be allocated to different UEs by the same PUCCH resource indicator (PRI) and the same PDSCH-to-HARQ_feedback timing indicator (K1) of group common DCI.
C. In case of PTP retransmission, in UE-specific DCI, a PUCCH resource indicator (PRI) and a PDSCH-to-HARQ_feedback timing indicator (K1) can be interpreted based on a PUCCH configuration (e.g. PUCCH-config) for unicast regardless of whether or not a PUCCH configuration (e.g. PUCCH-config) for multicast is configured.
D. A PUCCH Resource Indicator (PRI) may be indicated by group common DCI as follows.
1) Option 1A-1: A list of UE specific PRIs may be included in DCI.
2) Option 1A-2: group common PRI may be included in DCI.
E. K1 (PDSCH-to-HARQ_feedback timing indicator) may be indicated by group common DCI as follows.
1) Option 1B-1: A list of UE specific K1 values may be included in DCI.
As an example, different K1 values may be assigned to different UEs. For example, K1-UE1, K2-UE2, K3-UE3, . . . .
As another example, a K1 value may be shared by multiple UEs (e.g., K1-UE1/UE2, K2-UE3/UE4).
As another example, one K1 value may be a reference and other K1 values may be assigned based on the reference. For example, a list of {K1_ref, K1_offset (offset from reference)} may be indicated in DCI.
For example, UE1 may use K1_ref, UE2 may use K1_ref+K1_offest1, and UE3 may use K1_ref+K1_offest2.
2) Option 1B-2: A group common K1 value may be included in DCI.
In addition, when receiving group common DCI with a CRC scrambled by a G-RNTI and/or UE specific DCI with a CRC scrambled by a C-RNTI, when a Type-1 HARQ-ACK codebook for a PUCCH-config for multicast and/or a PUCCH-config for unicast is configured, a UE may configure Time Domain Resource Allocation (TDRA) to generate a type 1 HARQ-ACK codebook for HARQ-ACK(s) for a group common PDSCH scheduled by group common DCI and/or a UE specific PDSCH scheduled by UE specific DCI.
7. If decoding of a TB on a PDSCH transmission occasion fails, a UE may transmit a HARQ NACK to a base station on a PUCCH resources in a configured UL CFR (S906b).
By using a PUCCH resource, a UE may also transmit a HARQ-ACK for other PDSCH transmissions such as a unicast SPS PDSCH, a dynamic unicast PDSCH, PTP retransmission, and/or a dynamic group common PDSCH. In this case, to multiplex a HARQ-ACK on a PUCCH in a (sub)slot for an SPS PDSCH for multicast, an SPS PDSCH for unicast, a dynamically scheduled multicast PDSCH, and/or a dynamically scheduled unicast PDSCH, a UE may construct a codebook based on one or more options in step 7 above.
If a reference signal received power (RSRP) threshold is configured, a UE may use a NACK only based HARQ-ACK based on a measured RSRP of a serving cell. For example, if the measured RSRP is higher than (or equal to or higher than) the threshold value, a NACK only based HARQ-ACK may be transmitted through a group common PUCCH resource indicated by a PRI of DCI. On the other hand, if the measured RSRP is lower than (or equal to or less than) the threshold, a NACK only based HARQ-ACK may be changed to a HARQ-ACK based HARQ-ACK and transmitted through a UE-specific PUCCH resource indicated by a PRI of DCI.
Meanwhile, if a PDSCH aggregation factor (pdsch-AggregationFactor) is configured for a G-RNTI or a base station indicates a repetition number (repeat number) in DCI, a TB scheduled by group common DCI may be repeated for the Nth HARQ transmission of a TB within each symbol allocation among each PDSCH aggregation factor (pdsch-AggregationFactor) consecutive slots or among each repetition number (repeat number) consecutive slots.
8. A base station receiving a HARQ NACK with a TCI state may retransmit a PDCCH and a PDSCH with a TCI state in a DL CFR configured for TB retransmission. A UE may monitor a group common and/or UE-specific PDCCH with a TCI state on a search space configured in a DL CFR to receive TB retransmission (S907b).
A base station may retransmit a TB to only one of UEs in a group by a UE-specific PDCCH, and other UEs may not receive retransmission of a TB (e.g., because the other UEs successfully received the TB).
9. When a UE receives a PDCCH for retransmission of a TB (S908b), a UE may receive a PDSCH scheduled by DCI of a PDCCH (S909b, S910b).
If a UE successfully decodes a TB on a PDSCH, based on a mapping between an MBS service indicated by DCI and an HPN (HARQ process number) and/or between an MBS service indicated by DCI and a short ID(s) (if available), the UE may consider that the decoded TB is associated with an MTCH, an MRB, a TMGI, a G-RNTI and/or a short ID of an MBS service.
10. If decoding of a TB succeeds in a PDSCH transmission occasion, a UE may transmit a HARQ ACK to a base station through a PUCCH resource in a UL CFR configured according to step 7. On the other hand, if decoding of a TB on a PDSCH transmission occasion fails, a UE may transmit a HARQ NACK to a base station on a PUCCH resource in a configured UL CFR (S911b).
By using a PUCCH resource, a UE may also transmit HARQ-ACKs for other PDSCH transmissions such as a unicast SPS PDSCH, a dynamic unicast PDSCH, PTP retransmission, and/or a dynamic group common PDSCH. In this case, to multiplex HARQ-ACKs on a PUCCH in a (sub)slot for an SPS PDSCH for multicast, an SPS PDSCH for unicast, a dynamically scheduled multicast PDSCH, and/or a dynamically scheduled unicast PDSCH, a UE may construct a codebook based on one or more options in step 7 above.
Meanwhile, an example of
A base station may be a general term for an object that transmits and receives data with a terminal. For example, a base station may be a concept including one or more transmission points (TPs), one or more transmission and reception points (TRPs), etc. Also, a TP and/or a TRP may include a panel of a base station, a transmission and reception unit, etc. In addition, “TRP” may be replaced with expressions such as a panel, an antenna array, a cell (e.g., macro cell/small cell/pico cell, etc.)/a TP (transmission point), base station (base station, gNB, etc.), etc. As described above, TRPs may be classified according to information (e.g., index, ID) on a CORESET group (or CORESET pool). For example, when one UE is configured to transmit/receive with multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one UE. Configuration of such a CORESET group (or CORESET pool) may be performed through higher layer signaling (e.g., RRC signaling, etc.).
Referring to
In the prior art, the UE may receive unicast traffic through a UE-dedicated unicast PDSCH, and receive multicast traffic such as MBS through a group common multicast PDSCH. In this case, the UE may transmit unicast HARQ-ACK information for the unicast PDSCH and multicast HARQ-ACK information for the multicast PDssSCH.
In this regard, the conventional Type 1 codebook based on Frequency Division Multiplexing (FDM) is structured as follows. For example, assume that unicast PDSCH and multicast PDSCH, which are transmitted from the same TRP and have the same priority, are transmitted by FDM. In this case, to construct the Type 1 HARQ-ACK codebook, the UE may support the following operations. The HARQ-ACK bit for all PDSCH occasions over slots in all serving cells related to unicast precedes the HARQ-ACK bit for all PDSCH occasions over slots in all serving cells related to multicast. This is similar to the case of the joint Type 1 codebook for mTRP.
In addition, when the UE reports the capability to support FDM between unicast and multicast in the same slot, the UE may be semi-statically indicated to generate a Type 1 codebook according to the FDM method (i.e., the example method described above). On the other hand, the UE may not expect unicast and multicast to be scheduled in the FDM method.
In addition, the conventional Type 1 codebook based on Time Division Multiplexing (TDM) is structured as follows. For example, if unicast and multicast are TDM, to configure Type 1 HARQ-ACK codebook for unicast and multicast based on ACK/NACK to be multiplexed on the same PUCCH resource, the UE may determine the PDSCH reception candidate occasion(s) based on one of the following methods (method 1 and method 2).
According to the prior art, if unicast transmission and first multicast transmission are FDMed and unicast transmission and second multicast transmission are TDMed at the same time, it is not clear how UE constructs Type 1 HARQ-ACK codebook.
Therefore, in the present disclosure, in a situation where unicast PDSCH and multicast PDSCH are received together based on the FDM method and TDM method, or reception according to the FDM method and TDM method is frequently switched, methods for constructing a Type 1 codebook for HARQ-ACK will be proposed.
Referring to
As shown in
In this regard, when unicast HARQ-ACK and multicast HARQ-ACK for unicast PDSCH (1001) and different multicast PDSCHs (1002, 1003) are configured based on Type 1 codebook, ambiguity arises as to whether the UE will configure the Type 1 codebook based on the FDM method or the TDM method.
Accordingly, in the present disclosure, in a situation where the UE receives unicast PDSCH occasions and multicast PDSCH occasions together in the FDM method and the TDM method, or in a situation where reception according to the FDM method and the TDM method is frequently switched, methods for constructing a Type 1 codebook will be proposed.
Additionally, in the proposed methods of the present disclosure, unicast PDSCH occasion (1001) in
In the following embodiments, unicast ACK/NACK transmission may mean unicast HARQ-ACK transmission for unicast PDCCH/PDSCH, and multicast ACK/NACK transmission may mean multicast HARQ-ACK transmission for multicast PDCCH/PDSCH. Here, multicast HARQ-ACK transmission may be distinguished into NACK only-based HARQ-ACK transmission and ACK/NACK-based HARQ-ACK transmission based on configuration/indication/definition, etc.
In the following embodiments, ‘Type 1 codebook’ may mean Type 1 HARQ-ACK codebook for HARQ-ACK reporting.
In addition, in the following embodiments, ‘TDMed unicast/multicast PDSCH’ may refer to one or more unicast/multicast PDSCH transmitted based on the TDM method, and ‘FDMed unicast/multicast PDSCH’ may refer to one or more unicast/multicast PDSCHs transmitted based on the FDM method.
In addition, in the following embodiments, ‘TDMed Type 1 codebook’ may mean a HARQ-ACK codebook according to unicast/multicast PDSCH(s) transmitted based on the TDM method, that is, a TDM-based Type 1 codebook. ‘FDMed Type 1 codebook’ may mean a HARQ-ACK codebook according to unicast/multicast PDSCH(s) transmitted based on the FDM method, that is, an FDM-based Type 1 codebook.
This embodiment relates to a Type 1 codebook construction method for transmitting one PUCCH.
The examples described below relate to a Type 1 codebook configuration method for unicast/multicast PDSCH(s) transmitted based on the FDM method and/or TDM method, and different Type 1 codebook construction methods may be applied depending on the combination and/or type of method.
The division of examples described below is for convenience of explanation, and may be applied independently or in combination of two or more methods.
Regarding HARQ-ACK codebook configuration, the UE may be configured to construct an FDM-based Type 1 codebook when transmitting FDMed unicast/multicast PDSCH, and may be configured to construct a TDM-based Type 1 codebook when not FDMed unicast/multicast PDSCH transmission.
For example, depending on the settings of the base station, etc., when different PDSCH reception occasions for unicast and multicast are transmitted according to the FDM method, the UE may construct an FDM-based Type 1 codebook. On the other hand, if different PDSCH reception occasions for unicast and multicast are not transmitted according to the FDM method, the UE may construct a TDM-based Type 1 codebook.
In the method according to the example, when FDMed unicast/multicast PDSCH transmission occurs, the UE may assume that that unicast/multicast PDSCH reception according to the TDM method does not occur. Therefore, the UE may construct a Type 1 codebook only for the unicast K1 set to construct ssthe unicast HARQ-ACK bit. For example, UE determines PDSCH reception candidate occasions for slot timing values K1 in K1 set for unicast based on PDSCH TDRA set for unicast, in order to determine HARQ-ACK bits for all the PDSCH occasions over all the slots for all serving cells for unicast which precede HARQ-ACK bits for all the PDSCH occasions over all the slots for all serving cells for multicast.
Regarding HARQ-ACK codebook configuration, the UE may be configured to construct a TDM-based Type 1 codebook when transmitting TDMed unicast/multicast PDSCH, and may be configured to construct an FDM-based Type 1 codebook when it is not TDMed unicast/multicast PDSCH transmission.
For example, depending on the configuration of the base station, etc., when different PDSCH reception occasions for unicast and multicast are transmitted according to the TDM method, the UE may construct a TDM-based Type 1 codebook. On the other hand, when different PDSCH reception occasions for unicast and multicast are not transmitted according to the TDM method, the UE may construct an FDM-based Type 1 codebook.
In the method according to this example, when TDMed unicast/multicast PDSCH transmission occurs, the UE may assume that unicast/multicast PDSCH reception according to the FDM method does not occur. For example, UE determines PDSCH reception candidate occasions for slot timing values K1 in the intersection of K1 set for unicast (termed set A) and K1 set for multicast (termed set B), based on union of the PDSCH TDRA sets in order to determine Type 1 HARQ-ACK codebook.
Regarding HARQ-ACK codebook configuration, the UE may concatenate a TDM-based Type 1 codebook configured assuming that there is no FDMed unicast/multicast PDSCH and an FDM-based Type 1 codebook configured assuming that there is no TDMed unicast/multicast PDSCH.
For example, depending on the settings of the base station, etc., the UE may configure a TDM-based Type 1 codebook assuming that there is no FDMed unicast/multicast PDSCH, and the UE may separately configure an FDM-based Type 1 codebook assuming that there is no TDMed unicast/multicast PDSCH. The UE may construct a HARQ-ACK codebook by concatenating each Type 1 codebook.
At this time, the HARQ-ACK codebook may be concatenated in the order of TDM-based Type 1 codebook+FDM-based Type 1 codebook, or in the order of FDM-based Type 1 codebook+TDM-based Type 1 codebook.
In relation to configuring the HARQ-ACK codebook, a method of distinguishing between PUCCH resources to which the TDM method is applied and PUCCH resources to which the FDM method is applied may be considered.
For example, the base station may be configured to distinguish between PUCCH resources applying the TDM method and PUCCH resources applying the FDM method. Therefore, if it is determined that HARQ-ACK is transmitted on a specific PUCCH resource, the UE may configure and transmit the HARQ-ACK codebook based on a method of mapping to a specific PUCCH resource. That is, in PUCCH resources applying the TDM method, the UE may transmit a TDM-based Type 1 codebook configured assuming that there is no FDMed unicast/multicast PDSCH. On the other hand, in PUCCH resources applying the FDM method, the UE may transmit an FDM-based Type 1 codebook configured assuming that there is no TDMed unicast/multicast PDSCH.
In relation to the above-described example, PUCCH resources applying the TDM method and PUCCH resources applying the FDM method may be distinguished based on the following methods.
A method of activating/deactivating/switching a TDM-based Type 1 codebook or an FDM-based Type 1 codebook through specific signaling (e.g., DCI, MAC-CE, etc.) may be considered.
For example, the base station may activate/deactivate a specific UE or a specific UE group to configure a TDM-based Type 1 codebook or an FDM-based Type 1 codebook, by transmitting a UE dedicated DCI, a UE common DCI, a UE dedicated MAC-CE, and/or a UE common MAC-CE. Alternatively, through the above-described signaling, it is possible to indicate (to a specific UE or a specific UE group) to switch from the FDM-based Type 1 codebook configuration to the TDM-based Type 1 codebook configuration, or vice versa.
In this case, depending on the settings of the base station, etc., the UE that has received the above-described specific signaling (e.g., DCI, MAC-CE, etc.) may transmit HARQ-ACK information to inform the base station of whether to receive. Through the HARQ-ACK information, the base station may check whether the UE has received the specific signaling described above.
A method of separately constructing a Type 1 codebook assuming only unicast PDSCH and a Type 1 codebook assuming only multicast PDSCH and concatenating them may also be considered.
For example, the UE may construct the first Type 1 codebook only by receiving unicast PDSCH(s), assuming that there is no multicast PDSCH reception (according to the prior art, etc.). Additionally, the UE may construct the second Type 1 codebook only by receiving multicast PDSCH(s), assuming that there is no unicast PDSCH reception (according to prior art, etc.). Afterwards, the UE may construct a HARQ-ACK codebook by concatenating each Type 1 codebook.
At this time, the HARQ-ACK codebook may be concatenated in the order of Type 1 codebook according to unicast+Type 1 codebook according to multicast, or in the order of Type 1 codebook according to multicast+Type 1 codebook according to unicast.
This embodiment relates to a Type 1 codebook construction method for transmitting two PUCCHs.
The examples described below relate to a Type 1 codebook construction method for unicast/multicast PDSCH(s) transmitted based on the FDM method and/or TDM method, and different Type 1 codebook construction methods may be applied depending on the combination and/or type of method.
The division of examples described below is for convenience of explanation, and may be applied independently, or two or more methods may be applied in combination.
A method of transmitting the Type 1 codebook assuming only unicast PDSCH and the Type 1 codebook assuming only multicast PDSCH through separate PUCCHs may be considered.
For example, the UE may construct the first Type 1 codebook only by receiving unicast PDSCH(s), assuming that there is no multicast PDSCH reception (according to the prior art, etc.). Additionally, the UE may construct the second Type 1 codebook only by receiving multicast PDSCH(s), assuming that there is no unicast PDSCH reception (according to prior art, etc.). Thereafter, the UE may transmit the first Type 1 codebook through the first PUCCH resource (i.e., PUCCH 1) and the second Type 1 codebook through the second PUCCH resource (i.e., PUCCH 2).
A method of transmitting a TDM-based Type 1 codebook configured assuming that there is no FDMed unicast/multicast PDSCH and an FDM-based Type 1 codebook configured assuming that there is no TDMed unicast/multicast PDSCH through separate PUCCHs may be considered.
For example, depending on the configuration of the base station, etc., the UE may construct a TDM-based Type 1 codebook assuming that there is no FDMed unicast/multicast PDSCH, and may separately construct an FDM-based Type 1 codebook assuming that there is no TDMed unicast/multicast PDSCH. Afterwards, the corresponding UE may transmit each Type 1 codebook through different PUCCH resources.
This embodiment relates to a Type 1 codebook construction method according to reduced PDSCH reception capability.
As in
As another example, the base station may transmit unicast PDSCH occasion and multicast PDSCH occasion for G-RNTI #1 in TDM method, and may transmit multicast PDSCH occasion (1001) for G-RNTI #1 and multicast PDSCH occasion (1003) for G-RNTI #2 in FDM method.
In this case, if the UE wants to receive different multicast PDSCHs or if the UE capability satisfies this operation (i.e., is sufficient), the UE may receive both a unicast PDSCH and two different multicast PDSCHs. At this time, the UE may be configured to construct unicast HARQ-ACK and multicast HARQ-ACK for the above-described unicast PDSCH and different multicast PDSCHs based on Type 1 codebook, and the UE may construct configure a Type 1 codebook according to one or more of the above-described methods (e.g., Example 1 and Example 2).
Additionally, as mentioned above, in
In this case, if the UE wants to receive different multicast PDSCHs or if the UE capability satisfies this operation (i.e., is sufficient), the UE may receive all three different multicast PDSCHs. At this time, the UE may be configured to construct multicast HARQ-ACKs for the different multicast PDSCHs described above based on the Type 1 codebook, and tye UE may construct a Type 1 codebook according to one or more of the above-described methods (e.g., Example 1 and Example 2). In this case, a Type 1 codebook may be constructed by replacing the unicast PDSCH with a multicast PDSCH for G-RNTI #3 in the above-described methods.
However, if the UE has reduced UE capability (e.g., when there are two PDSCHs that may be received simultaneously, etc.), the base station and/or UE may be configured to operate according to the method(s) according to examples described below.
The division of examples described below is for convenience of explanation, and may be applied independently, or two or more methods may be applied in combination.
A method in which the UE skips or drops reception of a specific PDSCH may be considered.
For example, the terminal may be configured/defined to give up reception of PDSCHs that exceed its reception capability and construct a HARQ-ACK codebook only for the received PDSCH(s). That is, HARQ-ACK information for the PDSCH that the UE gave up receiving is not included in the HARQ-ACK codebook.
As an example, if the UE supports a UE capability that can only receive two PDSCHs at the same time, the UE may drop one multicast PDSCH in the situation of
As another example, when three multicast PDSCHs are transmitted according to the TDM method and the FDM method, the UE may drop a multicast PDSCH which is TDMed with any multicast PDSCH. In this case, the UE may receive two FDMed multicast PDSCHs and construct an FDM-based Type 1 codebook only for the actually received PDSCHs. On the other hand, the UE may drop a multicast PDSCH which is FDMed with any multicast PDSCH. In this case, the UE may receive two TDMed multicast PDSCHs and configure a TDM-based Type 1 codebook only for the actually received PDSCHs.
In relation to the above-described examples, the UE may select and skip or drop a PDSCH that exceeds the reception capability based on at least one of the methods (methods 3a to 3k) described below. For convenience of explanation, the following methods are assumed to be capable of receiving only two PDSCHs, but of course they may be extended and applied even when the UE is capable of receiving three or more PDSCHs.
It may be configured/defined to give priority to PDSCH reception with high priority (HP). Accordingly, the UE may skip/drop PDSCH reception with low priority (LP) that exceeds the UE capability. For example, if the priority index of two DCIs indicates HP and the priority index of the remaining DCI indicates LP among each DCI scheduling three PDSCHs, the UE may not receive the PDSCH scheduled by the DCI indicating LP.
It may be configured/defined so that reception of Unicast PDSCH takes priority. Accordingly, the UE may skip/drop multicast PDSCH reception that exceeds the UE capability. For example, when two unicast PDSCHs and one multicast are transmitted, a UE that can receive only two PDSCHs may skip/drop receiving the multicast PDSCH. For another example, when one unicast PDSCH and two multicast PDSCHs are transmitted as shown in
It may be configured/defined so that reception of the PDSCH with a low G-RNTI value is given priority. Accordingly, the UE may skip/drop PDSCH reception for a high RNTI value that exceeds the UE capability. For example, when a PDSCH with G-RNTI=10, a PDSCH with G-RNTI=20, and a PDSCH with G-RNTI=50 are transmitted, respectively, the UE may skip/drop PDSCH reception corresponding to the highest G-RNTI value, G-RNTI=50.
Alternatively, conversely, reception of the PDSCH with a high G-RNTI value may be configured/defined to be prioritized. Accordingly, the UE may skip/drop PDSCH reception for a low RNTI value that exceeds the UE capability. For example, when a PDSCH with G-RNTI=10, a PDSCH with G-RNTI=20, and a PDSCH with G-RNTI=50 are transmitted, respectively, the UE may skip/drop PDSCH reception corresponding to the lowest G-RNTI value, G-RNTI=10.
The base station may configure priorities for receiving multiple PDSCHs through RRC signaling (e.g., RRC message, etc.) and/or MAC-CE. Accordingly, the UE may skip/drop low-priority PDSCH reception that exceeds the UE capability.
For example, when a PDSCH with G-RNTI=10, a PDSCH with G-RNTI=20, and a PDSCH with G-RNTI=50 are each transmitted, the base station may assign priorities in the order of G-RNTI=10, 50, 20, and may indicate this information to the UE through an RRC message and/or MAC-CE. In this case, the UE may skip/drop reception of the PDSCH corresponding to the lowest priority G-RNTI=20.
For another example, when a unicast PDSCH, a PDSCH with G-RNTI=22, and a PDSCH with G-RNTI=55 are transmitted, respectively, the base station may assign priorities in the following order: G-RNTI=55, unicast, G-RNTI=22, and may indicate this information to the UE through an RRC message and/or MAC-CE. In this case, the UE may skip/drop reception of the PDSCH corresponding to the lowest priority G-RNTI=22.
The UE may report the priority for receiving multiple PDSCHs to the base station, and the UE may skip/drop low-priority PDSCH reception that exceeds the UE capability according to the report of UE.
For an example, when a PDSCH with G-RNTI=10, a PDSCH with G-RNTI=20, and a PDSCH with G-RNTI=50 are each transmitted, the UE may assign/configure priorities in the following order: G-RNTI=10, 50, 20, and report this information to the base station. In this case, the UE may skip/drop reception of the PDSCH corresponding to the lowest priority G-RNTI=20.
For another example, when a unicast PDSCH, a PDSCH with G-RNTI=22, and a PDSCH with G-RNTI=55 are transmitted, respectively, the UE may assign/determine priority in the following order: G-RNTI=55, unicast, G-RNTI=22, and report information about this to the base station. In this case, the UE may skip/drop reception of the PDSCH corresponding to the lowest priority G-RNTI=22.
Depending on the configuration of the base station, etc., when there are multiple Common Frequency Resource (CFR) associated BWPs or CFRs, it may be configured/defined to give priority to PDSCH reception scheduled by a low BWP index or low CFR index. Accordingly, the UE may skip/drop PDSCH reception corresponding to a high BWP index or a high CFR index that exceeds the UE capability. Alternatively, conversely, depending on the configuration of the base station, etc., if there are multiple CFR-related BWPs or CFRs, it may also be configured/defined to give priority to PDSCH reception scheduled by a high BWP index or high CFR index. Accordingly, the UE may skip/drop PDSCH reception corresponding to a low BWP index or low CFR index that exceeds the UE capability.
Depending on the configuration of the base station, etc., it may be configured/defined so that PDSCH reception with a low lowest PRB (index) takes priority over PDSCH reception with a high lowest PRB (index). Accordingly, the UE may skip/drop PDSCH reception with the lowest PRB (index) that exceeds the UE capability. Alternatively, conversely, it may be configured/defined so that PDSCH reception with a high lowest PRB (index) has priority over PDSCH reception with a low lowest PRB (index). Accordingly, the UE may skip/drop PDSCH reception with the lowest PRB (index) that exceeds the UE capability.
PDSCH reception of PCell/PSCell (i.e., Special Cell, SpCell) may be configured/defined to take priority. Accordingly, the UE may skip/drop PDSCH reception of the SCell that exceeds the UE capability. Here, PCell/PSCell and SCell may refer to a primary cell, primary secondary cell, and secondary cell, respectively, composed of carrier aggregation (CA). For example, when different multicase PDSCHs are transmitted to the CFR of the PCell/PSCell and the CFR of the SCell, respectively, the UE may receive the multicast PDSCH transmitted in the CFR of the PCell/PSCell and skip/drop PDSCH reception in the SCell CFR that exceeds the UE capability.
It may be configured/defined to prioritize PDSCH reception of a Master Cell Group (MCG) cell. Accordingly, the UE may skip/drop PDSCH reception of a Secondary Cell Group (SCG) cell that exceeds the UE capability. Here, MCG and SCG may refer to a cell group configured in a Dual connectivity (DC) relationship. As an example, when different multicast PDSCHs are transmitted through the CFR of an MCG cell and the CFR of an SCG cell, respectively, the UE may receive the multicat PDSCH transmitted through the CFR of the MCG cell and may skip/drop PDSCH reception on the CFR of the SCG cell that exceeds the UE capability.
It may be configured/defined to prioritize PDSCH reception of cells with a low cell index. Accordingly, the UE may skip/drop PDSCH reception of a cell with a high cell index exceeding the UE capability. Alternatively, conversely, it may be configured/defined to prioritize PDSCH reception of cells with a high cell index. Accordingly, the UE may skip/drop PDSCH reception of a cell with a low cell index that exceeds the UE capability.
It may be configured/defined to repair the PDSCH of an activated cell. Accordingly, the UE may skip/drop PDSCH reception of a deactivated cell that exceeds the UE capability.
A method in which the base station performs scheduling according to the UE capability may be considered. That is, the base station may schedule the UE so that it does not skip/drop PDSCH reception, considering the reduced UE capability.
For example, when the base station schedules unicast PDSCH transmission and two multicast PDSCH transmission, the base station may schedule transmission for the first multicast PDSCH with low priority to be performed only in TDM method with unicast PDSCH transmission. Accordingly, HARQ-ACK information for the first multicast PDSCH may always be configured to construct/generate HARQ-ACK information for the unicast PDSCH and a TDM-based Type 1 codebook. On the other hand, the base station may schedule the second multicast PDSCH to be transmitted only in FDM method with the first multicast PDSCH. Accordingly, when the first multicast PDSCH and the second multicast PDSCH are transmitted together, the UE may construct/generate an FDM-based Type 1 codebook. At this time, the terminal may construct/generate the HARQ-ACK codebook by constructing/generating multicast HARQ-ACKs for the first multicast PDSCH and the second multicast PDSCH into separate codebooks.
Alternatively, when the unicast PDSCH, the first multicast PDSCH, and the second multicast PDSCH are all transmitted together, the UE may construct/generate a TDM-based Type 1 codebook for the unicast PDSCH and the first multicast PDSCH, and may separately configure/generate an FDM-based Type 1 codebook for the unicast PDSCH and the second multicast PDSCH. That is, the UE may construct/generate the HARQ-ACK codebook through the following steps (step 1 and step 2).
As an example, in the above-described method, when the base station wants to transmit a unicast PDSCH, a first multicast PDSCH, and a second multicast PDSCH, Scheduling may be configured/defined to be performed based on the following constraints (constraints 1 to 4).
The base station may inform the UE of the above-described restrictions through higher layer signaling (e.g., RRC signaling/messaging, etc.). Based on this, the UE may be configured to construct a Type 1 codebook according to the TDM method and/or FDM method.
A method of constructing a codebook may be considered by considering reception of all PDSCHs transmitted regardless of whether the UE receives the PDSCH. Referring to the unicast/multicast PDSCH(s) transmission in
In other words, regardless of the transmission method of the base station and whether the UE actually receives it, the UE may always configure the codebook as if it has received three PDSCHs. As an example, in a situation where the unicast PDSCH, the first multicast PDSCH, and the second multicast PDSCH are all transmitted or can be transmitted, if the UE may simultaneously receive only up to two FDM-based or TDM-based PDSCHs, the terminal may select and skip/drop one PDSCH that exceeds the reception capability according to the method(s) in Embodiment 3-1 described above.
However, unlike the above-described embodiment 3-1, in embodiment 3-3, the UE may construct/generate a codebook based on the N PDSCHs configured by the base station regardless of actual reception. For example, when N is 3, the UE may construct a codebook by assuming that it always receives 3 PDSCHs, even when it actually receives only 2 PDSCHs (i.e., Type 1 codebook)s. Alternatively, the UE may construct a codebook assuming that three PDSCHs have been received only when scheduling for each of the three PDSCH transmissions is received through DCI.
Additionally/alternatively, when the unicast PDSCH, the first multicast PDSCH and the second multicast PDSCH are transmitted, the UE may skip/drop one PDSH that exceeds the reception capability according to the method(s) in Embodiment 3-1 described above.
For example, if the UE skips/drops the second multicast PDSCH, the UE may receive the unicast PDSCH and the first multicast PDSCH according to the TDM method, and may construct a TDM-based Type 1 codebook by assuming that the unicast PDSCH, the first multicast PDSCH, and the second multicast PDSCH are all received according to the TDM method. Alternatively, the unicast PDSCH and the first multicast PDSCH are transmitted according to the TDM method, the UE may construct a Type 1 codebook (according to the method described in Embodiment 3-2 above) by assuming that the second multicast PDSCH is scheduled according to the FDM method for the unicast PDSCH and the first multicast PDSCH. At this time, the UE may indicate HARQ-ACK information for the second multicast PDSCH that was not actually received as NACK in the Type 1 codebook (i.e., Type 1 HARQ-ACK codebook).
For another example, if the UE skips/drops the first multicast PDSCH, the UE may receive the unicast PDSCH and the second multicast PDSCH according to the FDM method, and may construct an FDM-based Type 1 codebook by assuming that the unicast PDSCH, the first multicast PDSCH, and the second multicast PDSCH are all received according to the FDM method. Alternatively, the unicast PDSCH and the second multicast PDSCH are transmitted according to the FDM method, the UE may construct a Type 1 codebook (according to the method described in Embodiment 3-2 above) by assuming that the first multicast PDSCH is scheduled according to the TDM method with respect to the unicast PDSCH. At this time, the UE may indicate HARQ-ACK information for the first multicast PDSCH that was not actually received as NACK in the Type 1 codebook (i.e., Type 1 HARQ-ACK codebook).
A method of constructing a HARQ-ACK codebook for M PDSCHs of a UE with N PDSCH reception capabilities will be described. If the UE has the ability to receive up to N FDMed unicast/multicast PDSCHs, the base station may be configured to construct up to M FDM-based HARQ-ACK codebooks. Here, M may be less than, greater than, or equal to N.
At this time, when N or more FDMed unicast/multicast PDSCHs are scheduled, the UE may drop reception of PDSCHs exceeding N. If M is greater than N, the UE may give up receiving more than N PDSCHs, and configure/determine all HARQ-ACK information for the PDSCHs for which reception was given up as NACK. On the other hand, if M is less than N, the base station may configure a specific rule for the UE and configure/indicate the UE to transmit HARQ-ACK information according to the specific rule. At this time, the specific rule may be configured/designated as a higher layer signaling (e.g., RRC message, etc.) or as a rule in the standard specification.
For example, if M=2 and N=3, a first example of base station configurations and rules may be as follows.
The first multicast PDSCH and the second multicast PDSCH may be transmitted only by FDM. In this case, the UE may construct two separate Type 1 codebooks for each of the first multicast PDSCH and the second multicast PDSCH according to the FDM-based Type 1 codebook construction method.
As a specific example, for the first Type 1 codebook, the UE may determine PDSCH reception candidate occasions for the slot timing value K1 that corresponds to set A but not set B, based on the PDSCH TDRA set for the first multicast PDSCH. As another specific example, for the second Type 1 codebook, the UE may determine PDSCH reception candidate occasions for the slot timing value K1 that corresponds to set B but does not correspond to set A, based on the PDSCH TDRA set for the second multicast PDSCH. In the examples, set A is the K1 set for the first multicast PDSCH, and set B is the K1 set for the second multicast PDSCH. Additionally, when the UE constructs an FDM-based Type 1 codebook, the first Type 1 codebook may precede the second Type 1 codebook.
The unicast PDSCH and the first multicast PDSCH may be transmitted only using the TDM method. In this case, the UE may construct one TDM-based Type 1 codebook.
When the unicast PDSCH, the first multicast PDSCH, and the second multicast PDSCH are transmitted, it may be configured/defined that the unicast PDSCH and the first multicast PDSCH are scheduled according to the TDM method, and the first multicast PDSCH is scheduled only by the FDM method for the unicast PDSCH and the first multicast PDSCH. In this case, the UE may construct a TDM-based Type 1 codebook with HARQ-ACK information for the unicast PDSCH and the first multicast PDSCH, and the UE may construct two separate Type 1 codebooks for the HARQ-ACK information for the first multicast PDSCH with the TDM-based Type 1 codebook configured above and the FDM-based Type 1 codebook.
For another example, when M=2 and N=3, a second example of base station configurations and rules may be as follows.
The first multicast PDSCH and the second multicast PDSCH may be transmitted only by TDM method. In this case, the UE may construct one TDM-based Type 1 codebook.
The unicast PDSCH and the first multicast PDSCH may be transmitted using only the FDM method. In this case, the UE may construct two separate Type 1 codebooks for each of the unicast PDSCH and the first multicast PDSCH according to the FDM-based Type 1 codebook construction method.
As a specific example, for the first Type 1 codebook, the UE may determine PDSCH reception candidate occasions for the slot timing value K1 that corresponds to set A but not set B, based on the PDSCH TDRA set for the unicast PDSCH. As another specific example, for the second Type 1 codebook, the UE may determine PDSCH reception candidate occasions for the slot timing value K1 that corresponds to set B but does not correspond to set A, based on the PDSCH TDRA set for the (first) multicast PDSCH. In the examples, set A is the K1 set for the unicast PDSCH, and set B is the K1 set for the (first) multicast PDSCH. Additionally, when the UE construct an FDM-based Type 1 codebook, the first Type 1 codebook may precede the second Type 1 codebook.
When the unicast PDSCH, the first multicast PDSCH, and the second multicast PDSCH are transmitted, it may be configured/defined that the first multicast PDSCH and the second multicast PDSCH are transmitted according to the TDM method, and the unicast PDSCH is transmitted only by the FDM method for the first multicast PDSCH and the second multicast PDSCH. In this case, the UE may construct a TDM-based Type 1 codebook with HARQ-ACK information for the first multicast PDSCH and the second multicast PDSCH, and the UE may construct two separate Type 1 codebooks for the HARQ-ACK information for the unicast PDSCH, including the TDM-based Type 1 codebook configured above and the FDM-based Type 1 codebook.
Additionally/alternatively, if the method and/or rules configured by the base station are not satisfied, the UE may drop the corresponding HARQ-ACK information without including it in the codebook (i.e., HARQ-ACK codebook). At this time, the UE shall to drop HARQ-ACK for PDSCH reception that cannot be included (i.e., cannot be included) in the corresponding codebook.
For example, in the first example of Embodiment 3-4 described above, when the unicast PDSCH and the two multicast PDSCHs are scheduled using only the FDM method, the UE may determine that it does not satisfy the rule corresponding to the first example configured by the base station, and may drop the HARQ-ACK for one PDSCH among three PDSCH receptions. In other words, the unicast PDSCH and the first multicast PDSCH shall be transmitted according to the TDM method, but since the scheduling is against the rules determined/configured by the base station, HARQ-ACK transmission for the first multicast PDSCH is dropped, and HARQ-ACK information for the corresponding PDSCH is not included in the HARQ-ACK codebook. Therefore, in this case, the UE may construct an FDM-based Type 1 codebook by assuming that only the unicast PDSCH and the second multicast PDSCH are received using the FDM method. Additionally/alternatively, in this case, the UE may be configured to drop reception of the first multicast PDSCH. Alternatively, the UE may be configured to receive the first multicast PDSCH if possible depending on the terminal capability, but transmit HARQ-ACK for the unicast PDSCH and the second multicast PDSCH.
This embodiment relates to a method of constructing a Type 1 codebook according to the K1 set for each G-RNTI group related to multicast PDSCH. Here, in relation to PDSCH reception, K1 may mean a slot timing value based on the scheduling DCI.
The base station may configure different K1 sets and TDRA sets for transmission based on different G-RNTIs, and may also configure different K1 sets and TDRA sets for each G-RNTI group containing multiple G-RNTIs. Here, the TDRA set may be related to time resource allocation for PDSCH reception.
At this time, when the K1 set is configured for each PUCCH configuration (e.g., PUCCH-Config), a PUCCH configuration may be configured for each G-RNTI, or a PUCCH configurations may be configured for each G-RNTI group. If the base station configures the K1 set and TDRA set as described above, the UE may configure a TDM-based Type 1 codebook through the following methods (method 4a and method 4b), considering the intersection between different G-RNTI-based transmissions.
Regarding unicast and multicast according to the TDM method, in order to construct Type 1 HARQ-ACK codebook for unicast and multicast based on ACK/NACK to be multiplexed on the same PUCCH resource, the UE may determine the PDSCH reception candidate occasion(s) based on at least one of the following examples. The following examples relate to the slot timing value K1 for determining PDSCH reception candidate occasion(s).
Example 1) For slot timing values K1, K1 in the intersection of K1 set for unicast PDSCH (termed set A) K1 set for first multicast PDSCH (termed set B), and K1 set for second multicast PDSCH (termed set C), based on union of the PDSCH TDRA sets
Example 2) For slot timing values K1, K1 in the intersection of K1 set for unicast PDSCH (termed set A) and K1 set for first multicast PDSCH or second multicast PDSCH (termed set B or C), based on union of the PDSCH TDRA sets
Example 3) For slot timing values K1, K1 in the intersection of K1 set for first multicast PDSCH (termed set B) and K1 set for second multicast PDSCH (termed set C), based on union of the PDSCH ssTDRA sets
Example 4) For slot timing values K1, K1 in set A but not in set B and C, based on PDSCH TDRA set for unicast
Example 5) For slot timing values K1, K1 in set B but not in set A, based on PDSCH TDRA set for first multicast PDSCH
Example 6) For slot timing values K1, K1 in set C but not in set A, based on PDSCH TDRA set for second multicast PDSCH
For TDM-ed unicast and multicast, for Type-1 HARQ-ACK codebook construction for ACK/NACK-based unicast and multicast to be multiplexed in the same PUCCH resource, the UE may determine PDSCH reception candidate occasions for slot timing values K1 in the union of K1 set for unicast PDSCH, K1 set for first multicast PDSCH and K1 set for second multicast PDSCH, based on the union of the PDSCH TDRA sets.
Additionally/alternatively, since the above-described K1 set is included in the PUCCH configuration (e.g., PUCCH-config), it may not be configured differently for each G-RNTI. Therefore, if the K1 set may be different for each G-RNTI group, For multicast according to the TDM method (i.e., TDMed multicast PDSCHs), methods (e.g., method 4a, method 4b) as described above may be required.
For example, in this case, when referring to methods of constructing a conventional TDM-based Type 1 codebook (e.g., Method 1 and Method 2), as in Method 1, intersection between different G-RNTI-based transmissions may be considered, and the UE may determine the PDSCH reception candidate occasion(s) by referring to Method 4a above. On the other hand, considering Method 2, there is no significant difference from the TDMed unicast/multicast case. The UE may determine the PDSCH reception candidate occasion(s) by referring to Method 4b above.
This embodiment relates to a method of constructing a HARQ-ACK codebook based on a sub-codebook (i.e., sub HARQ-ACK codebook), when unicast/multicast PDCCH/PDSCH transmission is supported in a multiple TRP (M-TRP) situation.
In this embodiment, the M-TRP method based on two TRPs is described, but this is for convenience of explanation and may be extended and applied to the M-TRP method based on multiple TRPs (e.g., three or more TRPs).
When M-TRP supports multicast PDCCH/PDSCH transmission, the following cases (hereinafter, Case 5a to Case 5e) may occur.
(Case 5a) The first TRP may be configured to transmit unicast PDSCH and multicast PDSCH, and the second TRP may be configured to transmit only unicast PDSCH. In this case, the UE may construct the first sub-codebook by multiplexing the HARQ-ACK information for the unicast PDSCH and multicast PDSCH of the first TRP, and the UE may construct HARQ-ACK information for the unicast PDSCH of the second TRP into a second sub-codebook.
(Case 5b) The first TRP may be configured to transmit unicast PDSCH and multicast PDSCH, and the second TRP may be configured to transmit unicast PDSCH and multicast PDSCH. Here, different multicast PDSCHs may correspond to M-TRP transmission based on the same G-RNTI, or may correspond to different single TRP (S-TRP) transmission based on different G-RNTI. In this case, the UE may construct the first sub-codebook by multiplexing the HARQ-ACK information for the unicast PDSCH and multicast PDSCH of the first TRP, and the UE may construct a second sub-codebook by multiplexing HARQ-ACK information for the unicast PDSCH and multicast PDSCH of the second TRP.
(Case 5c) The first TRP may be configured to transmit a unicast PDSCH, and the second TRP may be configured to transmit a multicast PDSCH. In this case, the UE may construct the HARQ-ACK information for the unicast PDSCH of the first TRP as the first sub-codebook, and the UE may construct HARQ-ACK information for the multicast PDSCH of the second TRP into a second sub-codebook.
(Case 5d) The first TRP may be configured to transmit a unicast PDSCH, and the second TRP may be configured to transmit multiple multicast PDSCHs. In this case, the UE may construct the HARQ-ACK information for the unicast PDSCH of the first TRP as the first sub-codebook, and the UE may construct a second sub-codebook by multiplexing HARQ-ACK information for multiple multicast PDSCHs of the second TRP.
(Case 5e) The first TRP may be configured to transmit a unicast PDSCH and multiple multicast PDSCHs, and the second TRP may be configured to transmit only a unicast PDSCH. In this case, the UE may construct the first sub-codebook by multiplexing the unicast PDSCH of the first TRP and HARQ-ACK information for multiple multicast PDSCHs, and the UE may construct HARQ-ACK information for the unicast PDSCH of the second TRP into a second sub-codebook.
The UE may construct a sub-codebook for each TRP as described above, and the UE may construct different sub-codebooks (e.g., the first sub-codebook and the second sub-codebook) with separate coding. The UE may construct the different sub-codebooks into one HARQ-ACK codebook and transmit it through one PUCCH. At this time, the base station may assign/configure whether the corresponding PUCCH will be transmitted through the first TRP (i.e., TRP 1) or the second TRP (i.e., TRP 2).
Alternatively, the different sub-codebooks described above may be transmitted through different PUCCHs. As a specific example, the UE may transmit the first sub-codebook through the first PUCCH (i.e., PUCCH 1) and transmit the second sub-codebook through the second PUCCH (i.e., PUCCH 2). At this time, the first PUCCH may be configured to be transmitted uplink to the first TRP, and the second PUCCH may be configured to be transmitted uplink to the second TRP.
Additionally/alternatively, according to base station configurations and/or specific rules, or the like, HARQ-ACK information for the multicast PDSCH transmitted by two TRPs may be included in only one sub-codebook and transmitted through one TRP.
That is, when the first TRP transmits at least one multicast PDSCH and the second TRP transmits at least one multicast PDSCH, the UE may construct the first sub-codebook or the second sub-codebook by multiplexing HARQ-ACK information for the multicast PDSCH of the first TRP and the second TRP. At this time, the first sub-codebook may be configured to be transmitted uplink to the first TRP, and the second sub-codebook may be configured to be transmitted uplink to the second TRP.
Additionally/alternatively, the sub-codebook construction method related to unicast PDSCH and the sub-codebook configuration method related to multicast PDSCH may be configured independently. For example, depending on base station configurations and/or specific rules, or the like, HARQ-ACK information for the unicast PDSCH transmitted by the two TRPs may be configured to be transmitted to both TRPs respectively, and HARQ-ACK information for all multicast PDSCHs transmitted by two TRPs may be configured to be transmitted only to one configured/assigned TRP. For other examples, additionally/alternatively, depending on base station configurations and/or specific rules, etc. HARQ-ACK information for all unicast PDSCHs transmitted by two TRPs may be configured to be transmitted to a specific TRP (e.g., the first TRP), and HARQ-ACK information for all multicast PDSCHs transmitted by two TRPs may be configured to be transmitted to the remaining TRP (e.g., the second TRP).
In step S1110, the UE may receive at least one of the first unicast PDSCH or the first multicast PDSCH. In this case, the UE may receive the corresponding PDSCH(s) based on the first QCL RS, herein, the first QCL RS may be related/corresponding to the first TRP in the above-described embodiments (e.g., Embodiments 1 to 5, especially Embodiment 5).
In step S1120, the UE may receive at least one of the second unicast PDSCH or the second multicast PDSCH. In this case, the UE may receive the corresponding PDSCH(s) based on the second QCL RS, herein, the second QCL RS may be related/corresponding to the second TRP in the above-described embodiments (eg, Embodiments 1 to 5, especially Embodiment 5).
Step S1110 and step S1120 may be performed simultaneously or independently and may correspond to the M-TRP-based unicast/multicast PDSCH transmission/reception operation in the above-described embodiments (e.g., Embodiments 1 to 5, especially Embodiment 5).
Afterwards, the UE may transmit HARQ-ACK information through one or more PUCCH (resources) based on the received PDSCH(s). As in the above-described embodiments (e.g. Examples 1 to 5, especially Embodiment 5), the HARQ-ACK information may include a first sub-HARQ-ACK codebook and a second sub-HARQ-ACK codebook determined based on the first unicast PDSCH, first multicast PDSCH, second unicast PDSCH, and/or second multicast PDSCH.
Here, as in the above-described embodiments (e.g. Embodiments 1 to 5, especially Embodiment 5), the first sub HARQ-ACK codebook and the second sub HARQ-ACK codebook may be transmitted through one PUCCH or may be transmitted through different PUCCHs. At this time, transmission through the one PUCCH is uplink transmission for either the first TRP (i.e., a concept corresponding to the first QCL RS) or the second TRP (i.e., a concept corresponding to the second QCL RS). Alternatively, transmission through the different PUCCHs may correspond to uplink transmission for the first TRP (i.e., a concept corresponding to the first QCL RS) and uplink transmission for the second TRP (i.e., a concept corresponding to the second QCL RS).
At this time, as in the above-described embodiments (e.g., Embodiments 1 to 5, especially Embodiment 5), transmission and detailed construction of the HARQ-ACK information (e.g., first sub-HARQ-ACK codebook, second sub-HARQ-ACK codebook) may be performed according to the configurations and/or specific rules of the base station.
For example, the first sub HARQ-ACK codebook may include HARQ-ACK information for at least one of the first unicast PDSCH or the first multicast PDSCH, and the second sub HARQ-ACK codebook may include HARQ-ACK information for at least one of the second unicast PDSCH or the second multicast PDSCH. At this time, the HARQ-ACK codebook including the first sub-HARQ-ACK codebook and the second sub-HARQ-ACK codebook may be transmitted through one PUCCH.
On the other hand, the first sub HARQ-ACK codebook may be transmitted through the PUCCH (i.e., PUCCH for the first TRP) associated with the first QCL RS, and the second sub HARQ-ACK codebook may be transmitted through another PUCCH (i.e., PUCCH for the second TRP) related to the second QCL RS. That is, each sub HARQ-ACK codebook may be transmitted through a different PUCCH. In this case, each sub HARQ-ACK codebook may be transmitted in the form of a HARQ-ACK codebook.
For example, in this case, the first sub HARQ-ACK codebook may include HARQ-ACK information for at least one of the first unicast PDSCH or the first multicast PDSCH, and the second sub HARQ-ACK codebook may include HARQ-ACK information for at least one of the second unicast PDSCH or the second multicast PDSCH.
For another example, based on the settings of a certain base station, HARQ-ACK information for the first multicast PDSCH and the second multicast PDSCH may be included in either the first sub-HARQ-ACK codebook or the second sub-HARQ-ACK codebook. That is, multicast HARQ-ACKs for two TRPs may be included in only one of the first sub-HARQ-ACK codebook or the second sub-HARQ-ACK codebook and transmitted to one TRP. At this time, HARQ-ACK information for the first unicast PDSCH may be included in the first sub HARQ-ACK codebook, and HARQ-ACK information for the second unicast PDSCH may be included in the second sub HARQ-ACK codebook. That is, the HARQ-ACK codebook configuration for unicast PDSCH and the HARQ-ACK codebook configuration for multicast PDSCH may be configured/performed according to independent methods.
For another example, based on the settings of a certain base station, the first sub HARQ-ACK codebook may include HARQ-ACK information for the first unicast PDSCH and the second unicast PDSCH, and the second sub HARQ-ACK codebook may include HARQ-ACK information for the first multicast PDSCH and the second multicast PDSCH. That is, all unicast HARQ-ACKs may be independently configured to be transmitted only in the first TRP, and all multicast HARQ-ACKs may be independently configured to be transmitted in the remaining (i.e., second) TRP.
In relation to the above-described operations, the UE may further receive configuration information on the PUCCH on which to transmit the first sub-HARQ-ACK codebook and the PUCCH on which the second sub-HARQ-ACK codebook will be transmitted. Additionally, the first multicast PDSCH and the second multicast PDSCH may be received based on the same G-RNTI or different G-RNTIs. Additionally, the first sub HARQ-ACK codebook and the second sub HARQ-ACK codebook may be determined based on independent coding schemes.
In step S1210, the base station may transmit at least one of the first unicast PDSCH or the first multicast PDSCH. In this case, the base station may transmit the corresponding PDSCH(s) based on the first QCL RS, herein, the first QCL RS may be related/corresponding to the first TRP in the above-described embodiments (e.g., Embodiments 1 to 5, especially Embodiment 5).
In step S1220, the base station may transmit at least one of the second unicast PDSCH or the second multicast PDSCH. In this case, the base station may transmit the corresponding PDSCH(s) based on the second QCL RS, herein, the second QCL RS may be related/corresponding to the second TRP in the above-described embodiments (eg, Embodiments 1 to 5, especially Embodiment 5).
Step S1210 and step S1220 may be performed simultaneously or independently and may correspond to the M-TRP-based unicast/multicast PDSCH transmission/reception operation in the above-described embodiments (e.g., Embodiments 1 to 5, especially Embodiment 5).
Afterwards, the base station may receive HARQ-ACK information through one or more PUCCH (resources) based on the received PDSCH(s). As in the above-described embodiments (e.g. Examples 1 to 5, especially Embodiment 5), the HARQ-ACK information may include a first sub-HARQ-ACK codebook and a second sub-HARQ-ACK codebook determined based on the first unicast PDSCH, first multicast PDSCH, second unicast PDSCH, and/or second multicast PDSCH.
Here, as in the above-described embodiments (e.g. Embodiments 1 to 5, especially Embodiment 5), the first sub HARQ-ACK codebook and the second sub HARQ-ACK codebook may be transmitted through one PUCCH or may be transmitted through different PUCCHs. At this time, transmission through the one PUCCH is uplink transmission for either the first TRP (i.e., a concept corresponding to the first QCL RS) or the second TRP (i.e., a concept corresponding to the second QCL RS). Alternatively, transmission through the different PUCCHs may correspond to uplink transmission for the first TRP (i.e., a concept corresponding to the first QCL RS) and uplink transmission for the second TRP (i.e., a concept corresponding to the second QCL RS).
At this time, as in the above-described embodiments (e.g., Embodiments 1 to 5, especially Embodiment 5), transmission and detailed construction of the HARQ-ACK information (e.g., first sub-HARQ-ACK codebook, second sub-HARQ-ACK codebook) may be performed according to the configurations and/or specific rules of the base station.
For example, the first sub HARQ-ACK codebook may include HARQ-ACK information for at least one of the first unicast PDSCH or the first multicast PDSCH, and the second sub HARQ-ACK codebook may include HARQ-ACK information for at least one of the second unicast PDSCH or the second multicast PDSCH. At this time, the HARQ-ACK codebook including the first sub-HARQ-ACK codebook and the second sub-HARQ-ACK codebook may be transmitted through one PUCCH.
On the other hand, the first sub HARQ-ACK codebook may be transmitted through the PUCCH (i.e., PUCCH for the first TRP) associated with the first QCL RS, and the second sub HARQ-ACK codebook may be transmitted through another PUCCH (i.e., PUCCH for the second TRP) related to the second QCL RS. That is, each sub HARQ-ACK codebook may be transmitted through a different PUCCH. In this case, each sub HARQ-ACK codebook may be transmitted in the form of a HARQ-ACK codebook.
For example, in this case, the first sub HARQ-ACK codebook may include HARQ-ACK information for at least one of the first unicast PDSCH or the first multicast PDSCH, and the second sub HARQ-ACK codebook may include HARQ-ACK information for at least one of the second unicast PDSCH or the second multicast PDSCH.
For another example, based on the settings of a certain base station, HARQ-ACK information for the first multicast PDSCH and the second multicast PDSCH may be included in either the first sub-HARQ-ACK codebook or the second sub-HARQ-ACK codebook. That is, multicast HARQ-ACKs for two TRPs may be included in only one of the first sub-HARQ-ACK codebook or the second sub-HARQ-ACK codebook and transmitted to one TRP. At this time, HARQ-ACK information for the first unicast PDSCH may be included in the first sub HARQ-ACK codebook, and HARQ-ACK information for the second unicast PDSCH may be included in the second sub HARQ-ACK codebook. That is, the HARQ-ACK codebook configuration for unicast PDSCH and the HARQ-ACK codebook configuration for multicast PDSCH may be configured/performed according to independent methods.
For another example, based on the settings of a certain base station, the first sub HARQ-ACK codebook may include HARQ-ACK information for the first unicast PDSCH and the second unicast PDSCH, and the second sub HARQ-ACK codebook may include HARQ-ACK information for the first multicast PDSCH and the second multicast PDSCH. That is, all unicast HARQ-ACKs may be independently configured to be transmitted only in the first TRP, and all multicast HARQ-ACKs may be independently configured to be transmitted in the remaining (i.e., second) TRP.
In relation to the above-described operations, the UE may further receive configuration information on the PUCCH on which to transmit the first sub-HARQ-ACK codebook and the PUCCH on which the second sub-HARQ-ACK codebook will be transmitted. Additionally, the first multicast PDSCH and the second multicast PDSCH may be received based on the same G-RNTI or different G-RNTIs. Additionally, the first sub HARQ-ACK codebook and the second sub HARQ-ACK codebook may be determined based on independent coding schemes.
General Device to which the Present Disclosure May be Applied
In reference to
A first wireless device 100 may include 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. A processor 102 may control a memory 104 and/or a transceiver 106 and may be configured to implement description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure. For example, a processor 102 may transmit a wireless signal including first information/signal through a transceiver 106 after generating first information/signal by processing information in a memory 104. In addition, a processor 102 may receive a wireless signal including second information/signal through a transceiver 106 and then store information obtained by signal processing of second information/signal in a memory 104. A memory 104 may be connected to a processor 102 and may store a variety of information related to an operation of a processor 102. For example, a memory 104 may store a software code including commands for performing all or part of processes controlled by a processor 102 or for performing description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure. Here, a processor 102 and a memory 104 may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (e.g., LTE, NR). A transceiver 106 may be connected to a processor 102 and may transmit and/or receive a wireless signal through one or more antennas 108. A transceiver 106 may include a transmitter and/or a receiver. A transceiver 106 may be used together with a RF (Radio Frequency) unit. In the present disclosure, a wireless device may mean a communication modem/circuit/chip.
A second wireless device 200 may include one or more processors 202 and one or more memories 204 and may additionally include one or more transceivers 206 and/or one or more antennas 208. A processor 202 may control a memory 204 and/or a transceiver 206 and may be configured to implement description, functions, procedures, proposals, methods and/or operation flows charts disclosed in the present disclosure. For example, a processor 202 may generate third information/signal by processing information in a memory 204, and then transmit a wireless signal including third information/signal through a transceiver 206. In addition, a processor 202 may receive a wireless signal including fourth information/signal through a transceiver 206, and then store information obtained by signal processing of fourth information/signal in a memory 204. A memory 204 may be connected to a processor 202 and may store a variety of information related to an operation of a processor 202. For example, a memory 204 may store a software code including commands for performing all or part of processes controlled by a processor 202 or for performing description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure. Here, a processor 202 and a memory 204 may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (e.g., LTE, NR). A transceiver 206 may be connected to a processor 202 and may transmit and/or receive a wireless signal through one or more antennas 208. A transceiver 206 may include a transmitter and/or a receiver. A transceiver 206 may be used together with a RF unit. In the present disclosure, a wireless device may mean a communication modem/circuit/chip.
Hereinafter, a hardware element of a wireless device 100, 200 will be described in more detail. It is not limited thereto, but 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., a functional layer such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more PDUs (Protocol Data Unit) and/or one or more SDUs (Service Data Unit) according to description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure. One or more processors 102, 202 may generate a message, control information, data or information according to description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure. One or more processors 102, 202 may generate a signal (e.g., a baseband signal) including a PDU, a SDU, a message, control information, data or information according to functions, procedures, proposals and/or methods disclosed in the present disclosure to provide it to one or more transceivers 106, 206. One or more processors 102, 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106, 206 and obtain a PDU, a SDU, a message, control information, data or information according to description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure.
One or more processors 102, 202 may be referred to as a controller, a micro controller, a micro processor or a micro computer. One or more processors 102, 202 may be implemented by a hardware, a firmware, a software, or their combination. In an example, one or more ASICs (Application Specific Integrated Circuit), one or more DSPs (Digital Signal Processor), one or more DSPDs (Digital Signal Processing Device), one or more PLDs (Programmable Logic Device) or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102, 202. Description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure may be implemented by using a firmware or a software and a firmware or a software may be implemented to include a module, a procedure, a function, etc. A firmware or a software configured to perform description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure may be included in one or more processors 102, 202 or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. Description, functions, procedures, proposals, methods and/or operation flow charts disclosed in the present disclosure may be implemented by using a firmware or a software in a form of a code, a command and/or a set of commands.
One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, a signal, a message, information, a program, a code, an instruction and/or a command in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, a flash memory, a hard drive, a register, a cash memory, a computer readable storage medium and/or their combination. One or more memories 104, 204 may be positioned inside and/or outside one or more processors 102, 202. In addition, one or more memories 104, 204 may be connected to one or more processors 102, 202 through a variety of technologies such as a wire or wireless connection.
One or more transceivers 106, 206 may transmit user data, control information, a wireless signal/channel, etc. mentioned in methods and/or operation flow charts, etc. of the present disclosure to one or more other devices. One or more transceivers 106, 206 may receiver user data, control information, a wireless signal/channel, etc. mentioned in description, functions, procedures, proposals, methods and/or operation flow charts, etc. disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and may transmit and receive a wireless signal. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information or a wireless signal to one or more other devices. In addition, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information or a wireless signal from one or more other devices. In addition, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208 and one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, a wireless signal/channel, etc. mentioned in description, functions, procedures, proposals, methods and/or operation flow charts, etc. disclosed in the present disclosure through one or more antennas 108, 208. In the present disclosure, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., an antenna port). One or more transceivers 106, 206 may convert a received wireless signal/channel, etc. into a baseband signal from a RF band signal to process received user data, control information, wireless signal/channel, etc. by using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, a wireless signal/channel, etc. which are processed by using one or more processors 102, 202 from a baseband signal to a RF band signal. Therefor, one or more transceivers 106, 206 may include an (analogue) oscillator and/or a filter.
Embodiments described above are that elements and features of the present disclosure are combined in a predetermined form. Each element or feature should be considered to be optional unless otherwise explicitly mentioned. Each element or feature may be implemented in a form that it is not combined with other element or feature. In addition, an embodiment of the present disclosure may include combining a part of elements and/or features. An order of operations described in embodiments of the present disclosure may be changed. Some elements or features of one embodiment may be included in other embodiment or may be substituted with a corresponding element or a feature of other embodiment. It is clear that an embodiment may include combining claims without an explicit dependency relationship in claims or may be included as a new claim by amendment after application.
It is clear to a person skilled in the pertinent art that the present disclosure may be implemented in other specific form in a scope not going beyond an essential feature of the present disclosure. Accordingly, the above-described detailed description should not be restrictively construed in every aspect and should be considered to be illustrative. A scope of the present disclosure should be determined by reasonable construction of an attached claim and all changes within an equivalent scope of the present disclosure are included in a scope of the present disclosure.
A scope of the present disclosure includes software or machine-executable commands (e.g., an operating system, an application, a firmware, a program, etc.) which execute an operation according to a method of various embodiments in a device or a computer and a non-transitory computer-readable medium that such a software or a command, etc. are stored and are executable in a device or a computer. A command which may be used to program a processing system performing a feature described in the present disclosure may be stored in a storage medium or a computer-readable storage medium and a feature described in the present disclosure may be implemented by using a computer program product including such a storage medium. A storage medium may include a high-speed random-access memory such as DRAM, SRAM, DDR RAM or other random-access solid state memory device, but it is not limited thereto, and it may include a nonvolatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices or other nonvolatile solid state storage devices. A memory optionally includes one or more storage devices positioned remotely from processor(s). A memory or alternatively, nonvolatile memory device(s) in a memory include a non-transitory computer-readable storage medium. A feature described in the present disclosure may be stored in any one of machine-readable mediums to control a hardware of a processing system and may be integrated into a software and/or a firmware which allows a processing system to interact with other mechanism utilizing a result from an embodiment of the present disclosure. Such a software or a firmware may include an application code, a device driver, an operating system and an execution environment/container, but it is not limited thereto.
Here, a wireless communication technology implemented in a wireless device 100, 200 of the present disclosure may include Narrowband Internet of Things for a low-power communication as well as LTE, NR and 6G. Here, for example, an NB-IoT technology may be an example of a LPWAN (Low Power Wide Area Network) technology, may be implemented in a standard of LTE Cat NB1 and/or LTE Cat NB2, etc. and is not limited to the above-described name. Additionally or alternatively, a wireless communication technology implemented in a wireless device XXX, YYY of the present disclosure may perform a communication based on a LTE-M technology. Here, in an example, a LTE-M technology may be an example of a LPWAN technology and may be referred to a variety of names such as an eMTC (enhanced Machine Type Communication), etc. For example, an LTE-M technology may be implemented in at least any one of various standards including 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M and so on and it is not limited to the above-described name. Additionally or alternatively, a wireless communication technology implemented in a wireless device XXX, YYY of the present disclosure may include at least any one of a ZigBee, a Bluetooth and a low power wide area network (LPWAN) considering a low-power communication and it is not limited to the above-described name. In an example, a ZigBee technology may generate PAN (personal area networks) related to a small/low-power digital communication based on a variety of standards such as IEEE 802.15.4, etc. and may be referred to as a variety of names.
A method proposed by the present disclosure is mainly described based on an example applied to 3GPP LTE/LTE-A, 5G system, but may be applied to various wireless communication systems other than the 3GPP LTE/LTE-A, 5G system.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2021-0103482 | Aug 2021 | KR | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2022/011623 | 8/5/2022 | WO |
