Patent Application
20230353314
Pursuant to 35 U.S.C. § 119(a), this application claims the benefit of earlier filing date and right of priority to Korean Patent Application Nos. 10-2022-0052401, filed on Apr. 27, 2022, and 10-2022-0082027, filed on Jul. 4, 2022, the contents of which are all hereby incorporated by reference herein in their entirety.
The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for performing uplink transmission and reception in a wireless communication system.
A mobile communication system has been developed to provide a voice service while guaranteeing mobility of users. However, a mobile communication system has extended even to a data service as well as a voice service, and currently, an explosive traffic increase has caused shortage of resources and users have demanded a faster service, so a more advanced mobile communication system has been required.
The requirements of a next-generation mobile communication system at large should be able to support accommodation of explosive data traffic, a remarkable increase in a transmission rate per user, accommodation of the significantly increased number of connected devices, very low End-to-End latency and high energy efficiency. To this end, a variety of technologies such as Dual Connectivity, Massive Multiple Input Multiple Output (Massive MIMO), In-band Full Duplex, Non-Orthogonal Multiple Access (NOMA), Super wideband Support, Device Networking, etc. have been researched.
A technical object of the present disclosure is to provide a method and apparatus for performing uplink transmission in a wireless communication system.
An additional technical object of the present disclosure is to provide a method and apparatus for transmitting/drop/multiplexing multiple physical control channels (e.g., PUCCH) when the simultaneous uplink transmission of the terminal may be supported in the wireless communication system.
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 terminal in the wireless communication system according to an aspect of the present disclosure may comprise: receiving transmission reference information related to a plurality of uplink channels from a network; and transmitting at least one of the plurality of uplink channels in one time unit, based on the transmission reference information. Wherein, the transmission reference information may include at least one of a control resource set pool (CORESET pool), an uplink channel group, an uplink channel format, uplink contents or a transmission scheme. The transmission of the at least one of the plurality of uplink channels may be performed based on a first operation corresponding to simultaneous transmission of the plurality of uplink channels or a second operation corresponding to at least one of multiplexing or partial drop for the plurality of uplink channels.
A method performed by a base station in the wireless communication system according to an additional aspect of the present disclosure may comprise: transmitting transmission reference information related to a plurality of uplink channels to a terminal; and receiving at least one of the plurality of uplink channels in one time unit, based on the transmission reference information. Wherein, the transmission reference information may include at least one of a control resource set pool (CORESET pool), an uplink channel group, an uplink channel format, uplink contents or a transmission scheme. The transmission of the at least one of the plurality of uplink channels may be performed based on a first operation corresponding to simultaneous transmission of the plurality of uplink channels or a second operation corresponding to at least one of multiplexing or partial drop for the plurality of uplink channels.
According to an embodiment of the present disclosure, a method and apparatus for performing uplink transmission in a wireless communication system may be provided.
According to an embodiment of the present disclosure, a method and apparatus for transmitting/drop/multiplexing multiple physical control channels (e.g., PUCCH) when the simultaneous uplink transmission of the terminal may be supported in the wireless communication system may be provided.
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.
BM: beam management
CQI: Channel Quality Indicator
CRI: channel state information-reference signal resource indicator
CSI: channel state information
CSI-IM: channel state information-interference measurement
CSI-RS: channel state information-reference signal
DMRS: demodulation reference signal
FDM: frequency division multiplexing
FFT: fast Fourier transform
IFDMA: interleaved frequency division multiple access
IFFT: inverse fast Fourier transform
L1-RSRP: Layer 1 reference signal received power
L1-RSRQ: Layer 1 reference signal received quality
MAC: medium access control
NZP: non-zero power
OFDM: orthogonal frequency division multiplexing
PDCCH: physical downlink control channel
PDSCH: physical downlink shared channel
PMI: precoding matrix indicator
RE: resource element
RI: Rank indicator
RRC: radio resource control
RSSI: received signal strength indicator
Rx: Reception
QCL: quasi co-location
SINR: signal to interference and noise ratio
SSB (or SS/PBCH block): Synchronization signal block (including PSS (primary synchronization signal), SSS (secondary synchronization signal) and PBCH (physical broadcast channel))
TDM: time division multiplexing
TRP: transmission and reception point
TRS: tracking reference signal
Tx: transmission
UE: user equipment
ZP: zero power
Overall System
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, p). In addition, although it is assumed that a very low subcarrier spacing is not used in a very high carrier frequency, a used numerology may be selected independently from a frequency band. In addition, a variety of frame structures according to a plurality of numerologies may be supported in a NR system.
Hereinafter, an OFDM numerology and frame structure which may be considered in a NR system will be described. A plurality of OFDM numerologies supported in a NR system may be defined as in the following Table 1.
NR supports a plurality of numerologies (or subcarrier spacings (SCS)) for supporting a variety of 5G services. For example, when a SCS is 15 kHz, a wide area in traditional cellular bands is supported, and when a SCS is 30 kHz/60 kHz, dense-urban, lower latency and a wider carrier bandwidth are supported, and when a SCS is 60 kHz or higher, a bandwidth wider than 24.25 GHz is supported to overcome a phase noise. An NR frequency band is defined as a frequency range in two types (FR1, FR2). FR1, FR2 may be configured as in the following Table 2. In addition, FR2 may mean a millimeter wave (mmW).
Regarding a frame structure in an NR system, a size of a variety of fields in a time domain is expresses as a multiple of a time unit of Tc=1/(Δfmax·Nf). Here, Δfmax is 480·103 Hz and Nf is 4096. Downlink and uplink transmission is configured (organized) with a radio frame having a duration of Tf=1/(ΔfmaxNf/100)·Tc=10 ms. Here, a radio frame is configured with 10 subframes having a duration of Tsf=(ΔfmaxNf/1000)·Tc=1 ms, respectively. In this case, there may be one set of frames for an uplink and one set of frames for a downlink. In addition, transmission in an uplink frame No. i from a terminal should start earlier by TTA=(NTA+NTA,offset) Tc than a corresponding downlink frame in a corresponding terminal starts. For a subcarrier spacing configuration μ, slots are numbered in an increasing order of nsμ∈{0, . . . , Nslotsubframe, μ−1} in a subframe and are numbered in an increasing order of 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.
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.
offsetToPointA for a primary cell (PCell) downlink represents a frequency offset between point A and the lowest subcarrier of the lowest resource block overlapped with a SS/PBCH block which is used by a terminal for an initial cell selection. It is expressed in resource block units assuming a 15 kHz subcarrier spacing for FR1 and a 60 kHz subcarrier spacing for FR2.
absoluteFrequencyPointA represents a frequency-position of point A expressed as in ARFCN (absolute radio-frequency channel number).
Common resource blocks are numbered from 0 to the top in a frequency domain for a subcarrier spacing configuration μ. The center of subcarrier 0 of common resource block 0 for a subcarrier spacing configuration μ is identical to ‘point A’. A relationship between a common resource block number nCRBμ and a resource element (k,l) for a subcarrier spacing configuration μ in a frequency domain is given as in the following Equation 1.
In Equation 1, k is defined relatively to point A so that k=0 corresponds to a subcarrier centering in point A. Physical resource blocks are numbered from 0 to NBWP,isize,μ−1 in a bandwidth part (BWP) and i is a number of a BWP. A relationship between a physical resource block nPRB and a common resource block nCRB in BWP i is given by the following Equation 2.
n
CRB
μ
=n
PRB
μ
+N
BWP,i
start, μ [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.
Operation Related to Multi-TRPs
A coordinated multi point (CoMP) scheme refers to a scheme in which a plurality of base stations effectively control interference by exchanging (e.g., using an X2 interface) or utilizing channel information (e.g., RI/CQI/PMI/LI(layer indicator), etc.) fed back by a terminal and cooperatively transmitting to a terminal. According to a scheme used, a CoMP may be classified into joint transmission(JT), coordinated Scheduling(CS), coordinated Beamforming(CB), dynamic Point Selection(DPS), dynamic Point Blocking(DPB), etc.
M-TRP transmission schemes that M TRPs transmit data to one terminal may be largely classified into i) eMBB M-TRP transmission, a scheme for improving a transfer rate, and ii) URLLC M-TRP transmission, a scheme for increasing a reception success rate and reducing latency.
In addition, with regard to DCI transmission, M-TRP transmission schemes may be classified into i) M-TRP transmission based on M-DCI(multiple DCI) that each TRP transmits different DCIs and ii) M-TRP transmission based on S-DCI(single DCI) that one TRP transmits DCI. For example, for S-DCI based M-TRP transmission, all scheduling information on data transmitted by M TRPs should be delivered to a terminal through one DCI, it may be used in an environment of an ideal BackHaul (ideal BH) where dynamic cooperation between two TRPs is possible.
For TDM based URLLC M-TRP transmission, scheme 3/4 is under discussion for standardization. Specifically, scheme 4 means a scheme in which one TRP transmits a transport block(TB) in one slot and it has an effect to improve a probability of data reception through the same TB received from multiple TRPs in multiple slots. Meanwhile, scheme 3 means a scheme in which one TRP transmits a TB through consecutive number of OFDM symbols (i.e., a symbol group) and TRPs may be configured to transmit the same TB through a different symbol group in one slot.
In addition, 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, multiple DCI based non-coherent joint transmission (NCJT)/single DCI based NCJT will be described.
NCJT(Non-coherent joint transmission) is a scheme in which a plurality of transmission points (TP) transmit data to one terminal by using the same time frequency resource, TPs transmit data by using a different DMRS(Demodulation Multiplexing Reference Signal) between TPs through a different layer (i.e., through a different DMRS port).
A TP delivers data scheduling information through DCI to a terminal receiving NCJT. Here, a scheme in which each TP participating in NCJT delivers scheduling information on data transmitted by itself through DCI is referred to as ‘multi DCI based NCJT’. As each of N TPs participating in NCJT transmission transmits DL grant DCI and a PDSCH to UE, UE receives N DCI and N PDSCHs from N TPs. Meanwhile, a scheme in which one representative TP delivers scheduling information on data transmitted by itself and data transmitted by a different TP (i.e., a TP participating in NCJT) through one DCI is referred to as ‘single DCI based NCJT’. Here, N TPs transmit one PDSCH, but each TP transmits only some layers of multiple layers included in one PDSCH. For example, when 4-layer data is transmitted, TP 1 may transmit 2 layers and TP 2 may transmit 2 remaining layers to UE.
Multiple TRPs (MTRPs) performing NCJT transmission may transmit DL data to a terminal by using any one scheme of the following two schemes.
First, ‘a single DCI based MTRP scheme’ is described. MTRPs cooperatively transmit one common PDSCH and each TRP participating in cooperative transmission spatially partitions and transmits a corresponding PDSCH into different layers (i.e., different DMRS ports) by using the same time frequency resource. Here, scheduling information on the PDSCH is indicated to UE through one DCI and which DMRS (group) port uses which QCL RS and QCL type information is indicated by the corresponding DCI (which is different from DCI indicating a QCL RS and a type which will be commonly applied to all DMRS ports indicated as in the existing scheme). In other words, M TCI states may be indicated through a TCI(Transmission Configuration Indicator) field in DCI (e.g., for 2 TRP cooperative transmission, M=2) and a QCL RS and a type may be indicated by using M different TCI states for M DMRS port group. In addition, DMRS port information may be indicated by using a new DMRS table.
Next, ‘a multiple DCI based MTRP scheme’ is described. Each of MTRPs transmits different DCI and PDSCH and (part or all of) the corresponding PDSCHs are overlapped each other and transmitted in a frequency time resource. Corresponding PDSCHs may be scrambled through a different scrambling ID (identifier) and the DCI may be transmitted through a CORESET belonging to a different CORESET group. (Here, a CORESET group may be identified by an index defined in a CORESET configuration of each CORESET. For example, when index=0 is configured for CORESETs 1 and 2 and index=1 is configured for CORESETs 3 and 4, CORESETs 1 and 2 are CORESET group 0 and CORESET 3 and 4 belong to a CORESET group 1. In addition, when an index is not defined in a CORESET, it may be construed as index=0) When a plurality of scrambling IDs are configured or two or more CORESET groups are configured in one serving cell, a UE may notice that it receives data according to a multiple DCI based MTRP operation.
Alternatively, whether of a single DCI based MTRP scheme or a multiple DCI based MTRP scheme may be indicated to UE through separate signaling. In an example, for one serving cell, a plurality of CRS (cell reference signal) patterns may be indicated to UE for a MTRP operation. In this case, PDSCH rate matching for a CRS may be different depending on a single DCI based MTRP scheme or a multiple DCI based MTRP scheme (because a CRS pattern is different).
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).
Hereinafter, partially overlapped NCJT will be described.
In addition, NCJT may be classified into fully overlapped NCJT that time frequency resources transmitted by each TP are fully overlapped and partially overlapped NCJT that only some time frequency resources are overlapped. In other words, for partially overlapped NCJT, data of both of TP 1 and TP 2 are transmitted in some time frequency resources and data of only one TP of TP 1 or TP 2 is transmitted in remaining time frequency resources.
Hereinafter, a method for improving reliability in Multi-TRP will be described.
As a transmission and reception method for improving reliability using transmission in a plurality of TRPs, the following two methods may be considered.
In reference to
In reference to
According to methods illustrated in
In addition, the above-described contents related to multiple TRPs are described based on an SDM (spatial division multiplexing) method using different layers, but it may be naturally extended and applied to a FDM (frequency division multiplexing) method based on a different frequency domain resource (e.g., RB/PRB (set), etc.) and/or a TDM (time division multiplexing) method based on a different time domain resource (e.g., a slot, a symbol, a sub-symbol, etc.).
Regarding a method for multiple TRPs based URLLC scheduled by single DCI, the following method is discussed.
1) Method 1 (SDM): Time and frequency resource allocation is overlapped and n (n≤Ns) TCI states in a single slot
1-a) Method 1a
1-b) Method 1b
1-c) Method 1c
In case of the method 1a and 1c, the same MCS is applied to all layers or all layer sets.
2) Method 2 (FDM): Frequency resource allocation is not overlapped and n (n≤Nf) TCI states in a single slot
2-a) Method 2a
2-b) Method 2b
For the method 2a, the same MCS is applied to all non-overlapping frequency resource allocation.
3) Method 3 (TDM): Time resource allocation is not overlapped and n (n≤Nt1) TCI states in a single slot
4) Method 4 (TDM): n (n≤Nt2) TCI states in K (n≤K) different slots
Hereinafter, MTRP URLLC is described.
In the present disclosure, DL MTRP URLLC means that multiple TRPs transmit the same data (e.g., the same 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 configured from a base station for which QCL RS/type (i.e., a DL TCI state) should be used in a layer/time/frequency resource receiving the same data/DCI. 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 configured. 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.
And, in the present disclosure, UL MTRP-URLLC means that multiple TRPs receive the same data/UCI(uplink control information) from any UE by using a different layer/time/frequency resource. For example, TRP 1 receives the same data/DCI from UE in resource 1 and TRP 2 receives the same data/DCI from UE in resource 2 to share received data/DCI 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. In this case, UE is configured from a base station for 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. For example, when the same data/UCI is transmitted 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 configured. Such UL MTRP URLLC may be applied to a PUSCH/a PUCCH.
In addition, in the present disclosure, when a specific TCI state (or TCI) is used (or mapped) in receiving data/DCI/UCI for any frequency/time/space resource (layer), it means as follows. For a DL, it may mean that a channel is estimated from a DMRS by using a QCL type and a QCL RS indicated by a corresponding TCI state in that frequency/time/space resource (layer) and data/DCI is received/demodulated based on an estimated channel. In addition, for a UL, it may mean that a DMRS and data/UCI are transmitted/modulated by using a Tx beam and power indicated by a corresponding TCI state in that frequency/time/space resource.
Here, an UL TCI state has Tx beam and/or Tx power information of UE and may configure spatial relation information, etc. to UE through other parameter, instead of a TCI state. An UL TCI state may be directly indicated by UL grant DCI or may mean spatial relation information of a SRS resource indicated by a SRI (sounding resource indicator) field of UL grant DCI. Alternatively, it may mean an open loop (OL) Tx power control parameter connected to a value indicated by a SRI field of UL grant DCI (e.g., j: an index for open loop parameter Po and alpha (up to 32 parameter value sets per cell), q d: an index of a DL RS resource for PL (pathloss) measurement (up to 4 measurements per cell), 1: a closed loop power control process index (up to 2 processes per cell)).
Hereinafter, MTRP eMBB is described.
In the present disclosure, MTRP-eMBB means that multiple TRPs transmit different data (e.g., a different TB) by using a different layer/time/frequency. UE configured with a MTRP-eMBB transmission method receives an indication on multiple TCI states through DCI and assumes that data received by using a QCL RS of each TCI state is different data.
On the other hand, UE may figure out whether of MTRP URLLC transmission/reception or MTRP eMBB transmission/reception by separately dividing 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, UE considers it as URLLC transmission and when CRC masking of DCI is performed by using a RNTI for eMBB, UE considers it as eMBB transmission. Alternatively, a base station may configure MTRP URLLC transmission/reception or TRP eMBB transmission/reception to UE through other new signaling.
In a description of the present disclosure, it is described by assuming cooperative transmission/reception between 2 TRPs for convenience of a description, but a method proposed in the present disclosure may be also extended and applied in 3 or more multiple TRP environments and in addition, it may be also extended and applied in multiple panel environments (i.e., by matching a TRP to a panel). In addition, a different TRP may be recognized as a different TCI state to UE. Accordingly, when UE receives/transmits data/DCl/UCI by using TCI state 1, it means that data/DCl/UCI is received/transmitted from/to a TRP 1.
Hereinafter, methods proposed in the present disclosure may be utilized in a situation that MTRPs cooperatively transmit a PDCCH (repetitively transmit or partitively transmit the same PDCCH). In addition, methods proposed in the present disclosure may be also utilized in a situation that MTRPs cooperatively transmit a PDSCH or cooperatively receive a PUSCH/a PUCCH.
In addition, in the present disclosure, when a plurality of base stations (i.e., MTRPs) repetitively transmit the same PDCCH, it may mean the same DCI is transmitted through multiple PDCCH candidates and it may also mean that a plurality of base stations repetitively transmit the same DCI. Here, the same DCI may mean two DCI with the same DCI format/size/payload. Alternatively, although two DCI has 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 occasion of DCI, so if DCI received at n occasions and DCI received at n+1 occasions inform UE of the same scheduling result, 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 the 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, when a plurality of base stations (i.e., MTRPs) partitively transmit the same PDCCH, it means that one DCI is transmitted through one PDCCH candidate, but TRP 1 transmits some resources that such a PDCCH candidate is defined and TRP 2 transmits the remaining resources. For example, when a PDCCH candidate corresponding to aggregation level m1+m2 is partitively transmitted by TRP 1 and TRP 2, a PDCCH candidate may be divided into PDCCH candidate 1 corresponding to aggregation level m1 and PDCCH candidate 2 corresponding to aggregation level m2, and TRP 1 may transmit PDCCH candidate 1 and TRP 2 may transmit PDCCH candidate 2 to a different time/frequency resource. After receiving PDCCH candidate 1 and PDCCH candidate 2, UE may generate a PDCCH candidate corresponding to aggregation level m1+m2 and try DCI decoding.
In addition, in the present disclosure, when UE repetitively transmits the same PUSCH so that a plurality of base stations (i.e., MTRPs) can receive it, it may mean that UE transmitted the same data through multiple PUSCHs. In this case, each PUSCH may be optimized and transmitted to an UL channel of a different TRP. For example, when UE repetitively transmits the same data through PUSCH 1 and 2, PUSCH 1 is transmitted by using UL TCI state 1 for TRP 1 and in this case, link adaptation such as a precoder/MCS, etc. may be also scheduled/applied to a value optimized for a channel of TRP 1. PUSCH 2 is transmitted by using UL TCI state 2 for TRP 2 and link adaptation such as a precoder/MCS, etc. may be also scheduled/applied to a value optimized for a channel of TRP 2. In this case, PUSCH 1 and 2 which are repetitively transmitted may be transmitted at a different time to be TDM, FDM or SDM.
In addition, in the present disclosure, when UE partitively transmits the same PUSCH so that a plurality of base stations (i.e., MTRPs) can receive it, it may mean that UE transmits one data through one PUSCH, but it divides resources allocated to that PUSCH, optimizes them for an UL channel of a different TRP and transmits them. For example, when UE transmits the same data through 10 symbol PUSCHs, data is transmitted by using UL TCI state 1 for TRP 1 in 5 previous symbols and in this case, link adaptation such as a precoder/MCS, etc. may be also scheduled/applied to a value optimized for a channel of TRP 1. The remaining data is transmitted by using UL TCI state 2 for TRP 2 in the remaining 5 symbols and in this case, link adaptation such as a precoder/MCS, etc. may be also scheduled/applied to a value optimized for a channel of TRP 2. In the example, transmission for TRP 1 and transmission for TRP 2 are TDM-ed by dividing one PUSCH into time resources, but it may be transmitted by a FDM/SDM method.
In addition, similarly to the above-described PUSCH transmission, also for a PUCCH, UE may repetitively transmit the same PUCCH or may partitively transmit the same PUCCH so that a plurality of base stations (i.e., MTRPs) receive it.
Hereinafter, a proposal of the present disclosure may be extended and applied to a variety of channels such as a PUSCH/a PUCCH/a PDSCH/a PDCCH, etc.
A proposal of the present disclosure may be extended and applied to both a case in which various uplink/downlink channels are repetitively transmitted to a different time/frequency/space resource and a case in which various uplink/downlink channels are partitively transmitted to a different time/frequency/space resource.
In the present disclosure, a transmission occasion (TO) may correspond to a resource unit in which a channel is transmitted/received or a candidate resource unit in which a channel may be transmitted/received. For example, when multiple channels are transmitted in the TDM scheme, TO may mean each channel that is or may be transmitted in different time resources. For example, when multiple channels are transmitted in the FDM scheme, TO may mean each channel that is or may be transmitted in different frequency resources (e.g., RBs). For example, when multiple channels are transmitted in the SDM scheme, TO may mean each channel that is or may be transmitted in different layers/beams/DMRS ports. One TCI state may be mapped to each TO. When the same channel is repeatedly transmitted, a complete DCl/data/UCI may be transmitted in one TO, and the receiving end may receive multiple TOs to increase the reception success rate.
The above-described single DCI (S-DCI)-based multi-TB PUSCH/PDSCH scheduling scheme may be applied, for example, to a case that one DCI simultaneously schedules a plurality of PUSCH/PDSCHs in a very high frequency band (e.g., band above 5.26 GHz). For example, multiple time-domain resource allocations (TDRAs) (or TOs) may be indicated at once through a TDRA field of DCI for scheduling PUSCH, and different TBs may be transmitted through a PUSCH in each TO. Frequency domain resource allocation (FDRA), MCS, transmit precoding matrix indicator (TPMI), SRI values of Multi-TB PUSCH scheduling DCI may be commonly applied to a plurality of TBs scheduled by the corresponding DCI. In addition, NDI, RV may be individually/independently indicated for each TB through the multi-TB PUSCH scheduling DCI. In addition, in such multi-TB PUSCH scheduling DCI, one value is indicated for the HARQ (process) number (HPN), but values sequentially increasing in the TO order from the initial TO may be applied.
Additionally, a S-DCI based M-TRP PUSCH repetition transmission scheme may be considered. In this regard, the base station configures two SRS sets to the terminal for S-DCI-based M-TRP PUSCH transmission, and each set is used to indicate a UL Tx port for/to TRP 1 and TRP 2, and a UL beam/QCL information. In addition, the base station performs SRS resource indication for each SRS resource set and may indicate up to two PC parameter sets, through two SRI fields included in one DCI.
For example, the first SRI field may indicate the SRS resource and PC parameter set defined in SRS resource set 0, and the second SRI field may indicate the SRS resource and PC parameter set defined in SRS resource set 1. The terminal may receive an indication of the UL Tx port, PC parameter set, and UL beam/QCL information for TRP 1 through the first SRI field, and, through this, the terminal performs PUSCH transmission in TO corresponding to SRS resource set 0. Similarly, the terminal may receive an indication of the UL Tx port, PC parameter set, and UL beam/QCL information for TRP 2 through the second SRI field, and through this, the terminal may perform PUSCH transmission in TO corresponding to SRS resource set 1.
In addition to the above-described SRI field, an existing one field may be extended to two fields so that TPMI, PTRS, and TPC-related fields may be indicated for each TRP.
Additionally, an SRS resource set indication field (e.g., a 2-bit field) may be defined, and based on this, the terminal may perform the S-TRP PUSCH repetition transmission by selecting a specific one of the two SRS resource sets, or may perform M-TRP PUSCH repetition transmission by selecting both SRS resource sets.
For example, codepoint “00” of the SRS resource set indication field may indicate the first SRS resource set, and codepoint “01” may indicate the second SRS resource set/definition. When codepoint “00” or “01” is indicated, S-TRP PUSCH transmission corresponding to the SRS resource set indicated by each codepoint may be performed. In addition, codepoint “10” may be configured/defined to indicate [first SRS resource set, second SRS resource set], and codepoint “11” may be configured/defined to indicate [second SRS resource set, first SRS resource set]. When codepoint “10” or “11” is indicated, M-TRP PUSCH transmission may be performed in the order in which SRS resource set pairs are indicated. When codepoint “10” is indicated, the first SRS resource set corresponds to the first PUSCH TO, and when codepoint “11” is indicated, the second SRS resource set corresponds to the first PUSCH TO.
Additionally, a single PUCCH resource-based M-TRP repetition PUCCH transmission scheme may be considered. In this regard, for single PUCCH resource-based M-TRP PUCCH transmission, the base station may activate/configure two spatial relation info on a single PUCCH resource to the terminal (if FR1, two PC parameter sets may be activated/configured). When UL UCI is transmitted through a corresponding PUCCH resource, each spatial relation info is used to indicate spatial relation info toward TRP 1 and TRP 2 to the terminal, respectively. For example, through the value indicated in the first spatial relation info, the terminal is indicated with Tx beam/PC parameter(s) toward TRP 1, and the terminal performs PUCCH transmission in the TO corresponding to TRP 1 by using the corresponding information. Similarly, through the value indicated in the second spatial relation info, the terminal is indicated the Tx beam/PC parameter(s) toward TRP 2, and the terminal performs PUCCH transmission in the TO corresponding to TRP 2 by using the corresponding information.
In addition, for M-TRP PUCCH repetition transmission, a configuration method has been improved so that two spatial relation info may be configured in a PUCCH resource. That is, when power control (PC) parameters such as PLRS, Alpha, PO, and closed loop index are set/configured for each spatial relation info, spatial relation RS may be configured. As a result, PC information and spatial relation RS information corresponding to the two TRPs may be configured through the two spatial relation info. Through this, the terminal transmits the UCI (i.e., CSI, ACK/NACK, SR, etc.) PUCCH by using the first spatial relation info in the first TO, and transmits the same UCI PUCCH by using the second spatial relation info in the second TO. In the present disclosure, a PUCCH resource configured with two spatial relation info may be referred to as an M-TRP PUCCH resource, and a PUCCH resource configured with one spatial relation info may be referred to as an S-TRP PUCCH resource.
Additionally, with respect to the proposal of the present disclosure, a unified TCI framework scheme may be considered. That is, the UL TCI state as well as the DL TCI state may be indicated together through the DL DCI (e.g., DCI format 1_1/1_2, etc.). Alternatively, only the UL TCI state may be indicated without indicating the DL TCI state through the DL DCI. Through this, schemes conventionally used for UL beam and power control (PC) configuration may be replaced through the above-described UL TCI state indication scheme.
As a specific example, one UL TCI state may be indicated through a TCI field in DL DCI. In this case, the UL TCI state may be applied to all PUSCH/PUCCHs after a certain time (e.g., beam application time), and may be applied to some or all of the indicated SRS resource sets. Alternatively, multiple UL TCI states (and/or DL TCI states) may be indicated through the TCI field in the DL DCI.
Method for Transmitting Physical Control Channel Considering Simultaneous Transmission Related to Multiple Transmission Element/Multiple Transmission Target
New methods in which a terminal simultaneously transmits several channels (CH)/reference signals (RSs) of the same type, the terminal simultaneously transmits several CHs/RSs of different types are being discussed. In the conventional scheme, the operation of the terminal transmitting a plurality of CHs/RSs in one time point (or in one time unit) is restricted. For example, for a terminal according to the conventional scheme, simultaneous transmission of a plurality of SRS resources belonging to different SRS resource sets is supported for uplink beam measurement, but simultaneous transmission of a plurality of different PUSCHs is not supported. Therefore, in order to support a more advanced terminal operation by alleviating the above restrictions, a method for simultaneously transmitting a plurality of CHs/RSs using a plurality of transmission elements of one terminal is being discussed.
For example, according to the present disclosure, a terminal may simultaneously perform uplink transmissions for multiple transmission targets using multiple transmission elements. In addition, the base station may simultaneously receive the uplink transmissions transmitted through the multiple transmission elements from the terminal in the multiple transmission targets. For example, a transmission element of the terminal may correspond to an antenna group or an antenna panel, and one antenna group/panel may correspond to one RS set (or one RS candidate set). That is, the antenna group/panel may be indicated/identified by the RS (candidate) set. For example, the transmission target of uplink transmission from the terminal may correspond to a TRP or a cell, and one TRP/cell may correspond to one CORESET group/pool. That is, the TRP/cell may be indicated/identified by the CORESET group/pool. For example, a simultaneous uplink transmission scheme for multiple transmission targets through multiple transmission elements may be referred to as simultaneous transmission across multi-panel (STxMP). However, the scope of the present disclosure is not limited by the name of the transmission scheme, the examples of the unit of the transmission element, and/or the examples of the unit of the transmission target.
As one example of STxMP operation, two PUSCHs corresponding to two UL TBs (e.g., a first PUSCH carrying a first TB, a second PUSCH carrying a second TB) may be scheduled on the same RB. In addition, an individual TCI state may be configured/indicated for each of a plurality of PUSCH transmissions. A plurality of TCI states may correspond to a plurality of transmission elements (e.g., a panel/RS set), respectively. In addition, one transmission element may correspond to one transmission target, respectively, and a plurality of transmission elements may correspond to one transmission target.
For example, a first spatial relation RS and a first power control (PC) parameter set (or a first UL TCI state) may be configured/indicated for a first PUSCH transmission, and a second spatial relation RS and a second PC parameter set (or a second UL TCI state) may be configured/indicated for a second PUSCH transmission. For example, the terminal may transmit a first PUSCH using a first panel corresponding to a first UL TCI state in a first time unit, and may transmit a second PUSCH using a second panel corresponding to a second UL TCI state in the first time unit. For example, the terminal may transmit (for the first CORESET pool) the first PUSCH through the first RS set based on the first UL TCI state in the first time unit, and may transmit the second PUSCH (for the second CORESET pool) through the second RS set based on the second UL TCI in the first time unit. A time unit may correspond to at least one of a symbol, a symbol group, a slot, or a slot group.
In this regard, when performing PUSCH scheduling through DCI, the base station may indicate whether to transmit the corresponding PUSCH through STxMP, single panel, or M-TRP repetition PUSCH. In this case, the terminal needs to have STxMP-related capabilities, and the STxMP mode needs to be enabled in advance through higher layer signaling (e.g., RRC signaling, etc.). For the indication, an existing SRS resource set indication field may be redefined and used, or a new DCI field may be introduced/defined.
For example, in the case of M-DCI-based M-TRP operation with a plurality of CORESET pools in a wireless communication system, a PUCCH linked to the first coreset pool (e.g., CORESET Pool 0) (e.g., first pucch, pucch 0) and a PUCCH linked to the second coreset pool (e.g. CORESET Pool 1) (e.g., second pucch, pucch 1) may be not scheduled for overlap at the same time, and may be Time Division Multiplexed (TDMed).
Unlike this, in a case of a collision between PUCCH linked to the same CORESET pool or a collision between PUCCH/PUSCH, it may be multiplexed with one channel, or some channels may be dropped according to the existing collision handling rule.
However, a terminal with STXMP-based transmission capability as described above (i.e. an enhanced terminal) may simultaneously transmit multiple PUCCHs that have occurred collision through multiple transmission elements (e.g., panels), without multiplexing/dropping. Additionally, a network (e.g., a base station) may simultaneously schedule PUCCHs linked to different CORESET pools for a corresponding terminal without the need for TDM-based scheduling, and the corresponding terminal may transmit PUCCHs linked to each CORESET pool according to the STxMP scheme.
The present disclosure proposes a method for determining under what conditions (existing) multiplexing/dropping is applied and under what conditions simultaneous transmission (e.g., STxMP-based transmission) is performed, when multiple PUCCHs are scheduled with overlapping for an STxMP-based transmission-enabled terminal.
In step S810, the terminal may receive transmission reference information related to a plurality of uplink channels from a network.
Here, the transmission reference information may include at least one of a control resource set pool (CORESET pool), an uplink channel group, an uplink channel format, uplink contents or a transmission scheme.
In step S820, the terminal may transmit at least one of the plurality of uplink channels to the network (in one time unit), based on the transmission reference information.
In this regard, the transmission of the at least one of the plurality of uplink channels may be performed based on at least one of i) a first operation corresponding to simultaneous transmission of the plurality of uplink channels or ii) a second operation corresponding to at least one of multiplexing or partial drop for the plurality of uplink channels. For example, the first operation may correspond to the above-described STxMP-based transmission, and the second operation may correspond to an operation according to the above-described (existing) collision resolution rule.
For example, when the plurality of uplink channels are associated with different CORESET pools, the transmission of the at least one of the plurality of uplink channels may be performed according to the first operation. On the other hand, when the plurality of uplink channels are associated with a same CORESET pool, the transmission of the at least one of the plurality of uplink channels may be performed according to the second operation.
For example, when the plurality of uplink channels are associated with different uplink channel groups, the transmission of the at least one of the plurality of uplink channels may be performed according to the first operation. On the other hand, when the plurality of uplink channels are associated with a same uplink channel group, the transmission of the at least one of the plurality of uplink channels may be performed according to the second operation.
For example, whether the transmission of the at least one of the plurality of uplink channels is performed according to the first operation may be determined based on at least one of the uplink channel format, the uplink contents or the transmission scheme for the plurality of uplink channels.
For example, when the number of the plurality of uplink channels exceeds the number of simultaneous transportable by the terminal, uplink channel(s) of the number of simultaneous transportable may be transmitted according to the first operation. In this regard, the uplink channel(s) of the number of simultaneous transportable may be associated with different reference signal candidate sets, respectively. Additionally or alternatively, the uplink channel(s) of the number of simultaneous transportable may be determined based on at least one of an index of the CORESET pool, an index of the uplink channel group or an index of resources.
For example, an application of the first operation or the second operation for the at least one of the plurality of uplink channels may be determined based on the number of uplink transmission configuration indicators (UL TCIs) configured for each of the plurality of uplink channels.
For example, the terminal may receive, from the network, indication information on an application of the first operation or the second operation related to the transmission of the at least one of the plurality of uplink channels. In this case, the terminal may perform uplink channel transmission by applying the first operation/second operation according to the corresponding indication information.
For example, the uplink contents may correspond to at least one of HARQ-ACK (Hybrid Automatic Repeat Request-acknowledgement) information, scheduling request or channel state information (CSI). Additionally or alternatively, the transmission scheme may be distinguished/classified based on whether an uplink channel is repeatedly transmitted.
In step S910, the base station may transmit transmission reference information related to a plurality of uplink channels to a terminal.
Here, the transmission reference information may include at least one of a control resource set pool (CORESET pool), an uplink channel group, an uplink channel format, uplink contents or a transmission scheme.
In step S920, the base station may receive at least one of the plurality of uplink channels from the terminal (in one time unit), based on the transmission reference information.
In this regard, the transmission of the at least one of the plurality of uplink channels may be performed based on at least one of i) a first operation corresponding to simultaneous transmission of the plurality of uplink channels or ii) a second operation corresponding to at least one of multiplexing or partial drop for the plurality of uplink channels. For example, the first operation may correspond to the above-described STxMP-based transmission, and the second operation may correspond to an operation according to the above-described (existing) collision resolution rule.
Since specific examples of the transmission reference information, the first operation (i.e., simultaneous transmission), and the second operation (i.e., multiplexing/partial drop) are the same as those described in
In the examples of
Hereinafter, in the present disclosure, when multiple physical control channels are scheduled with overlapping for a terminal for which simultaneous transmission is supported, a detailed method for transmitting/dropping/multiplexing a physical control channel by a terminal will be through various embodiments.
In the present disclosure, a case in which two UL TCI states are configured/indicated by a unified TCI indication scheme, two spatial relation info/RS and PC sets are configured by an existing UL M-TRP transmission method and two transmission elements (e.g., panels) are used is described as an example, the scope of the present disclosure is not limited to the example. That is, the proposal of the present disclosure may be extended and applied even when more than two (e.g., N1) UL TCI states are configured/indicated by the unified TCI indication scheme, when more than two (e.g., N2) spatial relation info/RS and PC sets are configured/indicated, and when more than two transmission elements are used.
Hereinafter, the proposal of the present disclosure has been described as a representative example of PUCCH, but may be extended and applied to other channels such as PUSCH/PDSCH/PDCCH.
Additionally, for clarity of description below, although a panel is assumed and described as a representative example of a transmission element of a terminal and a CORESET pool is assumed and described as a representative example of a transmission target of a terminal, the scope of the present disclosure is not limited to the example.
The embodiments described below are differentiated for clarity of explanation, and each embodiment may be applied independently, or a part/all configuration of one embodiment may be applied in combination/combination/replacement with some entire configurations of another embodiment.
A method of transmitting by the terminal the corresponding PUCCHs in the STxMP method when two PUCCHs in which a collision occurs are linked to different CORESET pools, otherwise, applying an existing collision handling rule may be considered.
For example, two TRPs corresponding to two CORESET pools have a large backhaul delay (e.g., a delay of tens of ms or more that may not be dynamically coordinated), and perform scheduling independent of each other.
Considering this point, it may not be desirable to multiplex PUCCHs linked to different CORESET pools. This is because a delay occurs in transmitting a multiplexed PUCCH received by one TRP to another TRP due to a backhaul delay.
Additionally, it may not be desirable to drop PUCCHs linked to different CORESET claim pools. This is because it is difficult for a TRP to receive a dropped PUCCH to recognize whether or not the corresponding PUCCH has been dropped because it may not recognize the PUCCH scheduling status of other TRPs.
Therefore, when two PUCCHs are linked to different CORESET pools, it may be desirable for the terminal to transmit the corresponding PUCCHs in the STxMP scheme. On the other hand, when two PUCCHs are linked to the same CORESET pool (or regarded as the same CORESET pool when there is no CORESET pool configuration), the terminal may follow the existing collision handling rule.
Additionally, in a case that CORESET pools are expanded to three or more, if PUCCH resources belonging to/connected to each of a first CORESET pool (e.g., CORESET pool 0), a second CORESET pool (e.g., CORESET pool 1) and a third CORESET pool (e.g., CORESET pool 2) are collided, the terminal may perform STxMP-based transmission by selecting two PUCCH resources from among three PUCCH resources.
In this regard, since a terminal supporting two panels may transmit two PUCCHs according to the STxMP scheme, one PUCCH resource needs to be dropped. In this case, the terminal may perform STxMP-based transmission by selecting two PUCCHs with low indexes and drop the PUCCH with a high index, based on the CORESET pool index/PUCCH resource index.
If the two PUCCHs selected as described above are associated with the same panel (i.e., configured to be transmitted using the same panel), the method may not be effective. Therefore, in this case, it is necessary to prioritize distinguishing PUCCHs associated with different panels. Thereafter, it may be desirable that the terminal selects a PUCCH based on the CORESET pool index/PUCCH resource index within the PUCCHs associated with the first panel, and selects a PUCCH based on the CORESET pool index/PUCCH resource index within the PUCCHs associated with the second panel. The corresponding method may also be used in Example 2 to be described later.
Additionally, STxMP-based transmission for two PUCCHs with different CORESET pools may not always be possible. For example, a terminal capable of STxMP but preferring/performing communication with both TRPs through the same panel due to a channel status between TRP-panels (hereinafter referred to as a first terminal) and a terminal unable to STxMP (hereinafter referred to as a second terminal) may be considered.
In the case of the second terminal, the corresponding terminal may report to the base station whether or not STxMP transmission is available in different CORESET pools as a UE capability, specifically, the terminal may distinguish and report whether STxMP is available in the same CORESET pool or not and whether STxMP is available between different CORESET pools. In the case of the first terminal, a terminal report on whether STxMP is available between different CORESET pools or not may be required for the corresponding terminal. The report may be consist of/configured with a MAC-CE or a dynamic UCI report, and considering that the report has an event based report property, a report based on the MAC-CE may be desirable.
A method of transmitting by the terminal the corresponding PUCCHs in the STxMP method when two PUCCHs in which a collision occurs are linked to different PUCCH groups, otherwise, applying an existing collision handling rule may be considered.
In this regard, a terminal may be configured with up to four PUCCH groups, and one or more PUCCH resources may be configured for each PUCCH group. The base station may reduce signaling overhead by updating a beam/power control (PC) set/spatial relation info/spatial relation RS for PUCCH(s) belonging to the same PUCCH group at once.
For example, the PUCCH resources of the first TRP may be configured to the first PUCCH group, and the PUCCH resources of the second TRP may be configured to the second PUCCH group, and then, the PUCCHs of each TRP may be grouped and used. In this case, a beam/power control (PC) set/spatial relation info/spatial relation RS for each group may be updated at once. Through this, the base station may commonly manage PUCCHs belonging to/bound to the same PUCCH group, and individually/separately manage PUCCHs existing in different PUCCH groups.
Considering the properties of the above-described PUCCH groups, it may be desirable that a (existing) collision handling rule is applied to PUCCHs of the same group and STxMP-based transmission is performed for PUCCHs of different groups.
When PUCCH resources belonging to each of the first PUCCH group, the second PUCCH group, and the third PUCCH group collide, the terminal selects two PUCCH resources from among the three PUCCH resources to perform STxMP-based transmission.
In this regard, since a terminal supporting two panels may transmit two PUCCHs according to the STxMP scheme, one PUCCH resource needs to be dropped. In this case, the terminal may perform STxMP-based transmission by selecting two PUCCHs with low indexes and drop the PUCCH with a high index, based on the PUCCH group index/PUCCH resource index.
If the two PUCCHs selected as described above are associated with the same panel (i.e., configured to be transmitted using the same panel), the method may not be effective. Therefore, in this case, as in Embodiment 1 described above, it is necessary to prioritize distinguishing PUCCHs associated with different panels. Thereafter, it may be desirable that the terminal selects a PUCCH based on the PUCCH group index/PUCCH resource index within the PUCCHs associated with each panel.
A method of applying an existing collision handling rule between PUCCH groups linked to the same CORESET pool when a linkage between a PUCCH group and a CORESET pool is configured/established, and performing STxMP-based transmission between PUCCH groups linked to different CORESET pools may be considered.
For example, a first PUCCH group and a second PUCCH group may be linked to a first CORESET pool (e.g., CORESET pool 0), and a third PUCCH group and a fourth PUCCH group may be linked to a second CORESET pool (e.g., CORESET pool 1). In this case, for a collision between PUCCHs belonging to the first PUCCH group and the second PUCCH group or between PUCCHs belonging to the third PUCCH group and the fourth PUCCH group, an existing collision handling rule may be applied. On the other hand, when there is a collision between PUCCHs belonging to PUCCH groups linked to different CORESET pools (e.g., the first PUCCH group and the third PUCCH group), the terminal may transmit the corresponding PUCCHs according to the STxMP scheme.
A method of restricting to perform STxMP-based transmission for collisions between specific PUCCH formats or restricting to perform STxMP-based transmission for collisions between specific UCI contents may be considered.
For example, information on a PUCCH format capable of STxMP-based transmission may be separately indicated to the terminal by the base station or may be agreed/defined in advance between the base station and the terminal. When the corresponding PUCCHs collide, the terminal may transmit the corresponding PUCCHs according to the STxMP scheme.
Alternatively, STxMP-based transmission may be performed only between same PUCCH formats, or conversely, STxMP-based transmission may be restricted to be performed only between different PUCCH formats.
For example, PUCCH formats 3 and 4 are similar in DMRS pattern/UCI encoding scheme, etc., and PUCCH formats 0, 1 and 2 may generate signals in a completely different manner from PUCCH formats 3 and 4. Additionally, signals may be generated in completely different ways between PUCCH formats 0, 1 and 2. Therefore, as described above, STxMP-based transmission may be performed for signals having similar signal generation schemes, and STxMP-based transmission may not be performed between different schemes.
Alternatively, whether to perform STxMP-based transmission may be determined according to whether the PUCCH on which a collision occurs is a long PUCCH (e.g., PUCCH format 1/3/4) or a short PUCCH (e.g., PUCCH format 0/2).
For example, simultaneous transmission (i.e., STxMP-based transmission) is possible in a collision between long PUCCHs or between short PUCCHs, and simultaneous transmission may not be possible in a collision between a long PUCCH and a short PUCCH.
According to the proposal of the present disclosure, when a collision between PUCCHs not performing STxMP transmission occurs, the terminal may drop/multiplex the PUCCH according to an existing collision handling rule.
Additionally or alternatively, UCI content capable of STxMP-based transmission (e.g., ACK/NACK, SR, periodic (P)-CSI, semi-persistent (SP)-CSI, aperiodic (AP)-CSI, etc.) may be configured by the base station or agreed/defined in advance between the base station and the terminal. When PUCCHs including the corresponding UCI collide, the terminal may transmit the corresponding PUCCHs according to the STxMP scheme. Alternatively, the terminal may perform STxMP-based transmission only between the same UCI contents or, conversely, STxMP-based transmission only between different UCI contents.
In the above-described embodiments (e.g., embodiments 1 to 4) of the present disclosure, it has been described assuming that one UL TCI (or spatial relation info/RS and/or PC set) is configured in a PUCCH resource.
Accordingly, when a collision between two PUCCHs occurs, a terminal supporting two panels may perform STxMP-based transmission by applying the UL TCI (i.e., UL TCI state) of each PUCCH. On the other hand, the base station may configure two UL TCIs for one PUCCH, and the terminal may perform STxMP-based transmission using the corresponding PUCCH. That is, the terminal may transmit one PUCCH through a first panel corresponding to a first UL TCI and simultaneously transmit the same PUCCH through a second panel corresponding to a second UL TCI.
For clarity of description below, as described above, a PUCCH configured with two UL TCIs is referred to as PUCCH A, and a PUCCH configured with one UL TCI is referred to as PUCCH B.
Transmission for PUCCH A/PUCCH B may be performed according to at least one of the following methods (options 5-1 to 5-4).
(Option 5-1)
When a collision between PUCCH A and PUCCH B occurs, the terminal may prioritize PUCCH A and drop PUCCH B or, conversely, prioritize PUCCH B and drop PUCCH A.
(Option 5-2)
When a collision between PUCCH A and PUCCH B occurs, PUCCH B may be multiplexed to PUCCH A and transmitted. At this time, the PUCCH may be transmitted using UL TCI in which the same RS is configured, by comparing the QCL reference RS (i.e., spatial relation RS) defined for the two UL TCIs of PUCCH A and the QCL reference RS of PUCCH B. Additionally, PUCCH transmission using different UL TCI may not be performed.
For example, a first UL TCI and a second UL TCI may be configured for PUCCH A, a third UL TCI may be configured for PUCCH B, and the QCL reference RSs of the first UL TCI and the third UL TCI may be the same. In this case, PUCCH B is multiplexed with PUCCH A, and the terminal may transmit PUCCH A through the first UL TCI. That is, STxMP-based transmission is not performed, and the corresponding PUCCH is transmitted through a single panel. Alternatively, the terminal may transmit the multiplexed PUCCH A through the first UL TCI and transmit the existing UCI of the non-multiplexed PUCCH A through the second UL TCI, thereby the terminal may perform STxMP-based transmission through two panels.
In the above method, comparison of QCL reference RSs has been utilized, but in addition to the top QCL source RS (i.e., QCL reference RS of QCL reference RS of UL TCI (e.g. RS A) or QCL reference RS of RS A)) may be compared.
Alternatively, instead of comparing QCL reference RSs, when UL panel information for TCI (i.e., UL TCI) exists/is configured, the above-described method may be applied through comparison between UL panels.
Alternatively, instead of comparing QCL reference RSs, the multiplexed UCI may be transmitted according to the STxMP scheme by multiplexing PUCCH B to PUCCH A and using/applying both two UL TCIs of PUCCH A.
(Option 5-3)
When a collision between PUCCH A and PUCCH B occurs, PUCCH A may be multiplexed with PUCCH B and transmitted. That is, UCI of two PUCCHs may be multiplexed and transmitted through PUCCH B.
At this time, as proposed in the above-described option 5-2, by comparing the QCL reference RS, the top QCL source RS, and the UL panel, and the like, the terminal may transmit PUCCH A and PUCCH B according to the STxMP scheme by additionally transmitting PUCCH A using a UL TCI that is not the same as the UL TCI of PUCCH B among two UL TCIs of PUCCH A.
For example, a first UL TCI and a second UL TCI may be configured and ACK/NACK transmission may be configured for PUCCH A, and a third Ul TCI may be configured and CSI transmission may be configured for PUCCH B. In this case, if the QCL reference RSs of the first UL TCI and the third UL TCI are the same, the terminal may multiplex ACK/NACK information and CSI and transmit them through PUCCH B, and simultaneously transmit the ACK/NACK information through PUCCH A by applying the second UL TCI.
(Option 5-4)
The terminal may transmit PUCCH A by applying only one UL TCI among two UL TCIs of PUCCH A and transmit PUCCH B, thereby transmitting PUCCH A and PUCCH B according to the STxMP scheme. As a result, PUCCH A may not be repeatedly transmitted through STxMP-based transmission but is transmitted only once, and PUCCH B may be simultaneously transmitted using the remaining panel(s) instead.
At this time, which UL TCI to apply among the two UL TCIs of PUCCH A may be determined through a method as in the following example. For example, the TCI having the lowest TCI state ID among the two UL TCIs may be determined to be applied. As another example, it may be determined to apply a first UL TCI (1st TCI state) among two UL TCIs. As another example, among the two UL TCIs, a UL TCI having a QCL reference RS different from the UL TCI of PUCCH B may be determined.
As a PUCCH transmission scheme, there are various schemes such as S-TRP-based PUCCH repetition/M-TRP-based PUCCH repetition/PUCCH without repetition.
In this regard, a method of applying or not applying STxMP-based transmission according to a transmission method in which a PUCCH in which a collision occurs is transmitted will be proposed.
For example, in the case of collision between repeated PUCCHs, STxMP-based transmission may be excluded, and existing collision handling rule may be applied.
In the case of a collision between an S-TRP-based repeated PUCCH and a non-repetition PUCCH, the repeated PUCCH may be given priority according to an existing collision handling rule. Additionally or alternatively, in this case, if the transmission panels of the S-TRP-based repeated PUCCH and the non-repeated PUCCH are different, STxMP-based transmission may be allowed.
Even in the case of a collision between a repeated PUCCH based on M-TRP and a PUCCH that is not repeated, STxMP based transmission may be disallowed by prioritizing M-TRP based repeated PUCCH. This is because, in the case of M-TRP based PUCCH repetition, it is complicated because a beam sweep may occur. Additionally or alternatively, when a collision occurs between a specific TO of an M-TRP based repeated PUCCH and a non-repeated PUCCH, STxMP-based transmission may be allowed if transmission panels of the two PUCCHs are different.
Additionally, when multiple TOs of repeated PUCCHs collide with non-repeated PUCCHs, the following scheme may be considered.
For example, in the case of intra-slot PUCCH repetition, a plurality of short PUCCHs may be repeatedly transmitted in one slot, and collision between one long PUCCH configured not to be repeated and the plurality of short PUCCHs may occur. In this case, STxMP-based transmission may be performed on a short PUCCH having a different transmission panel from a long PUCCH among a plurality of short PUCCHs in which a collision occurs, and an otherwise short PUCCH may be dropped. Alternatively, the terminal may drop all short PUCCHs in which collisions occur and preferentially transmit the long PUCCH. Conversely, the terminal may drop the long PUCCH and transmit the short PUCCH.
The proposals of the present disclosure may be applied through a specific rule, but the base station may directly indicate/provide configuration for a (specific) proposal method to the terminal without applying the specific rule.
According to the above-described proposal of the present disclosure, when the terminal capable of supporting simultaneous transmission (e.g., STxMP based transmission) and enabled receives scheduling/configuration of the collided PUCCHs, ambiguity regarding transmission/drop/multiplexing of the corresponding PUCCHs is resolved, and the PUCCH transmission scheme 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 included 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 100, 200 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 Ml, 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 100, 200 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-0052401 | Apr 2022 | KR | national |
| 10-2022-0082027 | Jul 2022 | KR | national |
