Patent Application
20250151063
The present disclosure relates to a wireless communication system, and more specifically to a method and device 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.
The technical problem of the present disclosure is to provide a method and device for performing uplink transmission and reception in a wireless communication system.
In addition, an additional technical problem of the present disclosure is to provide a method and device for transmitting and receiving absolute/relative timing advance (TA) commands set for each of a plurality of timing advance groups (TAGs) set for a serving cell.
Additionally, an additional technical problem of the present disclosure is to provide a method and device for managing/applying TA values for each of the plurality of TAGs set for the serving cell.
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.
According to one embodiment of the present disclosure, a method for of performing uplink transmission by a user equipment (UE) in a wireless communication system may include receiving configuration information related to a serving cell from a base station, wherein the configuration information including information about a plurality of timing advance groups (TAGs) associated with the serving cell; receiving, from the base station, downlink control information (DCI) including first indication information and second indication information; and performing at least one of first uplink transmission or second uplink transmission based on at least one of the first indication information or the second indication information, and based on the first uplink transmission being performed using the first indication information, a first transmission timing of the first uplink transmission may be based on a first TA value associated with a first TAG corresponding to the first indication information among the plurality of TAGs, and based on the second uplink transmission being performed using the second indication information, a second transmission timing of the second uplink transmission may be based on a second TA value associated with a second TAG corresponding to the second indication information among the plurality of TAGs.
According to one embodiment of the present disclosure, a method of performing uplink reception by a base station in a wireless communication system may include transmitting configuration information related to a serving cell to a user equipment (UE), wherein the configuration information including information about a plurality of timing advance groups (TAGs) associated with the serving cell; transmitting, to the UE, downlink control information (DCI) including first indication information and second indication information; and performing at least one of first uplink reception or second uplink reception based on at least one of the first indication information or the second indication information, and based on the first uplink reception being performed using the first indication information, a first transmission timing of the first uplink transmission may be based on a first TA value associated with a first TAG corresponding to the first indication information among the plurality of TAGs, and based on the second uplink reception being performed using the second indication information, a second transmission timing of the second uplink transmission may be based on a second TA value associated with a second TAG corresponding to the second indication information among the plurality of TAGs.
According to an embodiment of the present disclosure, a method and device for performing uplink transmission and reception in a wireless communication system may be provided.
In addition, according to various embodiments of the present disclosure, a method and device for transmitting and receiving absolute/relative TA commands configured for each of a plurality of TAGs configured for a serving cell may be provided.
In addition, according to various embodiments of the present disclosure, a method and device for managing/applying TA values for each of a plurality of TAGs set for a serving cell 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. Abase station (BS) may be substituted with a term such as a fixed station, a Node B, an eNB(evolved-NodeB), a gNB(Next Generation NodeB), a BTS(base transceiver system), an Access Point(AP), a Network(5G network), an AI(Artificial Intelligence) system/module, an RSU(road side unit), a robot, a drone(UAV: Unmanned Aerial Vehicle), an AR(Augmented Reality) device, a VR(Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be substituted with a term such as a UE(User Equipment), an MS(Mobile Station), a UT(user terminal), an MSS(Mobile Subscriber Station), an SS(Subscriber Station), an AMS(Advanced Mobile Station), a WT(Wireless terminal), an MTC(Machine-Type Communication) device, an M2M(Machine-to-Machine) device, a D2D(Device-to-Device) device, a vehicle, an RSU(road side unit), a robot, an AI(Artificial Intelligence) module, a drone(UAV: Unmanned Aerial Vehicle), an AR(Augmented Reality) device, a VR(Virtual Reality) device, etc.
The following description may be used for a variety of radio access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by a wireless technology such as UTRA(Universal Terrestrial Radio Access) or CDMA2000. TDMA may be implemented by a radio technology such as GSM(Global System for Mobile communications)/GPRS(General Packet Radio Service)/EDGE(Enhanced Data Rates for GSM Evolution). OFDMA may be implemented by a radio technology such as IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802-20, E-UTRA(Evolved UTRA), etc. UTRA is a part of a UMTS(Universal Mobile Telecommunications System). 3GPP(3rd Generation Partnership Project) LTE(Long Term Evolution) is a part of an E-UMTS(Evolved UMTS) using E-UTRA and LTE-A(Advanced)/LTE-A pro is an advanced version of 3GPP LTE. 3GPP NR(New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE/LTE-A/LTE-A pro.
To clarify description, it is described based on a 3GPP communication system (e.g., LTE-A, NR), but a technical idea of the present disclosure is not limited thereto. LTE means a technology after 3GPP TS(Technical Specification) 36.xxx Release 8. In detail, an LTE technology in or after 3GPP TS 36.xxx Release 10 is referred to as LTE-A and an LTE technology in or after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR means a technology in or after TS 38.xxx Release 15. LTE/NR may be referred to as a 3GPP system. “xxx” means a detailed number for a standard document. LTE/NR may be commonly referred to as a 3GPP system. For a background art, a term, an abbreviation, etc. used to describe the present disclosure, matters described in a standard document disclosed before the present disclosure may be referred to. For example, the following document may be referred to.
For 3GPP LTE, TS 36.211(physical channels and modulation), TS 36.212(multiplexing and channel coding), TS 36.213(physical layer procedures), TS 36.300(overall description), TS 36.331(radio resource control) may be referred to.
For 3GPP NR, TS 38.211(physical channels and modulation), TS 38.212(multiplexing and channel coding), TS 38.213(physical layer procedures for control), TS 38.214(physical layer procedures for data), TS 38.300(NR and NG-RAN(New Generation-Radio Access Network) overall description), TS 38.331(radio resource control protocol specification) may be referred to.
Abbreviations of terms which may be used in the present disclosure is defined as follows.
As more communication devices have required a higher capacity, a need for an improved mobile broadband communication compared to the existing radio access technology (RAT) has emerged. In addition, massive MTC (Machine Type Communications) providing a variety of services anytime and anywhere by connecting a plurality of devices and things is also one of main issues which will be considered in a next-generation communication. Furthermore, a communication system design considering a service/a terminal sensitive to reliability and latency is also discussed. As such, introduction of a next-generation RAT considering eMBB(enhanced mobile broadband communication), mMTC(massive MTC), URLLC(Ultra-Reliable and Low Latency Communication), etc. is discussed and, for convenience, a corresponding technology is referred to as NR in the present disclosure. NR is an expression which represents an example of a 5G RAT.
A new RAT system including NR uses an OFDM transmission method or a transmission method similar to it. A new RAT system may follow OFDM parameters different from OFDM parameters of LTE. Alternatively, a new RAT system follows a numerology of the existing LTE/LTE-A as it is, but may support a wider system bandwidth (e.g., 100 MHz). Alternatively, one cell may support a plurality of numerologies. In other words, terminals which operate in accordance with different numerologies may coexist in one cell.
A numerology corresponds to one subcarrier spacing in a frequency domain. As a reference subcarrier spacing is scaled by an integer N, a different numerology may be defined.
In reference to
A NR system may support a plurality of numerologies. Here, a numerology may be defined by a subcarrier spacing and a cyclic prefix (CP) overhead. Here, a plurality of subcarrier spacings may be derived by scaling a basic (reference) subcarrier spacing by an integer N (or, 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)Te than a corresponding downlink frame in a corresponding terminal starts. For a subcarrier spacing configuration p, 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.
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 p 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 p in a frequency domain is given as in the following Equation 1.
In Equation 1, k is defined relatively to point A so that k=0 corresponds to a subcarrier centering in point A. Physical resource blocks are numbered from 0 to NBWP,isize,μ−1 in a bandwidth part (BWP) and i is a number of a BWP. A relationship between a physical resource block nPRB and a common resource block nCRB in BWP i is given by the following Equation 2.
NBWP,istart,μ is a common resource block that a BWP starts relatively to common resource block 0.
In reference to
A carrier includes a plurality of subcarriers in a frequency domain. An RB (Resource Block) is defined as a plurality of (e.g., 12) consecutive subcarriers in a frequency domain. A BWP(Bandwidth Part) is defined as a plurality of consecutive (physical) resource blocks in a frequency domain and may correspond to one numerology (e.g., an SCS, a CP length, etc.). A carrier may include a maximum N (e.g., 5) BWPs. A data communication may be performed through an activated BWP and only one BWP may be activated for one terminal. In a resource grid, each element is referred to as a resource element (RE) and one complex symbol may be mapped.
In an NR system, up to 400 MHz may be supported per component carrier (CC). If a terminal operating in such a wideband CC always operates turning on a radio frequency (FR) chip for the whole CC, terminal battery consumption may increase. Alternatively, when several application cases operating in one wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.) are considered, a different numerology (e.g., a subcarrier spacing, etc.) may be supported per frequency band in a corresponding CC. Alternatively, each terminal may have a different capability for the maximum bandwidth. By considering it, a base station may indicate a terminal to operate only in a partial bandwidth, not in a full bandwidth of a wideband CC, and a corresponding partial bandwidth is defined as a bandwidth part (BWP) for convenience. A BWP may be configured with consecutive RBs on a frequency axis and may correspond to one numerology (e.g., a subcarrier spacing, a CP length, a slot/a mini-slot duration).
Meanwhile, a base station may configure a plurality of BWPs even in one CC configured to a terminal. For example, a BWP occupying a relatively small frequency domain may be configured in a PDCCH monitoring slot, and a PDSCH indicated by a PDCCH may be scheduled in a greater BWP. Alternatively, when UEs are congested in a specific BWP, some terminals may be configured with other BWP for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, etc., some middle spectrums of a full bandwidth may be excluded and BWPs on both edges may be configured in the same slot.
In other words, a base station may configure at least one DL/UL BWP to a terminal associated with a wideband CC. A base station may activate at least one DL/UL BWP of configured DL/UL BWP(s) at a specific time (by L1 signaling or MAC CE(Control Element) or RRC signaling, etc.). In addition, a base station may indicate switching to other configured DL/UL BWP (by L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, based on a timer, when a timer value is expired, it may be switched to a determined DL/UL BWP. Here, an activated DL/UL BWP is defined as an active DL/UL BWP. But, a configuration on a DL/UL BWP may not be received when a terminal performs an initial access procedure or before a RRC connection is set up, so a DL/UL BWP which is assumed by a terminal under these situations is defined as an initial active DL/UL BWP.
In a wireless communication system, a terminal receives information through a downlink from a base station and transmits information through an uplink to a base station. Information transmitted and received by a base station and a terminal includes data and a variety of control information and a variety of physical channels exist according to a type/a usage of information transmitted and received by them.
When a terminal is turned on or newly enters a cell, it performs an initial cell search including synchronization with a base station or the like (S601). For the initial cell search, a terminal may synchronize with a base station by receiving a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from a base station and obtain information such as a cell identifier (ID), etc. After that, a terminal may obtain broadcasting information in a cell by receiving a physical broadcast channel (PBCH) from a base station. Meanwhile, a terminal may check out a downlink channel state by receiving a downlink reference signal (DL RS) at an initial cell search stage.
A terminal which completed an initial cell search may obtain more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S602).
Meanwhile, when a terminal accesses to a base station for the first time or does not have a radio resource for signal transmission, it may perform a random access (RACH) procedure to a base station (S603 to S606). For the random access procedure, a terminal may transmit a specific sequence as a preamble through a physical random access channel (PRACH) (S603 and S605) and may receive a response message for a preamble through a PDCCH and a corresponding PDSCH (S604 and S606). A contention based RACH may additionally perform a contention resolution procedure.
A terminal which performed the above-described procedure subsequently may perform PDCCH/PDSCH reception (S607) and PUSCH(Physical Uplink Shared Channel)/PUCCH(physical uplink control channel) transmission (S608) as a general uplink/downlink signal transmission procedure. In particular, a terminal receives downlink control information (DCI) through a PDCCH. Here, DCI includes control information such as resource allocation information for a terminal and a format varies depending on its purpose of use.
Meanwhile, control information which is transmitted by a terminal to a base station through an uplink or is received by a terminal from a base station includes a downlink/uplink ACK/NACK(Acknowledgement/Non-Acknowledgement) signal, a CQI(Channel Quality Indicator), a PMI(Precoding Matrix Indicator), a RI(Rank Indicator), etc. For a 3GPP LTE system, a terminal may transmit control information of the above-described CQI/PMI/RI, etc. through a PUSCH and/or a PUCCH.
Table 5 represents an example of a DCI format in an NR system.
In reference to Table 5, DCI formats 0_0, 0_1 and 0_2 may include resource information (e.g., UL/SUL(Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to a transport block(TB) (e.g., MCS(Modulation Coding and Scheme), a NDI(New Data Indicator), a RV(Redundancy Version), etc.), information related to a HARQ(Hybrid—Automatic Repeat and request) (e.g., a process number, a DAI(Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, an antenna port, a CSI request, etc.), power control information (e.g., PUSCH power control, etc.) related to scheduling of a PUSCH and control information included in each DCI format may be pre-defined.
DCI format 0_0 is used for scheduling of a PUSCH in one cell. Information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled by a C-RNTI(Cell Radio Network Temporary Identifier) or a CS-RNTI(Configured Scheduling RNTI) or a MCS-C-RNTI(Modulation Coding Scheme Cell RNTI) and transmitted.
DCI format 0_1 is used to indicate scheduling of one or more PUSCHs or configure grant (CG) downlink feedback information to a terminal in one cell. Information included in DCI format 0_1 is CRC scrambled by a C-RNTI or a CS-RNTI or a SP-CSI-RNTI(Semi-Persistent CSI RNTI) or a MCS-C-RNTI and transmitted.
DCI format 0_2 is used for scheduling of a PUSCH in one cell. Information included in DCI format 0_2 is CRC scrambled by a C-RNTI or a CS-RNTI or a SP-CSI-RNTI or a MCS-C-RNTI and transmitted.
Next, DCI formats 1_0, 1_1 and 1_2 may include resource information (e.g., frequency resource allocation, time resource allocation, VRB(virtual resource block)-PRB(physical resource block) mapping, etc.), information related to a transport block(TB)(e.g., MCS, NDI, RV, etc.), information related to a HARQ (e.g., a process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., an antenna port, a TCI(transmission configuration indicator), a SRS(sounding reference signal) request, etc.), information related to a PUCCH (e.g., PUCCH power control, a PUCCH resource indicator, etc.) related to scheduling of a PDSCH and control information included in each DCI format may be pre-defined.
DCI format 1_0 is used for scheduling of a PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled by a C-RNTI or a CS-RNTI or a MCS-C-RNTI and transmitted.
DCI format 1_1 is used for scheduling of a PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled by a C-RNTI or a CS-RNTI or a MCS-C-RNTI and transmitted.
DCI format 1_2 is used for scheduling of a PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled by a C-RNTI or a CS-RNTI or a MCS-C-RNTI and transmitted.
The uplink frame number i for transmission from the UE starts TTA=(NTA+NTA,offset)Tc before the start of the corresponding downlink frame (i.e., downlink frame i) in the UE. That is, the uplink frame starts TTA before the corresponding downlink frame. Here, NTA,offset can be given except for msgA transmission on PUSCH (in this case, NTA=0).
Hereinafter, the NTA configuration method will be described.
NTA may be configured through i) a random access response (RAR), or ii) a timing advance command MAC control element (CE: control element).
In the case of a random access response or an absolute timing advance command MAC CE (TA) for a timing advance group, the timing advance command indicates NTA values with index values of TA=0, 2, . . . , 3846.
Here, the amount of time alignment for a TAG with a SCS of 2μ·15 kHz is NTA=TA·16·64/2μ. NTA is relative to the SCS of the first uplink transmission from the UE after receipt of the random access response or absolute timing advance command MAC CE.
MAC CE (hereinafter MAC RAR) for random access response has a fixed size as shown in
Timing advance command (TA) for TAG is index values of TA=0, 1, 2, . . . , 63 and indicates adjustment of the current NTA value (i.e., NTA_old) to a new NTA value (i.e. NTA_new). Here, in the case of SCS of 2μ·15 kHz, NTA_new=NTA_old+(TA−31)·16·64/2μ.
Timing Advance Command MAC CE is identified by a MAC subheader having a logical channel identity (LCID). Timing Advance Command MAC CE has a fixed size and consists of 1 octet as follows.
In the present disclosure, although it mainly illustrates and describes the four-step random access procedure (i.e. the RACH procedure), since the 2-step random access procedure is not excluded, the present disclosure may be equally applied to the 2-step random access procedure.
Hereinafter, the configuration method of NTA,offset will be described.
An information element (IE) for serving cell common configuration (e.g., ServingCellConfigCommon) is used to configure cell-specific parameters of the serving cell of the UE. When the UE accesses a cell from an idle state, the IE includes parameters that may generally be obtained from SSB, master information block (MIB), or SIBs. With this IE, the network provides information in dedicated signaling when configuring secondary cells (SCells) or additional cell groups (SCGs) to the UE. Additionally, the network provides the UE with special cells (SpCell) (master cell group (MCG) and SCG) when re-establishing synchronization.
Referring to Table 6, the n-TimingAdvanceOffset field (or parameter) indicates the NTA,offset to be applied to all uplink transmissions on the corresponding serving cell. If this field does not exist, the UE applies the values defined for the duplex mode and frequency range (FR) of the corresponding serving cell. Case 2: Method of applying predefined values to the serving cell according to duplex mode and frequency range (FR)
Table 7 illustrates the values of NTA,offset.
Referring to Table 7, the value of NTA,offset is determined according to the frequency range (FR) and band (band) of the cell used for uplink transmission. In the case of neither E-UTRA-NR coexistence nor NB-IoT-NR coexistence, but an FR1 FDD or TDD band, the value of NTA,offset is 25600. In the case of E-UTRA-NR and/or NB-IoT-NR coexistence, in the case of FR1 FDD band, the value of NTA,offset is 0. For the FR1 TDD band in the E-UTRA-NR and/or NB-IoT-NR coexistence case, the value of NTA,offset is 39936. If FR2, the value of NTA,offset is 13792.
As described above, the UE identifies the value of NTA,offset based on the n-TimingAdvanceOffset field (or parameter) information. However, if the UE does not receive n-TimingAdvanceOffset field (or parameter) information, the default value of NTA,offset is set to 25600 for the FR1 band. In the case of multiple UL carriers within the same timing advance group (TAG), the UE expects the same n-TimingAdvanceOffset value for all UL carriers, and a value of 39936 for NTA,offset may also be provided for the FDD serving cell.
Hereinafter, a timing advance group (TAG) will be described.
For cells configured by RRC and also with UL configured, TAG refers to a serving cell group using the same timing reference cell and the same timing advance value. The TAG containing the SpCell of the MAC entity is referred to as the primary TAG (PTAG: Primary Timing Advance Group), while the secondary TAG (STAG: Secondary Timing Advance Group) refers to other TAGs.
IE for TAG configuration (e.g., TAG-Config) is used to set parameters for the time-alignment group.
Table 8 illustrates TAG-Config IE.
Referring to Table 8, the tag-Id field (parameter) indicates the TAG of SpCell or SCell. This field uniquely identifies the TAG within the scope of the cell group. Additionally, the timeAlignmentTimer field (parameter) indicates the timealignmenttimer value ([ms]) for the TAG with tag-Id.
The maximum number of TAGs may be determined by the standard or by the base station, and may be, for example, 4.
IE for MAC cell group configuration (e.g., MAC-CellGroupConfig) is used to configure MAC parameters for the cell group, including discontinuous reception (DRX).
Table 9 illustrates part of MAC-CellGroupConfig IE.
Referring to Table 9, the TAG-Config IE may be configured through the tag-Config field in the MAC-CellGroupConfig IE. IE (e.g., CellGroupConfig) for cell group setting is used to configure a master cell group (MCG) or secondary cell group (SCG). A cell group is associated with one MAC entity, Radio Link Control (RLC) entities and includes a set of logical channels of a primary cell (SpCell) and one or more secondary cells (SCells).
Table 10 illustrates part of CellGroupConfig IE.
Referring to Table 10, the MAC-CellGroupConfig IE may be configured through the mac-CellGroupConfig field in CellGroupConfig IE. The maximum number of secondary cell groups may be determined by the standard or by the base station, and may be, for example, 3.
According to the current standard, different TA commands are possible for each timing advance group (TAG). A TAG may correspond to one or more cell groups, so the same TA command may be applied to all serving cells (s) in the cell group (s) corresponding to a specific TAG.
Specifically, the TAG is configured by RRC and may indicate a serving cell group that uses the same timing reference cell and the same timing advance value for a cell for which UL is set. The TAG including the SpCell of the MAC entity refers to the P(primary)TAG, and the S(secondary)TAG may refer to another TAG.
The maximum number of TAGs may be determined by the standard or by the base station, and may be, for example, 4.
The following parameters may be configured for maintenance of UL time alignment by RRC signaling for the UE.
The MAC entity shall:
If the MAC entity stops uplink transmission for an SCell due to the fact that the maximum uplink transmission timing difference between TAGs of the MAC entity or the maximum uplink transmission timing difference between TAGs of any MAC entity of the UE is exceeded, the MAC entity considers the timeAlignmentTimer associated with the SCell as expired.
When the timeAlignmentTimer associated with the TAG to which the serving cell belongs is not running, the MAC entity does not perform any uplink transmission on the serving cell except random access preamble and MSGA transmission. Additionally, when the timeAlignmentTimer associated with PTAG is not running, the MAC entity does not perform any uplink transmission on any serving cell except random access preamble and MSGA transmission on SpCell.
Meanwhile, when considering multi-TRP transmission introduced in Rel-16/17, the appropriate TA may have different values for each TRP (panel)-UE (panel) pair. For example, TA1 may be required for TRP1-UE, TA2 may be required for TRP2-UE, and TA1 and TA2 may have different values. The difference in TA values as described above may occur, for example, when the distance between TRPs and UEs is relatively large. For example, when the distance between TRP1 and the UE (Dist1) is significantly greater than the distance between TRP2 and the UE (Dist2) (Dist1>>Dist2), TA1 may also be significantly greater than TA2 (TA1>>TA2).
In the Rel-16/17 standard, multi-TRP transmission may be supported as follows. Different TRPs may be distinguished based on CORESET pool index, TCI state, SRS resource indicator (SRI), SpatialRelationInfo, pathloss (PL) reference RS, etc.
Meanwhile, the different TRPs may be included in the same cell group and, therefore, may be included in the same TAG. Therefore, even when different TA values are required for each TRP, according to the current standard, only the same TA value can be applied within the TAG, so TA values for each TRP cannot be supported.
In order to compensate for the above shortcomings, the present disclosure proposes a method for supporting different TA values for each TRP even within the same TAG.
The description of TRP in this disclosure is for convenience of explanation, and may also be interpreted as terms such as panel/beam. That is, the methods proposed in this disclosure can be applied/interpreted by replacing TRP with panel/beam.
In the present disclosure, a layer 1 (L1) signaling may refer to DCI-based dynamic signaling between a base station and a UE, and a layer 2 (L2) signaling may refer to higher layer signaling based on an RRC/MAC control element (CE: control element) between a base station and a UE.
The UE may receive configuration information related to the serving cell from the base station (S1010).
Here, configuration information related to the serving cell may include information about a plurality of timing advance groups (TAGs) associated with the serving cell. Each of the plurality of TAGs associated with the serving cell may correspond to a different TA value. And, the TA value corresponding to each TAG may mean an NTA value corresponding to the TAG ID or/and an (improved) TA command value corresponding to the TAG ID.
Additionally or alternatively, configuration information related to the serving cell may include information related to multiple TRP configuration, multiple TAG configuration for the serving cell, and uplink transmission and reception in an embodiment to be described later (e.g., any one or a combination of more than one in Embodiment 1, Embodiment 1-1, Embodiment 1-2, Embodiment 1-3, and detailed Embodiments).
The UE may receive downlink control information (DCI) including first indication information and second indication information from the base station (S1020).
As an example of the present disclosure, DCI may include information for scheduling an uplink channel. And, the first indication information includes a first SRS resource indicated by a first sounding reference signal (SRS) resource indicator field included in the DCI, and the second indication information may include the second SRS resource indicated by the second SRS resource indicator field included in the DCI.
As another example of the present disclosure, DCI may include information for scheduling a downlink channel. And, the first indication information includes information related to the first uplink TCI (transmission configuration indication) state indicated by the transmission configuration indication field included in the DCI (e.g., RS corresponding to the first uplink TCI state, etc.), and the second indication information may include information related to the second uplink TCI state indicated by the TCI field (e.g., RS corresponding to the second uplink TCI state, etc.).
The UE may perform at least one of first uplink transmission or second uplink transmission based on at least one of the first indication information or the second indication information (S1030).
As an example, based on the first uplink transmission being performed using first indication information (e.g., SRS resource indicated through the first SRI field or/and the first UL TCI state, etc.), the first transmission timing of the first uplink transmission may be based on the first TA value associated with the first TAG corresponding to the first indication information among the plurality of TAGs. And, based on the second uplink transmission being performed using the second indication information (e.g., SRS resource indicated through the second SRI field or/and the second UL TCI state, etc.), the second transmission timing of the second uplink transmission may be based on the second TA value associated with the second TAG corresponding to the second indication information among the plurality of TAGs.
Based on at least one of the first uplink transmission or the second uplink transmission being performed by the UE, an offset value (e.g., gap symbol, etc.) between the first transmission timing and the second transmission timing may be defined.
As another example, based on at least one of the first uplink transmission or the second uplink transmission being performed by the UE, the UE may receive information about the offset value between the first transmission timing and the second transmission timing from the base station. Here, information about the offset value between the first transmission timing and the second transmission timing may be based on channel state information (CSI) feedback transmitted from the terminal to the base station or terminal capabilities.
As another example of the present disclosure, the UE may receive configuration information related to the first physical uplink control channel (PUCCH) group and the second PUCCH group from the base station.
Here, the first transmission timing may be based on the first TA value associated with the first TAG corresponding to the first PUCCH group among the plurality of TAGs, and the second transmission timing may be based on the second TA value associated with the second TAG corresponding to the second PUCCH group among the plurality of TAGs. And, one or more spatial relation info may be configured for at least one PUCCH resource included in each of the first PUCCH group and the second PUCCH group.
As another example of the present disclosure, the UE may receive a timing advance command for each of the first TAG and the second TAG from the base station. Here, the first TA value may be based on the SCS of the BWP for which the largest subcarrier spacing (SCS) is configured among one or more bandwidth parts (BWPs) corresponding to the first TAG. And, the second TA value may be based on the SCS of the BWP for which the largest SCS is configured among one or more BWPs corresponding to the second TAG.
As another example, the first TA value may be based on the SCS of the BWP for which the largest SCS is configured among one or more BWPs corresponding to the second TAG.
As another example, the first TA value and the second TA value may be based on the SCS of the BWP for which the largest SCS is configured among one or more BWPs corresponding to a specific TAG among the first TAG and the second TAG.
The base station may transmit configuration information related to the serving cell to the UE (S1110). Here, configuration information related to the serving cell has been described with reference to
The base station may transmit DCI including first indication information and second indication information to the UE (S1120). Additionally or alternatively, the base station may transmit control information including a timing advance command for each of a plurality of (enhanced) TAGs configured in the serving cell to the UE.
The base station may perform at least one of first uplink reception and second uplink reception based on at least one of first indication information or second indication information (S1130). The reception timing of the first uplink may be based on the first TA value associated with the first TAG corresponding to the first indication information among the plurality of TAGs, and the reception timing of the second uplink may be based on the second TA value associated with the second TAG corresponding to the second indication information among the plurality of TAGs.
Hereinafter, a method for supporting different TA values for each TRP within the same TAG and a method for supporting different TA values for each TRP through multiple TAGs will be described in detail.
Embodiment 1 relates to a method for improving a timing advance command, a method for defining sub-groups that can have different TAs within a single TAG for this, and a method for configuring/indicating the UE for TA for a specific sub-group in the improved timing advance command. In describing the present disclosure, a sub-group that may have different TAs within a single TAG is named TASG.
The TA value of the UE may be defined through
For the above-described timing advance command, MAC-CE signaling including a TASG ID (i.e., enhanced timing advance command MAC-CE) may be introduced.
Here, the enhanced timing advance command MAC-CE may include a TASG ID, a TAG ID corresponding to the TASG ID, and/or an enhanced timing advance command for resources corresponding to the TASG ID in the TAG ID.
The enhanced timing advance command MAC-CE may be defined as an absolute value for the corresponding TASG ID and/or a relative value for the TAG ID corresponding to the corresponding TASG ID.
As an example, the enhanced timing advance command MAC-CE may be configured as shown in
Additionally or alternatively, an enhanced timing advance command indicating an absolute value for a specific TASG ID may be defined/implemented as in Equation 3.
In Equation 3, NTA,i refers to the NTA value corresponding to TASG ID i, and may refer to the enhanced TA command corresponding to TASG ID i.
Additionally or alternatively, an enhanced timing advance command indicating a relative value to the TAG ID may be defined/implemented as in Equation 4.
In Equation 4, NTA,i refers to the NTA value corresponding to TASG ID i, NA,last refers to the timing advance value that the UE received last (or most recently) in response to TAG ID x corresponding to TASG ID i, and refers to an enhanced TA command value corresponding to TASG ID i. Here, ‘relative value’ may mean a relative value (e.g., NA,last+
−31) with the TA value of the TAG to which the TASG belongs.
And, in the case of a specific TASG (e.g., TASG ID 0), it may be defined to use the NTA value corresponding to the TAG as is.
Additionally or alternatively, offset values between different TASGs may be configured/indicated for the UE. The above-described offset value may be configured/indicated through RRC/MAC-CE/DCI, etc. For example, a periodic or semi-persistent offset value may be configured/indicated for different TASG ID 0 and TASG ID 1 based on the deployment of TRP/panel, etc.
For example, when applying the TA value of TA 1 to TRP 1, as the above-described offset value is configured/indicated, ‘TA value of TA 1+offset value+TA value of TA 2’ may be applied to TRP 2. Accordingly, the payload for indicating/setting the TA value for each TASG may be reduced by the offset value.
The numbers and/or ranges related to TA, TAG, TASG, offset values, etc. described above are examples and do not limit the scope of the present disclosure. Accordingly, other numbers and/or ranges may be applied to the examples described above depending on the adjustment range and/or numerology (e.g., SCS) of the TA value, etc.
Based on Example 1, when defining sub-groups that can have different TAs within a single TAG, Embodiment 1-1 relates to a method for configuring/indicating sub-groups corresponding to UL resources, and a method of transmitting by applying the TA value configured/indicated for the sub-group corresponding to each UL resource.
As an example of the present disclosure, when scheduling UL resources (e.g., PUSCH/SRS/PUCCH/PRACH, etc.) based on DCI, the TASG ID may be indicated/set according to a method described later.
Method 1: In the scheduling DCI that schedules UL resources, a DCI field/RNTI is defined to indicate the TASG ID, and the corresponding TASG ID can be explicitly indicated using the DCI field/RNTI.
Method 2: The TASG ID may be implicitly indicated based on characteristics corresponding to the scheduling DCI for scheduling UL resources.
As an example of Method 2 (Method 2-1), the corresponding TASG ID may be implicitly indicated by CORESETpoolIndex, CORESET (or, a group of CORESETs), SS (search space) set (or group of SS sets) and/or TCI state (or group of TCI states) related to scheduling DCI.
As an example, as shown in
As an example of Method 2 (Method 2-2), a SRI (or group of SRI), spatialrelationinfo (or group of spatialrelationinfo), PathlossReferenceRS (or group of PathlossReferenceRS), SRI (or group of SRI), spatialrelationinfo (or group of spatialrelationinfo), PathlossReferenceRS (or group of PathlossReferenceRS) may be indicated implicitly.
As an example of Method 2 (Method 2-3), the corresponding TASG ID may be implicitly indicated based on an SRI (or group of SRIs) mapped/connected to a plurality of SRI fields (e.g., two SRI fields).
Specifically, when an S-DCI-based M-TRP PUSCH repetitive transmission operation is performed, two SRI fields may be included in the UL grant DCI. Each SRI field may correspond to a different TRP/panel. The UE may use the TA value for TASG ID 0 corresponding to the SRI (or group of SRIs) indicated by the first SRI field of the two SRI fields. Additionally, the UE may use the TA value for TASG ID 1 corresponding to the SRI (or group of SRIs) indicated by the second SRI field of the two SRI fields.
Here, in the case of S-DCI-based M-TRP transmission operation, all scheduling information for data transmitted by M-TRP must be transmitted through one DCI. Therefore, S-DCI-based M-TRP transmission operation may be performed in an ideal BH (ideal BackHaul) environment in which dynamic cooperation between two TRPs is possible.
As an example of Method 2 (Method 2-4), the corresponding TASG ID may be implicitly indicated using the integrated TCI state framework. For example, assume that two UL TCI states are indicated through the DL DCI format. The first UL TCI state may correspond to TASG ID 1, and the second UL TCI state may correspond to TASG ID 2.
Here, the UL resource/channel/transmission occasion (TO) using the first (/second) UL TCI state may follow the TA value associated with TASG ID 1 (/2).
In addition, TO may refer to each channel transmitted at different times when multiple channels are TDM, it may refer to each channel transmitted at different frequencies/RBs when multiple channels are FDM, and it may refer to each channel transmitted to a different layer/beam/DMRS port when multiple channels are SDM. As an example, one TCI state may be mapped to each TO. When transmitting the same channel repeatedly, the transmitting end may transmit a complete DCI/data/UCI to one TO, and the receiving end may receive multiple TOs to increase the reception success rate.
As an example of Method 2 (Method 2-5), the corresponding TASG ID may be implicitly indicated based on the PUCCH resource group. For example, each PUCCH resource group 0/1 may correspond to a TA value associated with each TASG ID 1/2. Here, the PUCCH resources of each PUCCH resource group may be applied only when one spatial relationship information is configured.
As an example of Method 2 (Method 2-6), the corresponding TASG ID may be implicitly indicated based on the UE Tx timing error group (TEG) ID.
Specifically, the UE may be configured to report UE TEG according to UE capabilities. Here, the TEG may be a UE TxTEG associated with the transmission of one or more UL SRS resources for positioning purposes with a Tx timing error difference within a certain margin.
For example, a timing error group (TEG) introduced for positioning purposes may be associated with/corresponding to a panel. The mapping relationship between each TEG ID and TASG ID may be configured/indicated by the base station, but may be defined in advance.
As another example of the present disclosure, when UL resources (e.g., PUSCH/SRS/PUCCH/PRACH, etc.) are scheduled based on RRC/MAC-CE, the TASG ID may be indicated/configured according to a method described later.
Method 1: The TASG ID corresponding to the UL resource may be added to the setting value for the UL resource.
Meanwhile, Embodiment 1 and Embodiment 1-1 described a method of defining a plurality of TASGs within a single TAG and applying independent/different TA values to each TASG.
Additionally or alternatively, multiple TAG IDs may be configured in the serving cell, and independent/different TA values may be applied to different UL resources/channels (e.g., PUSCH/PUCCH/SRS/PRACH, etc.) using different TAG IDs.
Specifically, one tag-ID may be configured for one serving cell through the “ServingCellConfig information element” of the basic wireless communication system. According to the present disclosure, multiple tag-IDs may be configured in one serving cell, and different TA values according to each tag-ID may be applied to UL resources/channels.
The method according to various embodiments of the present disclosure (e.g., Embodiment 1, Embodiment 1-1, Embodiment 1-2, Embodiment 1-3) may be applied even when a plurality of TAG IDs related to different TA values are configured in the serving cell. That is, in various embodiments of the present disclosure, ‘multiple TASG IDs within a single TAG’ can be replaced with ‘multiple TAG IDs within a single serving cell’.
Specifically, according to various embodiments of the present disclosure, a method for configuring/indicating multiple TAG IDs within a single serving cell, a method of configuring/indicating a TAG ID corresponding to a UL resource (corresponding to the serving cell) when multiple TAG IDs are configured/indicated, and for each UL resource, a method of transmitting by applying the configured/indicated TA value to the TAG ID corresponding to the UL resource may be applied.
As an example, when multiple tag-Ids are configured/indicated for a serving cell, in Embodiment 1-1, the method applied to a plurality of ‘sub-groups’ is applied to a plurality of ‘tag-Id’, so that independent/Different TA values may be applied.
When multiple TASGs are defined that refer to a single TAG (i.e., when multiple TASGs are defined within a single TAG), the maximum number of TAGs (i.e. ‘maxNrofTAGs’) (e.g. 4) defined in the current standard may not be expanded, thereby reducing the impact on the standard. Additionally, signaling overhead can be reduced by defining a small range of candidate values for TASG.
Assume that multiple TAG IDs are configured/defined for a single cell. If the maximum number of TAGs defined in the current standard is maintained, extending/using the TRP concept to TAGs may result in an insufficient number of TAGs for independent TA configuration/indication. When expanding the number of TAGs, the standard impact associated with that part may increase. The procedures in the basic wireless communication system defined for each TAG can be reused by extending them to the TRP concept.
In Embodiment 1-1, a method of configuring/indicating independent/different TA values for each TASG and applying independent/different TA values based on the corresponding TASG for each UL resource was described. Here, TASG is not intended to limit the scope of the present disclosure.
Therefore, even when TASG is not explicitly defined, the function of TASG in Embodiment 1-1 may be replaced based on different TA values that are independently managed (for each TRP/panel). Additionally, different TA values may be applied to each of the different UL resources based on the embodiment of the mapping relationship between TASG and UL resources.
Additionally or alternatively, when UL resources corresponding to different TASGs (or different TAGs) are transmitted, an offset value (e.g., gap symbol/slot value, etc.) may be defined between two UL resources so that stable transmission can be performed considering the time required for panel switching between the different UL resources.
The offset value between two UL resources may be configured/indicated from the base station to the UE based on L1/L2 signaling. Additionally or alternatively, a fixed offset value between two UL resources may be defined between the base station and the UE. Additionally or alternatively, the UE may transmit a report containing information about the offset value between two UL resources (e.g., CSI feedback/UE capability report, etc.), and the base station may configure/indicate an appropriate offset value for the UE based on a report containing information about the offset value between two UL resources.
Embodiment 1-2 relates to a method of updating the timeAlignmentTimer of a TAG when receiving an improved timing advance command corresponding to a specific TASG within a specific TAG based on Embodiment 1.
Here, the ‘specific TASG’ may be configured/indicated to the UE based on L1/L2 signaling, but is not limited thereto and may be defined by fixed rules. Additionally or alternatively, the ‘specific TASG’ may be determined based on the UE's reported value (error, CSI feedback/UE capability report, etc.), or the base station may configure/indicate the ‘specific TASG’ for the UE based on the UE's reported value.
As an example, a specific TASG may be a single TASG (e.g., TASG 0 or TASG 1, etc.) within a specific TAG. As another example, a specific TASG may be a plurality of TASG groups (e.g., TASG 0/1 or TASG 0/2, etc.) within a specific TAG.
A specific TAG may be composed of one or more cell groups and/or multiple serving cells. On the other hand, in the case of M-TRP operation, a related operation (e.g., timeAlignmentTimer update operation, etc.) may be supported only in a specific cell group/serving cell among a plurality of cell groups/serving cells constituting the TAG.
Accordingly, the timeAlignmentTimer of the TAG may be updated based on the TRP that can correspond to all cell groups/serving cells constituting the TAG. For example, assume that each TRP 1/2 corresponds to each TASG 0/1 and that different TA values are managed for each TRP accordingly. Additionally, it is assumed that TRP 1 can operate in the entire cell group/all serving cells, but TRP 2 can operate only in a specific serving cell. Here, the timeAlignmentTimer of the TAG may be updated based on the timing advance command for TRP 1. When updating the timeAlignmentTimer of the TAG based on the timing advance command for TRP 2, TRP 2 should synchronize within the serving cell that cannot operate, but may not be able to do so and may operate based on an incorrect synchronization value.
Although the description of the present disclosure is based on TRP, the description of the present disclosure can be applied even when considering multi-panels of a base station/UE.
Additionally or alternatively, even if an enhanced timing advance command corresponding to a TASG within a specific TAG is received, the timeAlignmentTimer of the TAG can be updated. If any one of the plurality of TRPs corresponding to a single TAG is indicated/configured a new TA value according to the method described above, the timeAlignmentTimer may be updated assuming that the UL synchronization is correct.
Additionally or alternatively, a timeAlignmentTimer may be defined for each TASG, and the timeAlignmentTimer may be updated for each TASG depending on whether a timing advance command for the corresponding TASG is received.
In a basic wireless communication system, if the UE has multiple active UL BWPs in the same TAG, including UL BWPs on both UL carriers in the serving cell, the timing advance command value may be relative to the largest SCS among several active UL BWPs. The applicable NTA_new value for the UL BWP with lower SCS may be rounded to align with the timing advance granularity for the UL BWP with lower SCS, and at the same time, it can meet timing advance accuracy requirements.
When an enhanced timing advance command is configured/indicated for each TASG based on the Embodiment 1, Embodiment 1-3 relates to a method of defining an enhanced timing advance command value based on the SCS of the BWP corresponding to the largest SCS among one or more BWPs corresponding to each TASG.
There may be differences in the TRP (i.e. TASG) that can operate for each BWP. Therefore, in order to accurately adjust the TA value for each TRP, the TA value for each TRP may be defined based on the largest SCS for each TRP.
Referring to (b) of
Although the above description is based on TRP, the above description may be applied even when considering multi-panels of a base station/UE.
In order to apply the above-described Embodiments 1-3, the Embodiment described below may be applied as a method for distinguishing TRP/panel (i.e., TASG) from a single BWP.
Example 1: Method of explicitly configuring/indicating TRP/panel/TASG information operated/supported by BWP
Example 2: Method for implicitly configuring/indicating TRP/panel/TASG information based on configuration values for each BWP
Example 2-1: TRP/panel/TASG information may be configured/indicated based on CORESETPoolIndex. For example, if CORESETPoolIndex is not configured or CORESETPoolIndex 0 is configured, the UE/base station may recognize the BWP as a BWP corresponding to TASG ID 0. As another example, if CORESETPoolIndex 1 is configured, the UE/base station may recognize the BWP as a BWP corresponding to TASG ID 1.
Example 2-2: TRP/panel/TASG information may be configured/indicated based on the SRS resource set. For example, if the SRS resource set for the same usage is set to one or less, the UE/base station may recognize the BWP as a BWP corresponding to TASG ID 0. If two or more SRS resource sets for the same purpose are configured, the UE/base station may recognize the BWP as the BWP corresponding to TASG ID 0/1.
Example 2-3: Assume that two SRI fields are configured/included in the UL grant DCI. As an example, the UE/base station may recognize the BWP as the BWP corresponding to TASG ID 0 for the first SRI field. As another example, the UE/base station may recognize the BWP as the BWP corresponding to TASG ID 1 for the second SRI field.
Additionally or alternatively, if two or more SRS resource sets for CB/NCB purposes are configured, the UE/base station may recognize the BWP as the BWP corresponding to TASG ID 0 for the first SRS resource set. As another example, the UE/base station may recognize the BWP as the BWP corresponding to TASG ID 1 for the second SRS resource set.
Example 2-4: When multiple spatial relation information (i.e., spatialRelationInfo) is configured/activated for each PUCCH resource in BWP configuration, the UE/base station may recognize the BWP as the BWP corresponding to TASG ID 0 for the first spatialRelationInfo. As another example, the UE/base station may recognize the BWP as the BWP corresponding to TASG ID 1 for the second spatialRelationInfo.
Example 2-5: The joint TCI state framework can be used to distinguish TRP/panel in a (single) BWP. For example, if the 1 TCI state is configured for a specific BWP, the base station/UE may recognize the BWP as a BWP with TRP 1. If 2 TCI state is configured in a specific BWP, the base station/UE may recognize the BWP as a BWP of TRP 1 and at the same time as a BWP of TRP 2.
Additionally or alternatively, it may be configured/indicated/defined to apply the largest SCS for TASG ID #y to TASG ID #x as is. The method described above may be applied when the timing advance command for TASG ID #x is configured/indicated in the form of an offset based on TASG ID #y.
Additionally or alternatively, it may be defined to calculate the TA value based on the same SCS for multiple TASGs corresponding to a single TAG. For example, it may be defined to calculate the TA value according to the largest SCS for the TASG of the first TASG/lowest/highest index among a plurality of TASGs corresponding to a single TAG.
Additionally or alternatively, a reference TRP may be configured/indicated/defined, and a TA value may be applied based on the largest SCS corresponding to the reference TRP.
Additionally or alternatively, the UE may not expect a numerology larger than the numerology of the reference TRP (i.e., SCS) to be configured. Additionally or alternatively, when two TAs are configured/indicated, they can be configured/indicated/defined so that the relaxed requirements compared to the requirements are applied. Additionally or alternatively, the TA value may be defined as a value corresponding to the largest SCS among (activated) BWPs corresponding to a plurality of TRPs (e.g., two TRPs).
Here, the UE/network side is an example and may be replaced with various devices as described with reference to
In the following description, the network side may be one base station including multiple TRPs, or may be one cell including multiple TRPs. Alternatively, the network side may include a plurality of remote radio heads (RRH)/remote radio units (RRU). For example, ideal/non-ideal backhaul may be set between TRP 1 and TRP 2, which constitute the network side. In addition, the following description is based on multiple TRPs, but it can be equally extended and applied to transmission through multiple panels/cells, and can also be extended and applied to transmission through multiple RRHs/RRUs, etc.
In addition, it is described based on a “TRP” in the following description, but as described above, a “TRP” may be applied by being substituted with an expression such as a panel, an antenna array, a cell (e.g., a macro cell/a small cell/a pico cell, etc.), a TP (transmission point), a base station(gNB, etc.), etc. As described above, a TRP may be classified according to information on a CORESET group (or a CORESET pool) (e.g., a CORESET index, an ID).
For example, if one UE is configured to transmit and receive with multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one UE. Configuration of such a CORESET group (or CORESET pool) may be performed through higher layer signaling (e.g., RRC signaling, etc.).
In addition, a base station may generally mean an object which performs transmission and reception of data with a terminal. For example, the base station may be a concept which includes at least one TP(Transmission Point), at least one TRP(Transmission and Reception Point), etc. In addition, a TP and/or a TRP may include a panel, a transmission and reception unit, etc. of a base station.
The UE may receive configuration information related to the serving cell (via/using TRP1 and/or TRP2) from the network side (S1201).
The configuration information may include information related to multiple TRP settings, multiple TAG settings for serving cells, and uplink transmission and reception described in the above-mentioned proposed method (e.g., any one or a combination of more than one in Embodiment 1, Embodiment 1-1, Embodiment 1-2, and detailed Embodiments).
The configuration information may be information used to configure a cell group including one or more serving cells (e.g., CellGroupConfig, see Table 10), or the configuration information may be information used to configure MAC parameters for a cell group including one or more serving cells (e.g., MAC-CellGroupConfig, see Table 9).
In addition, the configuration information may include information about the correspondence relationship between each TASG defined/configure within the plurality of TAGs and at least one of CORESET, SS set, TCI state, SRI, spatial relationship information, PL RS, BWP, and TAG index.
As another example, the configuration information may include information about the correspondence relationship between each of the plurality of TAGs and at least one of CORESET, SS set, TCI status, SRI, spatial relation information, PL RS, BWP, and TAG index.
Additionally, the configuration information may include information about a plurality of timing advance groups (TAGs) associated with the serving cell (or a cell group including one or more serving cells) (e.g., TAG-Config).
For example, when multiple TAGs are configured in the serving cell (or a cell group including one or more serving cells), information about the plurality of TAGs may correspond to a plurality of TAG-Configs. Alternatively, when one TAG is configured in the serving cell (or a cell group including one or more serving cells) and a plurality of sub-TAGs within the one TAG are configured, the information about the plurality of TAGs may correspond to information about the plurality of sub-TAGs within one TAG-Config.
The configuration information may be transmitted through a higher layer (e.g., RRC, MAC CE). The configuration information may include information related to uplink transmission based on a configured grant (CG). Additionally, if the configuration information is defined or configured in advance, the corresponding step may be omitted.
For example, the operation of the UE (100 or 200 in
The UE may receive control information including an (improved) timing advance command (via/using TRP1 and/or TRP2) from the network side (S1202).
Here, the control information may correspond to a random access response or TA command MAC CE, but is not limited thereto. Additionally, as described above, the TA command may indicate the NTA value.
Here, control information (e.g., random access response or TA command MAC CE) may include a TA command for each TASG belonging to a plurality of TAGs, and the TA command for each TAGS may individually indicate a TA value (e.g., NTA value) used to control uplink timing adjustment.
As another example, control information (e.g., random access response or TA command MAC CE) may include a TA command for each TAG, and the TA command for each TAG may individually indicate a TA value (e.g., NTA value) used to control uplink timing adjustment.
Here, for example, the TA command may indicate a difference value for each TAG compared to the TA value used to control uplink timing adjustment for the reference TAG.
Alternatively, if the plurality of TAGs correspond to a plurality of TASGs in a single TAG configured for the serving cell (or a cell group including one or more serving cells), the TA command may indicate an offset for each TASG based on the TA value used to control uplink timing adjustment for the single TAG. Alternatively, the TA command may individually indicate a TA value (e.g., NTA value) used to control uplink timing adjustment for each TASG.
For example, the operation of the UE (100 or 200 in
The UE may perform uplink transmission (via/using TRP1 and/or TRP2) from the network side (S1203).
Here, uplink transmission may be transmitted at a transmission timing determined in consideration of the timing relationship with the downlink frame previously described in
For example, based on the uplink transmission being associated with a specific TAG among a plurality of TAGs, the transmission timing of the uplink transmission may be determined based on a TA command for the specific TAG. The method according to the examples of the present disclosure (e.g., Embodiment 1, Embodiment 1-1, Embodiment 1-2, Embodiment 1-3, or a combination of one or more of the detailed Embodiments) may be applied to determine/configure/indicate a specific TAG among a plurality of TAGs.
Alternatively, although not shown in
For example, the UE may receive a DCI scheduling uplink/downlink from the network side. Additionally, if the control information is defined or configured in advance, the corresponding step may be omitted.
Here, DCI may be transmitted to the terminal through at least one CORESET included in the CORESET pool activated by MAC CE. As another example, DCI may be transmitted to the UE through at least one CORESET activated by MAC CE.
For example, the operation of the UE (100 or 200 in
General Device to which the Present Disclosure May be Applied
In reference to
A first 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 included 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 included 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 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 included 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 included 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 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 included 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 included 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 included 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 included 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 included 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. included 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. included 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. Therefore, 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 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 M1, 3) LTE Cat M2, 4) LTE non-BL(non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M and so on and it is not limited to the above-described name. Additionally or alternatively, a wireless communication technology implemented in a wireless device 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-0009679 | Jan 2022 | KR | national |
This application is the National Stage filing under 35 U.S.C. 371 of International Application No. PCT/KR2023/000997, filed on Jan. 20, 2023, which claims the benefit of earlier filing date and right of priority to Korean Application No. 10-2022-0009679, filed on Jan. 24, 2022, the contents of which are all incorporated by reference herein in their entirety.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2023/000997 | 1/20/2023 | WO |
