Patent Application
20250126623
The present disclosure relates to a wireless communication system, and more specifically, to a method and device for transmitting and receiving signals and channels based on group common in a wireless communication system.
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 and receiving a signal and a channel based on a group common in a wireless communication system.
A technical object of the present disclosure is to provide a method and apparatus related to application of a spatial parameter in transmission and reception of a signal and channel based on a group common basis.
A technical object of the present disclosure is to provide a method and apparatus for applying a spatial parameter by considering a cast type in which a control resource is configured, in relation to transmission and reception of a signal and channel based on a group common.
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 performed by a user equipment (UE) in a wireless communication system according to an aspect of the present disclosure may comprise: receiving configuration information for a control resource set (CORESET); receiving information indicating a transmission configuration indicator (TCI) state identifier (ID) for the CORESET; and receiving first downlink control information (DCI) on the CORESET based on a TCI state corresponding to the TCI state ID. In this regard, based on the CORESET being configured for a specific cast type, the TCI state corresponding to the TCI state ID may be not applied to reception of a second DCI on the CORESET.
A method performed by a base station in a wireless communication system according to an additional aspect of the present disclosure may comprise: transmitting configuration information for a control resource set (CORESET); transmitting information indicating a transmission configuration indicator (TCI) state identifier (ID) for the CORESET; and transmitting first downlink control information (DCI) on the CORESET based on a TCI state corresponding to the TCI state ID. In this regard, based on the CORESET being configured for a specific cast type, the TCI state corresponding to the TCI state ID may be not applied to reception of a second DCI on the CORESET.
According to an embodiment of the present disclosure, when a change/update of a spatial parameter is indicated based on a UE-specific medium access control-control element (MAC-CE), this has the effect of making it clear whether the spatial parameters are applicable to group common transmission and reception.
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, u). 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 (FRI, 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 Tt=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 ns,fμ∈{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,1) 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,istart,μ 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 1_0, 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/L1(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
It is referred to as a SDM (Spatial Division Multiplexing) based M-TRP URLLC transmission method. Layers belonging to different layer groups are respectively transmitted through DMRS ports belonging to different DMRS CDM groups.
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:
In schemes 1a and 1c described above, the same MCS is applied to all layers or sets of layers.
In scheme 2a, the same MCS is applied to all non-overlapping frequency resource allocations.
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.
Method for Transmitting and Receiving Channels/Signals Related to Multicast Broadcast service (MBS) based on a spatial parameter
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.)
(SDU), provided from a higher layer, and associated with a UE Contention Resolution Identity as part of a random access procedure.
Otherwise, the term Special Cell refers to the PCell. The Special Cell supports PUCCH transmission and contention-based random access and is always active.
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).
An enhanced wireless communication system (e.g., Rel-17 NR system) seeks to introduce a DL broadcast or DL multicast transmission method to support Multicast
Broadcast Service (MBS) services similar to existing MBMS (e.g., LTE MBMS). The 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, 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.
Referring to
As shown in
The base station may configure/provide PDSCH configurations for common frequency resource (CFR) to the UE separately from the PDSCH configurations (e.g., PDSCH Config) for BWP. At this time, the CFR may be associated with the active BWP of the UE, and some parameters may be configured in common for the CFR and BWP.
Therefore, the base station may configure/provide some parameters only in one PDSCH configuration without repeating (i.e., not repeatedly configuring) the PDSCH configuration for CFR and the PDSCH configuration for BWP. That is, if the configured value for parameter A is the same in the PDSCH configuration for CFR and the PDSCH configuration for BWP, the base station may include parameter A only in the PDSCH configuration for BWP.
In a wireless communication system, the base station may change/update the TCI state(s) for the unicast PDCCH through a UE-dedicated (i.e., UE-specific) medium access control-control element (MAC-CE).
In this regard, it may be unclear whether change/update of TCI state(s) for multicast PDCCH is applied through the corresponding MAC-CE.
Additionally, considering that multiple UEs may receive MAC-CE at different times, a problem may arise where the change/update timing of TCI state(s) for multicast PDCCH is unclear.
Accordingly, a method of applying the TCI state of multicast PDCCH based on the MAC-CE when changing/updating the TCI state for unicast PDCCH based on MAC-CE is proposed in the present disclosure, through embodiments.
The proposed method in the present disclosure is mainly explained using the case of multicast PDCCH as an example, but it may also be applied to other types of group common transmission (e.g., broadcast PDCCH).
Referring to
For example, the UE may receive the corresponding configuration information through higher layer signaling, and the corresponding CORESET may be configured in association with one or more TCI state related information.
The UE may receive information indicating the TCI state ID for the CORESET (S1020). Afterwards, the UE may receive the first DCI on the CORESET based on the TCI state corresponding to the TCI state ID (S1030).
For example, the information may be transmitted and received through MAC-CE for indicating the TCI state for the PDCCH monitored for reception of the first DCI (e.g., MAC CE for indicating the TCI state for the UE-specific PDCCH).
At this time, if the CORESET is configured for a specific cast type, the TCI state corresponding to the TCI state ID may not be applied (i.e., ignored) to the second DCI transmission and reception on the CORESET.
In this regard, the specific cast type may correspond to a multicast broadcast service (MBS) related cast type (e.g., multicast, broadcast, etc.).
For example, the first DCI may be based on a cast type other than the specific cast type, and the second DCI may be based on the specific cast type. As a specific example, the first DCI may correspond to a unicast DCI, and the second DCI may correspond to a multicast DCI. That is, the first DCI may correspond to a UE-specific DCI format based on scrambling by C-RNTI, and the second DCI may correspond to a group common DCI format based on scrambling by G-RNTI.
Additionally or alternatively, the CORESET may be configured for the first PDCCH configuration for the first DCI and the second PDCCH configuration for the second DCI, respectively. As a specific example, the CORESET may be configured in the PDCCH configuration for unicast use (e.g., PDCCH-Config), and may also be separately configured in the PDCCH configuration for multicast use (e.g., PDCCH-Config-Multicast).
Additionally or alternatively, in connection with receiving the first DCI, the information (e.g., MAC-CE-based TCI state indication information) may be configured/defined to be applied after a predefined time interval based on the transmission time of HARQ-ACK information for the corresponsding MAC-CE.
Additionally or alternatively, the second DCI transmission and reception in the CORESET may be performed by applying the TCI state configured through higher layer signaling (e.g., RRC message) before receiving the information. That is, for the second DCI transmission and reception, the TCI state indicated by the above information is not applied, and the previously configured/determined TCI state may be applied/used.
Additionally or alternatively, whether to apply the TCI state corresponding to the TCI state ID to the second DCI transmission and reception on the CORESET may be configured/determined through a higher layer message (e.g., RRC message). As a specific example, whether to apply the TCI state corresponding to the TCI state ID to transmission and reception of the second DCI may be configured/determined based on at least one of i) whether a specific indicator is included in the higher layer message or ii) the value of a specific indicator included in the higher layer message.
Referring to
For example, the base station may transmit the corresponding configuration information through higher layer signaling, and the corresponding CORESET may be configured in association with one or more TCI state related information.
The base station may transmit information indicating the TCI state ID for the CORESET (S1120). Afterwards, the base station may transmit the first DCI on the CORESET based on the TCI state corresponding to the TCI state ID (S1130).
For example, the information may be transmitted and received through MAC-CE for indicating the TCI state for the PDCCH monitored for reception of the first DCI (e.g., MAC CE for indicating the TCI state for the UE-specific PDCCH).
At this time, if the CORESET is configured for a specific cast type, the TCI state corresponding to the TCI state ID may not be applied (i.e., ignored) to the second DCI transmission and reception on the CORESET.
In this regard, the specific cast type may correspond to a multicast broadcast service (MBS) related cast type (e.g., multicast, broadcast, etc.).
For example, the first DCI may be based on a cast type other than the specific cast type, and the second DCI may be based on the specific cast type. As a specific example, the first DCI may correspond to a unicast DCI, and the second DCI may correspond to a multicast DCI. That is, the first DCI may correspond to a UE-specific DCI format based on scrambling by C-RNTI, and the second DCI may correspond to a group common DCI format based on scrambling by G-RNTI.
Additionally or alternatively, the CORESET may be configured for the first PDCCH configuration for the first DCI and the second PDCCH configuration for the second DCI, respectively. As a specific example, the CORESET may be configured in the PDCCH configuration for unicast use (e.g., PDCCH-Config), and may also be separately configured in the PDCCH configuration for multicast use (e.g., PDCCH-Config-Multicast).
Additionally or alternatively, in connection with receiving the first DCI, the information (e.g., MAC-CE-based TCI state indication information) may be configured/defined to be applied after a predefined time interval based on the transmission time of HARQ-ACK information for the corresponsding MAC-CE.
Additionally or alternatively, the second DCI transmission and reception in the CORESET may be performed by applying the TCI state configured through higher layer signaling (e.g., RRC message) before receiving the information. That is, for the second DCI transmission and reception, the TCI state indicated by the above information is not applied, and the previously configured/determined TCI state may be applied/used.
Additionally or alternatively, whether to apply the TCI state corresponding to the TCI state ID to the second DCI transmission and reception on the CORESET may be configured/determined through a higher layer message (e.g., RRC message). As a specific example, whether to apply the TCI state corresponding to the TCI state ID to transmission and reception of the second DCI may be configured/determined based on at least one of i) whether a specific indicator is included in the higher layer message or ii) the value of a specific indicator included in the higher layer message.
Hereinafter, with regard to
Hereinafter, the embodiments in the present disclosure are divided for convenience of explanation, and the embodiments may be applied independently, or configurations and methods of some embodiments may be applied in combination with other embodiments, or may be applied in substitution. For example, the contents of Embodiment 1 and the contents of Embodiment 2 of the present disclosure may be applied in combination with/replaced for each other.
This embodiment relates to a method of configuring/applying the TCI state for multicast PDCCH when indicating to change/update the TCI state for unicast PDCCH based on MAC-CE.
Referring to
The UE-specific MAC-CE for indicating the TCI state described in the present disclosure may mean the MAC-CE for indicating the TCI state for a UE-specific channel (e.g., UE-specific PDCCH, etc.).
For example, in the case of unicast PDCCH, a network (e.g., base station) may indicate the TCI state for PDCCH reception for the CORESET of a serving cell or serving cell configured by transmitting a UE-specific MAC-CE to indicate the TCI state. In this regard, the UE may receive a UE-specific MAC-CE to indicate the TCI state as shown in
In this case, it may be unclear whether the MAC-CE that activates the TCI state for the CORESET ID (e.g., the MAC-CE in
In this regard, when configured to indicate the TCI state of unicast CORESET through MAC-CE, at least one of the following methods (hereinafter referred to as method 1 and method 2) may be applied.
In the following methods, unicast CORESET means CORESET configured for unicast use, and as a specific example, it may correspond to CORESET configured in PDCCH-Config, which is a higher layer configuration. Additionally, multicast CORESET refers to a CORESET configured for multicast use, and as a specific example, it may correspond to CORESET configured in PDCCH-Config-Multicast, which is the higher layer configuration.
Additionally, each CORESET may be configured as a unicast CORESET or a multicast CORESET, or may be configured as both a unicast CORESET and a multicast CORESET.
A case where the unicast CORESET indicated by the above-described MAC-CE is configured to be used also for monitoring the multicast PDCCH and/or a case where a separate CORESET for multicast (i.e., multicast CORESET) is not included in the PDCCH configuration for multicast (e.g., PDCCH-Config-Multicast) may be considered.
In this case, for the CORESET ID and TCI state ID indicated by the corresponding MAC-CE, the UE may apply the corresponding CORESET ID and TCI state ID to receive not only unicast DCI but also multcast DCI (e.g., DCI format 4_0/4_1/4_2, etc.). That is, based on the MAC-CE, the UE may receive multicast DCI using the TCI state indicated on the indicated CORESET.
Alternatively, for the CORESET ID and TCI state ID indicated by the corresponding MAC-CE, the UE may not apply the TCI state indicated on the indicated CORESET for reception of multcast DCI (e.g., DCI format 4_0/4_1/4_2, etc.). That is, for multicast DCI, the UE may ignore the TCI state indication by the corresponding MAC-CE.
If a separate multicast CORESET is configured through a PDCCH configuaration for multicast (e.g., PDCCH-Config-Multicast), the UE may configure/apply the TCI state of multicast CORESET according to the following methods (hereinafter, method 2A and/or method 2B).
In other words, this method is about a method of applying the TCI state indicated by MAC-CE, considering the case where a CORESET is configured as both unicast CORESET and multicast CORESET.
In this method, a method of applying TCI state for DCI reception (i.e., mulciast DCI) in multicast CORESET is mainly explained. In the case of unicast CORESET, DCI reception (e.g., unicast DCI reception) may be performed on unicast CORESET by applying/updating the TCI state indicated by the corresponding MAC-CE.
(Method 2A) For the CORESET ID and TCI state ID indicated by the corresponding MAC-CE, the CORESET ID may be determined to indicate both the CORESET ID for unicast CORESET and the CORESET ID for multicast CORESET. Here, the CORESET ID for unicast CORESET corresponds to the CORESET ID of the PDCCH configuration for unicast (e.g., PDCCH-Config (for unicast)), and the CORESET ID for multicast CORESET may correspond to the CORESET ID of PDCCH configurations for multicast (e.g., PDCCH-Config-Multicast). In this case, the UE may change/update the existing TCI state (e.g., TCI state previously set through higher layer signaling, etc.) to the TCI state corresponding to the TCI state ID for both unicast CORESET and multicast CORESET.
In this regard, if a separate TCI state list (i.e., TCI state list for multicast purposes) is configured for multicast CORESET, for the TCI state of multicast CORESET, the TCI state ID may be determined to indicate one TCI state among the separate TCI state list. On the other hand, if a separate TCI state list is not configured for multicast CORESET, for the TCI state of multicast CORESET, the TCI state ID may be determined to indicate one TCI state among the TCI state list for unicast use. Afterwards, the UE may receive DCI (e.g., multicast DCI) on the multicast CORESET by applying/using the TCI state determined as described above.
(Method 2B) Alternatively, for the CORESET ID and TCI state ID indicated by the corresponding MAC-CE, the CORESET ID may be determined to indicate only the CORESET ID for unicast CORESET and not (all) the CORESET ID for multicast CORESET. Here, the CORESET ID for unicast CORESET may correspond to the CORESET ID of the PDCCH configuration for unicast (e.g., PDCCH-Config (for unicast)), and the CORESET ID for multicast CORESET may correspond to the CORESET ID of the PDCCH configuration for multicast (e.g., PDCCH-Config-Multicast). In this case, the UE may change/update the existing TCI state to the TCI state corresponding to the TCI state ID only for unicast CORESET.
In this regard, regarding multicast CORESET, the TCI state configured through higher layer signaling (e.g., RRC message/configuration) (i.e., existing TCI state) may be determined to be maintained unchanged through MAC-CE. In other words, the TCI state configured to the UE through an RRC message may not be changed/updated by the above-described MAC-CE (i.e., UE-specific MAC CE related to unicast CORESET). Afterwards, the UE may receive DCI (e.g., multicast DCI) on the multicast CORESET by applying/using the determined TCI state. That is, the UE may receive DCI (e.g. multicast DCI) on multicast CORESET by applying/using the existing TCI state, regardless of the TCI state ID indicated by the corresponding MAC-CE.
Alternatively, the UE may be configured to determine whether to apply the corresponding MAC-CE to multicast CORESET based on whether or not a specific indicator is included or the value of the specific indicator through higher layer signaling (e.g., RRC message/setting). That is, whether to apply the above-described UE-specific MAC-CE to multicast CORESET may be configured/indicated to the UE based on higher layer signaling.
For example, if a specific indicator is included (or not included) through the RRC message, or if a specific indicator indicates a specific value (e.g., X value), for multicast CORESET, the UE may determine that the TCI state configured through the above-described higher layer signaling (e.g., RRC message/configuration) is maintained unchanged through MAC-CE. Afterwards, the UE may receive DCI (e.g., multicast DCI) on the multicast CORESET by applying/using the determined TCI state.
For another example, if a specific indicator is not included (or included) through an RRC message, or if a specific indicator indicates a specific value (e.g., Y value), the UE may determine that the CORESET ID and TCI state ID indicated by the MAC-CE indicate both the CORESET ID for unicast CORESET and the CORESET ID for multicast CORESET. Here, the CORESET ID for unicast CORESET may correspond to the CORESET ID of the PDCCH configuration for unicast (e.g., PDCCH-Config (for unicast)), and the CORESET ID for multicast CORESET may correspond to the CORESET ID of PDCCH settings for multicast (e.g., PDCCH-Config-Multicast). In this case, the UE may change/update the existing TCI state to the TCI state corresponding to the TCI state ID for both unicast CORESET and multicast CORESET.
Regarding this example, if a separate TCI state list (i.e., TCI state list for multicast purposes) is configured for multicast CORESET, for the TCI state of multicast CORESET, the TCI state ID may be determined to indicate one TCI state among the separate TCI state list. On the other hand, if a separate TCI state list is not configured for multicast CORESET, for the TCI state of multicast CORESET, the TCI state ID may be determined to indicate one TCI state among the TCI state list for unicast use. Afterwards, the UE may receive DCI (e.g., multicast DCI) on the multicast CORESET by applying/using the TCI state determined as described above.
Additionally or alternatively, for multicast CORESET, in addition to the above-described MAC-CE (e.g., UE-dedicated MAC-CE as shown in
In this case, it may be decided to apply the TCI state indicated by the TCI state ID (field) to the multicast CORESET indicated by the multicast CORESET ID field. Afterwards, the UE may receive DCI (e.g., multicast DCI) on the multicast CORESET by applying/using the determined TCI state.
This embodiment relates to a method of indicating/applying/changing the TCI state of the muticast PDCCH at a specific time through the corresponding MAC-CE. This embodiment may be related to the application/change/interpretation of TCI state instructions and MAC-CE for unicast/multicast CORESET in Embodiment 1 described above.
In relation to the UE-specific MAC-CE for the above-described TCI state indication (e.g., TCI State Indication for UE-specific PDCCH MAC CE), the MAC-CE may be transmitted through a UE-specific unicast PDSCH and/or multicast PDSCH.
When MAC-CE including an activation command for the TCI state is received through unicast PDSCH or multicast PDSCH for G-RNTI, according to at least one of the following methods (hereinafter referred to as method A, method B, and method C), the UE receiving the corresponding G-RNTI may apply activation/deactivation of the TCI state based on the received MAC-CE.
(Method A) Regarding the application of the TCI state indication of the UE based on the received MAC-CE, a case where the UE transmits a PUCCH with HARQ-ACK information corresponding to the PDSCH carrying the MAC-CE including the activation command in slot n may be considered.
Accordingly, the indicated mapping between the TCI state and the codepoint of the TCI field in the DCI may be applied starting from the first slot after slot n+3Nslotsubframe,μ. Here, u is the subcarrier spacing (SCS) for the PUCCH.
According to Method A, since the PUCCH transmission timing may be different for different UEs, different UEs may apply MAC-CE at different timings.
(Method B) Regarding the application of the TCI state indication of the UE based on the received MAC-CE, after receiving the corresponding MAC-CE, a case where the UE receives a group common DCI (e.g., DCI format 4_2) including a TCI field with a valid value and a specific toggled bit may be considered. As an example, this case may be considered in a situation after the PUCCH with HARQ-ACK information corresponding to the PDSCH carrying the MAC-CE including the activation command is transmitted in slot n.
For example, when the UE receives the first group common DCI (e.g., DCI format 4_2) including the first MAC-CE and TCI fields and specific bits, the UE may determine the TCI state of the TCI field based on the first MAC-CE.
Afterwards, to align the application time of MAC-CE for different UEs receiving the multicast PDCCH for the same CORESET, the base station and the UE may operate as follows.
The UE may receive a second MAC-CE, transmit an ACK for the second MAC-CE, and receive a second group common DCI (e.g., DCI format 4_2) including a TCI field and specific bits. Here, the specific bit may not be toggled compared to the previous specific bit. In this case, the UE may determine the TCI state of the TCI field based on the first MAC-CE, regardless of whether ACK for the second MAC-CE is transmitted.
Additionally or alternatively, the UE may receive a second MAC-CE, transmit an ACK for the second MAC-CE, and transmit a second group common DCI (e.g., DCI Format 4_2s) including a TCI field and specific bits. Here, the specific bit may be toggled compared to the previous specific bit. In this case, the UE may determine the TCI state of the TCI field based on the second MAC-CE.
Additionally or alternatively, the UE may receive a second MAC-CE and receive a second group common DCI (eg, DCI format 4_2) including a TCI field and specific bits. Here, the specific bit may be toggled compared to the previous specific bit. In this case, the UE may determine the TCI state of the TCI field based on the second MAC-CE, regardless of whether ACK for the second MAC-CE is transmitted.
Additionally or alternatively, the second MAC-CE is not received, but the UE may receive a second group common DCI (e.g., DCI format 4_2) including a TCI field and specific bits. Here, the specific bit may be toggled compared to the previous specific bit. In this case, the UE may determine the TCI state of the TCI field based on the first MAC-CE and transmit a NACK for the multicast PDSCH scheduled by the second group common DCI. Alternatively, in this case, the UE may perform random access channel (RACH) (i.e., RACH-based random access procedure). Alternatively, in this case, the UE may apply the default TCI state configured by the RRC message to reception of multicast CORESET (i.e., reception of multicast PDCCH/DCI on multicast CORESET).
In this regard, the specific bit may be (one) bit of an existing field in a group common DCI (e.g., DCI format 4_2) or (one) bit of reserved bits. As a specific example, the specific bit may be a specific bit of the TCI field included in DCI format 4_2, a bit of the NDI field, a bit of the downlink assignment index (DAI) field, and/or a bit of an antenna port-related field.
(Method C) Regarding the application of the TCI state indication of the UE based on the received MAC-CE, a case where the UE receives a group common DCI (e.g. DCI format 4_2) including a TCI field with a valid value and the above-mentioned specific bit indicates (one) value of a specific field of the corresponding MAC-CE may be considered. As an example, this case may be considered in a situation after the PUCCH with HARQ-ACK information corresponding to the PDSCH carrying the MAC-CE including the activation command is transmitted in slot n.
For example, if the UE receives a first group common DCI (e.g., DCI format 4_2) including a first MAC-CE and TCI field, and the specific bit indicates the value of a specific field of the first MAC-CE, the UE may determine the TCI state of the TCI field based on the first MAC-CE.
Afterwards, to align the application time of MAC-CE for different terminals receiving the same group common DCI (e.g. DCI format 4_2) for the multicast PDSCH for the same G-RNTI, the base station and the UE may operate as follows.
If the UE receives a second MAC-CE and receives a first group common DCI (e.g., DCI format 4_2) including a TCI field, and the specific bit indicates the value of a specific field of the second MAC-CE, the UE may determine the TCI state of the TCI field based on the second MAC-CE.
Additionally or alternatively, if the UE receives a second MAC-CE, receives a first group common DCI (e.g., DCI format 4_2) including a TCI field, and the specific bit is a value other than the value of a specific field of the second MAC-CE, the UE may determine the TCI state of the TCI field based on the first MAC-CE.
In this regard, the specific bit may be (one) bit of an existing field in a group common DCI (e.g., DCI format 4_2) or (one) bit of reserved bits. As a specific example, the specific bit may be a specific bit of the TCI field included in DCI format 4_2, a bit of the NDI field, a bit of the downlink assignment index (DAI) field, and/or a bit of an antenna port-related field.
In addition, specific fields of the MAC-CE (i.e., first MAC-CE, second MAC-CE) may be a bit of an existing field or a new field of the UE-specific MAC-CE for TCI state indication (e.g., TCI States Indication for UE-specific PDCCH MAC CE).
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.
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 1E used to configure PDSCH parameters.
In this regard, one or more TMGIs may be configured and associated with tci-StatesToAddModList. If a PDSCH transmission is mapped to a TMGI associated with tci-StatesToAddModList, the PDSCH transmission may be associated with tci-StatesToAddModList.
One or more G-RNTIs may be configured and associated with tci-StatesToAddModList. If the PDSCH transmission is mapped to the MBS service of the G-RNTI associated with tci-StatesToAddModList, the PDSCH transmission may be associated with tci-StatesToAddModList.
The value of GC-CS-RNTI or CS-RNTI may be configured and associated with tci-StatesToAddModList. If the PDSCH transmission is mapped to a value of GC-CS-RNTI or CS-RNTI associated with tci-StatesToAddModList, the PDSCH transmission may be associated with tci-StatesToAddModList.
One or more HARQ process IDs may be configured and associated with tci-StatesToAddModList. If a PDSCH transmission is mapped to a HARQ process ID associated with tci-StatesToAddModList, the PDSCH transmission may be associated with tci-StatesToAddModList.
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 (S1302a, S1302b).
Referring to
A. For the configured SS, the UE determines the TCI state(s) of the PDCCH DM-RS to monitor the PDCCH in the CORESET specified by the CORESET ID of the SS configured as follows.
The Serving Cell ID of ‘TCI State Indication for UE-specific MAC CE’ shown in
PDSCH carrying a group common MAC CE such as ‘TCI State Indication for Group Common MAC CE’ is scheduled by DCI of which CRC is scrambled by G-RNTI or GC-CS-RNTI or CS-RNTI.
If PDSCH carrying the group common MAC CE is scheduled by DCI of which CRC is scrambled by G-RNTI, UE considers that the group common MAC CE applies to group common DCI reception with G-RNTI or UE specific DCI reception associated to G-RNTI (e.g., PTP retransmission for G-RNTI) or SPS (re) activation DCI associated to G-RNTI or SPS retransmission DCI associated to G-RNTI. For example, if PDSCH carrying ‘TCI State Indication for Group Common MAC CE’ is scheduled by DCI of which CRC is scrambled by G-RNTI, UE considers the TCI state indicated by the MAC CE is applied to group common DCI reception with G-RNTI or SPS retransmission DCI associated to G-RNTI.
Referring to
The Serving Cell ID field in the MAC CE indicates the identity of the Serving Cell for which the MAC CE applies. The Serving Cell ID corresponds to the serving cell associated to the CFR or the serving cell of UE's active BWP associated to the CFR. ConfigIndex field indicates CFR ID of the CFR or short ID of TMGI configured by the RRC message.
If CORESET ID field is included in ‘TCI State Indication for Group Common MAC CE’, up to N-2 TCI State ID fields may be added to indicate one or more TCI states activated for the CORESET of the CORESET ID either for the Serving Cell ID and ConfigIndex field or for the G-RNTI field.
Alternatively, instead of CORESET ID field, CORESET ID BITMAP field indicates 8 CORESET IDs, i.e. CORESET ID=0, 1, 2, . . . and 7. Each bit of CORESET ID BITMAP field indicates whether the TCI state ID of the corresponding CORESET ID configured for the configured SS is added in this MAC CE. If CORESET ID BITMAP field is not included in this MAC CE. 8 TCI state ID fields are included in this MAC CE for 8 CORESET IDs in the increasing order of CORESET ID. If the Serving Cell ID field and the ConfigIndex field are included, each TCI state ID indicates the TCI state for the CORESET ID for the Serving Cell ID field and the ConfigIndex field. If G-RNTI field is included, each TCI state ID indicates the TCI state for the CORESET ID for the G-RNTI in the increasing order of CORESET ID. The G-RNTI field may be replaced by TMGI field. In this case, each TCI state ID indicates the TCI state for the CORESET ID for TMGI in the increasing order of CORESET ID.
B. The UE receives the PDCCH in the CORESET specified by the CORESET ID of the SS configured with the TCI state determined for the CORESET ID as follows.ss
If only one TCI state is determined to monitor PDCCH with G-RNTI, the UE receives PDCCH with the determined TCI state.
If more than one TCI state is determined to monitor PDCCH with G-RNTI, the UE select one or more TCI states to receives PDCCH as follows.
If multiple CORETSETs are configured for same or different CORESET IDs on the configured SS, the UE may select one or multiple different TCI states. If multiple different TCI states are selected for multiple CORESETs for same or different CORESET IDs, the UE maps different TCI states to different CORESETs of same or different CORESET IDs as follows.
After mapping a different TCI state to another CORESET with the same or different CORESET ID, the UE receives one or more CORESETs mapped to the selected TCI state and monitors the PDCCH for GC-CS-RNTI, CS-RNTI, or G-RNTI.
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 (S1303a, S1303b).
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.
A base station may transmit a PDSCH carrying corresponding MBS service data to a UE (S1304a, S1304b) (In
For example, UE1 may receive a PDSCH based on TCI state 1 among PDSCHs (related to G-RNTI #1) transmitted in TCI state 1 and TCI state 2, and UE2 may receive PDSCH based on TCI state 4.
On the other hand, unlike the example of
Afterwards, according to the decoding status of PDSCH transmission, the UE transmits HARQ feedback to the base station (S1306a, S1306b). As an example, UE1 may transmit ACK information to gNB through PUCCH, and UE2 may transmit NACK information to gNB through PUCCH.
If the group common PDSCH is scheduled by a DCI format not having the TCI field present, and the time offset between the reception of the DL DCI and the corresponding PDSCH of the CFR is equal to or greater than a threshold timeDurationForQCL, if applicable for determining PDSCH antenna port quasi co-location, the UE assumes that the TCI state or the QCL assumption for the group common PDSCH is identical to the TCI state or QCL assumption whichever is applied for the CORESET used for the group common PDCCH transmission within the CFR.
Independent of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2, UE's assumption on QCL or TCI state for PDSCH reception may be different depending on whether the offset between the reception of the DL DCI and the corresponding PDSCH is “less than” or “equal to or larger than” the threshold timeDurationForQCL. For example, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, the UE assumes that the TCI state or the QCL assumption for PDSCH is identical to the TCI state or QCL assumption whichever is applied for the CORESET used for PDCCH transmission for a CFR, a BWP or a cell. Especially for group-common PDCCH, the threshold timeDurationForQCL may be determined as follows, considering the fact that different UEs receiving group-common PDCCH may report different values for the threshold timeDurationForQCL.
If the pdsch-AggregationFactor is configured, the TB scheduled by group common DCI may be repeated for Nth HARQ transmission of a TB within each symbol allocation among each of the pdsch-AggregationFactor consecutive slots, if configured. In this case, same or different TCI states may be configured for different slots of the repetition. Group common/UE specific MAC CE may be used to activate/deactivate TCI states or reconfigure mapping between TCI states and repetitions.
If group common DCI may indicate the number of repetitions for PDSCH for Nth HARQ transmission of a TB, same or different TCI states may be configured for different slots of the repetition. The DCI may be used to activate/deactivate TCI states or reconfigure mapping between TCI states and repetitions. For dynamic scheduling, the DCI schedules initial transmission or retransmission of group common PDSCH transmission(s). For semi-persistent scheduling, the DCI (de) activates a group common SPS configuration or schedules retransmission of group common PDSCH transmission(s).
gNB informs UE about mapping between a PDSCH transmission occasion and a TCI state by RRC message or Group common MAC CE or UE-specific MAC CE.
The UE selects TCI state for group common PDSCH scheduled by group common DCI according to the above mapping between PDSCH transmission occasions and TCI states.
The gNB may retransmit the TB to only one of the UEs in the group by UE-specific PDCCH while other UEs do not receive the retransmission of the TB. This is because the other UE successfully received the TB.
According to the embodiments of the present disclosure described above, when indicating change/update of spatial parameters (e.g., TCI state) based on a UE-specific MAC-CE, there is an effect of clarifying whether the spatial parameters are applied to group common transmission and reception.
That is, according to the embodiments of the present disclosure described above, when changing the TCI state for unicast PDCCH based on a MAC-CE, the TCI state of the multicast PDCCH may be changed at a specific time through the MAC-CE, or the TCI state of the multicast PDCCH may not be changed, so that the TCI state of the multicast PDCCH may be clarified.
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-2022-0018286 | Feb 2022 | KR | national |
This application is the National Stage filing under 35 U.S.C. 371 of International Application No. PCT/KR2023/001970, filed on Feb. 10, 2023, which claims the benefit of earlier filing date and right of priority to Korean Application No. 10-2022-0018286, filed on Feb. 11, 2022, the contents of which are all incorporated by reference herein in their entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2023/001970 | 2/10/2023 | WO |
